On Fri, Mar 19, 2010 at 14:00, Adam Tauno Williams wrote:
Or, even more likely, you have a driver issue specific to the system you are using. When you have an oops is it almost always a device driver.
Is it an oops? The thing that baffled me is the absolute lack of logging info. I've had problems with kernels in the past, where the Kernel died for whatever reason, and the caps lock, num lock and scroll lock LEDs would flash... as far as I remember there was some kind of dump to the messages log that at least gave some hint where the problem was... this time nothing.
Are your main system and secondary system really *identical* hardware? If not your comparison of the stability of the two doesn't mean much.
Definitely not. The unstable system is an Asus Eee... my "stable" system is a home built system on an AMD dual core. The comparison of the stability wasn't to say if one was stable why not the other since they are identical... it was just as a point of reference... nothing more. Anyway, I think the problem with whatever was spazzing out the 2.6.31.12 kernel-desktop has been resolved in a newer kernel. I pulled down the KOTD from the factory kernel repository (2.6.33), and it seems to be humming along fine now - I've had the laptop running for a few days now and put it through some testing, and haven't had a single lockup. C. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org