Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

bge0: EEPROM read timed

107 views
Skip to first unread message

pluknet

unread,
Mar 16, 2009, 6:37:54 AM3/16/09
to
Hi.

I got this on today's RELENG_6 with Broadcom BCM5722 A0, ASIC rev. 0xa200.

>From dmesg (bge related):

bge0: <Broadcom BCM5722 A0, ASIC rev. 0xa200> mem
0xe8400000-0xe840ffff irq 16 at device 0.0 on pci2
bge0: firmware handshake timed out, found 0x4b657654
bge0: firmware handshake timed out, found 0x4b657654
bge0: EEPROM read timed out
bge0: failed to read EEPROM
device_attach: bge0 attach returned 6
bge1: <Broadcom BCM5703 B0, ASIC rev. 0x1100> mem
0xe8600000-0xe860ffff irq 21 at device 1.0 on pci3
miibus0: <MII bus> on bge1
brgphy0: <BCM5703 10/100/1000baseTX PHY> on miibus0
brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto
bge1: Ethernet address: 00:21:5e:4d:05:c8


any hints?

P.S. I see EEPROM timeout fixes were already merged to RELENG_6 (I
have post-fix version certainly).
May that issue be somehow related?

--
wbr,
pluknet
_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"

pluknet

unread,
Mar 16, 2009, 8:09:21 AM3/16/09
to
2009/3/16 pluknet <plu...@gmail.com>:
> Hi.
>
> I got this on today's RELENG_6 with Broadcom BCM5722 A0, ASIC rev. 0xa200=

.
>
> From dmesg (bge related):
>
> bge0: <Broadcom BCM5722 A0, ASIC rev. 0xa200> mem
> 0xe8400000-0xe840ffff irq 16 at device 0.0 on pci2
> bge0: firmware handshake timed out, found 0x4b657654
> bge0: firmware handshake timed out, found 0x4b657654
> bge0: EEPROM read timed out
> bge0: failed to read EEPROM
> device_attach: bge0 attach returned 6
> bge1: <Broadcom BCM5703 B0, ASIC rev. 0x1100> mem
> 0xe8600000-0xe860ffff irq 21 at device 1.0 on pci3
> miibus0: <MII bus> on bge1
> brgphy0: <BCM5703 10/100/1000baseTX PHY> on miibus0
> brgphy0: =A010baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,

> 1000baseT-FDX, auto
> bge1: Ethernet address: 00:21:5e:4d:05:c8
>
>
> any hints?
>
> P.S. I see EEPROM timeout fixes were already merged to RELENG_6 (I
> have post-fix version certainly).
> May that issue be somehow related?
>

I guess it's a regression. Below are my speculations.

I tried to build on 6.2-R the bge(4) sources checked from later RELENG_6
just after BCM5722 support (from if_bgereg.h 1.36.2.11/ if_bge.c1.91.2.26)
in order to backport BCM5722 support into 6.2-R. After some tweaks it
was built, so..

What I got in dmesg (after native statically built bge(4) replacement
in boot loader prompt) is:
FreeBSD 6.2-RELEASE-p8 #13: Thu Feb 19 14:52:30 MSK 2009
[..snip..]
bgex0: <Broadcom BCM5722 A0, ASIC rev. 0xa200> mem


0xe8400000-0xe840ffff irq 16 at device 0.0 on pci2

bgex0: Ethernet address: 00:21:5e:4d:05:c7

Whoohoo..

So, here it even reached macaddr designation. (and going to panic at
nfs boot time (probably
to different locking scheme between 6.2 and 6.4, but it's an another story)=
).


--=20

John Baldwin

unread,
Mar 18, 2009, 2:11:15 PM3/18/09
to
On Monday 16 March 2009 8:08:26 am pluknet wrote:
> 2009/3/16 pluknet <plu...@gmail.com>:
> > Hi.
> >
> > I got this on today's RELENG_6 with Broadcom BCM5722 A0, ASIC rev. 0xa2=
00.

> >
> > From dmesg (bge related):
> >
> > bge0: <Broadcom BCM5722 A0, ASIC rev. 0xa200> mem
> > 0xe8400000-0xe840ffff irq 16 at device 0.0 on pci2
> > bge0: firmware handshake timed out, found 0x4b657654
> > bge0: firmware handshake timed out, found 0x4b657654
> > bge0: EEPROM read timed out
> > bge0: failed to read EEPROM
> > device_attach: bge0 attach returned 6
> > bge1: <Broadcom BCM5703 B0, ASIC rev. 0x1100> mem
> > 0xe8600000-0xe860ffff irq 21 at device 1.0 on pci3
> > miibus0: <MII bus> on bge1
> > brgphy0: <BCM5703 10/100/1000baseTX PHY> on miibus0
> > brgphy0: =A010baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> > 1000baseT-FDX, auto
> > bge1: Ethernet address: 00:21:5e:4d:05:c8
> >
> >
> > any hints?
> >
> > P.S. I see EEPROM timeout fixes were already merged to RELENG_6 (I
> > have post-fix version certainly).
> > May that issue be somehow related?
> >
>=20

> I guess it's a regression. Below are my speculations.
>=20

> I tried to build on 6.2-R the bge(4) sources checked from later RELENG_6
> just after BCM5722 support (from if_bgereg.h 1.36.2.11/ if_bge.c1.91.2.26)
> in order to backport BCM5722 support into 6.2-R. After some tweaks it
> was built, so..

Can you further narrow down where the regression occurs?

=2D-=20
John Baldwin

pluknet

unread,
Mar 18, 2009, 3:41:58 PM3/18/09
to
2009/3/18 John Baldwin <j...@freebsd.org>:

> On Monday 16 March 2009 8:08:26 am pluknet wrote:
>> 2009/3/16 pluknet <plu...@gmail.com>:
>> > Hi.
>> >
>> > I got this on today's RELENG_6 with Broadcom BCM5722 A0, ASIC rev. 0xa200.

>> >
>> > From dmesg (bge related):
>> >
>> > bge0: <Broadcom BCM5722 A0, ASIC rev. 0xa200> mem
>> > 0xe8400000-0xe840ffff irq 16 at device 0.0 on pci2
>> > bge0: firmware handshake timed out, found 0x4b657654
>> > bge0: firmware handshake timed out, found 0x4b657654
>> > bge0: EEPROM read timed out
>> > bge0: failed to read EEPROM
>> > device_attach: bge0 attach returned 6
>> > bge1: <Broadcom BCM5703 B0, ASIC rev. 0x1100> mem
>> > 0xe8600000-0xe860ffff irq 21 at device 1.0 on pci3
>> > miibus0: <MII bus> on bge1
>> > brgphy0: <BCM5703 10/100/1000baseTX PHY> on miibus0
>> > brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,

>> > 1000baseT-FDX, auto
>> > bge1: Ethernet address: 00:21:5e:4d:05:c8
>> >
>> >
>> > any hints?
>> >
>> > P.S. I see EEPROM timeout fixes were already merged to RELENG_6 (I
>> > have post-fix version certainly).
>> > May that issue be somehow related?
>> >
>>
>> I guess it's a regression. Below are my speculations.
>>
>> I tried to build on 6.2-R the bge(4) sources checked from later RELENG_6
>> just after BCM5722 support (from if_bgereg.h 1.36.2.11/ if_bge.c1.91.2.26)
>> in order to backport BCM5722 support into 6.2-R. After some tweaks it
>> was built, so..
>
> Can you further narrow down where the regression occurs?

I'm sorry, John. Today we moved to native 7.1-R installed from CD.
I can only confirm now that there is no any visible problems now.

bge0: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev.


0xa200> mem 0xe8400000-0xe840ffff irq 16 at device 0.0 on pci2

miibus0: <MII bus> on bge0
brgphy0: <BCM5722 10/100/1000baseTX PHY> PHY 1 on miibus0
brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto
bge0: Ethernet address: 00:21:5e:4d:05:c7
bge0: [ITHREAD]
bge1: <Broadcom NetXtreme Gigabit Ethernet Controller, ASIC rev.


0x1100> mem 0xe8600000-0xe860ffff irq 21 at device 1.0 on pci3

miibus1: <MII bus> on bge1
brgphy1: <BCM5703 10/100/1000baseTX PHY> PHY 1 on miibus1
brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,


1000baseT-FDX, auto
bge1: Ethernet address: 00:21:5e:4d:05:c8

bge1: [ITHREAD]
bge0: link state changed to UP
bge1: link state changed to UP

[root@ ~]# sysctl -a | grep bge
hw.bge.allow_asf: 0
dev.bge.0.%desc: Broadcom NetXtreme Gigabit Ethernet Controller, ASIC
rev. 0xa200
dev.bge.0.%driver: bge
dev.bge.0.%location: slot=0 function=0 handle=\_SB_.PCI0.EXP5.PXS5
dev.bge.0.%pnpinfo: vendor=0x14e4 device=0x165a subvendor=0x1014
subdevice=0x0378 class=0x020000
dev.bge.0.%parent: pci2
dev.bge.1.%desc: Broadcom NetXtreme Gigabit Ethernet Controller, ASIC
rev. 0x1100
dev.bge.1.%driver: bge
dev.bge.1.%location: slot=1 function=0
dev.bge.1.%pnpinfo: vendor=0x14e4 device=0x16c7 subvendor=0x1014
subdevice=0x026f class=0x020000
dev.bge.1.%parent: pci3
dev.bge.1.stats.FramesDroppedDueToFilters: 0
dev.bge.1.stats.DmaWriteQueueFull: 0
dev.bge.1.stats.DmaWriteHighPriQueueFull: 0
dev.bge.1.stats.NoMoreRxBDs: 0
dev.bge.1.stats.InputDiscards: 0
dev.bge.1.stats.InputErrors: 0
dev.bge.1.stats.RecvThresholdHit: 15574
dev.bge.1.stats.DmaReadQueueFull: 0
dev.bge.1.stats.DmaReadHighPriQueueFull: 0
dev.bge.1.stats.SendDataCompQueueFull: 0
dev.bge.1.stats.RingSetSendProdIndex: 0
dev.bge.1.stats.RingStatusUpdate: 15604
dev.bge.1.stats.Interrupts: 15604
dev.bge.1.stats.AvoidedInterrupts: 0
dev.bge.1.stats.SendThresholdHit: 0
dev.bge.1.stats.rx.Octets: 3478478
dev.bge.1.stats.rx.Fragments: 0
dev.bge.1.stats.rx.UcastPkts: 0
dev.bge.1.stats.rx.MulticastPkts: 0
dev.bge.1.stats.rx.FCSErrors: 0
dev.bge.1.stats.rx.AlignmentErrors: 0
dev.bge.1.stats.rx.xonPauseFramesReceived: 0
dev.bge.1.stats.rx.xoffPauseFramesReceived: 0
dev.bge.1.stats.rx.ControlFramesReceived: 0
dev.bge.1.stats.rx.xoffStateEntered: 0
dev.bge.1.stats.rx.FramesTooLong: 0
dev.bge.1.stats.rx.Jabbers: 0
dev.bge.1.stats.rx.UndersizePkts: 0
dev.bge.1.stats.rx.inRangeLengthError: 0
dev.bge.1.stats.rx.outRangeLengthError: 0
dev.bge.1.stats.tx.Octets: 0
dev.bge.1.stats.tx.Collisions: 0
dev.bge.1.stats.tx.XonSent: 0
dev.bge.1.stats.tx.XoffSent: 0
dev.bge.1.stats.tx.flowControlDone: 0
dev.bge.1.stats.tx.InternalMacTransmitErrors: 0
dev.bge.1.stats.tx.SingleCollisionFrames: 0
dev.bge.1.stats.tx.MultipleCollisionFrames: 0
dev.bge.1.stats.tx.DeferredTransmissions: 0
dev.bge.1.stats.tx.ExcessiveCollisions: 0
dev.bge.1.stats.tx.LateCollisions: 0
dev.bge.1.stats.tx.UcastPkts: 0
dev.bge.1.stats.tx.MulticastPkts: 0
dev.bge.1.stats.tx.BroadcastPkts: 0
dev.bge.1.stats.tx.CarrierSenseErrors: 0
dev.bge.1.stats.tx.Discards: 0
dev.bge.1.stats.tx.Errors: 0
dev.miibus.0.%parent: bge0
dev.miibus.1.%parent: bge1


FreeBSD 7.1-RELEASE

--
wbr,
pluknet

0 new messages