Date: Sun, 1 May 2016 08:35:10 -0400 From: Shawn Webb <shawn.webb@hardenedbsd.org> To: freebsd-current@freebsd.org Subject: MCA unrecoverable machine check exception on APU2 Message-ID: <20160501123510.GC90606@mutt-hardenedbsd>
next in thread | raw e-mail | index | archive | help
--3siQDZowHQqNOShm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hey All, I'm getting this panic. I'm not sure if it's a problem with the OS or the hardware as this is a bit too low-level for me. Here's the dmesg output along with the stack trace: MCA: Bank 0, Status 0xb400000000000135 MCA: Global Cap 0x0000000000000106, Status 0x0000000000000004 MCA: Vendor "AuthenticAMD", ID 0x730f01, APIC ID 3 MCA: CPU 3 UNCOR DCACHE L1 DRD error MCA: Address 0x44e9830 panic: Unrecoverable machine check exception cpuid =3D 3 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00f53cb= 390 vpanic() at vpanic+0x182/frame 0xfffffe00f53cb410 panic() at panic+0x43/frame 0xfffffe00f53cb470 mca_intr() at mca_intr+0x6b/frame 0xfffffe00f53cb490 trap() at trap+0xa8/frame 0xfffffe00f53cb6a0 calltrap() at calltrap+0x8/frame 0xfffffe00f53cb6a0 --- trap 0x1c, rip =3D 0xffffffff80b6ffe1, rsp =3D 0xfffffe00f53cb770, rbp = =3D 0xfffffe00f53cb7f0 --- callout_process() at callout_process+0x131/frame 0xfffffe00f53cb7f0 handleevents() at handleevents+0x16d/frame 0xfffffe00f53cb830 timercb() at timercb+0x227/frame 0xfffffe00f53cb880 lapic_handle_timer() at lapic_handle_timer+0x9f/frame 0xfffffe00f53cb8c0 Xtimerint() at Xtimerint+0x8c/frame 0xfffffe00f53cb8c0 --- interrupt, rip =3D 0xffffffff80b85a39, rsp =3D 0xfffffe00f53cb990, rbp = =3D 0xfffffe00f53cba70 --- sched_idletd() at sched_idletd+0x439/frame 0xfffffe00f53cba70 fork_exit() at fork_exit+0x84/frame 0xfffffe00f53cbab0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00f53cbab0 --- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 --- KDB: enter: panic [ thread pid 11 tid 100006 ] Stopped at kdb_enter+0x3b: movq $0,kdb_why db> This is running HardenedBSD 11-CURRENT/amd64 on the PC-Engines APU2. Is this worth filing a bug report upstream with FreeBSD or is this a hardware bug? Thanks, --=20 Shawn Webb HardenedBSD GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --3siQDZowHQqNOShm Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXJff8AAoJEGqEZY9SRW7uGw8QAI9G67DjTb27YM7kQSUd/T3K k7dGZjl+0loZ0LnTcSwsqv66Aybz0UNaiCU7M97CFsqOfO13BPWeWeq5TmbCaM9a lj+nyPxrjAdbNOrGZyAydHwJfiesUOvWZ18aeSVk9o+1GPDZV2CWDRLcXtm4to1O t0nkgl3x5+WOm3oaLPmuxZXmGG6dFRaaf5ogDHZU1gGW4sZdc/1d59E4haTJ+P4y Bxoduq/KkOlvmcmHI4EM4lntBQc/wO8ZGg0gtuomt59wLnYyMwRts2NsLkEZeRqo qkarwPXzBx9rAG+1DZtGTfvJs+uu6p6GL8AxG0UGYFN+HhSUA1w/oloLFK9hjHGo Kkl9+aFT2nnxc76B4lYGjSWzyFZtdIihZkck+1XgibcCfdgeRnQl2DTjULQqcDtJ NzbSLiv3Jp6RAyG0t8mZSJL1iyl8+XB8uy/vJDuGA+fEhF/GcW1ww2XiaWWRjcch FNF7oDbxRp7oLBe4yOWhdNV8ilqdAlzd6LBSMqPeTHvhLJ7vDYeA/eRZbnGR+kEV VTm1bhIwDOtt58RrtCRHdZSvMYCYFCBx8JEEXwJb5GFuggcjirTsXKYQHThJACNQ +EIEyZ6ddYL5jz/qkHWJt/YxYHUWatLRhLNKhWGANwiD6rGBS9IRP3Ufy9l1uwGW 1fQgXGOtxc2boTLWP00U =Pdsi -----END PGP SIGNATURE----- --3siQDZowHQqNOShm--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160501123510.GC90606>