Re: bnx(4) lockups?

[Masanobu SAITOH <msaitoh%execsw.org@localhost>]

On 2019/03/25 20:48, Stephen Borrill wrote:
> On Sat, 23 Mar 2019, Masanobu SAITOH wrote:
> > >   From my experience in bge(4), I suspect the bnx(4)'s hard hang might
> > > come from access conflict between the driver(CPU) and the embedded
> > > controller.
> >
> > One question.
> >
> > > bnx0 at pci1 dev 0 function 0: Broadcom NetXtreme II BCM5709 1000Base-T
> > > bnx0: Ethernet address 5c:f3:fc:e4:e6:78
> > > bnx0: interrupting at ioapic1 pin 4
> > > bnx0: ASIC BCM5709 C0 (0x57092003)
> > > bnx0: PCIe x2 5Gbps
> > > bnx0: Coal (RX:6,6,18,18; TX:20,20,80,80)
> > > bnx1 at pci1 dev 0 function 1: Broadcom NetXtreme II BCM5709 1000Base-T
> > > bnx1: Ethernet address 5c:f3:fc:e4:e6:7a
> > > bnx1: interrupting at ioapic1 pin 16
> > > bnx1: ASIC BCM5709 C0 (0x57092003)
> > > bnx1: PCIe x2 5Gbps
> > > bnx1: Coal (RX:6,6,18,18; TX:20,20,80,80)
> > > bnx2 at pci2 dev 0 function 0: Broadcom NetXtreme II BCM5709 1000Base-T
> > > bnx2: Ethernet address 5c:f3:fc:6b:c6:b4
> > > bnx2: interrupting at ioapic1 pin 5
> > > bnx2: ASIC BCM5709 C0 (0x57092003)
> > > bnx2: PCIe x2 5Gbps
> > > bnx2: Coal (RX:6,6,18,18; TX:20,20,80,80)
> > > bnx3 at pci2 dev 0 function 1: Broadcom NetXtreme II BCM5709 1000Base-T
> > > bnx3: Ethernet address 5c:f3:fc:6b:c6:b6
> > > bnx3: interrupting at ioapic1 pin 17
> > > bnx3: ASIC BCM5709 C0 (0x57092003)
> > > bnx3: PCIe x2 5Gbps
> > > bnx3: Coal (RX:6,6,18,18; TX:20,20,80,80)
> >
> > No MII PHYs?
>
> Sorry, missed them out.
>
> > Could you show me:
> >
> >     0) the dmesg output of the PHYs if available.
>
> All 4 are like this:
>
> bnx0 at pci1 dev 0 function 0: Broadcom NetXtreme II BCM5709 1000Base-T
> bnx0: Ethernet address 5c:f3:fc:e4:e6:78
> bnx0: interrupting at ioapic1 pin 4
> bnx0: ASIC BCM5709 C0 (0x57092003)
> bnx0: PCIe x2 5Gbps
> bnx0: Coal (RX:6,6,18,18; TX:20,20,80,80)
> brgphy0 at bnx0 phy 1: BCM5709 10/100/1000baseT PHY, rev. 8
>
> >     1) ifconfig -m
>
> bnx0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>          capabilities=3f00<IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx>
>          capabilities=3f00<UDP4CSUM_Rx,UDP4CSUM_Tx>
>          enabled=0
>          ec_capabilities=7<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU>
>          ec_enabled=0
>          address: 5c:f3:fc:e4:e6:78
>          media: Ethernet autoselect (1000baseT full-duplex)
>          status: active
>          supported Ethernet media:
>                  media none
>                  media 10baseT
>                  media 10baseT mediaopt full-duplex
>                  media 100baseTX
>                  media 100baseTX mediaopt full-duplex
>                  media 1000baseT
>                  media 1000baseT mediaopt full-duplex
>                  media autoselect
>          inet 10.4.0.11 netmask 0xffff0000 broadcast 10.4.255.255
>          inet6 fe80::5ef3:fcff:fee4:e678%bnx0 prefixlen 64 scopeid 0x1

Thanks. There is no problem in the output.

> >     2) pcictl pci0 dump -b [12] -d 0 -f [01]
>
> I only get output for -b 1 -d 0 -f 0:
>
> PCI configuration registers:
>    Common header:
>      0x00: 0x00791000 0x00100047 0x01040005 0x00000010
>
>      Vendor Name: Symbios Logic (0x1000)
>      Device Name: MegaRAID SAS2108 GEN2 (0x0079)

 It's not bnx(4) :)
 And, OK, it's not required because the device is BCM5709 C0 stepping
(P21(The chip marking's formula is different between bge and bnx)).
I have a card which has the same chip.


>      Command register: 0x0047
>        I/O space accesses: on
>        Memory space accesses: on
>        Bus mastering: on

(snip)

>      0xe0: 0x00000000 0x00000000 0x00000000 0x00000000
>      0xf0: 0x00000000 0x00000000 0x00000000 0x00000000

Back to the first mail:

> If connected to the Internet and traffic is flowing, it will lock solid after a while

Does the machine recover from the hard hang after stopping the traffic?
e.g. removing cable.

--
-----------------------------------------------
                SAITOH Masanobu (msaitoh%execsw.org@localhost
                                 msaitoh%netbsd.org@localhost)