From owner-freebsd-stable Sun Oct 1 12:25:50 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pathlink.net (linda.i1.pathlink.com [209.155.56.197]) by hub.freebsd.org (Postfix) with ESMTP id 689A437B66C for ; Sun, 1 Oct 2000 12:25:47 -0700 (PDT) Received: from data (c48797-a.frmt1.sfba.home.com [24.0.77.106]) by pathlink.net (8.9.3/8.9.3) with SMTP id MAA45944 for ; Sun, 1 Oct 2000 12:25:40 -0700 (PDT) (envelope-from kachun@pathlink.com) Message-Id: <200010011925.MAA45944@pathlink.net> To: freebsd-stable@freebsd.org Subject: Re: More panics (different hardware) From: kachun@pathlink.com (Kachun Lee) Date: Sun, 01 Oct 2000 12:25:37 -0700 X-Mailer: WinVN 0.99.8 (x86 32bit) In-Reply-To: References: <95295.970251478@winston.osd.bsdi.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , you say... > > >This system is a PII-300, 128M RAM, an IDE boot drive with an array of >8 seagate baracuda UW drives connected to an Adaptec U2W card. > >This system has been around as a test box. It is running a recent 4.1.1 >kernel from the middle of last week for vinum testing. I have been >experiencing this panic when rsync'ing a large nfs volume to the RAID5 >vinum volume. It usually takes several hours for this to occur. > >Originally, I was running on a generic kernel, but after I started having >difficulties, I compiled a minimal kernel (I had been using soft updates >on the vinum volume) > >I forgot to set dumpdev this time around, but this problem seems easily >reproducable. Thanks to all for their fantastic work. > >Regards, >Stephen > >Fatal trap 12: page fault while in kernel mode >fault virtual address = 0x14 >fault code = supervisor read, page not present >instruction pointer = 0x8:0xc0138c63 >stack pointer = 0x10:0xc8c31cc8 >frame pointer = 0x10:0xc8c31d30 >code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 >processor eflags = trace trap, interrupt enabled, resume, IOPL = 0 >current process = 4 (bufdaemon) >interrupt mask = bio >kernel: type 12 trap, code=0 >Stopped at ahc_action+0x1ef: movl 0x14(%esi),%eax >db> > [snip] I upgraded one of our news servers from 4.0-S to 4.1.1 Release. It panic'ed 3 times in 2 days at exactly the same location. Since it was one of productions system, I had to downgrade it back to 4.0-S. It was an ASUS P2B/DS Dual 800 PIII 512M Ram on board ahc plus 2 2940W. This was the panic info... Fatal trap 12: page fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 01000000 fault virtual address = 0x14 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0134bb3 stack pointer = 0x10:0xd6de3748 frame pointer = 0x10:0xd6de37b0 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 = 141 (nfsd) interrupt mask = bio <- SMP: XXX trap number = 12 panic: page fault mp_lock = 00000002; cpuid = 0; lapic.id = 01000000 boot() called on cpu#0 nm -n kernel ... c0133b9c T read_seeprom c01341ac T verify_cksum c01341e8 t ahc_create_path c0134220 T ahc_attach c0134608 t ahc_freebsd_intr c01346f4 T ahc_done c01349c4 t ahc_action <----------------------------- c0135308 t ahc_get_tran_settings c01353f8 t ahc_async c01354a4 t ahc_execute_scb c01359e4 t ahc_poll c0135ad0 t ahc_setup_data c0135c9c t ahc_set_recoveryscb c0135d1c T ahc_timeout ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message