The Tuesday 2008-07-22 at 12:13 +0200, Kevin Bader wrote:

...

Two weeks ago I installed Suse 11 on my laptop. Everything worked fine at the beginning, but now it crashes frequently. I've no clue where to look at to find the problem, so I really need some guidance on that. Here's some information:

- crashes occur without a specific event, sometimes after half an hour uptime, sometimes right after the logon - when it crashes keyboard and mouse doesn't work anymore; the display is either black or frozen - keyboard LEDs do _not_ blink, so I assume it's not a kernel panic - when it crashes, the cpu cooler goes full speed

Install a gadget to watch cpu temperature. Perhaps it is running high. Would be consistent with the fan going full speed.

- -- Cheers, Carlos E. R.

I don't think it is running high, because the fan goes fullspeed right when the crash occurs. If the cpu was running hot, the fan would start to make noise much earlier. kevin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Kevin Bader wrote:

...

The Tuesday 2008-07-22 at 12:13 +0200, Kevin Bader wrote:

...

Two weeks ago I installed Suse 11 on my laptop. Everything worked fine at the beginning, but now it crashes frequently. I've no clue where to look at to find the problem, so I really need some guidance on that. Here's some information:

- crashes occur without a specific event, sometimes after half an hour uptime, sometimes right after the logon - when it crashes keyboard and mouse doesn't work anymore; the display is either black or frozen - keyboard LEDs do _not_ blink, so I assume it's not a kernel panic - when it crashes, the cpu cooler goes full speed

Install a gadget to watch cpu temperature. Perhaps it is running high. Would be consistent with the fan going full speed.

- -- Cheers, Carlos E. R.

I don't think it is running high, because the fan goes fullspeed right when the crash occurs. If the cpu was running hot, the fan would start to make noise much earlier.

kevin Check https://bugzilla.novell.com/show_bug.cgi?id=389656 to see if it maybe applies. Regards Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-07-22 at 12:33 +0200, Kevin Bader wrote:

...

Install a gadget to watch cpu temperature. Perhaps it is running high. Would be consistent with the fan going full speed.

I don't think it is running high, because the fan goes fullspeed right when the crash occurs. If the cpu was running hot, the fan would start to make noise much earlier.

Maybe yes, maybe not. You'd better check. It could be something like detecting to high a temperature, setting the fan on high, then crashing. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIhwZXtTMYHG2NR9URAr9UAJ9zNtU8Zmnb2r7AZP522qoSBb55BgCfY/aL M+9JZvZESEKtzhqVkmd34cM= =oW6Q -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-07-23 at 12:28 +0200, Kevin Bader wrote:

...

Maybe yes, maybe not. You'd better check.

It could be something like detecting to high a temperature, setting the fan on high, then crashing.

Okay, I understand. But how do I check? If the system crashes right after it found out it's running hot, I cannot use a tool to monitor.. Is there a tool which logs the current temperature to a file?

The file might not have time to be written... if wanted, a cron job would do it. Or a script on a delay loop. Use something like "gkrellm" that displays on the desktop continuously. If the display freezes but is visible, you can still check the last temperature. Another alternative is "gkrellmd" to see it on another computer. There may be also desktop applets to display the temperature on the panel. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIhxLotTMYHG2NR9URAtlYAJ9UA5De1Rz21qSSrZRZGhVBNY7pWgCfX4lE /TSVa1EhNUNvdqJBXcMrYX4= =RCN4 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Per Jessen schrieb:

Kevin Bader wrote:

...

- crashes occur without a specific event, sometimes after half an hour uptime, sometimes right after the logon - when it crashes keyboard and mouse doesn't work anymore; the display is either black or frozen - keyboard LEDs do _not_ blink, so I assume it's not a kernel panic - when it crashes, the cpu cooler goes full speed - I didn't mess around with the daemon settings, everything is suse default - KDE session management is disabled - I can't reproduce the error manually - the system runs KDE 3.5, default kernel, everything is updated, all patches installed

I can deliver more information if needed, of course. I'd really appreciate your help.

Have you done a memory-test? memtest86+.

/Per Jessen, Zürich

No, I haven't yet. I'll try that and post the result in a few hours. kevin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

I had a similar problem on my T42P - updating to the latest kernel fixed it.

...

...

Per Jessen 7/22/2008 7:18 AM >>> Kevin Bader wrote:

- crashes occur without a specific event, sometimes after half an hour uptime, sometimes right after the logon - when it crashes keyboard and mouse doesn't work anymore; the display is either black or frozen - keyboard LEDs do _not_ blink, so I assume it's not a kernel panic - when it crashes, the cpu cooler goes full speed - I didn't mess around with the daemon settings, everything is suse default - KDE session management is disabled - I can't reproduce the error manually - the system runs KDE 3.5, default kernel, everything is updated, all patches installed

I can deliver more information if needed, of course. I'd really appreciate your help.

Have you done a memory-test? memtest86+. /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Michael Fischer schrieb:

On Tue, Jul 22, Kevin Bader wrote:

...

Hi!

Two weeks ago I installed Suse 11 on my laptop. Everything worked fine at the beginning, but now it crashes frequently. I've no clue where to look at to find the problem, so I really need some guidance on that. Here's some information:

- crashes occur without a specific event, sometimes after half an hour uptime, sometimes right after the logon - when it crashes keyboard and mouse doesn't work anymore; the display is either black or frozen - keyboard LEDs do _not_ blink, so I assume it's not a kernel panic - when it crashes, the cpu cooler goes full speed - I didn't mess around with the daemon settings, everything is suse default - KDE session management is disabled - I can't reproduce the error manually - the system runs KDE 3.5, default kernel, everything is updated, all patches installed

Not sure if this is applicable with your hardware, but..

I had a similar problem. In my case, the "fix" was to change from the onboard nic which hwinfo --netcard describes as

Model: "nVidia MCP67 Ethernet" Vendor: pci 0x10de "nVidia Corporation" Device: pci 0x054c "MCP67 Ethernet" SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x82b3 Revision: 0xa2 Driver: "forcedeth" Driver Modules: "forcedeth"

To a plain old 3c905C-TX/TX-M [Tornado]. No more random crashes.

Go figure.

Michael

Thanks for the suggestion. Anyhow, my laptop has only one onboard nic, which is not by nVidia. My laptop is a Fujitsu-Siemens Amilo A1650G, by the way. kevin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Rajko M. schrieb:

On Tuesday 22 July 2008 05:13:33 am Kevin Bader wrote:

...

Hi!

Two weeks ago I installed Suse 11 on my laptop. Everything worked fine at the beginning, but now it crashes frequently. I've no clue where to look at to find the problem, so I really need some guidance on that. Here's some information:

- crashes occur without a specific event, sometimes after half an hour uptime, sometimes right after the logon - when it crashes keyboard and mouse doesn't work anymore; the display is either black or frozen - keyboard LEDs do _not_ blink, so I assume it's not a kernel panic - when it crashes, the cpu cooler goes full speed - I didn't mess around with the daemon settings, everything is suse default - KDE session management is disabled - I can't reproduce the error manually - the system runs KDE 3.5, default kernel, everything is updated, all patches installed

I can deliver more information if needed, of course. I'd really appreciate your help.

kevin

Have you looked in /var/log/messages for a hint. Also, if it crashes now, how about running Live CD. It is default system before any updates and with simple video driver. It can help you to check /var/log/messages for last entries before crash.

I just booted in the system, I didn't touched anything and it crashed right after 6 seconds. Last entry in /var/log/messages is "su: (kevin) root to none". I don't really know what this means. I don't think running a LiveCD would help, because the system worked right after installation. The problems came after two weeks. Anyway, I don't have a good network connection here, so I can't get the LiveCD at the moment.. kevin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

...

I don't think running a LiveCD would help, because the system worked right after installation. The problems came after two weeks. Anyway, I don't have a good network connection here, so I can't get the LiveCD at the moment..

Pity. Running a live system, different version, would help determine if it is hardware, or something in version 11.0

-- Cheers, Carlos E. R.

It worked with 10.3, so I don't think it's an hardware error, unless there were some big changes. kevin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mittwoch 23 Juli 2008, Carlos E. R. wrote:

The Wednesday 2008-07-23 at 13:25 +0200, Kevin Bader wrote:

...

...

Pity. Running a live system, different version, would help determine if it is hardware, or something in version 11.0

...

...

It worked with 10.3, so I don't think it's an hardware error, unless there were some big changes.

But you'd have to run 10.3 now to make sure that no hardware broke in the interval.

It seems to point to software, though.

Are you using the propietary nividia driver? Or ATI? Try the generic one.

-- Cheers, Carlos E. R.

You pointed me to something: When I installed the propriatary ATI drivers (ATI radeon xpress 200m), something went wrong with aticonfig, so I had to change 'radeon' to 'fglrx' manually in xorg.conf. I just used sax2 to reconfigure my xserver, and now it *seems* to work - I have 3 hours uptime already :-) Thanks for your help, I will write again if it didn't work. And thanks to everybody else for the hints :-) kevin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org