linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastien Dugue <sebastien.dugue@bull.net>
To: Chirag Jog <chirag@linux.vnet.ibm.com>
Cc: J?rgen Mell <j.mell@t-online.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	rt-users <linux-rt-users@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Clark Williams <williams@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Josh Triplett <josht@linux.vnet.ibm.com>,
	"Timothy R. Chavez" <tim.chavez@linux.vnet.ibm.com>
Subject: Re: [PATCH] Fix Bug messages
Date: Thu, 31 Jul 2008 10:00:23 +0200	[thread overview]
Message-ID: <20080731100023.0221ec2b@bull.net> (raw)
In-Reply-To: <20080730171842.GB3420@linux.vnet.ibm.com>

On Wed, 30 Jul 2008 22:48:42 +0530 Chirag Jog <chirag@linux.vnet.ibm.com> wrote:

> * J?rgen Mell <j.mell@t-online.de> [2008-07-30 11:01:32]:
> 
> > Hello Thomas,
> > 
> > On Wednesday, 30. July 2008, Thomas Gleixner wrote:
> > > We are pleased to announce the 2.6.26-rt1 tree, which can be
> > > downloaded from the location:
> > 
> > I have tried the new kernel and have some good news and some bad news:
> > 
> > The good news: The machine boots and seems to run without major problems.
> > 
> > The bad news: It produces continuously lots of bug messages in the error 
> > logs (cf. attached dmesg.tgz). The error at rtmutex.c:743 was already 
> > present in 2.6.25-rt* when ACPI was enabled. The 'using smp_processor_id 
> > ()  in preemptible code' is new here with 2.6.26.
> > 
> > Machine is an old Athlon XP (single core) on an EPOX mainboard with VIA 
> > chipset.
> > 
> > If I can help with testing, please let me know.
> > 
> > Bye,
> >          Jürgen
> > 
> > 
> This patch should solve some of the bug messages.
> It does two things:
> 1. Change rt_runtime_lock to be a raw spinlock as the comment above it
> says: it is nested inside the rq lock.
> 
> 2. Change mnt_writers to be a per_cpu locked variable.
> This eliminates the need for the codepath to disable preemption and
> then potentially sleep, leading to the BUG messages
> 
> Signed-Off-By: Chirag <chirag@linux.vnet.ibm.com>

  Neat, the only remaining BUGs I see are from sock_prot_inuse_add()

BUG: using smp_processor_id() in preemptible [00000000] code: arping/1916
caller is .sock_prot_inuse_add+0x30/0x80
Call Trace:
[c0000000eed2f910] [c000000000010304] .show_stack+0x70/0x1bc (unreliable)
[c0000000eed2f9c0] [c0000000001a2340] .debug_smp_processor_id+0x138/0x168
[c0000000eed2fa70] [c0000000002181f4] .sock_prot_inuse_add+0x30/0x80
[c0000000eed2fb10] [c00000000026d96c] .udp_lib_get_port+0x2a8/0x320
[c0000000eed2fbc0] [c000000000275b30] .inet_bind+0x168/0x248
[c0000000eed2fc60] [c000000000215024] .sys_bind+0x98/0xdc
[c0000000eed2fd90] [c0000000002370bc] .compat_sys_socketcall+0xcc/0x214
[c0000000eed2fe30] [c0000000000086ac] syscall_exit+0x0/0x40
BUG: arping:1916 task might have lost a preemption check!
Call Trace:
[c0000000eed2f890] [c000000000010304] .show_stack+0x70/0x1bc (unreliable)
[c0000000eed2f940] [c00000000004e298] .preempt_enable_no_resched+0x60/0x78
[c0000000eed2f9c0] [c0000000001a2348] .debug_smp_processor_id+0x140/0x168
[c0000000eed2fa70] [c0000000002181f4] .sock_prot_inuse_add+0x30/0x80
[c0000000eed2fb10] [c00000000026d96c] .udp_lib_get_port+0x2a8/0x320
[c0000000eed2fbc0] [c000000000275b30] .inet_bind+0x168/0x248
[c0000000eed2fc60] [c000000000215024] .sys_bind+0x98/0xdc
[c0000000eed2fd90] [c0000000002370bc] .compat_sys_socketcall+0xcc/0x214
[c0000000eed2fe30] [c0000000000086ac] syscall_exit+0x0/0x40

...

  Thanks,

  Sebastien.


--
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

  parent reply	other threads:[~2008-07-31  7:59 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-25 20:09 2.6.24.7-rt15 Thomas Gleixner
2008-07-26 11:03 ` 2.6.24.7-rt15 Carsten Emde
     [not found] ` <1985e0f60807252248n581bdfa0s363f6ce0d283ec2c@mail.gmail.com>
2008-07-26 11:13   ` 2.6.24.7-rt15 Jaswinder Singh
2008-07-26 12:28     ` 2.6.24.7-rt15 Steven Rostedt
2008-07-26 13:22       ` 2.6.24.7-rt15 Daniel Walker
2008-07-26 18:28       ` 2.6.24.7-rt15 Jaswinder Singh
2008-07-27 16:16 ` 2.6.24.7-rt16 Thomas Gleixner
2008-07-27 20:28   ` 2.6.24.7-rt16 Avuton Olrich
2008-07-27 20:37     ` 2.6.24.7-rt16 Thomas Gleixner
2008-07-28  8:12   ` 2.6.24.7-rt16 Wolfgang Grandegger
2008-07-28  9:48     ` 2.6.24.7-rt16 Peter Zijlstra
2008-07-28 10:12       ` 2.6.24.7-rt16 Wolfgang Grandegger
2008-07-29 12:57   ` 2.6.24.7-rt16 Thomas Gleixner
2008-07-29 22:21     ` 2.6.26-rt1 Thomas Gleixner
2008-07-30  9:01       ` 2.6.26-rt1 Jürgen Mell
2008-07-30 17:18         ` [PATCH] Fix Bug messages Chirag Jog
2008-07-30 20:16           ` Jürgen Mell
2008-07-31  6:06           ` Peter Zijlstra
2008-07-31  8:00           ` Sebastien Dugue [this message]
2008-07-31 10:13             ` John Kacur
2008-07-31 11:23               ` Sebastien Dugue
2008-07-31 13:49                 ` John Kacur
2008-07-31 14:01                   ` Peter Zijlstra
2008-07-31 14:10                     ` John Kacur
2008-07-31 14:18                       ` Peter Zijlstra
2008-07-31 14:35                     ` Sebastien Dugue
2008-07-31 15:01                       ` Clark Williams
2008-07-31 15:14                         ` Sebastien Dugue
2008-08-01 21:11         ` 2.6.26-rt1 Paul E. McKenney
2008-08-13 13:30           ` 2.6.26-rt1 Juergen Beisert
2008-08-13 16:37             ` 2.6.26-rt1 Paul E. McKenney
2008-07-30 14:31       ` 2.6.26-rt1 John Kacur
2008-07-30 14:41       ` 2.6.26-rt1 Ryan Hope
2008-08-01 21:11       ` 2.6.26-rt1 Paul E. McKenney
2008-08-11  8:36       ` 2.6.26-rt1 Juergen Beisert

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=20080731100023.0221ec2b@bull.net \
    --to=sebastien.dugue@bull.net \
    --cc=chirag@linux.vnet.ibm.com \
    --cc=j.mell@t-online.de \
    --cc=josht@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=tim.chavez@linux.vnet.ibm.com \
    --cc=williams@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).