Re: Soft lockup in scsi_remove_target under 3.6 (regression from 3.5)

2012-10-03 Thread Jonathan McDowell
On Tue, Oct 02, 2012 at 10:46:22PM -0500, Mike Christie wrote: > On 10/02/2012 07:43 PM, Jonathan McDowell wrote: > > Upgraded to 3.6 today on my dev box and after seeing an FC attached SAN > > go down and come back up (due to an expected reboot) I started getting > > the following in my logs. It

Re: Soft lockup in scsi_remove_target under 3.6 (regression from 3.5)

2012-10-03 Thread Jonathan McDowell
On Tue, Oct 02, 2012 at 10:46:22PM -0500, Mike Christie wrote: On 10/02/2012 07:43 PM, Jonathan McDowell wrote: Upgraded to 3.6 today on my dev box and after seeing an FC attached SAN go down and come back up (due to an expected reboot) I started getting the following in my logs. It

Re: Soft lockup in scsi_remove_target under 3.6 (regression from 3.5)

2012-10-02 Thread Mike Christie
On 10/02/2012 07:43 PM, Jonathan McDowell wrote: > Upgraded to 3.6 today on my dev box and after seeing an FC attached SAN > go down and come back up (due to an expected reboot) I started getting > the following in my logs. It continues even after the array is back and > functioning - I'm seeing:

Soft lockup in scsi_remove_target under 3.6 (regression from 3.5)

2012-10-02 Thread Jonathan McDowell
Upgraded to 3.6 today on my dev box and after seeing an FC attached SAN go down and come back up (due to an expected reboot) I started getting the following in my logs. It continues even after the array is back and functioning - I'm seeing: kernel:[109104.348034] BUG: soft lockup - CPU#6 stuck

Soft lockup in scsi_remove_target under 3.6 (regression from 3.5)

2012-10-02 Thread Jonathan McDowell
Upgraded to 3.6 today on my dev box and after seeing an FC attached SAN go down and come back up (due to an expected reboot) I started getting the following in my logs. It continues even after the array is back and functioning - I'm seeing: kernel:[109104.348034] BUG: soft lockup - CPU#6 stuck

Re: Soft lockup in scsi_remove_target under 3.6 (regression from 3.5)

2012-10-02 Thread Mike Christie
On 10/02/2012 07:43 PM, Jonathan McDowell wrote: Upgraded to 3.6 today on my dev box and after seeing an FC attached SAN go down and come back up (due to an expected reboot) I started getting the following in my logs. It continues even after the array is back and functioning - I'm seeing: