Description of problem: When booting some of the newer systems that have longer running SMI routines (for USB legacy keyboard emulation). The system may panic with the message: Kernel panic - not syncing: IO-APIC + timer doesn't work! Try using 'noapic' kernel parameter. This is caused by SMI's occuring and stealing CPU cycles when the kernel is attempting to calibrate the Bogomips (i.e. loops_per_jiffy) value. Version-Release number of selected component (if applicable): RHEL4 (GOLD,U1,U2,U3 beta) How reproducible: Very intermittent. Can be exasperated by typing on USB keyboard during boot. Steps to Reproduce: 1. Reboot a system that uses SMI's (E.g. Dell PE6800) 2. Type on USB keyboard and/or place in reboot loop 3. repeat until failure. Actual results: System panics on boot. Expected results: No panic. Additional info:
Created attachment 123453 [details] Patch to resolve issue.
Raising priority to high based on Dell's U4 consideration.
Engineering asks if we can we make this bug PUBLIC.
Do not see anything that should prevent this from being a public bug. Please go ahead and make it public.
This issue is on Red Hat Engineering's list of planned work items for the upcoming Red Hat Enterprise Linux 4.4 release. Engineering resources have been assigned and barring unforeseen circumstances, Red Hat intends to include this item in the 4.4 release.
Robert, any upstream status on this issue? Move to U5 prop list.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this enhancement by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This enhancement is not yet committed for inclusion in an Update release.
Pinged Robert and asked for upstream status on the proposed patch (comment #14). Setting status to NEEDINFO waiting Robert's response.
The suggested patch is not upstream.
Unfortunately, this issue was unable to be addressed in RHEL4.5 due to the patch not being accepted upstream. We've moved it onto the list for RHEL4.6, but at last check the patch was still not upstream. Can Dell update us on the upstream status of this patch? Internal Status set to 'Waiting on Customer' Status set to: Waiting on Client This event sent from IssueTracker by gcase issue 86418
Unfortunately, this issue was unable to be addressed in RHEL4.5 due to the patch not being accepted upstream. We've moved it onto the list for RHEL4.6, but at last check the patch was still not upstream. Can Dell update us on the upstream status of this patch?
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
NAK on this request for R4.6 with proposed patch in comment #1. Submitter should review the problem and submit a backport of an upstream patch.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.