Bug 709979 - INFO: possible circular locking dependency detected
Summary: INFO: possible circular locking dependency detected
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 15
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-02 07:10 UTC by koukou73gr
Modified: 2012-06-06 13:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-06 13:22:50 UTC
Type: ---


Attachments (Terms of Use)
Trace (5.87 KB, application/octet-stream)
2011-06-02 07:10 UTC, koukou73gr
no flags Details

Description koukou73gr 2011-06-02 07:10:52 UTC
Created attachment 502436 [details]
Trace

Description of problem:
Sometimes while suspending to ram (mostly the first time after a fresh restart) I get an INFO trace, presumably while the system tries to shutdown the non-boot core of the CPU.

Suspending completes however and the system is able to resume afterwards.

Version-Release number of selected component (if applicable):
2.6.38.6-27.fc15.x86_64.debug #1

How reproducible:
I don't usually suspend to ram, I prefer hibernating instead (which also gives a similar trace, see bug 709544 ( https://bugzilla.redhat.com/show_bug.cgi?id=709544 ). But the few I do, I get it almost every time. 


Steps to Reproduce:
1. Boot
2. Login
3. Close lid to suspend.
  
Actual results:
Trace generated

Expected results:
No trace

Additional info:
This is on a Dell Latitude E4300, 6GB RAM, Intel GM45 with an SP9600 CPU. 

This laptop seems to hang into ACPI ( "ACPI: While loop taking a really long
time. loop_count=..." ) after some number of hibernation/thaw cycles and/or
throw random oops traces during hibernation/thaw that I was unable to save so
far. Hence I run a debug kernel and hope to catch something more in my logs
just before that happens. This INFO trace is such a catch.

Comment 1 Josh Boyer 2012-06-06 13:22:50 UTC
2.6.38.6 is fairly ancient at this point.  If you're still seeing this with the recent F16/F17 debug kernels, please open a new bug with the full trace.


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