From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Tue, 16 Nov 2010 08:53:31 -0500 To: 9fans@9fans.net Message-ID: <9b7166d89a65ca1ae755c6a78933e7bd@brasstown.quanstro.net> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] That deadlock, again Topicbox-Message-UUID: 82a7e7dc-ead6-11e9-9d60-3106f5b1d025 > I tried acid, but I'm just not familiar enough with it to make it > work. I tried > > rumble% acid 2052 /bin/exportfs > /bin/exportfs:386 plan 9 executable > /sys/lib/acid/port > /sys/lib/acid/386 > acid: src(0xf01e7377) > no source for ?file? cinap is right, the bug is in the kernel. we know that because it's a lock loop. that can only happen if the kernel screws up. also, the address is a kernel address (starts with 0xf). if you didn't know the lock loop message was from the kernel, you could grep for it ; cd /sys/src ; g '"lock (%#?[luxp]+ )loop' . ./9/port/taslock.c:61: print("lock %#p loop key %#lux pc %#lux held by pc %#lux proc %lud\n", - erik