Date: Wed, 23 Aug 2006 15:09:11 +0200 From: Stefan Bethke <stb@lassitu.de> To: "Patrick M. Hausen" <hausen@punkt.de> Cc: cvs-src@freebsd.org, Gleb Smirnoff <glebius@freebsd.org>, src-committers@freebsd.org, cvs-all@freebsd.org, Pyun YongHyeon <yongari@freebsd.org> Subject: Re: cvs commit: src/sys/dev/em if_em.c Message-ID: <F1B78FCF-7C22-436E-BAAE-57F2ACA45994@lassitu.de> In-Reply-To: <20060822190223.GB89314@hugo10.ka.punkt.de> References: <200608220232.k7M2WmCr080275@repoman.freebsd.org> <20060822152333.GV96644@FreeBSD.org> <44EB220A.5000709@centtech.com> <20060822153210.GW96644@FreeBSD.org> <44EB2437.5070206@centtech.com> <20060822185313.GX96644@FreeBSD.org> <20060822190223.GB89314@hugo10.ka.punkt.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 22.08.2006 um 21:02 schrieb Patrick M. Hausen:
> em interface, FTPing a large file while putting disk and cpu/memory
> load on the box -> occasional but easily reproducable complete hangs
> of network communication (ssh, ping - no reaction). Every time a
>
> em0: Missing Tx completion interrupt!
>
> is logged.
I have no idea whether the effect I'm seeing is related at all, but
the description fits. If I load the CPU (make world -j4 or gzip -9 </
dev/random >/dev/null), traffic over re0 stops and I get
Aug 22 09:30:20 diesel kernel: re0: watchdog timeout
Aug 22 09:30:20 diesel kernel: re0: link state changed to DOWN
Aug 22 09:30:23 diesel kernel: re0: link state changed to UP
Aug 22 09:30:35 diesel kernel: re0: watchdog timeout
Aug 22 09:30:35 diesel kernel: re0: link state changed to DOWN
Aug 22 09:30:39 diesel kernel: re0: link state changed to UP
until I stop the CPU hog; then, it appears to be working fine again.
I've got two rl's in there as well, and they appear to be completely
unaffected.
FreeBSD diesel 6.1-STABLE FreeBSD 6.1-STABLE #9: Fri Aug 18 00:32:12
CEST 2006 root@diesel:/usr/obj/usr/src/sys/DIESEL i386
rl0: <RealTek 8139 10/100BaseTX> port 0xe800-0xe8ff mem
0xdfdff000-0xdfdff0ff irq 16 at device 0.0 on pci1
miibus0: <MII bus> on rl0
rlphy0: <RealTek internal media interface> on miibus0
rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
rl0: Ethernet address: 00:a1:b0:f0:aa:a2
rl1: <RealTek 8139 10/100BaseTX> port 0xec00-0xecff mem
0xdfdfe000-0xdfdfe0ff irq 17 at device 5.0 on pci1
miibus1: <MII bus> on rl1
rlphy1: <RealTek internal media interface> on miibus1
rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
rl1: Ethernet address: 00:a1:b0:f0:a8:57
re0: <RealTek 8169SB/8110SB Single-chip Gigabit Ethernet> port
0xea00-0xeaff mem 0xdfdfd000-0xdfdfd0ff irq 18 at device 10.0 on pci1
miibus2: <MII bus> on re0
rgephy0: <RTL8169S/8110S media interface> on miibus2
rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX,
1000baseTX-FDX, auto
re0: Ethernet address: 00:01:29:2c:44:e9
re0: [FAST]
rl0@pci1:0:0: class=0x020000 card=0x813910ec chip=0x813910ec
rev=0x10 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter'
class = network
subclass = ethernet
rl1@pci1:5:0: class=0x020000 card=0x813910ec chip=0x813910ec
rev=0x10 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter'
class = network
subclass = ethernet
re0@pci1:10:0: class=0x020000 card=0x100a15bd chip=0x816910ec
rev=0x10 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8169 Gigabit Ethernet Adapter'
class = network
subclass = ethernet
--
Stefan Bethke <stb@lassitu.de> Fon +49 170 346 0140
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F1B78FCF-7C22-436E-BAAE-57F2ACA45994>