Question about xserve G5

[Javi Hotmail]

I also have a PowerMac G5 (Dual Core 2.3 Ghz) and it really works like a
charm. But the heatsink in literally four times the size of the Xserve.
And to be honest I don't know what they were thinking when Apple was
designing the airflow of the case, because is less than optimal in many
ways.

I know that is an overheating issue because the FreeBSD kernel start
spitting a message saying (CPU Diode is 134C, and maximum temperature
allowed is 90C).

After that the blowers got to maximum speed for few second. Sometime it
can actually regulate the temperature and it won't shut down. But if it
continues to print the same message for 5 seconds the kernel will
initiate shutdown automatically.

I really want to get cpufreq + powerd working because if this happens
you can also underclock the cpu to balance out the heat issue. But it
really seems to me that the implementation for G5 in cpufreq is a mess.
So I guess that I'll need to jump into that.

I've never used the kernel debugger (DDB) on a powerpc (my idea is to
use it via serial port). If anybody has any tips in this regard I'm all
ears.

Javi.

On 30/10/2020 13:47, Jason Bacon wrote:
>
> I don't have any overheating problems on my PowerMac G5, which I think
> is pretty similar except for the form factor.  Are you sure it's
> overheating that's causing the shutdown?
>
> The wild fan issue in my case oddly seems to be mitigated by having a
> monitor and keyboard connected during boot.  If I boot headless, the
> fans ramp up almost every time.  With monitor and keyboard, it almost
> never happens.
>
> On 10/29/20 2:15 PM, Javi Hotmail wrote:
>> Also another issue that (despite the fact that I cleaned the CPUs and
>> added new thermal paste) they overheat and the system turns off.
>>
>> With kern.smp.disabled=1 takes a bit longer, but it also shuts down. Is
>> this also a known issue?
>>
>>
>> Kind Regards,
>>
>> Javi.
>>
>>
>> On 29/10/2020 18:07, Javi Hotmail wrote:
>>> Here it is.
>>>
>>>
>>> Javi.
>>>
>>>
>>> On 29/10/2020 14:14, Nathan Whitehorn wrote:
>>>> Could you provide your dmesg? It would be nice to do what sensors you
>>>> have.
>>>> -Nathan
>>>>
>>>> On 10/29/20 8:36 AM, Javi Hotmail wrote:
>>>>> If I'm not mistake the issue then is how the PPC implementation reads
>>>>> the device tree data from open firmware correct?.
>>>>>
>>>>> I believe this implementation is within:
>>>>>
>>>>> pcr.c        pmcr.c        pmufreq.c
>>>>>
>>>>>
>>>>> Thanks in advance,
>>>>>
>>>>> Javi.
>>>>>
>>>>>
>>>>> On 29/10/2020 12:26, Michael Tuexen wrote:
>>>>>>> On 29. Oct 2020, at 10:51, Javi Hotmail <volkovdablo at hotmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hello all,
>>>>>>>
>>>>>>> I'm new in this mailing list, although I've been going back and
>>>>>>> forth
>>>>>>> with PPC (G4/G5) and FreeBSD since 9.0.
>>>>>>>
>>>>>>> I have a question that perhaps some of you already stumbled across,
>>>>>>> but
>>>>>>> I wanted to know if there is a way to get it to work before I
>>>>>>> jump in
>>>>>>> the code.
>>>>>>>
>>>>>>> I have a xserve G5 dual 2.3Ghz, and I installed FreeBSD 12.1. Works
>>>>>>> quite well, but I cannot get cpufreq + powerd/powerdxx to work
>>>>>>> at all.
>>>>>>>
>>>>>>> I get this:
>>>>>>>
>>>>>>> # powerdxx
>>>>>>> powerd++: (ENOFREQ) cannot access dev.cpu.0.freq, at least the
>>>>>>> first CPU
>>>>>>> core must support frequency updates
>>>>>>>
>>>>>>>
>>>>>>> This is the relevant part of sysctl:
>>>>>>> # sysctl dev.cpu
>>>>>>> dev.cpu.1.%parent: cpulist0
>>>>>>> dev.cpu.1.%pnpinfo: name=PowerPC,G5
>>>>>>> dev.cpu.1.%location:
>>>>>>> dev.cpu.1.%driver: cpu
>>>>>>> dev.cpu.1.%desc: Open Firmware CPU
>>>>>>> dev.cpu.0.%parent: cpulist0
>>>>>>> dev.cpu.0.%pnpinfo: name=PowerPC,G5
>>>>>>> dev.cpu.0.%location:
>>>>>>> dev.cpu.0.%driver: cpu
>>>>>>> dev.cpu.0.%desc: Open Firmware CPU
>>>>>>> dev.cpu.%parent:
>>>>>>>
>>>>>>> The issue is that after few minutes the fans ramp up to insane
>>>>>>> levels,
>>>>>>> and my goal with this is to use powerd or powerdxx to manage the
>>>>>>> situation.
>>>>>> The fans ramping up is a known issue. One way to work around it
>>>>>> is to
>>>>>> disable SMP.
>>>>>>
>>>>>> To disable SMP, put in /boot/loader.conf
>>>>>> kern.smp.disabled=1
>>>>>>
>>>>>> Best regards
>>>>>> Michael
>>>>>>> Thanks in advance,
>>>>>>>
>>>>>>> Javi.
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> freebsd-ppc at freebsd.org mailing list
>>>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-ppc
>>>>>>> To unsubscribe, send any mail to
>>>>>>> "freebsd-ppc-unsubscribe at freebsd.org"
>>>>> _______________________________________________
>>>>> freebsd-ppc at freebsd.org mailing list
>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-ppc
>>>>> To unsubscribe, send any mail to
>>>>> "freebsd-ppc-unsubscribe at freebsd.org"
>>>>>
>>>> _______________________________________________
>>>> freebsd-ppc at freebsd.org mailing list
>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-ppc
>>>> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe at freebsd.org"
>> _______________________________________________
>> freebsd-ppc at freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-ppc
>> To unsubscribe, send any mail to "freebsd-ppc-unsubscribe at freebsd.org"
>
>