I do not have one of these in Westford. I have provided Florian instructions on downloading and installing a test kernel for his 7700. P.
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.
Re-assigning this to tcamuso. P.
ACK
Prarit, I think this might be related to the mmconf problem. The dc5700 is blacklisted in RHEL5, but the dc7700 is not. I'm not sure the dc7700 use the same chipset as the dc5700, but it's very likely to use it or one of the variants I've included in the device blacklist in the patch. Can I forward a patch or a patched kernel to Florian to try? Do you know if RHEL4 works on the dc7700? I don't see it blacklisted in RHEL4.
Hey Tony, this never got blacklisted because we (Westford) don't have a 7700 to test with. The failure, however, is *exactly* the same. P.
Oh -- I should also add that "pci=nommconf" fixed the boot problem on Florian's 7700 in Europe. Bottom line -- the code never went in.... P.
Thanks, Prarit. Now I'm more certain that the mmconf patch will fix the 7700.
Upstream patch of the kernel will not be using the blacklist, and the existing blacklist does not include dc7700. The workaround for dc7700 remains pci=nommconf in the boot command.
I will be submitting a patch upstream that will fix the dc7700 and dc5700 problem. Here is a description of the problem. Bus sizing code writes 0xffffffff to the BARs to determine how much space they require. The 82Q963/Q965 graphics controller in the dc5700 wants to map 256MB, so the most significant bit of the BAR at offset 0x18 is set to decode MMIO addresses with the MSB set. The BAR is a 64-bit BAR, and the upper 32-bits are probably 0, so once we write the BAR with 0xffffffff, the device claims all addresses in the range 0x00000000.f0000000 to 0x00000001.00000000 which happens to include the MMCONFIG range set up by the BIOS for the dc5700. At this point no more forward progress can be made, since all MMCONFIG references are being claimed and swallowed by the graphics chip. There are several ways to address this. 1. A BIOS fix that places the MMCONFIG region in 64-bit space safely above 00000001.00000000 and out of reach of the graphics chip. 2. A change to the linux bus sizing algorithm to write 0xffffffff to the upper dword of the 64-bit register before sizing the lower dword. 3. A change to the linux pci config access routines so that all references below offset 0x40 in pci config space are made with legacy pci config. Most of the participants on the lkml, including me, believe that option 3 is the best one, because it guarantees that BARs will always be configured using legacy pci config access. However, Graphics chips are very likely to claim ever larger pieces of memory space, so it is still possible for the problem to occur if sizing code places the base address of the graphics device's 256MB address range within reach of the MMCONFIG area mapped by the BIOS. In the long run, the safest bet is for BIOS to map the MMCONFIG region into memory space that is unlikely to be mapped by bus-sizing code. The patch I am going to submit was suggested by Ivan Shakaysky on the LKML. The patch will use legacy PCI config access for the first 64 bytes of offset in PCI config space. This means that the BARs will always be programmed by legacy PCI config and temporarily mapping them into MMCONFIG space while conducting bus-sizing will not hang the system.
in 2.6.18-72.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5
Greetings Red Hat Partner, A fix for this issue should be included in the latest packages contained in RHEL5.2-Snapshot1--available now on partners.redhat.com. Please test and confirm that your issue is fixed. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to ASSIGNED. If you are receiving this message in Issue Tracker, please reply with a message to Issue Tracker about your results and I will update bugzilla for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager. Thank you
Greetings Red Hat Partner, A fix for this issue should be included in the latest packages contained in RHEL5.2-Snapshot3--available now on partners.redhat.com. Please test and confirm that your issue is fixed. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to ASSIGNED. If you are receiving this message in Issue Tracker, please reply with a message to Issue Tracker about your results and I will update bugzilla for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager. Thank you
Greetings Red Hat Partner, A fix for this issue should be included in the latest packages contained in RHEL5.2-Snapshot4--available now on partners.redhat.com. Please test and confirm that your issue is fixed. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to ASSIGNED. If you are receiving this message in Issue Tracker, please reply with a message to Issue Tracker about your results and I will update bugzilla for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager. Thank you
Greetings Red Hat Partner, A fix for this issue should be included in the latest packages contained in RHEL5.2-Snapshot6--available now on partners.redhat.com. We are nearing GA for 5.2 so please test and confirm that your issue is fixed ASAP. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to ASSIGNED. If you are receiving this message in Issue Tracker, please reply with a message to Issue Tracker about your results and I will update bugzilla for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager. Thank you
Greetings Red Hat Partner, A fix for this issue should be included in the latest packages contained in RHEL5.2-Snapshot7--available now on partners.redhat.com. We are nearing GA for 5.2--this is the last opportunity to test and confirm that your issue is fixed. After you (Red Hat Partner) have verified that this issue has been addressed, please perform the following: 1) Change the *status* of this bug to VERIFIED. 2) Add *keyword* of PartnerVerified (leaving the existing keywords unmodified) If this issue is not fixed, please add a comment describing the most recent symptoms of the problem you are having and change the status of the bug to ASSIGNED. If you are receiving this message in Issue Tracker, please reply with a message to Issue Tracker about your results and I will update bugzilla for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager. Thank you
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/RHBA-2008-0314.html