powerpc/180593: PowerMac G5 shuts down when building pcre

[Julio Merino]

>Number:         180593
>Category:       powerpc
>Synopsis:       PowerMac G5 shuts down when building pcre
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-ppc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jul 16 11:40:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator:     Julio Merino
>Release:        FreeBSD 10.0-CURRENT powerpc
>Organization:
>Environment:
System: FreeBSD mastodon.meroh.net 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r253339M: Sun Jul 14 19:07:28 EDT 2013 jmmv at mastodon.meroh.net:/usr/obj/usr/src/sys/GENERIC64 powerpc


	
>Description:
	I have a PowerMac G5 (dual PPC 970FX 2Ghz, 6GB of RAM) on which
	I'm running FreeBSD 10.0-CURRENT (but the same happened with
	9.1-RELEASE).  The machine is pretty much rock-solid in all
	cases: I have been able to build a variety of ports, and I can
	even do a buildworld -j3 without issues.

	Whenever I try to build pcre, the machine shuts down with this
	message:

	WARNING: Current temperature (U3 HEATSINK: 82.5 C) exceeds
	critical temperature (80.0 C)! Shutting down!

	The file that always causes this is libpcre16_la-pcre16_exec.lo.
	Pausing the compiler with Ctrl+Z every 1-3 seconds and then
	resuming it after 5 allows the compilation of this file to
	succeed without shutting the machine down.

	nwhitehorn@ mentioned that this could be a problematic fan, but
	I haven't been able to find it in the machine.

	Because the machine has been stable otherwise, I don't think
	this is a hardware issue and it seems to me that this is just a
	problem with the fcu driver and the way it manages this
	particular fan.

	See this thread
	http://lists.freebsd.org/pipermail/freebsd-ppc/2013-March/006207.html
	for the original discussion.
>How-To-Repeat:
	Get FreeBSD running on a PowerMac G5, build pcre, and see it
	the machine shutdown (assuming this is not a hardware problem).
>Fix:
	Unknown, but this particular problem can be worked around as
	described above.
>Release-Note:
>Audit-Trail:
>Unformatted: