Re: LOCKDEBUG panic in serial tty code

[Rafal Boni <rafal%pobox.com@localhost>]

On Tue, Jun 03, 2008 at 12:27:54PM +0100, Andrew Doran wrote:
> On Tue, Jun 03, 2008 at 12:29:57PM +0200, Hauke Fath wrote:
> 
> > Condition variable error: lockdebug_wakeup: interlocking mutex not held 
> > during wakeup
> > 
> > lock address : 0x000000000aa847a0 type     :               spin
> > initialized  : 0x00000000001c0138 interlock: 0x00000000003536c0
> > 
> > panic: LOCKDEBUG
> > Stopped in pid 0.6 (system) at  netbsd:cpu_Debugger+0x6: unlk a6
> > db> t
> > cpu_Debugger(2000,2001,a9adc1c,aa30e8c,aa30e9c) + 6
> > panic(2be5f7,aa847a0,2000,a9adc1c,aa84708) + 172
> > lockdebug_abort1(a9adc1c,2000,2be882,2be735,1) + 92
> > lockdebug_wakeup(aa847a0,1c0ffe) + aa
> > cv_broadcast(aa847a0,d06100,aa30f0c,265b9e,aa84708) + 1a
> > ttypull(aa84708) + 18
> > zsstart(aa84708) + 52
[...]

Ooh I hit this same panic on hpcarm after getting the sa11x0 / hpcarm
interrupt code beat into somewhat working shape.  Glad it's not something
specific to hpcarm :)... now I wonder if I can blame the serial console
(whole machine really) lockups on this as well...

Thanks for the report (makes me feel better) and thanks for looking at
finishing the locking, Andrew!

(it was the sa11x0 sacom in my case)
--rafal

-- 
  Time is an illusion; lunchtime, doubly so.     |/\/\|           Rafal Boni
                   -- Ford Prefect               |\/\/|      
rafal%pobox.com@localhost