linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: "Mathieu Bérard" <Mathieu.Berard@crans.org>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	Adrian Bunk <bunk@stusta.de>
Subject: Re: Regression between 2.6.20 and 2.6.21-rc1: NCQ problem with ahci and Hitachi drive
Date: Mon, 05 Mar 2007 11:00:33 +0900	[thread overview]
Message-ID: <45EB79C1.3070107@gmail.com> (raw)
In-Reply-To: <45EB6980.90600@crans.org>

Hello, Mathieu.

Mathieu Bérard wrote:
> Hello,
> I have and laptop with an ICH6M SATA Controller and an Hitachi hard drive.
> While it worked well using the ahci module and with NCQ enabled using
> Linux 2.6.20, it does not work anymore (hang at boot) with 2.6.21-rc*
> 
> My drive is among those that were recently blacklisted (see lkml post
> "[PATCH] libata:
> add NCQ blacklist entries from Silicon Image Windowsdriver)
> (Model Number: HTS541010G9SA00 and Firmware Revision: MBZOC60D)
> This blacklisting patch is in -mm now.
> So there is probably a drive related issue here, I'm just wondering why
> it just work
> flawlessly with a 2.6.20...
> 
> Relevant part of kernel log:
> [   16.044663] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> [   16.089475] ata1.00: ATA-7: HTS541010G9SA00, MBZOC60D, max UDMA/100
> [   16.089525] ata1.00: 195371568 sectors, multi 0: LBA48 NCQ (depth 31/32)

No, your drive isn't blacklisted yet.  NCQ is still being enabled.

> [   16.091804] ata1.00: configured for UDMA/100
> [   18.151756] SCSI device sda: write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
[--snip--]
> [   18.151856] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB)
> [   18.151911] sda: Write Protect is off
> [   18.151977] SCSI device sda: write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
> [....]
> [   48.143940] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2
> frozen
> [   48.143999] ata1.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0
> cdb 0x0 data 4096 in
> [   48.144000]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask
> 0x4 (timeout)

It looks like IRQ isn't getting through.  Does giving "acpi=off" kernel
parameter make any difference?

-- 
tejun

  reply	other threads:[~2007-03-05  2:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-05  0:51 Regression between 2.6.20 and 2.6.21-rc1: NCQ problem with ahci and Hitachi drive Mathieu Bérard
2007-03-05  2:00 ` Tejun Heo [this message]
2007-03-05 21:27   ` Mathieu Bérard
2007-03-14  5:31     ` Len Brown

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=45EB79C1.3070107@gmail.com \
    --to=htejun@gmail.com \
    --cc=Mathieu.Berard@crans.org \
    --cc=bunk@stusta.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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).