markjdb
commented
7 years ago Please show the kernel panic message and backtrace.
Open gldisater opened 7 years ago
markjdb
commented
7 years ago Please show the kernel panic message and backtrace.
gldisater
commented
7 years ago markjdb
commented
7 years ago Thanks. I pushed a change to drm-next which I think will address this - could you give it a try?
gldisater
commented
7 years ago That fixed the panic https://flic.kr/p/WJJ2HX
markjdb
commented
7 years ago So the attach is still failing? Please show the full dmesg.
gldisater
commented
7 years ago $ dmesg
Copyright (c) 1992-2017 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 12.0-CURRENT #11 71830e622af(drm-next): Fri Jul 14 19:28:19 EDT 2017
gldisater@current:/usr/obj/usr/src-fbsd-base-graphics/sys/GENERIC_DRM amd64
FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0)
WARNING: WITNESS option enabled, expect reduced performance.
VT(efifb): resolution 1920x1080
CPU: AMD Ryzen 7 1700 Eight-Core Processor (2994.44-MHz K8-class CPU)
Origin="AuthenticAMD" Id=0x800f11 Family=0x17 Model=0x1 Stepping=1
Features=0x178bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT>
Features2=0x7ed8320b<SSE3,PCLMULQDQ,MON,SSSE3,FMA,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
AMD Features=0x2e500800<SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM>
AMD Features2=0x35c233ff<LAHF,CMP,SVM,ExtAPIC,CR8,ABM,SSE4A,MAS,Prefetch,OSVW,SKINIT,WDT,TCE,Topology,PCXC,PNXC,DBE,PL2I,MWAITX>
Structured Extended Features=0x209c01a9<FSGSBASE,BMI1,AVX2,SMEP,BMI2,RDSEED,ADX,SMAP,CLFLUSHOPT,SHA>
XSAVE Features=0xf<XSAVEOPT,XSAVEC,XINUSE,XSAVES>
SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=32768
TSC: P-state invariant, performance statistics
real memory = 17179869184 (16384 MB)
avail memory = 16536436736 (15770 MB)
Event timer "LAPIC" quality 100
ACPI APIC Table:
failed to send pre message 14a ret is 0
failed to send message 14a ret is 0
failed to send pre message 5d ret is 0
failed to send message 5d ret is 0
failed to send pre message 109 ret is 0
failed to send message 109 ret is 0
failed to send pre message 62 ret is 0
failed to send message 62 ret is 0
failed to send pre message 18f ret is 0
failed to send message 18f ret is 0
failed to send pre message 301 ret is 0
failed to send message 301 ret is 0
failed to send pre message 109 ret is 0
failed to send message 109 ret is 0
failed to send pre message 14e ret is 0
failed to send message 14e ret is 0
failed to send pre message 150 ret is 0
failed to send message 150 ret is 0
failed to send pre message 136 ret is 0
failed to send message 136 ret is 0
failed to send pre message 53 ret is 0
failed to send message 53 ret is 0
failed to send pre message 169 ret is 0
failed to send message 169 ret is 0
failed to send pre message 185 ret is 0
failed to send message 185 ret is 0
failed to send pre message 187 ret is 0
failed to send message 187 ret is 0
failed to send pre message 188 ret is 0
failed to send message 188 ret is 0
failed to send pre message 10a ret is 0
failed to send message 10a ret is 0
failed to send pre message 305 ret is 0
failed to send message 305 ret is 0
failed to send pre message 26a ret is 0
failed to send message 26a ret is 0
failed to send pre message 209 ret is 0
failed to send message 209 ret is 0
failed to send pre message 206 ret is 0
failed to send message 206 ret is 0
failed to send pre message 5b ret is 0
failed to send message 5b ret is 0
failed to send pre message 205 ret is 0
failed to send message 205 ret is 0
failed to send pre message 20a ret is 0
failed to send message 20a ret is 0
[drm:gfx_v8_0_ring_test_ring] amdgpu: ring 0 test failed (scratch(0xC040)=0xCAFEDEAD)
[drm:amdgpu_init] hw_init of IP block
failed to send pre message 133 ret is 0
failed to send message 133 ret is 0 DPM is not running right now, no need to disable DPM!
failed to send pre message 261 ret is 0
failed to send message 261 ret is 0
failed to send pre message 261 ret is 0
failed to send message 261 ret is 0
failed to send pre message 261 ret is 0
failed to send message 261 ret is 0
failed to send pre message 261 ret is 0
failed to send message 261 ret is 0
failed to send pre message 261 ret is 0
failed to send message 261 ret is 0
failed to send pre message 261 ret is 0
failed to send message 261 ret is 0
failed to send pre message 261 ret is 0
failed to send message 261 ret is 0
failed to send pre message 261 ret is 0
failed to send message 261 ret is 0
failed to send pre message 261 ret is 0
failed to send message 261 ret is 0
failed to send pre message 261 ret is 0
failed to send message 261 ret is 0 [TTM] Finalizing pool allocator Zone kernel: Used memory at exit: 816 kiB Zone dma32: Used memory at exit: 816 kiB [drm] amdgpu: ttm finalized drmn0: Fatal error during GPU init [drm] amdgpu: finishing device. [TTM] Memory type 2 has not been initialized drmn0: linux_pci_attach failed! -22device_attach: drmn0 attach returned 22 [drm] Module unloaded Warning: memory type drm_driver leaked memory on destroy (3 allocations, 48 bytes leaked). Warning: memory type idr leaked memory on destroy (1 allocations, 16 bytes leaked). Warning: memory type lkpifw leaked memory on destroy (1 allocations, 32 bytes leaked). Warning: memory type idr leaked memory on destroy (5 allocations, 2560 bytes leaked). Warning: memory type linux leaked memory on destroy (554 allocations, 85136 bytes leaked). Warning: memory type linuxcurrent leaked memory on destroy (19 allocations, 2240 bytes leaked).
markjdb
commented
7 years ago I'm not seeing any such problems with an RX460. Could you bisect a bit? I suggest trying 620ce8b40109~ to start.
markjdb
commented
7 years ago To be clear, verify whether the revision before 620ce8b is good.
gldisater
commented
7 years ago 620ce8b panics, 9042fbaaaf6 does not panic but fails to attach
markjdb
commented
7 years ago Ok. The next revision to try would be 9c9c64a8.
gldisater
commented
7 years ago Sorry for not updating you with status. I spent a couple hours last night going back through commits trying to find a spot where it worked, but I couldn't find any and got myself into a hole with mismatched world and kernel. So I blew away the boot environment for drm-next and recreated it. Found a zfs snapshot of the drm-next snapshot I found that I know was working before, but it failed and panicked the system. I concluded that my upgrade to Ryzen was involved in the issue.
To test if it was uefi and scbuf that was the issue I reinstalled with a bios only boot and forced the uefi to use legacy and now on drm-next HEAD the driver attaches. It outputs a lot of "failed to send message", but it was doing that before.
markjdb
commented
7 years ago Ah, right, that's a known issue at the moment - I should have have caught it from the dmesg. The workaround for the time being is to set hw.syscons.disable="1" in loader.conf and load amdgpu via kld_list in rc.conf. This will cause vt to avoid using the EFI framebuffer and so you won't get any console output until amdgpu sets the mode. Fixing this is on my todo list but at the moment I'm preoccupied with getting these drivers working on stock FreeBSD.
Previously (late may) amdgpu would load and would have frequent flickers and errors reported in console, now kldload amdgpu reports it failed to all of the polaris10 firmware files and then the kernel panics 30seconds later.