All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 201727] Hardware Error reported on Ryzen 5 2500U
Date: Sat, 05 Jan 2019 01:20:14 +0000	[thread overview]
Message-ID: <bug-201727-2300-CSC9L1oc2M@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-201727-2300@https.bugzilla.kernel.org/>

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

--- Comment #14 from tones111@hotmail.com ---
I'm experiencing this bug on a Lenovo E585.  My boot logs also show only "256M
of VRAM memory ready" when running 4.19.12 or commit 284dec4317c8.  4.19.12
boots fine, but the commit in question causes a lockup.

Is there any data I can collect or patches to test to support resolving this? 
Thanks for any insight or direction.

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

  parent reply	other threads:[~2019-01-05  1:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19  9:25 [Bug 201727] New: Hardware Error reported on Ryzen 5 2500U bugzilla-daemon
2018-11-19  9:26 ` [Bug 201727] " 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 [this message]
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-CSC9L1oc2M@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.