From: Heiner Kallweit <hkallweit1@gmail.com>
To: VDR User <user.vdr@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: r8169 driver from kernel 5.0 crashing - napi_consume_skb
Date: Thu, 4 Apr 2019 21:41:38 +0200 [thread overview]
Message-ID: <939eb5de-de7e-86ba-d1d9-fac7faa14f2c@gmail.com> (raw)
In-Reply-To: <CAA7C2qgSd3XBdH9Kq2erzFCU8Z_f7XBFOj5RkbJip9TdKf6YJw@mail.gmail.com>
On 04.04.2019 16:28, VDR User wrote:
> Hi,
>
> Unfortunately I have to report that the crashing has resurfaced. I'm
> currently using kernel 5.0 with Heiner's fix applied. In the last few
> days I've had the crash occur 4 times now. I'm not sure how to further
> investigate this but I'm guessing a patch that adds more debugging
> output will be needed to track down where exactly things go bad and
> hopefully what exactly is triggering it? In 2 cases there was
> bi-directional traffic, in the other 2 cases there was only incoming
> traffic. In all cases the nic became unresponsive, all connections to
> the box died/timed out. After roughly 10 minutes the nic came back to
> life on its own without my intervention. The odd thing I noticed was
> the dmesg log showing the problem only shows up once in dmesg instead
> of 4 times to coincide with the 4 crashes/freezes. I don't think the
> box reboot itself, and if it did then dmesg should be clean.
>
> Please let me know what you think and how we should proceed. Thanks!
> Derek
>
Instead of having to wait for the issue: Can you trigger it with iperf3
in either direction?
next prev parent reply other threads:[~2019-04-04 19:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 19:02 r8169 driver from kernel 5.0 crashing VDR User
2019-03-10 19:35 ` Heiner Kallweit
2019-03-14 3:04 ` VDR User
2019-03-14 6:43 ` Heiner Kallweit
2019-03-14 15:10 ` VDR User
2019-03-14 18:08 ` Heiner Kallweit
2019-03-14 21:36 ` VDR User
2019-03-15 20:09 ` VDR User
2019-03-15 20:26 ` r8169 driver from kernel 5.0 crashing - napi_consume_skb Heiner Kallweit
2019-03-15 20:40 ` Alexander Duyck
2019-03-15 20:46 ` Heiner Kallweit
2019-03-15 22:09 ` Alexander Duyck
2019-03-15 22:27 ` Heiner Kallweit
[not found] ` <b470f0ee6071bded8e78e15e18df14ffbc32cd18.camel@linux.intel.com>
2019-03-16 9:07 ` Heiner Kallweit
2019-03-16 14:38 ` VDR User
2019-03-16 15:10 ` Heiner Kallweit
2019-03-16 17:08 ` Alexander Duyck
2019-03-17 8:25 ` Heiner Kallweit
2019-03-17 11:35 ` Heiner Kallweit
2019-03-17 15:23 ` VDR User
2019-03-17 15:41 ` VDR User
2019-03-17 15:49 ` Heiner Kallweit
2019-03-18 16:17 ` VDR User
2019-03-18 18:36 ` Heiner Kallweit
2019-03-21 19:35 ` VDR User
2019-03-22 19:03 ` Heiner Kallweit
2019-03-22 20:44 ` VDR User
2019-04-04 14:28 ` VDR User
2019-04-04 19:41 ` Heiner Kallweit [this message]
2019-04-04 22:11 ` VDR User
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=939eb5de-de7e-86ba-d1d9-fac7faa14f2c@gmail.com \
--to=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=user.vdr@gmail.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).