After countless more crashes and trying to switch to the terminal right
before the crash I could note down the following info:
CPU 0: Machine Check Exception: 5 Bank 4: ba00000052000402
RIP !INEXACT! 10:<ffffffff813e87cc> {intel_udke+0xcc/0x100}
TSC 1fdbb9031f
PROCESSOR 0:303c3 TIME 1390237456 SOCKET 0 APIC 0 microcode 17
mcelog gave me with mcelog --ascii < filename :
CPU 0: Machine Check Exception: 5 Bank 4: ba00000052000402
TSC 1fdbb9031f
Hardware event. This is not a software error.
CPU 0 BANK 4 TSC 1fdbb9031f
RIP !INEXACT! 10:ffffffff813e87cc
MISC 0
TIME 1390237456 Mon Jan 20 18:04:16 2014
STATUS ba00000052000402 MCGSTATUS 5
CPUID Vendor Intel Family 3 Model 12
RIP: intel_udke+0xcc/0x100}
PROCESSOR 0:303c3 TIME 1390237456 SOCKET 0 APIC 0 microcode 17
I checked all my RAM - no errors. The CPU is brandnew, very unlikely
that it has errors. And it works flawlessly as long as I'm not trying to
access h264 - this gets even more weird...
** Summary changed:
- System freeze while decoding H264 files
+ System freeze (kernel panic) while decoding H264 files
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270655
Title:
System freeze (kernel panic) while decoding H264 files
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/x264/+bug/1270655/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
