From: Jurgen Botz <jurgen@botz.org>
To: linux-kernel@vger.kernel.org
Subject: Reproducible SMP kernel deadlock in SCSI generic driver (sg)
Date: Sat, 04 May 2002 15:08:38 -0700 [thread overview]
Message-ID: <4595.1020550118@localhost> (raw)
The sg module reproducibly deadlocks the kernel for me after some time
of heavy I/O on an SMP system. This appears to be true in /all/ kernel
versions... I can reproduce it very reliably now in 2.4.19-pre8 and
2.5.13, and I've had problems with CD ripping on my SMP workstation at
least throughout the 2.4 series (I just never fully investigated before).
The bug is almost certainly in sg.c; here is what I've narrowed down...
- Deadlock when ripping CDs using generic device under SMP after some
amount of heavy I/O; higher transfer rate seems to make it happen
sooner.
- Happens with SCSI CD drives as well as IDE drives using ide-scsi or
USB drives using usb-storage.
- Deadlock happens sooner with usb-storage than with real SCSI device,
but will eventually happen in either case. In worst case I've seen
the deadlock after ~100MB transferred, in the best case after ~3-4GB
(i.e. ripped about 5-6 CDs).
- No deadlock when using sr device on SMP kernel
- No deadlock with sg or sr on UP kernel
Searching lkml didn't turn up any recent reports of anything like this,
but I suspect that's because not too many people are ripping CDs on
SMP systems these days... however, if anyone out there /does/ and
doesn't see lockups, please let me know.
:j
--
Jürgen Botz | While differing widely in the various
jurgen@botz.org | little bits we know, in our infinite
| ignorance we are all equal. -Karl Popper
next reply other threads:[~2002-05-04 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 22:08 Jurgen Botz [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-05 17:45 Reproducible SMP kernel deadlock in SCSI generic driver (sg) Douglas Gilbert
2002-05-12 22:24 ` Jurgen Botz
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=4595.1020550118@localhost \
--to=jurgen@botz.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