Re: spin_lock using kernel-smp-2.4.20-3.4

On Sun, Jun 08, 2003 at 09:20:18AM +0200, Christian Joensson wrote:
> I have been using Aurora for quite some time now, a single
> SuperSparc-(II) firewall SS20 (sun4m), a dual SuperSparc-(II) test
> compile machine for linux-sparc gcc (which I'd rather have running my
> quad Ross HyperSparc) and an single CPU UltraSparc I test compile
> machine for linux64-sparc gcc. They all the run kernel-2.4.20-3.4sparc
> kernel, in their respective flavour...
> 
> The dual sun4m system hangs quite often (say once a day), and it's a
> spin_lock all the time...
> 
> Today, it looked like this:
> 
> spin_lock(f3d1e73c) CPU#0 stuck at f0086f44, owner PC(fbe8c400:PC(0)
> spin_lock(f3d1e73c) CPU#1 stuck at f002cbbc, owner PC(fbe8c400:PC(0)
> 

and today it looks like this:

spin_lock(fae8c73c) CPU#0 stuck at f002cbbc, owner PC(00000000):CPU(0)
spin_lock(fae8c73c) CPU#0 stuck at f002cbbc, owner PC(00000000):CPU(0)

What can I do to track this?

Cheers,

/ChJ