From owner-freebsd-isdn Mon May 10 2:30:48 1999 Delivered-To: freebsd-isdn@freebsd.org Received: from peedub.muc.de (newpc.muc.ditec.de [194.120.126.33]) by hub.freebsd.org (Postfix) with ESMTP id 64A2314C8E for ; Mon, 10 May 1999 02:30:44 -0700 (PDT) (envelope-from garyj@peedub.muc.de) Received: from peedub.muc.de (localhost [127.0.0.1]) by peedub.muc.de (8.9.3/8.6.9) with ESMTP id LAA39285 for ; Mon, 10 May 1999 11:29:37 +0200 (CEST) Message-Id: <199905100929.LAA39285@peedub.muc.de> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-isdn@FreeBSD.ORG Subject: Re: irritating messages in all ttyv's Reply-To: Gary Jennejohn In-reply-to: Your message of "Mon, 10 May 1999 11:21:09 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 May 1999 11:29:37 +0200 From: Gary Jennejohn Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hellmuth Michaelis writes: >>From the keyboard of Luke Roberts: > >> >> May 8 12:59:09 dilis /kernel: i4b-L1-timer4_expired: state = F3 Deactiva >ted >> > >> >This is the error (!) message that layer 1 could not be accessed by the >> >upper layers (persistent deactivation). >> >> Hmm... what does this mean exactly? > >There is a timer started in layer 1 in case an upper layer wants to access >to S0 bus. When layer 1 is not able to access the bus for a certain amount >of time, you'll get this message because the timer timed out. > >Now this message could be generated by a strange ISDN setup or hardware >problem (twisted cable, etc) or by a bug so that the message is generated >under special circumstance even if everything is ok. > I think this can also occur if isdnd dies or fails to start for some reason. For example, you have a newer kernel and an old isdnd and the version numbers don't match. --- Gary Jennejohn Home - garyj@muc.de Work - garyj@fkr.dec.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message