From: Jan De Luyck <lkml@kcore.org>
To: linux-kernel@vger.kernel.org
Subject: [2.6.8.1] bad: scheduling while atomic! when loading aha152x driver
Date: Sun, 24 Oct 2004 21:14:58 +0200 [thread overview]
Message-ID: <200410242115.01067.lkml@kcore.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2383 bytes --]
Hello list,
Loading the aha152x driver resulted in this output, and shortly after a solid lock of the box happened.
Oct 24 21:08:13 faerun kernel: aha152x: BIOS test: passed, 1 controller(s) configured
Oct 24 21:08:13 faerun kernel: aha152x: resetting bus...
Oct 24 21:08:15 faerun kernel: aha152x3: vital data: rev=1, io=0x340 (0x340/0x340), irq=10, scsiid=7, reconnect=enabled, parity=enabled, synchronous=enabled, delay=1000, extended translation=disabled
Oct 24 21:08:16 faerun kernel: aha152x3: trying software interrupt, ok.
Oct 24 21:08:16 faerun kernel: scsi3 : Adaptec 152x SCSI driver; $Revision: 2.7 $
Oct 24 21:08:16 faerun kernel: (scsi-1:-1:-1) unexpected state (1)
Oct 24 21:08:30 faerun last message repeated 24 times
Oct 24 21:08:31 faerun kernel: (scsi3:0:0) cannot reuse command
Oct 24 21:08:31 faerun kernel: bad: scheduling while atomic!
Oct 24 21:08:31 faerun kernel: [schedule+1114/1120] schedule+0x45a/0x460
Oct 24 21:08:31 faerun kernel: [__down+137/256] __down+0x89/0x100
Oct 24 21:08:31 faerun kernel: [default_wake_function+0/32] default_wake_function+0x0/0x20
Oct 24 21:08:31 faerun kernel: [__mod_timer+208/384] __mod_timer+0xd0/0x180
Oct 24 21:08:31 faerun kernel: [__down_failed+8/12] __down_failed+0x8/0xc
Oct 24 21:08:31 faerun kernel: [pg0+143508100/1070325760] .text.lock.aha152x+0x19/0x35 [aha152x]
Oct 24 21:08:31 faerun kernel: [pg0+143489568/1070325760] timer_expired+0x0/0xc0 [aha152x]
Oct 24 21:08:31 faerun kernel: [pg0+143425216/1070325760] scsi_try_bus_device_reset+0x40/0x80 [scsi_mod]
Oct 24 21:08:31 faerun kernel: [pg0+143425818/1070325760] scsi_eh_bus_device_reset+0x5a/0xe0 [scsi_mod]
Oct 24 21:08:31 faerun kernel: [pg0+143427690/1070325760] scsi_eh_ready_devs+0x2a/0x60 [scsi_mod]
Oct 24 21:08:31 faerun kernel: [pg0+143428048/1070325760] scsi_unjam_host+0xb0/0xc0 [scsi_mod]
Oct 24 21:08:31 faerun kernel: [pg0+143428262/1070325760] scsi_error_handler+0xc6/0x100 [scsi_mod]
Oct 24 21:08:31 faerun kernel: [pg0+143428064/1070325760] scsi_error_handler+0x0/0x100 [scsi_mod]
Oct 24 21:08:31 faerun kernel: [kernel_thread_helper+5/24] kernel_thread_helper+0x5/0x18
Oct 24 21:08:31 faerun kernel: (scsi-1:-1:-1) unexpected state (1)
Oct 24 21:09:00 faerun last message repeated 73 times
Any pointers?
Thanks.
Jan
--
Your nature demands love and your happiness depends on it.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-10-24 19:14 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=200410242115.01067.lkml@kcore.org \
--to=lkml@kcore.org \
--cc=linux-kernel@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
Powered by JetHome