public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Valdis.Kletnieks@vt.edu
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
	Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Frank Ch. Eigler" <fche@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Christoph Hellwig <hch@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Jon Masters <jcm@redhat.com>
Subject: Re: [PATCH] Linux Kernel Markers Support for Proprierary Modules
Date: Fri, 25 Jan 2008 16:32:40 +0000	[thread overview]
Message-ID: <20080125163240.7d68cb24@core> (raw)
In-Reply-To: <15663.1201248183@turing-police.cc.vt.edu>

On Fri, 25 Jan 2008 03:03:03 -0500
Valdis.Kletnieks@vt.edu wrote:

> On Fri, 25 Jan 2008 08:56:09 +0100, Jan Engelhardt said:
> > So what is needed is an Oops with an explaining message
> > if (kernel_tainted) "blame that proprietary module first",
> > and make sure the user sees that oops even if in X.
> 
> The person who solves the "even if in X" problem will probably be nominated
> for sainthood by the Linux community.  "It just hung with flashing LED's" is
> just too common an event....

I've been poking at it a bit but it will need X server help, or
eventually the kernel mode switch code.

Alan

  reply	other threads:[~2008-01-25 15:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22 19:13 CONFIG_MARKERS Jon Masters
2008-01-23  3:00 ` CONFIG_MARKERS Frank Ch. Eigler
2008-01-23  3:10   ` CONFIG_MARKERS Mathieu Desnoyers
2008-01-23  4:17     ` CONFIG_MARKERS Jon Masters
2008-01-23 13:14       ` CONFIG_MARKERS Frank Ch. Eigler
2008-01-23 14:48         ` CONFIG_MARKERS Mathieu Desnoyers
2008-01-23 15:01           ` CONFIG_MARKERS Mathieu Desnoyers
2008-01-23 16:33             ` CONFIG_MARKERS Jon Masters
2008-01-23 17:11               ` CONFIG_MARKERS Mathieu Desnoyers
2008-01-24  5:25           ` CONFIG_MARKERS Valdis.Kletnieks
2008-01-24  6:19             ` CONFIG_MARKERS Jon Masters
2008-01-24 12:47               ` [PATCH] Linux Kernel Markers Support for Proprierary Modules Mathieu Desnoyers
2008-01-24 18:27                 ` Valdis.Kletnieks
2008-01-24 20:35                 ` Jon Masters
2008-01-25  1:27                 ` Rusty Russell
2008-01-25  7:56                 ` Jan Engelhardt
2008-01-25  8:03                   ` Valdis.Kletnieks
2008-01-25 16:32                     ` Alan Cox [this message]
2008-01-25 15:31                   ` Jon Masters
2008-01-25 16:01                     ` Jan Engelhardt
2008-01-26  3:27                     ` Rusty Russell
2008-01-26  4:21                       ` Jon Masters
2008-01-27 10:48                         ` Jan Engelhardt
  -- strict thread matches above, loose matches on Subject: below --
2008-02-02 19:51 Mathieu Desnoyers

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=20080125163240.7d68cb24@core \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=fche@redhat.com \
    --cc=hch@infradead.org \
    --cc=jcm@redhat.com \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=rusty@rustcorp.com.au \
    --cc=torvalds@linux-foundation.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