On Fri, Jan 21, 2011 at 4:23 PM, Linus Torvalds
<torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
>
> Or - and perhaps more likely - it's connected to the lid event, and
> how that interacts with user space and then eventually triggers the
> sleep event (which is quite likely - as mentioned, I think I've only
> ever seen the problem when I'm physically at the machine).
.. but with the 'test' suspend (echo core ..), the lid event is all
good too. And going back to non-testing (echo none ..), it works too.
Which really does seem to get me back to the whole "if it fails, it
seems to fail on the first suspend" thing. Don't ask me why. I have no
idea. But I just suspended that machine 100+ times using the test
thing (60 times at the gdm prompt, 60 times while logged in and with
glxgears running to verify dri/thermal interfaces), and then a couple
of times with the lid, and it all worked.
But I bet that if I rebooted the machine a few times, it would
eventually fail on the first suspend.
Some initialization issue, perhaps?
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
