From: Salvatore Bonaccorso <carnil@debian.org>
To: Vincas Dargis <vindrg@gmail.com>
Cc: Heiner Kallweit <hkallweit1@gmail.com>, netdev@vger.kernel.org
Subject: Re: About r8169 regression 5.4
Date: Sat, 15 Feb 2020 17:12:47 +0100 [thread overview]
Message-ID: <20200215161247.GA179065@eldamar.local> (raw)
In-Reply-To: <97b0eb30-7ae2-80e2-6961-f52a8bb26b81@gmail.com>
Hi Vincas,
On Sat, Feb 15, 2020 at 11:22:01AM +0200, Vincas Dargis wrote:
> 2020-02-14 22:14, Heiner Kallweit rašė:
> > On 14.02.2020 18:21, Vincas Dargis wrote:
> > > Hi,
> > >
> > > I've found similar issue I have myself since 5.4 on mailing list archive [0], for this device:
> > >
> > Thanks for reporting. As you refer to [0], do you use jumbo packets?
>
> Not sure, I guess not, because "1500"?
>
> $ ip link | fgrep enp
> 2: enp5s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
> state UP mode DEFAULT group default qlen 1000
>
> > Best of course would be a bisect between 5.3 and 5.4. Can you do this?
> > I have no test hardware with this chip version (RTL8411B).
>
> Uhm, never done that, I'll have to research how do I "properly" build kernel in "Debian way" first.
>
> > You could also try to revert a7a92cf81589 ("r8169: sync PCIe PHY init with vendor driver 8.047.01")
> > and check whether this fixes your issue.
> > In addition you could test latest 5.5-rc, or linux-next.
>
> I've tried linux-image-5.5.0-rc5-amd64 (5.5~rc5-1~exp1) package form Debian
> experimental, issue "WARNING: CPU: 6 PID: 0 at net/sched/sch_generic.c:447
> dev_watchdog+0x248/0x250" still occurs after some time after boot.
>
> I'll try first to rebuild one of the Debian kernels after reverting that
> a7a92cf81589 patch, for starters.
You can generate the a7a92cf81589 revert patch, and then for simple
testing of a patch and build have a look at the Simple patching and
building[1] section of the kernel handbook.
Hope this helps,
Regards,
Salvatore
[1] https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s4.2.2
next prev parent reply other threads:[~2020-02-15 16:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 17:21 About r8169 regression 5.4 Vincas Dargis
2020-02-14 20:14 ` Heiner Kallweit
2020-02-15 9:22 ` Vincas Dargis
2020-02-15 16:12 ` Salvatore Bonaccorso [this message]
2020-02-15 21:10 ` Vincas Dargis
2020-02-15 22:07 ` Vincas Dargis
2020-02-15 22:35 ` Heiner Kallweit
2020-02-15 23:27 ` Heiner Kallweit
2020-02-17 18:08 ` Vincas Dargis
2020-02-17 19:59 ` Heiner Kallweit
2020-02-18 18:36 ` Vincas Dargis
2020-02-19 21:54 ` Heiner Kallweit
2020-02-20 17:36 ` Vincas Dargis
2020-02-20 18:32 ` Heiner Kallweit
2020-02-21 20:21 ` Vincas Dargis
2020-02-21 21:01 ` Heiner Kallweit
2020-02-23 13:24 ` Vincas Dargis
2020-02-23 13:27 ` Heiner Kallweit
2020-02-24 19:49 ` Heiner Kallweit
2020-02-27 18:25 ` Vincas Dargis
2020-04-12 11:56 ` Lauri Jakku
2020-04-12 12:02 ` Lauri Jakku
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=20200215161247.GA179065@eldamar.local \
--to=carnil@debian.org \
--cc=hkallweit1@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vindrg@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 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.