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:

Is this on any system at all or on a particular type of system?  Moving to kernel since this is a host IOMMU bug.

2.6.32-329.el6.x86_64 boots fine on my system with intel_iommu=on, maybe something x2apic related?

I don't see attached console log.

Please also provide:
lspci, lspci -vvv, lspci -t output
dmesg log when no intel_iommu=on

Try a boot with 'intel_iommu=strict'

Created attachment 627914 [details]
host serial console log

(In reply to comment #4)
> I don't see attached console log.
I attached a console log.

> Please also provide:
> lspci, lspci -vvv, lspci -t output
> dmesg log when no intel_iommu=on
> 
This log file include lspci, lspci -vvv, lspci -t output and dmesg information.

> Try a boot with 'intel_iommu=strict'

host boot successfully and work well.

Created attachment 627916 [details]
lspci and dmesg log

Talked to the reporter, the reporter filed the two same( bz865666 and bz865665) bug by mistaking. Close one

*** This bug has been marked as a duplicate of bug 865666 ***