| 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
| ||
|
Message-ID: <CALfB72A+A9UDieFtYOMLB9c+XHO8nt8Lr-2pkikaqM=0fJ4OAQ@mail.gmail.com> Date: Thu, 19 Jan 2012 10:57:57 +0200 From: Albert Strasheim <fullung@...il.com> To: Roland Dreier <roland@...estorage.com> Cc: linux-rdma@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>, David Woodhouse <dwmw2@...radead.org> Subject: Re: kernel BUG at drivers/iommu/intel-iommu.c:1767 on F16 3.1.1-2.fc16.x86_64 Hello again On Tue, Dec 20, 2011 at 12:47 PM, Albert Strasheim <fullung@...il.com> wrote: > Any news on this one? > Regards > Albert > On Thu, Dec 8, 2011 at 8:31 PM, Albert Strasheim <fullung@...il.com> wrote: >> On Thu, Dec 8, 2011 at 8:29 PM, Roland Dreier <roland@...estorage.com> wrote: >>> On Thu, Dec 8, 2011 at 9:56 AM, Albert Strasheim <fullung@...il.com> wrote: >>>> I think the BIOS has VT-d enabled. dmesg says: >>>> PCI-DMA: Intel(R) Virtualization Technology for Directed I/O >>> Yes, you're crashing in the VT-d code. >>> If you don't care about that, you can boot with the kernel parameter >>> "intel_iommu=off" >>> as a workaround, but it would be nice to get to the bottom of this. >> I'm happy to test any patches or provide more information. Just checking up on this issue. Is there any further testing or information we can provide to help make a fix happen? Regards Albert -- 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