Hi, Jason Heeris wrote (Sun March 4, 2012): > The most watertight way I know of to capture kernel > output is a serial port and another computer. If, by any chance, you > have one on your machine
Not really an option (at least, not an easy one), I'm afraid. I only have two machines, and neither of them have serial ports. Rendered obsolete, indeed. Sven Joachim wrote (Sun March 4, 2012): > Either log in via ssh if that is still possible, The computer has gone well beyond the point of responding to anything coming in over the network by the time it has frozen. > or use netconsole to capture kernel messages. Thanks for the links. This looked promising, but I cannot get it to function. I can get the problem machine connected to a netbook successfully (I can talk between them over UDP using netcat). However, netconsole refuses to transmit any messages. I install the module just as the article you linked to suggests, and it appears to be correct when I see it logged in dmesg: [103337.293616] netconsole: local port 6665 [103337.293626] netconsole: local IP 0.0.0.0 [103337.293632] netconsole: interface 'eth0' [103337.293637] netconsole: remote port 6666 [103337.293642] netconsole: remote IP 192.168.0.1 [103337.293646] netconsole: remote ethernet address ff:ff:ff:ff:ff:ff [103337.293654] netconsole: local IP 192.168.0.2 [103337.293754] console [netcon0] enabled [103337.293762] netconsole: network logging started But this doesn't seem to work - there's just nothing transmitted. I can't even get it to send messages to a netcat listener on the same machine. Have you (or anyone) found this approach works? Is there something I'm missing? Thanks for your help so far. Peace, Brendon -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201203041717.11587.blhigg...@gmail.com
