From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 10 11:06:47 2014 Return-Path: Delivered-To: freebsd-hardware@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6B219EF for ; Mon, 10 Feb 2014 11:06:47 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3DFD11FD4 for ; Mon, 10 Feb 2014 11:06:47 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1AB6l3I080045 for ; Mon, 10 Feb 2014 11:06:47 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1AB6khq080043 for freebsd-hardware@FreeBSD.org; Mon, 10 Feb 2014 11:06:46 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 10 Feb 2014 11:06:46 GMT Message-Id: <201402101106.s1AB6khq080043@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-hardware@FreeBSD.org Subject: Current problem reports assigned to freebsd-hardware@FreeBSD.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2014 11:06:47 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- f kern/156241 hardware [mfi] 'zfs send' does not prevents disks to suspend if 1 problem total. From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 10 22:08:45 2014 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 78FE0F82; Mon, 10 Feb 2014 22:08:45 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 44F3F1DF0; Mon, 10 Feb 2014 22:08:45 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 1A685B95D; Mon, 10 Feb 2014 17:08:44 -0500 (EST) From: John Baldwin To: freebsd-hardware@freebsd.org Subject: Re: Followup On Recent MCA Madness. WAS: Need Help With MCA Code Date: Mon, 10 Feb 2014 16:18:43 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <52E73717.3000503@tundraware.com> <52EBE1FA.2040603@tundraware.com> <52ED5C97.8030503@tundraware.com> In-Reply-To: <52ED5C97.8030503@tundraware.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201402101618.43685.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 10 Feb 2014 17:08:44 -0500 (EST) Cc: Tim Daneliuk , freebsd-stable@freebsd.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2014 22:08:45 -0000 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 From owner-freebsd-hardware@FreeBSD.ORG Mon Feb 10 23:53:48 2014 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2222AD5; Mon, 10 Feb 2014 23:53:48 +0000 (UTC) Received: from ozzie.tundraware.com (ozzie.tundraware.com [75.145.138.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D0C2E1821; Mon, 10 Feb 2014 23:53:47 +0000 (UTC) Received: from [192.168.0.2] (viper.tundraware.com [192.168.0.2]) (authenticated bits=0) by ozzie.tundraware.com (8.14.8/8.14.8) with ESMTP id s1ANrbcI010637 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 10 Feb 2014 17:53:37 -0600 (CST) (envelope-from tundra@tundraware.com) Message-ID: <52F96681.3080604@tundraware.com> Date: Mon, 10 Feb 2014 17:53:37 -0600 From: Tim Daneliuk User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: Re: Followup On Recent MCA Madness. WAS: Need Help With MCA Code References: <52E73717.3000503@tundraware.com> <52EBE1FA.2040603@tundraware.com> <52ED5C97.8030503@tundraware.com> <201402101618.43685.jhb@freebsd.org> In-Reply-To: <201402101618.43685.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (ozzie.tundraware.com [75.145.138.73]); Mon, 10 Feb 2014 17:53:37 -0600 (CST) X-TundraWare-MailScanner-Information: Please contact the ISP for more information X-TundraWare-MailScanner-ID: s1ANrbcI010637 X-TundraWare-MailScanner: Found to be clean X-TundraWare-MailScanner-From: tundra@tundraware.com X-Spam-Status: No Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2014 23:53:48 -0000 On 02/10/2014 03:18 PM, John Baldwin wrote: >> On Saturday, February 01, 2014 3:44:07 pm Tim Daneliuk wrote: >> 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 I've been considering this, but I have a few more questions, if I may: - There was a time when the new Xorg stuff did not play well with VTYs. Is this still the case or has it been resolved? - If I were to set this option in make.conf, is it sufficient to simply force a recompilation of every port on the machine via portupgrade, or is there a better way? TIA, -- ---------------------------------------------------------------------------- Tim Daneliuk tundra@tundraware.com PGP Key: http://www.tundraware.com/PGP/ From owner-freebsd-hardware@FreeBSD.ORG Tue Feb 11 02:32:18 2014 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5D3E7F82; Tue, 11 Feb 2014 02:32:18 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E9FC315E1; Tue, 11 Feb 2014 02:32:17 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.8/8.14.8) with ESMTP id s1B2WAcT023863 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 10 Feb 2014 19:32:10 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.8/8.14.8/Submit) with ESMTP id s1B2W98U023860; Mon, 10 Feb 2014 19:32:10 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Mon, 10 Feb 2014 19:32:09 -0700 (MST) From: Warren Block To: Tim Daneliuk Subject: Re: Followup On Recent MCA Madness. WAS: Need Help With MCA Code In-Reply-To: <52F96681.3080604@tundraware.com> Message-ID: References: <52E73717.3000503@tundraware.com> <52EBE1FA.2040603@tundraware.com> <52ED5C97.8030503@tundraware.com> <201402101618.43685.jhb@freebsd.org> <52F96681.3080604@tundraware.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Mon, 10 Feb 2014 19:32:10 -0700 (MST) Cc: freebsd-stable@freebsd.org, freebsd-hardware@freebsd.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2014 02:32:18 -0000 On Mon, 10 Feb 2014, Tim Daneliuk wrote: > On 02/10/2014 03:18 PM, John Baldwin wrote: >>> On Saturday, February 01, 2014 3:44:07 pm Tim Daneliuk wrote: > > >>> 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 Important note: fourth-generation (Haswell) Intel CPU graphics are not supported yet. No idea on a time frame for that. > I've been considering this, but I have a few more questions, if I may: > > - There was a time when the new Xorg stuff did not play well with VTYs. > Is this still the case or has it been resolved? See https://wiki.freebsd.org/Newcons This has not yet been MFCed to 10-stable, so at present consoles are not visible after X has been started. Commands can still be typed, though. > - If I were to set this option in make.conf, is it sufficient to simply > force a recompilation of every port on the machine via portupgrade, > or is there a better way? The better way is shown on the KMS page, a bit farther down: https://wiki.freebsd.org/Graphics#Installing_KMS_Ports