Bug 172334
| Summary: | Invalid message 'Aieee!!! Remote IRR still set after unlock' | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 3 | Reporter: | Issue Tracker <tao> | ||||||
| Component: | kernel | Assignee: | Neil Horman <nhorman> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 3.0 | CC: | lwang, petrides, tao | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | RHSA-2006-0144 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2006-03-15 16:50:14 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 168424 | ||||||||
| Attachments: |
|
||||||||
|
Description
Issue Tracker
2005-11-02 21:45:06 UTC
Created attachment 120662 [details]
backport of RHEL4 patch to remove printk on read of undefined ioapic bit in level trigger mode
This is a backport of the RHEL4 patch for this printk on the incorrect reading
of the IRR bit when the apic is servicing a level triggered interrupt
Thanks for porting the rhel4 patch to address this in the i386 portion of rhel3. Will it also be appropriate to remove this piece of the code from the x86_64 file (linux-2.4.21/arch/x86_64/kernel/io_apic.c) ? A fix for this problem has just been committed to the RHEL3 U7 patch pool this evening (in kernel version 2.4.21-37.9.EL). Per c#5 are we making the same change in the x86_64 source ? Thanks. Created attachment 121325 [details]
patch committed to RHEL3 U7 last week
Yes. I've attached the patch that was committed.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2006-0144.html |