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, [email protected]
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada http://www.tancsa.com/
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "[email protected]"
