All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105018] Kernel panic when waking up after screen goes blank.
Date: Sat, 23 Jun 2018 13:26:26 +0000	[thread overview]
Message-ID: <bug-105018-502-rp7wfG6YfU@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105018-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 7652 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=105018

--- Comment #35 from Adam Bolte <abolte@systemsaviour.com> ---
I believe I've been seeing the same bug as of late.

[Sat Jun 23 23:02:04 2018] ------------[ cut here ]------------
[Sat Jun 23 23:02:04 2018] kernel BUG at
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:4713!
[Sat Jun 23 23:02:04 2018] invalid opcode: 0000 [#1] SMP PTI
[Sat Jun 23 23:02:04 2018] Modules linked in: ipt_REJECT(E) nf_reject_ipv4(E)
tun(E) bridge(E) stp(E) llc(E) fuse(E) ebtable_filter(E) ebtables(E)
ip6table_filter(E) ip6_tables(E) snd_hrtimer(E) snd_seq_midi(E)
snd_seq_midi_event(E) snd_rawmidi(E) snd_seq(E) snd_seq_device(E)
cpufreq_conservative(E) cpufreq_powersave(E) cpufreq_userspace(E)
nf_log_ipv4(E) nf_log_common(E) xt_LOG(E) xt_multiport(E) xt_conntrack(E)
iptable_filter(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) iptable_nat(E)
nf_conntrack_ipv4(E) nf_defrag_ipv4(E) nf_nat_ipv4(E) nf_nat(E) nf_conntrack(E)
xt_CHECKSUM(E) xt_tcpudp(E) iptable_mangle(E) binfmt_misc(E) nls_ascii(E)
nls_cp437(E) vfat(E) fat(E) mxm_wmi(E) amdkfd(E) snd_hda_codec_realtek(E)
snd_hda_codec_generic(E) amdgpu(E) intel_rapl(E) x86_pkg_temp_thermal(E)
intel_powerclamp(E) snd_hda_codec_hdmi(E)
[Sat Jun 23 23:02:04 2018]  chash(E) gpu_sched(E) snd_hda_intel(E) kvm_intel(E)
ttm(E) snd_hda_codec(E) efi_pstore(E) drm_kms_helper(E) snd_hda_core(E)
snd_pcsp(E) kvm(E) snd_hwdep(E) snd_pcm_oss(E) drm(E) irqbypass(E)
snd_mixer_oss(E) intel_cstate(E) snd_pcm(E) mei_me(E) i2c_algo_bit(E)
intel_uncore(E) snd_timer(E) coretemp(E) vhba(OE) snd(E) iTCO_wdt(E)
intel_rapl_perf(E) efivars(E) joydev(E) evdev(E) iTCO_vendor_support(E)
soundcore(E) shpchp(E) mei(E) sg(E) intel_pch_thermal(E) wmi(E) video(E)
acpi_pad(E) button(E) nfsd(E) auth_rpcgss(E) nfs_acl(E) lockd(E) grace(E)
parport_pc(E) ppdev(E) sunrpc(E) lp(E) parport(E) efivarfs(E) ip_tables(E)
x_tables(E) autofs4(E) ext4(E) crc16(E) mbcache(E) jbd2(E) fscrypto(E) btrfs(E)
zstd_decompress(E) zstd_compress(E) xxhash(E) algif_skcipher(E) af_alg(E)
raid10(E) raid456(E)
[Sat Jun 23 23:02:04 2018]  async_raid6_recov(E) async_memcpy(E) async_pq(E)
async_xor(E) async_tx(E) xor(E) raid6_pq(E) libcrc32c(E) crc32c_generic(E)
raid1(E) multipath(E) linear(E) dm_mirror(E) dm_region_hash(E) dm_log(E)
dm_crypt(E) dm_mod(E) raid0(E) md_mod(E) hid_generic(E) usbhid(E) hid(E)
sr_mod(E) cdrom(E) sd_mod(E) uas(E) usb_storage(E) crct10dif_pclmul(E)
crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) pcbc(E) aesni_intel(E)
ahci(E) xhci_pci(E) aes_x86_64(E) libahci(E) crypto_simd(E) nvme(E) xhci_hcd(E)
cryptd(E) glue_helper(E) libata(E) i2c_i801(E) alx(E) mdio(E) nvme_core(E)
scsi_mod(E) usbcore(E) fan(E) thermal(E)
[Sat Jun 23 23:02:04 2018] CPU: 2 PID: 1340 Comm: Xorg Tainted: G        W  OE 
   4.17.2+ #2
[Sat Jun 23 23:02:04 2018] Hardware name: MSI MS-7976/Z170A GAMING M7
(MS-7976), BIOS 1.J0 12/07/2017
[Sat Jun 23 23:02:04 2018] RIP: 0010:dm_update_crtcs_state+0x424/0x4b0 [amdgpu]
[Sat Jun 23 23:02:04 2018] RSP: 0018:ffffb84fc4affa90 EFLAGS: 00010246
[Sat Jun 23 23:02:04 2018] RAX: 0000000000000000 RBX: ffff9d7e34528280 RCX:
fffff1505f079c9f
[Sat Jun 23 23:02:04 2018] RDX: 0000000000000017 RSI: ffff9d7e41f63800 RDI:
0000000000000286
[Sat Jun 23 23:02:04 2018] RBP: 0000000000000000 R08: 0000000000000000 R09:
0000000000000000
[Sat Jun 23 23:02:04 2018] R10: ffffb84fc4affa90 R11: 00000000000005a0 R12:
ffff9d7e41f63800
[Sat Jun 23 23:02:04 2018] R13: ffff9d7ec0f61800 R14: ffff9d7ec66a8c00 R15:
0000000000000000
[Sat Jun 23 23:02:04 2018] FS:  00007f614ec0ba40(0000)
GS:ffff9d7eeec80000(0000) knlGS:0000000000000000
[Sat Jun 23 23:02:04 2018] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[Sat Jun 23 23:02:04 2018] CR2: 00007f1dbb1ec0c8 CR3: 000000081aa56005 CR4:
00000000003606e0
[Sat Jun 23 23:02:04 2018] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[Sat Jun 23 23:02:04 2018] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7:
0000000000000400
[Sat Jun 23 23:02:04 2018] Call Trace:
[Sat Jun 23 23:02:04 2018]  amdgpu_dm_atomic_check+0x1a1/0x3d0 [amdgpu]
[Sat Jun 23 23:02:04 2018]  drm_atomic_check_only+0x3f3/0x4f0 [drm]
[Sat Jun 23 23:02:04 2018]  ? handle_conflicting_encoders+0x26c/0x280
[drm_kms_helper]
[Sat Jun 23 23:02:04 2018]  drm_atomic_commit+0x13/0x50 [drm]
[Sat Jun 23 23:02:04 2018]  drm_atomic_helper_set_config+0x67/0x90
[drm_kms_helper]
[Sat Jun 23 23:02:04 2018]  __drm_mode_set_config_internal+0x67/0x110 [drm]
[Sat Jun 23 23:02:04 2018]  drm_mode_setcrtc+0x452/0x5a0 [drm]
[Sat Jun 23 23:02:04 2018]  ? amdgpu_cs_wait_ioctl+0xe5/0x160 [amdgpu]
[Sat Jun 23 23:02:04 2018]  ? drm_mode_getcrtc+0x170/0x170 [drm]
[Sat Jun 23 23:02:04 2018]  drm_ioctl_kernel+0x67/0xb0 [drm]
[Sat Jun 23 23:02:04 2018]  drm_ioctl+0x2d1/0x390 [drm]
[Sat Jun 23 23:02:04 2018]  ? drm_mode_getcrtc+0x170/0x170 [drm]
[Sat Jun 23 23:02:04 2018]  amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
[Sat Jun 23 23:02:04 2018]  do_vfs_ioctl+0xa2/0x620
[Sat Jun 23 23:02:04 2018]  ? __x64_sys_futex+0x88/0x180
[Sat Jun 23 23:02:04 2018]  ksys_ioctl+0x70/0x80
[Sat Jun 23 23:02:04 2018]  __x64_sys_ioctl+0x16/0x20
[Sat Jun 23 23:02:04 2018]  do_syscall_64+0x55/0x100
[Sat Jun 23 23:02:04 2018]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[Sat Jun 23 23:02:04 2018] RIP: 0033:0x7f614c650dd7
[Sat Jun 23 23:02:04 2018] RSP: 002b:00007ffd9280d9d8 EFLAGS: 00000246
ORIG_RAX: 0000000000000010
[Sat Jun 23 23:02:04 2018] RAX: ffffffffffffffda RBX: 000000000000000d RCX:
00007f614c650dd7
[Sat Jun 23 23:02:04 2018] RDX: 00007ffd9280da10 RSI: 00000000c06864a2 RDI:
000000000000000d
[Sat Jun 23 23:02:04 2018] RBP: 00007ffd9280da10 R08: 0000000000000000 R09:
000055a69128dca0
[Sat Jun 23 23:02:04 2018] R10: 00007ffd9280dad0 R11: 0000000000000246 R12:
00000000c06864a2
[Sat Jun 23 23:02:04 2018] R13: 000000000000000d R14: 000055a690954b90 R15:
000055a69128dca0
[Sat Jun 23 23:02:04 2018] Code: 4c 89 ee 48 89 c7 e8 bc f5 ff ff 84 c0 0f 84
b7 fe ff ff e9 a0 fe ff ff 48 83 b8 08 0d 00 00 00 0f 85 67 ff ff ff e9 f5 fe
ff ff <0f> 0b 41 8b 4f 60 48 c7 c2 d0 95 c7 c0 48 c7 c6 a0 57 ca c0 bf 
[Sat Jun 23 23:02:04 2018] RIP: dm_update_crtcs_state+0x424/0x4b0 [amdgpu] RSP:
ffffb84fc4affa90
[Sat Jun 23 23:02:04 2018] ---[ end trace 293f9551ffc27adc ]---

This is on a Fiji card. I have a 144Hz FreeSync-capable monitor, and can easily
reproduce the error with this command (where 143.86 is the xrandr-advertised
maximum frequency):

xrandr --output DisplayPort-0 --mode 2560x1440 --rate 143.86 --set "scaling
mode" "Full aspect"

Interestingly xrandr reports 59.95*+ as the current frequency, but my monitor
says 144Hz. I tried firing up Grey Goo under Wine and that game reports my
monitor running at 144Hz also. If I just run:

xrandr --output DisplayPort-0 --mode 2560x1440 --rate 143.86

then xrandr correctly reports 143.86* indicating that that frequency is now
selected.

I can also run the following:

xrandr --output DisplayPort-0 --mode 2560x1440 --set "scaling mode" "Full
aspect"

But if I combine these options as per the first command above, I get GUI crash.

The symptoms are simiar. In my case the screen is still on (not blank) but
completely frozen. I was able to SSH in to get the above trace from the dmesg
command. The machine cannot successfully shutdown or reboot and I need to
physically hard reset the box at this point.

As others have said, this is definitely a regression. This didn't happen in
older kernels.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 8491 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-06-23 13:26 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09  1:13 [Bug 105018] Kernel panic when waking up after screen goes blank bugzilla-daemon
2018-02-09  1:16 ` bugzilla-daemon
2018-02-09  9:21 ` bugzilla-daemon
2018-02-10 17:25 ` bugzilla-daemon
2018-02-10 17:31 ` bugzilla-daemon
2018-02-11  0:32 ` bugzilla-daemon
2018-02-12 15:55 ` bugzilla-daemon
2018-02-13  3:30 ` bugzilla-daemon
2018-02-13  3:38 ` bugzilla-daemon
2018-02-13 16:13 ` bugzilla-daemon
2018-02-13 16:13 ` bugzilla-daemon
2018-02-13 16:13 ` bugzilla-daemon
2018-02-13 16:14 ` bugzilla-daemon
2018-02-13 16:14 ` bugzilla-daemon
2018-02-13 18:40 ` bugzilla-daemon
2018-02-14  5:55 ` bugzilla-daemon
2018-02-14  6:14 ` bugzilla-daemon
2018-02-14  6:52 ` bugzilla-daemon
2018-02-14 14:35 ` bugzilla-daemon
2018-02-14 16:13 ` bugzilla-daemon
2018-02-15 20:59 ` bugzilla-daemon
2018-02-23 23:23 ` bugzilla-daemon
2018-02-27  5:23 ` bugzilla-daemon
2018-03-16  0:40 ` bugzilla-daemon
2018-03-20  0:55 ` bugzilla-daemon
2018-03-22  0:09 ` bugzilla-daemon
2018-03-24 12:49 ` bugzilla-daemon
2018-03-24 12:58 ` bugzilla-daemon
2018-03-26  1:25 ` bugzilla-daemon
2018-04-12  0:41 ` bugzilla-daemon
2018-04-12  4:19 ` bugzilla-daemon
2018-04-13  0:25 ` bugzilla-daemon
2018-04-30 14:10 ` bugzilla-daemon
2018-04-30 14:55 ` bugzilla-daemon
2018-05-01 13:37 ` bugzilla-daemon
2018-05-01 13:56 ` bugzilla-daemon
2018-06-23 13:26 ` bugzilla-daemon [this message]
2018-06-27 18:51 ` bugzilla-daemon
2018-07-05  5:56 ` bugzilla-daemon
2018-07-05  6:03 ` bugzilla-daemon
2018-09-06 18:12 ` bugzilla-daemon
2018-09-07  7:40 ` bugzilla-daemon
2018-09-07 22:35 ` bugzilla-daemon
2018-12-10 14:47 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-105018-502-rp7wfG6YfU@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.