[lkml]   [2008]   [Mar]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.25-rc3-mm1 - BUG at system shutdown time
On Wed, 12 Mar 2008 00:32:27 PDT, Andrew Morton said:
> On Thu, 06 Mar 2008 22:58:45 -0500 wrote:
> > On Tue, 04 Mar 2008 01:19:28 PST, Andrew Morton said:
> > >
> >
> > Dell Latitude D820, x86_64, Core2 Duo T7200
> >
> > 'shutdown -h' blows up at the very end. shutdown -r works OK.
> Did rc5-mm1 fix this?

Nope, still blows up with exactly the same traceback.

I may have to try again to figure out how to bisect the git-x86 tree - Ingo
send me a pointer to his git-x86 cheat sheet, I looked at it but I couldn't
figure out how to tell 'git bisect' that the starting good spot was "whatever
corresponded to the git-x86 patch in 24-rc8-mm1" and bad was "25-rc3-mm1". I
tried using the first commit ID listed in the patch, but that gave me this:

(looking at first few lines of the git-x86.patch in the 25-rc3-mm1 broken-out):

commit fa70e201463a7f3d86b995249e57a8e27b31b5f8
Author: Paolo Ciarrocchi <>
Date: Sun Feb 24 11:57:22 2008 +0100

but then:

% git bisect bad fa70e201463a7f3d86b995249e57a8e27b31b5f8
fatal: Needed a single revision
Bad rev input: fa70e201463a7f3d86b995249e57a8e27b31b5f8

And I didn't see any release tags in the x86 git tree that I could specify

(Once I get the good and bad markers set, it "should be easy" - I've managed
to git-bisect through Linus's git tree before, but that was always easy
because "bad" was HEAD and "good" had a nice v2.6.2mumble-rcN tag to specify...

[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2008-03-13 03:23    [W:0.330 / U:0.104 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site