[Kernel-packages] [Bug 1607894] Comment bridged from LTC Bugzilla

2017-03-09 Thread bugproxy 
--- Comment From naveed...@in.ibm.com 2017-03-09 08:06 EDT---
This issue is resolved in latest 14.04 build.. closing this bug as fixed
.13.0-112-generic dump.20170309072503090725# crash 
/usr/lib/debug/boot/vmlinux-3.

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 
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"...

KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-112-generic
DUMPFILE: dump.201703090725  [PARTIAL DUMP]
CPUS: 80
DATE: Thu Mar  9 07:23:46 2017
UPTIME: 00:11:05
LOAD AVERAGE: 0.00, 0.04, 0.04
TASKS: 640
NODENAME: ltciofvtr-hab2
RELEASE: 3.13.0-112-generic
VERSION: #159-Ubuntu SMP Fri Mar 3 15:29:14 UTC 2017
MACHINE: ppc64le  (2926 Mhz)
MEMORY: 256 GB
PANIC: "Oops: Kernel access of bad area, sig: 11 [#1]" (check log for details)
PID: 1845
COMMAND: "bash"
TASK: c03f6610  [THREAD_INFO: c03f7820]
CPU: 20
STATE: TASK_RUNNING (PANIC)

crash> bt
PID: 1845   TASK: c03f6610  CPU: 20  COMMAND: "bash"
#0 [c03f782034a0] .crash_kexec at c013875c
#1 [c03f78203690] .die at c0022618
#2 [c03f78203730] .bad_page_fault at c004a580
#3 [c03f782037b0] handle_page_fault at c0009584
Data Access error  [300] exception frame:
R0:  c05962acR1:  c03f78203aa0R2:  c1661000
R3:  0063R4:  c4b85bd0R5:  c4b964c8
R6:  02b0R7:  c18575c0R8:  c0e21000
R9:  0001R10: R11: 00c2
R12: 42422844R13: c7e44600R14: 010039206d68
R15: 1016e048R16: 1013ab40R17: 0100392069a8
R18: 1016ff10R19: 1016e048R20: 100c2f80
R21: R22: 10172008R23: 1016f880
R24: 0004R25: R26: 0001
R27: c14e8370R28: c19a4eb8R29: 0063
R30: c14bda68R31: c14e8730
NIP: c059534cMSR: 90009033OR3: c0009318
CTR: c0595320LR:  c05962acXER: 2000
CCR: 42422822MQ:  DAR: 
DSISR: 4200 Syscall Result: 
#4 [c03f78203aa0] .sysrq_handle_crash at c059534c
[Link Register ]  [c03f78203aa0] .__handle_sysrq at c05962ac
-- MORE --  forward: ,  or j  backward: b or k  quit: q
..

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1607894

Title:
  Unable to analyse vmcore/dump via crash due to bad kernel debug info
  build

Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Trusty:
  Fix Committed

Bug description:
  [ Test case ]
  * trigger a kernel crash dump
  * use crash tool to analyse it
  * ... on ppc64el architecture

  
  == Comment: #0 - NAVEED A. UPPINANGADY SALIH  - 2016-07-01 02:41:07 ==
  ---Problem Description---
  Unable to analyse vmcore/kernel dumpfile generated by 4.4.0-29-generic kernel 
with ddeb kernel debuginfo available in 
http://ddebs.ubuntu.com/pool/main/l/linux/

  http://ddebs.ubuntu.com/pool/main/l/linux/linux-image-4.4.0-29
  -generic-dbgsym_4.4.0-29.48_ppc64el.ddeb

  ---uname output---
   4.4.0-29-generic #48~14.04.1-Ubuntu SMP Wed Jun 29 19:55:03 UTC 2016 ppc64le 
ppc64le ppc64le GNU/Linux

  Machine Type = model   : 8247-22L machine : PowerNV
  8247-22L

  ---Steps to Reproduce---
   # crash /usr/lib/debug/boot/vmlinux-4.4.0-29-generic 
/var/crash/201606300840/dump.201606300840
  crash 7.0.3
  ...
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  crash: invalid kernel virtual address: 61c2555c09c17994  type: "possible"
  WARNING: cannot read cpu_possible_map
  crash: invalid kernel virtual address: 8a0f6ddee20c4116  type: "present"
  WARNING: cannot read cpu_present_map
  crash: invalid kernel virtual

[Kernel-packages] [Bug 1607894] Comment bridged from LTC Bugzilla

2016-08-25 Thread bugproxy 
--- Comment From hbath...@in.ibm.com 2016-08-25 06:05 EDT---
Can we expect upstream crash utility commits 6f1f78e33474 & 098cdab16dfa
included in crash package for the next update?

Thanks
Hari

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
https://bugs.launchpad.net/bugs/1607894

Title:
  Unable to analyse vmcore/dump via crash due to bad kernel debug info
  build

Status in crash package in Ubuntu:
  New

Bug description:
  == Comment: #0 - NAVEED A. UPPINANGADY SALIH  - 2016-07-01 02:41:07 ==
  ---Problem Description---
  Unable to analyse vmcore/kernel dumpfile generated by 4.4.0-29-generic kernel 
with ddeb kernel debuginfo available in 
http://ddebs.ubuntu.com/pool/main/l/linux/

  
http://ddebs.ubuntu.com/pool/main/l/linux/linux-image-4.4.0-29-generic-dbgsym_4.4.0-29.48_ppc64el.ddeb
   
  ---uname output---
   4.4.0-29-generic #48~14.04.1-Ubuntu SMP Wed Jun 29 19:55:03 UTC 2016 ppc64le 
ppc64le ppc64le GNU/Linux
   
  Machine Type = model   : 8247-22L machine : PowerNV 8247-22L 
   
  ---Steps to Reproduce---
   # crash /usr/lib/debug/boot/vmlinux-4.4.0-29-generic 
/var/crash/201606300840/dump.201606300840  
  crash 7.0.3
  ...
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  crash: invalid kernel virtual address: 61c2555c09c17994  type: "possible"
  WARNING: cannot read cpu_possible_map
  crash: invalid kernel virtual address: 8a0f6ddee20c4116  type: "present"
  WARNING: cannot read cpu_present_map
  crash: invalid kernel virtual address: 5a09344e320a1886  type: "online"
  WARNING: cannot read cpu_online_map
  WARNING: cannot read linux_banner string
  crash: /usr/lib/debug/boot/vmlinux-4.4.0-29-generic and 
/var/crash/201606300840/dump.201606300840 do not match!

  Userspace rpm: linux-image-4.4.0-29-generic-
  dbgsym_4.4.0-29.48_ppc64el.ddeb

  == Comment: #5 - Naresh Bannoth - 2016-07-27 04:12:09 ==

  The Latest kernel I am having is as follows

  root@ltcalpine-lp6:~# uname -a
  Linux ltcalpine-lp6 4.4.0-31-generic #50~14.04.1-Ubuntu SMP Wed Jul 13 
01:03:56 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
  root@ltcalpine-lp6:~# 

  >>> the issue same as posted originally.

  ...
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  crash: invalid kernel virtual address: 61c2555c09c17994  type: "possible"
  WARNING: cannot read cpu_possible_map
  crash: invalid kernel virtual address: 8a0f6ddee20c4116  type: "present"
  WARNING: cannot read cpu_present_map
  crash: invalid kernel virtual address: 5a09344e320a1886  type: "online"
  WARNING: cannot read cpu_online_map
  WARNING: cannot read linux_banner string
  crash: /usr/lib/debug/boot/vmlinux-4.4.0-31-generic and 
/var/crash/201607270248/dump.201607270248 do not match!

  
  == Comment: #6 - Hari Krishna Bathini - 2016-07-28 11:49:31 ==
  The kernel is compiled with gcc version 4.8.4 while the vmlinux pulled
  from http://ddebs.ubuntu.com/pool/main/l/linux/ is compiled with gcc
  version 5.3.1 which is the source of the issue.

   Resolved this by pulling the kernel debug symbols package from:

deb http://ddebs.ubuntu.com/ -updates  main

  which indeed has the vmlinux compiled with gcc version 4.8.4.
  But I got this error:

crash: invalid structure member offset: module_num_symtab
   FILE: kernel.c  LINE: 3049  FUNCTION: module_init()

  after the update owning to couple of missing patches listed below:

  
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 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)

  Applying the above patches on top of crash tool version 7.0.3-3ubuntu4.4,
  was able to analyze the dump. The patches apply cleanly..

  Thanks
  Hari

  
  == Comment: #8 - Naresh Bannoth - 2016-07-29 06:59:23 ==
  Verified with 4.4.0-31-generic kernel.
  on Applying the patches mentioned in the #C 6,