[Kernel-packages] [Bug 2026358] Re: can not umount cifs share
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2026358 Title: can not umount cifs share Status in linux package in Ubuntu: Confirmed Bug description: Hello, I can not umount a cifs share with umount /media/share. I alwas have to use umount -f -l /media/share. We have round about 260 installations with Automatic software distribution which need to unmount the share or it get stuck. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-154-generic 5.4.0-154.171 ProcVersionSignature: Ubuntu 5.4.0-154.171-generic 5.4.240 Uname: Linux 5.4.0-154-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 7 10:50 seq crw-rw 1 root audio 116, 33 Jul 7 10:50 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Fri Jul 7 10:57:48 2023 InstallationDate: Installed on 2021-12-15 (569 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-154-generic root=/dev/mapper/vg0--ubuntu-lv0--system ro maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-154-generic N/A linux-backports-modules-5.4.0-154-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026358/+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 2018960] Re: linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212 sk_stream_kill_queues+0xcf/0xe0
Saw this on U18 based nodes in gateway roles running
4.15.0-{211,212}-generic. It seems to be fixed in 4.15.0-213-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2018960
Title:
linux-image-5.4.0-149-generic (regression): 0 at net/core/stream.c:212
sk_stream_kill_queues+0xcf/0xe0
Status in linux-signed package in Ubuntu:
Fix Released
Status in linux-signed-kvm package in Ubuntu:
Fix Released
Bug description:
After upgrading and rebooting this Ubuntu 20.04 LTS server (Ubuntu
Focal), I noticed that it was suddenly getting a bunch of kernel log
(dmesg) reports like:
WARNING: CPU: 4 PID: 0 at net/core/stream.c:212
sk_stream_kill_queues+0xcf/0xe0
while investigating I determined that it is currently running the
focal-proposed kernel (linux-image-5.4.0-149-generic), which it turns
out was enabled for this server (clearly it seemed like a good idea at
the time).
I'm not expecting focal-proposed to be fixed as if it were a release
package, but since I couldn't find any reports on Launchpad I figured
I should let y'all know this focal-proposed package could do with some
additional work before it's actually released :-)
There have been at least 80 such reports in the last 5 hours since the
server was rebooted, differing only by the CPU core and the process
reported, although it seems the last one was a couple of hours ago, so
I guess it's traffic dependent/timing dependent.
ewen@naosr620:~$ uptime
16:27:32 up 5:19, 1 user, load average: 0.08, 0.14, 0.06
ewen@naosr620:~$ dmesg -t | grep WARNING | sed 's/CPU: [0-9]*/CPU: N/; s/PID:
[0-9]*/PID: N/;' | uniq -c
88 WARNING: CPU: N PID: N at net/core/stream.c:212
sk_stream_kill_queues+0xcf/0xe0
ewen@naosr620:~$
Ubuntu Release:
ewen@naosr620:~$ lsb_release -rd
Description: Ubuntu 20.04.6 LTS
Release: 20.04
ewen@naosr620:~$
Kernel/package version affected:
ewen@naosr620:~$ uname -a
Linux naosr620 5.4.0-149-generic #166-Ubuntu SMP Tue Apr 18 16:51:45 UTC 2023
x86_64 x86_64 x86_64 GNU/Linux
ewen@naosr620:~$ dpkg -l | grep linux-image | grep 149
ii linux-image-5.4.0-149-generic 5.4.0-149.166
amd64Signed kernel image generic
ii linux-image-generic5.4.0.149.147
amd64Generic Linux kernel image
ewen@naosr620:~$ apt-cache policy linux-image-5.4.0-149-generic
linux-image-5.4.0-149-generic:
Installed: 5.4.0-149.166
Candidate: 5.4.0-149.166
Version table:
*** 5.4.0-149.166 500
500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64
Packages
100 /var/lib/dpkg/status
ewen@naosr620:~$ apt-cache policy linux-image-generic
linux-image-generic:
Installed: 5.4.0.149.147
Candidate: 5.4.0.149.147
Version table:
*** 5.4.0.149.147 500
500 https://mirror.fsmg.org.nz/ubuntu focal-proposed/main amd64
Packages
100 /var/lib/dpkg/status
5.4.0.148.146 500
500 https://mirror.fsmg.org.nz/ubuntu focal-updates/main amd64
Packages
500 https://mirror.fsmg.org.nz/ubuntu focal-security/main amd64
Packages
5.4.0.26.32 500
500 https://mirror.fsmg.org.nz/ubuntu focal/main amd64 Packages
ewen@naosr620:~$
ewen@naosr620:~$ apt-cache show linux-image-5.4.0-149-generic | grep Source:
Source: linux-signed
ewen@naosr620:~$
Full example dmesg, including stack trace (they all seem to be WARNINGs, and
other than filling dmesg / system logs the system "appears to be running okay",
so I'm not going to rush another reboot now -- near end of business day):
ewen@naosr620:~$ date
Tue 09 May 2023 16:34:56 NZST
ewen@naosr620:~$ dmesg -T | tail -100 | grep -B 150 "end trace" | grep -A 999
"cut here"
[Tue May 9 14:21:18 2023] [ cut here ]
[Tue May 9 14:21:18 2023] WARNING: CPU: 10 PID: 0 at net/core/stream.c:212
sk_stream_kill_queues+0xcf/0xe0
[Tue May 9 14:21:18 2023] Modules linked in: mpt3sas raid_class
scsi_transport_sas mptctl mptbase vhost_net vhost tap ip6t_REJECT
nf_reject_ipv6 ip6table_mangle ip6table_nat ip6table_raw nf_log_ipv6 xt_recent
ipt_REJECT nf_reject_ipv4 xt_hashlimit xt_addrtype xt_multiport xt_comment
xt_conntrack xt_mark iptable_mangle xt_MASQUERADE iptable_nat xt_CT xt_tcpudp
iptable_raw nfnetlink_log xt_NFLOG nf_log_ipv4 nf_log_common xt_LOG nf_nat_tftp
nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_irc
ebtable_filter nf_nat_h323 ebtables nf_nat_ftp nf_nat_amanda ts_kmp
ip6table_filter nf_conntrack_amanda nf_nat ip6_tables nf_conntrack_sane
nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_netlink
nfnetlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc
nf_conntrack_h323 nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4
ip
[Kernel-packages] [Bug 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
The attachment "firmware-sof_2.0-1ubuntu4.2.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: In Progress Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Mantic: New Status in linux source package in Mantic: Incomplete Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+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 2020656] Re: system freeze (cpu fan goes high)
Hello I've created an issue on lenovo side, you can track it here : https://forums.lenovo.com/t5/Ubuntu/System-freeze-with- Ubuntu-22-04-to-23-04-on-P14s-gen3-AMD-version/m-p/5227346 To summarize, the only stable configuration I can get is to install lenovo oem kernel on ubuntu 20.04, the latest being 5.14.0-1059-oem. I've tried many kernel, even the 6.4.2 using mainline and none are ok. Hope this helps (and hope this bug will receive more attention, maybe I have not filled it in the correct place?) JF -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2020656 Title: system freeze (cpu fan goes high) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: More than once a day the system totally freeze. CPU fan then goes higher and higher. Does not seem to be related to system load as yesterday it happend during lunch break. Today's journalctl -b -1 last message is mai 24 11:50:06 ThinkPad-P14s kernel: watchdog: BUG: soft lockup - CPU#9 stuck for 167s! [opt ax7ixzwwoey:158586] There are many more of the same kind just before $ lsb_release -rd Description: Ubuntu 22.04.2 LTS Release: 22.04 $ apt-cache policy linux-image-5.19.0-42-generic linux-image-5.19.0-42-generic: Installé : 5.19.0-42.43~22.04.1 Candidat : 5.19.0-42.43~22.04.1 Table de version : *** 5.19.0-42.43~22.04.1 500 500 http://fr.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status Note this problem was present before last kernel updates ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-42-generic 5.19.0-42.43~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 24 12:00:08 2023 InstallationDate: Installed on 2023-03-25 (59 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: TERM=alacritty PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2020656/+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 2025984] Re: Size in crease in modules in 6.2.0-1007
Between 6.2.0-1006-kvm and 6.2.0-1007-kvm the main kernel changed from 6.2.0-23 to 6.2.0-24, but the changes are minimal (only 2 fixes), that seem unrelated to any potential size increase. Maybe there was a toolchain/binutils update? I'll check the binaries to see if I spot something interesting. -- 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/2025984 Title: Size in crease in modules in 6.2.0-1007 Status in linux package in Ubuntu: New Bug description: Hi, we haven't even been able to strip off all the weight we gained with bug 2015867 and now I've found another change eating another ~13mb. This time it might again be all intentional, and maybe even unchangeable. But I'd like to file it so that you can consciously think about it and we can be sure :-) Comparing 6.2.0-1006-kvm to 6.2.0-1007-kvm which is a Lunar SRU AFAICS. I see root@l-old:~# ll /usr/lib/modules/6.2.0-1006-kvm/kernel/net/ipv6 total 368 drwxr-xr-x 3 root root 4096 Jun 21 20:18 ./ drwxr-xr-x 21 root root 4096 Jun 21 20:18 ../ -rw-r--r-- 1 root root 26305 May 31 09:04 ah6.ko -rw-r--r-- 1 root root 119073 May 31 09:04 esp6.ko -rw-r--r-- 1 root root 16889 May 31 09:04 esp6_offload.ko -rw-r--r-- 1 root root 74929 May 31 09:04 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 13409 May 31 09:04 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 21 20:18 netfilter/ -rw-r--r-- 1 root root 54617 May 31 09:04 sit.ko -rw-r--r-- 1 root root 16961 May 31 09:04 tunnel6.ko -rw-r--r-- 1 root root 19449 May 31 09:04 xfrm6_tunnel.ko root@l-new:~# ll /usr/lib/modules/6.2.0-1007-kvm/kernel/net/ipv6 total 752 drwxr-xr-x 3 root root 4096 Jun 28 20:17 ./ drwxr-xr-x 21 root root 4096 Jun 28 20:17 ../ -rw-r--r-- 1 root root 92705 Jun 21 12:50 ah6.ko -rw-r--r-- 1 root root 118881 Jun 21 12:50 esp6.ko -rw-r--r-- 1 root root 83465 Jun 21 12:50 esp6_offload.ko -rw-r--r-- 1 root root 74481 Jun 21 12:50 ip6_udp_tunnel.ko -rw-r--r-- 1 root root 79129 Jun 21 12:50 ipcomp6.ko drwxr-xr-x 2 root root 4096 Jun 28 20:17 netfilter/ -rw-r--r-- 1 root root 123361 Jun 21 12:50 sit.ko -rw-r--r-- 1 root root 81905 Jun 21 12:50 tunnel6.ko -rw-r--r-- 1 root root 84137 Jun 21 12:50 xfrm6_tunnel.ko That is just an example, modules have been growing all over the place. In sum the mentioned ~13mb. But neither did all modules change, nor was it by an equal amount. Here for example sit.ko more than doubled. https://launchpad.net/ubuntu/+source/linux-kvm/6.2.0-1007.7 isn't too obvious either, so I'd appreciate you having a look. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CRDA: N/A CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: minimal CloudID: lxd CloudName: lxd CloudPlatform: lxd CloudSerial: 20230628 CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock) DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Error: [Errno 2] No such file or directory: 'lspci' Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci' Lsusb: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb' Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb' MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) TERM=xterm-256color ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-1007-kvm root=PARTUUID=c4efe7a6-19b9-4886-a813-48bddc64bc45 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 6.2.0-1007.7-kvm 6.2.12 RelatedPackageVersions: linux-restricted-modules-6.2.0-1007-kvm N/A linux-backports-modules-6.2.0-1007-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: cloud-image lunar Uname: Linux 6.2.0-1007-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 2/2/2022 dmi.bios.release: 0.0 dmi.bios.vendor: EDK II dmi.bios.version: unknown dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-8.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-8.0 dmi.modalias: dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd
[Kernel-packages] [Bug 2022361] Re: Please enable Renesas RZ platform serial installer
Applied to mantic/linux-unstable:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/unstable/commit/?id=6f2091e61e72ed73f92cf49d882fb19c50dd860c
Do you think we should SRU this change to lunar kernels (and jammy as
well)?
Thanks!
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: Confirmed
** Changed in: linux (Ubuntu Mantic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2022361
Title:
Please enable Renesas RZ platform serial installer
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Mantic:
Fix Committed
Bug description:
Package: linux
Version: Ubuntu-6.2.0-21.21
Severity: normal
File: /mantic/debian.master/config/annotations
Dear Maintainer,
The ubuntu kernel is missing a few configuration options for Renesas
RZ/G2M MPU as below:
#Modify the following config from m to y.
CONFIG_SERIAL_SH_SCI=y
#add below configuration
CONFIG_SERIAL_SH_SCI_CONSOLE=y
CONFIG_SERIAL_SH_SCI_EARLYCON=y
The above changes are required in annotations file:
"/mantic/debian.master/config/annotations"
code location:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n11372
#Modify the following line (change 'm' to 'y')
CONFIG_SERIAL_SH_SCI policy<{'arm64': 'y', 'armhf': 'y'}>
#Add the following lines:
CONFIG_SERIAL_SH_SCI_CONSOLE policy<{'arm64': 'y', 'armhf': 'y'}>
CONFIG_SERIAL_SH_SCI_EARLYCON policy<{'arm64': 'y', 'armhf': 'y'}>
Could you please add those configuration options to the Ubuntu kernel?
Best Regards
John
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022361/+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 2022361] Re: Please enable Renesas RZ platform serial installer
Hi Andrea
Thank you very much for the update.
>>Do you think we should SRU this change to lunar kernels (and jammy as well)?
Yes, please apply the changes in lunar and jammy as well. Thank you.
Best Regards
John
--
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/2022361
Title:
Please enable Renesas RZ platform serial installer
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
New
Status in linux source package in Jammy:
New
Status in linux source package in Lunar:
New
Status in linux source package in Mantic:
Fix Committed
Bug description:
[Impact]
The ubuntu installer does not work via serial ports for Renesas boards like
RZ/G2M-HiHope
(https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-hihope-rzg2m-reference-board,
RZ/G2L, RZ/G2LC, RZ/G2UL SMARC Board
(https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC).
The installation can be done using HDMI ports, but it would be nice to
support installation via serial port as well.
[Test case]
Try to install Ubuntu on a Renesas board.
[Fix]
Statically build SuperH SCI(F) serial port support (with
earlyconsole).
[Original bug report]
Package: linux
Version: Ubuntu-6.2.0-21.21
Severity: normal
File: /mantic/debian.master/config/annotations
Dear Maintainer,
The ubuntu kernel is missing a few configuration options for Renesas
RZ/G2M MPU as below:
#Modify the following config from m to y.
CONFIG_SERIAL_SH_SCI=y
#add below configuration
CONFIG_SERIAL_SH_SCI_CONSOLE=y
CONFIG_SERIAL_SH_SCI_EARLYCON=y
The above changes are required in annotations file:
"/mantic/debian.master/config/annotations"
code location:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n11372
#Modify the following line (change 'm' to 'y')
CONFIG_SERIAL_SH_SCI policy<{'arm64': 'y', 'armhf': 'y'}>
#Add the following lines:
CONFIG_SERIAL_SH_SCI_CONSOLE policy<{'arm64': 'y', 'armhf': 'y'}>
CONFIG_SERIAL_SH_SCI_EARLYCON policy<{'arm64': 'y', 'armhf': 'y'}>
Could you please add those configuration options to the Ubuntu kernel?
Best Regards
John
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022361/+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 2022361] Re: Please enable Renesas RZ platform serial installer
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Description changed:
+ [Impact]
+
+ The ubuntu installer does not work via serial ports for Renesas boards like
+ RZ/G2M-HiHope
(https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-hihope-rzg2m-reference-board,
RZ/G2L, RZ/G2LC, RZ/G2UL SMARC Board
(https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC).
+
+ The installation can be done using HDMI ports, but it would be nice to
+ support installation via serial port as well.
+
+ [Test case]
+
+ Try to install Ubuntu on a Renesas board.
+
+ [Fix]
+
+ Statically build SuperH SCI(F) serial port support (with earlyconsole).
+
+ [Original bug report]
+
Package: linux
- Version: Ubuntu-6.2.0-21.21
+ Version: Ubuntu-6.2.0-21.21
Severity: normal
File: /mantic/debian.master/config/annotations
Dear Maintainer,
The ubuntu kernel is missing a few configuration options for Renesas
RZ/G2M MPU as below:
#Modify the following config from m to y.
CONFIG_SERIAL_SH_SCI=y
#add below configuration
CONFIG_SERIAL_SH_SCI_CONSOLE=y
CONFIG_SERIAL_SH_SCI_EARLYCON=y
+ The above changes are required in annotations file:
+ "/mantic/debian.master/config/annotations"
- The above changes are required in annotations file:
"/mantic/debian.master/config/annotations"
-
-
- code location:
+ code location:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n11372
#Modify the following line (change 'm' to 'y')
CONFIG_SERIAL_SH_SCI policy<{'arm64': 'y', 'armhf': 'y'}>
#Add the following lines:
CONFIG_SERIAL_SH_SCI_CONSOLE policy<{'arm64': 'y', 'armhf': 'y'}>
CONFIG_SERIAL_SH_SCI_EARLYCON policy<{'arm64': 'y', 'armhf': 'y'}>
-
Could you please add those configuration options to the Ubuntu kernel?
Best Regards
John
--
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/2022361
Title:
Please enable Renesas RZ platform serial installer
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Focal:
New
Status in linux source package in Jammy:
New
Status in linux source package in Lunar:
New
Status in linux source package in Mantic:
Fix Committed
Bug description:
[Impact]
The ubuntu installer does not work via serial ports for Renesas boards like
RZ/G2M-HiHope
(https://www.renesas.com/us/en/products/microcontrollers-microprocessors/rz-mpus/rzg2m-hihope-rzg2m-reference-board,
RZ/G2L, RZ/G2LC, RZ/G2UL SMARC Board
(https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC).
The installation can be done using HDMI ports, but it would be nice to
support installation via serial port as well.
[Test case]
Try to install Ubuntu on a Renesas board.
[Fix]
Statically build SuperH SCI(F) serial port support (with
earlyconsole).
[Original bug report]
Package: linux
Version: Ubuntu-6.2.0-21.21
Severity: normal
File: /mantic/debian.master/config/annotations
Dear Maintainer,
The ubuntu kernel is missing a few configuration options for Renesas
RZ/G2M MPU as below:
#Modify the following config from m to y.
CONFIG_SERIAL_SH_SCI=y
#add below configuration
CONFIG_SERIAL_SH_SCI_CONSOLE=y
CONFIG_SERIAL_SH_SCI_EARLYCON=y
The above changes are required in annotations file:
"/mantic/debian.master/config/annotations"
code location:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/mantic/tree/debian.master/config/annotations#n11372
#Modify the following line (change 'm' to 'y')
CONFIG_SERIAL_SH_SCI policy<{'arm64': 'y', 'armhf': 'y'}>
#Add the following lines:
CONFIG_SERIAL_SH_SCI_CONSOLE policy<{'arm64': 'y', 'armhf': 'y'}>
CONFIG_SERIAL_SH_SCI_EARLYCON policy<{'arm64': 'y', 'armhf': 'y'}>
Could you please add those configuration options to the Ubuntu kernel?
Best Regards
John
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2022361/+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 2009243] Re: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card
Daniel (dkim-b) wrote on 2023-05-31: This will not be a kernel problem, but on another layer. I tested higher kernels up to 6.4 and no change. But since I have nowhere to connect the 5.1 output, I didn't want to do further research. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009243 Title: kernel 5.19.0-35 clobbers Creative S/B AE-7 Sound Card Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: 2023-03-03 Attempted install of kernel 5.19.0-35 using the Linux Mint package installer LM 21.1 Vera, release 21.1). Clobbered my Sound Blaster AE-7. Could not even locate the device using Sound manager utility on Linux Mint Panel (the enumerated device showed up as the embedded sound chip on the mobo which I had previously disabled in the UEFI setup). Uninstalled kernel and reverted back to 5.19.0-32 using Timeshift restore feature which worked fine before the update to 5.19.0-35. Tried again to install 5.19.0-35 the same way, just to be sure. The SB AE-7 got clobbered again. So restored back to 5.19.0-32 generic one more time, using Timeshift. SB AE-7 works fine now with this lower version kernel. Current hardware config: Asus Prime Z790-P wifi mobo. Intel Core i3-13100 processor (with Intel UHD 730 graphics). Corsair Vengeance DDR5 32gb (2x16) ram, 5200Mhz. 3 x Nvme SSD. Boot drive is Western Digital Black SN770 500gb. Asus Nvidia RTX-3050 PCIe graphics card. Creative Labs Sound Blaster AE-7 audio card (PCIe). On-board audio chip (Realtek 7.1 Surround Sound High Definition Audio) is disabled in UEFI. UEFI is AMI/BIOS, revision 0812. Linux Mint 21.1 is running on barebones hardware, no VM involved. No other O/S's are installed on the machine. - Running sudo lspci -vnvn > lspci-vnvn.log gave the following error message... pcilib: sysfs_read_vpd: read failed: No such device --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mikey 4106 F wireplumber /dev/snd/controlC0: mikey 4106 F wireplumber /dev/snd/seq:mikey 4105 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-31 (32 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: ASUS System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-32-generic root=UUID=854c280c-7c5c-494d-a304-db66cf592baf ro quiet splash ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-32-generic N/A linux-backports-modules-5.19.0-32-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: vera Uname: Linux 5.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/24/2023 dmi.bios.release: 8.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0812 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z790-P WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0812:bd02/24/2023:br8.12:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ790-PWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009243/+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 1977827] Re: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm
** Changed in: ubuntu-kernel-tests Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1977827 Title: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm Status in ubuntu-kernel-tests: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: Issue found on Jammy 5.15.0-36.37 with Power9 node baltar Test failed with: # [15] Generic dynamic event - check if duplicate events are caught [FAIL] Test Log: make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' TAP version 13 1..1 # selftests: ftrace: ftracetest # === Ftrace unit tests === # [1] Basic trace file check [PASS] # [2] Basic test for tracers [PASS] # [3] Basic trace clock test [PASS] # [4] Basic event tracing check [PASS] # [5] Change the ringbuffer size [PASS] # [6] Snapshot and tracing setting [PASS] # [7] trace_pipe and trace_marker[PASS] # [8] Test ftrace direct functions against tracers [UNRESOLVED] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] # [10] Generic dynamic event - add/remove eprobe events [PASS] # [11] Generic dynamic event - add/remove kprobe events [PASS] # [12] Generic dynamic event - add/remove synthetic events [PASS] # [13] Generic dynamic event - selective clear (compatibility) [PASS] # [14] Generic dynamic event - generic clear event [PASS] # [15] Generic dynamic event - check if duplicate events are caught [FAIL] # [16] event tracing - enable/disable with event level files [PASS] # [17] event tracing - restricts events based on pid notrace filtering [PASS] # [18] event tracing - restricts events based on pid [PASS] # [19] event tracing - enable/disable with subsystem level files [PASS] # [20] event tracing - enable/disable with top level files [PASS] # [21] Test trace_printk from module [PASS] # [22] ftrace - function graph filters with stack tracer [PASS] # [23] ftrace - function graph filters [PASS] # [24] ftrace - function pid notrace filters [PASS] # [25] ftrace - function pid filters [PASS] # [26] ftrace - stacktrace filter command[PASS] # [27] ftrace - function trace with cpumask [PASS] # [28] ftrace - test for function event triggers [PASS] # [29] ftrace - function trace on module [PASS] # [30] ftrace - function profiling [PASS] # [31] ftrace - function profiler with function tracing [PASS] # [32] ftrace - test reading of set_ftrace_filter[PASS] # [33] ftrace - test for function traceon/off triggers [PASS] # [34] ftrace - test tracing error log support [PASS] # [35] Test creation and deletion of trace instances while setting an event [PASS] # [36] Test creation and deletion of trace instances [PASS] # [37] Kprobe dynamic event - adding and removing[PASS] # [38] Kprobe dynamic event - busy event check [PASS] # [39] Kprobe dynamic event with arguments [PASS] # [40] Kprobe event with comm arguments [PASS] # [41] Kprobe event string type argument [PASS] # [42] Kprobe event symbol argument [PASS] # [43] Kprobe event argument syntax [PASS] # [44] Kprobes event arguments with types[PASS] # [45] Kprobe event user-memory access [UNSUPPORTED] # [46] Kprobe event auto/manual naming [PASS] # [47] Kprobe dynamic event with function tracer [PASS] # [48] Create/delete multiprobe on kprobe event [PASS] # [49] Kprobe event parser error log check [PASS] # [50] Kretprobe dynamic event with arguments[PASS] # [51] Kretprobe dynamic event with maxactive[PASS] # [52] Kretprobe %return suffix test [PASS] # [53] Register/unregister many kprobe events[PASS] # [54] Kprobe profile[PASS] # [55] Uprobe event parser error log check [PASS] # [56] test for the preemptirqsoff tracer[UNSUPPORTED] # [57] Meta-selftest: Checkbashisms [PASS] # [58] Test wakeup tracer[PASS] # [59] Test wakeup RT tracer [PASS] # [60] event trigger - test inter-event histogram trigger expected fail actions [XFAIL] # [61] event trigger - test field variable support [PASS] # [62] event trigger - test multiple actions on hist trigger [PASS] # [63] event trigger - test inter-event histogram trigger onchange action [PASS] # [64] event trigger - test inter-event histogram trigger onmatch action [PASS] # [65] event trigger - test inter-event histogram trigger onmatch-onmax a
[Kernel-packages] [Bug 2025538] Re: Unrequested kernel update
First of all, sorry for the inconvenience. The problem was caused by some missing dependencies which were not yet available in the archive. We are going to look into ways to make the update process more robust. Thank you for reporting the problem. ** Also affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-restricted-modules (Ubuntu) Status: New => Triaged ** Changed in: linux-restricted-modules (Ubuntu) Importance: Undecided => High ** Changed in: linux-restricted-modules (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-restricted-modules package in Ubuntu: Triaged Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2025538/+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 1977827] Re: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm
** Tags removed: verification-needed-kinetic ** Tags added: verification-done-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/1977827 Title: ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm Status in ubuntu-kernel-tests: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Committed Bug description: Issue found on Jammy 5.15.0-36.37 with Power9 node baltar Test failed with: # [15] Generic dynamic event - check if duplicate events are caught [FAIL] Test Log: make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' TAP version 13 1..1 # selftests: ftrace: ftracetest # === Ftrace unit tests === # [1] Basic trace file check [PASS] # [2] Basic test for tracers [PASS] # [3] Basic trace clock test [PASS] # [4] Basic event tracing check [PASS] # [5] Change the ringbuffer size [PASS] # [6] Snapshot and tracing setting [PASS] # [7] trace_pipe and trace_marker[PASS] # [8] Test ftrace direct functions against tracers [UNRESOLVED] # [9] Test ftrace direct functions against kprobes [UNRESOLVED] # [10] Generic dynamic event - add/remove eprobe events [PASS] # [11] Generic dynamic event - add/remove kprobe events [PASS] # [12] Generic dynamic event - add/remove synthetic events [PASS] # [13] Generic dynamic event - selective clear (compatibility) [PASS] # [14] Generic dynamic event - generic clear event [PASS] # [15] Generic dynamic event - check if duplicate events are caught [FAIL] # [16] event tracing - enable/disable with event level files [PASS] # [17] event tracing - restricts events based on pid notrace filtering [PASS] # [18] event tracing - restricts events based on pid [PASS] # [19] event tracing - enable/disable with subsystem level files [PASS] # [20] event tracing - enable/disable with top level files [PASS] # [21] Test trace_printk from module [PASS] # [22] ftrace - function graph filters with stack tracer [PASS] # [23] ftrace - function graph filters [PASS] # [24] ftrace - function pid notrace filters [PASS] # [25] ftrace - function pid filters [PASS] # [26] ftrace - stacktrace filter command[PASS] # [27] ftrace - function trace with cpumask [PASS] # [28] ftrace - test for function event triggers [PASS] # [29] ftrace - function trace on module [PASS] # [30] ftrace - function profiling [PASS] # [31] ftrace - function profiler with function tracing [PASS] # [32] ftrace - test reading of set_ftrace_filter[PASS] # [33] ftrace - test for function traceon/off triggers [PASS] # [34] ftrace - test tracing error log support [PASS] # [35] Test creation and deletion of trace instances while setting an event [PASS] # [36] Test creation and deletion of trace instances [PASS] # [37] Kprobe dynamic event - adding and removing[PASS] # [38] Kprobe dynamic event - busy event check [PASS] # [39] Kprobe dynamic event with arguments [PASS] # [40] Kprobe event with comm arguments [PASS] # [41] Kprobe event string type argument [PASS] # [42] Kprobe event symbol argument [PASS] # [43] Kprobe event argument syntax [PASS] # [44] Kprobes event arguments with types[PASS] # [45] Kprobe event user-memory access [UNSUPPORTED] # [46] Kprobe event auto/manual naming [PASS] # [47] Kprobe dynamic event with function tracer [PASS] # [48] Create/delete multiprobe on kprobe event [PASS] # [49] Kprobe event parser error log check [PASS] # [50] Kretprobe dynamic event with arguments[PASS] # [51] Kretprobe dynamic event with maxactive[PASS] # [52] Kretprobe %return suffix test [PASS] # [53] Register/unregister many kprobe events[PASS] # [54] Kprobe profile[PASS] # [55] Uprobe event parser error log check [PASS] # [56] test for the preemptirqsoff tracer[UNSUPPORTED] # [57] Meta-selftest: Checkbashisms [PASS] # [58] Test wakeup tracer[PASS] # [59] Test wakeup RT tracer [PASS] # [60] event trigger - test inter-event histogram trigger expected fail actions [XFAIL] # [61] event trigger - test field variable support [PASS] # [62] event trigger - test multiple actions on hist trigger [PASS] # [63] event trigger - test inter-event histogram trigger onchange action [PASS] # [64] event trigger - test inter-event histogram trigger onmatch action [PASS] # [65] event trigger - test inter-event histogram trigger o
[Kernel-packages] [Bug 2025353] Re: Add support of AMD Pink Sardine and RPL DMIC
This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu9.1 --- alsa-ucm-conf (1.2.6.3-1ubuntu9.1) lunar; urgency=medium * d/p/0001-acp63-add-initial-support-for-AMD-Pink-Sardine-ACP63.patch d/p/0002-acp63.conf-use-symbolic-link.patch d/p/0003-acp62-add-initial-support-for-AMD-ACP-v6.2-RPL.patch - Backport patches to add support AMD ACP RPL and Pink Sardine. (LP: #2025353) -- Aaron Ma Fri, 30 Jun 2023 10:16:41 +0200 ** Changed in: alsa-ucm-conf (Ubuntu Lunar) Status: Fix Committed => 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/2025353 Title: Add support of AMD Pink Sardine and RPL DMIC Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Released Status in alsa-ucm-conf source package in Mantic: Fix Released Bug description: [Impact] Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD Pink Sardine and RPL DMIC. [Fix] Add support of AMD Pink Sardine and RPL, DMIC and Micmute LED work fine. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025353/+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 2025353] Update Released
The verification of the Stable Release Update for alsa-ucm-conf has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you 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 alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2025353 Title: Add support of AMD Pink Sardine and RPL DMIC Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Released Status in alsa-ucm-conf source package in Mantic: Fix Released Bug description: [Impact] Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD Pink Sardine and RPL DMIC. [Fix] Add support of AMD Pink Sardine and RPL, DMIC and Micmute LED work fine. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025353/+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 2025538] Re: Unrequested kernel update
** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-restricted-modules package in Ubuntu: Triaged Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Triaged Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2025538/+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 2025538] Re: Unrequested kernel update
** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: Triaged => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu) Status: Confirmed => Triaged ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-restricted-modules package in Ubuntu: Triaged Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2025538/+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 2025353] Re: Add support of AMD Pink Sardine and RPL DMIC
This bug was fixed in the package alsa-ucm-conf - 1.2.6.3-1ubuntu1.7 --- alsa-ucm-conf (1.2.6.3-1ubuntu1.7) jammy; urgency=medium * d/p/0001-acp63-add-initial-support-for-AMD-Pink-Sardine-ACP63.patch d/p/0002-acp63.conf-use-symbolic-link.patch d/p/0003-acp62-add-initial-support-for-AMD-ACP-v6.2-RPL.patch - Backport patches to add support AMD ACP RPL and Pink Sardine. (LP: #2025353) -- Aaron Ma Fri, 30 Jun 2023 10:20:31 +0200 ** Changed in: alsa-ucm-conf (Ubuntu Jammy) Status: Fix Committed => 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/2025353 Title: Add support of AMD Pink Sardine and RPL DMIC Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released 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 Lunar: Fix Released Status in alsa-ucm-conf source package in Mantic: Fix Released Bug description: [Impact] Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD Pink Sardine and RPL DMIC. [Fix] Add support of AMD Pink Sardine and RPL, DMIC and Micmute LED work fine. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025353/+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 2012612] Update Released
The verification of the Stable Release Update for dkms 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 dkms in Ubuntu. https://bugs.launchpad.net/bugs/2012612 Title: Add new feature BUILD_EXCLUSIVE_CONFIG to jammy as well Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Jammy: Fix Released Status in dkms source package in Kinetic: Fix Released Bug description: [SRU Justification] Impact: Some dkms modules (like evdi-dkms) have this rule BUILD_EXCLUSIVE_CONFIG which prevent it from building if a specific configuration is enabled/disabled. This feature was released for kinetic but not for jammy. This backports the patch to jammy as well. [racb] This feature is required as the simplest way to deal with some of the HWE DKMS fixes needed in Jammy such as in bug 2012412. Fix: Backported BUILD_EXCLUSIVE_CONFIG.patch from kinetic. In order to be applied, I had to slightly modify the first junk. Other than that, it was a clean backport. [Testcase] $ sudo apt install linux-image-kvm linux-headers-kvm $ sudo apt install evdi-dkms Before the fix, it will fail with this error: DKMS make.log for evdi-1.12.0+dfsg for kernel 5.15.0-1029-kvm (x86_64) Thu Mar 23 10:10:14 UTC 2023 make: Entering directory '/usr/src/linux-headers-5.15.0-1029-kvm' CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_drv.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_dev.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_sysfs.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_modeset.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_connector.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_fb.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_gem.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_painter.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_params.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_cursor.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_debug.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.o /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c: In function ‘evdi_i2c_add’: /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c:49:16: error: implicit declaration of function ‘i2c_add_adapter’; did you mean ‘i2c_verify_adapter’? [-Werror=implicit-function-declaration] 49 | return i2c_add_adapter(adapter); |^~~ |i2c_verify_adapter /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c: In function ‘evdi_i2c_remove’: /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c:54:9: error: implicit declaration of function ‘i2c_del_adapter’; did you mean ‘i2c_verify_adapter’? [-Werror=implicit-function-declaration] 54 | i2c_del_adapter(adapter); | ^~~ | i2c_verify_adapter cc1: some warnings being treated as errors make[1]: *** [scripts/Makefile.build:297: /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.o] Error 1 make: *** [Makefile:1906: /var/lib/dkms/evdi/1.12.0+dfsg/build] Error 2 make: Leaving directory '/usr/src/linux-headers-5.15.0-1029-kvm' This fails because CONFIG_I2C=n for a KVM kernel derivative. Even though evdi has this build rule: BUILD_EXCLUSIVE_CONFIG="CONFIG_I2C CONFIG_DRM" After the fix, it will not build: Building initial module for 5.15.0-1029-kvm Error! The /var/lib/dkms/evdi/1.12.0+dfsg/5.15.0-1029-kvm/x86_64/dkms.conf for module evdi includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. The /var/lib/dkms/evdi/1.12.0+dfsg/5.15.0-1029-kvm/x86_64/dkms.conf for module evdi includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config. This indicates that it should not be built. Skipped. [Regression potential] Very low, this is just a simple feature to prevent building a module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2012612/+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 2012612] Re: Add new feature BUILD_EXCLUSIVE_CONFIG to jammy as well
This bug was fixed in the package dkms - 2.8.7-2ubuntu2.2 --- dkms (2.8.7-2ubuntu2.2) jammy; urgency=medium * Add new feature BUILD_EXCLUSIVE_CONFIG="CONFIG_FOO !CONFIG_BAR". Patch imported from kinetic (LP: #2012612) -- Roxana Nicolescu Thu, 23 Mar 2023 09:47:36 + ** Changed in: dkms (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2012612 Title: Add new feature BUILD_EXCLUSIVE_CONFIG to jammy as well Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Jammy: Fix Released Status in dkms source package in Kinetic: Fix Released Bug description: [SRU Justification] Impact: Some dkms modules (like evdi-dkms) have this rule BUILD_EXCLUSIVE_CONFIG which prevent it from building if a specific configuration is enabled/disabled. This feature was released for kinetic but not for jammy. This backports the patch to jammy as well. [racb] This feature is required as the simplest way to deal with some of the HWE DKMS fixes needed in Jammy such as in bug 2012412. Fix: Backported BUILD_EXCLUSIVE_CONFIG.patch from kinetic. In order to be applied, I had to slightly modify the first junk. Other than that, it was a clean backport. [Testcase] $ sudo apt install linux-image-kvm linux-headers-kvm $ sudo apt install evdi-dkms Before the fix, it will fail with this error: DKMS make.log for evdi-1.12.0+dfsg for kernel 5.15.0-1029-kvm (x86_64) Thu Mar 23 10:10:14 UTC 2023 make: Entering directory '/usr/src/linux-headers-5.15.0-1029-kvm' CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_drv.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_platform_dev.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_sysfs.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_modeset.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_connector.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_encoder.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_drm_drv.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_fb.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_gem.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_painter.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_params.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_cursor.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_debug.o CC [M] /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.o /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c: In function ‘evdi_i2c_add’: /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c:49:16: error: implicit declaration of function ‘i2c_add_adapter’; did you mean ‘i2c_verify_adapter’? [-Werror=implicit-function-declaration] 49 | return i2c_add_adapter(adapter); |^~~ |i2c_verify_adapter /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c: In function ‘evdi_i2c_remove’: /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.c:54:9: error: implicit declaration of function ‘i2c_del_adapter’; did you mean ‘i2c_verify_adapter’? [-Werror=implicit-function-declaration] 54 | i2c_del_adapter(adapter); | ^~~ | i2c_verify_adapter cc1: some warnings being treated as errors make[1]: *** [scripts/Makefile.build:297: /var/lib/dkms/evdi/1.12.0+dfsg/build/evdi_i2c.o] Error 1 make: *** [Makefile:1906: /var/lib/dkms/evdi/1.12.0+dfsg/build] Error 2 make: Leaving directory '/usr/src/linux-headers-5.15.0-1029-kvm' This fails because CONFIG_I2C=n for a KVM kernel derivative. Even though evdi has this build rule: BUILD_EXCLUSIVE_CONFIG="CONFIG_I2C CONFIG_DRM" After the fix, it will not build: Building initial module for 5.15.0-1029-kvm Error! The /var/lib/dkms/evdi/1.12.0+dfsg/5.15.0-1029-kvm/x86_64/dkms.conf for module evdi includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch. The /var/lib/dkms/evdi/1.12.0+dfsg/5.15.0-1029-kvm/x86_64/dkms.conf for module evdi includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config. This indicates that it should not be built. Skipped. [Regression potential] Very low, this is just a simple feature to prevent building a module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2012612/+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 2026725] [NEW] trackpad don't work
Public bug reported: trackpad don't work on my lenovo thinkpad a275 ** 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/2026725 Title: trackpad don't work Status in linux package in Ubuntu: New Bug description: trackpad don't work on my lenovo thinkpad a275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026725/+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 1956177] Re: battery not detected by ACPI
Yesterday i tried linux mint 21.1 on 1.14 bios its still exist Also i talked with fujitsu support and they told me your product not supporting linux and theres no new bios coming I dont know german but they saying 1.12 bios in linux mint doesnt have the bug? -- 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/1956177 Title: battery not detected by ACPI Status in linux package in Ubuntu: Confirmed Bug description: On my freshly installed Fujitsu Lifebook A3510 now running kubuntu 21.10 with kernel 5.13.0-22-generic, there is an issue with the internal battery. When kernel boots up, ACPI isn't able to detect it correctly, see dmesg line: [0.528105] ACPI: battery: Slot [BAT1] (battery absent) But asking lshw for power devices, it says: *-battery description: Lithium Ion Battery product: CP753347-01 vendor: FUJITSU physical id: 1 serial: 02A-Z201219003557Z slot: Internal Battery capacity: 45032mWh configuration: voltage=10,8V I've updated the BIOS to latest version 1.12 already, with no better result. What is the problem here, and how can I fix it? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thomas 945 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-12-31 (4 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK A3510 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=a67d854d-1ecf-4957-9b10-0204e42bbab0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 RelatedPackageVersions: linux-restricted-modules-5.13.0-22-generic N/A linux-backports-modules-5.13.0-22-generic N/A linux-firmware 1.201.3 Tags: impish Uname: Linux 5.13.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/22/2021 dmi.bios.release: 1.12 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 1.12 dmi.board.name: FJNBB6D dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: EQAB073106 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion1.12:bd09/22/2021:br1.12:efr1.9:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKA3510:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNBB6D:rvrEQAB073106:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr:skuSK00: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK A3510 dmi.product.sku: SK00 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+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 2024479] Re: kdump fails on arm64 when offset is not specified
Hi Jo, Thanks for the bug report, sru template, and debdiffs! For Mantic, we currently do not have sponsors that could upload, but I certainly can review the debdiff and give you some feedback/request changes before reaching out to another sponsor/uploader, to hopefully make their life easier. For the Mantic debdiff, it's great, thanks -- just some minor points: 1) the patch file name is 0001-*, and when looking at the tail of the series file, there's already a 0001, and some patches which don't follow a numbered convention? So, my suggestion would be to stick to the 'lpNNN-patch-subject.patch' convention, for the file name. 2.1) Nice touch on the DEP-3 headers! For Origin:, I just would like to suggest the URL be for the 'commit' page vs. a 'patch' page, which improves readability (colors/visual/etc), but note there's no strict requirement on this. 2.2) On Origin: again, if there's any changes for the patch to apply, please use the 'backport' keyword instead of 'upstream' (I didn't check, so it might be fully correct; but noting it just in case). (BTW, I could not review the code changes yet.) Now, on 'finding a sponsor' for Mantic, we can do that for you, or help you with it, in case you'd like to have the exposure/conversation with other people involved in the process. (It's totally fine to pick the former if you're busy or any other reason, this is what we're here for.) Please confirm which path you'd prefer this time. Thanks, Mauricio ** Changed in: kexec-tools (Ubuntu Mantic) Status: In Progress => Incomplete ** Tags added: se-sponsor-mfo ** Description changed: [Description] kdump fails on arm64, on machines with a lot of memory when offeset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel regions. + [Fix] + To address this issue the following upstrem commits are needed: - From the kernel side : - commit a9ae89df737756d92f0e14873339cf393f7f7eb0 - Author: Zhen Lei - Date: Wed Nov 16 20:10:44 2022 +0800 + - From the kernel side: - arm64: kdump: Support crashkernel=X fall back to reserve region above - DMA zones + commit a9ae89df737756d92f0e14873339cf393f7f7eb0 + Author: Zhen Lei + Date: Wed Nov 16 20:10:44 2022 +0800 - commit a149cf00b158e1793a8dd89ca492379c366300d2 - Author: Zhen Lei - Date: Wed Nov 16 20:10:43 2022 +0800 + arm64: kdump: Support crashkernel=X fall back to reserve region + above DMA zones - arm64: kdump: Provide default size when crashkernel=Y,low is not + commit a149cf00b158e1793a8dd89ca492379c366300d2 + Author: Zhen Lei + Date: Wed Nov 16 20:10:43 2022 +0800 + + arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools - commit b5a34a20984c4ad27cc5054d9957af8130b42a50 - Author: Chen Zhou - Date: Mon Jan 10 18:20:08 2022 +0800 + - From kexec-tools: - arm64: support more than one crash kernel regions + commit b5a34a20984c4ad27cc5054d9957af8130b42a50 + Author: Chen Zhou + Date: Mon Jan 10 18:20:08 2022 +0800 + + arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the 5.15 hwe focal kernel will be fixed. [Test] You need a machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump and trigger a crash. It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. [Regression Potential] KERNEL 5.15: To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. KEXEX - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality. Commit cf977b1af9ec67fab adds code w
[Kernel-packages] [Bug 2025095] Re: Jammy update: v5.15.111 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2025095 Title: Jammy update: v5.15.111 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.111 upstream stable release from git://git.kernel.org/ ASOC: Intel: sof_sdw: add quirk for Intel 'Rooks County' NUC M15 ASoC: soc-pcm: fix hw->formats cleared by soc_pcm_hw_init() for dpcm x86/hyperv: Block root partition functionality in a Confidential VM iio: adc: palmas_gpadc: fix NULL dereference on rmmod ASoC: Intel: bytcr_rt5640: Add quirk for the Acer Iconia One 7 B1-750 selftests mount: Fix mount_setattr_test builds failed asm-generic/io.h: suppress endianness warnings for readq() and writeq() x86/cpu: Add model number for Intel Arrow Lake processor wireguard: timers: cast enum limits members to int in prints wifi: mt76: mt7921e: Set memory space enable in PCI_COMMAND if unset arm64: Always load shadow stack pointer directly from the task struct arm64: Stash shadow stack pointer in the task struct on interrupt PCI: pciehp: Fix AB-BA deadlock between reset_lock and device_lock PCI: qcom: Fix the incorrect register usage in v2.7.0 config IMA: allow/fix UML builds USB: dwc3: fix runtime pm imbalance on probe errors USB: dwc3: fix runtime pm imbalance on unbind hwmon: (k10temp) Check range scale when CUR_TEMP register is read-write hwmon: (adt7475) Use device_property APIs when configuring polarity posix-cpu-timers: Implement the missing timer_wait_running callback blk-mq: release crypto keyslot before reporting I/O complete blk-crypto: make blk_crypto_evict_key() return void blk-crypto: make blk_crypto_evict_key() more robust ext4: use ext4_journal_start/stop for fast commit transactions staging: iio: resolver: ads1210: fix config mode tty: Prevent writing chars during tcsetattr TCSADRAIN/FLUSH xhci: fix debugfs register accesses while suspended tick/nohz: Fix cpu_is_hotpluggable() by checking with nohz subsystem MIPS: fw: Allow firmware to pass a empty env ipmi:ssif: Add send_retries increment ipmi: fix SSIF not responding under certain cond. kheaders: Use array declaration instead of char wifi: mt76: add missing locking to protect against concurrent rx/status calls pwm: meson: Fix axg ao mux parents pwm: meson: Fix g12a ao clk81 name soundwire: qcom: correct setting ignore bit on v1.5.1 pinctrl: qcom: lpass-lpi: set output value before enabling output ring-buffer: Sync IRQ works before buffer destruction crypto: api - Demote BUG_ON() in crypto_unregister_alg() to a WARN_ON() crypto: safexcel - Cleanup ring IRQ workqueues on load failure rcu: Avoid stack overflow due to __rcu_irq_enter_check_tick() being kprobe-ed reiserfs: Add security prefix to xattr name in reiserfs_security_write() KVM: nVMX: Emulate NOPs in L2, and PAUSE if it's not intercepted relayfs: fix out-of-bounds access in relay_file_read writeback, cgroup: fix null-ptr-deref write in bdi_split_work_to_wbs ksmbd: call rcu_barrier() in ksmbd_server_exit() ksmbd: fix NULL pointer dereference in smb2_get_info_filesystem() ksmbd: fix memleak in session setup i2c: omap: Fix standard mode false ACK readings riscv: mm: remove redundant parameter of create_fdt_early_page_table tracing: Fix permissions for the buffer_percent file iommu/amd: Fix "Guest Virtual APIC Table Root Pointer" configuration in IRTE ubifs: Fix memleak when insert_old_idx() failed ubi: Fix return value overwrite issue in try_write_vid_and_data() ubifs: Free memory for tmpfile name xfs: don't consider future format versions valid sound/oss/dmasound: fix build when drivers are mixed =y/=m rcu: Fix missing TICK_DEP_MASK_RCU_EXP dependency check selftests/resctrl: Return NULL if malloc_and_init_memory() did not alloc mem selftests/resctrl: Extend CPU vendor detection selftests/resctrl: Move ->setup() call outside of test specific branches selftests/resctrl: Allow ->setup() to return errors selftests/resctrl: Check for return value after write_schemata() selinux: fix Makefile dependencies of flask.h selinux: ensure av_permissions.h is built when needed tpm, tpm_tis: Do not skip reset of original interrupt vector tpm, tpm_tis: Claim locality before writin
[Kernel-packages] [Bug 2025090] Re: Jammy update: v5.15.110 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2025090 Title: Jammy update: v5.15.110 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.110 upstream stable release from git://git.kernel.org/ PCI/ASPM: Remove pcie_aspm_pm_state_change() selftests/kselftest/runner/run_one(): allow running non-executable files KVM: arm64: Retry fault if vma_lookup() results become invalid KVM: arm64: Fix buffer overflow in kvm_arm_set_fw_reg() drm/fb-helper: set x/yres_virtual in drm_fb_helper_check_var bluetooth: Perform careful capability checks in hci_sock_ioctl() USB: serial: option: add UNISOC vendor and TOZED LT70C product driver core: Don't require dynamic_debug for initcall_debug probe timing selftests: mptcp: join: fix "invalid address, ADD_ADDR timeout" riscv: Move early dtb mapping into the fixmap region riscv: Do not set initial_boot_params to the linear address of the dtb riscv: No need to relocate the dtb as it lies in the fixmap region Linux 5.15.110 UBUNTU: Upstream stable to v5.15.110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025090/+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 2024265] Re: Jammy update: v5.15.109 upstream stable release
** Changed in: linux (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024265 Title: Jammy update: v5.15.109 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.109 upstream stable release from git://git.kernel.org/ ARM: dts: rockchip: fix a typo error for rk3288 spdif node arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node arm64: dts: meson-g12-common: specify full DMC range arm64: dts: imx8mm-evk: correct pmic clock source netfilter: br_netfilter: fix recent physdev match breakage regulator: fan53555: Explicitly include bits header regulator: fan53555: Fix wrong TCS_SLEW_MASK virtio_net: bugfix overflow inside xdp_linearize_page() sfc: Split STATE_READY in to STATE_NET_DOWN and STATE_NET_UP. sfc: Fix use-after-free due to selftest_work netfilter: nf_tables: fix ifdef to also consider nf_tables=m i40e: fix accessing vsi->active_filters without holding lock i40e: fix i40e_setup_misc_vector() error handling netfilter: nf_tables: validate catch-all set elements netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements bnxt_en: Do not initialize PTP on older P3/P4 chips mlxfw: fix null-ptr-deref in mlxfw_mfa2_tlv_next() bonding: Fix memory leak when changing bond type to Ethernet net: rpl: fix rpl header size calculation mlxsw: pci: Fix possible crash during initialization spi: spi-rockchip: Fix missing unwind goto in rockchip_sfc_probe() bpf: Fix incorrect verifier pruning due to missing register precision taints e1000e: Disable TSO on i219-LM card to increase speed f2fs: Fix f2fs_truncate_partial_nodes ftrace event Input: i8042 - add quirk for Fujitsu Lifebook A574/H platform/x86 (gigabyte-wmi): Add support for A320M-S2H V2 selftests: sigaltstack: fix -Wuninitialized scsi: megaraid_sas: Fix fw_crash_buffer_show() scsi: core: Improve scsi_vpd_inquiry() checks net: dsa: b53: mmap: add phy ops s390/ptrace: fix PTRACE_GET_LAST_BREAK error handling nvme-tcp: fix a possible UAF when failing to allocate an io queue xen/netback: use same error messages for same errors platform/x86: gigabyte-wmi: add support for X570S AORUS ELITE rtmutex: Add acquire semantics for rtmutex lock acquisition slow path iio: light: tsl2772: fix reading proximity-diodes from device tree nilfs2: initialize unused bytes in segment summary blocks memstick: fix memory leak if card device is never registered kernel/sys.c: fix and improve control flow in __sys_setres[ug]id() mmc: sdhci_am654: Set HIGH_SPEED_ENA for SDR12 and SDR25 drm/i915: Fix fast wake AUX sync len mm/khugepaged: check again on anon uffd-wp during isolation mm: page_alloc: skip regions with hugetlbfs pages when allocating 1G pages sched/uclamp: Fix fits_capacity() check in feec() sched/uclamp: Make cpu_overutilized() use util_fits_cpu() sched/uclamp: Cater for uclamp in find_energy_efficient_cpu()'s early exit condition sched/fair: Detect capacity inversion sched/fair: Consider capacity inversion in util_fits_cpu() sched/uclamp: Fix a uninitialized variable warnings sched/fair: Fixes for capacity inversion detection MIPS: Define RUNTIME_DISCARD_EXIT in LD script docs: futex: Fix kernel-doc references after code split-up preparation purgatory: fix disabling debug info fuse: fix attr version comparison in fuse_read_update_size() fuse: always revalidate rename target dentry fuse: fix deadlock between atomic O_TRUNC and page invalidation udp: Call inet6_destroy_sock() in setsockopt(IPV6_ADDRFORM). tcp/udp: Call inet6_destroy_sock() in IPv6 sk->sk_destruct(). inet6: Remove inet6_destroy_sock() in sk->sk_prot->destroy(). dccp: Call inet6_destroy_sock() via sk->sk_destruct(). sctp: Call inet6_destroy_sock() via sk->sk_destruct(). pwm: meson: Explicitly set .polarity in .get_state() pwm: iqs620a: Explicitly set .polarity in .get_state() pwm: hibvt: Explicitly set .polarity in .get_state() counter: 104-quad-8: Fix race condition between FLAG and CNTR reads iio: adc: at91-sama5d2_adc: fix an error code in at91_adc_allocate_trigger() mm/page_alloc: fix potential deadlock on zonelist_update_seq seqlock ASoC: fsl_asrc_dma: fix potential null-ptr-deref ASN.1: Fix check for
[Kernel-packages] [Bug 2024479] Re: kdump fails on arm64 when offset is not specified
Mauricio is right in all he asks for, except most of them are "style"
which I'd recommend but not insist on.
$ dquilt rename -P 0001-arm64-support-more-than-one-crash-kernel-
regions.patch lp2024479-arm64-support-more-than-one-crash-kernel-
regions.patch
I thought it would be only refreshed, but the patch has an actual backport
change around the position of `fill_property' so it is a backport. But wait, is
it?
No, deeper inspection found this to be noise from the refresh - the function
was the same before and after patch. So we can take the content from upstream
as-is (will do) and keep the origin tag.
(It even pops the same content the old did add which confirms it is the same -
just with other diff context).
Bonus: updating the changelog to say the new filename.
With that in place, all is looking good.
I miss a PPA build here to be extra sure, but that issue (if any) would then be
on @joalif to resolve if breaking.
Uploaded to Mantic:
$ dput ubuntu ../kexec-tools_2.0.22-2ubuntu4_source.changes
Uploading kexec-tools using ftp to ubuntu (host: upload.ubuntu.com; directory:
/ubuntu)
running ppaforppaonly: Stop uploads to the archive with or to ppa without ~ppa
suffix.
running gitubuntu: Warn if uploading without git-ubuntu Vcs-* entries.
running gpg: check GnuPG signatures before the upload
running releasemismatch: Warn about mismatching suffixesg e.g. focal with a
XX.YY not being 20.04
running updatemaintainer: Stop if ubuntu changes are without ubuntu maintainer.
running suite-mismatch: check the target distribution for common errors
running badauthor: Stop if uploading with root@ or ubuntu@ email adresses.
running required-fields: check whether a field is present and non-empty in the
changes file
running checksum: verify checksums before uploading
running nobug: Stop if uploading without any bug reference.
running check-debs: makes sure the upload contains a binary package
running supported-distribution: check whether the target distribution is
currently supported (using distro-info)
{'allowed': ['release', 'proposed', 'backports', 'security'], 'known':
['release', 'proposed', 'updates', 'backports', 'security']}
running placeholderbug: Stop if using common placeholder numbers as bug
reference.
Uploading kexec-tools_2.0.22-2ubuntu4.dsc
Uploading kexec-tools_2.0.22-2ubuntu4.debian.tar.xz
Uploading kexec-tools_2.0.22-2ubuntu4_source.buildinfo
Uploading kexec-tools_2.0.22-2ubuntu4_source.changes
** Changed in: kexec-tools (Ubuntu Mantic)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2024479
Title:
kdump fails on arm64 when offset is not specified
Status in kexec-tools package in Ubuntu:
Fix Committed
Status in linux package in Ubuntu:
Incomplete
Status in kexec-tools source package in Focal:
In Progress
Status in linux source package in Focal:
Won't Fix
Status in kexec-tools source package in Jammy:
In Progress
Status in linux source package in Jammy:
Incomplete
Status in kexec-tools source package in Kinetic:
Won't Fix
Status in linux source package in Kinetic:
Won't Fix
Status in kexec-tools source package in Lunar:
In Progress
Status in kexec-tools source package in Mantic:
Fix Committed
Bug description:
[Description]
kdump fails on arm64, on machines with a lot of memory when offeset is not
specified,
e.g when /etc/default/grub.d/kdump-tools.cfg looks like:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G"
If kdump-tools.cfg specifies the offset e.g.:
GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G"
it works ok.
The reason for this is that the kernel needs to allocate memory for the
crashkernel both
in low and high memory.
This is addressed in kernel 6.2.
In addition kexec-tools needs to support more than one crash kernel regions.
[Fix]
To address this issue the following upstrem commits are needed:
- From the kernel side:
commit a9ae89df737756d92f0e14873339cf393f7f7eb0
Author: Zhen Lei
Date: Wed Nov 16 20:10:44 2022 +0800
arm64: kdump: Support crashkernel=X fall back to reserve region
above DMA zones
commit a149cf00b158e1793a8dd89ca492379c366300d2
Author: Zhen Lei
Date: Wed Nov 16 20:10:43 2022 +0800
arm64: kdump: Provide default size when crashkernel=Y,low is not
specified
- From kexec-tools:
commit b5a34a20984c4ad27cc5054d9957af8130b42a50
Author: Chen Zhou
Date: Mon Jan 10 18:20:08 2022 +0800
arm64: support more than one crash kernel regions
Affected releases:
Jammy, Focal, Bionic
For Bionic we won't fix it as we need to backport a lot of code and the
regression potential is too high.
The same applies for the Focal 5.4 kernel.
Only the 5.15 hwe focal kernel will be fixed.
[Test]
You need a machine (can be a VM
[Kernel-packages] [Bug 2026736] [NEW] Azure: Fix lockup in swiotlb when used as a CVM
Public bug reported: SRU Justification [Impact] Azxure CVM instances can lock up when run under stress. [Test Plan] MSFT tested using the nttcp test. [Regression potential] CVM instances could continue to lock up under stress. [Other info] SF: #00363432 ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Lunar) Importance: High Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => High ** Changed in: linux (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/2026736 Title: Azure: Fix lockup in swiotlb when used as a CVM Status in linux package in Ubuntu: Fix Released Status in linux source package in Lunar: In Progress Bug description: SRU Justification [Impact] Azxure CVM instances can lock up when run under stress. [Test Plan] MSFT tested using the nttcp test. [Regression potential] CVM instances could continue to lock up under stress. [Other info] SF: #00363432 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026736/+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 2024479] Re: kdump fails on arm64 when offset is not specified
Hey Christian, thanks for the quick review and sponsorship. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on arm64 when offset is not specified Status in kexec-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Incomplete Status in kexec-tools source package in Focal: In Progress Status in linux source package in Focal: Won't Fix Status in kexec-tools source package in Jammy: In Progress Status in linux source package in Jammy: Incomplete Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in kexec-tools source package in Lunar: In Progress Status in kexec-tools source package in Mantic: Fix Committed Bug description: [Description] kdump fails on arm64, on machines with a lot of memory when offeset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel regions. [Fix] To address this issue the following upstrem commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the 5.15 hwe focal kernel will be fixed. [Test] You need a machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump and trigger a crash. It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. [Regression Potential] KERNEL 5.15: To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. KEXEX - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality. Commit cf977b1af9ec67fab adds code without altering current functionality. Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features. KEXEC - JAMMY, LUNAR, MANTIC: Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that teh reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump. [Other] Commits to backport - MANTIC: kernel 6.3: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - LUNAR: kernel 6.2: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - KINETIC: WON'T FIX Kinetic won't be fixed as it EOLs soon. - JAMMY: kernel (5.15 kernel): a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified 4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel() 8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: kdump: Do not alloc
[Kernel-packages] [Bug 2024479] Re: kdump fails on arm64 when offset is not specified
@cpaelzer and @mfo thank both of your reviewing and sponsoring. @cpaelzer yes, if anything break, it's on me. Here's the PPA with the builds: https://launchpad.net/~canonical-support-eng/+archive/ubuntu/sf361158 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on arm64 when offset is not specified Status in kexec-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Incomplete Status in kexec-tools source package in Focal: In Progress Status in linux source package in Focal: Won't Fix Status in kexec-tools source package in Jammy: In Progress Status in linux source package in Jammy: Incomplete Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in kexec-tools source package in Lunar: In Progress Status in kexec-tools source package in Mantic: Fix Committed Bug description: [Description] kdump fails on arm64, on machines with a lot of memory when offeset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel regions. [Fix] To address this issue the following upstrem commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the 5.15 hwe focal kernel will be fixed. [Test] You need a machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump and trigger a crash. It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. [Regression Potential] KERNEL 5.15: To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. KEXEX - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality. Commit cf977b1af9ec67fab adds code without altering current functionality. Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features. KEXEC - JAMMY, LUNAR, MANTIC: Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that teh reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump. [Other] Commits to backport - MANTIC: kernel 6.3: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - LUNAR: kernel 6.2: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - KINETIC: WON'T FIX Kinetic won't be fixed as it EOLs soon. - JAMMY: kernel (5.15 kernel): a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified 4890cc1
[Kernel-packages] [Bug 2021572] Re: dGPU cannot resume because system firmware stuck in IPCS method
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2021572 Title: dGPU cannot resume because system firmware stuck in IPCS method Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [Impact] When a dGPU on a laptop is in PCIe D3cold and TBT port is connected to a monitor via a cable, unplugging the cable will make the dGPU unable to resume to D0. [Fix] There's a part of system firmware, IOM, need the driver to disconnect all TBT/Type-C phy to let dGPU function normally. [Test] With the fix applied, the dGPU continues to work after replugging video cable many times. [Where problems could occur] The fix is composed of several overhaul, so it's likely to regression i915 GFX driver. To limit the impact, only target OEM kernel for now. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2021572/+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 2024479] Re: kdump fails on arm64 when offset is not specified
** Changed in: linux (Ubuntu Jammy) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on arm64 when offset is not specified Status in kexec-tools package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Incomplete Status in kexec-tools source package in Focal: In Progress Status in linux source package in Focal: Won't Fix Status in kexec-tools source package in Jammy: In Progress Status in linux source package in Jammy: In Progress Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in kexec-tools source package in Lunar: In Progress Status in kexec-tools source package in Mantic: Fix Committed Bug description: [Description] kdump fails on arm64, on machines with a lot of memory when offeset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel regions. [Fix] To address this issue the following upstrem commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the 5.15 hwe focal kernel will be fixed. [Test] You need a machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump and trigger a crash. It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. [Regression Potential] KERNEL 5.15: To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. KEXEX - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality. Commit cf977b1af9ec67fab adds code without altering current functionality. Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features. KEXEC - JAMMY, LUNAR, MANTIC: Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that teh reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump. [Other] Commits to backport - MANTIC: kernel 6.3: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - LUNAR: kernel 6.2: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - KINETIC: WON'T FIX Kinetic won't be fixed as it EOLs soon. - JAMMY: kernel (5.15 kernel): a9ae89df737756d92f0e14873339cf393f7f7eb0 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones a149cf00b158e1793a8dd89ca492379c366300d2 arm64: kdump: Provide default size when crashkernel=Y,low is not specified 4890cc18f94979b406f95708f8cb238eb2d0e5a9 arm64/mm: Define defer_reserve_crashkernel() 8f0f104e2ab6eed4cad3b111dc206f843bda43ea arm64: k
[Kernel-packages] [Bug 2024479] Re: kdump fails on arm64 when offset is not specified
This bug was fixed in the package kexec-tools - 1:2.0.22-2ubuntu4 --- kexec-tools (1:2.0.22-2ubuntu4) mantic; urgency=medium * Support more than one crash kernel regions for arm64 (LP: #2024479) - d/p/lp2024479-arm64-support-more-than-one-crash-kernel-regions.patch -- Ioanna Alifieraki Mon, 03 Jul 2023 15:18:56 +0300 ** Changed in: kexec-tools (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/2024479 Title: kdump fails on arm64 when offset is not specified Status in kexec-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in kexec-tools source package in Focal: In Progress Status in linux source package in Focal: Won't Fix Status in kexec-tools source package in Jammy: In Progress Status in linux source package in Jammy: In Progress Status in kexec-tools source package in Kinetic: Won't Fix Status in linux source package in Kinetic: Won't Fix Status in kexec-tools source package in Lunar: In Progress Status in kexec-tools source package in Mantic: Fix Released Bug description: [Description] kdump fails on arm64, on machines with a lot of memory when offeset is not specified, e.g when /etc/default/grub.d/kdump-tools.cfg looks like: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G" If kdump-tools.cfg specifies the offset e.g.: GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=4G@4G" it works ok. The reason for this is that the kernel needs to allocate memory for the crashkernel both in low and high memory. This is addressed in kernel 6.2. In addition kexec-tools needs to support more than one crash kernel regions. [Fix] To address this issue the following upstrem commits are needed: - From the kernel side: commit a9ae89df737756d92f0e14873339cf393f7f7eb0 Author: Zhen Lei Date: Wed Nov 16 20:10:44 2022 +0800 arm64: kdump: Support crashkernel=X fall back to reserve region above DMA zones commit a149cf00b158e1793a8dd89ca492379c366300d2 Author: Zhen Lei Date: Wed Nov 16 20:10:43 2022 +0800 arm64: kdump: Provide default size when crashkernel=Y,low is not specified - From kexec-tools: commit b5a34a20984c4ad27cc5054d9957af8130b42a50 Author: Chen Zhou Date: Mon Jan 10 18:20:08 2022 +0800 arm64: support more than one crash kernel regions Affected releases: Jammy, Focal, Bionic For Bionic we won't fix it as we need to backport a lot of code and the regression potential is too high. The same applies for the Focal 5.4 kernel. Only the 5.15 hwe focal kernel will be fixed. [Test] You need a machine (can be a VM too) with large memory e.g. 128G. Install linux-crashdump and trigger a crash. It won't work unless the offset is specified because the memory crashkernel cannot be allocated. With the patches applied it works as expected without having to specify the offset. [Regression Potential] KERNEL 5.15: To address this problem in the 5.15 kernel we need to pull in 7 commits (see [Other] section for details. All the commits are changing code only for arm64 architecture and only the code related to reserving the crashkernel. This means that any regression potential will affect only the arm64 architecture and in particular the crash/kdump functionality. However, since the reservation of the crashkernel occurs at boot up, potentially things could go wrong there as well. KEXEX - FOCAL: To fix the kexec_tools in focal we need to pull in 6 commits (see [Other section for details]). They all cherry pick. Four out of six commits touch only arm64 code. Any regression potential because of these commits would regard either crashdump or kexec functionality. Commit cf977b1af9ec67fab adds code without altering current functionality. Commit f4ce0706d9574aecb7 adds functionality to read elf notes. In practive it moves the code from vmcore-dmesg.c to elf_info.c so it can be used by other features. KEXEC - JAMMY, LUNAR, MANTIC: Commit b5a34a20984c is pulled in, it cherry-picks. It changes only arm64 code. It enables kexec to recognise that teh reserved kernel may use more than one kernel region. Things could go worng when gatherinng a crashdump. [Other] Commits to backport - MANTIC: kernel 6.3: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - LUNAR: kernel 6.2: not affected kexec-tools: b5a34a20984c4ad27cc5054d9957af8130b42a50 arm64: support more than one crash kernel regions - KINETIC: WON'T FIX Kinetic won't be fixed as it EOLs soon. - JAMMY: kernel (5.15 kernel): a9ae89df737756d92f0e14873339cf393f7f7eb0
[Kernel-packages] [Bug 2023577] Re: cls_flower: off-by-one in fl_set_geneve_opt
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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 removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2023577 Title: cls_flower: off-by-one in fl_set_geneve_opt Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] An unprivileged user may cause an out-of-bounds write by setting up geneve options on the flower classifier. [Test case] https://seclists.org/oss-sec/2023/q2/219 [Potential regression] Users setting up geneve options on the flower tc classifier can be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023577/+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 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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 removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023220 Title: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Trusty: Incomplete Status in linux-oem-6.1 source package in Trusty: Invalid Status in linux source package in Xenial: Incomplete Status in linux-oem-6.1 source package in Xenial: Invalid Status in linux source package in Bionic: Incomplete Status in linux-oem-6.1 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.1 source package in Focal: Invalid Status in linux 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.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush the global TLB entries. This can lead to info leak or undefined behavior. [Mitigation] Boot with nopcid on affected systems. [Test case] There is no particular test case. [Potential regressions] This affects performance on the affected systems. TLB behavior could also be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023220/+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 2020531] Re: support python < 3.9 with annotations
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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 removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2020531 Title: support python < 3.9 with annotations Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Released Bug description: [Impact] At the moment we can't use the annotations scripts in focal, because we are using the'|=' update operator for merging dicts, that has been introduced with python 3.9. Rewrite the code that is using this operator in a more portable way and apply this change everywhere, so that annotations will work on any backport/derivative kernels. [Test case] Run `fakeroot debian/rules updateconfigs` in focal (using the new annotations model). [Fix] Try to use the '|=' operator in a try/except block, if it fails fallback to a more portable way. [Regression potential] With this change applied we may experience regressions during the updateconfigs phase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020531/+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 2020413] Re: fix typo in config-checks invocation
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2020413 Title: fix typo in config-checks invocation Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux-kvm source package in Jammy: Fix Released Bug description: [Impact] After migrating to the new annotations-only model in jammy we introduced a typo in debian/rules.d/4-checks.mk, that is triggered if we opt to not migrate to the new model and still use the old configs+annotations. [Test case] With debian./config/config.common.ubuntu present run the following command: $ fakeroot debian/rules clean updateconfigs [Fix] Replace @perl -> perl. [Regression potential] It's a trivial typo fix. Regressions can be introduced only if we are still using the old configs+annotations model. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020413/+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 2019131] Re: Add PPIN support for Intel EMR cpu
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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 removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2019131 Title: Add PPIN support for Intel EMR cpu Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Intel has introduced support for their new Emerald Rapids CPU. It was backported to Jammy in #lp2015372 and in #lp2015855. The remaining feature needed to fully support EMR is PPIN (the Protected Processor Inventory/Identification Number). This was recently pushed to upstream in 6.4 in commit 36168bc061b4368ad19e82b06a6463c95d3bb9a7. The change is very straightforward, it adds a new entry for EMERALDRAPIDS_X in the cpuids table where cpus that support ppin are listed. The table is then used in `ppin_init`. In Jammy, this implementation is missing. Both Amd and Intel have their own implementation which is doing pretty much the same. Instead of a list of cpus supported, a switch case is used instead in their init functions (amd_detect_ppin and intel_ppin_init). To reduce duplication of code and to help backport smoothly the new addition of EMR, commit 0dcab41d3487acadf64d0667398e032341bd9918 “x86/cpu: Merge Intel and AMD ppin_init() functions” was backported too. Thus commits: - 0dcab41d3487acadf64d0667398e032341bd9918: "x86/cpu: Merge Intel and AMD ppin_init() functions" - 36168bc061b4368ad19e82b06a6463c95d3bb9a7: "x86/cpu: Add Xeon Emerald Rapids to list of CPUs that support PPIN" are needed to support PPIN for EMR. [Testing] Kernel was built on cbd and boot tested on a VM. [Regression potential] Very low, it is a small refactor that removes duplication and it should not affect the functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019131/+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 2016269] Re: conntrack mark is not advertised via netlink
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1015.15 kernel in -proposed solves the problem. Please test
the kernel and update this bug with the results. If the problem is
solved, change the tag 'verification-needed-jammy' to 'verification-
done-jammy'. If the problem still exists, change the tag 'verification-
needed-jammy' to 'verification-failed-jammy'.
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 removed: verification-done-jammy
** Tags added: kernel-spammed-jammy-linux-nvidia-tegra verification-needed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2016269
Title:
conntrack mark is not advertised via netlink
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Status in linux source package in Kinetic:
Fix Released
Bug description:
SRU justification sent to ML:
[Impact]
There was a commit 95fcb42e5f20
("netfilter: ctnetlink: fix compilation warning after data race fixes in ct
mark")
that introduces a regression where the "mark" variable is no longer
dumped in netlink netfilter conntrack messages, which userspace tools use
to mark and track connections.
[Fix]
Introduce the upstream fix 9f7dd42f0db1
("netfilter: ctnetlink: revert to dumping mark regardless of event type")
that always dumps the 'mark' variable for conntrack entries.
This fix has also landed in 5.15 upstream stable.
[Test]
Run 'conntrack -E' and check the output of connection entries.
The 'mark' variable should now be present in connection entries after
the fix.
before fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
after fix:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789 dport=12345
src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] mark=0 use=1
[Where problems could occur]
The fixes are pretty straight forward so regression potential should be
minimal.
[Impact]
The last merge of the v5.15 stable (see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003134) has
introduced a bug on netlink netfilter conntrack messages.
The problematic commit is 95fcb42e5f20 ("netfilter: ctnetlink: fix
compilation warning after data race fixes in ct mark"):
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/?id=95fcb42e5f20
This bug has been fixed in upstream commit 9f7dd42f0db1 ("netfilter:
ctnetlink: revert to dumping mark regardless of event type"):
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9f7dd42f0db1
which has been backported in v5.15.103:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bef8cf77e21c
[Test Case]
Run 'conntrack -E' and check the output.
Before the problematic commit:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED]
mark=0 use=1
'mark=' is seen on connrtack event
after:
> tcp 6 2 ESTABLISHED src=10.100.0.1 dst=10.200.0.1 sport=6789
dport=12345 src=10.200.0.1 dst=10.100.0.1 sport=12345 dport=6789 [ASSURED] use=1
=> 'mark=' is not seen.
[Regression Potential]
The patch is quite simple. It has been backported in the official 5.15
stable. The risk of regression should be contained.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016269/+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 2008527] Re: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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-jammy-linux-nvidia-tegra -- 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/2008527 Title: [SRU]With "Performance per Watt (DAPC)" enabled in the BIOS, Bootup time is taking longer than expected Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification: [Impact] A Dell system that has a profile setting of "Performance Per Watt (DAPC)" enabled in the BIOS and running Ubuntu-22.04 does not boot into OS as quickly as expected. How reproducible: Steps to Reproduce: 1. On the Dell system enable "Performance Per Watt (DAPC)" from BIOS. 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time Expected results: OS should boot normally and need to consume less bootup time [Fix] 13fdbc8b8da6 cpufreq: ACPI: Defer setting boost MSRs [Test Plan] 1. Set system profile as "Performance Per Watt (DAPC)" from BIOS setting 2. Install Ubuntu-22.04 3. Boot into OS 4. Check the bootup time [Where problems could occur] Regression risk: low to medium. [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008527_dapc Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008527_dapc_kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008527/+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 2019000] Re: Use new annotations model
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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-jammy-linux-nvidia-tegra -- 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/2019000 Title: Use new annotations model Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Triaged Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Confirmed Bug description: [Impact] Starting with lunar we have introduced a new way to manage kernel configs, unifying the duplicated information defined in the annotations file + config chunks into an annotations-only model. [Test case] A kernel build can be considered a valid test case, in particular the specific command that is used to update the .config's for all the supported architectures and flavours: $ fakeroot debian/rules updateconfigs [Fix] Import the required changes in debian/ from lunar (with the required adjustments) to support the annotations-only model also in all the previous releases. [Regression potential] We may experience regressions during the updateconfigs step, especially with derivatives. Moreover, derivatives that want to transition to the new annotations model require to adjust the header in the annotations file as following (make sure to define the corresponding architectures and flavours): # FORMAT: 4 # ARCH: amd64 arm64 armhf ppc64el s390x # FLAVOUR: amd64-generic amd64-lowlatency arm64-generic arm64-generic-64k arm64-lowlatency arm64-lowlatency-64k armhf-generic armhf-generic-lpae ppc64el-generic s390x-generic After adjusting the header a special command is provided to transition to the new annotations-only model: $ fakeroot debian/rules migrateconfigs This command should automatically import the old configs into the new annotations file. A kernel with this change applied can still support the old annotations+configs model, the transition to the new model is not mandatory. Basically without using `fakeroot debian/rules migrateconfigs` the updateconfigs step will continue to use the old model and the old scripts (that is the safest approach to avoid potential unexpected .config changes). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019000/+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 2015972] Re: Dell: Enable speaker mute hotkey LED indicator
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2015972 Title: Dell: Enable speaker mute hotkey LED indicator Status in HWE Next: New Status in OEM Priority Project: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in alsa-ucm-conf source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in alsa-ucm-conf source package in Kinetic: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in alsa-ucm-conf source package in Lunar: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Feature Description] When users press the speaker mute hotkey and the speaker is muted, the speaker mute LED indicator will light up. When the speaker is not muted, the speaker mute LED indicator will light out. [Test Case] 1. run G16 with target kernel. 2. press the mute hotkey 3. check if speaker mute led can be switched. [Where problems could occur] Low, just register a speaker mute led control for dell-laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2015972/+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 2008751] Re: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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 removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008751 Title: [SRU] Backport request for hpwdt from upstream 6.1 to Jammy Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification: [Impact] Please pick up the latest hpwdt from the upstream 6.1 kernel for Jammy. This version enables hpwdt on RL300 aarch64. [Fix] ed835d8171fc watchdog/hpwdt: Include nmi.h only if CONFIG_HPWDT_NMI_DECODING 891862d5ba11 watchdog/hpwdt: Enable HP_WATCHDOG for ARM64 systems. [Test Plan] Boot system with the hpwdt enabled on an arm64 system [Where Problems Could Occur] Regression Risk is Low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008751_hpwdt_1 Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008751_hpwdt_kinetic_1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008751/+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 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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 removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [Test Plan] The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/smartpqi_2204_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : ke
[Kernel-packages] [Bug 2012335] Re: Ubuntu 22.04 raise abnormal NIC MSI-X requests with larger CPU cores (256)
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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-jammy-linux-nvidia-tegra -- 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/2012335 Title: Ubuntu 22.04 raise abnormal NIC MSI-X requests with larger CPU cores (256) Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: SRU Justification: [Impact] There is a user reporting errors in setup with their Intel E810 NIC with error messages saying that the driver cannot allocate enough MSI-X vectors on their 256 cpu-count system. It seems the ICE ethernet driver has an all or nothing approach to allocating MSI-X vectors and could request more MSI-X vectors than it finds available, which could lead to the driver failing to initialize and start. [Fix] The patch that fixes this allocates as many MSI-X vectors as it can to continue functionality by reducing the number of requested MSI-X vectors if it does not have enough to do full allocation. [Backport] In Jammy we do not carry patches for switchdev support in the driver so do not allocate the switchdev MSI-X vector for it. Also in Jammy use the older way of checking RDMA support by testing the RDMA bit is set as opposed to the newer ice_is_rdma_ena that the patch uses. [Test Plan] Install and startup Ice driver with an Intel 800 series NIC and check that we do not have the failure: Not enough device MSI-X vectors, requested = 260, available = 253 and check that everything works as expected. The backported patch for Jammy has been tested by the original user who submited the bug report with their high cpu count system and confirmed no errors. [Where problems could occur] There could be problems with the logic of reducing the MSI-X vector usage leading to more errors in the driver, but otherwise minimal regression potential as the code is mostly refactoring initial MSI-X setup. -- System Configuration OS: Ubuntu 22.04 LTS Kernel: 5.15.0-25-generic CPUs: 256 NIC: Intel E810 NIC with 512 MSIx vectors each function Errors Not enough device MSI-X vectors, requested = 260, available = 253 Findings (1) the current ice kernel driver (ice_main.c) will pre-allocate all required number of msix (even it's not enough for big core CPUs) (2) the commit https://github.com/torvalds/linux/commit/ce4626131112e1d0066a890371e14d8091323f99 has improved this logic, and it seems merged into kernel version from v6.1 So for supporting the new CPUs with more than 252 vCPUs, will Ubuntu kernel backport above patch to the current kernel (v5.15) ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012335/+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 2007745] Re: [SRU][Jammy] CONFIG_PCI_MESON is not enabled
This bug is awaiting verification that the linux-nvidia- tegra/5.15.0-1015.15 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification- done-jammy'. If the problem still exists, change the tag 'verification- needed-jammy' to 'verification-failed-jammy'. 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 removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-nvidia-tegra verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007745 Title: [SRU][Jammy] CONFIG_PCI_MESON is not enabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: SRU justification: [ Impact ] The PCI driver for the amlogic-based Meson platforms (CONFIG_PCI_MESON) is not enabled as a module in the kernel configuration: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/focal/tree/debian.master/config/config.common.ubuntu?h=master#n7036 [ Test Plan ] Check if pci_meson.ko is compiled and present in the linux-modules package. [ Where problems could occur ] * Enabling the driver could enable undesired dependencies * Kernel module does not compile and breaks the build [ Other Info ] This driver is important for systems like the ODROID HC4, which uses a PCIE-SATA bridge to provide a storage interface. This system is fully supported by the kernel (including a device tree), except for the fact that this PCI driver is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007745/+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 2026776] [NEW] arm64+ast2600: No Output from BMC's VGA port
Public bug reported: Hello, On systems that have the following combination of hardware...: 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ .. we see no output when connecting a display to the BMC's VGA port. Upon further investigation, we see that applying the following patch fixes this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6&id=4327a6137ed43a091d900b1ac833345d60f32228 Would it be possible to apply this patch to affected kernels? Using the aforementioned combination, the ast driver is broken without this patch. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Project changed: snap-octavia-diskimage-retrofit => linux ** Project changed: linux => 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/2026776 Title: arm64+ast2600: No Output from BMC's VGA port Status in linux package in Ubuntu: New Bug description: Hello, On systems that have the following combination of hardware...: 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ .. we see no output when connecting a display to the BMC's VGA port. Upon further investigation, we see that applying the following patch fixes this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6&id=4327a6137ed43a091d900b1ac833345d60f32228 Would it be possible to apply this patch to affected kernels? Using the aforementioned combination, the ast driver is broken without this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026776/+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 2026625] Re: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess r
** Tags removed: need-duplicate-check -- 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/2026625 Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: Occurred during installation ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown Date: Sat Jul 8 12:13:10 2023 ErrorMessage: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 MachineType: Alienware Alienware Aurora Ryzen Edition ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=b6810121-855e-41ef-a565-e89e88e0b75f ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.2, unpackaged RelatedPackageVersions: grub-pc 2.06-2ubuntu16 SourcePackage: linux Title: package linux-headers-6.2.0-24-generic 6.2.0-24.24 failed to install/upgrade: installed linux-headers-6.2.0-24-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to lunar on 2023-05-09 (60 days ago) dmi.bios.date: 01/13/2023 dmi.bios.release: 2.4 dmi.bios.vendor: Alienware dmi.bios.version: 2.4.0 dmi.board.name: 0NWN7M dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr2.4.0:bd01/13/2023:br2.4:svnAlienware:pnAlienwareAuroraRyzenEdition:pvr2.4.0:rvnAlienware:rn0NWN7M:rvrA00:cvnAlienware:ct3:cvrNotSpecified:sku098E: dmi.product.family: Alienware dmi.product.name: Alienware Aurora Ryzen Edition dmi.product.sku: 098E dmi.product.version: 2.4.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026625/+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 2026776] Re: arm64+ast2600: No Output from BMC's VGA port
** Also affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Description changed: Hello, On systems that have the following combination of hardware...: 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ .. we see no output when connecting a display to the BMC's VGA port. Upon further investigation, we see that applying the following patch fixes this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6&id=4327a6137ed43a091d900b1ac833345d60f32228 Would it be possible to apply this patch to affected kernels? Using the aforementioned combination, the ast driver is broken without this patch. + + https://github.com/NVIDIA-BaseOS-6/linux-nvidia-5.19/commit/055c9ec3739d7df1179db3ba054b00f3dd684560 + https://github.com/NVIDIA-BaseOS-6/linux-nvidia-6.2/commit/8ab3253c6a59eee3424fe0c60b1fc6dc9f2d73b7 ** Description changed: Hello, On systems that have the following combination of hardware...: 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ .. we see no output when connecting a display to the BMC's VGA port. Upon further investigation, we see that applying the following patch fixes this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6&id=4327a6137ed43a091d900b1ac833345d60f32228 - Would it be possible to apply this patch to affected kernels? Using the - aforementioned combination, the ast driver is broken without this patch. + [Action] https://github.com/NVIDIA-BaseOS-6/linux-nvidia-5.19/commit/055c9ec3739d7df1179db3ba054b00f3dd684560 https://github.com/NVIDIA-BaseOS-6/linux-nvidia-6.2/commit/8ab3253c6a59eee3424fe0c60b1fc6dc9f2d73b7 ** Description changed: - Hello, + [Issue] On systems that have the following combination of hardware...: 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ .. we see no output when connecting a display to the BMC's VGA port. Upon further investigation, we see that applying the following patch fixes this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6&id=4327a6137ed43a091d900b1ac833345d60f32228 [Action] https://github.com/NVIDIA-BaseOS-6/linux-nvidia-5.19/commit/055c9ec3739d7df1179db3ba054b00f3dd684560 https://github.com/NVIDIA-BaseOS-6/linux-nvidia-6.2/commit/8ab3253c6a59eee3424fe0c60b1fc6dc9f2d73b7 ** Description changed: [Issue] On systems that have the following combination of hardware...: 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ .. we see no output when connecting a display to the BMC's VGA port. Upon further investigation, we see that applying the following patch fixes this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6&id=4327a6137ed43a091d900b1ac833345d60f32228 [Action] + Please apply the following two backports to the appropriate Ubuntu HWE + kernels: + https://github.com/NVIDIA-BaseOS-6/linux-nvidia-5.19/commit/055c9ec3739d7df1179db3ba054b00f3dd684560 https://github.com/NVIDIA-BaseOS-6/linux-nvidia-6.2/commit/8ab3253c6a59eee3424fe0c60b1fc6dc9f2d73b7 -- 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/2026776 Title: arm64+ast2600: No Output from BMC's VGA port Status in linux package in Ubuntu: New Status in linux-hwe-5.19 package in Ubuntu: New Status in linux-hwe-6.2 package in Ubuntu: New Bug description: [Issue] On systems that have the following combination of hardware...: 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ .. we see no output when connecting a display to the BMC's VGA port. Upon further investigation, we see that applying the following patch fixes this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6&id=4327a6137ed43a091d900b1ac833345d60f32228 [Action] Please apply the following two backports to the appropriate Ubuntu HWE kernels: https://github.com/NVIDIA-BaseOS-6/linux-nvidia-5.19/commit/055c9ec3739d7df1179db3ba054b00f3dd684560 https://github.com/NVIDIA-BaseOS-6/linux-nvidia-6.2/commit/8ab3253c6a59eee3424fe0c60b1fc6dc9f2d73b7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026776/+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 2026776] Re: arm64+ast2600: No Output from BMC's VGA port
There is no need for kernel logs, we've already diagnosed the problem and are providing the solution. -- 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/2026776 Title: arm64+ast2600: No Output from BMC's VGA port Status in linux package in Ubuntu: New Status in linux-hwe-5.19 package in Ubuntu: New Status in linux-hwe-6.2 package in Ubuntu: New Bug description: [Issue] On systems that have the following combination of hardware...: 1) arm64 CPU 2) ASPEED AST2600 BMC: https://www.aspeedtech.com/server_ast2600/ .. we see no output when connecting a display to the BMC's VGA port. Upon further investigation, we see that applying the following patch fixes this issue: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/ast?h=v6.4-rc6&id=4327a6137ed43a091d900b1ac833345d60f32228 [Action] Please apply the following two backports to the appropriate Ubuntu HWE kernels: https://github.com/NVIDIA-BaseOS-6/linux-nvidia-5.19/commit/055c9ec3739d7df1179db3ba054b00f3dd684560 https://github.com/NVIDIA-BaseOS-6/linux-nvidia-6.2/commit/8ab3253c6a59eee3424fe0c60b1fc6dc9f2d73b7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026776/+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 2026779] [NEW] package linux-image-unsigned-6.2.0-1005-oracle 6.2.0-1005.5 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Public bug reported: . ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-unsigned-6.2.0-1005-oracle 6.2.0-1005.5 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jul 10 15:19:53 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2023-04-28 (73 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: dkms Title: package linux-image-unsigned-6.2.0-1005-oracle 6.2.0-1005.5 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2026779 Title: package linux-image-unsigned-6.2.0-1005-oracle 6.2.0-1005.5 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: . ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-unsigned-6.2.0-1005-oracle 6.2.0-1005.5 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Jul 10 15:19:53 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2023-04-28 (73 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: dkms Title: package linux-image-unsigned-6.2.0-1005-oracle 6.2.0-1005.5 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2026779/+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 2026780] [NEW] kernel module dell-smm-hwmon missing compatible model
Public bug reported: I'm running an Alienware M17 R5. The kernel module dell-smm-hwmon does not automatically load due to the DMI id being 'Alienware'. However, the system fan and cpu fan, as well as motherboard temperature sensors, are not detected until loading the dell-smm-hwmon module. After loading the module, with argument 'ignore_dmi=1', the temperature sensors and fan sensors are detected properly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 15:15:10 2023 InstallationDate: Installed on 2023-07-10 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) MachineType: Alienware Alienware m17 R5 AMD ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-24-generic root=UUID=a0b7daad-db0b-4ab7-a7e4-18ea04587079 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-24-generic N/A linux-backports-modules-6.2.0-24-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2023 dmi.bios.release: 1.9 dmi.bios.vendor: Alienware dmi.bios.version: 1.9.1 dmi.board.name: 0XV7MX dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: 1.9.1 dmi.ec.firmware.release: 0.25 dmi.modalias: dmi:bvnAlienware:bvr1.9.1:bd05/09/2023:br1.9:efr0.25:svnAlienware:pnAlienwarem17R5AMD:pvr1.9.1:rvnAlienware:rn0XV7MX:rvrA01:cvnAlienware:ct10:cvr1.9.1:sku0B5D: dmi.product.family: Alienware dmi.product.name: Alienware m17 R5 AMD dmi.product.sku: 0B5D dmi.product.version: 1.9.1 dmi.sys.vendor: Alienware ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- 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/2026780 Title: kernel module dell-smm-hwmon missing compatible model Status in linux package in Ubuntu: New Bug description: I'm running an Alienware M17 R5. The kernel module dell-smm-hwmon does not automatically load due to the DMI id being 'Alienware'. However, the system fan and cpu fan, as well as motherboard temperature sensors, are not detected until loading the dell-smm-hwmon module. After loading the module, with argument 'ignore_dmi=1', the temperature sensors and fan sensors are detected properly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-24-generic 6.2.0-24.24 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 15:15:10 2023 InstallationDate: Installed on 2023-07-10 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) MachineType: Alienware Alienware m17 R5 AMD ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-24-generic root=UUID=a0b7daad-db0b-4ab7-a7e4-18ea04587079 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-24-generic N/A linux-backports-modules-6.2.0-24-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2023 dmi.bios.release: 1.9 dmi.bios.vendor: Alienware dmi.bios.version: 1.9.1 dmi.board.name: 0XV7MX dmi.board.vendor: Alienware dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: 1.9.1 dmi.ec.firmware.release: 0.25 dmi.modalias: dmi:bvnAlienware:bvr1.9.1:bd05/09/2023:br1.9:efr0.25:svnAlienware:pnAlienwarem17R5AMD:pvr1.9.1:rvnAlienware:rn0XV7MX:rvrA01:cvnAlienware:ct10:cvr1.9.1:sku0B5D: dmi.product.family: Alienware dmi.product.name: Alienware m17 R5 AMD dmi.product.sku: 0B5D dmi.product.version: 1.9.1 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026780/+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 1786013] Autopkgtest regression report (linux-meta-nvidia-tegra/5.15.0.1015.15)
All autopkgtests for the newly accepted linux-meta-nvidia-tegra (5.15.0.1015.15) for jammy have finished running. The following regressions have been reported in tests triggered by the package: linux-nvidia-tegra/5.15.0-1015.15 (arm64) wireguard/unknown (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-nvidia-tegra [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
> I have had substantial performance problems since updating from ubuntu 22.10 > to 23.04. Maybe it's caused by thermald? See if `sudo systemctl stop thermald` can help. -- 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/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: New Bug description: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install undervolt==0.3.0) to force particular power limits (the provided values are intentional overkill): 1 │ from undervolt import read_power_limit, set_power_limit, PowerLimit, ADDRESSES 2 │ from pprint import pprint 3 │ 4 │ limits = read_power_limit(ADDRESSES) 5 │ pprint(vars(limits)) # print current values before setting them 6 │ 7 │ POWER_LIMITS = PowerLimit() 8 │ POWER_LIMITS.locked = True # lock means don't allow the value to be reset until a reboot. 9 │ POWER_LIMITS.backup_rest = 281474976776192 # afaik this is just a backup-on-failure setting, it has no effect here. 10 │ POWER_LIMITS.long_term_enabled = True 11 │ POWER_LIMITS.long_term_power = 160 # values are intentiona
[Kernel-packages] [Bug 2026754] Re: Xorg freeze
Thanks for the bug report. The attached Xorg logs seem to be old, from last month. Please run this command to collect a fresh log when the problem is happening: journalctl -b0 > journal.txt and attach the resulting text file here. ** Tags added: amdgpu hybrid multigpu multimonitor nvidia ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Summary changed: - Xorg freeze + [amdgpu][nvidia] HDMI picture not updating automatically, but only on mouse move. ** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2026754 Title: [amdgpu][nvidia] HDMI picture not updating automatically, but only on mouse move. Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in xorg-server package in Ubuntu: Incomplete Bug description: I use Asus FA507XI laptop with AMD 7940HS and NVIDIA RTX 4070. When using the second display via HDMI its picture not updating automatically, but only on mouse move. Additionally brightness control is not visible, so I can't change brightness. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.4.0-060400-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.54.03 Tue Jun 6 22:20:39 UTC 2023 GCC version: gcc version 12.1.0 (Ubuntu 12.1.0-2ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 18:22:48 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/535.54.03, 6.4.0-060400-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:2860] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:23bd] Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:23bd] InstallationDate: Installed on 2023-06-14 (25 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA507XI_FA507XI ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.4.0-060400-generic root=UUID=83cb4370-0eb1-47b5-8095-f0cc24cbfd0e ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2023 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FA507XI.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA507XI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFA507XI.307:bd06/14/2023:br5.29:efr3.4:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingA15FA507XI_FA507XI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA507XI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming A15 dmi.product.name: ASUS TUF Gaming A15 FA507XI_FA507XI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER 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.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 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/nvidia-gr
[Kernel-packages] [Bug 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
> Maybe it's caused by thermald? See if `sudo systemctl stop thermald` can help. I will try this, I will also reinstall the package. I am waiting to see if using sane power parameters in my script for bug 1 fixes the bug 2 issue, but that means I need to leave it sitting for 12+ hours so my iteration speed here is very slow. -- 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/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: New Bug description: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install undervolt==0.3.0) to force particular power limits (the provided values are intentional overkill): 1 │ from undervolt import read_power_limit, set_power_limit, PowerLimit, ADDRESSES 2 │ from pprint import pprint 3 │ 4 │ limits = read_power_limit(ADDRESSES) 5 │ pprint(vars(limits)) # print current values before setting them 6 │ 7 │ POWER_LIMITS = PowerLimit() 8 │ POWER_LIMITS.locked = True # lock means don't allow the value to be reset until a reboot. 9 │ POWER_LIMITS.backup_rest = 281474976776192 # afaik this is just a backup-on-failu
[Kernel-packages] [Bug 2026783] [NEW] soft lockup - likely NVIDIA GPU
Public bug reported: Using VirtualBox on the main host, with the "3d Acceleration" enabled for the windows 10 guest, I somehow triggered a bug. I suspect this is a bug in handling for the NVIDIA driver, it has an impact on the kernel because of the loaded module. Soft Lockups repeatedly occur, please see the dmesg logfile attached. Here is the spinlock -- [Mon Jul 10 18:37:39 2023] CPU: 4 PID: 90 Comm: irq/126-pciehp Tainted: P OEL 6.2.0-24-generic #24-Ubuntu [Mon Jul 10 18:37:39 2023] Hardware name: LENOVO 20XY0027US/20XY0027US, BIOS N32ET84W (1.60 ) 04/05/2023 [Mon Jul 10 18:37:39 2023] RIP: 0010:_raw_spin_unlock_irqrestore+0x21/0x60 [Mon Jul 10 18:37:39 2023] Code: 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 49 89 f0 48 89 e5 c6 07 00 0f 1f 00 41 f7 c0 00 02 00 00 74 06 fb 0f 1f 44 00 00 <65> ff 0d 90 a5 95 73 74 13 5d 31 c0 31 d2 31 c9 31 f6 31 ff 45 31 [Mon Jul 10 18:37:39 2023] RSP: 0018:ab64005ef780 EFLAGS: 0206 [Mon Jul 10 18:37:39 2023] RAX: RBX: 0001 RCX: [Mon Jul 10 18:37:39 2023] RDX: 0003d268 RSI: 0202 RDI: 9d86d183f668 [Mon Jul 10 18:37:39 2023] RBP: ab64005ef780 R08: 0202 R09: [Mon Jul 10 18:37:39 2023] R10: R11: R12: 0010 [Mon Jul 10 18:37:39 2023] R13: 0003d258 R14: ab64020b0008 R15: 0002 [Mon Jul 10 18:37:39 2023] FS: () GS:9d8a0f70() knlGS: [Mon Jul 10 18:37:39 2023] CS: 0010 DS: ES: CR0: 80050033 [Mon Jul 10 18:37:39 2023] CR2: 0153dfa8 CR3: 0002e5210006 CR4: 00772ee0 [Mon Jul 10 18:37:39 2023] PKRU: 5554 [Mon Jul 10 18:37:39 2023] Call Trace: [Mon Jul 10 18:37:39 2023] [Mon Jul 10 18:37:39 2023] os_release_spinlock+0x1a/0x30 [nvidia] [Mon Jul 10 18:37:39 2023] _nv038078rm+0xd9/0x100 [nvidia] [Mon Jul 10 18:37:39 2023] WARNING: kernel stack frame pointer at c662e071 in irq/126-pciehp:90 has bad value a30f4baf [ See the rest of the logs in the attached file. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg-logfile" https://bugs.launchpad.net/bugs/2026783/+attachment/5685294/+files/dmesg-logfile -- 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/2026783 Title: soft lockup - likely NVIDIA GPU Status in linux package in Ubuntu: New Bug description: Using VirtualBox on the main host, with the "3d Acceleration" enabled for the windows 10 guest, I somehow triggered a bug. I suspect this is a bug in handling for the NVIDIA driver, it has an impact on the kernel because of the loaded module. Soft Lockups repeatedly occur, please see the dmesg logfile attached. Here is the spinlock -- [Mon Jul 10 18:37:39 2023] CPU: 4 PID: 90 Comm: irq/126-pciehp Tainted: P OEL 6.2.0-24-generic #24-Ubuntu [Mon Jul 10 18:37:39 2023] Hardware name: LENOVO 20XY0027US/20XY0027US, BIOS N32ET84W (1.60 ) 04/05/2023 [Mon Jul 10 18:37:39 2023] RIP: 0010:_raw_spin_unlock_irqrestore+0x21/0x60 [Mon Jul 10 18:37:39 2023] Code: 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 49 89 f0 48 89 e5 c6 07 00 0f 1f 00 41 f7 c0 00 02 00 00 74 06 fb 0f 1f 44 00 00 <65> ff 0d 90 a5 95 73 74 13 5d 31 c0 31 d2 31 c9 31 f6 31 ff 45 31 [Mon Jul 10 18:37:39 2023] RSP: 0018:ab64005ef780 EFLAGS: 0206 [Mon Jul 10 18:37:39 2023] RAX: RBX: 0001 RCX: [Mon Jul 10 18:37:39 2023] RDX: 0003d268 RSI: 0202 RDI: 9d86d183f668 [Mon Jul 10 18:37:39 2023] RBP: ab64005ef780 R08: 0202 R09: [Mon Jul 10 18:37:39 2023] R10: R11: R12: 0010 [Mon Jul 10 18:37:39 2023] R13: 0003d258 R14: ab64020b0008 R15: 0002 [Mon Jul 10 18:37:39 2023] FS: () GS:9d8a0f70() knlGS: [Mon Jul 10 18:37:39 2023] CS: 0010 DS: ES: CR0: 80050033 [Mon Jul 10 18:37:39 2023] CR2: 0153dfa8 CR3: 0002e5210006 CR4: 00772ee0 [Mon Jul 10 18:37:39 2023] PKRU: 5554 [Mon Jul 10 18:37:39 2023] Call Trace: [Mon Jul 10 18:37:39 2023] [Mon Jul 10 18:37:39 2023] os_release_spinlock+0x1a/0x30 [nvidia] [Mon Jul 10 18:37:39 2023] _nv038078rm+0xd9/0x100 [nvidia] [Mon Jul 10 18:37:39 2023] WARNING: kernel stack frame pointer at c662e071 in irq/126-pciehp:90 has bad value a30f4baf [ See the rest of the logs in the attached file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026783/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net
[Kernel-packages] [Bug 2026783] Re: soft lockup - likely NVIDIA GPU
nvidia logfile added after a reboot -- forgot to add it at the time of the problem. May not be as useful. ** Attachment added: "nvidia-bug-report.log.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026783/+attachment/5685295/+files/nvidia-bug-report.log.gz -- 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/2026783 Title: soft lockup - likely NVIDIA GPU Status in linux package in Ubuntu: New Bug description: Using VirtualBox on the main host, with the "3d Acceleration" enabled for the windows 10 guest, I somehow triggered a bug. I suspect this is a bug in handling for the NVIDIA driver, it has an impact on the kernel because of the loaded module. Soft Lockups repeatedly occur, please see the dmesg logfile attached. Here is the spinlock -- [Mon Jul 10 18:37:39 2023] CPU: 4 PID: 90 Comm: irq/126-pciehp Tainted: P OEL 6.2.0-24-generic #24-Ubuntu [Mon Jul 10 18:37:39 2023] Hardware name: LENOVO 20XY0027US/20XY0027US, BIOS N32ET84W (1.60 ) 04/05/2023 [Mon Jul 10 18:37:39 2023] RIP: 0010:_raw_spin_unlock_irqrestore+0x21/0x60 [Mon Jul 10 18:37:39 2023] Code: 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 49 89 f0 48 89 e5 c6 07 00 0f 1f 00 41 f7 c0 00 02 00 00 74 06 fb 0f 1f 44 00 00 <65> ff 0d 90 a5 95 73 74 13 5d 31 c0 31 d2 31 c9 31 f6 31 ff 45 31 [Mon Jul 10 18:37:39 2023] RSP: 0018:ab64005ef780 EFLAGS: 0206 [Mon Jul 10 18:37:39 2023] RAX: RBX: 0001 RCX: [Mon Jul 10 18:37:39 2023] RDX: 0003d268 RSI: 0202 RDI: 9d86d183f668 [Mon Jul 10 18:37:39 2023] RBP: ab64005ef780 R08: 0202 R09: [Mon Jul 10 18:37:39 2023] R10: R11: R12: 0010 [Mon Jul 10 18:37:39 2023] R13: 0003d258 R14: ab64020b0008 R15: 0002 [Mon Jul 10 18:37:39 2023] FS: () GS:9d8a0f70() knlGS: [Mon Jul 10 18:37:39 2023] CS: 0010 DS: ES: CR0: 80050033 [Mon Jul 10 18:37:39 2023] CR2: 0153dfa8 CR3: 0002e5210006 CR4: 00772ee0 [Mon Jul 10 18:37:39 2023] PKRU: 5554 [Mon Jul 10 18:37:39 2023] Call Trace: [Mon Jul 10 18:37:39 2023] [Mon Jul 10 18:37:39 2023] os_release_spinlock+0x1a/0x30 [nvidia] [Mon Jul 10 18:37:39 2023] _nv038078rm+0xd9/0x100 [nvidia] [Mon Jul 10 18:37:39 2023] WARNING: kernel stack frame pointer at c662e071 in irq/126-pciehp:90 has bad value a30f4baf [ See the rest of the logs in the attached file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026783/+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 2026789] Re: Xorg display freeze when using gnome settings " display" to enable/disable displays on eGPU
Were you using Wayland when the freeze happened? Next time it happens, please reboot and then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: hybrid multigpu multimonitor nvidia ** Package changed: ubuntu => nvidia-graphics-drivers-535 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2026789 Title: Xorg display freeze when using gnome settings " display" to enable/disable displays on eGPU Status in nvidia-graphics-drivers-535 package in Ubuntu: Incomplete Bug description: When using the Ubuntu settings app to change displays I was enabling and disabling displays to see if I could replicate a problem. It appears that the drivers / setup are OK with 2x displays, but things start to fall apart when there are 3x displays. 2x displys managed by NVIDIA displayport connection, and 1x display managed by the Intel Iris GPU. I have noticed that windows appear to move between displays, so I think there is a problem with how the displays and the windows are arranged. Attached are as many logs as I can find for this problem. Notably, I am receiving errors in my local terminal when reporting this bug: [15578:15578:0710/200056.340294:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! [15578:15578:0710/200056.356275:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times! [15578:15578:0710/200056.357312:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! [15529:15529:0710/200138.416553:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented This appears to be related to DRM ?? Tehese messages occured as I enabled / disabled the displays on displayport: [Mon Jul 10 19:53:29 2023] [drm] [nvidia-drm] [GPU ID 0x5200] Framebuffer memory not appropriate for scanout [Mon Jul 10 19:53:29 2023] [drm] [nvidia-drm] [GPU ID 0x5200] Framebuffer memory not appropriate for scanout [Mon Jul 10 19:53:41 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0xfc099386 [Mon Jul 10 19:54:23 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0xcd359766 [Mon Jul 10 19:54:23 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0x40936ab7 These messages appeard when I started the gnome display manager : Mon Jul 10 19:46:16 2023] rfkill: input handler enabled [Mon Jul 10 19:46:17 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000 [Mon Jul 10 19:46:17 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000 [Mon Jul 10 19:46:17 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000 [Mon Jul 10 19:46:17 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0xf989da34 [Mon Jul 10 19:46:17 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0x32149488 [Mon Jul 10 19:46:18 2023] rfkill: input handler disabled [Mon Jul 10 19:46:25 2023] bijiben-shell-s[3102]: segfault at 7f9c05be1b13 ip 7f9c1bb4e5a1 sp 7fff6f49e438 error 4 in libgobject-2.0.so.0.7600.1[7f9c1bb24000+34000] likely on CPU 6 (core 2, socket 0) [Mon Jul 10 19:46:25 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48> 8b 00 48 3d fc 03 00 00 76 1c 48 83 e0 fc 0f b6 50 14 48 39 74 [Mon Jul 10 19:46:26 2023] bijiben-shell-s[3224]: segfault at 7fcb58c86283 ip 7fccc790c5a1 sp 7ffd276291d8 error 4 in libgobject-2.0.so.0.7600.1[7fccc78e2000+34000] likely on CPU 2 (core 2, socket 0) [Mon Jul 10 19:46:26 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48> 8b 00 48 3d fc 03 00 00 76 1c 48 83 e0 fc 0f b6 50 14 48 39 74 [Mon Jul 10 19:46:27 2023] bijiben-shell-s[3278]: segfault at 7f33cc004 ip 7f33f16425a1 sp 7ffd563f0fb8 error 4 in libgobject-2.0.so.0.7600.1[7f33f1618000+34000] likely on CPU 0 (core 0, socket 0) [Mon Jul 10 19:46:27 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74
[Kernel-packages] [Bug 2026229] Re: Crashing issue with 5.15 kernel
Thanks, we are trying out the jammy kernel to confirm it resolves the issue. Will report back -- 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/2026229 Title: Crashing issue with 5.15 kernel Status in linux package in Ubuntu: New Bug description: We have been working on making self-hosted GitHub actions runners available in Canonical and have encountered an issue which seems to be with the kernel. The github-runner charm is a machine charm that runs on virtual machines. The charm creates a LXD virtual machine inside the juju unit/machine and runs the GitHub self-hosted runner application. The self-hosted runner can be used on GitHub to run GitHub Actions. The deployment of github-runner charm consists of about 15 units/machines (one unit per machine). In the past, we would see about one machine going into “down” state about every 1-3 days. From the openstack hosting the machine, it seems the machine has crashed. The syslog includes the following entry: Jun 8 21:15:58 juju-e4d256-prod-github-runner-66 kernel: [27199.579882] BUG: kernel NULL pointer dereference, address: 0008 The syslog: https://pastebin.canonical.com/p/gYy3Z9XGkN/ Log on openstack: https://pastebin.canonical.com/p/fbGcmQv9JW/ The deployment of the charm was on the jammy series (22.04). This series uses the Linux kernel 5.15. For the last week, the team has been experimenting with upgrading the kernel to the HWE version which is 5.19. Since then we have not encountered crashes in the virtual machine hosting the juju machine. This mattermost thread includes our team’s discussion of this issue and the reason we decide to upgrade the kernel: https://chat.canonical.com/canonical/pl/h8wrrmcnh3d17dtjmg56zf5pwy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026229/+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
