From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 85351] 3.17-rc5 hangs on Supermicro X8DAH system
Date: Thu, 26 May 2016 23:02:56 +0000 [thread overview]
Message-ID: <bug-85351-2300-xtX8xIgGeW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-85351-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=85351
Joseph Bisch <joseph.bisch@hpe.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |joseph.bisch@hpe.com
--- Comment #2 from Joseph Bisch <joseph.bisch@hpe.com> ---
Happens to me too with 4.5.3-2_bpo8+1 from Debian jessie-backports. Attaching
kern.log, but relevant output is:
May 26 16:31:39 bl460gen9-03 kernel: [ 57.554859] fb: switching to
mgag200drmfb from simple
May 26 16:31:39 bl460gen9-03 kernel: [ 57.802070] Console: switching to
colour dummy device 80x25
May 26 16:31:39 bl460gen9-03 kernel: [ 58.075534] [drm:mgag200_driver_load
[mgag200]] *ERROR* can't reserve VRAM
May 26 16:31:39 bl460gen9-03 kernel: [ 58.402739] mgag200 0000:01:00.1: Fatal
error during GPU init: -6
--
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:[~2016-05-26 23:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-85351-2300@https.bugzilla.kernel.org/>
2014-10-23 15:54 ` [Bug 85351] 3.17-rc5 hangs on Supermicro X8DAH system bugzilla-daemon
2016-05-26 23:02 ` bugzilla-daemon [this message]
2016-05-26 23:03 ` bugzilla-daemon
2016-05-26 23:14 ` bugzilla-daemon
2016-06-08 23:23 ` 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-85351-2300-xtX8xIgGeW@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