Ubuntu 16.04.02: crash tool fails with error "cannot find 'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or 'cpu_active_map' symbols".

[bugproxy]

---Problem Description---

Ubuntu 16.04.02: crash tool fails with error "cannot find 'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or 'cpu_active_map' symbols".

---Steps to Reproduce---

1. Install 16.04.02 [ 4.8.0-32-generic ].
2. Configure kdump.
3. Install debug package.
4. trigger crash.
5. run crash tool on dump captured.

sudo tee /etc/apt/sources.list.d/ddebs.list << EOF
deb http://ddebs.ubuntu.com/ $(lsb_release -cs) main restricted universe multiverse
deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-security main restricted universe multiverse
deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-updates main restricted universe multiverse
deb http://ddebs.ubuntu.com/ $(lsb_release -cs)-proposed main restricted universe multiverse
EOF

sudo apt-get update
sudo apt-get install linux-image-$(uname -r)-dbgsym

path: /var/crash/201612190432

Logs
===

root@ltc-haba2:/var/crash/201612190432# crash /usr/lib/debug/boot/vmlinux-4.8.0-32-generic dump.201612190432

crash 7.1.4
Copyright (C) 2002-2015 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 "powerpc64le-unknown-linux-gnu"...

crash: PPC64: cannot find 'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or 'cpu_active_map' symbols

It appears problem is with System.map-4.8.0-32-generic file

(gdb) symbol-file System.map-4.8.0-32-generic -readshow
`/boot/System.map-4.8.0-32-generic': can't read symbols: File format not recognized.
(gdb)

crash System.map-4.8.0-32-generic /usr/lib/debug/boot/vmlinux-4.8.0-32-generic /var/crash/201612260004/dump.201612260004

crash 7.1.4
Copyright (C) 2002-2015 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 "powerpc64le-unknown-linux-gnu"...

crash: PPC64: cannot find 'cpu_possible_map', 'cpu_present_map', 'cpu_online_map' or 'cpu_active_map' symbols

[bugproxy (bugproxy)]

------- Comment (attachment only) From <email address hidden> 2017-01-10 03:49 EDT-------

[bugproxy (bugproxy)]

------- Comment (attachment only) From <email address hidden> 2017-01-10 03:49 EDT-------

[bugproxy (bugproxy)]

------- Comment on attachment From <email address hidden> 2017-01-24 03:30 EDT-------

Please replace crash and makedumpfile binaries with the one attached above and trigger a crash and re-try the test.

[Andrew Cloke (andrew-cloke)]

Initial triage: needs to be investigated by the crash tools maintainer.

[Manoj Iyer (manjo)]

The patch attached to comment #2 does not appear to be a fix for the issue reported in this bug. Could you pls point me to an upstream fix you might have identified that addresses this issue? I can make a best effort in merging that patch in Ubuntu.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-02-28 00:57 EDT-------
(In reply to comment #24)
> The patch attached to comment #2 does not appear to be a fix for the issue
> reported in this bug. Could you pls point me to an upstream fix you might
> have identified that addresses this issue? I can make a best effort in
> merging that patch in Ubuntu.

patch file for crash and makedumpfile attached above fixes this issue and been fixed with the following Ubuntu

https://launchpad.net/ubuntu/+source/crash/7.1.4-1ubuntu4.1
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.5.9-5ubuntu0.4

[Louis Bouchard (louis)]

So correct me if I'm wrong,but you are basically stating that this bug should be Marked as "Fix Released" since it is corrected by the latest crash/makedumpfile SRU ?

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-03-01 01:55 EDT-------
yes right. this is been fixed in

https://launchpad.net/ubuntu/+source/crash/7.1.4-1ubuntu4.1
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.5.9-5ubuntu0.4