Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
As subject. and cann't get useful infomation from monitor. I attached host serial console log.
Hit this issue with kernel-2.6.32-328.el6、kernel-2.6.32-320.el6 and kernel-2.6.32-325.el6.
For kernel-2.6.32-279.el6(GA kernel), It works well and haven't hit this issue.
Since kvm QE have tested device assignment and don't hit this issue on rhel6.3 GA
so add 'regression' keywords.
Currently, kvm QE want to test 'device assignment' with the latest kernel, because this bug we cann't continue. so add 'blocker' flags.
Version-Release number of selected component (if applicable):
host kernel:
kernel-2.6.32-328.el6
kernel-2.6.32-320.el6
kernel-2.6.32-325.el6.
How reproducible:
100%
Steps to Reproduce:
1.boot system with kernel parameter intel_iommu=on
2.
3.
Actual results:
boot fail, and monitor cann't get useful infomation.
Expected results:
boot successfully.
Additional info:
Comment 5Don Dutile (Red Hat)
2012-10-16 17:54:30 UTC
(In reply to comment #3)
> This bug and bug 861361 are different.
They both have the same set of DMAR faults for the same 02:00.0/i915 device.
How are they different? Please be very specific how you think they are different.
(In reply to comment #5)
> (In reply to comment #3)
> > This bug and bug 861361 are different.
>
> They both have the same set of DMAR faults for the same 02:00.0/i915 device.
> How are they different? Please be very specific how you think they are
> different.
I think main difference that bug 861361 hit kernel panic with kernel 2.6.32-279.e16.x86_64. This kernel version works well in our testing result.
okay found the problem in the backport of the kernel patches, a config option changed name upstream DMAR->INTEL_IOMMU and I didn't flag it during the rebase.
Patch on its way to rhkernel-list.
Comment 11RHEL Program Management
2012-10-17 04:10:34 UTC
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release. Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
Comment 14Don Dutile (Red Hat)
2012-10-17 14:16:03 UTC
(In reply to comment #3)
> This bug and bug 861361 are different.
My apologies, I thought the above statement was referring to 865665.
So, it appears that 865665 is a dupe of this bug. if so, please close as duplicate.
verify this issue with kernel 2.6.32-335.el6.x86_64
1. boot host with intel_iommu=on
2. boot guest with PF
result:
host and guest work well. and not found any error message.
base on testing result above. I think this bug is fixed.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2013-0496.html