[Kernel-packages] [Bug 1607894] Re: Unable to analyse vmcore/dump via crash due to bad kernel debug info build
https://launchpad.net/ubuntu/trusty/+queue?queue_state=1&queue_text=crash In trusty unapproved queue. -- 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: In Progress 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 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 ment
[Kernel-packages] [Bug 1607894] Re: Unable to analyse vmcore/dump via crash due to bad kernel debug info build
Hello bugproxy, or anyone else affected, Accepted crash into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/crash/7.0.3-3ubuntu4.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: crash (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed -- 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 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 initial
[Kernel-packages] [Bug 1607894] Re: Unable to analyse vmcore/dump via crash due to bad kernel debug info build
Hi Canonical, any update on this bug? It is an important fix for 14.04 IMO -- 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, it is working fine. I took the Compiled Binary attached in the BUG and able to analyse the Dumpfile without any issues. Thanks Naresh == Comment: #9 - Hari Kr
[Kernel-packages] [Bug 1607894] Re: Unable to analyse vmcore/dump via crash due to bad kernel debug info build
** Changed in: crash (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => Robert Hooker (sarvatt) -- 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, it is working fine. I took the Compiled Binary attached in the BUG and able to analyse the Dumpfile without any issues. Thanks N
[Kernel-packages] [Bug 1607894] Re: Unable to analyse vmcore/dump via crash due to bad kernel debug info build
crash (7.0.3-3ubuntu4.5) trusty; urgency=medium * Fix for: Unable to analyse vmcore/dump via crash due to bad kernel debug info build (LP: #1607894). -- Robert Hooker Thu, 01 Dec 2016 12:03:17 -0500 ** Patch added: "debdiff containing the fix" https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1607894/+attachment/4788691/+files/crash_7.0.3-3ubuntu4.5.debdiff -- 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:
[Kernel-packages] [Bug 1607894] Re: Unable to analyse vmcore/dump via crash due to bad kernel debug info build
The attachment "debdiff containing the fix" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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 c
[Kernel-packages] [Bug 1607894] Re: Unable to analyse vmcore/dump via crash due to bad kernel debug info build
** Description changed: + [ 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 - + 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 - + 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 /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:~# + 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: + Resolved this by pulling the kernel debug symbols package from: - deb http://ddebs.ubuntu.com/ -updates main + 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() + 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 - 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: - 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. - 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) - 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 098cdab16dfa6a85e9da
[Kernel-packages] [Bug 1607894] Re: Unable to analyse vmcore/dump via crash due to bad kernel debug info build
** Changed in: crash (Ubuntu) Importance: Undecided => High -- 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 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, it is working fine.
[Kernel-packages] [Bug 1607894] Re: Unable to analyse vmcore/dump via crash due to bad kernel debug info build
** Package changed: linux (Ubuntu) => crash (Ubuntu) -- 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, it is working fine. I took the Compiled Binary attached in the BUG and able to analyse the Dumpfile without any issues. Thanks Naresh == Comment: #9 - Hari Krishna Bathini - 2016-0
[Kernel-packages] [Bug 1607894] Re: Unable to analyse vmcore/dump via crash due to bad kernel debug info build
I can confirm that this version fixes the following issue : crash: invalid structure member offset: module_num_symtab FILE: kernel.c LINE: 3049 FUNCTION: module_init() using the latest linux-image-lts-xenial kernel ** Tags removed: verification-needed ** Tags added: verification-done -- 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 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
[Kernel-packages] [Bug 1607894] Re: Unable to analyse vmcore/dump via crash due to bad kernel debug info build
This bug was fixed in the package crash - 7.0.3-3ubuntu4.5 --- crash (7.0.3-3ubuntu4.5) trusty; urgency=medium * Fix for: Unable to analyse vmcore/dump via crash due to bad kernel debug info build (LP: #1607894). -- Robert Hooker Thu, 01 Dec 2016 12:03:17 -0500 ** Changed in: crash (Ubuntu Trusty) Status: Fix Committed => Fix Released -- 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 Released 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 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 ab
