Comment # 20 on bug 1196104 from Takashi Iwai

(In reply to Klaus Schneider-Grosch from comment #19)
> After installation of crash and decompression of
> vmlinux-5.16.11-lp153.2.g90630c5-default:
> 
> crash /var/crash/2022-03-01-19\:09/vmlinux-5.16.11-lp153.2.g90630c5-default
> /var/crash/2022-03-01-19\:09/vmcore
> 
> crash 7.2.9
> Copyright (C) 2002-2020  Red Hat, Inc.
> Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
> Copyright (C) 1999-2006  Hewlett-Packard Co
> Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
> Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
> Copyright (C) 2005, 2011  NEC Corporation
> Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
> Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
> This program is free software, covered by the GNU General Public License,
> and you are welcome to change it and/or distribute copies of it under
> certain conditions.  Enter "help copying" to see the conditions.
> This program has absolutely no warranty.  Enter "help warranty" for details.
> 
> crash: /var/crash/2022-03-01-19:09/vmlinux-5.16.11-lp153.2.g90630c5-default:
> no debugging data available
> crash: vmlinux-5.16.11-lp153.2.g90630c5-default.debug: debuginfo file not
> found
> 
> crash: either install the appropriate kernel debuginfo package, or
>        copy vmlinux-5.16.11-lp153.2.g90630c5-default.debug to this machine 

You could install the corresponding package, kernel-default-debuginfo from the
URL you downloaded the kernel, too.

> The notebook works only perfectly with the kernel
> 5.16.11-lp153.2.g90630c5-default from kernel stable backport repo.

Wait: how was this kdump created?  Wasn't it at the state where the machine got
stuck after resume?  Otherwise it's almost nonsense; we want the kdump at the
broken state, not the working state.

> I tried
> it also with Kernel 5.3.18-150300.59.49-default, but I could not achieve a
> kdump after trying resume. The system got stuck in a unknown  state.

And alt-sysrq-c didn't trigger the kdump at that state?