Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 0 replies
  • Subscribers 26 subscribers
  • Views 600 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Mellanox ConnectX-2 Ethernet adapter stops working

Sophos User4275

Hi all,

Seem to have an issue with my Sophos XG home firewall thats become worse following the latest update (SFOS 18.5.2 MR-2-Build380)

Its running on a HP SFF desktop PC with 6GB ram, and a 4th gen i7.

Using the standard Intel onboard NIC for my WAN interface (connecting with PPPoE) and a dual port Mellanox ConnectX-2 10 Gb adapter as the local interface (used for VLANs)

I've noticed that the local interface seems to stop working randomly out of the blue, rebooting the machine entirely resolves it (no unplugging or plugging SFPs/Fibre helps)

I've noticed around the time that I last had this problem, the following was logged:

Jan 1 01:02:28 (none) user.err kernel: [ 8.087233] ip_local_port_range: prefer different parity for start/end values.
Jan 1 01:02:28 (none) user.err kernel: [ 8.096009] packet dropped in ipsec0 device
Jan 1 01:02:28 (none) user.notice kernel: [ 8.170293] random: sshd: uninitialized urandom read (32 bytes read)
Jan 1 01:02:28 (none) user.notice kernel: [ 8.257377] random: tc: uninitialized urandom read (16 bytes read)
Jan 1 01:02:29 (none) user.err kernel: [ 8.476012] packet dropped in ipsec0 device
Jan 1 01:02:29 (none) user.info kernel: [ 8.981335] Watchdog driver for NexCom CR initialising.
Jan 1 01:02:29 (none) user.err kernel: [ 8.981337] NEXCOM_WATCHDOG: I/O address 0x00f2 busy
Jan 1 01:02:29 (none) user.info kernel: [ 9.012114] Watchdog driver for NexCom CR initialising.
Jan 1 01:02:29 (none) user.err kernel: [ 9.012115] NEXCOM_WATCHDOG: I/O address 0x00f2 busy
Jan 1 01:02:29 (none) user.info kernel: [ 9.044129] Watchdog driver for Portwell NAR-2085/5520/7090 initialising.
Jan 1 01:02:29 (none) user.info kernel: [ 9.044143] PW_NAR_WATCHDOG: Watchdog Device not supported
Jan 1 01:02:29 (none) user.info kernel: [ 9.088107] Watchdog driver for Portwell NAR-2085/5520/7090 initialising.
Jan 1 01:02:29 (none) user.info kernel: [ 9.088122] PW_NAR_WATCHDOG: Watchdog Device not supported

Any idea what could be causing this? Happy to get more logs as needed



This thread was automatically locked due to age.