Re: panic on 5.2 BETA: blockable sleep lock

2003-12-01 Thread Roger Hardiman
Hi Please can someone commit the bktr patch for me to fix 5.2-BETA (as long as re@ approve). I don't have the resources. I'm not suprised that I haven't heard from him because this issue came up at the start of the Thanksgiving holiday weekend. If only it were that simple. Actually I'm

Re: panic on 5.2 BETA: blockable sleep lock

2003-12-01 Thread Don Lewis
On 1 Dec, Roger Hardiman wrote: Hi Please can someone commit the bktr patch for me to fix 5.2-BETA (as long as re@ approve). I don't have the resources. If you're happy with the patch, I'll pursue re@ approval for the commit. I'm not suprised that I haven't heard from him because this

Re: panic on 5.2 BETA: blockable sleep lock

2003-12-01 Thread Don Lewis
On 1 Dec, Roger Hardiman wrote: Hi Please can someone commit the bktr patch for me to fix 5.2-BETA (as long as re@ approve). I don't have the resources. The patch has been committed with re@ approval. ___ [EMAIL PROTECTED] mailing list

Re: panic on 5.2 BETA: blockable sleep lock

2003-11-30 Thread Stefan Ehmann
On Fri, 2003-11-28 at 01:02, Don Lewis wrote: On 27 Nov, Stefan Ehmann wrote: On Wed, 2003-11-26 at 08:33, Don Lewis wrote: The problem is that selrecord() wants to lock a MTX_DEF mutex, which can cause a context switch if the mutex is already locked by another thread. This is contrary to

Re: panic on 5.2 BETA: blockable sleep lock

2003-11-30 Thread Don Lewis
On 30 Nov, Stefan Ehmann wrote: On Fri, 2003-11-28 at 01:02, Don Lewis wrote: On 27 Nov, Stefan Ehmann wrote: On Wed, 2003-11-26 at 08:33, Don Lewis wrote: The problem is that selrecord() wants to lock a MTX_DEF mutex, which can cause a context switch if the mutex is already locked by

Re: panic on 5.2 BETA: blockable sleep lock

2003-11-28 Thread Stefan Ehmann
On Fri, 2003-11-28 at 01:02, Don Lewis wrote: On 27 Nov, Stefan Ehmann wrote: On Wed, 2003-11-26 at 08:33, Don Lewis wrote: The problem is that selrecord() wants to lock a MTX_DEF mutex, which can cause a context switch if the mutex is already locked by another thread. This is contrary to

Re: panic on 5.2 BETA: blockable sleep lock

2003-11-28 Thread Stefan Ehmann
On Fri, 2003-11-28 at 01:02, Don Lewis wrote: On 27 Nov, Stefan Ehmann wrote: On Wed, 2003-11-26 at 08:33, Don Lewis wrote: The problem is that selrecord() wants to lock a MTX_DEF mutex, which can cause a context switch if the mutex is already locked by another thread. This is contrary to

Re: panic on 5.2 BETA: blockable sleep lock

2003-11-28 Thread Stefan Ehmann
On Fri, 2003-11-28 at 10:31, Stefan Ehmann wrote: On Fri, 2003-11-28 at 01:02, Don Lewis wrote: On 27 Nov, Stefan Ehmann wrote: On Wed, 2003-11-26 at 08:33, Don Lewis wrote: The problem is that selrecord() wants to lock a MTX_DEF mutex, which can cause a context switch if the mutex is

Re: panic on 5.2 BETA: blockable sleep lock

2003-11-27 Thread Stefan Ehmann
On Wed, 2003-11-26 at 08:33, Don Lewis wrote: The problem is that selrecord() wants to lock a MTX_DEF mutex, which can cause a context switch if the mutex is already locked by another thread. This is contrary to what bktr_poll() wants to accomplish by calling critical_enter(). Strange enough

Re: panic on 5.2 BETA: blockable sleep lock

2003-11-27 Thread Don Lewis
On 27 Nov, Stefan Ehmann wrote: On Wed, 2003-11-26 at 08:33, Don Lewis wrote: The problem is that selrecord() wants to lock a MTX_DEF mutex, which can cause a context switch if the mutex is already locked by another thread. This is contrary to what bktr_poll() wants to accomplish by calling

Re: panic on 5.2 BETA: blockable sleep lock

2003-11-26 Thread Don Lewis
On 26 Nov, Stefan Ehmann wrote: I got the following panic twice when starting xawtv using 5.2 BETA (CVS from Oct 23) panic: blockable sleep lock (sleep mutex) sellck @/usr/src/sys/kern/sys_generic.c:1145 I don't think it is directly related to bktr since the last commit there was ~3 months