From owner-freebsd-bugs@freebsd.org Sun Oct 23 15:31:46 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5FF8BC173DD for ; Sun, 23 Oct 2016 15:31:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 45283890 for ; Sun, 23 Oct 2016 15:31:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9NFVjAT057339 for ; Sun, 23 Oct 2016 15:31:46 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 183618] [panic] Dell PowerEdge R620 -- PERC H710 Mini (mfi) freezes and panics (softdep_deallocate_dependencies) Date: Sun, 23 Oct 2016 15:31:46 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-STABLE X-Bugzilla-Keywords: crash, needs-qa X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: ml@netfence.it X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: mfc-stable9? mfc-stable10? X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2016 15:31:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D183618 ml@netfence.it changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ml@netfence.it --- Comment #1 from ml@netfence.it --- Hello. I'm possibly hit by this bug too. My system will panic and reboot every night since I upgraded to 10.3; occasionally it will just hang without rebooting and require a hardware pow= er cycle. It never had this problem with 9.x. This box features nothing different from several others which are working perfectly; the only "peculiar" thing is the (Intel branded) RAID controller: #pciconf -lv ... mfi0@pci0:1:0:0: class=3D0x010400 card=3D0x92618086 chip=3D0x0079100= 0 rev=3D0x05 hdr=3D0x00 vendor =3D 'LSI Logic / Symbios Logic' device =3D 'MegaRAID SAS 2108 [Liberator]' class =3D mass storage subclass =3D RAID # mfiutil show adapter mfi0 Adapter: Product Name: Intel (R) RAID Controller RS2BL080 Serial Number: SV35012439 Firmware: 12.14.0-0185 RAID Levels: JBOD, RAID0, RAID1, RAID5, RAID6, RAID10, RAID50 Battery Backup: not present NVRAM: 32K Onboard Memory: 512M Minimum Stripe: 8K Maximum Stripe: 1M In constrast to the first bug report, I don't see any hardware error, no "g_vfs_done" line in the logs or whatever; the controller reports everythin= g is fine: # mfiutil show volumes mfi0 Volumes: Id Size Level Stripe State Cache Name mfid0 ( 835G) RAID-5 256K OPTIMAL Enabled=20 Still the backtrace on panic is the same: panic: softdep_deallocate_dependencies: dangling deps cpuid =3D 0 KDB: stack backtrace: #0 0xffffffff804ee170 at kdb_backtrace+0x60 #1 0xffffffff804b4576 at vpanic+0x126 #2 0xffffffff804b4443 at panic+0x43 #3 0xffffffff8068fd2a at softdep_deallocate_dependencies+0x6a #4 0xffffffff805394b5 at brelse+0x145 #5 0xffffffff8053793c at bufwrite+0x3c #6 0xffffffff806ae20f at ffs_write+0x3df #7 0xffffffff8076d519 at VOP_WRITE_APV+0x149 #8 0xffffffff806ec7c9 at vnode_pager_generic_putpages+0x2a9 #9 0xffffffff8076f3b7 at VOP_PUTPAGES_APV+0xa7 #10 0xffffffff806ea6f5 at vnode_pager_putpages+0xc5 #11 0xffffffff806e17f8 at vm_pageout_flush+0xc8 #12 0xffffffff806db432 at vm_object_page_collect_flush+0x182 #13 0xffffffff806db1cd at vm_object_page_clean+0x13d #14 0xffffffff806dadbe at vm_object_terminate+0x8e #15 0xffffffff806eac60 at vnode_destroy_vobject+0x90 #16 0xffffffff806b4232 at ufs_reclaim+0x22 #17 0xffffffff8076e5c7 at VOP_RECLAIM_APV+0xa7 I need to solve this ASAP and I'm willing to provide every info which might= be useful to developers. TIA. --=20 You are receiving this mail because: You are the assignee for the bug.=