In message: <200307091711.h69HBHbN083840_at_grimreaper.grondar.org> Mark Murray <mark_at_grondar.org> writes: : If I were to start instrumenting ep(4) with debug printf's, where is : the best place to start? I'm not sure that printf is the right way to track this down. You are seeing, iirc, that ep0 "works" for a period of time, typically very short, it hangs up. These sorts of things are hard to find with a printf. My first suggestion would be to enable WITNESS to see if it tells you about any LoR which might be a clue. The MPSAFE changes I made to pccbb just move up the tree one level where the Giant lock is taken out in this case. If the failure is early enough in the process, you might want to put printfs into pccbb_intr to see if they will show you what they tell you the order of the first few interrupts for the card are. maybe we're having a race with some interrupt before ep is really ready to field interrupts or something that the giant lock being held before protected against... WarnerReceived on Wed Jul 09 2003 - 09:08:13 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:14 UTC