From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Kyle Moffett <mrmacman_g4@mac.com>
Cc: Mark Hahn <hahn@physics.mcmaster.ca>,
LKML Kernel <linux-kernel@vger.kernel.org>,
John Livingston <jujutama@comcast.net>,
"Eric D. Mudama" <edmudama@gmail.com>,
Robert Hancock <hancockr@shaw.ca>
Subject: Re: [RESEND][2.6.15] New ATA error messages on upgrade to 2.6.15
Date: Sun, 02 Apr 2006 22:24:43 +0100 [thread overview]
Message-ID: <1144013084.31123.14.camel@localhost.localdomain> (raw)
In-Reply-To: <0FE43D5B-B25D-45C7-83ED-4DE1552EC9DB@mac.com>
On Sul, 2006-04-02 at 15:55 -0400, Kyle Moffett wrote:
> (2) It's extremely unlikely that the card itself is faulty; it
> exhibits identical symptoms on both drives and has ever since I
> originally purchased the card and installed 2.4.X on the system.
If it has always shown those symptoms then I'd say its quite likely the
card if the crystals/PLLs on it are out. It looks like the timing is
wrong, which means either the input clocks (eg PCI clock) are wrong (eg
37.5Mhz not 33 due to BIOS overclock settings or just plain out), the
card has a dodgy crystal/PLL or the kernel set it up wrong.
PCI timings won't move between motherboards, PLL faults wont move
between cards.
> (3) It's not possible that it's the power supply. As I said before
> I checked the power supply with an oscilliscope _during_boot_. The
I think you can rule that out. Insufficient power generally causes
drives to offline or spontaneously reset. It can cause weird symptoms as
it ends up back in PIO 0 but not ECC change downs except to PIO
> noticing a buggy firmware, then I'm hoping that with some help I can
> determine where the kernel driver is getting confused and correct the
> programmed bus timings (or whatever the hell isn't working). As my
> practical knowledge of the ATA and IDE protocols is quite limited I'm
> well out of my depth here and unable to debug without further
> assistance.
Unless anyone else is seeing the same problem with the same card variant
or you have two cards that do it then there isn't much that can be done
I suspect other than assume the hardware is iffy, rightly or wrongly.
I'd have expected a lot more reports if it were the controller.
(Having said that if you are reading this and your controller is a
Promise and does the same, please say so it might be vital to deducing a
pattern to problems)
Alan
next prev parent reply other threads:[~2006-04-02 21:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0604021508540.2653-100000@coffee.psychology.mcmaster.ca>
2006-04-02 19:55 ` Kyle Moffett
2006-04-02 21:24 ` Alan Cox [this message]
2006-04-02 22:00 ` Mark Hahn
2006-04-02 23:17 ` Kyle Moffett
2006-04-03 11:35 Mikael Pettersson
2006-04-03 12:32 ` Kyle Moffett
-- strict thread matches above, loose matches on Subject: below --
2006-04-03 9:07 Mikael Pettersson
2006-04-03 9:29 ` Alan Cox
[not found] <Pine.LNX.4.44.0604011333160.11853-100000@coffee.psychology.mcmaster.ca>
2006-04-02 0:05 ` Kyle Moffett
[not found] <5WD6n-5fR-9@gated-at.bofh.it>
[not found] ` <5WD6n-5fR-11@gated-at.bofh.it>
[not found] ` <5WD6n-5fR-13@gated-at.bofh.it>
[not found] ` <5WD6n-5fR-15@gated-at.bofh.it>
[not found] ` <5WD6n-5fR-17@gated-at.bofh.it>
[not found] ` <5WD6n-5fR-7@gated-at.bofh.it>
[not found] ` <5WEvy-7az-7@gated-at.bofh.it>
2006-04-01 19:03 ` Robert Hancock
2006-04-01 19:13 ` Kyle Moffett
[not found] <5VqEv-46l-49@gated-at.bofh.it>
[not found] ` <5VqEv-46l-47@gated-at.bofh.it>
[not found] ` <5WA8u-X3-5@gated-at.bofh.it>
[not found] ` <5WAi6-19q-13@gated-at.bofh.it>
[not found] ` <5WB4M-2kX-29@gated-at.bofh.it>
2006-04-01 1:21 ` Robert Hancock
2006-04-01 2:54 ` Kyle Moffett
2006-04-01 23:23 ` Alan Cox
[not found] <20060328090211.4D6F34C04A@penelope.moffetthome.net>
2006-03-28 17:57 ` [2.6.15] " Kyle Moffett
2006-03-31 22:16 ` [RESEND][2.6.15] " Kyle Moffett
2006-03-31 22:21 ` Eric D. Mudama
2006-03-31 23:13 ` Kyle Moffett
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=1144013084.31123.14.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=edmudama@gmail.com \
--cc=hahn@physics.mcmaster.ca \
--cc=hancockr@shaw.ca \
--cc=jujutama@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
/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
Powered by JetHome