Re: kern/52252: uvm_km_check_empty panic when loading any module

[Jaromír Doleček <jaromir.dolecek%gmail.com@localhost>]

Hello,

usually two things to check for wierd panic cases like this.

1. make sure to rebuild your complete kernel, to make sure no obsolete .o were used - make clean && make depend && make

2. make sure that DEBUG/LOCKDEBUG options between your kernel and the modules match - since DEBUG and LOCKDEBUG change size of critical kernel structures, kernel will trample over random structure contents since what module allocates is less than the kernel uses.

Looking on your config, it seems you do have the DEBUG and LOCKDEBUG options there, so I think that is your problem.

Jaromir

2017-05-23 22:29 GMT+02:00 Anthony Mallet <tho%netbsd.org@localhost>:

>  3. Can you reproduce this problem using a GENERIC kernel on the real
>      machine?

It seems to be OK with GENERIC. At least I can load modules with no
issue on one of the machine (did not try the other one yet). So that's
a strong hint.

I had already compared my config with GENERIC without noticing
anything suspect, but maybe you'll spot something.


# Diagnostic/debugging support options
makeoptions     COPTS="-O2 -fno-omit-frame-pointer"
#options        DIAGNOSTIC      # expensive kernel consistency checks
                                # XXX to be commented out on release branch
options         DEBUG           # expensive debugging checks/support
options         LOCKDEBUG       # expensive locking checks/support
#options        KMEMSTATS       # kernel memory statistics (vmstat -m)
makeoptions     DEBUG="-g"      # compile full symbol table