Re: crash unrelated to sym53c8xx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 8 Apr 2009 10:30:02 +0200
Nikola Ciprich <extmaillist@xxxxxxxxxxx> wrote:

> Hi Matthew,
> finally we caught the crash even with backtrace, here it goes:
> 
> [65468.555522] BUG: spinlock lockup on CPU#1, scsi_eh_9/5912, ec5625e0
> [65468.555522] Pid: 5912, comm: scsi_eh_9 Tainted: G        W  2.6.28lb.10 #1
> [65468.555522] Call Trace:
> [65468.555522]  [<c0333654>] _raw_spin_lock+0x144/0x180
> [65468.555522]  [<c046178c>] _spin_lock_irqsave+0x4c/0x60
> [65468.555522]  [<c031d111>] ? blk_put_request+0x21/0x50
> [65468.555522]  [<c031d111>] blk_put_request+0x21/0x50
> [65468.555522]  [<f827163c>] sg_finish_rem_req+0x9c/0xf0 [sg]
> [65468.555522]  [<f8272589>] sg_rq_end_io+0x1a9/0x2b0 [sg]
> [65468.555522]  [<c0461afc>] ? _spin_unlock_irqrestore+0x2c/0x50
> [65468.555522]  [<c031cda0>] end_that_request_last+0x50/0x230
> [65468.555522]  [<c046178c>] ? _spin_lock_irqsave+0x4c/0x60
> [65468.555522]  [<c031d05e>] blk_end_io+0x5e/0x90
> [65468.555522]  [<c031d0ea>] blk_end_request+0x1a/0x20
> [65468.555522]  [<f81a9305>] scsi_end_request+0x25/0x90 [scsi_mod]
> [65468.555522]  [<f81aa072>] scsi_io_completion+0x92/0x420 [scsi_mod]
> [65468.555522]  [<f81a973b>] ? scsi_device_unbusy+0x8b/0xb0 [scsi_mod]
> [65468.555522]  [<f81a3538>] scsi_finish_command+0x98/0x100 [scsi_mod]
> [65468.555522]  [<f81a790c>] ? scsi_eh_ready_devs+0x54c/0x720 [scsi_mod]
> [65468.555522]  [<f81a6eba>] scsi_eh_flush_done_q+0x4a/0x100 [scsi_mod]
> [65468.555522]  [<f81a815d>] scsi_error_handler+0x31d/0x520 [scsi_mod]
> [65468.555522]  [<c0461afc>] ? _spin_unlock_irqrestore+0x2c/0x50
> [65468.555522]  [<c021eda9>] ? complete+0x49/0x60
> [65468.555522]  [<f81a7e40>] ? scsi_error_handler+0x0/0x520 [scsi_mod]
> [65468.555522]  [<c023fda2>] kthread+0x42/0x70
> [65468.555522]  [<c023fd60>] ? kthread+0x0/0x70
> [65468.555522]  [<c02041c7>] kernel_thread_helper+0x7/0x10
> 
> Will it help?

This looks like a sg bug.

2.6.30-rc1 includes the following commit to fix this bug:

commit 015640edb1f346e0b2eda703587c4cd1c310ec1d
Author: FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx>
Date:   Fri Apr 3 19:28:06 2009 +0900

    [SCSI] sg: fix q->queue_lock on scsi_error_handler path


It's tagged 'Cc: stable@xxxxxxxxxx' so it will be merged into stable
trees too.
--
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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux