* James Bottomley <[EMAIL PROTECTED]> wrote: > Could you direct this poster to linux-scsi and we'll see if we can > finger the root cause (which will be difficult to do without getting a > boot trace).
FYI, here's a new one reported against 2.6.24-rc6-git7: http://bugzilla.kernel.org/show_bug.cgi?id=9674 Summary: Oops during rmmod'ing modeuls sdhci, sr_mod, ricoh_mmc, mmc_core Product: Other Version: 2.5 KernelVersion: 2.6.24-rc6-git7 has a very SCSI looking crash backtrace: [ 40.158530] Call Trace: [ 40.158537] [<ffffffff80331800>] elv_next_request+0xe0/0x170 [ 40.158543] [<ffffffff803f7fa9>] scsi_request_fn+0x69/0x360 [ 40.158547] [<ffffffff803352a2>] blk_execute_rq_nowait+0x62/0xb0 [ 40.158551] [<ffffffff80336d6a>] blk_execute_rq+0x8a/0x100 [ 40.158553] [<ffffffff803347e5>] get_request+0x155/0x2d0 [ 40.158557] [<ffffffff803f7d64>] scsi_execute+0xe4/0x120 [ 40.158560] [<ffffffff803f7e31>] scsi_execute_req+0x91/0x100 [ 40.158565] [<ffffffff8800b70b>] :sr_mod:sr_probe+0x21b/0x630 [ 40.158570] [<ffffffff802fa0a9>] sysfs_create_link+0xa9/0x150 [ 40.158575] [<ffffffff805620a5>] klist_next+0x35/0xe0 [ 40.158579] [<ffffffff803c34cc>] driver_probe_device+0x9c/0x1b0 [ 40.158582] [<ffffffff803c37b1>] __driver_attach+0xe1/0xf0 [ 40.158585] [<ffffffff803c36d0>] __driver_attach+0x0/0xf0 [ 40.158589] [<ffffffff803c26bd>] bus_for_each_dev+0x4d/0x80 [ 40.158592] [<ffffffff803c2acf>] bus_add_driver+0xaf/0x220 Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
