Date: Sat, 04 Mar 2017 22:34:39 -0800 From: "Chris H" <bsd-lists@bsdforge.com> To: freebsd-current@freebsd.org, Alastair Hogge <agh@fastmail.fm> Subject: Re: kernel trap 12 with interrupts disabled Message-ID: <7c300bdfa4f923ec5406e257dbb17ad1@ultimatedns.net> In-Reply-To: <3109513.uzeZf1mvEc@madcat.anarchadelic.> References: <959436378530ea6a182825fb1328bcb6@ultimatedns.net> <3244339.Sh8jFgR0Eq@madcat.anarchadelic.> <2e2714cc5f991d19c70ccff599aa3fe6@ultimatedns.net>, <3109513.uzeZf1mvEc@madcat.anarchadelic.>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 05 Mar 2017 14:26:31 +0800 Alastair Hogge <agh@fastmail.fm> wrote > On Sat, 4 Mar 2017 10:08:45 PM Chris H wrote: > > Thanks for the reply. > > I rebooted to kernel.old, so I could get the exact > > src revision I built this on. It's r314640 > > > > Any news as to whether it's safe to update src, and > > build a usable kernel? > > I am not able to boot a kernel > r314627. I currently have a r314627 kernel > running with a r314687 world. Looking at the output in my trap; I got the impression that the commit: r314636, might be to blame -- MCA: add AMD Error Thresholding support Currently the feature is implemented only for a subset of errors reported via Bank 4. The subset includes only DRAM-related errors. The new code builds upon and reuses the Intel CMC (Correctable MCE Counters) support code. However, the AMD feature is quite different and, unfortunately, much less regular. Just a guess, tho. I'm thinking to back that commit out, and giving world/kernel another shot. --Chris > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7c300bdfa4f923ec5406e257dbb17ad1>