dri-devel May 2018

dri-devel@lists.freedesktop.org

268 participants
1833 discussions

[Bug 106188] Can't successfully set pstates in pp_od_clk_voltage
by bugzilla-daemon＠freedesktop.org 08 May '18

08 May '18

https://bugs.freedesktop.org/show_bug.cgi?id=106188 Bug ID: 106188 Summary: Can't successfully set pstates in pp_od_clk_voltage Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: tempel.julian(a)gmail.com Hello, I specified "amdgpu.ppfeaturemask=0xffffffff" as a boot parameter so I could access "/sys/class/drm/card0/device/pp_od_clk_voltage". The pstate table for source and memory clocks looks correct. When I run "echo "s 7 1209 900" /sys/class/drm/card0/device/pp_od_clk_voltage", it returns "s 7 1209 900 /sys/class/drm/card0/device/pp_od_clk_voltage". When I run "echo "c" /sys/class/drm/card0/device/pp_od_clk_voltage" afterwards, it returns "c /sys/class/drm/card0/device/pp_od_clk_voltage". However, the change is not applied. When I do "cat /sys/class/drm/card0/device/pp_od_clk_voltage", it still says "7: 1196Mhz 1006 mV". And when I run "watch -n 0.5 cat /sys/kernel/debug/dri/0/amdgpu_pm_info", it reports " 1196 MHz (SCLK) 981 mV (VDDGFX) ". Am I making a mistake somewhere or should it work like this? I also tried "echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance_level" and setting pstates 5-7, but that didn't help either. In the documentation, I read that pp_od_clk_voltage should also include OD_range, but it's not there for me. Linux drm-next-4.18-wip 4.16.1.52132fd03 MSI RX 560 Aero ITX Thanks! -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 106309] MST Multi-Stream Transport Kills All Displays Using Radeon Driver On Radeon HD 7570
by bugzilla-daemon＠freedesktop.org 08 May '18

08 May '18

https://bugs.freedesktop.org/show_bug.cgi?id=106309 Alex Deucher <alexdeucher(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #4 from Alex Deucher <alexdeucher(a)gmail.com> --- The radeon driver does not support MST. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[PATCH] drm/i915/gvt: fix spelling mistake: "resseting" -> "resetting"
by Colin King 08 May '18

08 May '18

From: Colin Ian King <colin.king(a)canonical.com> Trivial fix to spelling mistake in gvt_dbg_core debug message Signed-off-by: Colin Ian King <colin.king(a)canonical.com> --- drivers/gpu/drm/i915/gvt/vgpu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/gvt/vgpu.c b/drivers/gpu/drm/i915/gvt/vgpu.c index 2e0a02a80fe4..7b856c9b4e07 100644 --- a/drivers/gpu/drm/i915/gvt/vgpu.c +++ b/drivers/gpu/drm/i915/gvt/vgpu.c @@ -502,7 +502,7 @@ void intel_gvt_reset_vgpu_locked(struct intel_vgpu *vgpu, bool dmlr, unsigned int resetting_eng = dmlr ? ALL_ENGINES : engine_mask; gvt_dbg_core("------------------------------------------\n"); - gvt_dbg_core("resseting vgpu%d, dmlr %d, engine_mask %08x\n", + gvt_dbg_core("resetting vgpu%d, dmlr %d, engine_mask %08x\n", vgpu->id, dmlr, engine_mask); vgpu->resetting_eng = resetting_eng; -- 2.17.0

1 0

[Bug 199025] Suspend hangs. Never fully suspends and impossible to return to running state.
by bugzilla-daemon＠bugzilla.kernel.org 08 May '18

08 May '18

https://bugzilla.kernel.org/show_bug.cgi?id=199025 --- Comment #30 from Patrice (p.polypa(a)free.fr) --- I can't access the faulty machine until next Saturday - but it runs Fedora28's latest Xfce . -- You are receiving this mail because: You are watching the assignee of the bug.

1 0

[Bug 199025] Suspend hangs. Never fully suspends and impossible to return to running state.
by bugzilla-daemon＠bugzilla.kernel.org 08 May '18

08 May '18

https://bugzilla.kernel.org/show_bug.cgi?id=199025 --- Comment #29 from Paul van Maaren (kernel(a)vanmaaren.org) --- I just did the runlevel test and it does not make difference for me. I did: ln -sf /usr/lib/systemd/system/multi-user.target /etc/systemd/system/default.target and a reboot to 4.16.6-302 and ran: echo mem > /sys/power/state The power light stayed on and it does not wake up. I tried the same after booting to 4.14.18-300 that worked fine. -- You are receiving this mail because: You are watching the assignee of the bug.

1 0

amdgpu hangs on boot or shutdown on AMD Raven Ridge CPU (Engineer Sample)
by Chris Chiu 08 May '18

08 May '18

Hi, We are working with new laptops that have the AMD Ravenl Ridge chipset with this `/proc/cpuinfo` https://gist.github.com/mschiu77/b06dba574e89b9a30cf4c450eaec49bc With the latest kernel 4.15, there're lots of different panics/oops during boot so no chance to get into X. It also happens during shutdown. Then I tried to build kernel from git://people.freedesktop.org/~agd5f/linux on branch amd-staging-drm-next with head on commit "drm: Fix trailing semicolon" and update the linux-firmware. Things seem to get better, only 1 oops observed. Here's the oops https://gist.github.com/mschiu77/1a68f27272b24775b2040acdb474cdd3. However, I still get stuck on the following messages during boot very often "" [ 4.998241] endless kernel: [drm] amdgpu kernel modesetting enabled. [ 4.998288] endless kernel: checking generic (e0000000 7f0000) vs hw (e0000000 10000000) [ 4.998289] endless kernel: fb: switching to amdgpudrmfb from EFI VGA "" I turned on drm.debug=0xe while booting, but no more information at this point. Anything I can do at this point? And there's 1 more information may be helpful. Sometimes the system boots OK with the blank screen, I can't switch to virtual console, but it did respond to the magic sys-rq key. The dmesg with drm.debug=0xe is here https://gist.github.com/mschiu77/291e47b1f07dc52be9461c55c820464c. I'm pretty sure it's due to the amdgpu driver. Because when I boot with my own kernel which disables the amdgpu driver, all these symptoms went away. Please suggest anything I can do for this. Thanks Chris

5 10

[PATCH 0/7] drm/mediatek: support hdmi output for mt2701 and mt7623
by Bibby Hsieh 08 May '18

08 May '18

Bibby Hsieh (3): drm/mediatek: implement connection from BLS to DPI0 drm/mediatek: add a error return value when clock driver has been prepared drm/mediatek: config component output by device node port chunhui dai (4): drm/mediatek: move dpi private data to device drm/mediatek: fix to get right bridge for dpi encoder drm/mediatek: add dpi driver for mt2701 and mt7623 drm/mediatek: add hdmi driver for different hardware drivers/gpu/drm/mediatek/Makefile | 4 +- drivers/gpu/drm/mediatek/mtk_dpi.c | 125 +++++++--- drivers/gpu/drm/mediatek/mtk_dpi_regs.h | 2 +- drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 14 +- drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 2 +- drivers/gpu/drm/mediatek/mtk_drm_drv.c | 38 ++- drivers/gpu/drm/mediatek/mtk_drm_drv.h | 4 +- drivers/gpu/drm/mediatek/mtk_hdmi.c | 88 +++++-- drivers/gpu/drm/mediatek/mtk_hdmi.h | 28 +++ drivers/gpu/drm/mediatek/mtk_hdmi_phy.c | 157 +++++++++++++ drivers/gpu/drm/mediatek/mtk_hdmi_regs.h | 1 + drivers/gpu/drm/mediatek/mtk_mt2701_hdmi_phy.c | 307 +++++++++++++++++++++++++ drivers/gpu/drm/mediatek/mtk_mt8173_hdmi_phy.c | 129 +---------- 13 files changed, 716 insertions(+), 183 deletions(-) create mode 100644 drivers/gpu/drm/mediatek/mtk_hdmi_phy.c create mode 100644 drivers/gpu/drm/mediatek/mtk_mt2701_hdmi_phy.c -- 2.12.5

2 8

[PATCH v3 1/3] drm/panel: Add RGB666 variant of Innolux AT070TN90
by Paul Kocialkowski 08 May '18

08 May '18

This adds timings for the RGB666 variant of the Innolux AT070TN90 panel, as found on the Ainol AW1 tablet. The panel also supports RGB888 output. When RGB666 mode is used instead, the two extra lanes per component are grounded. In the future, it might become necessary to introduce a dedicated device-tree property to specify the bus format and maybe specify it in the mode description instead of panel description so that the appropriate mode can be selected for each bus format. Signed-off-by: Paul Kocialkowski <contact(a)paulk.fr> --- drivers/gpu/drm/panel/panel-simple.c | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/drivers/gpu/drm/panel/panel-simple.c b/drivers/gpu/drm/panel/panel-simple.c index cbf1ab404ee7..351742df8ee1 100644 --- a/drivers/gpu/drm/panel/panel-simple.c +++ b/drivers/gpu/drm/panel/panel-simple.c @@ -1086,6 +1086,29 @@ static const struct panel_desc innolux_at070tn92 = { .bus_format = MEDIA_BUS_FMT_RGB888_1X24, }; +static const struct drm_display_mode innolux_at070tn90_mode = { + .clock = 40000, + .hdisplay = 800, + .hsync_start = 800 + 112, + .hsync_end = 800 + 112 + 1, + .htotal = 800 + 112 + 1 + 87, + .vdisplay = 480, + .vsync_start = 480 + 141, + .vsync_end = 480 + 141 + 1, + .vtotal = 480 + 141 + 1 + 38, + .vrefresh = 60, +}; + +static const struct panel_desc innolux_at070tn90 = { + .modes = &innolux_at070tn90_mode, + .num_modes = 1, + .size = { + .width = 154, + .height = 86, + }, + .bus_format = MEDIA_BUS_FMT_RGB666_1X18, +}; + static const struct display_timing innolux_g101ice_l01_timing = { .pixelclock = { 60400000, 71100000, 74700000 }, .hactive = { 1280, 1280, 1280 }, @@ -2154,6 +2177,9 @@ static const struct of_device_id platform_of_match[] = { }, { .compatible = "innolux,at070tn92", .data = &innolux_at070tn92, + }, { + .compatible = "innolux,at070tn90", + .data = &innolux_at070tn90, }, { .compatible ="innolux,g101ice-l01", .data = &innolux_g101ice_l01 -- 2.17.0

2 7

[PATCH] drm/etnaviv: mmuv2: support 40 bit phys address
by Lucas Stach 08 May '18

08 May '18

MMUv2 supports up to 40 bits of physical address by folding the upper 8 bits into bits [4:11] of the PTE. Signed-off-by: Lucas Stach <l.stach(a)pengutronix.de> --- drivers/gpu/drm/etnaviv/etnaviv_iommu_v2.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/etnaviv/etnaviv_iommu_v2.c b/drivers/gpu/drm/etnaviv/etnaviv_iommu_v2.c index 2d9d09608bc2..f2e4fa773e22 100644 --- a/drivers/gpu/drm/etnaviv/etnaviv_iommu_v2.c +++ b/drivers/gpu/drm/etnaviv/etnaviv_iommu_v2.c @@ -87,11 +87,14 @@ static int etnaviv_iommuv2_map(struct etnaviv_iommu_domain *domain, struct etnaviv_iommuv2_domain *etnaviv_domain = to_etnaviv_domain(domain); int mtlb_entry, stlb_entry, ret; - u32 entry = (u32)paddr | MMUv2_PTE_PRESENT; + u32 entry = lower_32_bits(paddr) | MMUv2_PTE_PRESENT; if (size != SZ_4K) return -EINVAL; + if (IS_ENABLED(CONFIG_PHYS_ADDR_T_64BIT)) + entry |= (upper_32_bits(paddr) & 0xff) << 4; + if (prot & ETNAVIV_PROT_WRITE) entry |= MMUv2_PTE_WRITEABLE; -- 2.17.0

1 0

[Bug 105786] System freeze, amdgpu 4.17-WIP, 4.16.0-rc1-576e538e5fe6
by bugzilla-daemon＠freedesktop.org 08 May '18

08 May '18

https://bugs.freedesktop.org/show_bug.cgi?id=105786 Bug ID: 105786 Summary: System freeze, amdgpu 4.17-WIP, 4.16.0-rc1-576e538e5fe6 Product: DRI Version: DRI git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: chris(a)degree.at Hi, I'm using drm-next-4.17-wip (4.16.0-rc1-576e538e5fe6) on a HP Envy x360 15-bq101ng. The system freezes with the following in journalctl -b -1: [ 0.000000] Linux version 4.16.0-rc1-576e538e5fe6 (chris@bb8) (gcc version 7.3.1 20180312 (GCC)) --snip Mar 28 14:54:48 bb8 kernel: [drm] amdgpu kernel modesetting enabled. Mar 28 14:54:48 bb8 kernel: fb: switching to amdgpudrmfb from EFI VGA Mar 28 14:54:48 bb8 kernel: amdgpu 0000:04:00.0: enabling device (0006 -> 0007) Mar 28 14:54:48 bb8 kernel: amdgpu 0000:04:00.0: VRAM: 256M 0x000000F400000000 - 0x000000F40FFFFFFF (256M used) Mar 28 14:54:48 bb8 kernel: amdgpu 0000:04:00.0: GTT: 1024M 0x000000F500000000 - 0x000000F53FFFFFFF Mar 28 14:54:48 bb8 kernel: [drm] amdgpu: 256M of VRAM memory ready Mar 28 14:54:48 bb8 kernel: [drm] amdgpu: 3072M of GTT memory ready. Mar 28 14:54:49 bb8 kernel: amdgpu: [powerplay] dpm has been enabled Mar 28 14:54:49 bb8 kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3 Mar 28 14:54:49 bb8 kernel: fbcon: amdgpudrmfb (fb0) is primary device Mar 28 14:54:49 bb8 kernel: amdgpu 0000:04:00.0: fb0: amdgpudrmfb frame buffer device Mar 28 14:54:49 bb8 kernel: amdgpu 0000:04:00.0: ring 0(gfx) uses VM inv eng 4 on hub 0 Mar 28 14:54:49 bb8 kernel: amdgpu 0000:04:00.0: ring 1(comp_1.0.0) uses VM inv eng 5 on hub 0 Mar 28 14:54:49 bb8 kernel: amdgpu 0000:04:00.0: ring 2(comp_1.1.0) uses VM inv eng 6 on hub 0 Mar 28 14:54:49 bb8 kernel: amdgpu 0000:04:00.0: ring 3(comp_1.2.0) uses VM inv eng 7 on hub 0 Mar 28 14:54:49 bb8 kernel: amdgpu 0000:04:00.0: ring 4(comp_1.3.0) uses VM inv eng 8 on hub 0 Mar 28 14:54:49 bb8 kernel: amdgpu 0000:04:00.0: ring 5(comp_1.0.1) uses VM inv eng 9 on hub 0 Mar 28 14:54:49 bb8 kernel: amdgpu 0000:04:00.0: ring 6(comp_1.1.1) uses VM inv eng 10 on hub 0 Mar 28 14:54:49 bb8 kernel: amdgpu 0000:04:00.0: ring 7(comp_1.2.1) uses VM inv eng 11 on hub 0 Mar 28 14:54:49 bb8 kernel: amdgpu 0000:04:00.0: ring 8(comp_1.3.1) uses VM inv eng 12 on hub 0 Mar 28 14:54:49 bb8 kernel: amdgpu 0000:04:00.0: ring 9(kiq_2.1.0) uses VM inv eng 13 on hub 0 Mar 28 14:54:49 bb8 kernel: amdgpu 0000:04:00.0: ring 10(sdma0) uses VM inv eng 4 on hub 1 Mar 28 14:54:49 bb8 kernel: amdgpu 0000:04:00.0: ring 11(vcn_dec) uses VM inv eng 5 on hub 1 Mar 28 14:54:49 bb8 kernel: amdgpu 0000:04:00.0: ring 12(vcn_enc0) uses VM inv eng 6 on hub 1 Mar 28 14:54:49 bb8 kernel: amdgpu 0000:04:00.0: ring 13(vcn_enc1) uses VM inv eng 7 on hub 1 Mar 28 14:54:49 bb8 kernel: [drm] Initialized amdgpu 3.25.0 20150101 for 0000:04:00.0 on minor 0 ---snip Mar 28 15:01:01 bb8 CROND[1427]: (root) CMD (run-parts /etc/cron.hourly) Mar 28 15:10:26 bb8 systemd[1]: Starting Cleanup of Temporary Directories... Mar 28 15:10:26 bb8 systemd[1]: Started Cleanup of Temporary Directories. Mar 28 15:10:50 bb8 kernel: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 1us * 10 tries - optc1_lock line:628 Mar 28 15:10:50 bb8 kernel: WARNING: CPU: 0 PID: 697 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:195 generic_reg_wait+0xdb/0x150 [amdgpu] Mar 28 15:10:50 bb8 kernel: Modules linked in: ctr ccm joydev mousedev msr nls_iso8859_1 nls_cp437 vfat fat hid_sensor_accel_3d hid_sensor_gyro_3d hid_sensor_incl_3d hid_sensor_rot> Mar 28 15:10:50 bb8 kernel: aes_x86_64 drm snd_pcm crypto_simd evdev glue_helper cfg80211 input_leds cryptd syscopyarea sysfillrect psmouse mac_hid snd_timer sysimgblt pcspkr fb_s> Mar 28 15:10:50 bb8 kernel: CPU: 0 PID: 697 Comm: gnome-shell Tainted: G C 4.16.0-rc1-576e538e5fe6 #5 Mar 28 15:10:50 bb8 kernel: Hardware name: HP HP ENVY x360 Convertible 15-bq1xx/83C6, BIOS F.13 11/10/2017 Mar 28 15:10:50 bb8 kernel: RIP: 0010:generic_reg_wait+0xdb/0x150 [amdgpu] Mar 28 15:10:50 bb8 kernel: RSP: 0018:ffffbf7ac22ef928 EFLAGS: 00010297 Mar 28 15:10:50 bb8 kernel: RAX: 0000000000000000 RBX: 000000000000000b RCX: 0000000000000000 Mar 28 15:10:50 bb8 kernel: RDX: 0000000000000000 RSI: ffff9ead0ea16418 RDI: ffff9ead0ea16418 Mar 28 15:10:50 bb8 kernel: RBP: 0000000000000001 R08: 00000000000003a4 R09: 0000000000000001 Mar 28 15:10:50 bb8 kernel: R10: 0000000000000002 R11: ffffffffaf55b42d R12: 0000000000000008 Mar 28 15:10:50 bb8 kernel: R13: ffff9ead083f1d80 R14: 0000000000000100 R15: 0000000000000001 Mar 28 15:10:50 bb8 kernel: FS: 00007f06506c5a00(0000) GS:ffff9ead0ea00000(0000) knlGS:0000000000000000 Mar 28 15:10:50 bb8 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 28 15:10:50 bb8 kernel: CR2: 00007f05fc175000 CR3: 00000003f33b2000 CR4: 00000000003406f0 Mar 28 15:10:50 bb8 kernel: Call Trace: Mar 28 15:10:50 bb8 kernel: optc1_lock+0x9e/0xb0 [amdgpu] Mar 28 15:10:50 bb8 kernel: dcn10_pipe_control_lock.part.25+0x27/0x70 [amdgpu] Mar 28 15:10:50 bb8 kernel: dcn10_apply_ctx_for_surface+0xf3/0x11f0 [amdgpu] Mar 28 15:10:50 bb8 kernel: ? dma_fence_wait_timeout+0x33/0x100 Mar 28 15:10:50 bb8 kernel: ? hubbub1_verify_allow_pstate_change_high+0xaa/0x1b0 [amdgpu] Mar 28 15:10:50 bb8 kernel: ? dcn10_verify_allow_pstate_change_high+0x18/0x20 [amdgpu] Mar 28 15:10:50 bb8 kernel: ? dcn10_set_bandwidth+0x275/0x2c0 [amdgpu] Mar 28 15:10:50 bb8 kernel: dc_commit_state+0x28b/0x580 [amdgpu] Mar 28 15:10:50 bb8 kernel: ? set_freesync_on_streams.part.6+0x92/0x260 [amdgpu] Mar 28 15:10:50 bb8 kernel: ? mod_freesync_set_user_enable+0x14e/0x190 [amdgpu] Mar 28 15:10:50 bb8 kernel: amdgpu_dm_atomic_commit_tail+0x361/0xce0 [amdgpu] Mar 28 15:10:50 bb8 kernel: ? amdgpu_bo_pin_restricted+0x1c9/0x2d0 [amdgpu] Mar 28 15:10:50 bb8 kernel: ? wait_for_completion_timeout+0x10f/0x130 Mar 28 15:10:50 bb8 kernel: ? wait_for_completion_interruptible+0x11e/0x170 Mar 28 15:10:50 bb8 kernel: ? dm_plane_helper_prepare_fb+0xdb/0x270 [amdgpu] Mar 28 15:10:50 bb8 kernel: commit_tail+0x3a/0x70 [drm_kms_helper] Mar 28 15:10:50 bb8 kernel: drm_atomic_helper_commit+0xfc/0x110 [drm_kms_helper] Mar 28 15:10:50 bb8 kernel: drm_atomic_connector_commit_dpms+0xe4/0xf0 [drm] Mar 28 15:10:50 bb8 kernel: drm_mode_obj_set_property_ioctl+0x174/0x290 [drm] Mar 28 15:10:50 bb8 kernel: ? drm_mode_obj_find_prop_id+0x40/0x40 [drm] Mar 28 15:10:50 bb8 kernel: drm_ioctl_kernel+0x59/0xb0 [drm] Mar 28 15:10:50 bb8 kernel: drm_ioctl+0x29c/0x340 [drm] Mar 28 15:10:50 bb8 kernel: ? drm_mode_obj_find_prop_id+0x40/0x40 [drm] Mar 28 15:10:50 bb8 kernel: ? eventfd_read+0xc9/0x250 Mar 28 15:10:50 bb8 kernel: amdgpu_drm_ioctl+0x49/0x80 [amdgpu] Mar 28 15:10:50 bb8 kernel: do_vfs_ioctl+0xa1/0x610 Mar 28 15:10:50 bb8 kernel: SyS_ioctl+0x74/0x80 Mar 28 15:10:50 bb8 kernel: do_syscall_64+0x62/0x120 Mar 28 15:10:50 bb8 kernel: entry_SYSCALL_64_after_hwframe+0x21/0x86 Mar 28 15:10:50 bb8 kernel: RIP: 0033:0x7f0650042d87 Mar 28 15:10:50 bb8 kernel: RSP: 002b:00007ffe4a78a568 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Mar 28 15:10:50 bb8 kernel: RAX: ffffffffffffffda RBX: 0000561ca87d3230 RCX: 00007f0650042d87 Mar 28 15:10:50 bb8 kernel: RDX: 00007ffe4a78a5a0 RSI: 00000000c01864ba RDI: 000000000000000b Mar 28 15:10:50 bb8 kernel: RBP: 00007ffe4a78a5a0 R08: 0000000000000000 R09: 0000000000000002 Mar 28 15:10:50 bb8 kernel: R10: 0000561ca87fbee8 R11: 0000000000000246 R12: 00000000c01864ba Mar 28 15:10:50 bb8 kernel: R13: 000000000000000b R14: 00007ffe4a78a7a0 R15: 00007f064f51e930 Mar 28 15:10:50 bb8 kernel: Code: 44 24 58 48 8b 4c 24 50 89 ee 48 c7 c7 b0 35 34 c1 8b 54 24 48 44 89 4c 24 08 e8 b1 ae 5b ff 41 83 7d 20 01 44 8b 4c 24 08 74 02 <0f> ff 48 83 c4 > Mar 28 15:10:50 bb8 kernel: ---[ end trace 73026ca0ecb74ff2 ]--- -- snip Networkmanager Mar 28 15:14:50 bb8 gnome-shell[697]: Screen lock is locked down, not locking Mar 28 15:14:50 bb8 kernel: ------------[ cut here ]------------ Mar 28 15:14:50 bb8 kernel: kernel BUG at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:4789! Mar 28 15:14:50 bb8 kernel: invalid opcode: 0000 [#1] PREEMPT SMP NOPTI Mar 28 15:14:50 bb8 kernel: Modules linked in: ctr ccm joydev mousedev msr nls_iso8859_1 nls_cp437 vfat fat hid_sensor_accel_3d hid_sensor_gyro_3d hid_sensor_incl_3d hid_sensor_rot> Mar 28 15:14:50 bb8 kernel: aes_x86_64 drm snd_pcm crypto_simd evdev glue_helper cfg80211 input_leds cryptd syscopyarea sysfillrect psmouse mac_hid snd_timer sysimgblt pcspkr fb_s> Mar 28 15:14:50 bb8 kernel: CPU: 2 PID: 697 Comm: gnome-shell Tainted: G WC 4.16.0-rc1-576e538e5fe6 #5 Mar 28 15:14:50 bb8 kernel: Hardware name: HP HP ENVY x360 Convertible 15-bq1xx/83C6, BIOS F.13 11/10/2017 Mar 28 15:14:50 bb8 kernel: RIP: 0010:dm_update_crtcs_state+0x345/0x3b0 [amdgpu] Mar 28 15:14:50 bb8 kernel: RSP: 0018:ffffbf7ac22efb50 EFLAGS: 00010246 Mar 28 15:14:50 bb8 kernel: RAX: 0000000000000000 RBX: ffff9ead0851a000 RCX: 000000000003d702 Mar 28 15:14:50 bb8 kernel: RDX: 000000000003d682 RSI: ffff9ead0eaa2d80 RDI: ffff9ead0e406e80 Mar 28 15:14:50 bb8 kernel: RBP: ffff9eacfa5d1800 R08: 0000000000022d80 R09: ffffffffc123b3db Mar 28 15:14:50 bb8 kernel: R10: ffffe46a4f9e4600 R11: 0000000000000001 R12: 0000000000000000 Mar 28 15:14:50 bb8 kernel: R13: ffff9eace791ec00 R14: ffff9eace791dc00 R15: ffff9eacde9c1f80 Mar 28 15:14:50 bb8 kernel: FS: 00007f06506c5a00(0000) GS:ffff9ead0ea80000(0000) knlGS:0000000000000000 Mar 28 15:14:50 bb8 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Mar 28 15:14:50 bb8 kernel: CR2: 000016a6f2d63218 CR3: 00000003f33b2000 CR4: 00000000003406e0 Mar 28 15:14:50 bb8 kernel: Call Trace: Mar 28 15:14:50 bb8 kernel: amdgpu_dm_atomic_check+0x29f/0x4d0 [amdgpu] Mar 28 15:14:50 bb8 kernel: drm_atomic_check_only+0x336/0x4e0 [drm] Mar 28 15:14:50 bb8 kernel: drm_atomic_commit+0x13/0x50 [drm] Mar 28 15:14:50 bb8 kernel: drm_atomic_connector_commit_dpms+0xe4/0xf0 [drm] Mar 28 15:14:50 bb8 kernel: drm_mode_obj_set_property_ioctl+0x174/0x290 [drm] Mar 28 15:14:50 bb8 kernel: ? drm_mode_obj_find_prop_id+0x40/0x40 [drm] Mar 28 15:14:50 bb8 kernel: drm_ioctl_kernel+0x59/0xb0 [drm] Mar 28 15:14:50 bb8 kernel: drm_ioctl+0x29c/0x340 [drm] Mar 28 15:14:50 bb8 kernel: ? drm_mode_obj_find_prop_id+0x40/0x40 [drm] Mar 28 15:14:50 bb8 kernel: ? eventfd_read+0xc9/0x250 Mar 28 15:14:50 bb8 kernel: amdgpu_drm_ioctl+0x49/0x80 [amdgpu] Mar 28 15:14:50 bb8 kernel: do_vfs_ioctl+0xa1/0x610 Mar 28 15:14:50 bb8 kernel: SyS_ioctl+0x74/0x80 Mar 28 15:14:50 bb8 kernel: do_syscall_64+0x62/0x120 Mar 28 15:14:50 bb8 kernel: entry_SYSCALL_64_after_hwframe+0x21/0x86 Mar 28 15:14:50 bb8 kernel: RIP: 0033:0x7f0650042d87 Mar 28 15:14:50 bb8 kernel: RSP: 002b:00007ffe4a78a568 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Mar 28 15:14:50 bb8 kernel: RAX: ffffffffffffffda RBX: 0000561ca87d3230 RCX: 00007f0650042d87 Mar 28 15:14:50 bb8 kernel: RDX: 00007ffe4a78a5a0 RSI: 00000000c01864ba RDI: 000000000000000b Mar 28 15:14:50 bb8 kernel: RBP: 00007ffe4a78a5a0 R08: 0000000000000003 R09: 0000000000000002 Mar 28 15:14:50 bb8 kernel: R10: 0000561ca87fbee8 R11: 0000000000000246 R12: 00000000c01864ba Mar 28 15:14:50 bb8 kernel: R13: 000000000000000b R14: 00007ffe4a78a7a0 R15: 00007f064f51e930 Mar 28 15:14:50 bb8 kernel: Code: 18 c6 00 01 0f 84 f7 fd ff ff e9 e9 fd ff ff 45 0f b6 4d 0a 41 f6 c1 0e 0f 84 5d fd ff ff 48 c7 04 24 00 00 00 00 e9 16 fe ff ff <0f> 0b 48 83 bb > Mar 28 15:14:50 bb8 kernel: RIP: dm_update_crtcs_state+0x345/0x3b0 [amdgpu] RSP: ffffbf7ac22efb50 Mar 28 15:14:50 bb8 kernel: ---[ end trace 73026ca0ecb74ff3 ]--- -- snip Networkmanager Mar 28 15:14:50 bb8 kernel: PM: suspend entry (deep) ---end -- You are receiving this mail because: You are the assignee for the bug.

1 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel May 2018