@breno re: point release meaning vs updates
Please note point releases refer to installation media only, which is a
consistent snapshot of cloud images, container images, server ISO, d-i,
etc. Built from xenial-updates & xenial-security pockets as published at
the time of the respin. xenial-updates/-security themselves are a moving
It's impossible to ship something in "16.04.2" today, as there is no
package archive that refers to "16.04.2". One simply continuously ships
updates in xenial-updates.
Thus the point of point-releases installation media, is to have
installers available with a newer kernel which hopefully supports more
hardware, and newer packages making post-install security/updates
upgrades quicker & smaller, as one does not need to catch up 2 years+ of
updates, just a few weeks of updates.
This issue does not appear to impact the installation media /
installation success, therefore it is not critical to ship in
installation media as respun for a point release. Hence it is targetted
to ship simply as any other SRU in xenial-updates.
Once the solution to this bug is found that is.
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to crash in Ubuntu.
[Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
Status in The Ubuntu-power-systems project:
Status in crash package in Ubuntu:
Status in crash source package in Xenial:
Status in crash source package in Artful:
Status in crash source package in Bionic:
Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel
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
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 ==========
.0-26-generic vmcore.2018011502271150227# crash
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 =>
== 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:
Author: Dave Anderson <ander...@redhat.com>
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.
Similar thing holds true for makedumpfile tool..
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~kernel-packages
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp