You can usually replicate that behavior by starting a few guests and
instead of shutdown stopping the libvirt-guests service.
If that works in your case as well it will easen having a look, so let
me ask does that work for you?
--
You received this bug notification because you are a member of Ker
These firmware blobs are excluded from the package because current
kernels don't reference them. What kernel are you running and what HW do
you have that needs it?
Please run 'apport-bug 1986743' on the affected machine.
--
You received this bug notification because you are a member of Kernel
Pa
Oh it's a staging driver that wants it.
--
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/1986743
Title:
REQUEST add meson vdec firmware to arm64 linux-firmware package
Status in
apport information
** Tags added: apport-collected jammy
** Description changed:
During boot, cryptsetup fails to decrypt the root partition in a,
seemingly, non-deterministic fashion. I know that the password is
correct and that the keymap is not a fault either, because I have
specifica
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1986623/+attachment/5609248/+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
** Also affects: linux-hwe-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-5.17 (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux (Ubuntu Kinetic)
Status: In Progress => Fix Committed
** Changed in: linux-hwe-5.17 (Ubuntu Jammy)
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1986623/+attachment/5609249/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "fstab.txt"
https://bugs.launchpad.net/bugs/1986623/+attachment/5609250/+files/fstab.txt
--
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/1986623
** Also affects: linux-hwe-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-5.17 (Ubuntu)
Status: New => Invalid
** Changed in: linux-hwe-5.17 (Ubuntu Jammy)
Status: New => In Progress
** Also affects: linux-allwinner-5.17 (Ubuntu)
Importance: U
** Also affects: linux-starfive-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-starfive-5.17 (Ubuntu)
Status: New => Invalid
** Changed in: linux-starfive-5.17 (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because y
Enable -proposed channel on HP 440/450/640/650 G9 and install
5.14.0-1049-oem, mic mute and audio mute LEDs work fine on it.
** 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.
** Changed in: linux-starfive-5.17 (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-hwe-5.17 (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-allwinner-5.17 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received t
The upstream driver is broken in that it doesn't use the MODULE_FIRMWARE
macro.
** Also affects: linux-firmware (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-firmware (U
Public bug reported:
1. Power on SUT and boot into UEFI setup.
2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC
NVMe RAID disk.
4. Boot into OS then check system logs to check if there are a
if intel vmd feature is disabled, it has "BAR 13: failed to assign"
message in the syslog.
** Attachment added: "20220803_disable_VMD_logs.zip"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986792/+attachment/5609273/+files/20220803_disable_VMD_logs.zip
--
You received this bug notif
If the vmd feature is enabled, the messsage will be showed in syslog.
** Attachment added: "syslog dmesg kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986792/+attachment/5609272/+files/dmesg%2C%20syslog%2C%20and%20kern.log.zip
--
You received this bug notification because
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 1986792
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
[Impact]
Compiler warns unused variable after commit 0c1d6921b07c ("UBUNTU:
SAUCE: drm/i915/display/psr: Reinstate fix for TGL + AUO panel flicker")
[Fix]
The variable is unused, remove it.
[Test]
Compiler no longer warns about it.
[Where problems could occur]
Nothing.
**
** Changed in: linux-azure-cvm (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-azure-cvm in Ubuntu.
https://bugs.launchpad.net/bugs/1981328
Title:
Azure: Fix the Focal Azu
Thanks for the note. I will send a patch upstream to fix the
MODULE_FIRMWARE situation.
--
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/1986743
Title:
REQUEST add meson vdec firm
I can verify the fix is working with the released 5.15.0-43.46
--
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/1978820
Title:
Jammy Charmed OpenStack deployment fails over connectivity is
Hi Conie,
can you please run `apport-collect 1986792` as requested in comment #3
for this bug?
Thanks
Jeff
--
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/1986792
Title:
There are faile
Small addition:
perhaps not clear from above:
The most visable issue, no wireless interface shows up , neither with ifconfig
-a, nor with iwconfig (for rtl8188eu on 5.17 oem kernel)
regards,
Arjan
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
Public bug reported:
[Impact]
The 5.19 kernel contains support for the PolarFire Icicle board. But
booting with linux-image-5.19.0-1002-generic_5.19.0-1002.2_riscv64.deb
fails.
The cause is that the device-tree incorrectly specifies the PLIC
interrupts used for the drivers/soc/sifive/sifive_l2_c
Public bug reported:
SRU Justification
[Impact]
The inclusion of the DKMS module v4l2loopback requires videodev
infrastructure. It is easier to use if these modules are included by
default in linux-modules-aws.
[Test Plan]
Extract linux-modules-aws and check for the presence of videodev.ko
[W
** Changed in: linux (Ubuntu Jammy)
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/1986470
Title:
linux-aws: Move zram to linux-modules
Statu
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
This happened to me when I upgraded from 20.04 to 22.04
I have had to do this manually as I don't think any of the command lines are
correct above. I actually lost my graphic interface in the process.
So at black screen I started a new TTY (Ctr alt F2)
I have gone to the folder
/var/lib/dpkg
I cop
** Changed in: linux-aws (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-aws (Ubuntu Kinetic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
The Kernel Packages team already owns the firmware-sof package. Ubuntu
Package Archive Administrators, please promote the package to the main
component in Ubuntu 22.04 and Kinetic.
** Changed in: firmware-sof (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because
** Package changed: linux (Ubuntu Jammy) => linux-aws (Ubuntu Jammy)
--
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/1986470
Title:
linux-aws: Move zram to linux-modules
Status in li
** Changed in: linux-aws (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-aws (Ubuntu Kinetic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
By the way, Debian created a new component, non-free-firmware, last
month. I don't believe any Debian packages have switched to it yet.
Based on this bug history, I'm guessing we'd want to automatically
import those packages to universe then (or main where we want it part of
our Canonical-supported
Public bug reported:
Backport the support for SMBIOS 3.4 and 3.5 specifications
in Ubuntu Kinetic (dmidecode 3.4) to Jammy (dmidecode 3.3)
to enable new hardware in the LTS release per SRU policy [1].
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases
** Affects: dmidecode (Ubuntu
This is also affecting the MSI MEG Z690I Unify motherboard; can not boot
any live disk images of Ubuntu 22.04
--
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/1842320
Title:
Can't boot: "e
Public bug reported:
The fan does not work in either the current version of ubuntu or
previous (focal fossa). it was working a few months ago, so this may be
new to this kernel, i didn't discover when it stopped working directly
:(
symptoms: gets very hot. no fan. eventually blackscreens while
** Description changed:
Backport the support for SMBIOS 3.4 and 3.5 specifications
in Ubuntu Kinetic (dmidecode 3.4) to Jammy (dmidecode 3.3)
to enable new hardware in the LTS release per SRU policy [1].
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Other_safe_cases
+
+ P.S.: SRU te
You have been subscribed to a public bug:
Operating system data:
Linux 5.15.0-46-generic #49-Ubuntu SMP Thu Aug 4 18:03:25 UTC 2022
x86_64 x86_64 x86_64 x86_64 GNU/Linux
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Just installed. When testing Ubuntu there was no problem.
Device data:
Dell
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/1986857
Title:
fan doesn't work
Status in li
** Package changed: ubuntu => linux (Ubuntu)
** Tags added: focal jammy
--
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/1986740
Title:
Black screen with lines when booting kernel 5.14 to
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 1986740
and then change the status of the bug to 'Confirmed'.
If, due to the nature
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
Makefile: link with -z noexecstack --no-warn-rwx-segments
x86: link vdso and boot with -z noexecstack --no-warn-rwx-segments
Revert "pNFS: nfs3_set_ds_client should set NFS_CS_NOPING"
scsi: Revert "scsi: qla2xxx: Fix disk failure to rediscover"
pNFS/flexfiles: Report RDMA connection errors to the s
** Changed in: linux (Ubuntu Kinetic)
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/1986865
Title:
Kinetic update: v5.19.2 upstream stable re
** Changed in: linux (Ubuntu Kinetic)
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/1986848
Title:
Kinetic update: v5.19.1 upstream stable re
Override component to main
firmware-sof 2.1.1-1ubuntu1 in kinetic: restricted/misc -> main
firmware-sof-signed 2.1.1-1ubuntu1 in kinetic amd64:
restricted/kernel/optional/100% -> main
firmware-sof-signed 2.1.1-1ubuntu1 in kinetic arm64:
restricted/kernel/optional/100% -> main
firmware-sof-signed
Same Problem here.
Using 22.04.1 LTS with 5.15.0-47-generic on Acer Aspire E 17 Laptop, because I
turned off plymouth I see the system hanging after displaying:
shutdown[1]: Rebooting
kvm: exiting hardware virtualization
ctrl+alt+SysReq+b works!
--
You received this bug notification because yo
This was also detected by autopkgtests:
https://autopkgtest.ubuntu.com/packages/v/vrms/kinetic/amd64
** Changed in: amd64-microcode (Ubuntu)
Importance: Undecided => High
** Changed in: amd64-microcode (Ubuntu)
Status: Confirmed => Triaged
** Also affects: linux-firmware (Ubuntu)
Im
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1986740
Title:
Black screen with lines when booting kernel 5.14 to 5.1
Public bug reported:
I have a recurring crash.
It does not record MCE information to the log file, but is presented on
the screen during the next boot.
I can recreate the problem.
1) Start a steam game
2) Close the game
3) Let the monitor sleep
4) Wake up the computer and start the game
*) It w
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 1986887
and then change the status of the bug to 'Confirmed'.
If, due to the nature
apport information
** Tags added: apport-collected
** Description changed:
I have a recurring crash.
It does not record MCE information to the log file, but is presented on
the screen during the next boot.
I can recreate the problem.
1) Start a steam game
2) Close the game
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1986887/+attachment/5609474/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1986887/+attachment/5609476/+files/IwConfig.txt
--
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/19
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1986887/+attachment/5609477/+files/Lspci.txt
--
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/1986887
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1986887/+attachment/5609482/+files/Lsusb-v.txt
--
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/1986
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1986887/+attachment/5609479/+files/Lsusb.txt
--
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/1986887
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1986887/+attachment/5609484/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1986887/+attachment/5609483/+files/PaInfo.txt
--
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/1986887
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1986887/+attachment/5609486/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1986887/+attachment/5609478/+files/Lspci-vt.txt
--
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/19
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1986887/+attachment/5609481/+files/Lsusb-t.txt
--
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/1986
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1986887/+attachment/5609491/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, whic
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1986887/+attachment/5609488/+files/RfKill.txt
--
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/1986887
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1986887/+attachment/5609490/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1986887/+attachment/5609489/+files/UdevDb.txt
--
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/1986887
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1986887/+attachment/5609485/+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
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1986887/+attachment/5609487/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
You have been subscribed to a public bug:
1. Power on SUT and boot into UEFI setup.
2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC
NVMe RAID disk.
4. Boot into OS then check system logs to
Public bug reported:
1. Power on SUT and boot into UEFI setup.
2. Enable VMD then reboot SUT and enter UEFI setup to create VROC NVMe RAID 0.
3. Install Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) on the VROC
NVMe RAID disk.
4. Boot into OS then check system logs to check if there are a
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 1986907
and then change the status of the bug to 'Confirmed'.
If, due to the nature
This memcg_test_3 failure on ARM64 instances is no longer causing
cgroup_fj_* test to fail, it just timeout with 30 seconds threshold.
Will need to test it again manually.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
@Colette, it's ok to grab the latest thermald from Debian.
thanks and Im preparing the 2.5.0 for ubuntu.
** Changed in: thermald (Ubuntu)
Assignee: (unassigned) => koba (kobako)
** Changed in: thermald (Ubuntu)
Status: New => In Progress
--
You received this bug notification because
** Tags added: kern-4195
--
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/1986796
Title:
amd64-microcode conflicts with linux-firmware
Status in amd64-microcode package in Ubuntu
** Tags added: kern-4194
--
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/1986743
Title:
REQUEST add meson vdec firmware to arm64 linux-firmware package
Status in linux-firmware
I shall confirm that after the fix mentioned above, my trackpad has been
working very well.
I think that is a software issue.
I have some suggestions to try:
- verify if this issue happens also in windows?
- try update all drivers using the tools provided by Lenovo
- maybe update BIOS
- in Windows
76 matches
Mail list logo
