On Jun 07 Dan Williams wrote: > On Mon, Jun 6, 2011 at 8:32 PM, Xiangliang Yu <yuxiangl@xxxxxxxxxxx> wrote: > > 2.6.39-rc4 work fine, but 2.6.39-rc5 has kernel panic. > > Still smells like a regression. If you run a git bisect between those > two versions it should be pretty straightforward to identify the > offending commit. There were some interesting block/scsi changes in > that window: > > Jens Axboe (5): > block: kill blk_flush_plug_list() export > cfq-iosched: read_lock() does not always imply rcu_read_lock() > block: get rid of QUEUE_FLAG_REENTER > block: remove stale kerneldoc member from __blk_run_queue() > elevator: check for ELEVATOR_INSERT_SORT_MERGE in !elvpriv case too > > Liu Yuan (1): > block, blk-sysfs: Fix an err return path in blk_register_queue() > > Tao Ma (1): > block: Remove the extra check in queue_requests_store > > Tejun Heo (1): > block: don't propagate unlisted DISK_EVENTs to userland Or try linux 3.0-rc2 which as yet another block queue lifetime vs. hotplug fix (which is not yet available in a 2.6.39.y kernel). -- Stefan Richter -=====-==-== -==- --=== http://arcgraph.de/sr/ -- 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
