linux-kernel - Re: kernel boot hangs after x86: insert_resorce for lapic addr after e820_reserve

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <86802c440805231705g534e9245oc359dc316ae5b1cd@mail.gmail.com>
Date:	Fri, 23 May 2008 17:05:34 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Ciaran McCreesh" <ciaran.mccreesh@...glemail.com>
Cc:	"Bjorn Helgaas" <bjorn.helgaas@...com>, mingo@...e.hu,
	linux-kernel@...r.kernel.org
Subject: Re: kernel boot hangs after x86: insert_resorce for lapic addr after e820_reserve_resources

On Fri, May 23, 2008 at 4:50 PM, Ciaran McCreesh
<ciaran.mccreesh@...glemail.com> wrote:
> (Apologies for the delay. I've not had physical access to the box for a
> few days.)
>
> On Mon, 19 May 2008 20:22:45 -0700
> "Yinghai Lu" <yhlu.kernel@...il.com> wrote:
>> >> 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
>
> Sorry, I'm getting confused here. I can't send /proc/iomem with the
> ram_reserve patch applied since the system won't boot (and it appears
> to collide with the original commit, so I can't revert that and apply
> the patch to get a booting system).

You don't need that patch...

> Without the ram_reserve
> patch, /proc/iomem is as it was earlier in the discussion.
>
>> can you boot with pnpacpi=off ?
>
> No, that doesn't help either.
how about /proc/iomem with pnpacpi=off?

YH
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/