Jun Kuriyama <[EMAIL PROTECTED]> writes:
> But I used linux.ko which sync'ed with kernel itself (both were built
> with same config). Is MUTEX_PROFILING not passed to kernel module
> building?
Modules are compiled without options.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
_
On Thu, 10 Jul 2003, Dag-Erling [iso-8859-1] Smørgrav wrote:
> Jun Kuriyama <[EMAIL PROTECTED]> writes:
> > I'm trying to use MUTEX_PROFILING, but paniced in linux ldconfig.
> > Any clues?
>
> is COMPAT_LINUX compiled into the kernel? You can't use modules with
> MUTEX_PROFILING; it changes the s
At Thu, 10 Jul 2003 08:32:28 +0200,
Dag-Erling Smørgrav wrote:
> > I'm trying to use MUTEX_PROFILING, but paniced in linux ldconfig.
> > Any clues?
>
> is COMPAT_LINUX compiled into the kernel? You can't use modules with
> MUTEX_PROFILING; it changes the size and layout of struct mtx, and
> since
Jun Kuriyama <[EMAIL PROTECTED]> writes:
> I'm trying to use MUTEX_PROFILING, but paniced in linux ldconfig.
> Any clues?
is COMPAT_LINUX compiled into the kernel? You can't use modules with
MUTEX_PROFILING; it changes the size and layout of struct mtx, and
since modules aren't built with the sam
At Fri, 27 Jun 2003 09:37:40 + (UTC),
kuriyama wrote:
> (kgdb) l *linux_brk+0x1a
> 0xc19d24ca is in linux_brk
> (/.a/black/host/disk/arena/home/kuriyama/ncvs/src/sys/compat/linux/linux_misc.c:217).
> 212
> 213 #ifdef DEBUG
> 214 if (ldebug(brk))
> 215 p
