From: Kurt Garloff <kurt@garloff.de>
To: --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 19:14:02 +0100 [thread overview]
Message-ID: <20001129191402.F5891@garloff.etpnet.phys.tue.nl> (raw)
In-Reply-To: <20001129130616.A4879@bastion.sprileet.net>
In-Reply-To: <20001129130616.A4879@bastion.sprileet.net>; from kernel@bastion.yi.org on Wed, Nov 29, 2000 at 01:06:16PM -0600
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
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.
A lockup however is not to be expected :-(
Regards,
--
Kurt Garloff <garloff@suse.de> Eindhoven, NL
GPG key: See mail header, key servers Linux kernel development
SuSE GmbH, Nuernberg, FRG SCSI, Security
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2000-11-29 18:45 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 [this message]
2000-11-29 18:20 ` James A Sutherland
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=20001129191402.F5891@garloff.etpnet.phys.tue.nl \
--to=kurt@garloff.de \
--cc=kernel@bastion.yi.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®