RX480 regression #158
Comments
|
Please show the kernel panic message and backtrace. |
|
Thanks. I pushed a change to drm-next which I think will address this - could you give it a try? |
|
That fixed the panic |
|
So the attach is still failing? Please show the full dmesg. |
|
$ dmesg 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 failed to send pre message 133 ret is 0 failed to send message 133 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 failed to send pre message 261 ret is 0 failed to send message 261 ret is 0 |
|
I'm not seeing any such problems with an RX460. Could you bisect a bit? I suggest trying 620ce8b~ to start. |
|
To be clear, verify whether the revision before 620ce8b is good. |
|
Ok. The next revision to try would be 9c9c64a. |
|
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. |
|
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.
The text was updated successfully, but these errors were encountered: