On 01/05/2012 11:24 PM, Stephen Shaw wrote:
On Wed, Jan 4, 2012 at 16:33, Cristian Rodríguez
wrote: On 04/01/12 20:29, Ruediger Oertel wrote:
yep, disabling VT-d ("directed I/O" sounds pretty close to iommu to me)
That's why I asked.. ;)
did help, after having that setting disabled in BIOS the kernel runs without any extra options.
Either BIOSes are screwed or the kernel is, I actually think both ;-(
THis is probably worth a bug report.
I have the same issue on my w520. The w520 has the nvidia optimus, so both intel and nvidia. If I set it to have both video cards enabled I don't have this issue, but if I set it to nvidia I see the problem. Turning off VT-d and enabling nvidia doesn't reproduce this issue.
-Stephen
Same here with a Dell M4600 precision (after reading this threads I get hope to be able to run 3.2) I believe more in a regression inside the kernel, knowing that 3.1 was working without any trouble. At least I'm running only with the nvidia, but the trouble exist with nouveau and nvidia blob (even new 295.06) I've added manually iommu_intel=on on my bootline time ago, I will now remove it. ps for Christian Rodriguez, sorry I will never kill my nvidia chipset, and replace it by the intel one. except if I goes to a kernel hacker summit. I'm a big addicted of wobbling windows, and nouveau can't do it ... :D -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org