1 |
Is the system freeze-up total, or is the screen and HID input (mouse, |
2 |
keyboard) simply frozen? If the box is on a network, try pinging it from |
3 |
another box and see if it and see if it responds, or if it's running any |
4 |
TCP/IP services, try connecting to them. |
5 |
|
6 |
I've had lockups on my system too, affecting the keyboard, mouse and screen, |
7 |
but they only happen once every month or two, and I've not worried about it. |
8 |
This is better performance than MS Windows, for sure ;-) They usually happen |
9 |
overnight while the box is on and running a screensaver. |
10 |
|
11 |
Thus spake steve fox on Sun, Oct 24, 2004 at 05:25:53PM CDT |
12 |
> My system also freezes completely, and at unpredictble intervals, |
13 |
> although only when using KDE or gnome. So, my thinking was that I had |
14 |
> a bad power supply, or bad memory somwhere, but then discovered that I |
15 |
> can run fluxbox/wmaker without any problems, although the KDE apps crash |
16 |
> if I run them within fluxbox/wmaker. |
17 |
> |
18 |
> I ran emerge sync && emerge -pue kde, then re-installed the whole mess |
19 |
> as if from an empty tree, and I get the same results. |
20 |
> |
21 |
> Some details: |
22 |
> AT1 Radeon 8500, dual AMD MP CPUs, xorg 6.8, 2.6.7 kernel, using radeon |
23 |
> driver with 3D acceleration. 1GB RAM and using NPTL. |
24 |
> |
25 |
> |
26 |
> Sound familiar to anyone? |
27 |
> Lindsay Haisley wrote: |
28 |
> >In my experience, system freezes are hardware-related, sometimes failed |
29 |
> >memory, or something else that throws the system completely off-track. One |
30 |
> >of the more common and less obvious culprits is a seriously unclean power |
31 |
> >from a failing power supply. It's difficult to troubleshoot this kind of |
32 |
> >thing that happens unpredictably, but it might be instructive to kill X and |
33 |
> >do a bit of stress testing from the cmd line, such as: |
34 |
> > |
35 |
> ># while [ 1 ]; do emerge openoffice; done |
36 |
> > |
37 |
> >[or some other large package that's heavy on i/o] |
38 |
> > |
39 |
> >Let this run for a few hours, days or whatever is the nominal time between |
40 |
> >lockups and see if the problem recurs, which will eliminate X if it does |
41 |
> >(but unfortunately not necessarily implicate X if it doesn't). |
42 |
> > |
43 |
> >I'm sure there are others who can suggest better stress-tests. |
44 |
> > |
45 |
> >Thus spake A. Gabriel W. Daleson on Sun, Oct 24, 2004 at 04:02:55PM CDT |
46 |
> > |
47 |
> >> I'm not sure if this is something serious or merely me being |
48 |
> >>incompetent at configuring X, but whenever I've run X on this Dell |
49 |
> >>Inspiron |
50 |
> >>XPS with a Radeon 9800 Mobility, the entire system locks up. It doesn't |
51 |
> >>seem |
52 |
> >>to follow any pattern - sometimes it's within the first five minutes, |
53 |
> >>other |
54 |
> >>times nearly an hour. |
55 |
> >> |
56 |
> >> The first time this happened, it destroyed the LCD, so I suspected |
57 |
> >>refresh rates were set wrong; changing the HorizSync to 75 and VertRefresh |
58 |
> >>to 60 hasn't helped. |
59 |
> >> |
60 |
> >> I've tried this with both the radeon driver included with X and |
61 |
> >>ATI's proprietary driver, as well as both gentoo-sources and |
62 |
> >>development-sources and X.org 6.7.0 and 6.8.0. |
63 |
> >> |
64 |
> >> I've had two lockups since then, but the display's still working. |
65 |
> >> |
66 |
> >> Does anyone have any ideas? Thanks for any help. |
67 |
> >> |
68 |
> >> Gabe. |
69 |
> >> |
70 |
> >> |
71 |
> >>-- |
72 |
> >>gentoo-desktop@g.o mailing list |
73 |
> >> |
74 |
> > |
75 |
> > |
76 |
> |
77 |
> |
78 |
> -- |
79 |
> gentoo-desktop@g.o mailing list |
80 |
> |
81 |
|
82 |
-- |
83 |
Lindsay Haisley | "Fighting against human | PGP public key |
84 |
FMP Computer Services | creativity is like | available at |
85 |
512-259-1190 | trying to eradicate | <http://pubkeys.fmp.com> |
86 |
http://www.fmp.com | dandelions" | |
87 |
| (Pamela Jones) | |
88 |
|
89 |
-- |
90 |
gentoo-desktop@g.o mailing list |