Re: 2.4.17 bug

[Michel Dänzer <daenzer@debian.org>]

On Tue, 2002-01-15 at 14:26, Russell Hires wrote: 

> First of all, thanks to xmon, I'm still running.

xmon doesn't help anything in that regard. If it's still running, that
just means it was an oops, not a panic. You should reboot ASAP nevertheless
because kernel structures may be corrupted.

> Second, I tried sending messages about this before, but I didn't
> realize my System.map was 500 KB. So, I'll just send a copy of the
> relevent portion of my kern.log, and ask to whom or where I need to
> send my System.map. 

Better try to pipe the oops output through ksymoops first. You can post
its output to linuxppc-dev@lists.linuxppc.org or a similar list.


> Jan 15 08:22:11 localhost kernel: kernel BUG at page_alloc.c:160!
> Jan 15 08:22:13 localhost kernel: kernel BUG at page_alloc.c:193!
> Jan 15 08:22:13 localhost kernel: kernel BUG at page_alloc.c:170!
> Jan 15 08:22:13 localhost kernel: kernel BUG at page_alloc.c:205!
> Jan 15 08:22:14 localhost kernel: kernel BUG at page_alloc.c:170!
> Jan 15 08:22:14 localhost kernel: kernel BUG at page_alloc.c:205!

Not looking good... what filesystem is that? Were you doing anything
special?


-- 
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member   /  CS student, Free Software enthusiast