Bug 433157

Summary: [lockdep] Hang on boot: INFO: possible recursive locking detected & BUG: soft lockup - CPU#1 stuck for 61s! [wpa_supplicant:2490]
Product: [Fedora] Fedora Reporter: Tom London <selinux>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 9   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-12-26 17:31:41 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:
Bug Depends On:    
Bug Blocks: 202141    
Attachments:
Description Flags
/var/log/messages when NetworkManager starts, system hangs
none
more lockdep messages from /var/log/messages none

Description Tom London 2008-02-17 00:47:42 UTC 
Description of problem:
kernel-2.6.25-0.50.rc2.fc9.i686 fails to complete init into runlevel 5

Get the INFO/recursive locking message when NetworkManager starts, and the
system "hangs": displays text login, but does not seem to accept any input.

I get the BUG/lockup after entering CTL-ALT-delete (the system does shutdown
"normally").

Sorry for jumping the gun on this version.... hoping to get one that supports
KVM ... :-)

System is a Thinkpad X60.

I'll attach what appears to be the relevant portion of /var/log/messages

Version-Release number of selected component (if applicable):
kernel-2.6.25-0.50.rc2.fc9.i686

How reproducible:
Every time.

Steps to Reproduce:
1.  Install, boot
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Tom London 2008-02-17 00:47:42 UTC 
Created attachment 295083 [details]
/var/log/messages when NetworkManager starts, system hangs
Comment 2 Tom London 2008-02-17 22:29:21 UTC 
Issue seems to be with NetworkManager (and derived kernel support).

Booting in runlevel 3 with NetworkManager "turned off" works. I can bring up the
network interface manually and do a "startx" without problems.

[Booting in runlevel 3 with NM "turned on" produces above problems and freeze.
Comment 3 Tom London 2008-02-18 01:26:25 UTC 
Created attachment 295122 [details]
more lockdep messages from /var/log/messages

Got more:

Feb 17 17:22:15 localhost kernel: [ INFO: possible circular locking dependency
detected ]
Feb 17 17:22:15 localhost kernel: 2.6.25-0.50.rc2.fc9 #1
Feb 17 17:22:15 localhost kernel:
-------------------------------------------------------
Feb 17 17:22:15 localhost kernel: losetup/3515 is trying to acquire lock:
Feb 17 17:22:15 localhost kernel:  (&bdev->bd_mutex){--..}, at: [<c04aa5e2>]
__blkdev_put+0x24/0x12f
Feb 17 17:22:15 localhost kernel: 
Feb 17 17:22:15 localhost kernel: but task is already holding lock:
Feb 17 17:22:15 localhost kernel:  (&lo->lo_ctl_mutex){--..}, at: [<f8ef1087>]
lo_ioctl+0x3d/0xa01 [loop]
Feb 17 17:22:15 localhost kernel: 
Feb 17 17:22:15 localhost kernel: which lock already depends on the new lock.

Complete spew in the attachment.
Comment 4 Jeff Moyer 2008-02-18 15:37:34 UTC 
Looks like this was reported upstream:

  http://lkml.org/lkml/2008/2/15/542

The second lockup (comment #3) is a different issue and probably warrants a
separate bugzilla.
Comment 5 Tom London 2008-02-21 15:52:35 UTC 
Don't seem to be getting lockdep issue with kernel-2.6.25-0.61.rc2.git4.fc9.i686
Comment 6 Charles R. Anderson 2008-02-22 16:24:46 UTC 
*** Bug 433329 has been marked as a duplicate of this bug. ***
Comment 7 Bug Zapper 2008-05-14 05:14:29 UTC 
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 8 Tom London 2008-12-26 17:31:41 UTC 
Closing this.

Must be long gone by now.....