Bug 106276

Summary: general protection fault in dc_validate_global_state on raven ridge
Product: DRI Reporter: ojab <ojab>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium CC: harry.wentland
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
stacktace in more readable format none

Description ojab 2018-04-27 08:31:55 UTC 
Raven ridge APU (2400g), no external GPU, linux-4.17-rc2, libdrm-2.4.91, mesa-18.1.0-rc1, xorg-server-1.19.6, xf86-video-amdgpu-18.0.1.

just happened after starting `X`:

[Fri Apr 27 08:25:55 2018] general protection fault: 0000 [#1] SMP NOPTI
[Fri Apr 27 08:25:55 2018] Modules linked in: nfnetlink_queue nfnetlink_log nfnetlink nfsd auth_rpcgss oid_registry nfs_acl lockd grace sunrpc sit tunnel4 ip_tunnel af_packet bridge stp llc ipv6 ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_conntrack iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_filter ip_tables x_tables tcp_bbr sch_fq_codel arc4 joydev input_leds hid_generic usbhid hid btrfs libcrc32c xor zstd_compress lzo_compress zlib_deflate raid6_pq zstd_decompress xxhash zlib_inflate lzo_decompress amdgpu edac_mce_amd kvm_amd kvm mfd_core chash ath10k_pci gpu_sched drm_kms_helper ath10k_core syscopyarea sysfillrect sysimgblt fb_sys_fops ttm snd_hda_codec_realtek irqbypass ath crc32_pclmul crc32c_intel snd_hda_codec_generic drm snd_hda_codec_hdmi mac80211 evdev pps_ldisc pps_core
[Fri Apr 27 08:25:55 2018]  snd_hda_intel drm_panel_orientation_quirks cfbfillrect cfbimgblt snd_hda_codec cfbcopyarea snd_hwdep 8250 i2c_algo_bit snd_hda_core fb xhci_pci sp5100_tco cfg80211 8250_base font snd_pcm xhci_hcd fbdev aesni_intel i2c_piix4 mpt3sas r8169 serial_core snd_timer i2c_core rtc_cmos aes_x86_64 snd crypto_simd cryptd usbcore hwmon video glue_helper soundcore mii backlight raid_class scsi_transport_sas button usb_common acpi_cpufreq processor unix
[Fri Apr 27 08:25:55 2018] CPU: 0 PID: 8835 Comm: Xorg.wrap Tainted: G        W       T 4.17.0-rc2-ojab #6
[Fri Apr 27 08:25:55 2018] RIP: 0010:resource_build_scaling_params+0x733/0x10c0 [amdgpu]
[Fri Apr 27 08:25:55 2018] RSP: 0018:ffffa498c1367b48 EFLAGS: 00010296
[Fri Apr 27 08:25:55 2018] RAX: 3a8d12265423e785 RBX: ffff8f66cb5ace18 RCX: 00000000fffffffe
[Fri Apr 27 08:25:55 2018] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 000000024ee4a102
[Fri Apr 27 08:25:55 2018] RBP: 000000004ee4a102 R08: 000000000000043a R09: 000000000004ce16
[Fri Apr 27 08:25:55 2018] R10: 7fffffffffffffff R11: 0000000000000001 R12: ffff8f66cb5ace28
[Fri Apr 27 08:25:55 2018] R13: 0000000000000009 R14: 0000000000000000 R15: ffff8f6ded8e1400
[Fri Apr 27 08:25:55 2018] FS:  00007f9e41779700(0000) GS:ffff8f6e5ee00000(0000) knlGS:0000000000000000
[Fri Apr 27 08:25:55 2018] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[Fri Apr 27 08:25:55 2018] CR2: 00007f9e40dffad3 CR3: 000000008b5d0000 CR4: 00000000003406f0
[Fri Apr 27 08:25:55 2018] Call Trace:
[Fri Apr 27 08:25:55 2018]  resource_build_scaling_params_for_context+0x2a/0x50 [amdgpu]
[Fri Apr 27 08:25:55 2018]  dc_validate_global_state+0x232/0x2b0 [amdgpu]
[Fri Apr 27 08:25:55 2018]  amdgpu_dm_atomic_check+0x399/0x3b0 [amdgpu]
[Fri Apr 27 08:25:55 2018]  drm_atomic_check_only+0x360/0x520 [drm]
[Fri Apr 27 08:25:55 2018]  ? drm_atomic_add_affected_connectors+0x128/0x140 [drm]
[Fri Apr 27 08:25:55 2018]  drm_atomic_commit+0x1e/0x70 [drm]
[Fri Apr 27 08:25:55 2018]  restore_fbdev_mode_atomic+0x1a8/0x210 [drm_kms_helper]
[Fri Apr 27 08:25:55 2018]  drm_fb_helper_restore_fbdev_mode_unlocked+0x61/0xa0 [drm_kms_helper]
[Fri Apr 27 08:25:55 2018]  drm_lastclose+0x30/0xc0 [drm]
[Fri Apr 27 08:25:55 2018]  drm_release+0x2ae/0x360 [drm]
[Fri Apr 27 08:25:55 2018]  __fput+0xec/0x210
[Fri Apr 27 08:25:55 2018]  task_work_run+0x96/0xc0
[Fri Apr 27 08:25:55 2018]  exit_to_usermode_loop+0xa5/0xb0
[Fri Apr 27 08:25:55 2018]  do_syscall_64+0xed/0x110
[Fri Apr 27 08:25:55 2018]  entry_SYSCALL_64_after_hwframe+0x49/0xbe
[Fri Apr 27 08:25:55 2018] RIP: 0033:0x7f9e4105d5c0
[Fri Apr 27 08:25:55 2018] RSP: 002b:00007ffdd8f4bb58 EFLAGS: 00000246 ORIG_RAX: 0000000000000003
[Fri Apr 27 08:25:55 2018] RAX: 0000000000000000 RBX: 00007ffdd8f4bbc0 RCX: 00007f9e4105d5c0
[Fri Apr 27 08:25:55 2018] RDX: 00007ffdd8f4bb80 RSI: 00000000c04064a0 RDI: 0000000000000003
[Fri Apr 27 08:25:55 2018] RBP: 0000000000000000 R08: 00007f9e40dff500 R09: 0000000000000000
[Fri Apr 27 08:25:55 2018] R10: 00007ffdd8f4b920 R11: 0000000000000246 R12: 0000000000000003
[Fri Apr 27 08:25:55 2018] R13: 0000000000000001 R14: 0000000000000001 R15: 00007ffdd8f4bbc0
[Fri Apr 27 08:25:55 2018] Code: 48 8b 40 48 e8 cf 10 e3 fb 84 c0 75 70 8b 4b 2c 8b 53 28 44 8b 4b 30 44 8b 43 34 41 8b b7 8c 00 00 00 88 44 24 38 48 8b 44 24
40 <48> 8b 78 10 89 74 24 28 41 8b b7 88 00 00 00 89 74 24 20 41 8b
[Fri Apr 27 08:25:55 2018] RIP: resource_build_scaling_params+0x733/0x10c0 [amdgpu] RSP: ffffa498c1367b48
[Fri Apr 27 08:25:55 2018] ---[ end trace 46e852690de93abb ]---


and next `X` just hangs doing nothing. Don't know how reproducible it is because I'm not using Xorg due to https://bugs.freedesktop.org/show_bug.cgi?id=106260
Comment 1 ojab 2018-04-27 08:33:09 UTC 
Created attachment 139161 [details]
stacktace in more readable format
Comment 2 Harry Wentland 2018-06-28 22:23:06 UTC 
I'm a bit confused. You mention this happens after starting X, and also mention you don't use Xorg. Can you clarify?

What kernel are you using?
Comment 3 ojab 2018-06-29 07:14:53 UTC 
It was from vanilla linux-4.17-rc2, "I'm not using X" should be read as "I'm not using X day-to-day".
Comment 4 Martin Peres 2019-11-19 08:36:21 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/355.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.