public inbox for dri-devel@lists.freedesktop.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 199357] New: amdgpu: hang a few seconds after logging in, most likely due to regression
Date: Wed, 11 Apr 2018 12:26:54 +0000	[thread overview]
Message-ID: <bug-199357-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=199357

            Bug ID: 199357
           Summary: amdgpu: hang a few seconds after logging in, most
                    likely due to regression
           Product: Drivers
           Version: 2.5
    Kernel Version: v4.16
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: master.homer@gmail.com
        Regression: No

Created attachment 275291
  --> https://bugzilla.kernel.org/attachment.cgi?id=275291&action=edit
Kernel log of the hang/crash

I've been testing kernel v4.16 on my computer, but it's basically unusable -
because after a few seconds or so after logging in it will do a soft lockup,
and I can't even switch to VT. I was, however, able to ssh in to it, which is
how I was able to get the kernel log. Right as the hang happened, I can see
this in the log:
Apr 11 14:04:13 homer-desktop kernel: [   45.532038]
[drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR*
[CRTC:45:crtc-1] flip_done timed out
Apr 11 14:04:23 homer-desktop kernel: [   55.772028]
[drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR*
[PLANE:37:plane-1] flip_done timed out
Apr 11 14:04:33 homer-desktop kernel: [   66.012282]
[drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] *ERROR*
[PLANE:44:plane-7] flip_done timed out

and after that is the regular kernel crash.

I have tried this on both v4.16 and v4.16.1 with the same results. However, it
doesn't happen on v4.15 (which is what I'm running now). So there must be some
kind of regression between those releases.

I am running stable KDE neon (which is based on Ubuntu LTS) with precompiled
kernels from the ubuntu mainline ppa.

-- 
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

             reply	other threads:[~2018-04-11 12:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-11 12:26 bugzilla-daemon [this message]
2018-04-11 12:27 ` [Bug 199357] amdgpu: hang a few seconds after logging in, most likely due to regression bugzilla-daemon
2018-04-11 13:37 ` bugzilla-daemon
2018-04-11 17:37 ` bugzilla-daemon
2018-04-11 18:35 ` bugzilla-daemon
2018-04-11 20:36 ` bugzilla-daemon
2018-04-12  8:06 ` bugzilla-daemon
2018-04-12 11:41 ` bugzilla-daemon
2018-04-12 11:42 ` bugzilla-daemon
2018-04-13 10:16 ` bugzilla-daemon
2018-04-17  7:03 ` bugzilla-daemon
2018-04-17 14:59 ` 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-199357-2300@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox