Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.rc > #257385 > unrolled thread
| Started by | Diederik de Haas <didi.debian@cknow.org> |
|---|---|
| First post | 2019-05-08 01:30 +0200 |
| Last post | 2019-07-21 03:00 +0200 |
| Articles | 9 — 5 participants |
Back to article view | Back to linux.debian.bugs.rc
Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub Diederik de Haas <didi.debian@cknow.org> - 2019-05-08 01:30 +0200
Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub Antonio De Luci <osrevolution@gmail.com> - 2019-05-08 14:10 +0200
Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub Diederik de Haas <didi.debian@cknow.org> - 2019-05-21 22:00 +0200
Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub Diederik de Haas <didi.debian@cknow.org> - 2019-05-21 22:20 +0200
Bug#928631: Alex Korobkin <korobkin+pp@gmail.com> - 2019-05-29 20:10 +0200
Bug#928631: Question Antonio De Luci <osrevolution@gmail.com> - 2019-06-22 13:10 +0200
Bug#928631: Question Diederik de Haas <didi.debian@cknow.org> - 2019-06-24 11:00 +0200
Bug#928631: Hillel Lubman <shtetldik@gmail.com> - 2019-07-14 21:50 +0200
Bug#928631: firmware-amd-graphics: Removing vega20 firmware files corrects the problem on my system Robin Cook <rcook@wyrms.net> - 2019-07-21 03:00 +0200
| From | Diederik de Haas <didi.debian@cknow.org> |
|---|---|
| Date | 2019-05-08 01:30 +0200 |
| Subject | Bug#928631: firmware-amd-graphics: Update to 20190502-1 causus hang of system directly after grub |
| Message-ID | <xVhH3-1oo-1@gated-at.bofh.it> |
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- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 76
Region 0: Memory at e0000000 (64-bit, prefetchable) [size=256M]
Region 2: Memory at f0000000 (64-bit, prefetchable) [size=2M]
Region 4: I/O ports at e000 [size=256]
Region 5: Memory at fcc00000 (32-bit, non-prefetchable) [size=512K]
Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: [48] Vendor Specific Information: Len=08 <?>
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: 00000000fee00000 Data: 0000
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: 00000020, Page Request Allocation: 00000000
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
If you need more info, let me know.
-- System Information:
Debian Release: 10.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental'), (1, 'experimental-debug')
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
firmware-amd-graphics depends on no packages.
firmware-amd-graphics recommends no packages.
Versions of packages firmware-amd-graphics suggests:
ii initramfs-tools 0.133
-- no debconf information
[toc] | [next] | [standalone]
| From | Antonio De Luci <osrevolution@gmail.com> |
|---|---|
| Date | 2019-05-08 14:10 +0200 |
| Message-ID | <xVtyx-mR-3@gated-at.bofh.it> |
| In reply to | #257385 |
[Multipart message — attachments visible in raw view] — view raw
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- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 73
Region 0: Memory at e0000000 (64-bit, prefetchable) [size=256M]
Region 2: Memory at f0000000 (64-bit, prefetchable) [size=2M]
Region 4: I/O ports at f000 [size=256]
Region 5: Memory at fe500000 (32-bit, non-prefetchable) [size=512K]
Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: <access denied>
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 0x0000, DMI type 0, 26 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 2.60
Release Date: 01/23/2019
Address: 0xF0000
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: 00000000-0000-0000-0000-00d86116f9eb
Wake-up Type: Power Switch
SKU Number: To be filled by O.E.M.
Family: To be filled by O.E.M.
[toc] | [prev] | [next] | [standalone]
| From | Diederik de Haas <didi.debian@cknow.org> |
|---|---|
| Date | 2019-05-21 22:00 +0200 |
| Message-ID | <y0j5v-1Lj-3@gated-at.bofh.it> |
| In reply to | #257385 |
[Multipart message — attachments visible in raw view] — view raw
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.
[toc] | [prev] | [next] | [standalone]
| From | Diederik de Haas <didi.debian@cknow.org> |
|---|---|
| Date | 2019-05-21 22:20 +0200 |
| Message-ID | <y0joR-27N-3@gated-at.bofh.it> |
| In reply to | #257385 |
[Multipart message — attachments visible in raw view] — view raw
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
[toc] | [prev] | [next] | [standalone]
| From | Alex Korobkin <korobkin+pp@gmail.com> |
|---|---|
| Date | 2019-05-29 20:10 +0200 |
| Subject | Bug#928631: |
| Message-ID | <y3bbr-3sK-1@gated-at.bofh.it> |
| In reply to | #257385 |
[Multipart message — attachments visible in raw view] — view raw
Exactly the same issue with AMD Vega 56 videocard, also depends on vega10_gpu_info.bin: May 29 11:49:37 debian1 kernel: [ 4.351872] amdgpu 0000:1a:00.0: firmware: direct-loading firmware amdgpu/vega10_gpu_info.bin <..> May 29 11:49:37 debian1 kernel: [ 4.352869] amdgpu 0000:1a:00.0: firmware: direct-loading firmware amdgpu/vega10_sos.bin May 29 11:49:37 debian1 kernel: [ 4.352895] amdgpu 0000:1a:00.0: firmware: direct-loading firmware amdgpu/vega10_asd.bin May 29 11:49:37 debian1 kernel: [ 4.352971] amdgpu 0000:1a:00.0: firmware: direct-loading firmware amdgpu/vega10_acg_smc.bin May 29 11:49:37 debian1 kernel: [ 4.352996] amdgpu 0000:1a:00.0: firmware: direct-loading firmware amdgpu/vega10_pfp.bin May 29 11:49:37 debian1 kernel: [ 4.353008] amdgpu 0000:1a:00.0: firmware: direct-loading firmware amdgpu/vega10_me.bin May 29 11:49:37 debian1 kernel: [ 4.353019] amdgpu 0000:1a:00.0: firmware: direct-loading firmware amdgpu/vega10_ce.bin May 29 11:49:37 debian1 kernel: [ 4.353031] amdgpu 0000:1a:00.0: firmware: direct-loading firmware amdgpu/vega10_rlc.bin May 29 11:49:37 debian1 kernel: [ 4.353109] amdgpu 0000:1a:00.0: firmware: direct-loading firmware amdgpu/vega10_mec.bin May 29 11:49:37 debian1 kernel: [ 4.353188] amdgpu 0000:1a:00.0: firmware: direct-loading firmware amdgpu/vega10_mec2.bin May 29 11:49:37 debian1 kernel: [ 4.355194] amdgpu 0000:1a:00.0: firmware: direct-loading firmware amdgpu/vega10_sdma.bin May 29 11:49:37 debian1 kernel: [ 4.355209] amdgpu 0000:1a:00.0: firmware: direct-loading firmware amdgpu/vega10_sdma1.bin -- -Alex
[toc] | [prev] | [next] | [standalone]
| From | Antonio De Luci <osrevolution@gmail.com> |
|---|---|
| Date | 2019-06-22 13:10 +0200 |
| Subject | Bug#928631: Question |
| Message-ID | <ybM49-XP-1@gated-at.bofh.it> |
| In reply to | #257385 |
Il 22/06/19 12:46, Diederik de Haas ha scritto: > On vrijdag 21 juni 2019 16:53:11 CEST Dean Loros wrote: >> Can I confirm that this is a problem with AMD graphics only--or will this >> affect all systems regardless of Video card type? > Yes. (bug is filed against firmware-amd-graphics) > > > Michael Becker: what CPU do you have? I have amd ryzen 2700X > Antonio De Luci: Are you running Sid as well? Yes, I have only Sid in the my personal computers > > > I feel 'bad' because this bug is preventing the whole of firmware-nonfree to > not migrate to testing/Buster and thus causes Buster to be released with > (somewhat) dated firmware. I suspect many would benefit from version 20190502-1. > > It very much looks to be an issue with the Vega 56/64 card + AMD Ryzen (7?) > CPU, ie a very specific combination. The people who ran into this issue are > running Sid (at least 2 of them), so wouldn't be affected by an 'old' version > in the next Stable. > > I remember there being 'stretch-ignore' tags to bugs and I would be fine if > 'buster-ignore' would be applied to this bug so firmware-nonfree can migrate to > testing/Buster.
[toc] | [prev] | [next] | [standalone]
| From | Diederik de Haas <didi.debian@cknow.org> |
|---|---|
| Date | 2019-06-24 11:00 +0200 |
| Subject | Bug#928631: Question |
| Message-ID | <ycsZr-1fi-1@gated-at.bofh.it> |
| In reply to | #258474 |
[Multipart message — attachments visible in raw view] — view raw
Just got a msg from Michael send to me personally, I assume by accident. Summary of the affected systems: AMD Ryzen 1700X + VEGA64 + Sid AMD Ryzen 2700X + VEGA64 + Sid AMD Ryzen 2700X + VEGA56 + Sid It's up to the maintainers, but as I said, I would be fine if severity of the bug is lowered or some other method is used so that firmware-nonfree version 20190502-1 can transition to testing and be included in Buster.
[toc] | [prev] | [next] | [standalone]
| From | Hillel Lubman <shtetldik@gmail.com> |
|---|---|
| Date | 2019-07-14 21:50 +0200 |
| Subject | Bug#928631: |
| Message-ID | <yjSFr-1tx-1@gated-at.bofh.it> |
| In reply to | #257385 |
Hi. 20190502-1 is already outdated, since amdgpu firmware had some updates upstream: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/log/amdgpu Does this problem still occur if you use latest upstream firmware? By the way, it works well for me (Ryzen 7 2700X / Vega 56), but I'm running kernel 5.2.1 in Debian testing. Best regards, Hillel Lubman.
[toc] | [prev] | [next] | [standalone]
| From | Robin Cook <rcook@wyrms.net> |
|---|---|
| Date | 2019-07-21 03:00 +0200 |
| Subject | Bug#928631: firmware-amd-graphics: Removing vega20 firmware files corrects the problem on my system |
| Message-ID | <ym8mJ-3B5-1@gated-at.bofh.it> |
| In reply to | #257385 |
Package: firmware-amd-graphics Version: 20190502-1 Followup-For: Bug #928631 Dear Maintainer, Updating to any version of the firmware-amd-graphics with the vega20 firmware causes my system to hang during boot after grub. Removing all the vega20 firmware files and causing initrd to rebuild corrects the problem and system boots normally. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/32 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled firmware-amd-graphics depends on no packages. firmware-amd-graphics recommends no packages. Versions of packages firmware-amd-graphics suggests: ii initramfs-tools 0.133 -- no debconf information
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.bugs.rc
csiph-web