[Kernel-packages] [Bug 1655625] [NEW] ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash

2017-01-11 Thread bugproxy 
Public bug reported:

vmcore captured by kdump cannot be opened with crash:

% sudo crash -d1 /usr/lib/debug/boot/vmlinux-4.8.0-34-generic 
/var/crash/201612282137/dump.201612282137
... ...
base kernel version: 0.8.0
linux_banner:

crash: /usr/lib/debug/boot/vmlinux-4 and 
/var/crash/201612282137/dump.201612282137 do not match!

Usage:

  crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
  crash [OPTION]... [NAMELIST]  (live system form)

Enter "crash -h" for details.


Looks like the 'linux_banner' cannot be understood by crash.

And when the vmcore was dumping, this message being showed:

[  729.609196] kdump-tools[5192]: The kernel version is not supported.
[  729.609447] kdump-tools[5192]: The makedumpfile operation may be incomplete.
---uname output---
Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = lpar 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 1. config kdump 
2. trigger kdump
3. analyse vmcore with crash
 
Userspace tool common name: crash/makedumpfile 
 
The userspace tool has the following bit modes: 64-bit 

Userspace rpm: makedumpfile 1.5.9-5ubuntu0.3/crash 7.1.4-1ubuntu4

Userspace tool obtained from project website:  na 
 
*Additional Instructions for Ping Tian Han/pt...@cn.ibm.com: 
-Post a private note with access information to the machine that the bug is 
occuring on.
-Attach ltrace and strace of userspace application.

xtime timespec.tv_sec: 586481e8: Wed Dec 28 21:24:24 2016
utsname:
 sysname: Linux
nodename: boblp1
 release: 4.8.0-32-generic
 version: #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016
 machine: ppc64le
  domainname: (none)
base kernel version: 4.8.0
verify_namelist:
dumpfile /proc/version:
Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)
/usr/lib/debug/boot/vmlinux-4.8.0-32-generic:
Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)

hypervisor: (undetermined)
crash: per_cpu_symbol_search(per_cpu__tvec_bases): NULL
ppc64_vmemmap_init: vmemmap base: f000

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

root@boblp1:/usr/lib/debug/boot# uname -a
Linux boblp1 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
root@boblp1:/usr/lib/debug/boot#


1. Missing v4.8 support related patches in crash tool

   commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
   Author: Dave Anderson 
   Date:   Fri Feb 12 14:32:53 2016 -0500

Fix for the changes made to the kernel module structure introduced by
this kernel commit for Linux 4.5 and later kernels:

  commit 8244062ef1e54502ef55f54cced659913f244c3e
  modules: fix longstanding /proc/kallsyms vs module insertion race.

Without the patch, the crash session fails during initialization
with the error message: "crash: invalid structure member offset:
module_num_symtab".
(ander...@redhat.com)

   commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
   Author: Dave Anderson 
   Date:   Wed Jan 20 09:56:36 2016 -0500

Fix for the changes made to the kernel module structure introduced by
this kernel commit for Linux 4.5 and later kernels:

  commit 7523e4dc5057e157212b4741abd6256e03404cf1
  module: use a structure to encapsulate layout.

Without the patch, the crash session fails during initialization
with the error message: "crash: invalid structure member offset:
module_init_text_size".
(seb...@linux.vnet.ibm.com)

   commit 1e92f9fad3a7e3042b16996306cb2335760ef8c8
   Author: Dave Anderson 
   Date:   Mon Feb 1 16:10:49 2016 -0500

Fix for the replacements made to the kernel's cpu_possible_mask,
cpu_online_mask, cpu_present_mask and cpu_active_mask symbols in
this kernel commit for Linux 4.5 and later kernels:

  commit 5aec01b834fd6f8ca49d1aeede665b950d0c148e
  kernel/cpu.c: eliminate cpu_*_mask

Without the patch, behavior is architecture-specific, dependent upon
whether the cpu mask values are used to calculate the number of cpus.
For example, ARM64 crash sessions fail during session initialization
with the error message "crash: zero-size memory allocation! (called
from )", whereas X86_64 sessions come up normally, but
cpu mask values of zero are stored internally.
(ander...@redhat.com)

   commit 182914debbb9a2671ef644027fedd339aa9c80e0
   Author: Dave Anderson 
   Date:   Fri Sep 23 09:09:15 2016

[Kernel-packages] [Bug 1655625] [NEW] ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash

2017-01-11 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

vmcore captured by kdump cannot be opened with crash:

% sudo crash -d1 /usr/lib/debug/boot/vmlinux-4.8.0-34-generic 
/var/crash/201612282137/dump.201612282137
... ...
base kernel version: 0.8.0
linux_banner:

crash: /usr/lib/debug/boot/vmlinux-4 and 
/var/crash/201612282137/dump.201612282137 do not match!

Usage:

  crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
  crash [OPTION]... [NAMELIST]  (live system form)

Enter "crash -h" for details.


Looks like the 'linux_banner' cannot be understood by crash.

And when the vmcore was dumping, this message being showed:

[  729.609196] kdump-tools[5192]: The kernel version is not supported.
[  729.609447] kdump-tools[5192]: The makedumpfile operation may be incomplete.
---uname output---
Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = lpar 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 1. config kdump 
2. trigger kdump
3. analyse vmcore with crash
 
Userspace tool common name: crash/makedumpfile 
 
The userspace tool has the following bit modes: 64-bit 

Userspace rpm: makedumpfile 1.5.9-5ubuntu0.3/crash 7.1.4-1ubuntu4

Userspace tool obtained from project website:  na 
 
*Additional Instructions for Ping Tian Han/pt...@cn.ibm.com: 
-Post a private note with access information to the machine that the bug is 
occuring on.
-Attach ltrace and strace of userspace application.

xtime timespec.tv_sec: 586481e8: Wed Dec 28 21:24:24 2016
utsname:
 sysname: Linux
nodename: boblp1
 release: 4.8.0-32-generic
 version: #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 2016
 machine: ppc64le
  domainname: (none)
base kernel version: 4.8.0
verify_namelist:
dumpfile /proc/version:
Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)
/usr/lib/debug/boot/vmlinux-4.8.0-32-generic:
Linux version 4.8.0-32-generic (buildd@bos01-ppc64el-001) (gcc version 5.4.0 
20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #34~16.04.1-Ubuntu SMP Tue Dec 
13 17:01:57 UTC 2016 (Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11)

hypervisor: (undetermined)
crash: per_cpu_symbol_search(per_cpu__tvec_bases): NULL
ppc64_vmemmap_init: vmemmap base: f000

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

root@boblp1:/usr/lib/debug/boot# uname -a
Linux boblp1 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
root@boblp1:/usr/lib/debug/boot#


1. Missing v4.8 support related patches in crash tool

   commit 098cdab16dfa6a85e9dad2cad604dee14ee15f66
   Author: Dave Anderson 
   Date:   Fri Feb 12 14:32:53 2016 -0500

Fix for the changes made to the kernel module structure introduced by
this kernel commit for Linux 4.5 and later kernels:

  commit 8244062ef1e54502ef55f54cced659913f244c3e
  modules: fix longstanding /proc/kallsyms vs module insertion race.

Without the patch, the crash session fails during initialization
with the error message: "crash: invalid structure member offset:
module_num_symtab".
(ander...@redhat.com)

   commit 6f1f78e33474d00d5f261d7ed9d835c558b34d61
   Author: Dave Anderson 
   Date:   Wed Jan 20 09:56:36 2016 -0500

Fix for the changes made to the kernel module structure introduced by
this kernel commit for Linux 4.5 and later kernels:

  commit 7523e4dc5057e157212b4741abd6256e03404cf1
  module: use a structure to encapsulate layout.

Without the patch, the crash session fails during initialization
with the error message: "crash: invalid structure member offset:
module_init_text_size".
(seb...@linux.vnet.ibm.com)

   commit 1e92f9fad3a7e3042b16996306cb2335760ef8c8
   Author: Dave Anderson 
   Date:   Mon Feb 1 16:10:49 2016 -0500

Fix for the replacements made to the kernel's cpu_possible_mask,
cpu_online_mask, cpu_present_mask and cpu_active_mask symbols in
this kernel commit for Linux 4.5 and later kernels:

  commit 5aec01b834fd6f8ca49d1aeede665b950d0c148e
  kernel/cpu.c: eliminate cpu_*_mask

Without the patch, behavior is architecture-specific, dependent upon
whether the cpu mask values are used to calculate the number of cpus.
For example, ARM64 crash sessions fail during session initialization
with the error message "crash: zero-size memory allocation! (called
from )", whereas X86_64 sessions come up normally, but
cpu mask values of zero are stored internally.
(ander...@redhat.com)

   commit 182914debbb9a2671ef644027fedd339aa9c80e0
   Author: Dave Anderson 
   Date:   Fri