From: Alan Pope <alan.pope@gmail.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andre Hedrick <andre@linux-ide.org>
Subject: Re: PDC202XX_OLD broken
Date: Wed, 8 Dec 2004 21:25:56 +0000 [thread overview]
Message-ID: <8e93903b041208132573a3c118@mail.gmail.com> (raw)
In-Reply-To: <58cb370e041207125864b97eea@mail.gmail.com>
On Tue, 7 Dec 2004 21:58:52 +0100, Bartlomiej Zolnierkiewicz
<bzolnier@gmail.com> wrote:
> You are using 40c cable instead of 80c one.
> Thus transfer rate is limited to UDMA33.
>
No, I'm using an 80c cable. I have even gone out and bought a new 80c
one just to make sure the cable isn't broken. I have also got two
identical disks, and experience exactly the same problem on both.
I booted with "ide2=dma" because it was booting with the disk in pio mode.
> Moreover pdc202xx_old has a bug in cable detection code.
> pdc202xx_old_cable_detect() always returns '0' (which means
> 80c cable) due to a sloppy coding - result of CIS & mask is
> truncated to 8 bits although CIS holds cable info in bits 10-11.
>
> Does this fix work for you?
>
Not tried it, but it wouldn't help me would it? I *do* have an 80c
cable, and the disk does show up in dmesg as a UDMA100 disk..
This is what happens when I thrash it, note my /home/alan is on
another non-UDMA100 disk on a separate controller.
# time cp -Rvp /home/alan/* temp
ide: failed opcode was: unknown
hde: DMA disabled
PDC202XX: Primary channel reset.
PDC202XX: Secondary channel reset.
(then lots of these)
end_request: I/O error, dev hde, sector 145225487
end_request: I/O error, dev hde, sector 145225495
end_request: I/O error, dev hde, sector 145225503
end_request: I/O error, dev hde, sector 145225511
end_request: I/O error, dev hde, sector 145225519
end_request: I/O error, dev hde, sector 145225527
end_request: I/O error, dev hde, sector 145225535
EXT3-fs error (device hde1) in ext3_prepare_write: IO failure
EXT3-fs error (device hde1) in start_transaction: Journal has aborted
printk: 2018 messages suppressed.
Buffer I/O error on device hde1, logical block 5
lost page write due to I/O error on hde1
end_request: I/O error, dev hde, sector 183
Any ideas?
Cheers,
Al.
next prev parent reply other threads:[~2004-12-08 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 22:05 PDC202XX_OLD broken Alan Pope
2004-12-07 13:21 ` Alan Cox
2004-12-07 20:13 ` Alan Pope
2004-12-07 20:58 ` Bartlomiej Zolnierkiewicz
2004-12-08 21:25 ` Alan Pope [this message]
2004-12-08 21:46 ` Bartlomiej Zolnierkiewicz
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=8e93903b041208132573a3c118@mail.gmail.com \
--to=alan.pope@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@linux-ide.org \
--cc=bzolnier@gmail.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