public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Xavier Bestel <xavier.bestel@free.fr>
To: Stephen Samuel <samuel@bcgreen.com>
Cc: Mike Fedyk <mfedyk@matchmail.com>,
	Bill Davidsen <davidsen@tmr.com>,
	Andre Hedrick <andre@linux-ide.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: A CD with errors (scratches etc.) blocks the whole system while reading damadged files
Date: 02 May 2002 10:49:50 +0200	[thread overview]
Message-ID: <1020329390.2595.9.camel@bip> (raw)
In-Reply-To: <3CD0F846.3070605@bcgreen.com>

Le jeu 02/05/2002 à 10:26, Stephen Samuel a écrit :
> I ran a similar type of test on a 2.4.9.31 (redhat 7.1 ) kernel.
> With the CD on HDD, I could read off of HDA just peachy while
> the system was choking on a scratched (aol) cd.

The "system grinding to a halt" happens to me too, when *ripping*
scratched cds. Note that it's when using *userspace* access to the block
device, with e.g. cdparanoia or grip (or dvd ripping tools).

My DVD drive is on a VT82C693A/694x (ABit VP6).


  reply	other threads:[~2002-05-02  8:50 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-18 13:13 A CD with errors (scratches etc.) blocks the whole system while reading damadged files Dr. Death
2002-04-19 14:14 ` Richard B. Johnson
2002-04-19 14:22   ` Kent Borg
2002-04-19 14:46     ` Richard B. Johnson
2002-04-19 14:50     ` A CD with errors (scratches etc.) blocks the whole system while reading damaged files Stephen Satchell
2002-04-19 14:28   ` A CD with errors (scratches etc.) blocks the whole system while reading damadged files Darrell Wright
2002-04-19 14:36   ` dr john halewood
2002-04-19 18:00   ` Oliver Xymoron
2002-04-23 22:34   ` Bill Davidsen
2002-04-24 12:31     ` Richard B. Johnson
2002-04-24 19:16       ` Bill Davidsen
2002-04-24 19:52         ` Richard B. Johnson
2002-04-24 22:58         ` Stephen Samuel
2002-04-25  3:33           ` Bill Davidsen
2002-04-26  4:04             ` Mike Fedyk
2002-04-26  5:42               ` Erik Andersen
2002-04-26  7:35               ` Andre Hedrick
2002-04-25 20:50                 ` Pavel Machek
2002-04-28  2:18                   ` Andre Hedrick
2002-04-26 15:48                 ` Mike Fedyk
2002-04-29 21:46                 ` Bill Davidsen
2002-05-02  3:45                   ` Mike Fedyk
2002-05-02  8:26                     ` Stephen Samuel
2002-05-02  8:49                       ` Xavier Bestel [this message]
2002-05-02  8:43                         ` Zwane Mwaikambo
2002-05-02  9:12                           ` Xavier Bestel
2002-05-02 15:48                         ` Mike Fedyk
2002-05-03  7:14                           ` Xavier Bestel
2002-05-02 15:40                       ` Mike Fedyk
2002-05-02 17:15                         ` Stephen Samuel
2002-04-26 15:23               ` Stephen Samuel
2002-04-26 10:16         ` Zwane Mwaikambo
2002-04-19 20:01 ` Erik Andersen
2002-04-21 15:18   ` Denis Vlasenko
2002-04-21 22:54   ` Hans-Peter Jansen
2002-04-22  5:38     ` Andre Hedrick
2002-04-22 14:49   ` Roger Larsson
  -- strict thread matches above, loose matches on Subject: below --
2002-04-30 21:18 Eric M

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=1020329390.2595.9.camel@bip \
    --to=xavier.bestel@free.fr \
    --cc=andre@linux-ide.org \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfedyk@matchmail.com \
    --cc=samuel@bcgreen.com \
    /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