On Wednesday 09 June 2010, Alan Jenkins wrote:
> Rafael J. Wysocki wrote:
> > On Tuesday 08 June 2010, Alan Jenkins wrote:
> >
> >> I found this bug 2.6.34 on my Asus EeePC 701 (x86_32 arch). It didn't
> >> happen to me before, when I was running nearly-2.6.33 or 2.6.32-release.
> >>
> >> I us
Rafael J. Wysocki wrote:
On Tuesday 08 June 2010, Alan Jenkins wrote:
I found this bug 2.6.34 on my Asus EeePC 701 (x86_32 arch). It didn't
happen to me before, when I was running nearly-2.6.33 or 2.6.32-release.
I used git-bisect, but unfortunately the result isn't very helpful. My
next
On Tuesday 08 June 2010, Alan Jenkins wrote:
> I found this bug 2.6.34 on my Asus EeePC 701 (x86_32 arch). It didn't
> happen to me before, when I was running nearly-2.6.33 or 2.6.32-release.
>
> I used git-bisect, but unfortunately the result isn't very helpful. My
> next step will be to try
Alan Jenkins wrote:
I found this bug 2.6.34 on my Asus EeePC 701 (x86_32 arch). It didn't
happen to me before, when I was running nearly-2.6.33 or 2.6.32-release.
I used git-bisect, but unfortunately the result isn't very helpful.
My next step will be to try to narrowing down the culprits by
I found this bug 2.6.34 on my Asus EeePC 701 (x86_32 arch). It didn't
happen to me before, when I was running nearly-2.6.33 or 2.6.32-release.
I used git-bisect, but unfortunately the result isn't very helpful. My
next step will be to try to narrowing down the culprits by disabling
individua
