[Kernel-packages] [Bug 2058452] Re: Support USB serial port for Dell DW5826e WWAN
** Description changed:
[SRU Justification]
[Impact]
Missing usb serial interface for Dell DW5826e.
[Fix]
* commit 129690fb229a ("USB: serial: qcserial: add new usb-id for Dell
Wireless DW5826e
"): in v6.8
[Test Case]
- 1. check system with USB\VID_413C_8217 and USB\VID_413C_8218
+ 1. check system with USB\VID_413C_8217 or USB\VID_413C_8218
creates corresponding tty port
[Where problems could occur]
The commit adds new device ID only, it won't impact devices which are
supported originally.
[Other Info]
Upstream commit:
https://github.com/torvalds/linux/commit/129690fb229a20b6e563a77a2c85266acecf20bc
Dell new platform with the device will be enabled by linux-oem-6.5.
The tty port will be utilized by the userspace fcc unlock program.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2058452
Title:
Support USB serial port for Dell DW5826e WWAN
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing usb serial interface for Dell DW5826e.
[Fix]
* commit 129690fb229a ("USB: serial: qcserial: add new usb-id for Dell
Wireless DW5826e
"): in v6.8
[Test Case]
1. check system with USB\VID_413C_8217 or USB\VID_413C_8218
creates corresponding tty port
[Where problems could occur]
The commit adds new device ID only, it won't impact devices which are
supported originally.
[Other Info]
Upstream commit:
https://github.com/torvalds/linux/commit/129690fb229a20b6e563a77a2c85266acecf20bc
Dell new platform with the device will be enabled by linux-oem-6.5.
The tty port will be utilized by the userspace fcc unlock program.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2058452/+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 2058452] Re: Support USB serial port for Dell DW5826e WWAN
** Description changed:
[SRU Justification]
[Impact]
Missing usb serial interface for Dell DW5826e.
[Fix]
* commit 129690fb229a ("USB: serial: qcserial: add new usb-id for Dell
Wireless DW5826e
"): in v6.8
[Test Case]
- 1. check system with USB\VID_413C_8217 creates corresponding tty
- port
+ 1. check system with USB\VID_413C_8217 and USB\VID_413C_8218
+ creates corresponding tty port
[Where problems could occur]
The commit adds new device ID only, it won't impact devices which are
supported originally.
[Other Info]
Upstream MP:
https://github.com/torvalds/linux/commit/129690fb229a20b6e563a77a2c85266acecf20bc
Dell new platform with the device will be enabled by linux-oem-6.5.
- The tty port will be utilized the userspace fcc unlock program.
+ The tty port will be utilized by the userspace fcc unlock program.
** Description changed:
[SRU Justification]
[Impact]
Missing usb serial interface for Dell DW5826e.
[Fix]
* commit 129690fb229a ("USB: serial: qcserial: add new usb-id for Dell
Wireless DW5826e
"): in v6.8
[Test Case]
- 1. check system with USB\VID_413C_8217 and USB\VID_413C_8218
- creates corresponding tty port
+ 1. check system with USB\VID_413C_8217 creates corresponding tty
+ port
[Where problems could occur]
The commit adds new device ID only, it won't impact devices which are
supported originally.
[Other Info]
- Upstream MP:
https://github.com/torvalds/linux/commit/129690fb229a20b6e563a77a2c85266acecf20bc
+ Upstream commit:
https://github.com/torvalds/linux/commit/129690fb229a20b6e563a77a2c85266acecf20bc
Dell new platform with the device will be enabled by linux-oem-6.5.
- The tty port will be utilized by the userspace fcc unlock program.
+ The tty port will be utilized the userspace fcc unlock program.
** Description changed:
[SRU Justification]
[Impact]
Missing usb serial interface for Dell DW5826e.
[Fix]
* commit 129690fb229a ("USB: serial: qcserial: add new usb-id for Dell
Wireless DW5826e
"): in v6.8
[Test Case]
- 1. check system with USB\VID_413C_8217 creates corresponding tty
- port
+ 1. check system with USB\VID_413C_8217 and USB\VID_413C_8218
+ creates corresponding tty port
[Where problems could occur]
The commit adds new device ID only, it won't impact devices which are
supported originally.
[Other Info]
Upstream commit:
https://github.com/torvalds/linux/commit/129690fb229a20b6e563a77a2c85266acecf20bc
Dell new platform with the device will be enabled by linux-oem-6.5.
- The tty port will be utilized the userspace fcc unlock program.
+ The tty port will be utilized by the userspace fcc unlock program.
** Tags added: oem-priority originate-from-2058338 somerville
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2058452
Title:
Support USB serial port for Dell DW5826e WWAN
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux-oem-6.5 source package in Jammy:
In Progress
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing usb serial interface for Dell DW5826e.
[Fix]
* commit 129690fb229a ("USB: serial: qcserial: add new usb-id for Dell
Wireless DW5826e
"): in v6.8
[Test Case]
1. check system with USB\VID_413C_8217 and USB\VID_413C_8218
creates corresponding tty port
[Where problems could occur]
The commit adds new device ID only, it won't impact devices which are
supported originally.
[Other Info]
Upstream commit:
https://github.com/torvalds/linux/commit/129690fb229a20b6e563a77a2c85266acecf20bc
Dell new platform with the device will be enabled by linux-oem-6.5.
The tty port will be utilized by the userspace fcc unlock program.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2058452/+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 2058573] Re: alsa/realtek: adjust max output valume for headphone on 2 LG machines
** Description changed: - This is for tracking purpose. + [Impact] + In an oem project, we found the max playback volume of the headphone + is too high on 2 LG machines, it could bring harm to listeners. As + requested by OEM customer, we need to decrease the max volume. + + + [Fix] + Cherry-pick a mainline kernel patch, this could fix this issue. + + [Test] + Booting with the patched kernel, plug the headphone, set the playback + volue to max, run: + amixer -c1 contents | grep -n2 "Headphone Playback Volume" + + The value is 77,77 instead of 87,87 like below: + numid=1,iface=MIXER,name='Headphone Playback Volume' + ; type=INTEGER,access=rw---R--,values=2,min=0,max=87,step=0 + : values=77,77 + + + [Where problems could occur] + This patch changes the amplifier's default value, probably + will make the audio malfunction, but this change is specific + to those 2 LG machines (by SSID), will not bring regression + to other machines. For those 2 machines, we already tested patch, + the audio worked well. ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Mantic) Importance: Undecided => High ** Changed in: linux (Ubuntu Noble) Importance: Undecided => High -- 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/2058573 Title: alsa/realtek: adjust max output valume for headphone on 2 LG machines Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: In Progress Bug description: [Impact] In an oem project, we found the max playback volume of the headphone is too high on 2 LG machines, it could bring harm to listeners. As requested by OEM customer, we need to decrease the max volume. [Fix] Cherry-pick a mainline kernel patch, this could fix this issue. [Test] Booting with the patched kernel, plug the headphone, set the playback volue to max, run: amixer -c1 contents | grep -n2 "Headphone Playback Volume" The value is 77,77 instead of 87,87 like below: numid=1,iface=MIXER,name='Headphone Playback Volume' ; type=INTEGER,access=rw---R--,values=2,min=0,max=87,step=0 : values=77,77 [Where problems could occur] This patch changes the amplifier's default value, probably will make the audio malfunction, but this change is specific to those 2 LG machines (by SSID), will not bring regression to other machines. For those 2 machines, we already tested patch, the audio worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058573/+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 2058452] Re: Support USB serial port for Dell DW5826e WWAN
** Also affects: linux-oem-6.5 (Ubuntu Noble)
Importance: Undecided
Assignee: Kai-Chuan Hsieh (kchsieh)
Status: New
** Also affects: linux-oem-6.5 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.5 (Ubuntu Noble)
Status: New => Opinion
** Changed in: linux-oem-6.5 (Ubuntu Noble)
Status: Opinion => Invalid
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh)
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-oem-6.5 (Ubuntu Noble)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2058452
Title:
Support USB serial port for Dell DW5826e WWAN
Status in HWE Next:
New
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux-oem-6.5 source package in Jammy:
New
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing usb serial interface for Dell DW5826e.
[Fix]
* commit 129690fb229a ("USB: serial: qcserial: add new usb-id for Dell
Wireless DW5826e
"): in v6.8
[Test Case]
1. check system with USB\VID_413C_8217 creates corresponding tty
port
[Where problems could occur]
The commit adds new device ID only, it won't impact devices which are
supported originally.
[Other Info]
Upstream MP:
https://github.com/torvalds/linux/commit/129690fb229a20b6e563a77a2c85266acecf20bc
Dell new platform with the device will be enabled by linux-oem-6.5.
The tty port will be utilized the userspace fcc unlock program.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2058452/+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 2058452] Re: Support USB serial port for Dell DW5826e WWAN
** Description changed:
[SRU Justification]
[Impact]
Missing usb serial interface for Dell DW5826e.
[Fix]
* commit 129690fb229a ("USB: serial: qcserial: add new usb-id for Dell
Wireless DW5826e
"): in v6.9-rc1
[Test Case]
1. check system with USB\VID_413C_8217 creates corresponding tty
port
[Where problems could occur]
The commit adds new device ID only, it won't impact devices which are
supported originally.
[Other Info]
Upstream MP:
https://github.com/torvalds/linux/commit/129690fb229a20b6e563a77a2c85266acecf20bc
Dell new platform with the device will be enabled by linux-oem-6.5.
+ The tty port will be utilized the userspace fcc unlock program.
** No longer affects: linux (Ubuntu)
** Description changed:
[SRU Justification]
[Impact]
Missing usb serial interface for Dell DW5826e.
[Fix]
* commit 129690fb229a ("USB: serial: qcserial: add new usb-id for Dell
Wireless DW5826e
- "): in v6.9-rc1
+ "): in v6.8
[Test Case]
1. check system with USB\VID_413C_8217 creates corresponding tty
port
[Where problems could occur]
The commit adds new device ID only, it won't impact devices which are
supported originally.
[Other Info]
Upstream MP:
https://github.com/torvalds/linux/commit/129690fb229a20b6e563a77a2c85266acecf20bc
Dell new platform with the device will be enabled by linux-oem-6.5.
The tty port will be utilized the userspace fcc unlock program.
--
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/2058452
Title:
Support USB serial port for Dell DW5826e WWAN
Status in HWE Next:
New
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in linux-oem-6.5 source package in Jammy:
New
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing usb serial interface for Dell DW5826e.
[Fix]
* commit 129690fb229a ("USB: serial: qcserial: add new usb-id for Dell
Wireless DW5826e
"): in v6.8
[Test Case]
1. check system with USB\VID_413C_8217 creates corresponding tty
port
[Where problems could occur]
The commit adds new device ID only, it won't impact devices which are
supported originally.
[Other Info]
Upstream MP:
https://github.com/torvalds/linux/commit/129690fb229a20b6e563a77a2c85266acecf20bc
Dell new platform with the device will be enabled by linux-oem-6.5.
The tty port will be utilized the userspace fcc unlock program.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2058452/+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 2058578] Re: Add support for several cs35l41 amplifier devices (laptop audio support)
I don't know how that got lost... "git clone" should be: git clone https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058578 Title: Add support for several cs35l41 amplifier devices (laptop audio support) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Support for the cs35l41_hda_property table has been already been backported to hwe-6.5-next: commit eec052d5cff271d7bf6854f28c62c4a6650c379b (HEAD -> hwe-6.5-next, tag: Ubuntu-hwe-6.5-6.5.0-27.28_22.04.1, origin/hwe-6.5-next) Support for several devices has been merged to torvalds/linux v6.8 tag: commit e8f897f4afef0031fe618a8e94127a0934896aba (HEAD, tag: v6.8) It would be great if the following commits for sound/pci/hda/cs35l41_hda_property.c could be cherry-picked for release in the near future (listed newest to oldest): b603d95692e47dc6f5f733e93c3841dc0c01e624 706c1fa1ab09f11a131fc4d699ce4c0224b1cb2d be220d2e5544ff094142d263db5cf94d034b5e39 c16dfab33f99fc3ff43d48253bc2784ccb84c1de 8c14dbf36424eb751d70c15f9a671549390057b2 7d65d70161ef75a3991480c91668ac11acedf211 ba7053b4b4a4ddcf530fa2b897e697004715d086 d110858a6925827609d11db8513d76750483ec06 ee694e7db47e1af00ffb29f569904a9ed576868f 916d051730ae48aef8b588fd096fefca4bc0590a ed7326a24a1a9af65fafefd86b505e7c3b968f6d 2b35b66d82dc4641ba60f7f3c36c0040eedb74e2 b257187bcff4bccc9e7a8f1b8a1a5526ff815af1 b592ed2e1d78a475f781802e441c499ab446975b 8c4c216db8fb84be9c4ca60d72b2066cf28f 2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f I am running on KDE neon 6.0 release 22.04 Linux Scott-Laptop 6.5.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 12 10:22:43 UTC 2 x86_64 x86_64 x86_64 GNU/Linux This works fine for me: #!/bin/bash git clone cd jammy git remote add upstream https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git git fetch upstream git checkout hwe-6.5-next commits="2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f 8c4c216db8fb84be9c4ca60d72b2066cf28f b592ed2e1d78a475f781802e441c499ab446975b b257187bcff4bccc9e7a8f1b8a1a5526ff815af1 2b35b66d82dc4641ba60f7f3c36c0040eedb74e2 ed7326a24a1a9af65fafefd86b505e7c3b968f6d 916d051730ae48aef8b588fd096fefca4bc0590a ee694e7db47e1af00ffb29f569904a9ed576868f d110858a6925827609d11db8513d76750483ec06 ba7053b4b4a4ddcf530fa2b897e697004715d086 7d65d70161ef75a3991480c91668ac11acedf211 8c14dbf36424eb751d70c15f9a671549390057b2 c16dfab33f99fc3ff43d48253bc2784ccb84c1de be220d2e5544ff094142d263db5cf94d034b5e39 706c1fa1ab09f11a131fc4d699ce4c0224b1cb2d b603d95692e47dc6f5f733e93c3841dc0c01e624" for c in $commits; do echo $c git cherry-pick $c done cp /boot/config-$(uname -r) .config make -j16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2058578/+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 2058578] [NEW] Add support for several cs35l41 amplifier devices (laptop audio support)
Public bug reported: Support for the cs35l41_hda_property table has been already been backported to hwe-6.5-next: commit eec052d5cff271d7bf6854f28c62c4a6650c379b (HEAD -> hwe-6.5-next, tag: Ubuntu-hwe-6.5-6.5.0-27.28_22.04.1, origin/hwe-6.5-next) Support for several devices has been merged to torvalds/linux v6.8 tag: commit e8f897f4afef0031fe618a8e94127a0934896aba (HEAD, tag: v6.8) It would be great if the following commits for sound/pci/hda/cs35l41_hda_property.c could be cherry-picked for release in the near future (listed newest to oldest): b603d95692e47dc6f5f733e93c3841dc0c01e624 706c1fa1ab09f11a131fc4d699ce4c0224b1cb2d be220d2e5544ff094142d263db5cf94d034b5e39 c16dfab33f99fc3ff43d48253bc2784ccb84c1de 8c14dbf36424eb751d70c15f9a671549390057b2 7d65d70161ef75a3991480c91668ac11acedf211 ba7053b4b4a4ddcf530fa2b897e697004715d086 d110858a6925827609d11db8513d76750483ec06 ee694e7db47e1af00ffb29f569904a9ed576868f 916d051730ae48aef8b588fd096fefca4bc0590a ed7326a24a1a9af65fafefd86b505e7c3b968f6d 2b35b66d82dc4641ba60f7f3c36c0040eedb74e2 b257187bcff4bccc9e7a8f1b8a1a5526ff815af1 b592ed2e1d78a475f781802e441c499ab446975b 8c4c216db8fb84be9c4ca60d72b2066cf28f 2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f I am running on KDE neon 6.0 release 22.04 Linux Scott-Laptop 6.5.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 12 10:22:43 UTC 2 x86_64 x86_64 x86_64 GNU/Linux This works fine for me: #!/bin/bash git clone cd jammy git remote add upstream https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git git fetch upstream git checkout hwe-6.5-next commits="2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f 8c4c216db8fb84be9c4ca60d72b2066cf28f b592ed2e1d78a475f781802e441c499ab446975b b257187bcff4bccc9e7a8f1b8a1a5526ff815af1 2b35b66d82dc4641ba60f7f3c36c0040eedb74e2 ed7326a24a1a9af65fafefd86b505e7c3b968f6d 916d051730ae48aef8b588fd096fefca4bc0590a ee694e7db47e1af00ffb29f569904a9ed576868f d110858a6925827609d11db8513d76750483ec06 ba7053b4b4a4ddcf530fa2b897e697004715d086 7d65d70161ef75a3991480c91668ac11acedf211 8c14dbf36424eb751d70c15f9a671549390057b2 c16dfab33f99fc3ff43d48253bc2784ccb84c1de be220d2e5544ff094142d263db5cf94d034b5e39 706c1fa1ab09f11a131fc4d699ce4c0224b1cb2d b603d95692e47dc6f5f733e93c3841dc0c01e624" for c in $commits; do echo $c git cherry-pick $c done cp /boot/config-$(uname -r) .config make -j16 ** Affects: linux-hwe-6.5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058578 Title: Add support for several cs35l41 amplifier devices (laptop audio support) Status in linux-hwe-6.5 package in Ubuntu: New Bug description: Support for the cs35l41_hda_property table has been already been backported to hwe-6.5-next: commit eec052d5cff271d7bf6854f28c62c4a6650c379b (HEAD -> hwe-6.5-next, tag: Ubuntu-hwe-6.5-6.5.0-27.28_22.04.1, origin/hwe-6.5-next) Support for several devices has been merged to torvalds/linux v6.8 tag: commit e8f897f4afef0031fe618a8e94127a0934896aba (HEAD, tag: v6.8) It would be great if the following commits for sound/pci/hda/cs35l41_hda_property.c could be cherry-picked for release in the near future (listed newest to oldest): b603d95692e47dc6f5f733e93c3841dc0c01e624 706c1fa1ab09f11a131fc4d699ce4c0224b1cb2d be220d2e5544ff094142d263db5cf94d034b5e39 c16dfab33f99fc3ff43d48253bc2784ccb84c1de 8c14dbf36424eb751d70c15f9a671549390057b2 7d65d70161ef75a3991480c91668ac11acedf211 ba7053b4b4a4ddcf530fa2b897e697004715d086 d110858a6925827609d11db8513d76750483ec06 ee694e7db47e1af00ffb29f569904a9ed576868f 916d051730ae48aef8b588fd096fefca4bc0590a ed7326a24a1a9af65fafefd86b505e7c3b968f6d 2b35b66d82dc4641ba60f7f3c36c0040eedb74e2 b257187bcff4bccc9e7a8f1b8a1a5526ff815af1 b592ed2e1d78a475f781802e441c499ab446975b 8c4c216db8fb84be9c4ca60d72b2066cf28f 2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f I am running on KDE neon 6.0 release 22.04 Linux Scott-Laptop 6.5.0-26-generic #26~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Mar 12 10:22:43 UTC 2 x86_64 x86_64 x86_64 GNU/Linux This works fine for me: #!/bin/bash git clone cd jammy git remote add upstream https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git git fetch upstream git checkout hwe-6.5-next commits="2e6f979037d5ae35c0ed38e2b63e9876eb7bc65f 8c4c216db8fb84be9c4ca60d72b2066cf28f b592ed2e1d78a475f781802e441c499ab446975b b257187bcff4bccc9e7a8f1b8a1a5526ff815af1 2b35b66d82dc4641ba60f7f3c36c0040eedb74e2 ed7326a24a1a9af65fafefd86b505e7c3b968f6d 916d051730ae48aef8b588fd096fefca4bc0590a ee694e7db47e1af00ffb29f569904a9ed576868f d110858a6925827609d11db8513d76750483ec06 ba7053b4b4a4ddcf530fa2b897e697004715d086 7d65d70161ef75a3991480c91668ac11acedf211 8c14dbf36424eb751d70c15f9a671549390057b2 c16dfab33f99fc3ff43d48253bc2784ccb84c1de
[Kernel-packages] [Bug 2054121] Re: Random Freezing
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
New
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-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.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
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.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+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 2058573] Re: alsa/realtek: adjust max output valume for headphone on 2 LG machines
** Summary changed: - alsa/realtek: adjust headphone max output valume on 2 LG machines + alsa/realtek: adjust max output valume for headphone on 2 LG machines -- 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/2058573 Title: alsa/realtek: adjust max output valume for headphone on 2 LG machines Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: In Progress Bug description: This is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058573/+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 2058477] Re: [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux-hwe-6.5-6.5.0/drivers/net/hyperv/
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Marcelo Cerri (mhcerri) -- 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/2058477 Title: [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux- hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1445:41" multiple times, especially during boot. Status in linux package in Ubuntu: New Bug description: Overview: A newly installed Ubuntu Server 22.04.4 on a Hyper-V virtual machine outputs error message "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux- hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1446:41" multiple times, especially during boot. Reproducing steps: 1. Download ubuntu-22.04.4-live-server-amd64.iso 2. Create a Hyper-V virtual machine. 3. Install Ubuntu 22.04.4 Server on the VM with the downloaded iso normally. 4. Boot the machine. Additional Information: - Host machine: Windows 10 Pro 22H2 OS Build 19045.3758 - Hyper-V configuration version: 9.0 - The error message "UBSAN: array-index-out-of-bounds" is similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008157, but the drivers are different. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058477/+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 2058480] Re: [Ubuntu 22.04.4/linux-image-6.5.0-1014-aws] Kernel outputs "UBSAN: array-index-out-of-bounds in /build/linux-aws-6.5-4tw9h1/linux-aws-6.5-6.5.0/drivers/net/xen-netf
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Marcelo Cerri (mhcerri) -- 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/2058480 Title: [Ubuntu 22.04.4/linux-image-6.5.0-1014-aws] Kernel outputs "UBSAN: array-index-out-of-bounds in /build/linux-aws-6.5-4tw9h1/linux- aws-6.5-6.5.0/drivers/net/xen-netfront.c:349:9 " multiple times, especially during boot Status in linux package in Ubuntu: New Bug description: A newly launched Ubuntu 22.04.4 EC2 instance outputs "UBSAN: array- index-out-of-bounds in /build/linux-aws-6.5-4tw9h1/linux- aws-6.5-6.5.0/drivers/net/xen-netfront.c:349:9" multiple times, especially during boot. Reproducing step: - Launch an Ubuntu 22.04.4 EC2 instance with the instance type t2.*. Additional Info: - Please use t2 instance to make sure to use xen-netfront as a network device. - This messages similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058477, which is related to netvsc.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058480/+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 2058483] Re: touchpad not working
** Changed in: linux-signed-hwe-6.5 (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058483 Title: touchpad not working Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: The touchpad is not in the xinput list and it doesn't work. I'm using hp pavilion 15 ec1021nl ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 20 14:21:02 2024 InstallationDate: Installed on 2024-03-20 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 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-6.5/+bug/2058483/+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 2058497] Re: package linux-image-6.5.0-1016-oem (not installed) failed to install/upgrade: installed linux-image-6.5.0-1016-oem package pre-removal script subprocess returned er
** Changed in: linux-signed-oem-6.5 (Ubuntu) Assignee: (unassigned) => Anthony Wong (anthonywong) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058497 Title: package linux-image-6.5.0-1016-oem (not installed) failed to install/upgrade: installed linux-image-6.5.0-1016-oem package pre- removal script subprocess returned error exit status 1 Status in linux-signed-oem-6.5 package in Ubuntu: New Bug description: I did not know this package was being installed. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-1016-oem (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Mar 16 21:13:08 2024 DuplicateSignature: package:linux-image-6.5.0-1016-oem:(not installed) Removing linux-image-6.5.0-1016-oem (6.5.0-1016.17) ... E: Aborting removal of the running kernel dpkg: error processing package linux-image-6.5.0-1016-oem (--remove): installed linux-image-6.5.0-1016-oem package pre-removal script subprocess returned error exit status 1 ErrorMessage: installed linux-image-6.5.0-1016-oem package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2024-03-11 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.11 SourcePackage: linux-signed-oem-6.5 Title: package linux-image-6.5.0-1016-oem (not installed) failed to install/upgrade: installed linux-image-6.5.0-1016-oem package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.5/+bug/2058497/+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 2058557] Re: Kernel panic during checkbox stress_ng_test on Grace running noble 6.8 (arm64+largemem) kernel
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Jose Ogando Justo (joseogando) -- 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/2058557 Title: Kernel panic during checkbox stress_ng_test on Grace running noble 6.8 (arm64+largemem) kernel Status in linux package in Ubuntu: New Bug description: A kernel oops and panic occurred during 22.04 SoC certification on Gunyolk (Grace/Grace) with 6.8 kernel, arm64+largemem variant Steps to reproduce: Run (as root) the following commands: add-apt-repository -y ppa:checkbox-dev/stable apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable apt update apt install -y canonical-certification-server /usr/lib/checkbox-provider-base/bin/stress_ng_test.py disk --device dm-0 --base-time 240 stress_ng_test caused a kernel panic after about 5 minutes. I have attached dmesg output from my reproducer to this report. Initially, this was identified via a panic during the above test, which was running as part of a run of certify-soc-22.04. Attached is a tarball containing: - apport.linux-image-6.8.0-11-generic-64k.kzsondji.apport: The output of `ubuntu-bug linux` on the machine (after reboot) - reproduced-dmesg.202403201942: The dmesg output captured by kdump when I reproduced my original issue by running only the single stress_ng_test.py command above (not the entire cert suite) - original-dmesg.txt: The dmesg output I captured when the stress_ng_test originally failed during the full cert suite run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058557/+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 2057454] Re: [Ubuntu 24.04] Failed to Install Ubuntu 24.04 with ISO attached to VirtualMedia of OSM.
I have not been able to recreate this issue. I was able to install an R760 with 24.04 with and without enabling openssh during an install using the Virtual Media. Can you try the latest daily build image that was released today? https://cdimage.ubuntu.com/ubuntu-server/daily-live/pending/ -- 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/2057454 Title: [Ubuntu 24.04] Failed to Install Ubuntu 24.04 with ISO attached to VirtualMedia of OSM. Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: On Dell PowerEdge system unable to complete Installation of Ubuntu 24.04 using ISO mounted by Virtual media option. Steps to Reproduce: - 1. Attach Ubuntu 24.04 ISO to RFS path of Virtual media. 2. Boot to F11 and select the Virtual Optical drive from Oneshot UEFI boot menu. 3. Begin the Ubuntu24.04 Installation. 4. Installation was failed. Expected Results: - The Installation should be successful without any errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057454/+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 2058573] [NEW] alsa/realtek: adjust headphone max output valume on 2 LG machines
Public bug reported: This is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Mantic) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Noble) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: In Progress ** Tags: jinju oem-priority originate-from-2055127 ** Package changed: linux-oem-6.5 (Ubuntu) => linux (Ubuntu) ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Assignee: Hui Wang (hui.wang) Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Mantic) Status: New => In Progress ** Changed in: linux (Ubuntu Noble) Status: New => In Progress ** Tags added: jinju oem-priority originate-from-2055127 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058573 Title: alsa/realtek: adjust headphone max output valume on 2 LG machines Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Mantic: In Progress Status in linux source package in Noble: In Progress Bug description: This is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2058573/+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 2054121] Re: Random Freezing
17:15:47 - SSL not avail
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5757691/+files/prevboot.txt
--
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/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
Incomplete
Bug description:
Random lockups in Ubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8
Uname: Linux 6.5.0-17-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.154.05 Thu Dec 28
15:37:48 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 16 09:08:41 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb0] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:12db]
InstallationDate: Installed on 2024-02-16 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64
(20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-17-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2023
dmi.bios.release: 1.60
dmi.bios.vendor: LENOVO
dmi.bios.version: M3JKT3CA
dmi.board.name: 32DD
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN 3305435660291
dmi.chassis.type: 35
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.25
dmi.modalias:
dmi:bvnLENOVO:bvrM3JKT3CA:bd11/15/2023:br1.60:efr1.25:svnLENOVO:pn30EF004VUS:pvrThinkStationP350Tiny:rvnLENOVO:rn32DD:rvrSDK0J40697WIN3305435660291:cvnLENOVO:ct35:cvrNone:skuLENOVO_MT_30EF_BU_Think_FM_ThinkStationP350Tiny:
dmi.product.family: ThinkStation P350 Tiny
dmi.product.name: 30EF004VUS
dmi.product.sku: LENOVO_MT_30EF_BU_Think_FM_ThinkStation P350 Tiny
dmi.product.version: ThinkStation P350 Tiny
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
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.7-3ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+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 2056354] Re: qat: Improve error recovery flows
** Changed in: linux (Ubuntu Noble) Status: Fix Committed => Fix Released -- 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/2056354 Title: qat: Improve error recovery flows Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: [Impact] This set improves the error recovery flows in the QAT drivers and adds a mechanism to test it through an heartbeat simulator. This is an upstream patch set applied to linux-next and scheduled for 6.9. Link to the upstream submission: https://patchwork.kernel.org/project/linux-crypto/cover/20240202105324.50391-1-mun.chun@intel.com/ We should apply this set to the Noble 6.8 kernel, in order to experience less issues with qat and improve maintainability. An added commit is required to update the configuration. [Test case] Unload and reload the module to verify that qat recover and log issues properly. Use the added error injection mechanism to verify the recovery flow. [Fix] Apply the following commits (from linux-next): 2ecd43413d76 Documentation: qat: fix auto_reset section 7d42e097607c crypto: qat - resolve race condition during AER recovery c2304e1a0b80 crypto: qat - change SLAs cleanup flow at shutdown 9567d3dc7609 crypto: qat - improve aer error reset handling 750fa7c20e60 crypto: qat - limit heartbeat notifications f5419a4239af crypto: qat - add auto reset on error 2aaa1995a94a crypto: qat - add fatal error notification 4469f9b23468 crypto: qat - re-enable sriov after pf reset ec26f8e6c784 crypto: qat - update PFVF protocol for recovery 758a0087db98 crypto: qat - disable arbitration before reset ae508d7afb75 crypto: qat - add fatal error notify method e2b67859ab6e crypto: qat - add heartbeat error simulator [Regression potential] We may experience qat regression when crashing or restarting the module. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056354/+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 2058557] Re: Kernel panic during checkbox stress_ng_test on Grace running noble 6.8 (arm64+largemem) kernel
This is also reproducible on the latest mainline version (https://kernel.ubuntu.com/mainline/v6.8/arm64/, retrieved 20 Mar 2024 @ 5 PM): 20 Mar 22:54: Running stress-ng aiol stressor for 240 seconds... [ 354.451450] Unable to handle kernel paging request at virtual address 17be9b4aa3e187be [ 354.459580] Mem abort info: [ 354.462439] ESR = 0x9621 [ 354.466274] EC = 0x25: DABT (current EL), IL = 32 bits [ 354.471703] SET = 0, FnV = 0 [ 354.474819] EA = 0, S1PTW = 0 [ 354.478024] FSC = 0x21: alignment fault [ 354.482118] Data abort info: [ 354.485056] ISV = 0, ISS = 0x0021, ISS2 = 0x [ 354.490662] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 354.495823] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 354.501251] [17be9b4aa3e187be] address between user and kernel address ranges [ 354.508548] Internal error: Oops: 9621 [#1] SMP [ 354.514245] Modules linked in: qrtr cfg80211 binfmt_misc nls_iso8859_1 input_leds dax_hmem cxl_acpi acpi_ipmi onboard_usb_hub nvidia_cspmu ipmi_ssif cxl_co re ipmi_devintf arm_cspmu_module arm_smmuv3_pmu ipmi_msghandler uio_pdrv_genirq uio spi_nor cppc_cpufreq joydev mtd acpi_power_meter dm_multipath nvme_fabrics efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 hid_generic rndis_host usbhid cdc_ether hid usbnet uas usb_storage crct10dif_ce polyval_ce polyval_generic ghash_ce s m4_ce_gcm sm4_ce_ccm sm4_ce sm4_ce_cipher sm4 sm3_ce sm3 nvme sha3_ce i2c_smbus ixgbe sha2_ce nvme_core ast sha256_arm64 xhci_pci sha1_ce xfrm_algo xhci_pci_r enesas i2c_algo_bit nvme_auth mdio spi_tegra210_quad i2c_tegra aes_neon_bs aes_neon_blk aes_ce_blk aes_ce_cipher [ 354.594676] CPU: 61 PID: 0 Comm: swapper/61 Kdump: loaded Not tainted 6.8.0-060800-generic-64k #202403131158 [ 354.604728] Hardware name: Supermicro MBD-G1SMH/G1SMH, BIOS 1.0c 12/28/2023 [ 354.611844] pstate: 034000c9 (nzcv daIF +PAN -UAO +TCO +DIT -SSBS BTYPE=--) [ 354.618962] pc : _raw_spin_lock_irqsave+0x44/0x100 [ 354.623863] lr : try_to_wake_up+0x68/0x758 [ 354.628053] sp : 8000807afaf0 [ 354.631436] x29: 8000807afaf0 x28: 0004 x27: [ 354.638731] x26: a06103dc8a98 x25: 8000807afd98 x24: 0002 [ 354.646027] x23: f8156840 x22: 17be9b4aa3e187be x21: [ 354.653323] x20: 0003 x19: 00c0 x18: 8000819a0098 [ 354.660619] x17: x16: x15: e97dca18 [ 354.667914] x14: x13: x12: [ 354.675208] x11: x10: x9 : a06100ba6810 [ 354.682504] x8 : x7 : 0040 x6 : 9080 [ 354.689800] x5 : c2fb0dc488b0 x4 : x3 : 894178c0 [ 354.697096] x2 : 0001 x1 : x0 : 17be9b4aa3e187be [ 354.704391] Call trace: [ 354.706886] _raw_spin_lock_irqsave+0x44/0x100 [ 354.711426] try_to_wake_up+0x68/0x758 [ 354.715254] wake_up_process+0x24/0x50 [ 354.719082] aio_complete+0x1c4/0x2b8 [ 354.722825] aio_complete_rw+0x11c/0x2c8 [ 354.726831] iomap_dio_bio_end_io+0x1f0/0x248 [ 354.731282] bio_endio+0x170/0x270 [ 354.734758] __dm_io_complete+0x180/0x200 [ 354.738855] clone_endio+0xc8/0x288 [ 354.742416] bio_endio+0x170/0x270 [ 354.745889] blk_mq_end_request_batch+0x2e0/0x558 [ 354.750696] nvme_pci_complete_batch+0x94/0x118 [nvme] [ 354.755958] nvme_irq+0x9c/0xb0 [nvme] [ 354.759788] __handle_irq_event_percpu+0x68/0x2c0 [ 354.764595] handle_irq_event+0x58/0xe8 [ 354.768511] handle_fasteoi_irq+0xb0/0x218 [ 354.772695] generic_handle_domain_irq+0x38/0x70 [ 354.777411] __gic_handle_irq_from_irqson.isra.0+0x180/0x310 [ 354.783195] gic_handle_irq+0x2c/0xa0 [ 354.786935] call_on_irq_stack+0x3c/0x50 [ 354.790941] do_interrupt_handler+0xb0/0xc8 [ 354.795214] el1_interrupt+0x48/0xf0 [ 354.798866] el1h_64_irq_handler+0x1c/0x40 [ 354.803050] el1h_64_irq+0x7c/0x80 [ 354.806523] cpuidle_enter_state+0xd8/0x790 [ 354.810795] cpuidle_enter+0x44/0x78 [ 354.814446] cpuidle_idle_call+0x15c/0x210 [ 354.818631] do_idle+0xb0/0x130 [ 354.821837] cpu_startup_entry+0x44/0x50 [ 354.825845] secondary_start_kernel+0xec/0x130 [ 354.830386] __secondary_switched+0xc0/0xc8 [ 354.834661] Code: b9001041 d503201f 5281 52800022 (88e17c02) [ 354.840893] SMP: stopping secondary CPUs [ 355.897569] SMP: failed to stop secondary CPUs 0-60,62-143 [ 355.904206] Starting crashdump kernel... [ 355.908214] [ cut here ] [ 355.912930] Some CPUs may be stale, kdump will be unreliable. [ 355.918807] WARNING: CPU: 61 PID: 0 at arch/arm64/kernel/machine_kexec.c:174 machine_kexec+0x48/0x1f0 [ 355.928236] Modules linked in: qrtr cfg80211 binfmt_misc nls_iso8859_1 input_leds dax_hmem
[Kernel-packages] [Bug 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
Hello, Got same issue linked to a vm_max_map_count too low. Regards. -- 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/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello there, I submit this request to improve the gaming experience in ubuntu for all users. Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just not starting because the vm_max_map_count is locked at 65530. If we change this value to a value > 20, all games are working well and there is no bug linked to maps. Some others distribution like Fedora or Pop OS, have already made the change few month before. It's time to Ubuntu to makes the change also. Thanks in advance for applying this request. How to make this change : One file to modify : /etc/sysctl.conf Add this line : vm.max_map_count=2147483642 Save Reboot and enjoy Best Regards Vinceff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2057792/+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 2056491] Re: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block`
Hi Chavez, thanks for checking it. I see this output: ``` Memory Keyboard Network Speaker ok 0 > printenv real-base -- Partition: common Signature: 0x70 --- real-basec0 c0 ok 0 > ``` I'm able to install Ubuntu Jammy 22.04 LTS into the same partitions. ISO via Virtual target device. I don't see the same error when trying an older image - working installation. Let me know if you need any other info. -- 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/2056491 Title: not able to install noble on PowerVM LPARs `Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block` Status in The Ubuntu-power-systems project: New Status in linux package in Ubuntu: New Bug description: After I select `Try or Install Ubuntu Server` on a PowerVM ppc64le Power9 or Power10 : error: out of memory. Press any key to continue... OF stdout device is: /vdevice/vty@3000 Preparing to boot Linux version 6.8.0-11-generic (buildd@bos01-ppc64el-003) (powerpc64le-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #11-Ubuntu SMP Wed Feb 14 00:33:03 UTC 2024 (Ubuntu 6.8.0-11.11-generic 6.8.0-rc4) Detected machine type: 0101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 256 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0e67 alloc_top: 2000 alloc_top_hi : 2000 rmo_top : 2000 ram_top : 2000 instantiating rtas at 0x1ec3... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x1078 -> 0x1078179e Device tree struct 0x1079 -> 0x107a Quiescing Open Firmware ... Booting Linux via __start() @ 0x0a75 ... [0.019184] plpks: POWER LPAR Platform KeyStore is not supported or enabled [0.114052] SED: plpks not available [0.114507] /dev/root: Can't open blockdev [0.114520] List of all bdev filesystems: [0.114523] ext3 [0.114523] ext2 [0.114525] ext4 [0.114527] squashfs [0.114529] vfat [0.114531] fuseblk [0.114532] [0.114535] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.114540] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.8.0-11-generic #11-Ubuntu [0.114545] Hardware name: IBM,9080-HEX POWER10 (raw) 0x800200 0xf06 of:IBM,FW1030.00 (NH1030_017) hv:phyp pSeries [0.114551] Call Trace: [0.114553] [c6403b40] [c16b2f28] dump_stack_lvl+0x70/0xb4 (unreliable) [0.114562] [c6403b70] [c01926ec] panic+0x300/0x524 [0.114568] [c6403c10] [c301146c] mount_root_generic+0x208/0x448 [0.114574] [c6403ce0] [c30118d8] prepare_namespace+0x98/0x430 [0.114580] [c6403d70] [c3010820] kernel_init_freeable+0x32c/0x37c [0.114585] [c6403de0] [c00115ec] kernel_init+0x34/0x298 [0.114591] [c6403e50] [c000dfbc] ret_from_kernel_user_thread+0x14/0x1c [0.114596] --- interrupt: 0 at 0x0 [0.117006] pstore: backend (nvram) writing error (-1) [0.119362] Rebooting in 10 seconds.. This is the message from a Power10(9080-HEX), but the same is happening on a PowrerVM-Power9 (9009-22A) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2056491/+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 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
I confirm this ! Please modify default value of VM_max_map_count -- 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/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello there, I submit this request to improve the gaming experience in ubuntu for all users. Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just not starting because the vm_max_map_count is locked at 65530. If we change this value to a value > 20, all games are working well and there is no bug linked to maps. Some others distribution like Fedora or Pop OS, have already made the change few month before. It's time to Ubuntu to makes the change also. Thanks in advance for applying this request. How to make this change : One file to modify : /etc/sysctl.conf Add this line : vm.max_map_count=2147483642 Save Reboot and enjoy Best Regards Vinceff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2057792/+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 2058557] [NEW] Kernel panic during checkbox stress_ng_test on Grace running noble 6.8 (arm64+largemem) kernel
Public bug reported: A kernel oops and panic occurred during 22.04 SoC certification on Gunyolk (Grace/Grace) with 6.8 kernel, arm64+largemem variant Steps to reproduce: Run (as root) the following commands: add-apt-repository -y ppa:checkbox-dev/stable apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable apt update apt install -y canonical-certification-server /usr/lib/checkbox-provider-base/bin/stress_ng_test.py disk --device dm-0 --base-time 240 stress_ng_test caused a kernel panic after about 5 minutes. I have attached dmesg output from my reproducer to this report. Initially, this was identified via a panic during the above test, which was running as part of a run of certify-soc-22.04. Attached is a tarball containing: - apport.linux-image-6.8.0-11-generic-64k.kzsondji.apport: The output of `ubuntu-bug linux` on the machine (after reboot) - reproduced-dmesg.202403201942: The dmesg output captured by kdump when I reproduced my original issue by running only the single stress_ng_test.py command above (not the entire cert suite) - original-dmesg.txt: The dmesg output I captured when the stress_ng_test originally failed during the full cert suite run ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "dmesg and ubuntu-bug outputs" https://bugs.launchpad.net/bugs/2058557/+attachment/5757643/+files/grace-panic.tar.xz -- 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/2058557 Title: Kernel panic during checkbox stress_ng_test on Grace running noble 6.8 (arm64+largemem) kernel Status in linux package in Ubuntu: New Bug description: A kernel oops and panic occurred during 22.04 SoC certification on Gunyolk (Grace/Grace) with 6.8 kernel, arm64+largemem variant Steps to reproduce: Run (as root) the following commands: add-apt-repository -y ppa:checkbox-dev/stable apt-add-repository -y ppa:firmware-testing-team/ppa-fwts-stable apt update apt install -y canonical-certification-server /usr/lib/checkbox-provider-base/bin/stress_ng_test.py disk --device dm-0 --base-time 240 stress_ng_test caused a kernel panic after about 5 minutes. I have attached dmesg output from my reproducer to this report. Initially, this was identified via a panic during the above test, which was running as part of a run of certify-soc-22.04. Attached is a tarball containing: - apport.linux-image-6.8.0-11-generic-64k.kzsondji.apport: The output of `ubuntu-bug linux` on the machine (after reboot) - reproduced-dmesg.202403201942: The dmesg output captured by kdump when I reproduced my original issue by running only the single stress_ng_test.py command above (not the entire cert suite) - original-dmesg.txt: The dmesg output I captured when the stress_ng_test originally failed during the full cert suite run To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058557/+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 2058550] [NEW] apply nvidia-tegra patches 2024 Mar 9-20
Public bug reported: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia-tegra and linux-nvida-tegra-igx). ** Affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2058550 Title: apply nvidia-tegra patches 2024 Mar 9-20 Status in linux-nvidia-tegra package in Ubuntu: New Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2058550/+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 2057454] Re: [Ubuntu 24.04] Failed to Install Ubuntu 24.04 with ISO attached to VirtualMedia of OSM.
This issue can be reproducible on 16G Platform also and below are the possible workarounds found during the experiments on 16G Platform. 1. During Installation of Ubuntu 24.04 when we disable/exclude [] Openssh server package issue won't be reproduced. After reboot and installing openssh server using 'apt-get install openssh-server' system is working as expected. 2. During Installation of Ubuntu 24.04 when we enable/include [x]Openssh server package. we are able to repro the issue. Thanks, Shubhakara P S -- 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/2057454 Title: [Ubuntu 24.04] Failed to Install Ubuntu 24.04 with ISO attached to VirtualMedia of OSM. Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: On Dell PowerEdge system unable to complete Installation of Ubuntu 24.04 using ISO mounted by Virtual media option. Steps to Reproduce: - 1. Attach Ubuntu 24.04 ISO to RFS path of Virtual media. 2. Boot to F11 and select the Virtual Optical drive from Oneshot UEFI boot menu. 3. Begin the Ubuntu24.04 Installation. 4. Installation was failed. Expected Results: - The Installation should be successful without any errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057454/+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 2058497] Re: package linux-image-6.5.0-1016-oem (not installed) failed to install/upgrade: installed linux-image-6.5.0-1016-oem package pre-removal script subprocess returned er
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058497 Title: package linux-image-6.5.0-1016-oem (not installed) failed to install/upgrade: installed linux-image-6.5.0-1016-oem package pre- removal script subprocess returned error exit status 1 Status in linux-signed-oem-6.5 package in Ubuntu: New Bug description: I did not know this package was being installed. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-1016-oem (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Mar 16 21:13:08 2024 DuplicateSignature: package:linux-image-6.5.0-1016-oem:(not installed) Removing linux-image-6.5.0-1016-oem (6.5.0-1016.17) ... E: Aborting removal of the running kernel dpkg: error processing package linux-image-6.5.0-1016-oem (--remove): installed linux-image-6.5.0-1016-oem package pre-removal script subprocess returned error exit status 1 ErrorMessage: installed linux-image-6.5.0-1016-oem package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2024-03-11 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.11 SourcePackage: linux-signed-oem-6.5 Title: package linux-image-6.5.0-1016-oem (not installed) failed to install/upgrade: installed linux-image-6.5.0-1016-oem package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.5/+bug/2058497/+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 2058498] [NEW] pwr-mlxbf: support Bobcat graceful shutdown via gpio6
Public bug reported: SRU Justification: [Impact] OCP3.0 project was discontinued and canceled so all stale code related to that was removed. The HID MLNXBF29 is used now for triggering a graceful shutdown for the Bobcat board. On the bobcat board, the main board cpld issues the shutdown request to the dpu cpld. the dpu cpld issues that request to ARM via GPIO6 and ARM should trigger a graceful shutdown and set the ARM boot progress to 6. [Fix] The HID MLNXBF29 is used now for triggering a graceful shutdown for the Bobcat board. On the bobcat board, the main board cpld issues the shutdown request to the dpu cpld. the dpu cpld issues that request to ARM via GPIO6 and ARM should trigger a graceful shutdown and set the ARM boot progress to 6. [Test Case] * Test shutdown on Bobcat via CPLD command. [Regression Potential] * no known regression as the OCP3.0 board was discontinued. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2058498 Title: pwr-mlxbf: support Bobcat graceful shutdown via gpio6 Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] OCP3.0 project was discontinued and canceled so all stale code related to that was removed. The HID MLNXBF29 is used now for triggering a graceful shutdown for the Bobcat board. On the bobcat board, the main board cpld issues the shutdown request to the dpu cpld. the dpu cpld issues that request to ARM via GPIO6 and ARM should trigger a graceful shutdown and set the ARM boot progress to 6. [Fix] The HID MLNXBF29 is used now for triggering a graceful shutdown for the Bobcat board. On the bobcat board, the main board cpld issues the shutdown request to the dpu cpld. the dpu cpld issues that request to ARM via GPIO6 and ARM should trigger a graceful shutdown and set the ARM boot progress to 6. [Test Case] * Test shutdown on Bobcat via CPLD command. [Regression Potential] * no known regression as the OCP3.0 board was discontinued. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2058498/+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 2058497] [NEW] package linux-image-6.5.0-1016-oem (not installed) failed to install/upgrade: installed linux-image-6.5.0-1016-oem package pre-removal script subprocess returned
Public bug reported: I did not know this package was being installed. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-1016-oem (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Mar 16 21:13:08 2024 DuplicateSignature: package:linux-image-6.5.0-1016-oem:(not installed) Removing linux-image-6.5.0-1016-oem (6.5.0-1016.17) ... E: Aborting removal of the running kernel dpkg: error processing package linux-image-6.5.0-1016-oem (--remove): installed linux-image-6.5.0-1016-oem package pre-removal script subprocess returned error exit status 1 ErrorMessage: installed linux-image-6.5.0-1016-oem package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2024-03-11 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.11 SourcePackage: linux-signed-oem-6.5 Title: package linux-image-6.5.0-1016-oem (not installed) failed to install/upgrade: installed linux-image-6.5.0-1016-oem package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058497 Title: package linux-image-6.5.0-1016-oem (not installed) failed to install/upgrade: installed linux-image-6.5.0-1016-oem package pre- removal script subprocess returned error exit status 1 Status in linux-signed-oem-6.5 package in Ubuntu: New Bug description: I did not know this package was being installed. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-1016-oem (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Mar 16 21:13:08 2024 DuplicateSignature: package:linux-image-6.5.0-1016-oem:(not installed) Removing linux-image-6.5.0-1016-oem (6.5.0-1016.17) ... E: Aborting removal of the running kernel dpkg: error processing package linux-image-6.5.0-1016-oem (--remove): installed linux-image-6.5.0-1016-oem package pre-removal script subprocess returned error exit status 1 ErrorMessage: installed linux-image-6.5.0-1016-oem package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2024-03-11 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.3 apt 2.4.11 SourcePackage: linux-signed-oem-6.5 Title: package linux-image-6.5.0-1016-oem (not installed) failed to install/upgrade: installed linux-image-6.5.0-1016-oem package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-6.5/+bug/2058497/+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 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
Got same issue -- 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/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello there, I submit this request to improve the gaming experience in ubuntu for all users. Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just not starting because the vm_max_map_count is locked at 65530. If we change this value to a value > 20, all games are working well and there is no bug linked to maps. Some others distribution like Fedora or Pop OS, have already made the change few month before. It's time to Ubuntu to makes the change also. Thanks in advance for applying this request. How to make this change : One file to modify : /etc/sysctl.conf Add this line : vm.max_map_count=2147483642 Save Reboot and enjoy Best Regards Vinceff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2057792/+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 2052961] Re: Error: OCI runtime error: crun: chmod : Operation not supported
** Also affects: crun (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2052961 Title: Error: OCI runtime error: crun: chmod : Operation not supported Status in crun package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-hwe-6.5 package in Ubuntu: Confirmed Bug description: There appears to be a regression due to a "change in the kernel" in which, as of "commit 5d1f903f75a80daa4dfb3d84e114ec8ecbf29956 in the kernel, present in a release since Linux 6.6 doesn't allow anymore to change the mode of a symlink, so just ignore the failure." Quote source: https://github.com/containers/crun/pull/1309#issue-1908555328 A fix for crun was committed as of v1.9.1, and I believe should be backported: https://github.com/containers/crun/commit/be16ee75ff8574698250352302e9d5496d888d69 I am attaching the apt/history.log file, which I believe reveals the kernel update that happened since February 8th that triggered the regression. This has been reproducible for me by using podman in combination with the "kind" tool (https://github.com/kubernetes- sigs/kind/releases/tag/v0.21.0 in this case) to attempt to start a Kubernetes cluster within a container. By running "kind create cluster" it is using the container image "kindest/node:v1.29.1" which triggers the error: "Error: OCI runtime error: crun: chmod `run/shm`: Operation not supported" ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: crun 1.8.5-1 ProcVersionSignature: Ubuntu 6.5.0-17.17-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 12 12:07:09 2024 InstallationDate: Installed on 2022-09-19 (511 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=screen-256color XDG_RUNTIME_DIR= SourcePackage: crun UpgradeStatus: Upgraded to mantic on 2023-11-07 (98 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crun/+bug/2052961/+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 2057454] Re: [Ubuntu 24.04] Failed to Install Ubuntu 24.04 with ISO attached to VirtualMedia of OSM.
** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Also affects: linux (Ubuntu Noble) Importance: Critical 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/2057454 Title: [Ubuntu 24.04] Failed to Install Ubuntu 24.04 with ISO attached to VirtualMedia of OSM. Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: On Dell PowerEdge system unable to complete Installation of Ubuntu 24.04 using ISO mounted by Virtual media option. Steps to Reproduce: - 1. Attach Ubuntu 24.04 ISO to RFS path of Virtual media. 2. Boot to F11 and select the Virtual Optical drive from Oneshot UEFI boot menu. 3. Begin the Ubuntu24.04 Installation. 4. Installation was failed. Expected Results: - The Installation should be successful without any errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057454/+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 2058357] Re: noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-lrg Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lrs Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + built: + from: 84640a198fbc9fca + route-entry: 1 kernel-stable-master-bug: 2058221 packages: - generate: linux-generate-oem-6.8 - lrg: linux-restricted-generate-oem-6.8 - lrm: linux-restricted-modules-oem-6.8 - lrs: linux-restricted-signatures-oem-6.8 - main: linux-oem-6.8 - meta: linux-meta-oem-6.8 - signed: linux-signed-oem-6.8 - phase: Holding before Packaging - phase-changed: Tuesday, 19. March 2024 09:51 UTC + generate: linux-generate-oem-6.8 + lrg: linux-restricted-generate-oem-6.8 + lrm: linux-restricted-modules-oem-6.8 + lrs: linux-restricted-signatures-oem-6.8 + main: linux-oem-6.8 + meta: linux-meta-oem-6.8 + signed: linux-signed-oem-6.8 + phase: Packaging + phase-changed: Wednesday, 20. March 2024 14:12 UTC reason: - :prepare-packages: Holding -b Not ready to be cranked - prepare-package: Holding -- waiting for parent tracker + :prepare-packages: Pending -- building in ppa (generate:M signed:M) + prepare-package: Stalled -- tag not published + prepare-package-generate: Stalled -- package not uploaded + prepare-package-lrm: Stalled -- tag not published + prepare-package-meta: Stalled -- tag not published + prepare-package-signed: Stalled -- tag not published and package not + uploaded variant: debs + versions: + lrm: 6.8.0-1001.1 + main: 6.8.0-1001.1 + meta: 6.8.0-1001.1 ~~: - tracker: - last-message: '2024-03-19 09:46:02.148495+00:00' + clamps: + self: 6.8.0-1001.1 + tracker: + last-message: '2024-03-19 09:46:02.148495+00:00' -- 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/2058357 Title: noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow abi-testing series: New Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow boot-testing series: New Status in Kernel SRU Workflow new-review series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-generate series: In Progress Status in Kernel SRU Workflow prepare-package-lrg series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-lrs series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow sru-review series: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- built: from: 84640a198fbc9fca route-entry: 1 kernel-stable-master-bug: 2058221 packages: generate: linux-generate-oem-6.8 lrg: linux-restricted-generate-oem-6.8 lrm: linux-restricted-modules-oem-6.8 lrs: linux-restricted-signatures-oem-6.8 main: linux-oem-6.8 meta: linux-meta-oem-6.8 signed: linux-signed-oem-6.8 phase: Packaging phase-changed: Wednesday, 20. March 2024 14:12 UTC reason: :prepare-packages: Pending -- building in ppa (generate:M signed:M) prepare-package: Stalled -- tag not published prepare-package-generate: Stalled -- package not uploaded prepare-package-lrm: Stalled -- tag not published prepare-package-meta: Stalled -- tag not published prepare-package-signed: Stalled -- tag not published and package not uploaded variant: debs versions: lrm: 6.8.0-1001.1 main: 6.8.0-1001.1 meta: 6.8.0-1001.1 ~~: clamps: self: 6.8.0-1001.1 tracker: last-message: '2024-03-19 09:46:02.148495+00:00' To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/2058357/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe
[Kernel-packages] [Bug 2058357] Re: noble/linux-oem-6.8: -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: - https://wiki.ubuntu.com/Kernel/kernel-sru-workflow + https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 2058221 packages: - generate: linux-generate-oem-6.8 - lrg: linux-restricted-generate-oem-6.8 - lrm: linux-restricted-modules-oem-6.8 - lrs: linux-restricted-signatures-oem-6.8 - main: supported - meta: linux-meta-oem-6.8 - signed: linux-signed-oem-6.8 + generate: linux-generate-oem-6.8 + lrg: linux-restricted-generate-oem-6.8 + lrm: linux-restricted-modules-oem-6.8 + lrs: linux-restricted-signatures-oem-6.8 + main: linux-oem-6.8 + meta: linux-meta-oem-6.8 + signed: linux-signed-oem-6.8 phase: Holding before Packaging phase-changed: Tuesday, 19. March 2024 09:51 UTC reason: - :prepare-packages: Holding -b Not ready to be cranked - prepare-package: Holding -- waiting for parent tracker + :prepare-packages: Holding -b Not ready to be cranked + prepare-package: Holding -- waiting for parent tracker variant: debs ~~: - tracker: - last-message: '2024-03-19 09:46:02.148495+00:00' + tracker: + last-message: '2024-03-19 09:46:02.148495+00:00' ** Summary changed: - noble/linux-oem-6.8: -proposed tracker + noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-generate Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-generate Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-lrg Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrg Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-lrs Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrs Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen (tjaalton) -- 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/2058357 Title: noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow abi-testing series: New Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow boot-testing series: New Status in Kernel SRU Workflow new-review series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-generate series: In Progress Status in Kernel SRU Workflow prepare-package-lrg series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-lrs series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow sru-review series: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- built: from: 84640a198fbc9fca route-entry: 1 kernel-stable-master-bug: 2058221 packages: generate: linux-generate-oem-6.8 lrg: linux-restricted-generate-oem-6.8 lrm: linux-restricted-modules-oem-6.8 lrs: linux-restricted-signatures-oem-6.8 main:
[Kernel-packages] [Bug 2058488] [NEW] [SPR] performance: Remove operations to mm_struct out of file mapping lock's critical section
Public bug reported: This is a public version of https://bugs.launchpad.net/bugs/2034985 Backport: 6852c46c783d mm/mmap: move vma operations to mm_struct out of the critical section of file mapping lock (merged upstream in 6.6) to jammy [Impact] The msg_bytes and msg_hdrs atomic counters are frequently updated when IPC msg queue is in heavy use, causing heavy cache bounce and overhead. Change them to percpu_counter greatly improve the performance. Since there is one percpu struct per namespace, additional memory cost is minimal. Reading of the count done in msgctl call, which is infrequent. So the need to sum up the counts in each CPU is infrequent. [Fix] Backport: 6852c46c783d mm/mmap: move vma operations to mm_struct out of the critical section of file mapping lock [Test] I have tested this code. [Where problems could occur] TODO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: intel ** Also affects: linux (Ubuntu Jammy) 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/2058488 Title: [SPR] performance: Remove operations to mm_struct out of file mapping lock's critical section Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034985 Backport: 6852c46c783d mm/mmap: move vma operations to mm_struct out of the critical section of file mapping lock (merged upstream in 6.6) to jammy [Impact] The msg_bytes and msg_hdrs atomic counters are frequently updated when IPC msg queue is in heavy use, causing heavy cache bounce and overhead. Change them to percpu_counter greatly improve the performance. Since there is one percpu struct per namespace, additional memory cost is minimal. Reading of the count done in msgctl call, which is infrequent. So the need to sum up the counts in each CPU is infrequent. [Fix] Backport: 6852c46c783d mm/mmap: move vma operations to mm_struct out of the critical section of file mapping lock [Test] I have tested this code. [Where problems could occur] TODO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058488/+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 2058485] Re: [ICX] [SPR] [ipc/msg] performance: Mitigate the lock contention with percpu counter
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: intel ** Also affects: linux (Ubuntu Jammy) 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/2058485 Title: [ICX] [SPR] [ipc/msg] performance: Mitigate the lock contention with percpu counter Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Bug description: This is a public version of https://bugs.launchpad.net/bugs/2034980 Backport: ipc/msg: mitigate the lock contention with percpu counter (merged upstream in 6.1) to jammy [Impact] The msg_bytes and msg_hdrs atomic counters are frequently updated when IPC msg queue is in heavy use, causing heavy cache bounce and overhead. Change them to percpu_counter greatly improve the performance. Since there is one percpu struct per namespace, additional memory cost is minimal. Reading of the count done in msgctl call, which is infrequent. So the need to sum up the counts in each CPU is infrequent. [Fix] Backport: 72d1e611082e ipc/msg: mitigate the lock contention with percpu counter [Test Plan] I have tested this code. [Where problems could occur] TODO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058485/+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 2058481] Re: [SPR] Networking performance fix for concurrency with the dst_entry data structure
** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => Thibf (thibf) -- 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/2058481 Title: [SPR] Networking performance fix for concurrency with the dst_entry data structure Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Bug description: This is a public version of https://bugs.launchpad.net/bugs/2028897 Backport: bc9d3a9f2afc (net: dst: Switch to rcuref_t reference counting, 2023-03-23) d288a162dd1c (net: dst: Prevent false sharing vs. dst_entry:: __refcnt, 2023-03-23) e5ab9eff46b0 (atomics: Provide atomic_add_negative() variants, 2023-03-23) ee1ee6db0779 (atomics: Provide rcuref - scalable reference counting, 2023-03-23) merged in 6.4 to jammy. [Impact] Address a bottleneck in the networking code related to struct dst_entry reference count, which results in networking performance loss with large number of connections, by adding rcuref as a scalable alternative solution. Developers report in the patch: The overall gain of both changes for localhost memtier ranges from 1.2X to 3.2X and from +2% to %5% range for networked operations on a 1Gb connection. A micro benchmark which enforces maximized concurrency shows a gain between 1.2X and 4.7X. [Fix] Upstream patch: bc9d3a9f2afc (net: dst: Switch to rcuref_t reference counting, 2023-03-23) d288a162dd1c (net: dst: Prevent false sharing vs. dst_entry:: __refcnt, 2023-03-23) e5ab9eff46b0 (atomics: Provide atomic_add_negative() variants, 2023-03-23) ee1ee6db0779 (atomics: Provide rcuref - scalable reference counting, 2023-03-23) [Test Plan] I have tested this code. [Where problems could occur] TODO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058481/+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 2058483] [NEW] touchpad not working
Public bug reported: The touchpad is not in the xinput list and it doesn't work. I'm using hp pavilion 15 ec1021nl ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 20 14:21:02 2024 InstallationDate: Installed on 2024-03-20 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2058483 Title: touchpad not working Status in linux-signed-hwe-6.5 package in Ubuntu: New Bug description: The touchpad is not in the xinput list and it doesn't work. I'm using hp pavilion 15 ec1021nl ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-26-generic 6.5.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 20 14:21:02 2024 InstallationDate: Installed on 2024-03-20 (0 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 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-6.5/+bug/2058483/+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 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
Non exhaustive list of games impacted by this bug: - Dayz - Hogwarts legacy - Counter-Strike 2 - Payday 2 - Star Citizen - Thanks. -- 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/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello there, I submit this request to improve the gaming experience in ubuntu for all users. Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just not starting because the vm_max_map_count is locked at 65530. If we change this value to a value > 20, all games are working well and there is no bug linked to maps. Some others distribution like Fedora or Pop OS, have already made the change few month before. It's time to Ubuntu to makes the change also. Thanks in advance for applying this request. How to make this change : One file to modify : /etc/sysctl.conf Add this line : vm.max_map_count=2147483642 Save Reboot and enjoy Best Regards Vinceff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2057792/+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 2058334] Re: package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to install/upgrade: installed linux-headers-6.5.0-26-generic package post-installation script subprocess r
Thank you for the help! I was thinking that it's a global issue.. but it
was my own.. Sorry for bothering.. you are doing a great job!
--
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/2058334
Title:
package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to
install/upgrade: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
Invalid
Bug description:
I got the error after login to the gnome
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-26-generic 6.5.0-26.26
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Mar 18 17:33:44 2024
ErrorMessage: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2021-12-26 (813 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-26-generic
root=UUID=336f83fe-a568-4a38-b14f-1d0964399570 ro rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau nvidia-drm.modset=1 migrations=off mitigations=off
quiet splash rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
nvidia-drm.modset=1 migrations=off mitigations=off vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: /usr/bin/python3.11, Python 3.11.6, python-is-python3, 3.11.4-1
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
RfKill:
SourcePackage: linux
Title: package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to
install/upgrade: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2023-10-14 (157 days ago)
dmi.bios.date: 09/12/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F27
dmi.board.asset.tag: Default string
dmi.board.name: Z690 GAMING X DDR4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF27:bd09/12/2023:br5.27:svnGigabyteTechnologyCo.,Ltd.:pnZ690GAMINGXDDR4:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ690GAMINGXDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Z690 MB
dmi.product.name: Z690 GAMING X DDR4
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058334/+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 2058481] [NEW] [SPR] Networking performance fix for concurrency with the dst_entry data structure
Public bug reported: This is a public version of https://bugs.launchpad.net/bugs/2028897 Backport: bc9d3a9f2afc (net: dst: Switch to rcuref_t reference counting, 2023-03-23) d288a162dd1c (net: dst: Prevent false sharing vs. dst_entry:: __refcnt, 2023-03-23) e5ab9eff46b0 (atomics: Provide atomic_add_negative() variants, 2023-03-23) ee1ee6db0779 (atomics: Provide rcuref - scalable reference counting, 2023-03-23) merged in 6.4 to jammy. [Impact] Address a bottleneck in the networking code related to struct dst_entry reference count, which results in networking performance loss with large number of connections, by adding rcuref as a scalable alternative solution. Developers report in the patch: The overall gain of both changes for localhost memtier ranges from 1.2X to 3.2X and from +2% to %5% range for networked operations on a 1Gb connection. A micro benchmark which enforces maximized concurrency shows a gain between 1.2X and 4.7X. [Fix] Upstream patch: bc9d3a9f2afc (net: dst: Switch to rcuref_t reference counting, 2023-03-23) d288a162dd1c (net: dst: Prevent false sharing vs. dst_entry:: __refcnt, 2023-03-23) e5ab9eff46b0 (atomics: Provide atomic_add_negative() variants, 2023-03-23) ee1ee6db0779 (atomics: Provide rcuref - scalable reference counting, 2023-03-23) [Test Plan] I have tested this code. [Where problems could occur] TODO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) 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/2058481 Title: [SPR] Networking performance fix for concurrency with the dst_entry data structure Status in linux package in Ubuntu: New Status in linux source package in Jammy: New Bug description: This is a public version of https://bugs.launchpad.net/bugs/2028897 Backport: bc9d3a9f2afc (net: dst: Switch to rcuref_t reference counting, 2023-03-23) d288a162dd1c (net: dst: Prevent false sharing vs. dst_entry:: __refcnt, 2023-03-23) e5ab9eff46b0 (atomics: Provide atomic_add_negative() variants, 2023-03-23) ee1ee6db0779 (atomics: Provide rcuref - scalable reference counting, 2023-03-23) merged in 6.4 to jammy. [Impact] Address a bottleneck in the networking code related to struct dst_entry reference count, which results in networking performance loss with large number of connections, by adding rcuref as a scalable alternative solution. Developers report in the patch: The overall gain of both changes for localhost memtier ranges from 1.2X to 3.2X and from +2% to %5% range for networked operations on a 1Gb connection. A micro benchmark which enforces maximized concurrency shows a gain between 1.2X and 4.7X. [Fix] Upstream patch: bc9d3a9f2afc (net: dst: Switch to rcuref_t reference counting, 2023-03-23) d288a162dd1c (net: dst: Prevent false sharing vs. dst_entry:: __refcnt, 2023-03-23) e5ab9eff46b0 (atomics: Provide atomic_add_negative() variants, 2023-03-23) ee1ee6db0779 (atomics: Provide rcuref - scalable reference counting, 2023-03-23) [Test Plan] I have tested this code. [Where problems could occur] TODO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058481/+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 2058480] [NEW] [Ubuntu 22.04.4/linux-image-6.5.0-1014-aws] Kernel outputs "UBSAN: array-index-out-of-bounds in /build/linux-aws-6.5-4tw9h1/linux-aws-6.5-6.5.0/drivers/net/xen-ne
Public bug reported: A newly launched Ubuntu 22.04.4 EC2 instance outputs "UBSAN: array- index-out-of-bounds in /build/linux-aws-6.5-4tw9h1/linux- aws-6.5-6.5.0/drivers/net/xen-netfront.c:349:9" multiple times, especially during boot. Reproducing step: - Launch an Ubuntu 22.04.4 EC2 instance with the instance type t2.*. Additional Info: - Please use t2 instance to make sure to use xen-netfront as a network device. - This messages similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058477, which is related to netvsc.c ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "apport.linux-image-6.5.0-1014-aws.gytyyqmu.apport" https://bugs.launchpad.net/bugs/2058480/+attachment/5757550/+files/apport.linux-image-6.5.0-1014-aws.gytyyqmu.apport -- 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/2058480 Title: [Ubuntu 22.04.4/linux-image-6.5.0-1014-aws] Kernel outputs "UBSAN: array-index-out-of-bounds in /build/linux-aws-6.5-4tw9h1/linux- aws-6.5-6.5.0/drivers/net/xen-netfront.c:349:9 " multiple times, especially during boot Status in linux package in Ubuntu: New Bug description: A newly launched Ubuntu 22.04.4 EC2 instance outputs "UBSAN: array- index-out-of-bounds in /build/linux-aws-6.5-4tw9h1/linux- aws-6.5-6.5.0/drivers/net/xen-netfront.c:349:9" multiple times, especially during boot. Reproducing step: - Launch an Ubuntu 22.04.4 EC2 instance with the instance type t2.*. Additional Info: - Please use t2 instance to make sure to use xen-netfront as a network device. - This messages similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058477, which is related to netvsc.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058480/+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 2058477] [NEW] [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux-hwe-6.5-6.5.0/drivers/net/hyper
Public bug reported: Overview: A newly installed Ubuntu Server 22.04.4 on a Hyper-V virtual machine outputs error message "UBSAN: array-index-out-of-bounds in /build/linux- hwe-6.5-34pCLi/linux-hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1446:41" multiple times, especially during boot. Reproducing steps: 1. Download ubuntu-22.04.4-live-server-amd64.iso 2. Create a Hyper-V virtual machine. 3. Install Ubuntu 22.04.4 Server on the VM with the downloaded iso normally. 4. Boot the machine. Additional Information: - Host machine: Windows 10 Pro 22H2 OS Build 19045.3758 - Hyper-V configuration version: 9.0 - The error message "UBSAN: array-index-out-of-bounds" is similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008157, but the drivers are different. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "apport.linux-image-6.5.0-26-generic.4wdzb1mh.apport" https://bugs.launchpad.net/bugs/2058477/+attachment/5757540/+files/apport.linux-image-6.5.0-26-generic.4wdzb1mh.apport ** Summary changed: - [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux-hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1445:41 + [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux-hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1445:41" multiple times, especially during boot. -- 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/2058477 Title: [Ubuntu 22.04.4/linux-image-6.5.0-26-generic] Kernel output "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux- hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1445:41" multiple times, especially during boot. Status in linux package in Ubuntu: New Bug description: Overview: A newly installed Ubuntu Server 22.04.4 on a Hyper-V virtual machine outputs error message "UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-34pCLi/linux- hwe-6.5-6.5.0/drivers/net/hyperv/netvsc.c:1446:41" multiple times, especially during boot. Reproducing steps: 1. Download ubuntu-22.04.4-live-server-amd64.iso 2. Create a Hyper-V virtual machine. 3. Install Ubuntu 22.04.4 Server on the VM with the downloaded iso normally. 4. Boot the machine. Additional Information: - Host machine: Windows 10 Pro 22H2 OS Build 19045.3758 - Hyper-V configuration version: 9.0 - The error message "UBSAN: array-index-out-of-bounds" is similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008157, but the drivers are different. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058477/+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 2058357] Re: noble/linux-oem-6.8: -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 2058221 packages: generate: linux-generate-oem-6.8 lrg: linux-restricted-generate-oem-6.8 lrm: linux-restricted-modules-oem-6.8 lrs: linux-restricted-signatures-oem-6.8 main: supported meta: linux-meta-oem-6.8 signed: linux-signed-oem-6.8 phase: Holding before Packaging phase-changed: Tuesday, 19. March 2024 09:51 UTC reason: :prepare-packages: Holding -b Not ready to be cranked prepare-package: Holding -- waiting for parent tracker variant: debs ~~: - clamps: - self: 6.8.0-1001.1 tracker: last-message: '2024-03-19 09:46:02.148495+00:00' -- 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/2058357 Title: noble/linux-oem-6.8: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow abi-testing series: New Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow boot-testing series: New Status in Kernel SRU Workflow new-review series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-generate series: New Status in Kernel SRU Workflow prepare-package-lrg series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-lrs series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow sru-review series: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 2058221 packages: generate: linux-generate-oem-6.8 lrg: linux-restricted-generate-oem-6.8 lrm: linux-restricted-modules-oem-6.8 lrs: linux-restricted-signatures-oem-6.8 main: supported meta: linux-meta-oem-6.8 signed: linux-signed-oem-6.8 phase: Holding before Packaging phase-changed: Tuesday, 19. March 2024 09:51 UTC reason: :prepare-packages: Holding -b Not ready to be cranked prepare-package: Holding -- waiting for parent tracker variant: debs ~~: tracker: last-message: '2024-03-19 09:46:02.148495+00:00' To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/2058357/+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 2058357] Re: noble/linux-oem-6.8: -proposed tracker
** Summary changed: - noble/linux-oem-6.8: 6.8.0-1001.1 -proposed tracker + noble/linux-oem-6.8: -proposed tracker -- 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/2058357 Title: noble/linux-oem-6.8: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow abi-testing series: New Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow boot-testing series: New Status in Kernel SRU Workflow new-review series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-generate series: New Status in Kernel SRU Workflow prepare-package-lrg series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-lrs series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow sru-review series: New Status in linux package in Ubuntu: New Status in linux source package in Noble: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 2058221 packages: generate: linux-generate-oem-6.8 lrg: linux-restricted-generate-oem-6.8 lrm: linux-restricted-modules-oem-6.8 lrs: linux-restricted-signatures-oem-6.8 main: supported meta: linux-meta-oem-6.8 signed: linux-signed-oem-6.8 phase: Holding before Packaging phase-changed: Tuesday, 19. March 2024 09:51 UTC reason: :prepare-packages: Holding -b Not ready to be cranked prepare-package: Holding -- waiting for parent tracker variant: debs ~~: clamps: self: 6.8.0-1001.1 tracker: last-message: '2024-03-19 09:46:02.148495+00:00' To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/2058357/+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 2054366] Re: Fix backported kria device tree changes
** Changed in: linux-xilinx-zynqmp (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2054366 Title: Fix backported kria device tree changes Status in linux-xilinx-zynqmp package in Ubuntu: Fix Released Status in linux-xilinx-zynqmp source package in Jammy: Fix Released Bug description: [ Impact ] * Kria device tree's were backported from Xilinx's 6.1 tree in order to add support for the KD240 platform (https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2046280) . Testing had previously been done a development branch with non-upstreamable patches. 3 issues were introduced to the KD240 image that was not present on the development branch. * Since all Xilinx device tree's are so interdependent all Kria and ZCU device trees were updated including certified platforms. [ Test Plan ] * QA will run certification testing on the KD240 platform * Normal certification testing will be run on all other certified platforms [ Where problems could occur ] * This impacts the device tree for certified Xilinx platforms which could break any of the device touched by the change. [ Fixes ] * 6.1 compatible string and interrupt-name for gpu: gpu@fd4b incorrectly backported * 6.1 compatible string for ethernet@ff0b incorrectly backported * dwc3_[01] quirks incorrectly updated for 6.1 * xilinx_ams field incorrectly updated. [ Other info ] * Private launchpad bugs that contain detail on the KD240 regressions: https://bugs.launchpad.net/limerick/+bug/2051228 https://bugs.launchpad.net/limerick/+bug/2051224 https://bugs.launchpad.net/limerick/+bug/2051201 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2054366/+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 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
Can confirm some games crash due to VM_max_map_count being set too low by default. -- 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/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello there, I submit this request to improve the gaming experience in ubuntu for all users. Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just not starting because the vm_max_map_count is locked at 65530. If we change this value to a value > 20, all games are working well and there is no bug linked to maps. Some others distribution like Fedora or Pop OS, have already made the change few month before. It's time to Ubuntu to makes the change also. Thanks in advance for applying this request. How to make this change : One file to modify : /etc/sysctl.conf Add this line : vm.max_map_count=2147483642 Save Reboot and enjoy Best Regards Vinceff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2057792/+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 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
I confirm this! Some games might crash low VM_max_map_count is set too low. -- 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/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello there, I submit this request to improve the gaming experience in ubuntu for all users. Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just not starting because the vm_max_map_count is locked at 65530. If we change this value to a value > 20, all games are working well and there is no bug linked to maps. Some others distribution like Fedora or Pop OS, have already made the change few month before. It's time to Ubuntu to makes the change also. Thanks in advance for applying this request. How to make this change : One file to modify : /etc/sysctl.conf Add this line : vm.max_map_count=2147483642 Save Reboot and enjoy Best Regards Vinceff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2057792/+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 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
I can confirm this! Some games do crash because of a to low VM_max_map_count. This change will improve the gaming experience on Ubuntu and thus would be a nice one to have in the next LTS release. -- 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/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello there, I submit this request to improve the gaming experience in ubuntu for all users. Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just not starting because the vm_max_map_count is locked at 65530. If we change this value to a value > 20, all games are working well and there is no bug linked to maps. Some others distribution like Fedora or Pop OS, have already made the change few month before. It's time to Ubuntu to makes the change also. Thanks in advance for applying this request. How to make this change : One file to modify : /etc/sysctl.conf Add this line : vm.max_map_count=2147483642 Save Reboot and enjoy Best Regards Vinceff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2057792/+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 2057792] Re: Some Games are crashing linked to a vm_max_map_count too low
Many crash because VM_max_count two low. -- 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/2057792 Title: Some Games are crashing linked to a vm_max_map_count too low Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello there, I submit this request to improve the gaming experience in ubuntu for all users. Today, Hogwarts Legacy, Star Citizen and few more games are crashing or just not starting because the vm_max_map_count is locked at 65530. If we change this value to a value > 20, all games are working well and there is no bug linked to maps. Some others distribution like Fedora or Pop OS, have already made the change few month before. It's time to Ubuntu to makes the change also. Thanks in advance for applying this request. How to make this change : One file to modify : /etc/sysctl.conf Add this line : vm.max_map_count=2147483642 Save Reboot and enjoy Best Regards Vinceff To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2057792/+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 2058191] Re: Getting SIGSEGV and SIGILL in many programs
Unfortunately those traces don't say much without the debugging symbols. If it happens also with the mainline kernel we should see similar bugs reported upstream, that's why I'm not very convinced about this being a kernel issue. More likely a library issue, considering that it happens with different applications (or interactions between kernel and a particular library). You mention that the last kernel that was working was like a 6.5? There's a huge delta between 6.5 and 6.8. Maybe we could try to restrict this range a bit more... At https://kernel.ubuntu.com/mainline/ you can find the debs of pretty much all the mainline kernel versions, maybe you could also test some kernels between 6.5 and 6.8 (assuming you can easily reproduce the problem), in order to restrict the range of changes and have a better idea where to look. Thanks! -- 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/2058191 Title: Getting SIGSEGV and SIGILL in many programs Status in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Okay, recently I upgraded to 24.04. I'm getting some SIGSEGV and SIGILLs from time to time. Sometimes the entire computer freezes and i can't even turn down unless i hold the power button for 5 secs. I tought it could be the kernel version, so I upgraded from Ubuntu's 6.8.0-11.11+1 to mainline 6.8.1. However, it didn't fix. Here are some softwares i got SIGSEGV or SIGILLs: - code-insiders (vscode) - brave (Brave browser) - bun (node.js alternative) - node.js I know i should upload more logs, but I didn't find the errors in syslog or journalctl. $ lsb_release -rd - No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+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 2058452] Re: Support USB serial port for Dell DW5826e WWAN
** Also affects: linux
Importance: Undecided
Status: New
** No longer affects: linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2058452
Title:
Support USB serial port for Dell DW5826e WWAN
Status in HWE Next:
New
Status in linux package in Ubuntu:
New
Status in linux-oem-6.5 package in Ubuntu:
New
Bug description:
[SRU Justification]
[Impact]
Missing usb serial interface for Dell DW5826e.
[Fix]
* commit 129690fb229a ("USB: serial: qcserial: add new usb-id for Dell
Wireless DW5826e
"): in v6.9-rc1
[Test Case]
1. check system with USB\VID_413C_8217 creates corresponding tty
port
[Where problems could occur]
The commit adds new device ID only, it won't impact devices which are
supported originally.
[Other Info]
Upstream MP:
https://github.com/torvalds/linux/commit/129690fb229a20b6e563a77a2c85266acecf20bc
Dell new platform with the device will be enabled by linux-oem-6.5.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2058452/+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 2058452] [NEW] Support USB serial port for Dell DW5826e WWAN
Public bug reported:
[SRU Justification]
[Impact]
Missing usb serial interface for Dell DW5826e.
[Fix]
* commit 129690fb229a ("USB: serial: qcserial: add new usb-id for Dell Wireless
DW5826e
"): in v6.9-rc1
[Test Case]
1. check system with USB\VID_413C_8217 creates corresponding tty
port
[Where problems could occur]
The commit adds new device ID only, it won't impact devices which are
supported originally.
[Other Info]
Upstream MP:
https://github.com/torvalds/linux/commit/129690fb229a20b6e563a77a2c85266acecf20bc
Dell new platform with the device will be enabled by linux-oem-6.5.
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Affects: linux-oem-6.5 (Ubuntu)
Importance: Undecided
Assignee: Kai-Chuan Hsieh (kchsieh)
Status: New
** Changed in: linux-oem-6.5 (Ubuntu)
Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh)
** Also affects: hwe-next
Importance: Undecided
Status: New
** Also affects: linux
Importance: Undecided
Status: New
** No longer affects: linux
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2058452
Title:
Support USB serial port for Dell DW5826e WWAN
Status in HWE Next:
New
Status in linux package in Ubuntu:
New
Status in linux-oem-6.5 package in Ubuntu:
New
Bug description:
[SRU Justification]
[Impact]
Missing usb serial interface for Dell DW5826e.
[Fix]
* commit 129690fb229a ("USB: serial: qcserial: add new usb-id for Dell
Wireless DW5826e
"): in v6.9-rc1
[Test Case]
1. check system with USB\VID_413C_8217 creates corresponding tty
port
[Where problems could occur]
The commit adds new device ID only, it won't impact devices which are
supported originally.
[Other Info]
Upstream MP:
https://github.com/torvalds/linux/commit/129690fb229a20b6e563a77a2c85266acecf20bc
Dell new platform with the device will be enabled by linux-oem-6.5.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2058452/+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 2049569] Re: Enable the mic-mute led on Dell MTL laptops
@mschiu77 the firmware-sof provided in your PPA works! The LEDs can
toggle accordingly after installation.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049569
Title:
Enable the mic-mute led on Dell MTL laptops
Status in HWE Next:
New
Status in firmware-sof package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.5 package in Ubuntu:
Invalid
Status in firmware-sof source package in Jammy:
Fix Committed
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.5 source package in Jammy:
Fix Released
Status in firmware-sof source package in Noble:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.5 source package in Noble:
Invalid
Bug description:
[SRU Justifications]
== kernels ==
[Impact]
On Dell's Precision 3550, Intel MTL platform, the MIC-Mute function is
working but the LED(on F4) state is not changed accordingly.
[Fix]
There's no problem on the same series on RPL platform. It needs MTL specific
SoF driver and controls to support the registered mixer switch. It requires the
patches in
https://lore.kernel.org/all/20230919103115.30783-1-peter.ujfal...@linux.intel.com/
and
https://lore.kernel.org/all/20230814232325.86397-1-pierre-louis.boss...@linux.intel.com/
[Test Case]
1. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD
icon.
2. The mic-mute led should be ON when mic-mute enabled, OFF when disabled.
[Where problems could occur]
It's only required for new sof-audio-pci-intel-mtl driver. The impact should
be restricting.
== firmware-sof ==
[Impact]
The mic-mute led not working on Intel MTL powered laptops.
[Fix]
For firmware-sof, it required the upstream commit fdc884baa4b3 ("Add
sof-ipc4-v2.8.1/mtl/, intel-signed + community") and the
sof-hda-generic-2ch.tplg from v2.8.1 to make sure the ipc4 topology and control
matches with the updated driver.
[Test Case]
1. enable -proposed pocket and install firmware-sof-signed
2. press mic-mute hot-key and check if mic-mute is enabled or not by the OSD
icon.
[Where problems could occur]
The updated sof-mtl.ri and the sof-hda-generic-2ch.tplg are shared by all
Intel MTL platforms. Need to verify audio function on MTL enpowered machines.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2049569/+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
Re: [Kernel-packages] [Bug 2058191] Re: Getting SIGSEGV and SIGILL in many programs
Yes, I have. The most frequent ones are bun (node.js alternative) and brave. On Wed, Mar 20, 2024, 4:50 AM Andrea Righi <2058...@bugs.launchpad.net> wrote: > Hm... honestly this looks more like a user-space / brave issue than a > kernel issue. Do you get similar SIGSEGV with other apps? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2058191 > > Title: > Getting SIGSEGV and SIGILL in many programs > > Status in Ubuntu: > New > Status in linux package in Ubuntu: > New > > Bug description: > Okay, recently I upgraded to 24.04. I'm getting some SIGSEGV and > SIGILLs from time to time. Sometimes the entire computer freezes and i > can't even turn down unless i hold the power button for 5 secs. > > I tought it could be the kernel version, so I upgraded from Ubuntu's > 6.8.0-11.11+1 to mainline 6.8.1. However, it didn't fix. > > Here are some softwares i got SIGSEGV or SIGILLs: >- code-insiders (vscode) >- brave (Brave browser) >- bun (node.js alternative) >- node.js > > I know i should upload more logs, but I didn't find the errors in > syslog or journalctl. > > $ lsb_release -rd > - > No LSB modules are available. > Description: Ubuntu Noble Numbat (development branch) > Release: 24.04 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+bug/2058191/+subscriptions > > -- 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/2058191 Title: Getting SIGSEGV and SIGILL in many programs Status in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Okay, recently I upgraded to 24.04. I'm getting some SIGSEGV and SIGILLs from time to time. Sometimes the entire computer freezes and i can't even turn down unless i hold the power button for 5 secs. I tought it could be the kernel version, so I upgraded from Ubuntu's 6.8.0-11.11+1 to mainline 6.8.1. However, it didn't fix. Here are some softwares i got SIGSEGV or SIGILLs: - code-insiders (vscode) - brave (Brave browser) - bun (node.js alternative) - node.js I know i should upload more logs, but I didn't find the errors in syslog or journalctl. $ lsb_release -rd - No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+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 2058334] Re: package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to install/upgrade: installed linux-headers-6.5.0-26-generic package post-installation script subprocess r
You have an unsupported DKMS installed that breaks the header package
installation. Please remove it:
$ dkms remove nvidia/535.161.07
--
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/2058334
Title:
package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to
install/upgrade: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
Invalid
Bug description:
I got the error after login to the gnome
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-26-generic 6.5.0-26.26
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Mar 18 17:33:44 2024
ErrorMessage: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2021-12-26 (813 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-26-generic
root=UUID=336f83fe-a568-4a38-b14f-1d0964399570 ro rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau nvidia-drm.modset=1 migrations=off mitigations=off
quiet splash rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
nvidia-drm.modset=1 migrations=off mitigations=off vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: /usr/bin/python3.11, Python 3.11.6, python-is-python3, 3.11.4-1
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
RfKill:
SourcePackage: linux
Title: package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to
install/upgrade: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2023-10-14 (157 days ago)
dmi.bios.date: 09/12/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F27
dmi.board.asset.tag: Default string
dmi.board.name: Z690 GAMING X DDR4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF27:bd09/12/2023:br5.27:svnGigabyteTechnologyCo.,Ltd.:pnZ690GAMINGXDDR4:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ690GAMINGXDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Z690 MB
dmi.product.name: Z690 GAMING X DDR4
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058334/+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 2058334] Re: package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to install/upgrade: installed linux-headers-6.5.0-26-generic package post-installation script subprocess r
Building module:
Cleaning build area...
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1
'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.5.0-26-generic
IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1
SYSSRC=/lib/modules/6.5.0-26-generic/build LD=/usr/bin/ld.bfd
CONFIG_X86_KERNEL_IBT= modules..(bad exit status: 2)
ERROR (dkms apport): There was a segmentation fault when trying to build the
module
Error! Bad return status for module build on kernel: 6.5.0-26-generic (x86_64)
Consult /var/lib/dkms/nvidia/535.161.07/build/make.log for more information.
dkms autoinstall on 6.5.0-26-generic/x86_64 failed for nvidia(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
* dkms: autoinstall for kernel 6.5.0-26-generic
...fail!
--
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/2058334
Title:
package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to
install/upgrade: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
Status in linux package in Ubuntu:
Invalid
Bug description:
I got the error after login to the gnome
ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: linux-headers-6.5.0-26-generic 6.5.0-26.26
ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Mar 18 17:33:44 2024
ErrorMessage: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
InstallationDate: Installed on 2021-12-26 (813 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-26-generic
root=UUID=336f83fe-a568-4a38-b14f-1d0964399570 ro rd.driver.blacklist=nouveau
modprobe.blacklist=nouveau nvidia-drm.modset=1 migrations=off mitigations=off
quiet splash rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
nvidia-drm.modset=1 migrations=off mitigations=off vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: /usr/bin/python3.11, Python 3.11.6, python-is-python3, 3.11.4-1
RelatedPackageVersions: grub-pc 2.12~rc1-10ubuntu4
RfKill:
SourcePackage: linux
Title: package linux-headers-6.5.0-26-generic 6.5.0-26.26 failed to
install/upgrade: installed linux-headers-6.5.0-26-generic package
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to mantic on 2023-10-14 (157 days ago)
dmi.bios.date: 09/12/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F27
dmi.board.asset.tag: Default string
dmi.board.name: Z690 GAMING X DDR4
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF27:bd09/12/2023:br5.27:svnGigabyteTechnologyCo.,Ltd.:pnZ690GAMINGXDDR4:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ690GAMINGXDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Z690 MB
dmi.product.name: Z690 GAMING X DDR4
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2058334/+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 2058191] Re: Getting SIGSEGV and SIGILL in many programs
Hm... honestly this looks more like a user-space / brave issue than a kernel issue. Do you get similar SIGSEGV with other apps? -- 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/2058191 Title: Getting SIGSEGV and SIGILL in many programs Status in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Okay, recently I upgraded to 24.04. I'm getting some SIGSEGV and SIGILLs from time to time. Sometimes the entire computer freezes and i can't even turn down unless i hold the power button for 5 secs. I tought it could be the kernel version, so I upgraded from Ubuntu's 6.8.0-11.11+1 to mainline 6.8.1. However, it didn't fix. Here are some softwares i got SIGSEGV or SIGILLs: - code-insiders (vscode) - brave (Brave browser) - bun (node.js alternative) - node.js I know i should upload more logs, but I didn't find the errors in syslog or journalctl. $ lsb_release -rd - No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+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 2051835] Re: [24.04 FEAT] Memory hotplug vmem pages (s390x)
Got marked as APPLIED by kernel team (Paolo). -- 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/2051835 Title: [24.04 FEAT] Memory hotplug vmem pages (s390x) Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: In Progress Bug description: The current s390 specific memory hotplug backend allocates 'struct page' management structures for all standby memory regions, when those standby regions are detected at ipl time. The reason for this is, that setting standby online memory is supposed to succeed especially in memory constrained environments, since lack of free memory is likely the reason why additional memory is brought online. If in such cases 'struct pages' would have to be allocated before memory could be brought up, this would likely fail, and contradict the whole rationale of memory hotplug. However pre-allocating memory for 'struct pages' comes with the downside that for highly unbalanced ratios of online/standby memory a system might even fail to ipl, because there is not enough memory available for all possible struct pages which are required for standby memory. The idea is to improve the situation: when standby memory is brought online, the memory for struct pages (and maybe other management structures) required for this new memory area should be taken from the online memory, instead of pre-allocating them. This would solve the problems with unbalanced ratios as described above. Note: there are intentions to tell customers that they should always define the maximum size of standby memory for their LPAR activation profiles. This would allow for maximum flexibility for all LPARs during runtime, given that the amount of standby memory cannot be changed during runtime. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2051835/+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 2058191] Re: Getting SIGSEGV and SIGILL in many programs
Reading my crash dump, i noticed a interesting thing. Here is the back trace: Downloading separate debug info for system-supplied DSO at 0x7ffe5ecc5000 Core was generated by `/opt/brave.com/brave/brave --type=renderer --crashpad-handler-pid=5837 --enable'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x58e16cb3b49e in ?? () [Current thread is 1 (LWP 1)] (gdb) bt #0 0x58e16cb3b49e in ?? () #1 0x7ffe5ec93780 in ?? () #2 0x in ?? () The first backtrace is located inside the brave binary as (gdb) info proc mappings says: Mapped address spaces: Start Addr End Addr Size Offset objfile [...] 0x58e16bb4b000 0x58e1778ad000 0xbd62000 0x2e1c000 /opt/brave.com/brave/brave [...] The second backtrace doesn't show in the mapped address list. But as the previous output says it's related to a "system-supplied DSO". I Googled it and a guy named fche on stackoverflow said "system-supplied-DSO means a shared library provided directly by the linux kernel such as VDSO". Is this right? If that's true, does this mean we have a big kernel issue? -- 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/2058191 Title: Getting SIGSEGV and SIGILL in many programs Status in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Okay, recently I upgraded to 24.04. I'm getting some SIGSEGV and SIGILLs from time to time. Sometimes the entire computer freezes and i can't even turn down unless i hold the power button for 5 secs. I tought it could be the kernel version, so I upgraded from Ubuntu's 6.8.0-11.11+1 to mainline 6.8.1. However, it didn't fix. Here are some softwares i got SIGSEGV or SIGILLs: - code-insiders (vscode) - brave (Brave browser) - bun (node.js alternative) - node.js I know i should upload more logs, but I didn't find the errors in syslog or journalctl. $ lsb_release -rd - No LSB modules are available. Description: Ubuntu Noble Numbat (development branch) Release: 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2058191/+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
