On Mon, Sep 22, 2008 at 3:53 AM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > On Sun, 21 Sep 2008, Justin Mattock wrote: > >> From over here, I did a bad install >> of isight-firmware-tools, causing hal and udev >> to clash. After making sure the package was either >> using hal or udev, there is no message of disable irq #23. >> If its not too much trouble is there a way to verify that this was >> the case, i.g. if udev creates a dev, then hal creates the same device >> will this cause ehci_hcd to have messages of this kind? If so >> then thats what happened, if not then theres something else causing this. > > You didn't read what I wrote earlier, did you? The "HC died" message > should NEVER occur! It doesn't matter what games you play with hal and > udev -- it should NEVER occur. Not ever. > > And since the "HC died" is what causes IRQ #23 to be disabled, that > shouldn't happen either. > > Alan Stern > > appologize for not fully understanidng, I'm just getting confused with why and what is causing this to occur. The only reason for playing with hal and udev is to have this message appear, if I leave them out of the picture the system runs fine. Anyways, I'm up to trying anything at this point, and again appologize for causing any heat. -- Justin P. Mattock -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
