From owner-freebsd-current Mon Aug 10 03:50:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA20899 for freebsd-current-outgoing; Mon, 10 Aug 1998 03:50:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.carrier.kiev.ua (burka.carrier.kiev.ua [193.193.193.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA20828 for ; Mon, 10 Aug 1998 03:49:59 -0700 (PDT) (envelope-from archer@lucky.net) Received: (from archer@localhost) by burka.carrier.kiev.ua (8.9.0/8.Who.Cares) id NAA09982 for current@freebsd.org; Mon, 10 Aug 1998 13:49:35 +0300 (EEST) Message-ID: <19980810134934.A6840@burka.carrier.kiev.ua> Date: Mon, 10 Aug 1998 13:49:35 +0300 From: Alexander Litvin To: current@FreeBSD.ORG Subject: Re: New softupdates code panics References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.2i In-Reply-To: ; from Brian Feldman on Sun, Aug 09, 1998 at 09:56:19AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Brian Feldman! In message about "New softupdates code panics" on Sun, Aug 09, 1998, at 09:56:19 AM you wrote: > Well, I had patched my ffs_softdep.c and my ufs_vnops.c according to > Luoqi and Kirk's patches and soon after rebooting, I got a panic (I don't > think I was removing anything at the time, but oh well there are other > processes than the ones I watch). I've still got the full debugging kernel > and a core dump, so if anyone wants more just ask. The same here. My system paniced two times for some 4 hours after I've booted kernel with Kirk's patches. The system was not very busy, just ordinary mail/news reception (it is home computer). Here's my backtrace: (kgdb) exec-file /var/crash/kernel.1 (kgdb) symbol-file /var/crash/kernel.debug.0 Reading symbols from /var/crash/kernel.debug.0...done. (kgdb) core-file /var/crash/vmcore.0 IdlePTD 2236416 initial pcb at 1d2304 panicstr: handle_workitem_remove: bad dir delta panic messages: --- panic: handle_workitem_remove: bad dir delta syncing disks... 32 31 28 23 13 2 done dumping to dev 20001, offset 196608 dump 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:286 286 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:286 #1 0xf01149e7 in panic ( fmt=0xf017a1dc "handle_workitem_remove: bad dir delta") at ../../kern/kern_shutdown.c:427 #2 0xf017a2b2 in handle_workitem_remove (dirrem=0xf04daa80) at ../../ufs/ffs/ffs_softdep.c:2560 #3 0xf0177729 in softdep_process_worklist (matchmnt=0x0) at ../../ufs/ffs/ffs_softdep.c:534 #4 0xf0133b46 in sched_sync () at ../../kern/vfs_subr.c:977 #5 0xf010846e in kproc_start (udata=0xf01c8264) at ../../kern/init_main.c:245 #6 0xf019c4d0 in fork_trampoline () #7 0x66da89f0 in ?? () Cannot access memory at address 0x19c410bb. > Cheers, > Brian Feldman > green@unixhelp.com > P.S. This is the first softupdates panic I've had in a _long_ time, so > good job you guys! --- Fairy Tale, n.: A horror story to prepare children for the newspapers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message