Manfred Spraul wrote:

> Martin Rode wrote:
> >
> > >
> > > Run this oops message through ksymoops please.  It will make debugging
> > > it alot easier.
> > >
> > >
> >
> > Since I did not compile the kernel myself, ksymoops is not too happy with
> > what is has to analyse the dump. I tried compile the Mandrake kernel myself
> > but there seems to be something unmatched. See below for what ksymoops
> > gives me.
> >
> looks good.
>
> > call trace: [<cc0139c44>] [<c0139d1c>] [<c0130af6>] [<c0108e93>]
>                 ^^^^^^^^^
>

I re-ran ksymoops and posted it again to the list.

> Is that the first oops, or was there another oops before this one?

I don't know. The server is in a different room from my office so all I saw was
the lock up and all I could do was copying the oops from screen. Our backup
regularily starts at 9 P.M., so I'm very confident that it 's gonna happen
again.

It did not happen with 2.2.18 or 2.2.19pre, that's for sure. With these kernel I
only had MM problems like vm_trying_to_free_unused_page etc.

Martin