The last time I had a system lock-out was several weeks ago, and just today, I experienced another.
I tried to access the system locally via the keyboard, no response. Mouse, same. Remotely, not responding, all remote connections, ports, etc. Not there.
Darn! hard reboot.
So, I looked at the system messages logs:
Aug 29 01:08:11 gold pulseaudio[7453]: alsa-sink.c: Increasing wakeup watermark to 125.99 ms Aug 29 10:14:32 gold kernel: imklog 3.22.1, log source = /proc/kmsg started.
Yep, there is a 9 hour gap of no activity. It looks like the system went to sleep just like I did when it was time for bed. I got up this morning, but my system never woke up. Lazy basta... oh, sorry. It died.
Well, what else can I do, there seems to be no way to figure out what is going on, if there is no record of it!
Dan .
On 08/29/2009 01:39 PM, Daniel B. Thurman wrote:
The last time I had a system lock-out was several weeks ago, and just today, I experienced another.
I tried to access the system locally via the keyboard, no response. Mouse, same. Remotely, not responding, all remote connections, ports, etc. Not there.
Darn! hard reboot.
So, I looked at the system messages logs:
Aug 29 01:08:11 gold pulseaudio[7453]: alsa-sink.c: Increasing wakeup watermark to 125.99 ms Aug 29 10:14:32 gold kernel: imklog 3.22.1, log source = /proc/kmsg started.
Yep, there is a 9 hour gap of no activity. It looks like the system went to sleep just like I did when it was time for bed. I got up this morning, but my system never woke up. Lazy basta... oh, sorry. It died.
Well, what else can I do, there seems to be no way to figure out what is going on, if there is no record of it!
It's locked up on me about a half dozen or so times in the past week. Additionally, the box suspends at random times[1] (it's not a laptop) and cannot be brought back out of it.
Also, Thunderbird and Firefox occasionally cannot display certain images properly[2] and Thunderbird crashes if I try to paste text that's been copied from either the terminal or jEdit. Yup, lots of nasty bugginess. I don't know what else to check and don't think I can deal with this much longer.
[1] https://www.redhat.com/archives/fedora-list/2009-August/msg02112.html [2] https://www.redhat.com/archives/fedora-list/2009-August/msg01845.html
On Sat, 29 Aug 2009 14:55:52 -0400 brian fedora@logi.ca wrote:
On 08/29/2009 01:39 PM, Daniel B. Thurman wrote:
The last time I had a system lock-out was several weeks ago, and just today, I experienced another.
It's locked up on me about a half dozen or so times in the past week. Additionally, the box suspends at random times[1] (it's not a laptop) and cannot be brought back out of it.
When F11 first came out I experienced lockups with FF 3.5 (and only FF) about 1 in 3 or 4 times when I was starting it. I started compiling my own kernels, elmininating all the functionality I don't use, tuning other parameters to different values than the default Fedora kernel, optimizing for my hardware and use case. Since then I haven't had a lockup.
Moral of the story - I think some of the pieces in the kernel don't play nice together.
No hard evidence for the suspicion, strictly anecdotal. I now run the official kernel only long enough to download the src.rpm and compile a custom kernel so I don't know if the problem is still there.
Daniel B. Thurman wrote:
The last time I had a system lock-out was several weeks ago, and just today, I experienced another.
I tried to access the system locally via the keyboard, no response. Mouse, same. Remotely, not responding, all remote connections, ports, etc. Not there.
Have you tested your memory?
Which graphics card are you running? Which driver? Which screensavers, come to that – if the system is locking up while you aren’t at it, then there’s a good chance that a 3D screensaver is exercising part of the driver that hasn’t been debugged properly.
Hope this helps,
James.
On 09/03/2009 10:28 AM, James Wilkinson wrote:
Daniel B. Thurman wrote:
The last time I had a system lock-out was several weeks ago, and just today, I experienced another.
I tried to access the system locally via the keyboard, no response. Mouse, same. Remotely, not responding, all remote connections, ports, etc. Not there.
Have you tested your memory?
yes
Which graphics card are you running?
Onboard Intel 945G/GZ chipset
Which driver?
Latest from Fedora updates.
Which screensavers,
Gnome screen saver - blank
come to that – if the system is locking up while you aren’t at it, then there’s a good chance that a 3D screensaver is exercising part of the driver that hasn’t been debugged properly.
With a blank screen?
Hope this helps,
James.
On Thursday 03 September 2009 23:51:50 Daniel B. Thurman wrote:
On 09/03/2009 10:28 AM, James Wilkinson wrote:
Daniel B. Thurman wrote:
The last time I had a system lock-out was several weeks ago, and just today, I experienced another.
Which graphics card are you running?
Onboard Intel 945G/GZ chipset
Which driver?
Latest from Fedora updates.
I believe the last two lines explain the issue. Search the list archives and the internet --- the Intel graphics drivers became more than unusable, since Fedora 10 time (basically, with the transition from XAA to EXA). The situation has improved significantly by now, in the sense that today the driver locks up on a monthly basis rather than every 15 minutes, and the luckiest people do not experience any more lockups at all.
The Intel drivers are going through a major code rewriting, and at some point in future may become stable enough again. Until then, consider yourself lucky enough if it hangs only once per month. Reboot and continue.
You also might try to force the old, XAA acceleration, or disable 3D acceleration completely, in xorg.conf. This might eliminate the lockups, while at the same time degrade performance of the graphics card (and Intel doesn't have too much performance to begin with, anyway...).
Or you may look inside /var/log/Xorg.0.log* to see if there is any backtrace of X or similar, and work from there.
Of course, maybe I am barking up the wrong tree, it is possible that the problem lies elsewhere. But given that you have Intel graphics, X logs are the first place to look for signs of trouble.
HTH, :-) Marko
On 09/03/2009 05:17 PM, Marko Vojinovic wrote:
On Thursday 03 September 2009 23:51:50 Daniel B. Thurman wrote:
On 09/03/2009 10:28 AM, James Wilkinson wrote:
Daniel B. Thurman wrote:
The last time I had a system lock-out was several weeks ago, and just today, I experienced another.
Which graphics card are you running?
Onboard Intel 945G/GZ chipset
Which driver?
Latest from Fedora updates.
I believe the last two lines explain the issue. Search the list archives and the internet --- the Intel graphics drivers became more than unusable, since Fedora 10 time (basically, with the transition from XAA to EXA). The situation has improved significantly by now, in the sense that today the driver locks up on a monthly basis rather than every 15 minutes, and the luckiest people do not experience any more lockups at all.
The Intel drivers are going through a major code rewriting, and at some point in future may become stable enough again. Until then, consider yourself lucky enough if it hangs only once per month. Reboot and continue.
You also might try to force the old, XAA acceleration, or disable 3D acceleration completely, in xorg.conf. This might eliminate the lockups, while at the same time degrade performance of the graphics card (and Intel doesn't have too much performance to begin with, anyway...).
Or you may look inside /var/log/Xorg.0.log* to see if there is any backtrace of X or similar, and work from there.
Of course, maybe I am barking up the wrong tree, it is possible that the problem lies elsewhere. But given that you have Intel graphics, X logs are the first place to look for signs of trouble.
HTH, :-) Marko
Since I have had a hung system every morning that I wake up, I have tested to see if I could stop this problem by not allowing certain applications to be running.
Keep in mind, that my F11 is heavily loaded with (almost everything), but stock programs.
I turned off Banshee, Amarok, Firefox, Thunderbird, and left my gnome screensaver running and set it to 'random'.
It did not hang overnight.
It's a bit early as I have further testing to do and try to 'divide & conquer' to see which applications is causing this problem.
Dan
-
brian -
Dan Thurman -
James Wilkinson -
Marko Vojinovic -
stan