Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2088733
Title:
low CPU frequency after wake up AMD Ryzen
Status in linux package in Ubuntu:
Confirmed
Bug description:
After wake up I can see at least once a week issue with CPU frequency
not going up. When running:
$ watch lscpu -e=CPU,MHZ
standard output looks like:
CPU MHZ
0 400.0000
1 1383.2480
2 400.0000
3 400.0000
4 400.0000
5 2699.7561
6 1288.0500
7 400.0000
8 400.0000
9 400.0000
10 400.0000
11 400.0000
12 3244.0720
13 400.0000
14 400.0000
15 1295.9050
while when the issue occurs, I can't see 600 Mhz or higher values in
the same graph. Which also means that response time of computer is
much lower and everything feels lazy.
Restart fixes the issue or plug power cable off and in again.
My CPU is AMD Ryzen™ 7 PRO 7840HS w/ Radeon™ 780M Graphics × 16
My kernel version: 6.8.0-48-generic #48-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 14:04:52 UTC 2024
OS version: Ubuntu 24.04.1 LTS
My laptop: HP ZBook Firefly 14 inch G10 A Mobile Workstation PC
I know about one more person with same machine type with the issue and
there is also this question on askubuntu which says there is third
person with this issue.
https://askubuntu.com/questions/1531956/cpu-too-slow-after-waking-up-
in-ubuntu-24-04-1
This bug looks pretty similar however should be fixed already, so creating new one
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2088733/+subscriptions
среда
[Bug 2088733] Re: low CPU frequency after wake up AMD Ryzen
Well, I have the exact same issue but for me the issue is completely uncorrelated with being plugged in or out. That means, I have faced the issue in all the following scenarios:
(1) plugged in the all the time
(2) plugged out all the time
(3) plugged in - suspend - plugged out - wake up
(4) plugged out - suspend - plugged in - wake up
However, I think all the times the issue appeared I had closed the lid!
I have Thinkpad, amd 7940hs, ubuntu 2.04.1 6.8.0.49
BIOS is allways updated to the latest version. Must be a linux issue because never faced this problem in windows.
Linux has never been kind to any hardware which is not too old, but this is utter nonsense.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2088733
Title:
low CPU frequency after wake up AMD Ryzen
Status in linux package in Ubuntu:
Confirmed
Bug description:
After wake up I can see at least once a week issue with CPU frequency
not going up. When running:
$ watch lscpu -e=CPU,MHZ
standard output looks like:
CPU MHZ
0 400.0000
1 1383.2480
2 400.0000
3 400.0000
4 400.0000
5 2699.7561
6 1288.0500
7 400.0000
8 400.0000
9 400.0000
10 400.0000
11 400.0000
12 3244.0720
13 400.0000
14 400.0000
15 1295.9050
while when the issue occurs, I can't see 600 Mhz or higher values in
the same graph. Which also means that response time of computer is
much lower and everything feels lazy.
Restart fixes the issue or plug power cable off and in again.
My CPU is AMD Ryzen™ 7 PRO 7840HS w/ Radeon™ 780M Graphics × 16
My kernel version: 6.8.0-48-generic #48-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 14:04:52 UTC 2024
OS version: Ubuntu 24.04.1 LTS
My laptop: HP ZBook Firefly 14 inch G10 A Mobile Workstation PC
I know about one more person with same machine type with the issue and
there is also this question on askubuntu which says there is third
person with this issue.
https://askubuntu.com/questions/1531956/cpu-too-slow-after-waking-up-
in-ubuntu-24-04-1
This bug looks pretty similar however should be fixed already, so creating new one
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2088733/+subscriptions
(1) plugged in the all the time
(2) plugged out all the time
(3) plugged in - suspend - plugged out - wake up
(4) plugged out - suspend - plugged in - wake up
However, I think all the times the issue appeared I had closed the lid!
I have Thinkpad, amd 7940hs, ubuntu 2.04.1 6.8.0.49
BIOS is allways updated to the latest version. Must be a linux issue because never faced this problem in windows.
Linux has never been kind to any hardware which is not too old, but this is utter nonsense.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2088733
Title:
low CPU frequency after wake up AMD Ryzen
Status in linux package in Ubuntu:
Confirmed
Bug description:
After wake up I can see at least once a week issue with CPU frequency
not going up. When running:
$ watch lscpu -e=CPU,MHZ
standard output looks like:
CPU MHZ
0 400.0000
1 1383.2480
2 400.0000
3 400.0000
4 400.0000
5 2699.7561
6 1288.0500
7 400.0000
8 400.0000
9 400.0000
10 400.0000
11 400.0000
12 3244.0720
13 400.0000
14 400.0000
15 1295.9050
while when the issue occurs, I can't see 600 Mhz or higher values in
the same graph. Which also means that response time of computer is
much lower and everything feels lazy.
Restart fixes the issue or plug power cable off and in again.
My CPU is AMD Ryzen™ 7 PRO 7840HS w/ Radeon™ 780M Graphics × 16
My kernel version: 6.8.0-48-generic #48-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 14:04:52 UTC 2024
OS version: Ubuntu 24.04.1 LTS
My laptop: HP ZBook Firefly 14 inch G10 A Mobile Workstation PC
I know about one more person with same machine type with the issue and
there is also this question on askubuntu which says there is third
person with this issue.
https://askubuntu.com/questions/1531956/cpu-too-slow-after-waking-up-
in-ubuntu-24-04-1
This bug looks pretty similar however should be fixed already, so creating new one
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2088733/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-oracle-5.15/5.15.0-1071.77~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-oracle-5.15 (5.15.0-1071.77~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/unknown (armhf)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-oracle-5.15
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/unknown (armhf)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-oracle-5.15
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-gcp-5.15/5.15.0-1072.80~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-gcp-5.15 (5.15.0-1072.80~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/unknown (armhf)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-gcp-5.15
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/unknown (armhf)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#linux-restricted-modules-gcp-5.15
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 2088733] Re: low CPU frequency after wake up AMD Ryzen
there are no updates:
$ sudo fwupdmgr update
Devices with no available firmware updates:
• ELAN07A8:00 04F3:31EC
• HP 5MP Camera
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• WD PC SN810 SDCPNRZ-2T00-1006
Devices with the latest available firmware version:
• Prometheus
• Prometheus IOTA Config
• System Firmware
• UEFI dbx
I tried to update the BIOS from BIOS where I could see version of BIOS
is from August this year. I was not able to confirm there is newer
version of BIOS available. I suppose I could try to write email to HP
support to confirm that information.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2088733
Title:
low CPU frequency after wake up AMD Ryzen
Status in linux package in Ubuntu:
New
Bug description:
After wake up I can see at least once a week issue with CPU frequency
not going up. When running:
$ watch lscpu -e=CPU,MHZ
standard output looks like:
CPU MHZ
0 400.0000
1 1383.2480
2 400.0000
3 400.0000
4 400.0000
5 2699.7561
6 1288.0500
7 400.0000
8 400.0000
9 400.0000
10 400.0000
11 400.0000
12 3244.0720
13 400.0000
14 400.0000
15 1295.9050
while when the issue occurs, I can't see 600 Mhz or higher values in
the same graph. Which also means that response time of computer is
much lower and everything feels lazy.
Restart fixes the issue or plug power cable off and in again.
My CPU is AMD Ryzen™ 7 PRO 7840HS w/ Radeon™ 780M Graphics × 16
My kernel version: 6.8.0-48-generic #48-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 14:04:52 UTC 2024
OS version: Ubuntu 24.04.1 LTS
My laptop: HP ZBook Firefly 14 inch G10 A Mobile Workstation PC
I know about one more person with same machine type with the issue and
there is also this question on askubuntu which says there is third
person with this issue.
https://askubuntu.com/questions/1531956/cpu-too-slow-after-waking-up-
in-ubuntu-24-04-1
This bug looks pretty similar however should be fixed already, so creating new one
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2088733/+subscriptions
$ sudo fwupdmgr update
Devices with no available firmware updates:
• ELAN07A8:00 04F3:31EC
• HP 5MP Camera
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• UEFI Device Firmware
• WD PC SN810 SDCPNRZ-2T00-1006
Devices with the latest available firmware version:
• Prometheus
• Prometheus IOTA Config
• System Firmware
• UEFI dbx
I tried to update the BIOS from BIOS where I could see version of BIOS
is from August this year. I was not able to confirm there is newer
version of BIOS available. I suppose I could try to write email to HP
support to confirm that information.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2088733
Title:
low CPU frequency after wake up AMD Ryzen
Status in linux package in Ubuntu:
New
Bug description:
After wake up I can see at least once a week issue with CPU frequency
not going up. When running:
$ watch lscpu -e=CPU,MHZ
standard output looks like:
CPU MHZ
0 400.0000
1 1383.2480
2 400.0000
3 400.0000
4 400.0000
5 2699.7561
6 1288.0500
7 400.0000
8 400.0000
9 400.0000
10 400.0000
11 400.0000
12 3244.0720
13 400.0000
14 400.0000
15 1295.9050
while when the issue occurs, I can't see 600 Mhz or higher values in
the same graph. Which also means that response time of computer is
much lower and everything feels lazy.
Restart fixes the issue or plug power cable off and in again.
My CPU is AMD Ryzen™ 7 PRO 7840HS w/ Radeon™ 780M Graphics × 16
My kernel version: 6.8.0-48-generic #48-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 14:04:52 UTC 2024
OS version: Ubuntu 24.04.1 LTS
My laptop: HP ZBook Firefly 14 inch G10 A Mobile Workstation PC
I know about one more person with same machine type with the issue and
there is also this question on askubuntu which says there is third
person with this issue.
https://askubuntu.com/questions/1531956/cpu-too-slow-after-waking-up-
in-ubuntu-24-04-1
This bug looks pretty similar however should be fixed already, so creating new one
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2088733/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-gke/5.15.0.1070.69)
All autopkgtests for the newly accepted linux-meta-gke (5.15.0.1070.69) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-470-server/unknown (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-gke
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-470-server/unknown (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-gke
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta/6.8.0-50.51)
All autopkgtests for the newly accepted linux-meta (6.8.0-50.51) for noble have finished running.
The following regressions have been reported in tests triggered by the package:
casper/1.498 (amd64)
glibc/2.39-0ubuntu8.3 (ppc64el)
lxc/unknown (ppc64el)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#linux-meta
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
The following regressions have been reported in tests triggered by the package:
casper/1.498 (amd64)
glibc/2.39-0ubuntu8.3 (ppc64el)
lxc/unknown (ppc64el)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#linux-meta
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
Fire Kirin APK offers exciting challenges with rewards to keep players
engaged. https://fire-kirinapk.com/
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1258837
Title:
[Dell Latitude E7440] ALPS touchpad keeps having state reset
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Utopic:
Fix Released
Status in linux source package in Vivid:
Fix Released
Status in linux package in Fedora:
Won't Fix
Bug description:
The mouse cursor keeps on jumping around, and these messages appear in the log when it happens:
Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced.
Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced.
The touchpad is recognised as a "AlpsPS/2 ALPS DualPoint TouchPad".
This is occurring with Ubuntu 13.10, though I have also seen this
behaviour in the version of Linux Mint based on Ubuntu 13.04.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-14-generic 3.11.0-14.21
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: allanc 1852 F.... pulseaudio
/dev/snd/controlC0: allanc 1852 F.... pulseaudio
Date: Sat Dec 7 22:19:22 2013
HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec
InstallationDate: Installed on 2013-12-07 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Dell Inc. Latitude E7440
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.11.0-14-generic N/A
linux-backports-modules-3.11.0-14-generic N/A
linux-firmware 1.116
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 07F3F4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7440
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+subscriptions
engaged. https://fire-kirinapk.com/
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1258837
Title:
[Dell Latitude E7440] ALPS touchpad keeps having state reset
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Utopic:
Fix Released
Status in linux source package in Vivid:
Fix Released
Status in linux package in Fedora:
Won't Fix
Bug description:
The mouse cursor keeps on jumping around, and these messages appear in the log when it happens:
Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced.
Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced.
The touchpad is recognised as a "AlpsPS/2 ALPS DualPoint TouchPad".
This is occurring with Ubuntu 13.10, though I have also seen this
behaviour in the version of Linux Mint based on Ubuntu 13.04.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-14-generic 3.11.0-14.21
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: allanc 1852 F.... pulseaudio
/dev/snd/controlC0: allanc 1852 F.... pulseaudio
Date: Sat Dec 7 22:19:22 2013
HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec
InstallationDate: Installed on 2013-12-07 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Dell Inc. Latitude E7440
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.11.0-14-generic N/A
linux-backports-modules-3.11.0-14-generic N/A
linux-firmware 1.116
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 07F3F4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7440
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+subscriptions
[Bug 1258837] Re: [Dell Latitude E7440] ALPS touchpad keeps having state reset
The Toca Boca World MOD APK version is easy to install and provides an
ad-free experience. https://apktocalife.com/
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1258837
Title:
[Dell Latitude E7440] ALPS touchpad keeps having state reset
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Utopic:
Fix Released
Status in linux source package in Vivid:
Fix Released
Status in linux package in Fedora:
Won't Fix
Bug description:
The mouse cursor keeps on jumping around, and these messages appear in the log when it happens:
Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced.
Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced.
The touchpad is recognised as a "AlpsPS/2 ALPS DualPoint TouchPad".
This is occurring with Ubuntu 13.10, though I have also seen this
behaviour in the version of Linux Mint based on Ubuntu 13.04.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-14-generic 3.11.0-14.21
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: allanc 1852 F.... pulseaudio
/dev/snd/controlC0: allanc 1852 F.... pulseaudio
Date: Sat Dec 7 22:19:22 2013
HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec
InstallationDate: Installed on 2013-12-07 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Dell Inc. Latitude E7440
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.11.0-14-generic N/A
linux-backports-modules-3.11.0-14-generic N/A
linux-firmware 1.116
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 07F3F4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7440
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+subscriptions
ad-free experience. https://apktocalife.com/
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1258837
Title:
[Dell Latitude E7440] ALPS touchpad keeps having state reset
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Utopic:
Fix Released
Status in linux source package in Vivid:
Fix Released
Status in linux package in Fedora:
Won't Fix
Bug description:
The mouse cursor keeps on jumping around, and these messages appear in the log when it happens:
Dec 7 21:57:26 wyvern kernel: [ 648.133841] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Dec 7 21:57:26 wyvern kernel: [ 648.134868] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Dec 7 21:57:26 wyvern kernel: [ 648.137921] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced.
Dec 7 21:57:26 wyvern kernel: [ 648.138852] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 lost sync at byte 1
Dec 7 21:57:26 wyvern kernel: [ 648.148833] psmouse serio1: DualPoint TouchPad at isa0060/serio1/input0 - driver resynced.
The touchpad is recognised as a "AlpsPS/2 ALPS DualPoint TouchPad".
This is occurring with Ubuntu 13.10, though I have also seen this
behaviour in the version of Linux Mint based on Ubuntu 13.04.
ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-14-generic 3.11.0-14.21
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: allanc 1852 F.... pulseaudio
/dev/snd/controlC0: allanc 1852 F.... pulseaudio
Date: Sat Dec 7 22:19:22 2013
HibernationDevice: RESUME=UUID=a2a36712-35de-4e20-9d1a-df3520f401ec
InstallationDate: Installed on 2013-12-07 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Dell Inc. Latitude E7440
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic.efi.signed root=UUID=d03a42e6-0dea-4969-a682-eb4d255abc70 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.11.0-14-generic N/A
linux-backports-modules-3.11.0-14-generic N/A
linux-firmware 1.116
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 07F3F4
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd08/14/2013:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E7440
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258837/+subscriptions
[Bug 2089113] Re: Keyboard backlight controls do not work on Asus ROG Zephyrus GA503RM in Oracular
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Oracular)
Status: New => In Progress
** Changed in: linux (Ubuntu Oracular)
Assignee: (unassigned) => Mitchell Augustin (mitchellaugustin)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2089113
Title:
Keyboard backlight controls do not work on Asus ROG Zephyrus GA503RM
in Oracular
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Oracular:
In Progress
Bug description:
SRU Justification:
[ Impact ]
The brightness of some ASUS ROG laptop keyboards cannot be adjusted
without this patch.
[ Test Plan ]
I verified that this patch applies cleanly to the Oracular kernel
at Ubuntu-6.11.0-9.9 and resolves the bug on my laptop
(Asus ROG GA503RM). I observed no regressions. This can be verified
on any similar model of laptop by testing keyboard brightness controls
once patched.
[ Fix ]
On almost all ASUS ROG series laptops the MCU used for the USB keyboard
also has a HID packet used for setting the brightness. This is usually
the same as the WMI method. But in some laptops the WMI method either
is missing or doesn't work, so we should default to the HID control.
[ Where problems could occur ]
I do not expect any regressions since this only touches parts of
asus-wmi and hid-asus that are covered by my test case, which worked
as intended.
[ Changes since v1 of this patch set ]
A patch series that fixes this is already upstream: https://lore.kernel.org/all/20240713074733.77334-2-luke@ljones.dev/
Corrected patch format issues
Luke D. Jones (1):
hid-asus: use hid for brightness control on keyboard
drivers/hid/hid-asus.c | 7 +++++
drivers/platform/x86/asus-wmi.c | 3 +-
include/linux/platform_data/x86/asus-wmi.h | 36 ++++++++++++++++++++++
3 files changed, 45 insertions(+), 1 deletion(-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2089113/+subscriptions
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Oracular)
Status: New => In Progress
** Changed in: linux (Ubuntu Oracular)
Assignee: (unassigned) => Mitchell Augustin (mitchellaugustin)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2089113
Title:
Keyboard backlight controls do not work on Asus ROG Zephyrus GA503RM
in Oracular
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Oracular:
In Progress
Bug description:
SRU Justification:
[ Impact ]
The brightness of some ASUS ROG laptop keyboards cannot be adjusted
without this patch.
[ Test Plan ]
I verified that this patch applies cleanly to the Oracular kernel
at Ubuntu-6.11.0-9.9 and resolves the bug on my laptop
(Asus ROG GA503RM). I observed no regressions. This can be verified
on any similar model of laptop by testing keyboard brightness controls
once patched.
[ Fix ]
On almost all ASUS ROG series laptops the MCU used for the USB keyboard
also has a HID packet used for setting the brightness. This is usually
the same as the WMI method. But in some laptops the WMI method either
is missing or doesn't work, so we should default to the HID control.
[ Where problems could occur ]
I do not expect any regressions since this only touches parts of
asus-wmi and hid-asus that are covered by my test case, which worked
as intended.
[ Changes since v1 of this patch set ]
A patch series that fixes this is already upstream: https://lore.kernel.org/all/20240713074733.77334-2-luke@ljones.dev/
Corrected patch format issues
Luke D. Jones (1):
hid-asus: use hid for brightness control on keyboard
drivers/hid/hid-asus.c | 7 +++++
drivers/platform/x86/asus-wmi.c | 3 +-
include/linux/platform_data/x86/asus-wmi.h | 36 ++++++++++++++++++++++
3 files changed, 45 insertions(+), 1 deletion(-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2089113/+subscriptions
[Bug 2089113] Re: Keyboard backlight controls do not work on Asus ROG Zephyrus GA503RM in Oracular
** Tags added: oracular
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2089113
Title:
Keyboard backlight controls do not work on Asus ROG Zephyrus GA503RM
in Oracular
Status in linux package in Ubuntu:
In Progress
Bug description:
SRU Justification:
[ Impact ]
The brightness of some ASUS ROG laptop keyboards cannot be adjusted
without this patch.
[ Test Plan ]
I verified that this patch applies cleanly to the Oracular kernel
at Ubuntu-6.11.0-9.9 and resolves the bug on my laptop
(Asus ROG GA503RM). I observed no regressions. This can be verified
on any similar model of laptop by testing keyboard brightness controls
once patched.
[ Fix ]
On almost all ASUS ROG series laptops the MCU used for the USB keyboard
also has a HID packet used for setting the brightness. This is usually
the same as the WMI method. But in some laptops the WMI method either
is missing or doesn't work, so we should default to the HID control.
[ Where problems could occur ]
I do not expect any regressions since this only touches parts of
asus-wmi and hid-asus that are covered by my test case, which worked
as intended.
[ Changes since v1 of this patch set ]
A patch series that fixes this is already upstream: https://lore.kernel.org/all/20240713074733.77334-2-luke@ljones.dev/
Corrected patch format issues
Luke D. Jones (1):
hid-asus: use hid for brightness control on keyboard
drivers/hid/hid-asus.c | 7 +++++
drivers/platform/x86/asus-wmi.c | 3 +-
include/linux/platform_data/x86/asus-wmi.h | 36 ++++++++++++++++++++++
3 files changed, 45 insertions(+), 1 deletion(-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2089113/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2089113
Title:
Keyboard backlight controls do not work on Asus ROG Zephyrus GA503RM
in Oracular
Status in linux package in Ubuntu:
In Progress
Bug description:
SRU Justification:
[ Impact ]
The brightness of some ASUS ROG laptop keyboards cannot be adjusted
without this patch.
[ Test Plan ]
I verified that this patch applies cleanly to the Oracular kernel
at Ubuntu-6.11.0-9.9 and resolves the bug on my laptop
(Asus ROG GA503RM). I observed no regressions. This can be verified
on any similar model of laptop by testing keyboard brightness controls
once patched.
[ Fix ]
On almost all ASUS ROG series laptops the MCU used for the USB keyboard
also has a HID packet used for setting the brightness. This is usually
the same as the WMI method. But in some laptops the WMI method either
is missing or doesn't work, so we should default to the HID control.
[ Where problems could occur ]
I do not expect any regressions since this only touches parts of
asus-wmi and hid-asus that are covered by my test case, which worked
as intended.
[ Changes since v1 of this patch set ]
A patch series that fixes this is already upstream: https://lore.kernel.org/all/20240713074733.77334-2-luke@ljones.dev/
Corrected patch format issues
Luke D. Jones (1):
hid-asus: use hid for brightness control on keyboard
drivers/hid/hid-asus.c | 7 +++++
drivers/platform/x86/asus-wmi.c | 3 +-
include/linux/platform_data/x86/asus-wmi.h | 36 ++++++++++++++++++++++
3 files changed, 45 insertions(+), 1 deletion(-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2089113/+subscriptions
[Bug 2089113] Re: Keyboard backlight controls do not work on Asus ROG Zephyrus GA503RM in Oracular
** Description changed:
+ SRU Justification:
+
+ [ Impact ]
+
+ The brightness of some ASUS ROG laptop keyboards cannot be adjusted
+ without this patch.
+
+ [ Test Plan ]
+
+ I verified that this patch applies cleanly to the Oracular kernel
+ at Ubuntu-6.11.0-9.9 and resolves the bug on my laptop
+ (Asus ROG GA503RM). I observed no regressions. This can be verified
+ on any similar model of laptop by testing keyboard brightness controls
+ once patched.
+
+ [ Fix ]
+
On almost all ASUS ROG series laptops the MCU used for the USB keyboard
also has a HID packet used for setting the brightness. This is usually
the same as the WMI method. But in some laptops the WMI method either
is missing or doesn't work, so we should default to the HID control.
- A patch series that fixes this is already upstream:
- https://lore.kernel.org/all/20240713074733.77334-2-luke@ljones.dev/
- I'm opening this bug to SRU this series into Oracular.
+ [ Where problems could occur ]
+
+ I do not expect any regressions since this only touches parts of
+ asus-wmi and hid-asus that are covered by my test case, which worked
+ as intended.
+
+ [ Changes since v1 of this patch set ]
+
+
+ A patch series that fixes this is already upstream: https://lore.kernel.org/all/20240713074733.77334-2-luke@ljones.dev/
+
+
+ Corrected patch format issues
+
+ Luke D. Jones (1):
+ hid-asus: use hid for brightness control on keyboard
+
+ drivers/hid/hid-asus.c | 7 +++++
+ drivers/platform/x86/asus-wmi.c | 3 +-
+ include/linux/platform_data/x86/asus-wmi.h | 36 ++++++++++++++++++++++
+ 3 files changed, 45 insertions(+), 1 deletion(-)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2089113
Title:
Keyboard backlight controls do not work on Asus ROG Zephyrus GA503RM
in Oracular
Status in linux package in Ubuntu:
In Progress
Bug description:
SRU Justification:
[ Impact ]
The brightness of some ASUS ROG laptop keyboards cannot be adjusted
without this patch.
[ Test Plan ]
I verified that this patch applies cleanly to the Oracular kernel
at Ubuntu-6.11.0-9.9 and resolves the bug on my laptop
(Asus ROG GA503RM). I observed no regressions. This can be verified
on any similar model of laptop by testing keyboard brightness controls
once patched.
[ Fix ]
On almost all ASUS ROG series laptops the MCU used for the USB keyboard
also has a HID packet used for setting the brightness. This is usually
the same as the WMI method. But in some laptops the WMI method either
is missing or doesn't work, so we should default to the HID control.
[ Where problems could occur ]
I do not expect any regressions since this only touches parts of
asus-wmi and hid-asus that are covered by my test case, which worked
as intended.
[ Changes since v1 of this patch set ]
A patch series that fixes this is already upstream: https://lore.kernel.org/all/20240713074733.77334-2-luke@ljones.dev/
Corrected patch format issues
Luke D. Jones (1):
hid-asus: use hid for brightness control on keyboard
drivers/hid/hid-asus.c | 7 +++++
drivers/platform/x86/asus-wmi.c | 3 +-
include/linux/platform_data/x86/asus-wmi.h | 36 ++++++++++++++++++++++
3 files changed, 45 insertions(+), 1 deletion(-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2089113/+subscriptions
+ SRU Justification:
+
+ [ Impact ]
+
+ The brightness of some ASUS ROG laptop keyboards cannot be adjusted
+ without this patch.
+
+ [ Test Plan ]
+
+ I verified that this patch applies cleanly to the Oracular kernel
+ at Ubuntu-6.11.0-9.9 and resolves the bug on my laptop
+ (Asus ROG GA503RM). I observed no regressions. This can be verified
+ on any similar model of laptop by testing keyboard brightness controls
+ once patched.
+
+ [ Fix ]
+
On almost all ASUS ROG series laptops the MCU used for the USB keyboard
also has a HID packet used for setting the brightness. This is usually
the same as the WMI method. But in some laptops the WMI method either
is missing or doesn't work, so we should default to the HID control.
- A patch series that fixes this is already upstream:
- https://lore.kernel.org/all/20240713074733.77334-2-luke@ljones.dev/
- I'm opening this bug to SRU this series into Oracular.
+ [ Where problems could occur ]
+
+ I do not expect any regressions since this only touches parts of
+ asus-wmi and hid-asus that are covered by my test case, which worked
+ as intended.
+
+ [ Changes since v1 of this patch set ]
+
+
+ A patch series that fixes this is already upstream: https://lore.kernel.org/all/20240713074733.77334-2-luke@ljones.dev/
+
+
+ Corrected patch format issues
+
+ Luke D. Jones (1):
+ hid-asus: use hid for brightness control on keyboard
+
+ drivers/hid/hid-asus.c | 7 +++++
+ drivers/platform/x86/asus-wmi.c | 3 +-
+ include/linux/platform_data/x86/asus-wmi.h | 36 ++++++++++++++++++++++
+ 3 files changed, 45 insertions(+), 1 deletion(-)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2089113
Title:
Keyboard backlight controls do not work on Asus ROG Zephyrus GA503RM
in Oracular
Status in linux package in Ubuntu:
In Progress
Bug description:
SRU Justification:
[ Impact ]
The brightness of some ASUS ROG laptop keyboards cannot be adjusted
without this patch.
[ Test Plan ]
I verified that this patch applies cleanly to the Oracular kernel
at Ubuntu-6.11.0-9.9 and resolves the bug on my laptop
(Asus ROG GA503RM). I observed no regressions. This can be verified
on any similar model of laptop by testing keyboard brightness controls
once patched.
[ Fix ]
On almost all ASUS ROG series laptops the MCU used for the USB keyboard
also has a HID packet used for setting the brightness. This is usually
the same as the WMI method. But in some laptops the WMI method either
is missing or doesn't work, so we should default to the HID control.
[ Where problems could occur ]
I do not expect any regressions since this only touches parts of
asus-wmi and hid-asus that are covered by my test case, which worked
as intended.
[ Changes since v1 of this patch set ]
A patch series that fixes this is already upstream: https://lore.kernel.org/all/20240713074733.77334-2-luke@ljones.dev/
Corrected patch format issues
Luke D. Jones (1):
hid-asus: use hid for brightness control on keyboard
drivers/hid/hid-asus.c | 7 +++++
drivers/platform/x86/asus-wmi.c | 3 +-
include/linux/platform_data/x86/asus-wmi.h | 36 ++++++++++++++++++++++
3 files changed, 45 insertions(+), 1 deletion(-)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2089113/+subscriptions
[Bug 2080378] Re: IOMMU warnings on AMD systems after booting into kdump kernel
Jammy verification:
1- Make sure the system is running an AMD epyc CPU with the 5.15 kernel
in proposed for jammy, and that kdump is enabled:
ubuntu@bomberto:~$ cat /etc/os-release | grep VERSION
VERSION_ID="22.04"
VERSION="22.04.5 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ubuntu@bomberto:~$ kdump-config show
DUMP_MODE: kdump
USE_KDUMP: 1
KDUMP_COREDIR: /var/crash
crashkernel addr: 0x
/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-127-generic
kdump initrd:
/var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-127-generic
current state: ready to kdump
kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-127-generic root=UUID=9502b5f6-5bc4-4d9c-a4e7-be0acb73fa48 ro panic=20 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
ubuntu@bomberto:~$ apt list linux-generic
Listing... Done
linux-generic/jammy-proposed,now 5.15.0.127.126 amd64 [installed]
N: There are 3 additional versions. Please use the '-a' switch to see them.
ubuntu@bomberto:~$ cat /proc/cpuinfo | grep EPYC
model name : AMD EPYC 7413 24-Core Processor
...
2- causing a kernel panic:
ubuntu@bomberto:~$ sudo su
root@bomberto:/home/ubuntu# echo c > /proc/sysrq-trigger
3- After reboot we can see that no warning are printed in dmesg:
ubuntu@bomberto:~$ sudo dmesg | grep WARNING
ubuntu@bomberto:~$
** Tags removed: verification-needed-jammy-linux
** Tags added: verification-done-jammy-linux
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2080378
Title:
IOMMU warnings on AMD systems after booting into kdump kernel
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Bug description:
[impact]
On some AMD systems, loading into a kdump kernel will show a few warnings IOMMU warnings during early boot. These warnings have not been observed yet to cause any issues but there is a fix upstream for them. Currently only focal-HWE and jammy 5.15 are affected. Newer kernel releases already have the fix. The stack traces look like the following:
[ 9.125703] WARNING: CPU: 0 PID: 1 at drivers/iommu/amd/init.c:829 iommu_init_irq+0x2f2/0x3c0
[ 9.134223] Modules linked in:
[ 9.137283] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.15.0-107-generic #117~20.04.1-Ubuntu
[ 9.145716] Hardware name: <hidden>
[ 9.153111] RIP: 0010:iommu_init_irq+0x2f2/0x3c0
[ 9.157729] Code: 90 ff 85 c0 0f 84 e8 fd ff ff be 01 00 00 00 44 89 ef 89 45 94 e8 2e dc 90 ff 4c 89 e7 e8 b6 cf 90 ff 8b 45 94 e9 6c fd ff ff <0f> 0b 31 c0 e9 63 fd ff ff 0f 0b 31 c0 e9 5a fd ff ff 31 c9 48 c7
[ 9.176475] RSP: 0018:ffffa005000fbd00 EFLAGS: 00010202
[ 9.181703] RAX: 0000000000000198 RBX: ffff9335af44a000 RCX: ffffa00500100000
[ 9.188838] RDX: ffffa00500100000 RSI: ffff9335c05b9140 RDI: ffff9335c05b95c8
[ 9.195970] RBP: ffffa005000fbd70 R08: ffffffffffffffff R09: 0000000000000000
[ 9.203101] R10: ffffffe000000000 R11: 0000000000000025 R12: ffff9335c0468cc0
[ 9.210231] R13: 000000000000001a R14: ffff9335b0151600 R15: 0000000000000006
[ 9.217362] FS: 0000000000000000(0000) GS:ffff9336aec00000(0000) knlGS:0000000000000000
[ 9.225446] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 9.231185] CR2: 0000000000000000 CR3: 000002006c810000 CR4: 0000000000350ef0
[ 9.238318] Call Trace:
[ 9.240763] <TASK>
[ 9.242869] ? show_regs.cold+0x1a/0x1f
[ 9.246710] ? iommu_init_irq+0x2f2/0x3c0
[ 9.250722] ? __warn+0x8b/0xe0
[ 9.253868] ? iommu_init_irq+0x2f2/0x3c0
[ 9.257883] ? report_bug+0xd5/0x110
[ 9.261461] ? handle_bug+0x39/0x90
[ 9.264956] ? exc_invalid_op+0x19/0x70
[ 9.268794] ? asm_exc_invalid_op+0x1b/0x20
[ 9.272980] ? iommu_init_irq+0x2f2/0x3c0
[ 9.276993] ? e820__memblock_setup+0x89/0x89
[ 9.281353] state_next+0x3f5/0x6ba
[ 9.284847] ? e820__memblock_setup+0x89/0x89
[ 9.289206] iommu_go_to_state+0x28/0x31
[ 9.293131] amd_iommu_init+0x15/0x4f
[ 9.296797] ? e820__memblock_setup+0x89/0x89
[ 9.301150] pci_iommu_init+0x1a/0x48
[ 9.304817] do_one_initcall+0x48/0x1e0
[ 9.308655] kernel_init_freeable+0x284/0x2f1
[ 9.313016] ? rest_init+0x100/0x100
[ 9.316593] kernel_init+0x1b/0x150
[ 9.320078] ? rest_init+0x100/0x100
[ 9.323658] ret_from_fork+0x22/0x30
[ 9.327238] </TASK>
[ 9.329431] ---[ end trace 6113ebe8cb8ce54f ]---
The commit that fixes the issue is:
* c5e1a1eb9279 ("iommu/amd: Simplify and Consolidate Virtual APIC
(AVIC) Enablement")
However another commit was also created that fixed compiler warnings
introduced by the above commit:
* be280ea763f7 ("iommu/amd: Fix compile warning in init code")
[Test Plan]
1- On a machine using an AMD CPU and running the focal-hwe or jammy
5.15 kernel, make sure kdump is configured following these steps:
https://ubuntu.com/server/docs/kernel-crash-dump
2- Trigger a kernel panic. This can be done using the command:
$ echo c > /proc/sysrq-trigger
3- When the machine reboots, you will notice IOMMU warnings during the
early phases of the boot process in dmesg.
4- After applying the two commits and repeating step 2. No IOMMU
warnings should show up anymore in dmesg.
[Fix]
Only the first commit of the below list is required to fix the bug, but the second one is good to have to avoid compilation warnings introduced by that commit:
* c5e1a1eb9279 ("iommu/amd: Simplify and Consolidate Virtual APIC (AVIC) Enablement")
* be280ea763f7 ("iommu/amd: Fix compile warning in init code")
[where problems could occur]
* IOMMU can fail to initialize after applying these commits on AMD
systems.
* There is a chance these commits do not fix IOMMU warnings for all
AMD system configurations
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080378/+subscriptions
1- Make sure the system is running an AMD epyc CPU with the 5.15 kernel
in proposed for jammy, and that kdump is enabled:
ubuntu@bomberto:~$ cat /etc/os-release | grep VERSION
VERSION_ID="22.04"
VERSION="22.04.5 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ubuntu@bomberto:~$ kdump-config show
DUMP_MODE: kdump
USE_KDUMP: 1
KDUMP_COREDIR: /var/crash
crashkernel addr: 0x
/var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-127-generic
kdump initrd:
/var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-127-generic
current state: ready to kdump
kexec command:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-127-generic root=UUID=9502b5f6-5bc4-4d9c-a4e7-be0acb73fa48 ro panic=20 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz
ubuntu@bomberto:~$ apt list linux-generic
Listing... Done
linux-generic/jammy-proposed,now 5.15.0.127.126 amd64 [installed]
N: There are 3 additional versions. Please use the '-a' switch to see them.
ubuntu@bomberto:~$ cat /proc/cpuinfo | grep EPYC
model name : AMD EPYC 7413 24-Core Processor
...
2- causing a kernel panic:
ubuntu@bomberto:~$ sudo su
root@bomberto:/home/ubuntu# echo c > /proc/sysrq-trigger
3- After reboot we can see that no warning are printed in dmesg:
ubuntu@bomberto:~$ sudo dmesg | grep WARNING
ubuntu@bomberto:~$
** Tags removed: verification-needed-jammy-linux
** Tags added: verification-done-jammy-linux
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2080378
Title:
IOMMU warnings on AMD systems after booting into kdump kernel
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Committed
Bug description:
[impact]
On some AMD systems, loading into a kdump kernel will show a few warnings IOMMU warnings during early boot. These warnings have not been observed yet to cause any issues but there is a fix upstream for them. Currently only focal-HWE and jammy 5.15 are affected. Newer kernel releases already have the fix. The stack traces look like the following:
[ 9.125703] WARNING: CPU: 0 PID: 1 at drivers/iommu/amd/init.c:829 iommu_init_irq+0x2f2/0x3c0
[ 9.134223] Modules linked in:
[ 9.137283] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.15.0-107-generic #117~20.04.1-Ubuntu
[ 9.145716] Hardware name: <hidden>
[ 9.153111] RIP: 0010:iommu_init_irq+0x2f2/0x3c0
[ 9.157729] Code: 90 ff 85 c0 0f 84 e8 fd ff ff be 01 00 00 00 44 89 ef 89 45 94 e8 2e dc 90 ff 4c 89 e7 e8 b6 cf 90 ff 8b 45 94 e9 6c fd ff ff <0f> 0b 31 c0 e9 63 fd ff ff 0f 0b 31 c0 e9 5a fd ff ff 31 c9 48 c7
[ 9.176475] RSP: 0018:ffffa005000fbd00 EFLAGS: 00010202
[ 9.181703] RAX: 0000000000000198 RBX: ffff9335af44a000 RCX: ffffa00500100000
[ 9.188838] RDX: ffffa00500100000 RSI: ffff9335c05b9140 RDI: ffff9335c05b95c8
[ 9.195970] RBP: ffffa005000fbd70 R08: ffffffffffffffff R09: 0000000000000000
[ 9.203101] R10: ffffffe000000000 R11: 0000000000000025 R12: ffff9335c0468cc0
[ 9.210231] R13: 000000000000001a R14: ffff9335b0151600 R15: 0000000000000006
[ 9.217362] FS: 0000000000000000(0000) GS:ffff9336aec00000(0000) knlGS:0000000000000000
[ 9.225446] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 9.231185] CR2: 0000000000000000 CR3: 000002006c810000 CR4: 0000000000350ef0
[ 9.238318] Call Trace:
[ 9.240763] <TASK>
[ 9.242869] ? show_regs.cold+0x1a/0x1f
[ 9.246710] ? iommu_init_irq+0x2f2/0x3c0
[ 9.250722] ? __warn+0x8b/0xe0
[ 9.253868] ? iommu_init_irq+0x2f2/0x3c0
[ 9.257883] ? report_bug+0xd5/0x110
[ 9.261461] ? handle_bug+0x39/0x90
[ 9.264956] ? exc_invalid_op+0x19/0x70
[ 9.268794] ? asm_exc_invalid_op+0x1b/0x20
[ 9.272980] ? iommu_init_irq+0x2f2/0x3c0
[ 9.276993] ? e820__memblock_setup+0x89/0x89
[ 9.281353] state_next+0x3f5/0x6ba
[ 9.284847] ? e820__memblock_setup+0x89/0x89
[ 9.289206] iommu_go_to_state+0x28/0x31
[ 9.293131] amd_iommu_init+0x15/0x4f
[ 9.296797] ? e820__memblock_setup+0x89/0x89
[ 9.301150] pci_iommu_init+0x1a/0x48
[ 9.304817] do_one_initcall+0x48/0x1e0
[ 9.308655] kernel_init_freeable+0x284/0x2f1
[ 9.313016] ? rest_init+0x100/0x100
[ 9.316593] kernel_init+0x1b/0x150
[ 9.320078] ? rest_init+0x100/0x100
[ 9.323658] ret_from_fork+0x22/0x30
[ 9.327238] </TASK>
[ 9.329431] ---[ end trace 6113ebe8cb8ce54f ]---
The commit that fixes the issue is:
* c5e1a1eb9279 ("iommu/amd: Simplify and Consolidate Virtual APIC
(AVIC) Enablement")
However another commit was also created that fixed compiler warnings
introduced by the above commit:
* be280ea763f7 ("iommu/amd: Fix compile warning in init code")
[Test Plan]
1- On a machine using an AMD CPU and running the focal-hwe or jammy
5.15 kernel, make sure kdump is configured following these steps:
https://ubuntu.com/server/docs/kernel-crash-dump
2- Trigger a kernel panic. This can be done using the command:
$ echo c > /proc/sysrq-trigger
3- When the machine reboots, you will notice IOMMU warnings during the
early phases of the boot process in dmesg.
4- After applying the two commits and repeating step 2. No IOMMU
warnings should show up anymore in dmesg.
[Fix]
Only the first commit of the below list is required to fix the bug, but the second one is good to have to avoid compilation warnings introduced by that commit:
* c5e1a1eb9279 ("iommu/amd: Simplify and Consolidate Virtual APIC (AVIC) Enablement")
* be280ea763f7 ("iommu/amd: Fix compile warning in init code")
[where problems could occur]
* IOMMU can fail to initialize after applying these commits on AMD
systems.
* There is a chance these commits do not fix IOMMU warnings for all
AMD system configurations
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080378/+subscriptions
Подписаться на:
Сообщения (Atom)