From: Sander Eikelenboom <linux@eikelenboom.it>
To: Joerg Roedel <joro@8bytes.org>
Cc: linux-kernel@vger.kernel.org
Subject: 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
Date: Wed, 11 Aug 2010 19:54:44 +0200 [thread overview]
Message-ID: <876929344.20100811195444@eikelenboom.it> (raw)
In-Reply-To: <20100810222419.GW23755@8bytes.org>
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@eikelenboom.it
prev parent reply other threads:[~2010-08-11 17:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1154489525.20100810164850@eikelenboom.it>
[not found] ` <20100810162606.GQ23755@8bytes.org>
2010-08-10 16:57 ` [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
2010-08-10 18:01 ` Joerg Roedel
2010-08-10 18:05 ` Sander Eikelenboom
2010-08-10 20:28 ` Joerg Roedel
2010-08-10 20:36 ` Sander Eikelenboom
2010-08-10 20:47 ` Joerg Roedel
2010-08-10 20:57 ` Sander Eikelenboom
2010-08-10 21:25 ` Joerg Roedel
2010-08-10 21:48 ` Sander Eikelenboom
2010-08-10 21:36 ` Sander Eikelenboom
2010-08-10 22:02 ` Joerg Roedel
2010-08-10 22:24 ` Joerg Roedel
2010-08-11 17:54 ` Sander Eikelenboom [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=876929344.20100811195444@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox