Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 02 Aug 1998 12:20:27 +0200
From:      Gerald Heinig <heinig@hdz-ima.rwth-aachen.de>
To:        marc@bowtie.nl
Cc:        Martin Husemann <martin@rumolt.teuto.de>, freebsd-isdn@FreeBSD.ORG
Subject:   Re: Tracing Kernel code (isppp) & possible isdnd bug
Message-ID:  <35C43D6B.D1743976@hdz-ima.rwth-aachen.de>
References:  <199808020951.LAA22639@bowtie.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?35C43D6B.D1743976>