[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1609756756.20100810200514@eikelenboom.it>
Date: Tue, 10 Aug 2010 20:05:14 +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
Hello Joerg,
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 ? :-)
--
Sander
Tuesday, August 10, 2010, 8:01:22 PM, you wrote:
> On Tue, Aug 10, 2010 at 06:57:45PM +0200, Sander Eikelenboom wrote:
>> The requested info is attached.
>> So that would mean a bios problem ? (those are not on my wishlist :-p)
> Yeah, looks like a BIOS problem. But the driver should handle that
> without crashing the system, so there is a bug in the driver too.
> Problem is:
> AMD-Vi: DEV_ALIAS_RANGE devid: 0a:01.0 flags: 00 devid_to: 0a:00.0
> AMD-Vi: DEV_RANGE_END devid: 0a:1f.7
> This means that PCI devices from 0a:01.0 to 0a:1f.7 may use their own
> device-id or 0a:00.0. But a device which id 0a:00.0 is not present in
> the system. From the lspci output this looks like your USB3 controler
> should alias to 09:00.0. I prepare a patch for you to fix the crash but
> I can't guarantee that your USB3 controler will work afterwards. If you
> see IO-Page-Faults please report them to me.
> 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/
Powered by blists - more mailing lists