From: Paul Wagland <paul@wagland.net>
To: Linux SCSI mailing list <linux-scsi@vger.kernel.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: Atul Mukker <atulm@lsil.com>
Subject: assertion failure with new megaraid beta driver leads to scheduling failure
Date: Thu, 15 Apr 2004 23:56:43 +0200 [thread overview]
Message-ID: <1082066202.2176.143.camel@morsel.kungfoocoder.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
Hi all,
Well, seems I have a penchance for causing trouble ;-)
I was playing around with the new beta driver, and was trying to remove
some logical drives using the dellmgr utility.
Well, something between the driver and the BIOS got unhappy, and all of
a sudden I got about 20 of the following lines:
assertion failed:(spin_is_locked(adapter->host_lock)), file: drivers/scsi/megaraid.c, line: 3061:megaraid_abort_handler
followed by (copied by hand... maybe I should set up a serial console :-):
bad: scheduling while atomic!
Call Trace:
[<c011cd5f>] schedule+0x58f/0x5a0
[<c01209a7>] __call_console_drivers+0x57/0x60
[<c0108126>] __down+0x86/0x100
[<c011cdc0>] default_wake_function+0x0/0x20
[<f8832790>] megaraid_reset_handler+0x0/0xc0 [megaraid]
[<c010833c>] __down_failed+0x8/0xc
[<f8833fee>] .text.lock.megaraid_clib+0x5/0x17 [megaraid]
[<f88327be>] megaraid_reset_handler+0x2e/0xc0 [megaraid]
this was called from:
scsi_try_bus_device_reset
scsi_eh_bus_device_reset
scsi_eh_ready_devs
scsi_unjam_host
default_wake_function
scsi_error_handler
scsi_error_handler
kernel_thread_helper
Thoughts and/or suggestions?
Cheers,
Paul
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-04-15 21:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1082066202.2176.143.camel@morsel.kungfoocoder.org \
--to=paul@wagland.net \
--cc=atulm@lsil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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