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: <86802c440805192022n29e191dfped3ee5afa7894288@mail.gmail.com>
Date:	Mon, 19 May 2008 20:22:45 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Ciaran McCreesh" <ciaran.mccreesh@...glemail.com>,
	"Bjorn Helgaas" <bjorn.helgaas@...com>
Cc:	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 Mon, May 19, 2008 at 8:16 PM, Ciaran McCreesh
<ciaran.mccreesh@...glemail.com> wrote:
> On Mon, 19 May 2008 19:48:38 -0700
> "Yinghai Lu" <yhlu.kernel@...il.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.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ