[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1498209076.20100810233659@eikelenboom.it>
Date: Tue, 10 Aug 2010 23:36:59 +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
It boots now, dmesg attached.
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
Download attachment "dmesg-amd-iommu-patched" of type "application/octet-stream" (96314 bytes)
Powered by blists - more mailing lists