Kernel Bug Tracker – Bug 11296
2.6.27-rc2-git4: suspend and power off fails on Asus M3A32-MVP
Last modified: 2008-08-22 11:21:56 UTC
Subject : 2.6.27-rc2-git4: suspend and power off fails on Asus M3A32-MVP
Submitter : "Rafael J. Wysocki" <email@example.com>
Date : 2008-08-09 21:21
References : http://marc.info/?l=linux-kernel&m=121831675111794&w=4
This entry is being used for tracking a regression from 2.6.26. Please don't
close it until the problem is fixed in the mainline.
Handled-By : "Langsdorf, Mark" <firstname.lastname@example.org>
fixed by commit f607e3a03c90e8c050cb0c12ec9967c2925cc812
Created attachment 17374 [details]
We used hardware tools to break into a failing system and catch the OOPS. It's slab corruption on resume, with a slab entry not having any valid links.
Created attachment 17375 [details]
another crash report
I rebuilt the kernel with slab and suspend/resume debugging enabled and tried again. A different but similar crash report.
Created attachment 17376 [details]
yet another crash report
One more crash report. This shows the slab corruption again, but doesn't indicate why.
This looks similar to the problem described in this e-mail thread:
Well, no, it doesn't really.
Is that with SLUB or SLAB? If this is with SLUB, then corrupting per-CPU memory could lead to that.
Would it be practicable to split the patch reverted by commit f607e3a03c90e8c050cb0c12ec9967c2925cc812 into two patches, one introducing the per-CPU variables and the other one actually causing them to be passed to acpi_processor_preregister_performance() ? Then, we could verify which part of the original patch causes the problem to happen.
No, it's SLAB.
I'll see what I can do split the patch. It won't be very useful that way, but I could create a bunch of unused per-cpu variables.
(In reply to comment #8)
> No, it's SLAB.
> I'll see what I can do split the patch. It won't be very useful that way, but
> I could create a bunch of unused per-cpu variables.
Well, if they are unused, we won't be able to check if per-CPU memory is corrupted.
In fact, I don't see anything other than some corruption of per-CPU memory that could result from this patch and lead to slab corruption.