Re: Using %stick where available

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

On Nov 7, 2012, at 4:26 AM, Erik Fair wrote:

> OK, a *slight* tempering of my enthusiasm; a test on a Sun Netra T1  
> model 200, i.e.
>
> mainbus0 (root): SUNW,UltraAX-i2 (Netra T1 200): hostid XXXXXXXX
> cpu0 at mainbus0: SUNW,UltraSPARC-IIe @ 500 MHz, UPA id 0
> cpu0: 16K instruction (32 b/l), 16K data (32 b/l), 256K external (64  
> b/l)
>
> yielded:
>
> trap type 0x10: cpu 0, pc=1009f54 npc=10c9fb4  
> pstate=0x44820016<PEF,PRIV,IE>
> kernel trap 10: illegal instruction
>
> ... and that halted the boot sequence. So we're going to have to be  
> careful about precisely which CPUs support the instruction in  
> question. Any bets on the UltraSPARC IIe that one finds in the Sun  
> Fire v120 (550/650 MHz, as opposed to the 500 MHz version in the  
> Netra T1 model 200)?


... and this is why I posted the patch here instead of committing  
right away.
UltraSPARC-IIe is supposed to support the system tick timer if I  
remember correctly, and the patch is supposed to touch the relevant  
registers /only/ if there's a 'stick-frequency' property on the root  
node. If it tried to mess with them anyway that's a bug. Any idea  
where exactly the trap came from? Which function would be enough to  
pin it down.
( just gdb your-kernel; disassemble 0x1009f54 )

have fun
Michael

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEVAwUBUJpPmspnzkX8Yg2nAQKlBQgAnpN5bExkTzaAtilaiURT3Hpi0F37Hh+G
OUoxgpOFhIs8YlSgJFuiqzWXbfLbu1D/KNTKW883t2wDIEyvRv0dhrmIFAKuGR79
fOYVX5QtCvHaifbr5RN0OMACj9s4GFYP5aXZeCrt5LCq8i6/TR4/PwEGYmccIu3K
7etjz+lKDzoP3oYxZvrreV/LkAr8QE6ms25/bZNJScwFqwCO1OJF8OzIra9eyrJM
VSpUQUGKcBswifcGRu6f1CrxXR/O3MN7PXtW6a7OM2fsS8ywk+Sys3GHwv1y/L+a
Q0W9V6JEa7IIxQR0en6zEUTaDPasH6EgeZbOGZFHIZBnipctPT97HA==
=pDi8
-----END PGP SIGNATURE-----