From: Tejun Heo <tj@kernel.org>
To: xerces8 <xerces8@butn.net>
Cc: Sergey Spiridonov <sena@hurd.homeunix.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: GA-MA790FX-DS5 SATA ahci NCQ erros on Jmicron 20360/20363 (JMB363) kernel 2.6.25-2 Debian/Lenny
Date: Sat, 30 Aug 2008 13:00:22 +0200 [thread overview]
Message-ID: <48B92846.7050004@kernel.org> (raw)
In-Reply-To: <WorldClient-F200808241844.AA44240046@butn.net>
xerces8 wrote:
> I have a JMB363 myself and it has its share of problems.
> I would say it is buggy hardware. (why would they otherwise
> release a new windows driver every week ? if not to workaround
> bugs in HW ;-)
Well, FWIW, JMB ahci's are one of my favorites and usually very well
behaved.
> My WD MyBook Studio Edition 500 GB external eSATA drive does not
> work on the JMB363 correctly no matter what I try. Both
> under linux and windows. I think the best was 30 minutes of
> (apparent) error free operation under windows.
This one is being discussed both with JMB and WD. It seems the bridge
chip used in the WD external drives is somehow incompatible with the
JMB ahci's. Don't know whose fault it is or how it can be worked
around yet. The issue is being tracked in the following bugzilla.
http://bugzilla.kernel.org/show_bug.cgi?id=9913
--
tejun
next prev parent reply other threads:[~2008-08-30 11:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <g8p6po$nm$1@ger.gmane.org>
2008-08-23 22:38 ` GA-MA790FX-DS5 SATA ahci NCQ erros on Jmicron 20360/20363 (JMB363) kernel 2.6.25-2 Debian/Lenny Jeff Garzik
2008-08-23 23:27 ` Chr
2008-08-24 0:27 ` Sergey Spiridonov
2008-08-24 4:39 ` Jeff Garzik
2008-08-24 23:31 ` Sergey Spiridonov
2008-08-25 14:52 ` xerces8
2008-09-17 12:07 ` Sergey Spiridonov
2008-09-17 15:31 ` Krzysztof Halasa
2008-08-24 16:44 ` xerces8
2008-08-30 11:00 ` Tejun Heo [this message]
2008-08-30 18:13 ` xerces8
2008-08-31 9:33 ` 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=48B92846.7050004@kernel.org \
--to=tj@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sena@hurd.homeunix.org \
--cc=xerces8@butn.net \
/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).