lspci: 01:01.0 Ethernet controller: Intel Corporation 82545GM Gigabit Ethernet Controller (rev 04) 01:02.0 Ethernet controller: Intel Corporation 82545GM Gigabit Ethernet Controller (rev 04) 02:01.0 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet Controller (rev 03) 02:01.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet Controller (rev 03) All interface are correctly configured. In kernel <2.6.26 get all OK, in newest kernels network interfaces are not working. Problem is in driver e1000. Tested on 2.6.31,2.6.32,2.6.34 and 2.6.35rc.
(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Fri, 25 Jun 2010 17:48:43 GMT bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=16293 > > Summary: 82545GM in newest kernel not working. > Product: Drivers > Version: 2.5 > Kernel Version: 2.6.32.15 > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: high > Priority: P1 > Component: Network > AssignedTo: drivers_network@kernel-bugs.osdl.org > ReportedBy: lukas.valach@zoznam.sk > Regression: No > > > lspci: > > 01:01.0 Ethernet controller: Intel Corporation 82545GM Gigabit Ethernet > Controller (rev 04) > 01:02.0 Ethernet controller: Intel Corporation 82545GM Gigabit Ethernet > Controller (rev 04) > 02:01.0 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet > Controller (rev 03) > 02:01.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet > Controller (rev 03) > > All interface are correctly configured. In kernel <2.6.26 get all OK, in > newest > kernels network interfaces are not working. Problem is in driver e1000. > Tested > on 2.6.31,2.6.32,2.6.34 and 2.6.35rc. A somewhat old e1000 regression?
Andrew Morton wrote: > (switched to email. Please respond via emailed reply-to-all, not via > the bugzilla web interface). > > On Fri, 25 Jun 2010 17:48:43 GMT > bugzilla-daemon@bugzilla.kernel.org wrote: > >> https://bugzilla.kernel.org/show_bug.cgi?id=16293 >> >> Summary: 82545GM in newest kernel not working. >> Product: Drivers Version: 2.5 >> Kernel Version: 2.6.32.15 >> Platform: All >> OS/Version: Linux >> Tree: Mainline >> Status: NEW >> Severity: high >> Priority: P1 >> Component: Network >> AssignedTo: drivers_network@kernel-bugs.osdl.org >> ReportedBy: lukas.valach@zoznam.sk >> Regression: No >> >> >> lspci: >> >> 01:01.0 Ethernet controller: Intel Corporation 82545GM Gigabit >> Ethernet Controller (rev 04) 01:02.0 Ethernet controller: Intel >> Corporation 82545GM Gigabit Ethernet Controller (rev 04) 02:01.0 >> Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet >> Controller (rev 03) 02:01.1 Ethernet controller: Intel Corporation >> 82546GB Gigabit Ethernet Controller (rev 03) >> >> All interface are correctly configured. In kernel <2.6.26 get all >> OK, in newest kernels network interfaces are not working. Problem is >> in driver e1000. Tested on 2.6.31,2.6.32,2.6.34 and 2.6.35rc. > > A somewhat old e1000 regression? I ran a quick test on net-next with 82545GM NICs and was able to pass traffic without issues. Would it be possible to get more information about the system/setup: 1. full lspci output (lspci -vvv) 2. ethtool -i ethX 3. ethtool -d ethX 4. ethtool -e ethX 5. dmesg - after loading the driver and configuring the interfaces 6. kernel config A better description of the issue would help as well. What exactly fails - ping? Thanks, Emil
Ping said request timeout. ARP records for gateway missing.
Created attachment 33332 [details] dmesg
Created attachment 33342 [details] lspci
Created attachment 33352 [details] ethtool
I have same problem, network is not working after upgrade from 2.6.26 to 26.32. Command ip link shows NO-CARRIER. I have attached lspci, dmesg and ethool from not working system.
No proggress? Should I add some more information?
This may be a core kernel interrupt routing issue on your platform, these lines in your dmesg are suspect: [ 2.913091] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection >>> [ 2.913126] e1000 0000:01:02.0: can't derive routing for PCI INT A [ 2.913130] e1000 0000:01:02.0: PCI INT A: no GSI - using IRQ 5 [ 4.030032] e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network Connection [ 4.030074] e1000 0000:02:01.0: can't derive routing for PCI INT A [ 4.030077] e1000 0000:02:01.0: PCI INT A: no GSI - using IRQ 5 [ 4.301021] e1000: 0000:02:01.0: e1000_probe: (PCI-X:100MHz:64-bit) 00:0e:0c:00:9a:6c [ 5.146024] e1000: eth2: e1000_probe: Intel(R) PRO/1000 Network Connection [ 5.146053] e1000 0000:02:01.1: can't derive routing for PCI INT B [ 5.146056] e1000 0000:02:01.1: PCI INT B: no GSI - using IRQ 7 [ 5.417011] e1000: 0000:02:01.1: e1000_probe: (PCI-X:100MHz:64-bit) 00:0e:0c:00:9a:6d [ 6.262070] e1000: eth3: e1000_probe: Intel(R) PRO/1000 Network Connection I think that you should check the (watch -d cat /proc/interrupts) output over 3-5 seconds, and see if there are any interrupts coming on eth1/2/3, there should be one every two seconds. if there is not you likely have an interrupt routing or IOAPIC problem. you could try booting with pci=noapic or some of the other troubleshooting options mentioned in kernel file Documentation/kernel-parameters.txt
Thanks for suggestion, after booting with option "pci=noacpi noapic" is network working.