From: Alan Pope <alan.pope@gmail.com>
To: lkml@think-future.de, Linux Kernel-Liste <linux-kernel@vger.kernel.org>
Subject: Re: Promise module (old) broken
Date: Sun, 5 Dec 2004 19:59:29 +0000 [thread overview]
Message-ID: <8e93903b041205115957fc@mail.gmail.com> (raw)
In-Reply-To: <20041205195358.DC2B5440E2@service.i-think-future.de>
On Sun, 5 Dec 2004 18:54:00 +0100, lkml@think-future.de
<lkml@think-future.de> wrote:
> Hi,
>
> up to the actual kernel rc 2.6.10rc3 has broken pdc 20265 support. As
> some kernel releases ago, one had to specify i/o ports on kernel
> cmdline. 2.4.28 kernel works w/o cmdline parameter.
>
> Is this behaviour intended? Will it be fixed in 2.6.10 release?
>
> W/o parameter kernel (2.6) does not recognise the pdc ide controller
> drives.
> dmesg output states: "ideX: Wait for ready failed before probe !"
>
> As of kernel rc 2.6.10rc1 the kernel even reported ide drive short
> read and seek errors on drives even not connected to the pdc
> controller but connected to the onboard controller (->/dev/hda1). In
> fact /dev/hda1 has no errors (so far).
>
> Any comments?
>
It's more broken than that here. I get the following errors in 2.6.8
through 2.6.9-ac9 & 2.6.10-rc2 with the old (PDC202XX_OLD) promise
driver, when placing the disk/controller under any load (in fact just
doing hdparm -t -T /dev/hde).
I get..
hde: dma_intr: status=0xff { Busy }
ide: failed opcode was: unknown
hde: DMA disabled
PDC202XX: Primary channel reset.
PDC202XX: Secondary channel reset.
(a number of times)
ide2: reset timed-out, status=0xff
end_request: I/O error, dev hde, sector 11776
Buffer I/O error on device hde, logical block 1472
(many times)
Cheers,
Al.
next prev parent reply other threads:[~2004-12-05 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-05 17:54 Promise module (old) broken lkml
2004-12-05 19:06 ` Bartlomiej Zolnierkiewicz
2004-12-05 19:59 ` Alan Pope [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-09 11:02 lkml
2004-12-09 11:12 lkml
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=8e93903b041205115957fc@mail.gmail.com \
--to=alan.pope@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@think-future.de \
/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