Hello, Andrew. On Thu, Nov 03, 2011 at 01:46:19PM -0500, Andrew Watts wrote: > On Thu, Nov 03, 2011 at 08:59:56AM -0700, Tejun Heo wrote: > > Andrew, just in case, can you please double check that you're > > reverting only that single commit (not all the ones afterwards) and > > the test results? If they're all okay, can you please trigger the > > problem, wait a while, trigger sysrq-t and attach the kernel log? > > Hi Tejun. > > I am only reverting 8ee294cd9def0004887da7f44b80563493b0a097 though I first > revert part of 1d64b655dc083df5c5ac39945ccbbc6532903bf1 so it reverts > cleanly. > > I am very sure of my test results; normally I get 4-5 bad resumes on a 20 > hibernate loop and get no bad resumes with the commit reverted. I have > been very thorough in my testing to ensure I am not generating false > positives or false negatives (repeating the loops many times). Thanks. Yeah, this is odd & interesting. > Below is the output you asked for (sysrq t). > > Thanks. > > ~ Andy > > ====================== > > > kernel: [ 345.226523] SysRq : Show State > kernel: [ 345.226531] task PC stack pid father > kernel: [ 345.226535] init S f4a47b68 5488 1 0 0x00000000 > kernel: [ 345.226765] kthreadd S 00000000 7172 2 0 0x00000000 This is missing all stack traces. Can you please turn on FRAME_POINTER and adjust log level such that all stack dumps are included too? Thank you. -- tejun _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/linux-pm
