Messages in this thread | | | Subject | Hoo-fscking-ray - (was Re: 2.6.25-rc3-mm1 - BUG at system shutdown time | From | Valdis.Kletnieks@vt ... | Date | Fri, 21 Mar 2008 23:11:18 -0400 |
| |
On Fri, 21 Mar 2008 21:12:11 BST, Ingo Molnar said: > > * Valdis.Kletnieks@vt.edu <Valdis.Kletnieks@vt.edu> wrote: > > > On Fri, 21 Mar 2008 20:58:13 BST, Ingo Molnar said: > > > > > no, we frequently regenerate the x86.git tree so the dates have little > > > relevance. If for any particular pull, x86/base is good and x86/latest > > > is bad, then the bug is somewhere in those 200-300 patches inbetween. > > > They are lined up linearly so should be perfectly bisectable. > > > > OK, off to go try the last few bisects then... > > well ... your git bisection log does look suspiciously 'good', so > something is wrong thee i think :-( > > the chance to get 8 'good' bisection points in a row is 1:256. OTOH, the > freshest x86 patches are always at the 'end' of the queue - which are > also the ones most likely to break anything.
On the other hand, this was broken in 25-rc3-mm1, so it's not a "fresh" patch...
> Are you sure the x86/base point is indeed 'good'? You can check it via: > > git-checkout -b tmp x86/base > > and build+boot it.
Did that, and it's good (as in 'shutdown -h now' powers off rather than BUG and hanging).
"You're at Witt's End" -- Adventure, c. 1978
OK.. so far I've got:
25-rc3-mm1 is bad 25-rc5-mm1 is bad, and bisected down to git-x86.patch x86/base as pulled last week is good bisected to within the last 9 entries of x86/latest is good.
So I can't seem to replicate it using the git-x86 tree, but bisecting -mm implicates it. How very strange.
I even went and pulled Andrew's mmotm pile as of this afternoon, and got that to built after having to heave only a dozen patches over the side and one or two hand-fixes of patches - and *that* one is good too.
So I'm thinking that it was some "bump in the night" that was broken in the x86 tree when Andrew pulled it for 25-rc5-mm1, but was fixed by the time I pulled it a few days later to start git-bisecting it.
Given that -mmotm isn't showing the problem, I'm having a hard time coming up with enthusiasm to keep chasing it. If I see it happen again in a -mm or Linus kernel, I'll restart the chase then....
[unhandled content-type:application/pgp-signature] | |