Incorrect MAC address on card (00:00:00 in device portion)

Bug #31502 reported by Patrice Vetsel
12
Affects Status Importance Assigned to Milestone
linux-source-2.6.15 (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

On my notebook and with udev ubuntu12 my /etc/iftab contain 2 good definitions for eth0 and eth1 with their MAC adress. (eth0 wlan and eth1 for network card)
But after initialisation, eth0 is renamed eth0_clashed.
For precision the udev ubuntu8 is the last working package, meanwhile it swap eth0 and eth1 randomly.

Changed in udev:
assignee: nobody → keybuk
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Which version of udev do you have installed? These problems should be fixed in 079-0ubuntu12.

If not, please attach your /etc/iftab and /etc/network/interfaces files AND the output of "ifconfig -a"

Thanks

Changed in udev:
status: Unconfirmed → Needs Info
Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote : more informations

These problems are not fixed with udev 079-0ubuntu12.

here are iftab / ifconfig -a / interfaces

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote : Re: eth0 on wifi card is called eth0_clashed

Please provide the output of the following command:

  /lib/udev/iftab_helper eth0 00:60:B3:97:EF:FB 1

Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

output is :
eth0

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

You need to reboot after upgrading to udev 0ubuntu12

Then everything should be fine -- your configuration is behaving consistently with the bug being fixed.

Changed in udev:
status: Needs Info → Rejected
Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

Of course i'v rebooted.
But for you i re-installed a fresh system with dapper daily of 1602 (contain udev ubuntu12)

There is a problem with mac adress i attach informations.

Changed in udev:
status: Rejected → Unconfirmed
Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote : informations

ifconfig -a and iftab

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote : Re: eth0 on wifi card is called eth0_clashed

I don't understand what you're showing me here ... your card has a different MAC address to the one named in your iftab file and is clashing ... this is correct behaviour?

Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

The "real" or "good" mac adress are shown in /etc/iftab

eth0 mac 00:60:b3:97:ef:fb
eth1 mac 00:0a:e4:48:d5:dd

But as shown by "ifconfig -a" the eth0_clashed has a new/different/unknow mac adress

eth0_clas ... HWaddr 00:30:B4:00:00:00

This notebook is working like a charm since first beta of hoary. Wifi card has problem since udev 079-0ubuntu09

I wondering if you test mac adress of the wifi card after or before loading firmware ?!
It's a "Network controller: Intersil Corporation Intersil ISL3890 [Prism GT/Prism Duette] (rev 01)"

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

If the MAC address is incorrect in "ifconfig -a" output, then this isn't a udev problem; it doesn't do anything to change those.

We process the event when the kernel indicates that the network device has been added (an "add" uevent from the "network" subsystem), if the driver does this before firmware has been received (and thus before the device is useful) then this is almost certainly a driver bug.

Reassigning to the kernel.

Changed in udev:
assignee: keybuk → ubuntu-kernel-team
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Note that a temporary workaround for the user is to place the incorrect MAC address in /etc/iftab instead.

Also, if you could remove the modules that drive both network cards, run "sudo udevmonitor -e", and then load the modules again - and attach the output of that command, we can see what the state of the card is at each point of the module insertion and firmware loading.

Revision history for this message
Matthew Garrett (mjg59) wrote :

What driver is being used for this card? Prism54? It's not uncommon for drivers to load firmware when the interface is brought up, which is obviously going to be some time after it's loaded. Why it would have this bizarre address before loading is beyond me, though.

Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote : more informations

Ok.
i'v removed prism54
then run
sudo udevmonitor -e
i attach the output when i do a modprobe prism54

More informations :
i edit /etc/iftab to add the wrong/bad mac adress :

# This file assigns persistent names to network interfaces.
# See iftab(5) for syntax.
#eth0 mac 00:60:b3:97:ef:fb
eth0 mac 00:30:b4:00:00:00
eth1 mac 00:0a:e4:48:d5:dd

I do a :
sudo rmmod prism54
sudo insmod prism54

and eth0 is working. The strange part is that if i do a :
sudo ifconfig -a

eth0 Lien encap:Ethernet HWaddr 00:60:B3:97:EF:FB
...

The eth0 card have the right mac adress. This card has 2 mac adress funny not ?! ;)

Revision history for this message
sam tygier (samtygier) wrote :

also seening this on a prism54 pcmcia wireless card (netgear wg511). breezy (and the dapper installer) see the mac address as 00:09:5b:e6:4c:03, but dapper sees 00:30:B4:00:00:00.

running 2.6.15-16.23 on powerpc, installed from 20060227 nightly.

Changed in linux-source-2.6.15:
status: Unconfirmed → Confirmed
Revision history for this message
sam tygier (samtygier) wrote :

i have found that activating the card fixes the IP address.

sam@titania-d:~$ ifconfig eth3
eth3 Link encap:Ethernet HWaddr 00:30:B4: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:1000
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
          Interrupt:58

sam@titania-d:~$ sudo ifconfig eth3 up
sam@titania-d:~$ ifconfig eth3
eth3 Link encap:Ethernet HWaddr 00:09:5B:E6:4C:03
          inet6 addr: fe80::209:5bff:fee6:4c03/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b) TX bytes:238 (238.0 b)
          Interrupt:58

Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

From changelog of linux-source-2.6.15 2.6.15-20.30

   * prism54: Via mjg59:
     - Load firmware before bring up interface.
     - Add prism54 softmac driver.

So I'm waiting for this new version to test if the bug is stille here or not.

Revision history for this message
Ante Karamatić (ivoks) wrote :

And?

Revision history for this message
Ben Collins (ben-collins) wrote :

Pretty sure that patch fixes it.

Changed in linux-source-2.6.15:
status: Confirmed → Fix Released
Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

I re-open the bug.
Fresh install of Dapper-beta.
After installation i'v always the problem.
Wifi card is well detected by the installation process.
/etc/iftab contain eth0 mac 00:60:b3:97:ef:fb arp 1

but after reboot a «sudo ifconfig -a» show eth1 (my ethernet card) and wifi is eth2 with incorrect address (HWaddr 00:3D:B4:00:00:00

Changed in linux-source-2.6.15:
status: Fix Released → Confirmed
Revision history for this message
Patrice Vetsel (vetsel-patrice) wrote :

Linux 2.6.15-21 resolve that bug. Thanks

Changed in linux-source-2.6.15:
status: Confirmed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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