On Thu, Mar 22, 2007 at 01:15:31AM -0700, Steve Langasek wrote:
In the meantime, I don't see any reason why we shouldn't patch the kernel to
disable hw iommu on nvidia systems only. I believe the attached patch
should do this. Are you in a position to confirm that this does disable hw
iommu
Hi Bastian,
On Sat, Mar 31, 2007 at 04:05:33PM +0200, Bastian Blank wrote:
On Thu, Mar 22, 2007 at 01:15:31AM -0700, Steve Langasek wrote:
In the meantime, I don't see any reason why we shouldn't patch the kernel to
disable hw iommu on nvidia systems only. I believe the attached patch
tags 404148 patch
thanks
On Wed, Mar 14, 2007 at 01:24:30AM +0100, Christoph Anton Mitterer wrote:
First of all,.. there is still no other solution than iommu=soft (at
least as of my knowledge) and we had even someone on the bugreport at
bugzilla.kernel.org who claimed that _only_ iommu=soft
Processing commands for [EMAIL PROTECTED]:
tags 404148 patch
Bug#404148: kernel: data corruption with nvidia chipsets and IDE/SATA drives //
memory hole mapping related bug?!
There were no tags set.
Tags added: patch
thanks
Stopping processing here.
Please contact me if you need assistance.
Steve Langasek wrote:
In all doing respect, I think that it's a much greater risk to not use
iommu=soft per default than doing so. Even if we imagine that there
would by systems that don't work with the sw-iommu it's likely that
they simply break (at boot time). And then the affected user
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.
what does the sarge kernel do when
On Tue, Mar 13, 2007 at 09:01:03PM +, 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
Hi.
Sorry that I've ignored the last answers to the bug but I somehow missed
the mail.
First of all,.. there is still no other solution than iommu=soft (at
least as of my knowledge) and we had even someone on the bugreport at
bugzilla.kernel.org who claimed that _only_ iommu=soft helped, but not
8 matches
Mail list logo
