This is becoming irritating. Clearly bisect isn't capable of
figuring out the bad commit for me, so I'm going to have to walk the commits
myself. *sigh* (The commit it thinks is the one that's causing the problem
for me yet again is very obviously barking up the wrong tree)
git bisect star
I just wanted to give a heads up so you knew where I'm at and that I
haven't forgotten to do the bisection. Well, I'm doing the bisection - and
it's having me chase wild geese. This bug is apparently not always occuring
when it's possible for it to, confusing the issue.
Currently I
On 2013-02-08 Friday at 01:11 + Ben Hutchings wrote:
> On Thu, 2013-02-07 at 12:36 -0500, tmhik...@gmail.com wrote:
> > Hmm. I'm not sure what's going on here but ever since I upgraded to
> > this kernel my CPU use has always been at 100% - various apps (top, pidstat,
> > conky) give differ
On Thu, 2013-02-07 at 12:36 -0500, tmhik...@gmail.com wrote:
> Hmm. I'm not sure what's going on here but ever since I upgraded to
> this kernel my CPU use has always been at 100% - various apps (top, pidstat,
> conky) give different reasons for this, conky&pidstat claims things like
> X/the
Hmm. I'm not sure what's going on here but ever since I upgraded to
this kernel my CPU use has always been at 100% - various apps (top, pidstat,
conky) give different reasons for this, conky&pidstat claims things like
X/the most active X application are cpu hogging, while top seems to think
5 matches
Mail list logo
