From: Robin Lee Powell <rlpowell@digitalkingdom.org>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Early boot hang on recent 2.6 kernels (> 2.6.3), on x86-64 with 16gb of RAM
Date: Mon, 18 Sep 2006 16:58:54 -0700 [thread overview]
Message-ID: <20060918235854.GL4610@chain.digitalkingdom.org> (raw)
In-Reply-To: <p73bqpd62b2.fsf@verdi.suse.de>
On Mon, Sep 18, 2006 at 09:50:41AM +0200, Andi Kleen wrote:
> Robin Lee Powell <rlpowell@digitalkingdom.org> writes:
> >
> > This version is rather different, as it ends in:
> >
> > HARDWARE ERROR
> > CPU 0: Machine Check Exception: 7 Bank 3: b40000000000083b
> > RIP 10:<ffffffff80446e3e> {pci_conf1_read+0xbe/0xf0}
> > TSC 2e7932dbf8 ADDR fdfc000cfc
> > This is not a software problem!
> > Run through mcelog --ascii to decode and contact your hardware vendor
> > Kernel panic - not syncing: Uncorrected machine check
>
> Decoded it gives
>
> ..
> bus error 'local node origin, request didn't time out
> data read mem transaction
> i/o access, level generic'
> ..
>
> It will probably boot with mce=off acpi=off pci=conf1
>
> You got some buggy device that causes a bus timeout when its config space
> is read. The old kernel most likely didn't touch it by luck.
>
> Please add the following patch and send the whole log.
> This will tell us which device has this problem.
Done; it's at
http://teddyb.org/~rlpowell/media/regular/lkml/hacked-boot.txt
Note that I had to us "mce=off acpi=off pci=conf1" to get any of
that hack's output to show up at all; I wasn't clear whether you
intended that or not.
-Robin
--
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/
Reason #237 To Learn Lojban: "Homonyms: Their Grate!"
Proud Supporter of the Singularity Institute - http://singinst.org/
next prev parent reply other threads:[~2006-09-18 23:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 22:32 Robin Lee Powell
2006-09-14 19:05 ` Same MCE on 4 working machines (was Re: Early boot hang on recent 2.6 kernels (> 2.6.3), on x86-64 with 16gb of RAM) Robin Lee Powell
2006-09-14 19:14 ` Lee Revell
2006-09-14 19:15 ` Robin Lee Powell
2006-09-15 5:42 ` Bharath Ramesh
2006-09-15 17:47 ` Robin Lee Powell
2006-09-15 18:07 ` Robin Lee Powell
2006-09-15 18:22 ` Alan Cox
2006-09-15 18:12 ` Robin Lee Powell
2006-09-18 7:52 ` Andi Kleen
2006-09-18 18:59 ` Robin Lee Powell
2006-09-15 11:45 ` Alan Cox
2006-09-15 18:29 ` Robin Lee Powell
2006-09-15 20:50 ` Alan Cox
2006-09-15 20:31 ` Robin Lee Powell
2006-09-15 23:18 ` Robin Lee Powell
2006-09-18 7:50 ` Early boot hang on recent 2.6 kernels (> 2.6.3), on x86-64 with 16gb of RAM Andi Kleen
2006-09-18 19:06 ` Robin Lee Powell
2006-09-18 23:58 ` Robin Lee Powell [this message]
2006-09-19 6:04 ` Andi Kleen
2006-09-19 6:28 ` Robin Lee Powell
2006-09-19 6:39 ` Andi Kleen
2006-09-19 17:46 ` Robin Lee Powell
2006-09-19 21:07 ` Robin Lee Powell
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=20060918235854.GL4610@chain.digitalkingdom.org \
--to=rlpowell@digitalkingdom.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®