mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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: Tue, 10 Aug 2010 23:48:55 +0200	[thread overview]
Message-ID: <1344272543.20100810234855@eikelenboom.it> (raw)
In-Reply-To: <20100810212551.GU23755@8bytes.org>

Hi Joerg,

Ok it boots ok now, but plugging in a USB device in the 2.0 controller (0a.01.*) results in a flood of error messages about the usb controller not functioning.
When running same kernel with amd_iommu=off results in ...the device at least registering properly as usb device (altough trying to use it now resulted in an entirely new oops probably in the driver of the videograbber.)

--
Sander

Tuesday, August 10, 2010, 11:25:51 PM, you wrote:

> On Tue, Aug 10, 2010 at 10:57:26PM +0200, Sander Eikelenboom wrote:
>> Hmmm the fun part seems to be .. that the usb devices on that usb2
>> controller seemed to work fine on Xen.

> Hmm, thats weird. In this case these devices probably do not alias at
> all. But lets wait for the results when you test my patch.


>>            +-0a.0-[0000:09-0a]----00.0-[0000:0a]--+-01.0
>>            |                                      +-01.1
>>            |                                      \-01.2

> Yeah, device 09:00.0 is a PCIe-to-PCI bridge and the addtional USB
> controlers are behind that bridge as legacy PCI devices. Thats why the
> BIOS sets up the alias-entry. It should set up 09:00.0 instead of
> 0a:00.0 to make things work correctly.

>         Joerg




-- 
Best regards,
 Sander                            mailto:linux@eikelenboom.it


  reply	other threads:[~2010-08-10 21:49 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   ` 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 [this message]
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=1344272543.20100810234855@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

all inboxes | Powered by JetHome®