Re: splassert: tsleep: want 0 have 1

2017-02-02 Thread Pedro Caetano
Hi, Running a release built with today's sources I've ran into a few more stack traces. --- syscall (number 54) --- --- syscall (number 97) --- --- syscall (number 105) --- stack traces below, extracted from /var/run/dmesg.boot. Cheers, Pedro Caetano ansible@q-tester $ > sysctl kern.version

Re: splassert: tsleep: want 0 have 1

2017-01-31 Thread Martin Pieuchot
On 30/01/17(Mon) 22:02, Pedro Caetano wrote: > Hi, > > On three of six VMs the following stack trace has been shown on logs. > All the systems are amd64 running the same snapshot, sources fecthed from > cvs january 28th, the only that crashed were running ospfd. > > stacks and dmesg below.

splassert: tsleep: want 0 have 1

2017-01-30 Thread Pedro Caetano
Hi, On three of six VMs the following stack trace has been shown on logs. All the systems are amd64 running the same snapshot, sources fecthed from cvs january 28th, the only that crashed were running ospfd. stacks and dmesg below. Best regards, Pedro Caetano splassert: tsleep: want 0 have 1