From owner-freebsd-isdn Mon Jan 14 1:53:11 2002 Delivered-To: freebsd-isdn@freebsd.org Received: from mailout10.sul.t-online.com (mailout10.sul.t-online.com [194.25.134.21]) by hub.freebsd.org (Postfix) with ESMTP id 2B8CB37B41C for ; Mon, 14 Jan 2002 01:53:08 -0800 (PST) Received: from fwd11.sul.t-online.de by mailout10.sul.t-online.com with smtp id 16Q3nf-0004XY-00; Mon, 14 Jan 2002 10:53:07 +0100 Received: from peedub.jennejohn.org (520017439985-0001@[217.80.228.12]) by fmrl11.sul.t-online.com with esmtp id 16Q3nV-22HqaWC; Mon, 14 Jan 2002 10:52:57 +0100 Received: by peedub.jennejohn.org (8.11.6/8.11.6) id g0E9r1Y15890; Mon, 14 Jan 2002 10:53:01 +0100 (CET) (envelope-from garyj) Message-Id: <200201140953.g0E9r1Y15890@peedub.jennejohn.org> Content-Type: text/plain; charset="iso-8859-1" From: Gary Jennejohn Reply-To: garyj@jennejohn.org To: Andrew Gordon Subject: Re: ifpi2 problems - partially fixed! Date: Mon, 14 Jan 2002 10:53:01 +0100 X-Mailer: KMail [version 1.3.2] Cc: References: <20020114090708.I29792-100000@server.arg.sj.co.uk> In-Reply-To: <20020114090708.I29792-100000@server.arg.sj.co.uk> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Sender: 520017439985-0001@t-dialin.net Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Monday 14 January 2002 00:23, Andrew Gordon wrote: > With this patch, I see the printf() at about the same point > where it used to lock up previously (and it now keeps going!). > > @@ -974,6 +972,8 @@ > /* was there an interrupt from this card ? */ > if ((stat & ASL_IRQ_Pending) == 0) > return; /* no */ > + > +again: > /* interrupts are high active */ > if (stat & ASL_IRQ_TIMER) > NDBGL1(L1_H_IRQ, "timer interrupt ???"); > @@ -987,6 +987,14 @@ > NDBGL1(L1_H_IRQ, "ISAC"); > ifpi2_isacsx_intr(sc); > } > + stat = bus_space_read_1(btag, bhandle, STAT0_OFFSET); > + NDBGL1(L1_H_IRQ, "stat %x", stat); > + /* Have we cleared all pending interrupts ? */ > + if ((stat & ASL_IRQ_Pending) != 0) > + { > + printf("Repeat IRQ!\n"); > + goto again; > + } > } > OK, this looks like a reasonable patch, I'll apply it. I think you're right about the slow HW. I did all my testing with a 1.2 GHz Athlon. I also recently installed the driver on a friend's machine with a 166 MHz P2 and never saw any problems under high load. > > > However, there is one remaining problem - which may be a > general I4B bug rather than ifpi2 specific. If I have full > debugging turned on as it tries to make a connection > (isdndebug -l1 -m), then I usually see this: > > Jan 13 19:56:27 router /kernel: i4b: unit 0, assigned TEI = > 116 = 0x74 i4b-L2 i4b_T200_timeout: unit 0, RC = 0 > i4b-L2 i4b_rxd_ack: ((N(R)-1)=127) != (UA=0) !!! > i4b-L2 i4b_invoke_retransmission: nr = 0 > i4b-L2 i4b_invoke_retransmission: nr(0) != vs(1) > i4b-L2 i4b_invoke_retransmission: ERROR, l2sc->vs = 0, > l2sc->ua_num = -1 i4b-L2 i4b_i_frame_queued_up: ERROR, mbuf > NULL after IF_DEQUEUE i4b-L3 T303_timeout: SETUP not answered, > cr = 98 > Hmm, I'll look into it. I also noticed a problem with my friend's machine. If I did a reboot the kernel hung due to an apparent problem with the ifpi2 being in a strange state (not completely reset by the software reset). I had to do a hard reset in order to avoid the hang. On my system here I never observed the problem. -- Gary Jennejohn garyj@jennejohn.org gj@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message