Opened 8 years ago

Closed 7 years ago

Last modified 5 years ago

#13360 closed bug (fixed)

acpi_task consuming 100% of one CPU and syslog full of KERN: port XXX messages

Reported by: davewthompson Owned by: tqh
Priority: normal Milestone: R1/beta2
Component: Drivers/ACPI Version: R1/Development
Keywords: acpi_task Cc:
Blocked By: Blocking:
Platform: All

Description (last modified by pulkomandy)

On my Lenovo ThinkCentre M93 one core is being consumed by the acpi_task constantly.

The syslog is also full of continuously-generated messages along the lines of:

KERN: usb hub 2: KERN: port 19 is not suspended
KERN: usb hub 2: port 19 is not in an over current state
KERN: usb hub 2: port 19 was reset
KERN: usb hub 2: KERN: port 20 is not suspended
KERN: usb hub 2: KERN: port 20 is not in an over current state
KERN: usb hub 2: port 20 was reset
KERN: usb hub 2: KERN: port 18 is not suspended
KERN: usb hub 2: KERN: port 18 is not in an over current state
KERN: usb hub 2: port 18 was reset

Attachments (2)

acpi_task_100.png (147.7 KB ) - added by fsv141 6 years ago.
about.png (34.5 KB ) - added by fsv141 6 years ago.

Download all attachments as: .zip

Change History (9)

comment:1 by pulkomandy, 8 years ago

These look like two unrelated problems. The USB errors seem to come from the XHCI (USB3) driver, in my case I get those all the time but they don't result in excessive CPU use.

comment:2 by pulkomandy, 8 years ago

Description: modified (diff)

comment:3 by diver, 8 years ago

Component: - GeneralDrivers/ACPI
Owner: changed from nobody to tqh

comment:4 by tqh, 7 years ago

Resolution: fixed
Status: newclosed

The ACPI task should be fixed in hrev51720 or hrev51771.

by fsv141, 6 years ago

Attachment: acpi_task_100.png added

by fsv141, 6 years ago

Attachment: about.png added

comment:5 by fsv141, 6 years ago

Lenovo E10-30. 100% load of one of the CPU cores.

Version 0, edited 6 years ago by fsv141 (next)

comment:6 by waddlesplash, 6 years ago

Please open a new ticket and attach a syslog.

comment:7 by nielx, 5 years ago

Milestone: UnscheduledR1/beta2

Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone

Note: See TracTickets for help on using tickets.