linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ken Moffat <zarniwhoop@ntlworld.com>
To: Gregor Jasny <gjasny@googlemail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Jeff Garzik <jgarzik@pobox.com>,
	linux-ide@vger.kernel.org
Subject: Re: 2.6.19-rc3 system freezes when ripping with cdparanoia at ioctl(SG_IO)
Date: Sun, 29 Oct 2006 21:31:06 +0000	[thread overview]
Message-ID: <20061029213106.GA25865@deepthought.linux.bogus> (raw)
In-Reply-To: <9d2cd630610291120l3f1b8053i5337cf3a97ba6ff0@mail.gmail.com>

On Sun, Oct 29, 2006 at 08:20:17PM +0100, Gregor Jasny wrote:
> Hi,
> 
> Today I tried the new cdparanoia from Debian Sid (3.10+debian~pre0-2).
> When I started ripping with "cdparanoia -d /dev/scd0 1" my system
> freezes after some seconds. There is no oops and even the console
> cursor stops blinking.
> 
> If I start cdparanoia with -g /dev/scd0 it starts ripping and but the
> kernel prints many "program cdparanoia not setting count and/or
> reply_len properly" warnings. But this seems to be a cdparanoia bug.
> 
> My CDROM:
> Vendor:                    PIONEER
> Product:                   DVD-ROM DVD-106
> Revision level:            1.22
> 
 I'm guessing this is really an IDE drive ?  If so, I suspect the
problem is in scsi emulation (which doesn't deny that the bug might
be at least partly in the application, although hanging the box is
nasty).

 Specifically, I've just compiled that version with the debian patch
on my (non-debian) amd64 and successfully ripped a CD (without any
log messages) on both 2.6.18 and 2.6.19-rc3 using /dev/hdc.

 So, if this isn't a real SCSI drive, as a work-around you could try
disabling ide-scsi and use the IDE device name.

Ken
-- 
das eine Mal als Tragödie, das andere Mal als Farce

  reply	other threads:[~2006-10-29 21:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-29 19:20 2.6.19-rc3 system freezes when ripping with cdparanoia at ioctl(SG_IO) Gregor Jasny
2006-10-29 21:31 ` Ken Moffat [this message]
2006-10-29 22:05   ` Brice Goglin
2006-10-30 11:45 ` Jens Axboe
2006-10-30 13:14   ` Gregor Jasny
2006-10-30 13:17   ` Gregor Jasny
2006-10-30 13:27     ` Jens Axboe
2006-11-09  9:46       ` Brice Goglin
2006-11-09 14:00         ` Tejun Heo
2006-11-09 14:14           ` Jeff Garzik
2006-11-09 20:13             ` Monty Montgomery
2006-11-09 15:50           ` Douglas Gilbert
2006-11-10 10:36             ` Luben Tuikov
2006-11-10 12:58               ` Douglas Gilbert
2006-11-10 20:08                 ` Luben Tuikov
2006-11-11 10:46                   ` Christoph Hellwig
2006-11-11 16:39                     ` Douglas Gilbert
2006-11-11 19:09                     ` Luben Tuikov
2006-11-14 22:52                       ` Monty Montgomery
2006-11-09 20:09           ` Monty Montgomery
2006-11-09 22:47             ` Tejun Heo
2006-11-10 16:15             ` Jens Axboe
2006-11-10 16:19               ` Brice Goglin
2006-11-10 16:23                 ` Jens Axboe
2006-11-14 12:24                   ` Brice Goglin
2006-11-14 12:29                     ` Jens Axboe
2006-11-14 12:40                       ` Brice Goglin
2006-11-14 12:50                         ` Jens Axboe

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=20061029213106.GA25865@deepthought.linux.bogus \
    --to=zarniwhoop@ntlworld.com \
    --cc=gjasny@googlemail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).