From owner-freebsd-stable@FreeBSD.ORG Sun Oct 19 14:47:29 2003 Return-Path: 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 2674516A4B3 for ; Sun, 19 Oct 2003 14:47:29 -0700 (PDT) Received: from techno.sub.ru (webmail.sub.ru [213.247.139.22]) by mx1.FreeBSD.org (Postfix) with SMTP id AA02A43F85 for ; Sun, 19 Oct 2003 14:47:27 -0700 (PDT) (envelope-from tarkhil@webmail.sub.ru) Received: (qmail 14270 invoked by uid 0); 19 Oct 2003 20:42:25 -0000 Received: from unknown (HELO tarkhil.over.ru) (213.148.23.65) by webmail.sub.ru with SMTP; 19 Oct 2003 20:42:25 -0000 Date: Mon, 20 Oct 2003 00:40:36 +0400 From: Alex Povolotsky To: freebsd-stable@freebsd.org Message-Id: <20031020004036.658045a7.tarkhil@webmail.sub.ru> Organization: sub.ru X-Mailer: Sylpheed version 0.9.3claws (GTK+ 1.2.10; i386-portbld-freebsd4.6) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Repeated panics with 4.8-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Oct 2003 21:47:29 -0000 Hello! I'm experiencing repeated (1-4 times a week) non-reproductable panics on 4.8-RELEASE-p13. Actually, they have begun with 4.5-RELEASE, and I hoped that upgrade helped me. Fatal trap 12: page fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 03000000 fault virtual address = 0x6c fault code = supervisor write, page not present instruction pointer = 0x8:0xc0273145 stack pointer = 0x10:0xe7e95dc8 frame pointer = 0x10:0xe7e95de8 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 = 77770 (suexec) interrupt mask = none <- SMP: XXX trap number = 12 panic: page fault mp_lock = 00000002; cpuid = 0; lapic.id = 03000000 boot() called on cpu#0 (kgdb) where #0 0xc017f142 in dumpsys () #1 0xc017ef13 in boot () #2 0xc017f36c in poweroff_wait () #3 0xc0274830 in trap_fatal () #4 0xc02744c1 in trap_pfault () #5 0xc027405f in trap () #6 0xc0273145 in setlock () #7 0xc3a222ba in ?? () #8 0xc01ad903 in vrele () #9 0xc01b4507 in vn_close () #10 0xc01b4e47 in vn_closefile () #11 0xc0174a03 in fdrop () #12 0xc017494b in closef () #13 0xc0173d4d in close () #14 0xc0274b61 in syscall2 () #15 0xc026224b in Xint0x80_syscall () #16 0x2804e718 in ?? () #17 0x2804d84f in ?? () Panic is ALWAYS in somewhere under Xint0x80_syscall. ALWAYS @Supervisor read"; different programs all the time. I think it is somethiung hardware-related, but what? The box is a little aged Intel ISP, 2 CPUs, 3 SCSI disks; correlation with disk activity is REALLY slight. Any ideas, what should I test? I don't get any random sig11. -- Alex.