Arthur Machlas put forth on 7/30/2010 9:04 AM:
>> BTW, I'm curious as to your motivations for this. Is this basically a
>> "Windows can do 800MHz, so $deity dammit, Linux should be able to do it as
>> well!" thing?
> Not as such. More like a my processor is supposed to scale from 800Mhz
> to 1.6Ghz, and its strange that it doesn't. I wonder why.
That's what I figured. I had a similar mindset when I was a younger man. Let
me share a relevant story:
Back in 1997 I bought a beautiful used Midnight Blue 1993 Ford Probe GT with
the hopped up 24 valve quad cam V6 and a 5 speed manual transmission. It was
Motor Trend Magazine's 1993 Car Of The Year. The tested top speed was 137
miles per hour. I was dead set on achieving that published top speed. I
didn't have a racetrack available for my testing. Over the course of about 3
weeks I would find open stretches of Interstate 370 with little to no traffic.
On 5 occasions I was able to hit 135 mph, but no more. I was determined to
hit the magical 137 that Motor Trend said it would do. On the six occasion on
a cool afternoon I had just hit 136 mph when I rocketed past a hidden Missouri
Highway Patrolman manning a radar gun. As soon as I saw the cherries in my
rear view mirror I slowed down and pulled over. Evading wasn't an option even
with that kind of speed and lead: you can't outrun a radio or a helicopter.
Due to traveling at almost double the posted speed limit I spent a mandatory
night in jail. The attorney cost me $450 and the ticket for doing 76 mph
_over_ the posted speed limit was $548, for a grand total of $998. The
attorney got the reckless driving charge dropped and massaged the speeding
charge so I only took a 2 point hit on my license instead of 5. A reckless
driving conviction along with the additional points would have put me into
what the insurance industry calls the "high risk" category, which would have
quadrupled my insurance premiums. That would have driven my monthly insurance
payment to just under $500/month, which was more than my split of rent at the
The moral of the story: Even if "they" say it will do it, and others have
achieved it, it's not always wise, nor cost effective, to maniacally chase the
> I suppose that will have to count as advice on how to proceed, but I
> hope you'll forgive me if I continue to search for an answer. Your
> comments are reassuring to me though, that it isn't a serious problem,
> and I do thank you for that.
There's nothing to forgive. It's your time and effort going into this. I'm
simply trying to save you large amounts of both as I've "been there and done
> At this point, I'm thinking it's a problem with the kernel or a
> problem with my bios, and I think there are some kernel command line
> parameters I can use to test the latter in Greg's book.
And before filing a kernel bug, it would be very wise to ask the questions you
have here on lkml before you submit a bug. Debian-users isn't really the
proper venue for discussing your problem. This is a user list, not a
developer list. There are very few, if any, kernel hackers on this list with
the knowledge/answers you are seeking. And no I'm not one of them. Having
more than cursory experience rolling my own kernels is a far cry from being a
kernel hacker. I'm not a C programmer.
My advice: expend your energy on aspects of Debian/Linux that will yield
practical, tangible benefits. This isn't one of them.
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org