From owner-freebsd-current Tue Nov 19 13:29: 9 2002 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 8524237B401 for ; Tue, 19 Nov 2002 13:29:08 -0800 (PST) Received: from c001.snv.cp.net (h000.c001.snv.cp.net [209.228.32.114]) by mx1.FreeBSD.org (Postfix) with SMTP id D2EAB43E77 for ; Tue, 19 Nov 2002 13:29:02 -0800 (PST) (envelope-from kutulu@kutulu.org) Received: (cpmta 7926 invoked from network); 19 Nov 2002 13:29:01 -0800 Received: from 64.212.128.3 (HELO kutulu) by smtp.register-admin.com (209.228.32.114) with SMTP; 19 Nov 2002 13:29:01 -0800 X-Sent: 19 Nov 2002 21:29:01 GMT Message-ID: <013601c29012$ad9e02a0$29330f0a@lcapps.educate.com> From: "Kutulu" To: Subject: hard drive panics & help getting backtraces... Date: Tue, 19 Nov 2002 16:29:00 -0500 Organization: KutuluWare Software Services MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 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 I'm having occasional panics when doing disk-intensive activities like a buildworld or portupgrade, and I'm having trouble getting useful backtraces. For some reason I can't get the kernel to write a dump out. Most recently, while updating the pkgdb, my system did this: Nov 19 14:47:19 basement syslogd: kernel boot file is /boot/kernel/kernel Nov 19 14:47:19 basement kernel: Slab at 0xc165bfd4, freei 1 = 0. Nov 19 14:47:19 basement kernel: panic: Duplicate free of item 0xc165b0cc from zone 0xc0a023c0(VMSPACE) Nov 19 14:47:19 basement kernel: Nov 19 14:47:19 basement kernel: Nov 19 14:47:19 basement kernel: syncing disks, buffers remaining... panic: bremfree: bp 0xc251d26c not locked Nov 19 14:47:19 basement kernel: Uptime: 1d1h20m15s Nov 19 14:47:19 basement kernel: Dumping 63 MB Nov 19 14:47:19 basement kernel: ata0: resetting devices .. Nov 19 14:47:19 basement kernel: panic: bremfree: bp 0xc250f3e8 not locked Nov 19 14:47:19 basement kernel: Uptime: 1d1h20m15s Nov 19 14:47:19 basement kernel: Terminate ACPI Nov 19 14:47:19 basement kernel: Automatic reboot in 15 seconds - press a key on the console to abort Nov 19 14:47:19 basement kernel: Rebooting... I have a dumpdev set up pointing to my swap space /dev/ad0s1b, I have DDB and DDB_UNATTENDED built into the kernel. I have a kernel with symbols in to use for getting a backtrace, if I could get a core dump from the kernel. What am I missing here? If neccessary, is there a way to force a core dump if I let it break into DDB and go sit at the console? --Mike Edenfield To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message