On Mon, Jun 6, 2011 at 8:32 PM, Xiangliang Yu <yuxiangl@xxxxxxxxxxx> wrote:
>>>>Subject: Re: BUG: linux-2.6.39 kernel panic issue when hot-plut disk during I/O
>>>
>>>>On 6/2/2011 8:27 PM, Xiangliang Yu wrote:
>>>>> Hi, all
>>>>> I upgrade kernel version to 2.6.39 and find out a kernel panic when I test the MVSAS driver: kernel panic if hot-plug disk during I/O. But the driver is OK in version 2.6.37
>>>
>>>>If it is a stable reproduction can you bisect it?
>>> What I use is latest kernel version (2.6.39).
>
>>Right, if the driver consistently fails in 2.6.39 and runs fine in
>>2.6.37 then you can use git bisect [1] to possibly find the commit
>>that broke things.
>>
>>git bisect start
>>git bisect bad v2.6.39
>>git bisect good v2.6.37
>><run test>
>>git bisect good/bad depending on test results.
>
>>Although you might try 2.6.38 first to cut down on the number of
>>kernels you need to test.
>
> 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
--
Dan
--
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
