Mark Lord wrote:
I also see it with the SLES10 kernel 2.6.16.21-0.8.
.. Obvious self-correction: not the same problem in the SLES10 kernel. I just got confused juggling five kernels around. :) But problem is still there in 2.6.19*. Rebuilding kernel now with frame pointers and DEBUG_INFO enabled. Cheers - 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/
- References:
- 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state
- From: Mark Lord <[email protected]>
- Re: 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state
- From: Jens Axboe <[email protected]>
- Re: 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state
- From: Arjan van de Ven <[email protected]>
- Re: 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state
- From: Jens Axboe <[email protected]>
- Re: 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state
- From: Arjan van de Ven <[email protected]>
- Re: 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state
- From: Jens Axboe <[email protected]>
- Re: 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state
- From: Arjan van de Ven <[email protected]>
- Re: 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state
- From: Jens Axboe <[email protected]>
- Re: 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state
- From: Mark Lord <[email protected]>
- Re: 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state
- From: Mark Lord <[email protected]>
- 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state
- Prev by Date: Re: 2.6.19-rc3: known unfixed regressions (v3)
- Next by Date: Re: [ckrm-tech] RFC: Memory Controller
- Previous by thread: Re: 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state
- Next by thread: Re: 2.6.19-rc3-git7: scsi_device_unbusy: inconsistent lock state
- Index(es):