From owner-freebsd-current Sun Apr 25 20:30:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from intrepid.leaky.com (cx74391-a.fed1.sdca.home.com [24.0.162.8]) by hub.freebsd.org (Postfix) with ESMTP id 01F3414C2D for ; Sun, 25 Apr 1999 20:30:42 -0700 (PDT) (envelope-from gshaffer@leaky.com) Received: (from admin@localhost) by intrepid.leaky.com (8.9.3/8.8.5) id UAA00978; Sun, 25 Apr 1999 20:28:47 -0700 (PDT) X-Authentication-Warning: intrepid.leaky.com: admin set sender to using -f Received: from aegis.leaky.com(199.184.74.2) by intrepid.leaky.com via smap (V2.1) id xma000973; Sun, 25 Apr 99 20:28:22 -0700 From: "Greg Shaffer" To: Cc: Subject: Fatal Trap 12 Date: Sun, 25 Apr 1999 20:31:28 -0700 Message-ID: <000101be8f95$45256410$024ab8c7@aegis.leaky.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I updated my source tree, successfully did a make buildworld and installworld. Rebuilt the kernel. Upon reboot I encountered the following trap. Fatal Trap 12: page fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 fault virtual address = 0xbfc00000 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01dc935 stack pointer = 0x10:0xc0295ed8 frame pointer = 0x10:0xc0295ed8 code segment = base 0x0 limit 0xfffff type 0x1b = DPL 0, page 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL=0 current process = 0 () interrupt mask = net tty bio cam <- SMP:XXX trap number = 12 mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 When it dropped into ddb I got the following: stopped at kvtop+0x2d: movl PTmap(,%eax,4),%edx At trace in ddb provides the following: kvtop(0) at kvtop+0x2d isa_compat_probe(...) at isa_compat_probe+0x297 DEVICE_PROBE(...) at DEVICE_PROBE+0x25 device_probe_child(...) at device_probe_child+0x4a device_probe_and_attach(...) at device_probe_and_attach+0x25 bus_generic_attach(...) at bus_generic_attach+0x16 configure(0) at configure+0x46 main at main+0x83 begin at begin+0x55 This is an dual 233MMX system with hardware I have been using for several years without any problems. The last kernel I built was on 4 April. Everything worked fine. Also, the GENERIC kernel does works. I have looked through my config file and compared it against GENERIC and nothing seems to be out of wack. The fault occured right after probing the ppbus. I thought that might be the problem, but commenting out the ppbus stuff does not prevent it from faulting. Any suggenstions would be appriciated. Thanks Greg Shaffer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message