Qemu crash...

Bakul Shah bakul at bitblocks.com
Thu Nov 23 13:23:02 PST 2006

> The problem is that kldloading a module if it's already in the kernel
> can cause a panic.  Also if the module becomes stale with respect to
> the running kernel, this approach can cause a lot of confusion.

I thought the following would do the trick:

    kldstat -m aio >/devnull 2>&1 || kldload aio

> Something I'd like to see is
> a) Fixing the kldload "double load" problems

See above.  Works in -current at least.

> b) That optional kernel subsystems register themselves with a sysctl,
> so that userland can easily determine whether a feature is present in
> the running kernel and take appropriate action (warn user, demand
> load, etc) if not.  compat[45]x support is another such case; there's
> no way for a port to tell whether the kernel supports running such
> binaries, and if not then the user will just get an error when they
> try to run it.

Isn't kldstat -v & kldstat -m good enough?

More information about the freebsd-ports mailing list