From: Peter Zijlstra <peterz@infradead.org>
To: lkp@lists.01.org
Subject: Re: [rfcomm_run] WARNING: CPU: 0 PID: 95 at kernel/sched/core.c:7312 __might_sleep()
Date: Mon, 27 Oct 2014 15:07:26 +0100 [thread overview]
Message-ID: <20141027140726.GJ3337@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20141027134948.GA8977@wfg-t540p.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
On Mon, Oct 27, 2014 at 09:49:48PM +0800, Fengguang Wu wrote:
> On Mon, Oct 27, 2014 at 02:36:27PM +0100, Peter Zijlstra wrote:
> > On Mon, Oct 27, 2014 at 09:06:21PM +0800, Fengguang Wu wrote:
> > > Hi Peter,
> > >
> > > FYI, this bug seems still there on v3.18-rc2.
> >
> > Oh, right, I commented out that patch and the audit one because I was
> > waiting for some feedback. Lemme go prod people.
>
> audit? I do hit an kauditd_thread warning recently:
Yep that one, see:
http://lkml.kernel.org/r/20141027134103.GA10476(a)twins.programming.kicks-ass.net
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Peter Hurley <peter@hurleysoftware.com>,
Marcel Holtmann <marcel@holtmann.org>, LKP <lkp@01.org>,
linux-kernel@vger.kernel.org, Richard Guy Briggs <rgb@redhat.com>,
Eric Paris <eparis@redhat.com>
Subject: Re: [rfcomm_run] WARNING: CPU: 0 PID: 95 at kernel/sched/core.c:7312 __might_sleep()
Date: Mon, 27 Oct 2014 15:07:26 +0100 [thread overview]
Message-ID: <20141027140726.GJ3337@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20141027134948.GA8977@wfg-t540p.sh.intel.com>
On Mon, Oct 27, 2014 at 09:49:48PM +0800, Fengguang Wu wrote:
> On Mon, Oct 27, 2014 at 02:36:27PM +0100, Peter Zijlstra wrote:
> > On Mon, Oct 27, 2014 at 09:06:21PM +0800, Fengguang Wu wrote:
> > > Hi Peter,
> > >
> > > FYI, this bug seems still there on v3.18-rc2.
> >
> > Oh, right, I commented out that patch and the audit one because I was
> > waiting for some feedback. Lemme go prod people.
>
> audit? I do hit an kauditd_thread warning recently:
Yep that one, see:
http://lkml.kernel.org/r/20141027134103.GA10476@twins.programming.kicks-ass.net
next prev parent reply other threads:[~2014-10-27 14:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 13:06 [rfcomm_run] WARNING: CPU: 0 PID: 95 at kernel/sched/core.c:7312 __might_sleep() Fengguang Wu
2014-10-27 13:36 ` Peter Zijlstra
2014-10-27 13:36 ` Peter Zijlstra
2014-10-27 13:49 ` Fengguang Wu
2014-10-27 13:49 ` Fengguang Wu
2014-10-27 14:07 ` Peter Zijlstra [this message]
2014-10-27 14:07 ` Peter Zijlstra
2014-10-27 17:33 ` Richard Guy Briggs
2014-10-27 17:33 ` Richard Guy Briggs
2014-10-27 14:03 ` Fengguang Wu
2014-10-27 14:03 ` Fengguang Wu
2014-10-31 12:10 ` Peter Zijlstra
2014-10-31 12:10 ` Peter Zijlstra
2014-10-31 13:15 ` Fengguang Wu
2014-10-31 13:15 ` Fengguang Wu
2014-10-31 13:57 ` Peter Zijlstra
2014-10-31 13:57 ` Peter Zijlstra
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=20141027140726.GJ3337@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=lkp@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.