From: Tejun Heo <htejun@gmail.com>
To: "Berck E. Nash" <flyboy@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: 2.6.18 - AHCI detection pauses excessively
Date: Fri, 01 Dec 2006 22:59:07 +0900 [thread overview]
Message-ID: <4570352B.9000704@gmail.com> (raw)
In-Reply-To: <45702F9A.5020406@gmail.com>
Berck E. Nash wrote:
> Hrm. It's not a Silicon Image chip, or at least doesn't claim to be:
Yeap, the controller is ich ahci but I'm pretty sure there's a PMP chip
connected to one of them. Look for 4723 in the following page.
http://www.asus.com/products4.aspx?modelmenu=2&model=1198&l1=3&l2=11&l3=248
> 00:1f.2 SATA controller: Intel Corporation 82801GR/GH (ICH7 Family)
> Serial ATA Storage Controller AHCI (rev 01) (prog-if 01 [AHCI 1.0])
> Subsystem: ASUSTeK Computer Inc. Unknown device 2606
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> Latency: 0
> Interrupt: pin B routed to IRQ 316
> Region 0: I/O ports at e400 [size=8]
> Region 1: I/O ports at e080 [size=4]
> Region 2: I/O ports at e000 [size=8]
> Region 3: I/O ports at dc00 [size=4]
> Region 4: I/O ports at d880 [size=16]
> Region 5: Memory at febfb800 (32-bit, non-prefetchable) [size=1K]
> Capabilities: [80] Message Signalled Interrupts: Mask- 64bit-
> Queue=0/0 Enable+
> Address: fee0300c Data: 4179
> Capabilities: [70] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot+,D3cold-)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> And, remember, this behavior started in 2.6.18 and didn't exist in
> 2.6.17. Would it help if I narrowed down which patch caused it?
Yeah, that's probably because we're now using IRQ-driven PIO for
IDENTIFY, so we're often slower at detecting IDENTIFY failure. We're
planning to go back to polling IDENTIFY. Anyways, the problem here is
that the 4723 is emulating ATA device for configuration but it isn't
doing it quite right. I'll ask SIMG about it.
--
tejun
prev parent reply other threads:[~2006-12-01 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4557B7D2.2050004@gmail.com>
[not found] ` <455B0BD7.20108@gmail.com>
[not found] ` <455B5ADF.2040503@gmail.com>
[not found] ` <20061127033550.GB11250@htj.dyndns.org>
[not found] ` <456AA89C.909@gmail.com>
2006-11-29 8:55 ` 2.6.18 - AHCI detection pauses excessively Tejun Heo
2006-11-29 18:53 ` Berck E. Nash
2006-11-29 19:27 ` Mark Lord
2006-12-01 7:07 ` Tejun Heo
2006-12-01 13:35 ` Berck E. Nash
2006-12-01 13:59 ` Tejun Heo [this message]
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=4570352B.9000704@gmail.com \
--to=htejun@gmail.com \
--cc=flyboy@gmail.com \
--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).