From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: David John <davidjon@xenontk.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.37-rc1 / rc2 Regression] PCI: Kernel Hangs On Boot
Date: Wed, 17 Nov 2010 12:24:49 -0700 [thread overview]
Message-ID: <20101117192449.GA12191@helgaas.com> (raw)
In-Reply-To: <4CE3F763.6080002@xenontk.org>
On Wed, Nov 17, 2010 at 09:10:19PM +0530, David John wrote:
> Commit dc9887dc ("x86/PCI: allocate space from the end of a region, not
> the beginning") causes the kernel to hang on my Dell Inspiron 1545.
> 2.6.36 and booting with pci=nocrs works fine. Reverting this commit also
> works. I am attaching the kernel log and system iomem from the working
> 2.6.36. It hangs at this location consistently:
>
> pci-stub: invalid id string ""
> ACPI: AC Adapter [AC] (on-line)
> input: Lid Switch as
> /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
>
> < hang >
>
> Let me know if you need any other info.
Thanks a lot for this report. I opened this bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=23132
to track it.
Would you mind attaching the dmesg log from 2.6.37-rc2 with
commit dc9887dc reverted? That should have a little more
information (PCI allocation closer to what fails, and also
more PNP resource information).
The PCI assignments Linux did are only for bridge windows,
and I don't see anything actually *using* those windows, so
I suspect they might conflict with an ACPI/PNP device, which
is what we're poking at when it hangs.
If you happen to have Windows on this box as well, an
Everest report (http://lavalys.com) would be interesting.
If not, no worries.
Thanks again,
Bjorn
next prev parent reply other threads:[~2010-11-17 19:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 15:40 [2.6.37-rc1 / rc2 Regression] PCI: Kernel Hangs On Boot David John
2010-11-17 19:24 ` Bjorn Helgaas [this message]
2010-11-18 8:30 ` David John
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=20101117192449.GA12191@helgaas.com \
--to=bjorn.helgaas@hp.com \
--cc=davidjon@xenontk.org \
--cc=jbarnes@virtuousgeek.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