re weird bug

[Milan Obuch]

Hi,
yesterday I csup'ped my 8-current sources on my MSI Wind netbook (again) and 
tried to build new kernel. There is again a problem with re interface. It 
just does not work, with following

re0: <RealTek 8101E/8102E/8102EL PCIe 10/100baseTX> port 0xc000-0xc0ff mem 
0xffd10000-0xffd10fff,0xffd00000-0xffd0ffff irq 16 at device 0.0 on pci1
re0: Chip rev. 0x34800000
re0: MAC rev. 0x00200000
re0: PHY write failed
re0: PHY write failed
re0: MII without any phy!
device_attach: re0 attach returned 6

in dmesg. This happened already some time ago, but I did not investigate it, 
just reverted to older kernel and later it disappeared. Today I found there 
is some timing issue or racing condition - when I boot with verbose message 
logging, it works with expected

re0: <RealTek 8101E/8102E/8102EL PCIe 10/100baseTX> port 0xc000-0xc0ff mem 
0xffd10000-0xffd10fff,0xffd00000-0xffd0ffff irq 16 at device 0.0 on pci1
re0: Reserved 0x1000 bytes for rid 0x18 type 3 at 0xffd10000
re0: MSI count : 1
re0: Chip rev. 0x34800000
re0: MAC rev. 0x00200000
miibus0: <MII bus> on re0
rlphy0: <RTL8201L 10/100 media interface> PHY 1 on miibus0
rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
re0: bpf attached
re0: Ethernet address: 00:1d:92:59:f5:8b
re0: [MPSAFE]
re0: [FILTER]

So I think some issue could be in miibus or rlphy code.
I am using stripped down kernel with no interfaces, I kldload if_re (and 
miibus as dependency), if that matters.
Has anybody an idea or patch to test? Something similar appeared recently on 
list, but I would like to get issue commented first (maybe with a pointer to 
patch).

Regards,
Milan