Andrea Campi wrote: > On Sat, Jan 25, 2003 at 11:55:01AM -0700, M. Warner Losh wrote: > > This sounds like it might be an interrupt storm. I'm not sure if the > > fwohci driver is failing to clear an interrupt source, or if the > > cardbus bridge is failing. Have you connected a fw device to the > > firewire card? > > I've been able to run a few more tests, even though I've not done abused > it in every way I have in my mind yet... > > The evidence I currently have is: > - if I load the modules at loader time everything is fine, with or without > a device attached > - if I load the modules later on, the kldload doesn't return and the system > stops responding; I can still enter DDB. The only way to recover from that is > to eject the card; at that point, the system is usable BUT as soon as there > is network activity, the system freezes hard (can't get to DDB). > > IMHO this is 100% an interrupt problem. Does this ring a bell with one of you, > or should I provide more info?
I expect that the attach of the device creates an interrupt if the system is already up. This would indicate that it was an order of operations problem in the driver registration for a "live" piece of hardware. Probably, it needs to attach the interrupt handler first, and then handle the result of an active probe as a special case (if it can). This should let you set up the hardware in the right order that you don't start getting interrupts because you've enabled them before establishing a handler. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
