1 |
My system also freezes completely, and at unpredictble intervals, |
2 |
although only when using KDE or gnome. So, my thinking was that I had |
3 |
a bad power supply, or bad memory somwhere, but then discovered that I |
4 |
can run fluxbox/wmaker without any problems, although the KDE apps crash |
5 |
if I run them within fluxbox/wmaker. |
6 |
|
7 |
I ran emerge sync && emerge -pue kde, then re-installed the whole mess |
8 |
as if from an empty tree, and I get the same results. |
9 |
|
10 |
Some details: |
11 |
AT1 Radeon 8500, dual AMD MP CPUs, xorg 6.8, 2.6.7 kernel, using radeon |
12 |
driver with 3D acceleration. 1GB RAM and using NPTL. |
13 |
|
14 |
|
15 |
Sound familiar to anyone? |
16 |
Lindsay Haisley wrote: |
17 |
> In my experience, system freezes are hardware-related, sometimes failed |
18 |
> memory, or something else that throws the system completely off-track. One |
19 |
> of the more common and less obvious culprits is a seriously unclean power |
20 |
> from a failing power supply. It's difficult to troubleshoot this kind of |
21 |
> thing that happens unpredictably, but it might be instructive to kill X and |
22 |
> do a bit of stress testing from the cmd line, such as: |
23 |
> |
24 |
> # while [ 1 ]; do emerge openoffice; done |
25 |
> |
26 |
> [or some other large package that's heavy on i/o] |
27 |
> |
28 |
> Let this run for a few hours, days or whatever is the nominal time between |
29 |
> lockups and see if the problem recurs, which will eliminate X if it does |
30 |
> (but unfortunately not necessarily implicate X if it doesn't). |
31 |
> |
32 |
> I'm sure there are others who can suggest better stress-tests. |
33 |
> |
34 |
> Thus spake A. Gabriel W. Daleson on Sun, Oct 24, 2004 at 04:02:55PM CDT |
35 |
> |
36 |
>> I'm not sure if this is something serious or merely me being |
37 |
>>incompetent at configuring X, but whenever I've run X on this Dell Inspiron |
38 |
>>XPS with a Radeon 9800 Mobility, the entire system locks up. It doesn't seem |
39 |
>>to follow any pattern - sometimes it's within the first five minutes, other |
40 |
>>times nearly an hour. |
41 |
>> |
42 |
>> The first time this happened, it destroyed the LCD, so I suspected |
43 |
>>refresh rates were set wrong; changing the HorizSync to 75 and VertRefresh |
44 |
>>to 60 hasn't helped. |
45 |
>> |
46 |
>> I've tried this with both the radeon driver included with X and |
47 |
>>ATI's proprietary driver, as well as both gentoo-sources and |
48 |
>>development-sources and X.org 6.7.0 and 6.8.0. |
49 |
>> |
50 |
>> I've had two lockups since then, but the display's still working. |
51 |
>> |
52 |
>> Does anyone have any ideas? Thanks for any help. |
53 |
>> |
54 |
>> Gabe. |
55 |
>> |
56 |
>> |
57 |
>>-- |
58 |
>>gentoo-desktop@g.o mailing list |
59 |
>> |
60 |
> |
61 |
> |
62 |
|
63 |
|
64 |
-- |
65 |
gentoo-desktop@g.o mailing list |