linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@samba.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Regression in 32-bit ppc kernel
Date: Sun, 29 Apr 2012 08:42:29 +1000	[thread overview]
Message-ID: <1335652949.20866.14.camel@pasglop> (raw)
In-Reply-To: <1335652870.20866.13.camel@pasglop>

On Sun, 2012-04-29 at 08:41 +1000, Benjamin Herrenschmidt wrote:
> On Sat, 2012-04-28 at 13:09 -0500, Larry Finger wrote:
> > I have done a little more debugging. The problem is definitely coming
> > from 
> > drivers/tty/serial/pmac_zilog.c. I am getting ChanB interrupts while
> > open, which 
> > causes the following code segment to return IRQ_NONE:
> > 
> >         if (r3 & (CHBEXT | CHBTxIP | CHBRxIP)) {
> >                 if (!ZS_IS_OPEN(uap_a)) {
> >                         pmz_debug("ChanB interrupt while open !\n");
> >                         goto skip_b;
> >                 }
> >                 write_zsreg(uap_b, R0, RES_H_IUS);
> >                 zssync(uap_b);
> >                 if (r3 & CHBEXT)
> > 
> > When this section is entered, r3 == 0x2 (CHBTxIP).
> > 
> > 
> Ok. The debug code was meant to spell "while not open" btw :-)
> 
> I have some ideas what's going on. I think the irda stuff can trigger
> interrupts during the open/close sequence before ZS_IS_OPEN is true.
> 
> I'll send a fix.

Hrm, actually, Andreas also found an actual bug here, as we aren't
testing uap_b but uap_a ... oops. I think when I tested chan b I always
had chan a open :-) That will be easy to fix.

Can you try turning the uap_a to uap_b test above and see if that fixes
some of it for you ?

Cheers,
Ben.

      reply	other threads:[~2012-04-28 22:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24 22:58 Regression in 32-bit ppc kernel Larry Finger
2012-04-24 23:53 ` Benjamin Herrenschmidt
2012-04-25  2:37   ` Larry Finger
2012-04-25  4:11     ` Benjamin Herrenschmidt
2012-04-25 15:00       ` Larry Finger
2012-04-25 21:44         ` Benjamin Herrenschmidt
2012-04-27 15:38           ` Larry Finger
2012-04-27 22:26             ` Benjamin Herrenschmidt
2012-04-28  0:02               ` Larry Finger
2012-04-28  0:42                 ` Benjamin Herrenschmidt
2012-04-28 18:09                   ` Larry Finger
2012-04-28 18:23                     ` Andreas Schwab
2012-04-28 22:48                       ` Benjamin Herrenschmidt
2012-04-28 23:17                         ` Larry Finger
2012-04-28 23:23                           ` Benjamin Herrenschmidt
2012-04-28 23:30                             ` Larry Finger
2012-04-28 22:41                     ` Benjamin Herrenschmidt
2012-04-28 22:42                       ` Benjamin Herrenschmidt [this message]

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=1335652949.20866.14.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.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).