Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: 8.99.1: exiting unheld spin mutex



Hi,

I'm sorry for late reply.

On 2017/06/07 3:08, Christos Zoulas wrote:
> In article <20170606173220.6e53czlyei7hep4h@danbala>,
> Thomas Klausner  <tk%giga.or.at@localhost> wrote:
>> Hi!
>>
>> I just upgraded from 7.99.75 to 8.99.1. The kernel didn't really come
>> up (I didn't watch the console at first). It paniced with a mutex
>> issue. When it came up again with a 8.99.1 kernel, it paniced while
>> writing the kernel core file to disk, with something like:
>>
>> SPL NOT LOWERED ON SYSCALL EXIT
>>
>> When it came up again, it paniced during startup, a bit later, with a
>> backtrace this time:
>>
>> Mutex error: mutex_vector_exit,720: exiting unheld spin mutex
>>
>> lock address : 0xfffffe882ef8d0b8
>> current cpu  :                  6
>> current lwp  : 0xfffffe881c147a40
>> owner field  : 0x0000000000000600 wait/spin: 0/1
>>
>> panic: lock error: Mutex: ... (same thing)
>> cpu6: begin traceback...
>> vpanic9)
>> snprintf()
>> lockdebug_abort()
>> mutex_vector_exit()
>> crypto_getfeat()
>> cryptof_ioctl()
>> sys_ioctl()
>> syscall() at netbsd:syscall+0x1d8
>> -- syscall (number 54) ---
>> 72c3f3d18baa:
>> cpu6: End traceback...
>>
>> That's with a DIAGNOSTIC kernel.
>>
> 
> I fixed it.

Thank you for your fix!


Thanks,

-- 
//////////////////////////////////////////////////////////////////////
Internet Initiative Japan Inc.

Device Engineering Section,
IoT Platform Development Department,
Network Division,
Technology Unit

Kengo NAKAHARA <k-nakahara%iij.ad.jp@localhost>


Home | Main Index | Thread Index | Old Index