From: Tejun Heo <htejun@gmail.com>
To: Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
Peer Chen <pchen@nvidia.com>, Kuan Luo <kluo@nvidia.com>
Subject: Re: 2.6.24.X: SATA/AHCI related boot delay. - not with 2.6.24.3
Date: Thu, 03 Apr 2008 10:48:22 +0900 [thread overview]
Message-ID: <47F43766.2070207@gmail.com> (raw)
In-Reply-To: <200804021909.41609.volker.armin.hemmann@tu-clausthal.de>
Hello, Volker.
Volker Armin Hemmann wrote:
> On Mittwoch, 2. April 2008, Tejun Heo wrote:
>> Volker Armin Hemmann wrote:
>>> On Mittwoch, 19. März 2008, Tejun Heo wrote:
>>>> Volker Armin Hemmann wrote:
>>>>> On Mittwoch, 19. März 2008, Tejun Heo wrote:
>>>>>> x UDMA/133 abar m8192@0xf9dfc000 port 0xf9dfc200
>>>>>>
>>>>>>> irq 315
>>>>>>> [ 38.125479] ata4: SATA max UDMA/133 abar m8192@0xf9dfc000 port
>>>>>>> 0xf9dfc280 irq 315
>>>>>>> [ 38.597035] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>>>>>>> [ 38.597732] ata1.00: ATA-7: WDC WD1600JS-00MHB1, 10.02E01, max
>>>>>>> UDMA/133 [ 38.597775] ata1.00: 312581808 sectors, multi 16: LBA48
>>>>>>> [ 38.598405] ata1.00: configured for UDMA/133
>>>>>>> [ 39.069342] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>>>>>>> [ 39.084225] ata2.00: ATA-8: SAMSUNG HD501LJ, CR100-12, max UDMA7
>>>>>>> [ 39.084264] ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth
>>>>>>> 0/32) [ 39.086268] ata2.00: configured for UDMA/133
>>>>>> So, just to confirm. With the updated patch, you don't see any
>>>>>> problem, right?
>>>>> Correct. With the updated patch I don't see problems in 'non-raid'
>>>>> mode. AHCI mode still has problems without nosmi. But that is an
>>>>> entirely different problem, right?
>>>> Yeap, can you please post the result of "lspci -nn"?
>>> with AHCI+nosmi, 2.6.24.3:
>>> 00:0a.0 SATA controller [0106]: nVidia Corporation MCP65 AHCI Controller
>>> [10de:044d] (rev a1)
>> Sorry about the long delay. Can you please test the attached patch in
>> both ahci and non-ahci modes w/o pci=nomsi and post resulting boot logs?
>
> patch -p1 < /home/energyman/mcp65-ahci-debug.patch
> patching file drivers/ata/libata-core.c
> Hunk #1 succeeded at 7136 (offset 2 lines).
> patching file drivers/ata/libata-eh.c
> Hunk #1 succeeded at 2083 (offset -107 lines).
> patching file drivers/pci/quirks.c
> Hunk #1 succeeded at 1733 with fuzz 1 (offset -122 lines).
>
> saved config, removed linux-2.6.24.3, unpacked 2.6.24.3 from tarball, reiser4
> and your patch, make oldconfig, make menuconfig, make all modules_install
> install.
>
> dmesgs are below.
[--snip--]
> In short, no changes at all.
Thanks for confirming.
Peer, Kuan. Volker is reporting detection problems on MCP65 AHCI.
The followings are what we've discovered till now.
1. When the controller is put into non-raid mode in BIOS
* If softreset is used, either the softreset itself or IDENTIFY
following it times out once. On retrial, it works fine. It
doesn't matter whether the SRST is issued by itself or as
follow-up-srst after hardreset. Using only hardreset works fine.
* The controller doesn't indicate MSI capability and MSI isn't used
by default.
2. When the controller is put into ahci mode in BIOS
* SRST works fine.
* The controller indicates MSI capability but MSI doesn't work
properly resulting in IRQ delivery failure. Adding
intx_disable_bug quirk doesn't help.
I've performed similar test on MCP67 and everything worked fine on it.
Both problems (SRST and MSI) can be worked around but I need more
information to work around those.
* Which chips are affected? Are there proper fixes?
* For the MSI problem, is it system wide problem or local to the ahci
controller?
Thanks.
--
tejun
next prev parent reply other threads:[~2008-04-03 1:48 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-09 18:22 2.6.24.X: SATA/AHCI related boot delay Volker Armin Hemmann
2008-03-10 13:05 ` Tejun Heo
2008-03-10 16:57 ` Volker Armin Hemmann
2008-03-16 8:34 ` Volker Armin Hemmann
2008-03-17 7:16 ` 2.6.24.X: SATA/AHCI related boot delay. - not with 2.6.24.3 Volker Armin Hemmann
2008-03-18 7:36 ` Tejun Heo
2008-03-18 10:59 ` Volker Armin Hemmann
2008-03-18 12:56 ` Tejun Heo
2008-03-18 13:33 ` Volker Armin Hemmann
2008-03-19 3:26 ` Tejun Heo
2008-03-19 3:27 ` Tejun Heo
2008-03-19 7:53 ` Volker Armin Hemmann
2008-03-19 8:58 ` Tejun Heo
2008-03-19 10:08 ` Volker Armin Hemmann
2008-03-19 11:43 ` Tejun Heo
2008-03-19 13:55 ` Volker Armin Hemmann
2008-04-02 3:57 ` Tejun Heo
2008-04-02 17:09 ` Volker Armin Hemmann
2008-04-03 1:48 ` Tejun Heo [this message]
2008-04-03 5:04 ` Volker Armin Hemmann
2008-04-03 5:26 ` Tejun Heo
2008-04-03 11:47 ` Volker Armin Hemmann
2008-04-11 6:05 ` Tejun Heo
2008-04-11 11:55 ` Volker Armin Hemmann
2008-04-12 1:27 ` Tejun Heo
2008-04-12 1:42 ` Jeff Garzik
2008-04-14 4:02 ` Peer Chen
2008-04-14 6:41 ` Volker Armin Hemmann
2008-04-14 8:11 ` Peer Chen
2008-04-14 21:12 ` Volker Armin Hemmann
2008-04-15 12:57 ` Peer Chen
2008-04-15 16:20 ` Volker Armin Hemmann
2008-04-18 5:51 ` Peer Chen
2008-04-19 13:48 ` Volker Armin Hemmann
2008-04-22 10:10 ` Peer Chen
2008-04-22 12:44 ` Volker Armin Hemmann
2008-04-22 14:11 ` Tejun Heo
2008-04-22 15:12 ` Volker Armin Hemmann
2008-05-29 14:54 ` Hemmann, Volker Armin
2008-05-30 4:19 ` Tejun Heo
2008-05-30 10:43 ` Hemmann, Volker Armin
2008-05-31 0:49 ` Tejun Heo
2008-06-03 7:56 ` Peer Chen
2008-06-09 9:17 ` Tejun Heo
2008-06-09 9:43 ` Tejun Heo
2008-06-09 14:49 ` Hemmann, Volker Armin
2008-04-03 10:44 ` Peer Chen
2008-04-11 6:06 ` Tejun Heo
2008-04-11 9:50 ` Peer Chen
2008-04-11 11:46 ` Volker Armin Hemmann
2008-03-27 16:40 ` Volker Armin Hemmann
-- strict thread matches above, loose matches on Subject: below --
2008-03-21 3:04 Fw: " osb972ww-linuxczmil
2008-03-21 10:42 ` Alan Cox
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=47F43766.2070207@gmail.com \
--to=htejun@gmail.com \
--cc=kluo@nvidia.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pchen@nvidia.com \
--cc=volker.armin.hemmann@tu-clausthal.de \
/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).