On Sun, 12 Aug 2007, Andrew Morton wrote:
> On Sun, 12 Aug 2007 20:15:51 +0300 (EEST) "Ilpo Järvinen" <[email protected]> wrote:
>
> > Hmm, it was really worth of it, I did:
> > $ git-fetch linus
> > $ git-reset --hard linus
> > [...make & install & boot...]
> >
> > ...and voila, the problem went away, so something else seems to have
> > fixed it between: ac07860264bd and 963c6527e0a0e. As you can notice,
> > I didn't even have to revert it (I was just double checking current
> > mainline first).
> >
> > Is there a need to get a more detailed view about the cause or something,
> > or are details of this issue clear enough to everyone? I can do some more
> > research if necessary, though expect a bit longer latencies during the
> > next week...
> >
> > In case none, thanks everyone, this issue seems solved. :-)
>
> We just had an acpi commit. Something like ed3110efb538d7acbf635095c1382118f7414f75
> might have fixed this.
...Yeah, it's very likely the same issue as bisect in that case seemed to
end up to the very same commit I found, and it was answered with that
fix...
--
i.
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]