Re: blk-8 oopses at boot (was: blk-7 fails to boot)

From: Jens Axboe (axboe@suse.de)
Date: Fri Nov 03 2000 - 14:11:29 EST


On Fri, Nov 03 2000, David Mansfield wrote:
> Hi Jens.
>
> I've tried your blk-8 patch and it oopses during boot. I only hand
> copied the stack trace, and ran it through ksymoops:
>
> Call Trace: [<c01310e0>] [<c0131f55>] [<c014c88e>] [<c014c3dc>]
> [<c01b9cea>] [<c014c4ea>] [<c014c456>]
> [<c01ba3a4>] [<c018c7ab>] [<c0105000>] [<c018c8ae>] [<c01070e7>]
> [<c0108ce3>]
> Warning (Oops_read): Code line not seen, dumping what data is available
>
> Trace; c01310e0 <__wait_on_buffer+90/c0>
> Trace; c0131f55 <bread+45/70>
> Trace; c014c88e <msdos_partition+8e/3f0>
> Trace; c014c3dc <check_partition+8c/d0>
> Trace; c01b9cea <sd_init_onedisk+75a/770>
> Trace; c014c4ea <grok_partitions+8a/d0>
> Trace; c014c456 <register_disk+26/30>
> Trace; c01ba3a4 <sd_finish+134/1c0>
> Trace; c018c7ab <scsi_register_device_module+eb/110>
> Trace; c0105000 <empty_bad_page+0/1000>
> Trace; c018c8ae <scsi_register_module+4e/60>
> Trace; c01070e7 <init+7/150>
> Trace; c0108ce3 <kernel_thread+23/30>
>
> I'm going to try taking MSDOS out of my .config to try to work around
> this. I'll keep you posted as to my progress.

Thanks, I think this is a generic msdos problem though. If it still
oopses without blk-8, could you send the complete oops please?

-- 
* Jens Axboe <axboe@suse.de>
* SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Tue Nov 07 2000 - 21:00:14 EST