Re: More DSI traps

[Frank Wille <frank%phoenix.owl.de@localhost>]

Martin Husemann wrote:

> I updated my NetBSD/prep RS6000 machine to -current and tried the
> pthread tests.

Today's current? Is the userland from the same date as the kernel?


> There are lots of failures, probably most of them with a
> common course, related to the DSI traps already discussed here.
> [...]
> Does this work on any other ppc cpu? 

Here are the results from my Synology NAS, running a current kernel and
userland from the 22nd of March:

syrinx# uname -mprs
NetBSD 5.99.48 sandpoint powerpc
syrinx# dmesg | grep cpu
cpu0 at mainbus0: 8245 (Revision 0.4), ID 0 (primary)
cpu0: HID0 0x90c000<DOZE,DPM,ICE,DCE>, powersave: 1
syrinx# ./t_fork fork
passed
syrinx# ./t_kill simple
passed

It also works fine on a Pegasos2/ofppc, using kernel and userland from the
same date, with a G3 CPU:

cpu0 at mainbus0: 750 (Revision 3.1), ID 0 (primary)
cpu0: HID0 0x8050c0ac<EMCP,NAP,DPM,ICE,DCE,SGE,BTIC,ABE,BHT>, powersave: 1
cpu0: 600.00 MHz, 512KB WB with ECC L2 cache
cpu0: L1 I-cache 32 KB 32B/line, D-cache 32 KB 32B/line
cpu0: L2 cache 128 KB 32B/line


> Since PR 44387 explicitly talks
> about t_mutex, which runs later, I suppose it works on G4 or newer.
> Interestingly I have so far been unable to reproduce the t_mutex
> failure on this cpu.

I didn't try the G3, but I can reproduce the bug on my Sandpoint NAS:

syrinx# ./t_mutex mutex2
1: Mutex-test 2
expected_timeout: PR port-powerpc/44387
1: Thread 0xffe00000
2: Second thread (0xefa00000). Count is 10000000
(here it hangs forever)

-- 
Frank Wille