[Kernel-packages] [Bug 1990167] Re: cma alloc failure in large 5.15 arm instances
Patches committed. Due for release in the 2023.01.30 SRU cycle. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1990167 Title: cma alloc failure in large 5.15 arm instances Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Jammy: Fix Committed Status in linux-aws source package in Kinetic: Fix Committed Bug description: When launching large arm64 instances on the focal or jammy ami, cma allocation errors appear in the dmesg out: [0.063255] cma: cma_alloc: reserved: alloc failed, req-size: 4096 pages, ret: -12 As far as I can tell, this does not impact instance launch in a meaningful way, but I am unsure of the other implications of this. I was able to confirm that these messages are only present in 5.15, as they do not show up in the bionic image, and rolling back focal to linux-aws 5.4 avoids them as well. This was present in at least 2 instance types and only appears to pop up in large sizes (2x4 does not produce them, 64x124 (c6gn.16xlarge) does) This could be as simple as just disabling CMA in the linux-aws pkg, as it appears this is already the case in linux-azure(LP: #1949770). Attaching dmesg out to the report. # Replication + Launch a large arm64 instance (c6gn.16xlarge) + Observe the messages in kern.log / dmesg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1990167/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006557] Re: [focal, jammy]Enable rdma-sniffer for libpcap
** Also affects: libpcap (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Summary changed: - [focal, jammy]Enable rdma-sniffer for libpcap + Enable rdma-sniffer for libpcap ** Also affects: libpcap (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libpcap (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: libpcap (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: libpcap (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libpcap (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: Invalid -- 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/2006557 Title: Enable rdma-sniffer for libpcap Status in libpcap package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in libpcap source package in Bionic: New Status in linux source package in Bionic: New Status in libpcap source package in Focal: New Status in linux source package in Focal: New Status in libpcap source package in Jammy: New Status in linux source package in Jammy: New Status in libpcap source package in Kinetic: New Status in linux source package in Kinetic: New Status in libpcap source package in Lunar: New Status in linux source package in Lunar: Invalid Bug description: Hi, The request is to build and configure stock package libpcap with rdma-sniffer enabled. We'd like users of rdma devices to be able to sniff on them using stock tcpdump. Currently when using default tcpdump It does not list rdma devices. $ tcpdump -D |grep -i rdma $ when using locally build tcpdump (with rdma enabled) $ cd $ ./tcpdump -D |grep -i rdma 24.rocep4s0 (RDMA sniffer) 25.rocep7s0f0 (RDMA sniffer) 26.rocep7s0f1 (RDMA sniffer) 27.rocep10s0f0 (RDMA sniffer) 28.rocep10s0f1 (RDMA sniffer) 29.rocep33s0f0 (RDMA sniffer) 30.rocep33s0f1 (RDMA sniffer) 31.rocep36s0f0 (RDMA sniffer) 32.ibp36s0f1 (RDMA sniffer) Locally build steps: clone sources: $ mkdir tcpdumpbuild $ cd tcpdumpbuild/ $ git clone https://github.com/the-tcpdump-group/tcpdump.git $ git clone https://github.com/the-tcpdump-group/libpcap.git install required packages (including rdma packages so libpcap is built with rdma enabled): $ apt install flex bison librdmacm-dev librdmacm1 rdma-core rdmacm-utils configure and build $ cd libpcap $ ./autogen.sh $ ./configure --enable-rdma=yes $ make cd ../tcpdump/ ./autogen.sh ./configure $ make now ./tcpdump -D can show rdma devices. Thanks ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpcap/+bug/2006557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
Commit a8671493d207 ("drm/amdgpu: make sure to init common IP before
gmc") intorduce a regression in 5.17-oem kernel and has been reverted
since 5.17.0-1027.28
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: Fix Released => In Progress
--
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/2000110
Title:
Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-5.17 source package in Jammy:
In Progress
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
In Progress
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-oem-5.17 source package in Lunar:
Invalid
Status in linux-oem-6.0 source package in Lunar:
Invalid
Bug description:
[Impact]
With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting
while entering graphics mode.
[Fix]
AMD provides a list of commits to fix this issue
1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a
2. drm/amdgpu: Don't enable LTR if not supported
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=6c20490663553cd7e07d8de8af482012329ab9d6
3. Patch series: fix PCI AER issues
drm/amdgpu: make sure to init common IP before gmc
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=a8671493d2074950553da3cf07d1be43185ef6c6
drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=e3163bc8ffdfdb405e10530b140135b2ee487f89
drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=dc1d85cb790f2091eea074cee24a704b2d6c4a06
4. Disable amdgpu runpm, will have a update later.
https://patchwork.freedesktop.org/patch/507366/
[Test]
Verified on the machine with AMD graphic card, and confirmed the issue is
gone.
[Where problems could occur]
The main idea is to disable BACO on those cards, the fix is quite
straightforward with 2 Fixes commits, have impact on limited cards.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2000110/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
** Description changed: [Impact] With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting while entering graphics mode. [Fix] + These 3 commits fix the issue + a8671493d207 drm/amdgpu: make sure to init common IP before gmc + e3163bc8ffdf drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega + dc1d85cb790f drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega + + == + V1. AMD provides a list of commits to fix this issue 1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a 2. drm/amdgpu: Don't enable LTR if not supported https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=6c20490663553cd7e07d8de8af482012329ab9d6 3. Patch series: fix PCI AER issues drm/amdgpu: make sure to init common IP before gmc https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=a8671493d2074950553da3cf07d1be43185ef6c6 drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=e3163bc8ffdfdb405e10530b140135b2ee487f89 drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=dc1d85cb790f2091eea074cee24a704b2d6c4a06 4. Disable amdgpu runpm, will have a update later. https://patchwork.freedesktop.org/patch/507366/ [Test] Verified on the machine with AMD graphic card, and confirmed the issue is gone. [Where problems could occur] The main idea is to disable BACO on those cards, the fix is quite straightforward with 2 Fixes commits, have impact on limited cards. -- 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/2000110 Title: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting while entering graphics mode. [Fix] These 3 commits fix the issue a8671493d207 drm/amdgpu: make sure to init common IP before gmc e3163bc8ffdf drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega dc1d85cb790f drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega == V1. AMD provides a list of commits to fix this issue 1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a 2. drm/amdgpu: Don't enable LTR if not supported https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=6c20490663553cd7e07d8de8af482012329ab9d6 3. Patch series: fix PCI AER issues drm/amdgpu: make sure to init common IP before gmc https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=a8671493d2074950553da3cf07d1be43185ef6c6 drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=e3163bc8ffdfdb405e10530b140135b2ee487f89 drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=dc1d85cb790f2091eea074cee24a704b2d6c4a06 4. Disable amdgpu runpm, will have a update later. https://patchwork.freedesktop.org/patch/507366/ [Test] Verified on the machine with AMD graphic card, and confirmed the issue is gone. [Where problems could occur] The main idea is to disable BACO on those cards, the fix is quite straightforward with 2 Fixes commits, have impact on limited cards. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1998285] Re: 5.15.0-53-UBSAN: shift-out-of-bounds in amdgpu
there was a kernel update today (5.15.0-60-generic) but I still see the
overflow followed by a kernel crash. So no change.
--
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
Status in linux package in Ubuntu:
Confirmed
Bug description:
from dmesg
1.313665] UBSAN: shift-out-of-bounds in
/build/linux-JjvoxS/linux-5.15.0/drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device_queue_manager.c:997:32
[1.313668] shift exponent 64 is too large for 64-bit type 'long long
unsigned int'
there is also a crash but i don't know if it's related.
1.313671] Call Trace:
[1.313672]
[1.313673] show_stack+0x52/0x5c
[1.313676] dump_stack_lvl+0x4a/0x63
[1.313678] dump_stack+0x10/0x16
[1.313679] ubsan_epilogue+0x9/0x49
[1.313680] __ubsan_handle_shift_out_of_bounds.cold+0x61/0xef
[1.313682] initialize_nocpsch.cold+0x15/0x59 [amdgpu]
[1.313841] device_queue_manager_init+0x208/0x3b0 [amdgpu]
[1.313946] kgd2kfd_device_init.cold+0x1af/0x483 [amdgpu]
[1.314079] amdgpu_amdkfd_device_init+0x135/0x170 [amdgpu]
[1.314178] amdgpu_device_ip_init+0x681/0x6a4 [amdgpu]
[1.314323] amdgpu_device_init.cold+0x25b/0x7db [amdgpu]
[1.314463] ? do_pci_enable_device+0xdb/0x110
[1.314466] amdgpu_driver_load_kms+0x1e/0x270 [amdgpu]
[1.314556] amdgpu_pci_probe+0x1ce/0x260 [amdgpu]
[1.314642] local_pci_probe+0x48/0x90
[1.314644] pci_device_probe+0x119/0x1f0
[1.314645] really_probe+0x21f/0x420
[1.314647] __driver_probe_device+0x119/0x190
[1.314648] driver_probe_device+0x23/0xc0
[1.314650] __driver_attach+0xbd/0x1f0
[1.314651] ? __device_attach_driver+0x120/0x120
[1.314652] bus_for_each_dev+0x7c/0xd0
[1.314654] driver_attach+0x1e/0x30
[1.314655] bus_add_driver+0x148/0x220
[1.314656] driver_register+0x95/0x100
[1.314657] __pci_register_driver+0x68/0x70
[1.314659] amdgpu_init+0x7c/0x1000 [amdgpu]
[1.314747] ? 0xc0fc
[1.314748] do_one_initcall+0x46/0x1e0
[1.314750] ? kmem_cache_alloc_trace+0x19e/0x2e0
[1.314752] do_init_module+0x52/0x260
[1.314753] load_module+0xb2b/0xbc0
[1.314754] __do_sys_finit_module+0xbf/0x120
[1.314756] __x64_sys_finit_module+0x18/0x20
[1.314757] do_syscall_64+0x59/0xc0
[1.314758] ? ksys_lseek+0x85/0xc0
[1.314759] ? exit_to_user_mode_prepare+0x37/0xb0
[1.314761] ? syscall_exit_to_user_mode+0x27/0x50
[1.314762] ? __x64_sys_lseek+0x18/0x20
[1.314763] ? do_syscall_64+0x69/0xc0
[1.314764] entry_SYSCALL_64_after_hwframe+0x61/0xcb
[1.314766] RIP: 0033:0x7fef87ab8a3d
[1.314767] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d c3 a3 0f 00 f7 d8 64 89 01 48
[1.314768] RSP: 002b:7fffe67aa7c8 EFLAGS: 0246 ORIG_RAX:
0139
[1.314770] RAX: ffda RBX: 55d1d00078a0 RCX:
7fef87ab8a3d
[1.314771] RDX: RSI: 7fef87c4f441 RDI:
0018
[1.314772] RBP: 0002 R08: R09:
0002
[1.314772] R10: 0018 R11: 0246 R12:
7fef87c4f441
[1.314773] R13: 55d1d002ea30 R14: 55d1d0011600 R15:
55d1d002eb10
[1.314774]
[1.314778]
gpu is Amd r 380 tonga 4Gb.
I was adviced to try 6.0 series of kernel and I dont see the ubsan error
there but I would like to get the fixes backported 5.15 series.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jarkko 1322 F pulseaudio
/dev/snd/controlC1: jarkko 1322 F pulseaudio
CasperMD5json: {
CurrentDesktop: MATE
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-09-19 (71 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
MachineType: ASUS System Product Name
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.0.0-1007-oem
root=UUID=62a471af-17fd-40e2-9304-b3e113e4f47f ro quiet splash
ProcVersionSignature: Ubuntu 6.0.0-1007.7-oem 6.0.3
RelatedPackageVersions:
linux-restricted-modules-6.0.0-1007-oem N/A
linux-backports-modules-6.0.0-1007-oem N/A
linux-firmware 20220329.git681281e4-0ubuntu3.7
Tags: vanessa
Uname: Linux 6.0.0-1007-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1949075] Re: [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 22.04
** Tags added: kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1949075 Title: [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on power-on on 22.04 Status in bluez package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: After moving to Impish, my bluetooth headset doesn't automatically connect when I power it on (it was working fine on hirsute). When I go to the bluetooth settings, select it and click connect, the first time it disconnects immediately and I see this line in bluetoothd log: Oct 28 13:57:11 arrakis bluetoothd[1106]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down After that, clicking the connect button again makes it work. I'm not sure where to find info to debug this furhter ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 13:57:34 2021 InstallationDate: Installed on 2021-10-16 (11 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20F6CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic root=/dev/mapper/ubuntu-root ro rootflags=subvol=@ quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2019 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R02ET71W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20F6CTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrR02ET71W(1.44):bd05/08/2019:br1.44:efr1.12:svnLENOVO:pn20F6CTO1WW:pvrThinkPadX260:skuLENOVO_MT_20F6_BU_Think_FM_ThinkPadX260:rvnLENOVO:rn20F6CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X260 dmi.product.name: 20F6CTO1WW dmi.product.sku: LENOVO_MT_20F6_BU_Think_FM_ThinkPad X260 dmi.product.version: ThinkPad X260 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:01:19:D5 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:56756 acl:285 sco:0 events:6453 errors:0 TX bytes:3721263 acl:3477 sco:0 commands:2751 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1949075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
The fix should contain below 3 commits and confirmed that doesn't introduce
regressions on Dell Inspiron 3585 with AMD GPU.
a8671493d207 drm/amdgpu: make sure to init common IP before gmc
e3163bc8ffdf drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for
vega
dc1d85cb790f drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
Kinetic(5.19) already contains those commits since 5.19.0-27.28.
BTW, I can reproduce the regression with only applied commit
a8671493d207 ("drm/amdgpu: make sure to init common IP before gmc").
With all the 3 commits, the issue is gone and the display works
normally.
--
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/2000110
Title:
Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-5.17 source package in Jammy:
In Progress
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
In Progress
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-oem-5.17 source package in Lunar:
Invalid
Status in linux-oem-6.0 source package in Lunar:
Invalid
Bug description:
[Impact]
With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting
while entering graphics mode.
[Fix]
These 3 commits fix the issue
a8671493d207 drm/amdgpu: make sure to init common IP before gmc
e3163bc8ffdf drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for
vega
dc1d85cb790f drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
==
V1.
AMD provides a list of commits to fix this issue
1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a
2. drm/amdgpu: Don't enable LTR if not supported
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=6c20490663553cd7e07d8de8af482012329ab9d6
3. Patch series: fix PCI AER issues
drm/amdgpu: make sure to init common IP before gmc
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=a8671493d2074950553da3cf07d1be43185ef6c6
drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=e3163bc8ffdfdb405e10530b140135b2ee487f89
drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=dc1d85cb790f2091eea074cee24a704b2d6c4a06
4. Disable amdgpu runpm, will have a update later.
https://patchwork.freedesktop.org/patch/507366/
[Test]
Verified on the machine with AMD graphic card, and confirmed the issue is
gone.
[Where problems could occur]
The main idea is to disable BACO on those cards, the fix is quite
straightforward with 2 Fixes commits, have impact on limited cards.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2000110/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
This bug was fixed in the package ubiquity - 22.04.19 --- ubiquity (22.04.19) jammy; urgency=medium * zsys-setup: generate correct zfs-list.cache for target (LP: #1993318) -- Dimitri John Ledkov Tue, 10 Jan 2023 16:26:48 + ** Changed in: ubiquity (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: Fix Released Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in zsys package in Ubuntu: Invalid Status in ubiquity source package in Jammy: Fix Released Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. [Testcase] tl;dr encrypted-zfs, firstboot, `systemctl daemon-reload` must not unmount half of mountpoints, ie. /var/lib. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. [End Testcase] Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993318] Update Released
The verification of the Stable Release Update for ubiquity 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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: Fix Released Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in zsys package in Ubuntu: Invalid Status in ubiquity source package in Jammy: Fix Released Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. [Testcase] tl;dr encrypted-zfs, firstboot, `systemctl daemon-reload` must not unmount half of mountpoints, ie. /var/lib. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. [End Testcase] Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001564] Re: Kernel crash due to Bluefield pka TRNG ioctl call
** 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/2001564 Title: Kernel crash due to Bluefield pka TRNG ioctl call Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Bluefield 3 on Ubuntu 22.04 and OpenSSL 3.0.2, encounters kernel crash/oops when HTTPS client uses OpenSSL with PKA engine during TLS handshake. The issue is with TRNG ioctl call. The kernel logs show the following errors. Unable to handle kernel access to user memory outside uaccess routines at virtual address ce65d328 BF3 on Ubuntu 22.04, OpenSSl 3.0.2 [Fix] * Change RNG ioctl kernel handler code to copy data from user to kernel space. [Test Case] openssl rand -engine pka 512 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2001564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002636] Re: broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19
This bug was fixed in the package broadcom-sta - 6.30.223.271-23~22.04.1 --- broadcom-sta (6.30.223.271-23~22.04.1) jammy; urgency=medium * Lunar import, remove dh-dkms from Build-dep (LP: #2002636). -- Paolo Pisati Thu, 12 Jan 2023 09:59:55 + ** Changed in: broadcom-sta (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to broadcom-sta in Ubuntu. https://bugs.launchpad.net/bugs/2002636 Title: broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19 Status in broadcom-sta package in Ubuntu: Invalid Status in broadcom-sta source package in Jammy: Fix Released Status in broadcom-sta source package in Kinetic: Fix Committed Bug description: [Impact] broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19. [Test case] $ sudo apt-get install broadcom-sta-dkms [Fix] The attached debdiff sync Jammy version to Lunar, minus the dh-dkms build-dep. [Regression potential] None, it's the same version we are already using in Lunar and it contains only fixes to the base version (that is the same among Jammy, Kinetic and Lunar). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2002636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002636] Update Released
The verification of the Stable Release Update for broadcom-sta 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 encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to broadcom-sta in Ubuntu. https://bugs.launchpad.net/bugs/2002636 Title: broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19 Status in broadcom-sta package in Ubuntu: Invalid Status in broadcom-sta source package in Jammy: Fix Released Status in broadcom-sta source package in Kinetic: Fix Committed Bug description: [Impact] broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19. [Test case] $ sudo apt-get install broadcom-sta-dkms [Fix] The attached debdiff sync Jammy version to Lunar, minus the dh-dkms build-dep. [Regression potential] None, it's the same version we are already using in Lunar and it contains only fixes to the base version (that is the same among Jammy, Kinetic and Lunar). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2002636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002636] Re: broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19
Hello Paolo, or anyone else affected, Accepted broadcom-sta into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/broadcom- sta/6.30.223.271-23~22.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: broadcom-sta (Ubuntu Kinetic) Status: Confirmed => Fix Committed ** Tags added: verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to broadcom-sta in Ubuntu. https://bugs.launchpad.net/bugs/2002636 Title: broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19 Status in broadcom-sta package in Ubuntu: Invalid Status in broadcom-sta source package in Jammy: Fix Released Status in broadcom-sta source package in Kinetic: Fix Committed Bug description: [Impact] broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19. [Test case] $ sudo apt-get install broadcom-sta-dkms [Fix] The attached debdiff sync Jammy version to Lunar, minus the dh-dkms build-dep. [Regression potential] None, it's the same version we are already using in Lunar and it contains only fixes to the base version (that is the same among Jammy, Kinetic and Lunar). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2002636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006557] Re: Enable rdma-sniffer for libpcap
** Bug watch added: Debian Bug tracker #1030898 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030898 ** Also affects: libpcap (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030898 Importance: Unknown Status: Unknown ** No longer affects: libpcap (Ubuntu Bionic) ** No longer affects: linux (Ubuntu Bionic) ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux (Ubuntu Jammy) ** No longer affects: linux (Ubuntu Kinetic) -- 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/2006557 Title: Enable rdma-sniffer for libpcap Status in libpcap package in Ubuntu: New Status in linux package in Ubuntu: Invalid Status in libpcap source package in Focal: New Status in libpcap source package in Jammy: New Status in libpcap source package in Kinetic: New Status in libpcap source package in Lunar: New Status in linux source package in Lunar: Invalid Status in libpcap package in Debian: Unknown Bug description: Hi, The request is to build and configure stock package libpcap with rdma-sniffer enabled. We'd like users of rdma devices to be able to sniff on them using stock tcpdump. Currently when using default tcpdump It does not list rdma devices. $ tcpdump -D |grep -i rdma $ when using locally build tcpdump (with rdma enabled) $ cd $ ./tcpdump -D |grep -i rdma 24.rocep4s0 (RDMA sniffer) 25.rocep7s0f0 (RDMA sniffer) 26.rocep7s0f1 (RDMA sniffer) 27.rocep10s0f0 (RDMA sniffer) 28.rocep10s0f1 (RDMA sniffer) 29.rocep33s0f0 (RDMA sniffer) 30.rocep33s0f1 (RDMA sniffer) 31.rocep36s0f0 (RDMA sniffer) 32.ibp36s0f1 (RDMA sniffer) Locally build steps: clone sources: $ mkdir tcpdumpbuild $ cd tcpdumpbuild/ $ git clone https://github.com/the-tcpdump-group/tcpdump.git $ git clone https://github.com/the-tcpdump-group/libpcap.git install required packages (including rdma packages so libpcap is built with rdma enabled): $ apt install flex bison librdmacm-dev librdmacm1 rdma-core rdmacm-utils configure and build $ cd libpcap $ ./autogen.sh $ ./configure --enable-rdma=yes $ make cd ../tcpdump/ ./autogen.sh ./configure $ make now ./tcpdump -D can show rdma devices. Thanks ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpcap/+bug/2006557/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950644] Re: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels
The API that was failing in this test was introduced in the 4.6 kernel
series (in b844f0ecbc56 ("vfs: define kernel_copy_file_from_fd()")), so
trusty's 4.4 kernel should not be affected. The linux-azure 4.15 kernels
in trusty and xenial have the needed fix applied, are they still
affected by this bug?
** Changed in: linux-azure (Ubuntu Jammy)
Status: New => Fix Released
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed => Invalid
** Changed in: linux-azure (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1950644
Title:
ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Trusty:
Invalid
Status in linux-azure source package in Trusty:
New
Status in linux-oem-5.10 source package in Trusty:
Invalid
Status in linux-oem-5.13 source package in Trusty:
Invalid
Status in linux-oem-5.14 source package in Trusty:
Invalid
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
New
Status in linux-oem-5.10 source package in Bionic:
Invalid
Status in linux-oem-5.13 source package in Bionic:
Invalid
Status in linux-oem-5.14 source package in Bionic:
Invalid
Status in linux source package in Focal:
Fix Released
Status in linux-azure source package in Focal:
Fix Released
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux-oem-5.13 source package in Focal:
Fix Released
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in linux-azure source package in Hirsute:
Fix Released
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux-oem-5.14 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Fix Released
Status in linux-azure source package in Impish:
Fix Released
Status in linux-oem-5.10 source package in Impish:
Invalid
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux-azure source package in Jammy:
Fix Released
Status in linux-oem-5.10 source package in Jammy:
Invalid
Status in linux-oem-5.13 source package in Jammy:
Invalid
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[Impact]
Some uses of kernel_read_file_from_fd may lead to a WARN when the file is
not opened for reading.
The WARNING, however, is not present on earlier kernels, which will return
a different error code. The fix, however, has been applied to upstream stable
and may be worth so tests can PASS without much change.
[Fix/Backport]
The fix is trivial, but the backport for Focal and Bionic was picked up
from 5.4.y upstream stable tree, because the function was moved to a
different file.
[Test case]
The finit_module02 test case from LTP covers this.
[Potential regression]
kernel_read_file_from_fd is used for module loading and kexec, so there is
where regressions might show up.
=
ubuntu_ltp / finit_module02 fails on Bionic Azure FIPS
(4.15.0-2039.43), Bionic Azure (4.15.0-1127.140), Focal Azure
(5.4.0-1064.67):
tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s
finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9)
finit_module02.c:119: TPASS: TestName: zero-fd : EINVAL (22)
finit_module02.c:119: TPASS: TestName: null-param : EFAULT (14)
finit_module02.c:119: TPASS: TestName: invalid-param : EINVAL (22)
finit_module02.c:119: TPASS: TestName: invalid-flags : EINVAL (22)
tst_capability.c:29: TINFO: Dropping CAP_SYS_MODULE(16)
finit_module02.c:119: TPASS: TestName: no-perm : EPERM (1)
tst_capability.c:41: TINFO: Permitting CAP_SYS_MODULE(16)
finit_module02.c:119: TPASS: TestName: module-exists : EEXIST (17)
finit_module02.c:119: TFAIL: TestName: file-not-readable expected EBADF:
ETXTBSY (26)
finit_module02.c:119: TPASS: TestName: directory : EINVAL (22)
HINT: You _MAY_ be missing kernel fixes, see:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=032146cda855
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950644/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to :
[Kernel-packages] [Bug 2000708] Re: udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper)
** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Medium -- 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/2000708 Title: udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Kinetic: In Progress Status in linux source package in Lunar: In Progress Bug description: Issue found with 5.19.0-28.29 Running 'make run_tests -C net TEST_PROGS=udpgro_frglist.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' TAP version 13 1..1 # selftests: net: udpgro_frglist.sh # Missing nat6to4 helper. Build bpfnat6to4.o selftest first not ok 1 selftests: net: udpgro_frglist.sh # exit=255 This is not a regression as the net test build was blocked with bug 1993155 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1976184] Re: Linux PV device frontends vulnerable to attacks by backends
All of these CVEs related to https://xenbits.xen.org/xsa/advisory-396.html have been addressed in every kernel except for - Ubuntu 20.04's linux-oem-5.14 - CVE-2022-23041 has not been addressed in the 4.15 based kernels. -- 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/1976184 Title: Linux PV device frontends vulnerable to attacks by backends Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-aws-5.15 package in Ubuntu: Fix Released Status in linux-aws-5.4 package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure-5.4 package in Ubuntu: Fix Released Status in linux-bluefield package in Ubuntu: Fix Released Status in linux-dell300x package in Ubuntu: New Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp-4.15 package in Ubuntu: New Status in linux-gcp-5.4 package in Ubuntu: Fix Released Status in linux-gke package in Ubuntu: Fix Released Status in linux-gke-5.4 package in Ubuntu: Fix Released Status in linux-gkeop package in Ubuntu: Fix Released Status in linux-gkeop-5.4 package in Ubuntu: Fix Released Status in linux-hwe-5.4 package in Ubuntu: Fix Released Status in linux-ibm package in Ubuntu: Fix Released Status in linux-ibm-5.4 package in Ubuntu: Fix Released Status in linux-intel-iotg-5.15 package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: Won't Fix Status in linux-oracle package in Ubuntu: New Status in linux-oracle-5.4 package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi-5.4 package in Ubuntu: Fix Released Status in linux-snapdragon package in Ubuntu: New Bug description: The packages listed above are vulnerable to the CVEs below in at least one Ubuntu release, as stated in the Ubuntu CVE Tracker, except for linux-azure-4.15, linux-dell300x, linux-gcp-4.15 and linux-snapdragon, that are only vulnerable to CVE-2022-23041. Please release fixed packages. Xen released a security advisory on March 10. (I was informed by the security team that it does not track security issues via Launchpad bugs, but in the Ubuntu CVE Tracker. However, the issue is unpatched for over 2.5 months and marked as needed for these combinations of source package and Ubuntu version in the Tracker, and therefore I am filing this bug.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004613] Re: Intel UHD Graphics 770 (ADL-S GT1) max res 1920x1080, should be 4K
Yes there's a problem with the cable or the port here. Looking at Dell's website they seem to confirm the built-in HDMI port on the Optiplex 3000 only supports HDMI 1.4, so it can't do 4K60Hz. To get HDMI 2.0 support on the Optiplex 3000 you need to be using the optional add-on port which screws into the rear panel. If you didn't get that optional second HDMI port with the machine then your only solution will be to use the DisplayPort. ** Package changed: linux (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Incomplete => Invalid -- 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/2004613 Title: Intel UHD Graphics 770 (ADL-S GT1) max res 1920x1080, should be 4K Status in Ubuntu: Invalid Bug description: This GPU should be capable of 4K resolution, but it's unavailable. Tried manually adding modeline with xrandr --newmode "3840x2160_60.00" 712.75 3840 4160 4576 5312 2160 2163 2168 2237 -hsync +vsync xrandr --addmode HDMI-3 "3840x2160_60.00" Still fails to set 4K resolution. Upgraded to signed kernel 5.19.0-28-generic #29~22.04.1-Ubuntu, added linux-modules-extra, ensured that system is loading i915 kernel module. inxi -G Graphics: Device-1: Intel driver: i915 v: kernel Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa Intel UHD Graphics 770 (ADL-S GT1) v: 4.6 Mesa 22.0.5 lspci -k | head -10 00:00.0 Host bridge: Intel Corporation Device 4650 (rev 05) Subsystem: Dell Device 0ac5 00:02.0 VGA compatible controller: Intel Corporation Device 4690 (rev 0c) Subsystem: Dell Device 0ac5 Kernel driver in use: i915 Kernel modules: i915 xrandr Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384 DP-1 disconnected (normal left inverted right x axis y axis) HDMI-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) HDMI-2 disconnected (normal left inverted right x axis y axis) HDMI-3 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 800mm x 450mm 1920x1080 60.00* 59.9430.0024.0029.9723.98 1920x1080i60.0059.94 1680x1050 59.88 1280x1024 75.0260.02 1440x900 59.90 1280x960 60.00 1360x768 60.02 1280x800 59.91 1152x864 75.00 1280x720 60.0030.0059.9429.9724.0023.98 1024x768 75.0370.0760.00 800x600 72.1975.0060.32 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0072.8160.0059.94 720x400 70.08 3840x2160_60.00 59.98 # <--- manually configured xrandr --output HDMI-3 --mode 3840x2160_60.00 xrandr: Configure crtc 0 failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-28.29~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Thu Feb 2 22:00:36 2023 DistUpgraded: 2023-01-28 19:49:57,594 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:4690] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0ac5] InstallationDate: Installed on 2020-07-18 (929 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 0480:0110 Toshiba America Inc External USB 3.0 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0c8 Foxconn / Hon Hai Wireless_Device Bus 001 Device 002: ID 248a:8367 Maxxter Telink Wireless Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 3000 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-28-generic root=/dev/mapper/vgkubuntu-root ro nosplash SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2023-01-29 (5 days ago) dmi.bios.date: 05/18/2022 dmi.bios.release: 1.1 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.60 dmi.board.name: 057FFP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
The locality to this apparmor denial suggests to me it's just the bluez snap that needs to request some extra privileges. Feb 07 23:50:34 ubuntu audit[1562]: AVC apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1562 comm="bluetoothd" family="alg" sock_type="seqpacket" protocol=0 requested_mask="create" denied_mask="create" Feb 07 23:50:34 ubuntu bluetoothd[1562]: src/advertising.c:read_adv_features_callback() Failed to read advertising features: Not Supported (0x0c) ** Package changed: linux (Ubuntu) => bluez (Ubuntu) -- 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/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
** Description changed:
[Impact]
With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting
while entering graphics mode.
[Fix]
These 3 commits fix the issue
a8671493d207 drm/amdgpu: make sure to init common IP before gmc
e3163bc8ffdf drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for
vega
dc1d85cb790f drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
+
+ cherry picked one moew commit as it fixes e3163bc8ffdfdb ("drm/amdgpu: move
nbio sdma_doorbell_range() into sdma code for vega")
+ 50b0e4d4da09 drm/amdgpu: fix sdma doorbell init ordering on APUs
==
V1.
AMD provides a list of commits to fix this issue
1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a
2. drm/amdgpu: Don't enable LTR if not supported
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=6c20490663553cd7e07d8de8af482012329ab9d6
3. Patch series: fix PCI AER issues
drm/amdgpu: make sure to init common IP before gmc
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=a8671493d2074950553da3cf07d1be43185ef6c6
drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=e3163bc8ffdfdb405e10530b140135b2ee487f89
drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=dc1d85cb790f2091eea074cee24a704b2d6c4a06
4. Disable amdgpu runpm, will have a update later.
https://patchwork.freedesktop.org/patch/507366/
[Test]
Verified on the machine with AMD graphic card, and confirmed the issue is
gone.
[Where problems could occur]
The main idea is to disable BACO on those cards, the fix is quite
straightforward with 2 Fixes commits, have impact on limited cards.
--
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/2000110
Title:
Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-5.17 source package in Jammy:
In Progress
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
In Progress
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-oem-5.17 source package in Lunar:
Invalid
Status in linux-oem-6.0 source package in Lunar:
Invalid
Bug description:
[Impact]
With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting
while entering graphics mode.
[Fix]
These 3 commits fix the issue
a8671493d207 drm/amdgpu: make sure to init common IP before gmc
e3163bc8ffdf drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for
vega
dc1d85cb790f drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
cherry picked one moew commit as it fixes e3163bc8ffdfdb ("drm/amdgpu: move
nbio sdma_doorbell_range() into sdma code for vega")
50b0e4d4da09 drm/amdgpu: fix sdma doorbell init ordering on APUs
==
V1.
AMD provides a list of commits to fix this issue
1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a
2. drm/amdgpu: Don't enable LTR if not supported
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=6c20490663553cd7e07d8de8af482012329ab9d6
3. Patch series: fix PCI AER issues
drm/amdgpu: make sure to init common IP before gmc
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=a8671493d2074950553da3cf07d1be43185ef6c6
drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=e3163bc8ffdfdb405e10530b140135b2ee487f89
drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=dc1d85cb790f2091eea074cee24a704b2d6c4a06
4. Disable amdgpu runpm, will have a update later.
https://patchwork.freedesktop.org/patch/507366/
[Test]
Verified on the machine with AMD graphic card, and confirmed the issue is
gone.
[Where problems could occur]
The main idea is to disable BACO on those cards,
[Kernel-packages] [Bug 2006636] Re: [Dell Inspiron 5521] Many Cyan Lines Cover Computer Screen
That's quite unusual. I would lean toward thinking that's a broken LCD panel. Just in case, please also remember to run: sudo update-grub after editing /etc/default/grub. And then reboot. -- 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/2006636 Title: [Dell Inspiron 5521] Many Cyan Lines Cover Computer Screen Status in linux package in Ubuntu: Incomplete Bug description: bunch of cyan lines appearing on my screen rapidly, pretty sure its a hardware issue but want to make sure the graphics drivers are up to date. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 13:34:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597] InstallationDate: Installed on 2023-02-06 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5521 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=da01a44b-4a96-4996-b2a4-594d4bcfee21 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0K08H3 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd04/18/2013:efr1.1:svnDellInc.:pnInspiron5521:pvrA07:rvnDellInc.:rn0K08H3:rvrA02:cvnDellInc.:ct8:cvrA07:skuxxx123x#ABA: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 5521 dmi.product.sku: xxx123x#ABA dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000110] Re: Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
** Changed in: linux (Ubuntu Kinetic)
Status: In Progress => Fix Released
--
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/2000110
Title:
Keeps rebooting with AMD W6400, W6600, and W6800 graphic cards
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.17 package in Ubuntu:
Invalid
Status in linux-oem-6.0 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Won't Fix
Status in linux-oem-5.17 source package in Jammy:
In Progress
Status in linux-oem-6.0 source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Status in linux-oem-5.17 source package in Kinetic:
Invalid
Status in linux-oem-6.0 source package in Kinetic:
Invalid
Status in linux source package in Lunar:
Fix Released
Status in linux-oem-5.17 source package in Lunar:
Invalid
Status in linux-oem-6.0 source package in Lunar:
Invalid
Bug description:
[Impact]
With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting
while entering graphics mode.
[Fix]
These 3 commits fix the issue
a8671493d207 drm/amdgpu: make sure to init common IP before gmc
e3163bc8ffdf drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for
vega
dc1d85cb790f drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
cherry picked one moew commit as it fixes e3163bc8ffdfdb ("drm/amdgpu: move
nbio sdma_doorbell_range() into sdma code for vega")
50b0e4d4da09 drm/amdgpu: fix sdma doorbell init ordering on APUs
==
V1.
AMD provides a list of commits to fix this issue
1. drm/amdgpu: Remove ATC L2 access for MMHUB 2.1.x
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=d2c4c1569a7d7d5c8f75963bf2d62d7aeac30e2a
2. drm/amdgpu: Don't enable LTR if not supported
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=6c20490663553cd7e07d8de8af482012329ab9d6
3. Patch series: fix PCI AER issues
drm/amdgpu: make sure to init common IP before gmc
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=a8671493d2074950553da3cf07d1be43185ef6c6
drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=e3163bc8ffdfdb405e10530b140135b2ee487f89
drm/amdgpu: move nbio ih_doorbell_range() into ih code for vega
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20221107=dc1d85cb790f2091eea074cee24a704b2d6c4a06
4. Disable amdgpu runpm, will have a update later.
https://patchwork.freedesktop.org/patch/507366/
[Test]
Verified on the machine with AMD graphic card, and confirmed the issue is
gone.
[Where problems could occur]
The main idea is to disable BACO on those cards, the fix is quite
straightforward with 2 Fixes commits, have impact on limited cards.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2000110/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006636] Re: [Dell Inspiron 5521] Many Cyan Lines Cover Computer Screen
Actually I might have seen artifacts like that before. It was when I was swapping LCD panels and I didn't have a clean connection on the ribbon cable between the LCD and the laptop's motherboard. If you don't know how to check that then it's safest not to try. -- 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/2006636 Title: [Dell Inspiron 5521] Many Cyan Lines Cover Computer Screen Status in linux package in Ubuntu: Incomplete Bug description: bunch of cyan lines appearing on my screen rapidly, pretty sure its a hardware issue but want to make sure the graphics drivers are up to date. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 13:34:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597] InstallationDate: Installed on 2023-02-06 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5521 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=da01a44b-4a96-4996-b2a4-594d4bcfee21 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0K08H3 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd04/18/2013:efr1.1:svnDellInc.:pnInspiron5521:pvrA07:rvnDellInc.:rn0K08H3:rvrA02:cvnDellInc.:ct8:cvrA07:skuxxx123x#ABA: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 5521 dmi.product.sku: xxx123x#ABA dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002013] Re: Fix headset mic not working issue on Dell Latitude 5340
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Assignee: (unassigned) => Chris Chiu (mschiu77) -- 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/2002013 Title: Fix headset mic not working issue on Dell Latitude 5340 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: New Status in linux-oem-6.0 source package in Kinetic: New Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] The Dell Latitude 5430 with Realtek audio codec ALC3254 fail to detect the headphone microphone and thus unable to record audio. [Fix] The realtek audio quirk ALC269_FIXUP_DELL4_MIC_NO_PRESENCE is required since the NID used for headphone microphone should be 0x1b instead of 0x1a, which is used for former ALC225/295 variants. [Test Case] 1. Plug in the headphone microphone on the problematic Dell Latitude 5430 laptop 2. Make sure it's detected in Audio Settings. (pulseaudio) 3. Record the sound via the headphone microphone and check the recorded content. [Where problems could occur] No. Since the audio fixup is only applied on the machine with particular subsystem ID. [Other Info] This is not yet available in mainline kernel but in linux-next, and need to be applied after SRU lp:2000909 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002373] Re: Mic Mute LED doesn't work on DMIC laptops
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2002373 Title: Mic Mute LED doesn't work on DMIC laptops Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Released Status in alsa-ucm-conf source package in Kinetic: Fix Released Status in alsa-ucm-conf source package in Lunar: Fix Released Bug description: [Impact] Mic mute LED doesn't work on Intel-based HP laptops. [Fix] Due to recent change on how kernel creates sound LEDs, there are two captures are registered, one from SoF and one from HDA. The SoF one is the "real" capture system uses. Since physical LED only gets light up when _all_ captures are muted, detach the HDA one so micmute LED only need to consider SoF capture's mute status. [Test] The mic mute LED works again on DMIC laptops. The legacy HDA systems are unaffected. [Where problems could occur] Theoretically the system may have more than two internal captures registered, then disabling one will not be enough. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006042] [NEW] [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram
You have been subscribed to a public bug: Hi, After waking up from suspend to RAM, my computer actually wakes up but can sometimes then hang on a black screen (no prompt, nothing displayed, screen is active). This issue happens quite frequently but seems rather random. I think certain circumstances lower the frequency (I'll elaborate in the report). First of all, I'm not exactly sure when it started but I would say first notable frequent occurrences were around summer 2021 (yes, I'm late, sorry for that). When this happens, Algr+SysRQ+[usb] is unresponsive. Or at least that's what I used to believe as it used to be true as I always tried from the laptop integrated keyboard. Until I connected an USB-C mechanical keyboard, from which I'm *sometimes* able to use the magic keys (not always, and with a lot of lag, but still). If magic keys are unresponsive, I need to hard reset/long press power. There is nothing unusual before that in syslog nor kern.log, at least not that I know of. Except the ^@^@^@ characters when I had to hard reset the computer. If I leave the laptop like that for a while, it eventually reboots by itself and stays on the FDE passphrase prompt (which is not nice as the screen can then stay on for a very long like that if I did not notice). I'm running KDE/Plasma desktop, and this issue has happened regardless of the display manager. I used to run Xorg but now I'm on wayland flavor (mostly to alleviate firefox rendering/compositing issues). This also seems unrelated to external screen being connected or not, as it happened in the past regardless of that parameter. Although, it *seems* frequency has lowered a bit since I changed the way I wake up my laptop. Higher frequency (almost every day): - no external screen or external screen connected to HDMI port - waking up from integrated keyboard power button short press Lower frequency (one to multiple times a week, but somewhat irregular, since ~ 2 months ago): - external screen connected to USB-C port - mechanical keyboard connected to USB-C port of screen - waking up from the mechanical keyboard It also seems to happen more frequently if I wake up the computer, do some very fast task and send it to sleep in under a few minutes. It's not guaranteed to happen, but seems to highly increase the probability. Also, this might be related so I'm adding that bit: I had to disable shutting the screen Off in energy saving settings, as enabling that option would trigger a similar behavior after a break long enough for that setting to trigger. I would come back on a laptop having self-rebooted and waiting for my input on the FDE passphrase prompt. During ACPI options testing, I noticed that setting might cause the sleep order to get cancelled. From that, I suspect in that case the laptop would go to sleep, then wake up immediately, which could have been triggering the bug as I described previously that rapid state changes would increase probability. Then as I described earlier, if I do nothing when this happens, the computer eventually reboots. This is only speculation as I'm usually not here to observe the behavior (this mostly happened during lunch breaks, which are long enough for all of these steps to happen). I disabled screen turn-off energy saving option a long while ago and have taken the habit of manually suspending to RAM when I intend on going away from the computer for more than a few minutes. As I described above, I've tried a few changes to check for behavior but that was a few months ago and I don't clearly remember all scenario. What I remember is that changing any of these did not resolve my issue and some even prevented my computer to even suspend to RAM properly (waking up immediately after). Among the options I tried is: - booting with a previous kernel, but then it's been happening for so long this would obviously not work (just for the sake of completion) - booting on latest mainstream kernel (tested linux-image-unsigned-6.0.9-060009-generic, this was the latest version when I tried a while ago) - booting with i915.enable_dpcd_backlight=3 (I think this one triggered the immediate wake up) - booting with nolapic, noapic (didn't try acpi=off nor acpi=ht as it seems to me it would disable suspend to RAM feature, right?) I think that's about it, and I'd be happy to try any suggestion. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: KDE Date: Sun Feb 5 12:41:36 2023 DistUpgraded: 2022-08-20 16:46:28,280 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu
[Kernel-packages] [Bug 1950644] Re: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels
Note that this test is still failing on X-4.4 AWS and T-4.4 AWS. INFO: Test start time: Wed Jan 4 12:03:51 UTC 2023 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 24091 -n 24091 -f /tmp/ltp-uU5zrx72XR/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_test.c:1528: TINFO: Timeout per run is 0h 00m 30s tst_kconfig.c:82: TINFO: Parsing kernel config '/lib/modules/4.4.0-1115-aws/build/.config' tst_lockdown.c:60: TINFO: Unable to determine system lockdown state finit_module02.c:122: TPASS: TestName: invalid-fd : ENOEXEC (8) finit_module02.c:122: TPASS: TestName: zero-fd : EINVAL (22) finit_module02.c:122: TPASS: TestName: null-param : EFAULT (14) finit_module02.c:122: TPASS: TestName: invalid-param : EINVAL (22) finit_module02.c:122: TPASS: TestName: invalid-flags : EINVAL (22) tst_capability.c:29: TINFO: Dropping CAP_SYS_MODULE(16) finit_module02.c:122: TPASS: TestName: no-perm : EPERM (1) tst_capability.c:41: TINFO: Permitting CAP_SYS_MODULE(16) finit_module02.c:122: TPASS: TestName: module-exists : EEXIST (17) finit_module02.c:122: TPASS: TestName: file-not-readable : EBADF (9) finit_module02.c:122: TFAIL: TestName: file-readwrite succeeded finit_module02.c:122: TPASS: TestName: directory : EISDIR (21) HINT: You _MAY_ be missing kernel fixes: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=032146cda855 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=39d637af5aa7 Summary: passed 9 failed 1 broken 0 skipped 0 warnings 0 Since they are ESM kernel now, I will mark them as won't fix. ** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu) Status: New => Fix Released ** Changed in: linux-aws (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-aws (Ubuntu Impish) Status: New => Fix Released ** Changed in: linux-aws (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: linux-aws (Ubuntu Bionic) Status: New => Fix Released ** Changed in: linux-aws (Ubuntu Focal) Status: New => Fix Released ** Changed in: linux-aws (Ubuntu Trusty) Status: New => Invalid ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: linux (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: linux-azure (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: linux-oem-5.10 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Xenial) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950644 Title: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Trusty: Invalid Status in linux-aws source package in Trusty: Invalid Status in linux-azure source package in Trusty: Invalid Status in linux-oem-5.10 source package in Trusty: Invalid Status in linux-oem-5.13 source package in Trusty: Invalid Status in linux-oem-5.14 source package in Trusty: Invalid Status in linux source package in Xenial: Won't Fix Status in linux-aws source package in Xenial: Won't Fix Status in linux-azure source package in Xenial: Won't Fix Status in linux-oem-5.10 source package in Xenial: Invalid Status in linux-oem-5.13 source package in Xenial: Invalid Status in linux-oem-5.14 source package in Xenial: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux
[Kernel-packages] [Bug 2006042] Re: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram
Thanks. It seems the kernel isn't waking from sleep. Can you attach a copy of /proc/acpi/wakeup ? ** Package changed: ubuntu => linux (Ubuntu) -- 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/2006042 Title: [Asus ZenBook UX430UAR] Laptop often freezes after waking up from suspend to ram Status in linux package in Ubuntu: Incomplete Bug description: Hi, After waking up from suspend to RAM, my computer actually wakes up but can sometimes then hang on a black screen (no prompt, nothing displayed, screen is active). This issue happens quite frequently but seems rather random. I think certain circumstances lower the frequency (I'll elaborate in the report). First of all, I'm not exactly sure when it started but I would say first notable frequent occurrences were around summer 2021 (yes, I'm late, sorry for that). When this happens, Algr+SysRQ+[usb] is unresponsive. Or at least that's what I used to believe as it used to be true as I always tried from the laptop integrated keyboard. Until I connected an USB-C mechanical keyboard, from which I'm *sometimes* able to use the magic keys (not always, and with a lot of lag, but still). If magic keys are unresponsive, I need to hard reset/long press power. There is nothing unusual before that in syslog nor kern.log, at least not that I know of. Except the ^@^@^@ characters when I had to hard reset the computer. If I leave the laptop like that for a while, it eventually reboots by itself and stays on the FDE passphrase prompt (which is not nice as the screen can then stay on for a very long like that if I did not notice). I'm running KDE/Plasma desktop, and this issue has happened regardless of the display manager. I used to run Xorg but now I'm on wayland flavor (mostly to alleviate firefox rendering/compositing issues). This also seems unrelated to external screen being connected or not, as it happened in the past regardless of that parameter. Although, it *seems* frequency has lowered a bit since I changed the way I wake up my laptop. Higher frequency (almost every day): - no external screen or external screen connected to HDMI port - waking up from integrated keyboard power button short press Lower frequency (one to multiple times a week, but somewhat irregular, since ~ 2 months ago): - external screen connected to USB-C port - mechanical keyboard connected to USB-C port of screen - waking up from the mechanical keyboard It also seems to happen more frequently if I wake up the computer, do some very fast task and send it to sleep in under a few minutes. It's not guaranteed to happen, but seems to highly increase the probability. Also, this might be related so I'm adding that bit: I had to disable shutting the screen Off in energy saving settings, as enabling that option would trigger a similar behavior after a break long enough for that setting to trigger. I would come back on a laptop having self-rebooted and waiting for my input on the FDE passphrase prompt. During ACPI options testing, I noticed that setting might cause the sleep order to get cancelled. From that, I suspect in that case the laptop would go to sleep, then wake up immediately, which could have been triggering the bug as I described previously that rapid state changes would increase probability. Then as I described earlier, if I do nothing when this happens, the computer eventually reboots. This is only speculation as I'm usually not here to observe the behavior (this mostly happened during lunch breaks, which are long enough for all of these steps to happen). I disabled screen turn-off energy saving option a long while ago and have taken the habit of manually suspending to RAM when I intend on going away from the computer for more than a few minutes. As I described above, I've tried a few changes to check for behavior but that was a few months ago and I don't clearly remember all scenario. What I remember is that changing any of these did not resolve my issue and some even prevented my computer to even suspend to RAM properly (waking up immediately after). Among the options I tried is: - booting with a previous kernel, but then it's been happening for so long this would obviously not work (just for the sake of completion) - booting on latest mainstream kernel (tested linux-image-unsigned-6.0.9-060009-generic, this was the latest version when I tried a while ago) - booting with i915.enable_dpcd_backlight=3 (I think this one triggered the immediate wake up) - booting with nolapic, noapic (didn't try acpi=off nor acpi=ht as it seems to me it would disable suspend to RAM feature, right?) I think that's about it, and I'd be happy to try any suggestion. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg
[Kernel-packages] [Bug 2006636] [NEW] [Dell Inspiron 5521] Many Cyan Lines Cover Computer Screen
You have been subscribed to a public bug: bunch of cyan lines appearing on my screen rapidly, pretty sure its a hardware issue but want to make sure the graphics drivers are up to date. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 13:34:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597] InstallationDate: Installed on 2023-02-06 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5521 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=da01a44b-4a96-4996-b2a4-594d4bcfee21 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0K08H3 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd04/18/2013:efr1.1:svnDellInc.:pnInspiron5521:pvrA07:rvnDellInc.:rn0K08H3:rvrA02:cvnDellInc.:ct8:cvrA07:skuxxx123x#ABA: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 5521 dmi.product.sku: xxx123x#ABA dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy ubuntu -- [Dell Inspiron 5521] Many Cyan Lines Cover Computer Screen https://bugs.launchpad.net/bugs/2006636 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002968] Re: Fix flicker display problem on some panels which support PSR2
** Changed in: linux-oem-6.0 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid -- 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/2002968 Title: Fix flicker display problem on some panels which support PSR2 Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Incomplete Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Incomplete Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] On some PSR2 supported panels, which connects to Intel Graphics has flicker symptom. It gets normal after booting the kernel with parameter `i915. enable_psr=0` [Fix] Backport one patch from upstream. https://cgit.freedesktop.org/drm-tip/commit/drivers/gpu/drm/i915/display/intel_psr.c?id=084aab04cc60e5eab32287d0483c33e12c92da87 [Test] Booting the patched kernel with problematic panel (LGD LCD_VD78M), check if the display has abnormal flickering problem on graphics interfaces. [Where problems could occur] The risk of regression is low. It only fixes problem on panels which support PSR2. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006458] Re: Frequent wakeups on HP Pro x360 435 13.3 inch G9 using Qualcomm FastConnect 6900
** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: New -- 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/2006458 Title: Frequent wakeups on HP Pro x360 435 13.3 inch G9 using Qualcomm FastConnect 6900 Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: New Status in linux-firmware source package in Kinetic: New Status in linux-firmware source package in Lunar: New Bug description: To whom it may concern: I was experiencing frequent wake-ups from s0i3x on a HP Pro 435 G9 convertible [1] using the Qualcomm FastConnect 6900 Soc [2]. The issue is related to FW revision WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.9 that comes bundled with Ubuntu 22.10. It appears the SoC increasingly triggering wake-ups after being suspended for approx. 4 hrs. Read the full story at [4]. The solution is to upgrade SoC firmware to rev WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23/ [3] Best regards,Carsten [1] https://support.hp.com/us-en/product/hp-pro-x360-435-13.3-inch-g9-notebook-pc/2101144107/document/ish_6053745-6053789-16 [2] https://www.qualcomm.com/products/technology/wi-fi/fastconnect/fastconnect-6900 [3] https://github.com/kvalo/ath11k-firmware/tree/master/WCN6855/hw2.0/1.1/WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.23 [4] https://gitlab.freedesktop.org/drm/amd/-/issues/2377 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2006458/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006636] Re: [Dell Inspiron 5521] Many Cyan Lines Cover Computer Screen
I have adjusted the kernel parameters by opening the grub file at /etc/default/grub and changing the GRUB_CMDLINE_LINUX_DEFAULT from "quiet splash" to "quiet splash i915.enable_psr=0". No significant change to the issue has occurred. ** Attachment added: "blueLines.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006636/+attachment/5645754/+files/blueLines.jpg -- 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/2006636 Title: [Dell Inspiron 5521] Many Cyan Lines Cover Computer Screen Status in linux package in Ubuntu: Incomplete Bug description: bunch of cyan lines appearing on my screen rapidly, pretty sure its a hardware issue but want to make sure the graphics drivers are up to date. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 13:34:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597] InstallationDate: Installed on 2023-02-06 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5521 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=da01a44b-4a96-4996-b2a4-594d4bcfee21 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0K08H3 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd04/18/2013:efr1.1:svnDellInc.:pnInspiron5521:pvrA07:rvnDellInc.:rn0K08H3:rvrA02:cvnDellInc.:ct8:cvrA07:skuxxx123x#ABA: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 5521 dmi.product.sku: xxx123x#ABA dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002013] Re: Fix headset mic not working issue on Dell Latitude 5340
included in Ubuntu-6.1.0-13.13 and up, and in oem-6.1 -1007 ** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Released ** Changed in: hwe-next Status: New => Fix Released ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-oem-6.1 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid -- 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/2002013 Title: Fix headset mic not working issue on Dell Latitude 5340 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: New Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Committed Status in linux source package in Kinetic: New Status in linux-oem-6.0 source package in Kinetic: New Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: New Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] The Dell Latitude 5430 with Realtek audio codec ALC3254 fail to detect the headphone microphone and thus unable to record audio. [Fix] The realtek audio quirk ALC269_FIXUP_DELL4_MIC_NO_PRESENCE is required since the NID used for headphone microphone should be 0x1b instead of 0x1a, which is used for former ALC225/295 variants. [Test Case] 1. Plug in the headphone microphone on the problematic Dell Latitude 5430 laptop 2. Make sure it's detected in Audio Settings. (pulseaudio) 3. Record the sound via the headphone microphone and check the recorded content. [Where problems could occur] No. Since the audio fixup is only applied on the machine with particular subsystem ID. [Other Info] This is not yet available in mainline kernel but in linux-next, and need to be applied after SRU lp:2000909 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950644] Re: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels
Hi Steve, sorry this was fell off from our radar. I can confirm that this issue does not exist with T-azure-4.15 / B-azure-4.15 anymore. INFO: Test start time: Thu Jan 12 03:57:05 UTC 2023 COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 2011 -n 2011 -f /tmp/ltp-ZOzvNj4f7j/alltests -l /dev/null -C /dev/null -T /dev/null LOG File: /dev/null FAILED COMMAND File: /dev/null TCONF COMMAND File: /dev/null Running tests... tst_test.c:1528: TINFO: Timeout per run is 0h 00m 30s tst_kconfig.c:82: TINFO: Parsing kernel config '/lib/modules/4.15.0-1159-azure/build/.config' tst_lockdown.c:60: TINFO: Unable to determine system lockdown state finit_module02.c:122: TPASS: TestName: invalid-fd : EBADF (9) finit_module02.c:122: TPASS: TestName: zero-fd : EINVAL (22) finit_module02.c:122: TPASS: TestName: null-param : EFAULT (14) finit_module02.c:122: TPASS: TestName: invalid-param : EINVAL (22) finit_module02.c:122: TPASS: TestName: invalid-flags : EINVAL (22) tst_capability.c:29: TINFO: Dropping CAP_SYS_MODULE(16) finit_module02.c:122: TPASS: TestName: no-perm : EPERM (1) tst_capability.c:41: TINFO: Permitting CAP_SYS_MODULE(16) finit_module02.c:122: TPASS: TestName: module-exists : EEXIST (17) finit_module02.c:122: TPASS: TestName: file-not-readable : EBADF (9) finit_module02.c:122: TPASS: TestName: file-readwrite : ETXTBSY (26) finit_module02.c:122: TPASS: TestName: directory : EINVAL (22) Summary: passed 10 failed 0 broken 0 skipped 0 warnings 0 Thanks! ** Changed in: linux-azure (Ubuntu Bionic) Status: New => Fix Released ** Changed in: linux-azure (Ubuntu Trusty) Status: New => Invalid ** Changed in: ubuntu-kernel-tests Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950644 Title: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Trusty: Invalid Status in linux-aws source package in Trusty: Invalid Status in linux-azure source package in Trusty: Invalid Status in linux-oem-5.10 source package in Trusty: Invalid Status in linux-oem-5.13 source package in Trusty: Invalid Status in linux-oem-5.14 source package in Trusty: Invalid Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: Won't Fix Status in linux-azure source package in Xenial: New Status in linux-oem-5.10 source package in Xenial: New Status in linux-oem-5.13 source package in Xenial: New Status in linux-oem-5.14 source package in Xenial: New Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux-azure source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-aws source package in Hirsute: Fix Released Status in linux-azure source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-aws source package in Impish: Fix Released Status in linux-azure source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-oem-5.10 source package in Jammy: Invalid Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Some uses of kernel_read_file_from_fd may lead to a WARN when the file is not opened for
[Kernel-packages] [Bug 2004235] Re: mlxbf-pmc counters not functional for llt_miss block
** 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/2004235 Title: mlxbf-pmc counters not functional for llt_miss block Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Currently, the driver uses fixed offsets for the control and data registers in the performance counter module. However, this is not correct since the module is not uniform in all HW blocks, and in this case, the llt_miss block is different from the rest. [Fix] The number of counters present in each block is not fixed, and hence the offsets for the control and data registers should also be calculated accordingly. [Test Case] Without the fix, writing 1 to the llt_miss "enable" file will not result in any of the counters incrementing. With the fix, the counters should increment even with the default event settings. [Regression Potential] Can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002501] Re: mlxbf-pmc support for BlueField-3
** 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/2002501 Title: mlxbf-pmc support for BlueField-3 Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Currently, the mlxbf-pmc driver supports only BlueField-1 and BlueField-2 devices. BlueField-3 is not supported. [Fix] Add support for BlueField-3 devices by adding new access mechanism for programming and reading counter values as in the new design, along with the list of supported events in each HW block in BlueField-3. [Test Case] Previously, the driver would not be loaded when the OS is loaded on a BlueField-3 card. With the fix, the driver should get loaded and create sysfs entries as a hwmon device under /sys/class/hwmon/hwmon0. [Regression Potential] The ACPI table needs to be in sync with this change since it depends on newly introduces parameters such as mss_enable and llt_enable, which were not present earlier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2002501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000909] Re: Microphone mute LED not working as expected after pressing the mic mute hotkey
is included in Ubuntu-6.1.0-13.13 and up, and in oem-6.1 -1007 ** Changed in: linux (Ubuntu Lunar) Status: In Progress => Fix Released ** Changed in: hwe-next Status: New => Fix Released ** Changed in: linux (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid -- 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/2000909 Title: Microphone mute LED not working as expected after pressing the mic mute hotkey Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Mic mute LED can't be toggled by the state of the mic-mute hotkey. [Fix] Create a new fixup to address the dual codec problem on particular platforms. [Test Case] Use the following command and check there's no duplicate mixer with the same name `Capture Switch`, `Capture Volume` $amixer controls [Where problems could occur] The commit only applies dual codec fixup on particular affected models. Should be no regression problem or any side effect to generic platforms. == original bug report == [Summary] Microphone mute LED won't turn on when pressing it [Steps to reproduce] 1. Press microphone mute hotkey [Expected result] LED turn on/off [Actual result] LED has no function when pressing the key [Failure rate] 3/3 [Additional information] CID: 202210-30776 SKU: QUKLA4-DVT1-C2-UBT Image: canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-quilladin+X64 system-manufacturer: Dell Inc. system-product-name: Latitude 3440 bios-version: 0.1.7 CPU: Genuine Intel(R) (12x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:a7a1] (rev 04) :01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1f9f] (rev a1) kernel-version: 6.0.0-1006-oem To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2000909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006636] Re: Many Cyan Lines Cover Computer Screen
Thanks for the bug report. Please try adding a kernel parameter: i915.enable_psr=0 Please also attach a photo of the problem. ** Summary changed: - Many Cyan Lines Cover Computer Screen + [Dell Inspiron 5521] Many Cyan Lines Cover Computer Screen ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/2006636 Title: [Dell Inspiron 5521] Many Cyan Lines Cover Computer Screen Status in linux package in Ubuntu: Incomplete Bug description: bunch of cyan lines appearing on my screen rapidly, pretty sure its a hardware issue but want to make sure the graphics drivers are up to date. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Feb 8 13:34:44 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:0597] InstallationDate: Installed on 2023-02-06 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5521 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=da01a44b-4a96-4996-b2a4-594d4bcfee21 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0K08H3 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd04/18/2013:efr1.1:svnDellInc.:pnInspiron5521:pvrA07:rvnDellInc.:rn0K08H3:rvrA02:cvnDellInc.:ct8:cvrA07:skuxxx123x#ABA: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 5521 dmi.product.sku: xxx123x#ABA dmi.product.version: A07 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006616] Re: package linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned erro
Your drive seems to be dying: [ 843.681582] sd 2:0:0:0: [sda] tag#16 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=35s [ 843.681588] sd 2:0:0:0: [sda] tag#16 CDB: Write(10) 2a 00 03 7d 98 00 00 0a 00 00 [ 843.681590] I/O error, dev sda, sector 58562560 op 0x1:(WRITE) flags 0x4000 phys_seg 71 prio class 0 [ 843.681609] sd 2:0:0:0: [sda] tag#31 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=33s [ 843.681611] sd 2:0:0:0: [sda] tag#31 CDB: Read(10) 28 00 06 38 06 a8 00 00 28 00 [ 843.681612] I/O error, dev sda, sector 104335016 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 843.681618] sd 2:0:0:0: [sda] tag#23 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=33s [ 843.681619] sd 2:0:0:0: [sda] tag#23 CDB: Read(10) 28 00 06 38 06 80 00 00 08 00 [ 843.681620] I/O error, dev sda, sector 104334976 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 843.681624] sd 2:0:0:0: [sda] tag#1 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=33s [ 843.681625] sd 2:0:0:0: [sda] tag#1 CDB: Read(10) 28 00 06 38 07 38 00 00 20 00 [ 843.681625] I/O error, dev sda, sector 104335160 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 843.681629] sd 2:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=33s [ 843.681630] sd 2:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 06 38 06 d8 00 00 10 00 [ 843.681631] I/O error, dev sda, sector 104335064 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 843.681726] sd 2:0:0:0: [sda] tag#30 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=32s [ 843.681730] sd 2:0:0:0: [sda] tag#30 CDB: Read(10) 28 00 01 ee e3 80 00 00 18 00 [ 843.681731] I/O error, dev sda, sector 32433024 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 843.681744] sd 2:0:0:0: [sda] tag#28 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=32s [ 843.681746] sd 2:0:0:0: [sda] tag#28 CDB: Read(10) 28 00 01 ee e3 50 00 00 08 00 [ 843.681747] I/O error, dev sda, sector 32432976 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 843.681751] sd 2:0:0:0: [sda] tag#27 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=32s [ 843.681752] sd 2:0:0:0: [sda] tag#27 CDB: Read(10) 28 00 01 ee e3 30 00 00 08 00 [ 843.681753] I/O error, dev sda, sector 32432944 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 843.681756] sd 2:0:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=32s [ 843.681757] sd 2:0:0:0: [sda] tag#8 CDB: Read(10) 28 00 06 36 c4 d0 00 00 20 00 [ 843.681758] I/O error, dev sda, sector 104252624 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 843.681762] sd 2:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=32s [ 843.681762] sd 2:0:0:0: [sda] tag#7 CDB: Read(10) 28 00 06 36 c4 a0 00 00 18 00 [ 843.681763] I/O error, dev sda, sector 104252576 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 843.681779] ata3: EH complete [ 843.689059] EXT4-fs warning (device sda3): ext4_end_bio:343: I/O error 10 writing to inode 3155395 starting block 7321280) [ 843.789948] Buffer I/O error on device sda3, logical block 7188480 [ 843.789955] Buffer I/O error on device sda3, logical block 7188481 [ 843.789957] Buffer I/O error on device sda3, logical block 7188482 [ 843.789958] Buffer I/O error on device sda3, logical block 7188483 [ 843.789959] Buffer I/O error on device sda3, logical block 7188484 [ 843.789960] Buffer I/O error on device sda3, logical block 7188485 [ 843.789961] Buffer I/O error on device sda3, logical block 7188486 [ 843.789962] Buffer I/O error on device sda3, logical block 7188487 -- 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/2006616 Title: package linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: Invalid Bug description: I ran the software update after a fresh install of 22.10. I had another instance yesterday where I had a similar issue, but I didn't send a report for it. I have 3 VMs of Ubuntu 22.10. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jobrien1609 F wireplumber /dev/snd/seq:jobrien1607 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed Feb 8 11:11:11 2023 Dependencies: firmware-sof-signed 2.1.1-1ubuntu1.1 ErrorMessage: installed linux-firmware package
[Kernel-packages] [Bug 2006692] Re: net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New -- 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/2006692 Title: net:fcnal-test.sh didn't return a non-zero value even with some sub- tests failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: New Status in linux source package in Focal: New Status in linux source package in Jammy: New Status in linux source package in Kinetic: New Bug description: Test result on Jammy reports there are 5 failed test cases in this fcnal-test.sh test: # Tests passed: 857 # Tests failed: 5 ok 1 selftests: net: fcnal-test.sh However the test didn't return a non-zero value to mark it as failed, making it difficult to spot these failures: # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping out, vrf device+address bind - ns-B IPv6 LLA [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981173] Re: Clear PCI errors left from BIOS
Patch reverted at upstream, not going to carry it over. ** Changed in: linux (Ubuntu Kinetic) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1981173 Title: Clear PCI errors left from BIOS Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Won't Fix Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Errors like Master Abort can be flagged before setting up PCI devices. [Fix] Clear PCI status that BIOS handed over to the OS. [Test] Using `lspci`, no more errors after boot. [Where problems could occur] If there's any driver's probe routine depends on PCI status to have different behavior, this can cause some cracks. There doesn't seem to be any driver doing such insane thing though. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006546] Re: Improve arp_ndisc_evict_nocarrier.sh test result processing
** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium -- 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/2006546 Title: Improve arp_ndisc_evict_nocarrier.sh test result processing Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Bug description: [Impact] The arp_ndisc_evict_nocarrier.sh in selftests/net didn't pass a proper return value for failed test cases. Thus we might get false negatives if the last command runs successfully. [Fix] * 1856628baa selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier This patch can be cherry-picked into affected kernels. Lunar has been patched already. J-hwe-5.17 will be deprecated thus it will be skipped. [Test] Run the patched test, this should not cause any regression as sub tests are good with our kernels (except there is a cleanup issue in bug 1968310) One can deliberately fail a test by hijacking the if statement for the return value check to make sure this patch is working as expected. [Where problems could occur] This patch improves the result interpretation, we might see new failures being reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981773] Re: Make cm32181 sensor work after system suspend
** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1981773 Title: Make cm32181 sensor work after system suspend Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: New Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] cm32181 ambient light sensor stops working after system suspend. [Fix] Add PM support for cm32181 so it can work after system suspend. [Test] The sysfs in_illuminance_input continues to change after system suspend. [Where problems could occur] This changeset is limited to a specific device, and it already lacks PM support - so the worst case is that it stops working after resume like it always has been. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003161] Re: Fix speaker mute hotkey doesn't work on Dell G16 series
** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium -- 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/2003161 Title: Fix speaker mute hotkey doesn't work on Dell G16 series Status in HWE Next: New Status in HWE Next lunar series: Invalid Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: New Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Speaker mute and Mic mute hotkey no function on the G16. [Fix] speaker mute event is sent by EC then dell-wmi can't recognize it. Add a new keymap for KEY_MUTE. Send for OEM kernels first then will SRU for generic kernel once the patch is merged. [Test Case] 1. boot-up with the kernel applied the fix. 2. Play video/audio. 3. Press the speak-mute hotkey 4. can't hear any sounds. [Where problems could occur] Low, only add a keymap the affect would be very limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2003161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18
as already stated above I did provide log files manually, as apport- collect is not installed on this system. I'm happy to provide further logfiles to debug this issue. ** 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/1998224 Title: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18 Status in linux package in Ubuntu: Confirmed Bug description: situation: ubuntu 18.04 server install on a supermicro x64 host. hot plug NVME ssd into NVME U.2 HotSwap Slot. problem: hot plug does not work/ nvme is not recognised. how to test: echo 1 > /sys/bus/pci/rescan dmesg output: [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io 0x1000-0x0fff] to [bus 41] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io 0x1000-0x0fff] to [bus 42] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] Kernel Version: 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux hardware information: tried with micron and intel NVME, e.g: INTEL SSDPE2KE016T8 after a reboot, the NVME is recognized, so there is no hardware problem. if you need additional debug information, feel free to ask. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006488] Re: Kill linux-kvm flavour
** Description changed: Use !hypervisor_is_type(X86_HYPER_NATIVE) checks ffe782df80 UBUNTU: SAUCE: smpboot: reuse timer calibration -> probably redundant on kvmclock systems 3b458961f1 UBUNTU: SAUCE: Increase the ext4 default commit age -> livecd-rootfs should do this in the ext4 superblock 4983291d45 UBUNTU: SAUCE: [kvm] tsc: make no_timer_check default to 1 -> already default on kvm systems bd43e884f4 UBUNTU: SAUCE: [kvm] tsc: make tsc= default to reliable - -> kvm init should do what vmware init is doing and setting TSC_RELIABLE capability - wrmsrl(HV_X64_MSR_TSC_INVARIANT_CONTROL, 0x1); - setup_force_cpu_cap(X86_FEATURE_TSC_RELIABLE); + -> in practice recent changes do disable the watchdog already, but do keep the sync And then we should change config to move virtio & ext4 filesystems as built in. -- 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/2006488 Title: Kill linux-kvm flavour Status in linux package in Ubuntu: Triaged Bug description: Use !hypervisor_is_type(X86_HYPER_NATIVE) checks ffe782df80 UBUNTU: SAUCE: smpboot: reuse timer calibration -> probably redundant on kvmclock systems 3b458961f1 UBUNTU: SAUCE: Increase the ext4 default commit age -> livecd-rootfs should do this in the ext4 superblock 4983291d45 UBUNTU: SAUCE: [kvm] tsc: make no_timer_check default to 1 -> already default on kvm systems bd43e884f4 UBUNTU: SAUCE: [kvm] tsc: make tsc= default to reliable -> in practice recent changes do disable the watchdog already, but do keep the sync And then we should change config to move virtio & ext4 filesystems as built in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006588] [NEW] 5.19.0-1004.4-generic crashes with installed radeon graphics card
Public bug reported: I tried to install https://cdimage.ubuntu.com/ubuntu-server/daily- live/current/lunar-live-server-riscv64.img.gz on an SiFive HiFive Unmatches board with a Radeon graphics card. I saw a crash: [ 22.208410] [drm] Initialized radeon 2.50.0 20080528 for :07:00.0 on minor 0 [ 44.013359] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [systemd-udevd:189] [ 44.020117] Modules linked in: gpu_sched radeon i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper rtc_da9063 syscopyarea sysfillrect da9063_regulator sysimgblt fb_sys_fops nvme drm mscc backlight macsec xhci_pci nvme_core xhci_pci_renesas macb i2c_ocores phylink [ 44.045737] CPU: 2 PID: 189 Comm: systemd-udevd Not tainted 5.19.0-1004-generic #4-Ubuntu [ 44.053885] Hardware name: SiFive HiFive Unmatched A00 (DT) [ 44.059440] epc : apply_relocate_add+0x118/0x292 [ 44.064043] ra : apply_relocate_add+0x88/0x292 [ 44.068559] epc : 800088e4 ra : 80008854 sp : ffd89b55fc80 [ 44.075772] gp : 81e2e6c8 tp : ffd89bd1ce00 t0 : 02718510 [ 44.082981] t1 : 027ce160 t2 : 0001376b s0 : ffd89b55fd20 [ 44.090191] s1 : ffc895f8f2f8 a0 : 0001376b a1 : 025d4000 [ 44.097399] a2 : 027ce15c a3 : 027ce15c a4 : 0002cae4 [ 44.104609] a5 : 0003a641 a6 : 0001e8d6 a7 : [ 44.111818] s2 : ffc895f8e438 s3 : ffc895f8e538 s4 : 0017 [ 44.119028] s5 : f000 s6 : 0014 s7 : ffc895a3d1b0 [ 44.126236] s8 : 810014f0 s9 : 0033 s10: 0001e8d6 [ 44.133445] s11: 0001376b t3 : 0100 t4 : 80008374 [ 44.140655] t5 : 00430560 t6 : 02e2c000 [ 44.145949] status: 00020120 badaddr: cause: 8005 [ 44.153860] [] load_module+0x826/0x9fc [ 44.159152] [] __do_sys_finit_module+0x98/0xfe [ 44.165146] [] sys_finit_module+0x24/0x30 [ 44.170704] [] ret_from_syscall+0x0/0x2 [ 68.013359] watchdog: BUG: soft lockup - CPU#2 stuck for 45s! [systemd-udevd:189] [ 68.020111] Modules linked in: gpu_sched radeon i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper rtc_da9063 syscopyarea sysfillrect da9063_regulator sysimgblt fb_sys_fops nvme drm mscc backlight macsec xhci_pci nvme_core xhci_pci_renesas macb i2c_ocores phylink ** Affects: linux-riscv (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2006588 Title: 5.19.0-1004.4-generic crashes with installed radeon graphics card Status in linux-riscv package in Ubuntu: New Bug description: I tried to install https://cdimage.ubuntu.com/ubuntu-server/daily- live/current/lunar-live-server-riscv64.img.gz on an SiFive HiFive Unmatches board with a Radeon graphics card. I saw a crash: [ 22.208410] [drm] Initialized radeon 2.50.0 20080528 for :07:00.0 on minor 0 [ 44.013359] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [systemd-udevd:189] [ 44.020117] Modules linked in: gpu_sched radeon i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper rtc_da9063 syscopyarea sysfillrect da9063_regulator sysimgblt fb_sys_fops nvme drm mscc backlight macsec xhci_pci nvme_core xhci_pci_renesas macb i2c_ocores phylink [ 44.045737] CPU: 2 PID: 189 Comm: systemd-udevd Not tainted 5.19.0-1004-generic #4-Ubuntu [ 44.053885] Hardware name: SiFive HiFive Unmatched A00 (DT) [ 44.059440] epc : apply_relocate_add+0x118/0x292 [ 44.064043] ra : apply_relocate_add+0x88/0x292 [ 44.068559] epc : 800088e4 ra : 80008854 sp : ffd89b55fc80 [ 44.075772] gp : 81e2e6c8 tp : ffd89bd1ce00 t0 : 02718510 [ 44.082981] t1 : 027ce160 t2 : 0001376b s0 : ffd89b55fd20 [ 44.090191] s1 : ffc895f8f2f8 a0 : 0001376b a1 : 025d4000 [ 44.097399] a2 : 027ce15c a3 : 027ce15c a4 : 0002cae4 [ 44.104609] a5 : 0003a641 a6 : 0001e8d6 a7 : [ 44.111818] s2 : ffc895f8e438 s3 : ffc895f8e538 s4 : 0017 [ 44.119028] s5 : f000 s6 : 0014 s7 : ffc895a3d1b0 [ 44.126236] s8 : 810014f0 s9 : 0033 s10: 0001e8d6 [ 44.133445] s11: 0001376b t3 : 0100 t4 : 80008374 [ 44.140655] t5 : 00430560 t6 : 02e2c000 [ 44.145949] status: 00020120 badaddr: cause: 8005 [ 44.153860] [] load_module+0x826/0x9fc [ 44.159152] [] __do_sys_finit_module+0x98/0xfe [ 44.165146] [] sys_finit_module+0x24/0x30 [ 44.170704] []
[Kernel-packages] [Bug 2006588] Re: 5.19.0-1004.4-generic crashes with installed radeon graphics card
# lspci 00:00.0 PCI bridge: SiFive, Inc. FU740-C000 RISC-V SoC PCI Express x8 to AXI4 Bridge 01:00.0 PCI bridge: ASMedia Technology Inc. ASM2824 PCIe Gen3 Packet Switch (rev 01) 02:00.0 PCI bridge: ASMedia Technology Inc. ASM2824 PCIe Gen3 Packet Switch (rev 01) 02:02.0 PCI bridge: ASMedia Technology Inc. ASM2824 PCIe Gen3 Packet Switch (rev 01) 02:03.0 PCI bridge: ASMedia Technology Inc. ASM2824 PCIe Gen3 Packet Switch (rev 01) 02:04.0 PCI bridge: ASMedia Technology Inc. ASM2824 PCIe Gen3 Packet Switch (rev 01) 02:08.0 PCI bridge: ASMedia Technology Inc. ASM2824 PCIe Gen3 Packet Switch (rev 01) 04:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host Controller 06:00.0 Non-Volatile memory controller: Sandisk Corp PC SN520 NVMe SSD (rev 01) 07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] 07:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio [Radeon HD 6450 / 7450/8450/8490 OEM / R5 230/235/235X OEM] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2006588 Title: 5.19.0-1004.4-generic crashes with installed radeon graphics card Status in linux-riscv package in Ubuntu: New Bug description: I tried to install https://cdimage.ubuntu.com/ubuntu-server/daily- live/current/lunar-live-server-riscv64.img.gz on an SiFive HiFive Unmatches board with a Radeon graphics card. I saw a crash: [ 22.208410] [drm] Initialized radeon 2.50.0 20080528 for :07:00.0 on minor 0 [ 44.013359] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [systemd-udevd:189] [ 44.020117] Modules linked in: gpu_sched radeon i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper rtc_da9063 syscopyarea sysfillrect da9063_regulator sysimgblt fb_sys_fops nvme drm mscc backlight macsec xhci_pci nvme_core xhci_pci_renesas macb i2c_ocores phylink [ 44.045737] CPU: 2 PID: 189 Comm: systemd-udevd Not tainted 5.19.0-1004-generic #4-Ubuntu [ 44.053885] Hardware name: SiFive HiFive Unmatched A00 (DT) [ 44.059440] epc : apply_relocate_add+0x118/0x292 [ 44.064043] ra : apply_relocate_add+0x88/0x292 [ 44.068559] epc : 800088e4 ra : 80008854 sp : ffd89b55fc80 [ 44.075772] gp : 81e2e6c8 tp : ffd89bd1ce00 t0 : 02718510 [ 44.082981] t1 : 027ce160 t2 : 0001376b s0 : ffd89b55fd20 [ 44.090191] s1 : ffc895f8f2f8 a0 : 0001376b a1 : 025d4000 [ 44.097399] a2 : 027ce15c a3 : 027ce15c a4 : 0002cae4 [ 44.104609] a5 : 0003a641 a6 : 0001e8d6 a7 : [ 44.111818] s2 : ffc895f8e438 s3 : ffc895f8e538 s4 : 0017 [ 44.119028] s5 : f000 s6 : 0014 s7 : ffc895a3d1b0 [ 44.126236] s8 : 810014f0 s9 : 0033 s10: 0001e8d6 [ 44.133445] s11: 0001376b t3 : 0100 t4 : 80008374 [ 44.140655] t5 : 00430560 t6 : 02e2c000 [ 44.145949] status: 00020120 badaddr: cause: 8005 [ 44.153860] [] load_module+0x826/0x9fc [ 44.159152] [] __do_sys_finit_module+0x98/0xfe [ 44.165146] [] sys_finit_module+0x24/0x30 [ 44.170704] [] ret_from_syscall+0x0/0x2 [ 68.013359] watchdog: BUG: soft lockup - CPU#2 stuck for 45s! [systemd-udevd:189] [ 68.020111] Modules linked in: gpu_sched radeon i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper rtc_da9063 syscopyarea sysfillrect da9063_regulator sysimgblt fb_sys_fops nvme drm mscc backlight macsec xhci_pci nvme_core xhci_pci_renesas macb i2c_ocores phylink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2006588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006588] Re: 5.19.0-1004.4-generic crashes with installed radeon graphics card
** Attachment added: "/var/log/syslog" https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2006588/+attachment/5645531/+files/syslog -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2006588 Title: 5.19.0-1004.4-generic crashes with installed radeon graphics card Status in linux-riscv package in Ubuntu: New Bug description: I tried to install https://cdimage.ubuntu.com/ubuntu-server/daily- live/current/lunar-live-server-riscv64.img.gz on an SiFive HiFive Unmatches board with a Radeon graphics card. I saw a crash: [ 22.208410] [drm] Initialized radeon 2.50.0 20080528 for :07:00.0 on minor 0 [ 44.013359] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [systemd-udevd:189] [ 44.020117] Modules linked in: gpu_sched radeon i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper rtc_da9063 syscopyarea sysfillrect da9063_regulator sysimgblt fb_sys_fops nvme drm mscc backlight macsec xhci_pci nvme_core xhci_pci_renesas macb i2c_ocores phylink [ 44.045737] CPU: 2 PID: 189 Comm: systemd-udevd Not tainted 5.19.0-1004-generic #4-Ubuntu [ 44.053885] Hardware name: SiFive HiFive Unmatched A00 (DT) [ 44.059440] epc : apply_relocate_add+0x118/0x292 [ 44.064043] ra : apply_relocate_add+0x88/0x292 [ 44.068559] epc : 800088e4 ra : 80008854 sp : ffd89b55fc80 [ 44.075772] gp : 81e2e6c8 tp : ffd89bd1ce00 t0 : 02718510 [ 44.082981] t1 : 027ce160 t2 : 0001376b s0 : ffd89b55fd20 [ 44.090191] s1 : ffc895f8f2f8 a0 : 0001376b a1 : 025d4000 [ 44.097399] a2 : 027ce15c a3 : 027ce15c a4 : 0002cae4 [ 44.104609] a5 : 0003a641 a6 : 0001e8d6 a7 : [ 44.111818] s2 : ffc895f8e438 s3 : ffc895f8e538 s4 : 0017 [ 44.119028] s5 : f000 s6 : 0014 s7 : ffc895a3d1b0 [ 44.126236] s8 : 810014f0 s9 : 0033 s10: 0001e8d6 [ 44.133445] s11: 0001376b t3 : 0100 t4 : 80008374 [ 44.140655] t5 : 00430560 t6 : 02e2c000 [ 44.145949] status: 00020120 badaddr: cause: 8005 [ 44.153860] [] load_module+0x826/0x9fc [ 44.159152] [] __do_sys_finit_module+0x98/0xfe [ 44.165146] [] sys_finit_module+0x24/0x30 [ 44.170704] [] ret_from_syscall+0x0/0x2 [ 68.013359] watchdog: BUG: soft lockup - CPU#2 stuck for 45s! [systemd-udevd:189] [ 68.020111] Modules linked in: gpu_sched radeon i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper rtc_da9063 syscopyarea sysfillrect da9063_regulator sysimgblt fb_sys_fops nvme drm mscc backlight macsec xhci_pci nvme_core xhci_pci_renesas macb i2c_ocores phylink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2006588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987670] Re: Add support for AMD PMF
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid -- 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/1987670 Title: Add support for AMD PMF Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: Some upcoming platforms support for AMD-PMF. This will enable ACPI platform profiles and some automatic transitions. The first 11 patches are queued up for 6.1 and also available in an immutable branch. https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform- drivers-x86.git/log/?h=platform-drivers-x86-amd-pmf Can you please merge these to OEM-6.0? We will have 3-5 more patches targeted later as well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987312] Re: IWLMEI may cause device down at resuming from s2idle
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-oem-6.1 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => 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/1987312 Title: IWLMEI may cause device down at resuming from s2idle Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Won't Fix Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in backport-iwlwifi-dkms source package in Kinetic: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in backport-iwlwifi-dkms source package in Lunar: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] WiFi interfaces unsolicitedly down at resuming from s2idle. [Fix] Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. [Test Case] Make sure iwlmei.ko is not built. [Where problems could occur] iwlmei was not enabled before 5.17 and was turned on automatically since then. This restores the state and shall not have impact on existing devices. == original bug report == Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987312/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991608] Re: TEE Support for CCP driver
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-oem-6.1 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => 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/1991608 Title: TEE Support for CCP driver Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] Missing support for of AMD Secure Processor device for PCI ID 0x14CA. [Fix] A patch is being proposed in upstream and CC-ed stable. [Test Case] Without a proper fix, following error appears in dmesg: ccp :02:00.5: tee: missing driver data ccp :02:00.5: tee initialization failed [Where problems could occur] This adds a new driver data entry to support ccp device that provides both sev and tee feature at the same time. [Other Info] While this is proposed to stable 5.15+, all kernels >= 5.15 are nominated for fix. == original bug description == Client and datacenter Zen4 SOC same PCI-ID but offer different functionality from the PSP. Genoa offers SEV, Client part offers TEE. This patch fixes an ERR level message and CCP driver functionality not working. ccp :02:00.5: tee: missing driver data ccp :02:00.5: tee initialization failed https://lore.kernel.org/linux- crypto/20220928184506.13981-1-mario.limoncie...@amd.com/T/#m1b933ea4b961d17cb1be5be74e2d22a860507ca0 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987595] Re: Support Intel IPU6 MIPI camera
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-oem-6.1 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid -- 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/1987595 Title: Support Intel IPU6 MIPI camera Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Incomplete Status in linux-firmware source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Incomplete Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [SRU Justfication:linux-firmware] [Impact] Need new firmware updates for additional camera senesors. [Fix] Firmware updates for Intel IPU6/VSC drivers, as well as new firmware blobs for hi556/ovti02c1. [Test Case] The driver will prompt for missed firmware blobs for a given platform. [Where problems could occur] There is still no suspend support for the camera driver, and user sessions across system suspend have to be restarted. [Other Info] New sensors are introduced in Jammy oem kernels only, and kinetic is nominated for future hwe migration. = original bug report == This is a follow-up for bug 1964983 but on different platforms that runs linux-oem-5.17 or newer. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989518] Re: AMD ACP 6.2 DMIC support
** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-oem-6.1 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Invalid -- 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/1989518 Title: AMD ACP 6.2 DMIC support Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: The patchset will be merged to upstream kernel v6.1, the unstable kernel will have the patchset automatically after the v6.1 is ready. The oem-5.17 kernel doesn't support this AMD generation platform yet, so this patchset is useless for oem-5.17 so far. [Impact] On the AMD PS platforms, the internal mic can't be detected and there is no internal mic for users to use. [Fix] Backport 13 patches from linux-next kernel to fix this problem. [Test] boot the patched kernel on the machine, after loging into the desktop, open the gnome-sound-setting, there is internal mic, and could record sound via internal mic. [Where problems could occur] This only impacts intenal mic support on AMD ps machines, it will match the pci device revision and apply the driver according to match result, in theory it will not bring regression on non-amd-ps machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1989518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000228] Re: Add initial support for Mediatek mt8195 demo platform
new debdiff based on 1.2.6.3-1ubuntu7 ** Patch added: "alsa-ucm-conf-lunar.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000228/+attachment/5645477/+files/alsa-ucm-conf-lunar.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2000228 Title: Add initial support for Mediatek mt8195 demo platform Status in alsa-ucm-conf package in Ubuntu: New Bug description: [Impact] Add initial support for Mediatek mt8195 demo platform https://github.com/alsa-project/alsa-ucm-conf/commit/7e2dbf2158bb2acd7bdf101acf5b49ec7400c6c9 https://github.com/alsa-project/alsa-ucm-conf/commit/445c079665979802d50b237fe5a55be82ffd0bd9 [Where problems could occur] Audio function doesn't work on Mediatek mt8195 demo platform. Play audio by aplay and gnome sound test: 1. HDMI audio: Pass 2. Headset: Pass [Test Case] Verify audio function (headset & hdmi audio) on Mediatek mt8195 demo platform. [Regression Potential] Add initial support for Mediatek mt8195 demo platform. There should be no risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/2000228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998224] Re: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18
okay, it seems that both acpi_pci_hotplug and pci_hotplug are enabled for this kernel: grep "CONFIG_HOTPLUG_PCI_ACPI=" /boot/config-`uname -r` CONFIG_HOTPLUG_PCI_ACPI=y grep "CONFIG_HOTPLUG_PCI=" /boot/config-`uname -r` CONFIG_HOTPLUG_PCI=y but still, hotplug is not working. the current situation is: I unplugged a correctly recognized Intel NVME and switched it for a Micron NVME, there is also a second intel nvme still installed. nvme list shows the intel nvme which remained in the system: nvme list Node SN Model Namespace Usage Format FW Rev - -- /dev/nvme0n1 PHLN130100QJ1P6AGN INTEL SSDPE2KE016T8 1 1.60 TB / 1.60 TB512 B + 0 B VDV10184 but when I look into /sys/, I still find shadows of the other intel nvme, which just got plugged out: find /sys/devices | egrep "nvme[0-9][0-9]?$" /sys/devices/pci:40/:40:01.1/:41:00.0/nvme/nvme0 /sys/devices/virtual/nvme-subsystem/nvme-subsys1/nvme1 /sys/devices/virtual/nvme-subsystem/nvme-subsys0/nvme0 also, nvme list-subsys, throws an error. I suppose because that old subsystem nvme-subsys1 does no longer exist, but is still referenced: nvme list-subsys free(): double free detected in tcache 2 Aborted googling the above error leads me to this bug report: https://github.com/linux-nvme/nvme-cli/issues/1707 when rescanning the pci bus via: echo 1 > /sys/bus/pci/rescan I get the following messages in dmesg: [Wed Feb 8 10:20:49 2023] pci :c3:00.0: PCI bridge to [bus c4] [Wed Feb 8 10:20:49 2023] pci :c3:00.0: bridge window [io 0xf000-0x] [Wed Feb 8 10:20:49 2023] pci :c3:00.0: bridge window [mem 0xb800-0xb90f] [Wed Feb 8 10:20:49 2023] pcieport :40:01.1: bridge window [io 0x1000-0x0fff] to [bus 41] add_size 1000 [Wed Feb 8 10:20:49 2023] pcieport :40:01.2: bridge window [io 0x1000-0x0fff] to [bus 42] add_size 1000 [Wed Feb 8 10:20:49 2023] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Wed Feb 8 10:20:49 2023] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] [Wed Feb 8 10:20:49 2023] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Wed Feb 8 10:20:49 2023] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Wed Feb 8 10:20:49 2023] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Wed Feb 8 10:20:49 2023] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Wed Feb 8 10:20:49 2023] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Wed Feb 8 10:20:49 2023] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] as already stated in the original bug report. how can I get rid of the now defunct nvme subsystem? anything else I could try? ** Bug watch added: github.com/linux-nvme/nvme-cli/issues #1707 https://github.com/linux-nvme/nvme-cli/issues/1707 ** Summary changed: - pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.107.121~18 + pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.135.152~18 -- 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/1998224 Title: pcie hotplug not working in linux-generic-hwe-18.04 5.4.0.135.152~18 Status in linux package in Ubuntu: Confirmed Bug description: situation: ubuntu 18.04 server install on a supermicro x64 host. hot plug NVME ssd into NVME U.2 HotSwap Slot. problem: hot plug does not work/ nvme is not recognised. how to test: echo 1 > /sys/bus/pci/rescan dmesg output: [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: bridge window [io 0x1000-0x0fff] to [bus 41] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: bridge window [io 0x1000-0x0fff] to [bus 42] add_size 1000 [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.2: BAR 13: failed to assign [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: no space for [io size 0x1000] [Mon Nov 28 15:46:33 2022] pcieport :40:01.1: BAR 13: failed to assign [io size 0x1000] Kernel Version: 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux hardware information: tried with micron and intel NVME,
[Kernel-packages] [Bug 2006588] Re: 5.19.0-1004.4-generic crashes with installed radeon graphics card
** Attachment added: "Console output" https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2006588/+attachment/5645530/+files/crash_20230208.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2006588 Title: 5.19.0-1004.4-generic crashes with installed radeon graphics card Status in linux-riscv package in Ubuntu: New Bug description: I tried to install https://cdimage.ubuntu.com/ubuntu-server/daily- live/current/lunar-live-server-riscv64.img.gz on an SiFive HiFive Unmatches board with a Radeon graphics card. I saw a crash: [ 22.208410] [drm] Initialized radeon 2.50.0 20080528 for :07:00.0 on minor 0 [ 44.013359] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [systemd-udevd:189] [ 44.020117] Modules linked in: gpu_sched radeon i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper rtc_da9063 syscopyarea sysfillrect da9063_regulator sysimgblt fb_sys_fops nvme drm mscc backlight macsec xhci_pci nvme_core xhci_pci_renesas macb i2c_ocores phylink [ 44.045737] CPU: 2 PID: 189 Comm: systemd-udevd Not tainted 5.19.0-1004-generic #4-Ubuntu [ 44.053885] Hardware name: SiFive HiFive Unmatched A00 (DT) [ 44.059440] epc : apply_relocate_add+0x118/0x292 [ 44.064043] ra : apply_relocate_add+0x88/0x292 [ 44.068559] epc : 800088e4 ra : 80008854 sp : ffd89b55fc80 [ 44.075772] gp : 81e2e6c8 tp : ffd89bd1ce00 t0 : 02718510 [ 44.082981] t1 : 027ce160 t2 : 0001376b s0 : ffd89b55fd20 [ 44.090191] s1 : ffc895f8f2f8 a0 : 0001376b a1 : 025d4000 [ 44.097399] a2 : 027ce15c a3 : 027ce15c a4 : 0002cae4 [ 44.104609] a5 : 0003a641 a6 : 0001e8d6 a7 : [ 44.111818] s2 : ffc895f8e438 s3 : ffc895f8e538 s4 : 0017 [ 44.119028] s5 : f000 s6 : 0014 s7 : ffc895a3d1b0 [ 44.126236] s8 : 810014f0 s9 : 0033 s10: 0001e8d6 [ 44.133445] s11: 0001376b t3 : 0100 t4 : 80008374 [ 44.140655] t5 : 00430560 t6 : 02e2c000 [ 44.145949] status: 00020120 badaddr: cause: 8005 [ 44.153860] [] load_module+0x826/0x9fc [ 44.159152] [] __do_sys_finit_module+0x98/0xfe [ 44.165146] [] sys_finit_module+0x24/0x30 [ 44.170704] [] ret_from_syscall+0x0/0x2 [ 68.013359] watchdog: BUG: soft lockup - CPU#2 stuck for 45s! [systemd-udevd:189] [ 68.020111] Modules linked in: gpu_sched radeon i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper rtc_da9063 syscopyarea sysfillrect da9063_regulator sysimgblt fb_sys_fops nvme drm mscc backlight macsec xhci_pci nvme_core xhci_pci_renesas macb i2c_ocores phylink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2006588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002812] Re: Revoke & rotate to new signing key
This bug was fixed in the package linux - 4.15.0-204.215 --- linux (4.15.0-204.215) bionic; urgency=medium * bionic/linux: 4.15.0-204.215 -proposed tracker (LP: #2003522) * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (4.15.0-203.214) bionic; urgency=medium * bionic/linux: 4.15.0-203.214 -proposed tracker (LP: #2001876) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * Bionic update: upstream stable patchset 2022-12-01 (LP: #1998542) - Revert "x86/cpu: Add a steppings field to struct x86_cpu_id" - x86/cpufeature: Add facility to check for min microcode revisions - x86/cpufeature: Fix various quality problems in the header - x86/devicetable: Move x86 specific macro out of generic code - x86/cpu: Add consistent CPU match macros - x86/cpu: Add a steppings field to struct x86_cpu_id - x86/entry: Remove skip_r11rcx - x86/cpufeatures: Move RETPOLINE flags to word 11 - x86/bugs: Report AMD retbleed vulnerability - x86/bugs: Add AMD retbleed= boot parameter - x86/bugs: Keep a per-CPU IA32_SPEC_CTRL value - x86/entry: Add kernel IBRS implementation - x86/bugs: Optimize SPEC_CTRL MSR writes - x86/speculation: Add spectre_v2=ibrs option to support Kernel IBRS - x86/bugs: Split spectre_v2_select_mitigation() and spectre_v2_user_select_mitigation() - x86/bugs: Report Intel retbleed vulnerability - entel_idle: Disable IBRS during long idle - x86/speculation: Change FILL_RETURN_BUFFER to work with objtool - x86/speculation: Add LFENCE to RSB fill sequence - x86/speculation: Fix RSB filling with CONFIG_RETPOLINE=n - x86/speculation: Fix firmware entry SPEC_CTRL handling - x86/speculation: Fix SPEC_CTRL write on SMT state change - x86/speculation: Use cached host SPEC_CTRL value for guest entry/exit - x86/speculation: Remove x86_spec_ctrl_mask - KVM: VMX: Prevent guest RSB poisoning attacks with eIBRS - KVM: VMX: Fix IBRS handling after vmexit - x86/speculation: Fill RSB on vmexit for IBRS - x86/common: Stamp out the stepping madness - x86/cpu/amd: Enumerate BTC_NO - x86/bugs: Add Cannon lake to RETBleed affected CPU list - x86/speculation: Disable RRSBA behavior - x86/speculation: Use DECLARE_PER_CPU for x86_spec_ctrl_current - x86/bugs: Warn when "ibrs" mitigation is selected on Enhanced IBRS parts - x86/speculation: Add RSB VM Exit protections - ocfs2: clear dinode links count in case of error - ocfs2: fix BUG when iput after ocfs2_mknod fails - x86/microcode/AMD: Apply the patch early on every logical thread - ata: ahci-imx: Fix MODULE_ALIAS - ata: ahci: Match EM_MAX_SLOTS with SATA_PMP_MAX_PORTS - KVM: arm64: vgic: Fix exit condition in scan_its_table() - [Config] updateconfigs for ARM64_ERRATUM_1742098 - arm64: errata: Remove AES hwcap for COMPAT tasks - r8152: add PID for the Lenovo OneLink+ Dock - btrfs: fix processing of delayed data refs during backref walking - ACPI: extlog: Handle multiple records - HID: magicmouse: Do not set BTN_MOUSE on double report - net/atm: fix proc_mpc_write incorrect return value - net: hns: fix possible memory leak in hnae_ae_register() - iommu/vt-d: Clean up si_domain in the init_dmars() error path - media: v4l2-mem2mem: Apply DST_QUEUE_OFF_BASE on MMAP buffers across ioctls - ACPI: video: Force backlight native for more TongFang devices - ALSA: Use del_timer_sync() before freeing timer - ALSA: au88x0: use explicitly signed char - USB: add RESET_RESUME quirk for NVIDIA Jetson devices in RCM - usb: dwc3: gadget: Don't set IMI for no_interrupt - usb: bdc: change state when port disconnected - usb: xhci: add XHCI_SPURIOUS_SUCCESS to ASM1042 despite being a V0.96 controller - xhci: Remove device endpoints from bandwidth list when freeing the device - tools: iio: iio_utils: fix digit calculation - iio: light: tsl2583: Fix module unloading - fbdev: smscufx: Fix several use-after-free bugs - mac802154: Fix LQI recording - drm/msm/hdmi: fix memory corruption with too many bridges - mmc: core: Fix kernel panic when remove non-standard SDIO card - kernfs: fix use-after-free in __kernfs_remove - s390/futex: add missing EX_TABLE entry to __futex_atomic_op() - Xen/gntdev: don't ignore kernel unmapping error - xen/gntdev: Prevent leaking grants - mm,hugetlb: take hugetlb_lock before decrementing h->resv_huge_pages - net: ieee802154: fix error return code in dgram_bind() - drm/msm: Fix return type of mdp4_lvds_connector_mode_valid - arc: iounmap() arg is volatile - ALSA: ac97: fix possible memory leak in snd_ac97_dev_register() - x86/unwind/orc: Fix unreliable stack dump with gcov - amd-xgbe: fix the SFP compliance codes check for DAC cables - amd-xgbe: add the
[Kernel-packages] [Bug 2002812] Re: Revoke & rotate to new signing key
This bug was fixed in the package linux - 5.4.0-139.156 --- linux (5.4.0-139.156) focal; urgency=medium * focal/linux: 5.4.0-139.156 -proposed tracker (LP: #2003486) * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.4.0-138.155) focal; urgency=medium * focal/linux: 5.4.0-138.155 -proposed tracker (LP: #2001845) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * Focal update: v5.4.224 upstream stable release (LP: #1999273) - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - media: s5p_cec: limit msg.len to CEC_MAX_MSG_SIZE - media: cros-ec-cec: limit msg.len to CEC_MAX_MSG_SIZE - media: dvb-frontends/drxk: initialize err to 0 - media: meson: vdec: fix possible refcount leak in vdec_probe() - scsi: core: Restrict legal sdev_state transitions via sysfs - HID: saitek: add madcatz variant of MMO7 mouse device ID - i2c: xiic: Add platform module alias - xfs: don't fail verifier on empty attr3 leaf block - xfs: use ordered buffers to initialize dquot buffers during quotacheck - xfs: gut error handling in xfs_trans_unreserve_and_mod_sb() - xfs: group quota should return EDQUOT when prj quota enabled - xfs: don't fail unwritten extent conversion on writeback due to edquot - xfs: Add the missed xfs_perag_put() for xfs_ifree_cluster() - Bluetooth: L2CAP: Fix attempting to access uninitialized memory - block, bfq: protect 'bfqd->queued' by 'bfqd->lock' - binder: fix UAF of alloc->vma in race with munmap() - btrfs: fix type of parameter generation in btrfs_get_dentry - tcp/udp: Make early_demux back namespacified. - kprobe: reverse kp->flags when arm_kprobe failed - tools/nolibc/string: Fix memcmp() implementation - tracing/histogram: Update document for KEYS_MAX size - capabilities: fix potential memleak on error path from vfs_getxattr_alloc() - fuse: add file_modified() to fallocate - efi: random: reduce seed size to 32 bytes - perf/x86/intel: Fix pebs event constraints for ICL - perf/x86/intel: Add Cooper Lake stepping to isolation_ucodes[] - ALSA: usb-audio: Add quirks for MacroSilicon MS2100/MS2106 devices - parisc: Make 8250_gsc driver dependend on CONFIG_PARISC - parisc: Export iosapic_serial_irq() symbol for serial port driver - parisc: Avoid printing the hardware path twice - ext4: fix warning in 'ext4_da_release_space' - ext4: fix BUG_ON() when directory entry has invalid rec_len - KVM: x86: Mask off reserved bits in CPUID.801AH - KVM: x86: Mask off reserved bits in CPUID.8008H - KVM: x86: emulator: em_sysexit should update ctxt->mode - KVM: x86: emulator: introduce emulator_recalc_and_set_mode - KVM: x86: emulator: update the emulation mode after CR0 write - mtd: rawnand: gpmi: Set WAIT_FOR_READY timeout based on program/erase times - drm/rockchip: dsi: Force synchronous probe - drm/i915/sdvo: Filter out invalid outputs more sensibly - drm/i915/sdvo: Setup DDC fully before output init - wifi: brcmfmac: Fix potential buffer overflow in brcmf_fweh_event_worker() - ipc: remove memcg accounting for sops objects in do_semtimedop() - Linux 5.4.224 * Focal update: v5.4.223
[Kernel-packages] [Bug 2002812] Re: Revoke & rotate to new signing key
This bug was fixed in the package linux - 5.15.0-60.66 --- linux (5.15.0-60.66) jammy; urgency=medium * jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450) * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.15.0-59.65) jammy; urgency=medium * jammy/linux: 5.15.0-59.65 -proposed tracker (LP: #2001801) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2022-47940 - ksmbd: validate length in smb2_write() * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x * support for same series backports versioning numbers (LP: #1993563) - [Packaging] sameport -- add support for sameport versioning * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Micron NVME storage failure [1344,5407] (LP: #1998883) - nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH * Jammy update: v5.15.78 upstream stable release (LP: #1998843) - scsi: lpfc: Rework MIB Rx Monitor debug info logic - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - KVM: x86: Treat #DBs from the emulator as fault-like (code and DR7.GD=1) - drm/amd/display: explicitly disable psr_feature_enable appropriately - mm/hugetlb: fix races when looking up a CONT-PTE/PMD size hugetlb page - HID: playstation: add initial DualSense Edge controller support - KVM: x86: Protect the unused bits in MSR exiting flags - KVM: x86: Copy filter arg outside kvm_vm_ioctl_set_msr_filter() - KVM: x86: Add compat handler for KVM_X86_SET_MSR_FILTER - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Remove magic number - RDMA/hns: Use hr_reg_xxx() instead of remaining roce_set_xxx() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - drm/msm/hdmi: Remove spurious IRQF_ONESHOT flag - drm/msm/hdmi: fix IRQ lifetime - video/fbdev/stifb: Implement the stifb_fillrect() function - fbdev: stifb: Fall back to cfb_fillrect() on 32-bit HCRX cards - mtd: parsers: bcm47xxpart: print correct offset on read error - mtd: parsers: bcm47xxpart: Fix
[Kernel-packages] [Bug 2002812] Re: Revoke & rotate to new signing key
This bug was fixed in the package linux - 5.19.0-31.32 --- linux (5.19.0-31.32) kinetic; urgency=medium * kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423) * amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks (LP: #2003524) - drm/amd: Delay removal of the firmware framebuffer * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.19.0-30.31) kinetic; urgency=medium * kinetic/linux: 5.19.0-30.31 -proposed tracker (LP: #2001756) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/2023.01.02) * Add some ACPI device IDs for Intel HID device (LP: #1995453) - platform/x86/intel/hid: Add some ACPI device IDs * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x riscv64 * BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9 (LP: #2001618) - powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations - powerpc/bpf/64: add support for atomic fetch operations - powerpc/bpf/64: Add instructions for atomic_[cmp]xchg * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Kinetic update: upstream stable patchset 2022-12-15 (LP: #1999828) - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - media: rkisp1: Don't pass the quantization to rkisp1_csm_config() - media: rkisp1: Initialize color space on resizer sink and source pads - media: rkisp1: Use correct macro for gradient registers - media: rkisp1: Zero v4l2_subdev_format fields in when validating links - media: s5p_cec: limit msg.len to CEC_MAX_MSG_SIZE - media: cros-ec-cec: limit msg.len to CEC_MAX_MSG_SIZE - media: dvb-frontends/drxk: initialize err to 0 - media: meson: vdec: fix possible refcount leak in vdec_probe() - media: v4l: subdev: Fail graciously when getting try data for NULL state - ACPI: APEI:
[Kernel-packages] [Bug 2002467] Re: ThinkPad L14 Gen 3 blank laptop screen on bootup
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1027.28 --- linux-oem-5.17 (5.17.0-1027.28) jammy; urgency=medium * jammy/linux-oem-5.17: 5.17.0-1027.28 -proposed tracker (LP: #2003451) * CVE-2022-3545 - nfp: fix use-after-free in area_cache_get() * CVE-2022-42895 - Bluetooth: L2CAP: Fix attempting to access uninitialized memory * ThinkPad L14 Gen 3 blank laptop screen on bootup (LP: #2002467) - Revert "drm/amdgpu: make sure to init common IP before gmc" * CVE-2023-0179 - netfilter: nft_payload: incorrect arithmetics when fetching VLAN header bits [ Ubuntu: 5.17.0-15.16~22.04.8 ] * jammy/linux-hwe-5.17: 5.17.0-15.16~22.04.8 -proposed tracker (LP: #2003452) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/2023.01.02) * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key * CVE-2022-45934 - Bluetooth: L2CAP: Fix u8 overflow * CVE-2022-42896 - Bluetooth: L2CAP: Fix accepting connection request for invalid SPSM - Bluetooth: L2CAP: Fix l2cap_global_chan_by_psm * CVE-2022-4378 - proc: proc_skip_spaces() shouldn't think it is working on C strings - proc: avoid integer type confusion in get_proc_long -- Timo Aaltonen Mon, 23 Jan 2023 12:37:39 +0200 ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-3545 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-42895 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-42896 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-4378 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-45934 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-0179 -- 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/2002467 Title: ThinkPad L14 Gen 3 blank laptop screen on bootup Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] The commit in 5.17.0.1026.27 introduce an regression that leads to the panel of ThinkPad L14 Gen 3 becomes blank after bootup 224dffc89a957 drm/amdgpu: make sure to init common IP before gmc [Fix] Revert this commit as it looks like it requires some other commits to work together, and from the discussion of the 5.10 stable, this commit has been reverted, too. https://gitlab.freedesktop.org/drm/amd/-/issues/2216 BTW, confirmed by Aaron Ma that 6.0 and 6.1 OEM kernels work well with this commit, so no need to revert it. [Test] Verified by Aaron Ma and the bug reporter. [Where problems could occur] Revert this commit will lead to the keep rebooting issue be re-opened(bug 2000110), I'll check the issue again and submit another solution for it. When booting linux-image-5.17.0-1026-oem version 5.17.0.1026.27 on a Lenovo ThinkPad L14 Gen 3 AMD (model 21C5CTO1WW), the screen goes blank shortly after bootup. As far as I can tell (the screen blanks pretty quickly, so I'm not 100% sure), the last message before the screen disappears is this one: Jan 9 07:58:30 work kernel: [1.321487] fb0: switching to amdgpu from EFI VGA Booting linux-image-5.17.0-1025-oem version 5.17.0.1025.26 works fine, so this appears to be a regression in whatever changes there were in the framebuffer/amdgpu drivers between 5.17.0.1025.26 and 5.17.0.1026.27. I think this should be high priority, because it gives the impression that the system is completely borked, when in actuality it's probably just waiting for me to enter my drive encryption password. If I type the encryption password, it seems to progress to starting the system (the microphone mute LED comes on as expected), but even X starting does not turn the screen back on. Switching to the frame buffer console with Ctrl-Alt-Fx does nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/2002467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006397] Re: nft_lookup crash when running DDOS attack
** Changed in: linux-bluefield (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2006397
Title:
nft_lookup crash when running DDOS attack
Status in linux-bluefield package in Ubuntu:
Invalid
Status in linux-bluefield source package in Focal:
Fix Committed
Bug description:
* Explain the bug
Running DDOS test on tcp port 22 will trigger kernel crash.
* Brief explanation of fixes
Do not update stateful expressions if lookup is inverted
* How to test
Configuration nftables with config file below:
flush ruleset
table inet filter {
chain input {
type filter hook input priority 0
jump filter_ssh
}
chain filter_ssh {
tcp dport { 22 } ct state new accept
}
}
* {22}: {} is mandatory to repro
If we don’t add {}, nft_lookup_eval function is never called and kernel crush
isn’t reproduced.
Then apply nft by doing:
# nft -f temp_nftables.conf
Start hping3 from peer:
# hping3 -I {Host Device} -p 22 -d 52 {SmartNIC IP Address} --flood
DPU side will crash with kernel call trace without this fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2006397/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006616] [NEW] package linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned er
Public bug reported: I ran the software update after a fresh install of 22.10. I had another instance yesterday where I had a similar issue, but I didn't send a report for it. I have 3 VMs of Ubuntu 22.10. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jobrien1609 F wireplumber /dev/snd/seq:jobrien1607 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed Feb 8 11:11:11 2023 Dependencies: firmware-sof-signed 2.1.1-1ubuntu1.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-02-08 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels Software International Inc. Parallels Virtual Platform PackageArchitecture: all ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=af475be1-f9b7-4d44-b271-c1b7c045f7c8 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu12.1 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2022 dmi.bios.release: 18.1 dmi.bios.vendor: Parallels Software International Inc. dmi.bios.version: 18.1.1 (53328) dmi.board.name: Parallels Virtual Platform dmi.board.vendor: Parallels Software International Inc. dmi.board.version: None dmi.chassis.type: 2 dmi.chassis.vendor: Parallels Software International Inc. dmi.ec.firmware.release: 18.1 dmi.modalias: dmi:bvnParallelsSoftwareInternationalInc.:bvr18.1.1(53328):bd12/02/2022:br18.1:efr18.1:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct2:cvr:skuUndefined: dmi.product.family: Parallels VM dmi.product.name: Parallels Virtual Platform dmi.product.sku: Undefined dmi.product.version: None dmi.sys.vendor: Parallels Software International Inc. ** Affects: linux-firmware (Ubuntu) Importance: Low Status: Invalid ** Tags: amd64 apport-package hardware-error kinetic -- 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/2006616 Title: package linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: Invalid Bug description: I ran the software update after a fresh install of 22.10. I had another instance yesterday where I had a similar issue, but I didn't send a report for it. I have 3 VMs of Ubuntu 22.10. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jobrien1609 F wireplumber /dev/snd/seq:jobrien1607 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed Feb 8 11:11:11 2023 Dependencies: firmware-sof-signed 2.1.1-1ubuntu1.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-02-08 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels Software International Inc. Parallels Virtual Platform PackageArchitecture: all ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=af475be1-f9b7-4d44-b271-c1b7c045f7c8 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu12.1 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 failed to install/upgrade: installed linux-firmware
[Kernel-packages] [Bug 2004807] Re: RDMA Back port DMA buffer fix
** Changed in: linux-aws (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux-aws (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-aws (Ubuntu Kinetic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/2004807
Title:
RDMA Back port DMA buffer fix
Status in linux-aws package in Ubuntu:
Fix Released
Status in linux-aws source package in Focal:
Fix Committed
Status in linux-aws source package in Jammy:
Fix Committed
Status in linux-aws source package in Kinetic:
Fix Committed
Bug description:
SRU Justification
[Impact]
When registering a new DMA MR after selecting the best aligned page size
for it, we iterate over the given sglist to split each entry to smaller,
aligned to the selected page size, DMA blocks.
In given circumstances where the sg entry and page size fit certain
sizes and the sg entry is not aligned to the selected page size, the
total size of the aligned pages we need to cover the sg entry is >= 4GB.
Under this circumstances, while iterating page aligned blocks, the
counter responsible for counting how much we advanced from the start of
the sg entry is overflowed because its type is u32 and we pass 4GB in
size. This can lead to an infinite loop inside the iterator function
because the overflow prevents the counter to be larger
than the size of the sg entry.
Fixes: a808273 ("RDMA/verbs: Add a DMA iterator to return aligned
contiguous memory blocks")
[Test Plan]
AWS tested
[Where things could go wrong]
What could possibly go wrong with Remote DMA scatter/gather list
errors ?
[Other Info]
SF: #00353710
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2004807/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006616] Re: package linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned erro
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => Low ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- 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/2006616 Title: package linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: Invalid Bug description: I ran the software update after a fresh install of 22.10. I had another instance yesterday where I had a similar issue, but I didn't send a report for it. I have 3 VMs of Ubuntu 22.10. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jobrien1609 F wireplumber /dev/snd/seq:jobrien1607 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed Feb 8 11:11:11 2023 Dependencies: firmware-sof-signed 2.1.1-1ubuntu1.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-02-08 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels Software International Inc. Parallels Virtual Platform PackageArchitecture: all ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=af475be1-f9b7-4d44-b271-c1b7c045f7c8 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu12.1 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2022 dmi.bios.release: 18.1 dmi.bios.vendor: Parallels Software International Inc. dmi.bios.version: 18.1.1 (53328) dmi.board.name: Parallels Virtual Platform dmi.board.vendor: Parallels Software International Inc. dmi.board.version: None dmi.chassis.type: 2 dmi.chassis.vendor: Parallels Software International Inc. dmi.ec.firmware.release: 18.1 dmi.modalias: dmi:bvnParallelsSoftwareInternationalInc.:bvr18.1.1(53328):bd12/02/2022:br18.1:efr18.1:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct2:cvr:skuUndefined: dmi.product.family: Parallels VM dmi.product.name: Parallels Virtual Platform dmi.product.sku: Undefined dmi.product.version: None dmi.sys.vendor: Parallels Software International Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2006616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006616] Re: package linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned erro
** Tags removed: need-duplicate-check -- 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/2006616 Title: package linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in linux-firmware package in Ubuntu: Invalid Bug description: I ran the software update after a fresh install of 22.10. I had another instance yesterday where I had a similar issue, but I didn't send a report for it. I have 3 VMs of Ubuntu 22.10. ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jobrien1609 F wireplumber /dev/snd/seq:jobrien1607 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Wed Feb 8 11:11:11 2023 Dependencies: firmware-sof-signed 2.1.1-1ubuntu1.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-02-08 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels Software International Inc. Parallels Virtual Platform PackageArchitecture: all ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=af475be1-f9b7-4d44-b271-c1b7c045f7c8 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu12.1 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2022 dmi.bios.release: 18.1 dmi.bios.vendor: Parallels Software International Inc. dmi.bios.version: 18.1.1 (53328) dmi.board.name: Parallels Virtual Platform dmi.board.vendor: Parallels Software International Inc. dmi.board.version: None dmi.chassis.type: 2 dmi.chassis.vendor: Parallels Software International Inc. dmi.ec.firmware.release: 18.1 dmi.modalias: dmi:bvnParallelsSoftwareInternationalInc.:bvr18.1.1(53328):bd12/02/2022:br18.1:efr18.1:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct2:cvr:skuUndefined: dmi.product.family: Parallels VM dmi.product.name: Parallels Virtual Platform dmi.product.sku: Undefined dmi.product.version: None dmi.sys.vendor: Parallels Software International Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2006616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006588] Re: 5.19.0-1004.4-generic crashes with installed radeon graphics card
Setting kernel.watchdog_thresh=60 in /etc/sysctl.d/99-watchdog_thresh.conf does not solve the problem. /etc/sysctl* is not included in the initrd and the issue occurs before the real root is mounted. 60 seconds is the maximum value. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/2006588 Title: 5.19.0-1004.4-generic crashes with installed radeon graphics card Status in linux-riscv package in Ubuntu: New Bug description: I tried to install https://cdimage.ubuntu.com/ubuntu-server/daily- live/current/lunar-live-server-riscv64.img.gz on an SiFive HiFive Unmatches board with a Radeon graphics card. I saw a crash: [ 22.208410] [drm] Initialized radeon 2.50.0 20080528 for :07:00.0 on minor 0 [ 44.013359] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [systemd-udevd:189] [ 44.020117] Modules linked in: gpu_sched radeon i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper rtc_da9063 syscopyarea sysfillrect da9063_regulator sysimgblt fb_sys_fops nvme drm mscc backlight macsec xhci_pci nvme_core xhci_pci_renesas macb i2c_ocores phylink [ 44.045737] CPU: 2 PID: 189 Comm: systemd-udevd Not tainted 5.19.0-1004-generic #4-Ubuntu [ 44.053885] Hardware name: SiFive HiFive Unmatched A00 (DT) [ 44.059440] epc : apply_relocate_add+0x118/0x292 [ 44.064043] ra : apply_relocate_add+0x88/0x292 [ 44.068559] epc : 800088e4 ra : 80008854 sp : ffd89b55fc80 [ 44.075772] gp : 81e2e6c8 tp : ffd89bd1ce00 t0 : 02718510 [ 44.082981] t1 : 027ce160 t2 : 0001376b s0 : ffd89b55fd20 [ 44.090191] s1 : ffc895f8f2f8 a0 : 0001376b a1 : 025d4000 [ 44.097399] a2 : 027ce15c a3 : 027ce15c a4 : 0002cae4 [ 44.104609] a5 : 0003a641 a6 : 0001e8d6 a7 : [ 44.111818] s2 : ffc895f8e438 s3 : ffc895f8e538 s4 : 0017 [ 44.119028] s5 : f000 s6 : 0014 s7 : ffc895a3d1b0 [ 44.126236] s8 : 810014f0 s9 : 0033 s10: 0001e8d6 [ 44.133445] s11: 0001376b t3 : 0100 t4 : 80008374 [ 44.140655] t5 : 00430560 t6 : 02e2c000 [ 44.145949] status: 00020120 badaddr: cause: 8005 [ 44.153860] [] load_module+0x826/0x9fc [ 44.159152] [] __do_sys_finit_module+0x98/0xfe [ 44.165146] [] sys_finit_module+0x24/0x30 [ 44.170704] [] ret_from_syscall+0x0/0x2 [ 68.013359] watchdog: BUG: soft lockup - CPU#2 stuck for 45s! [systemd-udevd:189] [ 68.020111] Modules linked in: gpu_sched radeon i2c_algo_bit drm_ttm_helper ttm drm_display_helper cec rc_core drm_kms_helper rtc_da9063 syscopyarea sysfillrect da9063_regulator sysimgblt fb_sys_fops nvme drm mscc backlight macsec xhci_pci nvme_core xhci_pci_renesas macb i2c_ocores phylink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/2006588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006620] Re: linux-aws-5.19 hibernation tasks sometimes fail to freeze
Here is the full syslog from which the portion in the bug description was extracted from. ** Attachment added: "c5.12xlarge-3-syslog.log" https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2006620/+attachment/5645600/+files/c5.12xlarge-3-syslog.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/2006620 Title: linux-aws-5.19 hibernation tasks sometimes fail to freeze Status in linux-aws package in Ubuntu: New Bug description: Hibernation on AWS instances with jammy/5.19.0-1019-aws sometimes fails due to the following failure to freeze: Feb 1 01:09:05 ip-172-31-54-178 kernel: [ 443.247854] PM: hibernation: hibernation entry Feb 1 01:09:05 ip-172-31-54-178 kernel: [ 443.347353] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Feb 1 01:09:05 ip-172-31-54-178 kernel: [ 443.347355] sched_clock: Marking unstable (442909362062, 1007864825)<-(443748056670, -400707172) Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 443.940489] Filesystems sync: 0.022 seconds Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 443.940492] Freezing user space processes ... (elapsed 0.001 seconds) done. Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 443.941611] OOM killer disabled. Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 443.943036] PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 443.943039] PM: hibernation: Marking nosave pages: [mem 0x0009f000-0x000f] Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 443.943041] PM: hibernation: Marking nosave pages: [mem 0xbffe8000-0x] Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 443.943950] PM: hibernation: Basic memory bitmaps created Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 443.943961] PM: hibernation: Preallocating image memory Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 630.782421] PM: hibernation: Allocated 9655951 pages for snapshot Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 630.782424] PM: hibernation: Allocated 38623804 kbytes in 186.83 seconds (206.73 MB/s) Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 630.782426] Freezing remaining freezable tasks ... Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.789826] Freezing of tasks failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0): Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792830] task:kswapd0 state:D stack:0 pid: 328 ppid: 2 flags:0x4000 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792833] Call Trace: Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792835] Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792837] __schedule+0x248/0x5d0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792842] schedule+0x58/0x100 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792844] io_schedule+0x46/0x80 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792846] blk_mq_get_tag+0x117/0x2e0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792852] ? destroy_sched_domains_rcu+0x40/0x40 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792857] __blk_mq_alloc_requests+0xc4/0x1e0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792859] blk_mq_get_new_requests+0xce/0x190 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792861] blk_mq_submit_bio+0x1e6/0x430 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792864] __submit_bio+0xf6/0x190 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792866] submit_bio_noacct_nocheck+0xc2/0x120 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792869] submit_bio_noacct+0x1c5/0x540 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792871] ? sio_write_complete+0x1f0/0x1f0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792875] submit_bio+0x47/0xf0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792877] __swap_writepage+0x157/0x570 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792879] swap_writepage+0x2f/0x80 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792880] pageout+0xe2/0x2f0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792883] shrink_page_list+0x60b/0xc80 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792885] shrink_inactive_list+0x1bc/0x4d0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792886] shrink_lruvec+0x2f5/0x450 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792888] shrink_node_memcgs+0x166/0x1d0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792890] shrink_node+0x156/0x5a0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792891] ? __schedule+0x250/0x5d0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792893] balance_pgdat+0x37b/0x880 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792894] ? zone_watermark_ok_safe+0x4f/0x100 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792899] ? balance_pgdat+0x880/0x880 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792900] kswapd+0x10c/0x1c0 Feb 1 01:12:33
[Kernel-packages] [Bug 2006620] [NEW] linux-aws-5.19 hibernation tasks sometimes fail to freeze
Public bug reported: Hibernation on AWS instances with jammy/5.19.0-1019-aws sometimes fails due to the following failure to freeze: Feb 1 01:09:05 ip-172-31-54-178 kernel: [ 443.247854] PM: hibernation: hibernation entry Feb 1 01:09:05 ip-172-31-54-178 kernel: [ 443.347353] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'. Feb 1 01:09:05 ip-172-31-54-178 kernel: [ 443.347355] sched_clock: Marking unstable (442909362062, 1007864825)<-(443748056670, -400707172) Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 443.940489] Filesystems sync: 0.022 seconds Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 443.940492] Freezing user space processes ... (elapsed 0.001 seconds) done. Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 443.941611] OOM killer disabled. Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 443.943036] PM: hibernation: Marking nosave pages: [mem 0x-0x0fff] Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 443.943039] PM: hibernation: Marking nosave pages: [mem 0x0009f000-0x000f] Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 443.943041] PM: hibernation: Marking nosave pages: [mem 0xbffe8000-0x] Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 443.943950] PM: hibernation: Basic memory bitmaps created Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 443.943961] PM: hibernation: Preallocating image memory Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 630.782421] PM: hibernation: Allocated 9655951 pages for snapshot Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 630.782424] PM: hibernation: Allocated 38623804 kbytes in 186.83 seconds (206.73 MB/s) Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 630.782426] Freezing remaining freezable tasks ... Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.789826] Freezing of tasks failed after 20.007 seconds (1 tasks refusing to freeze, wq_busy=0): Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792830] task:kswapd0 state:D stack:0 pid: 328 ppid: 2 flags:0x4000 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792833] Call Trace: Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792835] Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792837] __schedule+0x248/0x5d0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792842] schedule+0x58/0x100 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792844] io_schedule+0x46/0x80 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792846] blk_mq_get_tag+0x117/0x2e0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792852] ? destroy_sched_domains_rcu+0x40/0x40 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792857] __blk_mq_alloc_requests+0xc4/0x1e0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792859] blk_mq_get_new_requests+0xce/0x190 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792861] blk_mq_submit_bio+0x1e6/0x430 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792864] __submit_bio+0xf6/0x190 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792866] submit_bio_noacct_nocheck+0xc2/0x120 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792869] submit_bio_noacct+0x1c5/0x540 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792871] ? sio_write_complete+0x1f0/0x1f0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792875] submit_bio+0x47/0xf0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792877] __swap_writepage+0x157/0x570 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792879] swap_writepage+0x2f/0x80 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792880] pageout+0xe2/0x2f0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792883] shrink_page_list+0x60b/0xc80 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792885] shrink_inactive_list+0x1bc/0x4d0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792886] shrink_lruvec+0x2f5/0x450 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792888] shrink_node_memcgs+0x166/0x1d0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792890] shrink_node+0x156/0x5a0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792891] ? __schedule+0x250/0x5d0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792893] balance_pgdat+0x37b/0x880 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792894] ? zone_watermark_ok_safe+0x4f/0x100 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792899] ? balance_pgdat+0x880/0x880 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792900] kswapd+0x10c/0x1c0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792901] ? balance_pgdat+0x880/0x880 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792903] kthread+0xd1/0xf0 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792906] ? kthread_complete_and_exit+0x20/0x20 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792909] ret_from_fork+0x22/0x30 Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792913] Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792921] Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 650.792922] Restarting kernel threads ... done. Feb 1 01:12:33 ip-172-31-54-178 kernel: [ 651.516499] PM: hibernation: Basic memory bitmaps freed Feb 1
[Kernel-packages] [Bug 2004235] Re: mlxbf-pmc counters not functional for llt_miss block
This bug is awaiting verification that the linux-bluefield/5.4.0-1057.63 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 still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-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/2004235 Title: mlxbf-pmc counters not functional for llt_miss block Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Currently, the driver uses fixed offsets for the control and data registers in the performance counter module. However, this is not correct since the module is not uniform in all HW blocks, and in this case, the llt_miss block is different from the rest. [Fix] The number of counters present in each block is not fixed, and hence the offsets for the control and data registers should also be calculated accordingly. [Test Case] Without the fix, writing 1 to the llt_miss "enable" file will not result in any of the counters incrementing. With the fix, the counters should increment even with the default event settings. [Regression Potential] Can be considered minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2004235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002501] Re: mlxbf-pmc support for BlueField-3
This bug is awaiting verification that the linux-bluefield/5.4.0-1057.63 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 still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-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/2002501 Title: mlxbf-pmc support for BlueField-3 Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Currently, the mlxbf-pmc driver supports only BlueField-1 and BlueField-2 devices. BlueField-3 is not supported. [Fix] Add support for BlueField-3 devices by adding new access mechanism for programming and reading counter values as in the new design, along with the list of supported events in each HW block in BlueField-3. [Test Case] Previously, the driver would not be loaded when the OS is loaded on a BlueField-3 card. With the fix, the driver should get loaded and create sysfs entries as a hwmon device under /sys/class/hwmon/hwmon0. [Regression Potential] The ACPI table needs to be in sync with this change since it depends on newly introduces parameters such as mss_enable and llt_enable, which were not present earlier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2002501/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002361] Re: allow per-net notifier to follow netdev into namespace
This bug is awaiting verification that the linux-bluefield/5.4.0-1057.63
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 still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-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 netdev into namespace
Status in linux-bluefield package in Ubuntu:
Invalid
Status in linux-bluefield source package in Focal:
Fix Committed
Bug description:
* Explain the bug(s)
There is possible deadlock during reload mlxsw into initial netns made
possible by commit:
328fbe747ad4 ("net: Close race between {un, }register_netdevice_notifier()
and setup_net()/cleanup_net()").
* Brief explanation of fixes
Introduce dev_net variant that is basically per-net notifier with an
extension that re-registers the per-net notifier upon netdev namespace
change. Basically the per-net notifier follows the netdev into
namespace.
* How to test
# chroot /host nsenter -t 1 -n devlink dev reload ${port} netns ${NS}
* What it could break
none
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2002361/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2001564] Re: Kernel crash due to Bluefield pka TRNG ioctl call
This bug is awaiting verification that the linux-bluefield/5.4.0-1057.63 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 still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-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/2001564 Title: Kernel crash due to Bluefield pka TRNG ioctl call Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Status in linux-bluefield source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Bluefield 3 on Ubuntu 22.04 and OpenSSL 3.0.2, encounters kernel crash/oops when HTTPS client uses OpenSSL with PKA engine during TLS handshake. The issue is with TRNG ioctl call. The kernel logs show the following errors. Unable to handle kernel access to user memory outside uaccess routines at virtual address ce65d328 BF3 on Ubuntu 22.04, OpenSSl 3.0.2 [Fix] * Change RNG ioctl kernel handler code to copy data from user to kernel space. [Test Case] openssl rand -engine pka 512 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2001564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998863] Re: mlxbf-pmc: Fix event string typo
This bug is awaiting verification that the linux-bluefield/5.4.0-1057.63
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 still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-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/1998863
Title:
mlxbf-pmc: Fix event string typo
Status in linux-bluefield package in Ubuntu:
New
Status in linux-bluefield source package in Focal:
Fix Committed
Status in linux-bluefield source package in Jammy:
Fix Committed
Bug description:
SRU Justification:
[Impact]
Due to a typo, duplicate events are shown
[Fix]
* Fix event name typo.
[Test Case]
* cd /sys/class/hwmon/hwmon0/tilenetX ("X" may be 0..7)
root@localhost:/sys/class/hwmon/hwmon0/tilenet3# cat event_list | grep CRED
15: CDN_DIAG_N_OUT_OF_CRED
16: CDN_DIAG_S_OUT_OF_CRED
17: CDN_DIAG_E_OUT_OF_CRED
18: CDN_DIAG_W_OUT_OF_CRED
19: CDN_DIAG_C_OUT_OF_CRED
25: DDN_DIAG_N_OUT_OF_CRED
26: DDN_DIAG_S_OUT_OF_CRED
27: DDN_DIAG_E_OUT_OF_CRED
28: DDN_DIAG_W_OUT_OF_CRED
29: DDN_DIAG_C_OUT_OF_CRED
35: NDN_DIAG_N_OUT_OF_CRED <== Incorrectly was set to NDN_DIAG_S_OUT_OF_CRED
36: NDN_DIAG_S_OUT_OF_CRED
37: NDN_DIAG_E_OUT_OF_CRED
38: NDN_DIAG_W_OUT_OF_CRED
39: NDN_DIAG_C_OUT_OF_CRED
[Regression Potential]
* Duplicate events still get shown
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1998863/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1998938] Re: Add support for CT accounting stats
This bug is awaiting verification that the linux-bluefield/5.4.0-1057.63 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 still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-bluefield verification-needed-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/1998938 Title: Add support for CT accounting stats Status in linux-bluefield package in Ubuntu: New Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug(s) Add CT accounting stats per flow for TC CT rules. This is only available when nf_conn_acct is enabled so it won’t affect performance when not enabled. * Brief explanation of fixes Cherry-pick. No adaptation. First commit for SW, second commit of HW offloaded rules. * How to test Enable nf_conn_acct and check ct stats. * What it could break. Nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1998938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002636] Re: broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19
** Also affects: broadcom-sta (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: broadcom-sta (Ubuntu Kinetic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to broadcom-sta in Ubuntu. https://bugs.launchpad.net/bugs/2002636 Title: broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19 Status in broadcom-sta package in Ubuntu: Invalid Status in broadcom-sta source package in Jammy: Fix Committed Status in broadcom-sta source package in Kinetic: Confirmed Bug description: [Impact] broadcom-sta-dkms fails to build with jammy/linux-hwe-5.19. [Test case] $ sudo apt-get install broadcom-sta-dkms [Fix] The attached debdiff sync Jammy version to Lunar, minus the dh-dkms build-dep. [Regression potential] None, it's the same version we are already using in Lunar and it contains only fixes to the base version (that is the same among Jammy, Kinetic and Lunar). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2002636/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969342] Missing required logs.
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 1969342 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1969342 Title: running dpdk-testpmd shows "Failed to execute command of OP_SET_RSS_HENA" in vm with intree driver on ubuntu-22.04 Status in dpdk package in Ubuntu: Expired Status in linux package in Ubuntu: Incomplete Bug description: kernel version: kernel-5.15.0-1005-realtime DPDK version: 20.11.3 running ./dpdk-testpmd -c 0x0f -n 4 -- -i --portmask=0x3 in vm detail log: EAL: Probe PCI driver: net_iavf (8086:1889) device: :6f:01.0 (socket 0) iavf_execute_vf_cmd(): Cmd 26 not supported iavf_set_hena(): Failed to execute command of OP_SET_RSS_HENA iavf_default_rss_disable(): fail to disable default RSS,lack PF support EAL: Probe PCI driver: net_iavf (8086:1889) device: :6f:09.0 (socket 0) iavf_execute_vf_cmd(): Cmd 26 not supported iavf_set_hena(): Failed to execute command of OP_SET_RSS_HENA iavf_default_rss_disable(): fail to disable default RSS,lack PF support TELEMETRY: No legacy callbacks, legacy socket not created Interactive-mode selected testpmd: create a new mbuf pool : n=171456, size=2176, socket=0 testpmd: preferred mempool ops selected: ring_mp_mc Configuring Port 0 (socket 0) iavf_configure_queues(): RXDID[1] is not supported, request default RXDID[1] in Queue[0] Port 0: link state change event Port 0: link state change event Port 0: C6:C8:24:35:CE:2F Configuring Port 1 (socket 0) iavf_configure_queues(): RXDID[1] is not supported, request default RXDID[1] in Queue[0] Port 1: link state change event Port 1: link state change event Port 1: C6:F2:9C:FE:70:9D Checking link statuses... Done testpmd> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1969342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969342] Re: running dpdk-testpmd shows "Failed to execute command of OP_SET_RSS_HENA" in vm with intree driver on ubuntu-22.04
Thanks for the heads up, Jean-Mickael. It seems to me that this is actually a bug/request for the Linux kernel package, and not for dpdk. I'm adjust the tasks to reflect this. Please let us know if this is not accurate. Thanks. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1969342 Title: running dpdk-testpmd shows "Failed to execute command of OP_SET_RSS_HENA" in vm with intree driver on ubuntu-22.04 Status in dpdk package in Ubuntu: Expired Status in linux package in Ubuntu: Incomplete Bug description: kernel version: kernel-5.15.0-1005-realtime DPDK version: 20.11.3 running ./dpdk-testpmd -c 0x0f -n 4 -- -i --portmask=0x3 in vm detail log: EAL: Probe PCI driver: net_iavf (8086:1889) device: :6f:01.0 (socket 0) iavf_execute_vf_cmd(): Cmd 26 not supported iavf_set_hena(): Failed to execute command of OP_SET_RSS_HENA iavf_default_rss_disable(): fail to disable default RSS,lack PF support EAL: Probe PCI driver: net_iavf (8086:1889) device: :6f:09.0 (socket 0) iavf_execute_vf_cmd(): Cmd 26 not supported iavf_set_hena(): Failed to execute command of OP_SET_RSS_HENA iavf_default_rss_disable(): fail to disable default RSS,lack PF support TELEMETRY: No legacy callbacks, legacy socket not created Interactive-mode selected testpmd: create a new mbuf pool : n=171456, size=2176, socket=0 testpmd: preferred mempool ops selected: ring_mp_mc Configuring Port 0 (socket 0) iavf_configure_queues(): RXDID[1] is not supported, request default RXDID[1] in Queue[0] Port 0: link state change event Port 0: link state change event Port 0: C6:C8:24:35:CE:2F Configuring Port 1 (socket 0) iavf_configure_queues(): RXDID[1] is not supported, request default RXDID[1] in Queue[0] Port 1: link state change event Port 1: link state change event Port 1: C6:F2:9C:FE:70:9D Checking link statuses... Done testpmd> To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1969342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991691] Re: cannot change mount namespace
Hi again John, I managed to fix most of the denials now, and slack successfully starts up (still quite a few denies, but most can be explained). Took quite a few new rules. Thank you for your help and insight on this. I'll post updates as soon as I have them. I need to find the proper interfaces for the new rules first. -- 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/1991691 Title: cannot change mount namespace Status in Linux: New Status in linux package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Incomplete Bug description: Multiple snaps are either broken or "only" display permission denied messages. slack snap is not starting at all with: > update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.slack /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied firefox snap does start, but also logs errors: update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/doc /usr/share/doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/doc": lstat /var/lib/snapd/hostfs/usr/share/doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/fonts": lstat /var/lib/snapd/hostfs/usr/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/fonts /usr/local/share/fonts none bind,ro 0 0): cannot inspect "/usr/local/share/fonts": lstat /usr/local/share/fonts: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/cups/doc-root /usr/share/cups/doc-root none bind,ro 0 0): cannot create directory "/usr/share/cups/doc-root": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot create directory "/usr/share/gimp/2.0": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/gtk-doc": lstat /var/lib/snapd/hostfs/usr/share/gtk-doc: permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot create directory "/usr/share/libreoffice/help": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot inspect "/var/lib/snapd/hostfs/usr/share/xubuntu-docs": lstat /var/lib/snapd/hostfs/usr/share/xubuntu-docs: permission denied update.go:85: cannot change mount namespace according to change mount (/run/user/1000/doc/by-app/snap.firefox /run/user/1000/doc none bind,rw,x-snapd.ignore-missing 0 0): cannot inspect "/run/user/1000/doc": lstat /run/user/1000/doc: permission denied ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Oct 4 17:29:01 2022 InstallationDate: Installed on 2017-09-26 (1834 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170924) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2022-05-22 (134 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1991691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996540] Re: Kinetic update: upstream stable patchset 2022-11-14
This bug was fixed in the package linux - 5.19.0-31.32 --- linux (5.19.0-31.32) kinetic; urgency=medium * kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423) * amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks (LP: #2003524) - drm/amd: Delay removal of the firmware framebuffer * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.19.0-30.31) kinetic; urgency=medium * kinetic/linux: 5.19.0-30.31 -proposed tracker (LP: #2001756) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/2023.01.02) * Add some ACPI device IDs for Intel HID device (LP: #1995453) - platform/x86/intel/hid: Add some ACPI device IDs * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x riscv64 * BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9 (LP: #2001618) - powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations - powerpc/bpf/64: add support for atomic fetch operations - powerpc/bpf/64: Add instructions for atomic_[cmp]xchg * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Kinetic update: upstream stable patchset 2022-12-15 (LP: #1999828) - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - media: rkisp1: Don't pass the quantization to rkisp1_csm_config() - media: rkisp1: Initialize color space on resizer sink and source pads - media: rkisp1: Use correct macro for gradient registers - media: rkisp1: Zero v4l2_subdev_format fields in when validating links - media: s5p_cec: limit msg.len to CEC_MAX_MSG_SIZE - media: cros-ec-cec: limit msg.len to CEC_MAX_MSG_SIZE - media: dvb-frontends/drxk: initialize err to 0 - media: meson: vdec: fix possible refcount leak in vdec_probe() - media: v4l: subdev: Fail graciously when getting try data for NULL state - ACPI: APEI:
[Kernel-packages] [Bug 1996112] Re: Virtual GPU driver packaging regression
This bug was fixed in the package linux - 5.19.0-31.32 --- linux (5.19.0-31.32) kinetic; urgency=medium * kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423) * amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks (LP: #2003524) - drm/amd: Delay removal of the firmware framebuffer * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.19.0-30.31) kinetic; urgency=medium * kinetic/linux: 5.19.0-30.31 -proposed tracker (LP: #2001756) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/2023.01.02) * Add some ACPI device IDs for Intel HID device (LP: #1995453) - platform/x86/intel/hid: Add some ACPI device IDs * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x riscv64 * BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9 (LP: #2001618) - powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations - powerpc/bpf/64: add support for atomic fetch operations - powerpc/bpf/64: Add instructions for atomic_[cmp]xchg * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Kinetic update: upstream stable patchset 2022-12-15 (LP: #1999828) - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - media: rkisp1: Don't pass the quantization to rkisp1_csm_config() - media: rkisp1: Initialize color space on resizer sink and source pads - media: rkisp1: Use correct macro for gradient registers - media: rkisp1: Zero v4l2_subdev_format fields in when validating links - media: s5p_cec: limit msg.len to CEC_MAX_MSG_SIZE - media: cros-ec-cec: limit msg.len to CEC_MAX_MSG_SIZE - media: dvb-frontends/drxk: initialize err to 0 - media: meson: vdec: fix possible refcount leak in vdec_probe() - media: v4l: subdev: Fail graciously when getting try data for NULL state - ACPI: APEI:
[Kernel-packages] [Bug 1997113] Re: Jammy update: v5.15.76 upstream stable release
This bug was fixed in the package linux - 5.15.0-60.66 --- linux (5.15.0-60.66) jammy; urgency=medium * jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450) * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.15.0-59.65) jammy; urgency=medium * jammy/linux: 5.15.0-59.65 -proposed tracker (LP: #2001801) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2022-47940 - ksmbd: validate length in smb2_write() * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x * support for same series backports versioning numbers (LP: #1993563) - [Packaging] sameport -- add support for sameport versioning * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Micron NVME storage failure [1344,5407] (LP: #1998883) - nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH * Jammy update: v5.15.78 upstream stable release (LP: #1998843) - scsi: lpfc: Rework MIB Rx Monitor debug info logic - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - KVM: x86: Treat #DBs from the emulator as fault-like (code and DR7.GD=1) - drm/amd/display: explicitly disable psr_feature_enable appropriately - mm/hugetlb: fix races when looking up a CONT-PTE/PMD size hugetlb page - HID: playstation: add initial DualSense Edge controller support - KVM: x86: Protect the unused bits in MSR exiting flags - KVM: x86: Copy filter arg outside kvm_vm_ioctl_set_msr_filter() - KVM: x86: Add compat handler for KVM_X86_SET_MSR_FILTER - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Remove magic number - RDMA/hns: Use hr_reg_xxx() instead of remaining roce_set_xxx() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - drm/msm/hdmi: Remove spurious IRQF_ONESHOT flag - drm/msm/hdmi: fix IRQ lifetime - video/fbdev/stifb: Implement the stifb_fillrect() function - fbdev: stifb: Fall back to cfb_fillrect() on 32-bit HCRX cards - mtd: parsers: bcm47xxpart: print correct offset on read error - mtd: parsers: bcm47xxpart: Fix
[Kernel-packages] [Bug 1995453] Re: Add some ACPI device IDs for Intel HID device
This bug was fixed in the package linux - 5.19.0-31.32 --- linux (5.19.0-31.32) kinetic; urgency=medium * kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423) * amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks (LP: #2003524) - drm/amd: Delay removal of the firmware framebuffer * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.19.0-30.31) kinetic; urgency=medium * kinetic/linux: 5.19.0-30.31 -proposed tracker (LP: #2001756) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/2023.01.02) * Add some ACPI device IDs for Intel HID device (LP: #1995453) - platform/x86/intel/hid: Add some ACPI device IDs * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x riscv64 * BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9 (LP: #2001618) - powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations - powerpc/bpf/64: add support for atomic fetch operations - powerpc/bpf/64: Add instructions for atomic_[cmp]xchg * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Kinetic update: upstream stable patchset 2022-12-15 (LP: #1999828) - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - media: rkisp1: Don't pass the quantization to rkisp1_csm_config() - media: rkisp1: Initialize color space on resizer sink and source pads - media: rkisp1: Use correct macro for gradient registers - media: rkisp1: Zero v4l2_subdev_format fields in when validating links - media: s5p_cec: limit msg.len to CEC_MAX_MSG_SIZE - media: cros-ec-cec: limit msg.len to CEC_MAX_MSG_SIZE - media: dvb-frontends/drxk: initialize err to 0 - media: meson: vdec: fix possible refcount leak in vdec_probe() - media: v4l: subdev: Fail graciously when getting try data for NULL state - ACPI: APEI:
[Kernel-packages] [Bug 1996825] Re: Jammy update: v5.15.75 upstream stable release
This bug was fixed in the package linux - 5.15.0-60.66 --- linux (5.15.0-60.66) jammy; urgency=medium * jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450) * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.15.0-59.65) jammy; urgency=medium * jammy/linux: 5.15.0-59.65 -proposed tracker (LP: #2001801) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2022-47940 - ksmbd: validate length in smb2_write() * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x * support for same series backports versioning numbers (LP: #1993563) - [Packaging] sameport -- add support for sameport versioning * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Micron NVME storage failure [1344,5407] (LP: #1998883) - nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH * Jammy update: v5.15.78 upstream stable release (LP: #1998843) - scsi: lpfc: Rework MIB Rx Monitor debug info logic - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - KVM: x86: Treat #DBs from the emulator as fault-like (code and DR7.GD=1) - drm/amd/display: explicitly disable psr_feature_enable appropriately - mm/hugetlb: fix races when looking up a CONT-PTE/PMD size hugetlb page - HID: playstation: add initial DualSense Edge controller support - KVM: x86: Protect the unused bits in MSR exiting flags - KVM: x86: Copy filter arg outside kvm_vm_ioctl_set_msr_filter() - KVM: x86: Add compat handler for KVM_X86_SET_MSR_FILTER - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Remove magic number - RDMA/hns: Use hr_reg_xxx() instead of remaining roce_set_xxx() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - drm/msm/hdmi: Remove spurious IRQF_ONESHOT flag - drm/msm/hdmi: fix IRQ lifetime - video/fbdev/stifb: Implement the stifb_fillrect() function - fbdev: stifb: Fall back to cfb_fillrect() on 32-bit HCRX cards - mtd: parsers: bcm47xxpart: print correct offset on read error - mtd: parsers: bcm47xxpart: Fix
[Kernel-packages] [Bug 1993563] Re: support for same series backports versioning numbers
This bug was fixed in the package linux - 5.15.0-60.66 --- linux (5.15.0-60.66) jammy; urgency=medium * jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450) * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.15.0-59.65) jammy; urgency=medium * jammy/linux: 5.15.0-59.65 -proposed tracker (LP: #2001801) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2022-47940 - ksmbd: validate length in smb2_write() * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x * support for same series backports versioning numbers (LP: #1993563) - [Packaging] sameport -- add support for sameport versioning * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Micron NVME storage failure [1344,5407] (LP: #1998883) - nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH * Jammy update: v5.15.78 upstream stable release (LP: #1998843) - scsi: lpfc: Rework MIB Rx Monitor debug info logic - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - KVM: x86: Treat #DBs from the emulator as fault-like (code and DR7.GD=1) - drm/amd/display: explicitly disable psr_feature_enable appropriately - mm/hugetlb: fix races when looking up a CONT-PTE/PMD size hugetlb page - HID: playstation: add initial DualSense Edge controller support - KVM: x86: Protect the unused bits in MSR exiting flags - KVM: x86: Copy filter arg outside kvm_vm_ioctl_set_msr_filter() - KVM: x86: Add compat handler for KVM_X86_SET_MSR_FILTER - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Remove magic number - RDMA/hns: Use hr_reg_xxx() instead of remaining roce_set_xxx() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - drm/msm/hdmi: Remove spurious IRQF_ONESHOT flag - drm/msm/hdmi: fix IRQ lifetime - video/fbdev/stifb: Implement the stifb_fillrect() function - fbdev: stifb: Fall back to cfb_fillrect() on 32-bit HCRX cards - mtd: parsers: bcm47xxpart: print correct offset on read error - mtd: parsers: bcm47xxpart: Fix
[Kernel-packages] [Bug 2001618] Re: BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9
This bug was fixed in the package linux - 5.19.0-31.32 --- linux (5.19.0-31.32) kinetic; urgency=medium * kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423) * amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks (LP: #2003524) - drm/amd: Delay removal of the firmware framebuffer * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.19.0-30.31) kinetic; urgency=medium * kinetic/linux: 5.19.0-30.31 -proposed tracker (LP: #2001756) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/2023.01.02) * Add some ACPI device IDs for Intel HID device (LP: #1995453) - platform/x86/intel/hid: Add some ACPI device IDs * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x riscv64 * BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9 (LP: #2001618) - powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations - powerpc/bpf/64: add support for atomic fetch operations - powerpc/bpf/64: Add instructions for atomic_[cmp]xchg * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Kinetic update: upstream stable patchset 2022-12-15 (LP: #1999828) - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - media: rkisp1: Don't pass the quantization to rkisp1_csm_config() - media: rkisp1: Initialize color space on resizer sink and source pads - media: rkisp1: Use correct macro for gradient registers - media: rkisp1: Zero v4l2_subdev_format fields in when validating links - media: s5p_cec: limit msg.len to CEC_MAX_MSG_SIZE - media: cros-ec-cec: limit msg.len to CEC_MAX_MSG_SIZE - media: dvb-frontends/drxk: initialize err to 0 - media: meson: vdec: fix possible refcount leak in vdec_probe() - media: v4l: subdev: Fail graciously when getting try data for NULL state - ACPI: APEI:
[Kernel-packages] [Bug 1997981] Re: Jammy update: v5.15.77 upstream stable release
This bug was fixed in the package linux - 5.15.0-60.66 --- linux (5.15.0-60.66) jammy; urgency=medium * jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450) * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.15.0-59.65) jammy; urgency=medium * jammy/linux: 5.15.0-59.65 -proposed tracker (LP: #2001801) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2022-47940 - ksmbd: validate length in smb2_write() * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x * support for same series backports versioning numbers (LP: #1993563) - [Packaging] sameport -- add support for sameport versioning * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Micron NVME storage failure [1344,5407] (LP: #1998883) - nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH * Jammy update: v5.15.78 upstream stable release (LP: #1998843) - scsi: lpfc: Rework MIB Rx Monitor debug info logic - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - KVM: x86: Treat #DBs from the emulator as fault-like (code and DR7.GD=1) - drm/amd/display: explicitly disable psr_feature_enable appropriately - mm/hugetlb: fix races when looking up a CONT-PTE/PMD size hugetlb page - HID: playstation: add initial DualSense Edge controller support - KVM: x86: Protect the unused bits in MSR exiting flags - KVM: x86: Copy filter arg outside kvm_vm_ioctl_set_msr_filter() - KVM: x86: Add compat handler for KVM_X86_SET_MSR_FILTER - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Remove magic number - RDMA/hns: Use hr_reg_xxx() instead of remaining roce_set_xxx() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - drm/msm/hdmi: Remove spurious IRQF_ONESHOT flag - drm/msm/hdmi: fix IRQ lifetime - video/fbdev/stifb: Implement the stifb_fillrect() function - fbdev: stifb: Fall back to cfb_fillrect() on 32-bit HCRX cards - mtd: parsers: bcm47xxpart: print correct offset on read error - mtd: parsers: bcm47xxpart: Fix
[Kernel-packages] [Bug 1999528] Re: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later
This bug was fixed in the package linux - 5.19.0-31.32 --- linux (5.19.0-31.32) kinetic; urgency=medium * kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423) * amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks (LP: #2003524) - drm/amd: Delay removal of the firmware framebuffer * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.19.0-30.31) kinetic; urgency=medium * kinetic/linux: 5.19.0-30.31 -proposed tracker (LP: #2001756) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/2023.01.02) * Add some ACPI device IDs for Intel HID device (LP: #1995453) - platform/x86/intel/hid: Add some ACPI device IDs * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x riscv64 * BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9 (LP: #2001618) - powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations - powerpc/bpf/64: add support for atomic fetch operations - powerpc/bpf/64: Add instructions for atomic_[cmp]xchg * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Kinetic update: upstream stable patchset 2022-12-15 (LP: #1999828) - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - media: rkisp1: Don't pass the quantization to rkisp1_csm_config() - media: rkisp1: Initialize color space on resizer sink and source pads - media: rkisp1: Use correct macro for gradient registers - media: rkisp1: Zero v4l2_subdev_format fields in when validating links - media: s5p_cec: limit msg.len to CEC_MAX_MSG_SIZE - media: cros-ec-cec: limit msg.len to CEC_MAX_MSG_SIZE - media: dvb-frontends/drxk: initialize err to 0 - media: meson: vdec: fix possible refcount leak in vdec_probe() - media: v4l: subdev: Fail graciously when getting try data for NULL state - ACPI: APEI:
[Kernel-packages] [Bug 1999828] Re: Kinetic update: upstream stable patchset 2022-12-15
This bug was fixed in the package linux - 5.19.0-31.32 --- linux (5.19.0-31.32) kinetic; urgency=medium * kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423) * amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks (LP: #2003524) - drm/amd: Delay removal of the firmware framebuffer * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.19.0-30.31) kinetic; urgency=medium * kinetic/linux: 5.19.0-30.31 -proposed tracker (LP: #2001756) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/2023.01.02) * Add some ACPI device IDs for Intel HID device (LP: #1995453) - platform/x86/intel/hid: Add some ACPI device IDs * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x riscv64 * BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9 (LP: #2001618) - powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations - powerpc/bpf/64: add support for atomic fetch operations - powerpc/bpf/64: Add instructions for atomic_[cmp]xchg * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Kinetic update: upstream stable patchset 2022-12-15 (LP: #1999828) - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - media: rkisp1: Don't pass the quantization to rkisp1_csm_config() - media: rkisp1: Initialize color space on resizer sink and source pads - media: rkisp1: Use correct macro for gradient registers - media: rkisp1: Zero v4l2_subdev_format fields in when validating links - media: s5p_cec: limit msg.len to CEC_MAX_MSG_SIZE - media: cros-ec-cec: limit msg.len to CEC_MAX_MSG_SIZE - media: dvb-frontends/drxk: initialize err to 0 - media: meson: vdec: fix possible refcount leak in vdec_probe() - media: v4l: subdev: Fail graciously when getting try data for NULL state - ACPI: APEI:
[Kernel-packages] [Bug 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
This bug was fixed in the package linux - 5.15.0-60.66 --- linux (5.15.0-60.66) jammy; urgency=medium * jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450) * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.15.0-59.65) jammy; urgency=medium * jammy/linux: 5.15.0-59.65 -proposed tracker (LP: #2001801) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2022-47940 - ksmbd: validate length in smb2_write() * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x * support for same series backports versioning numbers (LP: #1993563) - [Packaging] sameport -- add support for sameport versioning * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Micron NVME storage failure [1344,5407] (LP: #1998883) - nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH * Jammy update: v5.15.78 upstream stable release (LP: #1998843) - scsi: lpfc: Rework MIB Rx Monitor debug info logic - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - KVM: x86: Treat #DBs from the emulator as fault-like (code and DR7.GD=1) - drm/amd/display: explicitly disable psr_feature_enable appropriately - mm/hugetlb: fix races when looking up a CONT-PTE/PMD size hugetlb page - HID: playstation: add initial DualSense Edge controller support - KVM: x86: Protect the unused bits in MSR exiting flags - KVM: x86: Copy filter arg outside kvm_vm_ioctl_set_msr_filter() - KVM: x86: Add compat handler for KVM_X86_SET_MSR_FILTER - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Remove magic number - RDMA/hns: Use hr_reg_xxx() instead of remaining roce_set_xxx() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - drm/msm/hdmi: Remove spurious IRQF_ONESHOT flag - drm/msm/hdmi: fix IRQ lifetime - video/fbdev/stifb: Implement the stifb_fillrect() function - fbdev: stifb: Fall back to cfb_fillrect() on 32-bit HCRX cards - mtd: parsers: bcm47xxpart: print correct offset on read error - mtd: parsers: bcm47xxpart: Fix
[Kernel-packages] [Bug 1999528] Re: [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later
This bug was fixed in the package linux - 5.15.0-60.66 --- linux (5.15.0-60.66) jammy; urgency=medium * jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450) * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.15.0-59.65) jammy; urgency=medium * jammy/linux: 5.15.0-59.65 -proposed tracker (LP: #2001801) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2022-47940 - ksmbd: validate length in smb2_write() * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x * support for same series backports versioning numbers (LP: #1993563) - [Packaging] sameport -- add support for sameport versioning * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Micron NVME storage failure [1344,5407] (LP: #1998883) - nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH * Jammy update: v5.15.78 upstream stable release (LP: #1998843) - scsi: lpfc: Rework MIB Rx Monitor debug info logic - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - KVM: x86: Treat #DBs from the emulator as fault-like (code and DR7.GD=1) - drm/amd/display: explicitly disable psr_feature_enable appropriately - mm/hugetlb: fix races when looking up a CONT-PTE/PMD size hugetlb page - HID: playstation: add initial DualSense Edge controller support - KVM: x86: Protect the unused bits in MSR exiting flags - KVM: x86: Copy filter arg outside kvm_vm_ioctl_set_msr_filter() - KVM: x86: Add compat handler for KVM_X86_SET_MSR_FILTER - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Remove magic number - RDMA/hns: Use hr_reg_xxx() instead of remaining roce_set_xxx() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - drm/msm/hdmi: Remove spurious IRQF_ONESHOT flag - drm/msm/hdmi: fix IRQ lifetime - video/fbdev/stifb: Implement the stifb_fillrect() function - fbdev: stifb: Fall back to cfb_fillrect() on 32-bit HCRX cards - mtd: parsers: bcm47xxpart: print correct offset on read error - mtd: parsers: bcm47xxpart: Fix
[Kernel-packages] [Bug 1998115] Re: Fix iosm: WWAN cannot build the connection (DW5823e)
This bug was fixed in the package linux - 5.15.0-60.66 --- linux (5.15.0-60.66) jammy; urgency=medium * jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450) * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.15.0-59.65) jammy; urgency=medium * jammy/linux: 5.15.0-59.65 -proposed tracker (LP: #2001801) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2022-47940 - ksmbd: validate length in smb2_write() * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x * support for same series backports versioning numbers (LP: #1993563) - [Packaging] sameport -- add support for sameport versioning * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Micron NVME storage failure [1344,5407] (LP: #1998883) - nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH * Jammy update: v5.15.78 upstream stable release (LP: #1998843) - scsi: lpfc: Rework MIB Rx Monitor debug info logic - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - KVM: x86: Treat #DBs from the emulator as fault-like (code and DR7.GD=1) - drm/amd/display: explicitly disable psr_feature_enable appropriately - mm/hugetlb: fix races when looking up a CONT-PTE/PMD size hugetlb page - HID: playstation: add initial DualSense Edge controller support - KVM: x86: Protect the unused bits in MSR exiting flags - KVM: x86: Copy filter arg outside kvm_vm_ioctl_set_msr_filter() - KVM: x86: Add compat handler for KVM_X86_SET_MSR_FILTER - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Remove magic number - RDMA/hns: Use hr_reg_xxx() instead of remaining roce_set_xxx() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - drm/msm/hdmi: Remove spurious IRQF_ONESHOT flag - drm/msm/hdmi: fix IRQ lifetime - video/fbdev/stifb: Implement the stifb_fillrect() function - fbdev: stifb: Fall back to cfb_fillrect() on 32-bit HCRX cards - mtd: parsers: bcm47xxpart: print correct offset on read error - mtd: parsers: bcm47xxpart: Fix
[Kernel-packages] [Bug 1998115] Re: Fix iosm: WWAN cannot build the connection (DW5823e)
This bug was fixed in the package linux - 5.19.0-31.32 --- linux (5.19.0-31.32) kinetic; urgency=medium * kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423) * amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks (LP: #2003524) - drm/amd: Delay removal of the firmware framebuffer * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.19.0-30.31) kinetic; urgency=medium * kinetic/linux: 5.19.0-30.31 -proposed tracker (LP: #2001756) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/2023.01.02) * Add some ACPI device IDs for Intel HID device (LP: #1995453) - platform/x86/intel/hid: Add some ACPI device IDs * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x riscv64 * BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9 (LP: #2001618) - powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations - powerpc/bpf/64: add support for atomic fetch operations - powerpc/bpf/64: Add instructions for atomic_[cmp]xchg * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Kinetic update: upstream stable patchset 2022-12-15 (LP: #1999828) - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - media: rkisp1: Don't pass the quantization to rkisp1_csm_config() - media: rkisp1: Initialize color space on resizer sink and source pads - media: rkisp1: Use correct macro for gradient registers - media: rkisp1: Zero v4l2_subdev_format fields in when validating links - media: s5p_cec: limit msg.len to CEC_MAX_MSG_SIZE - media: cros-ec-cec: limit msg.len to CEC_MAX_MSG_SIZE - media: dvb-frontends/drxk: initialize err to 0 - media: meson: vdec: fix possible refcount leak in vdec_probe() - media: v4l: subdev: Fail graciously when getting try data for NULL state - ACPI: APEI:
[Kernel-packages] [Bug 1998106] Re: Fix AMD-PState driver for Genoa CPU
This bug was fixed in the package linux - 5.15.0-60.66 --- linux (5.15.0-60.66) jammy; urgency=medium * jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450) * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.15.0-59.65) jammy; urgency=medium * jammy/linux: 5.15.0-59.65 -proposed tracker (LP: #2001801) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2022-47940 - ksmbd: validate length in smb2_write() * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x * support for same series backports versioning numbers (LP: #1993563) - [Packaging] sameport -- add support for sameport versioning * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Micron NVME storage failure [1344,5407] (LP: #1998883) - nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH * Jammy update: v5.15.78 upstream stable release (LP: #1998843) - scsi: lpfc: Rework MIB Rx Monitor debug info logic - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - KVM: x86: Treat #DBs from the emulator as fault-like (code and DR7.GD=1) - drm/amd/display: explicitly disable psr_feature_enable appropriately - mm/hugetlb: fix races when looking up a CONT-PTE/PMD size hugetlb page - HID: playstation: add initial DualSense Edge controller support - KVM: x86: Protect the unused bits in MSR exiting flags - KVM: x86: Copy filter arg outside kvm_vm_ioctl_set_msr_filter() - KVM: x86: Add compat handler for KVM_X86_SET_MSR_FILTER - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Remove magic number - RDMA/hns: Use hr_reg_xxx() instead of remaining roce_set_xxx() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - drm/msm/hdmi: Remove spurious IRQF_ONESHOT flag - drm/msm/hdmi: fix IRQ lifetime - video/fbdev/stifb: Implement the stifb_fillrect() function - fbdev: stifb: Fall back to cfb_fillrect() on 32-bit HCRX cards - mtd: parsers: bcm47xxpart: print correct offset on read error - mtd: parsers: bcm47xxpart: Fix
[Kernel-packages] [Bug 1998106] Re: Fix AMD-PState driver for Genoa CPU
This bug was fixed in the package linux - 5.19.0-31.32 --- linux (5.19.0-31.32) kinetic; urgency=medium * kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423) * amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks (LP: #2003524) - drm/amd: Delay removal of the firmware framebuffer * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.19.0-30.31) kinetic; urgency=medium * kinetic/linux: 5.19.0-30.31 -proposed tracker (LP: #2001756) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/2023.01.02) * Add some ACPI device IDs for Intel HID device (LP: #1995453) - platform/x86/intel/hid: Add some ACPI device IDs * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x riscv64 * BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9 (LP: #2001618) - powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations - powerpc/bpf/64: add support for atomic fetch operations - powerpc/bpf/64: Add instructions for atomic_[cmp]xchg * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Kinetic update: upstream stable patchset 2022-12-15 (LP: #1999828) - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - media: rkisp1: Don't pass the quantization to rkisp1_csm_config() - media: rkisp1: Initialize color space on resizer sink and source pads - media: rkisp1: Use correct macro for gradient registers - media: rkisp1: Zero v4l2_subdev_format fields in when validating links - media: s5p_cec: limit msg.len to CEC_MAX_MSG_SIZE - media: cros-ec-cec: limit msg.len to CEC_MAX_MSG_SIZE - media: dvb-frontends/drxk: initialize err to 0 - media: meson: vdec: fix possible refcount leak in vdec_probe() - media: v4l: subdev: Fail graciously when getting try data for NULL state - ACPI: APEI:
[Kernel-packages] [Bug 1997200] Re: Mediatek WLAN RZ616(MT7922) SAR table control
This bug was fixed in the package linux - 5.19.0-31.32 --- linux (5.19.0-31.32) kinetic; urgency=medium * kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423) * amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP blocks (LP: #2003524) - drm/amd: Delay removal of the firmware framebuffer * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.19.0-30.31) kinetic; urgency=medium * kinetic/linux: 5.19.0-30.31 -proposed tracker (LP: #2001756) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts - debian/dkms-versions -- update from kernel-versions (main/2023.01.02) * Add some ACPI device IDs for Intel HID device (LP: #1995453) - platform/x86/intel/hid: Add some ACPI device IDs * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x riscv64 * BPF_[AND|OR|XOR|FETCH|XCHG|CMPXCHG] in net:test_bpf.sh from ubuntu_kernel_selftests failed on K-5.19 P9 (LP: #2001618) - powerpc/bpf/64: add support for BPF_ATOMIC bitwise operations - powerpc/bpf/64: add support for atomic fetch operations - powerpc/bpf/64: Add instructions for atomic_[cmp]xchg * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Kinetic update: upstream stable patchset 2022-12-15 (LP: #1999828) - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - media: rkisp1: Don't pass the quantization to rkisp1_csm_config() - media: rkisp1: Initialize color space on resizer sink and source pads - media: rkisp1: Use correct macro for gradient registers - media: rkisp1: Zero v4l2_subdev_format fields in when validating links - media: s5p_cec: limit msg.len to CEC_MAX_MSG_SIZE - media: cros-ec-cec: limit msg.len to CEC_MAX_MSG_SIZE - media: dvb-frontends/drxk: initialize err to 0 - media: meson: vdec: fix possible refcount leak in vdec_probe() - media: v4l: subdev: Fail graciously when getting try data for NULL state - ACPI: APEI:
[Kernel-packages] [Bug 1989990] Re: [SRU] Ubuntu 22.04 - NVMe TCP - Host fails to reconnect to target after link down/link up sequence
This bug was fixed in the package linux - 5.15.0-60.66 --- linux (5.15.0-60.66) jammy; urgency=medium * jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450) * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.15.0-59.65) jammy; urgency=medium * jammy/linux: 5.15.0-59.65 -proposed tracker (LP: #2001801) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2022-47940 - ksmbd: validate length in smb2_write() * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x * support for same series backports versioning numbers (LP: #1993563) - [Packaging] sameport -- add support for sameport versioning * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Micron NVME storage failure [1344,5407] (LP: #1998883) - nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH * Jammy update: v5.15.78 upstream stable release (LP: #1998843) - scsi: lpfc: Rework MIB Rx Monitor debug info logic - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - KVM: x86: Treat #DBs from the emulator as fault-like (code and DR7.GD=1) - drm/amd/display: explicitly disable psr_feature_enable appropriately - mm/hugetlb: fix races when looking up a CONT-PTE/PMD size hugetlb page - HID: playstation: add initial DualSense Edge controller support - KVM: x86: Protect the unused bits in MSR exiting flags - KVM: x86: Copy filter arg outside kvm_vm_ioctl_set_msr_filter() - KVM: x86: Add compat handler for KVM_X86_SET_MSR_FILTER - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Remove magic number - RDMA/hns: Use hr_reg_xxx() instead of remaining roce_set_xxx() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - drm/msm/hdmi: Remove spurious IRQF_ONESHOT flag - drm/msm/hdmi: fix IRQ lifetime - video/fbdev/stifb: Implement the stifb_fillrect() function - fbdev: stifb: Fall back to cfb_fillrect() on 32-bit HCRX cards - mtd: parsers: bcm47xxpart: print correct offset on read error - mtd: parsers: bcm47xxpart: Fix
[Kernel-packages] [Bug 1989944] Re: [22.04/Jammy] Replace SAUCE AMD DP tunneling patch by upstream version
This bug was fixed in the package linux - 5.15.0-60.66 --- linux (5.15.0-60.66) jammy; urgency=medium * jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450) * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.15.0-59.65) jammy; urgency=medium * jammy/linux: 5.15.0-59.65 -proposed tracker (LP: #2001801) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2022-47940 - ksmbd: validate length in smb2_write() * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x * support for same series backports versioning numbers (LP: #1993563) - [Packaging] sameport -- add support for sameport versioning * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Micron NVME storage failure [1344,5407] (LP: #1998883) - nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH * Jammy update: v5.15.78 upstream stable release (LP: #1998843) - scsi: lpfc: Rework MIB Rx Monitor debug info logic - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - KVM: x86: Treat #DBs from the emulator as fault-like (code and DR7.GD=1) - drm/amd/display: explicitly disable psr_feature_enable appropriately - mm/hugetlb: fix races when looking up a CONT-PTE/PMD size hugetlb page - HID: playstation: add initial DualSense Edge controller support - KVM: x86: Protect the unused bits in MSR exiting flags - KVM: x86: Copy filter arg outside kvm_vm_ioctl_set_msr_filter() - KVM: x86: Add compat handler for KVM_X86_SET_MSR_FILTER - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Remove magic number - RDMA/hns: Use hr_reg_xxx() instead of remaining roce_set_xxx() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - drm/msm/hdmi: Remove spurious IRQF_ONESHOT flag - drm/msm/hdmi: fix IRQ lifetime - video/fbdev/stifb: Implement the stifb_fillrect() function - fbdev: stifb: Fall back to cfb_fillrect() on 32-bit HCRX cards - mtd: parsers: bcm47xxpart: print correct offset on read error - mtd: parsers: bcm47xxpart: Fix
[Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
This bug was fixed in the package linux - 5.15.0-60.66 --- linux (5.15.0-60.66) jammy; urgency=medium * jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450) * Revoke & rotate to new signing key (LP: #2002812) - [Packaging] Revoke and rotate to new signing key linux (5.15.0-59.65) jammy; urgency=medium * jammy/linux: 5.15.0-59.65 -proposed tracker (LP: #2001801) * Packaging resync (LP: #1786013) - [Packaging] update helper scripts * CVE-2022-47940 - ksmbd: validate length in smb2_write() * Fix iosm: WWAN cannot build the connection (DW5823e) (LP: #1998115) - net: wwan: iosm: fix driver not working with INTEL_IOMMU disabled - [Config] CONFIG_IOSM update annotations on arm64 armhf ppc64el s390x * support for same series backports versioning numbers (LP: #1993563) - [Packaging] sameport -- add support for sameport versioning * [DEP-8] Run ADT regression suite for lowlatency kernels Jammy and later (LP: #1999528) - [DEP-8] Fix regression suite to run on lowlatency * Micron NVME storage failure [1344,5407] (LP: #1998883) - nvme: add a bogus subsystem NQN quirk for Micron MTFDKBA2T0TFH * Jammy update: v5.15.78 upstream stable release (LP: #1998843) - scsi: lpfc: Rework MIB Rx Monitor debug info logic - serial: ar933x: Deassert Transmit Enable on ->rs485_config() - KVM: x86: Trace re-injected exceptions - KVM: x86: Treat #DBs from the emulator as fault-like (code and DR7.GD=1) - drm/amd/display: explicitly disable psr_feature_enable appropriately - mm/hugetlb: fix races when looking up a CONT-PTE/PMD size hugetlb page - HID: playstation: add initial DualSense Edge controller support - KVM: x86: Protect the unused bits in MSR exiting flags - KVM: x86: Copy filter arg outside kvm_vm_ioctl_set_msr_filter() - KVM: x86: Add compat handler for KVM_X86_SET_MSR_FILTER - RDMA/cma: Use output interface for net_dev check - IB/hfi1: Correctly move list in sc_disable() - RDMA/hns: Remove magic number - RDMA/hns: Use hr_reg_xxx() instead of remaining roce_set_xxx() - RDMA/hns: Disable local invalidate operation - NFSv4: Fix a potential state reclaim deadlock - NFSv4.1: Handle RECLAIM_COMPLETE trunking errors - NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot - SUNRPC: Fix null-ptr-deref when xps sysfs alloc failed - NFSv4.2: Fixup CLONE dest file size for zero-length count - nfs4: Fix kmemleak when allocate slot failed - net: dsa: Fix possible memory leaks in dsa_loop_init() - RDMA/core: Fix null-ptr-deref in ib_core_cleanup() - RDMA/qedr: clean up work queue on failure in qedr_alloc_resources() - net: dsa: fall back to default tagger if we can't load the one from DT - nfc: fdp: Fix potential memory leak in fdp_nci_send() - nfc: nxp-nci: Fix potential memory leak in nxp_nci_send() - nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send() - nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send() - net: fec: fix improper use of NETDEV_TX_BUSY - ata: pata_legacy: fix pdc20230_set_piomode() - net: sched: Fix use after free in red_enqueue() - net: tun: fix bugs for oversize packet when napi frags enabled - netfilter: nf_tables: netlink notifier might race to release objects - netfilter: nf_tables: release flow rule object from commit path - ipvs: use explicitly signed chars - ipvs: fix WARNING in __ip_vs_cleanup_batch() - ipvs: fix WARNING in ip_vs_app_net_cleanup() - rose: Fix NULL pointer dereference in rose_send_frame() - mISDN: fix possible memory leak in mISDN_register_device() - isdn: mISDN: netjet: fix wrong check of device registration - btrfs: fix inode list leak during backref walking at resolve_indirect_refs() - btrfs: fix inode list leak during backref walking at find_parent_nodes() - btrfs: fix ulist leaks in error paths of qgroup self tests - netfilter: ipset: enforce documented limit to prevent allocating huge memory - Bluetooth: virtio_bt: Use skb_put to set length - Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del() - Bluetooth: L2CAP: Fix memory leak in vhci_write - net: mdio: fix undefined behavior in bit shift for __mdiobus_register - ibmvnic: Free rwi on reset success - stmmac: dwmac-loongson: fix invalid mdio_node - net/smc: Fix possible leaked pernet namespace in smc_init() - net, neigh: Fix null-ptr-deref in neigh_table_clear() - ipv6: fix WARNING in ip6_route_net_exit_late() - vsock: fix possible infinite sleep in vsock_connectible_wait_data() - drm/msm/hdmi: Remove spurious IRQF_ONESHOT flag - drm/msm/hdmi: fix IRQ lifetime - video/fbdev/stifb: Implement the stifb_fillrect() function - fbdev: stifb: Fall back to cfb_fillrect() on 32-bit HCRX cards - mtd: parsers: bcm47xxpart: print correct offset on read error - mtd: parsers: bcm47xxpart: Fix
