public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David John <davidjon@xenontk.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
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: Thu, 18 Nov 2010 14:00:20 +0530	[thread overview]
Message-ID: <4CE4E41C.7020202@xenontk.org> (raw)
In-Reply-To: <20101117192449.GA12191@helgaas.com>

On 11/18/2010 12:54 AM, Bjorn Helgaas wrote:
> 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).

Attached in Bugzilla.

> If you happen to have Windows on this box as well, an
> Everest report (http://lavalys.com) would be interesting.
> If not, no worries.

Nope, no Windows on this box, Sorry.

Regards,
David.

      reply	other threads:[~2010-11-18  8:30 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
2010-11-18  8:30   ` David John [this message]

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=4CE4E41C.7020202@xenontk.org \
    --to=davidjon@xenontk.org \
    --cc=bjorn.helgaas@hp.com \
    --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