[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709



Hi,

On Sat, Jul 17, 2021 at 08:32:42PM +0200, spi@gmxpro.de wrote:
> 
> So, did some more testing.
> 
> 1) Tried two different ports for binding interface on the 4-port-NIC:
> again kernel panic
> 
> 2) Compiled mainline 5.14-rc1 (2021-07-11) kernel from kernel.org: again
> kernel panic with either two ports on the 4-port-NIC
> 
> 
> 3) Added another 2-port-NIC into server:
> 06:01.0 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet
> Controller (Copper) (rev 03)
> 
> 06:01.1 Ethernet controller: Intel Corporation 82546EB Gigabit Ethernet
> Controller (Copper) (rev 03)
> 
> driver: e1000
> version: 7.3.21-k8-NAPI
> 
> 
> When configuring a two port bonding interface on this Intel NIC there is
> no kernel panic neither with 5.14-rc1 nor 4.19.0-17-amd64.
> 
> 
> For me it seems there is an issue with the bnx2 driver used for the
> Broadcom Limited NetXtreme II BCM5709 Gigabit Ethernet (rev 20).

So sorry to not coming back to this earlier. Now that you were able to
reproduce the very same with mainline, can you report the issue to
upstream? cripts/get_maintainer.pl would suggst the following:

Rasesh Mody <rmody@marvell.com> (supporter:BROADCOM BNX2 GIGABIT ETHERNET DRIVER)
GR-Linux-NIC-Dev@marvell.com (supporter:BROADCOM BNX2 GIGABIT ETHERNET DRIVER)
"David S. Miller" <davem@davemloft.net> (maintainer:NETWORKING DRIVERS)
Jakub Kicinski <kuba@kernel.org> (maintainer:NETWORKING DRIVERS)
Ariel Elior <aelior@marvell.com> (supporter:BROADCOM BNX2X 10 GIGABIT ETHERNET DRIVER)
Sudarsana Kalluru <skalluru@marvell.com> (supporter:BROADCOM BNX2X 10 GIGABIT ETHERNET DRIVER)
GR-everest-linux-l2@marvell.com (supporter:BROADCOM BNX2X 10 GIGABIT ETHERNET DRIVER)
netdev@vger.kernel.org (open list:BROADCOM BNX2 GIGABIT ETHERNET DRIVER)
linux-kernel@vger.kernel.org (open list)

Please keep ideally directly the Debian bug ideally in the loop.

Regards,
Salvatore


Reply to: