Launchpad has imported 33 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=605888.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
I believe I'm also suffering from this issue; however, I've found a
workaround: boot the kernel with the iommu=pt parameter. From what I can
tell, this allows the iommu to function in the presence of an NVidia
graphics card.
--
You received this bug notification because you are a member of
Ubuntu beta2 lastest 3.0.2.21 and pre3.0.2.22 still the same problem
The screen goes black, no login screen and after 30 seconds, able to
swich to tty
Solution by now: disable iommu on my GA-990FXA-UD3 motherboard bios
Not a solution at all if i want to continue using pci pastrough and etc
--
so i finally get a computer with an IOMMU switch in BIOS, but turning it on
causes ubuntu to go to sleep at boot.
things go wrong between plymouth and lightdm.
the only way out is [SYSRQ]+R,E,I,S,U,B or cutting the power.
--
You received this bug notification because you are a member of Ubuntu
Thanks for the testing, much appreciated. I intend to apply this
alternative solution and upload shortly. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894070
Title:
IOMMU error loop
Hi,
I've built an alternative test kernel which reverts the out of tree
patch we applied and instead disables CONFIG_INTEL_IOMMU_DEFAULT_ON.
Could you please test this kernel and let me know your results, ie.
confirm the loop of DMAR error messages do not reappear. Thanks in
advance.
@Leann: no loop, no excessive DMAR messages being issued:
[cerdea-aws]cerdea@xango3$ cat /proc/version_signature
Ubuntu 3.2.0-9.17~lp894070v1-generic 3.2.1
[cerdea-aws]cerdea@xango3$ dmesg|grep DMAR
[0.00] ACPI: DMAR cf34ff18 00080 (v01 INTEL CP_DALE 0001
INTL 0001)
[
** Branch linked: lp:ubuntu/linux-ti-omap4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894070
Title:
IOMMU error loop early in boot
To manage notifications about this bug go to:
This bug was fixed in the package linux - 3.2.0-4.10
---
linux (3.2.0-4.10) precise; urgency=low
[ Kyle McMartin ]
* SAUCE: dmar: disable if ricoh multifunction detected
- LP: #894070
[ Seth Forshee ]
* SAUCE: dell-wmi: Demote unknown WMI event message to pr_debug
** Changed in: linux (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894070
Title:
IOMMU error loop early in boot
To manage notifications about this
Well job! works fine on i7-950/ASUS P6X58D-E and GTX-260.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894070
Title:
IOMMU error loop early in boot
To manage notifications about this bug go to:
** Tags added: rls-p-tracking
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Leann Ogasawara (leannogasawara)
** Changed in: linux (Ubuntu)
Milestone: None = precise-alpha-2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags removed: kernel-da-key kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894070
Title:
IOMMU error loop early in boot
To manage notifications about this bug go to:
Hi Carlos,
I'm going to do some bisecting to identify when the bug was introduced.
Before starting, could you test the 3.2.0-2.5 kernel just to see if it
happens to be fixed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(for the record, already answered on IRC)
Tested, still fails. Interesting that the RH bugs talk about VT-d. I do
not remember if this laptop BIOS has VT-d as an option (I am sure it has
a VT, probably VT-x). OTOH, it can be argued if the options displayed on
BIOS have a direct relation with
Hi Carlos,
Can you also confirm that this was not an issue with the the Ubuntu
3.1.0-1.3 kernel? That way we have a starting point for the bisect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In my prior comment I meant the 3.1.0-2.3 kernel:
https://launchpad.net/ubuntu/+source/linux/3.1.0-2.3/+build/2885386
I would also like to have you test a couple of mainline kernels, to rule
out an Ubuntu patch as a cause. Can you test with the upstream v3.1
kernel and upstream v3.2-rc2 kernel?
1. Ubuntu 3.1.0-2.3 -- works. This is the last 3.1 kernel I installed on this
machine
2. Mainline 3.2-rc1 -- works
3. Mainline 3.2-rc2 -- works.
OTOH I lost wireless on the 3.2 mainline.
Still to test 3.1 mainline
--
You received this bug notification because you are a member of Ubuntu
Bugs,
04:00.0 maps to your sd reader. The mainline kernels were using older
configs, and 3.2 in precise enabled CONFIG_MEMSTICK_R592 which hggdh's
SD reader device on 04:00.0 is using. It looks like this patch may fix
it.
Test kernel with that patch applied. What it does is disable intel_iommu
when it finds one of the 4 ricoh devices because it leads to problems
like this.
http://kernel.ubuntu.com/~sarvatt/lp894070/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
git commit that caused issue:
fe763ab898670195870b889e145483ce5c8997d5 UBUNTU: [Config] CONFIG_MEMSTICK_R592=m
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894070
Title:
IOMMU error loop early in
Sarvatt's test kernel works. We have a deal :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894070
Title:
IOMMU error loop early in boot
To manage notifications about this bug go to:
Just adding upstream thread for additional information.
https://lkml.org/lkml/2010/5/22/69
For now I suggest you continue to use the workaround of
'intel_iommu=off' until we are able to investigate further.
** Bug watch added: Red Hat Bugzilla #605888
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894070
Title:
IOMMU error loop early in boot
To manage notifications about this bug go to:
** Attachment added: snapshot of the error
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/894070/+attachment/2606186/+files/IMG_2022_140534.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894070
Title:
IOMMU error loop early in boot
To manage notifications about this bug go
** Attachment added: short video of boot console
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/894070/+attachment/2606188/+files/VID_2021_151323.3gp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
** Tags added: kernel-da-key
** Changed in: linux (Ubuntu)
Importance: Medium = High
** Tags added: kernel-key
--
You received this bug notification because you
Hi Carlos,
I've added this bug to the kernel team hotlist:
http://reports.qa.ubuntu.com/reports/kernel-bugs/reports/_kernel_hot_.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894070
Title:
29 matches
Mail list logo
