From mboxrd@z Thu Jan 1 00:00:00 1970 From: DIXLOR Subject: Re: rtmutex deadlock detected (3.18.19-rt15) Date: Mon, 27 Jul 2015 00:22:02 +0300 Message-ID: <55B54F7A.4030904@gmail.com> References: <55B39797.9020705@gmail.com> Reply-To: dixlor@gmail.com Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: linux-rt-users@vger.kernel.org To: Thomas Gleixner Return-path: Received: from mail-lb0-f180.google.com ([209.85.217.180]:36199 "EHLO mail-lb0-f180.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755241AbbGZVWH (ORCPT ); Sun, 26 Jul 2015 17:22:07 -0400 Received: by lbbqi7 with SMTP id qi7so42029589lbb.3 for ; Sun, 26 Jul 2015 14:22:05 -0700 (PDT) In-Reply-To: Sender: linux-rt-users-owner@vger.kernel.org List-ID: 26.07.2015 21:56, Thomas Gleixner =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > On Sat, 25 Jul 2015, DIXLOR wrote: >> # xfs_fsr; >> ^C >> >> [ 3380.373641] WARNING: CPU: 6 PID: 3664 at kernel/locking/rtmutex.h= :29 >> 0xffffffff814d4ea2() >> [ 3380.373641] rtmutex deadlock detected >> [ 3380.373645] Modules linked in: cpufreq_userspace cpufreq_powersav= e >> cpufreq_conservative nct6775 hwmon_vid xhci_hcd usbcore iTCO_wdt >> crct10dif_pclmul iTCO_vendor_support shpchp crc32c_intel i2c_i801 lp= c_ich >> i2c_core usb_common mfd_core button processor dm_mod raid1 ahci liba= hci fan >> thermal thermal_sys [last unloaded: xhci_pci] >> [ 3380.373646] CPU: 6 PID: 3664 Comm: xfs_fsr Tainted: G D 3.= 18.19-rt15 >> #3 >> [ 3380.373647] Hardware name: MSI MS-7823/B85M-G43 (MS-7823), BIOS V= 3.14B3 >> 06/23/2014 >> [ 3380.373647] 0000000000000000 0000000000000009 ffffffff814d1350 >> ffff8807ef65f538 >> [ 3380.373648] ffffffff810498dd ffff8807cf289d10 ffff8807ef65f5c0 >> 0000000000000000 >> [ 3380.373648] 0000000000000000 0000000000000002 ffffffff81049955 >> ffffffff81680648 >> [ 3380.373649] Call Trace: >> [ 3380.373649] [] ? 0xffffffff814d1350 > Can you please build your kernel with KALLSYSMS_ALL enabled, so we ge= t > a symbolic resolution of the call trace. > > You can also try and enable CONFIG_PROVE_LOCKING. That will give us > even more detailed information about the problem at hand. Note, that > CONFIG_PROVE_LOCKING slows down your kernel, so don't try to run on a > production environment. I found the reason: xfs mount with filestreams option. -- To unsubscribe from this list: send the line "unsubscribe linux-rt-user= s" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html