Messages in this thread | | | From | "Rafael J. Wysocki" <> | Subject | Re: 2.6.36-rc3 suspend issue (was: 2.6.35-rc4 / X201 issues) | Date | Thu, 9 Sep 2010 00:27:38 +0200 |
| |
On Wednesday, September 08, 2010, Nico Schottelius wrote: > Rafael J. Wysocki [Wed, Sep 08, 2010 at 01:28:52AM +0200]: > > On Wednesday, September 08, 2010, Nico Schottelius wrote: > > > Rafael J. Wysocki [Tue, Sep 07, 2010 at 11:48:41PM +0200]: > > > > On Tuesday, September 07, 2010, Jeff Chua wrote: > > > > > > > > > > Cool. Thanks for the short-cut! At least now, I can resume, but got a > > > > > lot of BUGS showing up upon resume after applying the patch. > > > > > > > > This also was reported IIRC, but there's no resolution so far. It's a > > > > different issue. > > > > > > Can somebody ping me, as soon as a git pull on linux-2.6 > > > should be as "stable" (or more stable) than 2.6.34? > > > > No one can say when that happens for your machine. > > True. I was more wondering, when the bisected issue will > be fixed, as this may give my machine some more chances > to work on Linux. > > Btw, do you also recognize a different pattern on LKML? > > In the past it was mostly "$device not support" && wait > for third party patch to go into upstream, whereas today > it "should be supported", but crashes/freezes sometimes.
Unfortunately, suspend to RAM is easy to break, so that happens in every merge window and if nobody reports the problem timely, it just slips through.
Thanks, Rafael
| |