** Summary changed:
- [i915] ThinkPad X201 (Arrandale) screen freezes
+ [i915] ThinkPad X201 (Arrandale) screen freezes in kernels >= 6.9.0
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084055
Title:
[i915] ThinkPad X201 (Arrandale) screen freezes in kernels >= 6.9.0
Status in linux package in Ubuntu:
New
Bug description:
I have multiple issues when running Oracular on my x201 without
`nomodeset` in the command line.
* Regular freezes, either in the ISO live session or on the freshly installed system.
* Issues when running flutter based apps, like Subiquity installer, or desktop security center, stating that "The renderer could not initialize".
I've already tried to set `i915.enable_psr=0` as per bug 2000829, but
it doesn't help with either of those, although maybe the freezes come
less quickly.
ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: linux-image-6.11.0-8-generic 6.11.0-8.8
ProcVersionSignature: Ubuntu 6.11.0-8.8-generic 6.11.0
Uname: Linux 6.11.0-8-generic x86_64
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: skia 1839 F.... pipewire
/dev/snd/controlC0: skia 1846 F.... wireplumber
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 9 14:32:30 2024
InstallationDate: Installed on 2024-10-09 (0 days ago)
InstallationMedia: Ubuntu 24.10 "Oracular Oriole" - Release amd64 (20241007.2)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=ehci-pci/3p, 480M
|__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/6p, 480M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=ehci-pci/3p, 480M
|__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/8p, 480M
MachineType: LENOVO 3626FAG
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 simpledrmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.11.0-8-generic root=UUID=10b360a0-9f1f-42ff-a5c6-c37ae439df5d ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 nomodeset
RelatedPackageVersions:
linux-restricted-modules-6.11.0-8-generic N/A
linux-backports-modules-6.11.0-8-generic N/A
linux-firmware 20240913.gita34e7a5f-0ubuntu2
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/17/2010
dmi.bios.release: 1.50
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET62WW (1.32 )
dmi.board.name: 3626FAG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.ec.firmware.release: 1.18
dmi.modalias: dmi:bvnLENOVO:bvr6QET62WW(1.32):bd12/17/2010:br1.50:efr1.18:svnLENOVO:pn3626FAG:pvrThinkPadX201:rvnLENOVO:rn3626FAG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:sku:
dmi.product.family: ThinkPad X201
dmi.product.name: 3626FAG
dmi.product.version: ThinkPad X201
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084055/+subscriptions
четверг
[Bug 2077287] Re: [SRU]Fail to locate the LED of NVME disk behind Intel VMD
Hi Michael,
This fixed the issue in 24.04. and 22.04.5 which has the 6.8 kernel.
[shangsong]: 1. When the fix will release or which release already contain the fix on 24.04?
2. Is it necessary to open a issue for Ubuntu 22.04.5 HWE kernel(6.8.0-40)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2077287
Title:
[SRU]Fail to locate the LED of NVME disk behind Intel VMD
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
Fix Released
Bug description:
[Impact]
Failed to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Test Plan]
1. Fresh install of Ubuntu server 24.04 on the Server with Intel VMD
2. Upgrade the kernel to 6.8.0-40 and install ledmon package
3. Locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Fix]
After checking the source code, it ran into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170. This patch 5560a612c20d3daacbf5da7913deefa5c31742f4 which is now upstream resolves this issue.
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077287/+subscriptions
This fixed the issue in 24.04. and 22.04.5 which has the 6.8 kernel.
[shangsong]: 1. When the fix will release or which release already contain the fix on 24.04?
2. Is it necessary to open a issue for Ubuntu 22.04.5 HWE kernel(6.8.0-40)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2077287
Title:
[SRU]Fail to locate the LED of NVME disk behind Intel VMD
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
Fix Released
Bug description:
[Impact]
Failed to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Test Plan]
1. Fresh install of Ubuntu server 24.04 on the Server with Intel VMD
2. Upgrade the kernel to 6.8.0-40 and install ledmon package
3. Locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Fix]
After checking the source code, it ran into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170. This patch 5560a612c20d3daacbf5da7913deefa5c31742f4 which is now upstream resolves this issue.
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077287/+subscriptions
[Bug 2077287] Re: [SRU]Fail to locate the LED of NVME disk behind Intel VMD
** Description changed:
[Impact]
Failed to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Test Plan]
1. Fresh install of Ubuntu server 24.04 on the Server with Intel VMD
- 2. Upgrade the kernel to 6.8.0-40 and install the ledmon package
- 3. Locate the LED of nvme device behind Intel VMD via below command
+ 2. Upgrade the kernel to 6.8.0-40 and install ledmon package
+ 3. Locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Fix]
- After checking the source code, it ran into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170. This patch 5560a612c20d3daacbf5da7913deefa5c31742f4 which is now upstream resolves this issue.
+ After check the source code, it run into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170, now the kernel upstream already merge the fix(Commit: 5560a612c20d3daacbf5da7913deefa5c31742f4), please also help to fix it on Ubuntu server 24.04, thanks.
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme
** Description changed:
[Impact]
Failed to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Test Plan]
1. Fresh install of Ubuntu server 24.04 on the Server with Intel VMD
2. Upgrade the kernel to 6.8.0-40 and install ledmon package
3. Locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Fix]
- After check the source code, it run into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170, now the kernel upstream already merge the fix(Commit: 5560a612c20d3daacbf5da7913deefa5c31742f4), please also help to fix it on Ubuntu server 24.04, thanks.
+ After checking the source code, it ran into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170. This patch 5560a612c20d3daacbf5da7913deefa5c31742f4 which is now upstream resolves this issue.
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2077287
Title:
[SRU]Fail to locate the LED of NVME disk behind Intel VMD
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
Fix Released
Bug description:
[Impact]
Failed to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Test Plan]
1. Fresh install of Ubuntu server 24.04 on the Server with Intel VMD
2. Upgrade the kernel to 6.8.0-40 and install ledmon package
3. Locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Fix]
After checking the source code, it ran into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170. This patch 5560a612c20d3daacbf5da7913deefa5c31742f4 which is now upstream resolves this issue.
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077287/+subscriptions
[Impact]
Failed to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Test Plan]
1. Fresh install of Ubuntu server 24.04 on the Server with Intel VMD
- 2. Upgrade the kernel to 6.8.0-40 and install the ledmon package
- 3. Locate the LED of nvme device behind Intel VMD via below command
+ 2. Upgrade the kernel to 6.8.0-40 and install ledmon package
+ 3. Locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Fix]
- After checking the source code, it ran into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170. This patch 5560a612c20d3daacbf5da7913deefa5c31742f4 which is now upstream resolves this issue.
+ After check the source code, it run into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170, now the kernel upstream already merge the fix(Commit: 5560a612c20d3daacbf5da7913deefa5c31742f4), please also help to fix it on Ubuntu server 24.04, thanks.
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme
** Description changed:
[Impact]
Failed to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Test Plan]
1. Fresh install of Ubuntu server 24.04 on the Server with Intel VMD
2. Upgrade the kernel to 6.8.0-40 and install ledmon package
3. Locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Fix]
- After check the source code, it run into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170, now the kernel upstream already merge the fix(Commit: 5560a612c20d3daacbf5da7913deefa5c31742f4), please also help to fix it on Ubuntu server 24.04, thanks.
+ After checking the source code, it ran into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170. This patch 5560a612c20d3daacbf5da7913deefa5c31742f4 which is now upstream resolves this issue.
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2077287
Title:
[SRU]Fail to locate the LED of NVME disk behind Intel VMD
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
Fix Released
Bug description:
[Impact]
Failed to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Test Plan]
1. Fresh install of Ubuntu server 24.04 on the Server with Intel VMD
2. Upgrade the kernel to 6.8.0-40 and install ledmon package
3. Locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Fix]
After checking the source code, it ran into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170. This patch 5560a612c20d3daacbf5da7913deefa5c31742f4 which is now upstream resolves this issue.
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077287/+subscriptions
[Bug 2077287] Re: [SRU]Fail to locate the LED of NVME disk behind Intel VMD
** Description changed:
[Impact]
Failed to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Test Plan]
- 1. Fresh install Ubuntu server 24.04 on the Server with Intel VMD
- 2. Upgrade kernel to 6.8.0-40 and install ledmon package
- 3. Locate the LED of nvme device behing Intel VMD via below command
+ 1. Fresh install of Ubuntu server 24.04 on the Server with Intel VMD
+ 2. Upgrade the kernel to 6.8.0-40 and install the ledmon package
+ 3. Locate the LED of nvme device behind Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Fix]
- After check the source code, it run into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170, now the kernel upstream already merge the fix(Commit: 5560a612c20d3daacbf5da7913deefa5c31742f4), please also help to fix it on Ubuntu server 24.04, thanks.
+ After checking the source code, it ran into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170. This patch 5560a612c20d3daacbf5da7913deefa5c31742f4 which is now upstream resolves this issue.
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2077287
Title:
[SRU]Fail to locate the LED of NVME disk behind Intel VMD
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
Fix Released
Bug description:
[Impact]
Failed to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Test Plan]
1. Fresh install of Ubuntu server 24.04 on the Server with Intel VMD
2. Upgrade the kernel to 6.8.0-40 and install ledmon package
3. Locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Fix]
After check the source code, it run into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170, now the kernel upstream already merge the fix(Commit: 5560a612c20d3daacbf5da7913deefa5c31742f4), please also help to fix it on Ubuntu server 24.04, thanks.
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077287/+subscriptions
[Impact]
Failed to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Test Plan]
- 1. Fresh install Ubuntu server 24.04 on the Server with Intel VMD
- 2. Upgrade kernel to 6.8.0-40 and install ledmon package
- 3. Locate the LED of nvme device behing Intel VMD via below command
+ 1. Fresh install of Ubuntu server 24.04 on the Server with Intel VMD
+ 2. Upgrade the kernel to 6.8.0-40 and install the ledmon package
+ 3. Locate the LED of nvme device behind Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Fix]
- After check the source code, it run into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170, now the kernel upstream already merge the fix(Commit: 5560a612c20d3daacbf5da7913deefa5c31742f4), please also help to fix it on Ubuntu server 24.04, thanks.
+ After checking the source code, it ran into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170. This patch 5560a612c20d3daacbf5da7913deefa5c31742f4 which is now upstream resolves this issue.
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2077287
Title:
[SRU]Fail to locate the LED of NVME disk behind Intel VMD
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
Fix Released
Bug description:
[Impact]
Failed to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Test Plan]
1. Fresh install of Ubuntu server 24.04 on the Server with Intel VMD
2. Upgrade the kernel to 6.8.0-40 and install ledmon package
3. Locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Fix]
After check the source code, it run into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170, now the kernel upstream already merge the fix(Commit: 5560a612c20d3daacbf5da7913deefa5c31742f4), please also help to fix it on Ubuntu server 24.04, thanks.
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077287/+subscriptions
[Bug 2077287] Re: Fail to locate the LED of NVME disk behind Intel VMD
Hi Shangsong,
What is the regression risk of this patch?
** Description changed:
+ [Impact]
1. Fresh install Ubuntu server 24.04 on the Server with Intel VMD
2. Upgrade kernel to 6.8.0-40 and install ledmon package
3. Fail to locate the LED of nvme device behing Intel VMD via below command
- # ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
+ # ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
- After check the source code, it run into the issue from the kernel
- commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170, now the kernel upstream
- already merge the fix(Commit: 5560a612c20d3daacbf5da7913deefa5c31742f4),
- please also help to fix it on Ubuntu server 24.04, thanks.
+ [Test Plan]
+ [Fix]
+ After check the source code, it run into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170, now the kernel upstream already merge the fix(Commit: 5560a612c20d3daacbf5da7913deefa5c31742f4), please also help to fix it on Ubuntu server 24.04, thanks.
+
+
+ [Where problems could occur]
+
+ [Other Info]
+ https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme
** Summary changed:
- Fail to locate the LED of NVME disk behind Intel VMD
+ [SRU]Fail to locate the LED of NVME disk behind Intel VMD
** Description changed:
[Impact]
- 1. Fresh install Ubuntu server 24.04 on the Server with Intel VMD
- 2. Upgrade kernel to 6.8.0-40 and install ledmon package
- 3. Fail to locate the LED of nvme device behing Intel VMD via below command
+ Failed to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Test Plan]
+
+ 1. Fresh install Ubuntu server 24.04 on the Server with Intel VMD
+ 2. Upgrade kernel to 6.8.0-40 and install ledmon package
+ 3. Locate the LED of nvme device behing Intel VMD via below command
+ # ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
+
[Fix]
After check the source code, it run into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170, now the kernel upstream already merge the fix(Commit: 5560a612c20d3daacbf5da7913deefa5c31742f4), please also help to fix it on Ubuntu server 24.04, thanks.
-
[Where problems could occur]
[Other Info]
+
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Oracular)
Status: New => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2077287
Title:
[SRU]Fail to locate the LED of NVME disk behind Intel VMD
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
Fix Released
Bug description:
[Impact]
Failed to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Test Plan]
1. Fresh install Ubuntu server 24.04 on the Server with Intel VMD
2. Upgrade kernel to 6.8.0-40 and install ledmon package
3. Locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Fix]
After check the source code, it run into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170, now the kernel upstream already merge the fix(Commit: 5560a612c20d3daacbf5da7913deefa5c31742f4), please also help to fix it on Ubuntu server 24.04, thanks.
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077287/+subscriptions
What is the regression risk of this patch?
** Description changed:
+ [Impact]
1. Fresh install Ubuntu server 24.04 on the Server with Intel VMD
2. Upgrade kernel to 6.8.0-40 and install ledmon package
3. Fail to locate the LED of nvme device behing Intel VMD via below command
- # ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
+ # ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
- After check the source code, it run into the issue from the kernel
- commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170, now the kernel upstream
- already merge the fix(Commit: 5560a612c20d3daacbf5da7913deefa5c31742f4),
- please also help to fix it on Ubuntu server 24.04, thanks.
+ [Test Plan]
+ [Fix]
+ After check the source code, it run into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170, now the kernel upstream already merge the fix(Commit: 5560a612c20d3daacbf5da7913deefa5c31742f4), please also help to fix it on Ubuntu server 24.04, thanks.
+
+
+ [Where problems could occur]
+
+ [Other Info]
+ https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme
** Summary changed:
- Fail to locate the LED of NVME disk behind Intel VMD
+ [SRU]Fail to locate the LED of NVME disk behind Intel VMD
** Description changed:
[Impact]
- 1. Fresh install Ubuntu server 24.04 on the Server with Intel VMD
- 2. Upgrade kernel to 6.8.0-40 and install ledmon package
- 3. Fail to locate the LED of nvme device behing Intel VMD via below command
+ Failed to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Test Plan]
+
+ 1. Fresh install Ubuntu server 24.04 on the Server with Intel VMD
+ 2. Upgrade kernel to 6.8.0-40 and install ledmon package
+ 3. Locate the LED of nvme device behing Intel VMD via below command
+ # ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
+
[Fix]
After check the source code, it run into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170, now the kernel upstream already merge the fix(Commit: 5560a612c20d3daacbf5da7913deefa5c31742f4), please also help to fix it on Ubuntu server 24.04, thanks.
-
[Where problems could occur]
[Other Info]
+
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Oracular)
Status: New => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2077287
Title:
[SRU]Fail to locate the LED of NVME disk behind Intel VMD
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Status in linux source package in Oracular:
Fix Released
Bug description:
[Impact]
Failed to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Test Plan]
1. Fresh install Ubuntu server 24.04 on the Server with Intel VMD
2. Upgrade kernel to 6.8.0-40 and install ledmon package
3. Locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Fix]
After check the source code, it run into the issue from the kernel commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170, now the kernel upstream already merge the fix(Commit: 5560a612c20d3daacbf5da7913deefa5c31742f4), please also help to fix it on Ubuntu server 24.04, thanks.
[Where problems could occur]
[Other Info]
https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/noble/+ref/lp_2077287_locate_led_nvme
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077287/+subscriptions
[Bug 2077287] Re: Fail to locate the LED of NVME disk behind Intel VMD
Hi Shangsong,
This fixed the issue in 24.04. and 22.04.5 which has the 6.8 kernel.
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2077287
Title:
Fail to locate the LED of NVME disk behind Intel VMD
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Bug description:
1. Fresh install Ubuntu server 24.04 on the Server with Intel VMD
2. Upgrade kernel to 6.8.0-40 and install ledmon package
3. Fail to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
After check the source code, it run into the issue from the kernel
commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170, now the kernel
upstream already merge the fix(Commit:
5560a612c20d3daacbf5da7913deefa5c31742f4), please also help to fix it
on Ubuntu server 24.04, thanks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077287/+subscriptions
This fixed the issue in 24.04. and 22.04.5 which has the 6.8 kernel.
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2077287
Title:
Fail to locate the LED of NVME disk behind Intel VMD
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Bug description:
1. Fresh install Ubuntu server 24.04 on the Server with Intel VMD
2. Upgrade kernel to 6.8.0-40 and install ledmon package
3. Fail to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
After check the source code, it run into the issue from the kernel
commit abaaac4845a0d6f39f83cbaba4c3b46ba5f93170, now the kernel
upstream already merge the fix(Commit:
5560a612c20d3daacbf5da7913deefa5c31742f4), please also help to fix it
on Ubuntu server 24.04, thanks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077287/+subscriptions
[Bug 2084855] [NEW] Ipason laptop track pad not working
Public bug reported:
The track pad on this laptop is not detected by Ubuntu at all. its a
ipason laptop. I am running Ubuntu version: 24.04.1 LTS the software
center appears to be version: 1.0.0
this is a fresh install of Ubuntu on a new laptop i got for a
cybersecurity school. it would be nice to not have to use a external
mouse since i intend on keeping this laptop on linux. at least for the
time being so that i can get accustom to using the terminal.
If it matters it is a Ipason Storm Dragon P3 and i can answer any other
questions that are required of me
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-47-generic 6.8.0-47.47
ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12
Uname: Linux 6.8.0-47-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: buker 2003 F.... pipewire
/dev/snd/controlC0: buker 2007 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 17 19:42:31 2024
InstallationDate: Installed on 2024-10-17 (0 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
MachineType: IPASON IPASON P3
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-47-generic root=UUID=3f26f9a3-41af-4713-8545-f481ff3de3a3 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.8.0-47-generic N/A
linux-backports-modules-6.8.0-47-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/16/2023
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: BIOS-P3TGL10
dmi.board.asset.tag: Default string
dmi.board.name: TN73
dmi.board.vendor: IPASON
dmi.board.version: V10
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: IPASON
dmi.chassis.version: Default string
dmi.ec.firmware.release: 0.7
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrBIOS-P3TGL10:bd08/16/2023:br5.19:efr0.7:svnIPASON:pnIPASONP3:pvrDefaultstring:rvnIPASON:rnTN73:rvrV10:cvnIPASON:ct10:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: IPASON P3
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: IPASON
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble wayland-session
** Attachment added: "a list of all devices the ubuntu recognizes from my laptop."
https://bugs.launchpad.net/bugs/2084855/+attachment/5829210/+files/devices
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084855
Title:
Ipason laptop track pad not working
Status in linux package in Ubuntu:
New
Bug description:
The track pad on this laptop is not detected by Ubuntu at all. its a
ipason laptop. I am running Ubuntu version: 24.04.1 LTS the software
center appears to be version: 1.0.0
this is a fresh install of Ubuntu on a new laptop i got for a
cybersecurity school. it would be nice to not have to use a external
mouse since i intend on keeping this laptop on linux. at least for the
time being so that i can get accustom to using the terminal.
If it matters it is a Ipason Storm Dragon P3 and i can answer any
other questions that are required of me
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-47-generic 6.8.0-47.47
ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12
Uname: Linux 6.8.0-47-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: buker 2003 F.... pipewire
/dev/snd/controlC0: buker 2007 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 17 19:42:31 2024
InstallationDate: Installed on 2024-10-17 (0 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
MachineType: IPASON IPASON P3
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-47-generic root=UUID=3f26f9a3-41af-4713-8545-f481ff3de3a3 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.8.0-47-generic N/A
linux-backports-modules-6.8.0-47-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/16/2023
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: BIOS-P3TGL10
dmi.board.asset.tag: Default string
dmi.board.name: TN73
dmi.board.vendor: IPASON
dmi.board.version: V10
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: IPASON
dmi.chassis.version: Default string
dmi.ec.firmware.release: 0.7
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrBIOS-P3TGL10:bd08/16/2023:br5.19:efr0.7:svnIPASON:pnIPASONP3:pvrDefaultstring:rvnIPASON:rnTN73:rvrV10:cvnIPASON:ct10:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: IPASON P3
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: IPASON
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084855/+subscriptions
The track pad on this laptop is not detected by Ubuntu at all. its a
ipason laptop. I am running Ubuntu version: 24.04.1 LTS the software
center appears to be version: 1.0.0
this is a fresh install of Ubuntu on a new laptop i got for a
cybersecurity school. it would be nice to not have to use a external
mouse since i intend on keeping this laptop on linux. at least for the
time being so that i can get accustom to using the terminal.
If it matters it is a Ipason Storm Dragon P3 and i can answer any other
questions that are required of me
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-47-generic 6.8.0-47.47
ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12
Uname: Linux 6.8.0-47-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: buker 2003 F.... pipewire
/dev/snd/controlC0: buker 2007 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 17 19:42:31 2024
InstallationDate: Installed on 2024-10-17 (0 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
MachineType: IPASON IPASON P3
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-47-generic root=UUID=3f26f9a3-41af-4713-8545-f481ff3de3a3 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.8.0-47-generic N/A
linux-backports-modules-6.8.0-47-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/16/2023
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: BIOS-P3TGL10
dmi.board.asset.tag: Default string
dmi.board.name: TN73
dmi.board.vendor: IPASON
dmi.board.version: V10
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: IPASON
dmi.chassis.version: Default string
dmi.ec.firmware.release: 0.7
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrBIOS-P3TGL10:bd08/16/2023:br5.19:efr0.7:svnIPASON:pnIPASONP3:pvrDefaultstring:rvnIPASON:rnTN73:rvrV10:cvnIPASON:ct10:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: IPASON P3
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: IPASON
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble wayland-session
** Attachment added: "a list of all devices the ubuntu recognizes from my laptop."
https://bugs.launchpad.net/bugs/2084855/+attachment/5829210/+files/devices
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084855
Title:
Ipason laptop track pad not working
Status in linux package in Ubuntu:
New
Bug description:
The track pad on this laptop is not detected by Ubuntu at all. its a
ipason laptop. I am running Ubuntu version: 24.04.1 LTS the software
center appears to be version: 1.0.0
this is a fresh install of Ubuntu on a new laptop i got for a
cybersecurity school. it would be nice to not have to use a external
mouse since i intend on keeping this laptop on linux. at least for the
time being so that i can get accustom to using the terminal.
If it matters it is a Ipason Storm Dragon P3 and i can answer any
other questions that are required of me
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-47-generic 6.8.0-47.47
ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12
Uname: Linux 6.8.0-47-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: buker 2003 F.... pipewire
/dev/snd/controlC0: buker 2007 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 17 19:42:31 2024
InstallationDate: Installed on 2024-10-17 (0 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
MachineType: IPASON IPASON P3
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-47-generic root=UUID=3f26f9a3-41af-4713-8545-f481ff3de3a3 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.8.0-47-generic N/A
linux-backports-modules-6.8.0-47-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/16/2023
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: BIOS-P3TGL10
dmi.board.asset.tag: Default string
dmi.board.name: TN73
dmi.board.vendor: IPASON
dmi.board.version: V10
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: IPASON
dmi.chassis.version: Default string
dmi.ec.firmware.release: 0.7
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrBIOS-P3TGL10:bd08/16/2023:br5.19:efr0.7:svnIPASON:pnIPASONP3:pvrDefaultstring:rvnIPASON:rnTN73:rvrV10:cvnIPASON:ct10:cvrDefaultstring:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: IPASON P3
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: IPASON
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084855/+subscriptions
[Bug 2084834] Re: [SRU] cpufreq: intel_pstate: Support Emerald Rapids OOB mode
Patch submitted: https://lists.ubuntu.com/archives/kernel-
team/2024-October/154680.html
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084834
Title:
[SRU] cpufreq: intel_pstate: Support Emerald Rapids OOB mode
Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
In Progress
Bug description:
This is a public version of: https://bugs.launchpad.net/bugs/2078894
[Impact]
In Emerald Rapids VMs with OOB P-states enabled, a stack trace is
printed during boot on 6.8 based kernels. The stack traces look like:
[ 1.206658] intel_pstate: Intel P-state driver initializing
[ 1.207453] unchecked MSR access error: WRMSR to 0x199 (tried to write 0x0000000000000800) at rIP: 0xffffffffb94c3b24 (native_write_msr+0x4/0x40)
[ 1.208422] Call Trace:
[ 1.208422] <TASK>
[ 1.208422] ? show_stack_regs+0x23/0x40
[ 1.208422] ? ex_handler_msr+0x10a/0x180
[ 1.208422] ? fixup_exception+0x183/0x390
[ 1.208422] ? gp_try_fixup_and_notify+0x23/0xc0
[ 1.208422] ? exc_general_protection+0x15e/0x480
[ 1.208422] ? asm_exc_general_protection+0x27/0x30
[ 1.208422] ? __pfx___wrmsr_on_cpu+0x10/0x10
[ 1.208422] ? native_write_msr+0x4/0x40
[ 1.208422] ? __wrmsr_on_cpu+0x4b/0x90
[ 1.208422] ? __pfx___rdmsr_on_cpu+0x10/0x10
[ 1.208422] ? __pfx___wrmsr_on_cpu+0x10/0x10
[ 1.208422] generic_exec_single+0x7e/0x120
[ 1.208422] smp_call_function_single+0x103/0x140
[ 1.208422] ? __pfx___wrmsr_on_cpu+0x10/0x10
[ 1.208422] wrmsrl_on_cpu+0x57/0x80
[ 1.208422] intel_pstate_set_pstate+0x3e/0x80
[ 1.208422] intel_pstate_get_cpu_pstates.constprop.0+0xd7/0x190
[ 1.208422] intel_pstate_init_cpu+0x3f/0x140
[ 1.208422] intel_cpufreq_cpu_init+0x44/0x270
[ 1.208422] ? freq_qos_add_notifier+0x45/0x80
[ 1.208422] cpufreq_online+0x444/0xb80
[ 1.208422] cpufreq_add_dev+0x99/0xd0
[ 1.208422] subsys_interface_register+0x11c/0x140
[ 1.208422] cpufreq_register_driver+0x1b5/0x330
[ 1.208422] intel_pstate_register_driver+0x48/0xd0
[ 1.208422] intel_pstate_init+0x25c/0x810
[ 1.208422] ? __pfx_intel_pstate_init+0x10/0x10
[ 1.208422] do_one_initcall+0x5b/0x310
[ 1.208422] do_initcalls+0x104/0x210
[ 1.208422] ? __pfx_kernel_init+0x10/0x10
[ 1.208422] kernel_init_freeable+0x134/0x1f0
[ 1.208422] kernel_init+0x1b/0x200
[ 1.208422] ret_from_fork+0x44/0x70
[ 1.208422] ? __pfx_kernel_init+0x10/0x10
[ 1.208422] ret_from_fork_asm+0x1b/0x30
[ 1.208422] </TASK>
[Fix]
Cherry pick of 7e1c3f584ee7 - cpufreq: intel_pstate: Support Emerald Rapids OOB mode
Upstream since v6.11.
Very simple change as the OOB identifying bits are same as for the prior
generation CPUs like Sapphire Rapids servers, so also add Emerald Rapids to the
intel_pstate_cpu_oob_ids[] list.
[Test Plan]
Set HW PM OOB mode in BIOS power management config.
Make sure that no cpufreq drivers are loaded. You can verify that
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver is not present or any cpufreq interface.
It's also already part of linux-aws:
https://bugs.launchpad.net/bugs/2078894
[Where problems could occur]
cpufreq regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084834/+subscriptions
team/2024-October/154680.html
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084834
Title:
[SRU] cpufreq: intel_pstate: Support Emerald Rapids OOB mode
Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
In Progress
Bug description:
This is a public version of: https://bugs.launchpad.net/bugs/2078894
[Impact]
In Emerald Rapids VMs with OOB P-states enabled, a stack trace is
printed during boot on 6.8 based kernels. The stack traces look like:
[ 1.206658] intel_pstate: Intel P-state driver initializing
[ 1.207453] unchecked MSR access error: WRMSR to 0x199 (tried to write 0x0000000000000800) at rIP: 0xffffffffb94c3b24 (native_write_msr+0x4/0x40)
[ 1.208422] Call Trace:
[ 1.208422] <TASK>
[ 1.208422] ? show_stack_regs+0x23/0x40
[ 1.208422] ? ex_handler_msr+0x10a/0x180
[ 1.208422] ? fixup_exception+0x183/0x390
[ 1.208422] ? gp_try_fixup_and_notify+0x23/0xc0
[ 1.208422] ? exc_general_protection+0x15e/0x480
[ 1.208422] ? asm_exc_general_protection+0x27/0x30
[ 1.208422] ? __pfx___wrmsr_on_cpu+0x10/0x10
[ 1.208422] ? native_write_msr+0x4/0x40
[ 1.208422] ? __wrmsr_on_cpu+0x4b/0x90
[ 1.208422] ? __pfx___rdmsr_on_cpu+0x10/0x10
[ 1.208422] ? __pfx___wrmsr_on_cpu+0x10/0x10
[ 1.208422] generic_exec_single+0x7e/0x120
[ 1.208422] smp_call_function_single+0x103/0x140
[ 1.208422] ? __pfx___wrmsr_on_cpu+0x10/0x10
[ 1.208422] wrmsrl_on_cpu+0x57/0x80
[ 1.208422] intel_pstate_set_pstate+0x3e/0x80
[ 1.208422] intel_pstate_get_cpu_pstates.constprop.0+0xd7/0x190
[ 1.208422] intel_pstate_init_cpu+0x3f/0x140
[ 1.208422] intel_cpufreq_cpu_init+0x44/0x270
[ 1.208422] ? freq_qos_add_notifier+0x45/0x80
[ 1.208422] cpufreq_online+0x444/0xb80
[ 1.208422] cpufreq_add_dev+0x99/0xd0
[ 1.208422] subsys_interface_register+0x11c/0x140
[ 1.208422] cpufreq_register_driver+0x1b5/0x330
[ 1.208422] intel_pstate_register_driver+0x48/0xd0
[ 1.208422] intel_pstate_init+0x25c/0x810
[ 1.208422] ? __pfx_intel_pstate_init+0x10/0x10
[ 1.208422] do_one_initcall+0x5b/0x310
[ 1.208422] do_initcalls+0x104/0x210
[ 1.208422] ? __pfx_kernel_init+0x10/0x10
[ 1.208422] kernel_init_freeable+0x134/0x1f0
[ 1.208422] kernel_init+0x1b/0x200
[ 1.208422] ret_from_fork+0x44/0x70
[ 1.208422] ? __pfx_kernel_init+0x10/0x10
[ 1.208422] ret_from_fork_asm+0x1b/0x30
[ 1.208422] </TASK>
[Fix]
Cherry pick of 7e1c3f584ee7 - cpufreq: intel_pstate: Support Emerald Rapids OOB mode
Upstream since v6.11.
Very simple change as the OOB identifying bits are same as for the prior
generation CPUs like Sapphire Rapids servers, so also add Emerald Rapids to the
intel_pstate_cpu_oob_ids[] list.
[Test Plan]
Set HW PM OOB mode in BIOS power management config.
Make sure that no cpufreq drivers are loaded. You can verify that
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver is not present or any cpufreq interface.
It's also already part of linux-aws:
https://bugs.launchpad.net/bugs/2078894
[Where problems could occur]
cpufreq regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084834/+subscriptions
[Bug 2082946] Re: Kernel 6.8.0-45-generic fails to boot on 24.04
Hi Matthew,
If you look at https://launchpad.net/~ubuntu-
toolchain-r/+archive/ubuntu/ppa/?field.series_filter=noble
it indeed shows that 6.8.0-45-generic is in there, and not -47, but
soon, Matthias Klose will probably build 6.8.0-47-generic and break you
again too.
emacs 29.4 is in oracular, you could use the debs from there instead?
Anyway, its all up to you.
Thanks,
Matthew
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2082946
Title:
Kernel 6.8.0-45-generic fails to boot on 24.04
Status in linux package in Ubuntu:
Invalid
Bug description:
The system is an ASUS Vivobook laptop with a Intel Core i7 chipset.
Yesterday the updates brought in a new kernel image: 6.8.0-45-generic.
Boot has failed since, apparently it is not able to find the root
volume and drops back to the initramfs prompt. No error messages are
shown during the failed boot process, however, when I try to quit the
initramfs prompt a few messages appear (see image attached).
With the original kernel (6.8.0-44-generic) the system boots fine and
the HDD is working as expected. The contents of the `fstab` file are
below.
```
$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=F8F9-FF58 /boot/efi vfat defaults 0 2
UUID=e13ff5f9-7a98-4e01-873f-b1a0fd440c77 / ext4 defaults 0 1
UUID=5d3a8f7f-d08f-4f65-bcda-55d3fa5f6cbd /home ext4 defaults 0 2
/swapfile none swap sw 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
```
Please let me know if I can provide further information. Thank you for
reading.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2082946/+subscriptions
If you look at https://launchpad.net/~ubuntu-
toolchain-r/+archive/ubuntu/ppa/?field.series_filter=noble
it indeed shows that 6.8.0-45-generic is in there, and not -47, but
soon, Matthias Klose will probably build 6.8.0-47-generic and break you
again too.
emacs 29.4 is in oracular, you could use the debs from there instead?
Anyway, its all up to you.
Thanks,
Matthew
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2082946
Title:
Kernel 6.8.0-45-generic fails to boot on 24.04
Status in linux package in Ubuntu:
Invalid
Bug description:
The system is an ASUS Vivobook laptop with a Intel Core i7 chipset.
Yesterday the updates brought in a new kernel image: 6.8.0-45-generic.
Boot has failed since, apparently it is not able to find the root
volume and drops back to the initramfs prompt. No error messages are
shown during the failed boot process, however, when I try to quit the
initramfs prompt a few messages appear (see image attached).
With the original kernel (6.8.0-44-generic) the system boots fine and
the HDD is working as expected. The contents of the `fstab` file are
below.
```
$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=F8F9-FF58 /boot/efi vfat defaults 0 2
UUID=e13ff5f9-7a98-4e01-873f-b1a0fd440c77 / ext4 defaults 0 1
UUID=5d3a8f7f-d08f-4f65-bcda-55d3fa5f6cbd /home ext4 defaults 0 2
/swapfile none swap sw 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
```
Please let me know if I can provide further information. Thank you for
reading.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2082946/+subscriptions
[Bug 2084695] Re: Kernel update through apt leaves the system with no working network connection.
Hi Pedro,
Great to hear that this helped you.
Hmm, we should probably try figure out why the modules weren't pulled in
when the image was installed.
Any chanced you could have a look through /var/log/apt/history.log, and
see when 6.8.0-47-generic was first installed, and what packages were
installed in that same transaction? And then of course, the most recent
one where you likely got modules installed, can you see if it was just
-modules, -modules-extra, or both.
Nicolas I'll have a think and write back to you soon.
Thanks,
Matthew
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084695
Title:
Kernel update through apt leaves the system with no working network
connection.
Status in linux package in Ubuntu:
Confirmed
Bug description:
I am using Ubuntu 24.04.1 LTS. After the upgrade to kernel 6.8.0-47
from 6.8.0-45, for the first time, Ubuntu was unable to recognize my
ethernet, wifi and bluetooth. None of these issues occurred before
since they were automatically recognized and configured by the
installer. The only solution I found was to revert to 6.8.0-45.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-47-generic (not installed)
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: pejalb 2399 F.... pipewire
/dev/snd/controlC0: pejalb 2402 F.... wireplumber
/dev/snd/controlC1: pejalb 2402 F.... wireplumber
/dev/snd/controlC2: pejalb 2402 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 16 11:58:38 2024
InstallationDate: Installed on 2024-09-24 (22 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
MachineType: Micro-Star International Co., Ltd. MS-7C95
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 simpledrmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic root=UUID=3ecf92ad-c19e-4c7b-a589-64a030b1fac5 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.8.0-45-generic N/A
linux-backports-modules-6.8.0-45-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/10/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 2.I0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B550M PRO-VDH WIFI (MS-7C95)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.I0:bd10/10/2023:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C95:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550MPRO-VDHWIFI(MS-7C95):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C95
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084695/+subscriptions
Great to hear that this helped you.
Hmm, we should probably try figure out why the modules weren't pulled in
when the image was installed.
Any chanced you could have a look through /var/log/apt/history.log, and
see when 6.8.0-47-generic was first installed, and what packages were
installed in that same transaction? And then of course, the most recent
one where you likely got modules installed, can you see if it was just
-modules, -modules-extra, or both.
Nicolas I'll have a think and write back to you soon.
Thanks,
Matthew
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084695
Title:
Kernel update through apt leaves the system with no working network
connection.
Status in linux package in Ubuntu:
Confirmed
Bug description:
I am using Ubuntu 24.04.1 LTS. After the upgrade to kernel 6.8.0-47
from 6.8.0-45, for the first time, Ubuntu was unable to recognize my
ethernet, wifi and bluetooth. None of these issues occurred before
since they were automatically recognized and configured by the
installer. The only solution I found was to revert to 6.8.0-45.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-47-generic (not installed)
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: pejalb 2399 F.... pipewire
/dev/snd/controlC0: pejalb 2402 F.... wireplumber
/dev/snd/controlC1: pejalb 2402 F.... wireplumber
/dev/snd/controlC2: pejalb 2402 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 16 11:58:38 2024
InstallationDate: Installed on 2024-09-24 (22 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
MachineType: Micro-Star International Co., Ltd. MS-7C95
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 simpledrmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic root=UUID=3ecf92ad-c19e-4c7b-a589-64a030b1fac5 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.8.0-45-generic N/A
linux-backports-modules-6.8.0-45-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.4
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/10/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 2.I0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B550M PRO-VDH WIFI (MS-7C95)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.I0:bd10/10/2023:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C95:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550MPRO-VDHWIFI(MS-7C95):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C95
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084695/+subscriptions
[Bug 2084836] [NEW] package linux-headers-6.8.0-47-generic 6.8.0-47.47 failed to install/upgrade: installed linux-headers-6.8.0-47-generic package post-installation script subprocess returned error exit status 11
Public bug reported:
encountered during an update
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-headers-6.8.0-47-generic 6.8.0-47.47
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: sri-chakra 2824 F.... pipewire
/dev/snd/controlC2: sri-chakra 2829 F.... wireplumber
/dev/snd/controlC0: sri-chakra 2829 F.... wireplumber
/dev/snd/controlC1: sri-chakra 2829 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Oct 17 06:46:19 2024
ErrorMessage: installed linux-headers-6.8.0-47-generic package post-installation script subprocess returned error exit status 11
InstallationDate: Installed on 2024-10-01 (17 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: ASUS System Product Name
ProcFB:
0 simpledrmdrmfb
1 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic root=UUID=9e11f456-5a99-4f09-ace4-d845b4d9b266 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.8.0-47-generic 6.8.0-47.47 failed to install/upgrade: installed linux-headers-6.8.0-47-generic package post-installation script subprocess returned error exit status 11
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/20/2023
dmi.bios.release: 4.4
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0404
dmi.board.asset.tag: Default string
dmi.board.name: Pro WS WRX90E-SAGE SE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0404:bd12/20/2023:br4.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSWRX90E-SAGESE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package need-duplicate-check noble
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084836
Title:
package linux-headers-6.8.0-47-generic 6.8.0-47.47 failed to
install/upgrade: installed linux-headers-6.8.0-47-generic package
post-installation script subprocess returned error exit status 11
Status in linux package in Ubuntu:
New
Bug description:
encountered during an update
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-headers-6.8.0-47-generic 6.8.0-47.47
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: sri-chakra 2824 F.... pipewire
/dev/snd/controlC2: sri-chakra 2829 F.... wireplumber
/dev/snd/controlC0: sri-chakra 2829 F.... wireplumber
/dev/snd/controlC1: sri-chakra 2829 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Oct 17 06:46:19 2024
ErrorMessage: installed linux-headers-6.8.0-47-generic package post-installation script subprocess returned error exit status 11
InstallationDate: Installed on 2024-10-01 (17 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: ASUS System Product Name
ProcFB:
0 simpledrmdrmfb
1 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic root=UUID=9e11f456-5a99-4f09-ace4-d845b4d9b266 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.8.0-47-generic 6.8.0-47.47 failed to install/upgrade: installed linux-headers-6.8.0-47-generic package post-installation script subprocess returned error exit status 11
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/20/2023
dmi.bios.release: 4.4
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0404
dmi.board.asset.tag: Default string
dmi.board.name: Pro WS WRX90E-SAGE SE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0404:bd12/20/2023:br4.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSWRX90E-SAGESE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084836/+subscriptions
encountered during an update
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-headers-6.8.0-47-generic 6.8.0-47.47
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: sri-chakra 2824 F.... pipewire
/dev/snd/controlC2: sri-chakra 2829 F.... wireplumber
/dev/snd/controlC0: sri-chakra 2829 F.... wireplumber
/dev/snd/controlC1: sri-chakra 2829 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Oct 17 06:46:19 2024
ErrorMessage: installed linux-headers-6.8.0-47-generic package post-installation script subprocess returned error exit status 11
InstallationDate: Installed on 2024-10-01 (17 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: ASUS System Product Name
ProcFB:
0 simpledrmdrmfb
1 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic root=UUID=9e11f456-5a99-4f09-ace4-d845b4d9b266 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.8.0-47-generic 6.8.0-47.47 failed to install/upgrade: installed linux-headers-6.8.0-47-generic package post-installation script subprocess returned error exit status 11
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/20/2023
dmi.bios.release: 4.4
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0404
dmi.board.asset.tag: Default string
dmi.board.name: Pro WS WRX90E-SAGE SE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0404:bd12/20/2023:br4.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSWRX90E-SAGESE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package need-duplicate-check noble
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084836
Title:
package linux-headers-6.8.0-47-generic 6.8.0-47.47 failed to
install/upgrade: installed linux-headers-6.8.0-47-generic package
post-installation script subprocess returned error exit status 11
Status in linux package in Ubuntu:
New
Bug description:
encountered during an update
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-headers-6.8.0-47-generic 6.8.0-47.47
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/seq: sri-chakra 2824 F.... pipewire
/dev/snd/controlC2: sri-chakra 2829 F.... wireplumber
/dev/snd/controlC0: sri-chakra 2829 F.... wireplumber
/dev/snd/controlC1: sri-chakra 2829 F.... wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
Date: Thu Oct 17 06:46:19 2024
ErrorMessage: installed linux-headers-6.8.0-47-generic package post-installation script subprocess returned error exit status 11
InstallationDate: Installed on 2024-10-01 (17 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: ASUS System Product Name
ProcFB:
0 simpledrmdrmfb
1 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-45-generic root=UUID=9e11f456-5a99-4f09-ace4-d845b4d9b266 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu2
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-headers-6.8.0-47-generic 6.8.0-47.47 failed to install/upgrade: installed linux-headers-6.8.0-47-generic package post-installation script subprocess returned error exit status 11
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/20/2023
dmi.bios.release: 4.4
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0404
dmi.board.asset.tag: Default string
dmi.board.name: Pro WS WRX90E-SAGE SE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0404:bd12/20/2023:br4.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnProWSWRX90E-SAGESE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084836/+subscriptions
[Bug 2084834] Re: [SRU] cpufreq: intel_pstate: Support Emerald Rapids OOB mode
** Description changed:
This is a public version of: https://bugs.launchpad.net/bugs/2078894
[Impact]
- In Emerald Rapids VMs, a stack trace is printed during boot on 6.8 based
- kernels. The stack traces look like:
+ In Emerald Rapids VMs with OOB P-states enabled, a stack trace is
+ printed during boot on 6.8 based kernels. The stack traces look like:
[ 1.206658] intel_pstate: Intel P-state driver initializing
[ 1.207453] unchecked MSR access error: WRMSR to 0x199 (tried to write 0x0000000000000800) at rIP: 0xffffffffb94c3b24 (native_write_msr+0x4/0x40)
[ 1.208422] Call Trace:
[ 1.208422] <TASK>
[ 1.208422] ? show_stack_regs+0x23/0x40
[ 1.208422] ? ex_handler_msr+0x10a/0x180
[ 1.208422] ? fixup_exception+0x183/0x390
[ 1.208422] ? gp_try_fixup_and_notify+0x23/0xc0
[ 1.208422] ? exc_general_protection+0x15e/0x480
[ 1.208422] ? asm_exc_general_protection+0x27/0x30
[ 1.208422] ? __pfx___wrmsr_on_cpu+0x10/0x10
[ 1.208422] ? native_write_msr+0x4/0x40
[ 1.208422] ? __wrmsr_on_cpu+0x4b/0x90
[ 1.208422] ? __pfx___rdmsr_on_cpu+0x10/0x10
[ 1.208422] ? __pfx___wrmsr_on_cpu+0x10/0x10
[ 1.208422] generic_exec_single+0x7e/0x120
[ 1.208422] smp_call_function_single+0x103/0x140
[ 1.208422] ? __pfx___wrmsr_on_cpu+0x10/0x10
[ 1.208422] wrmsrl_on_cpu+0x57/0x80
[ 1.208422] intel_pstate_set_pstate+0x3e/0x80
[ 1.208422] intel_pstate_get_cpu_pstates.constprop.0+0xd7/0x190
[ 1.208422] intel_pstate_init_cpu+0x3f/0x140
[ 1.208422] intel_cpufreq_cpu_init+0x44/0x270
[ 1.208422] ? freq_qos_add_notifier+0x45/0x80
[ 1.208422] cpufreq_online+0x444/0xb80
[ 1.208422] cpufreq_add_dev+0x99/0xd0
[ 1.208422] subsys_interface_register+0x11c/0x140
[ 1.208422] cpufreq_register_driver+0x1b5/0x330
[ 1.208422] intel_pstate_register_driver+0x48/0xd0
[ 1.208422] intel_pstate_init+0x25c/0x810
[ 1.208422] ? __pfx_intel_pstate_init+0x10/0x10
[ 1.208422] do_one_initcall+0x5b/0x310
[ 1.208422] do_initcalls+0x104/0x210
[ 1.208422] ? __pfx_kernel_init+0x10/0x10
[ 1.208422] kernel_init_freeable+0x134/0x1f0
[ 1.208422] kernel_init+0x1b/0x200
[ 1.208422] ret_from_fork+0x44/0x70
[ 1.208422] ? __pfx_kernel_init+0x10/0x10
[ 1.208422] ret_from_fork_asm+0x1b/0x30
[ 1.208422] </TASK>
[Fix]
Cherry pick of 7e1c3f584ee7 - cpufreq: intel_pstate: Support Emerald Rapids OOB mode
Upstream since v6.11.
Very simple change as the OOB identifying bits are same as for the prior
generation CPUs like Sapphire Rapids servers, so also add Emerald Rapids to the
intel_pstate_cpu_oob_ids[] list.
[Test Plan]
Set HW PM OOB mode in BIOS power management config.
Make sure that no cpufreq drivers are loaded. You can verify that
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver is not present or any cpufreq interface.
It's also already part of linux-aws:
https://bugs.launchpad.net/bugs/2078894
-
[Where problems could occur]
cpufreq regression.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084834
Title:
[SRU] cpufreq: intel_pstate: Support Emerald Rapids OOB mode
Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
New
Bug description:
This is a public version of: https://bugs.launchpad.net/bugs/2078894
[Impact]
In Emerald Rapids VMs with OOB P-states enabled, a stack trace is
printed during boot on 6.8 based kernels. The stack traces look like:
[ 1.206658] intel_pstate: Intel P-state driver initializing
[ 1.207453] unchecked MSR access error: WRMSR to 0x199 (tried to write 0x0000000000000800) at rIP: 0xffffffffb94c3b24 (native_write_msr+0x4/0x40)
[ 1.208422] Call Trace:
[ 1.208422] <TASK>
[ 1.208422] ? show_stack_regs+0x23/0x40
[ 1.208422] ? ex_handler_msr+0x10a/0x180
[ 1.208422] ? fixup_exception+0x183/0x390
[ 1.208422] ? gp_try_fixup_and_notify+0x23/0xc0
[ 1.208422] ? exc_general_protection+0x15e/0x480
[ 1.208422] ? asm_exc_general_protection+0x27/0x30
[ 1.208422] ? __pfx___wrmsr_on_cpu+0x10/0x10
[ 1.208422] ? native_write_msr+0x4/0x40
[ 1.208422] ? __wrmsr_on_cpu+0x4b/0x90
[ 1.208422] ? __pfx___rdmsr_on_cpu+0x10/0x10
[ 1.208422] ? __pfx___wrmsr_on_cpu+0x10/0x10
[ 1.208422] generic_exec_single+0x7e/0x120
[ 1.208422] smp_call_function_single+0x103/0x140
[ 1.208422] ? __pfx___wrmsr_on_cpu+0x10/0x10
[ 1.208422] wrmsrl_on_cpu+0x57/0x80
[ 1.208422] intel_pstate_set_pstate+0x3e/0x80
[ 1.208422] intel_pstate_get_cpu_pstates.constprop.0+0xd7/0x190
[ 1.208422] intel_pstate_init_cpu+0x3f/0x140
[ 1.208422] intel_cpufreq_cpu_init+0x44/0x270
[ 1.208422] ? freq_qos_add_notifier+0x45/0x80
[ 1.208422] cpufreq_online+0x444/0xb80
[ 1.208422] cpufreq_add_dev+0x99/0xd0
[ 1.208422] subsys_interface_register+0x11c/0x140
[ 1.208422] cpufreq_register_driver+0x1b5/0x330
[ 1.208422] intel_pstate_register_driver+0x48/0xd0
[ 1.208422] intel_pstate_init+0x25c/0x810
[ 1.208422] ? __pfx_intel_pstate_init+0x10/0x10
[ 1.208422] do_one_initcall+0x5b/0x310
[ 1.208422] do_initcalls+0x104/0x210
[ 1.208422] ? __pfx_kernel_init+0x10/0x10
[ 1.208422] kernel_init_freeable+0x134/0x1f0
[ 1.208422] kernel_init+0x1b/0x200
[ 1.208422] ret_from_fork+0x44/0x70
[ 1.208422] ? __pfx_kernel_init+0x10/0x10
[ 1.208422] ret_from_fork_asm+0x1b/0x30
[ 1.208422] </TASK>
[Fix]
Cherry pick of 7e1c3f584ee7 - cpufreq: intel_pstate: Support Emerald Rapids OOB mode
Upstream since v6.11.
Very simple change as the OOB identifying bits are same as for the prior
generation CPUs like Sapphire Rapids servers, so also add Emerald Rapids to the
intel_pstate_cpu_oob_ids[] list.
[Test Plan]
Set HW PM OOB mode in BIOS power management config.
Make sure that no cpufreq drivers are loaded. You can verify that
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver is not present or any cpufreq interface.
It's also already part of linux-aws:
https://bugs.launchpad.net/bugs/2078894
[Where problems could occur]
cpufreq regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084834/+subscriptions
This is a public version of: https://bugs.launchpad.net/bugs/2078894
[Impact]
- In Emerald Rapids VMs, a stack trace is printed during boot on 6.8 based
- kernels. The stack traces look like:
+ In Emerald Rapids VMs with OOB P-states enabled, a stack trace is
+ printed during boot on 6.8 based kernels. The stack traces look like:
[ 1.206658] intel_pstate: Intel P-state driver initializing
[ 1.207453] unchecked MSR access error: WRMSR to 0x199 (tried to write 0x0000000000000800) at rIP: 0xffffffffb94c3b24 (native_write_msr+0x4/0x40)
[ 1.208422] Call Trace:
[ 1.208422] <TASK>
[ 1.208422] ? show_stack_regs+0x23/0x40
[ 1.208422] ? ex_handler_msr+0x10a/0x180
[ 1.208422] ? fixup_exception+0x183/0x390
[ 1.208422] ? gp_try_fixup_and_notify+0x23/0xc0
[ 1.208422] ? exc_general_protection+0x15e/0x480
[ 1.208422] ? asm_exc_general_protection+0x27/0x30
[ 1.208422] ? __pfx___wrmsr_on_cpu+0x10/0x10
[ 1.208422] ? native_write_msr+0x4/0x40
[ 1.208422] ? __wrmsr_on_cpu+0x4b/0x90
[ 1.208422] ? __pfx___rdmsr_on_cpu+0x10/0x10
[ 1.208422] ? __pfx___wrmsr_on_cpu+0x10/0x10
[ 1.208422] generic_exec_single+0x7e/0x120
[ 1.208422] smp_call_function_single+0x103/0x140
[ 1.208422] ? __pfx___wrmsr_on_cpu+0x10/0x10
[ 1.208422] wrmsrl_on_cpu+0x57/0x80
[ 1.208422] intel_pstate_set_pstate+0x3e/0x80
[ 1.208422] intel_pstate_get_cpu_pstates.constprop.0+0xd7/0x190
[ 1.208422] intel_pstate_init_cpu+0x3f/0x140
[ 1.208422] intel_cpufreq_cpu_init+0x44/0x270
[ 1.208422] ? freq_qos_add_notifier+0x45/0x80
[ 1.208422] cpufreq_online+0x444/0xb80
[ 1.208422] cpufreq_add_dev+0x99/0xd0
[ 1.208422] subsys_interface_register+0x11c/0x140
[ 1.208422] cpufreq_register_driver+0x1b5/0x330
[ 1.208422] intel_pstate_register_driver+0x48/0xd0
[ 1.208422] intel_pstate_init+0x25c/0x810
[ 1.208422] ? __pfx_intel_pstate_init+0x10/0x10
[ 1.208422] do_one_initcall+0x5b/0x310
[ 1.208422] do_initcalls+0x104/0x210
[ 1.208422] ? __pfx_kernel_init+0x10/0x10
[ 1.208422] kernel_init_freeable+0x134/0x1f0
[ 1.208422] kernel_init+0x1b/0x200
[ 1.208422] ret_from_fork+0x44/0x70
[ 1.208422] ? __pfx_kernel_init+0x10/0x10
[ 1.208422] ret_from_fork_asm+0x1b/0x30
[ 1.208422] </TASK>
[Fix]
Cherry pick of 7e1c3f584ee7 - cpufreq: intel_pstate: Support Emerald Rapids OOB mode
Upstream since v6.11.
Very simple change as the OOB identifying bits are same as for the prior
generation CPUs like Sapphire Rapids servers, so also add Emerald Rapids to the
intel_pstate_cpu_oob_ids[] list.
[Test Plan]
Set HW PM OOB mode in BIOS power management config.
Make sure that no cpufreq drivers are loaded. You can verify that
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver is not present or any cpufreq interface.
It's also already part of linux-aws:
https://bugs.launchpad.net/bugs/2078894
-
[Where problems could occur]
cpufreq regression.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2084834
Title:
[SRU] cpufreq: intel_pstate: Support Emerald Rapids OOB mode
Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
New
Bug description:
This is a public version of: https://bugs.launchpad.net/bugs/2078894
[Impact]
In Emerald Rapids VMs with OOB P-states enabled, a stack trace is
printed during boot on 6.8 based kernels. The stack traces look like:
[ 1.206658] intel_pstate: Intel P-state driver initializing
[ 1.207453] unchecked MSR access error: WRMSR to 0x199 (tried to write 0x0000000000000800) at rIP: 0xffffffffb94c3b24 (native_write_msr+0x4/0x40)
[ 1.208422] Call Trace:
[ 1.208422] <TASK>
[ 1.208422] ? show_stack_regs+0x23/0x40
[ 1.208422] ? ex_handler_msr+0x10a/0x180
[ 1.208422] ? fixup_exception+0x183/0x390
[ 1.208422] ? gp_try_fixup_and_notify+0x23/0xc0
[ 1.208422] ? exc_general_protection+0x15e/0x480
[ 1.208422] ? asm_exc_general_protection+0x27/0x30
[ 1.208422] ? __pfx___wrmsr_on_cpu+0x10/0x10
[ 1.208422] ? native_write_msr+0x4/0x40
[ 1.208422] ? __wrmsr_on_cpu+0x4b/0x90
[ 1.208422] ? __pfx___rdmsr_on_cpu+0x10/0x10
[ 1.208422] ? __pfx___wrmsr_on_cpu+0x10/0x10
[ 1.208422] generic_exec_single+0x7e/0x120
[ 1.208422] smp_call_function_single+0x103/0x140
[ 1.208422] ? __pfx___wrmsr_on_cpu+0x10/0x10
[ 1.208422] wrmsrl_on_cpu+0x57/0x80
[ 1.208422] intel_pstate_set_pstate+0x3e/0x80
[ 1.208422] intel_pstate_get_cpu_pstates.constprop.0+0xd7/0x190
[ 1.208422] intel_pstate_init_cpu+0x3f/0x140
[ 1.208422] intel_cpufreq_cpu_init+0x44/0x270
[ 1.208422] ? freq_qos_add_notifier+0x45/0x80
[ 1.208422] cpufreq_online+0x444/0xb80
[ 1.208422] cpufreq_add_dev+0x99/0xd0
[ 1.208422] subsys_interface_register+0x11c/0x140
[ 1.208422] cpufreq_register_driver+0x1b5/0x330
[ 1.208422] intel_pstate_register_driver+0x48/0xd0
[ 1.208422] intel_pstate_init+0x25c/0x810
[ 1.208422] ? __pfx_intel_pstate_init+0x10/0x10
[ 1.208422] do_one_initcall+0x5b/0x310
[ 1.208422] do_initcalls+0x104/0x210
[ 1.208422] ? __pfx_kernel_init+0x10/0x10
[ 1.208422] kernel_init_freeable+0x134/0x1f0
[ 1.208422] kernel_init+0x1b/0x200
[ 1.208422] ret_from_fork+0x44/0x70
[ 1.208422] ? __pfx_kernel_init+0x10/0x10
[ 1.208422] ret_from_fork_asm+0x1b/0x30
[ 1.208422] </TASK>
[Fix]
Cherry pick of 7e1c3f584ee7 - cpufreq: intel_pstate: Support Emerald Rapids OOB mode
Upstream since v6.11.
Very simple change as the OOB identifying bits are same as for the prior
generation CPUs like Sapphire Rapids servers, so also add Emerald Rapids to the
intel_pstate_cpu_oob_ids[] list.
[Test Plan]
Set HW PM OOB mode in BIOS power management config.
Make sure that no cpufreq drivers are loaded. You can verify that
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver is not present or any cpufreq interface.
It's also already part of linux-aws:
https://bugs.launchpad.net/bugs/2078894
[Where problems could occur]
cpufreq regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2084834/+subscriptions
[Bug 2064508] Re: re-enable Ubuntu FAN in the Noble kernel
** Tags removed: verification-needed-oracular-linux
** Tags added: verification-done-oracular-linux
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2064508
Title:
re-enable Ubuntu FAN in the Noble kernel
Status in iproute2 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in iproute2 source package in Noble:
Invalid
Status in linux source package in Noble:
Fix Released
Status in iproute2 source package in Oracular:
Fix Released
Status in linux source package in Oracular:
In Progress
Bug description:
[Impact]
In LP: #2063298, we have opted to deprecate Ubuntu FAN support because
of the maintenance overhead and the possibility of regressions /
conflicts with the new networking eBPF APIs in kernels >= 6.8.
However, we cannot disable this feature in HWE/backport kernels, so it
seems safer to adjust the Ubuntu FAN kernel patch set to ensure proper
co-existence with the updated vxlan policy requirements in newer 6.8
kernels.
The re-introduction of Ubuntu FAN should be considered as a temporary
measure, aimed at facilitating a smooth transition during its
deprecation without disrupting existing users (specifically Juju), and
enabling the backporting of 6.8 kernels to older releases.
The main plan is still to deprecate Ubuntu FAN at some point in the
future.
[Test case]
Rely on the specific Ubuntu FAN regression test to validate the proper
kernel support of this feature:
https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-
tests/tree/ubuntu_fan_smoke_test?h=autotest3
[Fix]
Re-apply the Ubuntu FAN patch set to the latest Noble kernel 6.8 and
integrate the IFLA_VXLAN_FAN_MAP attribute type in vxlan_policy to
satisfy the strict length validation check.
[Regression potential]
We may experience regressions with eBPF vxlan capabilities and
potentially specific use cases of the Ubuntu FAN technology (Juju
installations).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2064508/+subscriptions
** Tags added: verification-done-oracular-linux
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2064508
Title:
re-enable Ubuntu FAN in the Noble kernel
Status in iproute2 package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
In Progress
Status in iproute2 source package in Noble:
Invalid
Status in linux source package in Noble:
Fix Released
Status in iproute2 source package in Oracular:
Fix Released
Status in linux source package in Oracular:
In Progress
Bug description:
[Impact]
In LP: #2063298, we have opted to deprecate Ubuntu FAN support because
of the maintenance overhead and the possibility of regressions /
conflicts with the new networking eBPF APIs in kernels >= 6.8.
However, we cannot disable this feature in HWE/backport kernels, so it
seems safer to adjust the Ubuntu FAN kernel patch set to ensure proper
co-existence with the updated vxlan policy requirements in newer 6.8
kernels.
The re-introduction of Ubuntu FAN should be considered as a temporary
measure, aimed at facilitating a smooth transition during its
deprecation without disrupting existing users (specifically Juju), and
enabling the backporting of 6.8 kernels to older releases.
The main plan is still to deprecate Ubuntu FAN at some point in the
future.
[Test case]
Rely on the specific Ubuntu FAN regression test to validate the proper
kernel support of this feature:
https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-
tests/tree/ubuntu_fan_smoke_test?h=autotest3
[Fix]
Re-apply the Ubuntu FAN patch set to the latest Noble kernel 6.8 and
integrate the IFLA_VXLAN_FAN_MAP attribute type in vxlan_policy to
satisfy the strict length validation check.
[Regression potential]
We may experience regressions with eBPF vxlan capabilities and
potentially specific use cases of the Ubuntu FAN technology (Juju
installations).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2064508/+subscriptions
Подписаться на:
Сообщения (Atom)