崩溃字符串：CPU4上的进程挂起(ialloc prod_proc_handler) 5001毫秒！
适用场景
ONTAP 9.10.1或更高版本
问题描述
发生崩溃、或者事件日志中可能会显示以下消息
Panic string: process on cpu4 hung (ialloc_prod_proc_handler) for 5001 milliseconds! in SK process ialloc_prod_proc_handler on release 9.11.0P1 (C) Panic occurred at: Fri May 6 06:24:36 2022 Panic in process: ialloc_prod_proc_handler Stack frame 0: maytag.ko::sk_save_stackframes(0xffffffff8a377ad0) + 0x30 Stack frame 1: maytag.ko::kmod_dumper(0xffffffff893db400) + 0x6ca Stack frame 2: kernel::dumpcore_on_dumpstack(0xffffffff80c31a60) + 0x5c Stack frame 3: kernel::doadump(0xffffffff806b3380) + 0x50 Stack frame 4: kernel::kern_reboot(0xffffffff806b2b60) + 0x403 Stack frame 5: kernel::vpanic(0xffffffff806b36c0) + 0x4ba Stack frame 6: kernel::panic(0xffffffff806b3450) + 0x42 Stack frame 7: kernel::sk_panic(0xffffffff806b3e60) + 0x62 Stack frame 8: maytag.ko::sk_timeout_cpuhog_mycpu(0xffffffff8b01a370) + 0x17b Stack frame 9: kernel::statclock(0xffffffff80647910) + 0x29 Stack frame 10: kernel::cpu_et_frequency(0xffffffff80b0be30) + 0xb6e Stack frame 11: kernel::cpu_et_frequency(0xffffffff80b0be30) + 0xe52 Stack frame 12: kernel::lapic_handle_timer(0xffffffff80b247a0) + 0xa2 Stack frame 13: kernel::Xtimerint(0xffffffff80ab79a0) + 0x128 Stack frame 14: maytag.ko::vdb_lock(0xffffffff8b042e40) + 0x33 Stack frame 15: maytag.ko::ialloc_process_work_item(0xffffffff89a78920) + 0x3f Stack frame 16: maytag.ko::ialloc_producer_proc_helper(0xffffffff89a78530) + 0x312 Stack frame 17: maytag.ko::pub_ialloc_producer_proc(0xffffffff89a784e0) + 0xb Stack frame 18: kernel::fork_exit(0xffffffff80672e50) + 0xb2 Stack frame 19: kernel::fork_trampoline_sk(0xffffffff80ab6b30) + 0xe
Process ialloc_prod_proc_handler ran for 2005 milliseconds Long running process: ialloc_prod_proc_handler Stack frame 0: maytag.ko::sk_save_stackframes(0xffffffff8a377ad0) + 0x30 Stack frame 1: maytag.ko::misc_set_stack_info(0xffffffff89630cb0) + 0x45 Stack frame 2: maytag.ko::sk_cpuhog_report(0xffffffff88020580) + 0xda Stack frame 3: maytag.ko::sk_timeout_cpuhog_mycpu(0xffffffff8b01a370) + 0xf7 Stack frame 4: kernel::statclock(0xffffffff80647910) + 0x29 Stack frame 5: kernel::cpu_et_frequency(0xffffffff80b0be30) + 0xb6e Stack frame 6: kernel::cpu_et_frequency(0xffffffff80b0be30) + 0xe52 Stack frame 7: kernel::lapic_handle_timer(0xffffffff80b247a0) + 0xa2 Stack frame 8: kernel::Xtimerint(0xffffffff80ab79a0) + 0x128 Stack frame 9: maytag.ko::ialloc_process_work_item(0xffffffff89a78920) + 0x3f Stack frame 10: maytag.ko::ialloc_producer_proc_helper(0xffffffff89a78530) + 0x312 Stack frame 11: maytag.ko::pub_ialloc_producer_proc(0xffffffff89a784e0) + 0xb Stack frame 12: kernel::fork_exit(0xffffffff80672e50) + 0xb2 Stack frame 13: kernel::fork_trampoline_sk(0xffffffff80ab6b30) + 0xe Process ialloc_prod_proc_handler ran for 3012 milliseconds Stack frame 9: maytag.ko::ialloc_check_heuristics(0xffffffff89a78a90) + 0x60 Stack frame 10: maytag.ko::ialloc_process_work_item(0xffffffff89a78920) + 0xbc Stack frame 11: maytag.ko::ialloc_producer_proc_helper(0xffffffff89a78530) + 0x312 Stack frame 12: maytag.ko::pub_ialloc_producer_proc(0xffffffff89a784e0) + 0xb Stack frame 13: kernel::fork_exit(0xffffffff80672e50) + 0xb2 Stack frame 14: kernel::fork_trampoline_sk(0xffffffff80ab6b30) + 0xe