Originally posted by brrrrttttt
View Post
Announcement
Collapse
No announcement yet.
Linux 4.17 Kernel Released With Big Updates For AMDGPU, CPU Power-Savings
Collapse
X
-
Originally posted by caligula View Post
So it would be ok for you if I contributed something to the kernel and depended on Java, C#, Fortran, MUMPS, Cobol, R, MATLAB, DigitalMars D, and Intercal?
- Likes 1
Comment
-
Originally posted by caligula View PostI really wish the kernel didn't require that many languages and tools to build.- It doesn't make any sense to have a single sed script when you already require awk.
- The css file is referred by a single python script, it could be defined inline.
- The xslt files are only used for a single document when you already have html, TeX, and Markdown. :-(
- m4, nant script, glade - why?
- TeX - only Documentation/cdrom/cdrom-standard.tex :-(
- Markdown - only Documentation/filesystems/path-lookup.md :-(
- It also makes little sense to have both Perl and Python scripts, or Python/Bash/Perl/Make when a single tool could handle it all - maybe Meson instead?
- C++ ? wat
Sounds like an intersting GSoC project...
- Likes 1
Comment
-
Originally posted by mike189 View PostStill havent been able to boot a kernel newer then 4.15.3-53 with my AMD R9 Nano via DP, HDMI works but cant have a usable screen with 30hz refresh. Anyone else have these issues?
Comment
-
edit: appears to be this: https://bugs.freedesktop.org/show_bug.cgi?id=106259
Hmm .. display freeze with 4.17 on Vega 56 here, using mpv with opengl/vdpau. Ubuntu 18.04, Padoka PPA, Unity desktop. Works fine with Linux 4.16.13, same everything except kernel.
amdgpu: [powerplay] No response from smu
amdgpu: [powerplay] Failed to send message: 0x46, ret value: 0x0
.. repeated 3 times ..
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring uvd timeout, last signaled seq=13, last emitted seq=16
[drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, last signaled seq=6629, last emitted seq=6632
[drm] No hardware hang detected. Did some blocks stall?
[drm] No hardware hang detected. Did some blocks stall?
amdgpu: [powerplay] No response from smu
amdgpu: [powerplay] Failed to send message: 0x46, ret value: 0x0
.. repeated 11 times ..
amdgpu: [powerplay] Failed to send message: 0x46, ret value: 0xfc
.. repeated many times, then:
kernel: INFO: task kworker/u32:8:343 blocked for more than 120 seconds.
kernel: Not tainted 4.17.0-lem #1
kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kernel: kworker/u32:8 D 0 343 2 0x80000000
kernel: Workqueue: events_unbound commit_work [drm_kms_helper]
kernel: Call Trace:
kernel: __schedule+0x284/0x880
kernel: Call Trace:
kernel: __schedule+0x284/0x880
kernel: schedule+0x33/0x90
kernel: schedule_timeout+0x1f0/0x370
kernel: ? amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
kernel: ? dce120_timing_generator_get_crtc_position+0x63/0x80 [amdgpu]
kernel: ? dce120_timing_generator_get_crtc_scanoutpos+0x63/0x80 [amdgpu]
kernel: dma_fence_default_wait+0x19b/0x260
kernel: ? dma_fence_release+0xb0/0xb0
kernel: amdgpu: [powerplay] Failed to send message: 0x46, ret value: 0xfc
kernel: INFO: task kworker/u32:8:343 blocked for more than 120 seconds.
kernel: Not tainted 4.17.0-lem #1
kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kernel: kworker/u32:8 D 0 343 2 0x80000000
kernel: Workqueue: events_unbound commit_work [drm_kms_helper]
kernel: Call Trace:
kernel: __schedule+0x284/0x880
kernel: schedule+0x33/0x90
kernel: schedule_timeout+0x1f0/0x370
kernel: ? amdgpu_cgs_read_register+0x14/0x20 [amdgpu]
kernel: ? dce120_timing_generator_get_crtc_position+0x63/0x80 [amdgpu]
kernel: ? dce120_timing_generator_get_crtc_scanoutpos+0x63/0x80 [amdgpu]
kernel: dma_fence_default_wait+0x19b/0x260
kernel: ? dma_fence_release+0xb0/0xb0
kernel: dma_fence_wait_timeout+0x3e/0x120
kernel: reservation_object_wait_timeout_rcu+0x163/0x360
kernel: amdgpu_dm_do_flip+0x11d/0x360 [amdgpu]
kernel: ? __slab_free+0x14d/0x2c0
kernel: amdgpu_dm_atomic_commit_tail+0xb4a/0xd70 [amdgpu]
kernel: ? drm_atomic_helper_wait_for_dependencies+0x150/0x200 [drm_kms_helper]
kernel: commit_tail+0x42/0x70 [drm_kms_helper]
kernel: commit_work+0x12/0x20 [drm_kms_helper]
kernel: process_one_work+0x1d5/0x3f0
kernel: worker_thread+0x32/0x400
kernel: kthread+0x121/0x140
kernel: ? process_one_work+0x3f0/0x3f0
kernel: ? kthread_create_worker_on_cpu+0x50/0x50
kernel: ret_from_fork+0x22/0x40
amdgpu: [powerplay] Failed to send message: 0x46, ret value: 0xfc
.. repeated many times until reset.
I was SSH'd in at the time, so could signal a restart.
Anyone can suggest where I might file a bug, do some more tests etc to get a useful bug report etc? Thanks.
Comment
-
Originally posted by lem79 View PostAnyone can suggest where I might file a bug, do some more tests etc to get a useful bug report etc?
Product: DRI, Component: DRM/AMDgpu.
- Likes 1
Comment
-
I have troubles with nvidia K2000M in form of GPIO mode for GPU from kernel 4.x. Last good distro for me with good kernel 3.19 was only Linux mint 17.3. From kernel 4.X have gpio mode at cards of nvidia on lots of laptops from HP, Lenovo and Acer. With mesa and proprietary driver it was same!Last edited by Atirage21; 04 June 2018, 03:27 PM.
Comment
-
For users which uses the Radeon Software Linux (AMDGPU-PRO 18.10). I checked that OpenCL from RSL 18.10 works fine with new kernel without any extra module. I don't know whether this kernel works fine with OpenGL/Vulkan driver part. However I run a PAL OpenCL and legacy OpenCL both without any extra modules and DKMS.
Comment
Comment