View unanswered posts | View active topics It is currently Mon Dec 10, 2018 6:20 am



Reply to topic  [ 84 posts ]  Go to page 1, 2, 3, 4, 5 ... 9  Next
 Utilite eth1 intel igb Detected Tx Unit Hang 
Author Message

Joined: Mon Oct 14, 2013 7:30 pm
Posts: 6
Post Utilite eth1 intel igb Detected Tx Unit Hang
This may be a topic for the archlinuxarm forums. My issue is the eth1, intel I211, is not working on Arch Linux. Any insight on how to fix this would be welcome.

I installed Arch linux Arm latest for Utilite - 3.0.35-7-ARCH. I was attempting to create a shorewall firewall router. Everything went OK for install and running as a router. However, as soon as any significant network traffic happens, the eth1, intel I211 ethernet hangs. Driver is igb.

# lspci -vv

01:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
Subsystem: Intel Corporation Device 0000
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: 32 bytes
Interrupt: pin A routed to IRQ 155
Region 0: Memory at 01200000 (32-bit, non-prefetchable) [size=128K]
Region 2: I/O ports at 1000000 [disabled] [size=32]
Region 3: Memory at 01220000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=1 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Address: 0000000000000000 Data: 0000
Masking: 00000000 Pending: 00000000
Capabilities: [70] MSI-X: Enable- Count=5 Masked-
Vector table: BAR=3 offset=00000000
PBA: BAR=3 offset=00002000
Capabilities: [a0] Express (v2) Endpoint, MSI 00
DevCap: MaxPayload 512 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+ FLReset-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend-
LnkCap: Port #4, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <2us, L1 <16us
ClockPM- Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Range ABCD, TimeoutDis+, LTR-, OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [100 v2] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr+ BadTLP- BadDLLP- Rollover+ Timeout+ NonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [140 v1] Device Serial Number 00-a0-c9-ff-ff-00-00-00
Capabilities: [1a0 v1] Transaction Processing Hints
Device specific mode supported
Steering table in TPH capability structure
Kernel driver in use: igb
Kernel modules: igb

I had a similar problem a while back with intel e1000e driver and a nic on a DG77KB intel MB. The native eth0 Freescale works just fine. Any suggestions are welcome.

Here is the error:

[ 5052.206166] igb 0000:01:00.0: Detected Tx Unit Hang
[ 5052.206171] Tx Queue <0>
[ 5052.206174] TDH <3>
[ 5052.206178] TDT <3>
[ 5052.206181] next_to_use <3>
[ 5052.206184] next_to_clean <19>
[ 5052.206187] buffer_info[next_to_clean]
[ 5052.206190] time_stamp <73fcf>
[ 5052.206193] next_to_watch <ffdd81a0>
[ 5052.206196] jiffies <74040>
[ 5052.206200] desc.status <108200>
[ 5054.206146] igb 0000:01:00.0: Detected Tx Unit Hang
[ 5054.206151] Tx Queue <0>
[ 5054.206154] TDH <3>
[ 5054.206157] TDT <3>
[ 5054.206160] next_to_use <3>
[ 5054.206163] next_to_clean <19>
[ 5054.206167] buffer_info[next_to_clean]
[ 5054.206170] time_stamp <73fcf>
[ 5054.206173] next_to_watch <ffdd81a0>
[ 5054.206176] jiffies <74108>
[ 5054.206179] desc.status <108200>
[ 5056.206148] igb 0000:01:00.0: Detected Tx Unit Hang
[ 5056.206153] Tx Queue <0>
[ 5056.206157] TDH <3>
[ 5056.206160] TDT <3>
[ 5056.206163] next_to_use <3>
[ 5056.206166] next_to_clean <19>
[ 5056.206169] buffer_info[next_to_clean]
[ 5056.206172] time_stamp <73fcf>
[ 5056.206175] next_to_watch <ffdd81a0>
[ 5056.206178] jiffies <741d0>
[ 5056.206182] desc.status <108200>

[ 5056.250343] ------------[ cut here ]------------
[ 5056.254987] WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0x2a8/0x2cc()
[ 5056.262222] NETDEV WATCHDOG: eth1 (igb): transmit queue 0 timed out
[ 5056.268496] Modules linked in: act_police cls_basic cls_flow cls_fw cls_u32 xt_CHECKSUM xt_statistic xt_CT xt_connlimit xt_realm xt_addrtype ip_set_hash_ip xt_comment xt_recent ipt_ULOG ipt_REJECT ipt_REDIRECT ipt_NETMAP ipt_MASQUERADE ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah xt_set ip_set nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_proto_udplite nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_TPROXY nf_defrag_ipv6 ip6_tables nf_tproxy_core xt_time xt_TCPMSS xt_tcpmss xt_sctp xt_policy xt_pkttype xt_physdev xt_owner xt_NFQUEUE xt_NFLOG xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_helper xt_hashlimit xt_DSCP xt_dscp xt_dccp xt_conntrack xt_connmark xt_CLASSIFY ipt_LOG xt_tcpudp xt_state iptable_raw iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_mangle iptable_filter ip_tables x_tables nfnetlink_log nfnetlink mwifiex_sdio btmrvl_sdio btmrvl mwifiex cfg80211 bluetooth pwm_bl backlight ads7846 igb ppp_generic slhc ipv6
[ 5056.382602] [<c0051cc4>] (unwind_backtrace+0x0/0xf8) from [<c0086184>] (warn_slowpath_common+0x4c/0x64)
[ 5056.392017] [<c0086184>] (warn_slowpath_common+0x4c/0x64) from [<c0086230>] (warn_slowpath_fmt+0x30/0x40)
[ 5056.401605] [<c0086230>] (warn_slowpath_fmt+0x30/0x40) from [<c04fb3f8>] (dev_watchdog+0x2a8/0x2cc)
[ 5056.410678] [<c04fb3f8>] (dev_watchdog+0x2a8/0x2cc) from [<c0092044>] (run_timer_softirq+0x11c/0x268)
[ 5056.419918] [<c0092044>] (run_timer_softirq+0x11c/0x268) from [<c008c04c>] (__do_softirq+0xb4/0x150)
[ 5056.429068] [<c008c04c>] (__do_softirq+0xb4/0x150) from [<c008c4c4>] (irq_exit+0x84/0x8c)
[ 5056.437269] [<c008c4c4>] (irq_exit+0x84/0x8c) from [<c004b794>] (handle_IRQ+0x50/0xb0)
[ 5056.445198] [<c004b794>] (handle_IRQ+0x50/0xb0) from [<c004a9f8>] (__irq_svc+0x38/0xc0)
[ 5056.453233] [<c004a9f8>] (__irq_svc+0x38/0xc0) from [<c00ec940>] (refresh_cpu_vm_stats+0x1c/0x118)
[ 5056.462218] [<c00ec940>] (refresh_cpu_vm_stats+0x1c/0x118) from [<c00eca54>] (vmstat_update+0x18/0x54)
[ 5056.471551] [<c00eca54>] (vmstat_update+0x18/0x54) from [<c009bd6c>] (process_one_work+0x11c/0x3a8)
[ 5056.480616] [<c009bd6c>] (process_one_work+0x11c/0x3a8) from [<c009c300>] (worker_thread+0x138/0x310)
[ 5056.489855] [<c009c300>] (worker_thread+0x138/0x310) from [<c00a0bd4>] (kthread+0x80/0x88)
[ 5056.498139] [<c00a0bd4>] (kthread+0x80/0x88) from [<c004b9dc>] (kernel_thread_exit+0x0/0x8)
[ 5056.506501] ---[ end trace 1baa6a3178441ae5 ]---


Sun Dec 22, 2013 10:31 pm
Profile

Joined: Wed May 25, 2011 11:05 am
Posts: 521
Post Re: Utilite eth1 intel igb Detected Tx Unit Hang
Which utilite model?
Don't think it's eth1, or eth0
ifconfig -a will show interface names


Mon Dec 23, 2013 1:02 am
Profile

Joined: Mon Oct 14, 2013 7:30 pm
Posts: 6
Post Re: Utilite eth1 intel igb Detected Tx Unit Hang
Utilite Pro, 2G memory, with two 1 Gbe. eth0 is Freescale, eth1 is Intel I211 on the PCIe bus using the 'igb' driver module. As I mentioned, I have had nearly the same issue with Intel 82579LM in the past. It eventually got fixed, probably from a bios update. However that nic could have the flash updated. ethtool does not show any flash for the I211.

# ethtool eth1
Settings for eth1:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: off
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes

# ethtool -e eth1
Cannot get EEPROM data: Invalid argument

# ethtool -i eth1
driver: igb
version: 4.1.2
firmware-version: 0. 0-0
bus-info: 0000:01:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no

# dmesg | grep eth
[ 1.567603] i2c-core: driver [isl29023] using legacy suspend method
[ 1.573873] i2c-core: driver [isl29023] using legacy resume method
[ 3.716058] systemd[1]: Expecting device sys-subsystem-net-devices-eth1.device...
[ 3.735956] systemd[1]: Expecting device sys-subsystem-net-devices-eth0.device...
[ 14.497937] igb 0000:01:00.0: eth1: (PCIe:2.5GT/s:Width x1)
[ 14.497943] igb 0000:01:00.0: eth1: MAC: 00:01:c0:14:1a:0a
[ 14.497957] igb 0000:01:00.0: eth1: PBA No: FFFFFF-0FF
[ 19.486516] eth0: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=1:00, irq=-1)
[ 19.487548] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 22.933403] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 22.933993] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 25.896733] igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 25.905013] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 33.195871] eth0: no IPv6 routers present
[ 36.665866] eth1: no IPv6 routers present
[ 5056.262222] NETDEV WATCHDOG: eth1 (igb): transmit queue 0 timed out
[ 5060.226737] igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
[ 5084.036730] igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

# ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.100.1 netmask 255.255.255.0 broadcast 192.168.100.255
inet6 fe80::201:c0ff:fe14:1d60 prefixlen 64 scopeid 0x20<link>
ether 00:01:c0:14:1d:60 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 6 bytes 468 (468.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.157 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::201:c0ff:fe14:1a0a prefixlen 64 scopeid 0x20<link>
ether 00:01:c0:14:1a:0a txqueuelen 1000 (Ethernet)
RX packets 29069 bytes 19975394 (19.0 MiB)
RX errors 0 dropped 3600 overruns 0 frame 0
TX packets 7223 bytes 627149 (612.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

mlan0: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 4c:aa:16:83:ac:43 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


Mon Dec 23, 2013 2:19 pm
Profile

Joined: Wed May 25, 2011 11:05 am
Posts: 521
Post Re: Utilite eth1 intel igb Detected Tx Unit Hang
Yes, the Intel pci might need work, another arch dev had this, had to put utilite pro on external ip address and give root password to compulab to fix. The tool to do this is Intel propriety


Mon Dec 23, 2013 3:11 pm
Profile

Joined: Mon Oct 14, 2013 7:30 pm
Posts: 6
Post Re: Utilite eth1 intel igb Detected Tx Unit Hang
Thanks for the response. So basically this is another Intel Nic that is messed up with power saving modes that do not work, and unlike a MB bios update, this requires "proprietary Intel tool" to fix?? This is crap. I've had enough of Intel ethernet adapters. This means that out of the box, the Utilite is non-functional on the second ethernet. That really sucks.


Tue Dec 24, 2013 2:34 am
Profile
Site Admin

Joined: Sun Mar 13, 2011 11:52 am
Posts: 390
Post Re: Utilite eth1 intel igb Detected Tx Unit Hang
WayneS wrote:
Thanks for the response. So basically this is another Intel Nic that is messed up with power saving modes that do not work, and unlike a MB bios update, this requires "proprietary Intel tool" to fix?? This is crap. I've had enough of Intel ethernet adapters. This means that out of the box, the Utilite is non-functional on the second ethernet. That really sucks.

There seems to be some confusion here...
The Intel NIC requires firmware pre-programming which is done with an Intel manufacturing tool. This pre-programming is performed as part of Utilite manufacturing process and does not need to be done by the user. The second GbE port is fully operational on all Utilite units and works out of the box.
Pepedog refers to an isolated case in which an early pre-production sample (sent to one of his team members) was not flashed correctly and needed to be re-flashed in the field.

Currently all Utilite units are being flashed with the firmware and MAC address and our testing procedures ensure that un-flashed units do not get past QA.

From the logs posted above it does look like the NIC is flashed correctly and the issue is not related to the pre-programming Pepedog has mentioned.

I will ask one of our SW engineers to look into this for further debugging assistance.

_________________
---------------------------
Igor Vaisbein
Utilite Product Manager

---------------------------


Tue Dec 24, 2013 9:22 am
Profile

Joined: Mon Jul 25, 2011 2:35 pm
Posts: 445
Post Re: Utilite eth1 intel igb Detected Tx Unit Hang
Hello WayneS,

The Utilite with a I211 nic has passed iperf tests without any hang issue. Unfortunately, we did not test it with ArchLinux turned into a router.

What Kernel does ArhLinux run on the Utilite?
I'd appreciate it if you could post:
# uname -r
# zcat /proc/config.gz

One more:
Can you please reproduce the issue using iperf, but with the native Utilite image?

Regards,
Valentin.


Tue Dec 24, 2013 2:44 pm
Profile

Joined: Wed May 25, 2011 11:05 am
Posts: 521
Post Re: Utilite eth1 intel igb Detected Tx Unit Hang
Arch is commit b0a0cd8acc6a1112ea3f9074707e5c26e2be1306 On gitoriuos.
Config is https://raw.github.com/archlinuxarm/PKG ... ite/config
Both interfaces work fine for me.


Tue Dec 24, 2013 3:37 pm
Profile

Joined: Mon Oct 14, 2013 7:30 pm
Posts: 6
Post Re: Utilite eth1 intel igb Detected Tx Unit Hang
3.0.35-7-ARCH and config is as shown in pepedog's posted link
https://raw.github.com/archlinuxarm/PKGBUILDs/master/core/linux-utilite/config

Arch linux as router is not an issue, simply using eth1 and trying to download packages, it will fail in the arch build.

I was not successful in building the latest igb driver. When I get some time I will test the release code.

Thanks for all your input.
Wayne


Wed Dec 25, 2013 2:19 pm
Profile

Joined: Mon Oct 14, 2013 7:30 pm
Posts: 6
Post Re: Utilite eth1 intel igb Detected Tx Unit Hang
Native image causes the same Tx Unit Hang if I run the iperf for more than the default 10 seconds. So perhaps the production iperf test is not run for long enough time.

Wayne

root@utilite-desktop:~# iperf -c 192.168.100.1 -t 100
------------------------------------------------------------
Client connecting to 192.168.100.1, TCP port 5001
TCP window size: 117 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.100.2 port 45402 connected with 192.168.100.1 port 5001
igb 0000:01:00.0: Detected Tx Unit Hang
Tx Queue <0>
TDH <ec>
TDT <ec>
next_to_use <ec>
next_to_clean <fb>
buffer_info[next_to_clean]
time_stamp <1eb79>
next_to_watch <ffdd8030>
jiffies <1ec30>
desc.status <0>


Wed Dec 25, 2013 6:38 pm
Profile
Display posts from previous:  Sort by  
Reply to topic   [ 84 posts ]  Go to page 1, 2, 3, 4, 5 ... 9  Next

Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group.
Designed by STSoftware for PTF.