From owner-freebsd-current Mon Mar 3 8:42:48 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62EC837B401 for ; Mon, 3 Mar 2003 08:42:46 -0800 (PST) Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52D2D43F3F for ; Mon, 3 Mar 2003 08:42:45 -0800 (PST) (envelope-from roberto@eurocontrol.fr) Received: from caerdonn.eurocontrol.fr (caerdonn.eurocontrol.fr [147.196.130.91]) by matrix.eurocontrol.fr (Postfix/TLS) with ESMTP id A72F84A9ED for ; Mon, 3 Mar 2003 17:42:39 +0100 (MET) Received: by caerdonn.eurocontrol.fr (Postfix/TLS, from userid 1193) id 992933B00; Mon, 3 Mar 2003 17:42:39 +0100 (CET) Date: Mon, 3 Mar 2003 17:42:39 +0100 From: Ollivier Robert To: FreeBSD Current Users' list Subject: Panic running mozilla when doing bg fsck Message-ID: <20030303164239.GA661@caerdonn.eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 5.0-CURRENT User-Agent: Mutt/1.5.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello everyone, I'm having panic fairly regularely at the moment and I've seen that trying to run mozilla when fsck_ffs is doing its work in the background is a Bad Thing[tm]. While I'm here, am I the only one to notice that stack traces are not very complete right now? initial pcb at physical address 0x00321080 panicstr: bremfree: bp 0xc7797a70 not locked panic messages: --- panic: Most recently used by none syncing disks, buffers remaining... panic: bremfree: bp 0xc7797a70 not locked Uptime: 7m37s Dumping 255 MB ata0: resetting devices .. done [CTRL-C to abort] [CTRL-C to abort] 16[CTRL-C to abort] [CTRL-C to abort] [CTRL-C to abort] 32 48 64 80 96 112 128 144 160 176 192 208 224 240 --- #0 doadump () at ../../../kern/kern_shutdown.c:239 239 dumping++; (kgdb) where #0 doadump () at ../../../kern/kern_shutdown.c:239 #1 0xc019d6a5 in boot (howto=260) at ../../../kern/kern_shutdown.c:371 #2 0xc019d8e3 in panic () at ../../../kern/kern_shutdown.c:542 #3 0xc01d7c47 in bremfreel (bp=0xc02d9d6d) at ../../../kern/vfs_bio.c:672 #4 0xc01d7bb5 in bremfree (bp=0x0) at ../../../kern/vfs_bio.c:659 #5 0xc01d9cdb in vfs_bio_awrite (bp=0xc264f000) at ../../../kern/vfs_bio.c:1714 #6 0xc01e0def in vop_stdfsync (ap=0xcdd8eaf4) at ../../../kern/vfs_default.c:755 #7 0xc016ad40 in spec_fsync (ap=0xcdd8eaf4) at ../../../fs/specfs/spec_vnops.c:422 #8 0xc016a2f8 in spec_vnoperate (ap=0x0) at ../../../fs/specfs/spec_vnops.c:123 #9 0xc02513a7 in ffs_sync (mp=0xc25a5200, waitfor=2, cred=0xc0eb5e80, td=0xc02fa620) at vnode_if.h:612 #10 0xc01eca6b in sync (td=0xc02fa620, uap=0x0) at ../../../kern/vfs_syscalls.c:138 #11 0xc019d2f2 in boot (howto=256) at ../../../kern/kern_shutdown.c:280 #12 0xc019d8e3 in panic () at ../../../kern/kern_shutdown.c:542 #13 0xc027895d in mtrash_ctor (mem=0xc264f000, size=0, arg=0x0) at ../../../vm/uma_dbg.c:138 #14 0xc0278a00 in mtrash_fini (mem=0x0, size=0) at ../../../vm/uma_dbg.c:189 #15 0xc02762a9 in zone_drain (zone=0x100) at ../../../vm/uma_core.c:630 #16 0xc0276ee5 in zone_foreach (zfunc=0xc0276070 ) at ../../../vm/uma_core.c:1166 #17 0xc0278277 in uma_reclaim () at ../../../vm/uma_core.c:1997 #18 0xc0272ef9 in vm_pageout_scan (pass=0) at ../../../vm/vm_pageout.c:691 #19 0xc0273fae in vm_pageout () at ../../../vm/vm_pageout.c:1480 #20 0xc018a6d4 in fork_exit (callout=0xc0273ce0 , arg=0x0, frame=0x0) at ../../../kern/kern_fork.c:871 [there must be something here after frame #20, right?] -- Ollivier ROBERT -=- Eurocontrol EEC/AMI -=- Ollivier.Robert@eurocontrol.fr FreeBSD caerdonn.eurocontrol.fr 5.0-CURRENT #6: Tue Jan 21 16:05:16 CET 2003 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message