[Group.of.nepali.translators] [Bug 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash
** Tags removed: triage-r ** Tags added: triage-g ** Changed in: ubuntu-power-systems Status: Fix Committed => Fix Released -- 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/1655625 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash Status in The Ubuntu-power-systems project: Fix Released Status in crash package in Ubuntu: Fix Released Status in makedumpfile package in Ubuntu: Fix Released Status in crash source package in Xenial: Fix Released Status in makedumpfile source package in Xenial: Fix Released Bug description: [SRU justification] This fix is required to make the crash tool usable. It does also improve makedumpfile filtering of pages. [Impact] Kernel crashes cannot be analysed with the crash tool. makedumpfile incorrectly filter pages. [Fix] Cherry-pick upstream commits fixing those issues. [Test Case] Running crash tool on a kernel crash file will display something like : # crash -s usr/lib/debug/boot/vmlinux-4.8.0-34-generic crash: read error: kernel virtual address: 81e29ff0 type: "pv_init_ops" crash: this kernel may be configured with CONFIG_STRICT_DEVMEM, which renders /dev/mem unusable as a live memory source. crash: trying /proc/kcore as an alternative to /dev/mem crash: seek error: kernel virtual address: 81e29ff0 type: "pv_init_ops" crash: seek error: kernel virtual address: 82166130 type: "shadow_timekeeper xtime_sec" crash: seek error: kernel virtual address: 81e0d304 type: "init_uts_ns" crash: usr/lib/debug/boot/vmlinux-4.8.0-34-generic and /var/crash/201701191308/dump.201701191308 do not match! With the fix, the crash command will work as expected Running the crash tool on a vmcore file produced by makedumpfile may return : crash: page excluded: kernel virtual address: <> type: "fill_task_struct" [Regression] None expected as those modifications are part of the Zesty and upstream version. The makedumpfile patches are in Yakkety and Zesty 1.6.0 & after [Original description of the problem] 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~1
[Group.of.nepali.translators] [Bug 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash
** Changed in: makedumpfile (Ubuntu) Assignee: Nish Aravamudan (nacc) => (unassigned) ** Changed in: makedumpfile (Ubuntu) Status: Confirmed => Fix Released -- 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/1655625 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash Status in The Ubuntu-power-systems project: Fix Committed Status in crash package in Ubuntu: Fix Released Status in makedumpfile package in Ubuntu: Fix Released Status in crash source package in Xenial: Fix Released Status in makedumpfile source package in Xenial: Fix Released Bug description: [SRU justification] This fix is required to make the crash tool usable. It does also improve makedumpfile filtering of pages. [Impact] Kernel crashes cannot be analysed with the crash tool. makedumpfile incorrectly filter pages. [Fix] Cherry-pick upstream commits fixing those issues. [Test Case] Running crash tool on a kernel crash file will display something like : # crash -s usr/lib/debug/boot/vmlinux-4.8.0-34-generic crash: read error: kernel virtual address: 81e29ff0 type: "pv_init_ops" crash: this kernel may be configured with CONFIG_STRICT_DEVMEM, which renders /dev/mem unusable as a live memory source. crash: trying /proc/kcore as an alternative to /dev/mem crash: seek error: kernel virtual address: 81e29ff0 type: "pv_init_ops" crash: seek error: kernel virtual address: 82166130 type: "shadow_timekeeper xtime_sec" crash: seek error: kernel virtual address: 81e0d304 type: "init_uts_ns" crash: usr/lib/debug/boot/vmlinux-4.8.0-34-generic and /var/crash/201701191308/dump.201701191308 do not match! With the fix, the crash command will work as expected Running the crash tool on a vmcore file produced by makedumpfile may return : crash: page excluded: kernel virtual address: <> type: "fill_task_struct" [Regression] None expected as those modifications are part of the Zesty and upstream version. The makedumpfile patches are in Yakkety and Zesty 1.6.0 & after [Original description of the problem] 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 -
[Group.of.nepali.translators] [Bug 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash
crash is in 7.1.7 whichi is in >= Zesty so dev is good ** Changed in: crash (Ubuntu) Status: Confirmed => Fix Released ** Changed in: crash (Ubuntu) Assignee: Nish Aravamudan (nacc) => (unassigned) -- 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/1655625 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash Status in The Ubuntu-power-systems project: Fix Committed Status in crash package in Ubuntu: Fix Released Status in makedumpfile package in Ubuntu: Confirmed Status in crash source package in Xenial: Fix Released Status in makedumpfile source package in Xenial: Fix Released Bug description: [SRU justification] This fix is required to make the crash tool usable. It does also improve makedumpfile filtering of pages. [Impact] Kernel crashes cannot be analysed with the crash tool. makedumpfile incorrectly filter pages. [Fix] Cherry-pick upstream commits fixing those issues. [Test Case] Running crash tool on a kernel crash file will display something like : # crash -s usr/lib/debug/boot/vmlinux-4.8.0-34-generic crash: read error: kernel virtual address: 81e29ff0 type: "pv_init_ops" crash: this kernel may be configured with CONFIG_STRICT_DEVMEM, which renders /dev/mem unusable as a live memory source. crash: trying /proc/kcore as an alternative to /dev/mem crash: seek error: kernel virtual address: 81e29ff0 type: "pv_init_ops" crash: seek error: kernel virtual address: 82166130 type: "shadow_timekeeper xtime_sec" crash: seek error: kernel virtual address: 81e0d304 type: "init_uts_ns" crash: usr/lib/debug/boot/vmlinux-4.8.0-34-generic and /var/crash/201701191308/dump.201701191308 do not match! With the fix, the crash command will work as expected Running the crash tool on a vmcore file produced by makedumpfile may return : crash: page excluded: kernel virtual address: <> type: "fill_task_struct" [Regression] None expected as those modifications are part of the Zesty and upstream version. The makedumpfile patches are in Yakkety and Zesty 1.6.0 & after [Original description of the problem] 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 r
[Group.of.nepali.translators] [Bug 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash
** Changed in: makedumpfile (Ubuntu) Assignee: Louis Bouchard (louis) => Nish Aravamudan (nacc) ** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: crash (Ubuntu) Assignee: (unassigned) => Nish Aravamudan (nacc) -- 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/1655625 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash Status in The Ubuntu-power-systems project: New Status in crash package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Confirmed Status in crash source package in Xenial: Fix Released Status in makedumpfile source package in Xenial: Fix Released Bug description: [SRU justification] This fix is required to make the crash tool usable. It does also improve makedumpfile filtering of pages. [Impact] Kernel crashes cannot be analysed with the crash tool. makedumpfile incorrectly filter pages. [Fix] Cherry-pick upstream commits fixing those issues. [Test Case] Running crash tool on a kernel crash file will display something like : # crash -s usr/lib/debug/boot/vmlinux-4.8.0-34-generic crash: read error: kernel virtual address: 81e29ff0 type: "pv_init_ops" crash: this kernel may be configured with CONFIG_STRICT_DEVMEM, which renders /dev/mem unusable as a live memory source. crash: trying /proc/kcore as an alternative to /dev/mem crash: seek error: kernel virtual address: 81e29ff0 type: "pv_init_ops" crash: seek error: kernel virtual address: 82166130 type: "shadow_timekeeper xtime_sec" crash: seek error: kernel virtual address: 81e0d304 type: "init_uts_ns" crash: usr/lib/debug/boot/vmlinux-4.8.0-34-generic and /var/crash/201701191308/dump.201701191308 do not match! With the fix, the crash command will work as expected Running the crash tool on a vmcore file produced by makedumpfile may return : crash: page excluded: kernel virtual address: <> type: "fill_task_struct" [Regression] None expected as those modifications are part of the Zesty and upstream version. The makedumpfile patches are in Yakkety and Zesty 1.6.0 & after [Original description of the problem] 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_
[Group.of.nepali.translators] [Bug 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash
This bug was fixed in the package makedumpfile - 1:1.5.9-5ubuntu0.4 --- makedumpfile (1:1.5.9-5ubuntu0.4) xenial; urgency=medium * d/p/0006-PATCH-Support-newer-kernels.patch : Support kernel versions up to 4.8 (LP: #1557751) * Turn hardcoded timeo and retrans NFS options into parameters that can be modified in /etc/default/kdump-tools. Also use the NFS defaults (timeo=600, retrans=3) for these parameters. Make those values visible in the 'show' command if NFS is configured (LP: #1641235) * Complete support for kernel versions 4.8 and later : d/p/0007-PATCH-Looking-for-page.compound_order-compound_dtor-.patch, d/p/0008-PATCH-Skip-examining-compound-tail-pages.patch (LP: #1655625) -- Louis Bouchard Wed, 11 Jan 2017 11:33:42 +0100 ** Changed in: makedumpfile (Ubuntu Xenial) Status: Fix Committed => Fix Released -- 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/1655625 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash Status in crash package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Confirmed Status in crash source package in Xenial: Fix Released Status in makedumpfile source package in Xenial: Fix Released Bug description: [SRU justification] This fix is required to make the crash tool usable. It does also improve makedumpfile filtering of pages. [Impact] Kernel crashes cannot be analysed with the crash tool. makedumpfile incorrectly filter pages. [Fix] Cherry-pick upstream commits fixing those issues. [Test Case] Running crash tool on a kernel crash file will display something like : # crash -s usr/lib/debug/boot/vmlinux-4.8.0-34-generic crash: read error: kernel virtual address: 81e29ff0 type: "pv_init_ops" crash: this kernel may be configured with CONFIG_STRICT_DEVMEM, which renders /dev/mem unusable as a live memory source. crash: trying /proc/kcore as an alternative to /dev/mem crash: seek error: kernel virtual address: 81e29ff0 type: "pv_init_ops" crash: seek error: kernel virtual address: 82166130 type: "shadow_timekeeper xtime_sec" crash: seek error: kernel virtual address: 81e0d304 type: "init_uts_ns" crash: usr/lib/debug/boot/vmlinux-4.8.0-34-generic and /var/crash/201701191308/dump.201701191308 do not match! With the fix, the crash command will work as expected Running the crash tool on a vmcore file produced by makedumpfile may return : crash: page excluded: kernel virtual address: <> type: "fill_task_struct" [Regression] None expected as those modifications are part of the Zesty and upstream version. The makedumpfile patches are in Yakkety and Zesty 1.6.0 & after [Original description of the problem] 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 D
[Group.of.nepali.translators] [Bug 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash
This bug was fixed in the package crash - 7.1.4-1ubuntu4.1 --- crash (7.1.4-1ubuntu4.1) xenial; urgency=medium * Cherry-pick upstream commit to complete support for 4.5+ kernels : d/p/0003-Fix-for-the-replacements-made-to-the-kernel-s-cpu_po.patch, d/p/0004-With-the-introduction-of-radix-MMU-in-Power-ISA-3.0-.patch, d/p/0005-Fix-for-Linux-commit-0139aa7b7fa12ceef095d99dc36606a.patch, d/p/0006-Fix-for-Linux-commit-edf14cdbf9a0e5ab52698ca66d07a76.patch, d/p/0007-Fix-to-recognize-and-support-x86_64-Linux-4.8-rc1-an.patch, d/p/0008-Fix-for-a-possible-segmentation-violation-when-analy.patch, d/p/0009-Fix-for-support-of-Linux-4.7-and-later-x86_64-ELF-kd.patch, d/p/0010-Linux-3.15-and-later-kernels-configured-with-CONFIG_.patch These commits are included in version 7.1.7 of crash and are required in order to correctly open 4.5 kernels and newer (LP: #1655625). -- Louis Bouchard Fri, 20 Jan 2017 17:53:30 +0100 ** Changed in: crash (Ubuntu Xenial) Status: Fix Committed => Fix Released -- 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/1655625 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash Status in crash package in Ubuntu: Confirmed Status in makedumpfile package in Ubuntu: Confirmed Status in crash source package in Xenial: Fix Released Status in makedumpfile source package in Xenial: Confirmed Bug description: [SRU justification] This fix is required to make the crash tool usable. It does also improve makedumpfile filtering of pages. [Impact] Kernel crashes cannot be analysed with the crash tool. [Fix] Cherry-pick upstream commits fixing those issues. [Test Case] Running crash tool on a kernel crash file will display something like : # crash -s usr/lib/debug/boot/vmlinux-4.8.0-34-generic crash: read error: kernel virtual address: 81e29ff0 type: "pv_init_ops" crash: this kernel may be configured with CONFIG_STRICT_DEVMEM, which renders /dev/mem unusable as a live memory source. crash: trying /proc/kcore as an alternative to /dev/mem crash: seek error: kernel virtual address: 81e29ff0 type: "pv_init_ops" crash: seek error: kernel virtual address: 82166130 type: "shadow_timekeeper xtime_sec" crash: seek error: kernel virtual address: 81e0d304 type: "init_uts_ns" crash: usr/lib/debug/boot/vmlinux-4.8.0-34-generic and /var/crash/201701191308/dump.201701191308 do not match! With the fix, the crash command will work as expected [Regression] None expected as those modifications are part of the Zesty and upstream version. [Original description of the problem] 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
[Group.of.nepali.translators] [Bug 1655625] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash
** Also affects: makedumpfile (Ubuntu) Importance: Undecided Status: New ** Also affects: crash (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Xenial) Importance: Undecided Status: New -- 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/1655625 Title: ISST-LTE:pVM:roselp4:ubuntu 16.04.2: vmcore cannot be analysed by crash Status in crash package in Ubuntu: New Status in makedumpfile package in Ubuntu: New Status in crash source package in Xenial: New Status in makedumpfile source package in Xenial: New Bug description: 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
