Bug 52631 - High CPU usage after resume on ASUS U36SD
Summary: High CPU usage after resume on ASUS U36SD
Status: CLOSED INVALID
Alias: None
Product: ACPI
Classification: Unclassified
Component: BIOS (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Aaron Lu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-13 16:33 UTC by Sergey Sharybin
Modified: 2013-03-06 00:42 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.7.2
Subsystem:
Regression: No
Bisected commit-id:


Attachments
ACPI interrupts before suspend (960 bytes, text/plain)
2013-01-13 16:33 UTC, Sergey Sharybin
Details
ACPI interrupts after suspend (961 bytes, text/plain)
2013-01-13 16:34 UTC, Sergey Sharybin
Details
ACPI dump before suspend (385.94 KB, text/plain)
2013-01-13 16:34 UTC, Sergey Sharybin
Details
ACPI dump after suspend (385.94 KB, text/plain)
2013-01-13 16:35 UTC, Sergey Sharybin
Details
lspci before suspend (44.39 KB, text/plain)
2013-01-13 16:35 UTC, Sergey Sharybin
Details
lspci after suspend (43.03 KB, text/plain)
2013-01-13 16:35 UTC, Sergey Sharybin
Details
dmesg of the whole lifecycle (63.41 KB, text/plain)
2013-01-13 16:36 UTC, Sergey Sharybin
Details

Description Sergey Sharybin 2013-01-13 16:33:50 UTC
Created attachment 91121 [details]
ACPI interrupts before suspend

Hi,

On my laptop which is ASUS U36SD i'm experiencing high CPU usage after resuming it form suspend-to-ram state. Actually, seems to be very much the same as report 29722.

This is pretty much strange issue, because initially this never happened, but at some point i've started experiencing this issue. That time seemed updating BIOS helped and everything worked fine for couple of months. But now the issue is back. Don't know if it's hardware issue or not, no idea how to troubleshot this.

In the attachments:
- acpidump before and after suspend
- acpi interrupts before and after suspend
- lspci -vvvxxx before and after suspend (where it seems strange nvidia card and usb3 controller have invalid header type after suspend)
- dmesg since system boot to the moment of after resume

Hope to have some expert opinion and thanks for the help :)
Comment 1 Sergey Sharybin 2013-01-13 16:34:13 UTC
Created attachment 91131 [details]
ACPI interrupts after suspend
Comment 2 Sergey Sharybin 2013-01-13 16:34:43 UTC
Created attachment 91141 [details]
ACPI dump before suspend
Comment 3 Sergey Sharybin 2013-01-13 16:35:00 UTC
Created attachment 91151 [details]
ACPI dump after suspend
Comment 4 Sergey Sharybin 2013-01-13 16:35:18 UTC
Created attachment 91161 [details]
lspci before suspend
Comment 5 Sergey Sharybin 2013-01-13 16:35:35 UTC
Created attachment 91171 [details]
lspci after suspend
Comment 6 Sergey Sharybin 2013-01-13 16:36:13 UTC
Created attachment 91181 [details]
dmesg of the whole lifecycle
Comment 7 Aaron Lu 2013-02-20 07:00:55 UTC
Hello Sergey,

Thanks for reporting this problem.

Do you have the problem on other kernels, e.g. 3.8 or 3.6 etc.?
And if possible, can you please test from which kernel this bug appeared?

Also, you can try booting with pcie_aspm=off, see if that makes any difference, thanks.
Comment 8 Sergey Sharybin 2013-02-22 08:04:44 UTC
Hi,

Pardon for delay. We've been busy with blender release..

Building kernel 3.8 right now.

My biggest fear is that it's not just kernel involved here, but also some hardware crap. However, no idea what could have caused this. So far all the tested older kernels showed the issue.

I'll give it a try with new 3.8 and pcie_aspm disabled and report back. For now working around the issue by disabling gpe01 (echo disabled > /sys/firmware/acpi/interrupts/gpe01)
Comment 9 Sergey Sharybin 2013-02-22 09:39:04 UTC
So, did some more tests.

Kernel 3.8 has got the same exact issue as 3.7.2 i'm currently using.
Using pcie_aspm=off does not seem to have any affect at all.
Comment 10 Aaron Lu 2013-02-25 03:07:48 UTC
The GPE01 tried to notify pci bridge 0x1c function 2 a BUS CHECK event, but the pci bridge does not exist on your system according to lspci output. I'm not sure what the problem is.

Can you please try to identify which is the last working kernel and then do a git bisect to find out the offending commit? Thanks.
Comment 11 Sergey Sharybin 2013-02-25 07:07:16 UTC
Yeah, i'll try to bisect and report back when will have more information. Hope it'll be within today or tomorrow.
Comment 12 Sergey Sharybin 2013-03-05 19:46:08 UTC
That took a little more time than i've expected. But i'm very much failed to figure something out. All the previous versions of kernel i've tested have the same issue. So i tend to believe it's actually a hardware or bios failure.

I even went crazy and tried installing windows, which have the same exact issue. 

So if you think there's nothing to be done form software/kernel side, i'll crack this guy open and try to reset bios.

P.S. The only thing i've figured out is that 3.9-rc1 does not wake up for me at all. Perhaps i'll try collecting more info about this issue and fire a separate report.
Comment 13 Aaron Lu 2013-03-06 00:42:10 UTC
(In reply to comment #12)
> That took a little more time than i've expected. But i'm very much failed to
> figure something out. All the previous versions of kernel i've tested have
> the
> same issue. So i tend to believe it's actually a hardware or bios failure.

Thanks for the testing.

> 
> I even went crazy and tried installing windows, which have the same exact
> issue. 
> 
> So if you think there's nothing to be done form software/kernel side, i'll
> crack this guy open and try to reset bios.

OK :-)

> 
> P.S. The only thing i've figured out is that 3.9-rc1 does not wake up for me
> at
> all. Perhaps i'll try collecting more info about this issue and fire a
> separate
> report.

Yes, please do that. And I'll close this bug as invalid, but if you find something new about it, please feel free to re-open it, thanks.

Note You need to log in before you can comment on or make changes to this bug.