Oops in dput() (was Re: Oops report)

Steve Dodd (dirk@loth.demon.co.uk)
Fri, 7 May 1999 17:56:22 +0100


On Fri, May 07, 1999 at 09:30:51AM +0200, root wrote:

> Linux 2.2.7 SMP ( 2 x PII, AIC7880 )

> Code: c0132a7b <dput+127/148> 00000000 <_EIP>: <===
> Code: c0132a7b <dput+127/148> 0: 8b 40 40 movl 0x40(%eax),%eax <===
> Code: c0132a7e <dput+12a/148> 3: 50 pushl %eax
> Code: c0132a7f <dput+12b/148> 4: 56 pushl %esi
> Code: c0132a80 <dput+12c/148> 5: 68 fc 6d 1d c0 pushl $0xc01d6dfc
> Code: c0132a85 <dput+131/148> a: e8 66 20 fe ff call c0114af0 <printk+0/188>

It looks like you're using egcs -- at least, you don't seem to be using gcc
2.7.2.3. What version of egcs? AFAICR compiling kernels with egcs 1.0.x had
some problems.

> Code: c0132a8a <dput+136/148> f: c7 05 00 00 00 movl $0x0,0x0
> Code: c0132a8f <dput+13b/148> 14: 00 00 00 00 00

So if it's any consolation, even if the printk had succeeded, the process
would have oops'd on the next line, anyway :)

S. (who's wondering if it's worth teaching himself about the dcache layer
tonight..)

-- 
Plug-and-Play is really nice, unfortunately it only works 50% of the time.
To be specific the "Plug" almost always works.            --unknown source

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/