Re: Problems with 32bit Fedora 7

From: Paul H. Hargrove (hargrove_at_hpcrd_dot_lbl_dot_gov)
Date: Wed Aug 29 2007 - 18:16:42 PDT

  • Next message: John Hodrien: "Re: Problems with 32bit Fedora 7"
    Note one minor correction below
    Paul H. Hargrove wrote:
    > John Hodrien wrote:
    >> I can't seem to get blcr working with Fedora 7 32bit.
    >> It seems to build and install happily under x86_64 but on a 32 bit 
    >> machine
    >> I've built the RPM with --target i686 but when loading the kernel 
    >> modules I
    >> get:
    >> vmadump: (from bproc-4.0.0pre8) Erik Hendriks <>
    >> vmadump: Modified for blcr 0.6.0_b7 <>
    >> blcr: Berkeley Lab Checkpoint/Restart (BLCR) module version 0.6.0_b7.
    >> blcr: Supports BLCR kernel interface version 0.6.0.
    >> blcr:
    >> Running kernel does not match the used to build blcr.o
    >> I've tried it with several different kernels (offical F7 releases) 
    >> with no
    >> joy.
    >> Am I missing something obvious?
    >> jh
    > John,
    >   I don't know exactly what the source of your problem is, but you are 
    > not missing anything obvious as far as I can tell.  However, I do have 
    > a guess.
    >   To access certain kernel symbols that are not exported to modules, 
    > BLCR's configure process locates the symbols in the and 
    > encodes the addresses in the BLCR kernel modules.  Such a practice is 
    > potentially error prone and could be dangerous if we tried to execute 
    > code at arbitrary addresses in the kernel.  For that reason, we 
    > extract from some addresses that can be compared against 
    > exported symbols and/or entries in the syscall table, and these are 
    > checked at module-load time.  The error message you see means that 
    > checks comparing addresses in against 2 exported symbols 
    > have failed.  This normally means that wrong file was used 
    > to build BLCR.
    >   Based on a previously reported issue, I suspect your problem may be 
    > related to having a "relocatable" kernel.  If you would, please, 
    > provide the output of the following three commands:
    > $ grep RELOCATE /boot/config-`uname -r`
    The line above should say RELOCATABLE rather than RELOCATE
    > $ grep -e register_chrdev -e register_blkdev /boot/`uname -r`
    > $ grep -e register_chrdev -e register_blkdev /proc/kallsyms
    > These are based on file locations on an FC6 system of mine, and might 
    > need to be changes slightly for F7.
    > Based on the output of those commands, I should be able to confirm if 
    > the problem is a relocatable kernel, and hopefully formulate a fix.
    > -Paul

  • Next message: John Hodrien: "Re: Problems with 32bit Fedora 7"