It is a r8168 card. The problem continues to happen with the dkms module
however.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841040
Title:
r8169 ethernet sometimes doesn't work after cold boot/b
I finally completed the bisection. An extremely large number of kernels
failed to build. This is the result:
# only skipped commits left to test
# possible first bad commit: [4d6ca227c768b50b05cf183974b40abe444e9d0c] Merge
branch 'for-4.12/asus' into for-linus
# possible first bad commit: [800f3
Make sure your unit really is an r8169, and not an r8168.
Whilst (as I understand it) the r8169 module is supposed
to work with an r8168, at least on my laptop (Acer Aspire E17
(E5-722-425Q), currently 18.04 (up-to-date)),
using the r8169 module has resulted in "flakely" behaviour
for as long as I
Reloading the module does clear the error for me.
I have never seen the problem where the link comes up but it won't
receive packets.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841040
Title:
r8
I've a similar bug occurring on the following kernel versions:
* 5.0.0-23-generic
* 5.0.0-25-generic
* 5.0.0-27-generic
However, quite a few things are different in my case.
As seen in logs, "Link is Down" is quickly followed up by "Link is Up" message,
but interface fails to serve any packets. A
I *think* there is better and more pleasant workaround rather than
rebooting every time this bug affects you.
Try putting your computer into suspension, then wake it up.
In most of the cases Ethernet interface fails to start at all. If it does, then
reloading its driver may help it this point:
Seems like you may be right. I could not reproduce it with
1bcf165ac6556d after about 10 attempts. This isn't conclusive
unfortunately. I will continue with a regular bisect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
I think it's unlikely that these two caused the regression.
Please file an upstream bug at https://bugzilla.kernel.org/
Product: Drivers
Component: Network
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
It is perhaps worth mentioning that there are only two patches to r8169
in this time frame:
commit 1bcf165ac6556dc55a596d524b8187d1ba7a8c7d
Author: Zhu Yanjun
Date: Sun Mar 12 05:02:54 2017 -0400
r8169: replace init_timer with setup_timer
Replace init_timer with setup_timer to si
I have managed to reproduce this as far back as 2f34c1231bfc9f which is
somewhere between 4.11 and 4.12rc1. I have been unable to reproduce it
with 4.11, but this may just be due to bad luck. I will continue testing
tomorrow.
--
You received this bug notification because you are a member of Ubunt
I am working on this but it is slow as the bug is difficult to
reproduce. It seems to happen more often after cold boots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841040
Title:
r8169 ethernet
(and by cold boots I mean very cold - like the computer has been
switched off for several hours.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841040
Title:
r8169 ethernet sometimes doesn't work a
Why -rc? The last working kernel I know of is from the 4.4 series.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841040
Title:
r8169 ethernet sometimes doesn't work after cold boot/boot
To manage
First, find the last good -rc kernel and the first bad -rc kernel from
http://kernel.ubuntu.com/~kernel-ppa/mainline/
Then,
$ sudo apt build-dep linux
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux
$ git bisect start
$ git bisect good $(the good version you
Is it possible to perform a kernel bisection to find the regression
commit?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841040
Title:
r8169 ethernet sometimes doesn't work after cold boot/boot
T
I disabled secure boot and I was able to reproduce the problem with
mainline on the first attempt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841040
Title:
r8169 ethernet sometimes doesn't work
Is it possible to disable secure boot and git mainline kernel a try?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841040
Title:
r8169 ethernet sometimes doesn't work after cold boot/boot
To manag
I am not able to test that kernel as it is not signed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841040
Title:
r8169 ethernet sometimes doesn't work after cold boot/boot
To manage notification
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc5/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841040
Title:
r8169 ethernet sometimes doesn't work after
apport information
** Tags added: apport-collected
** Description changed:
Whenever the computer is rebooted there is a roughly 50% chance that the
r8169 ethernet cannot negotiate a link. There is no relevant information
in dmesg except for the "link down" message. The work around is to ju
20 matches
Mail list logo
