On Sun 2015-01-04 15:03:02, Nicolas Pitre wrote: > On Sun, 4 Jan 2015, Pavel Machek wrote: > > > 9fc2105aeaaf56b0cf75296a84702d0f9e64437b breaks audio in python, and > > probably elsewhere, with message > > > > FATAL: cannot locate cpu MHz in /proc/cpuinfo > > > > I'm not the first one to hit it, see for example > > > > https://theredblacktree.wordpress.com/2014/08/10/fatal-cannot-locate-cpu-mhz-in-proccpuinfo/ > > https://devtalk.nvidia.com/default/topic/765800/workaround-for-fatal-cannot-locate-cpu-mhz-in-proc-cpuinf/?offset=1 > > > > Reading original changelog, I have to say "Stop breaking working > > setups. You know who you are!". > > > > Signed-off-by: Pavel Machek <pa...@ucw.cz> > > NAK. > > No setups actually relying on this completely fony bogomips value > bearing no links to hardware reality coule have been qualified as > "working".
You broke python-pyaudio in Debian 7.7, which is pretty new version... I'm not saying something relies on the _exact_ value there, but the change is bad. > The bogomips entry was removed from /proc/cpuinfo in 2013. We're now in > 2015. You're apparently the first to suggest moving the kernel back to > providing random values via /proc/cpuinfo. So this removal must not > have inconvenienced that many people in the end. Take a look at links above. One broken system would be enough... people noticed but did not complain on lkml. > Broken applications appear to have been fixed already as mentioned via > those links you provided above. So if you want a working setup, you may > stick with a kernel of the same vintage as your user space apps or > update the later. That is not how kernel development should work. See https://lkml.org/lkml/2012/12/23/75 > If that is still unacceptable to you for whatever reason, then the least > wrong compromize should be: > > seq_printf(m, "BogoMIPS\t: 1.00\n"); > > That'D allow for those broken applications to run while making clear > that the provided value is phony. I was about to suggest 0.00 but that > could trigger a divide by zero error somewhere I suppose. I don't know what 1.00 will cause, and neither do you, so what about simply reverting the bad patch? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
