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: <86802c440805182043n2a4855bcw6924f6df2fbdc9f4@mail.gmail.com>
Date:	Sun, 18 May 2008 20:43:09 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Ciaran McCreesh" <ciaran.mccreesh@...glemail.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 Sun, May 18, 2008 at 3:23 PM, Ciaran McCreesh
<ciaran.mccreesh@...glemail.com> wrote:
> On Sun, 18 May 2008 14:00:16 -0700
> "Yinghai Lu" <yhlu.kernel@...il.com> wrote:
>> >> wonder if init_apic_mapping need some delay with that strange
>> >> chipset.
>> >
>> > I don't see any additional information with apic=verbose with the
>> > broken kernel (although I only have a screen's worth of text that I
>> > can see -- the kernel doesn't get far enough to let me grab it).
>> > I've attached dmesg from a working kernel with apic=verbose in case
>> > that helps.
>>
>> or try to boot with initcall_debug to see where did it hang.
>
> The last initcall_debug messages are:
>
>    calling atiixp_ide_init+0x0/0x20
>    initcall atiixp_ide_init+0x0/0x20 returned 0 after 0 msecs
>    calling piix_ide_init+0x0/0xc0
>    initcall piix_ide_init+0x0/0xc0 returned 0 after 0 msecs
>    calling ide_scan_pcibus+0x0/0x100
>
> ide_scan_pcibus doesn't return. I tried shoving some printks in there,
> but as soon as I did it instead locked up in pci_init. Is it worth
> continuing this approach or will doing so not give useful results
> anyway?

could be pci iomem conflicts...
please enable CONFIG_PCI_DEBUG=y
and apply the following two debug patches

YH

View attachment "debug_extra_pci_res_range.patch" of type "text/x-patch" (1787 bytes)

View attachment "debug_extra_pci_bus_res.patch" of type "text/x-patch" (1299 bytes)