Re: panic in deadlkres() on r267110

2014-06-06 Thread Sean Bruno
On Fri, 2014-06-06 at 10:12 -0400, Glen Barber wrote: Two machines in the cluster panic last night with the same backtrace. It is unclear yet exactly what was happening on the systems, but both are port building machines using ports-mgmt/tinderbox. Any ideas or information on how to further

Re: panic in deadlkres() on r267110

2014-06-06 Thread Ryan Stone
On Fri, Jun 6, 2014 at 10:12 AM, Glen Barber g...@freebsd.org wrote: Two machines in the cluster panic last night with the same backtrace. It is unclear yet exactly what was happening on the systems, but both are port building machines using ports-mgmt/tinderbox. Any ideas or information on

Re: panic in deadlkres() on r267110

2014-06-06 Thread Glen Barber
On Fri, Jun 06, 2014 at 07:23:49AM -0700, Sean Bruno wrote: On Fri, 2014-06-06 at 10:12 -0400, Glen Barber wrote: Two machines in the cluster panic last night with the same backtrace. It is unclear yet exactly what was happening on the systems, but both are port building machines using

Re: panic in deadlkres() on r267110

2014-06-06 Thread Attilio Rao
On Fri, Jun 6, 2014 at 5:06 PM, Glen Barber g...@freebsd.org wrote: On Fri, Jun 06, 2014 at 07:23:49AM -0700, Sean Bruno wrote: On Fri, 2014-06-06 at 10:12 -0400, Glen Barber wrote: Two machines in the cluster panic last night with the same backtrace. It is unclear yet exactly what was

Re: panic in deadlkres() on r267110

2014-06-06 Thread Glen Barber
On Fri, Jun 06, 2014 at 11:06:40AM -0400, Glen Barber wrote: On Fri, Jun 06, 2014 at 07:23:49AM -0700, Sean Bruno wrote: On Fri, 2014-06-06 at 10:12 -0400, Glen Barber wrote: Two machines in the cluster panic last night with the same backtrace. It is unclear yet exactly what was happening

Re: panic in deadlkres() on r267110

2014-06-06 Thread Ryan Stone
On Fri, Jun 6, 2014 at 11:33 AM, Glen Barber g...@freebsd.org wrote: #4 0x8092fa39 in fork1 (td=0xf813ae7f4920, flags=20, pages=Cannot access memory at address 0x4 ) at /usr/src/sys/kern/kern_fork.c:268 This looks like a suspicious piece of code. Could something be causing

Re: panic in deadlkres() on r267110

2014-06-06 Thread Sean Bruno
On Fri, 2014-06-06 at 10:12 -0400, Glen Barber wrote: Two machines in the cluster panic last night with the same backtrace. It is unclear yet exactly what was happening on the systems, but both are port building machines using ports-mgmt/tinderbox. Any ideas or information on how to further

Re: panic in deadlkres

2010-06-28 Thread John Baldwin
On Friday 25 June 2010 4:52:22 pm pluknet wrote: On 25 June 2010 13:50, Anton Yuzhaninov cit...@citrin.ru wrote: I've got panic on 9-current from Jun 25 2010 May be this is bug in deadlock resolver panic: blockable sleep lock (sleep mutex) process lock @

Re: panic in deadlkres

2010-06-28 Thread Attilio Rao
2010/6/28 John Baldwin j...@freebsd.org: On Friday 25 June 2010 4:52:22 pm pluknet wrote: On 25 June 2010 13:50, Anton Yuzhaninov cit...@citrin.ru wrote: I've got panic on 9-current from Jun 25 2010 May be this is bug in deadlock resolver panic: blockable sleep lock (sleep mutex)

Re: panic in deadlkres

2010-06-25 Thread Anton Yuzhaninov
On Fri, 25 Jun 2010 09:50:40 + (UTC), Anton Yuzhaninov wrote: AY I've got panic on 9-current from Jun 25 2010 It's wrong date. The system is: FreeBSD 9.0-CURRENT #0: Fri May 28 23:47:37 MSD 2010 AY AY May be this is bug in deadlock resolver AY AY panic: blockable sleep lock (sleep mutex)

Re: panic in deadlkres

2010-06-25 Thread pluknet
On 25 June 2010 13:50, Anton Yuzhaninov cit...@citrin.ru wrote: I've got panic on 9-current from Jun 25 2010 May be this is bug in deadlock resolver panic: blockable sleep lock (sleep mutex) process lock @ /usr/src/sys/kern/kern_clock.c:203 db show alllocks Process 0 (kernel) thread