On 2013-01-14 14:47, Holm Tiffe wrote:
Martin Husemann wrote:On Mon, Jan 14, 2013 at 02:36:56PM +0100, Holm Tiffe wrote:..but it looks lik it where be working: db> show all procs PID LID S CPU FLAGS STRUCT LWP * NAME WAIT 2 > 1 7 0 40000 80e33d20 init 1 1 3 0 80 80f47aa0 init waityay!lock address : 0x000000008020e078 type : spin initialized : 0x00000000800e4f74so: x/i 0x00000000800e4f74 should tell you what code initialized the lock in question, and maybe x/x 0x000000008020e078 will tell more about the lock itself. MartinLike this? root time: 0x50f40b95 root file system type: nfs TODR stoppedWARNING: preposterous TOD clock time WARNING: using filesystem time WARNING: CHECK AND RESET THE DATE! init: copying out path `/sbin/init' 11 Mutex error: lockdebug_wantlock: locking against myself lock address : 0x000000008021b2e8 type : spin initialized : 0x00000000800ebae6 shared holds : 0 exclusive: 1 shares wanted: 0 exclusive: 1 current cpu : 0 last held: 0 current lwp : 0x0000000080f3faa0 last held: 0x0000000080f3faa0 last locked* : 0x00000000800ec6fc unlocked : 000000000000000000 owner field : 0x0000000000011700 wait/spin: 0/1 panic: LOCKDEBUG Stopped in pid 1.1 (init) at netbsd:panic+0x19: nop db> x/i 0x00000000800ebae6 netbsd:pmap_bootstrap+0x360: movl avail_end, r1 db> x/x 0x000000008021b2e8 netbsd:pvtable_lock: 11701 db>
Hmm. Here? #if defined(MULTIPROCESSOR) || defined(LOCKDEBUG) mutex_init(&pvtable_lock, MUTEX_DEFAULT, IPL_VM); #endifBut I don't understand how the init can cause that? I must be missing something...
Johnny -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt%softjar.se@localhost || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol