ixgbe crashes on debug builds when it fails to attach
When ixgbe fails to map registers, due to 64-bit addresses being used for example, it will end up panicking by blowing an assertion when it calls ddi_cb_unregister(). ddi_cb_unrgister() is asserting that the handle is not NULL. However, in this case, we've never called ddi_cb_register() because we failed to map our registers.
ddi_cb_unregister() is a little bit different in that it does actually explicitly handle the case where the entry is not NULL; however, I believe the assertion is there for the same reason that the !servicing_interrupt() one is there. Mainly that it's trying to help folks who are on debug builds who would normally cast these errors to void and drive on and therefore we shouldn't remove this assertion, but instead fix it.
Updated by Electric Monk almost 5 years ago
- Status changed from New to Closed
commit 895d6e020017428ea020dda826e399f341a20c37 Author: Robert Mustacchi <firstname.lastname@example.org> Date: 2017-01-03T01:23:00.000Z 7707 ixgbe crashes on debug builds when it fails to attach Reviewed by: Patrick Mooney <email@example.com> Reviewed by: Ryan Zezeski <firstname.lastname@example.org> Reviewed by: Joshua M. Clulow <email@example.com> Reviewed by: Jason King <firstname.lastname@example.org> Reviewed by: Toomas Soome <email@example.com> Reviewed by: Dale Ghent <firstname.lastname@example.org> Approved by: Gordon Ross <email@example.com>