We are affected on live machines too.
--
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/2002889
Title:
5.15.0-58.64 breaks xen bridge networking (pvh domU)
Status in linux package in
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5248
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5248
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5248
Importance: Unknown
Status: Unknown
** Tags added: i915
**
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/2003031
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (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/2003031
*** This bug is a duplicate of bug 2003031 ***
https://bugs.launchpad.net/bugs/2003031
Thanks. The log in comment #3 seems to show this is a duplicate of bug
2003031.
Please also remember to try the workaround in comment #2.
** This bug has been marked a duplicate of bug 2003031
Using
** Summary changed:
- gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel
says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
+ gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel
says "adding CRTC not allowed without
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1009.9 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' to 'verification-
done-jammy'. If the problem still
I suspect it was fixed with:
commit b292cafe2dd02d96a07147e4b160927e8399d5cc
Author: Felix Kuehling
Date: Wed Sep 21 17:45:59 2022 -0400
drm/amdkfd: Fix UBSAN shift-out-of-bounds warning
This was fixed in initialize_cpsch before, but not in initialize_nocpsch.
Factor sdma bitmap
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Kinetic)
Status: In Progress => Fix
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Lunar)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Lunar)
Assignee: Po-Hsu Lin (cypressyew) => Andrea Righi (arighi)
** Changed in: linux (Ubuntu Kinetic)
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
** 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-hwe-5.19 in Ubuntu.
** 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/2000772
Title:
powerpc-build in ubuntu_kernel_selftests
** 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/2000299
Title:
Fix W6400 hang after resume of S3 stress
** 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-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1992714
Title:
[SRU] SoF for RPL platform
The attachment "zfs-dkms-2.1.4-fix-zero-mac-io-error.patch" seems to be
a patch. If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Kinetic)
Status: Triaged => Fix Committed
--
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 (Ubuntu Lunar)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Lunar)
Assignee: AceLan Kao (acelankao) => Andrea Righi (arighi)
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Kinetic)
This is at least staged via stable.
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1999836
Title:
Fix
So. I'm affected as well.
Luckily there is a patch already:
https://patch-diff.githubusercontent.com/raw/openzfs/zfs/pull/14161.patch
HOW TO APPLY
-
=== Step 1: get patch ===
(see zfs-dkms-2.1.4-fix-zero-mac-io-error.patch attachment)
=== Step 2: install zfs-dkms and
*** This bug is a security vulnerability ***
Public security bug reported:
[Impact]
New upstream release. This is a database of wireless regulations, and
should updated in all releases to ensure users have the most up-to-date
regulatory information.
[Test Case]
Following reboot after
** 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-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1999836
Title:
Fix SUT can't displayed after
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Kernel
** Also affects: wireless-regdb (Ubuntu)
Importance: Undecided
Status: New
** Changed in: crda (Ubuntu)
Status: New => Fix Released
** Changed in: crda (Ubuntu Jammy)
Status: New => Fix Released
** Description changed:
Debian has just removed the crda package from the
** Tags removed: verification-needed-focal verification-needed-jammy
** Tags added: verification-done-focal verification-done-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/1996071
This fix will be included in grub2-unsigned/2.06-2ubuntu14.1 for
kinetic, jammy, focal, bionic. Binaries have been built in
https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/ppa/+packages
for kinetic.
Signing request: https://answers.launchpad.net/canonical-signing-
jobs/+question/704589
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1030.34~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1030.34~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1030.34~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1030.34~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1030.34~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1030.34~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1030.34~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1030.34~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1030.34~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1030.34~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1030.34~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1030.34~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' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
aws-5.15/5.15.0-1030.34~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' to
'verification-done-focal'. If the problem
Added journalctl output with kernel stacktrace.
** Attachment added: "drm_atomic_nonblocking_commit.log"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003998/+attachment/5643974/+files/drm_atomic_nonblocking_commit.log
--
You received this bug notification because you are a member
This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu1.3
---
alsa-ucm-conf (1.2.6.3-1ubuntu1.3) jammy; urgency=medium
* d/p/ucm2-sof-hda-dsp-Update-Mic-LED-settings.patch
d/p/ucm2-sof-hda-dsp-If.devdmic-cleanup.patch
- Backport patch to fix micmute LED. (LP:
This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu1.3
---
alsa-ucm-conf (1.2.6.3-1ubuntu1.3) jammy; urgency=medium
* d/p/ucm2-sof-hda-dsp-Update-Mic-LED-settings.patch
d/p/ucm2-sof-hda-dsp-If.devdmic-cleanup.patch
- Backport patch to fix micmute LED. (LP:
This bug is awaiting verification that the linux-
bluefield/5.15.0-1012.14 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' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-
bluefield/5.15.0-1012.14 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' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-
bluefield/5.15.0-1012.14 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' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-
bluefield/5.15.0-1012.14 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' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-
bluefield/5.15.0-1012.14 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' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-
bluefield/5.15.0-1012.14 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' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-
bluefield/5.15.0-1012.14 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' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-
bluefield/5.15.0-1012.14 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' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-
bluefield/5.15.0-1012.14 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' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-
bluefield/5.15.0-1012.14 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' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-
bluefield/5.15.0-1012.14 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' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-
bluefield/5.15.0-1012.14 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' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-
bluefield/5.15.0-1012.14 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' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-
bluefield/5.15.0-1012.14 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' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-
bluefield/5.15.0-1012.14 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' to 'verification-
done-jammy'. If the problem still
This bug is awaiting verification that the linux-
bluefield/5.15.0-1012.14 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' to 'verification-
done-jammy'. If the problem still
This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu4
---
alsa-ucm-conf (1.2.6.3-1ubuntu4) kinetic; urgency=medium
* d/p/ucm2-sof-hda-dsp-Update-Mic-LED-settings.patch
d/p/ucm2-sof-hda-dsp-If.devdmic-cleanup.patch
- Backport patch to fix micmute LED. (LP:
The verification of the Stable Release Update for alsa-ucm-conf has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu4
---
alsa-ucm-conf (1.2.6.3-1ubuntu4) kinetic; urgency=medium
* d/p/ucm2-sof-hda-dsp-Update-Mic-LED-settings.patch
d/p/ucm2-sof-hda-dsp-If.devdmic-cleanup.patch
- Backport patch to fix micmute LED. (LP:
The verification of the Stable Release Update for alsa-ucm-conf has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
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
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
@yk4ever: I am having the same issue. Was it a hardware issue? Does the
modprobe still work? In my case it does not. What kernel are you using
now?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Same issue as reported here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993052
--
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/2004110
Title:
Wifi keeps failing with: Failed
Not quite the same error as above. But this seems to be the same. Here
is the orginal:
[ 28.357969] iwlwifi :3d:00.0: Could not load the [0] uCode section
[ 28.358001] iwlwifi :3d:00.0: Failed to start INIT ucode: -110
Here is what I have:
sudo dmesg | grep -i wifi
[sudo] password for
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 2004110
and then change the status of the bug to 'Confirmed'.
If, due to the
Possibly related:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975460
--
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/2004110
Title:
Wifi keeps failing with: Failed to run INIT
70 matches
Mail list logo
