public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Yann.LEPROVOST@wavecom.fr
Cc: Daniel Walker <dwalker@mvista.com>,
	linux-kernel@vger.kernel.org, linux-kernel-owner@vger.kernel.org,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Ingo's  realtime_preempt patch causes kernel oops
Date: Wed, 24 May 2006 08:55:34 -0400	[thread overview]
Message-ID: <1148475334.24623.45.camel@localhost.localdomain> (raw)
In-Reply-To: <OFD8B7556E.13DD6F3A-ONC1257178.002C2D9A-C1257178.002D1FC5@wavecom.fr>

On Wed, 2006-05-24 at 10:06 +0200, Yann.LEPROVOST@wavecom.fr wrote:
> The debug serial unit is part of the mainline kernel, this is the common
> link to work with the CSB637 Cogent board.
> I don't know about others AT91RM9200 based board.
> 
> AT91RM9200 also have others USART, but there are no available output
> connectors on the CSB637 board.
> 

Hi Yann,

OK, do you only get the prints from the serial? If so than that is OK,
but if you also log in through the serial, then that is a problem.  In
other words, do you have something like mgetty running to log in through
the serial? 

Looking at the at91_interrupt it can call mutex spin_locks if receiving
data. So this needs care.

Thomas or Ingo,

Maybe the handling of IRQs needs to handle the case that shared irq can
have both a NODELAY and a thread.  The irq descriptor could have a
NODELAY set if any of the actions are NODELAY, but before calling the
interrupt handler (in interrupt context), check if the action is NODELAY
or not, and if not, wake up the thread if not done so already.

thoughts?

-- Steve



  reply	other threads:[~2006-05-24 12:55 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-23 13:40 Ingo's realtime_preempt patch causes kernel oops Yann.LEPROVOST
2006-05-23 14:09 ` Steven Rostedt
2006-05-23 14:19 ` Steven Rostedt
2006-05-23 14:26   ` Thomas Gleixner
2006-05-23 15:33   ` Daniel Walker
2006-05-23 16:02     ` Steven Rostedt
2006-05-23 16:27       ` Yann.LEPROVOST
2006-05-23 17:00         ` Steven Rostedt
2006-05-23 17:10           ` Yann.LEPROVOST
2006-05-23 18:21             ` Steven Rostedt
2006-05-24  8:06               ` Yann.LEPROVOST
2006-05-24 12:55                 ` Steven Rostedt [this message]
2006-05-24 13:13                   ` Thomas Gleixner
2006-05-24 15:32                     ` Sven-Thorsten Dietrich
2006-05-24 15:52                       ` Steven Rostedt
2006-05-24 16:03                         ` Thomas Gleixner
2006-05-24 16:38                           ` Steven Rostedt
2006-05-24 16:55                             ` Thomas Gleixner
2006-05-24 17:09                               ` Sven-Thorsten Dietrich
2006-05-24 16:06                         ` Daniel Walker
2006-05-24 13:58                   ` Yann.LEPROVOST
2006-05-24 16:43                   ` Esben Nielsen
2006-05-24 17:06                     ` Thomas Gleixner
2006-05-24 18:00                       ` Sven-Thorsten Dietrich
2006-05-30 10:00                         ` RT_PREEMPT problem with cascaded irqchip Yann.LEPROVOST
2006-05-30 10:27                           ` Thomas Gleixner
2006-05-30 10:26                             ` Yann.LEPROVOST
2006-05-30 11:22                               ` Thomas Gleixner
2006-05-30 14:44                                 ` Yann.LEPROVOST
2006-05-30 23:25                                   ` Thomas Gleixner
2006-05-31  8:26                                     ` Yann.LEPROVOST
2006-05-24 17:30                     ` Ingo's realtime_preempt patch causes kernel oops Sven-Thorsten Dietrich
     [not found] <OF928FB2B7.5CE25C69-ONC1257177.00596B7A-C1257177.005AAA6F@wavecom.fr>
2006-05-23 16:38 ` Daniel Walker
2006-05-23 16:44   ` Thomas Gleixner

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=1148475334.24623.45.camel@localhost.localdomain \
    --to=rostedt@goodmis.org \
    --cc=Yann.LEPROVOST@wavecom.fr \
    --cc=dwalker@mvista.com \
    --cc=linux-kernel-owner@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox