Re: About support for rtVAX300

[Holm Tiffe <holm%freibergnet.de@localhost>]

Holm Tiffe wrote:

> Martin Husemann wrote:
> 
> > On Mon, Jan 14, 2013 at 02:47:29PM +0100, Holm Tiffe wrote:
> > > db> x/x 0x000000008021b2e8
> > > netbsd:pvtable_lock:    11701
> > 
> > Good, so we know which lock it is.
> > 
> > Now do the x/i also for the "last locked" address, and do a bt
> > (backtrace) to get the call stack. The pvtable_lock is hold (by the code
> > pointed at in the last lock field) and one or two frames up from the "panic"
> > you will see the code that tries to lock it again.
> > 
> > Martin
> 
> owner field  : 0x0000000000011700 wait/spin:                0/1
> 
> panic: LOCKDEBUG
> Stopped in pid 1.1 (init) at    netbsd:panic+0x19:      nop
> db> x/i 0x00000000800ec6fc
> netbsd:pmap_enter+0x57c:        tstl    (r8)
> db> bt
> panic: LOCKDEBUG
> Stack traceback :
> 0x836c4a70: panic+0x19(0x801ed3b2)
> 0x836c4aa8:
> lockdebug_abort1+0x87(0x8023098c,0x17,0x801ed667,0x801da98e,0x1)
> 0x836c4af8: lockdebug_wantlock+0x108(0x8021b2e8,0x800ec958,0,0)
> 0x836c4b38: mutex_enter+0x235(0x8021b2e8)
> 0x836c4b7c: pmap_enter+0x7d8(0x80f5c078,0x7ffff000,0xed6000,0x7,0x21)
> 0x836c4bc4:
> uvm_fault_lower_enter+0xf3(0x836c4d5c,0x836c4d3c,0,0x80ed7fd0,0x8035
> a218)
> 0x836c4c0c: uvm_fault_lower+0xbe6(0x836c4d5c,0x836c4d3c,0x836c4cbc)
> 0x836c4c64: uvm_fault_internal+0x547(0x80eece58,0x7ffff000,0x1,0)
> 0x836c4d80: trap+0x2ac(0x836c4e44)
> 0x836c4e44: trap type=0x8 code=0x7ffffff5 pc=0x80000850 psl=0x8000004
> 0x836c4e10: copyin+0x18(0x801d52fd,0x7ffffff5,0xb)
> 0x836c4e90: start_init+0x146(0x80f3faa0)
> 0x836c4f64: cpu_lwp_bootstrap+0x15(0)
> 
> Gruß,
> 
> Holm (muß erstmal Zigaretten holen fahren)
> -- 


...and now? What's the problem?

Regards,

Holm
-- 
      Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, 
     Freiberger Straße 42, 09600 Oberschöna, USt-Id: DE253710583
  www.tsht.de, info%tsht.de@localhost, Fax +49 3731 74200, Mobil: 0172 8790 741