From: Douglas Gilbert <dougg@torque.net>
To: Jurgen Botz <jurgen@botz.org>, linux-kernel@vger.kernel.org
Subject: Re: Reproducible SMP kernel deadlock in SCSI generic driver (sg)
Date: Sun, 05 May 2002 13:45:04 -0400 [thread overview]
Message-ID: <3CD56FA0.FBCBD69B@torque.net> (raw)
Jurgen Botz <jurgen@botz.org>
> 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...
Jurgen,
Which version of cdparanoia (or whatever) are you using?
You mention deadlock, is the machine completely locked
up or is sg and the device inoperable? Since sg doesn't
take any "big" locks (e.g. io_request_lock) then it
shouldn't be able to lock up your machine without help
(from other drivers).
Assuming you can still execute commands on your box after the
"deadlock", I'm interested in WCHAN from ps. Here are some
ps variants:
ps -eo cmd,wchan
ps -eo fname,tty,pid,stat,pcpu,wchan
ps -eo pid,stat,pcpu,nwchan,wchan=WIDE-WCHAN-COLUMN -o args
The line for cdparanoia would be useful.
BTW ps needs to find the correct System.map for
the WCHAN output to be relevant.
Doug Gilbert
next reply other threads:[~2002-05-05 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-05 17:45 Douglas Gilbert [this message]
2002-05-12 22:24 ` Reproducible SMP kernel deadlock in SCSI generic driver (sg) Jurgen Botz
-- strict thread matches above, loose matches on Subject: below --
2002-05-04 22:08 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=3CD56FA0.FBCBD69B@torque.net \
--to=dougg@torque.net \
--cc=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