Bug #12387


X11 fails for certain Ryzen CPUs

Added by Gary Mills about 2 years ago. Updated over 1 year ago.

driver - device drivers
Start date:
Due date:
% Done:


Estimated time:
Gerrit CR:


When I upgrade from OI hipster-20191229 to OI hipster-20200212 and boot the new BE, I get an X11 hang on the console. The Xorg.0.log file ends like this:

        ARUBA, ARUBA
    [    72.142] (II) VESA: driver for VESA chipsets: vesa
    [    72.142] (++) using VT number 7

This system has an ASUS PRIME B350M-A motherboard. This board contains hardware for an on-CPU GPU because some Ryzen CPUs have built-in graphics. However, I'm using an AMD Ryzen 3 1200 CPU which does not have built-in graphics. This CPU requires an external graphics card. Other Ryzen CPUs also have this requirement. For this, I'm using a Radeon HD 7450 PCIe video card. The frame buffer device (/dev/fb) shows up like this:


I built debugging versions of the pcie and pcieb drivers from the latest illumos source and installed them in the new BE. In /etc/system, I've enabled full debugging in this manner:

    * Enable driver debugging
    set pcie:pcie_debug_flags = 1
    set pcieb:pcieb_dbg_print = 1
    set pcieb:pcieb_dbg_intr_print = 1

As far as I can tell, the kernel correctly identifies the video card. I've attached output from the serial console, as file cons.txt, to this bug report. Perhaps somebody will notice a problem in this file, although it looks okay to me.

At the end of the console output, these syslog messages appear:

Mar  7 09:48:49 ryzen genunix: WARNING: constraints forbid retire: /pci@0,0/pci1022,1453@1,3/pci1b21,1142@0
Mar  7 09:48:49 ryzen genunix: NOTICE: Device: already retired: /pci@0,0/pci1022,1453@1,3/pci1022,43b2@0,2/pci1022,43b4@0/pci1043,86f2@0

I don't know what triggers this message. Of course, syslog messages may be from an earlier time than the surrounding direct console messages. The path components in the messages are curious. The first is for an USB controller. Specifically, pci1022,1453@1,3 is an AMD PCIe GPP Bridge, and pci1b21,1142@0 is an ASMedia USB 3.1 Host Controller. The second message is for an unknown ASUS device. Specifically, pci1022,43b2@0,2 is an AMD Device unknown, pci1022,43b4@0 is for an AMD 300 Series Chipset PCIe Port, and pci1043,86f2@0 is for unknown ASUSTeK device.

I suspect that the virtual terminal service is using the wrong video device, thus causing the Xorg hang. How can I confirm or deny this idea?

I'm willing to use my Ryzen system to help debug the problem further, but I don't know how to do this now. Perhaps somebody can suggest a way.


cons.txt (51.6 KB) cons.txt Gary Mills, 2020-03-13 02:29 PM

Related issues

Related to illumos gate - Bug #12453: Missing shutdown log on AMD RyzenRejected


Also available in: Atom PDF