From: Andreas Herrmann <herrmann.der.user@googlemail.com>
To: Tvrtko Ursulin <tvrtko@ursulin.net>
Cc: linux-kernel@vger.kernel.org, Borislav Petkov <borislav.petkov@amd.com>
Subject: Re: 2.6.38 hangs on boot until key is pressed
Date: Thu, 31 Mar 2011 14:52:17 +0200 [thread overview]
Message-ID: <20110331125217.GB14693@alberich.amd.com> (raw)
In-Reply-To: <20110331124352.GA14693@alberich.amd.com>
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
next prev parent reply other threads:[~2011-03-31 12:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-27 19:18 2.6.38 hangs on boot until key is pressed Tvrtko Ursulin
2011-03-30 15:53 ` Andreas Herrmann
2011-03-30 18:18 ` Tvrtko Ursulin
2011-03-31 12:43 ` Andreas Herrmann
2011-03-31 12:52 ` Andreas Herrmann [this message]
2011-03-31 16:24 ` Tvrtko Ursulin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110331125217.GB14693@alberich.amd.com \
--to=herrmann.der.user@googlemail.com \
--cc=borislav.petkov@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tvrtko@ursulin.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox