On Wed, 8 Sep 2004 00:36:07 +0200, you wrote:
On Tuesday 07 September 2004 23:45, Mike wrote:
On Tue, 7 Sep 2004 14:02:44 +0200, you wrote:
On Tuesday 07 September 2004 13:43, James Knott wrote:
Mike wrote:
Well the subject says it all. How can I fix this short of re-installing?
I have no idea what you're talking about.
He is talking about a kernel bug. The kernel was doing something that shouldn't be interrupted, but it was. It should be reported, to suse if it's a suse kernel, or to the linux kernel mailing list if it's a kernel.org kernel
Any ideas Anders? This was during a boot. How do I report it,
this would fall under "technical feedback"
and can I get the info that SuSE will need from the boot log?
You should see those "scheduling while atomic" messages in /var/log/messages (or possibly /var/log/boot.msg) and together with each there should be a stack trace (i.e. a series of procedure names and their addresses and a few other values). That would be of interest in a kernel bug report
They are not in that file, or any other file in the /var/log directory.
I suspect they will want you to try it without the nvidia driver too, so uninstall that and see if you get the same error. Kernel developers are much nicer to you when you give them a stack trace that says "not tainted" :)
I'd love to, but it doesn't look like I can get them the info. :( I did notice another person has the same problem and right after a kernel update as well. Right now the big question is, do we re-install, or is there a way of recovering our systems?