Comment # 21 on bug 1196104 from
Ok, I installed kernel-default-debuginfo for the kernel
5.16.11-lp153.2.g90630c5-default. Sorry, I had overseen that I had to install
this package too.

The kdump was created when the machine got stuck after trying to resume with
kernel 5.16.11-lp153.2.g90630c5-default.

Output from crash:
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.

GNU gdb (GDB) 7.6
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu"...

WARNING: kernel relocated [478MB]: patching 144471 gdb minimal_symbol values

please wait... (gathering task table data)                             
crash: invalid structure member offset: task_struct_cpu
       FILE: task.c  LINE: 2875  FUNCTION: add_context()

[/usr/bin/crash] error trace: 563ad2181aa6 => 563ad2178709 => 563ad2200194 =>
563ad220010d

Something wrong here?

Booted with Kernel 5.3.18-150300.59.49-default alt-sysrq-c did not trigger the
dump after resume. Generally, the machine did not work properly with that
kernel (problems with opening LVM - must vgchange -a y manually and wait a bit,
then init 5 manually), so I changed from the very beginning to the almost
perfect working Kernel 5.16.9 and following versions up to 5.16.11.


You are receiving this mail because: