Re: scheduler bug: process running since 5124095h

[Mike Galbraith]

On Mon, 2010-03-29 at 12:54 +0200, Peter Zijlstra wrote:
> On Mon, 2010-03-29 at 12:52 +0200, Mike Galbraith wrote:
> > > I have a simple way to reproduce this:
> > > 1. Boot the system, run top, confirm everything is normal
> > > 2. Run latencytop, and quit (I used version 0.5)
> > > 3. Run top, see 5124095h in the TIME column
> > 
> > Indeed, and I don't even have CONFIG_LATENCYTOP set.  It bisected
> > to...
> > 
> > 761b1d26df542fd5eb348837351e4d2f3bc7bffe is the first bad commit
> > commit 761b1d26df542fd5eb348837351e4d2f3bc7bffe
> > Author: Hidetoshi Seto <seto.hidetoshi@xxxxxxxxxxxxxx>
> > Date:   Thu Nov 12 13:33:45 2009 +0900
> 
> 
> Oh lovely, and reverting that cures the issue?

Haven't done so yet, will do later this afternoon.

	-Mike

--
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/