linux-kernel - Re: 2.6.38 hangs on boot until key is pressed

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:	Thu, 31 Mar 2011 14:52:17 +0200
From:	Andreas Herrmann <herrmann.der.user@...glemail.com>
To:	Tvrtko Ursulin <tvrtko@...ulin.net>
Cc:	linux-kernel@...r.kernel.org,
	Borislav Petkov <borislav.petkov@....com>
Subject: Re: 2.6.38 hangs on boot until key is pressed

On Thu, Mar 31, 2011 at 02:43:52PM +0200, Andreas Herrmann wrote:
> On Wed, Mar 30, 2011 at 07:18:17PM +0100, Tvrtko Ursulin wrote:
> > On Wed, 2011-03-30 at 17:53 +0200, Andreas Herrmann wrote:
> > > On Sun, Mar 27, 2011 at 08:18:05PM +0100, Tvrtko Ursulin wrote:
> > > > 
> > > > Hi all,
> > > > 
> > > > It always happens at the same spot. 2.6.37 is fine with almost
> > > > identical .config. Dmesg and config attached.
> > > 
> > > 
> > > Hi,
> > > 
> > > can you please send dmesg when 2.6.37 is booted.
> > > Also output of "lspci -nnxxxx" would be of interest.
> 
> Sorry, forgot to say that lspci -nnxxxx should also be run as root.
> (To get complete PCI config space.)
> 
> > > dmidecode (as root) would also help.
> > 
> > Attached.
> 
> Thanks.
> 
> > > Does it help to disable C1e in your BIOS (if there is such an option)?
> > > If there is no such option please try to boot 2.6.38.1 with idle=mwait
> > > on the command line.
> > 
> > Both tests (on their own) booted without hanging.
> 
> Ok.
> 
> This reminds me on some Gigabyte mainboards (for which we couldn't
> root cause the problem). The workaround for those boards was to boot
> with acpi_skip_timer_override.
> 
> The Gigabyte mainboards had some odd lapic_id settings and yours too:
> 
> > [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
> > [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
> > [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x02] enabled)
> > [    0.000000] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] enabled)
> > [    0.000000] ACPI: LAPIC (acpi_id[0x05] lapic_id[0x84] disabled)   <====
> > [    0.000000] ACPI: LAPIC (acpi_id[0x06] lapic_id[0x85] disabled)   <====
> > [    0.000000] ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi_base[0])
> > [    0.000000] IOAPIC[0]: apic_id 4, version 33, address 0xfec00000, GSI 0-23
> 
> This should rather look like

Sorry, forget this statement. You have a quad-core and not a six-core
CPU so this setting seems to be ok. (But it's still worth to try the
acpi_skip_timer_override option.)


Andreas
--
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/