Re: lockup when C1E and high-resolution timers enabled

2015-07-13 Thread Christoph Fritz
Hi, the whole error (freeze under heavy IO when C1E enabled) here is referable to motherboard 'GA-970A-UD3P (rev. 1.0)', changing it to a 'Asus M5A97 PLUS' fixes my problems here. I'm not sure if this GA-970A board is just broken or has some general problems. Thanks -- chf -- To unsubscribe

Re: lockup when C1E and high-resolution timers enabled

2015-06-15 Thread Borislav Petkov
On Mon, Jun 15, 2015 at 10:01:41AM +0200, Christoph Fritz wrote: > I should have mentioned that, I already tested that, it doesn't fix > the described lockup :-( Hmm, can you boot with "log_buf_len=16M ignore_loglevel debug initcall_debug apic=debug" and send me full dmesg from that box? Priva

Re: lockup when C1E and high-resolution timers enabled

2015-06-15 Thread Christoph Fritz
On Mon, 2015-06-15 at 09:54 +0200, Borislav Petkov wrote: > Just to rule out the aspect that your issue might be fixed by microcode > but that microcode needs to be loaded early, can you enable the early > microcode loader, put the microcode in initrd as described here: > > Documentation/x86/early

Re: lockup when C1E and high-resolution timers enabled

2015-06-15 Thread Borislav Petkov
On Mon, Jun 15, 2015 at 01:05:07AM +0200, Christoph Fritz wrote: > > > 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 > > >

Re: lockup when C1E and high-resolution timers enabled

2015-06-14 Thread Christoph Fritz
On Sun, 2015-06-14 at 23:24 +0800, Daniel J Blueman wrote: > val=0x$(setpci -s 00:18.3 0xd4.l) # read D18F3xD4 > val=$((val &~(1 << 13))) # clear bit13 (MTC1eEn) > setpci -d 1022:1603 0xd4.l=$(printf %x $val) # write back This slows down the whole system dramatically: - before: MTC1eEn set: Boot

Re: lockup when C1E and high-resolution timers enabled

2015-06-14 Thread Christoph Fritz
> > 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] mic

Re: lockup when C1E and high-resolution timers enabled

2015-06-14 Thread Borislav Petkov
On Sun, Jun 14, 2015 at 06:39:56AM +0200, Christoph Fritz wrote: > 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:

Re: lockup when C1E and high-resolution timers enabled

2015-06-14 Thread Daniel J Blueman
On 14 June 2015 at 22:49, Christoph Fritz wrote: > On Sun, 2015-06-14 at 15:54 +0800, Daniel J Blueman wrote: >> As a workaround, you can probably just disable message triggered C1E >> (see the BKDG p399 [1]): >> >> val=0x$(setpci -s 00:18.4 0xd4.l) # read D18F3xD4 > > mhm... $(setpci -s 00:18.4 0

Re: lockup when C1E and high-resolution timers enabled

2015-06-14 Thread Christoph Fritz
On Sun, 2015-06-14 at 15:54 +0800, Daniel J Blueman wrote: > As a workaround, you can probably just disable message triggered C1E > (see the BKDG p399 [1]): > > val=0x$(setpci -s 00:18.4 0xd4.l) # read D18F3xD4 mhm... $(setpci -s 00:18.4 0xd4.l) returns zero, this can't be right. -- To unsubscr

Re: lockup when C1E and high-resolution timers enabled

2015-06-14 Thread Daniel J Blueman
On 14 June 2015 at 12:39, Christoph Fritz wrote: > 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)

Re: lockup when C1E and high-resolution timers enabled

2015-06-13 Thread Christoph Fritz
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(

Re: lockup when C1E and high-resolution timers enabled

2015-06-13 Thread Daniel J Blueman
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

Re: lockup when C1E and high-resolution timers enabled

2015-06-13 Thread Christoph Fritz
On Sat, 2015-06-13 at 22:19 +0200, Heinz Diehl wrote: > On 13.06.2015, Christoph Fritz wrote: > > > - 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

Re: lockup when C1E and high-resolution timers enabled

2015-06-13 Thread Heinz Diehl
On 13.06.2015, Christoph Fritz wrote: > - 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 I encountered quit

lockup when C1E and high-resolution timers enabled

2015-06-13 Thread Christoph Fritz
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