From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tejun Heo <htejun@gmail.com>
Cc: Mark Hatle <fray@gate.crashing.org>, linux-ide@vger.kernel.org
Subject: Re: sata_nv failure on 2.4.18 (Fedora Core 6)
Date: Wed, 25 Oct 2006 15:26:16 +1000 [thread overview]
Message-ID: <1161753976.22582.46.camel@localhost.localdomain> (raw)
In-Reply-To: <20061025042811.GJ13677@htj.dyndns.org>
> Does the problem occur on 2.6.18 but not on earlier version? If it
> doesn't happen on 2.6.17, we can rule out h/w problem.
Difficult to say... this is a fresh install of FC6 and it's a production
box (heh, it handles my email !) so we can't easily test plenty
different kernels on it unfortunately... If 2.6.17 can be booted and
works fine on FC6, might be worth giving it a go but I wouldnt' expect
too many tests of that sort.
> * If 2.6.17 shows the same problem : could be a faulty drive or
> problem in the controller. NV SATA controllers supply two
> interfaces - legacy TF/BMDMA and ADMA. The former tends to react
> badly when error condition occurs. Driver for ADMA interface is
> under development. It could be that the controller cannot cope with
> transient transmission errors. If this is the case, ADMA driver
> should be able to fix it.
Do we have any contact at nVidia that could rule on that issue ? The
drives both appear to work fine on the SIL controller...
> * If 2.6.17 doesn't show the same problem : My first suspicion is
> weird IRQ problem. Play with the usual IRQ options - acpi, noacpi,
> etc... and see if anything changes.
Ben.
next prev parent reply other threads:[~2006-10-25 5:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 4:01 sata_nv failure on 2.4.18 (Fedora Core 6) Mark Hatle
2006-10-25 4:28 ` Tejun Heo
2006-10-25 4:35 ` Mark Hatle
2006-10-25 5:03 ` Mark Hatle
2006-10-25 5:27 ` Benjamin Herrenschmidt
2006-10-25 5:46 ` Tejun Heo
2006-10-25 5:26 ` Benjamin Herrenschmidt [this message]
2006-10-25 5:51 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2006-11-09 22:29 Jonathan Cohen
2006-11-21 6:58 ` Tejun Heo
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=1161753976.22582.46.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=fray@gate.crashing.org \
--cc=htejun@gmail.com \
--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).