From owner-freebsd-isdn Sun Aug 2 03:23:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA22935 for freebsd-isdn-outgoing; Sun, 2 Aug 1998 03:23:02 -0700 (PDT) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from mail.rwth-aachen.de (mail.RWTH-Aachen.DE [137.226.144.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA22851 for ; Sun, 2 Aug 1998 03:21:56 -0700 (PDT) (envelope-from heinig@hdz-ima.rwth-aachen.de) Received: from HDZ-IMA.RWTH-Aachen.de (majestix.hdz-ima.RWTH-Aachen.DE) by mail.rwth-aachen.de (PMDF V5.1-10 #30440) with ESMTP id <01J04M5WE0CI0007ZP@mail.rwth-aachen.de> for freebsd-isdn@FreeBSD.ORG; Sun, 2 Aug 1998 12:22:31 +0200 Received: from MAJESTIX/MAIL by HDZ-IMA.RWTH-Aachen.de (Mercury 1.20); Sun, 02 Aug 1998 12:21:46 +0000 Received: from MAIL by MAJESTIX (Mercury 1.20); Sun, 02 Aug 1998 12:21:20 +0000 Received: from hdz-ima.rwth-aachen.de by HDZ-IMA.RWTH-Aachen.de (Mercury 1.20) with ESMTP; Sun, 02 Aug 1998 12:21:13 +0000 Date: Sun, 02 Aug 1998 12:20:27 +0200 From: Gerald Heinig Subject: Re: Tracing Kernel code (isppp) & possible isdnd bug To: marc@bowtie.nl Cc: Martin Husemann , freebsd-isdn@FreeBSD.ORG Message-id: <35C43D6B.D1743976@hdz-ima.rwth-aachen.de> MIME-version: 1.0 X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit References: <199808020951.LAA22639@bowtie.nl> Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Marc van Kempen wrote: > [..] > > > > > >This is no ISDN level bug. The connection is coming up, but the lcp state > >machine decides to go to state "close" when ipcp goes to "open". This is > >wrong. The rest shows the normal way of disconnecting after lcp enters "close" > >state. So: the bug is on our side (there is no "lcp input..." logged that > >would cause a change to "close"), and it's not in the ISDN related stuff. > > > >Looks like an isppp bug to me. Time to hunt... > > > If you need more specific debug info, just tell me what to do when > it occurs again. If you could just say how you do a kernel trace, that'd be really cool. I wanted to have a go at debugging the problem myself, but I've never worked in the kernel before. All I know is that a *lot* of things that work OK in userland get rather harder in the kernel. Cheers Gerald To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message