1:09 p.m.
Hi,
I'm trying to use the latest crash via the git repo, on the just
released linux-4.9-rc1 kernel, and I'm hitting this failure when loading
the vmcore. Any ideas?
My crash git HEAD is:
commit 64531dc850f2840cedafa143fe051d2cfeae5247
Author: Dave Anderson <anderson(a)redhat.com>
Date: Thu Oct 13 14:32:43 2016 -0400
crash-7.1.5 -> crash-7.1.6
[root@stevo1 crash]# ./crash /usr/local/src/linux-2.6/vmlinux
/var/crash/127.0.0.1-2016-10-17-02\:12\:50/vmcore
crash 7.1.6
Copyright (C) 2002-2016 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"...
crash: cannot determine thread return address
please wait... (gathering task table data)
crash: invalid structure member offset: thread_info_cpu
FILE: task.c LINE: 2364 FUNCTION: store_context()
[./crash] error trace: 4caf3c => 4c3010 => 4bbac6 => 51da6d
51da6d: OFFSET_verify+189
4bbac6: store_context+1030
4c3010: refresh_hlist_task_table_v3+2256
4caf3c: task_init+3724
[root@stevo1 crash]#
Thanks,
Steve.
4:02 p.m.
Hi,
I'm trying to use the latest crash via the git repo, on the just
released linux-4.9-rc1 kernel, and I'm hitting this failure when loading
the vmcore. Any ideas?
Apparently the 4.9 thread_info structure no longer has a "cpu" member?
Dave
My crash git HEAD is:
commit 64531dc850f2840cedafa143fe051d2cfeae5247
Author: Dave Anderson <anderson(a)redhat.com>
Date: Thu Oct 13 14:32:43 2016 -0400
crash-7.1.5 -> crash-7.1.6
[root@stevo1 crash]# ./crash /usr/local/src/linux-2.6/vmlinux
/var/crash/127.0.0.1-2016-10-17-02\:12\:50/vmcore
crash 7.1.6
Copyright (C) 2002-2016 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"...
crash: cannot determine thread return address
please wait... (gathering task table data)
crash: invalid structure member offset: thread_info_cpu
FILE: task.c LINE: 2364 FUNCTION: store_context()
[./crash] error trace: 4caf3c => 4c3010 => 4bbac6 => 51da6d
51da6d: OFFSET_verify+189
4bbac6: store_context+1030
4c3010: refresh_hlist_task_table_v3+2256
4caf3c: task_init+3724
[root@stevo1 crash]#
Thanks,
Steve.
--
Crash-utility mailing list
Crash-utility(a)redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
9:58 a.m.
----- Original Message -----
> Hi,
>
> I'm trying to use the latest crash via the git repo, on the just
> released linux-4.9-rc1 kernel, and I'm hitting this failure when loading
> the vmcore. Any ideas?
Apparently the 4.9 thread_info structure no longer has a "cpu" member?
Dave
Hi Steve,
It's all due to the 4.9 introduction of CONFIG_THREAD_INFO_IN_TASK:
commit 15f4eae70d365bba26854c90b6002aaabb18c8aa
Author: Andy Lutomirski <luto(a)kernel.org>
Date: Tue Sep 13 14:29:25 2016 -0700
x86: Move thread_info into task_struct
Now that most of the thread_info users have been cleaned up,
this is straightforward.
Most of this code was written by Linus.
Originally-from: Linus Torvalds <torvalds(a)linux-foundation.org>
Signed-off-by: Andy Lutomirski <luto(a)kernel.org>
Cc: Borislav Petkov <bp(a)alien8.de>
Cc: Brian Gerst <brgerst(a)gmail.com>
Cc: Denys Vlasenko <dvlasenk(a)redhat.com>
Cc: H. Peter Anvin <hpa(a)zytor.com>
Cc: Jann Horn <jann(a)thejh.net>
Cc: Josh Poimboeuf <jpoimboe(a)redhat.com>
Cc: Linus Torvalds <torvalds(a)linux-foundation.org>
Cc: Peter Zijlstra <peterz(a)infradead.org>
Cc: Thomas Gleixner <tglx(a)linutronix.de>
Link:
http://lkml.kernel.org/r/a50eab40abeaec9cb9a9e3cbdeafd32190206654.1473801...
Signed-off-by: Ingo Molnar <mingo(a)kernel.org>
commit c65eacbe290b8141554c71b2c94489e73ade8c8d
Author: Andy Lutomirski <luto(a)kernel.org>
Date: Tue Sep 13 14:29:24 2016 -0700
sched/core: Allow putting thread_info into task_struct
If an arch opts in by setting CONFIG_THREAD_INFO_IN_TASK_STRUCT,
then thread_info is defined as a single 'u32 flags' and is the first
entry of task_struct. thread_info::task is removed (it serves no
purpose if thread_info is embedded in task_struct), and
thread_info::cpu gets its own slot in task_struct.
This is heavily based on a patch written by Linus.
Originally-from: Linus Torvalds <torvalds(a)linux-foundation.org>
Signed-off-by: Andy Lutomirski <luto(a)kernel.org>
Cc: Borislav Petkov <bp(a)alien8.de>
Cc: Brian Gerst <brgerst(a)gmail.com>
Cc: Denys Vlasenko <dvlasenk(a)redhat.com>
Cc: H. Peter Anvin <hpa(a)zytor.com>
Cc: Jann Horn <jann(a)thejh.net>
Cc: Josh Poimboeuf <jpoimboe(a)redhat.com>
Cc: Linus Torvalds <torvalds(a)linux-foundation.org>
Cc: Peter Zijlstra <peterz(a)infradead.org>
Cc: Thomas Gleixner <tglx(a)linutronix.de>
Link:
http://lkml.kernel.org/r/a0898196f0476195ca02713691a5037a14f2aac5.1473801...
Signed-off-by: Ingo Molnar <mingo(a)kernel.org>
commit d896fa20a70c9e596438728561e058a74ed3196b
Author: Linus Torvalds <torvalds(a)linux-foundation.org>
Date: Tue Sep 13 14:29:23 2016 -0700
um/Stop conflating task_struct::stack with thread_info
thread_info may move in the future, so use the accessors.
[ Andy Lutomirski wrote this changelog message and changed
"task_thread_info(child)->cpu" to "task_cpu(child)". ]
Signed-off-by: Linus Torvalds <torvalds(a)linux-foundation.org>
Signed-off-by: Andy Lutomirski <luto(a)kernel.org>
Cc: Borislav Petkov <bp(a)alien8.de>
Cc: Brian Gerst <brgerst(a)gmail.com>
Cc: Denys Vlasenko <dvlasenk(a)redhat.com>
Cc: H. Peter Anvin <hpa(a)zytor.com>
Cc: Jann Horn <jann(a)thejh.net>
Cc: Josh Poimboeuf <jpoimboe(a)redhat.com>
Cc: Peter Zijlstra <peterz(a)infradead.org>
Cc: Thomas Gleixner <tglx(a)linutronix.de>
Link:
http://lkml.kernel.org/r/3439705d9838940cc82733a7335fa8c654c37db8.1473801...
Signed-off-by: Ingo Molnar <mingo(a)kernel.org>
You don't have a configuration choice with x86, as it appears it's an
architecture
requirement. It's a fairly significant intrusion w/respect to the crash utility,
so you're pretty much out of luck, for now anyway.
Any chance you can make your vmlinux/vmcore pair available for me to download?
Dave
> My crash git HEAD is:
>
> commit 64531dc850f2840cedafa143fe051d2cfeae5247
> Author: Dave Anderson <anderson(a)redhat.com>
> Date: Thu Oct 13 14:32:43 2016 -0400
>
> crash-7.1.5 -> crash-7.1.6
>
> [root@stevo1 crash]# ./crash /usr/local/src/linux-2.6/vmlinux
> /var/crash/127.0.0.1-2016-10-17-02\:12\:50/vmcore
>
>
> crash 7.1.6
> Copyright (C) 2002-2016 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"...
>
> crash: cannot determine thread return address
> please wait... (gathering task table data)
> crash: invalid structure member offset: thread_info_cpu
> FILE: task.c LINE: 2364 FUNCTION: store_context()
>
> [./crash] error trace: 4caf3c => 4c3010 => 4bbac6 => 51da6d
>
> 51da6d: OFFSET_verify+189
> 4bbac6: store_context+1030
> 4c3010: refresh_hlist_task_table_v3+2256
> 4caf3c: task_init+3724
>
> [root@stevo1 crash]#
>
>
> Thanks,
>
>
> Steve.
>
> --
> Crash-utility mailing list
> Crash-utility(a)redhat.com
> https://www.redhat.com/mailman/listinfo/crash-utility
>
>
--
Crash-utility mailing list
Crash-utility(a)redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
11:27 a.m.
----- Original Message -----
You don't have a configuration choice with x86, as it appears
it's an architecture
requirement. It's a fairly significant intrusion w/respect to the crash utility,
so you're pretty much out of luck, for now anyway.
Any chance you can make your vmlinux/vmcore pair available for me to
download?
Dave
Never mind -- they just released a 4.9-based Fedora kernel today, so
I was able to provision this live system to tinker with:
# uname -r
4.9.0-0.rc1.git0.2.fc26.x86_64
# cat /proc/cpuinfo | grep processor
processor : 0
processor : 6
processor : 8
processor : 10
processor : 16
processor : 22
processor : 24
processor : 26
# crash
crash 7.1.6
Copyright (C) 2002-2016 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 [544MB]: patching 84223 gdb minimal_symbol values
WARNING: cpu 6 DOUBLEFAULT stack: init_tss: 0 orig_ist: ffff92d9d6f85000
WARNING: cpu 6 NMI stack: init_tss: 0 orig_ist: ffff92d9d6f86000
WARNING: cpu 6 DEBUG stack: init_tss: 0 orig_ist: ffff92d9d6f88000
WARNING: cpu 6 MCE stack: init_tss: 0 orig_ist: ffff92d9d6f89000
WARNING: cpu 8 DOUBLEFAULT stack: init_tss: 0 orig_ist: ffff92d9d7005000
WARNING: cpu 8 NMI stack: init_tss: 0 orig_ist: ffff92d9d7006000
WARNING: cpu 8 DEBUG stack: init_tss: 0 orig_ist: ffff92d9d7008000
WARNING: cpu 8 MCE stack: init_tss: 0 orig_ist: ffff92d9d7009000
WARNING: cpu 10 DOUBLEFAULT stack: init_tss: 0 orig_ist: ffff92d9d7085000
WARNING: cpu 10 NMI stack: init_tss: 0 orig_ist: ffff92d9d7086000
WARNING: cpu 10 DEBUG stack: init_tss: 0 orig_ist: ffff92d9d7088000
WARNING: cpu 10 MCE stack: init_tss: 0 orig_ist: ffff92d9d7089000
WARNING: cpu 16 DOUBLEFAULT stack: init_tss: 0 orig_ist: ffff92d9d7205000
WARNING: cpu 16 NMI stack: init_tss: 0 orig_ist: ffff92d9d7206000
WARNING: cpu 16 DEBUG stack: init_tss: 0 orig_ist: ffff92d9d7208000
WARNING: cpu 16 MCE stack: init_tss: 0 orig_ist: ffff92d9d7209000
WARNING: cpu 22 DOUBLEFAULT stack: init_tss: 0 orig_ist: ffff92d9d7385000
WARNING: cpu 22 NMI stack: init_tss: 0 orig_ist: ffff92d9d7386000
WARNING: cpu 22 DEBUG stack: init_tss: 0 orig_ist: ffff92d9d7388000
WARNING: cpu 22 MCE stack: init_tss: 0 orig_ist: ffff92d9d7389000
WARNING: cpu 24 DOUBLEFAULT stack: init_tss: 0 orig_ist: ffff92d9d7405000
WARNING: cpu 24 NMI stack: init_tss: 0 orig_ist: ffff92d9d7406000
WARNING: cpu 24 DEBUG stack: init_tss: 0 orig_ist: ffff92d9d7408000
WARNING: cpu 24 MCE stack: init_tss: 0 orig_ist: ffff92d9d7409000
WARNING: cpu 26 DOUBLEFAULT stack: init_tss: 0 orig_ist: ffff92d9d7485000
WARNING: cpu 26 NMI stack: init_tss: 0 orig_ist: ffff92d9d7486000
WARNING: cpu 26 DEBUG stack: init_tss: 0 orig_ist: ffff92d9d7488000
WARNING: cpu 26 MCE stack: init_tss: 0 orig_ist: ffff92d9d7489000
crash: cannot determine thread return address
crash: invalid structure member offset: thread_info_cpu
FILE: task.c LINE: 2364 FUNCTION: store_context()
[./crash] error trace: 4c4016 => 4bec3d => 52831a => 528299
528299: OFFSET_verify.part.28+73
52831a: OFFSET_verify+58
4bec3d: store_context+1021
4c4016: refresh_hlist_task_table_v3+2246
#
Thanks,
Dave
10:51 a.m.
Steve,
I have checked in a patch that (at least tentatively) handles the new
CONFIG_THREAD_INFO_IN_TASK configuration introduced in 4.9-rc1:
https://github.com/crash-utility/crash/commit/c9f932440bd06f0a3d6d3ecc30d...
There are still other issues with the most recent kernels, but this patch
should at least get you to a prompt.
Thanks,
Dave
----- Original Message -----
----- Original Message -----
> You don't have a configuration choice with x86, as it appears it's an
architecture
> requirement. It's a fairly significant intrusion w/respect to the crash
utility,
> so you're pretty much out of luck, for now anyway.
>
> Any chance you can make your vmlinux/vmcore pair available for me to
> download?
>
> Dave
>
Never mind -- they just released a 4.9-based Fedora kernel today, so
I was able to provision this live system to tinker with:
# uname -r
4.9.0-0.rc1.git0.2.fc26.x86_64
# cat /proc/cpuinfo | grep processor
processor : 0
processor : 6
processor : 8
processor : 10
processor : 16
processor : 22
processor : 24
processor : 26
# crash
crash 7.1.6
Copyright (C) 2002-2016 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 [544MB]: patching 84223 gdb minimal_symbol values
WARNING: cpu 6 DOUBLEFAULT stack: init_tss: 0 orig_ist: ffff92d9d6f85000
WARNING: cpu 6 NMI stack: init_tss: 0 orig_ist: ffff92d9d6f86000
WARNING: cpu 6 DEBUG stack: init_tss: 0 orig_ist: ffff92d9d6f88000
WARNING: cpu 6 MCE stack: init_tss: 0 orig_ist: ffff92d9d6f89000
WARNING: cpu 8 DOUBLEFAULT stack: init_tss: 0 orig_ist: ffff92d9d7005000
WARNING: cpu 8 NMI stack: init_tss: 0 orig_ist: ffff92d9d7006000
WARNING: cpu 8 DEBUG stack: init_tss: 0 orig_ist: ffff92d9d7008000
WARNING: cpu 8 MCE stack: init_tss: 0 orig_ist: ffff92d9d7009000
WARNING: cpu 10 DOUBLEFAULT stack: init_tss: 0 orig_ist: ffff92d9d7085000
WARNING: cpu 10 NMI stack: init_tss: 0 orig_ist: ffff92d9d7086000
WARNING: cpu 10 DEBUG stack: init_tss: 0 orig_ist: ffff92d9d7088000
WARNING: cpu 10 MCE stack: init_tss: 0 orig_ist: ffff92d9d7089000
WARNING: cpu 16 DOUBLEFAULT stack: init_tss: 0 orig_ist: ffff92d9d7205000
WARNING: cpu 16 NMI stack: init_tss: 0 orig_ist: ffff92d9d7206000
WARNING: cpu 16 DEBUG stack: init_tss: 0 orig_ist: ffff92d9d7208000
WARNING: cpu 16 MCE stack: init_tss: 0 orig_ist: ffff92d9d7209000
WARNING: cpu 22 DOUBLEFAULT stack: init_tss: 0 orig_ist: ffff92d9d7385000
WARNING: cpu 22 NMI stack: init_tss: 0 orig_ist: ffff92d9d7386000
WARNING: cpu 22 DEBUG stack: init_tss: 0 orig_ist: ffff92d9d7388000
WARNING: cpu 22 MCE stack: init_tss: 0 orig_ist: ffff92d9d7389000
WARNING: cpu 24 DOUBLEFAULT stack: init_tss: 0 orig_ist: ffff92d9d7405000
WARNING: cpu 24 NMI stack: init_tss: 0 orig_ist: ffff92d9d7406000
WARNING: cpu 24 DEBUG stack: init_tss: 0 orig_ist: ffff92d9d7408000
WARNING: cpu 24 MCE stack: init_tss: 0 orig_ist: ffff92d9d7409000
WARNING: cpu 26 DOUBLEFAULT stack: init_tss: 0 orig_ist: ffff92d9d7485000
WARNING: cpu 26 NMI stack: init_tss: 0 orig_ist: ffff92d9d7486000
WARNING: cpu 26 DEBUG stack: init_tss: 0 orig_ist: ffff92d9d7488000
WARNING: cpu 26 MCE stack: init_tss: 0 orig_ist: ffff92d9d7489000
crash: cannot determine thread return address
crash: invalid structure member offset: thread_info_cpu
FILE: task.c LINE: 2364 FUNCTION: store_context()
[./crash] error trace: 4c4016 => 4bec3d => 52831a => 528299
528299: OFFSET_verify.part.28+73
52831a: OFFSET_verify+58
4bec3d: store_context+1021
4c4016: refresh_hlist_task_table_v3+2246
#
Thanks,
Dave
--
Crash-utility mailing list
Crash-utility(a)redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
2990
days inactive
2993
days old
devel@lists.crash-utility.osci.io
4 comments
3 participants
participants (3)
-
Dave Anderson -
Dave Anderson -
Steve Wise