Date: Mon, 10 Feb 2014 16:18:43 -0500 From: John Baldwin <jhb@freebsd.org> To: freebsd-hardware@freebsd.org Cc: Tim Daneliuk <tundra@tundraware.com>, freebsd-stable@freebsd.org Subject: Re: Followup On Recent MCA Madness. WAS: Need Help With MCA Code Message-ID: <201402101618.43685.jhb@freebsd.org> In-Reply-To: <52ED5C97.8030503@tundraware.com> References: <52E73717.3000503@tundraware.com> <52EBE1FA.2040603@tundraware.com> <52ED5C97.8030503@tundraware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday, February 01, 2014 3:44:07 pm Tim Daneliuk wrote: > On 01/31/2014 11:48 AM, Tim Daneliuk wrote: > > On 01/31/2014 11:22 AM, John Baldwin wrote: > >> On Wednesday, January 29, 2014 6:49:21 pm Tim Daneliuk wrote: > >>> Resending in hopes that people on one of the other lists will have some insight here: > >>> > >>> On 01/27/2014 10:50 PM, Tim Daneliuk wrote: > >>>> I am running 9.2 stable i386 r261207. As noted earlier: > >>>> > >>>>> I just replaced mobo/CPU on FBSD server (Gigabyte Z-87-D3HP with > >>>>> an Intel i3-4130). I am not overclocking ... but I continue to see this sort of thing: > >>>> > >>>>> MCA: CPU 0 COR (1) internal parity error > >>>> > >>>> Dmesg shows: > >>>> > >>>>> MCA: Vendor "GenuineIntel", ID 0x306c3, APIC ID 0 > >>>>> MCA: CPU 0 COR (1) internal parity error > >>>>> MCA: Bank 0, Status 0x90000040000f0005 > >>>>> MCA: Global Cap 0x0000000000000c07, Status 0x0000000000000000_ > >>>> > >>>> I've swapped CPUs (i5). I've fiddled with an endless supply of > >>>> mobo settings. I've switched power supplies. I've moved mem > >>>> sticks around .... No joy. > >>>> > > This got resolved when I did a completely fresh install of FBSD 10 > on the server. This made the MCAs go away. I therefore conclude > that there were one of several possible root causes: > > - FreeBSD i386 doesn't play nice with Haswell parts > - FreeBSD 9.2-STABLE i386 doesn't place nice with Haswell parts > - My FreeBSD 9.2-STABLE i386 instance was corrupted somehow > > My belief is that it is mostly likely the last culprit, absent > someone confirming that the first two are possibilities. > > The good thing that came out of this is that I finally > upgraded this server in some important ways: > > - 64 bit > - FreeBSD 10 > - Latest bind 9 > > Now, if I could just figure out how to get stock X to > run at 1920x1080 on HD4600 graphics. Apparently neither the > intel of vesa drivers know how to do this, or at least I've > had no luck with it. The intel driver doesn't even recognize > the hardware as something it supports. > > "X on a server?" you say? Yes, for intermittent use of fluxbox > to run a bunch of xterms. For the Intel graphics you want to use i915kms. However, you need to build your ports with 'WITH_NEW_XORG=yes' set in /etc/make.conf. There are more details about this on the wiki. https://wiki.freebsd.org/Graphics -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201402101618.43685.jhb>