On Monday, April 01, 2013 12:29:46 pm Xin Li wrote: > Yes, this is a bandaid and the right fix should be refactor the code a > little bit to make sure that no interrupt handler is installed before > the driver have done other initializations but I don't have hardware > that can reproduce this issue handy to validate changes like that.
It is not that easy. I instrumented the crap out of the igb driver on the one machine where I could reliably reproduce this and kept clearing the interrupt cause register during attach multiple times and still got a spurious interrupt. I believe this is a chip bug of some sort, but I've no idea whose fault it is. It has only been reported on SuperMicro *8* boards to date. -- John Baldwin _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
