From: Paul <set@pobox.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.50 NCR5380/PAS16] bad: scheduling while atomic!
Date: Wed, 4 Dec 2002 22:23:50 -0500 [thread overview]
Message-ID: <20021205032350.GX1432@squish.home.loc> (raw)
In-Reply-To: <1038932271.11439.22.camel@irongate.swansea.linux.org.uk>
Alan Cox <alan@lxorguk.ukuu.org.uk>, on Tue Dec 03, 2002 [04:17:51 PM] said:
>
> Im using generic 5380 on 2.5.x but not 2.5.50 yet. Can you turn on all
> the NCR5380 debugging and see where it errors from (the trace doesnt
> give an answer as gcc has been smartly inlining functions used in one
> place only I suspect)
>
Hi;
Paul
set@pobox.com
SCSI subsystem driver Revision: 1.00
scsi-pas16 : probing io_port 0388
scsi-pas16 : detected board.
scsi-pas16 : io_port = 0388
scsi : NCR5380_all_init()
scsi0 : irq = 10
scsi0 : at 0x0388 irq 10 options CAN_QUEUE=32 CMD_PER_LUN=2 release=3 generic options AUTOPROBE_IRQ AUTOSENSE PSEUDO DMA UNSAFE USLEEP, USLEEP_POLL=200 USLEEP_SLEEP=20 generic release=7
scsi-pas16 : probing io_port 0384
scsi-pas16 : probing io_port 038c
scsi-pas16 : probing io_port 0288
scsi-pas16 : io_port = 0000
scsi0 : Pro Audio Spectrum-16 SCSI
LINE:1160 Adding c3f34200 to 00000000
scsi0 : command added to tail of queue
scsi0 : not connected
MAIN tmp=c3f34200 target=0 busy=0 lun=0
LINE:1232 Removing: ffffffff->c3f34200 c3f34200->00000000
scsi0 : main() : command for target 0 lun 0 removed from issue_queue
scsi0 : starting arbitration, id = 7
scsi0 : arbitration complete
scsi0 : won arbitration
scsi0 : selecting target 0
bad: scheduling while atomic!
Call Trace:
[<c0112a85>] schedule+0x3d/0x2c0
[<c012045c>] worker_thread+0x144/0x2cc
[<c0120318>] worker_thread+0x0/0x2cc
[<c025caac>] NCR5380_main+0x0/0x2dc
[<c0112d48>] default_wake_function+0x0/0x2c
[<c0112d48>] default_wake_function+0x0/0x2c
[<c0108935>] kernel_thread_helper+0x5/0xc
bad: scheduling while atomic!
Call Trace:
[<c0112a85>] schedule+0x3d/0x2c0
[<c012045c>] worker_thread+0x144/0x2cc
[<c0120318>] worker_thread+0x0/0x2cc
[<c025caac>] NCR5380_main+0x0/0x2dc
[<c0112d48>] default_wake_function+0x0/0x2c
[<c0112d48>] default_wake_function+0x0/0x2c
[<c0108935>] kernel_thread_helper+0x5/0xc
......
prev parent reply other threads:[~2002-12-05 3:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-03 1:39 Paul
2002-12-03 16:17 ` Alan Cox
2002-12-05 3:23 ` Paul [this message]
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=20021205032350.GX1432@squish.home.loc \
--to=set@pobox.com \
--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
all inboxes | Powered by JetHome®