Re: [9fans] That deadlock, again

[erik quanstrom <quanstro@quanstro.net>]

> 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