2.5.70-bk10 oops when trying to mount root from raid-1 device
2.5.70-bk10 has some raid fixes, but raid-1 still fails unlike 2.5.70-mm4.
bk10 successfully discovers raid-1 and raid-0 arrays, but this happens when the kernel tries to mount root:
<lots of ordinary boot messages>
md ... autorun DONE
<this is where I normally get VFS: Mounted root (ext2 filesystem) readonly.
I got this instead:>
unable to handle kernel paging request at 5a5a5a86
EIP at put_all_bios+0x047/0x80
process swapperraid_end_bio_iodeadline_next_requestraid1_end_requestscsi_request_fnbio_endio__end_that_request_firstscsi_end_requestscsi_io_completionsd_rw_intrscsi_finish_commandscsi_softirqdo_softirqdo_IRQdefault_idlecommon_interruptdefault_idledefault_idlecpu_idlerest_initstart_kernelunknown_bootoption
<0> kernel panic, exception in interrupt
This is a dual celeron with two scsi disks, with
two raid-1 arrays and one raid-0. The
kernel is compiled with preempt and devfs,
using gcc-3.3
Helge Hafting
Quoted 4 lines · Helge Hafting
2.5.70-bk10 has some raid fixes, but raid-1 still fails unlike 2.5.70-mm4.
Quoted 8 lines
bk10 successfully discovers raid-1 and raid-0 arrays, but this happens when the kernel tries to mount root:
<lots of ordinary boot messages>
md ... autorun DONE
<this is where I normally get VFS: Mounted root (ext2 filesystem) readonly.
I got this instead:>
unable to handle kernel paging request at5a5a5a86
This is "use of uninitialised memory". 0x6b6b6b6b is "use of freed memory".
It's supposed to be that way in Linus's tree too, but I screwed it up.
Quoted 1 line
EIP at
put_all_bios+0x047/0x80
I'd be suspecting that the write_bios[] array isn't being memset somewhere.
struct bio **bio = r1_bio->write_bios + i;