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/2039339
Title:
package linux-headers-generic-
Public bug reported:
"Informats"
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-headers-generic-hwe-22.04 5.15.0.43.44
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux 5.15.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevic
quick google search comes up with:
https://falco.org/docs/event-sources/kernel/
https://medium.com/@lumontec/some-freshness-with-linux-security-modules-and-ebpf-676ac363a135
https://blog.aquasec.com/linux-security-with-tracee-and-ebpf
https://www.infoq.com/presentations/facebook-google-bpf-linux-k
[Expired for zfs-linux (Ubuntu) because there has been no activity for
60 days.]
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.laun
The issue won't occur in Lunar. It's only specifically a problem with gdm when
a kernel has been configured this way.
It's not a problem in Jammy yet, but will be a problem when such a kernel gets
backported as HWE.
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: Ne
** Changed in: linux-gcp-5.15 (Ubuntu Focal)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2037087
Title:
TCPDirect patches
Status in linux
i try with linux-meta (5.15.0.88.85) kernel and the problem are present
too
--
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/2039334
Title:
Intel usb problem with gamepad device descr
** Attachment added: "lsub.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2039334/+attachment/5709309/+files/lsub.txt
** Also affects: linux-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
P
@daniel can you post the exit of command sudo lsusb -v please. I
recently report this bug
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2039334
maybe are releated
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2
Public bug reported:
In last kernel my xbox chinese gamepad no are detected in other pc with other
hardware work i think are releated with:
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Because same occurs in other pc with intel processor
uname -a
Linux PC 6.2.0-34-g
This has been marked as fixed in mantic, but this bug does not say what
the plan is for lunar, which is still the supported upgrade path from
jammy.
** Changed in: gdm3 (Ubuntu Jammy)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kerne
Paolo's merge request has been applied in qa-regression-testing, thanks!
** Changed in: qa-regression-testing
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchp
The firmware-sof upload in lunar-proposed contains a sha256sum.txt with
the checksums of all the firmware. But every line of this file is
different from every line in the previous version, because the version
number is encoded. Likewise, the file paths within the package encode
the version. This
** Description changed:
- SRU Jusitification for firmware-sof
+ SRU Justification for firmware-sof
[Impact]
To support Smart Amplifier IC ALC1319D, it requires sof-bin v2.2.6
[Fix]
Pull sof-bin v2.2.6 and for the completeness pull in v2.2.5, too
[Test Case]
Install the fixes o
Public bug reported:
sdhci-dwcmshc MLNXBF30:00: __mmc_blk_ioctl_cmd: data error -110
SRU Justification:
[Impact]
This change is needed to avoid intermittent "sdhci-dwcmshc MLNXBF30:00:
__mmc_blk_ioctl_cmd: data error -110" error under stress test
[Fix]
The fix added a quirk for the BF3 sdhci d
Public bug reported:
The new 6.5 kernel in mantic causes a large amount of UBSAN warnings at
boot when using bcache (see attached dmesg log, truncated after last
error). The volume still mounts fine and I haven't observed any data
corruption.
There seems to have been some discussion about this on
Same release but GPU is a 7900 XTX
--
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/2039313
Title:
After installing latest version of linux-firmware system doesn't boot
Status in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: iproute2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
ht
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.
kernel log from boot
** Attachment removed: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2009952/+attachment/5709257/+files/kern.log
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2009952/+attachment/5709262/+files/k
Public bug reported:
I've encountered the issue after installing a new kernel and so forth
using apt-get upgrade. I've isolated the issue by rolling back the
system and installing every package one by one. When I install linux-
firmware it hangs I think when it wants to start the gpu.
Can boot in
DRI device 0 DMCUB F/W version: 0x08002300
○ PSR 2 with Y coordinates (eDP 1.4a) [3]
○ Sink OUI: Parade
○ resv_40f: 01
○ ID String: 08-03
○ PSR Status: 00-00-02
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2009952/+attachment/5709257/+files/kern
I verified the issue on kernel linux/5.4.0-166.183, linux/5.15.0-88.98
and linux/6.2.0-36.37 and the issue is fixed. I was able to run enclave
in debug mode in all 3 kernels.
** Tags removed: verification-needed-lunar-linux
** Tags added: verification-done-lunar-linux
--
You received this bug no
** Tags removed: verification-needed-jammy-linux
** Tags added: verification-done-jammy-linux
--
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/2034745
Title:
[regression] Unable to initial
What is the easiest way to share kernel log :) ?
dmesg > dmesg.log ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2009952
Title:
[amdgpu][psr] Screen flickering/ tearing on 6.1
** Tags removed: verification-needed-focal-linux
** Tags added: verification-done-focal-linux
--
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/2034745
Title:
[regression] Unable to initial
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
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/2038542
Title:
package linux-tools-5.15.0-83
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1043.49~20.04.1 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-linux-
intel-iotg-5.15' to 'verification-
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1043.49~20.04.1 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-linux-
intel-iotg-5.15' to 'verification-
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1043.49~20.04.1 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-linux-
intel-iotg-5.15' to 'verification-
Can you please share your kernel log from a boot that had the failure, and
without that parameter in place share the output of this script?
https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/psr.py
--
You received this bug notification because you are a member of Kernel
Packages, which
I have a similar problem with Xubuntu and kernel version linux-
image-6.5.0-9-generic. Adding "amdgpu.dcdebugmask=0x10" to
/etc/default/grub fixes the flickering screen.
OS: Xubuntu 23.10 x86_64
21F8003HMX ThinkPad T14s Gen 4
CPU: AMD Ryzen 7 PRO 7840U w/ Radeon
--
You received this bug notifica
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/2039280
Title:
Support IP address protocol
Status in iproute2 package in Ubuntu:
** Description changed:
+ SRU Justification
- 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
+
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
Can you test the newest from -proposed (166) to confirm it is not the
same bug? It's not TCG indeed but for now, I don't have other ideas.
Will continue looking into it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
** Also affects: iproute2 (Ubuntu Mantic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/2039280
Title:
Su
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/2039288
Title:
package linux-headers-6.2.0-34
Public bug reported:
Installing updates
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.2.0-34-generic 6.2.0-34.34
ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevices
Removing Jammy from nominations as jammy:linux-gcp-6.2 and jammy:linux-
aws-6.2 will be getting the patch via lunar:linux-gcp and lunar:linux-
aws respectively.
** No longer affects: linux-gcp (Ubuntu Jammy)
** No longer affects: linux-aws (Ubuntu Jammy)
--
You received this bug notification be
** Changed in: linux-gcp (Ubuntu Jammy)
Status: New => Triaged
** Changed in: linux-gcp (Ubuntu Lunar)
Status: New => Triaged
** Changed in: linux-gcp (Ubuntu Mantic)
Status: New => Triaged
** Changed in: linux-aws (Ubuntu Lunar)
Status: New => Triaged
** Changed in:
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1006.6
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-jammy-linux-oem-6.5' to 'verification-done-
jammy-linux-oem-6.5'.
This bug is awaiting verification that the linux-oem-6.5/6.5.0-1006.6
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-jammy-linux-oem-6.5' to 'verification-done-
jammy-linux-oem-6.5'.
** Patch added: "iproute2_6.1.0-1ubuntu3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2039280/+attachment/5709212/+files/iproute2_6.1.0-1ubuntu3.debdiff
** Description changed:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
pr
** Description changed:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that m
Public bug reported:
[Impact]
IPv4 and IPv6 addresses can be assigned a protocol value that indicates the
provenance of the IP address. The attribute is modeled after ip route
protocols, and essentially allows the administrator or userspace stack to
tag addresses in some way that makes sense to t
Public bug reported:
Consistent naming of onboard NIC on all Pi on all Ubuntu
We should have the one distro config, to force consistent oboard NIC naming on
all Pi on all Ubuntu in the one place.
Let's find all the puzzle pieces and do it onces, and for all
** Affects: linux-raspi (Ubuntu)
> Probably the version installed was 5.4.0-162.
Yes, you are probably right. I was only looking at the date of the
kernel file. The bug is reproducible with Linux 5.4.0-164.181, however.
> I checked some discussions from here https://gitlab.com/qemu-
project/qemu/-/issues/1696 and it seems it's s
** Attachment added: "dmesg_i8042.debug_i8042.nopnp_i8042.noaux_i8042.nomux.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+attachment/5709207/+files/dmesg_i8042.debug_i8042.nopnp_i8042.noaux_i8042.nomux.log
--
You received this bug notification because you a
** Attachment added: "dmesg_i8042.debug_i8042.nopnp.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+attachment/5709206/+files/dmesg_i8042.debug_i8042.nopnp.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
** Attachment added: "dmesg_i8042.debug_i8042.nopnp_i8042.noaux.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+attachment/5709205/+files/dmesg_i8042.debug_i8042.nopnp_i8042.noaux.log
--
You received this bug notification because you are a member of Kernel
Pa
** Attachment added: "dmesg_i8042.debug.log"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2034477/+attachment/5709204/+files/dmesg_i8042.debug.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-
I have this laptop (V15 AMN on R3 7320U / 16G RAM), have built 6.5.7 kernel
with all I2C drivers.
Uploading several of dmesg dump files with different parameters and xinput dump
file.
Hope we will see a fix soon.
Also can notice, "extra buttons" kind of working, even can setup screen
brightness
On the 1st of September, we started preparing 164, it was released last
week. Probably the version installed was 5.4.0-162.
Could you try this with the version from -proposed? It's 5.4.0-166.183.
I checked some discussions from here
https://gitlab.com/qemu-project/qemu/-/issues/1696 and it seems
** Changed in: ubuntu-release-notes
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2037642
Title:
[FFe] Raspberry Pi 5 support
Stat
We have live updates with unattended updates. Our first recording of
this problem is Sept. 5th, so this points towards Linux 5.4.0-164.181
being the culprit unless you updated this package just a few days
before. Linux 5.4.0-164.181 was installed on our systems Sept 1st, and
this has been a problem
Can you tell us from which version you upgraded to 164? It would be
helpful to narrow down what changes happened in between.
--
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/2039258
Title:
Hello Chengen, or anyone else affected,
Accepted makedumpfile into jammy-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.7.0-1ubuntu0.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Chengen, or anyone else affected,
Accepted makedumpfile into lunar-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.7.2-1ubuntu0.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Reply #2
~~~
$ uname -a
Linux 6.5.0-1005-oem #5-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 6 12:13:41 UTC
2023 x86_64 x86_64 x86_64 GNU/Linux
$ sudo cat /sys/kernel/debug/pmc_core/slp_s0_residency_usec
0
$ sudo rtcwake -m mem -s 5
rtcwake: assuming RTC uses UTC ...
rtcwake: wakeup from "mem" using /dev/
Reply #2
~~~
u@u-OptiPlex-SFF-7010:~$ uname -a
Linux u-OptiPlex-SFF-7010 6.5.0-1005-oem #5-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct
6 12:13:41 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
u@u-OptiPlex-SFF-7010:~$ sudo cat
/sys/kernel/debug/pmc_core/slp_s0_residency_usec
0
u@u-OptiPlex-SFF-7010:~$ sudo rtcw
This is a successfull boot of qemu.
** Attachment added: "log89"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+attachment/5709154/+files/log89
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
This is a failing boot of qemu that we killed after some time.
** Attachment added: "log90"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+attachment/5709155/+files/log90
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2039258/+attachment/5709152/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, whic
We managed to reproduce the failure on a fresh install of Ubuntu 20.04
using this script. It occurred already on the 90th iteration.
---
for i in {1..1}
do
echo Run $i
guestfish -vx -a /dev/null run >& log$i
done
---
Here is what we did after booting a fresh install
a
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2039258/+attachment/5709151/+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/2039258/+attachment/5709150/+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/2039258
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2039258/+attachment/5709147/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2039258/+attachment/5709148/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2039258/+attachment/5709149/+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
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2039258/+attachment/5709143/+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/2039
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2039258/+attachment/5709145/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2039258/+attachment/5709146/+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: "PciMultimedia.txt"
https://bugs.launchpad.net/bugs/2039258/+attachment/5709144/+files/PciMultimedia.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2039258/+attachment/5709142/+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/20
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2039258/+attachment/5709140/+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: "Card0.Codecs.codec.0.txt"
https://bugs.launchpad.net/bugs/2039258/+attachment/5709139/+files/Card0.Codecs.codec.0.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2039258/+attachment/5709141/+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/2039258
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/2039258/+attachment/5709138/+files/CRDA.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/2039258
Ti
apport information
** Tags added: apport-collected focal
** Description changed:
We have a number of Ubuntu 20.04 servers that have recently been
upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27.
About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU
indefinat
** Tags removed: verification-needed-jammy-linux-oem-6.1
** Tags added: verification-done-jammy-linux-oem-6.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2036184
Title:
Infini
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 2039258
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
We have a number of Ubuntu 20.04 servers that have recently been
upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27.
About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU
indefinately. A number of our utilities are using qemu for processing,
so we get
On 23.04 the microphone is working already. I have tried to upgrade
yesterday to 23.10, but the install windows are not appearing properly,
so cannot see the steps. (With the updater tool the upgrade did not
appear yet.)
The other windows on the live DVD, like Libre Office, or the settings
windows
** Changed in: linux-aws (Ubuntu Mantic)
Importance: Undecided => High
** Changed in: linux-aws (Ubuntu Mantic)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchp
87 matches
Mail list logo
