From owner-freebsd-hardware@FreeBSD.ORG Mon Jun 4 08:47:27 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB0A91065670; Mon, 4 Jun 2012 08:47:27 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id B077C8FC12; Mon, 4 Jun 2012 08:47:27 +0000 (UTC) Received: by dadv36 with SMTP id v36so5805035dad.13 for ; Mon, 04 Jun 2012 01:47:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=DfhkOteJ/XJCSvBIOA4uskugb9gwM3+yXrPgn7rqEaU=; b=a7mLIjPKhE3aZQkz2Pv1ozJu2J61qw3k091n4WCC1P21fwGCV9GYoNPkuOGrf2EzQv y/q+6+e2SO87Ewbjzs9hsEViy3IBsLdQvlv0F0B9232MU9OX/s0XR3PsOvsLzO13n3kS o1QMobvLZCtHRbsL/PEOUh5W10e/qWD4TN/sm4Y3mCHj2m+l5zd8mMbiKyw5ovuv1uM9 b77IzIZPA+lFQJGc9Oo61XvQKXmMHtBdWBqZACdXGjEoAIT1at9Dw0SNXElWayv3k3M7 E2RLRXRlXD7zPlW21HPITtiN+dArwJoTMdEVpBy1GdAwsnu703BVdtjvTypN/JzfANfj VDlQ== Received: by 10.68.217.40 with SMTP id ov8mr10514036pbc.131.1338799647360; Mon, 04 Jun 2012 01:47:27 -0700 (PDT) Received: from pyunyh@gmail.com ([114.111.62.249]) by mx.google.com with ESMTPS id of1sm12601171pbb.15.2012.06.04.01.47.23 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 04 Jun 2012 01:47:25 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Mon, 04 Jun 2012 17:47:20 -0700 From: YongHyeon PYUN Date: Mon, 4 Jun 2012 17:47:20 -0700 To: Mike Tancsa Message-ID: <20120605004720.GB4010@michelle.cdnetworks.com> References: <4FC03C83.4030109@sentex.net> <20120601200942.GD10661@michelle.cdnetworks.com> <4FC8A903.6060203@sentex.net> <201206011030.52753.jhb@freebsd.org> <4FCA223F.5080009@sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4FCA223F.5080009@sentex.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-hardware@freebsd.org Subject: Re: pcie realtek issue (re driver) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 08:47:28 -0000 On Sat, Jun 02, 2012 at 10:25:03AM -0400, Mike Tancsa wrote: > On 6/1/2012 10:30 AM, John Baldwin wrote: > > > > BTW, it would be interesting to see what the AER errors are. Can you apply > > www.freebsd.org/~jhb/patches/pciconf_e.patch to pciconf and paste the output > > of 'pciconf -lcbe' for re0? > > > > Hi, > Using the pciconf from HEAD, > > re0@pci0:4:0:0: class=0x020000 card=0x816810ec chip=0x816810ec rev=0x03 > hdr=0x00 > vendor = 'Realtek Semiconductor Co., Ltd.' > device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller' > class = network > subclass = ethernet > bar [10] = type I/O Port, range 32, base 0, size 256, disabled > bar [18] = type Memory, range 64, base 0xfe200000, size 4096, disabled > bar [20] = type Prefetchable Memory, range 64, base 0xf0000000, > size 16384, disabled > cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 > cap ff[50] = unknown > PCI errors = Master Data Parity Error > Sent Target-Abort > Received Target-Abort > Received Master-Abort > Signalled System Error > Detected Parity Error > Hmm, Target abort/parity error looks serious to me. Could you remove re(4) driver in kernel and perform cold boot and check the AER errors again? (I assume your controller is not a stand-alone PCIe controller so I excluded resitting the controller). > > ---Mike From owner-freebsd-hardware@FreeBSD.ORG Mon Jun 4 11:07:39 2012 Return-Path: Delivered-To: freebsd-hardware@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4BA38106564A for ; Mon, 4 Jun 2012 11:07:39 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1BE848FC0A for ; Mon, 4 Jun 2012 11:07:39 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q54B7cVu017436 for ; Mon, 4 Jun 2012 11:07:38 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q54B7csu017434 for freebsd-hardware@FreeBSD.org; Mon, 4 Jun 2012 11:07:38 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 4 Jun 2012 11:07:38 GMT Message-Id: <201206041107.q54B7csu017434@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 Cc: Subject: Current problem reports assigned to freebsd-hardware@FreeBSD.org X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2012 11:07:39 -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 -------------------------------------------------------------------------------- o kern/156241 hardware [mfi] 'zfs send' does not prevents disks to suspend if 1 problem total. From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 6 18:02:51 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB7331065679 for ; Wed, 6 Jun 2012 18:02:51 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1-6.sentex.ca [IPv6:2607:f3e0:0:1::12]) by mx1.freebsd.org (Postfix) with ESMTP id 7D28B8FC16 for ; Wed, 6 Jun 2012 18:02:51 +0000 (UTC) Received: from [192.168.43.26] (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.5/8.14.4) with ESMTP id q56I2oc4034632; Wed, 6 Jun 2012 14:02:50 -0400 (EDT) (envelope-from mike@sentex.net) Message-ID: <4FCF9B42.4090100@sentex.net> Date: Wed, 06 Jun 2012 14:02:42 -0400 From: Mike Tancsa Organization: Sentex Communications User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: pyunyh@gmail.com References: <4FC03C83.4030109@sentex.net> <20120601200942.GD10661@michelle.cdnetworks.com> <4FC8A903.6060203@sentex.net> <201206011030.52753.jhb@freebsd.org> <4FCA223F.5080009@sentex.net> <20120605004720.GB4010@michelle.cdnetworks.com> In-Reply-To: <20120605004720.GB4010@michelle.cdnetworks.com> X-Enigmail-Version: 1.4.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org Subject: Re: pcie realtek issue (re driver) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2012 18:02:51 -0000 On 6/4/2012 8:47 PM, YongHyeon PYUN wrote: > Hmm, Target abort/parity error looks serious to me. Could you > remove re(4) driver in kernel and perform cold boot and check the > AER errors again? > (I assume your controller is not a stand-alone PCIe controller so > I excluded resitting the controller). Hi, This is a stand alone card actually. Here it is after a power cycle. Perhaps just a bad card ? none2@pci0:4:0:0: class=0x020000 card=0xffffffff chip=0x816810ec rev=0x03 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller' class = network subclass = ethernet bar [10] = type I/O Port, range 32, base 0, size 256, disabled bar [18] = type Memory, range 64, base 0, size 4096, disabled bar [20] = type Prefetchable Memory, range 64, base 0, size 16384, disabled cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 cap 05[50] = MSI supports 1 message, 64 bit cap 10[70] = PCI-Express 2 endpoint IRQ 2 max data 128(128) link x1(x1) cap 11[ac] = MSI-X supports 4 messages in maps 0x20 and 0x2c PCI errors = Master Data Parity Error Sent Target-Abort Received Target-Abort Received Master-Abort Signalled System Error Detected Parity Error -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/ From owner-freebsd-hardware@FreeBSD.ORG Thu Jun 7 05:45:50 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 10D3F106564A for ; Thu, 7 Jun 2012 05:45:50 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id BB9D88FC08 for ; Thu, 7 Jun 2012 05:45:49 +0000 (UTC) Received: by dadv36 with SMTP id v36so373458dad.13 for ; Wed, 06 Jun 2012 22:45:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=uVw7DO3Nm+P+WoguGoJ2MhRFvyY+Kxpc0UC8ogIO56E=; b=CQJT6gfLGQPVN5DlGxKv4WRzaXoDwfeTIRksYQif1nz6JfnDrfJ4Ii5tV4XM5TnDo7 5S55tl8y/lQ7PtJuoiUqwybG/VZ1biKx4KL7pq1/bB4WlRqc2+rbNtko8zutC+nObMgz FdACnibqfPvaufMpI0t3fQBIm/sZu/uPL65wzH4hkTFBK5dsBC6bAafL5ZvLsD7kkCmU wHK3KFJWfQsfMlKhfNCyBd+pHqEjK42J3zn+5dVGo65i+r1WjtNEBlYcaiV2NElWLI5N uYr7cUh26lHQEgsdBVqVR3o/ZISawEGcXMUh/eekheqGgRFtOfPjpNU8BZM5gKxBvLnb u8HA== Received: by 10.68.204.227 with SMTP id lb3mr4852847pbc.92.1339047949246; Wed, 06 Jun 2012 22:45:49 -0700 (PDT) Received: from pyunyh@gmail.com ([114.111.62.249]) by mx.google.com with ESMTPS id kt1sm2911581pbc.32.2012.06.06.22.45.45 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 06 Jun 2012 22:45:47 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Thu, 07 Jun 2012 14:45:42 -0700 From: YongHyeon PYUN Date: Thu, 7 Jun 2012 14:45:42 -0700 To: Mike Tancsa Message-ID: <20120607214542.GE3834@michelle.cdnetworks.com> References: <4FC03C83.4030109@sentex.net> <20120601200942.GD10661@michelle.cdnetworks.com> <4FC8A903.6060203@sentex.net> <201206011030.52753.jhb@freebsd.org> <4FCA223F.5080009@sentex.net> <20120605004720.GB4010@michelle.cdnetworks.com> <4FCF9B42.4090100@sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4FCF9B42.4090100@sentex.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-hardware@freebsd.org Subject: Re: pcie realtek issue (re driver) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Jun 2012 05:45:50 -0000 On Wed, Jun 06, 2012 at 02:02:42PM -0400, Mike Tancsa wrote: > On 6/4/2012 8:47 PM, YongHyeon PYUN wrote: > > Hmm, Target abort/parity error looks serious to me. Could you > > remove re(4) driver in kernel and perform cold boot and check the > > AER errors again? > > (I assume your controller is not a stand-alone PCIe controller so > > I excluded resitting the controller). > > > Hi, > This is a stand alone card actually. Here it is after a power cycle. > Perhaps just a bad card ? Probably yes. For parity errors there is nothing can be done in driver side. It would be interesting to know how other operating systems handle this. > > none2@pci0:4:0:0: class=0x020000 card=0xffffffff chip=0x816810ec > rev=0x03 hdr=0x00 > vendor = 'Realtek Semiconductor Co., Ltd.' > device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller' > class = network > subclass = ethernet > bar [10] = type I/O Port, range 32, base 0, size 256, disabled > bar [18] = type Memory, range 64, base 0, size 4096, disabled > bar [20] = type Prefetchable Memory, range 64, base 0, size 16384, > disabled > cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 > cap 05[50] = MSI supports 1 message, 64 bit > cap 10[70] = PCI-Express 2 endpoint IRQ 2 max data 128(128) link x1(x1) > cap 11[ac] = MSI-X supports 4 messages in maps 0x20 and 0x2c > PCI errors = Master Data Parity Error > Sent Target-Abort > Received Target-Abort > Received Master-Abort > Signalled System Error > Detected Parity Error From owner-freebsd-hardware@FreeBSD.ORG Fri Jun 8 22:17:11 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9F9A8106566C for ; Fri, 8 Jun 2012 22:17:11 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by mx1.freebsd.org (Postfix) with ESMTP id 31EFE8FC14 for ; Fri, 8 Jun 2012 22:17:11 +0000 (UTC) Received: by wibhm6 with SMTP id hm6so1681234wib.1 for ; Fri, 08 Jun 2012 15:17:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=YVDXMY3NZqd0Y1Vk9qsT0Kfieg0aB681HVcYwcHaFg4=; b=qCAxwL3437FyxqMTauyUbz/MWQnAu90YC6yYeZ9GaQgb4RbJhpY2rbUQgd1sQ/MOfC ds2fKWssY6IztNDfYLRKXnqVv/sin906qcPDwqZWAShjGXUXv61fE10XXcQOtYqjhiVC qO3Q2J9kM8BsZJZXw2o20bllSr6nvzmr2SX/JcUwCBTH7BautB9P6rauhM3Xxva5KGzt EykX7/e/5TaSXLwdauLXuvV49rQfdjyw0R0r8EcBP9VNTuzFHtZp2PzieXSoU1Y8ryZ0 8z8eMNmX2vKqGuL7AVHWnP0WWCNHozOn2sFYg44nPgvmqojeJsKrjBZEyP81gEDQSRRv DL2w== MIME-Version: 1.0 Received: by 10.216.196.166 with SMTP id r38mr2080986wen.161.1339193830209; Fri, 08 Jun 2012 15:17:10 -0700 (PDT) Received: by 10.180.84.39 with HTTP; Fri, 8 Jun 2012 15:17:10 -0700 (PDT) In-Reply-To: <201206081611.q58GBW0J097808@fire.js.berklix.net> References: <201206081611.q58GBW0J097808@fire.js.berklix.net> Date: Fri, 8 Jun 2012 18:17:10 -0400 Message-ID: From: grarpamp To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Sat, 09 Jun 2012 01:54:30 +0000 Cc: Subject: Re: UEFI Secure Boot Specs - And some sanity X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2012 22:17:11 -0000 >> Isn't there a lot of needless handwaving going on when the spec is >> pretty clear that installing your own complete PKI tree will all >> boil down to what is effectively a jumper on the motherboard? > Hoping a jumper Might be under an easily unscrewable panel seems unlikely. I did say "effectively". If people would actually read that chapter in the spec (minimally 27.5) they would find that they can: - Load a new PK without asking if in default SetupMode - If not in SetupMode, chainload a new PK provided it is signed by the current PK. - Clear the PK in a 'secure platform specific method'. There's nothing that says PK SetupMode has to be a jumper. Entering the equivalent of good old pre-boot BIOS setup mode would work so long as the OS can't get to it without the request being signed by the current PK. The point of Secure Boot is firmware checked protection against software access... not physical access protection. The spec speaks liberally of 'platform owner' being able to do whatever they want. More handwaving about EULA's and branding aside, that means US. I seriously think that people are blowing this topic way out of context, and seeing it everywhere is getting really old. People should instead be working on the facts and writing the various motherboard manufacturers to ask them what their expected PK update model will be, and to educate them if not. And to work at committing it to their OS. And yes, that includes Compal and Quanta and those sorts of OEM laptop/embedded makers. I'll send $100 to the FreeBSD foundation if those retail board makers I listed don't give the option to install/replace the PK. Nuff said. ps: I don't really care what MS does with their own branded products in the embedded/small space. Plenty of millionaires out there now who are in tune with opensource who could startup, buy the same ARM/ATOM/etc chips, the same support chips, load Android and sell it to the masses. Lot's of overseas ODM's out there for them to pick from too. Phones, tablets, notebooks, laptops... it's all there. FreeBSD on your phone in 10 years. From owner-freebsd-hardware@FreeBSD.ORG Sat Jun 9 14:16:43 2012 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA9231065674 for ; Sat, 9 Jun 2012 14:16:43 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id 99EA58FC0A for ; Sat, 9 Jun 2012 14:16:43 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from ) id 1SdMT4-000Mja-VA for freebsd-hardware@freebsd.org; Sat, 09 Jun 2012 14:16:43 +0000 Date: Sat, 09 Jun 2012 07:16:42 -0700 Message-ID: From: Randy Bush To: freebsd-hardware@freebsd.org In-Reply-To: <20120609120030.A9E27106572E@hub.freebsd.org> References: <20120609120030.A9E27106572E@hub.freebsd.org> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Subject: keying boot X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2012 14:16:43 -0000 > I did say "effectively". If people would actually read that chapter > in the spec (minimally 27.5) they would find that they can: > - Load a new PK without asking if in default SetupMode > - If not in SetupMode, chainload a new PK provided it is > signed by the current PK. > - Clear the PK in a 'secure platform specific method'. > > There's nothing that says PK SetupMode has to be a jumper. beware. what it is today may not be what it will be tomorrow. these are the folk who believe in Trusted Computing. http://en.wikipedia.org/wiki/Trusted_Computing randy