lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20101114105844.5f708321@nehalam>
Date:	Sun, 14 Nov 2010 10:58:44 -0800
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Guillaume Leclanche <guillaume@...lanche.net>
Cc:	netdev@...r.kernel.org
Subject: Re: sky2 for on-board 88e8055 fails to detect mac address

On Sun, 14 Nov 2010 12:42:06 +0100
Guillaume Leclanche <guillaume@...lanche.net> wrote:

> Hello,
> 
> I use a "Marvell Technology Group Ltd. 88E8055 PCI-E Gigabit Ethernet
> Controller".
> It seems that the sky2 module doesn't manage to grab the mac address
> from the HW :
> 
> [    0.741173] sky2: driver version 1.28
> [    0.741206] sky2 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
> [    0.741216] sky2 0000:02:00.0: setting latency timer to 64
> [    0.741244] sky2 0000:02:00.0: Yukon-2 EC Ultra chip revision 2
> [    0.741339] sky2 0000:02:00.0: irq 44 for MSI/MSI-X
> [    0.744781] sky2 0000:02:00.0: eth0: addr 00:00:00:00:00:00
> 
> Of course I can set the mac address manually with "ip link set eth0
> addr ..." (and then it works fine) but I guess that's not the normal
> behavior from the driver?
> 
> I'd be happy to troubleshoot but I'm not very used to kernel
> internals, so tell me if you need some output.
> Below a few targeted info about my system.
> 
> Guillaume
> 
> 2.6.35-22-generic #35-Ubuntu SMP Sat Oct 16 20:36:48 UTC 2010 i686 GNU/Linux
> 
> 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055
> PCI-E Gigabit Ethernet Controller
> 	Subsystem: Marvell Technology Group Ltd. 88E8055 PCI-E Gigabit
> Ethernet Controller
> 	Flags: bus master, fast devsel, latency 0, IRQ 44
> 	Memory at fe8fc000 (64-bit, non-prefetchable) [size=16K]
> 	I/O ports at a800 [size=256]
> 	Expansion ROM at fe8c0000 [disabled] [size=128K]
> 	Capabilities: [48] Power Management version 3
> 	Capabilities: [50] Vital Product Data
> 	Capabilities: [5c] MSI: Enable+ Count=1/1 Maskable- 64bit+
> 	Capabilities: [e0] Express Legacy Endpoint, MSI 00
> 	Capabilities: [100] Advanced Error Reporting
> 	Kernel driver in use: sky2
> 	Kernel modules: sky2

The driver reads the MAC address from EEPROM.
There are a couple of possibilities:
1. The driver could have problem when reading the value because of a timing issue.
   BUT I doubt that because when that happens the driver would see ff:ff:ff:ff:ff:ff
2. The BIOS is screwing it up on boot.
   Did you enable the device in the BIOS?
3. The vendor screwed up and didn't program the address into the hardware.

It doesn't look like a kernel/driver problem at all.



--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ