From owner-freebsd-current Tue May 14 08:03:19 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA16075 for current-outgoing; Tue, 14 May 1996 08:03:19 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA16070 for ; Tue, 14 May 1996 08:03:15 -0700 (PDT) Received: from diablo.ppp.de (diablo.ppp.de [193.141.101.34]) by who.cdrom.com (8.6.12/8.6.11) with SMTP id IAA25970 for ; Tue, 14 May 1996 08:03:14 -0700 Received: from allegro.lemis.de by diablo.ppp.de with smtp (Smail3.1.28.1 #1) id m0uJKwp-000QaFC; Tue, 14 May 96 16:19 MET DST From: grog@lemis.de (Greg Lehey) Organisation: LEMIS, Schellnhausen 2, 36325 Feldatal, Germany Phone: +49-6637-919123 Fax: +49-6637-919122 Received: (grog@localhost) by allegro.lemis.de (8.6.9/8.6.9) id PAA11697 for current@freebsd.org; Tue, 14 May 1996 15:58:07 +0200 Message-Id: <199605141358.PAA11697@allegro.lemis.de> Subject: More on the ktrace panic To: current@freebsd.org Date: Tue, 14 May 1996 15:58:07 +0200 (MET DST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I started a set of looping ktrace processes and was able to repeat what I am pretty sure is the same panic. Here are the details, copied from the ddb output: Fatal trape 12: page fault while in kernel mode fault virtual address = 0xdeadc0de (:-) fault code = supervisor read, page not present instruction pointer = 0x8:0xf0117a54 stack pointer = 0x10:0xefbffc1c frame pointer = 0x10:0xefbffc38 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 19593 (ppp) interrupt mask = net tty bio kernel: type 12 trap, code=0 Stopped at _free+0x174: movl 0(%eax),%eax stack trace: _free+0x174 _allocbuf+0x1c8 _ffs_realloccg+0x3d5 _ffs_balloc+0x30e _ffs_write+0x2e5 _ktrwrite+0xcd _ktrgenio+0xa5 _write+0xf9 _syscall+0x195 And after typing all that in, I got a dump this time :-) The valued 0xdeadc0de doesn't sound that random to me. I'll follow it up, but if anybody else can give me a pointer, I'd be grateful. Greg