linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Darcy L. Watkins" <dwatkins@tranzeo.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Kernel 2.6.33.1-rt11 on PPC405 UIC spinlock and serial input overruns
Date: Tue, 6 Apr 2010 09:59:56 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.1004060946000.32352@localhost.localdomain> (raw)
In-Reply-To: <1270145758.27946.48.camel@localhost.localdomain>

On Thu, 1 Apr 2010, Darcy L. Watkins wrote:
> In arch/powerpc/sysdev/uic.c changing all the spinlock functions for
> &uic->lock to their raw_ equivalents appears to fix it.  Also since the

Yes, that lock needs to be raw.

> invoking code appears to already have an rtmutex locked already whenever
> any of these paths are executed, I also tried simply commenting out the
> whole UIC spinlock altogether and that works too.
>
> Perhaps someone more familiar with the powerpc kernel code can advise me
> as to whether or not the uic->lock spinlock in uic.c is redundant (i.e.
> correct to remove it) or the raw spinlock is still needed.

Looks redundant, but I need to have a closer look. Converted it to raw
for now.
 
> I have also observed the following type of errors in dmesg output...
> 
> [  145.583931] ttyS0: 1 input overrun(s)
> 
> I observe these whether I have the earlier BUG present or either of my
> changes to get rid of the BUG error messages.
> 
> All of these conditions also appear when I build kernel 2.6.31.12-rt21
> for the same hardware.
> 
> They do NOT appear when I build kernel 2.6.29.6-rt24 for the same
> hardware.  They also do NOT appear for kernel 2.6.30, 2.6.31 or 2.6.33

Hmm. Which UART driver is this ?

Thanks,

	tglx


  reply	other threads:[~2010-04-06  8:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01 18:15 Kernel 2.6.33.1-rt11 on PPC405 UIC spinlock and serial input overruns Darcy L. Watkins
2010-04-06  7:59 ` Thomas Gleixner [this message]
     [not found]   ` <1270562527.30658.40.camel@localhost.localdomain>
     [not found]     ` <alpine.LFD.2.00.1004061645090.32352@localhost.localdomain>
2010-04-06 18:38       ` Darcy Watkins
2010-04-07 14:19         ` 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=alpine.LFD.2.00.1004060946000.32352@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=dwatkins@tranzeo.com \
    --cc=linux-rt-users@vger.kernel.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 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).