Bug 743206

Summary: [abrt] kernel: [ INFO: possible recursive locking detected ]
Product: [Fedora] Fedora Reporter: Masao Takahashi <masao-takahashi>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED RAWHIDE 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: i686   
OS: Unspecified   
Whiteboard: abrt_hash:230430d23c27274bfe8f95cfb15b1690cef3fd6e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-05 00:36:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Masao Takahashi 2011-10-04 08:27:32 UTC
libreport version: 2.0.6
abrt_version:   2.0.4.981
cmdline:        memtest=1 hpet=verbose clocksource=hpet ro root=UUID=7609fdc1-3769-4208-a41d-ca1c55d77cd8 rhgb quiet LANG=ja_JP.UTF-8 KEYTABLE=jp106 plymouth_theme=charge selinux=0
comment:        reading syslog
kernel:         undefined
reason:         [ INFO: possible recursive locking detected ]
time:           Tue Oct  4 08:22:02 2011

backtrace:
:[ INFO: possible recursive locking detected ]
:3.1.0-rc8.fc17.i686+ #5
:---------------------------------------------
:systemd-logind/822 is trying to acquire lock:
:(&ep->mtx){+.+.+.}, at: [<c052417e>] ep_scan_ready_list+0x32/0x151
:but task is already holding lock:
:(&ep->mtx){+.+.+.}, at: [<c0524614>] sys_epoll_ctl+0x103/0x481
:other info that might help us debug this:
:Possible unsafe locking scenario:
:      CPU0
:      ----
: lock(&ep->mtx);
: lock(&ep->mtx);
:*** DEADLOCK ***
:May be due to missing lock nesting notation
:2 locks held by systemd-logind/822:
:#0:  (epmutex){+.+.+.}, at: [<c05245cf>] sys_epoll_ctl+0xbe/0x481
:#1:  (&ep->mtx){+.+.+.}, at: [<c0524614>] sys_epoll_ctl+0x103/0x481
:stack backtrace:
:Pid: 822, comm: systemd-logind Not tainted 3.1.0-rc8.fc17.i686+ #5
:Call Trace:
:[<c08366fd>] ? printk+0x2d/0x2f
:[<c0469bc6>] __lock_acquire+0x7f6/0xb48
:[<c04044ba>] ? dump_trace+0x92/0xbc
:[<c040b8f4>] ? save_stack_trace+0x30/0x4a
:[<c052417e>] ? ep_scan_ready_list+0x32/0x151
:[<c046a316>] lock_acquire+0xb2/0xee
:[<c052417e>] ? ep_scan_ready_list+0x32/0x151
:[<c083d304>] __mutex_lock_common+0x53/0x388
:[<c052417e>] ? ep_scan_ready_list+0x32/0x151
:[<c0469204>] ? mark_lock+0x26/0x1f2
:[<c043173e>] ? __might_sleep+0x36/0x108
:[<c0469204>] ? mark_lock+0x26/0x1f2
:[<c083d73f>] mutex_lock_nested+0x3e/0x44
:[<c052417e>] ? ep_scan_ready_list+0x32/0x151
:[<c052417e>] ep_scan_ready_list+0x32/0x151
:[<c0523d37>] ? ep_remove+0x9b/0x9b
:[<c05242b1>] ep_poll_readyevents_proc+0x14/0x16
:[<c0523f42>] ep_call_nested.constprop.3+0x6d/0x9a
:[<c052429d>] ? ep_scan_ready_list+0x151/0x151
:[<c052403e>] ep_eventpoll_poll+0x45/0x55
:[<c0524710>] sys_epoll_ctl+0x1ff/0x481
:[<c0523e67>] ? ep_send_events_proc+0xd5/0xd5
:[<c0843b63>] sysenter_do_call+0x12/0x3c

event_log:
:2011-10-04-17:24:31* (exited with 1)
:2011-10-04-17:25:30> Submitting oops report to http://submit.kerneloops.org/submitoops.php
:2011-10-04-17:26:33  Kernel oops has not been sent due to Couldn't connect to server
:2011-10-04-17:26:33* (exited with 1)

smolt_data:
:Traceback (most recent call last):
:  File "/usr/bin/smoltSendProfile", line 152, in <module>
:    profile = smolt.get_profile()
:  File "/usr/share/smolt/client/smolt.py", line 1415, in get_profile
:    return Hardware()
:  File "/usr/share/smolt/client/smolt.py", line 1004, in Hardware
:    _hardware_instance = _Hardware()
:  File "/usr/share/smolt/client/smolt.py", line 591, in __init__
:    self.host = Host()
:  File "/usr/share/smolt/client/smolt.py", line 283, in __init__
:    self.systemMemory = Gate().process('ram_size', memory['ram'], 0)
:TypeError: 'NoneType' object is not subscriptable

Comment 1 Masao Takahashi 2011-10-04 08:27:43 UTC
Package: kernel
Architecture: i686
OS Release: Fedora release 16 (Verne)

Comment
-----
reading syslog

Comment 2 Josh Boyer 2011-10-04 12:54:27 UTC
(In reply to comment #0)
> libreport version: 2.0.6
> abrt_version:   2.0.4.981
> cmdline:        memtest=1 hpet=verbose clocksource=hpet ro
> root=UUID=7609fdc1-3769-4208-a41d-ca1c55d77cd8 rhgb quiet LANG=ja_JP.UTF-8
> KEYTABLE=jp106 plymouth_theme=charge selinux=0
> comment:        reading syslog
> kernel:         undefined
> reason:         [ INFO: possible recursive locking detected ]
> time:           Tue Oct  4 08:22:02 2011
> 
> backtrace:
> :[ INFO: possible recursive locking detected ]
> :3.1.0-rc8.fc17.i686+ #5

It looks like you built this kernel yourself?  Fedora has a patch that should fix this already.

Comment 3 Masao Takahashi 2011-10-05 00:36:42 UTC
(In reply to comment #2)
> (In reply to comment #0)
> > libreport version: 2.0.6
> > abrt_version:   2.0.4.981
> > cmdline:        memtest=1 hpet=verbose clocksource=hpet ro
> > root=UUID=7609fdc1-3769-4208-a41d-ca1c55d77cd8 rhgb quiet LANG=ja_JP.UTF-8
> > KEYTABLE=jp106 plymouth_theme=charge selinux=0
> > comment:        reading syslog
> > kernel:         undefined
> > reason:         [ INFO: possible recursive locking detected ]
> > time:           Tue Oct  4 08:22:02 2011
> > 
> > backtrace:
> > :[ INFO: possible recursive locking detected ]
> > :3.1.0-rc8.fc17.i686+ #5
> 
> It looks like you built this kernel yourself?  Fedora has a patch that should
> fix this already.
OK I will  try it.
I close this issue.