Bug 16462
Summary: | Kernel does not correctly set IOAPIC interrupt types | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | John William <jw2357> |
Component: | kernel | Assignee: | Michael K. Johnson <johnsonm> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-08-17 17:59:08 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: |
Description
John William
2000-08-17 17:59:07 UTC
We depend on the bios tables. If they are wrong we cant do a lot about it. You can override bits of the apic configuration but if the bios is wrong I think noapic is way safer As to the other comment. Some combinations of edge trigger devices can be used together. Not many but enough I'd be reluctant to second guess vendor info that on most boards is *very* good data. Well something should be done to fix this. Otherwise, every HP Vectra XU 5/90 SMP in existence won't boot the standard RedHat distro if something is installed in one of the PCI slots. I can tell you the "solution" (noapic) isn't immediately obvious either. Getting the out-of-the box RH6.2 running on one of these machines is difficult enough because of the AM53C974 SCSI controller but the "noapic" thing can really throw someone for a loop. I hate to bring up the comparison, but there must be a solution because NT 4.0 dual-boots fine on the same machine with the same hardware that causes RH6.2 to crash-and-burn. Maybe another way to look at the problem might be: are there any consequences to forcing LEVEL on a PCI interrupt? Particularly a shared one? Or is the performance hit of "noapic" not enough to worry about so I should let the whole thing go? |