Bug 60636
Summary: | dmesg/kernel log polluted with power state changed by ACPI to D0/D3 | ||
---|---|---|---|
Product: | Drivers | Reporter: | Oleksii Shevchuk (alxchk) |
Component: | USB | Assignee: | Alan Stern (stern) |
Status: | CLOSED OBSOLETE | ||
Severity: | normal | CC: | leho, stern, tianyu.lan |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 3.10.1 | Subsystem: | |
Regression: | No | Bisected commit-id: |
Description
Oleksii Shevchuk
2013-07-27 06:01:39 UTC
Hi, This seems EHCI fluctuates between D0 and D3. Please try to disabe EHCI runtime PM via powertop. It looks like the dev_info line in drivers/pci/pci-acpi.c:acpi_pci_set_power_state() should be changed to dev_dbg. The "latency timer" message in pci.c:pcibios_set_master() already uses KERN_DEBUG. This will prevent the kernel log from being spammed. The dmesg log is a different matter. I don't know what causes those constant suspends and resumes. You could get more information by enabled CONFIG_USB_DEBUG. (In reply to Alan Stern from comment #2) > It looks like the dev_info line in > drivers/pci/pci-acpi.c:acpi_pci_set_power_state() should be changed to > dev_dbg. The "latency timer" message in pci.c:pcibios_set_master() already > uses KERN_DEBUG. Yes, dev_dbg makes more sense. I will send a patch to change it. > > This will prevent the kernel log from being spammed. The dmesg log is a > different matter. I don't know what causes those constant suspends and > resumes. You could get more information by enabled CONFIG_USB_DEBUG. From the logs, this should be a EHCI issue and so reassign to USB component. Oleksii, if you want to find out what causes the continuing suspends and resumes, you should capture a usbmon trace of the USB bus corresponding to the 1d.0 controller, and attach it to this bug report. |