Date: Sat, 14 Jul 2001 10:15:14 -0700 From: Julian Elischer <julian@elischer.org> To: Martin McFlySr <Martin@McFlySr.Kurgan.Ru> Cc: freebsd-stable@FreeBSD.ORG, net@FreeBSD.ORG Subject: Re: mpd, (GRE/NETGRAPH), kernel panic, abort trap in FreeBSD 3.4 Message-ID: <3B507E22.10AF8D81@elischer.org> References: <1836672504.20010714144450@McFlySr.Kurgan.Ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Martin McFlySr wrote: > > Hello net@FreeBSD.ORG, > > #uname -a > FreeBSD 4.3-STABLE #3: Fri Jul 13 09:37:43 MSD 2001 > > In MyKernel i include all "options NETGRAPH*". > > After run mpd (for pptp session to other fbsd/mpd) and establish session > > >---- > Jul 13 10:22:29 mpd: [vpn] CCP: state change Req-Sent --> Ack-Sent > Jul 13 10:22:29 mpd: [vpn] IPCP: rec'd Configure Ack #2 link 0 (Ack-Sent) > Jul 13 10:22:29 mpd: IPADDR 212.1.227.125 > Jul 13 10:22:29 mpd: COMPPROTO VJCOMP, 16 comp. channels, no comp-cid > Jul 13 10:22:29 mpd: [vpn] IPCP: state change Ack-Sent --> Opened > Jul 13 10:22:29 mpd: [vpn] IPCP: LayerUp > Jul 13 10:22:29 mpd: 200.200.200.200 -> 192.168.1.1 > Jul 13 10:22:29 mpd: [vpn] IFACE: Up event > Jul 13 10:22:29 mpd: [vpn] exec: /sbin/ifconfig ng0 200.200.200.200 192.168 > .1.1 netmask 0xffffffff -link0 > Jul 13 10:22:29 mpd: [vpn] exec: /sbin/route add 0.0.0.0 192.168.1.1 > Jul 13 10:22:29 mpd: [vpn] IFACE: Up event > Jul 13 10:22:29 mpd: MPPC > Jul 13 10:22:29 mpd: 0x00000040: MPPE, 128 bit > Jul 13 10:22:29 mpd: [vpn] CCP: state change Ack-Sent --> Opened > u 23:34 12-Jul-2001) > >---- > > and after 1...2 minutes FreeBSD got a abort trrap 12, address 0x70. > > Hardware is Ok - last " make world " proceeded 6 hours, and mistakes have > not arisen. > > Precisely same problem is described in the letter: > > >--- > Subject: mpd-3.2 makes FreeBSD 4.2R panic > Message-ID: <Pine.SOL.4.10.10104131130310.10167-100000@callisto.rug.ac.be> > Date: Fri, 13 Apr 2001 12:03:48 +0200 (MET DST) > >--- > > but no answer was given :( > > What can i fix this ? If it is reporoducable for you, then you need to make a debug kernel (config -g MYKERNEL) then enable core-dumps (dumpon /dev/ad0s1b) then make sure that when it happens a core-dump is made and then saved at next boot After that you can cd /sys/compile/MYKERNEL gdb -k kernel.debug /somewhere/crashdump to get a full traceback. (info stack) and send that to us.. :-) > > Thank you, > > -- > Saturday, 14 July 2001, > 14:03 > > Best regards from future, > Martin McFlySr, HillDale. -- +------------------------------------+ ______ _ __ | __--_|\ Julian Elischer | \ U \/ / hard at work in | / \ julian@elischer.org +------>x USA \ a very strange | ( OZ ) \___ ___ | country ! +- X_.---._/ presently in San Francisco \_/ \\ v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B507E22.10AF8D81>