Re: [2.6.35] AMD-Vi: Enabling IOMMU at 0000:00:00.2 cap 0x40 BUG: unable to handle kernel NULL pointer dereference at 0000000000000198

[Sander Eikelenboom]

Hello Joerg,

Had to apply the patch by hand, and found 2 typo's:

arch/x86/kernel/amd_iommu.c: In function âdo_attachâ:
arch/x86/kernel/amd_iommu.c:1456: error: implicit declaration of function âset_dte_enryâ
arch/x86/kernel/amd_iommu.c: In function âdo_detachâ:
arch/x86/kernel/amd_iommu.c:1486: error: implicit declaration of function âclear_dte_enryâ
make[2]: *** [arch/x86/kernel/amd_iommu.o] Error 1



Should be "entry" of course.

--

Sander
Wednesday, August 11, 2010, 12:24:19 AM, you wrote:

> On Tue, Aug 10, 2010 at 11:36:59PM +0200, Sander Eikelenboom wrote:
>> It boots now, dmesg attached.

> Ok, here is a quick and dirty patch wich should make your system boot
> again. It introduces other issues which will show up when you try to
> assign the devices to a virtual machine. But at least the devices should
> work again on bare-metal.

>         Joerg




-- 
Best regards,
 Sander                            mailto:linux@xxxxxxxxxxxxxx

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/