public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Sander Eikelenboom <linux@eikelenboom.it>
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: Tue, 10 Aug 2010 22:28:39 +0200	[thread overview]
Message-ID: <20100810202839.GS23755@8bytes.org> (raw)
In-Reply-To: <1609756756.20100810200514@eikelenboom.it>

[-- Attachment #1: Type: text/plain, Size: 712 bytes --]

On Tue, Aug 10, 2010 at 08:05:14PM +0200, Sander Eikelenboom wrote:
> Could you also provide a perhaps more specific message what is wrong
> with the bios, that i could forward to MSI, in the hope it will reach
> the bios engineers someday ? :-)

Lets first prove that my theory is right before contacting MSI directly.
Can you try the attached patch? it should fix the boot-crash. When the
system booted successfully please try some USB device (make sure it uses
the seperate usb-controler, I guess the seperate device is responsible
for USB 3, so try to plug a device into one of your USB 3 ports).
If you finished that please send me whether it worked or not and the
full dmesg output of the system.

	Joerg


[-- Attachment #2: iommu-crash-fix.diff --]
[-- Type: text/x-diff, Size: 415 bytes --]

diff --git a/arch/x86/kernel/amd_iommu.c b/arch/x86/kernel/amd_iommu.c
index 0d20286..6b4fb05 100644
--- a/arch/x86/kernel/amd_iommu.c
+++ b/arch/x86/kernel/amd_iommu.c
@@ -153,6 +153,8 @@ static int iommu_init_device(struct device *dev)
 	pdev = pci_get_bus_and_slot(PCI_BUS(alias), alias & 0xff);
 	if (pdev)
 		dev_data->alias = &pdev->dev;
+	else
+		dev_data->alias = dev;
 
 	atomic_set(&dev_data->bind, 0);
 

  reply	other threads:[~2010-08-10 20:28 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 [this message]
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

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=20100810202839.GS23755@8bytes.org \
    --to=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@eikelenboom.it \
    /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