From owner-freebsd-bugs@FreeBSD.ORG Tue Sep 30 16:20:08 2008 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5CAAB1065748 for ; Tue, 30 Sep 2008 16:20:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4AB8A8FC13 for ; Tue, 30 Sep 2008 16:20:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8UGK7Tn028641 for ; Tue, 30 Sep 2008 16:20:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8UGK78l028640; Tue, 30 Sep 2008 16:20:07 GMT (envelope-from gnats) Date: Tue, 30 Sep 2008 16:20:07 GMT Message-Id: <200809301620.m8UGK78l028640@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Harald Hanche-Olsen Cc: Subject: Re: kern/119868: [zfs] 7.0 kernel panic during boot with ZFS and WD1600JS X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Harald Hanche-Olsen List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Sep 2008 16:20:08 -0000 The following reply was made to PR kern/119868; it has been noted by GNATS. From: Harald Hanche-Olsen To: bug-followup@FreeBSD.org, johan@giantfoo.org Cc: Subject: Re: kern/119868: [zfs] 7.0 kernel panic during boot with ZFS and WD1600JS Date: Tue, 30 Sep 2008 17:49:17 +0200 (CEST) The original reporter seems to have given up on this. I have seen something very similar, and thought I could provide some more information. I now have three disks all in an unusable state, causing freebsd to panic upon seeing these disks. Common to all is that they contained ZFS pools that were online when the computer crashed, possibly for unrelated reasons. Upon reboot, the computer would panic when noticing the disk; in fact, immediately after printing the standard message giving the device name and disk type on the console. ZFS may however be incidental to the problem: The panic happens even if I don't have zfs.ko loaded when the problem disk is plugged in. I wonder if it could be related to kern/127115 somehow? I cannot get a dump unfortunately - the console says "Dumping xxx MB" and hangs if I have activated kernel dumps (using dumpon) before triggering the panic. So I compiled a debug kernel and obtained a backtrace using ddb instead. Here is output, copied by hand from a photo of the screen: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x3f80 fault code = supervisor read data, page not present [...] current process = 2 (g_event) [thread pid 2 tid 100007 ] Stopped at bcmp+0x8: repe cmpsq (%rsi),%es:(%rdi) db> trace Tracing pid 2 tid 100007 td 0xffffff0001129000 bcmp() at bcmp+0x8 g_part_taste() at g_part_taste+0x252 g_new_provider_event() at g_new_provider_event+0x75 g_run_events() at g_run_events+0x1b8 g_event_procbody() at g_event_procbody+0x57 fork_exit() at fork_exit+0x11f fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffffffb3600d30, rbp = 0 --- I am really not very familiar with ddb. Let me know if you wish me to dig deeper, but then I need a pointer as to what to look for. - Harald