Oops: 0000 (2.1.89)

Ragnar Hojland Espinosa (root@lightside.ddns.org)
Sun, 8 Mar 1998 15:25:34 +0100 (MET)

This nuked the superblock of my root fs :| Luckily it was recoverable, but
it was very scary ;). HD's DMA was on. Here's the trace, just in case it helps:

Trace: c0143614 <ext2_free_blocks+2e8/2f0> [EIP]
Trace: c01436e7 <ext2_new_block+cb/8e8>
Trace: c012a3c3 <sync_buffers+117/1cc>
Trace: c012a5d0 <sys_fsync+14/158>
Trace: c0142016 <V2_minix_read_inode+122/1b4>
Trace: c012a431 <sync_buffers+185/1cc>
Trace: c012a61a <sys_fsync+5e/158>
Trace: c012a17c <init_private_file+2c/5c>
Trace: c012a689 <sys_fsync+cd/158>
Trace: c0128867 <sys_open+4f/f8>
Trace: c010995a <setup_rt_frame+1a2/1cc>
Trace: c010002b <startup_32+2b/b8>

After the Oops, something like this followed:

irq timeout: status 0x58
{ DriveReady SeekComplete DataRequest }
DMA disabled
ide0: reset

____/| Ragnar Hojland (tech.support@redestb.es) Fingerprint 94C4B
\ o.O| 2F0D27DE025BE2302C
=(_)= "Thou shalt not follow the NULL pointer for 104B78C56 B72F0822
U chaos and madness await thee at its end." hkp://keys.pgp.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu