My Oracle Support Banner

Oracle VM 3: Analyzing UEK5 Crashdump Fails with "WARNING: cannot read linux_banner string" (Doc ID 2481442.1)

Last updated on DECEMBER 06, 2020

Applies to:

Oracle VM - Version 3.4.1 and later
Linux x86-64

Symptoms

The analysis of the vmcore using latest crash utility (e.g. 7.2.3 version on OL7) fails similar to below:

$ crash uek5.vmcore usr/lib/debug/lib/modules/4.14.35-1818.4.7.el7uek.x86_64/vmlinux

crash 7.2.3

...

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 "x86_64-unknown-linux-gnu"...

WARNING: cannot read linux_banner string
crash: usr/lib/debug/lib/modules/4.14.35-1818.4.7.el7uek.x86_64/vmlinux and uek5.vmcore do not match!

Usage:

crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS] (dumpfile form)
crash [OPTION]... [NAMELIST] (live system form)

Enter "crash -h" for details.

 

For same VM booting with UEK4 (or older kernel) , the vmcore file can be read by crash utility without problems.

The problem ONLY occurs for vmcore file collected on Oracle VM server via 'xm dump-core'. If the vmcore is generated by Kdump on Linux server, there is no such issue.

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.