9.7 killed eth0 for me... It had to be 'taken out'.

RE: 9.7 killed eth0 for me... It had to be 'taken out'.

Amodin — Fri, 22 May 2020 11:36:14 GMT

So I guess no one figured this out after not hearing from anyone. My guess with this is that typical driver issue you guys seem to have with the e1000 card which has been an issue for years that you seem to avoid and not address. I really don't have an option to change it out, because it's part of the SuperMicro board I have.

There's literally nothing wrong with the NIC. It's only a problem with using a Sophos product.

RE: 9.7 killed eth0 for me... It had to be 'taken out'.

Amodin — Sat, 23 Nov 2019 00:07:48 GMT

@Jaydeep

So I updated to 9.7, and here we are again, having the same issue. I managed to get the Kernal Message loaded and this is what is repeating almost non-stop:

2019:11:22-18:04:15 amodin kernel: [34136.708014] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
2019:11:22-18:04:15 amodin kernel: [34136.708014]   TDH                  <26>
2019:11:22-18:04:15 amodin kernel: [34136.708014]   TDT                  <74>
2019:11:22-18:04:15 amodin kernel: [34136.708014]   next_to_use          <74>
2019:11:22-18:04:15 amodin kernel: [34136.708014]   next_to_clean        <24>
2019:11:22-18:04:15 amodin kernel: [34136.708014] buffer_info[next_to_clean]:
2019:11:22-18:04:15 amodin kernel: [34136.708014]   time_stamp           <10080dd1c>
2019:11:22-18:04:15 amodin kernel: [34136.708014]   next_to_watch        <26>
2019:11:22-18:04:15 amodin kernel: [34136.708014]   jiffies              <10080e2f1>
2019:11:22-18:04:15 amodin kernel: [34136.708014]   next_to_watch.status <0>
2019:11:22-18:04:15 amodin kernel: [34136.708014] MAC Status             <40080083>
2019:11:22-18:04:15 amodin kernel: [34136.708014] PHY Status             <796d>
2019:11:22-18:04:15 amodin kernel: [34136.708014] PHY 1000BASE-T Status  <3800>
2019:11:22-18:04:15 amodin kernel: [34136.708014] PHY Extended Status    <3000>
2019:11:22-18:04:15 amodin kernel: [34136.708014] PCI Status             <10>
2019:11:22-18:04:15 amodin kernel: [34136.719680] e1000e 0000:00:19.0 eth0: Reset adapter unexpectedly
2019:11:22-18:04:19 amodin kernel: [34140.443550] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

RE: 9.7 killed eth0 for me... It had to be 'taken out'.

Amodin — Thu, 21 Nov 2019 21:11:38 GMT

Something that began happening this afternoon. I did a search of the eth0 error, and seems to be not so much a hardware issue but a Linux/Debian/Ubuntu issue. I think this might be related to what I was seeing with 9.7, just in a different format. I found this after I got we just experienced the same issue we had when we had 9.7 installed.

https://duckduckgo.com/?q=eth0%3A+Detected+Hardware+Unit+Hang%3A&t=ffcm&atb=v158-1&ia=web

I also found this issue on these forums under version 9 at least.

https://community.sophos.com/products/unified-threat-management/f/hardware-installation-up2date-licensing/29557/interface-eth0-hangs?pi2353=2

https://community.sophos.com/products/unified-threat-management/astaroorg/f/utm-9-2-beta/65588/9-194-5-bug-intel-nic-crashes-under-load

I wonder if the XG version of Sophos would have the same issue, if this is apparently linux flavor related?

2019:11:21-14:58:28 amodin kernel: [1048959.819318] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:
2019:11:21-14:58:28 amodin kernel: [1048959.819318]   TDH                  <2e>
2019:11:21-14:58:28 amodin kernel: [1048959.819318]   TDT                  <75>
2019:11:21-14:58:28 amodin kernel: [1048959.819318]   next_to_use          <75>
2019:11:21-14:58:28 amodin kernel: [1048959.819318]   next_to_clean        <2d>
2019:11:21-14:58:28 amodin kernel: [1048959.819318] buffer_info[next_to_clean]:
2019:11:21-14:58:28 amodin kernel: [1048959.819318]   time_stamp           <10f9a75f9>
2019:11:21-14:58:28 amodin kernel: [1048959.819318]   next_to_watch        <2f>
2019:11:21-14:58:28 amodin kernel: [1048959.819318]   jiffies              <10f9a78c6>
2019:11:21-14:58:28 amodin kernel: [1048959.819318]   next_to_watch.status <0>
2019:11:21-14:58:28 amodin kernel: [1048959.819318] MAC Status             <40080083>
2019:11:21-14:58:28 amodin kernel: [1048959.819318] PHY Status             <796d>
2019:11:21-14:58:28 amodin kernel: [1048959.819318] PHY 1000BASE-T Status  <38ff>
2019:11:21-14:58:28 amodin kernel: [1048959.819318] PHY Extended Status    <3000>
2019:11:21-14:58:28 amodin kernel: [1048959.819318] PCI Status             <10>
2019:11:21-14:58:30 amodin kernel: [1048961.822349] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang:

RE: 9.7 killed eth0 for me... It had to be 'taken out'.

Amodin — Fri, 15 Nov 2019 22:44:15 GMT

We really noticed it a lot about every two hours, almost on the dot even though eth0 was so quickly resetting itself. I am somewhat tempted to try and reproduce the error, but at the same time, not - haha.

Supermicro SuperServer LGA1150 350W 1U Rackmount Server Barebone System, Black SYS-5018D-MF is what I use for my UTM, with an Intel quadport card (currently not used). I just use the onboard dual NIC.

RE: 9.7 killed eth0 for me... It had to be 'taken out'.

BAlfson — Mon, 11 Nov 2019 19:30:52 GMT

Interesting. Earlier this year, I had a client with unexplained slowness related to eth0, so we had Sophos RMA their appliance after we demonstrated that everything worked perfectly if we just put the LAN on eth5. After the new unit arrived, we switched back to eth0 from eth5 after restoring the configuration. We were amazed to see the same problem, so we moved the LAN back to eth5 and everything was fine, so we left it there. I suspect it's a combination of an obscure bug and a particular combination of settings.

Cheers - Bob

RE: 9.7 killed eth0 for me... It had to be 'taken out'.

Amodin — Tue, 05 Nov 2019 17:51:29 GMT

No unfortunately, as I said I couldn't get to it as the UTM went silent and I couldn't even get back into it. I do remember eth0 interface resetting about every other second.

I went back to 9.603-1 and everything worked great. (EDIT: Also updated to .603-4 and -5, no problems there either). I checked the same logs and did not see the same messages, there was very little there actually, compared to what 9.7 was pushing.

RE: 9.7 killed eth0 for me... It had to be 'taken out'.

Jaydeep — Tue, 05 Nov 2019 15:49:59 GMT

Hi Amodin

Do you have any information about the errors you've seen in kernel logs? I've not seen any trend yet for issues related to Interface after 9.7 update. I'll go through the UTM forum to see if there's anything or if we can find any patterns.