Bug 152199
Summary: | agpgart-serverworks fail on hp netserver lc 2000 | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Karl Latiss <karl+rhbugzilla> | ||||
Component: | kernel | Assignee: | Dave Jones <davej> | ||||
Status: | CLOSED NEXTRELEASE | QA Contact: | Brian Brock <bbrock> | ||||
Severity: | low | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 4.0 | CC: | dravet, jbaron, pfrields, riel | ||||
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: | 2005-09-30 08:49: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
Karl Latiss
2005-03-26 01:06:16 UTC
one of your host bridges must have AGP capabilities (lspci -vvv will tell you), even if the box physically has no slots. It's a little difficult to detect this situation unfortunatly. I'll see if I can hardcode a check for that particular failure in the serverworks driver, and silence the warnings.. lspci -vvv (attached) indeed does show agp capabilities and in fact the onboard card reports itself as an agp card. Who would have thunk! That being the case I wonder why I see the errors then? Created attachment 112383 [details]
output of lspci -vvv
This is a duplicate of bug 124593 which was closed earlier. This problem has been around since FC2. This bug is in FC3 and RHEL 3 too. the lack of specs on this chipset make it pretty much impossible to come up with any workaround. Silencing the warning is actually quite invasive too, as it involves interpreting return codes across two modules in a generic routine. The warning is however totally harmless, so for rhel4, I'm not going to change this, for fear of breaking any working setups (as well as undocumented, that driver is quite fragile in parts) Hopefully at some point I'll come up with something upstream that will be done in time for rhel5. |