From: Jens Axboe <jens.axboe@oracle.com>
To: "René Peters" <ice.face@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SCSI drives, audio CDs and temporary system freeze with AIC7xxx
Date: Thu, 24 May 2007 11:27:55 +0200 [thread overview]
Message-ID: <20070524092755.GO5722@kernel.dk> (raw)
In-Reply-To: <200705241112.55901.ice.face@gmx.de>
On Thu, May 24 2007, René Peters wrote:
> Hello!
>
> Inserting of audio CDs causes my system to hang with high I/O-load while
> kded's mediamanagement is running.
> Long time later (round about 10-20 minutes) the system comes back again and
> i'm able to play the audio CD. The issue is reproduceable with the following
> drive:
> ->CD-R PX-W1210S
> Data CD's don't show this behavior.
> No system freeze or any other bad behavior with audio CDs after stopping
> kded's mediamanagement by hand. Maybe it is a kernel bug, maybe a bug in
> kded.
My guess would be that the program is issuing some command that craps
out the drive (or controller). It could be a wrong length, or some other
cdb field set incorrectly.
You should try and run blktrace on the device, so we can see which
command is wreaking havoc. In short steps:
- Download http://brick.kernel.dk/snaps/blktrace-git-latest.tar.gz,
untar, make, make install.
- Make sure your config has blktrace support, it's
CONFIG_BLK_DEV_IO_TRACE and is in the block layer menu.
Now you are ready to reproduce the problem.
- Run blktrace /dev/sr0 (I'm assuming you only have the one SCSI cd-rom).
- Insert an audio CD.
This should now cause the adaptec drive to go nuts like it usually does.
Once things have settled down and the freeze is over, ctrl-c blktrace.
Then do:
- blkparse sr0 -o sr0.log
and send sr0.log in a reply to this message.
--
Jens Axboe
prev parent reply other threads:[~2007-05-24 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 9:12 SCSI drives, audio CDs and temporary system freeze with AIC7xxx René Peters
2007-05-24 9:27 ` Jens Axboe [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=20070524092755.GO5722@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=ice.face@gmx.de \
--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