On Tue, 2015-07-21 at 19:48 -0500, golinux wrote: > On 2015-07-21 18:28, Ben Hutchings wrote: > > On Tue, 2015-07-21 at 17:07 -0500, golinux wrote: > > > After the last kernel upgrade to 2.6.32-48squeeze13, suspend is > > > failing > > > on my squeeze. It had been working flawlessly since the original > > > install in May of 2011. But since December 2014 I have been having > > > kernel failure issues and even posted about it here. > > > > > > https://lists.debian.org/debian-lts/2014/12/msg00035.html > > > > Sorry I missed that. The problem may lie with the nvidia driver, which > > we have no way to support. > > > > > This message is in both the boot and kernel logs. I suspended. I > > > didn't hibernate. So why is the system trying to find a 'hibernation > > > image'. Any ideas how to fix this? > > > > It's trying to find a hibernation image because that's exactly how it > > finds out whether the system was hibernated. These log messages are > > completely normal on a fresh boot (if you turn the log level high > > enough). > > > > [...] > > > I thought I might try to forcing a kernel version but the only option > > > is > > > to 2.6.32-48squeeze6. > > > > <http://snapshot.debian.org/package/linux-2.6/> has all the old > > versions you care to try. > > > > > I have been pretty flat out with a back injury for over 2 months and > > > don't have much keyboard time. So hoping this can be fixed easily. > > > > I'm afraid I can't see any recent changes that look likely to have > > influenced suspend behaviour. > > > > Ben. > > > > > Thanks for your time and advice . . . > > > > > > golinux > > > > > > > > I appreciate the timely response. Why did you think it might be the > nVidia driver? Maybe compiz is the culprit? I just checked the the > .xsession-errors and nothing is jumping out at me (but what do I know). > There is some polkit-gnome-authentication and python stuff mentioned. > Currently, there are a few pending upgrades including a few for python > so I should probably do that. Just don't want to make things worse. > > I just tried hibernation and it did work, though I had to change > desktops to get the monitor to display/draw completely. Then there was > another kernel failure message. Perhaps there is something new in > there. I see nvidia mentioned along with lots of other stuff. Any more > thoughts? [...] Sorry, I don't think I can help further. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part