Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752379AbbF2IJh (ORCPT <rfc822;w@1wt.eu>);
	Mon, 29 Jun 2015 04:09:37 -0400
Received: from mail.skyhub.de ([78.46.96.112]:38530 "EHLO mail.skyhub.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1751376AbbF2IJd (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Mon, 29 Jun 2015 04:09:33 -0400
Date: Mon, 29 Jun 2015 10:09:14 +0200
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
Message-ID: <20150629080914.GB12383@pd.tnic>
References: <1435305314-14337-1-git-send-email-rui.y.wang@intel.com>
 <CAKMK7uF5pbWsVOqLhh4Gp4rCt1=-0zXrJSChCcV0YCJCk1VnZA@mail.gmail.com>
 <3908561D78D1C84285E8C5FCA982C28F32AA062A@ORSMSX114.amr.corp.intel.com>
 <CAKMK7uH_p3Dkt0xtSPaZwWuJvHFUVSahquzfuwR313qOOknfng@mail.gmail.com>
 <20150627141237.GE26543@pd.tnic>
 <CAKMK7uF3rvUh9hEr8zC9vV8HL4aHRk-6+Gif7GEW-C5cFWQDuQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAKMK7uF3rvUh9hEr8zC9vV8HL4aHRk-6+Gif7GEW-C5cFWQDuQ@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1884
Lines: 52

On Sat, Jun 27, 2015 at 07:56:19PM +0200, Daniel Vetter wrote:

<snip very useful explanation for !GPU people>

> Which could all happen very much after the kernel made it's dying
> sigh. Display hw has long stopped being this simple and display
> drivers also.

Thanks for the explanation. I was fearing that it would go in such
direction though. :\ Oh well.

So there are two observations to be ventured here:

* there's still no robust and simple way to save/show oops messages on
laptops. When a laptop crashes and the user has only this one machine,
catching the oops can be a serious PITA. Laptop most likely doesn't have
serial, modeset is hard to do, as you explained, and saving it into
persistent storage (UEFI) might brick it in some cases or whatever the
firmware will do to it. I guess we can keep wishing here for something
better.

* The server aspect might not really need GPU modesetting IMHO because
realistically, servers have serial so the oops can go out there. Which
begs the other question:

Shouldn't drm_fb_helper_panic() and that path below it simply be
removed?

I mean, if it needs to do all that hw-reconf on the panic path and if
that reconfiguration is not completely reliable, maybe we shouldn't do
it all?

This way, we will basically remain as quiet as possible in order not
to muddle the system unreasonably when we're about to die and the only
thing we want to catch is an oops or maybe kexec the crash kernel...

Oops will go out on serial anyway and server will kexec - GPU/fb stuff
doesn't do anything. Yes, no?

Hmmm.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/