> > Why not simply skip that call if ci_flush_bp is NULL? > > Because ci_flush_bp should probably be set to something so I figured > the diagnostic is better than skipping it. In my case it was > because mainbus_match_primary() was not matching to the cpu device > when it should have, which prompted me to change the DTB reg values.
Fair enough.