From: Simon Farnsworth <simon@farnz.org.uk>
To: linux-ide@vger.kernel.org
Subject: VIA AHCI NCQ [was: Re: Recent AHCI drivers do not work with VIA VT8251 controllers (regression in 2.6.19 from 2.6.18)]
Date: Wed, 31 Jan 2007 20:34:34 +0000 [thread overview]
Message-ID: <200701312034.36499.simon@farnz.org.uk> (raw)
In-Reply-To: <20070130155355.GB12475@reddwarf.farnz.org.uk>
[-- Attachment #1: Type: text/plain, Size: 943 bytes --]
On Tuesday 30 January 2007 15:53, Simon Farnsworth wrote:
> Hello,
>
> I've got a VIA VT8251 AHCI controller, driving two Maxtor SATA disks.
> Under Linux 2.6.18.5, it works; using 2.6.19.1, it fails to work (bug
> report at http://bugzilla.kernel.org/show_bug.cgi?id=7589 - note that
> pci=nomsi does not fix things for me, as I still get no interrupts).
>
I've been going through 2.6.20-rc releases this evening. 2.6.20-rc7 resolves
my AHCI fault (although not the MSI problem); it looks like Tejun Heo's fix
to ahci_thaw() in a718728f9e40ec79c0879ec6509a54fee214f5b2 fixes things for
my setup.
Of course, I'm now curious as to why NCQ is disabled on VIA AHCI controllers.
Is there a known hardware bug I should be wary of, or is it just a case of
being cautious due to the other issues with the VT8251 (in which case I'll
try enabling it and reporting back)?
--
Thanks for the code and the fix,
Simon Farnsworth
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-01-31 21:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 15:53 Recent AHCI drivers do not work with VIA VT8251 controllers (regression in 2.6.19 from 2.6.18) Simon Farnsworth
2007-01-31 20:34 ` Simon Farnsworth [this message]
2007-02-01 1:20 ` VIA AHCI NCQ [was: Re: Recent AHCI drivers do not work with VIA VT8251 controllers (regression in 2.6.19 from 2.6.18)] 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=200701312034.36499.simon@farnz.org.uk \
--to=simon@farnz.org.uk \
--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).