Right, I forgot about that jeff. If you're running syslog-ng, you
can go into /etc/syslog-ng/syslog-ng.conf and add a line:
destination console_all { ("/dev/ttyS01"); };
although, I'm not sure if you're locking up if syslog-ng will keep scrolling. I don't know if netcat (nc) will either...
On 6/21/05, Jeff Moyer <jmoyer@redhat.com> wrote:
==> Regarding Re: [Wlug] HOWTO debug hard lockups; Andy Stewart <andystewart@comcast.net> adds:
andystewart> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
andystewart> Jeff Moyer wrote:
>> ==> Regarding Re: [Wlug] HOWTO debug hard lockups; Andy Stewart
>> <andystewart@comcast.net> adds:
>>
andystewart> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>>
andystewart> Eric Martin wrote:
>>>> In reguards to seeing messages on minicom, what logger do you have
>>>> installed? Can you just shovel kernel messages over to ttyS01? eg
>>>> sudo tailf /var/log/kernel ttyS01
>>
andystewart> I did that per your suggestion and it works just fine.
>> Umm, it works just fine so long as the system is up and running. You
>> really want the kernel to be printing directly to the console.
>> Otherwise, when the system locks up and the NMI fires, you still won't
>> get your messages over the serial console.
>>
>> Andy, it looked to me like you had things configured properly. Indeed,
>> I use a very similar setup all of the time. The only difference is it
>> works for me. (I hate that phrase).
>>
>> I'm not sure what to suggest at this point. If you do an alt-sysrq-h,
>> does that at least print out over the serial console?
>>
>> -Jeff
>>
andystewart> HI Jeff,
andystewart> If I do an alt-sysrq-h, I get the one line help on the serial
andystewart> console. If I do alt-sysrq-m to show memory, I see "SysRq :
andystewart> Show Memory" ont the serial console, but nothing more (unless
andystewart> I use Eric's trick). If I go to runlevel 1, alt-sysrq-m has
andystewart> the entire output on the serial console.
You have all of the luck. How about trying netconsole? It's easy enough
to setup. On the host which will receive the logs, do something like this:
nc -u -l -p 6666
On the problematic system, load the netconsole module:
modprobe netconsole netconsole=@<ip-of-this-machine>/<ethX>,6666@<ip-of-server>/<MAC-address-of-server>
You can try this or not, depending on whether you still experience
crashes. It sounds like the latest kernel fixed things right up for you,
right?
Oh well, good to have in your bag of tricks, I guess.
-Jeff
_______________________________________________
Wlug mailing list
Wlug@mail.wlug.org
http://mail.wlug.org/mailman/listinfo/wlug