Re: Call for stge(4) testers

On Thu, Jul 06, 2006 at 11:52:39AM +0000, Csaba Henk wrote:
 > On 2006-07-06, Pyun YongHyeon <pyunyh_at_gmail.com> wrote:
 > > What model/maker you've got(pciconf -lv output)?
 > 
 > stge0_at_pci0:11:0:        class=0x020000 card=0x545013f0 chip=0x102113f0 rev=0x07 hdr=0x00
 >     vendor   = 'Sundance Technology Inc'
 >     class    = network
 >     subclass = ethernet
 > 
 > And this is what shows up in dmesg:
 > 
 > Jul  6 07:50:23 leavemealone kernel: stge0: <Sundance TC9021 Gigabit Ethernet> port 0xe000-0xe0ff mem 0xef000000-0xef0001ff irq 11 at device 11.0 on pci0
 > Jul  6 07:50:23 leavemealone kernel: stge0: phy read fail
 > Jul  6 07:50:23 leavemealone last message repeated 31 times
 > Jul  6 07:50:23 leavemealone kernel: miibus2: <MII bus> on stge0
 > Jul  6 07:50:23 leavemealone kernel: e1000phy0: <Marvell 88E1000 Gigabit PHY> on miibus2
 > Jul  6 07:50:23 leavemealone kernel: e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto
 > 

Since your NIC has a Marvell PHY and shows many "phy read fail"
message I have to investigate the root cause. I don't have
TC9021 NIC with Marvell PHY. So I can't sure I can fix it.

Does ifconfig(8) reports correct link speed/status?
Does "phy read fail" message shows only at device attach time?

-- 
Regards,
Pyun YongHyeon