[Bug 175333] Re: first eth device gets new number on resume
** Changed in: linux (Ubuntu) Assignee: Registry Administrators (registry) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/175333 Title: first eth device gets new number on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/175333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175333] Re: first eth device gets new number on resume
** Changed in: linux (Ubuntu) Status: Incomplete => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/175333 Title: first eth device gets new number on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/175333/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175333] Re: first eth device gets new number on resume
Just want to try to keep this report up to date. Care to test and confirm this issue remains with the latest development release of Ubuntu (ie Karmic). ISO CD images are available from http://cdimage.ubuntu.com/releases/ . -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175333] Re: first eth device gets new number on resume
I'm having this problem with ubuntu jaunty: r...@ubuntu:~# dmesg | grep eth [4.691544] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61. [4.691952] forcedeth :00:0a.0: PCI INT A -> Link[LMAC] -> GSI 20 (level, low) -> IRQ 20 [4.691957] forcedeth :00:0a.0: setting latency timer to 64 [4.692081] forcedeth :00:0a.0: Invalid Mac address detected: 00:00:00:00:00:00 [4.692085] forcedeth :00:0a.0: Please complain to your hardware vendor. Switching to a random MAC. [5.209066] forcedeth :00:0a.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:00:6c:4a:6c:49 [5.209071] forcedeth :00:0a.0: highdma pwrctl mgmt timirq lnktim msi desc-v3 [ 11.388152] udev: renamed network interface eth0 to eth5 [ 23.681659] forcedeth :00:0a.0: irq 2300 for MSI/MSI-X [ 34.004012] eth5: no IPv6 routers present [ 881.974103] eth5: link down. -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175333] Re: first eth device gets new number on resume
Has anyone been able to confirm with Intrepid? Thanks. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175333] Re: first eth device gets new number on resume
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test: 1) If you are comfortable installing packages on your own, the linux- image-2.6.27-* package is currently available for you to install and test. --or-- 2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD. Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback. ** Tags added: cft-2.6.27 -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175333] Re: first eth device gets new number on resume
Unfortunately the reverse byte-ordering problem of the MAC address after suspend is still present in Hardy (forcedeth driver), although perhaps not in its original form. If I suspend or hibernate the usual way, all is good. I need wake-on- lan, however, and the net card must therefore first be put to sleep (ACPI D3 state). Doing this, hibernate still works, but after resuming from suspend, the byte-ordering of the MAC address is inverted, and the interface gets a new name. A simple workaround: Invert the byte ordering before putting the net card to sleep. Some useful commands for the purpose: ethtool -s eth0 wol g # enable wake-on-lan on eth0 ethtool -i eth0 | grep bus-info # Find PCI bus/device/function Returns "bus-info: :00:04.0 (bus 0, device 4, function 0)" in my case. pci-config is used to set power state to D3, but first the ID must be identified based on the bus-info. List IDs for bus 0: pci-config -B0 -a Returns "Device #12 at bus 0 device/function 4/0, 006610de". Shutdown eth0 and reverse MAC address to avoid problems after resume: ifconfig eth0 down hw ether 08:f6:11:6e:0c:00 # hw MAC is 00:0c:6e:11:f6:08 Set power state of device #12 to D3: pci-config -B0 -S -#12 Now suspend or hibernate. Please note that in order to wake up the machine, you need to use the reversed MAC address: etherwake 08:f6:11:6e:0c:00 All is well after the wake-up call, but without the MAC reversal above, eth0 would be lost after suspend (in any case eth0 needs to be shut down, otherwise the machine will hang when the NIC power state is changed). I am happy with my work-around, so I am not eager to try out patches (and my experience with kernel patching is very limited). Also, I am not sure where this bug should be reported. Thanks, Lars Details: Motherboard: Asus A7N8X Deluxe Linux corolla 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686 GNU/Linux 00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev a1) pci-config is at ftp://ftp.scyld.com/pub/diag/pci-config.c and the power-down procedure was inspired by http://www.nvnews.net/vbulletin/archive/index.php/t-21578.html -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175333] Re: first eth device gets new number on resume
I would just like to point out that sam tygiers bug is not the same as mine, but related ofcourse. >From sam tygiers dmesg: [5.752349] forcedeth :00:0a.0: Invalid Mac address detected: 00:00:00:00:00:00 This card don't read an address at all, whereas my card got it backwards. The patch I linked to earlier here will not work and is most likely included in the hardy kernel anyway. -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175333] Re: first eth device gets new number on resume
** Attachment added: "70-persistent-net.rules" http://launchpadlibrarian.net/13895202/70-persistent-net.rules -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175333] Re: first eth device gets new number on resume
after another suspend it changes again eth10 Link encap:Ethernet HWaddr 00:00:6c:6b:a4:b0 -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175333] Re: first eth device gets new number on resume
** Attachment added: "lspci-vv.txt" http://launchpadlibrarian.net/13895039/lspci-vv.txt -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175333] Re: first eth device gets new number on resume
I am seeing this in hardy on an aspire 7520. after reboot eth8 Link encap:Ethernet HWaddr 00:1b:38:68:92:6c after suspend eth9 Link encap:Ethernet HWaddr 00:00:6c:2b:83:26 i will attach dmesg and lspci -vv ** Changed in: linux (Ubuntu) Sourcepackagename: None => linux -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175333] Re: first eth device gets new number on resume
** Attachment added: "dmesg.txt" http://launchpadlibrarian.net/13895034/dmesg.txt -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175333] Re: first eth device gets new number on resume
I hope I assigned this to the right identity. This bug should be easy to backport to a current gutsy kernel. Patch is provided at http://lkml.org/lkml/2008/1/3/418 ** Changed in: ubuntu Assignee: (unassigned) => Kernel Bugs (kernel-bugs) -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175333] Re: first eth device gets new number on resume
New forcedeth version 0.61 that now ships with Hardy 8.04 Alpha 6 cured this problem on my nVidia nForce 610M chipset. Any chance of forcedeth driver updates to older kernels? -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175333] Re: first eth device gets new number on resume
Bug has been confirmed on LKML, and a patch has been provided there, for testing, which solves the issue in my case. See links below: For a complete discussion on LKML: http://lkml.org/lkml/2008/1/2/253 The provided patch: http://lkml.org/lkml/2008/1/3/418 ** Changed in: ubuntu Status: New => Confirmed -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175333] Re: first eth device gets new number on resume
After some research it apperas that the forcedeth driver, which I use, has had issues with reverse mac addresses in other contexts. A guess is that the driver attempts to correct the address byte order on boot up, but fails to restore on suspend, and therefore reverses the corrected address on resume. I've tried to look up who maintains the driver but found nothing in the driver source files or MAINTAINERS file from the kernel source. -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 175333] Re: first eth device gets new number on resume
Just noticed in that dmesg output that the mac address has a revered byte-order. As I don't know what to do with that I'll leave the bug here. -- first eth device gets new number on resume https://bugs.launchpad.net/bugs/175333 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
