From: Peter Favrholdt <linux-ide@how.dk>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: linux-ide@vger.kernel.org
Subject: Re: sata_promise: port is slow to respond, reset failed
Date: Tue, 04 Sep 2007 19:20:29 +0200 [thread overview]
Message-ID: <46DD93DD.8020100@how.dk> (raw)
In-Reply-To: <18141.5115.238011.870159@alkaid.it.uu.se>
Mikael Pettersson wrote:
> nForce2. Hmm..
Peter Favrholdt wrote:
> > 11: 27474 XT-PIC-XT libata, libata, ohci_hcd:usb3,
> > NVidia nForce2
> That "mystery" device makes me strongly suspect that you've
> loaded the binary-only nvidia drivers. If that's true, then
> the machine's problems may just as well be caused by that driver,
> not sata_promise. (We've seen that happen before.)
I didn't load any special NVidia driver - vanilla kernel only. The
graphics card is Matrox G550. The nForce2 could be the nForce2 SMBus or
the nForce2 IDE. Here is the result of dmesg | grep -i nforce
[ 26.379422] NFORCE2: IDE controller at PCI slot 0000:00:09.0
[ 26.379481] NFORCE2: chipset revision 162
[ 26.379525] NFORCE2: not 100% native mode: will probe irqs later
[ 26.379575] NFORCE2: BIOS didn't set cable bits correctly. Enabling
workaround.
[ 26.379634] NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller
[ 31.861284] i2c_adapter i2c-0: nForce2 SMBus adapter at 0x5000
[ 31.861391] i2c_adapter i2c-1: nForce2 SMBus adapter at 0x5500
> I can reproduce it on an Intel 440BX chipset machine with a PIII.
> However, that chipset, while very good in its day, is rather old now.
I believe the problem here only shows if all four sata ports are
stressed simultaneously (I should test this thoroughly). The dependence
on Barracuda 7200.10 could be because these disks are faster than the
others tested, this needed in order for the PCI contention to arise?
(I'm still wild-guessing here).
Best regards,
Peter
next prev parent reply other threads:[~2007-09-04 17:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-03 8:11 sata_promise: port is slow to respond, reset failed Mikael Pettersson
2007-09-03 11:59 ` Tomi Orava
2007-09-03 20:38 ` Peter Favrholdt
2007-09-04 8:14 ` Mikael Pettersson
2007-09-04 17:20 ` Peter Favrholdt [this message]
2007-09-04 18:47 ` Mikael Pettersson
2007-09-04 16:37 ` Chuck Ebbert
-- strict thread matches above, loose matches on Subject: below --
2007-09-02 17:02 Mikael Pettersson
2007-09-02 23:04 ` Peter Favrholdt
2007-09-02 15:11 Mikael Pettersson
2007-09-02 11:12 Peter Favrholdt
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=46DD93DD.8020100@how.dk \
--to=linux-ide@how.dk \
--cc=linux-ide@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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).