Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#51322 - [linux] idma64 leads to high usage after boot, vanishes after suspend
Attached to Project:
Arch Linux
Opened by Thomas Bohn (tehabe) - Tuesday, 11 October 2016, 10:32 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 03 March 2022, 11:48 GMT
Opened by Thomas Bohn (tehabe) - Tuesday, 11 October 2016, 10:32 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 03 March 2022, 11:48 GMT
|
DetailsDescription:
After boot the interrupt idma64.0 shows high usage in powertop and prevents the processor from idling and resulting in higher energy consumption. Additional info: linux 4.7.6-1 and 4.8.1-1 Steps to reproduce: boot and launch powertop to confirm that idma64 is waking up the system 481 mW 1.1 ms/s 417.2 Interrupt [16] idma64.0 After suspend this entry is no longer visible. |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Thursday, 03 March 2022, 11:48 GMT
Reason for closing: Fixed
Additional comments about closing: 2022-02-27: A task closure has been requested. Reason for request: No updates in years. Let's assume fixed upstream.
Thursday, 03 March 2022, 11:48 GMT
Reason for closing: Fixed
Additional comments about closing: 2022-02-27: A task closure has been requested. Reason for request: No updates in years. Let's assume fixed upstream.
Comment by Doug Newgard (Scimmia) -
Tuesday, 11 October 2016, 14:26 GMT
Reporting upstream kernel issues here isn't going to do much.
Comment by Thomas Bohn (tehabe) -
Monday, 21 November 2016, 02:46 GMT
I reported it to the Kernel bug tracker and also added some information about it. But that didn't help either.