Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 601203 - Crash 5.0.4 emits cannot read cpu_possible... warnings and terminates.
Crash 5.0.4 emits cannot read cpu_possible... warnings and terminates.
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: crash (Show other bugs)
5.0
All Linux
low Severity medium
: rc
: ---
Assigned To: Dave Anderson
Red Hat Kernel QE team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-06-07 09:09 EDT by Jerry Levy
Modified: 2010-06-07 09:28 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-06-07 09:22:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
-d7 output from crash startup (12.17 KB, text/plain)
2010-06-07 09:09 EDT, Jerry Levy
no flags Details

  None (edit)
Description Jerry Levy 2010-06-07 09:09:48 EDT
Created attachment 421816 [details]
-d7 output from crash startup

Description of problem: At startup, crash emits messages (below, under Actual Results) and terminates.

Version-Release number of selected component (if applicable): crash 5.0.4, also crash-4.1.2-4.el5

How reproducible: Appears to repro every time on this host:
# uname -a
Linux linux21775.corp.emc.com 2.6.18-128.el5 #1 SMP Wed Dec 17 11:41:38 EST 2008 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.5 (Tikanga)

Steps to Reproduce:
1. Build the following:
#include <stdio.h>
#include <stdlib.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>
#include <signal.h>

int main (int argc, char *argv[]) {
        int fd;
        char *bogus = 0;

        fd = open(bogus,O_RDONLY);
        raise(11);
        printf("Opened %d\n", fd);
        close(fd);
}

2. Code produces a core file. 

3.Run "crash /usr/lib/debug/lib/modules/2.6.18-128.el5/vmlinux core.5294"
  
Actual results:
This GDB was configured as "x86_64-unknown-linux-gnu"...

crash: read error: kernel virtual address: ffffffff80431260  type: "possible"
WARNING: cannot read cpu_possible_map
crash: read error: kernel virtual address: ffffffff803d9520  type: "present"
WARNING: cannot read cpu_present_map
crash: read error: kernel virtual address: ffffffff803d4260  type: "online"
WARNING: cannot read cpu_online_map
crash: read error: kernel virtual address: ffffffff803db200  type: "xtime"

Expected results:
Crash session to debug code.

Additional info: Does not appear to occur on a core generated from a different host.
Comment 1 Dave Anderson 2010-06-07 09:21:30 EDT
> Expected results:
> Crash session to debug code.

The crash utility is for use with dumpfiles generated from kernel crashes
(kdump, netdump, diskdump, KVM dump etc.), and not for core files from
user-space programs .

> Additional info: Does not appear to occur on a core generated from a different
> host.

That makes no sense.
Comment 2 Jerry Levy 2010-06-07 09:28:16 EDT
True enough. Thanks... the core from the other host was indeed a kernel dump.

Note You need to log in before you can comment on or make changes to this bug.