public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: DIXLOR <dixlor@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: rtmutex deadlock detected (3.18.19-rt15)
Date: Fri, 31 Jul 2015 01:15:47 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1507310111200.3825@nanos> (raw)
In-Reply-To: <55B54F7A.4030904@gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1863 bytes --]

On Mon, 27 Jul 2015, DIXLOR wrote:
> 26.07.2015 21:56, Thomas Gleixner пишет:
> > 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_powersave
> > > cpufreq_conservative nct6775 hwmon_vid xhci_hcd usbcore iTCO_wdt
> > > crct10dif_pclmul iTCO_vendor_support shpchp crc32c_intel i2c_i801 lpc_ich
> > > i2c_core usb_common mfd_core button processor dm_mod raid1 ahci libahci
> > > 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 V3.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]  [<ffffffff814d1350>] ? 0xffffffff814d1350
> > Can you please build your kernel with KALLSYSMS_ALL enabled, so we get
> > 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.

Ok. So we still need to investigate what happens there.

Is there anything else required than

   - xfs mount with filestreams option
   - Running xfs_fsr and ^C it?

Thanks,

	tglx

      reply	other threads:[~2015-07-30 23:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-25 14:05 rtmutex deadlock detected (3.18.19-rt15) DIXLOR
2015-07-26 18:56 ` Thomas Gleixner
2015-07-26 21:22   ` DIXLOR
2015-07-30 23:15     ` Thomas Gleixner [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.11.1507310111200.3825@nanos \
    --to=tglx@linutronix.de \
    --cc=dixlor@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox