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]

Date:	Sat, 17 May 2008 20:55:20 -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 Sat, May 17, 2008 at 5:41 PM, Ciaran McCreesh
<ciaran.mccreesh@...glemail.com> wrote:
> The commit 3def3d6ddf43dbe20c00c3cbc38dfacc8586998f (x86:
> insert_resorce for lapic addr after e820_reserve_resources) causes my
> x86_64 box to to lock up early on in the boot process. Reverting only
> this commit with current git head gives a successful boot.
>
> The last messages outputted to the screen with a failed boot are:
>
>    pci 0000:00:13.2: OHCI: BIOS handoff failed (BIOS bug?) 00000184
>    Clocksource tsc unstable (delta = 475235503 ns)
>
> The handoff message appears not to be related, and occurs with all
> kernels. The 'clocksource' message appears only with the above commit.
>
> The box has an Abit F-190HD motherboard with a Q6600 CPU. A .config,
> dmesg from git head with the above commit reverted and lspci -v are
> attached.
>
> What further information can I provide to help work this issue out?

can you try to boot with apic=verbose? please don't revert that patch...

wonder if init_apic_mapping need some delay with that strange chipset.

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/