Messages in this thread | | | From | "Mukker, Atul" <> | Subject | RE: assertion failure with new megaraid beta driver leads to sche duling failure | Date | Thu, 15 Apr 2004 18:36:50 -0400 |
| |
Paul,
Random deletion has issues with this version of the driver. Sreenivas will release the next version tomorrow morning with the fix.
Thanks -Atul
> -----Original Message----- > From: Paul Wagland [mailto:paul@wagland.net] > Sent: Thursday, April 15, 2004 5:57 PM > To: Linux SCSI mailing list; Linux kernel mailing list > Cc: Atul Mukker > Subject: assertion failure with new megaraid beta driver leads to > scheduling failure > > > 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 > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |