Summary: | [em] interface watchdog timeouts and stops receiving packets | ||
---|---|---|---|
Product: | Base System | Reporter: | Neil Hoggarth <neil> |
Component: | kern | Assignee: | jfv |
Status: | Closed Overcome By Events | ||
Severity: | Affects Only Me | CC: | sbruno |
Priority: | Normal | Keywords: | IntelNetworking |
Version: | 7.0-STABLE | ||
Hardware: | Any | ||
OS: | Any |
Description
Neil Hoggarth
2008-04-20 11:40:02 UTC
State Changed From-To: open->feedback Neil: Please additionally provide output of `ifconfig em0' and `sysctl hw.em' Over to maintainer(s). Responsible Changed From-To: freebsd-bugs->freebsd-net Neil: Please additionally provide output of `ifconfig em0' and `sysctl hw.em' Over to maintainer(s). On Sun, 20 Apr 2008, vwe@FreeBSD.org wrote: > Neil: Please additionally provide output of `ifconfig em0' and `sysctl hw.em' The output of "ifconfig em0" looks like this: em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM> ether 00:0e:0c:06:c2:3a inet 10.0.0.7 netmask 0xff000000 broadcast 10.255.255.255 media: Ethernet autoselect (1000baseTX <full-duplex>) status: active "sysctl hw.em" gives an "unknown oid" error. "sysctl dev.em" gives: dev.em.0.%desc: Intel(R) PRO/1000 Network Connection Version - 6.7.3 dev.em.0.%driver: em dev.em.0.%location: slot=9 function=0 dev.em.0.%pnpinfo: vendor=0x8086 device=0x100e subvendor=0x8086 subdevice=0x002e class=0x020000 dev.em.0.%parent: pci2 dev.em.0.debug: -1 dev.em.0.stats: -1 dev.em.0.rx_int_delay: 0 dev.em.0.tx_int_delay: 66 dev.em.0.rx_abs_int_delay: 66 dev.em.0.tx_abs_int_delay: 66 dev.em.0.rx_processing_limit: 100 For the record, the problem persists following the recent MFC of the em driver and locking fix in delta 1.184.2.3 of if_em.c. ifconfig em0: em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 options=9b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM> ether 00:0e:0c:06:c2:3a inet 10.0.0.7 netmask 0xff000000 broadcast 10.255.255.255 media: Ethernet autoselect (1000baseTX <full-duplex>) status: active sysctl dev.em: dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 6.9.5 dev.em.0.%driver: em dev.em.0.%location: slot=9 function=0 dev.em.0.%pnpinfo: vendor=0x8086 device=0x100e subvendor=0x8086 subdevice=0x002e class=0x020000 dev.em.0.%parent: pci2 dev.em.0.debug: -1 dev.em.0.stats: -1 dev.em.0.rx_int_delay: 0 dev.em.0.tx_int_delay: 66 dev.em.0.rx_abs_int_delay: 66 dev.em.0.tx_abs_int_delay: 66 dev.em.0.rx_processing_limit: 100 State Changed From-To: feedback->open Feedback received. Responsible Changed From-To: freebsd-net->jfv Over to maintainer. This chipset is handled by lem(4) nowadays. I suspect it needs to have its watchdog handling updated, but I'm unable to test this specific chipset. If this is still a problem with 10.2r or stable/10, please reopen this issue and we'll look at porting the watchdog enhancements over to lem(4). |