Hi,

Azndrew Morton:
> What is 2.6.17-test-1.29?

My test build; standard kernel during bisection.

> How do you know that 5d0cf410e94b1f1ff852c3f210d22cc6c5a27ffa caused this?
> 
git bisect.

> Are you able to test the below?  It should fix up the reporting.
> 
Applied.

> Are you able to compare the present bootlog with the 2.6.17 bootlog?
> 
Sure. The diff says:

 checking TSC synchronization across 4 CPUs:
+CPU#0 had 748437 usecs TSC skew, fixed it up.
+CPU#1 had 748437 usecs TSC skew, fixed it up.
+CPU#2 had -748437 usecs TSC skew, fixed it up.
+CPU#3 had -748437 usecs TSC skew, fixed it up.
 Brought up 4 CPUs
-migration_cost=4000,8000
+migration_cost=85,1724

... but apparently, that skew is not corrected.

These numbers do match the difference in observed "date" outputs.

-- 
Matthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@smurf.noris.de
Disclaimer: The quote was selected randomly. Really. | http://smurf.noris.de
 - -
The first place you look for something
is the last place you'd expect to find it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/