This bug was fixed in the package linux-oem - 4.15.0-1043.48
---
linux-oem (4.15.0-1043.48) bionic; urgency=medium
[ Ubuntu: 4.15.0-52.56 ]
* Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard
manipulation (LP: #1831638)
- SAUCE: tcp:
This bug was fixed in the package linux-oem - 4.15.0-1043.48
---
linux-oem (4.15.0-1043.48) bionic; urgency=medium
[ Ubuntu: 4.15.0-52.56 ]
* Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard
manipulation (LP: #1831638)
- SAUCE: tcp:
** Changed in: linux-oem (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
r8169 no internet after suspending
To manage notifications about this
** Also affects: linux-oem (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem (Ubuntu Bionic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package linux - 4.15.0-36.39
---
linux (4.15.0-36.39) bionic; urgency=medium
* CVE-2018-14633
- iscsi target: Use hex2bin instead of a re-implementation
* CVE-2018-17182
- mm: get rid of vmacache_flush_all() entirely
linux (4.15.0-35.38)
For me the version in bionic-proposed also seems to work fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
r8169 no internet after suspending
To manage notifications about this
Earlier problems seem to have been caused by the packages not all
arriving in the archive together, and apt-get/aptitude and myself
getting very confused - apologies for noise. Can now confirm that
4.15.0-35.38 seems to solve the issue; tags adjusted.
** Tags removed: verification-needed-bionic
New bug report opened:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792635
On 14 September 2018 at 21:29, Steve Dodd wrote:
> Well 4.15.0-35.38 doesn't even finish booting on my machine. Doesn't
> find the root volume and the USB keyboard doesn't finish booting.
> Chances are the r8169
Well 4.15.0-35.38 doesn't even finish booting on my machine. Doesn't
find the root volume and the USB keyboard doesn't finish booting.
Chances are the r8169 fix is fine but I can't test.
On 14 September 2018 at 18:02, Brad Figg wrote:
> This bug is awaiting verification that the kernel in
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
I've found these discussion, installed latest r8169 driver and at last
internet begins to restore after suspending! Before that nothing help,
including "modprobe -r r8169" and restart NetworkManager. I'm happy! )))
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: linux (Ubuntu Bionic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
r8169 no internet after suspending
To manage notifications
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
r8169 no internet after suspending
To manage notifications
Kai-Heng Feng,
Success, I tried #63 and it worked.
This is great, thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
r8169 no internet after suspending
To manage notifications
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
r8169 no internet after suspending
To manage
** Description changed:
+ ===SRU Justification===
+ [Impact]
+ r8169 failed to establish connection after the fix for LP: #1752772
+ landed.
+
+ [Fix]
+ Accepts BIOS WoL settings again, and disables MSI-X for certain chip
+ revisions.
+
+ [Test]
+ Users confirmed the fix worked for them.
+
+
Yup, this kernel finally fixes things for me too (I did remember to
disable my other workaround) - thanks Kai, look forward to seeing it
SRU'd.
On 24 August 2018 at 09:39, Jan Rathmann wrote:
> Kai-Heng, the bug seems to be gone on my system with your newest kernel
> in #63 and I don't
Kai-Heng, the bug seems to be gone on my system with your newest kernel
in #63 and I don't experience any regression so far. Thanks for your
work!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Folks,
Please try this kernel out:
https://people.canonical.com/~khfeng/r8169/
If there's no more regression, I'll make a SRU request and the next
kernel will contain the fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached is a work-around for the in-kernel driver that is as unhacky as
I can make it.
Drop it in /etc/initramfs-tools/scripts/init-top and chmod a+x it. Add
'r8169_disable_msi' to your kernel command line (/etc/default/grub,
usually.) Remember to update-initramfs and update-grub as necessary.
Thanks Marco #59 !!!
The last r8168 package solves this problem :
Installing the lastest version of the r8168 driver found at
http://mirrors.edge.kernel.org/ubuntu/pool/universe/r/r8168/
(r8168-dkms_8.046.00-1_all.deb)
--
You received this bug notification because you are a member of Ubuntu
@Heiner,
This is a regression caused by my backport fix for LP: #1752772.
I pulled these four commits:
r8169: fix interrupt number after adding support for MSI-X interrupts
r8169: improve interrupt handling
r8169: disable WOL per default
r8169: remove some WOL-related dead code
r8169: remove
This is the only solution that worked for me:
https://askubuntu.com/a/1053520/222403
Installing the lastest version of the r8168 driver found at
http://mirrors.edge.kernel.org/ubuntu/pool/universe/r/r8168/
(r8168-dkms_8.046.00-1_all.deb)
Cheers!
--
You received this bug notification because
Can we cherry-pick
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=7c53a722459c1d6ffb0f5b2058c06ca8980b8600
for bionic?
On 10 August 2018 at 12:49, Heiner Kallweit <1779...@bugs.launchpad.net>
wrote:
> @Steve, there's some resistance amongst kernel maintainers
@Steve, there's some resistance amongst kernel maintainers against additional
module parameters. Each new parameter increases complexity and makes
maintenance harder.
Most likely it would result in a NAK when trying to fix an issue with one
broken exotic (sorry..) system in the kernel,
@Heiner, I know a number of other modules have a "use_msi_x" option - I
guess that would be too much to ask given I'm the only one who seems to
need it so far? :)
On 9 August 2018 at 16:54, David Jordan wrote:
> I can reproduce the issue with ethernet failing on the r8169 on resume
> from
I can reproduce the issue with ethernet failing on the r8169 on resume
from suspend with the current kernel. This is a regression since a
previous kernel on 18.04 since the symptoms occur after installing
updates.
I can also confirm that Kai's kernel seems to fix ethernet after suspend
on at
It's was only Kai's kernel from comment #39 that didn't boot - I've not had
any other problems on that front.
On 9 August 2018 at 12:05, Heiner Kallweit <1779...@bugs.launchpad.net>
wrote:
> Whether other systems suffer from the same MSI-X incompatability we'll
> know only once I get more such
Whether other systems suffer from the same MSI-X incompatability we'll
know only once I get more such bug reports. So far your report is the
only one.
You said if MSI-X is enabled it doesn't even boot. Any error message or
does it just silently stop?
And no, I'm not aware of any way to disable
Just double-checked with lspci -vvv and indeed the Realtek NIC is the only
MSI-X capable device. Is there anyway to disable MSI-X globally but leave
MSI on? All I can find is pci=nomsi which seems a bit heavy handed..
On 9 August 2018 at 10:08, Steve Dodd wrote:
> Yup, afraid so, Beelink S1:
Yup, afraid so, Beelink S1: https://www.amazon.co.uk/dp/B077HKCT78 - I'm
basically using it as an old-fashioned X Terminal. They promised a BIOS
update to "make it work with Linux" but I never got it to install and they
stopped answering my emails :( Happy to put it down to broken hardware so
long
Good that it's fixed for you. Indeed your BIOS seems to be broken with
regard to MSI-X. According to the vendor part of the MAC address your
mini PC is some no-name China product?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@kalle1
Your one liner seems to fix things - thank you! Also discovered I can
work around by writing 0 to /sys/devices/pci//msi_bus, which will
at least mean I can run unpatched Ubuntu kernels until we figure this
out :)
Anybody still having problems and wanting to test if this is their issue
is
Hmm, no "IOMMU" messages in dmesg, and the CPU is supposed to support it,
so I guess it is disabled,
however this machine really doesn't have a BIOS to speak of, in terms of
configurable settings anyway :(
On 8 August 2018 at 14:42, Heiner Kallweit <1779...@bugs.launchpad.net>
wrote:
> One more
I'm about to dash out, but will try the above change later. Meanwhile,
relevant bits of dmesg:
[4.440185] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[4.445120] r8169 :01:00.0: enabling device ( -> 0003)
[4.458178] r8169 :01:00.0 eth0: RTL8168g/8111g at 0x
(ptrval),
One more hint: I found few reports where people had problems
(independent of what is being discussed here) with MSI-X when VT-d is
disabled in the BIOS. Could you check this as well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Apart from switching to a more up-to-date API after this commit MSI-X
will be used if available. Maybe your system has a problem with MSI-X.
If you keep the commit and just do the following change, does it fix the
issue?
Replace
flags = PCI_IRQ_ALL_TYPES;
with
flags = PCI_IRQ_LEGACY |
Progress!
I have built ubuntu-bionic.git myself and discovered the only commit I
have to revert to get things working again is this one:
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
bionic.git/commit/?id=41450d46ba126887b9548cfcdf99957da5418ca5
@Kai, does that help you at all? If nothing else
@Kai-Heng your latest kernel completely breaks the network using r8169
for me. The system sort of manages to complete startup but fails to
attach an address to the network card. This is accompanied with lots of
console output similar to this
```
Aug 7 14:46:28 kernel: [ 25.761050] r8169
I can't even boot Kai's latest kernel! The system hard locks early in the
boot process, I have tried blacklisting r8169 and rebuilding the initramfs,
pretty sure it is not loaded by the point at which it hangs. My hardware is
cursed...
On 7 August 2018 at 21:13, Jan Rathmann wrote:
> @Kai-Heng
@Kai-Heng
I can confirm what Erik says - my network card seems to come up properly after
suspend with the backported kernel in #39.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
@Kai-Heng your last kernel seems to have done the trick for me!
My network comes back up after standby.
Also it installs nicely next to my current kernels awesome!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Jan, I made a new backport based on net-next, please try it out:
https://people.canonical.com/~khfeng/bionic-r8169-backport2/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
r8169 no
I've just built net-next direct from git and still have the same issue -
the NIC doesn't come back after suspend, even with rmmod / modprobe.
Is there any upstream awareness of this? Bug tracker and/or mailing list
discussion?
--
You received this bug notification because you are a member of
I also tried the net-next from kai-heng and I have the same issue no
network from boot.
I tried 4.17.12 using ukuu and I get the following firmware load error:
[ 43.570575] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a
lmp_ver=06 lmp_subver=8821
[ 43.570577] Bluetooth: hci0: rtl:
@Kai-Heng sorry for my late response to your question #22 (holidays) for
me everything worked on 4.14.0-23 and stopped working after that
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
@Kai-Heng
I did that, with net-next directly it seems that everything is working again at
least as good as in 4.15.0-23 (Network card comes up at boot, and also after
suspend.
So hopefully this got fixed in net-next.
--
You received this bug notification because you are a member of Ubuntu
Ok, can you try net-next [1] directly?
[1] https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
r8169 no internet after
@Kai-Heng
With this kernel version, unfortunately my network doesn't come up at all (even
after fresh power on. Reloading driver does not help).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Please try this kernel:
https://people.canonical.com/~khfeng/bionic-r8169-backport/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
r8169 no internet after suspending
To manage
The commits that causes the regression is a fix for another issue, LP:
#1752772. So we can't simply revert those fixes because it will regress
other users.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I still think there are multiple bugs here. Some of us have a network that
absolutely will not come back up after suspend with kernel version
>4.15.0-23, even after reloading the driver. So there is a very clear
regression that I would really like see resolved / rolled back. Breaking
stuff in an
Ok, I can confirm what I wrote on #28 on another installation.
Very hard for me to tackle this down - since bisecting obviously didn't
work.
Here is a summary of what I found out about this bug:
- Artful (or any other previous Ubuntu version) was not affected (at least not
to that extend, see
@Kai-Heng
Weird, I reinstalled and tested 4.15.0-23 again, and it seems that with
4.15.0-23 it can also happen that network is not coming up after suspend and
the driver has to be reloaded.
I'm going to further test this on another installation.
--
You received this bug notification because
i have the same issue with r8169 and Kubuntu 18.04.
with kernel version higher than 4.15.0-23 the network is not coming back from
suspend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Jan, so with 4.15.0-23, the NIC comes back every time the system
suspend/resume?
Steve, Erik, let's discuss your issue on LP: #1784542, since this bug is
limited to systemd suspend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A bit off-topic but: on a third machine of mine, booting into into
Bionic leaves the network card in a state where WoL won't work at all,
even after rebooting back into Trusty (3.13.0.) Have to power cycle the
machine, then WoL is fine.. (r8169 driver again, obviously)
--
You received this bug
I have to correct myself a bit: Network coming up correctly after
suspend only works from time to time. On the cases where it's not
working, the driver still has to be reloaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
lp1779817 kernel from #19 doesn't help me, last working kernel is
4.15.0-23.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
r8169 no internet after suspending
To manage notifications
Erik, did the ethernet work in previous kernel version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
r8169 no internet after suspending
To manage notifications about this bug go
I have tried both kernels lp1779817 and mainline 4.18-rc6 but the
problem is still there for me, also for me the
modprobe -r r8169 && modprobe r8169
has not worked with any of the kernels
My card is:
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express
This patch did help, my network comes up again after suspend with that
kernel version. Thanks alot!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
r8169 no internet after suspending
Please try the kernel [1] compiled with patch in [2].
[1] https://people.canonical.com/~khfeng/lp1779817/
[2] https://bugzilla.kernel.org/show_bug.cgi?id=200195
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bionic's kernel doesn't have commit
b489141369f78ead6ed540cff29ac1974852cd7f.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779817
Title:
r8169 no internet after suspending
To manage
See https://bugzilla.kernel.org/show_bug.cgi?id=200195
** Bug watch added: Linux Kernel Bug Tracker #200195
https://bugzilla.kernel.org/show_bug.cgi?id=200195
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
65 matches
Mail list logo
