public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Fritz <chf.fritz@googlemail.com>
To: Daniel J Blueman <daniel@quora.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: lockup when C1E and high-resolution timers enabled
Date: Sun, 14 Jun 2015 06:39:56 +0200	[thread overview]
Message-ID: <1434256796.1699.5.camel@googlemail.com> (raw)
In-Reply-To: <CAMVG2sun44_6QqNPBCUj7gdQGZyy9R_mULqkF-=Uv_wuUHV9oQ@mail.gmail.com>

On Sun, 2015-06-14 at 11:13 +0800, Daniel J Blueman wrote:
> On Sunday, June 14, 2015 at 4:00:06 AM UTC+8, Christoph Fritz wrote:
> > Hi,
> >
> >  on following computer configuration, I do get hard lockup under heavy
> > IO-Load (using rsync):
> >
> >  - CONFIG_HIGH_RES_TIMERS=y
> >  - CPU: AMD FX(tm)-8350 Eight-Core Processor (family 0x15 model 0x2)
> >  - Motherboard: 'GA-970A-UD3P (rev. 1.0)' AMD 970/SB950
> >  - BIOS: C1E enabled (on 'GA-970A-UD3P' there is no disable option)
> >  - Kernels: 4.1.0-rc6, 4.0.x, 3.16.x
> >
> > Tests:
> >  - add kernel parameter "idle=halt" -> system runs fine
> >  - disable CONFIG_HIGH_RES_TIMERS -> system runs fine
> >  - change motherboard and disable C1E -> system runs fine
> >  - change CPU to AMD Phenom II X6 Processor -> system runs fine
> [..]
> 
> C1E disconnects HyperTransport links when all cores enter C1 (halt)
> for a period of time; this is all at the platform level, so isn't due
> to the kernel. The AMD AGESA code which controls the setup of this
> mechanism is updated in the F2g BIOS:
> http://www.gigabyte.com/products/product-page.aspx?pid=4717#bios
> 
> Did you try both BIOS releases with defaults?

Yes, rechecked both versions: Same bad behaviour.

> If still issues, also try with the current family 10h microcode from
> http://www.amd64.org/microcode/amd-ucode-latest.tar.bz2

Don't you mean family 15h for 'AMD FX(tm)-8350' ?

already using latest microcode:

[    0.514490] microcode: CPU0: patch_level=0x06000822
[    0.514497] microcode: CPU1: patch_level=0x06000822
[    0.514508] microcode: CPU2: patch_level=0x06000822
[    0.514519] microcode: CPU3: patch_level=0x06000822
[    0.514529] microcode: CPU4: patch_level=0x06000822
[    0.514540] microcode: CPU5: patch_level=0x06000822
[    0.514550] microcode: CPU6: patch_level=0x06000822
[    0.514561] microcode: CPU7: patch_level=0x06000822



  reply	other threads:[~2015-06-14  4:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14  3:13 lockup when C1E and high-resolution timers enabled Daniel J Blueman
2015-06-14  4:39 ` Christoph Fritz [this message]
2015-06-14  7:54   ` Daniel J Blueman
2015-06-14 14:49     ` Christoph Fritz
2015-06-14 15:24       ` Daniel J Blueman
2015-06-14 23:38         ` Christoph Fritz
2015-06-14 16:47   ` Borislav Petkov
2015-06-14 23:05     ` Christoph Fritz
2015-06-15  7:54       ` Borislav Petkov
2015-06-15  8:01         ` Christoph Fritz
2015-06-15  8:10           ` Borislav Petkov
2015-07-13  7:32             ` Christoph Fritz
  -- strict thread matches above, loose matches on Subject: below --
2015-06-13 19:53 Christoph Fritz
2015-06-13 20:19 ` Heinz Diehl
2015-06-13 20:58   ` Christoph Fritz

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=1434256796.1699.5.camel@googlemail.com \
    --to=chf.fritz@googlemail.com \
    --cc=daniel@quora.org \
    --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