Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
On Fri, Feb 20, 2009 at 12:29:32PM +0100, Peter Luciak wrote: > I've managed to hook up a serial console and capture the output on > another computer, but I don't get any stack trace. > Linux version 2.6.26.8 (root at vwsrv2.met.gov.om) (gcc version 4.0.2 > 20051125 (Red Hat 4.0.2-8)) #2 SMP Thu Feb 19 11:57:53 GST 2009 > Command line: ro root=/dev/md0 console=ttyS0,115200 console=tty0 > > The machine is then self-rebooted via iTCO-wdt watchdog. > > I have done a "echo 8 > /proc/sys/kernel/printk" and also enabled the > "early printk" in kernel config, but still no usable output. In > /etc/syslog.conf I have > kern.* /dev/ttyS0 don't do that. if it is a hard crash, syslog won't have any time to print anything anymore. let the kernel itself log to the ttyS0. try to swap > Command line: ro root=/dev/md0 console=ttyS0,115200 console=tty0 to > Command line: ro root=/dev/md0 console=tty0 console=ttyS0,115200 i.e. mention ttyS0 last on the kernel command line. that used to help. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. __ please don't Cc me, but send to list -- I'm subscribed