Re: ZFS assertions

From: Santiago Martinez <sm_at_codenetworks.net>
Date: Wed, 10 Feb 2021 11:26:36 +0000
Hi there. sorry for the delay... the sofa kidnapped me yesterday :)

link to the image : https://pasteboard.co/JNHlfgP.jpg

OCR of it:

--------------------------------------------------------------------------------------------------------------------------------------------------

#10 0xffffffff80ba1ac6 at cngrab+0x16
#11 0xffffffff80cBadic at vpanic+0xec
#12 0xffffffff8236bb3a at spl_panic+0x3a
#13 0xffffffff82344686 at avl_add+Bx156
#14 0xffffffffB24d63ea at zap_lockdir_impl+8x3ea
#15 0xffffffff824d948b at zap_cursor_retrieve+8x19b
#16 0xffffffffB823875e0 at zfs_freebsd_readdir+_at_8x3eB
#17 0xffffffffB823875e0 at zfs_freebsd_readdir+_at_8x3eB
WARNING acrtc->event failed at
/usr/ports/graphics/drm-devel-kmod/work/drm-kmod=-drm_v5.4.92_1/drivers/gpu/drn/amd/display/amdgpu_dm/amdgpu_d.c:5894
#2 BxfFffffff82f79836 at commit_tail+Bx46
#4 Bxfffffff82f813b8 at drm_client_nodeset_commit_atomic+B8x148
#5 BxffFfffff82rf81119 at drm_client_nodeset_comnit_force+8x69
#6 BxfFffffff82fc153a at drm_fb_helper_restore_fbdev_mode_unlocked+8x7a
#7 BxFFFfFfff82fbb527 at vt_kms_postswitch+8x167
#11 BxFfffffff8dcBadic at vpanic+Bxec
#12 BxfFffffff8236bb3a at spl_panic+Bx3a
#13 BxFFfffff82344686 at avl_add+8x156
#14 BxfFFIfffff824d63ea at zap_lockdir_impl+Bx3ea
#15 BxFFFFffff824d948b at zap_cursor_retrieve+8x19b

panic: VERIFY(avl_find(tree, neuw_node, &uhere) == NULL) failed

cpuid = 14
time = 1612951853
KDB: stack backtrace:
db_trace_self_urapper() at db_trace_self_urapper+8x2b/frame 8xfffffeBf14d86E
vpanic() at vpanic+8x181/frame Oxfffffe814d868520
spl_panic() at spl_panic+8x3a/frame Bxfffffed14d868580
avl_add() at avl_add+8x156/frame 8xfffffefd14d8685ch
zap_lockdir_impl() at zap_lockdir_impl+8x3ea/frame BxfffffeB814d868690
zap_cursor_retrieve() at zap_cursor_retrieve+8x19b/frame Bxfffffe_at_14d868710
zfs_ freebsd readdir() at zfs_freebsd_readdir+8x3e8/frame BxfffffeB14d868940
VOP_RERDDIR_APV() at VOP_READDIR_APV+Bx38/frame BxfffffeB14d868960
kern_getdirentries() at kern_getdirentries+8x1fb/frame 8xfffffeB14d868a50
sys_getdirentries() at sys_getdirentries+_at_x29/frame BxfffffeB14d868a80
amd64_syscall() at amd64_syscall+Bx12e/frame Oxfffffed14d868bbo
fast_syscall_conmon() at fast_syscall_common+8xf8/frame _at_xfffffed14d868bbo
-â syscall (554, FreeBSD ELF64, sys_getdirentries), rip = 8x88dc8839a,
rsp = _at_x7fffffffcB68, rbp = Ox7?fFFffffcBad â
KDB: enter: panic

--------------------------------------------------------------------------------------------------------------------------------------------------



On 2/10/21 12:51 AM, Alan Somers wrote:

> On Tue, Feb 9, 2021 at 5:37 PM Graham Perrin <grahamperrin_at_gmail.com> wrote:
>
>> On 09/02/2021 14:41, Alan Somers wrote:
>>
>> Re: Current - kernel dump while plasma loading.
>>> … ZFS assertions weren't actually enabled until last night. …
>> <
>> https://cgit.freebsd.org/src/commit/?id=174a7e578a33c01401e33f9bfcc077fc3155251c>
>>
>> noted with thanks.
>>
>> I typically use a GENERIC-NODEBUG kernel config, does this partially
>> negate the benefits of assertions?
>>
>> (If so: for the ZFS case, I'll change it.)
>>
>> Thanks
>>
> That's right.  Most assertions are disabled in GENERIC-NODEBUG.
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"


Received on Wed Feb 10 2021 - 10:26:43 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:27 UTC