Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[SOLVED] Squeeze Kernel Upgrade Broke Suspend to Ram

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
User avatar
Digger1
Posts: 153
Joined: 2011-01-08 21:03
Location: Colorado Springs, CO

[SOLVED] Squeeze Kernel Upgrade Broke Suspend to Ram

#1 Post by Digger1 »

Yesterday, I ran a security update that upgraded my Squeeze kernel from 2.6.32-48squeeze8 to 2.6.32-48squeeze9.

Ever since then, my suspend to ram (STR) function is broken.

The machine will suspend normally, but will not resume. When I try to awaken the machine, I can hear the fan in the tower start up (the subject machine is a desktop computer, please see below for specifics), but the machine seems to be otherwise dead (e.g. the monitor stays blank, pressing the "caps lock" key on my keyboard does not activate said keyboard's "caps lock" led, Ctrl-Alt-F[x] has no effect, etc). My only recourse at that point is a hardware reset (ouch!).

I tried running

Code: Select all

pm-suspend
from a terminal, with no joy. Same result running

Code: Select all

echo -n "mem" > /sys/power/state
from a terminal.

I checked the /var/log/pm-suspend.log file and noticed that each

Code: Select all

...performing suspend
line used to (before said kernel upgrade) be directly followed by a

Code: Select all

...Awake.
line, but, now, all said

Code: Select all

...performing suspend
lines are followed by an

Code: Select all

Initial commandline parameters...
line.

Before this, STR has worked well ever since I first loaded Squeeze on this machine back in 2012.

Any ideas as to where I can go next? Has anyone experienced a similar problem after said kernel upgrade?

TIA!

Here is my rig:

Code: Select all

Squeeze 6.0.10; 2.6.32-5-amd64

Intel i7-980 Gulftown CPU
Asus P6X58D Premium Motherboard
EVGA GeForce GTS-450 Graphics Card
G.SKILL Ripjaw DDR3-1600, PC3-12800, 1.5v RAM (6x4GB sticks, 24GB total)
Crucial RealSSD C300 128GB SSD
Western Digital Caviar Black 1TB HDD
Corsair HX850 PSU
MSI TV@nywhere Plus Analog Video Capture Card
Asus DRW-24B1ST Black STAT 24X DVD/CD Player/Burner, OEM
AFT XM-35U Black Kiosk Card Reader (3.5")
Lian Li PC-9F Case
2006-Vintage HP Internet Keyboard (PS/2)
Acer H203H LCD Wide-Screen monitor
Logitech M-SBF96 PS/2 Mouse
HP Photosmart Premium Fax e-All-In-One C410 Printer
Actiontec Q1000 Modem/Router
1998-Vintage Altec Lansing Speakers
Last edited by Digger1 on 2018-08-14 17:07, edited 2 times in total.
Squeeze on two machines, Wheezy on the other...
http://www.astronautbiker.com

User avatar
dilberts_left_nut
Administrator
Administrator
Posts: 5343
Joined: 2009-10-05 07:54
Location: enzed
Has thanked: 12 times
Been thanked: 66 times

Re: Squeeze Kernel Upgrade Broke Suspend to Ram

#2 Post by dilberts_left_nut »

Running nvidia blob?
Tried rebuilding the kernel module? (dpkg-reconfigure nvidia-kernel-dkms)
AdrianTM wrote:There's no hacker in my grandma...

User avatar
Digger1
Posts: 153
Joined: 2011-01-08 21:03
Location: Colorado Springs, CO

Re: Squeeze Kernel Upgrade Broke Suspend to Ram

#3 Post by Digger1 »

dilberts_left_nut wrote:Running nvidia blob?
Tried rebuilding the kernel module? (dpkg-reconfigure nvidia-kernel-dkms)
dln,

As a matter of fact, I do have nvidia-kernel-dkms loaded.

I will research the procedure you mention and report back...thanks for your insight.

Any other ideas out there?
Squeeze on two machines, Wheezy on the other...
http://www.astronautbiker.com

User avatar
Digger1
Posts: 153
Joined: 2011-01-08 21:03
Location: Colorado Springs, CO

Re: Squeeze Kernel Upgrade Broke Suspend to Ram

#4 Post by Digger1 »

I tried

Code: Select all

dpkg-reconfigure nvidia-kernel-dkms
Got the following feedback:

Code: Select all

-------- Uninstall Beginning --------
Module:  nvidia
Version: 275.36
Kernel:  2.6.32-5-amd64 (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

nvidia.ko:
 - Uninstallation
   - Deleting from: /lib/modules/2.6.32-5-amd64/updates/dkms/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod....

DKMS: uninstall Completed.

------------------------------
Deleting module version: 275.36
completely from the DKMS tree.
------------------------------
Done.
Loading new nvidia-275.36 DKMS files...
Building only for 2.6.32-5-amd64
Building initial module for 2.6.32-5-amd64
Done.

nvidia.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/2.6.32-5-amd64/updates/dkms/

depmod....

DKMS: install Completed.

Unfortunately, the problem persists. I would like to point out that, as stated in the OP, the problem does not seem to me to be nvidia related, since the computer appears to be locked up after being resumed.

Any other ideas out there?
Squeeze on two machines, Wheezy on the other...
http://www.astronautbiker.com

ohZeishi
Posts: 88
Joined: 2014-12-05 19:51

Re: Squeeze Kernel Upgrade Broke Suspend to Ram

#5 Post by ohZeishi »

To make sure that it really was the kernel update that caused the problem, you could try installing the old version again: http://snapshot.debian.org/binary/linux ... 2-5-amd64/

User avatar
Digger1
Posts: 153
Joined: 2011-01-08 21:03
Location: Colorado Springs, CO

Re: Squeeze Kernel Upgrade Broke Suspend to Ram

#6 Post by Digger1 »

ohZeishi wrote:To make sure that it really was the kernel update that caused the problem, you could try installing the old version again: http://snapshot.debian.org/binary/linux ... 2-5-amd64/
oh,

Excellent suggestion! I did just that and then STR started working correctly!

Now the question to all:

Do I stay with the (unsecure) version of the kernel, or do I try and figure out what the problem was with the upgraded kernel?


(For the record, I downgraded all six packages that were associatied with the subject kernel upgrade:

linux-image-2.6.32-5-amd64
firmware-linux-free
linux-headers-2.6.32-5-common
linux-doc-2.6.32
linux-headers-2.6.32-5-amd64
linux-libc-dev

Yeah, I know that not all of these packages needed to be downgraded in order to fix my STR problem, but, since I was in no mood to fiddle-fart around with it, I decided to go ugly early...)
Squeeze on two machines, Wheezy on the other...
http://www.astronautbiker.com

ohZeishi
Posts: 88
Joined: 2014-12-05 19:51

Re: Squeeze Kernel Upgrade Broke Suspend to Ram

#7 Post by ohZeishi »

Hard to say. The changelog http://metadata.ftp-master.debian.org/c ... _changelog is quite long and contains AFAICT nothing that screams "I break suspend to ram". So it could be hard to find the exact cause.
You could look if there is anything in there that's relevant for your system, especially the fixed CVEs.

User avatar
Digger1
Posts: 153
Joined: 2011-01-08 21:03
Location: Colorado Springs, CO

Re: Squeeze Kernel Upgrade Broke Suspend to Ram

#8 Post by Digger1 »

ohZeishi wrote:Hard to say. The changelog http://metadata.ftp-master.debian.org/c ... _changelog is quite long and contains AFAICT nothing that screams "I break suspend to ram". So it could be hard to find the exact cause.
You could look if there is anything in there that's relevant for your system, especially the fixed CVEs.
Thanks for the link!

Well, nothing jumps out at me, either, but, to tell you the truth, it's all about 100% gobbledy-gook to this old fighther pilot....

I guess I'll just sit tight until the next kernel upgrade comes along and hope for better luck. Either that or switch to Wheezy!
Squeeze on two machines, Wheezy on the other...
http://www.astronautbiker.com

User avatar
Digger1
Posts: 153
Joined: 2011-01-08 21:03
Location: Colorado Springs, CO

UPDATE - Today's Squeeze Kernel Upgrade

#9 Post by Digger1 »

I had high hopes that today's kernel upgrade would fix my problem.

But, alas, those hopes were dashed upon the ragged, rocky coast of despair.....

Back to the downgrade I mentioned above.
Squeeze on two machines, Wheezy on the other...
http://www.astronautbiker.com

User avatar
Issyer
Posts: 3032
Joined: 2007-05-23 02:59
Location: Khakassia

Re: Squeeze Kernel Upgrade Broke Suspend to Ram

#10 Post by Issyer »

Usually suspend wakes up when video driver is wrong. The issue is not related to kernel at all. Maybe, your nvidia was not compiled properly? Try a different driver. Such problem happens even on windows. http://en.community.dell.com/support-fo ... t/19538482

User avatar
Digger1
Posts: 153
Joined: 2011-01-08 21:03
Location: Colorado Springs, CO

Re: Squeeze Kernel Upgrade Broke Suspend to Ram

#11 Post by Digger1 »

Issyer wrote:Usually suspend wakes up when video driver is wrong. The issue is not related to kernel at all. Maybe, your nvidia was not compiled properly? Try a different driver. Such problem happens even on windows. http://en.community.dell.com/support-fo ... t/19538482
Iss,

Thanks for your input. However, the posts I've made above seem to indicate that my problem is kernel-related, not nvidia-related.
Squeeze on two machines, Wheezy on the other...
http://www.astronautbiker.com

User avatar
Issyer
Posts: 3032
Joined: 2007-05-23 02:59
Location: Khakassia

Re: Squeeze Kernel Upgrade Broke Suspend to Ram

#12 Post by Issyer »

OK. Kernel-related if that satisfies your issue.

User avatar
Digger1
Posts: 153
Joined: 2011-01-08 21:03
Location: Colorado Springs, CO

Re: Squeeze Kernel Upgrade Broke Suspend to Ram

#13 Post by Digger1 »

Now, Issyer has me doubting myself in my belief that I have a kernel issue, not a nvidia issue...

In brief, here is what has happened (see the above posts for a more detailed version of events):

1. Here is my system:

Code: Select all

Squeeze 6.0.10; 2.6.32-5-amd64

Intel i7-980 Gulftown CPU
Asus P6X58D Premium Motherboard
EVGA GeForce GTS-450 Graphics Card
G.SKILL Ripjaw DDR3-1600, PC3-12800, 1.5v RAM (6x4GB sticks, 24GB total)
Crucial RealSSD C300 128GB SSD
Western Digital Caviar Black 1TB HDD
Corsair HX850 PSU
MSI TV@nywhere Plus Analog Video Capture Card
Asus DRW-24B1ST Black STAT 24X DVD/CD Player/Burner, OEM
AFT XM-35U Black Kiosk Card Reader (3.5")
Lian Li PC-9F Case
2006-Vintage HP Internet Keyboard (PS/2)
Acer H203H LCD Wide-Screen monitor
Logitech M-SBF96 PS/2 Mouse
HP Photosmart Premium Fax e-All-In-One C410 Printer
Actiontec Q1000 Modem/Router
1998-Vintage Altec Lansing Speakers
2. Squeeze has been running happily on this machine since January 2012.

3. On December 10, 2014, I ran a security update that upgraded my Squeeze kernel from 2.6.32-48squeeze8 to 2.6.32-48squeeze9.

4. In short order, I noticed that the suspend to ram (STR) function was broken. The machine would suspend normally, but would not resume. When I tried to awaken the machine, I could hear the fan in the tower start up, but the machine seemed to be otherwise dead (e.g. the monitor stayed blank, pressing the "caps lock" key on my keyboard did not activate said keyboard's "caps lock" LED, Ctrl-Alt-F[x] had no effect, etc). My only recourse at that point was a hardware reset (ouch!).

5. Thinking that the nvidia blob I'm running could be the problem, I rebuilt the associated kernel module:

Code: Select all

dpkg-reconfigure nvidia-kernel-dkms
No joy.

6. I then downgraded all of the six packages associated with the suspect kernel upgrade. After this, STR started working again.


Based on the evidence, my limited experience with such matters leads me to believe that my STR problem is caused by the kernel upgrade, not my nvidia blob. Am I missing anything here?

TIA!
Squeeze on two machines, Wheezy on the other...
http://www.astronautbiker.com

User avatar
Issyer
Posts: 3032
Joined: 2007-05-23 02:59
Location: Khakassia

Re: Squeeze Kernel Upgrade Broke Suspend to Ram

#14 Post by Issyer »

"Kernel" is a vast concept. It includes also modules like for nvidia that are built natively, you know. Since you didn't try vesa or nouveau, it doesn't explain anything. I had a similar issue with ati. As soon I changed driver to radeon everything worked fine. Of course, they are not proprietary but how can you know that it was not nvidia corporation who failed to catch up with the latest kernel upgrade? Remember, if the glass is half full, it is also half empty.

User avatar
Digger1
Posts: 153
Joined: 2011-01-08 21:03
Location: Colorado Springs, CO

Re: Squeeze Kernel Upgrade Broke Suspend to Ram

#15 Post by Digger1 »

I looked into the possibility of nvidia-related packages being the cause of my STR problem.

First, let me say that I've been using nvidia packages that were from the official Debian Squeeze Backports repo.

1. Since these backported packages had upgrades available (again, from the official Debian Squeeze Backports repo), I upgraded them:

Code: Select all

nvidia-vdpau-driver:amd64 (280.13.really.275.36-1~bpo60+1, 295.59-1~bpo60+2)
nvidia-kernel-dkms:amd64 (280.13.really.275.36-1~bpo60+1, 295.59-1~bpo60+2)
xserver-xorg-video-nvidia:amd64 (280.13.really.275.36-1~bpo60+1, 295.59-1~bpo60+2)
libgl1-nvidia-glx:amd64 (280.13.really.275.36-1~bpo60+1, 295.59-1~bpo60+2)
libgl1-nvidia-alternatives:amd64 (280.13.really.275.36-1~bpo60+1, 295.59-1~bpo60+2)
nvidia-alternative:amd64 (280.13.really.275.36-1~bpo60+1, 295.59-1~bpo60+2)
nvidia-glx:amd64 (280.13.really.275.36-1~bpo60+1, 295.59-1~bpo60+2)
nvidia-settings:amd64 (290.10-1~bpo60+1, 295.49-1~bpo60+1)
libglx-nvidia-alternatives:amd64 (280.13.really.275.36-1~bpo60+1, 295.59-1~bpo60+2)
Aptitude also "threw in" the following package as a result of the above upgrades

Code: Select all

libxnvctrl0:amd64 (295.49-1~bpo60+1, automatic)
2. I again upgraded my six previously downgraded 2.6.32-48squeeze8 kernel-related packages to their latest 2.6.32-48squeeze10 versions.

A fresh reboot, and...STR was still broken.

3. Inspired by my earlier backported package upgrades, I upgraded few other packages that I had earlier loaded from the official Debian Squeeze Backport repo:

Code: Select all

gnucash:amd64 (2.4.10-2~bpo60+1, 2.4.10-2~bpo60+2)
gnucash-common:amd64 (2.4.10-2~bpo60+1, 2.4.10-2~bpo60+2)
firmware-linux:amd64 (0.32~bpo60+1, 0.36+wheezy.1~bpo60+1)
linux-base:amd64 (3.3~bpo60+1, 3.4~bpo60+1)
firmware-linux-nonfree:amd64 (0.32~bpo60+1, 0.36+wheezy.1~bpo60+1)
libswscale2:amd64 (0.8-2~bpo60+1, 0.8.6-1~bpo60+1)
libavutil51:amd64 (0.8-2~bpo60+1, 0.8.6-1~bpo60+1)
libnss3:amd64 (3.13.4-3~bpo60+1, 3.14.5-1~bpo60+1)
libbluray1:amd64 (0.0~git20110717.3477b65-3~bpo60+1, 0.2.2-1~bpo60+2)
libavfilter2:amd64 (0.8-2~bpo60+1, 0.8.6-1~bpo60+1)
libavdevice53:amd64 (0.8-2~bpo60+1, 0.8.6-1~bpo60+1)
libbluray-bdj:amd64 (0.0~git20110717.3477b65-3~bpo60+1, 0.2.2-1~bpo60+2)
libavcodec53:amd64 (0.8-2~bpo60+1, 0.8.6-1~bpo60+1)
libpostproc52:amd64 (0.8-2~bpo60+1, 0.8.6-1~bpo60+1)
libavformat53:amd64 (0.8-2~bpo60+1, 0.8.6-1~bpo60+1)
libnss3-1d:amd64 (3.13.4-3~bpo60+1, 3.14.5-1~bpo60+1)
libsqlite3-0:amd64 (3.7.12.1-1~bpo60+1, 3.7.13-1~bpo60+1)
5. I then ran another

Code: Select all

dpkg-reconfigure nvidia-kernel-dkms
Another reboot, and...STR was still broken!

4. I again downgraded the six kernel-related packages and STR works again...

I'm fairly convinced that my video driver has nothing to do with the STR problem.

Comments, anyone?
Squeeze on two machines, Wheezy on the other...
http://www.astronautbiker.com

User avatar
Digger1
Posts: 153
Joined: 2011-01-08 21:03
Location: Colorado Springs, CO

Re: Squeeze Kernel Upgrade Broke Suspend to Ram

#16 Post by Digger1 »

As Squeeze users know, an upgrade for the 2.6.32 kernel became avaliable today, the 2.6.32-48squeeze11 version.

I half-heartedly performed the upgrade, rebooted, then tried an STR.

No go.

I then downgraded the six abovementioned packages back to their 2.6.32-48squeeze8 versions and, not surprisingly, STR started working again.

Sigh...
Squeeze on two machines, Wheezy on the other...
http://www.astronautbiker.com

pendrachken
Posts: 1394
Joined: 2007-03-04 21:10
Location: U.S.A. - WI.

Re: Squeeze Kernel Upgrade Broke Suspend to Ram

#17 Post by pendrachken »

Have you tried kernel 3.2.x from squeeze-backports? According to a package search you should be able to try out 3.2.0-0bpo for x86 / AMD_64.
fortune -o
Your love life will be... interesting.
:twisted: How did it know?

The U.S. uses the metric system too, we have tenths, hundredths and thousandths of inches :-P

User avatar
Digger1
Posts: 153
Joined: 2011-01-08 21:03
Location: Colorado Springs, CO

Re: Squeeze Kernel Upgrade Broke Suspend to Ram

#18 Post by Digger1 »

pendrachken wrote:Have you tried kernel 3.2.x from squeeze-backports? According to a package search you should be able to try out 3.2.0-0bpo for x86 / AMD_64.
pen,

Thanks for that suggestion. I tried loading that kernel, but then my Xwindows was broken.

I suppose I could have dug into it, but I just didn't feel like dicking with it right now....

So, I undid all of the installs, upgrades, and package removals that said kernel upgrade induced.
Squeeze on two machines, Wheezy on the other...
http://www.astronautbiker.com

User avatar
Digger1
Posts: 153
Joined: 2011-01-08 21:03
Location: Colorado Springs, CO

Re: Squeeze Kernel Upgrade Broke Suspend to Ram

#19 Post by Digger1 »

I tried version 13 of the 2.6.32 kernel.

Same STR problem.

Downgraded back to version 8.
Squeeze on two machines, Wheezy on the other...
http://www.astronautbiker.com

User avatar
Digger1
Posts: 153
Joined: 2011-01-08 21:03
Location: Colorado Springs, CO

Re: Squeeze Kernel Upgrade Broke Suspend to Ram

#20 Post by Digger1 »

To finally suitcase this issue (sort of):

As long as I was using Squeeze (the final kernel update left me at version 20), the problem never resolved itself. I just (lazily) lived with it until upgrading to Wheezy a month ago (I know, I'm still far behind...maybe I'll get Jessie loaded onto the subject machine by the end of 2019...maybe...).

In any event, the upgrade fixed my STR problem! Notably, I was able to use the Nouveau video driver for my nVidia card, as Wheezy's version of Nouveau could handle said card.

After giving the issue some thought, I think that members dilberts_left_nut and Issayer were on the right track. I think that the problem was related to the nVidia blob that I had loaded under Squeeze.

All is well!
Squeeze on two machines, Wheezy on the other...
http://www.astronautbiker.com

Post Reply