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:
Since we already reached the stabilization phase of xenial/16.04 with .5 (and
.6), with the focus on stability and security, and because this is not a really
bug, rather than 'nice to have' to _not_ show /dev/kvm in case already running
virtualized on KVM (because nested KVM is not supported on
I upgraded the firmware on tiselius (boston p9) and ran the testcase and
it works as expected.
ubuntu@tiselius:~$ sudo /sbin/hwclock --set --date "2019/06/10 12:55:00"; sudo
/sbin/hwclock
2019-06-10 12:54:59.969984+00:00
ubuntu@tiselius:~$
should I wait for the release version of the firmware
Verified debian-installer in {disco,cosmic,bionic}-proposed.
The verification has been done with the netboot image files
for disco/cosmic/bionic (and hwe-netboot for bionic),
using regular and lvm partitioning,
on VMs for the architectures amd64/i386/arm64/ppc64el
and baremetal for amd64.
All
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1757218
Title:
QCA9377 isn't being recognized sometimes
i'm testing with settings ethtool -K eno1 gso off gro off tso off rx off
tx off
Few days ago my provider replaced all hardware, and attach network to another
switch port.
Also network cable is replaced
Cannot test kernel at this moment. System is already live.
Maybe Shivaram Lingamneni can run
The nature of this bug is clear and it does not require any logs, so
setting the status to "confirmed". In case anyone needs anything, please
let me know and I'll do my best.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you
@rnsc: Can you please share the VM's full serial log, which can be
obtained from Azure portal's Boot Diagnostics -> Serial log?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
BTW, on latest 4.4.0-150-generic ubuntu kernel, both adaptive-rx and
adaptive-tx were not supported.
# uname -a
Linux 2p2699v4-217 4.4.0-150-generic #176-Ubuntu SMP Wed May 29 18:56:26 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
# ethtool -C enp129s0 adaptive-rx on adaptive-tx on
# ethtool -c
** Tags added: nvidia s3
** Description changed:
I you watch a movie that uses CUDA/VDPAU (nvdec for mpv, vdpau for VLC)
decoding with {410,415,418,430} and pause the movie and do a S3 (suspend to
RAM) ... everything that needs CUDA and GPU acceleration stop working. will
update with
No, it didn't work on 4.13.0 kernel either.
# uname -a
Linux 2p2699v4-217 4.13.0-46-generic #51-Ubuntu SMP Tue Jun 12 12:36:29 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
# ethtool -i enp129s0
driver: mlx5_core
version: 5.0-0
firmware-version: 14.24.1000 (MT_2430110032)
expansion-rom-version:
"20fb5a635a0c" also works just fine on my side, will continue with the
kernel bisect.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx
** Description changed:
- No matter if I tried it with 410.x series, 415.x series, 418.x or 430.x
series after an S3 (suspend to RAM) ... everything that needs CUDA and GPU
acceleration stop working. will update with appropriate dmesg output.
- Fun fact: I just tried adding info putting this
PTI makes my 2 32 bit laptops unstable. I have lubuntu 18.04 installed on both
and they both started having trouble after the linux-image upgrade from
4.15.0-46/47 to 4.15.0-50/51. They either fail to boot without locking up or
fail to shut down cleanly. I rarely get any useful logs or messages
** Merge proposal linked:
https://code.launchpad.net/~smb/ubuntu/+source/iproute2/+git/iproute2/+merge/368924
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
Building a kernel with "37efe80ce85f drm/vmwgfx: use monotonic event
timestamps" being the HEAD doesn't exhibit the issue.
I'm now building and about to test 37efe80ce85f^1 (AKA 20fb5a635a0c) to confirm.
In theory it should fails with "20fb5a635a0c" if "37efe80ce85f" is the one.
- Eric
--
You
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1812822
Title:
Guest crashed when detaching the ovs interface device
Discussed with IBM that we need some help evaluating the VM dumps.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1831899
Title:
Kernel Oops 3b in libc-2.23 unable to handle pointer
Thanks for the glue. It does affect userspace apps. For applications use
udev, they will detect extra device number rather than expected number.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Per the above, are we safe to grab the latest kernel upgrades now and do
away with the dis_ucode_ldr workaround in grub at this point?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1828166
Title:
perf top problem on z with Ubuntu 18.04
Status in
** Changed in: linux (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1829972
Title:
Require improved hypervisor detection patch in Ubuntu
** Merge proposal linked:
https://code.launchpad.net/~rbalint/ubuntu-seeds/+git/ubuntu/+merge/368911
** Merge proposal linked:
https://code.launchpad.net/~rbalint/ubuntu-seeds/+git/platform/+merge/368915
--
You received this bug notification because you are a member of Kernel
Packages,
@rnsc, what kernel were you using?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
Azure Instance never recovered during series of instance reboots.
Status in
** Changed in: ubuntu-power-systems
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832388
Title:
[power9] [Cosmic] kernel panic while testing kdump
This problem appears to been have resolved with nvidia
430.26-0ubuntu0~gpu19.04.1 for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu.
https://bugs.launchpad.net/bugs/1825626
Title:
nvLock:
** Changed in: linux-firmware (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux-firmware (Ubuntu Cosmic)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
** Tags added: sru-20190603
** Tags added: amd64
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1830316
Title:
ksm06* from mm test suite in LTP failed on D
Status in
Excellent and nice post. This is such a great resource that you are providing
and you give it away for free. I love seeing that understands the value. I'm
glad to have found this post as its such an interesting one! I have also
something very interesting for you. Visit our blog post- Create
** Tags added: sru-20190603
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1833028
Title:
fanotify06 from ubuntu_ltp_syscalls failed
Status in ubuntu-kernel-tests:
In Progress
Status
Yeah, it seems to only occur with the TFTP setup that maas creates - and in all
former cases it resolved a few days later - most likely by size of images
changing.
That is the reason we need the files from an affected case.
@Reto - please see in the bug description above, there is a section "If
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: Incomplete
** Also affects: linux (Ubuntu Cosmic)
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1833065
and then change the status of the bug to 'Confirmed'.
If, due to the
** Tags added: oem-priority originate-from-1829966 somerville
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1833065
Title:
Intel WiFi (CNVi) module has no function on Comet Lake
Public bug reported:
Wireless module not detected by the system with the following error
messages in the log:
00:14.3 Network controller [0280]: Intel Corporation Device [8086:02f0]
Subsystem: Intel Corporation Device [8086:4030]
...
[ 4.195232] iwlwifi :00:14.3: enabling device ( ->
** Description changed:
== SRU Justification ==
- fanotify06 test from ubuntu_ltp_syscalls reported that test #1 for overlayfs
has received more than one expected event:
+ fanotify06 test from ubuntu_ltp_syscalls reported that test #1 for
+ overlayfs has received more than one expected event:
Public bug reported:
No matter if I tried it with 410.x series, 415.x series, 418.x or 430.x series
after an S3 (suspend to RAM) ... everything that needs CUDA and GPU
acceleration stop working. will update with appropriate dmesg output.
Fun fact: I just tried adding info putting this system
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Status: New => Triaged
** Changed in: mutter (Ubuntu)
Importance: Undecided => High
**
** Attachment added: "faster travel text"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832613/+attachment/5271139/+files/y20190617%20faster%20travel%20expl.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "slower travel text"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832613/+attachment/5271140/+files/y20190617%20slower%20travel%20expl.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
- This is a new test for overlayfs:
+ == SRU Justification ==
+ fanotify06 test from ubuntu_ltp_syscalls reported that test #1 for overlayfs
has received more than one expected event:
+
<<>>
tag=fanotify06 stime=1560747299
cmdline="fanotify06"
contacts=""
Private bug reported:
The current implementation is incomplete and there are paths from kernel
to userspace on which the CPU buffers are not cleared.
Fix that by backporting the MDS_USER_CLEAR_CPU_BUFFERS macro from stable
3.16 and use that in assembly entry/exit code.
** Affects: linux
The status for mutter will remain incomplete till someone tries the
suggestion from comment #31.
Sorry, I still can't reproduce this bug myself.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The problem I mentioned in comment #15 is now logged as bug 1833045.
It's clearly different to this one.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never
Would it be possible to try 4.4.0-143?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832863
Title:
Kernel 4.4.0.145 (& subsequent) boots to black screen.
Status in linux package in
** Tags added: kernel-block-ppa
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832508
Title:
linux: 4.18.0-23.24 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status
** Tags added: kernel-block-ppa
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832492
Title:
linux: 5.0.0-18.19 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status
** Tags added: kernel-block-ppa
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832578
Title:
linux: 4.15.0-53.57 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status
** Tags added: kernel-block-ppa
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832593
Title:
linux: 4.4.0-152.179 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796553
Title:
BT mouse getting reset during operation
Status in Linux:
Confirmed
Status in linux package in
Maybe this is actually more complex performance
bug than I first suspected, seems like you just
have to play game of snake with icon list or simple
text in editor.
e.g.
asdefg asdefg asdefg
asdefg asdefg asdefg
CORRECT
asdefg asdefg asdefg
asdefg asdefg asdefg
I am currently on Manjaro with 5.0 Kernel and the touchpad does not
disconnect but whenever I close the lid on the laptop and open it again,
it starts lagging and disconnects so I need to do a restart. On the
previous kernel it used to disconnect and also I have tried 5.1 and it
was also
Please test this patch.
** Patch added: "btusb-no-autosuspend.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/527/+files/btusb-no-autosuspend.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Please test this patch.
** Patch added: "btusb-no-autosuspend.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796553/+attachment/5271112/+files/btusb-no-autosuspend.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Not currently using Ubuntu, but I can attest that this exact same issue
persists across all distro's that I have tried.
Currently on Arch with kernel 5.19 and it still happens (ASUS FX503VM).
If it helps anyone narrow down the problem (well above my skill level),
kernel version 5.0 seemed to have
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc5/
If the issue persists, please file an upstream bug at
https://bugs.freedesktop.org/
Product: DRI
Component: DRM/intel
--
You received this bug notification because you are a member of Kernel
Packages,
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc5/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832004
Title:
[amdgpu] display hanging after
Hello, I noticed the same behavior on one of my Azure VM.
It wasn't rebooted thought, it just started blurting out "hyperv_fb" errors in
a loop. (that's all I could display in the Serial Console on Azure, even
sending SysRq to reboot the machine wasn't doing anything, I was forced to
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: ubuntu-kernel-tests
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Disco)
Assignee:
Hi, same problem here, keyboard backlight and some Fn don't work:
- F5 (fan overboost, that's ok if it doesn't work)
- F6 (don't know what it is)
- F7 (screen brightness down)
- F8 (screen brightness up)
- F10 (disable touchpad)
- F11 (screen sleep)
- F12 (airplane mode)
- keyboard arrow up
As I understood it, the fix was unfortunately some days to late for the
he previous Kernel SRU cycle. I then expected the fix to be applied for
the current SRU cycle, that is, 03-Jun through 30-Jun. I still assume
that is the case?
--
You received this bug notification because you are a member
Commit ID got upstream accepted with kernel v5.2-rc3, so will be automatically
part of 19.10, when target kernel 5.2 finally lands in eoan.
Kernel SRU needed for 19.04 and 18.04.
** Changed in: ubuntu-z-systems
Status: New => Triaged
--
You received this bug notification because you are
Commit ID got upstream accepted with kernel v5.2-rc3, so will be automatically
part of 19.10, when target kernel 5.2 finally lands in eoan.
Kernel SRU needed for 19.04 and 18.04.
** Changed in: ubuntu-z-systems
Status: New => Triaged
--
You received this bug notification because you are
101 - 166 of 166 matches
Mail list logo
