<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">Hi Ben, <blockquote type="cite">I mentioned the HD 5450 purely as a matter of archeological interest. </blockquote> Ok, in that case looking at the lspci -tv output doesn't tell us anything new. <blockquote type="cite">I suspected, but couldn't prove, that the problem might have something to do with the bridge (IBM POWER8 Host Bridge (PHB3)). </blockquote> In that case you would see the problem with the caicos as well. Or are there issues random enough that there could actually be some problem with the caicos as well and we haven't noticed it so far? See it is really really odd that this should only happen with the cedar. On the other hand if it works for now, I don't see much issue having this workaround. Regards, Christian. Am 23.02.2018 um 17:02 schrieb Ben Crocker: </div> <blockquote type="cite" cite="mid:CALk+eRccKjoYv29E4wphbLb4ib6r6w6ThxSZ9gf86GH2DyMQ_Q@mail.gmail.com"> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <div dir="ltr">Hi Christian, Michel, Alex, et al., I mentioned the HD 5450 purely as a matter of archeological interest. Back to the FirePro 2270 and Embedded Radeon E6465: I've attached text from both "lspci -tv" and "lspci -v." Actually I'm attaching a couple of different "lspci -v" outputs, one with the FirePro 2270 in place and one with the E6465 in (the same) place. I suspected, but couldn't prove, that the problem might have something to do with the bridge (IBM POWER8 Host Bridge (PHB3)). But I want to reiterate: <ul> <li>Cedar GPU -> problem (before patch, that is);</li> <li>Caicos GPU in the same slot -> no problem</li> </ul> -- Ben P.S. Alex, thanks for applying the patch so expeditiously! </div> <div class="gmail_extra"> <div class="gmail_quote">On Fri, Feb 23, 2018 at 2:45 AM, Christian König <<a href="mailto:ckoenig.leichtzumerken@gmail.com" target="_blank" moz-do-not-send="true">ckoenig.leichtzumerken@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Am 22.02.2018 um 18:56 schrieb Michel Dänzer: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> On 2018-02-22 06:37 PM, Ben Crocker wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> One of my colleagues did discover a "Radeon HG 5450 PCI" from February 2010 which did, apparently, have a Cedar GPU and very definitely had a (plain old) PCI connector. </blockquote> There must be a PCIe-to-PCI bridge on that board. The GPU itself is always PCIe, and treated accordingly by the driver. </blockquote> Ben, just an educated guess but is this one the one which is failing to work correctly? Cause the PCIe bus interface is pretty much identical over all generations of the last decade or so. Only the newest Vega10 generation is a bit different. So I strongly thing that this isn't related to the device being a Cedar at all, but rather that you have a bridge above it which doesn't correctly handle 64bit transfers. Can you please send and "lspci -t" of both the working and the problematic devices? Thanks, Christian. </blockquote> </div> </div> </blockquote> </body> </html>