Messages in this thread |  | | Date | Thu, 12 Sep 2002 13:48:00 +0200 | From | lists@corewars ... | Subject | Re: 2.4.19 OOPS [Repost] |
| |
Hm, actually I am.
And from the oops traces, the offending intruction always seems to be a pop.
I'll upgrade and try again.
Thanks, Sapan
On Wed, Sep 11, 2002 at 06:48:16PM +0100, Alan Cox wrote: > On Wed, 2002-09-11 at 18:16, lists@corewars.org wrote: > > Just in case this might shed some more light on the problem... > > I recompiled the kernel with frame pointers about a week ago, and I > > didn't face a single oops till today morning, when I recompiled the > > kernel without frame-pointers and I've been getting the same > > oopses all day. > > > > Are you using gcc 3.0.x or an early gcc 3.1.x. There are bugs in those > where they write below the stack pointer which means an IRQ will corrupt > stuff. Turning on frame pointers might well hide this > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |