From mboxrd@z Thu Jan 1 00:00:00 1970 From: marty Date: Wed, 19 Aug 2009 00:26:32 +0000 Subject: duplicate MAC addresses Message-Id: <4A8B46B8.3090308@goodoldmarty.com> MIME-Version: 1 Content-Type: multipart/mixed; boundary="------------enig5578722359BE2D9CC519A51B" List-Id: References: <4A8B0E98.6030202@goodoldmarty.com> In-Reply-To: <4A8B0E98.6030202@goodoldmarty.com> To: linux-hotplug@vger.kernel.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig5578722359BE2D9CC519A51B Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Greg KH wrote: > > On Tue, Aug 18, 2009 at 04:27:04PM -0400, marty wrote: >> >> I got trouble... >> >> (duplicate MAC addresses) > > > > That's a bug in your hardware, have you asked your manufacturer to > > resolve this for you? That violates the ethernet spec... > > > > thanks, > > > > greg k-h > > ' Thanks for responding Greg, Indeed the MACs should be unique, and they ARE according to kernel. As I was only guessing can you please be a bit more specific as to 'where' you believe that problem lies? Then I can contact manufacturer with good information. Thanks so much, PS: Thanks,thanks,thanks,thanks... for the work you have done with linux. Marty B. PPS: for Matt Dharm Your email fragged my ancient email client and I had to do more work. Gaa= a... What's with that I wonder? I have enough problems right now. plaintext only, thanks... > I got trouble... > (duplicate MAC addresses) >=20 > I have a Jetway atom-330 mini-itx board with a builtin NIC and 3-NIC > daughtercard. All 4 NICS are realtek 8169. The software is recent. > The machine works impressively except for described following issues: >=20 > The builtin NIC always comes in as eth0 on boot. > The remaining daughtercard NICS have MACS from a different sequence. > On boot all 4 NICS are seen as unique by the kernel and assigned unique= > interrupts, (which is very nice). >=20 > Enter udev... >=20 > On boot udev stalls for 120+ seconds while it executes > i801_smbus functions. This may be a unsupported hardware issue > or other software issue but it is not normal. This may be the problem. >=20 > After udev finishes the "70-persistent-net.rules" are borked and eth3 i= s > assigned the MAC of eth0, causing a duplicate MAC. > On the next boot udev sees the duplicate and renames eth3 to eth3_renam= e > and the network scripts won't enable it. It becomes useless. >=20 > "ip link show" always lists eth3/eth3_rename with the MAC of eth0 as be= low. Why? >=20 > 2: eth0: mtu 1500 qdisc pfifo_fast st= ate > UNKNOWN qlen 1000 > link/ether 00:30:18:ab:4a:8f brd ff:ff:ff:ff:ff:ff > 3: eth1: mtu 1500 qdisc pfifo_fast st= ate > UNKNOWN qlen 1000 > link/ether 00:30:18:ab:6a:46 brd ff:ff:ff:ff:ff:ff > 4: eth2: mtu 1500 qdisc pfifo_fast st= ate > UNKNOWN qlen 1000 > link/ether 00:30:18:ab:6a:47 brd ff:ff:ff:ff:ff:ff > 5: eth3_rename: mtu 1500 qdisc noop state DOWN ql= en 1000 > link/ether 00:30:18:ab:4a:8f brd ff:ff:ff:ff:ff:ff >=20 > What I really don't know is: > After the kernel probes the hardware and acquires the MACs, where > does it keep that info? > Why doesn't udev use that correct probed kernel info for eth3, rather t= han > configure eth3 with the MAC of eth0? Why probe the hardware trice? > Where is this going wrong? I suspect i801_smbus... >=20 > Marty B. --=20 An artist who is forced to work a specific schedule, is no longer an artist; he is just hired help. Inspiration cannot be purchased. --------------enig5578722359BE2D9CC519A51B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFKi0bBjZr5zqVRQKIRAjW7AJ9jcgk6VgUiWYmWSWSQeaTNF6j84wCePyV0 wPHq49+44dwWl8D/KRo++QM= =lJPK -----END PGP SIGNATURE----- --------------enig5578722359BE2D9CC519A51B--