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: Wed, 14 Feb 2018 06:52:04 +0000	[thread overview]
Message-ID: <bug-105018-502-NZus8boSDl@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105018-502@http.bugs.freedesktop.org/>


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

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

--- Comment #16 from L.S.S. <ragnaros39216@yandex.com> ---
Just installed and booted the new kernel. It seems to have fixed the issue at
least to the extent that it would not totally crash the system like it used to.

However, I still see these in journalctl. This is after I locked the screen
then wake the screen up 3 times.

1st time:

Feb 14 14:35:17 linuxsys kernel: [drm:dm_logger_write [amdgpu]] *ERROR* Failed
to get VBLANK!
Feb 14 14:35:37 linuxsys kernel: [drm:dm_logger_write [amdgpu]] *ERROR* Failed
to get VBLANK!
Feb 14 14:35:57 linuxsys kernel: [drm:dm_logger_write [amdgpu]] *ERROR* Failed
to get VBLANK!
Feb 14 14:36:10 linuxsys kernel: [drm] {1920x1080, 2080x1111@138700Khz}
...
Feb 14 14:36:17 linuxsys kernel: [drm] RBRx2 pass VS=1, PE=0
Feb 14 14:36:17 linuxsys kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR*
dc_stream_state is NULL for crtc '1'!
Feb 14 14:36:17 linuxsys kernel: [drm:dm_crtc_get_scanoutpos [amdgpu]] *ERROR*
dc_stream_state is NULL for crtc '1'!
Feb 14 14:36:17 linuxsys kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR*
dc_stream_state is NULL for crtc '1'!
Feb 14 14:36:17 linuxsys kernel: WARNING: CPU: 10 PID: 1485 at
drivers/gpu/drm/drm_vblank.c:612
drm_calc_vbltimestamp_from_scanoutpos+0x2c5/0x340 [drm]
Feb 14 14:36:17 linuxsys kernel: Modules linked in: cmac rfcomm fuse bnep
vmnet(O) arc4 nls_iso8859_1 nls_cp437 vfat fat amdkfd amd_iommu_v2 amdgpu
iwlmvm ax88179_178a usbnet mac80211 mii uvcvideo btusb videobuf2_vmalloc btrtl
videobuf2_mem
Feb 14 14:36:17 linuxsys kernel:  rng_core tpm_tis tpm_tis_core k10temp shpchp
battery ac rtc_cmos wmi i2c_piix4 tpm asus_wireless i2c_hid pinctrl_amd
gpio_amdpt evdev mac_hid acpi_cpufreq sch_fq_codel vmmon(O) vmw_vmci
vboxnetflt(O) vboxne
Feb 14 14:36:17 linuxsys kernel: CPU: 10 PID: 1485 Comm: xfwm4 Tainted: G      
    O     4.15.3-1-MANJARO #1
Feb 14 14:36:17 linuxsys kernel: Hardware name: ASUSTeK COMPUTER INC.
GL702ZC/GL702ZC, BIOS GL702ZC.303 12/15/2017
Feb 14 14:36:17 linuxsys kernel: RIP:
0010:drm_calc_vbltimestamp_from_scanoutpos+0x2c5/0x340 [drm]
Feb 14 14:36:17 linuxsys kernel: RSP: 0018:ffffa97548adfb30 EFLAGS: 00010082
Feb 14 14:36:17 linuxsys kernel: RAX: ffffffffc15e54c0 RBX: ffff8a1375ae6800
RCX: 0000000000000001
Feb 14 14:36:17 linuxsys kernel: RDX: ffffffffc0d4d380 RSI: 0000000000000001
RDI: ffffffffc0d4b24e
Feb 14 14:36:17 linuxsys kernel: RBP: ffffa97548adfb98 R08: 0000000000000000
R09: ffffffffc0d2c870
Feb 14 14:36:17 linuxsys kernel: R10: ffffffffc140b320 R11: ffffffffb15c7f2d
R12: 0000000000000001
Feb 14 14:36:17 linuxsys kernel: R13: ffffa97548adfbac R14: ffffa97548adfbe0
R15: ffff8a1377b6a000
Feb 14 14:36:17 linuxsys kernel: FS:  00007f2e273eb980(0000)
GS:ffff8a137e880000(0000) knlGS:0000000000000000
Feb 14 14:36:17 linuxsys kernel: CS:  0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Feb 14 14:36:17 linuxsys kernel: CR2: 00007feda6f5a000 CR3: 00000007da154000
CR4: 00000000003406e0
Feb 14 14:36:17 linuxsys kernel: Call Trace:
Feb 14 14:36:17 linuxsys kernel:  ? set_cursor+0x80/0x80
Feb 14 14:36:17 linuxsys kernel:  ? set_cursor+0x80/0x80
Feb 14 14:36:17 linuxsys kernel:  drm_get_last_vbltimestamp+0x54/0x90 [drm]
Feb 14 14:36:17 linuxsys kernel:  drm_update_vblank_count+0x77/0x250 [drm]
Feb 14 14:36:17 linuxsys kernel:  drm_vblank_enable+0xbd/0x100 [drm]
Feb 14 14:36:17 linuxsys kernel:  drm_vblank_get+0x8d/0xb0 [drm]
Feb 14 14:36:17 linuxsys kernel:  drm_wait_vblank_ioctl+0x12a/0x6a0 [drm]
Feb 14 14:36:17 linuxsys kernel:  ? unix_stream_recvmsg+0x53/0x70
Feb 14 14:36:17 linuxsys kernel:  ? drm_legacy_modeset_ctl_ioctl+0x100/0x100
[drm]
Feb 14 14:36:17 linuxsys kernel:  drm_ioctl_kernel+0x5b/0xb0 [drm]
Feb 14 14:36:17 linuxsys kernel:  drm_ioctl+0x2d5/0x370 [drm]
Feb 14 14:36:17 linuxsys kernel:  ? drm_legacy_modeset_ctl_ioctl+0x100/0x100
[drm]
Feb 14 14:36:17 linuxsys kernel:  ? do_iter_write+0xdc/0x190
Feb 14 14:36:17 linuxsys kernel:  ? vfs_writev+0xb9/0x110
Feb 14 14:36:17 linuxsys kernel:  amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
Feb 14 14:36:17 linuxsys kernel:  do_vfs_ioctl+0xa4/0x630
Feb 14 14:36:17 linuxsys kernel:  ? __sys_recvmsg+0x4e/0x90
Feb 14 14:36:17 linuxsys kernel:  ? __sys_recvmsg+0x7d/0x90
Feb 14 14:36:17 linuxsys kernel:  SyS_ioctl+0x74/0x80
Feb 14 14:36:17 linuxsys kernel:  do_syscall_64+0x75/0x190
Feb 14 14:36:17 linuxsys kernel:  entry_SYSCALL_64_after_hwframe+0x21/0x86
Feb 14 14:36:17 linuxsys kernel: RIP: 0033:0x7f2e23a38d87
Feb 14 14:36:17 linuxsys kernel: RSP: 002b:00007ffd8b7da1c8 EFLAGS: 00000246
ORIG_RAX: 0000000000000010
Feb 14 14:36:17 linuxsys kernel: RAX: ffffffffffffffda RBX: 00007ffd8b7da1f0
RCX: 00007f2e23a38d87
Feb 14 14:36:17 linuxsys kernel: RDX: 00007ffd8b7da1f0 RSI: 00000000c018643a
RDI: 000000000000000c
Feb 14 14:36:17 linuxsys kernel: RBP: 0000000001006d10 R08: 0000000000800109
R09: 0000000000000000
Feb 14 14:36:17 linuxsys kernel: R10: 0000000000000000 R11: 0000000000000246
R12: 00000000c018643a
Feb 14 14:36:17 linuxsys kernel: R13: 000000000080619a R14: 00000000010cd380
R15: 0000000000000000
Feb 14 14:36:17 linuxsys kernel: Code: e1 48 c7 c2 80 d3 d4 c0 be 01 00 00 00
48 c7 c7 4e b2 d4 c0 e8 6d 62 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 48 d3 d4 c0 31 f6 48 c7 c7 4b b2 
Feb 14 14:36:17 linuxsys kernel: ---[ end trace e345f4b7c52fbc5c ]---
Feb 14 14:36:17 linuxsys kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR*
dc_stream_state is NULL for crtc '1'!
Feb 14 14:36:17 linuxsys kernel: [drm:dm_crtc_get_scanoutpos [amdgpu]] *ERROR*
dc_stream_state is NULL for crtc '1'!
Feb 14 14:36:17 linuxsys kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR*
dc_stream_state is NULL for crtc '1'!
Feb 14 14:36:25 linuxsys kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR*
dc_stream_state is NULL for crtc '1'!
Feb 14 14:36:25 linuxsys kernel: [drm:dm_crtc_get_scanoutpos [amdgpu]] *ERROR*
dc_stream_state is NULL for crtc '1'!
Feb 14 14:36:25 linuxsys kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR*
dc_stream_state is NULL for crtc '1'!
Feb 14 14:36:25 linuxsys kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR*
dc_stream_state is NULL for crtc '1'!
Feb 14 14:36:25 linuxsys kernel: [drm:dm_crtc_get_scanoutpos [amdgpu]] *ERROR*
dc_stream_state is NULL for crtc '1'!
Feb 14 14:36:25 linuxsys kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR*
dc_stream_state is NULL for crtc '1'!

2nd time:

Feb 14 14:40:37 linuxsys kernel: [drm:dm_logger_write [amdgpu]] *ERROR* Failed
to get VBLANK!
Feb 14 14:40:57 linuxsys kernel: [drm:dm_logger_write [amdgpu]] *ERROR* Failed
to get VBLANK!
Feb 14 14:41:17 linuxsys kernel: [drm:dm_logger_write [amdgpu]] *ERROR* Failed
to get VBLANK!
Feb 14 14:41:37 linuxsys kernel: [drm:dm_logger_write [amdgpu]] *ERROR* Failed
to get VBLANK!
Feb 14 14:41:57 linuxsys kernel: [drm:dm_logger_write [amdgpu]] *ERROR* Failed
to get VBLANK!
Feb 14 14:42:05 linuxsys kernel: [drm] {1920x1080, 2080x1111@138700Khz}

3rd time:

Feb 14 14:44:26 linuxsys kernel: [drm:dm_logger_write [amdgpu]] *ERROR* Failed
to get VBLANK!
Feb 14 14:44:46 linuxsys kernel: [drm:dm_logger_write [amdgpu]] *ERROR* Failed
to get VBLANK!

The "failed to get VBLANK" errors still appear, and the 1st time seems to have
crashed something, but the system still works, and there are no traces of
crashes like that from the 1st time, during the 2nd and 3rd time.

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

[-- Attachment #1.2: Type: text/html, Size: 8433 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-02-14  6:52 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 [this message]
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
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-NZus8boSDl@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.