From owner-freebsd-current Mon Oct 5 01:05:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27825 for freebsd-current-outgoing; Mon, 5 Oct 1998 01:05:07 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27820 for ; Mon, 5 Oct 1998 01:05:03 -0700 (PDT) (envelope-from kpielorz@caladan.tdx.co.uk) Received: from localhost (kpielorz@localhost) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id JAA07294 for ; Mon, 5 Oct 1998 09:04:40 +0100 (BST) Date: Mon, 5 Oct 1998 09:04:38 +0100 (BST) From: Karl Pielorz To: current@FreeBSD.ORG Subject: Panic with heavy diskaccess - current as of 10/04/98 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, I keep seeing the panic below while I'm trying to untar a 1.5Gb file on my system... I used samba to copy it accross from my PC, which would result in a similar panic about 1 out of 3 attempts... Having safely (and finally) got it accross to the 3.0 box, untarring it _always_ generates the panic at some point... The volume it's on in using Vinum... I've been testing Vinum for a few months, and it was working fine... Having said that - I can't find anything in the panic that looks like 'vinum' - but I'm not an expert ;-) I tried cvsup'ing when I got this error (latest was 11am on Sunday) - can anyone suggest anything? The panic details are below - I've heard nasty things about crashdumps at the moment - are these safe to enable now? If you need more details, most the system config is online at my website - look at http://www.tdx.com/diag Basically it's an SMP machine, no softupdates, no 'noatime' stuff either, apart from Vinum it's mostly 'standard' stuff, 256Mb RAM, twin P-Pro 200's, 3 x 2940UW's + 4 IDE drives (not running bus mastering etc.) The machines had no termination / scsi problems in the past (even under extreme duress)... Regards, Karl Panic Info: Fatal trap 12: page fault while in kernel mode mp_lock = 00000002; cpuid = 0; lapic.id = 00000000 fault virtual address = 0x767265b3 fault code = supervisor write, page not present instruction pointer = 0x8:0xfa631335 stack pointer = 0x10:0xfa5c6de8 frame pointer = 0x10:0xfa5c6df8 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 = 4 (syncer) interrupt mask = <- SMP: XXX kernel: type 12 trap, code=0 Stopped at 0xfa631335: incl 0x40(%eax) db> trace _end(f167afa0,0,f6674690,f6674690,80000000) at 0xfa631335 _end(f6674690,0,f6674690,fa5c6e44,f016387a) at 0xfa631107 _end(f6674690,20000234,fa5c6e50,f0162fa9,fa5c6e74) at 0xfa630ea2 _spec_strategy(fa5c6e74,fa5c6e5c,f019ba25,fa5c6e74,fa5c6e80) at _spec_strategy+0x3e _spec_vnoperate(fa5c6e74,fa5c6e80,f015014f,fa5c6e74,10) at _spec_vnoperate+0x15 _ufs_vnoperatespec(fa5c6e74) at _ufs_vnoperatespec+0x15 _bwrite(f6674690,fa5c6e98,f01547f1,fa5c6ebc,fa5c6ea4) at _bwrite+0xaf _vop_stdbwrite(fa5c6ebc,fa5c6ea4,f0162fa9,fa5c6ebc,fa5c6eb0) at _vop_stdbwrite+0xe _vop_defaultop(fa5c6ebc,fa5c6eb0,f019ba25,fa5c6ebc,fa5c6ec4) at _vop_defaultop+0x15 _spec_vnoperate(fa5c6ebc,fa5c6ec4,f0150368,fa5c6ebc,f01e6828) at _spec_vnoperate+0x15 _ufs_vnoperatespec(fa5c6ebc,f01e6828,f6674690,fa5c6ef0,f0194002) at _ufs_vnoperatespec+0x15 _bawrite(f6674690,0,0,f1720000,f6c0e000) at _bawrite+0x2c _ffs_sbupdate(f16bf600,3,0,f16bfa00,fa5b7b00) at _ffs_sbupdate+0x17e _ffs_sync(f16bfa00,3,f15e1800,fa5b7b00,f16bfa00,2) at _ffs_sync+0x292 _sync_fsync(fa5c6f88) at _sync_fsync+0x74 _sched_sync(fa5b7bf3,f01569cb,f01ed108,2000,f01b1850) at _sched_sync+0xa4 _kproc_start(f01ed108) at _kproc_start+0x32 _fork_trampoline() at _fork_trampoline+0x30 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message