On Thu, 4 Aug 2005 22:05, Gabriel Devenyi wrote:
> Con Kolivas wrote:
> > I have to think about it. This seems a problem only on one type of cpu
> > for some strange reason (lemme guess; athlon?) and indeed leaving out the
> > sleep 1 followed by the check made results far less reliable. This way
> > with the sleep 1 I have not had spurious results returned by the
> > calibration. I'm open to suggestions if anyone's got one.
>
> Yeah, thats right, it spins forever on both my athlon-tbird and my
> athlon64 (in x86_64 mode). I'll take another look at the code tonight,
> to see if I can figure out why its causing this, or another way of
> incurring the delay you're looking for.
I'd appreciate it. It's almost like some power stepping that's responsible.
I've never seen it happen on any intel processor (including the pentiumM ones
which have truckloads of power saving features). I've asked many people if
they're running some equivalent of cool'n'quiet or powernow* and they all
insist they're not... I'm not that familiar with all the powersaving techs
though.
Cheers,
Con
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |