Hello,
May I know have you solved the above problem? I also encounter valgrind said
there is memory leak in libasound2 for aarch64 architecture device. I also not
sure how to solve the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
@superm1 Thank for your reply. The method can make AMD graphic card
work!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2045382
Title:
AMD Lexa PRO graphic card can't wo
I've tried the kernel parameter and those artifacts are still happening.
But just on my FHD screen; not on my other screens (1440p).
--
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/2038998
Mario,
Do you know the sha1 of missing patches?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/2045382
Title:
AMD Lexa PRO graphic card can't work
Status in linux-signe
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-hwe-5.19 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.
ProblemType: Bug
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: john 3528 F pipewire
john 3533 F wireplumber
/dev/snd/controlC0: john 3533 F wireplumber
/dev/snd/seq:
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/2011385/+attachment/5726202/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.ne
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2011385/+attachment/5726203/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.laun
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/2011385/+attachment/5726204/+files/PaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2011385/+attachment/5726206/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2011385/+attachment/5726205/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https
Also get this problem of no sound output from speakers on a Razer laptop
(headphones work fine). Using firmware-sof-signed 2.2.6-1ubuntu1.2.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.n
Here is the link:
https://github.com/Mafoelffen1/OpenZFS-Ubuntu-Admin/blob/main/ZFS-DKMS-WORK-AROUND.md
It is tested. It is somewhat daunting... But it works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://b
This issue was already reported in
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/2037082
--
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/2045512
Title:
UBSAN: array-index-out-
This bug was fixed in the package linux - 6.2.0-39.40
---
linux (6.2.0-39.40) lunar; urgency=medium
* lunar/linux: 6.2.0-39.40 -proposed tracker (LP: #2043451)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight
This bug was fixed in the package linux - 6.2.0-39.40
---
linux (6.2.0-39.40) lunar; urgency=medium
* lunar/linux: 6.2.0-39.40 -proposed tracker (LP: #2043451)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight
This bug was fixed in the package linux-raspi - 6.2.0-1018.20
---
linux-raspi (6.2.0-1018.20) lunar; urgency=medium
* lunar/linux-raspi: 6.2.0-1018.20 -proposed tracker (LP: #2041550)
* openvswitch fails on raspberry pi 4 (LP: #2040524)
- [Packaging] raspi: Include openvswitc
This bug was fixed in the package linux - 6.2.0-39.40
---
linux (6.2.0-39.40) lunar; urgency=medium
* lunar/linux: 6.2.0-39.40 -proposed tracker (LP: #2043451)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight
This bug was fixed in the package linux - 6.2.0-39.40
---
linux (6.2.0-39.40) lunar; urgency=medium
* lunar/linux: 6.2.0-39.40 -proposed tracker (LP: #2043451)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight
This bug was fixed in the package linux - 6.2.0-39.40
---
linux (6.2.0-39.40) lunar; urgency=medium
* lunar/linux: 6.2.0-39.40 -proposed tracker (LP: #2043451)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight
This bug was fixed in the package linux - 6.2.0-39.40
---
linux (6.2.0-39.40) lunar; urgency=medium
* lunar/linux: 6.2.0-39.40 -proposed tracker (LP: #2043451)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight
This bug was fixed in the package linux - 6.2.0-39.40
---
linux (6.2.0-39.40) lunar; urgency=medium
* lunar/linux: 6.2.0-39.40 -proposed tracker (LP: #2043451)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight
This bug was fixed in the package linux - 6.2.0-39.40
---
linux (6.2.0-39.40) lunar; urgency=medium
* lunar/linux: 6.2.0-39.40 -proposed tracker (LP: #2043451)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight
This bug was fixed in the package linux - 6.2.0-39.40
---
linux (6.2.0-39.40) lunar; urgency=medium
* lunar/linux: 6.2.0-39.40 -proposed tracker (LP: #2043451)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight
This bug was fixed in the package linux - 6.2.0-39.40
---
linux (6.2.0-39.40) lunar; urgency=medium
* lunar/linux: 6.2.0-39.40 -proposed tracker (LP: #2043451)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight
This bug was fixed in the package linux - 6.2.0-39.40
---
linux (6.2.0-39.40) lunar; urgency=medium
* lunar/linux: 6.2.0-39.40 -proposed tracker (LP: #2043451)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight
This bug was fixed in the package linux - 6.2.0-39.40
---
linux (6.2.0-39.40) lunar; urgency=medium
* lunar/linux: 6.2.0-39.40 -proposed tracker (LP: #2043451)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight
This bug is awaiting verification that the linux-kvm/6.2.0-1018.18
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-lunar-linux-kvm' to 'verification-done-lunar-
linux-kvm'. If the prob
This bug is awaiting verification that the linux-aws/6.2.0-1017.17
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-lunar-linux-aws' to 'verification-done-lunar-
linux-aws'. If the prob
This bug is awaiting verification that the linux-lowlatency-
hwe-6.2/6.2.0-1018.18~22.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-jammy-linux-
lowlatency-hwe-6.2' to 'verifica
This bug is awaiting verification that the linux-gcp/6.2.0-1020.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-lunar-linux-gcp' to 'verification-done-lunar-
linux-gcp'. If the prob
This bug is awaiting verification that the linux-azure/6.2.0-1018.18
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-lunar-linux-azure' to 'verification-done-lunar-
linux-azure'. If th
This bug is awaiting verification that the linux-starfive/6.2.0-1010.11
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-lunar-linux-starfive' to 'verification-done-
lunar-linux-starfiv
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-39.40~22.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-jammy-linux-
hwe-6.2' to 'verification-done-jammy-linux-hw
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-39.40~22.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-jammy-linux-
hwe-6.2' to 'verification-done-jammy-linux-hw
This bug is awaiting verification that the linux-kvm/6.2.0-1018.18
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-lunar-linux-kvm' to 'verification-done-lunar-
linux-kvm'. If the prob
This bug is awaiting verification that the linux-gcp/6.2.0-1020.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-lunar-linux-gcp' to 'verification-done-lunar-
linux-gcp'. If the prob
This bug is awaiting verification that the linux-azure/6.2.0-1018.18
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-lunar-linux-azure' to 'verification-done-lunar-
linux-azure'. If th
This bug is awaiting verification that the linux-lowlatency-
hwe-6.2/6.2.0-1018.18~22.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-jammy-linux-
lowlatency-hwe-6.2' to 'verifica
This bug is awaiting verification that the linux-aws/6.2.0-1017.17
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-lunar-linux-aws' to 'verification-done-lunar-
linux-aws'. If the prob
This bug is awaiting verification that the linux-starfive/6.2.0-1010.11
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-lunar-linux-starfive' to 'verification-done-
lunar-linux-starfiv
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-39.40~22.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-jammy-linux-
hwe-6.2' to 'verification-done-jammy-linux-hw
This bug is awaiting verification that the linux-lowlatency-
hwe-6.2/6.2.0-1018.18~22.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-jammy-linux-
lowlatency-hwe-6.2' to 'verifica
This bug is awaiting verification that the linux-gcp/6.2.0-1020.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-lunar-linux-gcp' to 'verification-done-lunar-
linux-gcp'. If the prob
This bug is awaiting verification that the linux-kvm/6.2.0-1018.18
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-lunar-linux-kvm' to 'verification-done-lunar-
linux-kvm'. If the prob
This bug is awaiting verification that the linux-azure/6.2.0-1018.18
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-lunar-linux-azure' to 'verification-done-lunar-
linux-azure'. If th
This bug is awaiting verification that the linux-aws/6.2.0-1017.17
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-lunar-linux-aws' to 'verification-done-lunar-
linux-aws'. If the prob
This bug is awaiting verification that the linux-starfive/6.2.0-1010.11
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-lunar-linux-starfive' to 'verification-done-
lunar-linux-starfiv
This bug is awaiting verification that the linux-lowlatency-
hwe-6.2/6.2.0-1018.18~22.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-jammy-linux-
lowlatency-hwe-6.2' to 'verifica
This bug is awaiting verification that the linux-azure/6.2.0-1018.18
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-lunar-linux-azure' to 'verification-done-lunar-
linux-azure'. If th
This bug is awaiting verification that the linux-gcp/6.2.0-1020.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-lunar-linux-gcp' to 'verification-done-lunar-
linux-gcp'. If the prob
This bug is awaiting verification that the linux-starfive/6.2.0-1010.11
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-lunar-linux-starfive' to 'verification-done-
lunar-linux-starfiv
This bug is awaiting verification that the linux-lowlatency-
hwe-6.2/6.2.0-1018.18~22.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-jammy-linux-
lowlatency-hwe-6.2' to 'verifica
This bug is awaiting verification that the linux-aws/6.2.0-1017.17
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-lunar-linux-aws' to 'verification-done-lunar-
linux-aws'. If the prob
This bug is awaiting verification that the linux-kvm/6.2.0-1018.18
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-lunar-linux-kvm' to 'verification-done-lunar-
linux-kvm'. If the prob
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-39.40~22.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-jammy-linux-
hwe-6.2' to 'verification-done-jammy-linux-hw
This bug is awaiting verification that the linux-aws/6.2.0-1017.17
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-lunar-linux-aws' to 'verification-done-lunar-
linux-aws'. If the prob
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-39.40~22.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-jammy-linux-
hwe-6.2' to 'verification-done-jammy-linux-hw
This bug is awaiting verification that the linux-gcp/6.2.0-1020.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-lunar-linux-gcp' to 'verification-done-lunar-
linux-gcp'. If the prob
This bug is awaiting verification that the linux-azure/6.2.0-1018.18
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-lunar-linux-azure' to 'verification-done-lunar-
linux-azure'. If th
This bug is awaiting verification that the linux-starfive/6.2.0-1010.11
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-lunar-linux-starfive' to 'verification-done-
lunar-linux-starfiv
This bug is awaiting verification that the linux-gcp/6.2.0-1020.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-lunar-linux-gcp' to 'verification-done-lunar-
linux-gcp'. If the prob
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-39.40~22.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-jammy-linux-
hwe-6.2' to 'verification-done-jammy-linux-hw
This bug is awaiting verification that the linux-kvm/6.2.0-1018.18
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-lunar-linux-kvm' to 'verification-done-lunar-
linux-kvm'. If the prob
This bug is awaiting verification that the linux-azure/6.2.0-1018.18
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-lunar-linux-azure' to 'verification-done-lunar-
linux-azure'. If th
This bug is awaiting verification that the linux-starfive/6.2.0-1010.11
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-lunar-linux-starfive' to 'verification-done-
lunar-linux-starfiv
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-39.40~22.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-jammy-linux-
hwe-6.2' to 'verification-done-jammy-linux-hw
This bug is awaiting verification that the linux-lowlatency-
hwe-6.2/6.2.0-1018.18~22.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-jammy-linux-
lowlatency-hwe-6.2' to 'verifica
This bug is awaiting verification that the linux-aws/6.2.0-1017.17
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-lunar-linux-aws' to 'verification-done-lunar-
linux-aws'. If the prob
This bug is awaiting verification that the linux-gcp/6.2.0-1020.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-lunar-linux-gcp' to 'verification-done-lunar-
linux-gcp'. If the prob
Public bug reported:
Hello! 👋
We have Ubuntu OS-based servers running in both AWS and Azure clouds.
These servers are handling thousands of connections, and we've been
experiencing issues with TCP memory usage since upgrading to Ubuntu
22.04.3 from 22.04.2.
$ cat /proc/net/sockstat
sockets: used
Public bug reported:
SRU Justification
[Impact]
The kvm flavours currently do not enable CONFIG_DMI_SYSFS. This stops
VMs using these kernels from being configurable using qemu or cloud-
hypervisor's SMBIOS type 11 strings. This feature is supported and used
widely by systemd:
https://www.freed
AFAIU by default it's unattended-upgrades that takes care of removing
old kernel (and kernel module packages). Apparently it doesn't pass
--purge when it removes the old kernel packages. Should it?
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
Public bug reported:
Debian source format 1.0 cannot remove files, create symlinks and change
permission in the .diff.gz tarball. Therefore any changes in these 3
categories cannot be represented without any tricks. To solve this,
the `reconstruct` script is used every time we build the source pac
I'm not sure why kernel 6.2 keeps getting suggested by the ubuntu bot,
it's never been affected by this bug, at least not on any kernel
packaged for ubuntu 23.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bug
@arighi I created another bug for this because it is a general issue, not only
for this `is_rust_module.sh` script.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045562
The command `rm -f` should stay because in v6.5 the script is still there, and
in debian 1.0 we don't properly represen
** Tags removed: verification-done-mantic
** Tags added: verification-done-mantic-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/2042850
Title:
Boot log print hang on screen, no lo
** Tags removed: verification-needed-lunar-linux-aws
verification-needed-lunar-linux-azure
** Tags added: verification-done-lunar-linux-aws
verification-done-lunar-linux-azure
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
** Description changed:
+ SRU Justification:
+
+ [Impact]
+
Debian source format 1.0 cannot remove files, create symlinks and change
permission in the .diff.gz tarball. Therefore any changes in these 3
categories cannot be represented without any tricks. To solve this,
the `reconstruct`
All autopkgtests for the newly accepted linux-meta-hwe-6.2
(6.2.0.39.40~22.04.16) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
backport-iwlwifi-dkms/9858-0ubuntu3.4 (armhf)
Please visit the excuses page listed below and investi
It's probably a duplicate of the same patches missing for bug 2036742.
https://github.com/torvalds/linux/commit/64ffd2f1d00c6235dabe9704bbb0d9ce3e28147f
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu.
http
That was already CC to stable, so I suggest checking the latest 5.15.y.
If that's still not working, you probably need
https://github.com/torvalds/linux/commit/2757a848cb0f184850d3e0a33b4a69e8014fdc5d
backported too.
--
You received this bug notification because you are a member of Kernel
Package
** Changed in: linux-nvidia-6.2 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2042697
Title:
Pull request to address thermal core
** Tags removed: verification-needed-jammy-linux-oem-6.5
** Tags added: verification-done-jammy-linux-oem-6.5
--
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/2041495
Title:
Could
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.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-lunar-linux-riscv' to 'verification-done-lunar-
linux-riscv'. If th
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.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-lunar-linux-riscv' to 'verification-done-lunar-
linux-riscv'. If th
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.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-lunar-linux-riscv' to 'verification-done-lunar-
linux-riscv'. If th
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.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-lunar-linux-riscv' to 'verification-done-lunar-
linux-riscv'. If th
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.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-lunar-linux-riscv' to 'verification-done-lunar-
linux-riscv'. If th
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.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-lunar-linux-riscv' to 'verification-done-lunar-
linux-riscv'. If th
@copong
> I'm not sure why kernel 6.2 keeps getting suggested by the ubuntu bot, it's
> never been affected by this bug, at least not on any kernel packaged for
> ubuntu 23.04.
Maybe the bug had been backported?
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Lunar)
Status: New => In Progress
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in:
I don't believe so, I'm on one of the affected laptops on
6.2.0-37-generic / 23.04 with no issues. It's 23.10's kernel 6.5 that
triggers the issue for me. The bug is also about 23.10, which wouldn't
have kernel 6.2 anyway.
--
You received this bug notification because you are a member of Kernel
P
I have tried this (patches suggested in comment #40) and the problem
seems to have gone away. It may be too soon to say but my test scenario
(which never gave me a false negative before) finished without issues.
Of course this is not a 'fix', so I'm curious to see what the OP has to
say about this
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-azure-fips' to
'verification-done-jammy-li
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-azure-fips' to
'verification-done-jammy-li
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-azure-fips' to
'verification-done-jammy-li
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-azure-fips' to
'verification-done-jammy-li
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-azure-fips' to
'verification-done-jammy-li
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-azure-fips' to
'verification-done-jammy-li
1 - 100 of 140 matches
Mail list logo
