no network connection after reboot - be2net: FW not responding

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
0
down vote

favorite












I'm using an AMD Threadripper 1920X running on a Gigabyte Designare X399 motherboard. Furthermore it has an Emulex OneConnect 10Gb NIC. This NIC works fine until I reboot my computer: The boot process then takes longer than usual and the Interface comes up, receives its static IP address from Network Manager but is not able send/receive network traffic. If I grep in syslog for be2net, this is the out, the error comes on the end:



May 15 09:55:15 workstation kernel: [ 1.057712] be2net 0000:07:00.0: be2net version is 11.4.0.0
May 15 09:55:15 workstation kernel: [ 1.058031] be2net 0000:07:00.0: PCIe error reporting enabled
May 15 09:55:15 workstation kernel: [ 1.404059] be2net 0000:07:00.0: FW config: function_mode=0x3, function_caps=0x7
May 15 09:55:15 workstation kernel: [ 1.544087] be2net 0000:07:00.0: Max: txqs 1, rxqs 5, rss 4, eqs 16, vfs 0
May 15 09:55:15 workstation kernel: [ 1.544089] be2net 0000:07:00.0: Max: uc-macs 30, mc-macs 64, vlans 64
May 15 09:55:15 workstation kernel: [ 1.544133] be2net 0000:07:00.0: enabled 1 MSI-x vector(s) for NIC
May 15 09:55:15 workstation kernel: [ 1.688095] be2net 0000:07:00.0: created 1 TX queue(s)
May 15 09:55:15 workstation kernel: [ 1.712087] be2net 0000:07:00.0: created 1 RX queue(s)
May 15 09:55:15 workstation kernel: [ 1.799038] be2net 0000:07:00.0: FW version is 4.9.416.2
May 15 09:55:15 workstation kernel: [ 1.805191] be2net 0000:07:00.0: HW Flow control - TX:1 RX:1
May 15 09:55:15 workstation kernel: [ 1.813392] be2net 0000:07:00.0: Adapter does not support HW error recovery
May 15 09:55:15 workstation kernel: [ 1.813522] be2net 0000:07:00.0: Emulex OneConnect: PF port 1
May 15 09:55:15 workstation kernel: [ 1.813595] be2net 0000:07:00.1: be2net version is 11.4.0.0
May 15 09:55:15 workstation kernel: [ 1.813855] be2net 0000:07:00.1: PCIe error reporting enabled
May 15 09:55:15 workstation kernel: [ 2.064095] be2net 0000:07:00.1: FW config: function_mode=0x3, function_caps=0x7
May 15 09:55:15 workstation kernel: [ 2.188096] be2net 0000:07:00.1: Max: txqs 1, rxqs 5, rss 4, eqs 16, vfs 0
May 15 09:55:15 workstation kernel: [ 2.188098] be2net 0000:07:00.1: Max: uc-macs 30, mc-macs 64, vlans 64
May 15 09:55:15 workstation kernel: [ 2.188148] be2net 0000:07:00.1: enabled 1 MSI-x vector(s) for NIC
May 15 09:55:15 workstation kernel: [ 2.296098] be2net 0000:07:00.1: created 1 TX queue(s)
May 15 09:55:15 workstation kernel: [ 2.320099] be2net 0000:07:00.1: created 1 RX queue(s)
May 15 09:55:15 workstation kernel: [ 2.430614] be2net 0000:07:00.1: FW version is 4.9.416.2
May 15 09:55:15 workstation kernel: [ 2.437790] be2net 0000:07:00.1: HW Flow control - TX:1 RX:1
May 15 09:55:15 workstation kernel: [ 2.445992] be2net 0000:07:00.1: Adapter does not support HW error recovery
May 15 09:55:15 workstation kernel: [ 2.446111] be2net 0000:07:00.1: Emulex OneConnect: PF port 2
May 15 09:55:15 workstation kernel: [ 2.447419] be2net 0000:07:00.0 enp7s0f0: renamed from eth0
May 15 09:55:15 workstation kernel: [ 2.464282] be2net 0000:07:00.1 enp7s0f1: renamed from eth1
May 15 09:55:15 workstation sensors[1628]: be2net-pci-0700
May 15 09:55:15 workstation sensors[1628]: be2net-pci-0701
May 15 09:55:16 workstation kernel: [ 10.483582] be2net 0000:07:00.0 enp7s0f0: Link is Up
May 15 09:55:16 workstation kernel: [ 10.502938] be2net 0000:07:00.0 enp7s0f0: Link is Up
May 15 09:55:16 workstation kernel: [ 10.573081] be2net 0000:07:00.1 enp7s0f1: Link is Down
May 15 09:55:16 workstation kernel: [ 10.594631] be2net 0000:07:00.1 enp7s0f1: Link is Down
May 15 09:57:04 workstation kernel: [ 118.627524] be2net 0000:07:00.1: FW not responding
May 15 09:57:04 workstation kernel: [ 118.627530] be2net 0000:07:00.1: enp7s0f1: Link down
May 15 09:57:04 workstation kernel: [ 118.678167] be2net 0000:07:00.1: did not receive flush compl
May 15 09:58:01 workstation kernel: [ 176.252105] be2net 0000:07:00.0: FW not responding
May 15 09:58:01 workstation kernel: [ 176.252113] be2net 0000:07:00.0: enp7s0f0: Link down
May 15 09:58:01 workstation kernel: [ 176.262246] be2net 0000:07:00.0: txq0: cleaning 318 pending tx-wrbs
May 15 09:58:01 workstation kernel: [ 176.313025] be2net 0000:07:00.0: did not receive flush compl
May 15 09:58:11 workstation kernel: [ 186.333781] be2net 0000:07:00.0: be2net version is 11.4.0.0


I've found this page from 2015, where someone states, that be2net breaks when dma_alloc_coherent memory is not zeroed out. This seems to match my observations, as the memory contains no data upon a fresh start from powered off, while a restart not clears my RAM and so the driver has data in the memory received from the kernel, exposes it to the card and the cards firmware crashes.



Furthermore it somehow seems related to IOMMU. So I tried differend kernel parameters without success:



iommu=fullflush amd_iommu=fullflush disable_ddw


I hope some has an idea, what I can do to fix this. I've tried zeroing out my RAM with "sdmem -ll" on shutdown, but the driver memory is allocaed on such a low level, that I cannot zero it that way.




networking drivers kernel firmware




share|improve this question




















  • In case an administrator sees this: Can you please move this thread to Server Fault? Maybe I got higher chances for an answer there because it is somehow related to enterprise networking hardware/driver. Thank you
    – Oliver R.
    May 18 at 11:11














up vote
0
down vote

favorite












I'm using an AMD Threadripper 1920X running on a Gigabyte Designare X399 motherboard. Furthermore it has an Emulex OneConnect 10Gb NIC. This NIC works fine until I reboot my computer: The boot process then takes longer than usual and the Interface comes up, receives its static IP address from Network Manager but is not able send/receive network traffic. If I grep in syslog for be2net, this is the out, the error comes on the end:



May 15 09:55:15 workstation kernel: [ 1.057712] be2net 0000:07:00.0: be2net version is 11.4.0.0
May 15 09:55:15 workstation kernel: [ 1.058031] be2net 0000:07:00.0: PCIe error reporting enabled
May 15 09:55:15 workstation kernel: [ 1.404059] be2net 0000:07:00.0: FW config: function_mode=0x3, function_caps=0x7
May 15 09:55:15 workstation kernel: [ 1.544087] be2net 0000:07:00.0: Max: txqs 1, rxqs 5, rss 4, eqs 16, vfs 0
May 15 09:55:15 workstation kernel: [ 1.544089] be2net 0000:07:00.0: Max: uc-macs 30, mc-macs 64, vlans 64
May 15 09:55:15 workstation kernel: [ 1.544133] be2net 0000:07:00.0: enabled 1 MSI-x vector(s) for NIC
May 15 09:55:15 workstation kernel: [ 1.688095] be2net 0000:07:00.0: created 1 TX queue(s)
May 15 09:55:15 workstation kernel: [ 1.712087] be2net 0000:07:00.0: created 1 RX queue(s)
May 15 09:55:15 workstation kernel: [ 1.799038] be2net 0000:07:00.0: FW version is 4.9.416.2
May 15 09:55:15 workstation kernel: [ 1.805191] be2net 0000:07:00.0: HW Flow control - TX:1 RX:1
May 15 09:55:15 workstation kernel: [ 1.813392] be2net 0000:07:00.0: Adapter does not support HW error recovery
May 15 09:55:15 workstation kernel: [ 1.813522] be2net 0000:07:00.0: Emulex OneConnect: PF port 1
May 15 09:55:15 workstation kernel: [ 1.813595] be2net 0000:07:00.1: be2net version is 11.4.0.0
May 15 09:55:15 workstation kernel: [ 1.813855] be2net 0000:07:00.1: PCIe error reporting enabled
May 15 09:55:15 workstation kernel: [ 2.064095] be2net 0000:07:00.1: FW config: function_mode=0x3, function_caps=0x7
May 15 09:55:15 workstation kernel: [ 2.188096] be2net 0000:07:00.1: Max: txqs 1, rxqs 5, rss 4, eqs 16, vfs 0
May 15 09:55:15 workstation kernel: [ 2.188098] be2net 0000:07:00.1: Max: uc-macs 30, mc-macs 64, vlans 64
May 15 09:55:15 workstation kernel: [ 2.188148] be2net 0000:07:00.1: enabled 1 MSI-x vector(s) for NIC
May 15 09:55:15 workstation kernel: [ 2.296098] be2net 0000:07:00.1: created 1 TX queue(s)
May 15 09:55:15 workstation kernel: [ 2.320099] be2net 0000:07:00.1: created 1 RX queue(s)
May 15 09:55:15 workstation kernel: [ 2.430614] be2net 0000:07:00.1: FW version is 4.9.416.2
May 15 09:55:15 workstation kernel: [ 2.437790] be2net 0000:07:00.1: HW Flow control - TX:1 RX:1
May 15 09:55:15 workstation kernel: [ 2.445992] be2net 0000:07:00.1: Adapter does not support HW error recovery
May 15 09:55:15 workstation kernel: [ 2.446111] be2net 0000:07:00.1: Emulex OneConnect: PF port 2
May 15 09:55:15 workstation kernel: [ 2.447419] be2net 0000:07:00.0 enp7s0f0: renamed from eth0
May 15 09:55:15 workstation kernel: [ 2.464282] be2net 0000:07:00.1 enp7s0f1: renamed from eth1
May 15 09:55:15 workstation sensors[1628]: be2net-pci-0700
May 15 09:55:15 workstation sensors[1628]: be2net-pci-0701
May 15 09:55:16 workstation kernel: [ 10.483582] be2net 0000:07:00.0 enp7s0f0: Link is Up
May 15 09:55:16 workstation kernel: [ 10.502938] be2net 0000:07:00.0 enp7s0f0: Link is Up
May 15 09:55:16 workstation kernel: [ 10.573081] be2net 0000:07:00.1 enp7s0f1: Link is Down
May 15 09:55:16 workstation kernel: [ 10.594631] be2net 0000:07:00.1 enp7s0f1: Link is Down
May 15 09:57:04 workstation kernel: [ 118.627524] be2net 0000:07:00.1: FW not responding
May 15 09:57:04 workstation kernel: [ 118.627530] be2net 0000:07:00.1: enp7s0f1: Link down
May 15 09:57:04 workstation kernel: [ 118.678167] be2net 0000:07:00.1: did not receive flush compl
May 15 09:58:01 workstation kernel: [ 176.252105] be2net 0000:07:00.0: FW not responding
May 15 09:58:01 workstation kernel: [ 176.252113] be2net 0000:07:00.0: enp7s0f0: Link down
May 15 09:58:01 workstation kernel: [ 176.262246] be2net 0000:07:00.0: txq0: cleaning 318 pending tx-wrbs
May 15 09:58:01 workstation kernel: [ 176.313025] be2net 0000:07:00.0: did not receive flush compl
May 15 09:58:11 workstation kernel: [ 186.333781] be2net 0000:07:00.0: be2net version is 11.4.0.0


I've found this page from 2015, where someone states, that be2net breaks when dma_alloc_coherent memory is not zeroed out. This seems to match my observations, as the memory contains no data upon a fresh start from powered off, while a restart not clears my RAM and so the driver has data in the memory received from the kernel, exposes it to the card and the cards firmware crashes.



Furthermore it somehow seems related to IOMMU. So I tried differend kernel parameters without success:



iommu=fullflush amd_iommu=fullflush disable_ddw


I hope some has an idea, what I can do to fix this. I've tried zeroing out my RAM with "sdmem -ll" on shutdown, but the driver memory is allocaed on such a low level, that I cannot zero it that way.




networking drivers kernel firmware




share|improve this question




















  • In case an administrator sees this: Can you please move this thread to Server Fault? Maybe I got higher chances for an answer there because it is somehow related to enterprise networking hardware/driver. Thank you
    – Oliver R.
    May 18 at 11:11












up vote
0
down vote

favorite









up vote
0
down vote

favorite











I'm using an AMD Threadripper 1920X running on a Gigabyte Designare X399 motherboard. Furthermore it has an Emulex OneConnect 10Gb NIC. This NIC works fine until I reboot my computer: The boot process then takes longer than usual and the Interface comes up, receives its static IP address from Network Manager but is not able send/receive network traffic. If I grep in syslog for be2net, this is the out, the error comes on the end:



May 15 09:55:15 workstation kernel: [ 1.057712] be2net 0000:07:00.0: be2net version is 11.4.0.0
May 15 09:55:15 workstation kernel: [ 1.058031] be2net 0000:07:00.0: PCIe error reporting enabled
May 15 09:55:15 workstation kernel: [ 1.404059] be2net 0000:07:00.0: FW config: function_mode=0x3, function_caps=0x7
May 15 09:55:15 workstation kernel: [ 1.544087] be2net 0000:07:00.0: Max: txqs 1, rxqs 5, rss 4, eqs 16, vfs 0
May 15 09:55:15 workstation kernel: [ 1.544089] be2net 0000:07:00.0: Max: uc-macs 30, mc-macs 64, vlans 64
May 15 09:55:15 workstation kernel: [ 1.544133] be2net 0000:07:00.0: enabled 1 MSI-x vector(s) for NIC
May 15 09:55:15 workstation kernel: [ 1.688095] be2net 0000:07:00.0: created 1 TX queue(s)
May 15 09:55:15 workstation kernel: [ 1.712087] be2net 0000:07:00.0: created 1 RX queue(s)
May 15 09:55:15 workstation kernel: [ 1.799038] be2net 0000:07:00.0: FW version is 4.9.416.2
May 15 09:55:15 workstation kernel: [ 1.805191] be2net 0000:07:00.0: HW Flow control - TX:1 RX:1
May 15 09:55:15 workstation kernel: [ 1.813392] be2net 0000:07:00.0: Adapter does not support HW error recovery
May 15 09:55:15 workstation kernel: [ 1.813522] be2net 0000:07:00.0: Emulex OneConnect: PF port 1
May 15 09:55:15 workstation kernel: [ 1.813595] be2net 0000:07:00.1: be2net version is 11.4.0.0
May 15 09:55:15 workstation kernel: [ 1.813855] be2net 0000:07:00.1: PCIe error reporting enabled
May 15 09:55:15 workstation kernel: [ 2.064095] be2net 0000:07:00.1: FW config: function_mode=0x3, function_caps=0x7
May 15 09:55:15 workstation kernel: [ 2.188096] be2net 0000:07:00.1: Max: txqs 1, rxqs 5, rss 4, eqs 16, vfs 0
May 15 09:55:15 workstation kernel: [ 2.188098] be2net 0000:07:00.1: Max: uc-macs 30, mc-macs 64, vlans 64
May 15 09:55:15 workstation kernel: [ 2.188148] be2net 0000:07:00.1: enabled 1 MSI-x vector(s) for NIC
May 15 09:55:15 workstation kernel: [ 2.296098] be2net 0000:07:00.1: created 1 TX queue(s)
May 15 09:55:15 workstation kernel: [ 2.320099] be2net 0000:07:00.1: created 1 RX queue(s)
May 15 09:55:15 workstation kernel: [ 2.430614] be2net 0000:07:00.1: FW version is 4.9.416.2
May 15 09:55:15 workstation kernel: [ 2.437790] be2net 0000:07:00.1: HW Flow control - TX:1 RX:1
May 15 09:55:15 workstation kernel: [ 2.445992] be2net 0000:07:00.1: Adapter does not support HW error recovery
May 15 09:55:15 workstation kernel: [ 2.446111] be2net 0000:07:00.1: Emulex OneConnect: PF port 2
May 15 09:55:15 workstation kernel: [ 2.447419] be2net 0000:07:00.0 enp7s0f0: renamed from eth0
May 15 09:55:15 workstation kernel: [ 2.464282] be2net 0000:07:00.1 enp7s0f1: renamed from eth1
May 15 09:55:15 workstation sensors[1628]: be2net-pci-0700
May 15 09:55:15 workstation sensors[1628]: be2net-pci-0701
May 15 09:55:16 workstation kernel: [ 10.483582] be2net 0000:07:00.0 enp7s0f0: Link is Up
May 15 09:55:16 workstation kernel: [ 10.502938] be2net 0000:07:00.0 enp7s0f0: Link is Up
May 15 09:55:16 workstation kernel: [ 10.573081] be2net 0000:07:00.1 enp7s0f1: Link is Down
May 15 09:55:16 workstation kernel: [ 10.594631] be2net 0000:07:00.1 enp7s0f1: Link is Down
May 15 09:57:04 workstation kernel: [ 118.627524] be2net 0000:07:00.1: FW not responding
May 15 09:57:04 workstation kernel: [ 118.627530] be2net 0000:07:00.1: enp7s0f1: Link down
May 15 09:57:04 workstation kernel: [ 118.678167] be2net 0000:07:00.1: did not receive flush compl
May 15 09:58:01 workstation kernel: [ 176.252105] be2net 0000:07:00.0: FW not responding
May 15 09:58:01 workstation kernel: [ 176.252113] be2net 0000:07:00.0: enp7s0f0: Link down
May 15 09:58:01 workstation kernel: [ 176.262246] be2net 0000:07:00.0: txq0: cleaning 318 pending tx-wrbs
May 15 09:58:01 workstation kernel: [ 176.313025] be2net 0000:07:00.0: did not receive flush compl
May 15 09:58:11 workstation kernel: [ 186.333781] be2net 0000:07:00.0: be2net version is 11.4.0.0


I've found this page from 2015, where someone states, that be2net breaks when dma_alloc_coherent memory is not zeroed out. This seems to match my observations, as the memory contains no data upon a fresh start from powered off, while a restart not clears my RAM and so the driver has data in the memory received from the kernel, exposes it to the card and the cards firmware crashes.



Furthermore it somehow seems related to IOMMU. So I tried differend kernel parameters without success:



iommu=fullflush amd_iommu=fullflush disable_ddw


I hope some has an idea, what I can do to fix this. I've tried zeroing out my RAM with "sdmem -ll" on shutdown, but the driver memory is allocaed on such a low level, that I cannot zero it that way.




networking drivers kernel firmware




share|improve this question












I'm using an AMD Threadripper 1920X running on a Gigabyte Designare X399 motherboard. Furthermore it has an Emulex OneConnect 10Gb NIC. This NIC works fine until I reboot my computer: The boot process then takes longer than usual and the Interface comes up, receives its static IP address from Network Manager but is not able send/receive network traffic. If I grep in syslog for be2net, this is the out, the error comes on the end:



May 15 09:55:15 workstation kernel: [ 1.057712] be2net 0000:07:00.0: be2net version is 11.4.0.0
May 15 09:55:15 workstation kernel: [ 1.058031] be2net 0000:07:00.0: PCIe error reporting enabled
May 15 09:55:15 workstation kernel: [ 1.404059] be2net 0000:07:00.0: FW config: function_mode=0x3, function_caps=0x7
May 15 09:55:15 workstation kernel: [ 1.544087] be2net 0000:07:00.0: Max: txqs 1, rxqs 5, rss 4, eqs 16, vfs 0
May 15 09:55:15 workstation kernel: [ 1.544089] be2net 0000:07:00.0: Max: uc-macs 30, mc-macs 64, vlans 64
May 15 09:55:15 workstation kernel: [ 1.544133] be2net 0000:07:00.0: enabled 1 MSI-x vector(s) for NIC
May 15 09:55:15 workstation kernel: [ 1.688095] be2net 0000:07:00.0: created 1 TX queue(s)
May 15 09:55:15 workstation kernel: [ 1.712087] be2net 0000:07:00.0: created 1 RX queue(s)
May 15 09:55:15 workstation kernel: [ 1.799038] be2net 0000:07:00.0: FW version is 4.9.416.2
May 15 09:55:15 workstation kernel: [ 1.805191] be2net 0000:07:00.0: HW Flow control - TX:1 RX:1
May 15 09:55:15 workstation kernel: [ 1.813392] be2net 0000:07:00.0: Adapter does not support HW error recovery
May 15 09:55:15 workstation kernel: [ 1.813522] be2net 0000:07:00.0: Emulex OneConnect: PF port 1
May 15 09:55:15 workstation kernel: [ 1.813595] be2net 0000:07:00.1: be2net version is 11.4.0.0
May 15 09:55:15 workstation kernel: [ 1.813855] be2net 0000:07:00.1: PCIe error reporting enabled
May 15 09:55:15 workstation kernel: [ 2.064095] be2net 0000:07:00.1: FW config: function_mode=0x3, function_caps=0x7
May 15 09:55:15 workstation kernel: [ 2.188096] be2net 0000:07:00.1: Max: txqs 1, rxqs 5, rss 4, eqs 16, vfs 0
May 15 09:55:15 workstation kernel: [ 2.188098] be2net 0000:07:00.1: Max: uc-macs 30, mc-macs 64, vlans 64
May 15 09:55:15 workstation kernel: [ 2.188148] be2net 0000:07:00.1: enabled 1 MSI-x vector(s) for NIC
May 15 09:55:15 workstation kernel: [ 2.296098] be2net 0000:07:00.1: created 1 TX queue(s)
May 15 09:55:15 workstation kernel: [ 2.320099] be2net 0000:07:00.1: created 1 RX queue(s)
May 15 09:55:15 workstation kernel: [ 2.430614] be2net 0000:07:00.1: FW version is 4.9.416.2
May 15 09:55:15 workstation kernel: [ 2.437790] be2net 0000:07:00.1: HW Flow control - TX:1 RX:1
May 15 09:55:15 workstation kernel: [ 2.445992] be2net 0000:07:00.1: Adapter does not support HW error recovery
May 15 09:55:15 workstation kernel: [ 2.446111] be2net 0000:07:00.1: Emulex OneConnect: PF port 2
May 15 09:55:15 workstation kernel: [ 2.447419] be2net 0000:07:00.0 enp7s0f0: renamed from eth0
May 15 09:55:15 workstation kernel: [ 2.464282] be2net 0000:07:00.1 enp7s0f1: renamed from eth1
May 15 09:55:15 workstation sensors[1628]: be2net-pci-0700
May 15 09:55:15 workstation sensors[1628]: be2net-pci-0701
May 15 09:55:16 workstation kernel: [ 10.483582] be2net 0000:07:00.0 enp7s0f0: Link is Up
May 15 09:55:16 workstation kernel: [ 10.502938] be2net 0000:07:00.0 enp7s0f0: Link is Up
May 15 09:55:16 workstation kernel: [ 10.573081] be2net 0000:07:00.1 enp7s0f1: Link is Down
May 15 09:55:16 workstation kernel: [ 10.594631] be2net 0000:07:00.1 enp7s0f1: Link is Down
May 15 09:57:04 workstation kernel: [ 118.627524] be2net 0000:07:00.1: FW not responding
May 15 09:57:04 workstation kernel: [ 118.627530] be2net 0000:07:00.1: enp7s0f1: Link down
May 15 09:57:04 workstation kernel: [ 118.678167] be2net 0000:07:00.1: did not receive flush compl
May 15 09:58:01 workstation kernel: [ 176.252105] be2net 0000:07:00.0: FW not responding
May 15 09:58:01 workstation kernel: [ 176.252113] be2net 0000:07:00.0: enp7s0f0: Link down
May 15 09:58:01 workstation kernel: [ 176.262246] be2net 0000:07:00.0: txq0: cleaning 318 pending tx-wrbs
May 15 09:58:01 workstation kernel: [ 176.313025] be2net 0000:07:00.0: did not receive flush compl
May 15 09:58:11 workstation kernel: [ 186.333781] be2net 0000:07:00.0: be2net version is 11.4.0.0


I've found this page from 2015, where someone states, that be2net breaks when dma_alloc_coherent memory is not zeroed out. This seems to match my observations, as the memory contains no data upon a fresh start from powered off, while a restart not clears my RAM and so the driver has data in the memory received from the kernel, exposes it to the card and the cards firmware crashes.



Furthermore it somehow seems related to IOMMU. So I tried differend kernel parameters without success:



iommu=fullflush amd_iommu=fullflush disable_ddw


I hope some has an idea, what I can do to fix this. I've tried zeroing out my RAM with "sdmem -ll" on shutdown, but the driver memory is allocaed on such a low level, that I cannot zero it that way.





networking drivers kernel firmware





share|improve this question











share|improve this question




share|improve this question










asked May 15 at 10:24









Oliver R.

1066




1066











  • In case an administrator sees this: Can you please move this thread to Server Fault? Maybe I got higher chances for an answer there because it is somehow related to enterprise networking hardware/driver. Thank you
    – Oliver R.
    May 18 at 11:11
















  • In case an administrator sees this: Can you please move this thread to Server Fault? Maybe I got higher chances for an answer there because it is somehow related to enterprise networking hardware/driver. Thank you
    – Oliver R.
    May 18 at 11:11















In case an administrator sees this: Can you please move this thread to Server Fault? Maybe I got higher chances for an answer there because it is somehow related to enterprise networking hardware/driver. Thank you
– Oliver R.
May 18 at 11:11




In case an administrator sees this: Can you please move this thread to Server Fault? Maybe I got higher chances for an answer there because it is somehow related to enterprise networking hardware/driver. Thank you
– Oliver R.
May 18 at 11:11















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1036466%2fno-network-connection-after-reboot-be2net-fw-not-responding%23new-answer', 'question_page');

);

Post as a guest






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1036466%2fno-network-connection-after-reboot-be2net-fw-not-responding%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

pylint3 and pip3 broken

Image
Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I have tried sudo apt remove --purge on various packages. I get the same when I reinstall. I have also tried reinstall using aptitude. This does not work. My current workaround is to run pylint3 as root, which works, but is bad practice. pip3 $ pip3 Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pip/_vendor/__init__.py", line 33, in vendored __import__(vendored_name, globals(), locals(), level=0) ImportError: No module named 'pip._vendor.pkg_resources' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/bin/pip3", line 9, in <module> from pip import main File "/usr/lib/python3/dist-packages/pip/__init__.py", line 13, in <module> from pip.exceptions import InstallationError, CommandError, PipError File "/usr/lib/python3/dist-packages/pip/exceptions.py", line 6, ...
Read more

Missing snmpget and snmpwalk

Image
Clash Royale CLAN TAG #URR8PPP up vote 0 down vote favorite I have installed Zabbix appliance, directly preinstalled and found that there is missing snmpwalk and snmpget commands. I tried to install it with: apt-get install net-snmp-utils but I have error message: Unable to locate package. I have also check what from SNMP is preinstalled and there is: libsnmp-base libsnmp30:amd64 snmp-mibs-downloader snmpd snmptrapd snmptrapfmt How can I install snmpget and snmpwalk ? snmp zabbix share | improve this question edited Jan 29 at 10:10 Yaron 8,552 7 18 38 asked Jan 29 at 9:51 Alfista 1 apt install snmp perhaps ? If named differently - apt cache snmp – fugitive Jan 29 at 10:00 add a comment  |  up vote 0 down vote favorite I have installed Zabbix appliance, directly preinstalled and found that there is missing snmpwalk and snmpget commands. I tried...
Read more

How to enroll fingerprints to Ubuntu 17.10 with VFS491

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I decided to switch from Windows to Ubuntu 17.10, I meet it like 8 years ago and I didn't decided to switch until now (haha). Well, my actual device is an HP Probook 4540s with a Validity fingerprint sensor (VFS491). The fingerprint sensor worked fine on Windows but I can't get it to work in Ubuntu. The device is recognized as 138a:003d but is not detected as a fingerprint scanner by some apps like Fingerprint GUI. I want to use the fingerprint scanner to log in into my user account in Ubuntu but it doesn't supports fingerprints without special software and the drivers of the fingerprint scanner are available for Windows but not for any Linux distribution. I found something on GitHub (https://github.com/eekpie/libfprint) about the integration of the VFS491 in libfprint and I think it can help but I don't know what to do with it, so that's why I need the help of the community to do it since I am...
Read more