From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Linux SCSI list <linux-scsi@vger.kernel.org>, nikola.ciprich@linuxbox.cz
Subject: Re: crash unrelated to sym53c8xx
Date: Wed, 8 Apr 2009 10:30:02 +0200 [thread overview]
Message-ID: <20090408083002.GA9961@develbox.linuxbox.cz> (raw)
In-Reply-To: <20090402193927.GA7106@nik-comp.linuxbox.cz>
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?
BR
nik
x
--
-------------------------------------
Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava
tel.: +420 596 603 142
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------
next prev parent reply other threads:[~2009-04-08 8:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-02 7:54 sym53c8xx: WARNING on module unload, crashes on further usage Nikola Ciprich
2009-04-02 11:23 ` Matthew Wilcox
2009-04-02 12:26 ` Nikola Ciprich
2009-04-02 12:28 ` Nikola Ciprich
2009-04-02 12:49 ` crash unrelated to sym53c8xx Matthew Wilcox
2009-04-02 12:59 ` Nikola Ciprich
2009-04-02 13:01 ` Matthew Wilcox
2009-04-02 19:39 ` Nikola Ciprich
2009-04-08 8:30 ` Nikola Ciprich [this message]
2009-04-08 8:42 ` FUJITA Tomonori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090408083002.GA9961@develbox.linuxbox.cz \
--to=extmaillist@linuxbox.cz \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=nikola.ciprich@linuxbox.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox