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
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
Package: kernel
Severity: critical
Justification: causes serious data loss
Hi everybody.
I'm currently (together with others) investigating in a severe data
corruption problem that at least many users might suffer from.
A short description, when you validate lots of GBs over and over with
501 - 503 of 503 matches
Mail list logo
