linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Frank van Maarseveen <frankvm@frankvm.com>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
	Anton Blanchard <anton@samba.org>, Andrew Morton <akpm@osdl.org>,
	Linas Vepstas <linas@austin.ibm.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	torvalds@osdl.org
Subject: Re: [PATCH] kernel/printk.c  lockless access
Date: Sun, 09 Jan 2005 23:00:48 +0000	[thread overview]
Message-ID: <1105278075.12028.29.camel@localhost.localdomain> (raw)
In-Reply-To: <20050109104425.GA9524@janus>

On Sul, 2005-01-09 at 10:44, Frank van Maarseveen wrote:
> What about UDP (or just eth) broadcasting the oops and catching it
> on another system? That would be useful if one has a lot of systems
> (I have about 40) and makes it possible to immediately alert someone
> without the need for ping games.

netdump and kgdb both can do this. The 2.6.10-tiny1 has some nice kgdb
patches that include using the polling network debug interfaces.


  parent reply	other threads:[~2005-01-10  0:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06 19:58 [PATCH] kernel/printk.c lockless access Linas Vepstas
2005-01-06 20:50 ` Andi Kleen
2005-01-07  0:12 ` Andrew Morton
2005-01-07  0:26   ` Anton Blanchard
2005-01-07  0:25     ` Randy.Dunlap
2005-01-07  1:54       ` Alan Cox
2005-01-09 10:44         ` Frank van Maarseveen
2005-01-09 22:31           ` David Wagner
2005-01-09 23:00           ` Alan Cox [this message]
2005-01-10 20:43             ` Matt Mackall
2005-01-08  2:37 ` Keith Owens

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=1105278075.12028.29.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=frankvm@frankvm.com \
    --cc=linas@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    --cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).