Sorry,
the debugging and debdiff was done on the target machine so that the email ID
was missed.
This attached new debdiff also included the patch and lp number
information in the changelog.
And also updated the truncated description.
** Patch added: "bluez_5.48-0ubuntu3.5.debdiff"
https:/
This looks like a hardware or driver problem with the Radeon Pro WX
7100. Your logs show two issues:
1. Xorg logs that the monitor is being repeatedly redetected. So it
sounds like the monitor is not plugged in properly. Maybe try a new
monitor cable.
2. The kernel is logging more serious issues:
** Changed in: linux (Ubuntu)
Status: Expired => In Progress
--
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/1879470
Title:
stress-ng on gcov enabled focal kernel triggers OOPS
St
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/1888193
Title:
[amdgpu] Xorg freeze
Status i
The test has passed with 5.4.0-42.46 on all different arches.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
The results look good to me. The only case that looks like a failure
doesn't really have the nvidia modules loaded, so it's ok.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal
** Tags added: verification-done verification-done-bionic
verification-done-fo
Issues in dmesg in kernel are my fault - I'm developing app, which faults
GPU.
Have you read my description of the narrowed down issue?
pon., 20 lip 2020 o 09:50 Daniel van Vugt <1888...@bugs.launchpad.net>
napisał(a):
> This looks like a hardware or driver problem with the Radeon Pro WX
> 7100.
The test has passed with 5.3.0-64.58 on all different arches.
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
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
https://gitlab.gnome.org/GNOME/mutter/-/issues/1351
but currently it looks related to nvidia/nouveau driver
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1351
https://gitlab.gnome.org/GNOME/mutter/-/issues/1351
--
You received this bug notification because you are a member of K
Public bug reported:
the upgrade process assumes ZFS-utils is not configured and has exit
code 1
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: zfsutils-linux 0.8.3-1ubuntu12.1
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelMod
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1888202
Title:
package zfsutils-linux 0.8.3-1ubuntu12.1 failed to install/upgrade:
installed zf
** Description changed:
- Running stress-ng coverage testss on an ARM64 VM gcov 5.4.0-26-generic
- focal kernel trips the following oops:
+ == SRU Justification Focal RISC-V ==
+
+ Running stress-ng coverage tests on an ARM64 VM gcov 5.4.0-26-generic
+ focal kernel trips an oops because the kerne
Alex, did you read comment 7? 'low' isn't responding to what the
regression potential should provide, it's there to describe what impact
the change could have to know on what to focus the testing
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
@Sean, the failure you have seen here in 5.4 I believe it's for btrfs
instead (bug 1866323), not for xfs.
** Tags removed: 5.4 sru-20200629
--
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/1
** Tags added: 5.4 sru-20200629
--
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/1866323
Title:
btrfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
Status in ubuntu-kernel-t
The results look good to me. The only case that looks like a failure
doesn't really have the nvidia modules loaded, so it's ok.
** Also affects: nvidia-graphics-drivers-440-server (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-440-server (Ubuntu Bionic
Neither 111 nor 109 kernel nor any older would work with a full boot
into system.
So I was advised to get rid of the amdgpu drivers and make sure the open
source AMD drivers are installed.
https://amdgpu-install.readthedocs.io/en/latest/install-installing.html
#uninstalling-the-amdgpu-graphics-st
Probably fucked up installation was the cause of this. sorry for
bothering.
I recently reinstalled Kubuntu because I was frustrated with the stability of
my system. It still hadn't really improved since switch to kernel 5.4
And, magically, all the crashes are gone. So, no idea why but something i
Hello Didi,
The issue we face could be different : on the Lenovo Legion-5 15ARH05
(which is the object of this bug report) there is no working trick to
boot on Windows then Ubuntu : it just never worked under Linux on the
two BIOS tested (factory I think EUCN16WW and June update EUCN19WW), in
UEFI
Public bug reported:
Hello Ubuntu engineer. Thankyou for supporting me in your own time.
Laptop: lenovo Thinkbook 15-IIL
kernal: Linux 5.4.0-40-generic
happy to provide any more info. afraid couldn't find my touchpad manufacturer.
Thank you very much for your help.
ProblemType: Bug
DistroRel
** Description changed:
[Impact]
- * only impact Bionic machines because series after Bionic already
- included this patch.
+ This patch is for this issue:
+ steps:
+ 1. pair bluetooth keyboard
+ 2. see the dialog asking user input the code for pairing.
+ 3. press "esc" to cancel it.
+ 4
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/1888223
Title:
Touchpad not listed in /proc/b
sorry for bad habit that I miss-understanded before.
I revised it and put detail information there.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1887910
Title:
[bionic]blutoothd segfau
Why the status update to invalid? Several people have confirmed this
issue.
--
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/1822581
Title:
HP 1030 G3 fn-keys not working
Status in linux
You have been subscribed to a public bug:
Description: zipl: Fix KVM IPL without bootindex
Symptom: Failed IPL on KVM when no bootindex is specified.
Problem: Without bootindex specified there is no IPL parmblock
on KVM which can be read by the stage3 loader.
Solution:
Last night I built a kernel from drm-tip. CONFIG_BPFILTER is disabled
because of regressions, otherwise config is the same as used in
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/
I was eventually able to reproduce the problem but it seemed like I need
to reboot in order to do so
Now attaching failed dmesg.
** Attachment added: "failed-sound-dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879401/+attachment/5394330/+files/failed-sound-dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
Public bug reported:
Description: zipl: Fix KVM IPL without bootindex
Symptom: Failed IPL on KVM when no bootindex is specified.
Problem: Without bootindex specified there is no IPL parmblock
on KVM which can be read by the stage3 loader.
Solution: In case diag308
Public bug reported:
I'm using a computer Lenovo IdeaPad s145 and I've installed Ubuntu 20.04 LTS
and my touchpad doesn't work at all. xinput gives:
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointe
** Package changed: linux (Ubuntu) => s390-tools (Ubuntu)
--
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/1888231
Title:
[UBUNTU 20.04] zipl: Fix KVM IPL without bootindex
Status in s390
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => 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/1888229
Title:
Touchpad doesn't work
Status
--- Comment on attachment From jan.hoepp...@de.ibm.com 2020-07-20 11:15
EDT---
This is a patch that potentially fixes the issue. Can you please apply the
patch and run your tests with it? Please let me know if this fixes the issues
for you.
Please note that this patch is for testing _
You have been subscribed to a public bug:
After updating to package "linux-image-5.4.0-42-generic" (5.4.0.42.45)
several hundred system-log similar entires per minute are thrown at log:
kernel amdgpu :09:00.0: amdgpu: [mmhub] page fault (src_id:0 ring:169
vmid:0 pasid:0, for process pid 0
** Package changed: linux-hwe-5.4 (Ubuntu) => linux (Ubuntu)
--
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/1888116
Title:
kernel 5.4.0-42-generic looping amdgpu errors
Status in linux
Funny you say that there has been a problem with the Wifi on this
machine since it was solely running Windows 10. Best Buy could not fix
it and did not want to cheaply replace it. Sometimes (unable to
reproduce) the wifi loses the ability to detect networks and I would
have to reboot in order to re
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 1888116
and then change the status of the bug to 'Confirmed'.
If, due to the nature
This bug was fixed in the package linux - 5.4.0-42.46
---
linux (5.4.0-42.46) focal; urgency=medium
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
* linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimi
This bug was fixed in the package linux - 5.4.0-42.46
---
linux (5.4.0-42.46) focal; urgency=medium
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
* linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimi
This bug was fixed in the package linux - 5.4.0-42.46
---
linux (5.4.0-42.46) focal; urgency=medium
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
* linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimi
This bug was fixed in the package linux - 5.4.0-42.46
---
linux (5.4.0-42.46) focal; urgency=medium
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
* linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimi
This bug was fixed in the package linux - 5.4.0-42.46
---
linux (5.4.0-42.46) focal; urgency=medium
* focal/linux: 5.4.0-42.46 -proposed tracker (LP: #1887069)
* linux 4.15.0-109-generic network DoS regression vs -108 (LP: #1886668)
- SAUCE: Revert "netprio_cgroup: Fix unlimi
This bug was fixed in the package linux-restricted-modules - 5.4.0-42.46
---
linux-restricted-modules (5.4.0-42.46) focal; urgency=medium
* Master version: 5.4.0-42.46
linux-restricted-modules (5.4.0-41.45) focal; urgency=medium
* Master version: 5.4.0-41.45
* Packaging resyn
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => 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/1887011
Title:
Xenial update: v4.4.230 upstream stable rel
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => 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/1885932
Title:
Xenial update: v4.4.229 upstream stable rel
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => 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/1887838
Title:
Eoan update: upstream stable patchset 2020-07
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => 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/1887573
Title:
Eoan update: upstream stable patchset 2020-07
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => 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/1887188
Title:
Eoan update: upstream stable patchset 2020-07
--- Comment From niklas.schne...@ibm.com 2020-07-20 12:57 EDT---
(In reply to comment #19)
> On Fri, 26 Jun 2020 at 15:01, bugproxy <1877...@bugs.launchpad.net> wrote:
> >
> > (In reply to comment #17)
> > > Eoan and later d-i, new installer, curtin do not install
> > > /etc/kernel-img.conf
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => 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/1884766
Title:
use-after-free in af_alg_accept() due to bh
** Changed in: linux (Ubuntu)
Status: In Progress => 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/1886105
Title:
Disco update: upstream stable patchset 2020-07-02
** Changed in: linux (Ubuntu)
Status: In Progress => 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/1886876
Title:
Disco update: upstream stable patchset 2020-07-08
** Changed in: linux (Ubuntu Eoan)
Status: In Progress => 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/1886568
Title:
Eoan update: upstream stable patchset 2020-07
** Changed in: linux-raspi2 (Ubuntu Eoan)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1887156
Title:
USB ports not working on the Pi 4
** Changed in: ubuntu-z-systems
Status: New => In Progress
--
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/1879707
Title:
[UBUNTU 20.04] mke2fs dasd(fba),Failing CCW,default ERP ha
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-aws (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1
is maybe this also handled by gnome-flashback directly?
--
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/1878421
Title:
Using two GPUs with one monitor each, one is always black
Status in
mhm, ubuntu-session is same...i see cursor but no background/window
while dragging, this time it looks stable, after loggin out (from
ubuntu-session), i see login-form on laptop-screen and purple background
on external monitor. after logging into flashback it's same as in
ubuntu-session with black
It shouldn't be long that Ubuntu 20.04 kernel gets it from upstream.
--
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/1882823
Title:
int3403 thermal INT3403:00
Status in linux package in
The patch was meraged to 5.4 stable 5 hours ago -
=
This is a note to let you know that I've just added the patch titled
thermal: int3403_thermal: Downgrade error message
to the 5.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux
The cycle_test failure does not reproduce on everyrun. In order to
validate you'll have to run the test a few times. Moreover, seems that
ZZ lpars are easier to reproduce this.
Last, this patch fixes this bug:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=3337bf41e0d
Actually, this bug does not reproduce on everyrun. In order to validate
you'll have to run the test a few times. Moreover, seems that ZZ lpars
are easier to reproduce this.
Last, this patch fixes this bug:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=3337bf41e0dd70b
I did experience a complete lock of my system on the latest kernel and
it was worse then before, in a way that I was not able even to ssh to my
VM at all :(
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
Thanks for the review, it turns out that this failure has always been
present.
Going back to the Bionic 20180705 and Xenial 20180705, which were the
first releases of minimal, also showed that the system "Failed to find
module 'ib_iser'".
Is this something that could be fixed in order to prevent
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1881813/+attachment/5394404/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
Correction I was able to shh it took very long time.
Attaching log files
** Attachment added: "journal1.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881813/+attachment/5394402/+files/journal1.txt
--
You received this bug notification because you are a member of Kernel
Packages
** Attachment added: "prevjournal1.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881813/+attachment/5394403/+files/prevjournal1.txt
** Description changed:
Not too much info yet, will add apport report, but see it very often on 20.04
(upgraded from 18.04)
---
ProblemType:
Similar to bug 1888000, it appears this failure has also always been
present. I verified this against the focal 20200423 (oldest release with
5.4.0-1009-kvm) and 20200703 (newest release with 5.4.0-1018-kvm)
serials.
While this is no longer blocking image publication, is this something
that could
Since the workaround involves amd's iommu and kernel 5.5, we may be able
to find a patch that fixes this by cherry-pikcy: git log --pretty=short
v5.4..v5.5 -- drivers/iommu/amd_iommu.c
commit 1daa56bcfd8b329447e0c1b1e91c3925d08489b7
Merge: a5255bc31673 9b3a713feef8
Author: Linus Torvalds
Mer
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-firmware (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1887968
apport-collect tells me that this bug is not open anymore (or not started by
me) so i attach all relevant information, configurations and log files as
tar.gz archive
Pls advice if any other information is reqired
** Attachment added: "all relevant log files"
https://bugs.launchpad.net/ubuntu
A test kernel, based on UBUNTU: Ubuntu-5.4.0-42.46, is available @
https://people.canonical.com/~alexhung/LP1887218/ver1/
If this solves this bug, we can keep bisecting. If not, we can try other
patches.
The following commits are excluded:
== merges ==
1daa56bcfd8b329447e0c1b1e91c3925d08489b7
99
--- Comment From z...@us.ibm.com 2020-07-20 17:09 EDT---
I download iproute2-4.19.0.tar.gz from this upstream url:
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git
Build and tested on my existing ppc64 Genesis OS (4.15.0-1039-ibm-gt),
I do see it now reports correct tcp_flags m
This bug was fixed in the package linux - 4.15.0-112.113
---
linux (4.15.0-112.113) bionic; urgency=medium
* bionic/linux: 4.15.0-112.113 -proposed tracker (LP: #1887048)
* Packaging resync (LP: #1786013)
- update dkms package versions
* CVE-2020-11935
- SAUCE: aufs: d
This bug was fixed in the package linux-kvm - 4.15.0-1071.72
---
linux-kvm (4.15.0-1071.72) bionic; urgency=medium
* bionic/linux-kvm: 4.15.0-1071.72 -proposed tracker (LP: #1887041)
[ Ubuntu: 4.15.0-112.113 ]
* bionic/linux: 4.15.0-112.113 -proposed tracker (LP: #1887048)
*
This bug was fixed in the package linux - 4.15.0-112.113
---
linux (4.15.0-112.113) bionic; urgency=medium
* bionic/linux: 4.15.0-112.113 -proposed tracker (LP: #1887048)
* Packaging resync (LP: #1786013)
- update dkms package versions
* CVE-2020-11935
- SAUCE: aufs: d
This bug was fixed in the package linux - 4.15.0-112.113
---
linux (4.15.0-112.113) bionic; urgency=medium
* bionic/linux: 4.15.0-112.113 -proposed tracker (LP: #1887048)
* Packaging resync (LP: #1786013)
- update dkms package versions
* CVE-2020-11935
- SAUCE: aufs: d
This bug was fixed in the package linux - 4.4.0-186.216
---
linux (4.4.0-186.216) xenial; urgency=medium
* xenial/linux: 4.4.0-186.216 -proposed tracker (LP: #1885514)
* Xenial update: v4.4.228 upstream stable release (LP: #1884564)
- ipv6: fix IPV6_ADDRFORM operation logic
This bug was fixed in the package linux - 4.4.0-186.216
---
linux (4.4.0-186.216) xenial; urgency=medium
* xenial/linux: 4.4.0-186.216 -proposed tracker (LP: #1885514)
* Xenial update: v4.4.228 upstream stable release (LP: #1884564)
- ipv6: fix IPV6_ADDRFORM operation logic
This bug was fixed in the package linux - 4.4.0-186.216
---
linux (4.4.0-186.216) xenial; urgency=medium
* xenial/linux: 4.4.0-186.216 -proposed tracker (LP: #1885514)
* Xenial update: v4.4.228 upstream stable release (LP: #1884564)
- ipv6: fix IPV6_ADDRFORM operation logic
This bug was fixed in the package linux - 4.4.0-186.216
---
linux (4.4.0-186.216) xenial; urgency=medium
* xenial/linux: 4.4.0-186.216 -proposed tracker (LP: #1885514)
* Xenial update: v4.4.228 upstream stable release (LP: #1884564)
- ipv6: fix IPV6_ADDRFORM operation logic
This bug was fixed in the package linux - 4.4.0-186.216
---
linux (4.4.0-186.216) xenial; urgency=medium
* xenial/linux: 4.4.0-186.216 -proposed tracker (LP: #1885514)
* Xenial update: v4.4.228 upstream stable release (LP: #1884564)
- ipv6: fix IPV6_ADDRFORM operation logic
This bug was fixed in the package linux-kvm - 4.4.0-1077.84
---
linux-kvm (4.4.0-1077.84) xenial; urgency=medium
* xenial/linux-kvm: 4.4.0-1077.84 -proposed tracker (LP: #1885506)
* LXD 4.2 broken on linux-kvm due to missing VLAN filtering (LP: #1882955)
- [Config] VLAN_8021Q
This bug was fixed in the package linux - 4.4.0-186.216
---
linux (4.4.0-186.216) xenial; urgency=medium
* xenial/linux: 4.4.0-186.216 -proposed tracker (LP: #1885514)
* Xenial update: v4.4.228 upstream stable release (LP: #1884564)
- ipv6: fix IPV6_ADDRFORM operation logic
** Description changed:
Description:
When the speed of data with a usb disk device is too high, the probes
that check if the disk still exists is missed. This makes the disk to be
unmounted and is remounted with an other drive letter (/dev/sdX). If
this disk is the root ("/"), the com
This bug is present in all kernels tested from 4.15. Tested kernels are
at the end of this comment. The bug appears to depend heavily on the
speed of data. For example it works erasing a disk with all kernels with
dd if=/dev/urandom, but not with faster if=/dev/zero or if="openssl"
(exact syntax in
Log of udev event, when the bug happens.
# udevadm monitor | grep -v power_supply
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[4837.212964] remove
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.4.
Log of udev event, when the bug happens.
# udevadm monitor | grep -v power_supply
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[25.226057] remove
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.
Log of udev event, when the bug happens.
# udevadm monitor | grep -v power_supply
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[255114.318220] remove
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/ho
Log of udev event, when the bug happens.
# udevadm monitor | grep -v power_supply
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[10316.148582] remove
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/hos
Log of udev event, when the bug happens.
# udevadm monitor | grep -v power_supply
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[255114.318220] remove
/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/ho
Log of udev event, when the bug happens.
# udevadm monitor | grep -v power_supply
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[259892.454355] remove
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.
Log of udev event, when the bug happens.
# udevadm monitor | grep -v power_supply
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent
KERNEL[258304.180050] remove
/devices/pci:00/:00:14.0/usb2/2-4/2-4.4/2-4.
Public bug reported:
Hello,
I run Ubuntu 20.04 LTS on my Acer Aspire E5-573G and Ubuntu can't found my
bluetooth device.
I have a QCNFA335 (QCA9565) which can normally support both wifi and
bluetooth
I can use both wifi and bluetooth on windows 10.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
For 20.04 focal 5.4 kernel. it should be in this SRU cycle released on
10 Aug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1886247
Title:
Realtek [10ec:c82f] Subsystem [17aa:c
Nice! You don’t do anything on this and then expire it. Good job! So
much for stating that you want people to report bugs. What a waste of
time!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1852001
Title:
KDE GUI freeze on high disk IO
Status in linux package in
It might help to disable the built-in wifi. Try doing it in the BIOS. If
that doesn't work then you can disable the kernel driver of the built-in
wifi by adding a line:
blacklist ath10k_pci
to /etc/modprobe.d/blacklist.conf and then reboot.
--
You received this bug notification because you ar
** Tags added: 5.3 sru-20200629
--
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/1879299
Title:
enable disable fan test in ubuntu_fan_smoke_test failed on E/F s390x
LPAR / zVM ( docker s
** Tags added: hwe-networking-wifi
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1867559
Title:
Qualcomm Atheros QCA9377 wifi 802.11ac very unstable and low speed
Status in li
1 - 100 of 149 matches
Mail list logo
