mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Ciaran McCreesh" <ciaran.mccreesh@googlemail.com>,
	"Bjorn Helgaas" <bjorn.helgaas@hp.com>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org
Subject: Re: kernel boot hangs after x86: insert_resorce for lapic addr after e820_reserve_resources
Date: Mon, 19 May 2008 20:25:49 -0700	[thread overview]
Message-ID: <86802c440805192025x5172dd3eh583c79823b0d38a2@mail.gmail.com> (raw)
In-Reply-To: <86802c440805192022n29e191dfped3ee5afa7894288@mail.gmail.com>

On Mon, May 19, 2008 at 8:22 PM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> On Mon, May 19, 2008 at 8:16 PM, Ciaran McCreesh
> <ciaran.mccreesh@googlemail.com> wrote:
>> On Mon, 19 May 2008 19:48:38 -0700
>> "Yinghai Lu" <yhlu.kernel@gmail.com> wrote:
>>> >> >> could be pci iomem conflicts...
>>> >> >> please enable CONFIG_PCI_DEBUG=y
>>> >> >> and apply the following two debug patches
>>> >> >
>>> >> > dmesg with debugging attached.
>>> >>
>>> >> the iomem allocation seems good...
>>> >>
>>> >> can you send out /proc/iomem?
>>> >
>>> > 00000000-0009ffff : pnp 00:09
>>> > <snip>
>>>
>>> seems acpi pnp resource cause some problem....
>>>
>>> please try attached patch and send out /proc/mtrr
>>
>> The patch doesn't help I'm afraid.
>
> sorry, please send /proc/iomem
>
> after check request_resource and insert resource...
>
> it seems if you insert or request one small one, and request big one,
> then only have big one, but if you insert the big one, the small one
> will because big one's child...
>
> so at that case, could be pnp res return from acpi (dsdt) is bigger
> than e820 region...
>
> so it seems the offending patch just reveal problem cause by pnp code.

can you boot with pnpacpi=off ?

YH

  reply	other threads:[~2008-05-20  3:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-18  0:41 Ciaran McCreesh
2008-05-18  3:55 ` Yinghai Lu
2008-05-18 15:41   ` Ciaran McCreesh
2008-05-18 21:00     ` Yinghai Lu
2008-05-18 22:23       ` Ciaran McCreesh
2008-05-19  3:43         ` Yinghai Lu
2008-05-20  0:44           ` Ciaran McCreesh
2008-05-20  1:22             ` Yinghai Lu
2008-05-20  1:24               ` Ciaran McCreesh
2008-05-20  2:48                 ` Yinghai Lu
2008-05-20  3:16                   ` Ciaran McCreesh
2008-05-20  3:22                     ` Yinghai Lu
2008-05-20  3:25                       ` Yinghai Lu [this message]
2008-05-23 23:50                       ` Ciaran McCreesh
2008-05-24  0:05                         ` Yinghai Lu
2008-05-24  1:09                           ` Ciaran McCreesh
2008-05-24  1:51                             ` Yinghai Lu
2008-05-24  2:29                               ` Yinghai Lu

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=86802c440805192025x5172dd3eh583c79823b0d38a2@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=ciaran.mccreesh@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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

all inboxes | Powered by JetHome®