[haiku-development] Re: bug 2084

2009/2/16 Peter Kerpedjiev <pkerpedjiev@xxxxxxxxx>:
> It's on a laptop. Before plugging in the device, f12 works fine. After
> I plug it in... nothing.
>
> I've tried plugging in a usb keyboard and a usb drive. The outcome is the 
> same.
>
> -Peter
>
> 2009/2/16 Urias McCullough <umccullough@xxxxxxxxx>:
>> On Mon, Feb 16, 2009 at 4:06 PM, Peter Kerpedjiev <pkerpedjiev@xxxxxxxxx> 
>> wrote:
>>> If haiku hangs and doesn't respond to f12 or ctr-alt-del, is there a
>>> starting point for trying to figure out what went wrong? I've checked the
>>> syslog and everything seems to be in order. There are no new messages
>>> printed.
>>
>> If it's a USB keyboard, the f12 -> kdl is disabled...
>>
>> If it's PS2 (plugged directly into a PS2 port on your computer) then I
>> guess that sounds bad.
>>
>> - Urias
>>

If I plug in a usb device before booting, when it gets past the splash
screen the os hangs. If I hit f12 I get the following (summarized)
stack trace:

thread; fxp_int_handler

switch_sem_etc
acquire_sem
intr_handler
create_kernel_thread_kentry()
thread_kthread_exit

If I continue, the os continues to run, but nothing happens. I retain
the ability to hit f12 and enter KDL. Once I move the trackpad, the
system completely hangs. It stops responding to f12.

If I boot without a USB device plugged, I'm able to use the system
just fine. If I then plug in the USB device, the keyboard continues to
work. Hitting f12 yields the following stack:

switch_sem_etc
user_acquire_sem_etc
handle_syscall
...
Yeah baby, very shagadelic [sic]

or...

switch_sem_etc
_user_acquire_sem_etc
handle_syscall
...
multi_audio_output_143_st

Moving the mouse (trackpad) causes the system to completely hang.

It looks like all of the above functions are waiting on a semaphore.
Perhaps the usb device acquires it and doesn't release it?

Could the mouse interrupt handler be causing a deadlock?  Can
interrupt handlers acquire sempahores?

-Peter

Other related posts: