From: Sebastian B. <sb...@bi...> - 2005-04-11 19:43:34
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 mm...@ru... wrote: > So it turns out that /proc/cpuinfo reports a clockspeed of 0 Mhz (CPU MHz > : 0.0000) on my system. This caused PPC to generate some default value which > apparently doesn't work well on my system. Thanks for investigating this! I still wonder what exactly happens here (why does darwin panic?) I'll add a 1000 MHz fallback, this is better than nothing. > > I've temporarily hard-coded a clockspeed value into systimer.cc and recompiled, > and now ppc works great. > > If anyone else has encountered the problem, another temporary workaround > is to run ppc using "nice" (nice -n2 ppc ppc.conf) -- the lower priority > for the process seems to work better with the default value that ppc is > using. > > > Now I just need to find out why cpuinfo is broken. If anyone has an idea, > please let me know. CC'ing pearpc-devel We already know that /proc/cpuinfo is non-optimal solution, especially for processors with frequency scaling (i.e. for energy saving). Unfortunately we haven't found a general solution for this yet. > > Thanks, > Marc > Gruß, Sebastian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBQlrTWP81M8QtvOSJAQLNwAf9GR04rWZHWW7jxu4MPtVKA1q6tGyRPE6G fN24c3dZ701a4OCEouwCI6R0lrKsEX0hgL8+PeEmllRwlwXBd2w0YG3zBWKjWuu2 oIJSAMOS7hDXAz1IksDGsft85SUqZOOsynMFiau/d6p3mpwkuv158QyYded7CcdV e2KvQ9jhfc5Vm3ohm8Lx6y7lK0XXbpkC1gRv464jg8Opj4ykzkgM2MneZmxyG+XD mWZNzNIioTp/7FIhFsRWuOOYZQ3JOnKgDZBcBmxHfPPoarEtPXS0TTmvFlWgy8e0 H3UIE77ggmGCyiY2BPzQWLIbpPJUhqSU6/c6LwvY4I0rXc0sNjbCdw== =QmMs -----END PGP SIGNATURE----- |