From: Tejun Heo <htejun@gmail.com>
To: Christian <christiand59@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ
Date: Thu, 22 Mar 2007 01:35:52 +0900 [thread overview]
Message-ID: <46015EE8.7000001@gmail.com> (raw)
In-Reply-To: <200703211534.30943.christiand59@web.de>
Christian wrote:
> I've tested multiple kernels (including -mm series) in the range of 2.6.19.7
> (before sata_nv adma support went in) up to 2.6.20-rc4.
> Every NCQ enabled kernel I've tested showed ata errors in dmesg. So I came to
> the conclusion that my system was faulty. I ran memtest86+ for a long time,
> but no errors were found. After some fiddling with my HW I discovered that
> the nforce chipset fan induced some kind of electro magnetic interference to
> the southbridge, which could clearly be heard as a low frequency noise if I
> plugged in my speakers to the onboard sound. After replacing the fan, my
> system is stable again. Now running 2.6.21-rc3-mm2+rsdlv31 without errors.
> Really strange problem he ;-)
Man, that's the strangest way to solve ATA command failures I've ever
heard of. Kudos to you for finding it out. :-)
--
tejun
next prev parent reply other threads:[~2007-03-21 16:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.wBi/iM3CKSfrll7UnPHTbU0scEQ@ifi.uio.no>
2007-03-16 13:56 ` [BUG 2.6.21-rc3-git9] SATA NCQ failure with Samsum HD401LJ Robert Hancock
2007-03-16 14:44 ` Christian
2007-03-18 5:43 ` Tejun Heo
2007-03-18 20:31 ` Christian
2007-03-19 2:48 ` Tejun Heo
2007-03-19 7:08 ` Christian
2007-03-19 7:39 ` Tejun Heo
2007-03-21 14:34 ` Christian
2007-03-21 16:35 ` Tejun Heo [this message]
2007-03-19 12:09 ` Jeff Garzik
2007-03-20 9:41 ` Max Kellermann
2007-03-19 12:21 ` Pablo Sebastian Greco
2007-03-16 11:20 Max Kellermann
2007-03-16 14:34 ` Christian
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=46015EE8.7000001@gmail.com \
--to=htejun@gmail.com \
--cc=christiand59@web.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.