Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 11 May 2019 18:28:05 -0700
From:      Mark Millard <marklmi@yahoo.com>
To:        Andreas Tobler <andreast-list@fgznet.ch>
Cc:        FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>
Subject:   Re: 970/PowerMac G5 cpudep_ap_bootstrap slb-related hangup *solved* . . .
Message-ID:  <620D56E6-ACCC-4592-9E11-7B48FD2061C6@yahoo.com>
In-Reply-To: <73ec1772-adeb-a501-a8ff-91b22cfbb1ff@fgznet.ch>
References:  <2E7A0894-E5B0-4776-95F2-76B7EE0EE93C@yahoo.com> <C3272E01-41D8-4E4C-8F4B-CF9DC6E37B3D@yahoo.com> <73ec1772-adeb-a501-a8ff-91b22cfbb1ff@fgznet.ch>

next in thread | previous in thread | raw e-mail | index | archive | help


On 2019-May-11, at 14:26, Andreas Tobler <andreast-list at fgznet.ch> =
wrote:

> On 10.05.19 12:23, Mark Millard via freebsd-ppc wrote:
>=20
>> Of course, whitespace details, may not be well preserved
>> below. (The commenting out of the two #if/#endif lines
>> was unnecessary and is not done in the below.)
>> # svnlite diff /mnt/usr/src/sys/ | more
>> Index: /mnt/usr/src/sys/powerpc/aim/mp_cpudep.c
>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>> --- /mnt/usr/src/sys/powerpc/aim/mp_cpudep.c    (revision 347003)
>> +++ /mnt/usr/src/sys/powerpc/aim/mp_cpudep.c    (working copy)
>> @@ -68,6 +68,46 @@
>>         case IBM970:
>>         case IBM970FX:
>>         case IBM970MP:
>> +               /* Set HIOR to 0 */
>> +               __asm __volatile("mtspr 311,%0" :: "r"(0));
>> +               powerpc_sync();
>=20
> Thank you for this incredible investigation! My quad is now under =
heavy load and behaves as expected.


You are welcome.


One long-term issue is still definitely active,
happening sometimes:

The thread(s) stuck-in-sleep problem can still happen.

This is worse than just the fans and the buf*deamon*
thread timeouts during shutdown: those same threads
were not doing there on-going jobs earlier, starting
when they first got stuck. The fans and shutdown
messages (and wait time) just make it rather obvious.

The command:

top -HIStazopid

will frequently show the threads in question when
they are not stuck. But it will also not show the
ones that are already stuck-sleeping.


=3D=3D=3D
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?620D56E6-ACCC-4592-9E11-7B48FD2061C6>