dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101391] New: Lockup after resume (kernel BUG at include/drm/drm_mm.h:145!)
Date: Sun, 12 Jul 2015 09:12:10 +0000	[thread overview]
Message-ID: <bug-101391-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 101391
           Summary: Lockup after resume (kernel BUG at
                    include/drm/drm_mm.h:145!)
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.1
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: harn-solo@gmx.de
        Regression: No

Created attachment 182481
  --> https://bugzilla.kernel.org/attachment.cgi?id=182481&action=edit
dmesg log

Hi,

since kernel version 4.1 (4.1.1, 4.1.2) shortly (5-10s) after a resume from
s2ram, the system freezes. See attached log. This bug is reproducible.

Thanks.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2015-07-12  9:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-12  9:12 bugzilla-daemon [this message]
2015-07-13  1:58 ` [Bug 101391] Lockup after resume (kernel BUG at include/drm/drm_mm.h:145!) bugzilla-daemon
2015-07-13 18:42 ` bugzilla-daemon
2015-08-05 17:17 ` bugzilla-daemon
2015-08-06  2:12 ` bugzilla-daemon
2015-08-12  9:01 ` bugzilla-daemon
2015-08-12  9:12 ` bugzilla-daemon
2015-09-26 16:37 ` 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-101391-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