Re: Today's RELENG_5_4 and 'lock cmpxchgl'

2005-07-19 Thread Marc Olzheim
On Tue, Jul 19, 2005 at 01:53:14PM +0200, Marc Olzheim wrote: > On Fri, Jul 15, 2005 at 08:05:23AM -0400, Kris Kennaway wrote: > > > Ok, even non-SMP 7-CURRENT crashes on it, so I do not believe that I'm > > > the only one seeing this... > > > > You're not..as noted, it's been widely reported. >

Re: Today's RELENG_5_4 and 'lock cmpxchgl'

2005-07-19 Thread Marc Olzheim
On Fri, Jul 15, 2005 at 08:05:23AM -0400, Kris Kennaway wrote: > > Ok, even non-SMP 7-CURRENT crashes on it, so I do not believe that I'm > > the only one seeing this... > > You're not..as noted, it's been widely reported. Could you give me any pointers to where this has been discussed before ?

Re: Today's RELENG_5_4 and 'lock cmpxchgl'

2005-07-15 Thread Kris Kennaway
On Fri, Jul 15, 2005 at 12:05:39PM +0200, Marc Olzheim wrote: > On Fri, Jul 15, 2005 at 11:40:27AM +0200, Marc Olzheim wrote: > > On Thu, Jul 14, 2005 at 01:44:04PM -0400, Kris Kennaway wrote: > > > > The -CURRENT traces are very different from these, but I don't have > > > > comconsole on the -CUR

Re: Today's RELENG_5_4 and 'lock cmpxchgl'

2005-07-15 Thread Marc Olzheim
On Fri, Jul 15, 2005 at 11:40:27AM +0200, Marc Olzheim wrote: > On Thu, Jul 14, 2005 at 01:44:04PM -0400, Kris Kennaway wrote: > > > The -CURRENT traces are very different from these, but I don't have > > > comconsole on the -CURRENT machine. > > > > Thanks. > > Am I really the only one seeing th

Re: Today's RELENG_5_4 and 'lock cmpxchgl'

2005-07-15 Thread Marc Olzheim
On Thu, Jul 14, 2005 at 01:44:04PM -0400, Kris Kennaway wrote: > > The -CURRENT traces are very different from these, but I don't have > > comconsole on the -CURRENT machine. > > Thanks. Since I get plenty of opportunities to fiddle in the debugger now, because this happens a lot (we use screen a

Re: Today's RELENG_5_4 and 'lock cmpxchgl'

2005-07-14 Thread Kris Kennaway
On Thu, Jul 14, 2005 at 03:05:20PM +0200, Marc Olzheim wrote: > > You need to obtain the debugging traceback for the panic and include > > it in the PR. > > Added two crash traces, one for the open() variant, one for the close() > variant. > > The -CURRENT traces are very different from these, b

Re: Today's RELENG_5_4 and 'lock cmpxchgl'

2005-07-14 Thread Marc Olzheim
On Wed, Jul 13, 2005 at 02:41:18PM -0400, Kris Kennaway wrote: > > > Make sure you recompile any modules when activating INVARIANTS, or > > > you'll get panics. > > > > Of course... make buildkernel and make installkernel do that for me... ;) > > Not if you are using third party port modules. W

Re: Today's RELENG_5_4 and 'lock cmpxchgl'

2005-07-13 Thread Kris Kennaway
On Wed, Jul 13, 2005 at 02:55:22PM +0200, Marc Olzheim wrote: > On Wed, Jul 13, 2005 at 08:00:31AM -0400, Kris Kennaway wrote: > > > Stress testing this gives me instant fatal trap 12 on both 11 juli's > > > CURRENT and RELENG_5. > > > > > > I'll file a PR. > > > > Make sure you recompile any mod

Re: Today's RELENG_5_4 and 'lock cmpxchgl'

2005-07-13 Thread Marc Olzheim
On Wed, Jul 13, 2005 at 08:00:31AM -0400, Kris Kennaway wrote: > > Stress testing this gives me instant fatal trap 12 on both 11 juli's > > CURRENT and RELENG_5. > > > > I'll file a PR. > > Make sure you recompile any modules when activating INVARIANTS, or > you'll get panics. Of course... make

Re: Today's RELENG_5_4 and 'lock cmpxchgl'

2005-07-13 Thread Kris Kennaway
On Wed, Jul 13, 2005 at 11:29:39AM +0200, Marc Olzheim wrote: > On Mon, Jul 11, 2005 at 04:32:16PM +0200, Marc Olzheim wrote: > > On Sun, Jul 03, 2005 at 10:38:58AM +0200, Philippe PEGON wrote: > > > >The panic appears to be an instance of a known bug in 5.4 (and > > > >INVARIANTS will not fix it,

Re: Today's RELENG_5_4 and 'lock cmpxchgl'

2005-07-13 Thread Marc Olzheim
On Mon, Jul 11, 2005 at 04:32:16PM +0200, Marc Olzheim wrote: > On Sun, Jul 03, 2005 at 10:38:58AM +0200, Philippe PEGON wrote: > > >The panic appears to be an instance of a known bug in 5.4 (and > > >INVARIANTS will not fix it, but may just delay the inevitable by > > >changing timings). See Doug

Re: Today's RELENG_5_4 and 'lock cmpxchgl'

2005-07-11 Thread Marc Olzheim
On Sun, Jul 03, 2005 at 10:38:58AM +0200, Philippe PEGON wrote: > >The panic appears to be an instance of a known bug in 5.4 (and > >INVARIANTS will not fix it, but may just delay the inevitable by > >changing timings). See Doug White's recent emails which point to a > >patch you should test. > >

Re: Today's RELENG_5_4 and 'lock cmpxchgl'

2005-07-03 Thread Philippe PEGON
Kris Kennaway a écrit : On Fri, Jul 01, 2005 at 03:03:35PM +0200, Marc Olzheim wrote: On Fri, Jul 01, 2005 at 12:41:39PM +0200, Marc Olzheim wrote: On Fri, Jul 01, 2005 at 12:14:58PM +0200, Marc Olzheim wrote: Somehow, this sounds familiar, i.e.: the "lock cmpxchgl": Fatal trap 12: page fa

Re: Today's RELENG_5_4 and 'lock cmpxchgl'

2005-07-01 Thread Kris Kennaway
On Fri, Jul 01, 2005 at 03:03:35PM +0200, Marc Olzheim wrote: > On Fri, Jul 01, 2005 at 12:41:39PM +0200, Marc Olzheim wrote: > > On Fri, Jul 01, 2005 at 12:14:58PM +0200, Marc Olzheim wrote: > > > Somehow, this sounds familiar, i.e.: the "lock cmpxchgl": > > > > > > Fatal trap 12: page fault whil

Re: Today's RELENG_5_4 and 'lock cmpxchgl'

2005-07-01 Thread Marc Olzheim
On Fri, Jul 01, 2005 at 12:41:39PM +0200, Marc Olzheim wrote: > On Fri, Jul 01, 2005 at 12:14:58PM +0200, Marc Olzheim wrote: > > Somehow, this sounds familiar, i.e.: the "lock cmpxchgl": > > > > Fatal trap 12: page fault while in kernel mode > ... > > Stopped at 0xc05160c3 = knote+0x27:

Re: Today's RELENG_5_4 and 'lock cmpxchgl'

2005-07-01 Thread Marc Olzheim
On Fri, Jul 01, 2005 at 12:14:58PM +0200, Marc Olzheim wrote: > Somehow, this sounds familiar, i.e.: the "lock cmpxchgl": > > Fatal trap 12: page fault while in kernel mode ... > Stopped at 0xc05160c3 = knote+0x27:lock cmpxchgl > %ecx,0x1c(%edx) Somehow I think I solved this last