mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rui Wang <rui.y.wang@intel.com>
To: daniel.vetter@ffwll.ch
Cc: bp@alien8.de, tony.luck@intel.com, airlied@redhat.com,
	robdclark@gmail.com, matthew.d.roper@intel.com,
	gong.chen@intel.com, linux-kernel@vger.kernel.org,
	Rui Wang <rui.y.wang@intel.com>
Subject: Re: drm/mgag200: doesn't work in panic context
Date: Tue, 30 Jun 2015 10:53:57 +0800	[thread overview]
Message-ID: <1435632837-32056-1-git-send-email-rui.y.wang@intel.com> (raw)

On Monday, June 29, 2015 5:25 PM, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> As long as the display is up and running we should have a fair stab at
> showing the oops - it's just that no one has seriously bothered with
> the necessary infastructure, automated testing (it won't work
> otherwise) and driver work.

I think testing can be done by injecting a fatal machine check exception
via einj's debugfs interface. I can reproduce the hard hang every time.
I think It can be a simple script or C program do to the automated testing.
If anyone has any patch I'll be happy to help test it out.

Thanks
Rui

             reply	other threads:[~2015-06-30  3:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30  2:53 Rui Wang [this message]
2015-06-30  6:36 ` Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2015-07-01  7:26 Rui Wang
2015-07-01  9:59 ` Daniel Vetter
2015-06-30  7:23 Rui Wang
2015-06-30 15:23 ` Daniel Vetter
2015-06-26  7:55 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
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

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=1435632837-32056-1-git-send-email-rui.y.wang@intel.com \
    --to=rui.y.wang@intel.com \
    --cc=airlied@redhat.com \
    --cc=bp@alien8.de \
    --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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®