Announcement

Collapse
No announcement yet.

Linux 5.5-rc6 Released With Some Notable Radeon Graphics Fixes Plus Other Random Work

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Linux 5.5-rc6 Released With Some Notable Radeon Graphics Fixes Plus Other Random Work

    Phoronix: Linux 5.5-rc6 Released With Some Notable Radeon Graphics Fixes Plus Other Random Work

    Linus Torvalds has just issued Linux 5.5-rc6 as the latest test release ahead of the stable Linux 5.5 kernel due out in a few weeks...

    http://www.phoronix.com/scan.php?pag...5-rc6-Released

  • sandy8925
    replied
    Originally posted by khnazile View Post

    Kernel driver faults. Computer becomes unresponsive. Sometimes amdgpu manages to reset itself, but context of all graphics applications including your desktop is lost and they're effectively dead. There are multiple reports of this on Bugzilla/Gitlab.
    Ah, the same crap I faced on my R9 390. So the status quo hasn't changed one bit, contrary to bridgman's and AMD fans' assertions.

    As soon as a decently powerful Intel Xe dGPU is released, I'll just ditch this stupid AMD card.

    Leave a comment:


  • aht0
    replied
    Okay, tnx. I won't bother checking it in depth when you say so. Tnx for the heads-up.

    Leave a comment:


  • BS86
    replied
    Originally posted by archola View Post

    Was it actually caused by a bug in the previous release candidates of kernel 5.5 that got fixed just now (I can't see anything in the commit log), or is it caused by something else? Or is it not fixed and I just haven't triggered the bug yet somehow?
    i really hope that it was fixed. Will try when I am home again tonight (It's 8 AM here) I don't think that the fix will have anything with clock in its name or description. I think it is/was a side effect or regression of some other change.

    Originally posted by aht0 View Post

    I could try it, Asus ROG board, Ryzen/discrete Vega rig.
    Would be great! But if rc6 already fixed it, it might not be needed.

    Edit: the problem IS fixed in rc6. 5 reboots and no clock reset. With rc5 it is still reproducible.
    Last edited by BS86; 01-14-2020, 12:39 PM.

    Leave a comment:


  • aht0
    replied
    Originally posted by BS86 View Post
    I have a very strange problem with the 5.5 Kernels so far: 8 out of 10 times when I reboot or shutdown, the system clock is reset to 1.1.2017 00:00 in BIOS.
    That behaviour does not happen on Kernels 5.4.10 and earlier, and it also does not happen on Windows.

    Things already done:
    - Replaced mainboard battery (as it happens only with Kernel 5.5, that obviously did not fix it - but I realized that my mainboard only resets the time and date when removing the battery)
    - checked for BIOS updates (none there: 5406 is installed and the latest version)
    - linux-firmware is also up-to date (20200107 on Manjaro)

    My relevant hardware: Asus ROG Strix X470-F Gaming and a Ryzen 2700X, full UEFI/GPT setup.

    I only noticed that behaviour because on every boot after the clock reset happening, systemd-fsck kicks in for all partitions and that displays a message during boot for my rotation harddisk and slows down booting (the trigger for the fsck is the system time being earlier than the last mount time). If it would be a SSD only system, I would not even notice the behaviour because the NTP service already synced when the GUI displays the clock. The only way to see it is by checking the BIOS clock.

    Does anyone else notice that behavior or can check if their hardware clock in BIOS is reset after rebooting with a 5.5 Kernel?

    Edit: If it is important: Asus uses American Megatrends BIOS'es.
    I could try it, Asus ROG board, Ryzen/discrete Vega rig.

    Leave a comment:


  • set135
    replied
    Originally posted by archola View Post

    I'm a bit confused now. I've built 5.5-rc6 (while using 5.5-rc5) after writing my previous post, upgraded the rest of the system, rebooted, corrected the hardware clock because it was of course reset, and booted into both 5.5-rc6 and 5.4.11 several times throughout the day, but the clock didn't reset even once after that. This is a bit surprising, because it happened all the time previously. Was it actually caused by a bug in the previous release candidates of kernel 5.5 that got fixed just now (I can't see anything in the commit log), or is it caused by something else? Or is it not fixed and I just haven't triggered the bug yet somehow?
    Well, you can boot 5.5-rc5 again, and see what happens... One thing to consider is that the distribution usually (?) sets the BIOS clock from the running system time during shutdown. (Because the running system time is generally more accurate.) So, a bug or change in how your distro does this might cause a problem, or maybe something causes the system time to get messed up during shutdown, and the wrong time gets synced to the BIOS. So, another thing to test would be to disable whatever unit systemd (or whatever init) uses to do the sync'ing.

    Leave a comment:


  • BS86
    replied
    Originally posted by archola View Post

    I'm having a similar problem with my Asus ROG Strix X570-F Gaming, which I've bought for my new Ryzen 3950X at the end of November last year. It's always resetting the clock to 2019-01-01
    Well, that sounds EXACTLY like my problem. For my X470, 1.1.2017 is the earliest possible date. For yours, it is 1.1.2019. Looking forward to your findings with 5.4.

    I have absolutely no idea what in the kernel would cause that behaviour. I suspect something that "talks" to the UEFI, but what exactly it is, no idea.

    I have a Vega64 which also gets better with each kernel, but so far, I am back to 5.4 because of that reset - issue.

    Leave a comment:


  • archola
    replied
    Originally posted by archola View Post
    I will check this later today with an older kernel when I get the time and come back with the results.
    I'm a bit confused now. I've built 5.5-rc6 (while using 5.5-rc5) after writing my previous post, upgraded the rest of the system, rebooted, corrected the hardware clock because it was of course reset, and booted into both 5.5-rc6 and 5.4.11 several times throughout the day, but the clock didn't reset even once after that. This is a bit surprising, because it happened all the time previously. Was it actually caused by a bug in the previous release candidates of kernel 5.5 that got fixed just now (I can't see anything in the commit log), or is it caused by something else? Or is it not fixed and I just haven't triggered the bug yet somehow?

    Leave a comment:


  • lowlands
    replied
    Originally posted by Sethox View Post

    Same here, a system with Vega 56 GPU and no issues besides a minor problem I do not use (not my particular use case), my system after hibernating (when the system wakes up) the GPU goes 100% fan speed and stays with a black screen.

    I usually turn off that particular function since I either turn off the computer or have it on to be used thus does not count as a problem for me.
    Which distro do you use? With Fedora you need to specify the resume=<device> in grub or it won't come back properly after hibernate.

    Leave a comment:


  • aufkrawall
    replied
    *sigh*, still no progress with this:
    https://gitlab.freedesktop.org/drm/amd/issues/1001

    Leave a comment:

Working...
X