On Friday, January 11, 2008 3:58 Ivan Kokshaysky wrote:
> On Fri, Jan 11, 2008 at 02:38:03PM -0700, Matthew Wilcox wrote:
> > On Fri, Jan 11, 2008 at 01:28:30PM -0800, Linus Torvalds wrote:
> > > Hmm. Were all those reports root-caused to just that BAR probing?
> > > If so, we may be in better shape than I worried.
> >
> > I believe so.
>
> Ditto.
>
> One typical problem is that on "Intel(r) 3 Series Experss Chipset
> Family" MMCONFIG probing of the BAR #2 (frame buffer address) of
> integrated graphics device locks up the machine (depending on BIOS
> settings, of course). This happens because the frame buffer of IGD
> has higher decode priority than MMCONFIG range, as stated in Intel
> docs...
Yeah, I'm only aware of 3:
- the BAR overlapping w/MMCONFIG problem described above
- ATI chipset config space retry bug
- VIA (?) chipset host bridges don't respond well to having decode
disabled (they stop decoding RAM addresses as well)
That's it afaik, so I've never really known where Linus' paranoia comes
from. OTOH I haven't been too keen to challenge it either; MMCONFIG
space is only just beginning to be tested widely with the deployment of
Vista, so we'll doubtless see more problems on older chipsets if we
enable it by default.
Jesse
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
