group.of.nepali.translators team mailing list archive

[Thadeu Lima de Souza Cascardo <1746088@xxxxxxxxxxxxxxxxxx>]

I have just marked this as Invalid for Bionic, as the crash version on
Bionic is capable of analyzing 4.15 kernels (and older 4.13 kernels,
even though no one should be using such kernels on Bionic).

If there are any bugs about specific functionalities on that Bionic
crash version, please report it as a different bug. See, for example,
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1765660.

Cascardo.

** Changed in: crash (Ubuntu Bionic)
       Status: In Progress => Invalid

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1746088

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Fix Released
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Invalid

Bug description:
  [Impact]
  It won't be possible to analyze dumps produced by newer kernels (hwe on xenial, for example).

  [Test Case]
  Tested that this version of crash can analyze both GA (4.4) and hwe (4.15) kernels.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older kernels. The smoke test helps a little, but more testing may be desirable.


  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel (Ubuntu 16.04.4)

  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8001-22C

  ---Steps to Reproduce---
   This bug follow up bug of https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows

  Once you generate the kdump
  use crash to analyze the vmcore and we get this error

  ================console logs ==========

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash /usr/lib/debug/boot/vmlinux-4.13.

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

  please wait... (gathering module symbol data)
  WARNING: cannot access vmalloc'd module memory

  crash: invalid structure member offset: thread_info_task
         FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

    100833e0: (undetermined)
    1017d220: OFFSET_verify+80
    1011552c: task_init+5084
    1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

    commit c8178eca9c74f81a7f803a58d339635cc152e8d9
    Author: Dave Anderson <anderson@xxxxxxxxxx>
    Date:   Thu Nov 9 11:39:05 2017 -0500

      Update for support of Linux 4.14 and later PPC64 kernels where the
      hash page table geometry accomodates a larger virtual address range.
      Without the patch, the virtual-to-physical translation of user space
      virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
      invalid translation or otherwise fail.
      (hbathini@xxxxxxxxxxxxxxxxxx)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746088/+subscriptions