From: speedy <speedy@3d-io.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re[2]: [BUG REPORT, 2.6.22] sata controler failure on nforce 2 chipset
Date: Tue, 29 Apr 2008 02:55:43 +0200 [thread overview]
Message-ID: <986072.20080429025543@3d-io.com> (raw)
In-Reply-To: <20080425231108.03dfa7cb.akpm@linux-foundation.org>
Hello Andrew,
Saturday, April 26, 2008, 8:11:08 AM, you wrote:
>> On Wed, 23 Apr 2008 01:14:59 +0200 speedy <speedy@3d-io.com> wrote:
>> Hello Linux kernel crew,
>>
>> [Consider this more as a datapoint then a bug report, as after
>> one network and one sata/southbridge issues showing up
>> interminnently, the ASRock motherboard involved will be
>> scrapped for a different one]
>>
>> The integrated NVidia sata controller and/or the hard-drive has failed
>> during operation with the following output:
AM> 2.6.22 is rather old. Can you please retest 2.6.25?
Unfortunately not, the motherboard has been changed for a
different one in that server, as I needed to deploy it. The
system is now behaving properly.
If someone of the kernel developers is interested in toying with
an NForce 2 motherboard which probably overheats the southbridge
and crashes approx. once a day under I/O load, I could ask the
management to donate it.
It reproduces:
* "RX unit hang detected" in i1000 drivers
* SATA soft-raid (infinite?) HDD resetting loop
;)
Cheers!
--
Best regards,
speedy mailto:speedy@3d-io.com
next prev parent reply other threads:[~2008-04-29 0:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <396712385.20080423011459@3d-io.com>
2008-04-26 6:11 ` [BUG REPORT, 2.6.22] sata controler failure on nforce 2 chipset Andrew Morton
2008-04-29 0:55 ` speedy [this message]
2008-04-29 14:48 ` Re[2]: " Oliver Pinter
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=986072.20080429025543@3d-io.com \
--to=speedy@3d-io.com \
--cc=akpm@linux-foundation.org \
--cc=linux-ide@vger.kernel.org \
--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 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).