Bug 801501

Summary: Unable to reset IRR for apic: 5, pin :0-255
Product: [Fedora] Fedora Reporter: Jon Dufresne <jon.dufresne>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, midgoon
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: kernel-3.2.10-3.fc16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-11 16:52:52 UTC Type: ---
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 Flags
dmesg apic=verbose none

Description Jon Dufresne 2012-03-08 17:17:12 UTC
Created attachment 568701 [details]
dmesg apic=verbose

Description of problem:
I receive the following message on boot:

Unable to reset IRR for apic: 5, pin :0
Unable to reset IRR for apic: 5, pin :1
...
Unable to reset IRR for apic: 5, pin :255


Version-Release number of selected component (if applicable):
kernel-2.6.42.9-1.fc15.x86_64

How reproducible:
100%. Every boot. Interrupts normal plymouth splash.

Steps to Reproduce:
1. Boot
  
Actual results:
Receive message.

Expected results:
Receive no message. Plymouth is displayed uninterrupted.

Additional info:
Attaching dmesg with "apic=verbose" boot.

Comment 1 Josh Boyer 2012-03-09 14:19:33 UTC
This looks similar to bug 784445.  Do you know which kernel this started with?

Comment 2 Josh Boyer 2012-03-09 14:36:16 UTC
Could you test the kernel from this scratch build when it completes?

http://koji.fedoraproject.org/koji/taskinfo?taskID=3872921

Comment 3 Jon Dufresne 2012-03-09 23:17:40 UTC
> Do you know which kernel this started with?

Sorry I do not. At least a month ago.

> Could you test the kernel from this scratch build when it completes?

I receive no messages with the kernel. Looks good :)

Comment 4 Josh Boyer 2012-03-12 13:20:17 UTC
Thank you for testing.  We'll get this into the next official update.

Comment 5 Fedora Update System 2012-03-13 11:35:20 UTC
kernel-3.2.10-1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/kernel-3.2.10-1.fc16

Comment 6 Josh Boyer 2012-03-13 14:12:04 UTC
*** Bug 784445 has been marked as a duplicate of this bug. ***

Comment 7 Fedora Update System 2012-03-13 15:59:55 UTC
kernel-2.6.42.10-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/kernel-2.6.42.10-1.fc15

Comment 8 Fedora Update System 2012-03-15 02:21:52 UTC
Package kernel-3.2.10-1.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-3.2.10-1.fc16'
as soon as you are able to, then reboot.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-3712/kernel-3.2.10-1.fc16
then log in and leave karma (feedback).

Comment 9 Fedora Update System 2012-03-17 23:58:05 UTC
kernel-3.2.10-3.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 10 Fedora Update System 2012-03-26 04:02:00 UTC
kernel-2.6.42.12-1.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Fedora Update System 2012-03-26 18:01:30 UTC
kernel-2.6.42.12-1.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Jon Dufresne 2012-05-11 01:14:53 UTC
After a recent update this bug has returned.

Comment 13 Josh Boyer 2012-06-07 17:56:36 UTC
Which update?  Are you seeing it with 2.6.43/3.3?

Comment 14 Jon Dufresne 2012-06-11 16:52:52 UTC
> Which update?  Are you seeing it with 2.6.43/3.3?

I recently upgraded the entire OS to Fedora 17 and am not longer seeing this. Closing.