JustOverride Posted June 1, 2022 Share Posted June 1, 2022 (edited) I have been getting the errors below. This started after upgrading to 6.10, but I have also started to use Swag along with some other vaultwarden and nextcloud. I happen to caught this once, when it happens the unraid dashboard is unresponsive (dockers appear to continue to work fine). This issue also stops after a while. I appreciate any assistance/feedback. I have removed what I thought was identifiable info, if you need any additional details let me know. May 29 18:46:24 ServerName kernel: vetha2fb6ef: renamed from eth0 May 29 18:46:24 ServerName avahi-daemon[7235]: Interface vethbb#####.IPv6 no longer relevant for mDNS. May 29 18:46:24 ServerName avahi-daemon[7235]: Leaving mDNS multicast group on interface vethbb#####.IPv6 with address v6IPaddress##. May 29 18:46:24 ServerName kernel: br-(rand###/letters): port 2(vethbb#####) entered disabled state May 29 18:46:24 ServerName kernel: device vethbb##### left promiscuous mode May 29 18:46:24 ServerName kernel: br-(rand###/letters): port 2(vethbb#####) entered disabled state May 29 18:46:24 ServerName avahi-daemon[7235]: Withdrawing address record for v6IPaddress##1 on vethbb#####. May 29 18:46:24 ServerName kernel: br-(rand###/letters): port 2(vethe#####) entered blocking state May 29 18:46:24 ServerName kernel: br-(rand###/letters): port 2(vethe#####) entered disabled state May 29 18:46:24 ServerName kernel: device vethe##### entered promiscuous mode May 29 18:46:24 ServerName kernel: br-(rand###/letters): port 2(vethe#####) entered blocking state May 29 18:46:24 ServerName kernel: br-(rand###/letters): port 2(vethe#####) entered forwarding state May 29 18:46:24 ServerName kernel: eth0: renamed from veth8dcd8d2 May 29 18:46:24 ServerName kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe#####: link becomes ready May 29 18:46:26 ServerName avahi-daemon[7235]: Joining mDNS multicast group on interface vethe#####.IPv6 with address fe80::d8d9:e1ff:fe88:8a3. May 29 18:46:26 ServerName avahi-daemon[7235]: New relevant interface vethe#####.IPv6 for mDNS. May 29 18:46:26 ServerName avahi-daemon[7235]: Registering new address record for fe80::d8d9:e1ff:fe88:8a3 on vethe#####.*. May 29 19:24:31 ServerName kernel: br-(rand###/letters): port 3(veth3####b9) entered disabled state May 29 19:24:31 ServerName kernel: vethbc7f3e1: renamed from eth0 May 29 19:24:31 ServerName avahi-daemon[7235]: Interface veth3####b9.IPv6 no longer relevant for mDNS. May 29 19:24:31 ServerName avahi-daemon[7235]: Leaving mDNS multicast group on interface veth3####b9.IPv6 with address v6IPaddress##2. May 29 19:24:31 ServerName kernel: br-(rand###/letters): port 3(veth3####b9) entered disabled state May 29 19:24:31 ServerName kernel: device veth3####b9 left promiscuous mode May 29 19:24:31 ServerName kernel: br-(rand###/letters): port 3(veth3####b9) entered disabled state May 29 19:24:31 ServerName avahi-daemon[7235]: Withdrawing address record for v6IPaddress##2 on veth3####b9. May 29 19:25:58 ServerName emhttpd: spinning down /dev/sdh May 29 19:28:11 ServerName kernel: br-(rand###/letters): port 3(vethe#####) entered blocking state May 29 19:28:11 ServerName kernel: br-(rand###/letters): port 3(vethe#####) entered disabled state May 29 19:28:11 ServerName kernel: device vethe##### entered promiscuous mode May 29 19:28:11 ServerName kernel: eth0: renamed from veth140669f May 29 19:28:11 ServerName kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethe#####: link becomes ready May 29 19:28:11 ServerName kernel: br-(rand###/letters): port 3(vethe#####) entered blocking state May 29 19:28:11 ServerName kernel: br-(rand###/letters): port 3(vethe#####) entered forwarding state May 29 19:28:13 ServerName avahi-daemon[7235]: Joining mDNS multicast group on interface vethe#####.IPv6 with address fe80::c4ee:cdff:fe96:b1db. May 29 19:28:13 ServerName avahi-daemon[7235]: New relevant interface vethe#####.IPv6 for mDNS. May 29 19:28:13 ServerName avahi-daemon[7235]: Registering new address record for fe80::c4ee:cdff:fe96:b1db on vethe#####.*. May 29 19:33:01 ServerName emhttpd: spinning down /dev/sdi May 29 19:34:01 ServerName kernel: br-(rand###/letters): port 3(vethe#####) entered disabled state May 29 19:34:01 ServerName kernel: veth140669f: renamed from eth0 May 29 19:34:01 ServerName avahi-daemon[7235]: Interface vethe#####.IPv6 no longer relevant for mDNS. May 29 19:34:01 ServerName avahi-daemon[7235]: Leaving mDNS multicast group on interface vethe#####.IPv6 with address fe80::c4ee:cdff:fe96:b1db. May 29 19:34:01 ServerName kernel: br-(rand###/letters): port 3(vethe#####) entered disabled state May 29 19:34:01 ServerName kernel: device vethe##### left promiscuous mode May 29 19:34:01 ServerName kernel: br-(rand###/letters): port 3(vethe#####) entered disabled state May 29 19:34:01 ServerName avahi-daemon[7235]: Withdrawing address record for fe80::c4ee:cdff:fe96:b1db on vethe#####. May 29 19:34:01 ServerName kernel: br-(rand###/letters): port 3(vethad56df4) entered blocking state May 29 19:34:01 ServerName kernel: br-(rand###/letters): port 3(vethad56df4) entered disabled state May 30 16:33:23 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:33:23 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:33:23 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:33:23 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 132 May 30 16:33:23 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 108 May 30 16:33:54 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:33:54 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 92 May 30 16:34:19 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:19 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:19 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 132 May 30 16:34:19 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 124 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 200 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 700 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 180 May 30 16:34:34 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 596 May 30 16:34:53 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:53 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 340 May 30 16:34:55 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:55 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:55 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 948 May 30 16:34:55 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:55 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 324 May 30 16:34:55 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:34:55 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 132 May 30 16:34:55 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:35:19 ServerName kernel: net_ratelimit: 9 callbacks suppressed May 30 16:35:19 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:35:19 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 1316 May 30 16:35:25 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:35:25 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:35:25 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 124 May 30 16:35:25 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:35:25 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 236 May 30 16:35:25 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:35:25 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 340 May 30 16:35:25 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 348 May 30 16:35:58 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 116 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 372 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 724 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:26 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 596 May 30 16:36:42 ServerName kernel: net_ratelimit: 1 callbacks suppressed May 30 16:36:42 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:42 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:42 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:42 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 260 May 30 16:36:47 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:36:47 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 132 May 30 16:37:19 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:38:37 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:38:37 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 688 May 30 16:38:51 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:38:59 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:38:59 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 656 May 30 16:39:06 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:39:06 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 324 May 30 16:39:46 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:39:46 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:39:46 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 196 May 30 16:39:46 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 372 May 30 16:39:51 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:39:51 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:39:51 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 724 May 30 16:39:51 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:39:51 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 1496 May 30 16:39:51 ServerName kernel: sky2 0000:0a:00.0: error interrupt status=0x40000008 May 30 16:39:51 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 536 May 30 16:39:51 ServerName kernel: sky2 0000:0a:00.0 eth0: rx error, status 0x7ffc0001 length 84 May 30 17:11:11 ServerName kernel: TCP: request_sock_TCP: Possible SYN flooding on port ####. Sending cookies. Check SNMP counters. [2022-05-30 00:41:13.920][request][INFO] GET /admin/diagnostics [2022-05-30 00:41:14.951][response][INFO] (diagnostics) GET /admin/diagnostics => 200 OK [2022-05-30 00:49:31.496][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:53710. [2022-05-30 00:49:31.518][request][INFO] GET /api/accounts/revision-date [2022-05-30 00:49:31.518][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 00:49:31.566][request][INFO] POST /identity/connect/token [2022-05-30 00:49:31.568][response][INFO] (login) POST /identity/connect/token => 200 OK [2022-05-30 00:49:31.617][request][INFO] GET /api/sync [2022-05-30 00:49:31.619][response][INFO] (sync) GET /api/sync?<data..> => 200 OK [2022-05-30 01:05:47.537][request][INFO] POST /identity/connect/token [2022-05-30 01:05:47.539][response][INFO] (login) POST /identity/connect/token => 200 OK [2022-05-30 01:05:47.576][request][INFO] GET /api/accounts/revision-date [2022-05-30 01:05:47.576][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 01:05:47.584][request][INFO] GET /api/sync [2022-05-30 01:05:47.586][response][INFO] (sync) GET /api/sync?<data..> => 200 OK [2022-05-30 01:20:21.381][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:42682. [2022-05-30 01:20:21.448][request][INFO] GET /api/accounts/revision-date [2022-05-30 01:20:21.449][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 02:57:14.651][request][INFO] GET /api/accounts/revision-date [2022-05-30 02:57:14.652][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 03:04:52.544][request][INFO] POST /identity/connect/token [2022-05-30 03:04:52.546][response][INFO] (login) POST /identity/connect/token => 200 OK [2022-05-30 03:04:52.627][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:47352. [2022-05-30 03:04:52.633][request][INFO] GET /api/accounts/revision-date [2022-05-30 03:04:52.633][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 03:41:44.006][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:45732. [2022-05-30 03:41:44.027][request][INFO] GET /api/accounts/revision-date [2022-05-30 03:41:44.028][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 03:53:29.595][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:48368. [2022-05-30 03:53:29.677][request][INFO] GET /api/accounts/revision-date [2022-05-30 03:53:29.678][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 09:57:05.847][request][INFO] POST /identity/connect/token [2022-05-30 09:57:05.850][response][INFO] (login) POST /identity/connect/token => 200 OK [2022-05-30 09:57:05.907][request][INFO] GET /api/accounts/revision-date [2022-05-30 09:57:05.908][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 10:53:24.734][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:38604. [2022-05-30 10:53:24.806][request][INFO] GET /api/accounts/revision-date [2022-05-30 10:53:24.806][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 11:41:44.836][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:53574. [2022-05-30 11:41:44.905][request][INFO] GET /api/accounts/revision-date [2022-05-30 11:41:44.906][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 12:45:37.765][request][INFO] POST /identity/connect/token [2022-05-30 12:45:37.767][response][INFO] (login) POST /identity/connect/token => 200 OK [2022-05-30 12:45:37.835][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:43316. [2022-05-30 12:45:37.841][request][INFO] GET /api/accounts/revision-date [2022-05-30 12:45:37.841][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 12:57:28.374][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:35930. [2022-05-30 12:57:28.395][request][INFO] GET /api/accounts/revision-date [2022-05-30 12:57:28.396][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 14:12:21.811][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:46842. [2022-05-30 14:12:21.838][request][INFO] GET /api/accounts/revision-date [2022-05-30 14:12:21.839][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 16:10:44.365][request][INFO] POST /identity/connect/token [2022-05-30 16:10:44.367][response][INFO] (login) POST /identity/connect/token => 200 OK [2022-05-30 16:10:44.446][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:50864. [2022-05-30 16:10:44.504][request][INFO] GET /api/accounts/revision-date [2022-05-30 16:10:44.504][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 16:51:18.227][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:54980. [2022-05-30 16:51:18.251][request][INFO] GET /api/accounts/revision-date [2022-05-30 16:51:18.251][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 17:12:43.792][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:42284. [2022-05-30 17:12:43.865][request][INFO] GET /api/accounts/revision-date [2022-05-30 17:12:43.865][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 17:34:14.676][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:40482. [2022-05-30 17:34:14.744][request][INFO] GET /api/accounts/revision-date [2022-05-30 17:34:14.744][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 17:46:57.416][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:55264. [2022-05-30 17:46:57.492][request][INFO] GET /api/accounts/revision-date [2022-05-30 17:46:57.493][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 20:45:11.352][request][INFO] POST /identity/connect/token [2022-05-30 20:45:11.356][response][INFO] (login) POST /identity/connect/token => 200 OK [2022-05-30 20:45:11.443][parity_ws::io][INFO] Accepted a new tcp connection from 172.18.0.34:33428. [2022-05-30 20:45:13.471][request][INFO] GET /api/accounts/revision-date [2022-05-30 20:45:13.471][response][INFO] (revision_date) GET /api/accounts/revision-date => 200 OK [2022-05-30 21:38:03.216][request][INFO] GET /admin [2022-05-30 21:38:03.216][response][INFO] (admin_login) GET /admin/ [2] => 200 OK [2022-05-30 21:38:33.253][request][INFO] POST /admin [2022-05-30 21:38:33.254][response][INFO] (post_admin_login) POST /admin/ => 303 See Other [2022-05-30 21:38:33.309][request][INFO] GET /admin [2022-05-30 21:38:33.310][response][INFO] (admin_page) GET /admin/ => 200 OK Edited June 2, 2022 by JustOverride Quote Link to comment
MAM59 Posted June 2, 2022 Share Posted June 2, 2022 the 2nd log (receive errors, syn flooding etc) would tell me to check the cables (and more important the plugs). Looks like you are having a contact problem on either receive or sending side. Note that modern RJ45 plugs/outlets are a little bit longer than before. When put into an "old" card/switch port, they dont fit really tightly anymore. The same is true for old cables in new ports, they are somewhat a bit loose. Try to move it and see if the error shows up. If it does, find a working position and use a bit of hot glue to keep the cable in place. (yeah seems to be a very basic and lame advice, but really, its the 99% solution) Of course these errors also can show up from broken network cards / switches or wrong cables (10Gbe UTP cables are really complicated to buy working ones. The cables are usuall ok, but the plugs are a mess and if the lenght goes over 30m, its just plain luck if they work and if they work stable over the time. Better consider going fiber in this case) Sadly, you did not tell us, what kind of card and mobo this is. 1 Quote Link to comment
JustOverride Posted June 10, 2022 Author Share Posted June 10, 2022 On 6/2/2022 at 12:43 AM, MAM59 said: the 2nd log (receive errors, syn flooding etc) would tell me to check the cables (and more important the plugs). Looks like you are having a contact problem on either receive or sending side. Note that modern RJ45 plugs/outlets are a little bit longer than before. When put into an "old" card/switch port, they dont fit really tightly anymore. The same is true for old cables in new ports, they are somewhat a bit loose. Try to move it and see if the error shows up. If it does, find a working position and use a bit of hot glue to keep the cable in place. (yeah seems to be a very basic and lame advice, but really, its the 99% solution) Of course these errors also can show up from broken network cards / switches or wrong cables (10Gbe UTP cables are really complicated to buy working ones. The cables are usuall ok, but the plugs are a mess and if the lenght goes over 30m, its just plain luck if they work and if they work stable over the time. Better consider going fiber in this case) Sadly, you did not tell us, what kind of card and mobo this is. Thanks for the info, as it is not a persistent issue I may be able to live with it until I upgrade to 10G RJ45. I have a 'HP 530SFP+ 10Gb Dual Port PCIe Ethernet Adapter Card 656244-001 w/ SFP' on a EVGA X79 FTW. Quote Link to comment
MAM59 Posted June 11, 2022 Share Posted June 11, 2022 note that there are several people here that report strange problems with these hp branded cards (which should be called "intel"). See other threads for this like or So far, no general solution was found, only educated guesses and speculations. I had a lot of these intel cards here (but only the utp version), kicked them out and switched to mellanox. since them, the network ghosts are gone here. My faith in these cards / drivers is very limited or even down to 0% (but this is my personal opinion, most of the time the cards work but sometimes they dropped connections, lost links, restarted and so on. drove me crazy) (i still have about 10 of them on the shelf, nobody wants them 🙂 ) Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.