From: Yinghai <yinghai.lu@oracle.com>
To: Andy Isaacson <adi@hexapodia.org>
Cc: linux-kernel@vger.kernel.org,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Chris Wright <chrisw@sous-sol.org>,
Matthew Wilcox <willy@linux.intel.com>
Subject: Re: [2.6.34-rc1 REGRESSION] ahci 0000:00:1f.2: controller reset failed (0xffffffff)
Date: Tue, 06 Apr 2010 18:08:04 -0700 [thread overview]
Message-ID: <4BBBDAF4.4020304@oracle.com> (raw)
In-Reply-To: <20100406225425.GA8292@hexapodia.org>
On 04/06/2010 03:54 PM, Andy Isaacson wrote:
> This Dell Precision WorkStation T3400 doesn't boot 2.6.34-rc1 (tried
> 522dba71). 2.6.33 was fine, and it's been running various stable
> kernels for the last 18 months. Unfortunately I can't reasonably bisect
> as I need this machine to be usable, but I can test specific patches or
> options. (three or four reboots is fine, 15 is not.)
>
> full dmesg from failing boot and a successful boot at
> http://web.hexapodia.org/~adi/tmp/20100406-pci-ahci-reset-fail/
>
> I suspect it's due to:
>
> [ 3.094038] pci 0000:00:1f.2: no compatible bridge window for [mem 0xff970000-0xff9707ff]
> [ 3.103001] pci 0000:00:1f.2: can't reserve [mem 0xff970000-0xff9707ff]
>
> so I've CCed a few recent committers to setup-res.c.
>
can you try to boot with pci=nocrs ?
also please check with -rc4.
YH
next prev parent reply other threads:[~2010-04-07 1:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 22:54 [2.6.34-rc1 REGRESSION] ahci 0000:00:1f.2: controller reset failed (0xffffffff) Andy Isaacson
2010-04-07 1:08 ` Yinghai [this message]
2010-04-07 1:28 ` Andy Isaacson
2010-04-07 2:19 ` Yinghai Lu
2010-04-07 3:59 ` Bjorn Helgaas
2010-04-07 4:13 ` Andy Isaacson
2010-04-07 4:21 ` Bjorn Helgaas
2010-04-07 17:16 ` Andy Isaacson
2010-04-07 18:08 ` Bjorn Helgaas
2010-04-07 18:42 ` Andy Isaacson
2010-04-12 17:56 ` Bjorn Helgaas
2010-04-12 19:33 ` Andy Isaacson
2010-04-12 21:56 ` Matthew Wilcox
2010-04-13 2:14 ` H. Peter Anvin
2010-04-13 1:51 ` H. Peter Anvin
2010-04-09 19:10 ` Maciej Rutecki
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=4BBBDAF4.4020304@oracle.com \
--to=yinghai.lu@oracle.com \
--cc=adi@hexapodia.org \
--cc=bjorn.helgaas@hp.com \
--cc=chrisw@sous-sol.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@linux.intel.com \
/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.