Re: 1.3.72 instability

Bjorn Ekwall (bj0rn@blox.se)
Tue, 12 Mar 1996 22:25:26 +0100 (MET)

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Next message: Bryn Paul Arnold Jones: "Re: make fails ..."
Previous message: Bas Mevissen: "psaux / watchdog combination problem ..."
In reply to: Markus Gutschke: "Re: Outstanding pre-production issues and next dev. cycle..."
Next in thread: Bryn Paul Arnold Jones: "Re: 1.3.72 instability"

Linus wrote:
> Chris Evans: "1.3.72 instability" (Mar 11, 19:54):
> >
> > Anyway, 1.3.72 seems rather more keen to crash than other kernels,
> > sometime to the point of complete hang... so here's a few OOPSES.
> >
> > Mar 11 16:07:50 jcr00 kernel: Unable to handle kernel paging request at virtual address c1013583
[...]
> > EIP: 1013583: OUT OF RANGE
[...]
>
> I've seen a few of these, and they _all_ seem to be related to module
> use. I simply cannot debug panic's that happen in a module (as you can
> see, the stack trace and EIP are not even found by ksymoops), especially
> as I don't even know _what_ module it is.
[...]
>
> Linus

If you can reproduce this Oops "at will", use the option "-m" to insmod.
This will give you a loadmap that you can use when you want to find
exactly _where_ a module dies. Don't forget to save the loadmap for
every "insmod", though...

Bjorn <bj0rn@blox.se> <http://www.pi.se/blox/>

Next message: Bryn Paul Arnold Jones: "Re: make fails ..."
Previous message: Bas Mevissen: "psaux / watchdog combination problem ..."
In reply to: Markus Gutschke: "Re: Outstanding pre-production issues and next dev. cycle..."
Next in thread: Bryn Paul Arnold Jones: "Re: 1.3.72 instability"