Re: bge fail on netboot of NetBSD-6 on v215 and v240

Martin Husemann <[email protected]>
Newsgroups gmane.os.netbsd.ports.sparc64
Message-ID <[email protected]>
On Wed, May 15, 2013 at 01:14:29PM +0900, Masanobu SAITOH wrote:
> >
> >  Alignment problem?


Doesn't look like it.

bge0 at pci0 dev 2 function 0: Broadcom BCM5704C Dual Gigabit Ethernet
bge0: interrupting at ivec 37c8
data error type 32 sfsr=808008 sfva=e0023040 afsr=10080005000000 afva=7f6000010$
data fault: pc=13fe2d0 addr=e0023040 sfsr=0x808008<ASI=0x80,W>
kernel trap 32: data access error

(gdb) list *(bge_attach+0x784)
0x11a51a4 is in bge_attach (../../../../dev/pci/if_bge.c:3612).
3607             * Read the hardware config word in the first 32k of NIC internal
3608             * memory, or fall back to the config word in the EEPROM.
3609             * Note: on some BCM5700 cards, this value appears to be unset.
3610             */
3611            hwcfg = hwcfg2 = hwcfg3 = hwcfg4 = 0;
3612            if (bge_readmem_ind(sc, BGE_SRAM_DATA_SIG) ==
3613                BGE_SRAM_DATA_SIG_MAGIC) {
3614                    uint32_t tmp;
3615    
3616                    hwcfg = bge_readmem_ind(sc, BGE_SRAM_DATA_CFG);

This is from a v210, dmesg for the first two bge instances is:

schizo0:  pci0 at schizo0
pci0: i/o space, memory space enabled
bge0 at pci0 dev 2 function 0: Broadcom BCM5704C Dual Gigabit Ethernet
bge0: interrupting at ivec 37c8
bge0: ASIC BCM5704 A3 (0x2003), Ethernet address 00:03:ba:45:d5:ed
brgphy0 at bge0 phy 1: BCM5704 1000BASE-T media interface, rev. 0
brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
bge1 at pci0 dev 2 function 1: Broadcom BCM5704C Dual Gigabit Ethernet
bge1: interrupting at ivec 37c9
bge1: ASIC BCM5704 A3 (0x2003), Ethernet address 00:03:ba:45:d5:ee
brgphy1 at bge1 phy 1: BCM5704 1000BASE-T media interface, rev. 0
brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto


Martin
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.