Results 1 to 1 of 1
  1. #1
    ROG Member Array
    Join Date
    Nov 2017
    Reputation
    10
    Posts
    22

    Exclamation [GL702ZC] Kernel Panic when waking up after screen went blank.

    I'm running latest Manjaro and this problem existed since day one. At first I could not find out exactly why, but eventually after looking at journalctl I was able to find traces of kernel oops panics.

    I'm able to easily reproduce it by doing the following:
    1. Lock the screen, let it keep blank for a while (for at least 3 minutes).
    2. Try to wake the screen up by moving the mouse.

    The screen would not wake up and the computer appeared crashed. It's 100% reproducible and could be done on a fresh boot. I don't think the modules are related as it happened after fresh installs, before I eventually install the software I needed.

    This is the log about one of the times that it happened. Apparently the culprit appears to be dce110_vblank_set+0x4f/0xb0 [amdgpu] with the topmost function in the call trace being amdgpu_dm_set_crtc_irq_state+0x31/0x60 [amdgpu].

    I'm doing this on 4.15 kernel, but I recall the same problem occurred on 4.14 as well. It does not appear to be related to the DC, either.

    Code:
    Feb 03 08:28:23 linuxsys kernel: BUG: unable to handle kernel NULL pointer dereference at (null)
    Feb 03 08:28:23 linuxsys kernel: IP: dce110_vblank_set+0x4f/0xb0 [amdgpu]
    Feb 03 08:28:23 linuxsys kernel: PGD 7d8afd067 P4D 7d8afd067 PUD 7d8b00067 PMD 0
    Feb 03 08:28:23 linuxsys kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
    Feb 03 08:28:23 linuxsys kernel: Modules linked in: vmw_vsock_vmci_transport vsock cmac rfcomm fuse bnep vmnet(O) amdkfd amd_iommu_v2 amdgpu arc4 iwlmvm btusb btrtl btbcm btintel edac_mce_amd mac80211 kvm_amd wmi_bmof serio bluetooth ax8817
    Feb 03 08:28:23 linuxsys kernel: sysfillrect rfkill sysimgblt rng_core fb_sys_fops soundcore tpm_crb shpchp wmi tpm_tis thermal ac tpm_tis_core battery video tpm i2c_hid asus_wireless button acpi_cpufreq sch_fq_codel vmmon(O) vmw_vmci vbox
    Feb 03 08:28:23 linuxsys kernel: CPU: 8 PID: 1492 Comm: xfwm4 Tainted: G O 4.15.0-1-MANJARO #1
    Feb 03 08:28:23 linuxsys kernel: Hardware name: ASUSTeK COMPUTER INC. GL702ZC/GL702ZC, BIOS GL702ZC.303 12/15/2017
    Feb 03 08:28:23 linuxsys kernel: RIP: 0010:dce110_vblank_set+0x4f/0xb0 [amdgpu]
    Feb 03 08:28:23 linuxsys kernel: RSP: 0018:ffff9ee388c7bbe0 EFLAGS: 00010002
    Feb 03 08:28:23 linuxsys kernel: RAX: ffff90d8ddbb0000 RBX: 0000000000000001 RCX: 0000000000000000
    Feb 03 08:28:23 linuxsys kernel: RDX: 0000000000000000 RSI: 000000000000000c RDI: 0000000000000000
    Feb 03 08:28:23 linuxsys kernel: RBP: ffff90db7178a880 R08: 0000000000000000 R09: 0000000000000000
    Feb 03 08:28:23 linuxsys kernel: R10: 00007ffdbffc9720 R11: ffff90db791c3b00 R12: ffff90db6a806700
    Feb 03 08:28:23 linuxsys kernel: R13: ffffffffc0e99ba0 R14: ffff90db69200000 R15: ffff90db6a37ab68
    Feb 03 08:28:23 linuxsys kernel: FS: 00007f22ddf93980(0000) GS:ffff90db7e800000(0000) knlGS:0000000000000000
    Feb 03 08:28:23 linuxsys kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Feb 03 08:28:23 linuxsys kernel: CR2: 0000000000000000 CR3: 00000007f9bf6000 CR4: 00000000003406e0
    Feb 03 08:28:23 linuxsys kernel: Call Trace:
    Feb 03 08:28:23 linuxsys kernel: amdgpu_dm_set_crtc_irq_state+0x31/0x60 [amdgpu]
    Feb 03 08:28:23 linuxsys kernel: amdgpu_irq_update+0x55/0x90 [amdgpu]
    Feb 03 08:28:23 linuxsys kernel: drm_vblank_enable+0x84/0x100 [drm]
    Feb 03 08:28:23 linuxsys kernel: drm_vblank_get+0x8d/0xb0 [drm]
    Feb 03 08:28:23 linuxsys kernel: drm_wait_vblank_ioctl+0x12a/0x690 [drm]
    Feb 03 08:28:23 linuxsys kernel: ? unix_stream_recvmsg+0x53/0x70
    Feb 03 08:28:23 linuxsys kernel: ? drm_legacy_modeset_ctl_ioctl+0x100/0x100 [drm]
    Feb 03 08:28:23 linuxsys kernel: drm_ioctl_kernel+0x5b/0xb0 [drm]
    Feb 03 08:28:23 linuxsys kernel: drm_ioctl+0x2d5/0x370 [drm]
    Feb 03 08:28:23 linuxsys kernel: ? drm_legacy_modeset_ctl_ioctl+0x100/0x100 [drm]
    Feb 03 08:28:23 linuxsys kernel: ? do_iter_write+0xdc/0x190
    Feb 03 08:28:23 linuxsys kernel: ? vfs_writev+0xb9/0x110
    Feb 03 08:28:23 linuxsys kernel: amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
    Feb 03 08:28:23 linuxsys kernel: do_vfs_ioctl+0xa4/0x630
    Feb 03 08:28:23 linuxsys kernel: ? __sys_recvmsg+0x4e/0x90
    Feb 03 08:28:23 linuxsys kernel: ? __sys_recvmsg+0x7d/0x90
    Feb 03 08:28:23 linuxsys kernel: SyS_ioctl+0x74/0x80
    Feb 03 08:28:23 linuxsys kernel: entry_SYSCALL_64_fastpath+0x20/0x83
    Feb 03 08:28:23 linuxsys kernel: RIP: 0033:0x7f22da5dfd87
    Feb 03 08:28:23 linuxsys kernel: RSP: 002b:00007ffdbffc9768 EFLAGS: 00000246
    Feb 03 08:28:23 linuxsys kernel: Code: e8 17 20 04 00 83 e8 4e 0f b6 d0 48 89 d0 48 c1 e0 05 48 01 d0 48 c1 e0 05 49 03 86 60 01 00 00 84 db 48 8b b8 78 02 00 00 74 18 <48> 8b 07 be 02 00 00 00 48 8b 80 d8 00 00 00 e8 6d 63 c0 cf 84
    Feb 03 08:28:23 linuxsys kernel: RIP: dce110_vblank_set+0x4f/0xb0 [amdgpu] RSP: ffff9ee388c7bbe0
    Feb 03 08:28:23 linuxsys kernel: CR2: 0000000000000000
    Feb 03 08:28:23 linuxsys kernel: —[ end trace 0e2fa94fe7517dd5 ]—
    When I was trying to debug and reproduce the problem I found additional error lines talking about NULL, too.
    Apparently I found something different, which seems to be related and could be found before the actual kernel panic.
    Code:
    Feb 07 15:59:11 linuxsys kernel: [drm] {1920x1080, 2080x1111@138700Khz}
    Feb 07 15:59:19 linuxsys kernel: [drm] RBRx2 pass VS=1, PE=0
    Feb 07 15:59:19 linuxsys kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR* dc_stream_state is NULL for crtc '1'!
    Feb 07 15:59:19 linuxsys kernel: [drm:dm_crtc_get_scanoutpos [amdgpu]] *ERROR* dc_stream_state is NULL for crtc '1'!
    Feb 07 15:59:19 linuxsys kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR* dc_stream_state is NULL for crtc '1'!
    Feb 07 15:59:19 linuxsys kernel: WARNING: CPU: 0 PID: 1520 at drivers/gpu/drm/drm_vblank.c:612 drm_calc_vbltimestamp_from_scanoutpos+0x2c5/0x340 [drm]
    Feb 07 15:59:19 linuxsys kernel: Modules linked in: vmw_vsock_vmci_transport vsock cmac rfcomm fuse bnep vmnet(O) nls_iso8859_1 nls_cp437 vfat fat arc4 amdkfd amd_iommu_v2 btusb iwlmvm btrtl amdgpu btbcm btintel uvcvideo videobuf2_vmalloc m
    Feb 07 15:59:19 linuxsys kernel:  glue_helper cryptd pcspkr k10temp i2c_piix4 shpchp wmi thermal battery ac tpm_crb tpm_tis tpm_tis_core asus_wireless video tpm i2c_hid button acpi_cpufreq sch_fq_codel vmmon(O) vmw_vmci vboxnetflt(O) vboxne
    Feb 07 15:59:19 linuxsys kernel: CPU: 0 PID: 1520 Comm: xfwm4 Tainted: G           O     4.15.0-1-MANJARO #1
    Feb 07 15:59:19 linuxsys kernel: Hardware name: ASUSTeK COMPUTER INC. GL702ZC/GL702ZC, BIOS GL702ZC.303 12/15/2017
    Feb 07 15:59:19 linuxsys kernel: RIP: 0010:drm_calc_vbltimestamp_from_scanoutpos+0x2c5/0x340 [drm]
    Feb 07 15:59:19 linuxsys kernel: RSP: 0018:ffffb26203adbb50 EFLAGS: 00010086
    Feb 07 15:59:19 linuxsys kernel: RAX: ffffffffc12994c0 RBX: ffff9af8fa453800 RCX: 0000000000000001
    Feb 07 15:59:19 linuxsys kernel: RDX: ffffffffc09dd068 RSI: 0000000000000001 RDI: ffffffffc09db0d8
    Feb 07 15:59:19 linuxsys kernel: RBP: ffffb26203adbbb8 R08: 0000000000000000 R09: ffffffffc09bd4a0
    Feb 07 15:59:19 linuxsys kernel: R10: ffffffffc10bf320 R11: ffffffffa756c36d R12: 0000000000000001
    Feb 07 15:59:19 linuxsys kernel: R13: ffffb26203adbbcc R14: ffffb26203adbc00 R15: ffff9af8f1d8f000
    Feb 07 15:59:19 linuxsys kernel: FS:  00007fa7ed48e980(0000) GS:ffff9af8fe600000(0000) knlGS:0000000000000000
    Feb 07 15:59:19 linuxsys kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Feb 07 15:59:19 linuxsys kernel: CR2: 00007fb70910f000 CR3: 00000007d95f4000 CR4: 00000000003406f0
    Feb 07 15:59:19 linuxsys kernel: Call Trace:
    Feb 07 15:59:09 linuxsys systemd[9201]: Started Virtual filesystem service.
    Feb 07 15:59:11 linuxsys kernel: [drm] {1920x1080, 2080x1111@138700Khz}
    Feb 07 15:59:19 linuxsys kernel: [drm] RBRx2 pass VS=1, PE=0
    Feb 07 15:59:19 linuxsys kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR* dc_stream_state is NULL for crtc '1'!
    Feb 07 15:59:19 linuxsys kernel: [drm:dm_crtc_get_scanoutpos [amdgpu]] *ERROR* dc_stream_state is NULL for crtc '1'!
    Feb 07 15:59:19 linuxsys kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR* dc_stream_state is NULL for crtc '1'!
    Feb 07 15:59:19 linuxsys kernel: WARNING: CPU: 0 PID: 1520 at drivers/gpu/drm/drm_vblank.c:612 drm_calc_vbltimestamp_from_scanoutpos+0x2c5/0x340 [drm]
    Feb 07 15:59:19 linuxsys kernel: Modules linked in: vmw_vsock_vmci_transport vsock cmac rfcomm fuse bnep vmnet(O) nls_iso8859_1 nls_cp437 vfat fat arc4 amdkfd amd_iommu_v2 btusb iwlmvm btrtl amdgpu btbcm btintel uvcvideo videobuf2_vmalloc m
    Feb 07 15:59:19 linuxsys kernel:  glue_helper cryptd pcspkr k10temp i2c_piix4 shpchp wmi thermal battery ac tpm_crb tpm_tis tpm_tis_core asus_wireless video tpm i2c_hid button acpi_cpufreq sch_fq_codel vmmon(O) vmw_vmci vboxnetflt(O) vboxne
    Feb 07 15:59:19 linuxsys kernel: CPU: 0 PID: 1520 Comm: xfwm4 Tainted: G           O     4.15.0-1-MANJARO #1
    Feb 07 15:59:19 linuxsys kernel: Hardware name: ASUSTeK COMPUTER INC. GL702ZC/GL702ZC, BIOS GL702ZC.303 12/15/2017
    Feb 07 15:59:19 linuxsys kernel: RIP: 0010:drm_calc_vbltimestamp_from_scanoutpos+0x2c5/0x340 [drm]
    Feb 07 15:59:19 linuxsys kernel: RSP: 0018:ffffb26203adbb50 EFLAGS: 00010086
    Feb 07 15:59:19 linuxsys kernel: RAX: ffffffffc12994c0 RBX: ffff9af8fa453800 RCX: 0000000000000001
    Feb 07 15:59:19 linuxsys kernel: RDX: ffffffffc09dd068 RSI: 0000000000000001 RDI: ffffffffc09db0d8
    Feb 07 15:59:19 linuxsys kernel: RBP: ffffb26203adbbb8 R08: 0000000000000000 R09: ffffffffc09bd4a0
    Feb 07 15:59:19 linuxsys kernel: R10: ffffffffc10bf320 R11: ffffffffa756c36d R12: 0000000000000001
    Feb 07 15:59:19 linuxsys kernel: R13: ffffb26203adbbcc R14: ffffb26203adbc00 R15: ffff9af8f1d8f000
    Feb 07 15:59:19 linuxsys kernel: FS:  00007fa7ed48e980(0000) GS:ffff9af8fe600000(0000) knlGS:0000000000000000
    Feb 07 15:59:19 linuxsys kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    Feb 07 15:59:19 linuxsys kernel: CR2: 00007fb70910f000 CR3: 00000007d95f4000 CR4: 00000000003406f0
    Feb 07 15:59:19 linuxsys kernel: Call Trace:
    Feb 07 15:59:19 linuxsys kernel:  drm_get_last_vbltimestamp+0x54/0x90 [drm]
    Feb 07 15:59:19 linuxsys kernel:  drm_update_vblank_count+0x77/0x250 [drm]
    Feb 07 15:59:19 linuxsys kernel:  drm_vblank_enable+0xbd/0x100 [drm]
    Feb 07 15:59:19 linuxsys kernel:  drm_vblank_get+0x8d/0xb0 [drm]
    Feb 07 15:59:19 linuxsys kernel:  drm_wait_vblank_ioctl+0x12a/0x690 [drm]
    Feb 07 15:59:19 linuxsys kernel:  ? unix_stream_recvmsg+0x53/0x70
    Feb 07 15:59:19 linuxsys kernel:  ? drm_legacy_modeset_ctl_ioctl+0x100/0x100 [drm]
    Feb 07 15:59:19 linuxsys kernel:  drm_ioctl_kernel+0x5b/0xb0 [drm]
    Feb 07 15:59:19 linuxsys kernel:  drm_ioctl+0x2d5/0x370 [drm]
    Feb 07 15:59:19 linuxsys kernel:  ? drm_legacy_modeset_ctl_ioctl+0x100/0x100 [drm]
    Feb 07 15:59:19 linuxsys kernel:  ? do_iter_write+0xdc/0x190
    Feb 07 15:59:19 linuxsys kernel:  ? vfs_writev+0xb9/0x110
    Feb 07 15:59:19 linuxsys kernel:  amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
    Feb 07 15:59:19 linuxsys kernel:  do_vfs_ioctl+0xa4/0x630
    Feb 07 15:59:19 linuxsys kernel:  ? __sys_recvmsg+0x4e/0x90
    Feb 07 15:59:19 linuxsys kernel:  ? __sys_recvmsg+0x7d/0x90
    Feb 07 15:59:19 linuxsys kernel:  SyS_ioctl+0x74/0x80
    Feb 07 15:59:19 linuxsys kernel:  entry_SYSCALL_64_fastpath+0x20/0x83
    Feb 07 15:59:19 linuxsys kernel: RIP: 0033:0x7fa7e9adbd87
    Feb 07 15:59:19 linuxsys kernel: RSP: 002b:00007ffcb824e6e8 EFLAGS: 00000246
    Feb 07 15:59:19 linuxsys kernel: Code: e1 48 c7 c2 68 d0 9d c0 be 01 00 00 00 48 c7 c7 d8 b0 9d c0 e8 1d 66 fe ff 48 8b 83 98 03 00 00 48 83 78 20 00 0f 84 6f fd ff ff <0f> ff e9 68 fd ff ff 48 c7 c2 30 d0 9d c0 31 f6 48 c7 c7 d5 b0 
    Feb 07 15:59:19 linuxsys kernel: ---[ end trace 84870e1685606f71 ]---
    Feb 07 15:59:19 linuxsys kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR* dc_stream_state is NULL for crtc '1'!
    Feb 07 15:59:19 linuxsys kernel: [drm:dm_crtc_get_scanoutpos [amdgpu]] *ERROR* dc_stream_state is NULL for crtc '1'!
    Feb 07 15:59:19 linuxsys kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR* dc_stream_state is NULL for crtc '1'!
    Feb 07 15:59:27 linuxsys kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR* dc_stream_state is NULL for crtc '1'!
    Feb 07 15:59:27 linuxsys kernel: [drm:dm_crtc_get_scanoutpos [amdgpu]] *ERROR* dc_stream_state is NULL for crtc '1'!
    Feb 07 15:59:27 linuxsys kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR* dc_stream_state is NULL for crtc '1'!
    Feb 07 15:59:27 linuxsys kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR* dc_stream_state is NULL for crtc '1'!
    Feb 07 15:59:27 linuxsys kernel: [drm:dm_crtc_get_scanoutpos [amdgpu]] *ERROR* dc_stream_state is NULL for crtc '1'!
    Feb 07 15:59:27 linuxsys kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR* dc_stream_state is NULL for crtc '1'!
    Are any other Linux users experiencing such problems with this laptop? At first I though it might be the distro so I posted about it on the Manjaro forums. I once thought about using a custom kernel as I did not know what the cause was back then, but I didn't have time, and it's not as convenient as in actual Arch Linux to do so. With the new discoveries, I believe the distro had nothing to do with this. As I could not find similar bugs reported elsewhere else so I think it might be both driver and device related.

    For the time being, I could only mitigate it by disabling whatever that could cause the screen go blank in the Power Management options, and avoid locking the screen if possible (as it can also blank the screen). As I also use the laptop for work, I often risk losing work progress because of this...

    EDIT 2: Apparently this is a kernel issue and this device is not the only one affected. I've filed a bug report here, and at present, patches were made available which fixed the crashing issue as far as I have tested.
    Last edited by lss41771; 02-15-2018 at 05:37 AM. Reason: It's a kernel issue and patches were available.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •