SIOCGMIIREG errors on e1000e interface
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
keepalived (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Binary package hint: keepalived
Running keepalived on 10.04 LTS (running fully updated) throws SIOCGMIIREG errors, it seems to be related to the e1000e driver.
I compiled the latest keepalived version (1.2.2) from source and this resolves the problem.
# dpkg -l | grep keepalived
ii keepalived 1.1.17-2ubuntu1 Failover and monitoring daemon for LVS clust
Errors:
---------
Keepalived_vrrp: SIOCGMIIREG on eth3.4005 failed: Input/output error
Keepalived_
Keepalived_vrrp: SIOCGMIIREG on eth3.4005 failed: Input/output error
Keepalived_
Keepalived_vrrp: SIOCGMIIREG on eth3.4005 failed: Input/output error
Keepalived_
Keepalived_vrrp: SIOCGMIIREG on eth3.4005 failed: Input/output error
Keepalived_
Keepalived_vrrp: SIOCGMIIREG on eth3.4005 failed: Input/output error
Keepalived_
Keepalived_vrrp: SIOCGMIIREG on eth3.4005 failed: Input/output error
Keepalived_
lspci of the nic: (intel quad gig copper nic)
-------
06:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06)
Subsystem: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 33
Region 0: Memory at fe3a0000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at fe380000 (32-bit, non-prefetchable) [size=128K]
Region 2: I/O ports at ccc0 [size=32]
Expansion ROM at e0100000 [disabled] [size=128K]
Capabilities: [c8] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+
Status: D0 PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+
Address: 00000000fee0300c Data: 41d1
Capabilities: [e0] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr- TransPend-
LnkCap: Port #4, Speed 2.5GT/s, Width x4, ASPM L0s, Latency L0 <4us, L1 <64us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
Capabilities: [100] Advanced Error Reporting <?>
Capabilities: [140] Device Serial Number 1e-bb-f6-
Kernel driver in use: e1000e
Kernel modules: e1000e
Hi there,
Thank you for taking the time to report bugs and trying to make Ubuntu better.
Unfortunately,. I've been unable to reproduce this error. However, after some online research this problem appears to be with version 1.1.17 and maybe 1.1.18. Starting from 1.1.19 this seems to be fixed. Unfortunately there doesn't seem to exist a patch to fix this issue specifically but rather just to use a newer upstream version according to what I've read.
For now, I'll be marking this bug as incomplete until a bit more research is done in the issue and maybe finding the appropriate patch in upstream.