All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	"Wang, Rui Y" <rui.y.wang@intel.com>,
	Dave Airlie <airlied@redhat.com>,
	"Clark, Rob" <robdclark@gmail.com>,
	"Roper, Matthew D" <matthew.d.roper@intel.com>,
	"Chen, Gong" <gong.chen@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: drm/mgag200: doesn't work in panic context
Date: Sat, 27 Jun 2015 16:12:37 +0200	[thread overview]
Message-ID: <20150627141237.GE26543@pd.tnic> (raw)
In-Reply-To: <CAKMK7uH_p3Dkt0xtSPaZwWuJvHFUVSahquzfuwR313qOOknfng@mail.gmail.com>

On Sat, Jun 27, 2015 at 03:52:56PM +0200, Daniel Vetter wrote:
> Hm, what do you mean by fixing this in the allocator? I've made some
> rough sketch of the problem space in
> http://www.x.org/wiki/DRMJanitors/ under "Make panic handling work".
> Problem is that the folks which know what to do (drm hackers) have
> zero incentive to fix it (since if you blow up a drm driver any kind
> of fbcon panic handling is hopeless anyway).

Ok, silly question: switching the GPU output to the simplest,
supported-by-all-GPUs mode before panicking is not that easy too, right?

Or does that mean, one needs to reinit GPU in order to even show
something...

Thanks.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--

  reply	other threads:[~2015-06-27 14:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26  7:55 drm/mgag200: doesn't work in panic context Rui Wang
2015-06-26  9:27 ` Daniel Vetter
2015-06-26 18:30   ` Luck, Tony
2015-06-27 13:52     ` Daniel Vetter
2015-06-27 14:12       ` Borislav Petkov [this message]
2015-06-27 17:56         ` Daniel Vetter
2015-06-29  8:09           ` Borislav Petkov
2015-06-29  9:25             ` Daniel Vetter
2015-06-29  9:42               ` Borislav Petkov
2015-06-29  9:58                 ` Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2015-06-30  2:53 Rui Wang
2015-06-30  6:36 ` Daniel Vetter
2015-06-30  7:23 Rui Wang
2015-06-30 15:23 ` Daniel Vetter
2015-07-01  7:26 Rui Wang
2015-07-01  9:59 ` Daniel Vetter

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=20150627141237.GE26543@pd.tnic \
    --to=bp@alien8.de \
    --cc=airlied@redhat.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=gong.chen@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.d.roper@intel.com \
    --cc=robdclark@gmail.com \
    --cc=rui.y.wang@intel.com \
    --cc=tony.luck@intel.com \
    /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.