I'm not the person Linus was addressing, but I've had plenty of
oopses with 2.2.1 - 2.2.10 and have not sent any in.
So far as I know there are only two ways to capture the data related to
an oops. Write it down with a pencil, or capture it via a serial port
on another machine. The first seems too prone to errors, and the second
just isn't realistic for me and my cluster of machines. Too many
serial cables going every which way. Or maybe I'm just lazy.
I have a setup which oopses in 5 minutes to a few days when compiled
with SMP support. The identical source compiled without SMP runs
forever as far as I can tell.
Since all things have previously be discussed on this list, I'm going
to let my linux "newbieism" show by asking for a feature which has
undoubtably been asked for before and has undoubtable been shot
down for very legitimate reasons.
I would like my oops'ing systems to send the oops to another system via
an ethernet interface. How about a UDP packet? Nice connectionless
protocol. Compile the MAC/IP address into the kernel. Opps occurs,
build the UDP packet with the measly 2K oops message in it and send.
-- Brian Litzinger <brian@litzinger.com>- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/