From: Neftin, Sasha <sasha.neftin@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] e1000e Detected Hardware Unit Hang
Date: Mon, 26 Mar 2018 08:48:05 +0300 [thread overview]
Message-ID: <4a1bebce-0174-2604-79d4-1fd92a033ff6@intel.com> (raw)
In-Reply-To: <1104005455.161583.1521817756059@mail.libero.it>
On 3/23/2018 18:09, Marco Berizzi wrote:
> Marco Berizzi wrote:
>>
>> Neftin Sasha wrote:
>>
>>> On 21/03/2018 18:19, Marco Berizzi wrote:
>>>
>>>> Marco Berizzi wrote:
>>>>>
>>>>
>>>>> Hello everyone,
>>>>>
>>>>> I'm getting this error with a Slackware linux 64bit running 4.16-rc6:
>>>>> I have also done a full hardware replacement, but the problem is still
>>>>> present. This box is running squid, named, sshd and strongswan.
>>>>>
>>>>> On february 3, I have replaced the network switch where this NIC is
>>>>> connected to (from cisco 3750 to HPE 5130).
>>>>> As you may see, the problem has popped up from Feb 13 with linux
>>>>> 4.15.3, but yesterday the problem has arisen also with 4.15.2 (I
>>>>> wanted to start a git bisect, but it is pointless).
>>>>
>>>> I think I have found the root cause. Before getting this error the
>>>> interface MTU was 9000bytes, and now it is 1500bytes.
>>>> Good. Please, try also disable TCP segmentation offload: ethtool -K
>>>>
>>>> tso off. Keep us update.
>>
>> Hi Sasha,
>>
>> thanks for the quick response.
>> I have disabled the tso:
>>
>> ethtool -K eth2 tso off
>> Cannot get device udp-fragmentation-offload settings: Operation not supported
>> Cannot get device udp-fragmentation-offload settings: Operation not supported
>>
>> I will keep you updated. Unfortunately I'm encountering this error
>> message not more than once a day. So my response will be a little
>> delayed.
>
> Hi Sasha,
>
> after more than 24 hours no error messages has popped up, so this is a
> good workaround.
>
> Question: is there a way to get the 82579LM working with the tso? Or is this
> an hardware bug?
>
This is HW bug. Currently we have no workaround in a driver. So, you can
try work with disable TSO or alternatively play with MTU size. Our more
new HW should go over this bug.
next prev parent reply other threads:[~2018-03-26 5:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 10:56 [Intel-wired-lan] e1000e Detected Hardware Unit Hang Marco Berizzi
2018-03-21 16:19 ` Marco Berizzi
2018-03-22 3:31 ` Neftin, Sasha
2018-03-22 3:35 ` Neftin, Sasha
2018-03-22 10:40 ` Marco Berizzi
2018-03-23 15:09 ` Marco Berizzi
2018-03-26 5:48 ` Neftin, Sasha [this message]
2018-03-26 15:13 ` Ben Greear
2018-03-27 14:47 ` Neftin, Sasha
2018-03-28 16:26 ` Marco Berizzi
2018-03-28 16:45 ` Ben Greear
2018-03-28 16:53 ` Marco Berizzi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4a1bebce-0174-2604-79d4-1fd92a033ff6@intel.com \
--to=sasha.neftin@intel.com \
--cc=intel-wired-lan@osuosl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.