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 14:26:12 +0900 [thread overview]
Message-ID: <47F46A74.504@gmail.com> (raw)
In-Reply-To: <200804030704.21480.volker.armin.hemmann@tu-clausthal.de>
Hello, Volker.
Volker Armin Hemmann wrote:
>>> 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?
>
>
> I rebooted with non-raid set, without pci=nomsi
>
> this is cat /proc/interrupts:
> CPU0 CPU1
> 0: 57 1 IO-APIC-edge timer
> 1: 0 81 IO-APIC-edge i8042
> 8: 0 1 IO-APIC-edge rtc
> 9: 0 1 IO-APIC-fasteoi acpi
> 12: 0 3 IO-APIC-edge i8042
> 17: 2 2868 IO-APIC-fasteoi nvidia
> 18: 0 0 IO-APIC-fasteoi EMU10K1
> 22: 4 745 IO-APIC-fasteoi ehci_hcd:usb1
> 314: 0 158 PCI-MSI-edge eth0
> 315: 7 12769 PCI-MSI-edge ahci
>
> as you can see, only the sata controller and the network uses msi.
>
> And networking works - or I wouldn't be able to send you this mail.
I guess the ahci controller works too. This is getting confusing, so
MSI doesn't work iff the controller is configured as ahci in BIOS?
> I will reboot from systemresucecd later today and post some results with
> ahci-mode set, no nomsi. Just can't try patches that way.
Is sytemrescuecd using the same kernel? Otherwise, it will only add
more to the confusion.
--
tejun
next prev parent reply other threads:[~2008-04-03 5:26 UTC|newest]
Thread overview: 60+ 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
2008-04-03 5:04 ` Volker Armin Hemmann
2008-04-03 5:26 ` Tejun Heo [this message]
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 4:02 ` Peer Chen
2008-04-14 6:41 ` Volker Armin Hemmann
2008-04-14 8:11 ` Peer Chen
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 12:57 ` Peer Chen
2008-04-15 16:20 ` Volker Armin Hemmann
2008-04-18 5:51 ` Peer Chen
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 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-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-03 10:44 ` Peer Chen
2008-04-11 6:06 ` Tejun Heo
2008-04-11 9:50 ` Peer Chen
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=47F46A74.504@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.