From: Damacus Porteng <kernel@bastion.yi.org>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: IDE-SCSI/HPT366 Problem
Date: Wed, 29 Nov 2000 22:52:10 -0600 [thread overview]
Message-ID: <20001129225210.A10380@bastion.sprileet.net> (raw)
In-Reply-To: <20001129191402.F5891@garloff.etpnet.phys.tue.nl> <Pine.LNX.4.10.10011291025411.1743-100000@master.linux-ide.org>
In-Reply-To: <Pine.LNX.4.10.10011291025411.1743-100000@master.linux-ide.org>; from Andre Hedrick on Wed, Nov 29, 2000 at 10:27:17AM -0800
Andre:
Is that to say that I'd experience this problem with any EIDE CDRW used on one
of the HPT366 channels, or is it to say that only several CDRWs aren't
supported under this chipset?
Also, in regards to Kurt, I wasn't running the CDRW on the same channel as the
source.
Intel PIIX4 HPT366
----------- ------
/dev/hda (CDRW, worked) /dev/hde (boot: 36.5G)
/dev/hdb /dev/hdf (storage: 61.4G)
/dev/hdc /dev/hdg (CDRW, failed)
/dev/hdd /dev/hdh
In the crashing setup, the boot drive was /dev/hde, source drive was /dev/hdf.
CDRW was /dev/hdg (Second channel, master.) In the working setup, boot and
source were the same, CDRW was moved to hda.
Regards,
Damacus Porteng
On Wed, Nov 29, 2000 at 10:27:17AM -0800, Andre Hedrick wrote:
> On Wed, 29 Nov 2000, Kurt Garloff wrote:
>
> > Strange. If you read data from the harddisk on an IDE channel and write it
> > (with cdrecord) to some CDRW on the same IDE channel, you have to expect
> > trouble: As with IDE there is no disconnect from the bus (as opposed to
> > SCSI), you risk buffer underruns.
> > A lockup however is not to be expected :-(
>
> It is completely expected bacause of teh active timing changes done on
> this chipset design. The timings are for ATA DMA and not ATAPI.
> You should expect a 100% hardlock on mistimed IO access.
>
> Cheers,
>
> Andre Hedrick
> CTO Timpanogas Research Group
> EVP Linux Development, TRG
> Linux ATA Development
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
--
Damnit, Linus, I'm a network admin, not a kernel hacker!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-30 4:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-29 19:06 --Damacus Porteng--
2000-11-29 18:14 ` Kurt Garloff
2000-11-29 18:20 ` James A Sutherland
2000-11-29 18:27 ` Andre Hedrick
2000-11-30 4:52 ` Damacus Porteng [this message]
2000-11-30 6:25 ` Andre Hedrick
2000-11-30 12:12 ` Kurt Garloff
2000-11-30 1:08 ` Mike A. Harris
2000-11-29 18:23 ` Andre Hedrick
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=20001129225210.A10380@bastion.sprileet.net \
--to=kernel@bastion.yi.org \
--cc=andre@linux-ide.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
all inboxes | Powered by JetHome®