From: Andi Kleen <ak@suse.de>
To: Akinobu Mita <mita@miraclelinux.com>
Cc: ak@suse.de, linux-kernel@vger.kernel.org, mark.langsdorf@amd.com
Subject: Re: x86-64 Uncorrected machine check panic on boot
Date: Thu, 21 Apr 2005 13:56:08 +0200 [thread overview]
Message-ID: <20050421115608.GU7715@wotan.suse.de> (raw)
In-Reply-To: <200504192212.44742.mita@miraclelinux.com>
On Tue, Apr 19, 2005 at 10:12:43PM +0900, Akinobu Mita wrote:
> Hello,
>
> I got the following Machine Check Exception on 4-way Opteron Server.
> I've tried 2.6.11.7 and 2.6.12-rc2.
> The kernel parameter "nomce" could help to boot it up.
Sounds like a bogus BIOS. It should disable these machine checks
for timeout on pci config access imho.
What 4way board did you use? Can you check if there is a BIOS
update?
-Andi
>
> I wrote this panic messages by hand.
> This panic seems to happen around "arch/x86_64/pci/../../i386/pci/direct.c:28"
>
> ==========================================================
> Calling initcall 0xffffffff........: netlink_proto_init...
> NET: Registered protocol family 16
>
> Calling initcall 0xffffffff........: pcibus_class_init...
> Calling initcall 0xffffffff........: pci_driver_init
> Calling initcall 0xffffffff........: tty_class_init
> Calling initcall 0xffffffff........: mtrr_if_init
> Calling initcall 0xffffffff........: pci_direct_init
>
> CPU3: Machine Check Exception: 7 Bank 3: b40000000000083b
> RIP 10: <ffffffff802cfefe> {pci_conf1_read+0xce/0x110}
> TSC 85ece4f ADDR fdfc000cfe
>
> kernel panic - not syncing: Uncorrected machine check
> ==========================================================
>
>
> $ addr2line -e vmlinux ffffffff802cfee0
> arch/x86_64/pci/../../i386/pci/direct.c:28
>
> $ addr2line -e vmlinux ffffffff802cfee2
> include/asm/io.h:81
>
> $ addr2line -e vmlinux ffffffff802cfefe
> include/asm/io.h:84
>
>
prev parent reply other threads:[~2005-04-21 11:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 13:12 Akinobu Mita
2005-04-21 11:56 ` Andi Kleen [this message]
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=20050421115608.GU7715@wotan.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.com \
--cc=mita@miraclelinux.com \
/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
all inboxes | Powered by JetHome®