Nicholas A. Bellinger wrote: >>> So far during my initial testing, I am running into a two different >>> exceptions. One NULL pointer deference OOPS after half dozen Open/iSCSI >>> login/logouts in block/elevator.c:elv_dequeue_request(). Here is the >>> trace from SCSI softirq context: >>> >>> http://linux-iscsi.org/builds/user/nab/2.6.28-rc6-oops-0.png >>> http://linux-iscsi.org/builds/user/nab/2.6.28-rc6-oops-1.png Can you build with debug info and find out which line is the offending one? >>> The other one is a BUG_ON in blk/blk-timeout.c:177 in blk_add_timeout() >>> that happens after a few hundred MB of READ_10 traffic, which also >>> appears to pass through elv_dequeue_request() at some point: >>> >>> http://linux-iscsi.org/builds/user/nab/2.6.28-rc6-oops-2.png >>> http://linux-iscsi.org/builds/user/nab/2.6.28-rc6-oops-4.png Hmmm... this means blk_add_timer() is being called after the request is already completed. All the problem discovered till now have to do with timeout going off without the low level driver knowing about the request. I don't have much idea and it'll probably be best to trace what's going on using blktrace or printks. Maybe this is caused by list corruption as with the first issue or request completion races with requeueing? -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
