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: Fri, 31 Oct 2014 14:57:20 +0100 [thread overview]
Message-ID: <20141031135720.GL10501@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20141031131531.GA28258@wfg-t540p.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 406 bytes --]
On Fri, Oct 31, 2014 at 09:15:31PM +0800, Fengguang Wu wrote:
> Nope. However I find some more bugs that happen around thermal_apic_exit.
> One DEBUG_LOCKS_WARN_ON, one "task blocked for more than 120 seconds",
> and some RCU stalls. I just queued bisects for them. Hopefully we can
> get some results tomorrow.
Yeah, something is very sick there indeed... Hope it settles down and
goes away :-)
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: LKP <lkp@01.org>,
linux-kernel@vger.kernel.org, Fenghua Yu <fenghua.yu@intel.com>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Subject: Re: [rfcomm_run] WARNING: CPU: 0 PID: 95 at kernel/sched/core.c:7312 __might_sleep()
Date: Fri, 31 Oct 2014 14:57:20 +0100 [thread overview]
Message-ID: <20141031135720.GL10501@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <20141031131531.GA28258@wfg-t540p.sh.intel.com>
On Fri, Oct 31, 2014 at 09:15:31PM +0800, Fengguang Wu wrote:
> Nope. However I find some more bugs that happen around thermal_apic_exit.
> One DEBUG_LOCKS_WARN_ON, one "task blocked for more than 120 seconds",
> and some RCU stalls. I just queued bisects for them. Hopefully we can
> get some results tomorrow.
Yeah, something is very sick there indeed... Hope it settles down and
goes away :-)
next prev parent reply other threads:[~2014-10-31 13:57 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
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 [this message]
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=20141031135720.GL10501@worktop.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.