linux-kernel - 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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1893257730.20100810225726@eikelenboom.it>
Date:	Tue, 10 Aug 2010 22:57:26 +0200
From:	Sander Eikelenboom <linux@...elenboom.it>
To:	Joerg Roedel <joro@...tes.org>
CC:	linux-kernel@...r.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

Hmmm the fun part seems to be .. that the usb devices on that usb2 controller seemed to work fine on Xen.
And i have some problems about xen not willing to passthrough things with the usb3 controllers (supposedly due to the (extra) bridges),
that are the controllers on 04:00.0 and 08:00.0

-[0000:00]-+-00.0
           +-00.2
           +-02.0-[0000:0d]--+-00.0
           |                 \-00.1
           +-05.0-[0000:0c]----00.0
           +-06.0-[0000:0b]----00.0
           +-0a.0-[0000:09-0a]----00.0-[0000:0a]--+-01.0
           |                                      +-01.1
           |                                      \-01.2
           +-0b.0-[0000:05-08]----00.0-[0000:06-08]--+-01.0-[0000:08]----00.0
           |                                         \-02.0-[0000:07]----00.0
           +-0d.0-[0000:04]----00.0
           +-11.0
           +-12.0
           +-12.2
           +-13.0
           +-13.2
           +-14.0
           +-14.3
           +-14.4-[0000:03]----06.0
           +-14.5
           +-15.0-[0000:02]--
           +-16.0
           +-16.2
           +-18.0
           +-18.1
           +-18.2
           +-18.3
           \-18.4

I had hoped things would become easier/better with my new mobo including iommu :-)
Doesn't seem that way yet. Previously i had 2 usb2.0 controllers(1x pci 1x pci-e) and 1 usb3.0(pci-e) passed through (with xen-swiotlb and no hardware iommu).. and that worked fine grabbing video 24/7 for several weeks.


But lets hope for the best :-)

--
Sander




Tuesday, August 10, 2010, 10:47:21 PM, you wrote:

> Hi Sander,

> On Tue, Aug 10, 2010 at 10:36:35PM +0200, Sander Eikelenboom wrote:
>> Errr which seperate usb controller ? .. it has actually:
>> - 1 pci-e usb 2.0 controller
>> - 2 pci-e usb 3.0 controller (one of which includes a sata controller as well)

> The devices should be attached to this controler:

> 0a:01.0 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) (prog-if 10 [OHCI])
> 0a:01.1 USB Controller [0c03]: NEC Corporation USB [1033:0035] (rev 43) (prog-if 10 [OHCI])
> 0a:01.2 USB Controller [0c03]: NEC Corporation USB 2.0 [1033:00e0] (rev 04) (prog-if 20 [EHCI])

> The PCI devices associated with that controler alias to 0a:00.0 which
> does not exist in your system (hence the crash). And the fact that these
> devices have an alias makes me believe that the BIOS detects them as
> legacy PCI devices. PCI-e does typically not has aliases. Can you send
> lcpi -t output to see to which upstream bridge these devices are
> connected to?

>         Joerg




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

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