Occassional freezing on open suse 10
Hello, I've been using open suse for a couple of days now, and I feel there are some stability issues on my PC. The PC locks up occasionally when logging in or out of a KDE session. The mouse curser moves, but no access to keyboard, and I cannot switch to a terminal using alt-F switch. I also found the system locked up after I let it running overnight, only see a static picture of the screensaver on, with no response. I have applied all the latest updates. My hardware is AMD 2800, 512 MB RAM, Nvidia2 based graphics card, and a Maudio 7.1 sound card. I wish to believe this a hardware problem, but XP runs smooth on this machine. Is there any way to lookup cause of crash in any log files after a reboot? Thanks, Shibu
On Tuesday 29 November 2005 09:57, Shibu Basheer wrote:
Hello,
I've been using open suse for a couple of days now, and I feel there are some stability issues on my PC. The PC locks up occasionally when logging in or out of a KDE session. The mouse curser moves, but no access to keyboard, and I cannot switch to a terminal using alt-F switch. I also found the system locked up after I let it running overnight, only see a static picture of the screensaver on, with no response. I have applied all the latest updates.
My hardware is AMD 2800, 512 MB RAM, Nvidia2 based graphics card, and a Maudio 7.1 sound card.
I wish to believe this a hardware problem, but XP runs smooth on this machine. Is there any way to lookup cause of crash in any log files after a reboot?
Thanks, Shibu ========
Sure, /var/log/messages should give you something to start with on system mishaps. Lee
Hi :) BandiPat wrote:
On Tuesday 29 November 2005 09:57, Shibu Basheer wrote:
Hello,
I've been using open suse for a couple of days now, and I feel there are some stability issues on my PC. The PC locks up occasionally when logging in or out of a KDE session. The mouse curser moves, but no access to keyboard, and I cannot switch to a terminal using alt-F switch. I also found the system locked up after I let it running overnight, only see a static picture of the screensaver on, with no response. I have applied all the latest updates.
My hardware is AMD 2800, 512 MB RAM, Nvidia2 based graphics card, and a Maudio 7.1 sound card.
I wish to believe this a hardware problem, but XP runs smooth on this machine. Is there any way to lookup cause of crash in any log files after a reboot?
Thanks, Shibu ========
Sure, /var/log/messages should give you something to start with on system mishaps.
Check out /var/log/XFree86.0.log too. Rafa -- Rafa Grimán Systems Engineer Silicon Graphics Spain Santa Engracia , 120 - Planta Baja 28003 Madrid, Spain Tel: +34 91 3984200 Fax: +34 91 3984201 Móvil: +34 628 117 940 http://www.sgi.com
Hello, Am Dienstag, 29. November 2005 15:57 schrieb Shibu Basheer:
I've been using open suse for a couple of days now, and I feel there are some stability issues on my PC. The PC locks up occasionally when logging in or out of a KDE session. The mouse curser moves, but no access to keyboard, and I cannot switch to a terminal using alt-F switch.
If you are in a X session currently, you need Ctrl additionally, so try ctrl-alt-f1 ;-)
I also found the system locked up after I let it running overnight, only see a static picture of the screensaver on, with no response.
If you have a second machine: can you ping the "frozen" machine? Can you ssh into it (given ssh is enabled and not blocked by firewall)?
I wish to believe this a hardware problem, but XP runs smooth on this machine. Is there any way to lookup cause of crash in any log files after a reboot?
You already heard about several files in /var/log/ ;-) If you have some seconds between logging in and the freeze, you can also press ctrl-alt-f10 directly after login and check error messages on the console - even if they can't be written to /var/log/messages for any reason. Regards, Christian Boltz -- [lange Antwort schreib] [begreif] [lange falsche Antwort lösch] Genial. [Ratti in fontlinge-devel]
Am Dienstag, 29. November 2005 15:57 schrieb Shibu Basheer:
Hello,
I've been using open suse for a couple of days now, and I feel there are some stability issues on my PC. The PC locks up occasionally when logging in or out of a KDE session. The mouse curser moves, but no access to keyboard, and I cannot switch to a terminal using alt-F switch. I also found the system locked up after I let it running overnight, only see a static picture of the screensaver on, with no response. I have applied all the latest updates. I also had these freezes. They must be because of a certain screensaver module, but I couldn't find out, which one. Just change the screensaver to one fix module instead of random, then this problem should be gone.
Marcel -- Üdvözlettel -- Mit freundlichen Grüssen, Marcel Hilzinger
Marcel Hilzinger wrote:
Am Dienstag, 29. November 2005 15:57 schrieb Shibu Basheer:
Hello,
I've been using open suse for a couple of days now, and I feel there are some stability issues on my PC. The PC locks up occasionally when logging in or out of a KDE session. The mouse curser moves, but no access to keyboard, and I cannot switch to a terminal using alt-F switch. I also found the system locked up after I let it running overnight, only see a static picture of the screensaver on, with no response. I have applied all the latest updates.
I also had these freezes. They must be because of a certain screensaver module, but I couldn't find out, which one. Just change the screensaver to one fix module instead of random, then this problem should be gone.
Marcel
I had this problem too on 2 machines. I resolve it by disabling acpi (acpi=off at boot time). Andre.
On 11/29/05, Shibu Basheer
Hello,
I've been using open suse for a couple of days now, and I feel there are some stability issues on my PC. The PC locks up occasionally when logging in or out of a KDE session. The mouse curser moves, but no access to keyboard, and I cannot switch to a terminal using alt-F switch. I also found the system locked up after I let it running overnight, only see a static picture of the screensaver on, with no response. I have applied all the latest updates.
This happened to me again today. I was in gnome, the screen locked up when I did a simple switch to another window using alt-tab. The system itself was not down, as the amorok was still playing music, and I was able to ssh into it from another machine. Help! Here are some logs: /var/log/messages Nov 30 22:31:28 mini su: (to root) sbasheer on /dev/pts/1 Nov 30 22:33:09 mini gconfd (root-21653): starting (version 2.12.0), pid 21653 user 'root' Nov 30 22:33:09 mini gconfd (root-21653): Resolved address "xml:readonly:/etc/opt/gnome/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Nov 30 22:33:09 mini gconfd (root-21653): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1 Nov 30 22:33:09 mini gconfd (root-21653): Resolved address "xml:readonly:/etc/opt/gnome/gconf/gconf.xml.defaults" to a read-only configuration source at position 2 Nov 30 22:33:39 mini gconfd (root-21653): GConf server is not in use, shutting down. Nov 30 22:33:39 mini gconfd (root-21653): Exiting Nov 30 22:34:08 mini kernel: NVRM: Xid: 6, PE0000 0764 08f6f6f6 00000000 98676767 b14e4e4e from /var/log/XFree86.0.log tion "AutoRepeat" "500 30" (**) Option "XkbRules" "xfree86" (**) Keyboard[0]: XkbRules: "xfree86" (**) Option "XkbModel" "ltcd" (**) Keyboard[0]: XkbModel: "ltcd" (**) Option "XkbLayout" "us" (**) Keyboard[0]: XkbLayout: "us" (**) Option "CustomKeycodes" "off" (**) Keyboard[0]: CustomKeycodes disabled (**) Option "Protocol" "explorerps/2" (**) Mouse[1]: Device: "/dev/input/mice" (**) Mouse[1]: Protocol: "explorerps/2" (**) Option "CorePointer" (**) Mouse[1]: Core Pointer (**) Option "Device" "/dev/input/mice" (**) Option "Buttons" "7" (==) Mouse[1]: Emulate3Buttons, Emulate3Timeout: 50 (**) Option "ZAxisMapping" "4 5" (**) Mouse[1]: ZAxisMapping: buttons 4 and 5 (**) Mouse[1]: Buttons: 7 (II) XINPUT: Adding extended input device "Mouse[1]" (type: MOUSE) (II) XINPUT: Adding extended input device "Keyboard[0]" (type: KEYBOARD) (II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type: Other) (II) Mouse[1]: ps2EnableDataReporting: succeeded Could not init font path element /usr/X11R6/lib/X11/fonts/local, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID, removing from list! (II) 3rd Button detected: disabling emulate3Button
participants (6)
-
Andre Malin -
BandiPat -
Christian Boltz -
Marcel Hilzinger -
Rafa Grimán -
Shibu Basheer