You're right, the change is upstream. I've not checked in since I made my own. Consider a cvs fix may be more appropriate now.
Bertrand. 2011/6/7 Gilles Espinasse <[email protected]> > Selon LANOUX Bertrand <[email protected]>: > > > Hi all, > > > > I have noticed the "unknown HZ value" message still appears at boot time > and > > under some unpredictable circumstances when running the ps command, even > > after applying the procps-3.2.8-fix_HZ_errors-1.patch (I currently use a > SMP, > > 2.6.38.4 tickless kernel). > > So after looking inside the procps code and patch, I deduced the > > linux_version_code variable was not correctly valued. After starting to > make > > my own patch, I came across a similar issue when looking over the net > (seen > > on > > > > http://www.linuxquestions.org/questions/slackware-14/slackware-13-37-rc-unknown-hz-value-after-procps-upgrade-871679/ > ). > > It seems the constructor functions don't run as the package expect on > recent > > libgcc. > > > > After applying it, the message definitively disappeared. The patch is > > attached (another solution is to prioritize the constructor functions). > > > > It works well since quite a while for me now, so may it be taken into > account > > for those who have encountered the same inconvenience. Have a look ? > > > > Thanks for reading, > > > > Bertrand. > > > the upstream code does not use the changes in > > http://www.linuxfromscratch.org/patches/lfs/development/procps-3.2.8-fix_HZ_errors-1.patch > only the __attribute__((constructor)) fix > http://procps.cvs.sourceforge.net/viewvc/procps/procps/proc/ > > I was mostly ready to report too, had a diff made from cvs upstream but > this > disk crashed 2 days ago. > > > Gilles > -- > http://linuxfromscratch.org/mailman/listinfo/lfs-dev > FAQ: http://www.linuxfromscratch.org/faq/ > Unsubscribe: See the above information page >
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
