mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: James A Sutherland <jas88@cam.ac.uk>
To: Kurt Garloff <kurt@garloff.de>,
	--Damacus Porteng-- <kernel@bastion.yi.org>
Cc: Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: IDE-SCSI/HPT366 Problem
Date: Wed, 29 Nov 2000 18:20:09 +0000	[thread overview]
Message-ID: <00112918235301.10869@dax.joh.cam.ac.uk> (raw)
In-Reply-To: <20001129130616.A4879@bastion.sprileet.net> <20001129191402.F5891@garloff.etpnet.phys.tue.nl>
In-Reply-To: <20001129191402.F5891@garloff.etpnet.phys.tue.nl>

On Wed, 29 Nov 2000, Kurt Garloff wrote:
> 
> On Wed, Nov 29, 2000 at 01:06:16PM -0600, --Damacus Porteng-- wrote:
> > Problem:
> > 	The problem lies with using my EIDE CDRW - I set it up properly using
> > 	IDE-SCSI.  I can use my mp3tocdda shell script to encode mp3s to CD
> > 	(uses cdrecord as well) on the fly using either drive, however, when I
> > 	use cdrecord to write a data CD, the system hard-locks, no kernel
> > 	panic messages, and no Magic SysRQ keystroke works.  
> > 
> > 	Quite odd that I could do the cdrecord for audio tracks, but not
> > 	data..
> 
> 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. 

There shouldn't be any problems if you have the disk and CDrw drive on
different IDE busses, though, as I do. Also, provided the CDrw drive is
releasing the bus at times (which it should, presumably, since it can't be fast
enough to max out the bus all the time), you can then burst the data in from
the HDD, even on a shared bus. Even the fastest CDrw drive shouldn't get
underruns, I think.

Having said that, I'd still want to have both drives on different busses;
ideally, a SCSI CDrw and DVD drive, and ATA/100 HDDs. Now I just need to get
the numbers right on the lottery :-)

> A lockup however is not to be expected :-(

Indeed - a lockup is never the right result!


James.
-
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/

  reply	other threads:[~2000-11-29 18:55 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 [this message]
2000-11-29 18:27   ` Andre Hedrick
2000-11-30  4:52     ` Damacus Porteng
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=00112918235301.10869@dax.joh.cam.ac.uk \
    --to=jas88@cam.ac.uk \
    --cc=kernel@bastion.yi.org \
    --cc=kurt@garloff.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

all inboxes | Powered by JetHome®