> > What happens if you don't include firewire_ohci? > > Yeah, deleting firewire_ohci fixed the problem (with "noapic" specified). > > > Must you use "noapic"? That can cause IRQ routing problems... > > Ok, I retested without "noapic" and, fortunately, everything worked just > fine.
That is, without "noapic" but *with* firewire_ohci? Good. Avoid using that option if you don't need to. > > The reason your audio craps out *too* is that it's one of the > > zillion devices sharing IRQ #11. Bugs in any one of their > > drivers could cause problems like this. > > If you are 100% sure that it was not usb-ohci fault (could be > firewire_ohci's then), then let it be. The fingers seem to point to firewire_ohci or "noapic". That firewire stack is new, so a bug there is very believable. Changing IRQ routing by not using the APIC is probably closest to the root cause of the problem. > However, reverting that patch _helped_ for me > previously (with "noapic"). Hopefully, other people won't get > bitten by the same problem. As Alan noted, it's not uncommon that fixing one bug uncovers new problems. With three factors uncovered *so far* with this problem, the root cause still not clear to me. But I'd guess it relates to the way you disabled APIC IRQ routing. - Dave - To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
