On Mon, 30 Jan 2012, Stefan Krüger wrote:
> Hi,
>
> ...
>
> # kldload crypto
> cryptosoft0: <software crypto> on motherboard
> spin_lock: 0xffffffff830601c0, indefinite wait (1 secs)!
> ... bunch of indefinite waits
> Trace beginning at frame 0xffffffe0a7443be0
> spin_lock_contested() at spin_lock_contested+0xd4 0xffffffff8032e989
> spin_lock_contested() at spin_lock_contested+0xd4 0xffffffff8032e989
> lockmgr() at lockmgr+0x8e 0xffffffff80309317
> crypto_ret_proc() at crypto_ret_proc+0x22 0xffffffff8303d43b
> ... some more indefinite waits
> spin_lock: 0xffffffff830601c0, indefinite wait (59 secs)!
> panic: spin_lock: 0xffffffff830601c0, indefinite wait!
>
> cpuid = 1
> Trace beginning at frame 0xffffffe0a7443b60
> panic() at panic+0x1fb 0xffffffff803186ad
> panic() at panic+0x1fb 0xffffffff803186ad
> spin_lock_contested() at spin_lock_contested+0x104 0xffffffff8032e9b9
> lockmgr() at lockmgr+0x8e 0xffffffff80309317
> crypto_ret_proc() at crypto_ret_proc+0x22 0xffffffff8303d43b
> Debugger("panic")
>
> And I'm pretty stuck on this one :(
>
> More info and/or kernel crashdump available on request
Ok,
I guess I'm to blame here. I have a custom KERNCONF (lot's of debugging stuff
turned on) and I was rebuilding the modules like this:
cd /usr/src/sys/crypto && make && make install
Which doesn't seem to use the same compiler flags/options that were used for
the kernel...
So, sorry for the noise :(
