From owner-freebsd-current Sun Sep 10 19:45:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 95A5037B43C for ; Sun, 10 Sep 2000 19:45:29 -0700 (PDT) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.0/8.11.0) with ESMTP id e8B2jO400259 for ; Sun, 10 Sep 2000 19:45:28 -0700 (PDT) (envelope-from null@pozo.com) Message-Id: <4.3.2.7.2.20000910192526.00b280e0@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 10 Sep 2000 19:45:25 -0700 To: current@freebsd.org From: Manfred Antar Subject: New Fatal trap in Current SMP (random.dev changes ??) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From a new kernel compiled from sources current 7:30 pm 9/10/00 pacific time Although the first occurrence happened this morning after compiling a kernel after the random dev changes. The system boots and mounts disks. When it gets to this point: Additional routing options: TCP extensions=NO TCP keepalive=YES. routing daemons:. I think the random dev kicks in at this point Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = 0c000000 fault virtual address = 0x2c fault code = supervisor read, page not present instruction pointer = 0x8:0xc014f280 stack pointer = 0x10:0xc9a74f84 frame pointer = 0x10:0xc9a74f9c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1,def 32 1,gran 1 processor flags = interrupt enabled, resume, IOPL = 0 current process = 2 (random) trap number = 12 panic: page fault cpuid = 1; lapic.id = 0x000000 boot() called on cpu#1 syncing disks....... The machine then is frozen and needs a reset to work again the debugger is unavailable Manfred ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message