When started with option -i, ntfsresize only evaluates the minimal size
needed for the stored data. There may be a subsequent ntfsresize to
actually do some resizing, which might not be run when you kill the
parent process.
--
You received this bug notification because you are a member of Kernel
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1948767/+attachment/5536630/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1948767/+attachment/5536631/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.ne
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1948767/+attachment/5536629/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1948767/+attachment/5536621/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1948767/+attachment/5536618/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.ne
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1948767/+attachment/5536617/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.laun
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1948767/+attachment/5536625/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1948767/+attachment/5536616/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/19
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1948767/+attachment/5536620/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.ne
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1948767/+attachment/5536627/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1948767/+attachment/5536623/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1948767/+attachment/5536622/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1948767/+attachment/5536624/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1948767/+attachment/5536626/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1948767/+attachment/5536628/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1948767/+attachment/5536619/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Tags added: apport-collected focal
** Description changed:
[SRU Justification]
[Impact]
Few recent AMD systems shows "snd_hda_intel :00:1f.3: azx_get_response
timeout" and fail to detect the HDMI/DP audio output device when connects to
external monitor. It wi
It seems that installing the 495 drivers from the Nvidia website has
fixed this issue for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1947432
Title:
[HP OMEN
You can also apply the fix manually be editing
/lib/systemd/system/bluetooth.service and changing:
#Restart=on-failure
to
Restart=on-failure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net
** 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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1945967
Title:
rtw89 kernel module for Realtek 8
** Tags removed: originate-from-1943787
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1949026
Title:
System hangs on purple screen
Status in OEM Priority Project:
Public bug reported:
We are facing an issue that GDM starts with Wayland instead of Xorg,
despite of 61-gdm.rules' gdm-disable-wayland for NVIDIA graphics.
The issue happens because gdm-disable-wayland is executed after GDM has
started. The reason why the udev rules takes so long is because the t
(Or Ubuntu systems post-fix but with pools created while the bug was
active - and is there a fix possible, or is it "make a new pool"? Is
there a diagnostic possible to be sure either way?)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to z
It appears BlueZ upstream does not restart on failure, but in Ubuntu we
turned on restart-on-failure in version 5.53-0ubuntu3. I suggest the
best way to get that fix right now is to upgrade to Ubuntu 20.04.
** Changed in: bluez (Ubuntu)
Status: New => Fix Released
--
You received this bug
I don't think the GUI is meant to start bluetoothd at all. It only
toggles the power state of the Bluetooth hardware. It assumes bluetoothd
is always running. So failure to restart after a crash is a problem with
bluez's systemd scripting.
** Package changed: gnome-control-center (Ubuntu) => bluez
You have been subscribed to a public bug:
I had bluetooth crash (see logs below). After the crash, I attempted to
restart bluetooth by pressing the On/Off switch in the top-right of the
Bluetooth tab of gnome-control-center (it was set to off). After
pressing the switch, the switch read "On", bu
Stefan, do filesystems affected by this need to be rebuilt in order to
be used by other OpenZFS distributions or releases of Ubuntu that
predate the introduction of the bug?
Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux
** Tags added: impish
** Description changed:
In KUbuntu 21.10, most media buttons in my bluetooth headphones stopped
working. This includes the "play/pause" button, "play next" (calls after
long press of volume increase), and "play previous" (long press of
volume decrease). The volume +/
This causes an AX201 iwlwifi firmware regression filed in
https://bugs.launchpad.net/somerville/+bug/1948949.
** Tags removed: verification-needed-focal
** Tags added: verification-failed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Tags added: psr
--
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/1937072
Title:
[Lenovo Yoga Slim 7 14IIL05] PSR causes incomplete screen redraws
Status in linux package in Ubuntu:
T
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
*** This bug is a duplicate of bug 1949009 ***
https://bugs.launchpad.net/bugs/1949009
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demons
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
*** This bug is a duplicate of bug 1949007 ***
https://bugs.launchpad.net/bugs/1949007
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demons
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** 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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1941893
Title:
Improve performance and idle powe
** 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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1945361
Title:
[Yellow Carp] USB4 interdomain co
** Changed in: zfs-linux (Ubuntu)
Assignee: Colin Ian King (colin-king) => (unassigned)
** Changed in: zfs-linux (Ubuntu Impish)
Assignee: Colin Ian King (colin-king) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Changed in: linux (Ubuntu Focal)
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/1947885
Title:
Focal update: v5.4.149 upstream stable relea
** Changed in: linux (Ubuntu Focal)
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/1947886
Title:
Focal update: v5.4.150 upstream stable relea
** Changed in: linux (Ubuntu Focal)
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/1947888
Title:
Focal update: v5.4.151 upstream stable relea
This bug is awaiting verification that the linux-oem-5.13/5.13.0-1018.22
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 exist
** Changed in: linux (Ubuntu Hirsute)
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/1947781
Title:
Hirsute update: upstream stable patchset 2
This bug is awaiting verification that the linux-oem-5.13/5.13.0-1018.22
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 exist
** Changed in: linux (Ubuntu Hirsute)
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/1948873
Title:
Hirsute update: upstream stable patchset 2
** Changed in: linux (Ubuntu Impish)
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/1947191
Title:
Impish update: v5.13.19 upstream stable rel
** Changed in: linux (Ubuntu Impish)
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/1948485
Title:
Impish update: upstream stable patchset 202
** Changed in: linux (Ubuntu Impish)
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/1948977
Title:
Impish update: upstream stable patchset 202
1) I do NOT know how to retrieve the ntfsresize options.
2) In order to retrieve file system metadata in the attached 'ntfsinfo.log'
file, I used following command :
$ for dev in $(sudo blkid -o device -t TYPE=ntfs); do sudo ntfsinfo -fm
"$dev"; echo; done
** Attachment added: "File system
This bug is awaiting verification that the linux-azure-
cvm/5.4.0-1063.66+cvm2 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 stil
This bug is awaiting verification that the linux-azure-
cvm/5.4.0-1063.66+cvm2 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 stil
@randomdave, in case you didn't, i think you have to disable the
trackpoint as well as the trackpad.
some people have reported that just disabling the trackpoint but leaving
the trackpad enabled works, but you lose the trackpad buttons and have
to configure tap-to-click.
for others it only works
Exact package causing the issue is not obvious, but I add bluez.
** Package changed: ubuntu => bluez (Ubuntu)
--
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/1948877
Title:
Bluetooth hea
You have been subscribed to a public bug:
In KUbuntu 21.10, most media buttons in my bluetooth headphones stopped
working. This includes the "play/pause" button, "play next" (calls after
long press of volume increase), and "play previous" (long press of
volume decrease). The volume +/- buttons the
This bug was fixed in the package linux-intel-5.13 - 5.13.0-1007.7
---
linux-intel-5.13 (5.13.0-1007.7) focal; urgency=medium
* focal/linux-intel-5.13: 5.13.0-1007.7 -proposed tracker (LP:
#1946503)
* [iotg][tgl][tgl-aaeon] 20211006 image does not boot (LP: #1946223)
- Revert
No, "pcie_aspm=off" does not help.
I also tried uninstalling broadcom-sta-dkms. It blacklists the b44
module via /etc/modprobe.d/broadcom-sta-dkms.conf and also
https://wiki.debian.org/wl says that b44 is incompatible with wl. This
did not help either.
My laptop seems fine with just having the b4
This bug was fixed in the package linux-intel-5.13 - 5.13.0-1007.7
---
linux-intel-5.13 (5.13.0-1007.7) focal; urgency=medium
* focal/linux-intel-5.13: 5.13.0-1007.7 -proposed tracker (LP:
#1946503)
* [iotg][tgl][tgl-aaeon] 20211006 image does not boot (LP: #1946223)
- Revert
This bug was fixed in the package linux-intel-5.13 - 5.13.0-1007.7
---
linux-intel-5.13 (5.13.0-1007.7) focal; urgency=medium
* focal/linux-intel-5.13: 5.13.0-1007.7 -proposed tracker (LP:
#1946503)
* [iotg][tgl][tgl-aaeon] 20211006 image does not boot (LP: #1946223)
- Revert
This bug was fixed in the package linux-intel-5.13 - 5.13.0-1007.7
---
linux-intel-5.13 (5.13.0-1007.7) focal; urgency=medium
* focal/linux-intel-5.13: 5.13.0-1007.7 -proposed tracker (LP:
#1946503)
* [iotg][tgl][tgl-aaeon] 20211006 image does not boot (LP: #1946223)
- Revert
This bug was fixed in the package linux-intel-5.13 - 5.13.0-1007.7
---
linux-intel-5.13 (5.13.0-1007.7) focal; urgency=medium
* focal/linux-intel-5.13: 5.13.0-1007.7 -proposed tracker (LP:
#1946503)
* [iotg][tgl][tgl-aaeon] 20211006 image does not boot (LP: #1946223)
- Revert
This bug was fixed in the package linux-intel-5.13 - 5.13.0-1007.7
---
linux-intel-5.13 (5.13.0-1007.7) focal; urgency=medium
* focal/linux-intel-5.13: 5.13.0-1007.7 -proposed tracker (LP:
#1946503)
* [iotg][tgl][tgl-aaeon] 20211006 image does not boot (LP: #1946223)
- Revert
@Etienne - agree, probably a dupe
@Jeremy - I ran "ntfsresize -f -i /dev/sda4" manually before the
installer ran and ntfsresize had no issue. Later during this same run,
I saw the hang when ntfsresize was run by Ubiquity.
@Jean-Pierre - I suspect this is a kernel bug more than I suspect a
ntfsre
For future reference, this bug has been reported in Ubuntu KVM hosts
outside of the specific kdump test scenario (i.e. when running actual
VMs in production-like setups). The "kdump with multiple CPUs" case was
discovered as an alternative that hits the same MMU context bug, without
needing complex
Our serves are affected by this bug too in focal and it triggered today
in one of our servers.
Distributor ID: Ubuntu
Description: Ubuntu 20.04.3 LTS
Release: 20.04
Codename: focal
We have seen this in:
- Ubuntu 5.4.0-89.100-generic
- Ubuntu 5.4.0-88.99-generic
--
You received this bug notifica
I have the same hardware as rudolfharney. Kernel panic still happening
in linux-image-5.13.0-20-generic even after rudulf's suggestion "start
BIOS, exit with SAVE=YES". Also, disabling the trackpad doesn't prevent
the panic.
--
You received this bug notification because you are a member of Kernel
I have no idea why the status has changed ... the fix hasn't entered the
archive yet.
** Changed in: linux-raspi (Ubuntu Impish)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in U
** Changed in: linux-raspi (Ubuntu Impish)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1946368
Title:
HDMI output freezes under curr
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
Experiencing the same problem after upgrade to Impish. I have determined
that the desktop does actually start after a resume from suspend, but
the screen remains blank, with the backlight on. (To determine this, I
used a keyboard shortcut to launch a terminal window and typed a reboot
command succe
hirsute linux-aws 5.11.0-1021.22 i3.metal,i3en.24xlarge,r5.metal
** Tags added: sru-20211018
--
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/1830585
Title:
cpuset_memory_spread fro
Problem fixed with release of linux-oem-5.14.0-1006
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1948610
Title:
Home directory not recognized
Status in linux-meta-oem-5.
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
--
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/194
Seen with aws 5.11.0-1021.22 on m5a.large and r5.metal
** Tags added: aws sru-20211018
--
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/1929247
Title:
kernel/selftests: seccomp_benchm
Public bug reported:
The nvidia-driver-XXX-server meta-package "Recommends" nvidia-settings.
I think it would be better to demote nvidia-settings to a "Suggests" for
these packages because of all the following:
- The Ubuntu default behavior is to install "recommended" packages.
- The -server pack
You have been subscribed to a public bug:
The nvidia-driver-XXX-server meta-package "Recommends" nvidia-settings.
I think it would be better to demote nvidia-settings to a "Suggests" for
these packages because of all the following:
- The Ubuntu default behavior is to install "recommended" package
To confirm running kernel 5.11.0.27
--
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/1948958
Title:
No Wi-fi device found
Status in linux package in Ubuntu:
Incomplete
Bug description:
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 1948958
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
P14s Gen 2 running 20.04.3 doesn't find Wi-Fi and only ethernet works.
Tested fine on 21.4 and 21.10 however devices need to be on LTS.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification because you are a
I am seeing a similar issue with a second monitor plugged in. I am
using nouveau and it crashes the X server and logs me out. I have
attached a log of what happened. This is NOT connected with a screen
lock, it happens randomly.
Display is:
*-display
description: VGA c
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe-5.8 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.8 in Ubuntu.
https://bug
This still exist. Maybe we can help somehow to resolve it?
Linux insspb-kubuntu 5.4.0-89-generic #100-Ubuntu SMP Fri Sep 24
14:50:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
root@insspb-kubuntu:/home/insspb# xrandr
The reverts are in the latest firmware tree:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu?id=d7b50e61669dc137924337d03d09b8986eb752a3
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/amdgpu?id=d843e520a4b0d92b986645548d1
Same issue with Lenovo ThinkPad E15 Gen 2, AMD Ryzen 7 4700u with radeon
graphics × 8 (AMD Renoir graphic).
stable workaround: start BIOS, exit with SAVE=YES (don't need to change
anything).
A (better) solution would be highly appreciated. Thank you!
--
You received this bug notification becaus
I had exact same issue on ubuntu 20.04 with same system "lenovo yoga slim7
14IIL05"
Putting "i915.enable_psr=0" to GRUB_CMDLINE_LINUX_DEFAULT fixed issues such as
rendering, screen tearing, delaying.
--
You received this bug notification because you are a member of Kernel
Packages, which is sub
** Description changed:
Update the NVIDIA series and introduce the new 495 series in Bionic,
Focal, Hirsute, and Impish.
[Impact]
These releases provide both bug fixes and new features, and we would like to
make sure all of our users have access to these improvements.
See the cha
** Description changed:
[Impact]
When kexec'ing into a crash kernel with ncpus > 1, VMs can raise a KVM
emulation failure. This will cause the VM to go into the "paused" state, and
prevents it from being restored without a full VM restart.
This happens only when there are multiple enabl
VERIFICATION FOCAL
Installed makedumpfile from proposed.
Testing on a Focal machine running 5.11 kernel.
# uname -rv
5.11.0-40-generic #44~20.04.1-Ubuntu SMP Wed Oct 20 19:04:34 UTC 2021
Trigger crash:
# echo 1 > /proc/sys/kernel/sysrq
# echo c > /proc/sysrq-trigger
After reboot contents of /v
VERIFICATION ON FOCAL
Installed makedumpfile from proposed.
Testing on a Focal machine running 5.11 kernel.
# uname -rv
5.11.0-40-generic #44~20.04.1-Ubuntu SMP Wed Oct 20 19:04:34 UTC 2021
Trigger crash:
# echo 1 > /proc/sys/kernel/sysrq
# echo c > /proc/sysrq-trigger
>From console output :
** Description changed:
[Impact]
When kexec'ing into a crash kernel with ncpus > 1, VMs can raise a KVM
emulation failure. This will cause the VM to go into the "paused" state, and
prevents it from being restored without a full VM restart.
This happens only when there are multiple enabl
** Tags added: sru-20211018
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1928890
Title:
vrf_route_leaking.sh in net from ubuntu_kernel_selftests linux ADT
test failure with
** Tags added: aws sru-20211018
--
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/1871015
Title:
test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed
with H (Check VM connec
** Information type changed from Private to Public
** Description changed:
- Update the NVIDIA drivers October 2021
+ Update the NVIDIA series in Bionic, Focal, Hirsute.
+
+ [Impact]
+ These releases provide both bug fixes and new features, and we would like to
+ make sure all of our users have
1 - 100 of 133 matches
Mail list logo
