From owner-freebsd-isdn Sun Feb 28 8:11:20 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (Postfix) with ESMTP id 0D79514F00 for ; Sun, 28 Feb 1999 08:11:14 -0800 (PST) (envelope-from rock@cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.3/1999020800) with ESMTP id RAA24347 for ; Sun, 28 Feb 1999 17:10:56 +0100 (CET) Received: from cs.uni-sb.de (maxtnt-010.rz.uni-sb.de [134.96.70.137]) by cs.uni-sb.de (8.9.3/1999020800) with ESMTP id RAA25665 for ; Sun, 28 Feb 1999 17:10:55 +0100 (CET) X-Authentication-Warning: mail.cs.uni-sb.de: Host maxtnt-010.rz.uni-sb.de [134.96.70.137] claimed to be cs.uni-sb.de Message-ID: <36D96ADC.DCF87A60@cs.uni-sb.de> Date: Sun, 28 Feb 1999 17:12:12 +0100 From: "D. Rock" X-Mailer: Mozilla 4.5 [de] (WinNT; U) X-Accept-Language: de MIME-Version: 1.0 To: freebsd-isdn@FreeBSD.ORG Subject: Re: HSCX wait for XFW timeout (was Re: error message in the logs - 00.70) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am now also seeing these messages sometimes, just after I swiched from an 1.7GB IDE drive to an 4GB IDE drive. Because of some problems with the new drive, I couldn't turn on DMA (which was enabled on the old drive). I never saw this messages with the old one, with the new drive the first message appeared after a few minutes. Daniel Hellmuth Michaelis schrieb: > > Wolfgang Helbig wrote: > > > > i4b-L1-isic_hscx_waitxfw: HSCX wait for XFW timeout! > > > > > > means, and i forgot to answer that one. This is an indication that an IRQ > > > from the HSCX (the chip handling the B-channel) got lost - most likely > > > > Hmm. This timeout occurs while waiting for the transmit buffer > > to accept another 32 bytes to transmit. I don't see how a lost interrupt > > can cause this timeout. (Even if you have IDE drives) > > My theory is, that while waiting, someone else blocks the interrupt for that > long time, that another HSCX transaction starts immediately (by chance out of > the blocked interrupt in which another HSCX interrupt occurs) which clears > implicitely the flag we are waiting for (perhaps i should introduce a > flag signalling that we are in such a wait status, and see what happenes > and who might clear it, but i'm too lazy to do that right now ....). > > When the system in question was changed from SCSI to IDE (nothing else did > change) those messages started to occur, with SCSI i never saw a single > such message. > > hellmuth > -- > Hellmuth Michaelis hm@kts.org Hamburg, Europe > We all live in a yellow subroutine, yellow subroutine, yellow subroutine ... > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isdn" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message