Bug 1383085

Summary: [abrt] BUG: sleeping function called from invalid context at kernel/locking/mutex.c:620
Product: [Fedora] Fedora Reporter: 3keepmovingforward3
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: gansalmon, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab, peljasz
Target Milestone: ---Flags: jforbes: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e47e102307c83a6aac8c33847559de5cb9b418fc
Whiteboard: abrt_hash:2ed8a332285fd6be62a12378fad6e6b0aa8383a2;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-28 17:19:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: dmesg none

Description 3keepmovingforward3 2016-10-09 18:51:50 UTC 
Additional info:
reporter:       libreport-2.7.2
BUG: sleeping function called from invalid context at kernel/locking/mutex.c:620
in_atomic(): 1, irqs_disabled(): 0, pid: 16, name: watchdog/1
no locks held by watchdog/1/16.
CPU: 1 PID: 16 Comm: watchdog/1 Not tainted 4.9.0-0.rc0.git4.1.fc26.x86_64 #1
Hardware name: Dell Inc. Inspiron 3558/0PNFDX, BIOS A10 05/31/2016
 ffffb404806e7c58 ffffffffa946c303 ffff9f3011080000 ffffffffa9c7067f
 ffffb404806e7c80 ffffffffa90e01e8 ffffffffa9c7067f 000000000000026c
 0000000000000000 ffffb404806e7ca8 ffffffffa90e02fa ffff9f30129de8e8
Call Trace:
 [<ffffffffa946c303>] dump_stack+0x86/0xc3
 [<ffffffffa90e01e8>] ___might_sleep+0x178/0x240
 [<ffffffffa90e02fa>] __might_sleep+0x4a/0x80
 [<ffffffffa91e3a65>] ? perf_event_ctx_lock_nested+0x25/0x1f0
 [<ffffffffa9903023>] mutex_lock_nested+0x43/0x3f0
 [<ffffffffa91e3a65>] ? perf_event_ctx_lock_nested+0x25/0x1f0
 [<ffffffffa91e3a65>] ? perf_event_ctx_lock_nested+0x25/0x1f0
 [<ffffffffa91e3b0f>] perf_event_ctx_lock_nested+0xcf/0x1f0
 [<ffffffffa91e3a65>] ? perf_event_ctx_lock_nested+0x25/0x1f0
 [<ffffffffa90dbd0d>] ? smpboot_thread_fn+0x12d/0x1f0
 [<ffffffffa91e3c41>] perf_event_disable+0x11/0x40
 [<ffffffffa9198b76>] watchdog_nmi_disable+0x36/0x70
 [<ffffffffa90dbc14>] ? smpboot_thread_fn+0x34/0x1f0
 [<ffffffffa9198c0c>] watchdog_disable+0x5c/0x80
 [<ffffffffa90dbd43>] smpboot_thread_fn+0x163/0x1f0
 [<ffffffffa90dbbe0>] ? sort_range+0x30/0x30
 [<ffffffffa90d7602>] kthread+0x102/0x120
 [<ffffffffa99018fc>] ? wait_for_completion+0x4c/0x140
 [<ffffffffa90d7500>] ? kthread_park+0x60/0x60
 [<ffffffffa990753a>] ret_from_fork+0x2a/0x40
Comment 1 3keepmovingforward3 2016-10-09 18:52:00 UTC 
Created attachment 1208639 [details]
File: dmesg
Comment 2 Justin M. Forbes 2017-04-11 14:45:41 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.
Comment 3 Justin M. Forbes 2017-04-28 17:19:03 UTC 
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the 
relevant data from the latest kernel you are running and any data that might have been requested previously.