Menu
▾
▴
Re: [E1000-devel] none of driver from e1000-7.6.15.5 to e1000-7.6.9works for me
|
From: Tantilov, E. S <emi...@in...> - 2008-04-26 00:25:34
|
We've had several reports like this in the past. This is most likely a problem with your BIOS - can you check for BIOS updates for this board (what model/make is it btw)? Keep in mind that you will have to rerun the script with the EEPROM fix after a BIOS reflash. For more information about MSI check out the MSI-HOWTO.txt file under the Documentation folder in the kernel source. The interface should work fine with MSI disabled - let us know if you run into other issues. Thanks, Emil -----Original Message----- From: Reeve Yang [mailto:ree...@gm...] Sent: Friday, April 25, 2008 4:48 PM To: Tantilov, Emil S Cc: e10...@li... Subject: Re: [E1000-devel] none of driver from e1000-7.6.15.5 to e1000-7.6.9works for me I compiled with PCI_MSI disabled, it works! But what is it on earth? Sorry I don't know nothing about this. Would it have other side effects? - Reeve On Fri, Apr 25, 2008 at 12:12 PM, Tantilov, Emil S <emi...@in...> wrote: > Please copy e100-devel on your replies - there are others on the list > that may be able to help. > > You said that you were able to pass traffic with the in-kernel driver, > but there were perf issues. Can you try it again after the eeprom fix > and see if it works better? > > At least at first glance I don't see anything obviously wrong. The > interface seems to be generating interrupts and getting link ... > > Another thing to try - build e1000 with MSI disabled: > make CFLAGS_EXTRA=-DDISABLE_PCI_MSI > > Thanks, > Emil > > > > -----Original Message----- > From: Reeve Yang [mailto:ree...@gm...] > Sent: Friday, April 25, 2008 11:25 AM > To: Tantilov, Emil S > Subject: Re: [E1000-devel] none of driver from e1000-7.6.15.5 to > e1000-7.6.9works for me > > Sorry, forget output of ethtool... > > > bash-2.05a# ethtool -e eth1 > Offset Values > ------ ------ > 0x0000 00 30 48 5c 88 4f 20 0d 46 f7 57 00 ff ff ff ff > 0x0010 ff ff ff ff 6b 02 9a 10 d9 15 9a 10 86 80 df 80 > 0x0020 00 00 00 20 54 7e 00 00 00 10 da 00 04 00 00 27 > 0x0030 c9 6c 50 31 32 07 0b 04 84 29 00 00 00 f0 06 07 > 0x0040 08 10 00 00 04 0f ff 7f 01 4d ff ff ff ff ff ff > 0x0050 14 00 1d 00 14 00 1d 00 af aa 1e 00 00 00 1d 00 > 0x0060 00 01 00 40 ff ff ff ff ff ff ff ff ff ff ff ff > 0x0070 ff ff ff ff ff ff ff ff ff ff ff ff ff ff fa 26 > > On Fri, Apr 25, 2008 at 11:22 AM, Reeve Yang <ree...@gm...> > wrote: > > Hi Emil, > > > > Thanks for pointing that out. I download the script, and it says my > > hardware is applicable for the fix so fixed the eeprom. Unfortunately > > after rebooting the problem remains. > > > > Here is more information. > > bash-2.05a# modinfo e1000 > > filename: > /lib/modules/2.6.22.15/kernel/drivers/net/e1000/e1000.ko > > author: Intel Corporation, <lin...@in...> > > description: Intel(R) PRO/1000 Network Driver > > license: GPL > > version: 7.6.15.5 > > vermagic: 2.6.22.15 SMP mod_unload PENTIUM4 > > .... > > bash-2.05a# lspci -vv (only shows e1000 related) > > 03:00.0 0200: 8086:108c (rev 03) > > Subsystem: 15d9:108c > > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > > ParErr- Stepping- SERR+ FastB2B- > > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > > <TAbort- <MAbort- >SERR- <PERR- > > Latency: 0, Cache Line Size 10 > > Interrupt: pin A routed to IRQ 16 > > Region 0: Memory at efa00000 (32-bit, non-prefetchable) > [size=128K] > > Region 2: I/O ports at 4000 [size=32] > > Capabilities: [c8] Power Management version 2 > > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA > > PME(D0+,D1-,D2-,D3hot+,D3cold+) > > Status: D0 PME-Enable- DSel=0 DScale=1 PME- > > Capabilities: [d0] Message Signalled Interrupts: 64bit+ > > Queue=0/0 Enable- > > Address: 0000000000000000 Data: 0000 > > Capabilities: [e0] Express Endpoint IRQ 0 > > Device: Supported: MaxPayload 256 bytes, PhantFunc 0, > ExtTag- > > Device: Latency L0s <512ns, L1 <64us > > Device: AtnBtn- AtnInd- PwrInd- > > Device: Errors: Correctable- Non-Fatal- Fatal- > Unsupported- > > Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ > > Device: MaxPayload 128 bytes, MaxReadReq 512 bytes > > Link: Supported Speed 2.5Gb/s, Width x1, ASPM unknown, > Port 0 > > Link: Latency L0s <128ns, L1 <64us > > Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch- > > Link: Speed 2.5Gb/s, Width x1 > > > > 04:00.0 0200: 8086:109a > > Subsystem: 15d9:109a > > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > > ParErr- Stepping- SERR+ FastB2B- > > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > > <TAbort- <MAbort- >SERR- <PERR- > > Latency: 0, Cache Line Size 10 > > Interrupt: pin A routed to IRQ 218 > > Region 0: Memory at efb00000 (32-bit, non-prefetchable) > [size=128K] > > Region 2: I/O ports at 5000 [size=32] > > Capabilities: [c8] Power Management version 2 > > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA > > PME(D0+,D1-,D2-,D3hot+,D3cold+) > > Status: D0 PME-Enable- DSel=0 DScale=1 PME- > > Capabilities: [d0] Message Signalled Interrupts: 64bit+ > > Queue=0/0 Enable+ > > Address: 00000000fee0300c Data: 414a > > Capabilities: [e0] Express Endpoint IRQ 0 > > Device: Supported: MaxPayload 256 bytes, PhantFunc 0, > ExtTag- > > Device: Latency L0s <512ns, L1 <64us > > Device: AtnBtn- AtnInd- PwrInd- > > Device: Errors: Correctable- Non-Fatal- Fatal- > Unsupported- > > Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ > > Device: MaxPayload 128 bytes, MaxReadReq 512 bytes > > Link: Supported Speed 2.5Gb/s, Width x1, ASPM unknown, > Port 0 > > Link: Latency L0s <128ns, L1 <64us > > Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch- > > Link: Speed 2.5Gb/s, Width x1 > > > > 06:00.0 0200: 8086:109a > > Subsystem: 15d9:109a > > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > > ParErr- Stepping- SERR+ FastB2B- > > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > > <TAbort- <MAbort- >SERR- <PERR- > > Latency: 0, Cache Line Size 10 > > Interrupt: pin A routed to IRQ 18 > > Region 0: Memory at efc00000 (32-bit, non-prefetchable) > [size=128K] > > Region 2: I/O ports at 6000 [size=32] > > Capabilities: [c8] Power Management version 2 > > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA > > PME(D0+,D1-,D2-,D3hot+,D3cold+) > > Status: D0 PME-Enable- DSel=0 DScale=1 PME- > > Capabilities: [d0] Message Signalled Interrupts: 64bit+ > > Queue=0/0 Enable- > > Address: 0000000000000000 Data: 0000 > > Capabilities: [e0] Express Endpoint IRQ 0 > > Device: Supported: MaxPayload 256 bytes, PhantFunc 0, > ExtTag- > > Device: Latency L0s <512ns, L1 <64us > > Device: AtnBtn- AtnInd- PwrInd- > > Device: Errors: Correctable- Non-Fatal- Fatal- > Unsupported- > > Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ > > Device: MaxPayload 128 bytes, MaxReadReq 512 bytes > > Link: Supported Speed 2.5Gb/s, Width x1, ASPM unknown, > Port 0 > > Link: Latency L0s <128ns, L1 <64us > > Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch- > > Link: Speed 2.5Gb/s, Width x1 > > > > 08:00.0 0200: 8086:109a > > Subsystem: 15d9:109a > > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- > > ParErr- Stepping- SERR+ FastB2B- > > Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- > > <TAbort- <MAbort- >SERR- <PERR- > > Latency: 0, Cache Line Size 10 > > Interrupt: pin A routed to IRQ 19 > > Region 0: Memory at efd00000 (32-bit, non-prefetchable) > [size=128K] > > Region 2: I/O ports at 7000 [size=32] > > Capabilities: [c8] Power Management version 2 > > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA > > PME(D0+,D1-,D2-,D3hot+,D3cold+) > > Status: D0 PME-Enable- DSel=0 DScale=1 PME- > > Capabilities: [d0] Message Signalled Interrupts: 64bit+ > > Queue=0/0 Enable- > > Address: 0000000000000000 Data: 0000 > > Capabilities: [e0] Express Endpoint IRQ 0 > > Device: Supported: MaxPayload 256 bytes, PhantFunc 0, > ExtTag- > > Device: Latency L0s <512ns, L1 <64us > > Device: AtnBtn- AtnInd- PwrInd- > > Device: Errors: Correctable- Non-Fatal- Fatal- > Unsupported- > > Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ > > Device: MaxPayload 128 bytes, MaxReadReq 512 bytes > > Link: Supported Speed 2.5Gb/s, Width x1, ASPM unknown, > Port 0 > > Link: Latency L0s <128ns, L1 <64us > > Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch- > > Link: Speed 2.5Gb/s, Width x1 > > > > bash-2.05a# cat /proc/interrupts > > CPU0 CPU1 > > 0: 374955 0 IO-APIC-edge timer > > 1: 4 0 IO-APIC-edge i8042 > > 3: 7487 0 IO-APIC-edge serial > > 4: 1929 0 IO-APIC-edge serial > > 8: 0 0 IO-APIC-edge rtc > > 9: 0 0 IO-APIC-fasteoi acpi > > 14: 0 0 IO-APIC-edge libata > > 15: 0 0 IO-APIC-edge libata > > 16: 0 0 IO-APIC-fasteoi uhci_hcd:usb5 > > 18: 0 0 IO-APIC-fasteoi uhci_hcd:usb4 > > 19: 11135 0 IO-APIC-fasteoi libata, uhci_hcd:usb3 > > 20: 62 0 IO-APIC-fasteoi ehci_hcd:usb1, > uhci_hcd:usb2 > > 218: 174 0 PCI-MSI-edge eth1 > > NMI: 0 0 > > LOC: 102 374459 > > ERR: 0 > > MIS: 0 > > > > bash-2.05a# dmesg (I load e1000-7.6.15 by defaut) > > e1000: 0000:03:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) > > 00:30:48:5c:88:4e > > e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection > > ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 17 (level, low) -> IRQ 17 > > PCI: Setting latency timer of device 0000:04:00.0 to 64 > > e1000: 0000:04:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) > > 00:30:48:5c:88:4f > > e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection > > ACPI: PCI Interrupt 0000:06:00.0[A] -> GSI 18 (level, low) -> IRQ 18 > > PCI: Setting latency timer of device 0000:06:00.0 to 64 > > e1000: 0000:06:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) > > 00:30:48:5c:88:50 > > e1000: eth2: e1000_probe: Intel(R) PRO/1000 Network Connection > > ACPI: PCI Interrupt 0000:08:00.0[A] -> GSI 19 (level, low) -> IRQ 19 > > PCI: Setting latency timer of device 0000:08:00.0 to 64 > > e1000: 0000:08:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x1) > > 00:30:48:5c:88:51 > > e1000: eth3: e1000_probe: Intel(R) PRO/1000 Network Connection > > ip_tables: (C) 2000-2006 Netfilter Core Team > > i2c /dev entries driver > > ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 19 (level, low) -> IRQ 19 > > w83627hf: Found W83627HF chip at 0x290 > > softdog: version magic '2.6.17.4 SMP mod_unload PENTIUM4 gcc-3.2' > > should be '2.6.22.15 SMP mod_unload PENTIUM4 ' > > Software Watchdog Timer: 0.07 initialized. soft_noboot=0 > > soft_margin=60 sec (nowayout= 0) > > nf_conntrack version 0.5.0 (8183 buckets, 65464 max) > > ip6_tables: (C) 2000-2006 Netfilter Core Team > > ADDRCONF(NETDEV_UP): eth1: link is not ready > > e1000: eth1: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full > > Duplex, Flow Control: RX/TX > > ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready > > process `named' is using obsolete setsockopt SO_BSDCOMPAT > > uml_htap0: no IPv6 routers present > > eth1: no IPv6 routers present > > > > > > > > On Fri, Apr 25, 2008 at 8:54 AM, Tantilov, Emil S > > <emi...@in...> wrote: > > > Could you please provide some more information: > > > > > > lspci -vv > > > dmesg (after initial boot and loading the driver) > > > cat /proc/interrupts (after trying to pass some traffic) > > > ethtool -e eth0 > > > > > > If you take a look at the README included with e1000 7.6.15.5 > there is a > > > section about an issue with 82573 that may be the cause for your > > > problems. Check it out and try the fix (there is a script that you > can > > > run - the link is in the README). > > > > > > Thanks, > > > Emil > > > > > > > > > > > > -----Original Message----- > > > From: e10...@li... > > > [mailto:e10...@li...] On Behalf Of > Reeve > > > Yang > > > Sent: Thursday, April 24, 2008 8:03 PM > > > To: e10...@li... > > > Subject: [E1000-devel] none of driver from e1000-7.6.15.5 to > > > e1000-7.6.9works for me > > > > > > My kernel version is 2.6.22.15, the chip set is 82573L Gigabit > > > Ethernet Controller. The e1000 driver from kernel itself (I think > it's > > > 7.3.20 works) but it has performance issue. While I'm trying to > > > upgrade to 7.6.15.5, the driver can be loaded (I compiled as a > > > module), and shows in sysfs, etc. Everything looks fine. But I > just > > > cannot ping to outside or ping from outside, and got freezing > randomly > > > (I guess kernel crashed). > > > > > > I'll appreciate if anyone could shed some lights on it. I won't > > > believe there is only me have this problem (if this is a problem). > Or > > > I have missed anything? > > > > > > Thanks. > > > - Reeve > > > > > > > ------------------------------------------------------------------------ > > > - > > > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > > > Don't miss this year's exciting event. There's still time to save > $100. > > > Use priority code J8TL2D2. > > > > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/j > > > avaone > > > _______________________________________________ > > > E1000-devel mailing list > > > E10...@li... > > > https://lists.sourceforge.net/lists/listinfo/e1000-devel > > > > > > |