Bug#623594: closed by Ben Hutchings <email@example.com> (Re: Bug#623594: system freeze during boot with IOMMMU enabled)
On Thu, Apr 21, 2011 at 09:05:14PM +0200, Robin Axelsson wrote:
> On 2011-04-21 20:03, Debian Bug Tracking System wrote:
> >n Thu, Apr 21, 2011 at 05:41:29PM +0200, Robin Axelsson wrote:
> >>> Package: Debian-testing-amd64-DC-1.iso (latest version converted to boot
> >>> USB)
> >>> Severity: Critical
> >>> Platform: x86_64 Linux (also .386/i686)
> >>> > Description of problem:
> >>> Since I updated the firmware of my BIOS to a revision that supports AMD
> >>> IOMMU and turned that feature on, pretty much anything that runs
> >>> Linux fails to boot All I see about half a second after I pass the
> >>> GRUB bootloader is a blinking cursor in the upper left corner. The
> >>> mouse gets disabled (i.e. powered off in spite of being plugged in)
> >>> and the keyboard doesn't even respond to caps-lock, num-lock and
> >>> scroll-lock toggles (numlock light is constantly on).
> >>> > I assume that it is needless to say that this is a
> >>non-issue when
> >>> the IOMMU feature is disabled.
> >So there is a bug in the BIOS, and you have a workaround for it.
> >I don't see a bug in Debian.
> I don't understand your statement. IOMMU is a feature that allows
> for passthrough of I/O devices to virtual machines. I need this
> feature on my computer but Debian doesn't work with that feature.
Like many new hardware features, IOMMUs must be correctly described
by the BIOS before an operating system can use them.
> If this was due to a bug in the BIOS why the does it not crash
> Citrix Xenserver 5.6, Windows 7 x64 or even FreeDOS/MS-DOS?
Because they don't try to use the IOMMU.
We get into the habit of living before acquiring the habit of thinking.
- Albert Camus