Bug#655944: marked as done (linux-image-3.1.0-1-amd64: Kernel threads use significant amount of CPU)
Your message dated Sat, 24 Apr 2021 06:04:48 -0700 (PDT) with message-id <60841770.1c69fb81.25338.6...@mx.google.com> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #655944, regarding linux-image-3.1.0-1-amd64: Kernel threads use significant amount of CPU to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 655944: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 3.1.8-2 Severity: normal On my laptop, kernel threads use somewhere between 25% - 80% of one of the CPUs, even on idle. At the suggestion of a friend, I looked at the contents of /sys/firmware/acpi/interrupts/, and noticed that gpe18 was rising at about 10 a second. Searching through the standard logfiles didn't show anything related to gpe18, however looking through the installation logs, I found this line ACPI Error: No handler or method for GPE[18], disabling event (20090903/evgpe-706) which suggested that the issue was with ACPI. Decompiling the dsdt table and then recompiling according to http://en.gentoo- wiki.com/wiki/ACPI/Fix_common_problems in order to try to guess what hardware was the issue, gave me the three following errors: dsdt.dsl 2124: 0x, // Length Error4122 - ^ Invalid combination of Length and Min/Max fixed flags dsdt.dsl 2131: 0x07E0, // Length Error4118 - ^ Length is not equal to fixed Min/Max window dsdt.dsl 2138: 0x0F00, // Length Error4118 - ^ Length is not equal to fixed Min/Max window Is there any other information that would be useful in finding out why the CPU usage is so high? -- Package-specific info: ** Version: Linux version 3.1.0-1-amd64 (Debian 3.1.8-2) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-11) ) #1 SMP Tue Jan 10 05:01:58 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.1.0-1-amd64 root=/dev/mapper/pandora-root ro quiet ** Not tainted ** Kernel log: [5.369898] ATOM BIOS: Lenovo [5.369958] radeon :01:00.0: VRAM: 1024M 0x - 0x3FFF (1024M used) [5.369962] radeon :01:00.0: GTT: 512M 0x4000 - 0x5FFF [5.377902] iwlagn :03:00.0: device EEPROM VER=0x15d, CALIB=0x6 [5.377906] iwlagn :03:00.0: Device SKU: 0X50 [5.377909] iwlagn :03:00.0: Valid Tx ant: 0X1, Valid Rx ant: 0X3 [5.381232] iwlagn :03:00.0: Tunable channels: 13 802.11bg, 0 802.11a channels [5.381236] [drm] Detected VRAM RAM=1024M, BAR=256M [5.381239] [drm] RAM width 128bits DDR [5.381294] [TTM] Zone kernel: Available graphics memory: 4089264 kiB. [5.381296] [TTM] Zone dma32: Available graphics memory: 2097152 kiB. [5.381298] [TTM] Initializing pool allocator. [5.381323] [drm] radeon: 1024M of VRAM memory ready [5.381325] [drm] radeon: 512M of GTT memory ready. [5.381342] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [5.381344] [drm] Driver supports precise vblank timestamp query. [5.381355] iwlagn :03:00.0: RF_KILL bit toggled to disable radio. [5.381434] radeon :01:00.0: irq 44 for MSI/MSI-X [5.381442] radeon :01:00.0: radeon: using MSI. [5.381489] [drm] radeon: irq initialized. [5.381495] [drm] GART: num cpu pages 131072, num gpu pages 131072 [5.382093] [drm] Loading REDWOOD Microcode [5.386113] iwlagn :03:00.0: loaded firmware version 39.31.5.1 build 35138 [5.386225] Registered led device: phy0-led [5.389763] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [5.393030] radeon :01:00.0: WB enabled [5.398958] input: Ideapad extra buttons as /devices/platform/ideapad/input/input8 [5.409318] [drm] ring test succeeded in 1 usecs [5.409449] [drm] radeon: ib pool ready. [5.409515] [drm] ib test succeeded in 0 usecs [5.409521] failed to evaluate ATIF got AE_BAD_PARAMETER [5.409913] [drm] Radeon Display Connectors [5.409916] [drm] Connector 0: [5.409918] [drm] LVDS [5.409921] [drm] DDC: 0x6560 0x6560 0x6564 0x6564 0x6568 0x6568 0x656c 0x656c [5.409923] [drm] Encoders: [5.409925] [drm] LCD1: INTERNAL_UNIPHY [5.409927] [drm] Connector 1: [5.409929] [drm] HDMI-A [5.409931] [drm] HPD1 [5.409934] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c [5.409936]
Bug#655944: marked as done (linux-image-3.1.0-1-amd64: Kernel threads use significant amount of CPU)
Your message dated Thu, 27 Jun 2013 19:42:51 +0200 with message-id 20130627174251.GD4252@pisco.westfalen.local and subject line Closing has caused the Debian Bug report #655944, regarding linux-image-3.1.0-1-amd64: Kernel threads use significant amount of CPU to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 655944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.1.8-2 Severity: normal On my laptop, kernel threads use somewhere between 25% - 80% of one of the CPUs, even on idle. At the suggestion of a friend, I looked at the contents of /sys/firmware/acpi/interrupts/, and noticed that gpe18 was rising at about 10 a second. Searching through the standard logfiles didn't show anything related to gpe18, however looking through the installation logs, I found this line ACPI Error: No handler or method for GPE[18], disabling event (20090903/evgpe-706) which suggested that the issue was with ACPI. Decompiling the dsdt table and then recompiling according to http://en.gentoo- wiki.com/wiki/ACPI/Fix_common_problems in order to try to guess what hardware was the issue, gave me the three following errors: dsdt.dsl 2124: 0x, // Length Error4122 - ^ Invalid combination of Length and Min/Max fixed flags dsdt.dsl 2131: 0x07E0, // Length Error4118 - ^ Length is not equal to fixed Min/Max window dsdt.dsl 2138: 0x0F00, // Length Error4118 - ^ Length is not equal to fixed Min/Max window Is there any other information that would be useful in finding out why the CPU usage is so high? -- Package-specific info: ** Version: Linux version 3.1.0-1-amd64 (Debian 3.1.8-2) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-11) ) #1 SMP Tue Jan 10 05:01:58 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.1.0-1-amd64 root=/dev/mapper/pandora-root ro quiet ** Not tainted ** Kernel log: [5.369898] ATOM BIOS: Lenovo [5.369958] radeon :01:00.0: VRAM: 1024M 0x - 0x3FFF (1024M used) [5.369962] radeon :01:00.0: GTT: 512M 0x4000 - 0x5FFF [5.377902] iwlagn :03:00.0: device EEPROM VER=0x15d, CALIB=0x6 [5.377906] iwlagn :03:00.0: Device SKU: 0X50 [5.377909] iwlagn :03:00.0: Valid Tx ant: 0X1, Valid Rx ant: 0X3 [5.381232] iwlagn :03:00.0: Tunable channels: 13 802.11bg, 0 802.11a channels [5.381236] [drm] Detected VRAM RAM=1024M, BAR=256M [5.381239] [drm] RAM width 128bits DDR [5.381294] [TTM] Zone kernel: Available graphics memory: 4089264 kiB. [5.381296] [TTM] Zone dma32: Available graphics memory: 2097152 kiB. [5.381298] [TTM] Initializing pool allocator. [5.381323] [drm] radeon: 1024M of VRAM memory ready [5.381325] [drm] radeon: 512M of GTT memory ready. [5.381342] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [5.381344] [drm] Driver supports precise vblank timestamp query. [5.381355] iwlagn :03:00.0: RF_KILL bit toggled to disable radio. [5.381434] radeon :01:00.0: irq 44 for MSI/MSI-X [5.381442] radeon :01:00.0: radeon: using MSI. [5.381489] [drm] radeon: irq initialized. [5.381495] [drm] GART: num cpu pages 131072, num gpu pages 131072 [5.382093] [drm] Loading REDWOOD Microcode [5.386113] iwlagn :03:00.0: loaded firmware version 39.31.5.1 build 35138 [5.386225] Registered led device: phy0-led [5.389763] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [5.393030] radeon :01:00.0: WB enabled [5.398958] input: Ideapad extra buttons as /devices/platform/ideapad/input/input8 [5.409318] [drm] ring test succeeded in 1 usecs [5.409449] [drm] radeon: ib pool ready. [5.409515] [drm] ib test succeeded in 0 usecs [5.409521] failed to evaluate ATIF got AE_BAD_PARAMETER [5.409913] [drm] Radeon Display Connectors [5.409916] [drm] Connector 0: [5.409918] [drm] LVDS [5.409921] [drm] DDC: 0x6560 0x6560 0x6564 0x6564 0x6568 0x6568 0x656c 0x656c [5.409923] [drm] Encoders: [5.409925] [drm] LCD1: INTERNAL_UNIPHY [5.409927] [drm] Connector 1: [5.409929] [drm] HDMI-A [5.409931] [drm] HPD1 [5.409934] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c [5.409936] [drm] Encoders: [5.409938] [drm] DFP1:
