Public bug reported:
Example of how was detected that the syslog stop working, it has couple
of days without reporting:
root@ilzlnx4:~# tail -f /var/log/syslog
Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664541] sd 3:0:0:2: [sdt] tag#81 CDB:
Inquiry 12 01 c9 00 fe 00
Sep 15 17:16:52 ilzlnx4 kernel:
You have been subscribed to a public bug:
Example of how was detected that the syslog stop working, it has couple
of days without reporting:
root@ilzlnx4:~# tail -f /var/log/syslog
Sep 15 17:16:52 ilzlnx4 kernel: [3725853.664541] sd 3:0:0:2: [sdt] tag#81 CDB:
Inquiry 12 01 c9 00 fe 00
Sep 15 17:
In BIOS, Change to RAID/Intel RST and create a volume.
Boot with 5.6.0.1028, the raid device can be found in /dev
#sudo fdisk -l
/dev/mapper/lsw_gdejahcjf_Volume1p1 2048 2000420863 2000418816 953.9G 83 Linu
--
You received this bug notification because you are a member of Kernel
Packages, which i
Public bug reported:
I've symlinked /lib/systemd/system/reboot.target to
/lib/systemd/system/kexec.target and everything works fine except my
framebuffer screen which on very initial screen with full disk
encryption password starts to floating horizontally. I'm able to use it,
after blindly typing
This is working fine in Ubuntu 20.10
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
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/1125452
Title:
[Lenovo T530]:
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: Fix Committed => In Progress
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubunt
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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag 'verifica
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
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
Ubuntu 20.04 user, can confirm this bug.
--
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/1838151
Title:
Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing
wide band
Failed with gkeop-5.4 as well.
** Tags added: sru-20200831
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1837348
Title:
test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests
fib_tests.sh / fib-onlink-tests.sh failed with Error: Unknown device
type. on gkeop-5.4
** Tags added: sru-20200831
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1812622
Title:
fib
I asked our desktop team about this, and Iain Lane mentioned that Ubuntu
overrides the GNOME default of auto-suspending, but that override only
takes effect if you have the ubuntu-settings package installed. I tested
this out on a Saber system, and I can confirm that it does seem to only
happen whe
Same here.
Same computer as original bug report (Hewlett-Packard HP Pavilion 11 x360 PC)
But different distro release (Xubuntu 20.04)
Laptop keyboard and trackpad totally nonfunctional on any kernel higher
than 5.4.0.42. Starting with 5.4.0-45 and all further kernels to today
(2020-09-22) the pro
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 'verifica
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 'verifica
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 'verifica
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 'verifica
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 'verifica
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 'verifica
The warning messages occurred between "ACPI: EC: interrupt blocked" and
"ACPI: EC: interrupt unblocked". Let's try to apply all (17) mainline
patches to ACPI EC to Ubuntu-5.4.0-47.51.
If this solves the problems we can then bi-select to identify which
patches are the solution and then backport to
UCT mentions commits 9060cb719e61b685ec0102574e10337fa5f445ea (specific
to AF_ALG) and ff7b11aa481f682e0e9711abfeb7d03f5cd612bf (all sockets).
The other commit we should care about is
6d8c50dcb029872b298eea68cc6209c866fd3e14 ("socket: close race condition
between sock_close() and sockfs_setattr()"
** Tags added: 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/bugs/1886769
Title:
[ 0.00] Initramfs unpacking failed: Decoding failed
Status in linux package in Ubuntu:
Confirmed
Cannot upload crash dumps due to timeout presumably due to size (1.6Gb).
Here're links instead:
1. http://temp.karakhorum.com/dl/crash_202009120944.tar.bz2
2. http://temp.karakhorum.com/dl/crash_202009121459.tar.bz2
--
You received this bug notification because you are a member of Kernel
Packag
** Changed in: nvidia-graphics-drivers-450-server (Ubuntu)
Status: In Progress => Fix Released
** Changed in: nvidia-graphics-drivers-450 (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux-restricted-modules (Ubuntu)
Status: Triaged => Fix Released
--
You rec
It appears to fail only for ppc64el. The proper solution sounds to be
complicated; would it be suitable as a temporary workaround to drop that
arch from the cpufreqd package (and leave this bug open until the
underlying issue is resolved)?
--
You received this bug notification because you are a
It seems that you *can* chown a socket, so this call just works fine. No
races with close needed. So, it seems to be a bogus assumption on the
part of the test.
Cascardo.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
1. kernel 5.4.0-48 -"quiet" -"splash" +"dis_ucode_ldr"
cat /proc/cpuinfo > cpuinfo-5.4.0-48.txt
dpkg -s intel-microcode | grep Version > intel-microcode-5.4.0-48.txt
2. kernel 4.15.0-112 -"quiet" -"splash" -"dis_ucode_ldr"
cat /proc/cpuinfo > cpuinfo-4.15.0-112.txt
dpkg -s intel-microcode | grep
I'll test the 5.8 kernel this weekend.
I'll upload a couple of tarballs next.
--
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/1895563
Title:
Kernel Oops: Rsyncing to bcache device w/o ba
Hi ~richard-from-davel and ~marco-zannoni,
Could you please test kernel 5.4.0-48, just released to
focal-updates a few hours ago and confirm it that helps?
It has fixes for two of the four patches introduced between
5.4.0-42 and 5.4.0-45/-47 (reported to be good/bad versions.)
Thanks,
Mauricio
Interesting.
For that you can add 'dis_ucode_ldr' in GRUB_CMDLINE_LINUX_DEFAULT in
/etc/default/grub.
Then run 'sudo update-grub', and confirm the change with 'grep dis_ucode_ldr
/boot/grub/grub.cfg'.
You should see non-recovery lines w/ that option as well.
Could you please upload /proc/cpuinf
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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
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/1896519
Title:
kworker consumes 80% of CPU
S
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: yakkety
--
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/1896521
Title:
Mounti
Good catch Mauricio!
1. "nomodeset" did not help.
2. "dis_ucode_ldr" succeed.
The logs after the successful boot are attached.
What can I do to make the boot use "dis_ucode_ldr" by default?
** Attachment added: "var_log3.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1895458/+a
Public bug reported:
Given these logical volumes on a Drobo 5D mounting will result in a
hang:
root@atx1:/var/log# lvs vg-drobo
LV VG Attr LSizePool Origin Data% Meta% Move Log
Cpy%Sync Convert
encrypted vg-drobo -wi-a- 1000.00g
** Attachment added: "syslog entries showing several "blocked for more than 120
seconds" errors"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896521/+attachment/5413021/+files/syslog
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
So, the test is running with the newer definition as it is picked up
from linux-libc-dev. But the kernel (linux-oem-5.6, in this case)
doesn't know about it. So it fails.
However, any binaries out there would be using the old definition, which
the linux-oem-5.6 should accept just fine. I guess we
Public bug reported:
Like yesterday I have noticed my CPU on Leonovo Thinkpad T590 laptop has
starting to be consumed by kworker for 80% of 2-CPU 4-core processor.
I also see fan works like crazy and "ejects" hot air non stop. This has
never happened in my 6 months of having this new laptop.
Pro
Ok, so nothing yet on the screen seems to suggest either
a graphics-related issue or a different, early problem.
The successful test to boot into recovery mode provides
a very good lead; thanks for coming up with that.
These are the 3 kernel options added by the recovery mode,
per the kern.log fi
Removing 'quiet splash' and adding 'earlyprintk=vga ignore_loglevel'
changed nothing - no more info on the screen.
Than I rebooted kernel 5.4.0-48 in recovery mode (Your system is
currently running without video hardware acceleration) and I am
attaching the var_log2.tar.gz
** Attachment added: "v
(The zero size problem mentioned above also occurs occasionally on
ubuntu 18.04, and the workaround is to add a sleep in the user script
after modprobe nbd, so that's really a separate problem.)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Thanks.
Ok, so there's nothing printed to console after grub loads the kernel
and initramfs.
The parameters in your grub config look good (kernel+initramfs+cmdline
w/ root= and ro.)
Could you please try without 'quiet splash' again, but add the options:
'earlyprintk=vga ignore_loglevel' ?
That
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 1896504
and then change the status of the bug to 'Confirmed'.
If, due to the nature
>From Apttermlog:
Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu6) ...
Loading new bcmwl-6.30.223.271+bdcom DKMS files...
Building for 5.4.0-47-generic 5.8.0-18-generic
Building for architecture x86_64
Building initial module for 5.4.0-47-generic
ERROR (dkms apport): kernel package lin
Public bug reported:
[Impact]
tc ebpf program that uses BPF_FUNC_skb_change_head are rejected.
This helper exists since linux v4.10, but it cannot be used until the the
upstream commit 6f3f65d80dac ("net: bpf: Allow TC programs to call
BPF_FUNC_skb_change_head"):
https://git.kernel.org/pub/scm
You have been subscribed to a public bug:
wifi not working
installed bcmwl-kernel-source package post-installation script
subprocess returned error exit status 6
Errors were encountered while processing:
bcmwl-kernel-source
E: Sub-process /usr/bin/dpkg returned an error code (1)
ProblemType:
Please find attached a snapshot of the boot screen
(var_log.tar.gz::var_log/1.jpg) and the screen after Ctrl+x
(var_log.tar.gz::var_log/2.jpg) - it simply freezes and displays nothing
more.
What I did:
1. booted kernel 5.4.0-48 without "quiet" & "splash" - 1.jpg
2. Ctrl+x - the computer totally fr
I've uploaded the update for Groovy to debian, it will get sync'd into
Ubuntu in the next 24 hours. I've uploaded the fix for Focal to Ubuntu
for SRU.
** Changed in: thermald (Ubuntu Focal)
Assignee: (unassigned) => Colin Ian King (colin-king)
** Changed in: thermald (Ubuntu Focal)
St
I'm the maintainer for thermald, I'll upload the fix to groovy and SRU
this for focal today.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1896419
Title:
Comet Lake CPUID family:mode
** Also affects: thermald (Ubuntu Groovy)
Importance: Undecided
Assignee: Kai-Chuan Hsieh (kchsieh)
Status: In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1896
Now that we got the change we sort of wanted from the beginning I have
created a test build of virt-manager with the change applied.
I need to debug if that now really enters the right code paths for non
fallocate.
--
You received this bug notification because you are a member of Kernel
Packages
It works (as expected):
before:
4 0 17337 263 20 0 163108 4240 - Sl ? 0:47 \_
/usr/bin/qemu-img create -f qcow2 -o
preallocation=falloc,compat=1.1,lazy_refcounts
/var/lib/libvirt/images/ubuntu20.04.qcow2 26214400K
Now:
4 0 43901 263 20 0 163108 5436
Patch request submitted for focal:
https://lists.ubuntu.com/archives/kernel-team/2020-September/thread.html#113609
changing status to 'In Progress' for focal.
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of K
Hi Petar,
Thanks for the bug report.
Unfortunately there's little details about the error.
Could you please post a picture of your compute screen
once the 5.4 kernel fails to boot?
(after you removed the 'quiet' and 'splash' options in
the grub editor, and pressed ctrl-x to boot.)
Mainly looki
Hey Martin.
The issues reported on comment 1 and commment 24 have different stack
trace signatures, and do not seem to be the same issue at all.
I'll thus mark this bug as Invalid as apparently you couldn't reproduce
the original issue anymore.
If the new issue is still present with the latest 5
Debian bug created.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970686
** Bug watch added: Debian Bug tracker #970686
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970686
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to therm
FYI, the patch on the mailing list is here:
https://lists.ubuntu.com/archives/kernel-team/2020-September/113590.html
--
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/1891151
Title:
md: imp
** Changed in: virt-manager
Status: Confirmed => Fix Released
--
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/1847105
Title:
very slow disk creation, snapshotting
Status in vi
Okay now that I actually look into this and wrap my head around it,
virt-manager should change.
See this previously mentioned change:
https://github.com/virt-manager/virt-manager/commit/15a6a7e2105440df528f75c4df4d2471df28bd1e
The idea behind virt-manager's default was if user selected 'raw' for
Recently installed a brand new copy of Linux Mint 20 Cinnamon and
suffered frequent freezes. The workaround suggested in comment #45 fixed
these for me. My current kernel is 5.4.0-47-generic, and I'm using a
Intel© Core™ i5-6500T CPU (2.50GHz × 4) with Intel Corporation HD
Graphics 530.
--
You re
Oops, please remove the --dry-run from apt install.
--
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/1895563
Title:
Kernel Oops: Rsyncing to bcache device w/o backing cache kernel panic
S
--- Comment From heinz-werner_se...@de.ibm.com 2020-09-21 09:07 EDT---
IBM bugzilla status->closed, Fix Released for focal and groovy
--
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/
Hey Brendan,
Thanks for reporting this bug.
It looks like the crashdump files didn't come through?
Could you please try to reproduce with the 5.8 kernel from Groovy on
your Bionic install?
These are the steps to install it.
Please remove the .list file as soon as you install the packages, to avo
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/1896482
Title:
acpi event detection crashes
Public bug reported:
Right after booting, acpi lid open/close is detected as it should be by
the kernel, but some time later it crashes, so I have to manually
suspend the system. The traceback is here:
Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here
]
Sep 20 11:
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.51.06-0ubuntu0.18.04.2
---
nvidia-graphics-drivers-450-server (450.51.06-0ubuntu0.18.04.2) bionic;
urgency=medium
* debian/dkms_nvidia/patches/buildfix_kernel_5.8.patch:
- Fix build failure (LP: #1887674
This bug was fixed in the package nvidia-graphics-drivers-450-server -
450.51.06-0ubuntu0.20.04.2
---
nvidia-graphics-drivers-450-server (450.51.06-0ubuntu0.20.04.2) focal;
urgency=medium
* debian/dkms_nvidia/patches/buildfix_kernel_5.8.patch:
- Fix build failure (LP: #1887674)
This bug was fixed in the package nvidia-graphics-drivers-450 -
450.66-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-450 (450.66-0ubuntu0.20.04.1) focal; urgency=medium
* Initial release (LP: #1887674).
-- Alberto Milone Tue, 14 Jul 2020
10:12:39 +0200
** Changed in: nvidia-grap
This bug was fixed in the package linux-azure - 5.4.0-1026.26
---
linux-azure (5.4.0-1026.26) focal; urgency=medium
* focal/linux-azure: 5.4.0-1026.26 -proposed tracker (LP: #1894641)
* Mellanox Check For Write Combining Support (LP: #1874503)
- IB/mlx5: Align usage of QP1 cr
This bug was fixed in the package linux - 4.4.0-190.220
---
linux (4.4.0-190.220) xenial; urgency=medium
* xenial/linux: 4.4.0-190.220 -proposed tracker (LP: #1893431)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* [Hyper-V] VSS and File Copy daem
This bug was fixed in the package linux-azure - 5.4.0-1026.26
---
linux-azure (5.4.0-1026.26) focal; urgency=medium
* focal/linux-azure: 5.4.0-1026.26 -proposed tracker (LP: #1894641)
* Mellanox Check For Write Combining Support (LP: #1874503)
- IB/mlx5: Align usage of QP1 cr
This bug was fixed in the package linux-azure - 5.4.0-1026.26
---
linux-azure (5.4.0-1026.26) focal; urgency=medium
* focal/linux-azure: 5.4.0-1026.26 -proposed tracker (LP: #1894641)
* Mellanox Check For Write Combining Support (LP: #1874503)
- IB/mlx5: Align usage of QP1 cr
This bug was fixed in the package linux-azure - 5.4.0-1026.26
---
linux-azure (5.4.0-1026.26) focal; urgency=medium
* focal/linux-azure: 5.4.0-1026.26 -proposed tracker (LP: #1894641)
* Mellanox Check For Write Combining Support (LP: #1874503)
- IB/mlx5: Align usage of QP1 cr
This bug was fixed in the package nvidia-graphics-drivers-450 -
450.66-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-450 (450.66-0ubuntu0.18.04.1) bionic; urgency=medium
* Initial release (LP: #1887674).
-- Alberto Milone Tue, 14 Jul 2020
10:12:39 +0200
** Changed in: nvidia-gra
This bug was fixed in the package linux - 4.4.0-190.220
---
linux (4.4.0-190.220) xenial; urgency=medium
* xenial/linux: 4.4.0-190.220 -proposed tracker (LP: #1893431)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* [Hyper-V] VSS and File Copy daem
The verification of the Stable Release Update for nvidia-graphics-
drivers-450 has completed successfully and the package is now being
released to -updates. Subsequently, the Ubuntu Stable Release Updates
Team is being unsubscribed and will not receive messages about this bug
report. In the event
@sil2100
I'll create MP to Debian.
I'll notify you once my MP is ready.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1896419
Title:
Comet Lake CPUID family:model:stepping 0x6:a5:2
Thanks @mkaya387 that worked prefectly for me.
I understand that chattr is the command in the GNU operating system
(with Linux kernel) that allows a user to set certain attributes of a
file.
But can you elaborate on your solution of this issue?
--
You received this bug notification because you
I just verified if the patch/commit also landed in groovy and it did.
Hence updating the groovy entry to Fix Released and with that the entire case.
** Changed in: linux (Ubuntu Groovy)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fi
** Changed in: linux (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
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/1891454
Title:
[UBUNTU 20.04] kernel: s390/cpum_cf,perf:
I just verified if the patches/commits are in groovy master-next and they are.
Hence updating the groovy entry to Fix Released as well - and with that the
entire case.
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Fix Released
** Changed in: ubuntu-z-systems
Status: I
** Changed in: hwe-next
Status: New => Fix Released
--
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/1867704
Title:
alsa/hdmi: support nvidia mst hdmi/dp audio
Status in HWE Ne
** Changed in: linux-oem-5.6 (Ubuntu)
Status: Triaged => Fix Released
** Changed in: hwe-next
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.n
This bug was fixed in the package linux-azure - 4.15.0-1096.106~16.04.1
---
linux-azure (4.15.0-1096.106~16.04.1) xenial; urgency=medium
* xenial/linux-azure: 4.15.0-1096.106~16.04.1 -proposed tracker (LP:
#1894681)
[ Ubuntu: 4.15.0-1096.106 ]
* bionic/linux-azure-4.15: 4.15.0
This bug was fixed in the package linux-azure - 4.15.0-1096.106~16.04.1
---
linux-azure (4.15.0-1096.106~16.04.1) xenial; urgency=medium
* xenial/linux-azure: 4.15.0-1096.106~16.04.1 -proposed tracker (LP:
#1894681)
[ Ubuntu: 4.15.0-1096.106 ]
* bionic/linux-azure-4.15: 4.15.0
I see there are problems with this patch.
Any chance to solve this bug?
--
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/1861554
Title:
Radeon mobility HD3450 (RV620) heavy screen flickeri
This bug was fixed in the package linux-azure - 4.15.0-1096.106~16.04.1
---
linux-azure (4.15.0-1096.106~16.04.1) xenial; urgency=medium
* xenial/linux-azure: 4.15.0-1096.106~16.04.1 -proposed tracker (LP:
#1894681)
[ Ubuntu: 4.15.0-1096.106 ]
* bionic/linux-azure-4.15: 4.15.0
This bug was fixed in the package linux - 5.4.0-48.52
---
linux (5.4.0-48.52) focal; urgency=medium
* focal/linux: 5.4.0-48.52 -proposed tracker (LP: #1894654)
* mm/slub kernel oops on focal kernel 5.4.0-45 (LP: #1895109)
- SAUCE: Revert "mm/slub: fix a memory leak in sysfs_s
This bug was fixed in the package linux-azure - 4.15.0-1096.106~16.04.1
---
linux-azure (4.15.0-1096.106~16.04.1) xenial; urgency=medium
* xenial/linux-azure: 4.15.0-1096.106~16.04.1 -proposed tracker (LP:
#1894681)
[ Ubuntu: 4.15.0-1096.106 ]
* bionic/linux-azure-4.15: 4.15.0
This bug was fixed in the package linux-hwe - 4.15.0-118.119~16.04.1
---
linux-hwe (4.15.0-118.119~16.04.1) xenial; urgency=medium
* xenial/linux-hwe: 4.15.0-118.119~16.04.1 -proposed tracker (LP:
#1894696)
[ Ubuntu: 4.15.0-118.119 ]
* bionic/linux: 4.15.0-118.119 -proposed tr
1 - 100 of 165 matches
Mail list logo
