[haiku-development] Re: AHCI driver ready for testing

  • From: Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Mon, 01 Oct 2007 17:49:06 +0200

On 2007-10-01 at 17:24:52 [+0200], Axel Dörfler <axeld@xxxxxxxxxxxxxxxx> 
wrote:
> Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
> > > queue:   86 4d 32 6b 92 29 36
> > > last acquired by: 134, count: 1024
> > > last released by: 134, count: 1
> > Unless I'm mistaken, this means, the thread has acquired the
> > semaphore with
> > count 1024 (as write lock) and then released it with count 1 (as read
> > lock).
> > 
> > Since the commit list still seems to be out of order, I haven't seen
> > Axel's
> > recent commits, but I guess one of them is to blame. I'll have a
> > look.
> 
> In this case the above should read: last acquired by: -134, count: 1024

Yeah, right.

> It looks more like it first had a read lock, and then later acquired a
> write lock that it still owns.

Yes, it had a read lock, released it, acquired a write lock successfully 
and is now waiting for a read lock while still having the write lock.

CU, Ingo

Other related posts: