On Tue, Mar 13, 2007 at 09:01:03PM +0000, Peter Green wrote: > despite the best intentions of debian i am convinced that most users will > not read the release notes and over the lifetime of the etch release > having large ammounts (just how much is needed to trigger this bug btw) of > memory will become more and more common.
AIUI the bug triggers on systems with memory in excess of 5GB. Limited to server-class hardware. I hope server admins are aware of the contents of release notes. > what is the performance impact of using the safe option on all hardware > even that not affected by this bug? would using that option by default > result in a noticable performance degrdation? It's unknown to me whether all other currently-supported systems even *work* if iommu=soft is set. This is not the time to gamble with the kernel. If a targetted patch is available that sets iommu=soft for the chipset in question, that would be a good candidate for the next kernel upload, which may or may not make it into r0. But if no one has a good fix to offer, I think we need to settle for documenting it as errata given that upstream doesn't have a proper fix for this yet. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
