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 201727] New: Hardware Error reported on Ryzen 5 2500U
Date: Mon, 19 Nov 2018 09:25:33 +0000	[thread overview]
Message-ID: <bug-201727-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 201727
           Summary: Hardware Error reported on Ryzen 5 2500U
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.20-rc3
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: misko.herko@gmail.com
        Regression: No

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

How to reproduce: Boot and start any graphical application, for example gdm
Expected: gdm will start
Actual: screen goes black, with the cursor visible in top left corner,
log is full of [Hardware Error]

I have bisected the bug, it seems it is introduced in commit
284dec4317c8e76f45d3ce922f673c80331812f1.

let me know if you think the hardware is actually broken, but i have had no
issues on windows, and no hardware errors on 4.19 kernel.

-- 
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-11-19  9:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19  9:25 bugzilla-daemon [this message]
2018-11-19  9:26 ` [Bug 201727] Hardware Error reported on Ryzen 5 2500U bugzilla-daemon
2018-11-19  9:26 ` bugzilla-daemon
2018-11-19  9:27 ` bugzilla-daemon
2018-11-19 10:58 ` bugzilla-daemon
2018-11-19 11:03 ` bugzilla-daemon
2018-11-19 11:40 ` bugzilla-daemon
2018-11-19 11:47 ` bugzilla-daemon
2018-11-19 11:48 ` bugzilla-daemon
2018-11-19 12:50 ` bugzilla-daemon
2018-11-19 16:31 ` bugzilla-daemon
2018-12-09 21:01 ` bugzilla-daemon
2018-12-17  5:43 ` bugzilla-daemon
2018-12-29 21:06 ` bugzilla-daemon
2019-01-05  1:20 ` bugzilla-daemon
2019-01-07  4:30 ` bugzilla-daemon
2019-01-18 20:43 ` bugzilla-daemon
2019-01-24 12:53 ` 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-201727-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