public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com,
	ak@linux.intel.com, tglx@linutronix.de,
	Yinghai Lu <yinghai@kernel.org>,
	Huang Ying <ying.huang@intel.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-tip-commits@vger.kernel.org
Subject: Re: [boot crash] Re: [tip:x86/mce3] x86, mce: use 64bit machine check code on 32bit
Date: Mon, 17 Aug 2009 10:35:44 +0200	[thread overview]
Message-ID: <20090817083544.GC15390@elte.hu> (raw)
In-Reply-To: <4A88E3E4.40506@jp.fujitsu.com>


* Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com> wrote:

> Hi Ingo,
> 
> Ingo Molnar wrote:
> > * tip-bot for Andi Kleen <ak@linux.intel.com> wrote:
> > 
> >> Commit-ID:  4efc0670baf4b14bc95502e54a83ccf639146125
> >> Gitweb:     http://git.kernel.org/tip/4efc0670baf4b14bc95502e54a83ccf639146125
> >> Author:     Andi Kleen <ak@linux.intel.com>
> >> AuthorDate: Tue, 28 Apr 2009 19:07:31 +0200
> >> Committer:  H. Peter Anvin <hpa@zytor.com>
> >> CommitDate: Thu, 28 May 2009 09:24:13 -0700
> >>
> >> x86, mce: use 64bit machine check code on 32bit
> 
> (snip)
> 
> > 
> > This commit causes a new regression, it broke the bootup on one of 
> > my -tip testsystems, an older, Pentium-M based HP laptop (HP 
> > OmniBook 6000 EA).
> > 
> > The symptom is that the bootup hard-hangs after MCE init:
> > 
> >  [    0.022996] Mount-cache hash table entries: 512
> >  [    0.024996] Initializing cgroup subsys debug
> >  [    0.025996] Initializing cgroup subsys cpuacct
> >  [    0.026995] Initializing cgroup subsys devices
> >  [    0.027995] Initializing cgroup subsys freezer
> >  [    0.028995] mce: CPU supports 5 MCE banks
> > 
> > Kernel config attached. cpuinfo:
> > 
> > processor	: 0
> > vendor_id	: GenuineIntel
> > cpu family	: 6
> > model		: 8
> > model name	: 06/08
> > stepping	: 10
> > cpu MHz		: 846.372
> 
> According to the cpuid, I suppose this cpu is Pentium III.

yep.

> > fdiv_bug	: no
> > hlt_bug		: no
> > f00f_bug	: no
> > coma_bug	: no
> > fpu		: yes
> > fpu_exception	: yes
> > cpuid level	: 2
> > wp		: yes
> > flags		: fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse up
> 
> None of acpi, apic, and tm is available.
> So at least thermal codes should be innocent.

yes.

> > bogomips	: 1692.74
> > clflush size	: 32
> > power management:
> > 
> > 	Ingo
> 
> Could you try boot your laptop with mce=nobootlog?

Hm, why should that make any difference? mce=nobootlog only 
influences whether we pass records into the mcelog buffer but does 
not affect whether we touch the hardware.

	Ingo

  reply	other threads:[~2009-08-17  8:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tip-4efc0670baf4b14bc95502e54a83ccf639146125@git.kernel.org>
2009-08-12 11:36 ` [boot crash] Re: [tip:x86/mce3] x86, mce: use 64bit machine check code on 32bit Ingo Molnar
2009-08-17  5:00   ` Hidetoshi Seto
2009-08-17  8:35     ` Ingo Molnar [this message]
2009-08-17  9:08       ` Hidetoshi Seto
2009-08-17  9:18         ` Ingo Molnar
2009-08-17  9:20         ` Ingo Molnar
2009-08-17 11:08           ` Andi Kleen
2009-08-17 11:24             ` Ingo Molnar
2009-09-22 15:41             ` Ingo Molnar
2009-09-23 15:22               ` Andi Kleen
2009-09-23 16:18                 ` Ingo Molnar
2009-08-17 10:56         ` Andi Kleen
2009-08-17 11:00           ` Ingo Molnar
2009-08-17 11:29         ` [PATCH] x86, mce: Don't initialize MCEs on unknown CPUs Ingo Molnar
2009-08-17 11:35           ` Andi Kleen
2009-08-17 11:53             ` Ingo Molnar
2009-08-17 13:28               ` Andi Kleen
2009-08-17 11:25   ` [boot crash] Re: [tip:x86/mce3] x86, mce: use 64bit machine check code on 32bit Andi Kleen

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=20090817083544.GC15390@elte.hu \
    --to=mingo@elte.hu \
    --cc=ak@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rjw@sisk.pl \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    --cc=tglx@linutronix.de \
    --cc=ying.huang@intel.com \
    --cc=yinghai@kernel.org \
    /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