From: Mark Lord <liml@rtr.ca>
To: Harri Olin <harri.olin@gmail.com>
Cc: linux-ide@vger.kernel.org, Artem Bokhan <aptem@ngs.ru>
Subject: Re: sata_mv, io stucks
Date: Sat, 15 Nov 2008 23:59:44 -0500 [thread overview]
Message-ID: <491FA8C0.2090804@rtr.ca> (raw)
In-Reply-To: <491FA4D8.1010708@rtr.ca>
Mark Lord wrote:
>
> Yeah, I see what I was missing earlier: "(timeout)".
> So it's "none of" the driver paths.
>
> This could very well be due to one/several of the as-yet un-addressed
> chipset errata for the 6081. Someday we'll have software workarounds
> for those, but I'm (still) waiting on Marvell for stuff.
>
> I will look and see if this makes sense based on the errata info
> that I have already though (under NDA).
>
> Harri / Artem: what type/speed of slots are your 6081 controllers in?
> PCI, or PCI-X? Bus speed?
..
Mmm.. Harri at least previously said:
> Contoller is Supermicro AOC-SAT2-MV8, connected to 133MHz PCI-X slot on one computer,
> 66MHz 64bit PCI slot on the second machine and to normal 32bit PCI slot on third computer.
..
And Artem said:
> The controller is AOC-SAT2-MV8 too.
..
So I guess I need to know if Artem is using PCI-X, and the bus width + speed.
Cheers
next prev parent reply other threads:[~2008-11-16 4:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 12:25 sata_mv, io stucks Artem Bokhan
2008-10-23 8:53 ` Artem Bokhan
2008-10-23 16:07 ` Mark Lord
2008-11-15 15:18 ` Harri Olin
2008-11-15 21:35 ` Mark Lord
2008-11-15 23:41 ` Harri Olin
2008-11-15 23:44 ` Justin Piszcz
2008-11-15 23:47 ` Harri Olin
2008-11-15 23:52 ` Justin Piszcz
2008-11-16 4:43 ` Mark Lord
2008-11-16 4:59 ` Mark Lord [this message]
2008-11-16 9:13 ` Justin Piszcz
2008-11-17 5:22 ` Mark Lord
2008-11-17 14:10 ` Bokhan Artem
2008-11-16 12:35 ` Harri Olin
2008-11-16 17:32 ` Harri Olin
2008-10-23 13:31 ` Harri Olin
2008-10-23 16:32 ` Bokhan Artem
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=491FA8C0.2090804@rtr.ca \
--to=liml@rtr.ca \
--cc=aptem@ngs.ru \
--cc=harri.olin@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).