From: Borislav Petkov <bp@alien8.de>
To: Rus <rus@sfinxsoft.com>
Cc: Andreas Herrmann <andreas.herrmann3@amd.com>,
linux-kernel@vger.kernel.org
Subject: Re: 3.[34].x Reproducable [Firmware bug] message upon warm boot only
Date: Thu, 7 Jun 2012 17:13:52 +0200 [thread overview]
Message-ID: <20120607151352.GA8261@x1.osrc.amd.com> (raw)
In-Reply-To: <CAKgfjTn3KXmDio0F0M3syeHnDc=ByKZu1ipe7S+75KRcCBy0QA@mail.gmail.com>
On Thu, Jun 07, 2012 at 05:51:51PM +0300, Rus wrote:
> .........
> processor : 0
> vendor_id : AuthenticAMD
> cpu family : 21
> model : 1
> model name : AMD FX(tm)-8150 Eight-Core Processor
> stepping : 2
Ok, family F15h, as expected.
> >> Is this message harmless or this is some problem with hardware/bios/Linux ?
> >
> > Mostly harmless, fix is already upstream: f227d306cf3 and also on its
> > way to stable. You can try 3.5-rc1 on the box (it should be pretty
> > stable on AMD) or wait for the stable backport.
>
> Ok, compiling ... will report soon. The reason I've asked - this
> particular brand new box is freezing once at a 2-3 days without any
> output - no oops, no sysrq, nothing. So I'm trying to investigate what
> is the problem. The previous kernels (3.3.x) have the serious problem
> with iommu - the onboard USB3.0 and Ethernet did not work at all on
> them. The 3.4.x is better, but seems like still freezing.
Hmm, that doesn't sound good. What exactly do you do when it freezes,
any repeatable usage patterns? Does the freeze happen if you disable
IOMMU in the BIOS?
Do you have serial console attached to it?
Do you have CONFIG_DETECT_HUNG_TASK enabled? Also CONFIG_PROVE_LOCKING,
CONFIG_KMEMCHECK, CONFIG_DEBUG_PREEMPT. These are just a couple of debug
options to enable right now which could tell us more.
Anything else that I'm forgetting?
Ah, and send me dmesg privately pls, from 3.4 and 3.5-rc1.
That's all I can think of right now.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-06-07 15:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKgfjTktMLc5bfqhCOKy0evssxggofNQqLT-gQqBkHcBvOgF0g@mail.gmail.com>
2012-06-07 13:40 ` 3.[34].x Reproducable [Firmware bug] message upon warm boot only Rus
2012-06-07 14:24 ` Borislav Petkov
2012-06-07 14:51 ` Rus
2012-06-07 15:13 ` Borislav Petkov [this message]
2012-06-07 19:02 ` Rus
2012-06-07 19:33 ` lockdep and kmemcheck Borislav Petkov
2012-06-07 19:45 ` Borislav Petkov
2012-06-08 6:10 ` Tejun Heo
2012-06-08 7:55 ` Peter Zijlstra
2012-06-08 8:02 ` Peter Zijlstra
2012-06-08 8:06 ` Borislav Petkov
2012-06-07 21:00 ` 3.[34].x Reproducable [Firmware bug] message upon warm boot only Rus
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=20120607151352.GA8261@x1.osrc.amd.com \
--to=bp@alien8.de \
--cc=andreas.herrmann3@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rus@sfinxsoft.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