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/