From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199139] System freezes (kernel, amdgpu NULL pointer dereference) when video enters powersafe state
Date: Tue, 20 Mar 2018 07:41:14 +0000 [thread overview]
Message-ID: <bug-199139-2300-g0Zdrn1WvB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-199139-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=199139
--- Comment #5 from Eduard (wirch.eduard@gmail.com) ---
But it causes follow up problems:
kernel: [drm:dm_logger_write [amdgpu]] *ERROR* Failed to get VBLANK!
kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR* dc_stream_state is NULL
for crtc '1'!
kernel: [drm:dm_crtc_get_scanoutpos [amdgpu]] *ERROR* dc_stream_state is NULL
for crtc '1'!
kernel: [drm:dm_vblank_get_counter [amdgpu]] *ERROR* dc_stream_state is NULL
for crtc '1'!
kernel: WARNING: CPU: 10 PID: 1119 at drivers/gpu/drm/drm_vblank.c:612
drm_calc_vbltimestamp_from_scanoutpos+0x2c5/0x340 [drm]
kernel: Modules linked in: cmac rfcomm fuse ipt_MASQUERADE
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype
iptable_filter xt_conntrack nf_nat nf_conntrack libcr>
kernel: wmi_bmof mxm_wmi fb_sys_fops soundcore dca rng_core pcbc rfkill
aesni_intel aes_x86_64 crypto_simd glue_helper sp5100_tco cryptd pcspkr
i2c_piix4 k10temp shpchp rtc_cmos wmi pinctrl_amd gpio_amdpt evdev mac_hid
acpi_cpufreq crypto_user ip_tables >
kernel: CPU: 10 PID: 1119 Comm: xfwm4 Not tainted 4.15.10-1.1-MANJARO #1
kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X370
Taichi, BIOS P3.30 01/15/2018
kernel: RIP: 0010:drm_calc_vbltimestamp_from_scanoutpos+0x2c5/0x340 [drm]
kernel: RSP: 0018:ffffb128c747fb30 EFLAGS: 00010086
kernel: RAX: ffffffffc143c540 RBX: ffffa30e940cf000 RCX: 0000000000000001
kernel: RDX: ffffffffc12303c8 RSI: 0000000000000001 RDI: ffffffffc122e26e
kernel: RBP: ffffb128c747fb98 R08: 0000000000000000 R09: ffffffffc120f8b0
kernel: R10: ffffffffc1262320 R11: ffffffffb55ccf2d R12: 0000000000000001
kernel: R13: ffffb128c747fbac R14: ffffb128c747fbe0 R15: ffffa30d496af800
kernel: FS: 00007fa8a541a980(0000) GS:ffffa30edee80000(0000)
knlGS:0000000000000000
kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: 00007fbf500135b8 CR3: 0000000e7e82a000 CR4: 00000000003406e0
kernel: Call Trace:
kernel: ? set_cursor+0x80/0x80
kernel: ? set_cursor+0x80/0x80
kernel: drm_get_last_vbltimestamp+0x54/0x90 [drm]
kernel: drm_update_vblank_count+0x77/0x250 [drm]
kernel: drm_vblank_enable+0xbd/0x100 [drm]
kernel: drm_vblank_get+0x8d/0xb0 [drm]
kernel: drm_wait_vblank_ioctl+0x12a/0x660 [drm]
kernel: ? unix_stream_recvmsg+0x53/0x70
kernel: ? drm_legacy_modeset_ctl_ioctl+0x100/0x100 [drm]
kernel: drm_ioctl_kernel+0x5b/0xb0 [drm]
kernel: drm_ioctl+0x2d5/0x370 [drm]
kernel: ? drm_legacy_modeset_ctl_ioctl+0x100/0x100 [drm]
kernel: ? do_iter_write+0xdc/0x190
kernel: ? vfs_writev+0xb9/0x110
kernel: amdgpu_drm_ioctl+0x49/0x80 [amdgpu]
kernel: do_vfs_ioctl+0xa4/0x630
kernel: ? __sys_recvmsg+0x4e/0x90
kernel: ? __sys_recvmsg+0x7d/0x90
kernel: SyS_ioctl+0x74/0x80
kernel: do_syscall_64+0x74/0x190
kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2
kernel: RIP: 0033:0x7fa8a1a6fd87
kernel: RSP: 002b:00007fff3c9e7a48 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
kernel: RAX: ffffffffffffffda RBX: 00007fff3c9e7a70 RCX: 00007fa8a1a6fd87
kernel: RDX: 00007fff3c9e7a70 RSI: 00000000c018643a RDI: 000000000000000c
kernel: RBP: 0000000002251590 R08: 0000000000800105 R09: 0000000000000000
kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 00000000c018643a
kernel: R13: 0000000000801813 R14: 000000000233d510 R15: 0000000000000000
kernel: Code: e1 48 c7 c2 c8 03 23 c1 be 01 00 00 00 48 c7 c7 6e e2 22 c1 e8 5d
62 fe ff 48 8b 83 98 03 00 00 48 83 78 20 00 0f 84 6f fd ff ff <0f> 0b e9 68 fd
ff ff 48 c7 c2 90 03 23 c1 31 f6 48 c7 c7 6b e2
kernel: ---[ end trace d9312f249097de3a ]---
And the system freezes every 7s for 3s.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-03-20 7:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 9:04 [Bug 199139] New: System freezes (kernel, amdgpu NULL pointer dereference) when video enters powersafe state bugzilla-daemon
2018-03-19 9:05 ` [Bug 199139] " bugzilla-daemon
2018-03-19 9:05 ` bugzilla-daemon
2018-03-19 9:11 ` bugzilla-daemon
2018-03-19 14:49 ` bugzilla-daemon
2018-03-20 7:36 ` bugzilla-daemon
2018-03-20 7:41 ` bugzilla-daemon [this message]
2018-03-20 7:41 ` bugzilla-daemon
2018-03-20 13:23 ` bugzilla-daemon
2018-09-04 9:37 ` bugzilla-daemon
2018-09-14 6:21 ` bugzilla-daemon
2018-09-14 13:00 ` bugzilla-daemon
2018-09-17 7:09 ` bugzilla-daemon
2018-09-17 7:11 ` bugzilla-daemon
2018-09-17 7:11 ` bugzilla-daemon
2018-09-17 7:13 ` bugzilla-daemon
2018-09-24 6:50 ` bugzilla-daemon
2018-09-24 13:10 ` bugzilla-daemon
2018-10-01 13:26 ` bugzilla-daemon
2018-10-26 8:18 ` bugzilla-daemon
2018-10-26 14:58 ` bugzilla-daemon
2018-10-30 9:11 ` bugzilla-daemon
2019-01-04 7:53 ` bugzilla-daemon
2019-01-04 9:18 ` bugzilla-daemon
2019-01-07 15:22 ` 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-199139-2300-g0Zdrn1WvB@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.