Jon, If you can , please send "cat /proc/interrupts" output before and after the issue. Thanks.
-Tushar -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Friday, September 17, 2010 3:46 PM To: [email protected] Subject: Re: [E1000-devel] tx unit hang fc11 Quoting "Dave, Tushar N" <[email protected]>: > Sorry to hear that you have such issue with card. > Is the issue happen only on one system or on multiple systems? > > -Tushar Hello Tushar, I have only tried it on this Linux system, in windows the card works. I have an Intel machine running slack 11 I could try it on but I really would like to use the card in the AMD box as well. Is there anything I can supply you with or anything I could try that would help in solving the issue? Jon > > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Thursday, September 16, 2010 11:54 PM > To: [email protected] > Subject: [E1000-devel] tx unit hang fc11 > > I am having an issue with an Intel card, 82546EB, using the e1000 > driver. It happens as soon as the driver is loaded and will not work. > Using latest driver from sourceforge and have also tried previous > driver 8.0.19. Here is all the information I could think to give that > might help in solving this issue for me. I have verified that the card > does indeed work by testing it in an alternative OS. > > I have tried using the ignore_64bit_dma=1 option as well as > TxDescriptorSet=4 TxDescriptors=1024 options when loading the module > with no discernible difference in behavior. > > Let me know if there is anything else I need to provide or if I have > missed the obvious answer. > > Thanks for any assistance, > > Jon > > uname -r > > 2.6.30.10-105.2.23.fc11.x86_64 > > cat /proc/cpuinfo > > processor : 0 > vendor_id : AuthenticAMD > cpu family : 16 > model : 2 > model name : AMD Phenom(tm) 9500 Quad-Core Processor > stepping : 2 > cpu MHz : 2209.681 > cache size : 512 KB > physical id : 0 > siblings : 4 > core id : 0 > cpu cores : 4 > apicid : 0 > initial apicid : 0 > fpu : yes > fpu_exception : yes > cpuid level : 5 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca > cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt > pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nonstop_tsc > extd_apicid pni monitor cx16 lahf_lm cmp_legacy svm extapic cr8_legacy > abm sse4a misalignsse 3dnowprefetch osvw ibs > bogomips : 4419.35 > TLB size : 1024 4K pages > clflush size : 64 > cache_alignment : 64 > address sizes : 48 bits physical, 48 bits virtual > power management: ts ttp tm stc 100mhzsteps hwpstate > > > > > I am seeing this in dmesg when I issue an ifconfig eth2 or 3 up: > > ADDRCONF(NETDEV_UP): eth3: link is not ready > ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready > e1000: eth2: e1000_clean_tx_irq: Detected Tx Unit Hang > Tx Queue <0> > TDH <2> > TDT <2> > next_to_use <2> > next_to_clean <0> > buffer_info[next_to_clean] > time_stamp <100112192> > next_to_watch <0> > jiffies <100113ce8> > next_to_watch.status <0> > e1000: eth3: e1000_clean_tx_irq: Detected Tx Unit Hang > Tx Queue <0> > TDH <18> > TDT <18> > next_to_use <18> > next_to_clean <0> > buffer_info[next_to_clean] > time_stamp <100113741> > next_to_watch <0> > jiffies <1001140d0> > next_to_watch.status <0> > e1000: eth3: e1000_clean_tx_irq: Detected Tx Unit Hang > Tx Queue <0> > TDH <18> > TDT <18> > next_to_use <18> > next_to_clean <0> > buffer_info[next_to_clean] > time_stamp <100113741> > next_to_watch <0> > jiffies <1001148a0> > next_to_watch.status <0> > > > eth3 Link encap:Ethernet HWaddr 00:02:A5:4F:80:80 > inet addr:192.168.9.21 Bcast:192.168.9.255 Mask:255.255.255.0 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > ethtool -i eth3 > driver: e1000 > version: 8.0.23-NAPI > firmware-version: N/A > bus-info: 0000:01:06.0 > > > cat /proc/interrupts: > > CPU0 CPU1 CPU2 CPU3 > 0: 130 0 0 0 XT-PIC-XT timer > 1: 400 0 0 0 XT-PIC-XT i8042 > 2: 0 0 0 0 XT-PIC-XT cascade > 5: 283 0 0 0 XT-PIC-XT > ohci_hcd:usb2, eth2 > 7: 1 0 0 0 XT-PIC-XT > 8: 24 0 0 0 XT-PIC-XT rtc0 > 9: 0 0 0 0 XT-PIC-XT acpi > 10: 3499 0 0 0 XT-PIC-XT > ehci_hcd:usb1, sata_nv > 11: 3656 0 0 0 XT-PIC-XT sata_nv > 12: 114 0 0 0 XT-PIC-XT i8042 > 14: 1756 0 0 0 XT-PIC-XT > pata_amd > 15: 0 0 0 0 XT-PIC-XT > pata_amd > 27: 0 0 0 703 PCI-MSI-edge eth0 > NMI: 0 0 0 0 Non-maskable interrupts > LOC: 14285 11771 18909 8489 Local timer interrupts > SPU: 0 0 0 0 Spurious interrupts > RES: 1716 2915 1976 1761 Rescheduling interrupts > CAL: 25 79 80 83 Function call interrupts > TLB: 369 530 421 333 TLB shootdowns > TRM: 0 0 0 0 Thermal event interrupts > THR: 0 0 0 0 Threshold APIC interrupts > ERR: 1 > MIS: 0 > > lspci -vv: > > 01:06.0 Ethernet controller: Intel Corporation 82546EB Gigabit > Ethernet Controller (Copper) (rev 01) > Subsystem: Compaq Computer Corporation NC7170 Gigabit Server Adapter > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium > >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 252 (63750ns min), Cache Line Size: 64 bytes > Interrupt: pin A routed to IRQ 11 > Region 0: Memory at fdde0000 (64-bit, non-prefetchable) [size=128K] > Region 2: Memory at fdd80000 (64-bit, non-prefetchable) [size=256K] > Region 4: I/O ports at bc00 [size=64] > [virtual] Expansion ROM at fde00000 [disabled] [size=256K] > Capabilities: [dc] Power Management version 2 > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA > PME(D0+,D1-,D2-,D3hot+,D3cold+) > Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME- > Capabilities: [e4] PCI-X non-bridge device > Command: DPERE- ERO+ RBC=512 OST=1 > Status: Dev=00:00.0 64bit+ 133MHz+ SCD- USC- > DC=simple DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz- > Capabilities: [f0] MSI: Enable- Count=1/1 Maskable- 64bit+ > Address: 0000000000000000 Data: 0000 > Kernel driver in use: e1000 > Kernel modules: e1000 > > 01:06.1 Ethernet controller: Intel Corporation 82546EB Gigabit > Ethernet Controller (Copper) (rev 01) > Subsystem: Compaq Computer Corporation NC7170 Gigabit Server Adapter > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > ParErr- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium > >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 252 (63750ns min), Cache Line Size: 64 bytes > Interrupt: pin B routed to IRQ 5 > Region 0: Memory at fddc0000 (64-bit, non-prefetchable) [size=128K] > Region 4: I/O ports at b800 [size=64] > Capabilities: [dc] Power Management version 2 > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA > PME(D0+,D1-,D2-,D3hot+,D3cold-) > Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=1 PME- > Capabilities: [e4] PCI-X non-bridge device > Command: DPERE- ERO+ RBC=512 OST=1 > Status: Dev=00:00.1 64bit+ 133MHz+ SCD- USC- > DC=simple DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz- > Capabilities: [f0] MSI: Enable- Count=1/1 Maskable- 64bit+ > Address: 0000000000000000 Data: 0000 > Kernel driver in use: e1000 > Kernel modules: e1000 > > > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > E1000-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/e1000-devel > To learn more about Intel® Ethernet, visit > http://communities.intel.com/community/wired > ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
