Re: spin_lock: kernel-2.4.20-3.1sparcsmp on dual SS20

Maybe if you learn forth.  Otherwise I'd recommend doing what Ingo says. 
  I had to do something similar once.  From a host watching the console 
of interest I just ran cat < /dev/ttyS1 >> /var/tmp/consolewatch.log . 
You could even put that in /etc/inittab to make sure it's always running.

-charles

Christian Joensson wrote:
> On Wed, Apr 30, 2003 at 03:50:26PM +0200, Ingo T. Storm wrote:
> 
>>>btw, I have to write these spin_lock information manually from the
>>>screen onto paper, then reboot and from the hand written paper info,
>>
>>I
>>
>>>make a file with the spin_lock info and then feed that through
>>>ksymoops...
>>>
>>>Isn't there a smart way? logging? OBP?
>>
>>Use serial console and a terminal program with logging. Even
>>Hyperterminal can do that ;-)
>>
> 
> 
> 
> well, it took me three days of heavy compilation and then it
> happened...
> 
> is there any way to, e.g., from OBP define logging of these kind of
> messages, kernel oops, CPU spin_lock, to some file, remote or local to
> the machine?
> 
> Cheers,
> 
> /ChJ
> 
> _______________________________________________
> aurora-sparc-devel mailing list
> [email protected]
> http://lists.linuxpower.org/mailman/listinfo/aurora-sparc-devel