Re: HPET regression in 2.6.26 versus 2.6.25 -- why Yinghai's revertmay have failed

[Bill Fink]

Hi David,

On Thu, 14 Aug 2008, David Witbrodt wrote:

> > > I used 'git apply --check ' first, and got no errors, so
> > > I applied it, built, installed, and rebooted.
> > 
> > that patch revert to use request_resource, so there is some other problem
> > 
> > YH
> 
> I finished experimenting last night with trying to find the last commit
> in the gittree that would let me revert the problem successfully...
> and I got completely raped.
> 
> The bisecting took me all the way back to the first commit introducing
> the problem on these motherboards:  3def3d6d...
> 
> Considering these 3 consecutive commits (according to 'git log')from late
> Feb. 2008, between kernel versions 2.6.25 and 2.6.26-rc1:
> ---------------------------------------------------------
> 
> 700efc1b...:  the last kernel I can build and run just fine.
> 
> 3def3d6d...:  this one builds, but locks up in inet_init() once the sequence
> of function calls reaches synchronize_rcu().  Reverting here works, but is
> trivial and silly, just reproducing 700efc1b...
> 
> 1e934dda...:  attempting to revert the changes from 3def3d6d... (just one
> commit before!) already fails.
> ---------------------------------------------------------
> 
> This last commit has an effect on my machine that prevents attempts to
> revert 3def3d6d... from working as intended.  This may explain why
> Yinghai's patch providing the revert for 2.6.27-rc3 did not work.
> (Hopefully none of the other changes between Feb. and Aug. would also keep
> the revert from working, but I wouldn't bet my life on it....)
> 
> The 3d... and 1e... commits are quite small, touching only 4 files total,
> and both commits involve calls to insert_resource().  Something on my 2
> problem machines is behaving badly in this area.

I wonder if it would help to revert both the 3def3d6d... and 1e934dda...
commits.  If there are 2 (or more) problematic commits, then of course
it wouldn't help to revert just one of the two commits.  This is one of
the nastiest type of debugging scenario, when there is more than one
cause of the observed problem, although in such case the multiple
causes are often related in some way.

						-Bill
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/