From: uixjjji1@umail.furryterror.org (Zygo Blaxell)
To: <linux-kernel@vger.kernel.org>
Subject: Linux 2.4.9 (and 2.4.8-ac{11,12}) IDE brokenness (and workaround for non-PDC20268R chipsets)
Date: 27 Aug 2001 14:50:31 -0400 [thread overview]
Message-ID: <9me4pn$iko$1@shippou.furryterror.org> (raw)
On some machines running 2.4.9 and 2.4.8-ac1[12], I get an unending stream of these:
Aug 27 14:46:39 kasumi kernel: hdh: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 27 14:46:39 kasumi kernel: hdh: drive not ready for command
Aug 27 14:46:45 kasumi kernel: hdf: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 27 14:46:45 kasumi kernel: hdf: drive not ready for command
Aug 27 14:46:45 kasumi kernel: hdh: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Aug 27 14:46:45 kasumi kernel: hdh: drive not ready for command
This only seems to happen to some drives or drive/controller combinations.
For disks on PIIX controllers, sometimes the DMA doesn't get turned on at
startup. A simple 'hdparm -d1 /dev/hdc' can fix this.
Unfortunately, this is what happens on a Promise Fasttrak 100 TX2 (PCI device
ID 0x6268):
root@kasumi:~# hdparm -d1 /dev/hde
/dev/hde:
setting using_dma to 1 (on)
HDIO_SET_DMA failed: Operation not permitted
using_dma = 0 (off)
root@kasumi:~# cat /proc/ide/pdc202xx
PDC202XX Chipset.
------------------------------- General Status ---------------------------------
Burst Mode : enabled
Host Mode : Tri-Stated
Bus Clocking : 100 External
IO pad select : 10 mA
Status Polling Period : 15
Interrupt Check Status Polling Delay : 15
--------------- Primary Channel ---------------- Secondary Channel -------------
enabled enabled
66 Clocking enabled enabled
Mode MASTER Mode MASTER
Error Error
--------------- drive0 --------- drive1 -------- drive0 ---------- drive1 ------
DMA enabled: no no no no
DMA Mode: PIO--- PIO--- PIO--- PIO---
PIO Mode: PIO ? PIO ? PIO ? PIO ?
The drives function perfectly (as far as I can tell, anyway) when I
use a hacked version of 2.4.6 which simply uses the PDC20268 driver
(PCI id 0x4d68) on my PDC20268R card (PCI id 0x6268).
--
Zygo Blaxell (Laptop) <zblaxell@feedme.hungrycats.org>
GPG = D13D 6651 F446 9787 600B AD1E CCF3 6F93 2823 44AD
reply other threads:[~2001-08-27 18:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='9me4pn$iko$1@shippou.furryterror.org' \
--to=uixjjji1@umail.furryterror.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.