Re: [linux] [5.19.0] task hung for indefinite time with call traces when rebooted with Kexec

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Please check https://elinux.org/images/1/14/Linuxkerneldebugging.pdf for example.

e.g. ./scripts/faddr2line vmlinux scsi_remove_target+0x314/0x390

On 2022/08/18 18:43, Tasmiya Nalatwad wrote:
> Please find the location in source code from where i am seeing the call traces generating
> 
> On 8/6/22 15:30, Tetsuo Handa wrote:
>> On 2022/08/05 15:54, Tasmiya Nalatwad wrote:
>>> Greetings,
>>>
>>> [linux] [5.19.0] task hung for indefinite time with call traces when rebooted with Kexec, A restart is required to recover the machine.
>>
>> kexec is waiting for workqueues ("kworker/3:1" and "kworker/3:0") to complete.
>> If this problem happens only when rebooting with kexec, something in kexec path
>> might be preventing these workqueues from completing.
>>
>> Anyway, please repost with locations in source code like syzbot report does.




[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux