All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tim Sander" <tim.sander@hbm.com>
To: "Peter Zijlstra" <peterz@infradead.org>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Paul E. McKenney" <paulmck@us.ibm.com>,
	"linux-rt-users" <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.0.1-rt8 - Regression to 3.0-rt7
Date: Thu, 11 Aug 2011 14:52:28 +0200	[thread overview]
Message-ID: <201108111452.29075.tim.sander@hbm.com> (raw)
In-Reply-To: <1313064142.7144.1.camel@twins>

Hi Peter

Am Donnerstag, 11. August 2011, 14:02:22 schrieb Peter Zijlstra:
> On Thu, 2011-08-11 at 13:30 +0200, Tim Sander wrote:
> > The error does not occur  when configured with
> > CONFIG_PREEMPT_RT_FULL=y
> > but with
> > CONFIG_PREEMPT_RTB=y.
> > The same error also happens with
> > CONFIG_PREEMPT_LL=y. (A log is appended after the other log just
> > search for CONFIG_PREEMPT_LL
> > for starting point).
> 
> Does the below (on top of -rt8) cure things for you? Shouldn't make a
> difference for PREEMPT_LL though, so maybe there's something else busted
> as well. But from what I can tell PREEMPT_BASE should be fine with such
> things disabling preemption..
I havent tested but i tested appling rt8 to 3.0 and then git diffstat.
Kind of a manual bisecting. Since you still seem to be currently looking at 
this: 
The current remaining offenders on the list from 3.0-rt7 are:
 git diff --stat rt8-test
 kernel/ksysfs.c       |   12 ------
 kernel/lockdep.c      |    5 ++-
 kernel/sched_cpupri.c |   28 ++-------------
 localversion-rt       |    2 +-
 mm/memory.c           |    2 -
 mm/slab.c             |   92 +++++++++++-------------------------------------
 6 files changed, 29 insertions(+), 112 deletions(-)

Will test the patch later on.

Best regards
Tim

Hottinger Baldwin Messtechnik GmbH, Im Tiefen See 45, 64293 Darmstadt, Germany | www.hbm.com 

Registered as GmbH (German limited liability corporation) in the commercial register at the local court of Darmstadt, HRB 1147  
Company domiciled in Darmstadt | CEO: Andreas Huellhorst | Chairman of the board: James Charles Webster

Als Gesellschaft mit beschraenkter Haftung eingetragen im Handelsregister des Amtsgerichts Darmstadt unter HRB 1147 
Sitz der Gesellschaft: Darmstadt | Geschaeftsfuehrung: Andreas Huellhorst | Aufsichtsratsvorsitzender: James Charles Webster

The information in this email is confidential. It is intended solely for the addressee. If you are not the intended recipient, please let me know and delete this email.

Die in dieser E-Mail enthaltene Information ist vertraulich und lediglich für den Empfaenger bestimmt. Sollten Sie nicht der eigentliche Empfaenger sein, informieren Sie mich bitte kurz und loeschen diese E-Mail.


WARNING: multiple messages have this Message-ID (diff)
From: "Tim Sander" <tim.sander@hbm.com>
To: "Peter Zijlstra" <peterz@infradead.org>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Paul E. McKenney" <paulmck@us.ibm.com>,
	"linux-rt-users" <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.0.1-rt8 - Regression to 3.0-rt7
Date: Thu, 11 Aug 2011 14:52:28 +0200	[thread overview]
Message-ID: <201108111452.29075.tim.sander@hbm.com> (raw)
In-Reply-To: <1313064142.7144.1.camel@twins>

Hi Peter

Am Donnerstag, 11. August 2011, 14:02:22 schrieb Peter Zijlstra:
> On Thu, 2011-08-11 at 13:30 +0200, Tim Sander wrote:
> > The error does not occur  when configured with
> > CONFIG_PREEMPT_RT_FULL=y
> > but with
> > CONFIG_PREEMPT_RTB=y.
> > The same error also happens with
> > CONFIG_PREEMPT_LL=y. (A log is appended after the other log just
> > search for CONFIG_PREEMPT_LL
> > for starting point).
> 
> Does the below (on top of -rt8) cure things for you? Shouldn't make a
> difference for PREEMPT_LL though, so maybe there's something else busted
> as well. But from what I can tell PREEMPT_BASE should be fine with such
> things disabling preemption..
I havent tested but i tested appling rt8 to 3.0 and then git diffstat.
Kind of a manual bisecting. Since you still seem to be currently looking at 
this: 
The current remaining offenders on the list from 3.0-rt7 are:
 git diff --stat rt8-test
 kernel/ksysfs.c       |   12 ------
 kernel/lockdep.c      |    5 ++-
 kernel/sched_cpupri.c |   28 ++-------------
 localversion-rt       |    2 +-
 mm/memory.c           |    2 -
 mm/slab.c             |   92 +++++++++++-------------------------------------
 6 files changed, 29 insertions(+), 112 deletions(-)

Will test the patch later on.

Best regards
Tim

Hottinger Baldwin Messtechnik GmbH, Im Tiefen See 45, 64293 Darmstadt, Germany | www.hbm.com 

Registered as GmbH (German limited liability corporation) in the commercial register at the local court of Darmstadt, HRB 1147  
Company domiciled in Darmstadt | CEO: Andreas Huellhorst | Chairman of the board: James Charles Webster

Als Gesellschaft mit beschraenkter Haftung eingetragen im Handelsregister des Amtsgerichts Darmstadt unter HRB 1147 
Sitz der Gesellschaft: Darmstadt | Geschaeftsfuehrung: Andreas Huellhorst | Aufsichtsratsvorsitzender: James Charles Webster

The information in this email is confidential. It is intended solely for the addressee. If you are not the intended recipient, please let me know and delete this email.

Die in dieser E-Mail enthaltene Information ist vertraulich und lediglich für den Empfaenger bestimmt. Sollten Sie nicht der eigentliche Empfaenger sein, informieren Sie mich bitte kurz und loeschen diese E-Mail.

--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-08-11 12:52 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-05 21:44 [ANNOUNCE] 3.0.1-rt8 Peter Zijlstra
2011-08-08 13:55 ` rcu stalls running 3.0.1-rt8 Mike Galbraith
2011-08-08 23:10   ` Paul E. McKenney
2011-08-09  1:14     ` Mike Galbraith
2011-08-09 15:13 ` [ANNOUNCE] 3.0.1-rt8 - Regression to 3.0-rt7 Tim Sander
2011-08-11  9:43   ` Peter Zijlstra
2011-08-11 11:30     ` Tim Sander
2011-08-11 12:02       ` Peter Zijlstra
2011-08-11 12:52         ` Tim Sander [this message]
2011-08-11 12:52           ` Tim Sander
2011-08-11 15:28         ` Tim Sander
2011-08-11 15:28           ` Tim Sander
2011-08-11 12:41       ` Peter Zijlstra
2011-08-11 16:04         ` Tim Sander
2011-08-11 16:04           ` Tim Sander
2011-08-11 16:14           ` Peter Zijlstra
2011-08-11 16:22             ` Tim Sander
2011-08-11 16:41               ` Tim Sander
2011-08-11 16:41                 ` Tim Sander
2011-08-11 16:39           ` Peter Zijlstra
2011-08-11 17:08             ` Tim Sander
2011-08-11 17:08               ` Tim Sander
2011-08-11 18:05           ` Peter Zijlstra
2011-08-11 18:05             ` Peter Zijlstra
2011-08-12  8:59             ` Tim Sander
2011-08-12  8:59               ` Tim Sander
2011-08-11 10:45   ` Peter Zijlstra
2011-08-11 15:36     ` Tim Sander
2011-08-11 15:36       ` Tim Sander
2011-08-09 18:31 ` [ANNOUNCE] 3.0.1-rt8 Fernando Lopez-Lezcano
2011-08-09 18:47   ` Peter Zijlstra
2011-08-10  1:08     ` Paul E. McKenney
2011-08-10  1:07   ` Paul E. McKenney

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=201108111452.29075.tim.sander@hbm.com \
    --to=tim.sander@hbm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=paulmck@us.ibm.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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.