From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin C.Atkins To: 9fans@cse.psu.edu Subject: Re: [9fans] GUI toolkit for Plan 9 Message-Id: <20020305094617.73bc6fb1.martin@mca-ltd.com> In-Reply-To: <20020304140240.F04DF199B3@mail.cse.psu.edu> References: <20020304140240.F04DF199B3@mail.cse.psu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Date: Tue, 5 Mar 2002 09:46:17 +0530 Topicbox-Message-UUID: 5faef4de-eaca-11e9-9e20-41e7f4b1d025 Thanks Nigel, On Mon, 4 Mar 2002 14:02:41 0000 nigel@9fs.org wrote: > du -a . | grep ... Great hack! Thanks also to the other who pointed this out. > > panic iunlock can be caused by two things: > > if(l->key == 0) > print("iunlock: not locked: pc %luX\n", getcallerpc(&l)); > if(!l->isilock) > print("iunlock of lock: pc %lux, held by %lux\n", getcallerpc(&l), l->pc); > Actually I don't remember a pc - is this because it happened before Plan9 proper got going? I.e. long before the "root is from..." question. (Possibly at about the "using sdC0!..." line), but I don't remember for sure. As I remember the message was simply: panic iunlock I suppose the real fustration was that there didn't seem to be anything I could do about it, short of re-installing from scratch (and having the installer screw up my partition table - again!) > i.e. iunlocking something not locked at all, or iunlocking something > that was locked. > > lock = spin lock > ilock = disable interrupts and spin lock > > the real interest is the pc printed out, because it tells you where the iunlock() > was called from. You can consult the kernel image to find out where this > is. > > Anyway, like I said... It's working great now! Martin -- Martin C. Atkins martin@mca-ltd.com Mission Critical Applications Ltd, U.K.