On Tue, 10 Dec 2002, Tvrtko A. Ursulin wrote: | > > Is it ok to sleep in probe() ? | > > | > > My testing says - NO. For example, I want to query some information from | > > device as soon it is connected. If I sumbit one small interrupt urb (8 | > > bytes) and sleep until completion handler wakes me up, everything is ok. | > > But if I try to do it 2 times (2 same urbs) - deadlock. | > > | > > So I guess it is not ok to sleep in a probe. Just wanted somebody to | > > confirm this. | > | > On the contrary. You may sleep in probe(). | | Thanks! I found that out later by digging through the source. | | Although, I still don't have a slightest clue why I am having problems I have. | When I send one urb - ok. Two urbs - deadlock. | | Is kernel trying to say something by blinking with CapsLock and ScrollLock | (synchronized) ?
In a 2.4 kernel? Yes, that's a panic notification. In drivers/char/pc_keyb.c: /* Tell the user who may be running in X and not see the console that we have panic'ed. This is to distingush panics from "real" lockups. Could in theory send the panic message as morse, but that is left as an exercise for the reader. */ void panic_blink(void) -- ~Randy ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
