> >I should have mentioned; you can probably also avoid it by letting your 
> >BIOS give the USB controller an IRQ, since it'll almost certainly also 
> >perform whatever initialisation the driver is currently missing out on.
> Right, that is what I did once I realized that this particular commit
> was the culprit.

The commit isn't (really) the culprit; it's just exposed a bug in the USB 
chipset driver in question.  (I'm mostly just making this point so that 
other people don't go blaming 'correct' PCI behaviour for their problems 

... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
           V I C T O R Y   N O T   V E N G E A N C E

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to