From owner-freebsd-stable Fri Mar 7 4:28: 7 2003 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BA0837B401 for ; Fri, 7 Mar 2003 04:28:04 -0800 (PST) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CF9343F3F for ; Fri, 7 Mar 2003 04:28:03 -0800 (PST) (envelope-from mike@sentex.net) Received: from house.sentex.net (cage.simianscience.com [64.7.134.1]) by smtp1.sentex.ca (8.12.8/8.12.6) with ESMTP id h27CS2x6006668; Fri, 7 Mar 2003 07:28:03 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <5.2.0.9.0.20030307072636.084b9348@192.168.0.12> X-Sender: mdtancsa@192.168.0.12 X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Fri, 07 Mar 2003 07:30:04 -0500 To: "Michael L. Squires" From: Mike Tancsa Subject: Re: Still seeing SMP panics on a older dual PIII (with debug kernel and crash dumps) Cc: FreeBSD Stable In-Reply-To: <200303061545.h26FjtBk003346@siralan.org> References: <5.2.0.9.0.20030306071303.081fe368@192.168.0.12> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is this not the same place as the last 2 panics ? SMP 2 cpus IdlePTD at phsyical address 0x0038c000 initial pcb at physical address 0x002ed580 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 fault virtual address = 0xf5257d97 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0192a6c stack pointer = 0x10:0xdda6ae40 frame pointer = 0x10:0xdda6ae5c 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 = 33568 (sendmail) interrupt mask = <- SMP: XXX trap number = 12 panic: page fault mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 boot() called on cpu#1 #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 487 if (dumping++) { (kgdb) bt #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 #1 0xc0155878 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:316 #2 0xc0155ce0 in poweroff_wait (junk=0xc02c0d19, howto=-1070856209) at /usr/src/sys/kern/kern_shutdown.c:595 #3 0xc0283d71 in trap_fatal (frame=0xdda6ae00, eva=4112874903) at /usr/src/sys/i386/i386/trap.c:974 #4 0xc02839e9 in trap_pfault (frame=0xdda6ae00, usermode=0, eva=4112874903) at /usr/src/sys/i386/i386/trap.c:867 #5 0xc0283547 in trap (frame={tf_fs = -578748392, tf_es = -577699824, tf_ds = -576323568, tf_edi = -1016904475, tf_esi = -1027665755, tf_ebp = -576278948, tf_isp = -576278996, tf_ebx = -182092393, tf_edx = -1027665721, tf_ecx = -1027665723, tf_eax = 28, tf_trapno = 12, tf_err = 0, tf_eip = -1072092564, tf_cs = 8, tf_eflags = 66178, tf_esp = 13568, tf_ss = -1016904480}) at /usr/src/sys/i386/i386/trap.c:466 #6 0xc0192a6c in ifa_ifwithnet (addr=0xc36344e0) at /usr/src/sys/net/if.c:611 #7 0xc01b6e05 in in_pcbladdr (inp=0xdb942e00, nam=0xc36344e0, plocal_sin=0xdda6ae94) at /usr/src/sys/netinet/in_pcb.c:459 #8 0xc01b6ef3 in in_pcbconnect (inp=0xdb942e00, nam=0xc36344e0, p=0xdd913040) at /usr/src/sys/netinet/in_pcb.c:526 #9 0xc01cc7e9 in udp_connect (so=0xdb704c40, nam=0xc36344e0, p=0xdd913040) at /usr/src/sys/netinet/udp_usrreq.c:866 #10 0xc0174a54 in soconnect (so=0xdb704c40, nam=0xc36344e0, p=0xdd913040) at /usr/src/sys/kern/uipc_socket.c:389 #11 0xc0178118 in connect (p=0xdd913040, uap=0xdda6af80) at /usr/src/sys/kern/uipc_syscalls.c:394 #12 0xc02840b5 in syscall2 (frame={tf_fs = 673906735, tf_es = 673906735, tf_ds = -1078001617, tf_edi = -1077983904, tf_esi = 59, tf_ebp = -1077996464, tf_isp = -576278572, tf_ebx = 673944780, tf_edx = 0, tf_ecx = 0, tf_eax = 98, tf_trapno = 12, tf_err = 2, tf_eip = 673621160, tf_cs = 31, tf_eflags = 659, tf_esp = -1077997132, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1175 #13 0xc027085b in Xint0x80_syscall () cannot read proc at 0 (kgdb) Also, if it were a hardware issue, would not the crashes be a little more random than 24hrs ? ---Mike At 10:45 AM 3/6/2003 -0500, Michael L. Squires wrote: > > Its an older dual PIII. Can anyone tell me if the dumps point to a > > hardware issue, or if its crashing in the same spot each time ? I can > blast > > it with buildworlds and it never dies. Generally I have yet to find bad > > hardware that could pass that.... But always a first time. > >I have a P6DGH with two PII/300's running 4.8-RC2; mptable crashes with >a "HOSED" error message for the extended table (indicative of a BIOS >problems) but no crashes. > >MLS > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet since 1994 www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message