From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 25BBEB6FD8 for ; Sun, 29 Apr 2012 08:49:48 +1000 (EST) Message-ID: <1335652949.20866.14.camel@pasglop> Subject: Re: Regression in 32-bit ppc kernel From: Benjamin Herrenschmidt To: Larry Finger Date: Sun, 29 Apr 2012 08:42:29 +1000 In-Reply-To: <1335652870.20866.13.camel@pasglop> References: <4F973026.3020103@lwfinger.net> <1335311621.15830.42.camel@pasglop> <4F976352.4060001@lwfinger.net> <1335327081.21961.28.camel@pasglop> <4F98117C.7080309@lwfinger.net> <1335390257.21961.53.camel@pasglop> <4F9ABD67.3060704@lwfinger.net> <1335565573.20866.7.camel@pasglop> <4F9B3398.9060701@lwfinger.net> <1335573757.20866.12.camel@pasglop> <4F9C3252.7020508@lwfinger.net> <1335652870.20866.13.camel@pasglop> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Cc: linuxppc-dev@lists.ozlabs.org, Paul Mackerras , LKML List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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.