From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: ide-scsi scheduling while atomic in linux-2.6.0-test11
Date: 11 Dec 2003 00:53:13 GMT [thread overview]
Message-ID: <br8f5p$uv7$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 3FD6AF84.5010805@samwel.tk
In article <3FD6AF84.5010805@samwel.tk>, Bart Samwel <bart@samwel.tk> wrote:
| [1.] One line summary of the problem:
|
| ide-scsi scheduling while atomic in linux-2.6.0-test11
|
| [2.] Full description of the problem/report:
|
| ide-scsi gives me "scheduling while atomic" while burning a CDRW in
| linux-2.6.0-test11, when an interrupt is lost. I have no clue what
| caused this; I was writing a CDRW that might have been faulty, but
| otherwise nothing unusual. The CDRW is a Samsung SW-408B on the
| secondary slave. While burning, I was extracting audio data from a CD in
| the DVD player that was on the secondary master.
I can believe you might have lost an interrupt...
|
| [3.] Keywords (i.e., modules, networking, kernel):
|
| ide-scsi, cd-writing
|
| [4.] Kernel version (from /proc/version):
|
| Linux version 2.6.0-test11 (root@samwel.tk) (gcc version 3.3.2 (Debian))
| #6 Sun Nov 30 22:25:31 CET 2003
Linus posted a patch, which I hope has made it into bk by now, which may
or may not help, but you are better investigating any issue using the
lastest version.
|
| [5.] Output of Oops.. message (if applicable) with symbolic information
| resolved (see Documentation/oops-tracing.txt)
[...snip...]
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
prev parent reply other threads:[~2003-12-11 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-10 5:30 ide-scsi scheduling while atomic in linux-2.6.0-test11 Bart Samwel
2003-12-10 5:20 ` dan carpenter
2003-12-10 7:03 ` Christian Borntraeger
2003-12-11 0:53 ` bill davidsen [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='br8f5p$uv7$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.