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

On 2007-10-01 at 12:56:36 [+0200], Marcus Overhagen 
<marcusoverhagen@xxxxxxxx> wrote:
> Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
> > <marcusoverhagen@xxxxxxxx> wrote:
> 
> > > The AHCI SATA driver is now in a working state and has write support
> 
> > We had VM+BFS deadlock problems, but it seems Axel managed to fix or work
> > around them yesterday or today. The current version (r22392) fully boots
> > here again.
> 
> I just tested with r22393 and it indeed fully boots, Terminal, Deskbar and 
> Tracker
> all start. I can even move a Tracker window :)
> 
> But the bad news: when clicking on Deskbar, the system deadlocks. It appears
> to be semaphore 4.
> 
> regards
> Marcus
> 
> PS: some infos:
> 
> kdebug> waiting 4
> thread         id  state        sem/cv cpu pri  stack      team  name
> 0x90afd000     86  waiting           4   -  15  0x9464f000   54  w>Deskbar
> 0x9090a800     29  waiting           4   -   5  0x803c0000    1  syslog 
> sender
> 0x90a28000     4d  waiting           4   -  10  0x906cb000   47  
> _input_server_event_loop_
> 0x90988000     32  waiting           4   -  10  0x803d3000   2f  
> timer_thread
> 0x90b14000     92  waiting           4   -  10  0x94761000   47  AT 
> Keyboard 1 watcher
> 0x90983000     36  waiting           4   -  10  0x803e3000   36  net_server
> kdebug> sem 4
> SEM: 0x93f5f0b0
> id:      0x4
> name:    'kernel_aspacelock'
> owner:   0x0
> count:   0xfffffff9
> 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.

CU, Ingo

Other related posts: