From owner-freebsd-hackers Sat Jan 13 16:50:50 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA01266 for hackers-outgoing; Sat, 13 Jan 1996 16:50:50 -0800 (PST) Received: from peedub.gj.org (ns075.munich.netsurf.de [194.64.166.75]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA01259 for ; Sat, 13 Jan 1996 16:50:40 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by peedub.gj.org (8.7.3/8.6.9) with SMTP id BAA07474; Sun, 14 Jan 1996 01:50:33 GMT Message-Id: <199601140150.BAA07474@peedub.gj.org> X-Authentication-Warning: peedub.gj.org: Host localhost [127.0.0.1] didn't use HELO protocol X-Mailer: exmh version 1.6 4/21/95 To: freebsd-hackers@freefall.FreeBSD.org cc: isdn@muc.ditec.de Subject: Re: Status of ISDN drivers From: Gary Jennejohn Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Jan 1996 01:50:32 +0000 Sender: owner-hackers@FreeBSD.ORG Precedence: bulk I wrote: > This bug is extrememly hard to track down beacuse the fault address is > totally bogus, e.g. 8:0. That's why I suspect that the stack is getting > trashed. what I really meant was that the instruction pointer is 8:0. Makes it hard to track down where the fault is occurring. Here's the last panic message, in case anyone's interested: Jan 11 21:37:23 newpc /kernel: Fatal trap 12: page fault while in kernel mode Jan 11 21:37:23 newpc /kernel: fault virtual address = 0x0 Jan 11 21:37:23 newpc /kernel: fault code = supervisor read, page not present Jan 11 21:37:24 newpc /kernel: instruction pointer = 0x8:0x0 Jan 11 21:37:24 newpc /kernel: code segment = base 0x0, limit 0xffff f, type 0x1b Jan 11 21:37:24 newpc /kernel: = DPL 0, pres 1, def32 1, gran 1 Jan 11 21:37:24 newpc /kernel: processor eflags = interrupt enabled, resume, IOP L = 0 Jan 11 21:37:24 newpc /kernel: current process = Idle Jan 11 21:37:25 newpc /kernel: interrupt mask = net --- Gary Jennejohn Home - Gary.Jennejohn@munich.netsurf.de Work - gjennejohn@frt.dec.com