Bug 9073
Summary: | Ethernet not functioning on Nvidia MCP51 since (at least 2.6.21.6); works perfectly with 2.6.18 | ||
---|---|---|---|
Product: | Networking | Reporter: | Philippe Bourcier (buffalo.phil) |
Component: | Other | Assignee: | Arnaldo Carvalho de Melo (acme) |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | CC: | aabdulla, c-d.hailfinger.kernel.2004, eswierk, manfred |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.23 | Subsystem: | |
Regression: | Yes | Bisected commit-id: |
Description
Philippe Bourcier
2007-09-26 03:12:44 UTC
What is not functioning? - Do you see an interface when you type "ifconfig"? - Are the Rx and Tx counters not incrementing? - Can you check "cat /proc/interrupts"? - Is the ethernet cable link light on? Linux ile 2.6.23-rc5-amd64 #1 SMP Mon Sep 17 01:12:09 UTC 2007 x86_64 GNU/Linux lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:162 errors:0 dropped:0 overruns:0 frame:0 TX packets:162 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12410 (12.1 KiB) TX bytes:12410 (12.1 KiB) CPU0 CPU1 0: 297 35914 IO-APIC-edge timer 1: 0 83 IO-APIC-edge i8042 2: 0 0 XT-PIC-XT cascade 5: 2 534 IO-APIC-fasteoi ohci_hcd:usb1, ahci 7: 27 37803 IO-APIC-fasteoi sata_nv 8: 0 0 IO-APIC-edge rtc 9: 0 0 IO-APIC-edge acpi 10: 0 412 IO-APIC-fasteoi HDA Intel 11: 3 5092 IO-APIC-fasteoi firewire_ohci, sata_nv 12: 0 4 IO-APIC-edge i8042 15: 0 28 IO-APIC-fasteoi ehci_hcd:usb2 NMI: 0 0 LOC: 47595 36065 ERR: 0 I use currently: $ uname -a ;/sbin/ifconfig; cat /proc/interrupts Linux ile 2.6.18-5-amd64 #1 SMP Thu Aug 30 01:14:54 UTC 2007 x86_64 GNU/Linux eth1 Link encap:Ethernet HWaddr 26:9E:A6:F3:18:00 inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::249e:a6ff:fef3:1800/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1414364 errors:0 dropped:0 overruns:0 frame:0 TX packets:1982183 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:828681731 (790.2 MiB) TX bytes:937220033 (893.8 MiB) Interrupt:15 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:21859 errors:0 dropped:0 overruns:0 frame:0 TX packets:21859 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1309464 (1.2 MiB) TX bytes:1309464 (1.2 MiB) CPU0 CPU1 0: 23891512 0 IO-APIC-level timer 1: 32475 0 IO-APIC-edge i8042 2: 0 0 XT-PIC cascade 5: 239633 0 IO-APIC-level ohci_hcd:usb2 7: 1375701 0 IO-APIC-level libata 8: 0 0 IO-APIC-edge rtc 9: 0 0 IO-APIC-edge acpi 10: 5876763 0 IO-APIC-level HDA Intel, nvidia 11: 163683 0 IO-APIC-level ohci1394, libata 15: 12942617 0 IO-APIC-level ehci_hcd:usb1, eth1 NMI: 11628 13299 LOC: 23893116 23893147 ERR: 0 MIS: 0 It looks like you received and transmitted quite a few packets. If you perform a ping, do either of the counters increment? Also, does the interrupt count increment for eth1 (i.e. 15)? Once in the failing state, can you send me the output of "ethtool -d eth1"? as I said first: "the forcedeth driver is broken on Nvidia MCP51 since (at least 2.6.21.6); works perfectly with 2.6.18" this bug report is about 2.6.23-rc5-amd64 $ sudo ethtool -d eth1 Cannot get driver information: No such device Comment #2 gave you a working example on 2.6.18-5-amd64 if you want to compare Ok, I didn't realize that Comment 2 was on working system. In the dmesg trace I see the following: eth0: forcedeth.c: subsystem: 01043:81bc bound to 0000:00:14.0 net eth2: device_rename: sysfs_create_symlink failed (-17) udev: renamed network interface eth0 to eth2 Not sure what the renaming is all about. What happens if you manually perform "ifconfig eth0 up" or "ifconfig eth2 up". $ sudo ifconfig eth0 up eth0: ERROR while getting interface flags: No such device $ sudo ifconfig eth2 up $ sudo ifconfig eth2 Link encap:Ethernet HWaddr 00:18:F3:A6:9E:26 inet6 addr: fe80::218:f3ff:fea6:9e26/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7 errors:0 dropped:0 overruns:0 frame:0 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:420 (420.0 b) TX bytes:4294967713 (4.0 GiB) Interrupt:15 Base address:0xe000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:162 errors:0 dropped:0 overruns:0 frame:0 TX packets:162 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12410 (12.1 KiB) TX bytes:12410 (12.1 KiB) yeah! for a reason I that don't understand, udev now renames eth0 in eth2 in 2.6.18, it renamed it in eth1 on my debian, i changed that in: /etc/network/interfaces thanks a lot Ayaz for showing me the way! |