[opensuse] Utterly Shocked - Suse system lockups
I have been using Suse since at least v8, and for the first time (other than when I have done something stupid) I have experienced two lock-ups where I have had to re-cycle the power to gain access again. Error seems to be Xorg related:- Feb 5 09:13:43 Desktopnew kernel: Xorg[3052]: segfault at 1b8 ip 54e4b5 sp 7fff 1fab96f0 error 4 in Xorg[400000+1c0000] Feb 5 09:13:43 Desktopnew kernel: klogd 1.4.1, ---------- state change -------- -- Feb 5 09:13:43 Desktopnew kdm[3003]: X server for display :0 terminated unexpec tedly Feb 5 09:13:43 Desktopnew gconfd (pburness-30173): Exiting Feb 5 09:13:44 Desktopnew kernel: gvfs-fuse-daemo[6705] general protection ip:7 fb1118b655a sp:7fff1b4e4ce0 error:0 in libpthread-2.8.so[7fb1118ae000+16000] Feb 5 09:13:46 Desktopnew kernel: [fglrx] Gart USWC size:192 M. Feb 5 09:13:46 Desktopnew kernel: [fglrx] Gart cacheable size:60 M. Feb 5 09:13:46 Desktopnew kernel: [fglrx] Reserved FB block: Shared offset:0, s ize:1000000 Feb 5 09:13:46 Desktopnew kernel: [fglrx] Reserved FB block: Unshared offset:7f fc000, size:4000 On reboot, I seem to have lost my desktop icons (Firefox etc. only one left is Wastebin. I did get this message on startup.... Feb 5 10:10:55 Desktop syslog-ng[1897]: syslog-ng version 1.6.12 starting Feb 5 10:10:56 Desktop console-kit-daemon[2002]: WARNING: Failed to acquire org .freedesktop.ConsoleKit Feb 5 10:10:56 Desktop console-kit-daemon[2002]: WARNING: Could not acquire nam e; bailing out Only thing I've done recently is an update of KDE to 4.2. I'm running SuSE 11.0 Any suggestions anybody? Thanks Phil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday February 5 2009, Philip Burness wrote:
I have been using Suse since at least v8, and for the first time (other than when I have done something stupid) I have experienced two lock-ups where I have had to re-cycle the power to gain access again.
Please make an attempt to control line wrapping when you excerpt log files so we don't have to reassemble them to see what's going on.
Error seems to be Xorg related:-
Feb 5 09:13:43 Desktopnew kernel: Xorg[3052]: segfault at ... Feb 5 09:13:43 Desktopnew kdm[3003]: X server for display :0 terminated unexpectedly ...
If this is the primary failure, then you can try a couple of things to achieve a more controlled shutdown: 1) CTRL+ALT-F1 (through F6) to get to a virtual console which is a simple text-mode akin to an external, serial-connected TTY. 2) Connect and log in via SSH from another computer. If you can log (use root) in with either of these approaches, you can probably effect a proper shutdown using the the "reboot" command.
On reboot, I seem to have lost my desktop icons (Firefox etc. only one left is Wastebin.
If you cannot effect a controlled shutdown / reboot, try this: In order to minimize damage to your file system when you have to shut down in the worst possible way—by cycling the power—you should use the "Magic SysRq" key combination for sync-ing your file systems. To do this, hold down ALT and Sys Rq and type an S. If you can switch virtual consoles but still can't get any response on VCs 1 through 6, you can switch to VC 10 (ALT+F10; note that you only add CTRL to the VC switch key combination when you're in an X server VC, usually VC 7) where you will see two lines printed (hopefully) when you performan Magic SysRq Sync: first "SysRq : Emergency Sync" and shortly thereafter another line with a time stamp and the words "Emergeny Sync complete". At this point you can pull the plug, as it were, on your system with a minimum of damage to your files.
...
Any suggestions anybody?
Thanks Phil
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 05 February 2009 15:06:51 Randall R Schulz wrote:
On Thursday February 5 2009, Philip Burness wrote:
I have been using Suse since at least v8, and for the first time (other than when I have done something stupid) I have experienced two lock-ups where I have had to re-cycle the power to gain access again.
Please make an attempt to control line wrapping when you excerpt log files so we don't have to reassemble them to see what's going on.
Error seems to be Xorg related:-
Feb 5 09:13:43 Desktopnew kernel: Xorg[3052]: segfault at ... Feb 5 09:13:43 Desktopnew kdm[3003]: X server for display :0 terminated unexpectedly ...
If this is the primary failure, then you can try a couple of things to achieve a more controlled shutdown:
1) CTRL+ALT-F1 (through F6) to get to a virtual console which is a simple text-mode akin to an external, serial-connected TTY.
2) Connect and log in via SSH from another computer.
If you can log (use root) in with either of these approaches, you can probably effect a proper shutdown using the the "reboot" command.
On reboot, I seem to have lost my desktop icons (Firefox etc. only one left is Wastebin.
If you cannot effect a controlled shutdown / reboot, try this:
In order to minimize damage to your file system when you have to shut down in the worst possible way—by cycling the power—you should use the "Magic SysRq" key combination for sync-ing your file systems. To do this, hold down ALT and Sys Rq and type an S.
If you can switch virtual consoles but still can't get any response on VCs 1 through 6, you can switch to VC 10 (ALT+F10; note that you only add CTRL to the VC switch key combination when you're in an X server VC, usually VC 7) where you will see two lines printed (hopefully) when you performan Magic SysRq Sync: first "SysRq : Emergency Sync" and shortly thereafter another line with a time stamp and the words "Emergeny Sync complete".
At this point you can pull the plug, as it were, on your system with a minimum of damage to your files.
...
Any suggestions anybody?
Thanks Phil
Randall Schulz Sorry about the line wrap - I'll remember for next time.
At the time I did try to switch to virtual consoles, also tried Ctrl-Alt- Backspace to restart X but no joy :-( Thanks for the tip on the file sync - will try that if it happens again. Interestingly, which I forgot to mention before, both instances occurred while I was clicking on something in Konqueror.... Best Regards Phil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2009-02-05 at 15:54 -0000, Philip Burness wrote:
On Thursday 05 February 2009 15:06:51 Randall R Schulz wrote:
Please make an attempt to control line wrapping when you excerpt log files so we don't have to reassemble them to see what's going on. ... Sorry about the line wrap - I'll remember for next time.
Not wanting to be controversial, but I prefer to see long log lines, not wrapped around. It makes easier reading for me. Different people, different preferences. I actually re-assemble wrapped long lines back to read them! >:-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmLDwAACgkQtTMYHG2NR9VghACfW+ffE746jZ4oZ/AB1HZqG6ln YB0AnAiZoftmv53CFIRKXfgqg/pfHHcI =EBx4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday February 5 2009, Carlos E. R. wrote:
On Thursday, 2009-02-05 at 15:54 -0000, Philip Burness wrote:
On Thursday 05 February 2009 15:06:51 Randall R Schulz wrote:
Please make an attempt to control line wrapping when you excerpt log files so we don't have to reassemble them to see what's going on.
I guess by "control" I just meant exercise control instead of letting your email client do its default thing. In this case, the wrapping was undesirable (as you, too, are saying) and "control" meant inhibit it.
...
Sorry about the line wrap - I'll remember for next time.
Not wanting to be controversial, but I prefer to see long log lines, not wrapped around. It makes easier reading for me.
That's what I asked him to do and I believe that's what he's saying he will do in the future.
Different people, different preferences. I actually re-assemble wrapped long lines back to read them! >:-)
As do I (and as I did with the few log file lines I quoted in my reply to Phillip's original post).
-- Cheers, Carlos E. R.
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. schreef:
On Thursday, 2009-02-05 at 15:54 -0000, Philip Burness wrote:
On Thursday 05 February 2009 15:06:51 Randall R Schulz wrote:
Please make an attempt to control line wrapping when you excerpt log files so we don't have to reassemble them to see what's going on. ... Sorry about the line wrap - I'll remember for next time.
Not wanting to be controversial, but I prefer to see long log lines, not wrapped around. It makes easier reading for me.
Different people, different preferences. I actually re-assemble wrapped long lines back to read them! >:-)
There is always pastebin :-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello, On Thu, 05 Feb 2009, Randall R Schulz wrote: [Sysrq + s]
At this point you can pull the plug, as it were, on your system with a minimum of damage to your files.
Why stop there and not use Sysrq + u and Sysrq + b? -dnh -- "I have a very firm grasp on reality! I can reach out and strangle it any time!" -- from the BSD fortune file -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 07 February 2009 12:59:21 David Haller wrote:
On Thu, 05 Feb 2009, Randall R Schulz wrote: [Sysrq + s]
At this point you can pull the plug, as it were, on your system with a minimum of damage to your files. Why stop there and not use Sysrq + u and Sysrq + b?
Or Alt+SysRq+o if you don't want to reboot. (For example, because you need to rearrange/pull hardware.) -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
On Saturday February 7 2009, David Haller wrote:
Hello,
On Thu, 05 Feb 2009, Randall R Schulz wrote: [Sysrq + s]
At this point you can pull the plug, as it were, on your system with a minimum of damage to your files.
Why stop there and not use Sysrq + u and Sysrq + b?
Why not indeed? Especially if you can't reach the reset button. Then again, "pull the plug" is clearly a metaphor that encompasses unmounting and rebooting via Magic SysRq.
-dnh
RRS -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 07 February 2009 02:27:23 pm Randall R Schulz wrote:
On Saturday February 7 2009, David Haller wrote:
Hello,
On Thu, 05 Feb 2009, Randall R Schulz wrote: [Sysrq + s]
At this point you can pull the plug, as it were, on your system with a minimum of damage to your files.
Why stop there and not use Sysrq + u and Sysrq + b?
Why not indeed? Especially if you can't reach the reset button.
Then again, "pull the plug" is clearly a metaphor that encompasses unmounting and rebooting via Magic SysRq.
All right. I'll bite......What is SysRq? Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hello, On Sat, 07 Feb 2009, Bob S wrote:
On Saturday 07 February 2009 02:27:23 pm Randall R Schulz wrote:
On Saturday February 7 2009, David Haller wrote:
Hello,
On Thu, 05 Feb 2009, Randall R Schulz wrote: [Sysrq + s]
At this point you can pull the plug, as it were, on your system with a minimum of damage to your files.
Why stop there and not use Sysrq + u and Sysrq + b?
Why not indeed? Especially if you can't reach the reset button.
Then again, "pull the plug" is clearly a metaphor that encompasses unmounting and rebooting via Magic SysRq.
All right. I'll bite......What is SysRq?
==== /usr/src/linux/Documentation/sysrq.txt ==== * What is the magic SysRq key? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ It is a 'magical' key combo you can hit which the kernel will respond to regardless of whatever else it is doing, unless it is completely locked up. [..] ==== You might have to install the kernel sources first. -dnh -- Too bloated to crash, it can only bounce gently into the limits set by the laws of physics and stop, wobbling slightly. -- unknown -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 07 February 2009 10:06:52 pm Bob S wrote:
All right. I'll bite......What is SysRq?
Google: What is SysRq http://en.wikipedia.org/wiki/System_request http://en.wikipedia.org/wiki/Magic_SysRq_key Google: "What is SysRq?" http://www.thegeekstuff.com/2008/12/safe-reboot-of-linux-using-magic-sysrq-k... When you want to use it hold Alt key first, otherwise you will be surprised with number of KSnapshot windows that will appear. Withoug Magic (Alt) key it works as a Print Screen. It is a bug, as whatever calls KSnapshot when PrtScrn is pressed should not call new instance of KSnapshot, before key is released. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Bob S wrote:
On Saturday 07 February 2009 02:27:23 pm Randall R Schulz wrote:
On Saturday February 7 2009, David Haller wrote:
Hello,
On Thu, 05 Feb 2009, Randall R Schulz wrote: [Sysrq + s]
At this point you can pull the plug, as it were, on your system with a minimum of damage to your files.
Why stop there and not use Sysrq + u and Sysrq + b?
Why not indeed? Especially if you can't reach the reset button.
Then again, "pull the plug" is clearly a metaphor that encompasses unmounting and rebooting via Magic SysRq.
All right. I'll bite......What is SysRq?
Bob S
Most keyboards have a SysRq key, which is usually used by pressing <Ctrl> Print Screen. It's not normally used in applications, but can be used for certain issues. -- Use OpenOffice.org <http://www.openoffice.org> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
James Knott wrote:
Bob S wrote:
On Saturday 07 February 2009 02:27:23 pm Randall R Schulz wrote:
On Saturday February 7 2009, David Haller wrote:
Hello,
On Thu, 05 Feb 2009, Randall R Schulz wrote: [Sysrq + s]
At this point you can pull the plug, as it were, on your system with a minimum of damage to your files.
Why stop there and not use Sysrq + u and Sysrq + b?
Why not indeed? Especially if you can't reach the reset button.
Then again, "pull the plug" is clearly a metaphor that encompasses unmounting and rebooting via Magic SysRq.
All right. I'll bite......What is SysRq?
Bob S
Most keyboards have a SysRq key, which is usually used by pressing <Ctrl> Print Screen. It's not normally used in applications, but can be used for certain issues.
James, Don't you mean Alt+PrintScreen? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
James Knott wrote:
Bob S wrote:
On Saturday 07 February 2009 02:27:23 pm Randall R Schulz wrote:
On Saturday February 7 2009, David Haller wrote:
Hello,
On Thu, 05 Feb 2009, Randall R Schulz wrote: [Sysrq + s]
At this point you can pull the plug, as it were, on your system with a minimum of damage to your files.
Why stop there and not use Sysrq + u and Sysrq + b?
Why not indeed? Especially if you can't reach the reset button.
Then again, "pull the plug" is clearly a metaphor that encompasses unmounting and rebooting via Magic SysRq.
All right. I'll bite......What is SysRq?
Bob S
Most keyboards have a SysRq key, which is usually used by pressing <Ctrl> Print Screen. It's not normally used in applications, but can be used for certain issues.
James,
Don't you mean Alt+PrintScreen?
Sorry, yes. -- Use OpenOffice.org <http://www.openoffice.org> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday February 9 2009, David C. Rankin wrote:
James Knott wrote:
...
Most keyboards have a SysRq key, which is usually used by pressing <Ctrl> Print Screen. It's not normally used in applications, but can be used for certain issues.
James,
Don't you mean Alt+PrintScreen?
Magic SysRq requires holding ALT and the key labelled "Prt Scr / Sys Rq" (where the slash is a horizontal bar and Prt Scr is above and Sys Rq is below) followed by the action key: S for sync, U for unmount, B for reboot, etc. As for activating the primary "print screen" and "system request" functions, I do know that under KDE on openSUSE 11.1, simply pressing that key (without modifiers) activates KSnapshot, suggesting that the default is the upper label (Prt Scr). Adding shift to that key does nothing by default.
-- David C. Rankin
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Philip Burness wrote:
I have been using Suse since at least v8, and for the first time (other than when I have done something stupid) I have experienced two lock-ups where I have had to re-cycle the power to gain access again.
Error seems to be Xorg related:- Feb 5 09:13:43 Desktopnew kernel: Xorg[3052]: segfault at 1b8 ip 54e4b5 sp 7fff 1fab96f0 error 4 in Xorg[400000+1c0000] Feb 5 09:13:43 Desktopnew kernel: klogd 1.4.1, ---------- state change -------- -- Feb 5 09:13:43 Desktopnew kdm[3003]: X server for display :0 terminated unexpec tedly Feb 5 09:13:43 Desktopnew gconfd (pburness-30173): Exiting Feb 5 09:13:44 Desktopnew kernel: gvfs-fuse-daemo[6705] general protection ip:7 fb1118b655a sp:7fff1b4e4ce0 error:0 in libpthread-2.8.so[7fb1118ae000+16000] Feb 5 09:13:46 Desktopnew kernel: [fglrx] Gart USWC size:192 M. Feb 5 09:13:46 Desktopnew kernel: [fglrx] Gart cacheable size:60 M. Feb 5 09:13:46 Desktopnew kernel: [fglrx] Reserved FB block: Shared offset:0, s ize:1000000 Feb 5 09:13:46 Desktopnew kernel: [fglrx] Reserved FB block: Unshared offset:7f fc000, size:4000
On reboot, I seem to have lost my desktop icons (Firefox etc. only one left is Wastebin.
I did get this message on startup.... Feb 5 10:10:55 Desktop syslog-ng[1897]: syslog-ng version 1.6.12 starting Feb 5 10:10:56 Desktop console-kit-daemon[2002]: WARNING: Failed to acquire org .freedesktop.ConsoleKit Feb 5 10:10:56 Desktop console-kit-daemon[2002]: WARNING: Could not acquire nam e; bailing out Only thing I've done recently is an update of KDE to 4.2. I'm running SuSE 11.0
Any suggestions anybody?
Thanks Phil
Phil, Memory is 100% good right? No chance of ram errors? Also, if it is a 64-bit box, you should install mcelog to eliminate any other hardware possibilities. (there is always the 4.2 uncertainty that is a possibility) It's not exactly a tried and proven desktop at this stage of the game. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 05 February 2009 12:53:17 David C. Rankin wrote:
Philip Burness wrote:
I have been using Suse since at least v8, and for the first time (other than when I have done something stupid) I have experienced two lock-ups where I have had to re-cycle the power to gain access again.
Error seems to be Xorg related:- Feb 5 09:13:43 Desktopnew kernel: Xorg[3052]: segfault at 1b8 ip 54e4b5 sp 7fff 1fab96f0 error 4 in Xorg[400000+1c0000] Feb 5 09:13:43 Desktopnew kernel: klogd 1.4.1, ---------- state change -------- -- Feb 5 09:13:43 Desktopnew kdm[3003]: X server for display :0 terminated unexpec tedly Feb 5 09:13:43 Desktopnew gconfd (pburness-30173): Exiting Feb 5 09:13:44 Desktopnew kernel: gvfs-fuse-daemo[6705] general protection ip:7 fb1118b655a sp:7fff1b4e4ce0 error:0 in libpthread-2.8.so[7fb1118ae000+16000] Feb 5 09:13:46 Desktopnew kernel: [fglrx] Gart USWC size:192 M. Feb 5 09:13:46 Desktopnew kernel: [fglrx] Gart cacheable size:60 M. Feb 5 09:13:46 Desktopnew kernel: [fglrx] Reserved FB block: Shared offset:0, s ize:1000000 Feb 5 09:13:46 Desktopnew kernel: [fglrx] Reserved FB block: Unshared offset:7f fc000, size:4000
On reboot, I seem to have lost my desktop icons (Firefox etc. only one left is Wastebin.
I did get this message on startup.... Feb 5 10:10:55 Desktop syslog-ng[1897]: syslog-ng version 1.6.12 starting Feb 5 10:10:56 Desktop console-kit-daemon[2002]: WARNING: Failed to acquire org .freedesktop.ConsoleKit Feb 5 10:10:56 Desktop console-kit-daemon[2002]: WARNING: Could not acquire nam e; bailing out Only thing I've done recently is an update of KDE to 4.2. I'm running SuSE 11.0
Any suggestions anybody?
Thanks Phil
Phil,
Memory is 100% good right? No chance of ram errors? Also, if it is a 64-bit box, you should install mcelog to eliminate any other hardware possibilities. (there is always the 4.2 uncertainty that is a possibility) It's not exactly a tried and proven desktop at this stage of the game.
If you're looking for complete stability you shouldn't be using 4.2 Don't flame me, I'm all for 4.x, it's wonderful, but I'm still using and recommending 3.5 for stability. Also, Phil, are use using an nVidia or AIT graphics card? If so are you suing the free drivers/Xorg modules or are you using the appropriate commercial drivers? JW -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 05 February 2009 19:06:10 JW wrote:
On Thursday 05 February 2009 12:53:17 David C. Rankin wrote:
Philip Burness wrote:
I have been using Suse since at least v8, and for the first time (other than when I have done something stupid) I have experienced two lock-ups where I have had to re-cycle the power to gain access again.
Error seems to be Xorg related:- Feb 5 09:13:43 Desktopnew kernel: Xorg[3052]: segfault at 1b8 ip 54e4b5 sp 7fff 1fab96f0 error 4 in Xorg[400000+1c0000] Feb 5 09:13:43 Desktopnew kernel: klogd 1.4.1, ---------- state change -------- -- Feb 5 09:13:43 Desktopnew kdm[3003]: X server for display :0 terminated unexpec tedly Feb 5 09:13:43 Desktopnew gconfd (pburness-30173): Exiting Feb 5 09:13:44 Desktopnew kernel: gvfs-fuse-daemo[6705] general protection ip:7 fb1118b655a sp:7fff1b4e4ce0 error:0 in libpthread-2.8.so[7fb1118ae000+16000] Feb 5 09:13:46 Desktopnew kernel: [fglrx] Gart USWC size:192 M. Feb 5 09:13:46 Desktopnew kernel: [fglrx] Gart cacheable size:60 M. Feb 5 09:13:46 Desktopnew kernel: [fglrx] Reserved FB block: Shared offset:0, s ize:1000000 Feb 5 09:13:46 Desktopnew kernel: [fglrx] Reserved FB block: Unshared offset:7f fc000, size:4000
On reboot, I seem to have lost my desktop icons (Firefox etc. only one left is Wastebin.
I did get this message on startup.... Feb 5 10:10:55 Desktop syslog-ng[1897]: syslog-ng version 1.6.12 starting Feb 5 10:10:56 Desktop console-kit-daemon[2002]: WARNING: Failed to acquire org .freedesktop.ConsoleKit Feb 5 10:10:56 Desktop console-kit-daemon[2002]: WARNING: Could not acquire nam e; bailing out Only thing I've done recently is an update of KDE to 4.2. I'm running SuSE 11.0
Any suggestions anybody?
Thanks Phil
Phil,
Memory is 100% good right? No chance of ram errors? Also, if it is a 64-bit box, you should install mcelog to eliminate any other hardware possibilities. (there is always the 4.2 uncertainty that is a possibility) It's not exactly a tried and proven desktop at this stage of the game.
If you're looking for complete stability you shouldn't be using 4.2
Don't flame me, I'm all for 4.x, it's wonderful, but I'm still using and recommending 3.5 for stability.
Also, Phil, are use using an nVidia or AIT graphics card? If so are you suing the free drivers/Xorg modules or are you using the appropriate commercial drivers?
JW I'm using ATI with commercial drivers. I know KDE4.2 is still relatively unstable, but I have always run latest and most risky - I have just never experienced complete freeze of my SuSE systems before. Seg faults, application freeze etc, but complete freeze nah..
Phil -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Philip Burness wrote:
On Thursday 05 February 2009 19:06:10 JW wrote:
On Thursday 05 February 2009 12:53:17 David C. Rankin wrote:
Philip Burness wrote:
I have been using Suse since at least v8, and for the first time (other than when I have done something stupid) I have experienced two lock-ups where I have had to re-cycle the power to gain access again.
Error seems to be Xorg related:- Feb 5 09:13:43 Desktopnew kernel: Xorg[3052]: segfault at 1b8 ip 54e4b5 sp 7fff 1fab96f0 error 4 in Xorg[400000+1c0000] Feb 5 09:13:43 Desktopnew kernel: klogd 1.4.1, ---------- state change -------- -- Feb 5 09:13:43 Desktopnew kdm[3003]: X server for display :0 terminated unexpec tedly Feb 5 09:13:43 Desktopnew gconfd (pburness-30173): Exiting Feb 5 09:13:44 Desktopnew kernel: gvfs-fuse-daemo[6705] general protection ip:7 fb1118b655a sp:7fff1b4e4ce0 error:0 in libpthread-2.8.so[7fb1118ae000+16000] Feb 5 09:13:46 Desktopnew kernel: [fglrx] Gart USWC size:192 M. Feb 5 09:13:46 Desktopnew kernel: [fglrx] Gart cacheable size:60 M. Feb 5 09:13:46 Desktopnew kernel: [fglrx] Reserved FB block: Shared offset:0, s ize:1000000 Feb 5 09:13:46 Desktopnew kernel: [fglrx] Reserved FB block: Unshared offset:7f fc000, size:4000
On reboot, I seem to have lost my desktop icons (Firefox etc. only one left is Wastebin.
I did get this message on startup.... Feb 5 10:10:55 Desktop syslog-ng[1897]: syslog-ng version 1.6.12 starting Feb 5 10:10:56 Desktop console-kit-daemon[2002]: WARNING: Failed to acquire org .freedesktop.ConsoleKit Feb 5 10:10:56 Desktop console-kit-daemon[2002]: WARNING: Could not acquire nam e; bailing out Only thing I've done recently is an update of KDE to 4.2. I'm running SuSE 11.0
Any suggestions anybody?
Thanks Phil Phil,
Memory is 100% good right? No chance of ram errors? Also, if it is a 64-bit box, you should install mcelog to eliminate any other hardware possibilities. (there is always the 4.2 uncertainty that is a possibility) It's not exactly a tried and proven desktop at this stage of the game. If you're looking for complete stability you shouldn't be using 4.2
Don't flame me, I'm all for 4.x, it's wonderful, but I'm still using and recommending 3.5 for stability.
Also, Phil, are use using an nVidia or AIT graphics card? If so are you suing the free drivers/Xorg modules or are you using the appropriate commercial drivers?
JW I'm using ATI with commercial drivers. I know KDE4.2 is still relatively unstable, but I have always run latest and most risky - I have just never experienced complete freeze of my SuSE systems before. Seg faults, application freeze etc, but complete freeze nah..
Phil
Phil, When you say latest do you mean the 8-12 (ver. 8.561) release or the 9-1 (ver. 8.573) release? The 8-12 release has a known broken 3D problem, the 9-1 release has lingering performance problems with some users reporting that they cannot even load the driver. There is some indication that the 9-2 driver may be better from 1 feeback from a 9-2b tester. In the interim, I'd switch to the 'radeon' driver (radeon.ko) and see if your problem continue. 'sax2 -r -m 0=radeon' should do it. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am Freitag, 6. Februar 2009 10:06:40 schrieb Philip Burness:
Memory is 100% good right? No chance of ram errors? Also, if it is a 64-bit box, you should install mcelog to eliminate any other hardware possibilities. (there is always the 4.2 uncertainty that is a possibility) It's not exactly a tried and proven desktop at this stage of the game.
If I am not mistaken, you did not yet answer the question whether you tested your RAM and are sure that there are no memory errors. The memory test is on every opensuse DVD, so you just need to boot from it and select it from the boot menu. Further you could check whether all cards and modules (RAM) are fit tight into their slots. If one of the latter is lose you get random lockups. Sven -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I have a similar Xorg lockout requiring hard reboot. It happens about once a day. Symptoms: * processing: system first slows to a crawl * keyboard: auto-repeat function usually stops working first * keyboard: eventually locks up entirely * mouse: often locks up as well * sound: sometimes get a continuous beep or alarm-like wail * kde: applications refuse to close normally * kde: receive "not responding" prompt box * kde: forced termination sometimes has no effect * kde: if applications do terminate, wallpaper is blank -- no icons * command-line shutdown: * : sometimes it is possible to enter a shutdown command * : shutdown issues "system shutdown message", then hangs I've created a bash file that uses ps to dump system status every 3 seconds. Would output from that be helpful? Are there better diagnostic tools available? If so, what are they? Is this a known bug? I'm told that my 10.2 system is no longer supported. But before I upgrade, I want to know whether I will get the same problem in 11.0. If the problem has not been previously identified and solved in 10.2, then it seems to me that there is a good chance that it persists into 11.0, so I am once again attempting to inform the community. My two previous attempts are: http://lists.opensuse.org/opensuse/2009-01/msg04811.html -- 30 Jan 2009 http://lists.opensuse.org/opensuse/2008-12/msg01873.html -- 23 Dec 2008 --- On Thu, 2/5/09, Philip Burness <pburness@btopenworld.com> wrote:
From: Philip Burness <pburness@btopenworld.com> Subject: [opensuse] Utterly Shocked - Suse system lockups To: opensuse@opensuse.org Date: Thursday, February 5, 2009, 9:51 AM I have been using Suse since at least v8, and for the first time (other than when I have done something stupid) I have experienced two lock-ups where I have had to re-cycle the power to gain access again.
Error seems to be Xorg related:- Feb 5 09:13:43 Desktopnew kernel: Xorg[3052]: segfault at 1b8 ip 54e4b5 sp 7fff 1fab96f0 error 4 in Xorg[400000+1c0000] Feb 5 09:13:43 Desktopnew kernel: klogd 1.4.1, ---------- state change -------- -- Feb 5 09:13:43 Desktopnew kdm[3003]: X server for display :0 terminated unexpec tedly Feb 5 09:13:43 Desktopnew gconfd (pburness-30173): Exiting Feb 5 09:13:44 Desktopnew kernel: gvfs-fuse-daemo[6705] general protection ip:7 fb1118b655a sp:7fff1b4e4ce0 error:0 in libpthread-2.8.so[7fb1118ae000+16000] Feb 5 09:13:46 Desktopnew kernel: [fglrx] Gart USWC size:192 M. Feb 5 09:13:46 Desktopnew kernel: [fglrx] Gart cacheable size:60 M. Feb 5 09:13:46 Desktopnew kernel: [fglrx] Reserved FB block: Shared offset:0, s ize:1000000 Feb 5 09:13:46 Desktopnew kernel: [fglrx] Reserved FB block: Unshared offset:7f fc000, size:4000
On reboot, I seem to have lost my desktop icons (Firefox etc. only one left is Wastebin.
I did get this message on startup.... Feb 5 10:10:55 Desktop syslog-ng[1897]: syslog-ng version 1.6.12 starting Feb 5 10:10:56 Desktop console-kit-daemon[2002]: WARNING: Failed to acquire org .freedesktop.ConsoleKit Feb 5 10:10:56 Desktop console-kit-daemon[2002]: WARNING: Could not acquire nam e; bailing out Only thing I've done recently is an update of KDE to 4.2. I'm running SuSE 11.0
Any suggestions anybody?
Thanks Phil
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu February 5 2009 8:51:51 am Philip Burness wrote:
I have been using Suse since at least v8, and for the first time (other than when I have done something stupid) I have experienced two lock-ups where I have had to re-cycle the power to gain access again.
It took me a while to get caught up on mail, but I'd like to add to this. I experience lockups every time I run KDE4. They happen whether or not I have compositing turned on. This has happened ever since the first or second build after 4.2 was released - and yes, it's still 4.2. After the lockup, there is absolutely no response from the computer whatsoever, including when I've tried the SysRq combinations after I found out about them here. I watch the hard drive light always after a lockup and it's dead until I do a hard reset. My RAM is okay. I tried booting the rescue thing from the install disk and running fsck, but it complains about being unable to create a bad blocks file and I'm not sure how to get around that. Still, I doubt that this is the problem because no other window manager does this (having tried WindowMaker, IceWM, Twindy, KDE3 and fvwm2 - all running mostly KDE4 applications). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2009-02-09 at 17:36 -0600, Constantinos Maltezos wrote:
I experience lockups every time I run KDE4. They happen whether or not I have compositing turned on. This has happened ever since the first or second build ... My RAM is okay. I tried booting the rescue thing from the install disk and running fsck, but it complains about being unable to create a bad blocks file and I'm not sure how to get around that.
Huh-oh... if you do have bad blocks, that's a "bad thing". It might only affect files belonging to kde4. Chance! - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmQzHUACgkQtTMYHG2NR9UNIgCfdVzaNiW0HyGAmcC5duZ+nVeK /asAnjuULKqhXi+QQJFR3Oge5BmN9mpO =uWvS -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon February 9 2009 6:38:11 pm Carlos E. R. wrote:
On Monday, 2009-02-09 at 17:36 -0600, Constantinos Maltezos wrote:
My RAM is okay. I tried booting the rescue thing from the install disk and running fsck, but it complains about being unable to create a bad blocks file and I'm not sure how to get around that.
Huh-oh... if you do have bad blocks, that's a "bad thing". It might only affect files belonging to kde4. Chance!
Yeah, which is why I'm trying to figure out how to run it to where it writes bad blocks to a file. I'm not sure what it wants. I was specifying a file on the virtual RAM drive - does it want a physical drive to write to? My file system is reiserfs, by the way. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon February 9 2009 10:45:46 pm Constantinos Maltezos wrote:
On Mon February 9 2009 6:38:11 pm Carlos E. R. wrote:
On Monday, 2009-02-09 at 17:36 -0600, Constantinos Maltezos wrote:
My RAM is okay. I tried booting the rescue thing from the install disk and running fsck, but it complains about being unable to create a bad blocks file and I'm not sure how to get around that.
Huh-oh... if you do have bad blocks, that's a "bad thing". It might only affect files belonging to kde4. Chance!
Yeah, which is why I'm trying to figure out how to run it to where it writes bad blocks to a file. I'm not sure what it wants. I was specifying a file on the virtual RAM drive - does it want a physical drive to write to? My file system is reiserfs, by the way.
Okay, a quick update on this: I still haven't figured out how to specify a bad blocks file to fsck.reiserfs without it complaining, but I was thinking about the times I updated through yast. If some files of some package(s) for KDE4 that are accessed enough to cause a lockup every time KDE4 is run are written on some bad blocks, wouldn't yast complain when I tried to update them? Anyway, aside from that, I logged into KDE3 for the first time in a long time (I thought I had used it more recently than that) and after about seven minutes, it locked up. It seems to me that the only common thread is compositing (I have those more primitive effects KDE3 has available turned on, even though I use kwin). This made me suspect my video card. I did indeed experience video troubles when trying to start games (UT2004 and Descent 3) from WindowMaker. After, I was successfully able to launch Doom 3 and I loaded a saved game and let it sit for a few hours - no lockup. Could it be that KDE4 and KDE3 with accelerated graphical features would lock my system up but a game as graphically intensive as Doom 3 would not? I would try Compiz if I could get it to work, but I can't seem to. It occurs to me that the gpu is overheating, but wouldn't it overheat with Doom 3 worse? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 12 February 2009 12:02:38 am Constantinos Maltezos wrote:
Could it be that KDE4 and KDE3 with accelerated graphical features would lock my system up but a game as graphically intensive as Doom 3 would not? I would try Compiz if I could get it to work, but I can't seem to. It occurs to me that the gpu is overheating, but wouldn't it overheat with Doom 3 worse?
Could be graphic driver issues. What adapter you are using? lspci hwinfo --gfxcard output would help to begin troubleshooting. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu February 12 2009 12:02:38 am Constantinos Maltezos wrote:
Could it be that KDE4 and KDE3 with accelerated graphical features would lock my system up but a game as graphically intensive as Doom 3 would not? I would try Compiz if I could get it to work, but I can't seem to. It occurs to me that the gpu is overheating, but wouldn't it overheat with Doom 3 worse?
Okay, here we are almost a month later. I'm still using WindowMaker, which is cool, but I really miss my KDE. So you don't have to read back through, when I use KDE4 (and a few times when I've used KDE3), my system doesn't run for very long before it completely locks up - no key sequence or anything else will get it to do anything until I do a hard reset. I looked for anything that would give me a clue, including the log files. I checked the last backup of /var/log/messages and didn't see anything interesting... until now. This time, I looked at more than one of those backups and they all end with the same thing, this: Feb 16 21:46:11 goddamnmaddog syslog-ng[2062]: SIGHUP received, restarting syslog-ng Feb 16 21:46:11 goddamnmaddog kernel: hub 6-0:1.0: unable to enumerate USB device on port 4 Feb 16 21:46:11 goddamnmaddog kernel: klogd 1.4.1, ---------- state change ---------- Feb 16 21:46:12 goddamnmaddog kernel: hub 6-0:1.0: unable to enumerate USB device on port 4 Sorry about the word wrap - I figure it's not too bad. I'll resend with word wrap turned off if anyone asks. Around the beginning of the year, I bought a USB card because the built-in USB has gotten flaky. The addition of the card not only gave me these new ports, but it made the flaky built-in stuff work right, as well. Might it also have caused this problem? When KDE asks the system if anything's been plugged in, might it cause the system to freak out with my card? I'm thinking about removing or disabling something, but I'd like to know if there's a way for me to figure out what's going on before I start ripping stuff out of my box. Does anyone have any suggestions? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2009-03-08 at 15:00 -0600, Constantinos Maltezos wrote:
Feb 16 21:46:11 goddamnmaddog kernel: hub 6-0:1.0: unable to enumerate USB device on port 4
It might be whatever is plugged there, not the card. You can try swaping the devices, and see if it then complains about port 3 or whatever, instead. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkm2bScACgkQtTMYHG2NR9Ur9wCfdZSWrJjlxuMx1axWfMU+9u4q Hx8AniB497ZeVTMwXGoUbt8NFYpcLRGz =dxow -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 09 February 2009 05:36:37 pm Constantinos Maltezos wrote:
On Thu February 5 2009 8:51:51 am Philip Burness wrote:
I have been using Suse since at least v8, and for the first time (other than when I have done something stupid) I have experienced two lock-ups where I have had to re-cycle the power to gain access again.
It took me a while to get caught up on mail, but I'd like to add to this.
I experience lockups every time I run KDE4. They happen whether or not I have compositing turned on. .... ... no other window manager does this (having tried WindowMaker, IceWM, Twindy, KDE3 and fvwm2 - all running mostly KDE4 applications).
What graphic adapter you have? If ATI/Nvidia try running opensource drivers. -- Regards, Rajko -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Mon February 9 2009 6:57:00 pm Rajko M. wrote:
What graphic adapter you have? If ATI/Nvidia try running opensource drivers.
I use nVidia. It just so happens that after trying to upgrade my driver there (mentioned in an email posted here earlier), it changed my xorg.conf to use the nv driver. I got the same outcome from that. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (14)
-
Amedee Van Gasse -
Bob S -
Boyd Stephen Smith Jr. -
Carlos E. R. -
Charles Obler -
Constantinos Maltezos -
David C. Rankin -
David Haller -
James Knott -
JW -
Philip Burness -
Rajko M. -
Randall R Schulz -
Sven Burmeister