| 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
| ||
|
Date: Tue, 10 Aug 2010 20:01:22 +0200 From: Joerg Roedel <joro@...tes.org> To: Sander Eikelenboom <linux@...elenboom.it> 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 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 -- 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