The suspend monster is back! The suspend-to-ram is fine, but upon
resume, screen is blank. Haven't bisected in case someone has also
done so.
It's very recent. ... between commit
831d52bc153971b70e64eccfbed2b232394f22f8 and
44f2c5c841da1b1e0864d768197ab1497b5c2cc1.
Thanks,
Jeff
On Saturday, February 05, 2011, Jeff Chua wrote:
> The suspend monster is back! The suspend-to-ram is fine, but upon
> resume, screen is blank. Haven't bisected in case someone has also
> done so.
>
> It's very recent. ... between commit
> 831d52bc153971b70e64eccfbed2b232394f22f8 and
> 44f2c5c841da1b1e0864d768197ab1497b5c2cc1.
No idea. I bet on DRI.
Thanks,
Rafael
On Saturday, February 05, 2011, Jeff Chua wrote:
> The suspend monster is back! The suspend-to-ram is fine, but upon
> resume, screen is blank. Haven't bisected in case someone has also
> done so.
>
> It's very recent. ... between commit
> 831d52bc153971b70e64eccfbed2b232394f22f8 and
> 44f2c5c841da1b1e0864d768197ab1497b5c2cc1.
BTW, please don't reply to messages containing patches with reports of problems
that aren't caused by those patches. It's confusing at best and at worst it
may result in the patches being rejected.
Thanks,
Rafael
On Sat, Feb 5, 2011 at 7:31 AM, Jeff Chua <[email protected]> wrote:
>
> The suspend monster is back! The suspend-to-ram is fine, but upon
> resume, screen is blank. Haven't bisected in case someone has also
> done so.
>
> It's very recent. ... between commit
> 831d52bc153971b70e64eccfbed2b232394f22f8 and
> 44f2c5c841da1b1e0864d768197ab1497b5c2cc1.
Hmm. It's almost certainly one of the DRI patches, but which one? I
think bisection is the only way to figure it out. It shouldn't be too
bad, since there's only 120 commits in that range.
In fact, you can almost certainly just bisect from 89840966c579 to
bb5b583b5279, which is just 31 commits and should get you bisected in
just five tries or so.
Linus