This bug was fixed in the package linux - 5.19.0-35.36
---
linux (5.19.0-35.36) kinetic; urgency=medium
* kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)
* CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461
linux (5.19.0-34.35) kinetic; urgency
This bug was fixed in the package linux-restricted-modules -
5.15.0-67.74
---
linux-restricted-modules (5.15.0-67.74) jammy; urgency=medium
* Master version: 5.15.0-67.74
* Miscellaneous Ubuntu changes
- debian/tracking-bug -- update from master
linux-restricted-modules (5.1
This bug was fixed in the package linux-restricted-modules -
5.19.0-35.36
---
linux-restricted-modules (5.19.0-35.36) kinetic; urgency=medium
* Master version: 5.19.0-35.36
* LRMv7: Enable the open NVIDIA kernel modules (LP: #1988836)
- [Packaging] convert to v7.2 autogen for
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1012.12
---
linux-oem-6.0 (6.0.0-1012.12) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1012.12 -proposed tracker (LP: #2004348)
* CVE-2023-0469
- io_uring/filetable: fix file reference underflow
* LSM: Configuri
This bug was fixed in the package linux - 5.19.0-35.36
---
linux (5.19.0-35.36) kinetic; urgency=medium
* kinetic/linux: 5.19.0-35.36 -proposed tracker (LP: #2004652)
* CVE-2023-0461
- SAUCE: Fix inet_csk_listen_start after CVE-2023-0461
linux (5.19.0-34.35) kinetic; urgency
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1028.29
---
linux-oem-5.17 (5.17.0-1028.29) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1028.29 -proposed tracker (LP:
#2004346)
* CVE-2023-0045
- x86/bugs: Flush IBP in ib_prctl_set()
* Packaging resync (L
This bug was fixed in the package linux-ibm - 5.19.0-1018.20
---
linux-ibm (5.19.0-1018.20) kinetic; urgency=medium
* kinetic/linux-ibm: 5.19.0-1018.20 -proposed tracker (LP: #2004288)
* Kinetic update: upstream stable patchset 2023-01-27 (LP: #2004051)
- [Config] Update conf
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
Aha, cool, thanks Mike; I started with xxd myself, and got stuff that
looked enough like ELF objects that I was prepared to trust file's
assessment of them as ELF objects.
My machine with non-zero content at the end:
Linux hunt 4.15.0-201-generic #212-Ubuntu SMP Mon Nov 28 11:29:59 UTC 2022
x86_6
I am getting this same bug on a 6.0.0 kernel with the igb driver. This
is on a Dell XPS15 2022 on Kubuntu 22.04. If it matters, I have disabled
the MAC address passthrough.
lspci:
:00:14.3 Network controller [0280]: Intel Corporation Alder Lake-P PCH CNVi
WiFi [8086:51f0] (rev 01)
:05:00
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2002361
Title:
allow per-net notifier to follow
I got a kernel upgrade from Linux mint 5.15.0-67
I see no change in dmesg.
--
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/1998285
Title:
5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu
S
Feature is not available yet. Need to verify after
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2008136
** Tags removed: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu
Experiencing this as well.
22.04 LTS
Lenovo Lenovo YOGA 720-15IKB
Intel® HD Graphics 630
External Dell monitor native resolution 2560x1440, connected through USB-C
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://
This bug is awaiting verification that the linux-aws/5.15.0-1032.36
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 exists, ch
This bug is awaiting verification that the linux-aws/5.15.0-1032.36
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 exists, ch
This bug is awaiting verification that the linux-aws/5.15.0-1032.36
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 exists, ch
This bug is awaiting verification that the linux-aws/5.15.0-1032.36
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 exists, ch
This bug is awaiting verification that the linux-aws/5.15.0-1032.36
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 exists, ch
This bug is awaiting verification that the linux/5.15.0-68.75 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 exists, change t
This bug is awaiting verification that the linux/5.15.0-68.75 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 exists, change t
This bug is awaiting verification that the linux/5.15.0-68.75 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 exists, change t
This bug is awaiting verification that the linux/5.15.0-68.75 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 exists, change t
This bug is awaiting verification that the linux/5.15.0-68.75 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 exists, change t
This bug is awaiting verification that the linux/5.15.0-68.75 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 exists, change t
This bug is awaiting verification that the linux/5.15.0-68.75 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 exists, change t
This bug is awaiting verification that the linux/5.15.0-68.75 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 exists, change t
This bug is awaiting verification that the linux/5.15.0-68.75 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 exists, change t
This bug is awaiting verification that the linux/5.15.0-68.75 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 exists, change t
This bug is awaiting verification that the linux/5.15.0-68.75 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 exists, change t
This bug is awaiting verification that the linux-gcp/5.15.0-1031.38
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 exists, ch
This bug is awaiting verification that the linux-azure/5.15.0-1035.42
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 exists,
This bug is awaiting verification that the linux-azure/5.15.0-1035.42
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 exists,
This bug is awaiting verification that the linux-azure/5.15.0-1035.42
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 exists,
This bug is awaiting verification that the linux-azure/5.15.0-1035.42
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 exists,
This bug is awaiting verification that the linux-azure/5.15.0-1035.42
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 exists,
It happened again. Notice the same amdgpu errors near the end.
** Attachment added: "second_freeze.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008118/+attachment/5650838/+files/second_freeze.log
--
You received this bug notification because you are a member of Kernel
Packages,
I can see this fcnal-test.sh test failing with 5.15.0-68.75
Thanks
** Tags removed: verification-needed-jammy
** Tags added: 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.n
All autopkgtests for the newly accepted linux-restricted-modules-aws
(5.15.0-1032.36) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page listed
All autopkgtests for the newly accepted linux-restricted-modules-aws
(5.15.0-1032.36) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page listed
All autopkgtests for the newly accepted linux-restricted-modules-azure
(5.15.0-1035.42) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page list
All autopkgtests for the newly accepted linux-restricted-modules-azure
(5.15.0-1035.42) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page list
I just found many similar reports.
1. https://github.com/QubesOS/qubes-issues/issues/6923
2. https://gitlab.freedesktop.org/drm/amd/-/issues/2266
3. https://gitlab.freedesktop.org/drm/amd/-/issues/822
They all have the same amdgpu errors:
```
mar 01 23:01:25 workstation1 kernel: [drm:psp_load_no
This is now affecting Bionic
With upstream commit a1d6cd88c "selftests/ftrace: event_triggers: wait
longer for test_event_enable" applied via stable update, ftrace in
Bionic proposed (4.15.0-207.218) is now failing with:
$ sudo ./ftracetest ./test.d/ftrace/func_event_triggers.tc
[1] ftrace - tes
All autopkgtests for the newly accepted linux-restricted-modules-gcp
(5.15.0-1031.38) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page listed
** Also affects: linux-hwe-5.19 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-5.19 (Ubuntu)
Status: New => Fix Released
** No longer affects: linux-hwe-5.19 (Ubuntu Kinetic)
--
You received this bug notification because you are a member of Kernel
Packages,
Confirmed the fix is in linux-hwe-5.19 ... it looks like this:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=77c092e054262b594614bad5e5f47e57c5d29639
** Also affects: linux-hwe-5.19 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe-5.19
Public bug reported:
[Impact]
The perf tool use scandir() to iterate threads and sort in alphabetical order
when synthesizing PERF_RECORD_ events.
If the process ID is and it has one thread (tid = 1), the thread will
be processed before the process.
It results in PERF_RECORD_FORK events
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 2008971
and then change the status of the bug to 'Confirmed'.
If, due to the nature
The fix is in jammy linux-hwe-5.19 and also in kinetic 5.19.0-35.36 ...
but still not in lunar until 6.1 is released.
** Changed in: linux (Ubuntu Kinetic)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
Public bug reported:
Make Wayland sessions work with fbdev. For when KMS/DRM support is
missing in the kernel but the device still has legacy graphics.
Currently Xorg already does this with a custom driver that allows it to
fall back to using fbdev. We could do the same with mutter but it's
unlik
We will also need to fix bug 1919400 before Xorg is ever retired. But
this is all in the distant future.
--
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/2008977
Title:
Make Wayland sessio
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 2008977
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => ChengEn, Du (chengendu)
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => ChengEn, Du (chengendu)
** Changed in: linux (Ubuntu)
S
** 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/2008977
Title:
Make Wayland sessions work with fbdev
Status in linux
Nope, not fixed in 5.19.0-32-generic
https://bugs.launchpad.net/ubuntu/+bug/2008540/comments/5
** Changed in: linux (Ubuntu)
Status: Fix Committed => Confirmed
** Changed in: linux-hwe-5.19 (Ubuntu)
Status: Fix Released => Confirmed
** No longer affects: linux
** Bug watch added:
Now tracking in:
https://gitlab.freedesktop.org/drm/amd/-/issues/2282
** Tags removed: fixed-in-linux-6.1 fixed-upstream
--
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/bugs/1980831
Ti
I am also experiencing this issue on a brand new Lenovo X1 Carbon Gen 10
with a regular HD screen (1920x1200). The workaround of disabling PSR
via altering grub options worked for me:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_psr=0"
Should this bug description be generalized?
--
*** This bug is a duplicate of bug 1980831 ***
https://bugs.launchpad.net/bugs/1980831
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2282
https://gitlab.freedesktop.org/drm/amd/-/issues/2282
** Changed in: linux
Remote watch: gitlab.freedesktop.org/drm/amd/-/issues #2135 =>
*** This bug is a duplicate of bug 1980831 ***
https://bugs.launchpad.net/bugs/1980831
Ubuntu 21.10 is no longer supported but the same issue is being tracked
in bug 1980831.
** This bug has been marked a duplicate of bug 1980831
GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [
*** This bug is a duplicate of bug 1980831 ***
https://bugs.launchpad.net/bugs/1980831
Ubuntu 21.04 is no longer supported but the same issue is being tracked
in bug 1980831.
** This bug has been marked a duplicate of bug 1980831
GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [
Didn't see this failure with B-azure 4.15.0-1162.177
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1814
** Summary changed:
- XPS 9320 screen flicker on UHD panel 3840x2400
+ screen flicker after PSR2 enabled
--
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/2007516
Title:
screen fli
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-oem-6.1 (Ubuntu)
Status: New => Confirmed
--
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.ne
Also happens on (all?) lunar machines with the 5.19 kernel.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags added: lunar
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Pa
as per Cyrus,
'''
kernel 5.15.0-68.75 verified pass.
Kernel: 5.15.0-68.75
SKU: Alxd-Low-DVT-C1_202209-30619
Monitor: PA238Q (FHD)
Monitor: Gechi On-Lap 1303 (FHD)
'''
Cyrus, thanks
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notif
After the upgrade of grub-efi-amd64-bin 2.06-2ubuntu14.1 and
grub-efi-amd64-signed 2.06-2ubuntu14.1,
everything runs as it should.
Oh, I had also installed the updated kernel - 5.15.0-67-generic x86_64
--
You received this bug notification because you are a member of Kernel
Packages, which is s
Public bug reported:
After upgrading to 5.17.0-1027-oem, my laptop fails to suspend. Instead
it turns off.
Journald output:
Mar 02 17:31:47 nugget systemd[1]: NetworkManager-dispatcher.service:
Deactivated successfully.
Mar 02 17:31:53 nugget NetworkManager[940]: [1677740513.3571] manager:
s
101 - 168 of 168 matches
Mail list logo
