From: Udo van den Heuvel <udovdh@xs4all.nl>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: "Holger Hoffstätte" <holger@applied-asynchrony.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>
Subject: Re: 5.4.1 WARNINGs with r8169
Date: Wed, 4 Dec 2019 03:51:09 +0100 [thread overview]
Message-ID: <a3757aa2-9d72-1bb4-4524-edb0b7d191dd@xs4all.nl> (raw)
In-Reply-To: <3a1706be-e236-6f08-73eb-734f0ae41bbb@gmail.com>
On 03-12-2019 20:58, Heiner Kallweit wrote:
> - full dmesg log
The rest of dmesg is irrelevant but we will try to oblige of course
> - last known good kernel version
5.2.21-rt13
Because of the mutex issues I switched to 5.4.1.
> - whether problem persists if you switch the one interface with jumbo
> packets to standard MTU
That test is prepared already.
> - best would be a bisect result
The offending commit is already known. (!?)
Udo
prev parent reply other threads:[~2019-12-04 2:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <46e7dcf9-3c89-25c1-ccb8-336450047bec@xs4all.nl>
2019-12-01 9:52 ` 5.4.1 WARNINGs with r8169 Holger Hoffstätte
2019-12-01 10:27 ` Udo van den Heuvel
2019-12-01 15:30 ` Udo van den Heuvel
2019-12-03 19:58 ` Heiner Kallweit
2019-12-03 22:11 ` Stephen Hemminger
2019-12-04 2:51 ` Udo van den Heuvel [this message]
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=a3757aa2-9d72-1bb4-4524-edb0b7d191dd@xs4all.nl \
--to=udovdh@xs4all.nl \
--cc=hkallweit1@gmail.com \
--cc=holger@applied-asynchrony.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 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).