Comment 6 for bug 435885

I suppose whether it's the same bug for different BAR numbers depends on how you look at it. The suggested kernel patch disables this for BAR 6 only, reason being: "since
this is BAR 6, is we have a ROM which has been mapped high, and then
not unmapped. -- We shouldn't warn about not being able to allocate ROM BARs. They are
often deliberately mapped outside the range of parent windows in order
to disable them."

On the other hand, "given that sometimes the ROM is important, it seems like an
error. Really we should be smarter about re-allocating things as
necessary..." Smarter re-allocation could fix this for other BAR numbers as well. Further, as I understand it, the BAR numbers are device-specific and on some devices the other BAR numbers may be ROM as well.

I hope this bug gets looked at by someone who can decide what to do :-)