<< | Thread Index | >> ]    [ << | Date Index | >> ]

To: cipe-l,AT,inka,DOT,de
Subject: Re: CIPE fails in RH FC3 kernels (2.6.9 & 2.6.10)
From: Karl Kleinpaste <karl,AT,charcoal,DOT,com>
Date: Mon, 07 Mar 2005 00:45:21 -0500
In-reply-to: <vxk4qfttyo2.fsf@mesquite.charcoal.com> (Karl Kleinpaste'smessage of "Wed, 02 Mar 2005 18:29:01 -0500")
References: <vxk8y55u0rk.fsf@mesquite.charcoal.com><1109805810.31991.137.camel@les-home.futuresource.com><vxk4qfttyo2.fsf@mesquite.charcoal.com>

I have rebuilt the RH kernel .src.rpm successfully without REGPARM.
(Life lesson: don't leave spurious $ARCH variables lying around, which
are otherwise useful for $PATH-specific settings.)

  --- kernel-2.6.10-i586.config.~1~     2005-02-09 23:02:21.000000000 -0500
  +++ kernel-2.6.10-i586.config 2005-03-03 10:24:19.000000000 -0500
  @@ -2503 +2503 @@
  -CONFIG_REGPARM=y
  +# CONFIG_REGPARM is not set

The resulting kernel is installed and running.  I built CIPE 1.6.0
against that kernel with --disable-debug --disable-pkcipe
--enable-bug-compatible.  It identifies itself in config.h as being
REGPARM-free:

  /* Use register parameter passing (EXPERIMENTAL) */
  /* #undef USE_REGPARM */

But the resulting cipcb.ko still chokes the new kernel with an oops.
Others seem to have FC3 + REGPARM disabled + CIPE 1.6.0 running
without incident.  Am I missing some other bit of magic?


<< | Thread Index | >> ]    [ << | Date Index | >> ]