From: Mikael Pettersson <mikpe@csd.uu.se>
To: camm@enhanced.com, linux-kernel@vger.kernel.org
Subject: Re: 2.2.19+ide: corrupts ide tape output
Date: Mon, 21 May 2001 23:49:14 +0200 (MET DST) [thread overview]
Message-ID: <200105212149.XAA10612@harpo.it.uu.se> (raw)
On 21 May 2001 14:49:55 -0400, Camm Maguire <camm@enhanced.com> wrote:
>Greetings! 2.2.19+ide, applied the patch because this box has a new
>Promise PDC20267 ide controller. 14GB HP Colorado tape drive. Before
>we installed the new ide controller and patched the kernel, i.e. with
>unpatched 2.2.19 running on a different ide controller, this setup
>works just fine. Now I get the following occasionally, which results
>in corrupted dumps to tape:
>
>May 21 10:27:47 intech9 kernel: hdh: status error: status=0x40 { DriveReady }
>May 21 10:27:47 intech9 kernel: ide-scsi: Strange, packet command initiated yet DRQ isn't asserted
You added a Promise Ultra100 PCI card, right?
>From what I hear, it doesn't support ATAPI devices well, only disks.
So if you moved the HP tape drive to the PDC, move it back to
the mainboard's IDE controller.
Also, don't disable the mainboard's controller thinking you can save
some interrupts that way. Andre Hedrick (Linux IDE guy) once wrote
that this could cause the PDC to grab IRQ 14, which had some nasty
side-effects.
(My main box runs with disks on a Promise Ultra100 card and
ATAPI CD-RW and tape on the mainboard's IDE (440BX) controller.
Both 2.2+ide and 2.4 work fine.)
/Mikael
next reply other threads:[~2001-05-21 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-21 21:49 Mikael Pettersson [this message]
2001-05-24 21:27 ` Camm Maguire
-- strict thread matches above, loose matches on Subject: below --
2001-05-21 18:49 Camm Maguire
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=200105212149.XAA10612@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=camm@enhanced.com \
--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®