Camaleón noela...@gmail.com writes:
Well, no kernel oops is good but if you can reproduce this kernel bug
every time you trigger the hibernation from GNOME when resuming the
system, at least you can open a bug for this in Debian BTS. You are
clearly having some sort of problem with the
Hi Jeffrin,
Thanks for the advice.
I think some module which help in the suspend/resume
process has failed to complete initialization.
EDAC(Error Correction And Detection) module might
have found error in a device or may be the module
needs a patch.
You can do dmesg | grep edac and see
On Fri, 25 Feb 2011 10:56:26 -0800, Richard Lawrence wrote:
Thanks, Camaleón, for these suggestions.
Make a quick and easy test: create a new user and try to
hibernate/resume from there and see how it goes.
Ok, here's where I'm at:
1) A new user (pmtest) can indeed hibernate and resume
On Thu, 24 Feb 2011 20:56:10 -0800, Richard Lawrence wrote:
I upgraded from Lenny to Squeeze this past weekend. Since then, I
haven't been able to successfully resume after a suspend to disk, which
had been working fine in Lenny (with Linux 2.6.26). Basically, on boot,
I see a blinking
Thanks, Camaleón, for these suggestions.
Make a quick and easy test: create a new user and try to hibernate/resume
from there and see how it goes.
Ok, here's where I'm at:
1) A new user (pmtest) can indeed hibernate and resume from the console
without issue
2) My regular user account (rwl)
On Thu, Feb 24, 2011 at 08:56:10PM -0800, Richard Lawrence wrote:
But I'm uncertain where to look for more information (I can't find
anything more informative anywhere in /var/log), or how to go about
determining whether this is a configuration issue I can fix or a bug
that I should file.
Hi all,
I upgraded from Lenny to Squeeze this past weekend. Since then, I
haven't been able to successfully resume after a suspend to disk, which
had been working fine in Lenny (with Linux 2.6.26). Basically, on boot,
I see a blinking cursor, followed by a completely blank (unresponsive --
no
7 matches
Mail list logo