Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753710AbbF3DMJ (ORCPT ); Mon, 29 Jun 2015 23:12:09 -0400 Received: from mga03.intel.com ([134.134.136.65]:11413 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752787AbbF3DMB (ORCPT ); Mon, 29 Jun 2015 23:12:01 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,374,1432623600"; d="scan'208";a="752940045" From: Rui Wang 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 Subject: Re: drm/mgag200: doesn't work in panic context Date: Tue, 30 Jun 2015 10:53:57 +0800 Message-Id: <1435632837-32056-1-git-send-email-rui.y.wang@intel.com> X-Mailer: git-send-email 1.7.5.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 856 Lines: 18 On Monday, June 29, 2015 5:25 PM, Daniel Vetter 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 -- 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/