Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub
On dinsdag 21 mei 2019 21:20:18 CEST Diederik de Haas wrote: > What was the reason for the test? FTR: before I did the test I had already downgraded firmware-amd-graphics and consequently also firmware-linux-nonfree and firmware-misc-nonfree back to version 20190114-1 signature.asc Description: This is a digitally signed message part.
Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub
On dinsdag 21 mei 2019 21:20:18 CEST Diederik de Haas wrote: > Checking 'git log' for that specific file before I did the test made me > conclude it wouldn't make a difference with packaged version 20190114-1 > (but did the test anyway as requested). To verify whether that single file wasn't an anomaly, I compared the vega10* files from the 20190114-1 package with the files from the requested commit using SHA256 and they were all exactly the same. signature.asc Description: This is a digitally signed message part.
Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub
On dinsdag 21 mei 2019 19:24:07 CEST Romain Perier wrote: > Hi, Hi, > firmware-amd-graphics 20190502-1 is based onto upstream commit > 92e17d0dd2437140fab044ae62baf69b35d7d1fa, that is commit "amdgpu: update > vega20 to the latest 19.10 firmware" . Two commits behind there is commit > "amdgpu: update vega10 to the latest 19.10 firmware", that is already > included in firmware-amd-graphics 20190502-1. > > Could you try to revert "amdgpu: update vega10 to the latest 19.10 > firmware" ? So try to use the firmware for vega10 that is before this > commit. Does it work for you ? > > 1. Use linux-firmware.git with last HEAD in the master branch > 2. git checkout 4ea5c73b96ed4a508f90047e22ccbaa477481310 (commit "amdgpu: > update polaris11 to the latest 19.10 firmware", that is the commit before > bumping vega10 to 19.10) 3. Copy vega10 binary blobs to > /lib/firmware/amdgpu > > Does it work ? Yes, that does work. What did surprise me is that I saw a blinking cursor, which I don't see with firmware-amd-graphics version 20190114-1. $ git log --oneline -- amdgpu/vega10_ce.bin 0f22c85 Revert "amdgpu: update vega10 fw for 18.50 release" ec4b0cd amdgpu: update vega10 fw for 18.50 release ac5f8bd amdgpu: update vega10 firmware to 18.40 10e2971 amdgpu: sync up vega10 firmware with 18.20 release 0d672f7 amdgpu: sync up vega10 firmware with 18.10 release f0698be amdgpu: add initial vega10 firmware This tells me I'm running actually running "ac5f8bd amdgpu: update vega10 firmware to 18.40" https://tracker.debian.org/news/1021249/accepted-firmware-nonfree-20190114-1-source-into-unstable/ contains: - amd-graphics: + "Polaris10", "Polaris11", "Raven" firmware updates to sync with 18.50 release + "Fiji", "Tonga", "Vega10", "Carrizo" firmware updates to sync with 18.40 release So in both cases I'm supposed to run the exact same firmware version, so even the minor change in behavior (blinking cursor) surprises me. What was the reason for the test? Checking 'git log' for that specific file before I did the test made me conclude it wouldn't make a difference with packaged version 20190114-1 (but did the test anyway as requested). Cheers, Diederik signature.asc Description: This is a digitally signed message part.
Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub
On Tue, May 21, 2019 at 09:59:21AM +0200, Diederik de Haas wrote: > Got a new MB BIOS and after installing that, I made a new attempt with > firmware-amd-graphics version 20190502-1. > It failed again, but it got slightly further this time. > I saw a remount message, then a blinking cursor and then blank > screen+freeze+monitor in standby modus. > I figured that would've produced a kern.log and it did; see attachment. > > I have the upstream git repo on my machine and when I did > "git log -- amdgpu/vega10_ce.bin" I noticed commit > 0f22c8527439eaaf5c3fcf87b31c89445b6fa84d with the following message: > Revert "amdgpu: update vega10 fw for 18.50 release" > > This reverts commit ec4b0cd394472ee1491df6ef5f215d1f0953f836. > > This causes GPU hangs for some users. Let's revert for now > while we try and root cause the issue. > > Sounds familiar. > > What I could do is getting the various versions of amdgpu/vega10* from the > upstream git repo and place them in /lib/firmware/amdgpu/ to see which > versions > work and which don't. > Would that be useful? Any specific tests I should do or data to gather > (please > indicate how I should do that) > > Cheers, > Diederik Hi, firmware-amd-graphics 20190502-1 is based onto upstream commit 92e17d0dd2437140fab044ae62baf69b35d7d1fa, that is commit "amdgpu: update vega20 to the latest 19.10 firmware" . Two commits behind there is commit "amdgpu: update vega10 to the latest 19.10 firmware", that is already included in firmware-amd-graphics 20190502-1. Could you try to revert "amdgpu: update vega10 to the latest 19.10 firmware" ? So try to use the firmware for vega10 that is before this commit. Does it work for you ? 1. Use linux-firmware.git with last HEAD in the master branch 2. git checkout 4ea5c73b96ed4a508f90047e22ccbaa477481310 (commit "amdgpu: update polaris11 to the latest 19.10 firmware", that is the commit before bumping vega10 to 19.10) 3. Copy vega10 binary blobs to /lib/firmware/amdgpu Does it work ? Thanks, Regards, Romain > May 21 08:48:40 bagend kernel: [0.00] Linux version 4.19.0-5-amd64 > (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-7)) #1 SMP > Debian 4.19.37-3 (2019-05-15) > May 21 08:48:40 bagend kernel: [0.00] Command line: > BOOT_IMAGE=/vmlinuz-4.19.0-5-amd64 > root=UUID=a2a5e481-0ac6-4e68-818f-38255bf7dd57 ro quiet > May 21 08:48:40 bagend kernel: [0.00] x86/fpu: Supporting XSAVE > feature 0x001: 'x87 floating point registers' > May 21 08:48:40 bagend kernel: [0.00] x86/fpu: Supporting XSAVE > feature 0x002: 'SSE registers' > May 21 08:48:40 bagend kernel: [0.00] x86/fpu: Supporting XSAVE > feature 0x004: 'AVX registers' > May 21 08:48:40 bagend kernel: [0.00] x86/fpu: xstate_offset[2]: > 576, xstate_sizes[2]: 256 > May 21 08:48:40 bagend kernel: [0.00] x86/fpu: Enabled xstate > features 0x7, context size is 832 bytes, using 'compacted' format. > May 21 08:48:40 bagend kernel: [0.00] BIOS-provided physical RAM map: > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x-0x0009d3ff] usable > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x0009d400-0x0009] reserved > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x000e-0x000f] reserved > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x0010-0x09cf] usable > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x09d0-0x09ff] reserved > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x0a00-0x0a1f] usable > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x0a20-0x0a20afff] ACPI NVS > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x0a20b000-0x0aff] usable > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x0b00-0x0b01] reserved > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0x0b02-0xd873efff] usable > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0xd873f000-0xdb030fff] reserved > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0xdb031000-0xdb137fff] ACPI data > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0xdb138000-0xdb244fff] usable > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0xdb245000-0xdb60afff] ACPI NVS > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0xdb60b000-0xdc68bfff] reserved > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem > 0xdc68c000-0xdeff] usable > May 21 08:48:40 bagend kernel: [0.00] BIOS-e820: [mem >
Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub
On zaterdag 18 mei 2019 14:08:17 CEST Michael Becker wrote: > But I did not notice any spontaneous reboots so far. The spontaneous reboots seems to be an entirely different issue, see https:// bugs.debian.org/cgi-bin/bugreport.cgi?bug=924895#15 for details. signature.asc Description: This is a digitally signed message part.
Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub
Package: firmware-amd-graphics Followup-For: Bug #928631 Dear Maintainer, I had the same problem after upgrading to 20190502-1. I downgraded back to 20190502-1 and was able to normally boot into my system. But I did not notice any spontaneous reboots so far. The following lspci output is from after I downgraded the package. Hope this helps in some way. lspci -vvv -s 0b:00.0 0b:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Sapphire Technology Limited Vega 10 XL/XT [Radeon RX Vega 56/64] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [64] Express (v2) Legacy Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 256 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 8GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+, EqualizationPhase1+ EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest- Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [150 v2] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [200 v1] #15 Capabilities: [270 v1] #19 Capabilities: [2a0 v1] Access Control Services ACSCap: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans- ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans- Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 0020, Page Request Allocation: Capabilities: [2d0 v1] Process Address Space ID (PASID) PASIDCap: Exec+ Priv+, Max PASID Width: 10 PASIDCtl: Enable- Exec- Priv- Capabilities: [320 v1] Latency Tolerance Reporting Max snoop latency: 0ns Max no snoop latency: 0ns Kernel driver in use: amdgpu Kernel modules: amdgpu -- System Information: Debian Release: 10.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub
Package: firmware-amd-graphics Version: 20190502-1 Severity: critical Justification: breaks the whole system I have the same problem, my system is: Product Name: X470 GAMING PRO CARBON (MS-7B78) CPU: AMD Ryzen 7 2700X Eight-Core Processor GPU: Asus ROG Strix RX VEGA64 OC edition 8GB "THE SAME GPU" I( have boot with "nomodeset" into grub line. I have tested boot with: 4.19-3-amd64,4.19-4-amd64 and 4.19-5-amd64 always the same problem. Tonight douwgrade the packages lspci -vvv for VGA VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Vega 10 XL/XT [Radeon RX Vega 56/64] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: amdgpu Kernel modules: amdgpu cpuinfo for CPU processor : 0 vendor_id : AuthenticAMD cpu family : 23 model : 8 model name : AMD Ryzen 7 2700X Eight-Core Processor stepping: 2 microcode : 0x800820b cpu MHz : 3504.383 cache size : 512 KB physical id : 0 siblings: 16 core id : 0 cpu cores : 8 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate sme ssbd sev ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca bugs: sysret_ss_attrs null_seg spectre_v1 spectre_v2 spec_store_bypass bogomips: 7402.64 TLB size: 2560 4K pages clflush size: 64 cache_alignment : 64 address sizes : 43 bits physical, 48 bits virtual power management: ts ttp tm hwpstate cpb eff_freq_ro [13] [14] dmidecode for Mainboard Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 60 structures occupying 2512 bytes. Table at 0x000E6910. Handle 0x, DMI type 0, 26 bytes BIOS Information Vendor: American Megatrends Inc. Version: 2.60 Release Date: 01/23/2019 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.13 Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B78 Version: 1.0 Serial Number: To be filled by O.E.M. : UUID: ----00d86116f9eb Wake-up Type: Power Switch SKU Number: To be filled by O.E.M. Family: To be filled by O.E.M.
Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub
Package: firmware-amd-graphics Version: 20190502-1 Severity: critical Justification: breaks the whole system Today's Sid update brought in new kernel and various firmware updates, after which I rebooted the system. Saw Grub loading, but after it started kernel 4.19.0-5-amd64, it stopped loading the system. My Asus Crosshair VII system gave Q-code 8 as error, which stands for "System Agent initialization after microcode loading". Also tried booting with 4.19.0-4-amd64, but got the same error Started up my LiveRescueCD stick, downloaded firmware-amd-graphics_20190114-1_all.deb, copied it to /root/ of my normal system, chrooted into it and did "dpkg -i firmware-amd-graphics_20190114-1_all.deb" and then rebooted my system, which now did start as normally. As this is the only change I did, I'm quite sure I'm reporting it against the correct package (in contrast to what reportbug tried to tell me). I have reported another bug against amd64-microcode which may be relevant: 924895. Slight addition: I do sometimes get the spontanous reboots. System info: MB: Asus ROG CROSSHAIR VII HERO (BIOS: 2203) CPU: AMD Ryzen 7 1800X Eight-Core Processor (family: 0x17, model: 0x1, stepping: 0x1) GPU: Asus ROG Strix RX VEGA64 OC edition 8GB # lspci -vv -s 0c:00.0 0c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Vega 10 XL/XT [Radeon RX Vega 56/64] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [64] Express (v2) Legacy Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag+ PhantFunc- AuxPwr- NoSnoop+ MaxPayload 256 bytes, MaxReadReq 512 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #0, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 8GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Not Supported DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete+, EqualizationPhase1+ EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest- Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee0 Data: Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 Capabilities: [150 v2] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+ AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn- Capabilities: [200 v1] #15 Capabilities: [270 v1] #19 Capabilities: [2a0 v1] Access Control Services ACSCap: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans- ACSCtl: SrcValid- TransBlk- ReqRedir- CmpltRedir- UpstreamFwd- EgressCtrl- DirectTrans- Capabilities: [2b0 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable+, Smallest Translation Unit: 00 Capabilities: [2c0 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+
