From: Stephen Samuel <samuel@bcgreen.com>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: Bill Davidsen <davidsen@tmr.com>,
linux-kernel@vger.kernel.org, Andre Hedrick <andre@linux-ide.org>
Subject: Re: A CD with errors (scratches etc.) blocks the whole system while reading damadged files
Date: Fri, 26 Apr 2002 08:23:14 -0700 [thread overview]
Message-ID: <3CC970E2.2030407@bcgreen.com> (raw)
In-Reply-To: <3CC738AD.50905@bcgreen.com> <Pine.LNX.3.96.1020424232237.4586B-100000@gatekeeper.tmr.com> <20020426040457.GO574@matchmail.com>
> I don't think it has to do with the IRQs, but it sounds like the entire ide
> chipset (think two cables one one chipset...) has stopped responding when
> ONE device (out of a possible four (with two cables)) has failed media.
In my case, I was able to read data from hda while the cdrom
on hdd was trying to recover data from a scratched disk.
Reading data from hdc (shared cable with the CDROM), on the
other hand, was VERY slow.
I have an 82371AB PIIX4 ide interface (dual IDE chipset),
It's part of a 440BX chipset board.
If accessing on one IDE interface (C/D) causes the other (A/B) to lockup,
I'd guess you've got especially cheap hardware on your box.
--
Stephen Samuel +1(604)876-0426 samuel@bcgreen.com
http://www.bcgreen.com/~samuel/
Powerful committed communication, reaching through fear, uncertainty and
doubt to touch the jewel within each person and bring it to life.
next prev parent reply other threads:[~2002-04-26 15:25 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
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 [this message]
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=3CC970E2.2030407@bcgreen.com \
--to=samuel@bcgreen.com \
--cc=andre@linux-ide.org \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.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