On Sun, Jan 06, 2008 at 12:30:34AM +0400, Alexander Shaduri wrote:
> > Get a serial console? Take another box, plug e.g. pl2303-based
> > usb-to-serial (several bucks these days) into it, stick null-modem
> > convertor (ditto) on its serial end and attach to ttyS0 on the
> > victim. console=ttyS0 on victim, something like minicom on watcher
> > and tell it to capture log into file...
>
> I will try that (as soon as I acquire the necessary parts).
netconsole should be more quick:
* one more box with ethernet card
* CONFIG_NETCONSOLE=y
* CONFIG_ {your NIC driver} =y
* on crashing box add the following line to the kernel boot options
[EMAIL PROTECTED]/eth0,[EMAIL PROTECTED]/dst-MAC
where scr-ip -- IP of crashing box
eth0 -- interface on crashing box
9353 -- destination port (for netcat to listen on target box)
dst-ip -- IP of a box which collect logs
dst-MAC -- MAC of the interface on destination box
* on destination box run netcat
nc -u -l -p 9353 &>1.log
[* add ignore_loglevel on crashing box if paranoid]
Now reboot crashing box and reproduce the bug, chances are high that it
will send oops over network.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
