From: Randy Dunlap <randy.dunlap@oracle.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Rusty Russell <rusty@rustcorp.com.au>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
andreas.herrmann3@amd.com
Subject: 2.6.29 boot hang
Date: Tue, 31 Mar 2009 13:45:35 -0700 [thread overview]
Message-ID: <49D280EF.1080507@oracle.com> (raw)
(If this is old news, would someone please tell me the status
of this problem? or if there is a known CPU issue, tell me.
Thanks.)
On a 4-proc x86_64 (HP BladeCenter, AMD CPUs) system, booting 2.6.29
(or earlier, back to 2.6.28-6921-g873392c) hangs during boot.
git bisect says:
873392ca514f87eae39f53b6944caf85b1a047cb is first bad commit
commit 873392ca514f87eae39f53b6944caf85b1a047cb
Author: Rusty Russell <rusty@rustcorp.com.au>
Date: Wed Dec 31 23:54:56 2008 +1030
PCI: work_on_cpu: use in drivers/pci/pci-driver.c
~~~~~~~~~~~~~~~~~~~~~
The last messages are usually like this:
Initializing CPU#1
Calibrating delay using timer specific routine.. 5224.09 BogoMIPS (lpj=10448183)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
CPU 1/0x2 -> Node 1
CPU: Physical Processor ID: 1
CPU: Processor Core ID: 0
CPU1: Dual-Core AMD Opteron(tm) Processor 8218 stepping 02
lockdep: fixing up alternatives.
Booting processor 2 APIC 0x1 ip 0x6000
Initializing CPU#2
Calibrating delay using timer specific routine.. 5224.12 BogoMIPS (lpj=10448242)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
CPU 2/0x1 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
CPU2: Dual-Core AMD Opteron(tm) Processor 8218 stepping 02
lockdep: fixing up alternatives.
Booting processor 3 APIC 0x3 ip 0x6000
Initializing CPU#3
Calibrating delay using timer specific routine.. 5224.11 BogoMIPS (lpj=10448230)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
If I change CONFIG_MICROCODE_AMD=y to CONFIG_MICROCODE_AMD=n & rebuild,
the kernel boots successfully.
There are never any kernel oops/panic/error messages. I suppose that the
CPU microcode update (if there actually is one) causes some kind of
problem that prevents messages.
Suggestions, fixes, etc.??
Thanks,
--
~Randy
next reply other threads:[~2009-03-31 20:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 20:45 Randy Dunlap [this message]
2009-03-31 21:01 ` 2.6.29 boot hang Morten P.D. Stevens
2009-03-31 21:54 ` Randy Dunlap
2009-03-31 23:42 ` Rusty Russell
2009-04-01 4:51 ` Randy Dunlap
2009-04-01 4:52 ` Randy Dunlap
2009-04-01 4:56 ` Randy Dunlap
2009-04-01 6:33 ` Rusty Russell
2009-04-01 17:30 ` Randy Dunlap
2009-04-02 0:42 ` Rusty Russell
2009-04-02 1:34 ` Randy Dunlap
2009-04-02 16:35 ` Randy Dunlap
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=49D280EF.1080507@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=andreas.herrmann3@amd.com \
--cc=bjorn.helgaas@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=rusty@rustcorp.com.au \
/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