crash subcommand bt -a displays incomplete information
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
makedumpfile (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
---Steps to Reproduce---
1) Using latest daily ISO install 14.04.02 as a Power VM guest. The LPAR has vTPM functionality enabled.
2) Upgrade the kernel to 3.19 level (3.19.0-18-generic)
3) Configure kdump. A fix is required to configure kdump. Refer to defect (https:/
4) Trigger a dump. Dump is captured successfully.
5) Install dbgsym package for the kernel
6) Use crash to analyze the dump.
Crash tool is able to read the dump. But it fails to list back trace for CPUS using bt command.
# crash /usr/lib/
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://
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-
KERNEL: /usr/lib/
DUMPFILE: dump.201506040624 [PARTIAL DUMP]
CPUS: 16
DATE: Wed Dec 31 19:00:00 1969
UPTIME: 00:02:32
LOAD AVERAGE: 0.01, 0.01, 0.01
TASKS: 245
NODENAME: alp9
RELEASE: 3.19.0-18-generic
VERSION: #18~14.04.1-Ubuntu SMP Wed May 20 09:40:36 UTC 2015
MACHINE: ppc64le (3724 Mhz)
MEMORY: 100 GB
PANIC: "Oops: System Reset, sig: 6 [#1]" (check log for details)
PID: 0
COMMAND: "swapper/0"
TASK: c0000000013cca80 (1 of 16) [THREAD_INFO: c000000001448000]
CPU: 0
STATE: TASK_RUNNING (PANIC)
crash> bt -a
PID: 0 TASK: c0000000013cca80 CPU: 0 COMMAND: "swapper/0"
PID: 0 TASK: c0000003dbf3b3c0 CPU: 1 COMMAND: "swapper/1"
PID: 0 TASK: c0000003dbf39f00 CPU: 2 COMMAND: "swapper/2"
PID: 0 TASK: c0000003dbf38a40 CPU: 3 COMMAND: "swapper/3"
PID: 0 TASK: c0000003dbf37580 CPU: 4 COMMAND: "swapper/4"
PID: 0 TASK: c0000003dbf360c0 CPU: 5 COMMAND: "swapper/5"
PID: 0 TASK: c0000003dbf34c00 CPU: 6 COMMAND: "swapper/6"
PID: 0 TASK: c0000003dbf33740 CPU: 7 COMMAND: "swapper/7"
PID: 0 TASK: c0000003dbf32280 CPU: 8 COMMAND: "swapper/8"
PID: 0 TASK: c0000003dbf30dc0 CPU: 9 COMMAND: "swapper/9"
PID: 0 TASK: c0000003dbf2f900 CPU: 10 COMMAND: "swapper/10"
PID: 0 TASK: c0000003dbf2e440 CPU: 11 COMMAND: "swapper/11"
PID: 0 TASK: c0000003dbf2cf80 CPU: 12 COMMAND: "swapper/12"
PID: 0 TASK: c0000003dbf2bac0 CPU: 13 COMMAND: "swapper/13"
PID: 0 TASK: c0000003dbf2a600 CPU: 14 COMMAND: "swapper/14"
PID: 0 TASK: c0000003dbf29140 CPU: 15 COMMAND: "swapper/15"
crash> bt
PID: 0 TASK: c0000000013cca80 CPU: 0 COMMAND: "swapper/0"
crash>
== Comment: #5 - Hari Krishna Bathini <email address hidden> - 2015-06-08 00:31:41 ==
The fix patch is upstream in crash git repo
git://github.
commit id: dc4ea682a21567d
It is part of upstream crash version 7.1.0.
Thanks
Hari
tags: | added: architecture-ppc64le bugnameltc-125880 severity-high targetmilestone-inin--- |
tags: |
added: severity-medium removed: severity-high |
affects: | ubuntu → makedumpfile (Ubuntu) |
tags: |
added: targetmilestone-inin14043 removed: targetmilestone-inin--- |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1463653/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]