[r8169] mac addres lost

Bug #165052 reported by Guffmonger
8
Affects Status Importance Assigned to Milestone
Linux
Invalid
Medium
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

I installed a cli 2.6.22-14-xen based system from an ubuntu-7.10-alternate-amd64.iso image.
Everything worked fine untill I rebooted the system afterwhich eth0 dissappears and re-appears as eth1 with an incorrect mac-address (FE:FF:FF:FF:FF:FF)
This of course results in my static network configuration not functioning as eth0 no longer exists.
No matter how many times I reboot the system eth0 remains eth1 and assumes the mac-address (FE:FF:FF:FF:FF:FF)
Only after shutting down the system and removing the power for about 5-10 seconds does eth0 return with the correct mac-address.

I have tried 3 different kernels without any improvement
   2.6.22-14-xen (ubuntu)
   2.6.22-14-generic (ubuntu)
   2.6.23.8 (kernel.org - compiled using config from 2.6.22-14-generic)

My Gigabyte G33M-DS2R motherboard has an on-board Realtek RTL8111b (see results of lspci below for more details)

By default, the kernel chooses the r8169 module for this device.
I tried using the r8168 as supplied by Realtek on their web site (r8168-8.003.00.tar.bz2)
This also did not solve the problem.

I suspect that there might be an issue with udev.

Information............

BEFORE FIRST REBOOT
===================

Contents of /etc/udev/rules.d/70-persistent-net.rules
-----------------------------------------------------
# PCI device 0x10ec:0x8168 (r8168)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1a:4d:##:##:##", NAME="eth0"

ifconfig -a
-----------
eth0 Link encap:Ethernet HWaddr 00:1A:4D:##:##:##
          inet addr:192.168.###.### Bcast:192.168.###.### Mask:255.255.###.###
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:794 errors:0 dropped:0 overruns:0 frame:0
          TX packets:200 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:61672 (60.2 KB) TX bytes:33093 (32.3 KB)

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:561 (561.0 b) TX bytes:561 (561.0 b)

peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
          RX packets:1050 errors:0 dropped:0 overruns:0 frame:0
          TX packets:210 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:85173 (83.1 KB) TX bytes:33773 (32.9 KB)
          Interrupt:17 Base address:0x2000

veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
          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:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00
          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:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00
          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:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
          RX packets:200 errors:0 dropped:0 overruns:0 frame:0
          TX packets:794 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:33093 (32.3 KB) TX bytes:61672 (60.2 KB)

vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
          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:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
          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:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
          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:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
          UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
          RX packets:1056 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:69809 (68.1 KB) TX bytes:0 (0.0 b)

AFTER FIRST AND EVERY REBOOT
============================

Contents of /etc/udev/rules.d/70-persistent-net.rules
-----------------------------------------------------
# PCI device 0x10ec:0x8168 (r8168)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:1a:4d:##:##:##", NAME="eth0"

# PCI device 0x10ec:0x8168 (r8168)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="fe:ff:ff:ff:ff:ff", NAME="eth1"

ifconfig -a
-----------
eth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
          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)
          Interrupt:17 Base address:0x2000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          UP LOOPBACK RUNNING MTU:16436 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:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

veth0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
          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:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

veth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
          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:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00
          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:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00
          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:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
          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:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
          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:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
          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:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
          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:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

xenbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
          UP BROADCAST RUNNING NOARP 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:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

FURTHER INFORMATION
===================

HARDWARE
--------

Motherboard:
   Gigabyte G33M-DS2R
BIOS:
   F5 (09/07/2007)
CPU:
   Core 2 Duo E6750
HD:
   WDC WD5000YS

uname -a
--------
Linux node1 2.6.22-14-xen #1 SMP Sun Oct 14 23:20:20 GMT 2007 x86_64 GNU/Linux

lspci -nnvv
-----------
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 01)
        Subsystem: Giga-byte Technology Unknown device [1458:e000]
        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: 32 bytes
        Interrupt: pin A routed to IRQ 17
        Region 0: I/O ports at d000 [size=256]
        Region 2: Memory at f2000000 (64-bit, non-prefetchable) [size=4K]
        [virtual] Expansion ROM at f3200000 [disabled] [size=64K]
        Capabilities: [40] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold+)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [48] Vital Product Data
        Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable-
                Address: 0000000000000000 Data: 0000
        Capabilities: [60] Express Endpoint IRQ 0
                Device: Supported: MaxPayload 1024 bytes, PhantFunc 0, ExtTag+
                Device: Latency L0s unlimited, L1 unlimited
                Device: AtnBtn+ AtnInd+ PwrInd+
                Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
                Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
                Device: MaxPayload 128 bytes, MaxReadReq 4096 bytes
                Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s, Port 0
                Link: Latency L0s unlimited, L1 unlimited
                Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
                Link: Speed 2.5Gb/s, Width x1
        Capabilities: [84] Vendor Specific Information

lshw -C Network
---------------
  *-network
       description: Ethernet interface
       product: RTL8111/8168B PCI Express Gigabit Ethernet controller
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: peth0
       version: 01
       serial: 00:1a:4d:##:##:##
       size: 1GB/s
       capacity: 1GB/s
       width: 64 bits
       clock: 33MHz
       capabilities: pm vpd msi pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=r8168 driverversion=8.003.00-NAPI duplex=full latency=0 link=yes module=r8168 port=twisted pair speed=1GB/s
....

Revision history for this message
Oleksij Rempel (olerem) wrote :

This is known issue... i had one PC with this card and WindowsXp installed in my network. And it seems like there is no fix for it, see:
http://marc.info/?l=linux-kernel&m=116414200419321&w=2

I leave this bug confirmed, but it should be changed to "Will Not be Fixed"

Revision history for this message
Claus Rosenberger (claus-rosenberger) wrote :

I don't know if it is a problem with xen or with the network interface driver.

The big question is, should the original MAC address to be restored on startup of the machine or not?

Whats happening here is that xen is moving the physical interface eth0 to peth0. The dom0 will use a virtual interface eth0 which get the original MAC address of the network card. peth0 which is the physical card is only in bridging mode and has the virtual MAC address FE:FF:FF:FF:FF:FF. After the restart peth0 has still FE:FF:FF:FF:FF:FF which is wrong because it will be loaded as eth0 first. Then it starts from the beginning, eth0 with the wrong MAC will be copied to peth0 and the wrong MAC will be transported to the virtual device eth0.

There are two ways how that problem can be solved.

1. with xend stop the script network-bridge should be started with parameter stop, at this point the original mac address we be set to the physical device again.
2. on every startup or load of the module r8169 the mac address has to be set to the interface card.

Perhaps anybody can give more hints to following points:

1. Is there a command to restore the original MAC address of a r8169 interface card?
2. Should the original MAC address not be set back on system startup by the interface itself?

Revision history for this message
Oleksij Rempel (olerem) wrote :

- hardware of r8169 is broken and ( linux/windows ) driver can't do any thing about it.
- ubuntu should hard connect mac with interface, so 00:1A:4D:##:##:## = eth0 and FE:FF:FF:FF:FF:FF = eth1, _see_ /etc/iftab

> Perhaps anybody can give more hints to following points:
> 1. Is there a command to restore the original MAC address of a r8169 interface card?
> 2. Should the original MAC address not be set back on system startup by the interface itself?
1. yes, ip l set eth0 addr 04:44:44:44:44:04
2. no. this is hardware problem and only complete power off can help.

Revision history for this message
Oleksij Rempel (olerem) wrote :

hmmm... please can you attach your dmesg. and if it possible with newest hardy kernel.
If it really not fixable hardware problem, kernel should warn about it. if not - i will take this bug.

Revision history for this message
Claus Rosenberger (claus-rosenberger) wrote :
Download full text (26.4 KiB)

dmesg:

[ 0.000000] Linux version 2.6.22-14-xen (buildd@crested) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Sun Oct 14 23:20:20 GMT 2007 (Unofficial)
[ 0.000000] Command line: root=UUID=0e673891-c974-4ac4-be3f-6d023bf168aa ro console=tty0
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] Xen: 0000000000000000 - 00000000f19cd000 (usable)
[ 0.000000] Entering add_active_range(0, 0, 989645) 0 entries of 256 used
[ 0.000000] end_pfn_map = 989645
[ 0.262178] DMI 2.3 present.
[ 0.262316] Entering add_active_range(0, 0, 989645) 0 entries of 256 used
[ 0.271420] Zone PFN ranges:
[ 0.271422] DMA 0 -> 989645
[ 0.271424] DMA32 989645 -> 989645
[ 0.271426] Normal 989645 -> 989645
[ 0.271427] early_node_map[1] active PFN ranges
[ 0.271429] 0: 0 -> 989645
[ 0.271431] On node 0 totalpages: 989645
[ 0.291230] DMA zone: 13530 pages used for memmap
[ 0.291232] DMA zone: 0 pages reserved
[ 0.291235] DMA zone: 976115 pages, LIFO batch:31
[ 0.344018] DMA32 zone: 0 pages used for memmap
[ 0.344021] Normal zone: 0 pages used for memmap
[ 0.355282] ACPI: RSDP 000F6950, 0014 (r0 GBT )
[ 0.355291] ACPI: RSDT DDEE3000, 0034 (r1 GBT GBTUACPI 42302E31 GBTU 1010101)
[ 0.355302] ACPI: FACP DDEE3040, 0074 (r1 GBT GBTUACPI 42302E31 GBTU 1010101)
[ 0.355313] ACPI: DSDT DDEE30C0, 4607 (r1 GBT GBTUACPI 1000 MSFT 100000C)
[ 0.355320] ACPI: FACS DDEE0000, 0040
[ 0.355326] ACPI: SSDT DDEE7780, 0248 (r1 PTLTD POWERNOW 1 LTP 1)
[ 0.355333] ACPI: MCFG DDEE7A00, 003C (r1 GBT GBTUACPI 42302E31 GBTU 1010101)
[ 0.355340] ACPI: APIC DDEE7700, 0068 (r1 GBT GBTUACPI 42302E31 GBTU 1010101)
[ 0.355373] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.355375] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
[ 0.355381] ACPI: LAPIC_NMI (acpi_id[0x00] dfl dfl lint[0x1])
[ 0.355383] ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
[ 0.355388] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
[ 0.355395] IOAPIC[0]: apic_id 2, address 0xfec00000, GSI 0-23
[ 0.355400] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.355403] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[ 0.355405] ACPI: IRQ0 used by override.
[ 0.355406] ACPI: IRQ2 used by override.
[ 0.355408] ACPI: IRQ9 used by override.
[ 0.355413] Setting APIC routing to xen
[ 0.355415] Using ACPI (MADT) for SMP configuration information
[ 0.355424] Allocating PCI resources starting at f1000000 (gap: f0000000:ec00000)
[ 0.355430] PERCPU: Allocating 25096 bytes of per cpu data
[ 0.355461] Built 1 zonelists. Total pages: 976115
[ 0.355463] Kernel command line: root=UUID=0e673891-c974-4ac4-be3f-6d023bf168aa ro console=tty0
[ 0.356026] Initializing CPU#0
[ 0.356147] PID hash table entries: 4096 (order: 12, 32768 bytes)
[ 0.356238] Xen reported: 2305.290 MHz processor.
[ 0.357432] Console: colour VGA+ 80x50
[ 0.363861] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes)
[ 0.366799] Inode-cache hash table entries...

Revision history for this message
Claus Rosenberger (claus-rosenberger) wrote :

Following workaround if only one card of this type is installed.

File /etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", DRIVERS=="?*", SYSFS{vendor}=="0x10ec", SYSFS{device}=="0x8167", NAME="eth0"

The card is always eth0 with every MAC address, even with the wrong.

File /etc/network/interfaces
# The primary network interface
auto eth0
iface eth0 inet static
        address 10.0.0.1
        netmask 255.255.255.0
        network 10.0.0.0
        broadcast 10.0.0.255
        hwaddress ether xx:xx:xx:xx:xx:xx <---- original hw mac address

Revision history for this message
Claus Rosenberger (claus-rosenberger) wrote :

The Realtek driver is not working better, one additional problem i have found. the peth0 interface (physical in xen configuration) is responding to arp requests even if no arp is configured). Perhaps it's an additional problem of the hardware.

Revision history for this message
Oleksij Rempel (olerem) wrote : Re: [Bug 165052] Re: [r8169] mac addres lost

Please test this kernel and attach dmesg as file. do not post it.

wget
http://de.archive.ubuntu.com/ubuntu/pool/main/l/linux/linux-image-2.6.24-1-386_2.6.24-1.2_i386.deb
sudo dpkg -i linux-image-2.6.24-1-386_2.6.24-1.2_i386.deb

to unisntall use:
sudo dpkg -r linux-image-2.6.24-1

Revision history for this message
Claus Rosenberger (claus-rosenberger) wrote :
Revision history for this message
Oleksij Rempel (olerem) wrote :

can you please test if MAC will be recovered after complete poweroff.
And try to disable "wake on lan" in BIOS.

Changed in linux-source-2.6.22:
assignee: nobody → bug-track
Revision history for this message
Claus Rosenberger (claus-rosenberger) wrote :

There is no difference :(

Revision history for this message
Oleksij Rempel (olerem) wrote :

Claus, or you have a bit different issue to primary post or you didn't wrote or tested some thing. Primary bug is:
1. first start, mac is correct
2. after reboot or normal poweroff, mac is wrong ( fe:ff:ff:ff:ff:ff ).
3. after complete poweroff ( PC should be _unplugged_ for at lest 10 seconds ) mac will be recovered.

probably you should remove/comment udev and/or interfaces entry's you made.
To exclude other services start machine in "recovery mode" / single mode and check if mac is still fe:ff...
If mac still fe:ff.. set it some thing other for example 11:22:33.... and reboot again in recovery mode.

try to get some more info.
echo "options r8169 debug=16" > /etc/modprobe.d/r8169

Revision history for this message
Claus Rosenberger (claus-rosenberger) wrote :

1. yes
2. yes
3. no, even with switched off machine und unplugged network and electricity there is a wrong mac

the card is storing the changed mac and remember on next boot. i changed a few things and use a workaround now which makes sense only if there is not more then one r8169 inside of the machine.

Revision history for this message
Oleksij Rempel (olerem) wrote :

Great! I understood it :)

Revision history for this message
Oleksij Rempel (olerem) wrote :

I forwarded this report upstream:
http://bugzilla.kernel.org/show_bug.cgi?id=9560
please subscribe it.

Revision history for this message
Oleksij Rempel (olerem) wrote :

Please test it with newest hardy kernel.

Changed in linux-source-2.6.22:
assignee: bug-track → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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.

Changed in linux:
status: Unknown → In Progress
Changed in linux:
status: In Progress → Invalid
Revision history for this message
Manoj Iyer (manjo) wrote :

Can you also confirm this issue exists with the most recent Karmic Koala 9.10 Alpha release? ISO CD images are available at http://cdimage.ubuntu.com/releases/karmic/ . If the issue remains with Karmic it would be great to then also test the latest upstream mainline kernel available. This will allow additional upstream developers to examine this issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Thanks in advance.

Revision history for this message
Boniek (boniek12p) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Changed in linux:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.