From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200304042251.h34Mpb502659@zamenhof.cs.utwente.nl> To: 9fans@cse.psu.edu Subject: Re: [9fans] lock loop messages (anything particular I should do?) In-reply-to: Your message of "Fri, 04 Apr 2003 17:12:27 -0500." References: From: Axel Belinfante MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2630.1049496695.1@zamenhof.cs.utwente.nl> Date: Sat, 5 Apr 2003 00:51:36 +0200 Topicbox-Message-UUID: 8aebb7a8-eacb-11e9-9e20-41e7f4b1d025 > > lock 0x8029bd68 loop key 0xdeaddead pc 0x80104e08 held by pc 0x80104e08 pro > c 486 > > The numbers are irrelevant to me. You have to look at them through > your kernel. Ok. I was wondering wether it meant something that the same pc number appeared twice in the lock line. Or is it just one number that gets printed twice? Acid tells me: term% acid 9pcdisk 9pcdisk:386 plan 9 boot image /sys/lib/acid/port /sys/lib/acid/386 acid: src(0x80104e08) /sys/src/9/pc/mmu.c:332 327 328 mach0 = MACHP(0); 329 330 lock(&mmukmaplock); 331 >332 if((pte = mmuwalk(mach0->pdb, va, 1, 0)) == nil){ 333 unlock(&mmukmaplock); 334 return 0; 335 } 336 if(!(*pte & PTESIZE) && mmuwalk(mach0->pdb, va, 2, 0) == nil){ 337 unlock(&mmukmaplock); acid: My /sys/src/9/pc/mmu.c is of Apr 11 2002. In case it helpful: I compiled that kernel on Feb 18 2003. Axel.