From: Tejun Heo <htejun@gmail.com>
To: Florian Effenberger <florian@effenberger.org>
Cc: linux-ide@vger.kernel.org, jeff@garzik.org
Subject: Re: libata interface fatal error
Date: Mon, 25 Jun 2007 11:49:04 +0900 [thread overview]
Message-ID: <467F2D20.1080700@gmail.com> (raw)
In-Reply-To: <467E5652.3060500@effenberger.org>
Florian Effenberger wrote:
> sorry, it seems it was all a false alert and our mainboard was
> defective. At the end, it turned on only sometimes. To test it, we
> wanted to install Windows, which didn't work as well.
>
> Now the dealer changed the motherboard, and we are just fine with 3.0
> Gbps and Kernel 2.6.21.5.
>
> Sorry for the big confusion and for your great help! I didn't know the
> board was defective in the first place, there have been no indications
> like that...
Yeah, things like these are tricky. SATA is usually the first one to
suffer from hardware defect including power fluctuation due to input
power, PSU or on-board voltage regulator problems because the link is
relatively long and runs at very high speed. I also heard that SATA
cables should have been made more resistant to interference but I'm no
expert in that area.
It's interesting to see how it got solved. Thanks for another data
point to blame hardware when I don't have a clue. :-)
--
tejun
next prev parent reply other threads:[~2007-06-25 2:49 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-26 9:43 libata interface fatal error Florian Effenberger
2007-05-29 9:16 ` Tejun Heo
2007-05-29 14:16 ` Florian Effenberger
2007-06-06 21:23 ` Florian Effenberger
2007-06-07 9:50 ` Tejun Heo
2007-06-07 14:08 ` Florian Effenberger
2007-06-13 10:37 ` Florian Effenberger
2007-06-14 9:43 ` Tejun Heo
2007-06-14 11:12 ` Florian Effenberger
2007-06-14 12:25 ` Tejun Heo
2007-06-14 15:12 ` Florian Effenberger
2007-06-18 3:10 ` Tejun Heo
2007-06-18 6:08 ` Tomi Orava
2007-06-18 6:28 ` Tejun Heo
2007-06-18 10:38 ` Florian Effenberger
2007-06-18 10:44 ` Tejun Heo
2007-06-16 10:23 ` Florian Effenberger
2007-06-18 3:13 ` Tejun Heo
2007-06-18 10:44 ` Florian Effenberger
2007-06-18 10:56 ` Tejun Heo
2007-06-18 11:28 ` Florian Effenberger
2007-06-18 11:30 ` Tejun Heo
2007-06-18 11:32 ` Florian Effenberger
2007-06-24 11:32 ` Florian Effenberger
2007-06-25 2:49 ` Tejun Heo [this message]
2007-06-25 8:47 ` Florian Effenberger
-- strict thread matches above, loose matches on Subject: below --
2007-06-18 7:05 Mikael Pettersson
2007-06-18 7:13 ` Tejun Heo
2007-06-18 10:47 ` Florian Effenberger
2007-06-18 17:14 ` Ansgar Knappheide
2007-06-18 18:54 ` Tomi Orava
2007-05-24 13:25 Florian Effenberger
2007-05-24 13:45 ` Tejun Heo
2007-05-24 14:08 ` Florian Effenberger
2007-05-24 14:21 ` Tejun Heo
2007-05-24 14:47 ` Florian Effenberger
2007-05-24 14:53 ` Tejun Heo
2007-05-24 15:28 ` Florian Effenberger
2007-05-24 14:55 ` Greg Freemyer
2007-05-24 14:59 ` Tejun Heo
2007-05-24 15:00 ` Florian Effenberger
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=467F2D20.1080700@gmail.com \
--to=htejun@gmail.com \
--cc=florian@effenberger.org \
--cc=jeff@garzik.org \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).