Re: 8.99.1: exiting unheld spin mutex

2017-06-06 Thread Kengo NAKAHARA
Hi, I'm sorry for late reply. On 2017/06/07 3:08, Christos Zoulas wrote: > In article <20170606173220.6e53czlyei7hep4h@danbala>, > Thomas Klausner 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 wi

Re: 8.99.1: exiting unheld spin mutex

2017-06-06 Thread Christos Zoulas
In article <20170606173220.6e53czlyei7hep4h@danbala>, Thomas Klausner 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 >writi

Re: 8.99.1: exiting unheld spin mutex

2017-06-06 Thread Martin Husemann
On Tue, Jun 06, 2017 at 07:32:20PM +0200, Thomas Klausner wrote: > Mutex error: mutex_vector_exit,720: exiting unheld spin mutex > > lock address : 0xfe882ef8d0b8 > current cpu : 6 > current lwp : 0xfe881c147a40 > owner field : 0x0600 wait/spin: 0/1 This is

8.99.1: exiting unheld spin mutex

2017-06-06 Thread Thomas Klausner
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 EXI