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: Sat, 12 Apr 2008 10:27:20 +0900 [thread overview]
Message-ID: <48000FF8.300@gmail.com> (raw)
In-Reply-To: <200804111355.55364.volker.armin.hemmann@tu-clausthal.de>
Volker Armin Hemmann wrote:
> Hi,
>
>> Aiee.... Can you please try 2.6.25-rc8 with both configurations? And
>> w/o systemrescuecd? Just seeing whether things mount properly or not is
>> good enough. There isn't much risk of losing data.
>
> 2.6.25-rc8 is a 'no change'. AHCI+pci=nomsi boots, AHCI without hangs.
> with AHCI I also get this:
>
> [ 0.363828] ------------[ cut here ]------------
> [ 0.363828] WARNING: at drivers/ata/ahci.c:645 ahci_init_one+0x190/0xa3a()
> [ 0.363828] Modules linked in:
> [ 0.363828] Pid: 1, comm: swapper Not tainted 2.6.25-rc8 #2
Heh.. that's AHCI_EN not getting set. Peer, any ideas? The driver set
AHCI_EN in the HOST_CTL register but on reading back it's still clear.
Thanks.
--
tejun
next prev parent reply other threads:[~2008-04-12 1:27 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
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 [this message]
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=48000FF8.300@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).