All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juri Lelli <juri.lelli@arm.com>
To: lkp@lists.01.org
Subject: Re: [sched/deadline] kernel BUG at kernel/sched/deadline.c:805!
Date: Mon, 16 Feb 2015 15:12:44 +0000	[thread overview]
Message-ID: <54E208EC.6010909@arm.com> (raw)
In-Reply-To: <20150216144412.GS24151@twins.programming.kicks-ass.net>

[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]

Hi,

On 16/02/15 14:44, Peter Zijlstra wrote:
> On Mon, Feb 16, 2015 at 02:08:21PM +0100, Peter Zijlstra wrote:
>> On Mon, Feb 16, 2015 at 03:38:34PM +0300, Kirill Tkhai wrote:
>>> We shouldn't enqueue migrating tasks. Please, try this one instead ;)
>>
>> Ha, we should amend that task-rq-lock loop for that. See below.
>>
>> I've not yet tested; going to try and reconstruct a .config that
>> triggers the oops.
> 
> OK, I had to remove -enable-kvm from Wu's script, otherwise the test
> would not hit the CBS limit, and then I had to remove the panic on
> softlockup because well, qemu is so slow you're going to hit that :-)
> 
> But the good news is that I could reproduce and this patch does indeed
> seem to solve it.
> 

I also tested this on top of tip, with kvm actually. So, 1019a359d3dc
seemed to reintroduce what aee38ea95419 "sched/deadline: Fix races
between rt_mutex_setprio() and dl_task_timer()" fixed. But, this patch
seems to fix it again :).

Thanks,

- Juri


WARNING: multiple messages have this Message-ID (diff)
From: Juri Lelli <juri.lelli@arm.com>
To: Peter Zijlstra <peterz@infradead.org>, Kirill Tkhai <tkhai@yandex.ru>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
	Ingo Molnar <mingo@kernel.org>, LKP <lkp@01.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [sched/deadline] kernel BUG at kernel/sched/deadline.c:805!
Date: Mon, 16 Feb 2015 15:12:44 +0000	[thread overview]
Message-ID: <54E208EC.6010909@arm.com> (raw)
In-Reply-To: <20150216144412.GS24151@twins.programming.kicks-ass.net>

Hi,

On 16/02/15 14:44, Peter Zijlstra wrote:
> On Mon, Feb 16, 2015 at 02:08:21PM +0100, Peter Zijlstra wrote:
>> On Mon, Feb 16, 2015 at 03:38:34PM +0300, Kirill Tkhai wrote:
>>> We shouldn't enqueue migrating tasks. Please, try this one instead ;)
>>
>> Ha, we should amend that task-rq-lock loop for that. See below.
>>
>> I've not yet tested; going to try and reconstruct a .config that
>> triggers the oops.
> 
> OK, I had to remove -enable-kvm from Wu's script, otherwise the test
> would not hit the CBS limit, and then I had to remove the panic on
> softlockup because well, qemu is so slow you're going to hit that :-)
> 
> But the good news is that I could reproduce and this patch does indeed
> seem to solve it.
> 

I also tested this on top of tip, with kvm actually. So, 1019a359d3dc
seemed to reintroduce what aee38ea95419 "sched/deadline: Fix races
between rt_mutex_setprio() and dl_task_timer()" fixed. But, this patch
seems to fix it again :).

Thanks,

- Juri


  reply	other threads:[~2015-02-16 15:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-16  7:20 [sched/deadline] kernel BUG at kernel/sched/deadline.c:805! Fengguang Wu
2015-02-16  7:20 ` Fengguang Wu
2015-02-16 11:52 ` Kirill Tkhai
2015-02-16 11:52   ` Kirill Tkhai
2015-02-16 12:38   ` Kirill Tkhai
2015-02-16 12:38     ` Kirill Tkhai
2015-02-16 13:08     ` Peter Zijlstra
2015-02-16 13:08       ` Peter Zijlstra
2015-02-16 14:44       ` Peter Zijlstra
2015-02-16 14:44         ` Peter Zijlstra
2015-02-16 15:12         ` Juri Lelli [this message]
2015-02-16 15:12           ` Juri Lelli
2015-02-18 17:06     ` [tip:sched/core] sched/dl: Prevent enqueue of a sleeping task in dl_task_timer() tip-bot for Kirill Tkhai
2015-02-16 12:49 ` [sched/deadline] kernel BUG at kernel/sched/deadline.c:805! Peter Zijlstra
2015-02-16 12:49   ` Peter Zijlstra
2015-02-16 13:25   ` Fengguang Wu
2015-02-16 13:25     ` Fengguang Wu
2015-02-16 13:29     ` Peter Zijlstra
2015-02-16 13:29       ` Peter Zijlstra
2015-02-16 13:37     ` Fengguang Wu
2015-02-16 13:37       ` Fengguang Wu
2015-02-18 18:00       ` Ingo Molnar
2015-02-18 18:00         ` Ingo Molnar

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=54E208EC.6010909@arm.com \
    --to=juri.lelli@arm.com \
    --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.