From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Rogério Brito" <rbrito@ime.usp.br>
Cc: Jeff Garzik <jeff@garzik.org>, Michael Tokarev <mjt@tls.msk.ru>,
Mark Lord <lkml@rtr.ca>,
linux-kernel@vger.kernel.org
Subject: Re: Quick question about libata and hdparm
Date: Mon, 20 Apr 2009 19:40:17 +0100 [thread overview]
Message-ID: <20090420194017.4edd5674@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20090420173526.GA7935@ime.usp.br>
> Can you comment on the dmesg log attached? I'd like to, at least,
> understand what is happening, since I'm starting to consider using
> libata with all my computers.
Its logging a couple of transmission errors. The CRC is computed by
hardware each end and compared (by hardware).
> This computer, in particular, uses an IDE drive with a 40 ribbon cable
> (and, thus, no UDMA/66). The cable is well put (checked two times
> already) and I believe that everything is OK with this cable, since I
> substituted it was already substituting one that gave me the same
> results.
It's tuned down to UDMA33 which looks correct.
If I saw a lot of these I'd suspect something like a controller timing
setup error, but you seem to just have occasional ones in the log which
really does look like genuine CRC errors from electrical noise or similar.
You don't happen to have any amateur radio transmitters or telsa coils in
the room with it ;) ?
next prev parent reply other threads:[~2009-04-20 18:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 0:22 Rogério Brito
2009-04-19 6:31 ` Robert Hancock
2009-04-19 12:33 ` Mark Lord
2009-04-19 12:44 ` Michael Tokarev
2009-04-19 12:57 ` Jeff Garzik
2009-04-19 13:06 ` Michael Tokarev
2009-04-19 20:11 ` Rogério Brito
2009-04-19 21:27 ` Jeff Garzik
2009-04-20 17:35 ` Rogério Brito
2009-04-20 18:40 ` Alan Cox [this message]
2009-04-20 20:41 ` Rogério Brito
2009-04-20 21:16 ` Alan Cox
2009-04-20 20:31 ` Bartlomiej Zolnierkiewicz
2009-04-20 20:45 ` Rogério Brito
2009-04-20 21:19 ` Alan Cox
2009-04-20 22:57 ` Rogério Brito
2009-04-21 5:32 ` Rogério Brito
2009-04-21 12:59 ` Bartlomiej Zolnierkiewicz
2009-04-23 5:56 ` Rogério Brito
2009-04-23 21:31 ` Bartlomiej Zolnierkiewicz
2009-04-24 3:00 ` Rogério Brito
2009-05-01 9:18 ` Rogério Brito
2009-05-01 10:31 ` Alan Cox
2009-05-01 11:50 ` Rogério Brito
2009-05-01 13:16 ` Alan Cox
2009-05-01 14:19 ` Rogério Brito
2009-05-01 11:20 ` Bartlomiej Zolnierkiewicz
2009-05-11 18:34 ` Jeff Garzik
2009-04-19 20:03 ` Rogério Brito
2009-04-19 23:41 ` Mark Lord
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=20090420194017.4edd5674@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=mjt@tls.msk.ru \
--cc=rbrito@ime.usp.br \
/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