Created attachment 521365 [details]
kernel trace from messages
Description of problem:
After resume from hibernate I get
[ INFO: inconsistent lock state ]
Version-Release number of selected component (if applicable):
resume from hibernate
Steps to Reproduce:
kernel trace according to attachment
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
Up to it didn't show up again, though it was quite sporadic for some time now...
[Mass hibernate bug update]
Dave Airlied has found an issue causing some corruption in the i915 fbdev after a resume from hibernate. I have included his patch in this scratch build:
This will probably not solve all of the issues being tracked at the moment, but it is worth testing when the build completes. If this seems to clear up the issues you see with hibernate, please report your results in the bug.
I'm still experiencing frequent problems with hibernate and kernel 3.3.2. I also have the Intel N10 graphics adapter and i915 driver. I wonder if the patch mentioned in the previous comment has been included in 3.3.2?
F16's hibernate has never worked reliably on my netbook. Usually it crashes on resume with kernel oops/trace, but sometimes during hibernate and sometimes I cannot access the console messages at all.
# Mass update to all open bugs.
Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.
Please retest with this kernel, and let us know if your problem has been fixed.
In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with. Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.
If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.