kern/45241: jme ethernet driver unable to read link layer address from controller

[emmanuel%libera.cc@localhost]

>Number:         45241
>Category:       kern
>Synopsis:       jme ethernet driver unable to read link layer address from 
>controller
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Aug 11 08:20:00 +0000 2011
>Originator:     Emmanuel Kasper
>Release:        5.1
>Organization:
>Environment:
NetBSD netbook.libera.cc 5.1 NetBSD 5.1 (GENERIC) #0: Sun Nov  7 14:39:56 UTC 
2010  
builds%b6.netbsd.org@localhost:/home/builds/ab/netbsd-5-1-RELEASE/i386/201011061943Z-obj/home/builds/ab/netbsd-5-1-RELEASE/src/sys/arch/i386/compile/GENERIC
 i386
>Description:
At boot time, the NetBSD is unable to read the mac adress from my Jmicron 
ethernet card.

/home/manu $ dmesg | grep jme 
jme0 at pci1 dev 0 function 5
jme0: JMicron JMC260 Gigabit Ethernet Controller
jme0: PCI device revision : 0x2, Chip revision: 0x22
jme0: error reading Ethernet address
jme0: Ethernet address 00:00:00:00:00:00
jme0: interrupting at ioapic0 pin 16
ukphy0 at jme0 phy 1: Generic IEEE 802.3u media interface

This prevents out-of-the box TPC/IP networking from functionning on this 
interface as you may guess ...

As I have on this machine a FAST ethernet controller, and not a GIGABIT 
ethernet controller, I am wondering if the root problem is not a wrongly 
detected controller.

/home/manu $ dmesg | grep ukphy       
ukphy0 at jme0 phy 1: Generic IEEE 802.3u media interface
ukphy0: OUI 0x00d831, model 0x0022, rev. 1
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

FWIW the controlle works properly with Linux 2.6.38.



>How-To-Repeat:
reboot
dmesg | grep jme0
>Fix:
Adding manually an link adress with
ifconfig jme0 link 00:11:22:33:44:55 active
fixes the problem