Bug 754258

Summary: [abrt] kernel: [ INFO: possible recursive locking detected ]
Product: [Fedora] Fedora Reporter: Nicolas Mailhot <nicolas.mailhot>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:0025bf077ea21e6e81f3d9e24ea6c959bb1c4bde
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 18:38:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: smolt_data
none
File: backtrace none

Description Nicolas Mailhot 2011-11-15 20:58:09 UTC 
libreport version: 2.0.7
abrt_version:   2.0.6
cmdline:        ro root=/dev/VolGroup00/systeme SYSFONT=latarcyrheb-sun16 LANG=fr_FR.UTF-8 KEYTABLE=fr-latin9 quiet
comment:        On boot               
kernel:         3.2.0-0.rc1.git3.1.fc17.x86_64
reason:         [ INFO: possible recursive locking detected ]
time:           dim. 13 nov. 2011 17:36:44 CET

backtrace:      Text file, 3198 bytes
smolt_data:     Text file, 3331 bytes

event_log:
:2011-11-15-21:56:01> Smolt profile successfully saved
:2011-11-15-21:56:55> Envoie du rapport oops vers http://submit.kerneloops.org/submitoops.php
:2011-11-15-21:57:59  Kernel oops has not been sent due to Couldn't connect to server
:2011-11-15-21:57:59* (exited with 1)
Comment 1 Nicolas Mailhot 2011-11-15 20:58:13 UTC 
Created attachment 533843 [details]
File: smolt_data
Comment 2 Nicolas Mailhot 2011-11-15 20:58:15 UTC 
Created attachment 533844 [details]
File: backtrace
Comment 3 Dave Jones 2011-12-06 18:38:50 UTC 

*** This bug has been marked as a duplicate of bug 728316 ***