Comment 0 for bug 1523606

Revision history for this message
Dave Chiluk (chiluk) wrote :

[Impact]

  * Crash prints
"crash: page excluded: kernel virtual address: ffff8808595a0000 type: "fill_task_struct" "
      on 4.2 and newer levels of the kernel.

[Test Case]

An example of the issue.
$ crash ddeb/usr/lib/debug/boot/vmlinux-4.2.0-18-generic 00092116-dump.201511300126

crash 7.0.3
Copyright (C) 2002-2013 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"...

please wait... (gathering task table data)
crash: page excluded: kernel virtual address: ffff88105b1a0000 type: "fill_task_struct"

crash: page excluded: kernel virtual address: ffff881052fa8000 type: "fill_task_struct"

crash: page excluded: kernel virtual address: ffff880111770000 type: "fill_task_struct"

crash: page excluded: kernel virtual address: ffff880836578000 type: "fill_task_struct"

crash: page excluded: kernel virtual address: ffff880859e68000 type: "fill_task_struct"

crash: page excluded: kernel virtual address: ffff88085b858000 type: "fill_task_struct"

crash: page excluded: kernel virtual address: ffff88084c448000 type: "fill_task_struct"

crash: page excluded: kernel virtual address: ffff88105b530000 type: "fill_task_struct"

crash: page excluded: kernel virtual address: ffff8808595a0000 type: "fill_task_struct"

crash: page excluded: kernel virtual address: ffff8801065a0000 type: "fill_task_struct"

crash: page excluded: kernel virtual address: ffff8808488d0000 type: "fill_task_struct"

crash: page excluded: kernel virtual address: ffff880859dd0000 type: "fill_task_struct"

crash: page excluded: kernel virtual address: ffff880855750000 type: "fill_task_struct"

crash: page excluded: kernel virtual address: ffff881058cd0000 type: "fill_task_struct"

crash: page excluded: kernel virtual address: ffff880bb5150000 type: "fill_task_struct"
      KERNEL: ddeb/usr/lib/debug/boot/vmlinux-4.2.0-18-generic
    DUMPFILE: 00092116-dump.201511300126 [PARTIAL DUMP]
        CPUS: 24
        DATE: Thu Jan 1 00:00:00 1970
      UPTIME: 3 days, 13:28:22
LOAD AVERAGE: 528.67, 526.12, 465.03
       TASKS: 1208
    NODENAME: <redacted>
     RELEASE: 4.2.0-18-generic
     VERSION: #22~14.04.1-Ubuntu SMP Fri Nov 6 22:20:11 UTC 2015
     MACHINE: x86_64 (2397 Mhz)
      MEMORY: 63.9 GB
       PANIC: "Kernel panic - not syncing: NMI IOCK error: Not continuing"
         PID: 0
     COMMAND: "swapper/0"
        TASK: ffffffff81c14500 (1 of 24) [THREAD_INFO: ffffffff81c00000]
         CPU: 0
       STATE: TASK_RUNNING (PANIC)

[Regression Potential]

[TBD]
 * discussion of how regressions are most likely to manifest as a result of this change.

 * It is assumed that any SRU candidate patch is well-tested before
   upload and has a low overall risk of regression, but it's important
   to make the effort to think about what ''could'' happen in the
   event of a regression.

 * This both shows the SRU team that the risks have been considered,
   and provides guidance to testers in regression-testing the SRU.

[Other Info]

It looks like
https://github.com/crash-utility/crash/commit/80b49a879e0ba8ce7c365a2fd88693128a79310f
is the fix for this issue.

Related conversation on mailing list.
https://www.redhat.com/archives/crash-utility/2015-November/msg00022.html