[Bug 183618] [panic] Dell PowerEdge R620 -- PERC H710 Mini (mfi) freezes and panics (softdep_deallocate_dependencies)

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183618

ml at netfence.it changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ml at netfence.it

--- Comment #1 from ml at 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 power
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 at pci0:1:0:0:        class=0x010400 card=0x92618086 chip=0x00791000 rev=0x05
hdr=0x00
    vendor     = 'LSI Logic / Symbios Logic'
    device     = 'MegaRAID SAS 2108 [Liberator]'
    class      = mass storage
    subclass   = 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 everything is
fine:
# mfiutil show volumes
mfi0 Volumes:
  Id     Size    Level   Stripe  State   Cache   Name
 mfid0 (  835G) RAID-5     256K OPTIMAL Enabled 



Still the backtrace on panic is the same:
panic: softdep_deallocate_dependencies: dangling deps
cpuid = 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.

-- 
You are receiving this mail because:
You are the assignee for the bug.