Unfortunately, I have to leave now for the weekend and will be able to
restart testing on monday.
Nevertheless, I've booted the latest precise kernel without
intel_iommu=off to verify that the bug still persists:
root@faui49i:~# uname -a
Linux faui49i 3.2.0-17-generic #26-Ubuntu SMP Fri Feb 17 21:35:49 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
root@faui49i:~# uptime
19:27:55 up 24 min, 1 user, load average: 0.00, 0.01, 0.06
So it *seems* the bug does no longer happen, but I really need to keep
the machine running for a longer amount of time to be sure.
Nevertheless, the conclusio of bug #907377 was to disable INTEL_IOMMU by
default AFAIUI the changelog:
* Revert "SAUCE: dmar: disable if ricoh multifunction detected"
* [Config] Disable CONFIG_INTEL_IOMMU_DEFAULT_ON
- LP: #907377, #911236
* [Config] Enable CONFIG_IRQ_REMAP
Therefore, I believe that the option intel_iommu=off is now used by
default. Will this option be kept for precise release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914161
Title:
Linux 3.2 freezes system on FUJITSU ESPRIMO P7935
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/914161/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
