Date: Sun, 8 Dec 1996 13:41:13 -0800 (PST) From: Jake Hamby <jehamby@lightside.com> To: hackers@freebsd.org Subject: How do I diagnose user-mode PPP coredumps? Message-ID: <Pine.BSF.3.95.961208133801.447A-100000@hamby1>
next in thread | raw e-mail | index | archive | help
I use the user-mode PPP daemon extensively on my FreeBSD-current box, and often, after a number of HDLC errors, it will coredump. The ppp.log looks like: 12-08 13:30:21 [143] HDLC errors -> FCS: 5 ADDR: 0 COMD: 0 PROTO: 0 12-08 13:31:21 [143] HDLC errors -> FCS: 1 ADDR: 0 COMD: 0 PROTO: 0 12-08 13:32:21 [143] HDLC errors -> FCS: 4 ADDR: 0 COMD: 0 PROTO: 0 12-08 13:33:21 [143] HDLC errors -> FCS: 1 ADDR: 0 COMD: 0 PROTO: 0 12-08 13:35:21 [143] HDLC errors -> FCS: 1 ADDR: 0 COMD: 0 PROTO: 0 12-08 13:36:21 [143] HDLC errors -> FCS: 1 ADDR: 0 COMD: 0 PROTO: 0 12-08 13:36:21 [143] Signal 11, core dump. The weird thing is that process 143 is still alive, and I must manually "kill -9" it, in order for the phone line to hang up. The other problem is that I don't get a core file anywhere, because it seems to be trapping the SIGSEGV. Does anyone else have this problem? What steps should I follow to start tracing it? I don't know why I'm getting the HDLC errors in the first place, but I have seen CRC errors using PPP with other OS's, so it's possible there's a dirty connection on my ISP's end, or on mine. Any help will be greatly appreciated, and I will post a send-pr when I've found the culprit. -- Jake
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.961208133801.447A-100000>