lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 21 Mar 2014 18:27:42 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Matthias Graf <matthias.graf@...ovgu.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: PROBLEM: Fatal Machine Check >= 3.13.5-101.fc19.x86_64

On Fri, Mar 21, 2014 at 06:10:23PM +0100, Matthias Graf wrote:
> Please CC me on replies.
> 
> [1.] Kernel panic: Fatal Machine Check after booting >=
> 3.13.5-101.fc19.x86_64; 3.12.11-201.fc19.x86_64 works fine!
> [2.] Screen freezes a few seconds after Gnome appears. The error message
> (see attachement) is seldom still printed to the screen. Booting
> 3.12.11-201 with otherwise the same setup, I do not see the panic.
> Booting on different hardware (my laptop) does not produce the panic. I
> also notice low frames per seconds after gnome started up, right before
> the panic occures. I therefore suppose this is graphics hardware related.
> [3.] Fatal Machine Check Exception, RIP Inexact, apic_timer_interrupt,
> Kernel panic
> [4.] 3.13.6-100.fc19.x86_64 && 3.13.5-103.fc19.x86 && 3.13.5-101.fc19.x86_64
> [5.] OCRed: (see Attachement for photo)
> 
> Started Accounts Service.
> [ 34.348483] mce: [Hardware Error]: CPU 3: Machine Check Exception: 5 Bank 8: bZ88884888888888
> [ 44.468168] mce: [Hardware Error]: HIP ?IHEXfiCT? 18:<ffffffff816881f8> {apicgtimer_interrupt+8x8/8x88}
> I 44.468168] mce: [Hardware Error]: TSC 36S??8ad8c
> f 44.468168] mce: [Hardware Error]: PROCESSOR 8:6fb TIM 138471666? SOCKET 8 HPIC 2 microcode ba
> I 44.468168] mce: [Hardware Error]: Run the above through 'mcelog ~~ascii’

This looks like you had some text recognition done on the jpeg. :-)

Please correct the error message to be exactly as in the jpeg and run it
through mcelog --ascii to see what that bank 8 is trying to tell us.

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists