From: Matt Mackall <mpm@selenic.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Frank van Maarseveen <frankvm@frankvm.com>,
"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: Mon, 10 Jan 2005 12:43:06 -0800 [thread overview]
Message-ID: <20050110204306.GE2995@waste.org> (raw)
In-Reply-To: <1105278075.12028.29.camel@localhost.localdomain>
On Sun, Jan 09, 2005 at 11:00:48PM +0000, Alan Cox wrote:
> 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.
Netconsole can sends oopses over UDP right now in mainline (since
2.6.3 or so?). And my kgdb over ethernet bits have been in -mm for
quite some time as well.
(Though testing of -tiny is still appreciated of course.)
--
Mathematics is the supreme nostalgia of our time.
next prev parent reply other threads:[~2005-01-10 20:45 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
2005-01-10 20:43 ` Matt Mackall [this message]
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=20050110204306.GE2995@waste.org \
--to=mpm@selenic.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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).