From: Siva Reddy Kallam <siva.kallam@broadcom.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Linux Netdev List <netdev@vger.kernel.org>,
Prashant Sreedharan <prashant@broadcom.com>,
Michael Chan <mchan@broadcom.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: NETDEV WATCHDOG: eth0 (tg3): transmit queue 0 timed out
Date: Wed, 28 Feb 2018 19:40:33 +0530 [thread overview]
Message-ID: <CAMet4B7UraUZNO9rHyr3xxpJGcijffAK9YpYmOxA2Ax4eGfFgw@mail.gmail.com> (raw)
On Sat, Feb 24, 2018 at 3:48 PM, Borislav Petkov <bp@alien8.de> wrote:
> Hi,
>
> this didn't happen before but after 4.16-rc1 my tg3 nic stops for
> whatever reason and the connection to the machine is dead. It didn't show
> anything in dmesg until today.
>
> The IO pagefaults look like it is trying to access something it
> shouldn't and maybe that's why it times out.
>
> It triggers pretty quickly so I'd call it a reliable reproducer and thus
> I can test patches... :-)
>
> Thx.
Thanks for reporting this. Somehow, this mail moved to my spam folder.
Hence, delay in response.
Looks like this is similar to below issue and it was reported some time back.
https://www.spinics.net/lists/netdev/msg482757.html
We are actively working on this. We will soon provide you an update on this.
next reply other threads:[~2018-02-28 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 14:10 Siva Reddy Kallam [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-20 6:11 NETDEV WATCHDOG: eth0 (tg3): transmit queue 0 timed out Satish Baddipadige
2018-03-20 16:18 ` Borislav Petkov
2018-03-26 18:05 ` Borislav Petkov
2020-02-03 11:20 ` Borislav Petkov
2018-02-24 10:18 Borislav Petkov
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=CAMet4B7UraUZNO9rHyr3xxpJGcijffAK9YpYmOxA2Ax4eGfFgw@mail.gmail.com \
--to=siva.kallam@broadcom.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=prashant@broadcom.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).