Bug 1008958
Summary: | Enabling VT-D in BIOS and intel_iommu=on floods dmesg logs with DMAR faults | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Daniel Berrangé <berrange> |
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | alex.williamson, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, marcelo.barbosa, skottler |
Target Milestone: | --- | Flags: | jforbes:
needinfo?
|
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-03-10 14:45:22 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Attachments: |
Description
Daniel Berrangé
2013-09-17 12:03:35 UTC
Created attachment 798771 [details]
dmesg from successful boot with firewire device disabled in bios and intel_iommu=on set
Created attachment 798778 [details]
lspci -vv when firewire is enabled in BIOS, which results in unbootable machine with intel_iommu=on
Created attachment 798783 [details]
lspci -vv after disabling firewire in BIOS which allows intel_iommu=on to boot successfully
We used to carry a patch called dmar-disable-when-ricoh-multifunction.patch for this issue. According to bug 880051 it should have no longer been needed and was dropped some time ago. Alex, do you know if there are quirks upstream that should handle the issue that Daniel has reported? *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. (In reply to Josh Boyer from comment #4) > We used to carry a patch called dmar-disable-when-ricoh-multifunction.patch > for this issue. According to bug 880051 it should have no longer been > needed and was dropped some time ago. > > Alex, do you know if there are quirks upstream that should handle the issue > that Daniel has reported? No, the patch mentioned in bug 880051 comment 3 makes the IOMMU groups for broken Ricoh devices work. That solves the problem for things like VFIO which makes use of IOMMU groups. DMA ops does not yet do that. The long term solution for DMA ops is something like the requester ID interface that I've proposed, but hasn't made it past the RFC stage. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.12.6-200.fc19. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20. If you experience different issues, please open a new bug report for those. *********** MASS BUG UPDATE ************** This bug has been in a needinfo state for more than 1 month and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 19, please feel free to reopen the bug and provide the additional information requested. |