Dne 28.11.2012 17:01, Linus Torvalds napsal(a):
Adding more people (and the acpi list) to this report.
I'm seeing *very* few changes to the core suspend/resume path in 3.7,
and while there are some acpia updates, they seem to be pretty mild
too.
I think the acpi_os_wait_semaphore thing is a red herring - that's
just stale on the stack.
Do you have the register state from the oops? Or at least the "Code:"
line? It would be nice to see exactly where the oops happens, and I
cannot line up your "acpi_ns_lookup + 0xa1/0x5b9" with any code due
to different compilers (and configurations etc).
Linus
I've opened https://bugzilla.kernel.org/show_bug.cgi?id=51071
and attached picture there which is all I have.
I'll try to decode exact code line.
In all cases - I've played even with 3.4 kernel - which also does not survive
multiple resumes in docking station - though it just leaves black screen - so
this oops is rather 'progress' and it also could be false path.
It's probably not a regression from 3.6 - since this problem was there for
much longer - but now it has just become much more visible.
As I usually do not have reason to make multiple suspend/resumes in dock I've
not noticed it until now when I've tried to capture this ACPI trace.
Zdenek
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
