Kernel 2.6.24-17 - broken resume from suspend to RAM

Bug #226279 reported by APavlov
260
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
Hardy
Fix Released
High
Tim Gardner
Intrepid
Invalid
Undecided
Unassigned

Bug Description

Hi,

After a recent Hardy kernel upgrade from to 2.6.24-16 to 2.6.24-17 my machine stopped coming back from suspended-to-ram state. The HDD spins up but nothing else happens - neither the screen comes back from power-save, nor the keyboard changes its LED states in response to keypresses. I managed to get this diagnostic piece from dmesg using the resume-trace procedure (see the entire dmesg log attached):

[ 27.735308] registered taskstats version 1
[ 27.735393] Magic number: 0:968:373
[ 27.735395] hash matches /build/buildd/linux-2.6.24/drivers/base/power/main.c:112

Revision history for this message
APavlov (pavlov81) wrote :
Revision history for this message
APavlov (pavlov81) wrote :
Revision history for this message
APavlov (pavlov81) wrote :
Revision history for this message
APavlov (pavlov81) wrote :
Revision history for this message
Joss Winn (josswinn) wrote :

I think I'm getting this, too. Since the kernel upgrade, resume from suspend results in a blank screen. Restarting X doesn't work. I have to power off.

Running on Lenovo 3000 N100.

Revision history for this message
APavlov (pavlov81) wrote :

After some more investigation it appeared that the machine resumes but it takes ABSURDLY long time (anywhere from 90sec to 8 minutes). There are some ACPI errors in dmesg - see the attachment for a dmesg log after a single STR-Resume.

Revision history for this message
Ryan Bair (dr.bair) wrote :

Same here. I've even tried dropping the nvidia driver so I can say I've tried it with a non-tainted kernel.

Revision history for this message
APavlov (pavlov81) wrote :

I have tried disabling nvidia driver, too, as well as unloading some acpi-related modules and removing cpufrequtils - to no avail. It just hangs for ages in the same code fragment (see dmesg.resumed, the "resume" part)

Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → High
status: New → Triaged
Revision history for this message
Matthias Jordan (matthiasjordan) wrote :

I guess I can confim this for my last-gen iBook G4. Also with linux-2.6.24-17 (Hardy).

I put the machine to sleep which works just fine. After that I wake it up and the screen turns on again. The text on it is a log line reading "drm_sysfs_suspend". Nothing more.

The machine does not respond to ping or ssh afterwards, neither directly after the wake-up nor 10 or 28 minutes later. There is some disk activity during the whole time span, though.

Another issue is that the machine again wakes up by pressing the touchpad button, which is a regression. Problem here is that the closed lid presses the button when put in a tight bag. This would cause the machine to return from sleep, which is clearly not intended here.

Revision history for this message
Mark Atkinson (ma300000) wrote :

The same problem occurs on my IBM T40 type 2373
"drm_sysfs_suspend"
Linux 2.6.24-16-generic (Hardy)

Revision history for this message
Jos Dehaes (jos-dehaes) wrote :

here too on a Dell Latitude D820, nvidia.

Revision history for this message
Danny Wood (danwood76) wrote :

I have had the same problems on a Toshiba L30 10V.

Resume from suspend works perfectly with a vanilla 2.6.24.3, I've tried various different kernel options on the Ubuntu kernel source to no avail.
I believe the problem lies with one of the kernel patches applied by the Ubuntu team.

This is quite a serious issue and there is a thread on the forums about it:
http://ubuntuforums.org/showthread.php?p=4970453#post4970453

Revision history for this message
elgilicious (elginearl-deactivatedaccount) wrote :

I can confirm on my machine, which has the following specs:

AMD 64 X2 5600+ (OC'ed to 3.2 GHz)
Asus M2N-E nForce 570 Ultra
4GB Corsair XMS DDR2 (800Mhz)
160 GB Western Digital Caviar
e-VGA GeForce 8800 GTS 512
Acer AL2216W LCD
Sound Blaster Audigy SE
Logitech X-540 5.1

Revision history for this message
empthollow (empthollow) wrote :

I can confirm this as well on toshiba laptop l25-s119
not sure of mobo,
radeon xpress 200m video
atheros wifi card
ac97 audio
realtek 8139 NIC
ati ixp sb400 usb controller

Revision history for this message
Joss Winn (josswinn) wrote :

I've tried the Ubuntu PPA 2.6.25-1 kernel and that doesn't resume from suspend either. I'm now using 2.6.24-16 with no issues.

Revision history for this message
Thomas Hammerl (thomas-hammerl) wrote :

I can confirm this on my Samsung R20. Resume stopped working after the upgrade to 2.6.24-17. Works fine with 2.6.24-16.

Revision history for this message
Stepan Zastupov (redchrom) wrote :

Benq Joybook r42, resume broken in 2.6.24-17 too :(

Revision history for this message
Danny Wood (danwood76) wrote :

I would just like to add that my resume from suspend doesnt work in 2.6.24-16-generic either, though im sure its the same bug.

Revision history for this message
khul (klas-physto) wrote :

Just changed from Gutsy to Hardy and had this problem on an hp tc4400. Fan comes on, screen black,
keyboard (including caps lock light) doesn't work. Have to power off. See no signs of any attempt to
resume in the logs. I changed back from 2.6.24-17 to old kernel (2.6.22-14) and it works.

Revision history for this message
am28111 (am28111) wrote :

I also have this problem as well. Resume was working fine in 2.6.24-16.

Revision history for this message
Stepan Zastupov (redchrom) wrote :

_Great_ job guys, you have pushed the new kernel to recommended updates but forgot to fix this bug.

Revision history for this message
Nick B. (futurepilot) wrote :

Same problem here on two computers.

HP a1150y desktop PC GeForce 6600
Dell Inspiron 8200 laptop. GeForce2 Go

Suspend worked perfectly on the -16 kernel using the Nvidia driver on both computers. Totally broke after upgrading as described. Hard drive spins up and that's about it. The screen never turns back on. No other hardware seems to get woken up.

Danny Wood (danwood76)
Changed in linux:
status: Triaged → Confirmed
Revision history for this message
Xandros Pilosa (folivora) wrote :

Confirming.
I have just marked Bug #234615 as duplicate of this bug.

Revision history for this message
Doc. Odine (doc-odine-cz) wrote :

I can confirm that on my FS Esprimo Mobile V5505. It has been doing that since Gutsy though. Typical resume time is between 60 and 120 seconds.

Revision history for this message
Tim Gardner (timg-tpi) wrote :

I believe suspend/resume problems have been exacerbated by the switch from FAIR_USER_SCHED to FAIR_CGROUP_SCHED. Please try the following:

echo "SUSPEND_MODULES=ehci-hcd" > /tmp/unload_modules
chmod +x /tmp/unload_modules
sudo mv /tmp/unload_modules /etc/pm/config.d

Revision history for this message
VladimirCZ (vlabla) wrote :

I can confirm this.

In my installation stopped working:
- switching on the CRT monitor when resuming from the suspend state
- resume from hibernate state (at some phase of restart the system freezes)
All these disfunctions applies to updated 2.6.24-17 kernel with updated nVidia-glx-new driver (updated on 26-May-2008)

With previous kernel 2.6.24-16 both resume processes work well.

My hardware & OS:
--------------------------
Asus mb P5KPL with Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz
Videocard GeForce 8500 GT
CRT Dell P1130
Ubuntu 8.04 (gnome) 64-bit desktop

Revision history for this message
Jos Dehaes (jos-dehaes) wrote :

I can confirm that setting ehci-hcd in unload_modules fixes resume with -17 kernel.

Revision history for this message
VladimirCZ (vlabla) wrote :

Please, accept this correction of my previous report:

I can confirm the same suspend - resume dysfunction.

I have tried Tim Gardner's setting ehci-hcd in unload_modules, but my PC did not suspend at all. Only screen became black (monitor was on) and HDD was writing intensively for a few minutes and then it lowered activity and nothing else happened. I had to reset the PC.

Revision history for this message
Xandros Pilosa (folivora) wrote :

Hi,
sorry to report, that SUSPEND_MODULES=ehci-hcd or in my case uhci-hcd (USB 1) does not solve the problem on my machine with 2.6.24-17.
With -16 kernel both suspend methods remain functional.

Revision history for this message
Pirouette Cacahuète (lissyx) wrote :

I can confirm the issue on a Toshiba Satellite Pro A100 PSAAA.
Works fine using 2.6.24-16-generic.

Revision history for this message
Peter Kerekfy (kerekfyp) wrote :

Confirm on HP Compaq nc6400 (hardy x86)

Following instructions on https://wiki.ubuntu.com/DebuggingKernelSuspend, dmesg says:
[ 39.175813] Magic number: 0:968:196
[ 39.175815] hash matches /build/buildd/linux-2.6.24/drivers/base/power/main.c:112
[ 39.175846] hash matches device ttys8
[ 39.175852] hash matches device ttypb

Revision history for this message
Nick B. (futurepilot) wrote :

Creating the unload_modules file did not work. The only thing that was different was that on resume the hard drive light was constantly on, but I couldn't hear any activity. Screen was still off, nothing responded to any input.

Revision history for this message
APavlov (pavlov81) wrote :

Tim's fix with unload_modules did not work for me either. There were no changes in the symptoms, and I could not check it with the -16 kernel because it would not boot complaining about a screwed NVidia driver (strange).

Revision history for this message
Peter Kerekfy (kerekfyp) wrote :

The unload_modules fix does not work for me either.
Booting the old 2.6.24-16 kernel makes suspend work again so it is very likely that the change from -16 to -17 causes the problem.

Revision history for this message
Matthias Jordan (matthiasjordan) wrote :

To me, the 2.6.24-16-powerpc was just as bad as the -17 but I downgraded to 2.6.22-14-powerpc and now suspend2ram works just fine. Hibernation sadly doen't work, though.

So with no changes other then the kernel and related modules, this seems like a kernel problem.

Revision history for this message
albert fishnets (mateolingerhaus) wrote :

I can confirm this bug on a gigabyte g33m dsr2 motherboard with core 2 duo processor and ATI graphics card. I can also confirm that Tims fix caused the computer to reduce to just spinning the drive and and required a hard reboot to restore the system.

Revision history for this message
Tim Gardner (timg-tpi) wrote :

OK, my next theory is the that scheduler change from CONFIG_FAIR_USER_SCHED to CONFIG_FAIR_CGROUP_SCHED has broken suspend, so I've built a kernel with the original scheduler setting. Please test by loading and running the kernel/lum packages from http://people.ubuntu.com/~rtg/linux-2.6.24-19. For example (if you are running the 64 bit kernel):

wget http://people.ubuntu.com/~rtg/linux-2.6.24-19/linux-image-2.6.24-19-generic_2.6.24-19.33_amd64.deb
wget http://people.ubuntu.com/~rtg/linux-2.6.24-19/linux-ubuntu-modules-2.6.24-19-generic_2.6.24-19.26_amd64.deb
sudo dpkg -i linux-image-2.6.24-19-generic_2.6.24-19.33_amd64.deb linux-ubuntu-modules-2.6.24-19-generic_2.6.24-19.26_amd64.deb
sudo reboot

Changed in linux:
assignee: ubuntu-kernel-team → timg-tpi
status: Confirmed → In Progress
Revision history for this message
Thomas Pifer (zero456) wrote :

Tim, is it possible to add a 2.6.24-19 restricted modules package so as to test this with an NVIDIA graphics card?

Revision history for this message
albert fishnets (mateolingerhaus) wrote :

Attempted 2.6.24-19 upgrade and rebooted to a white screen as there were no drivers for my ATI card. Went into graphics safe mode and attempted suspend. Computer suspended and I then pressed power to resume. It did exactly the same thing as with -17 except when I did hard reboot via the power supply it continued to just idle with the hard drive spinnig. I pulled all power for five minutes to see if I could get the RAM to clear. No luck, when power was resumed system went right back to just spinning the hard drive with a blank screen and no BIOS. I opened the case and pulled the CMOS jumper. That fixed it. System is back online. I uninstalled the -19 kernal cause it's scary.

Revision history for this message
Danny Wood (danwood76) wrote :

The kernel you supplied does not fix the issue.
On my custom 2.6.24.3 kernel (in which suspend works) I have this option enabled also so I highly doubt that this is causing the suspend issue.

Attached is the config for my working vanilla kernel if it helps you.

Revision history for this message
Gilles Gigan (gillesg) wrote :

Same symptoms as first reported, on Toshiba A100 - ATI Xpress 200M, ati binary driver. Suspend used to work fine (with 2.6.24-16), but after upgrade to -17 resume is broken. Black screen, no backlight, no HD activity. Magic dont work either. Turning off and back on doesnt restart the laptop, it stays frozen right after power on (no backlight, no HD activity). The only way to get it to boot again is to unplug both AC and battery, plug them back and try again. I tried the -19 kernel without success.
The resume-trace procedure shows:
[ 19.035013] registered taskstats version 1
[ 19.035146] Magic number: 0:968:373
[ 19.035149] hash matches /build/buildd/linux-2.6.24/drivers/base/power/main.c:112
As an aside note, I had to fix resume under 2.6.24-16 to get it to work properly: I had to use "sudo /etc/acpi/sleep.sh force" otherwise it wouldnt resume. But under -17, it doesnt work anymore.

Revision history for this message
Roberto Cássio Jr. (rcsdnj) wrote :

I'm having this problem too, and the behavior on my machine looks EXACTLY like a problem I had when testing Hardy Beta (only works after unplugging the power cable and plugging it again, like some reported). Suspend stopped working after a change called "tsc prevent time going backwards" (introduced in kernel 2.6.24-15.27), and it was fixed when this change was reverted, in the subsequent kernel (2.6.24-16.30). The link for the bug is here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/213723

Is there any possibility that this modification was included again by mistake?

Revision history for this message
ddumanis (dave-davedumanis) wrote :

I can resume from suspend, but networking (wired and wireless) is broken when I do. Everything worked fine in the previous kernel.

One word: regression.

Revision history for this message
Yann (lostec) wrote :

Same problem on a Toshiba P100 with 2.6.24-17-generic (T2300, 3945abg, Gb eth intel, nvdia 7600 Go with proprietary drv):

Suspend in -16 was almost working (no sound at resume, but this laptop suffer from acpi bugs and my prevous dapper+powersaved was also behaving the same :-().

In -17 it hangs at suspend just after disabling PCI IRQ for wifi pci id (iwl3945 related bug? argh, ipw was good, why changing for a LTS?!), just before syncing disks (comparing /var/log/message with unsucessfull suspend in -17 en successful one in -16).

Clearly a regression.

Steve Langasek (vorlon)
Changed in linux:
assignee: nobody → timg-tpi
importance: Undecided → High
milestone: none → ubuntu-8.04.1
status: New → Incomplete
status: Incomplete → In Progress
Revision history for this message
Charles Profitt (cprofitt) wrote :

I am having the same issue on a custom built:

Intel DP965LT w e6600 processor
Nvidia 8800 GTS (using the restricted driver from repos)

If I select the 2.6.24-16 kernel all is well, but the -17 just hangs and requires a reset button.

I am running 64bit.

Revision history for this message
thearch (alessandro-plasmati) wrote :

I have the same problem on this kernel.
ATI Radeon 9200SE with open source drivers.
With old kernel everything is fine.

Revision history for this message
Guido Jäkel (guido-jaekel) wrote : even on plain vanilla hardware

This is a "me too".

But i want to note, that i'm running it on an comparatively "old" and plain vanilla surf/email station: P4/1.6Ghz (no HT), PATA-100, AGP-GraphicCard (Matrox MGA550), uhci (USB 1.1), no WLAN, ...

may be this helps to exclude some things

good luck

Guido

Revision history for this message
Dexter (pogany-tamas+bug) wrote :

I can confirm this bug, I have to use 2.6.24-16, it is working fine.
My computer is:
MSI PM8M3-V motherboard
3.06 GHz Celeron Processor
1GB ram
Nvidia Geforce 5500

Revision history for this message
peddy (peddy22) wrote :

I can confirm this bug, suspend/resume fine worked fine in the previous kernel.

Revision history for this message
steve. (launchpad-coles) wrote :

Me too.
Suspend was working well in 2.6.24-16 but is broken after the upgrade to 2.6.24-17
Hardware Lenovo 3000 C200

Revision history for this message
Drolyk (drolyk) wrote :

The same problem. I`m trying to experement with SUSPEND_MODULES, but no luck.

Revision history for this message
Strelock (udafa) wrote :

I would like to confirm this bug on Compaq nw 8440. Failed to resume from suspend after update to 2.6.24-17. Simply booting to 2.6.24-16 solves the issue.

Revision history for this message
mazerj (james-mazer) wrote :

In case it matters -- I can confirm on a Sony Vaio pcg-z1vap. Suspend/resume/hibernate
all work fine under 2.4.24-16, freezes on resume with 2.4.24-17. Ubuntu pushed -17, but
if I boot to the -16 kernel via grub, keeping all else the same, everything works fine.

Revision history for this message
Robb Munson (r.munson) wrote :

A lot of confirms on this one, me added to it...its confirmed and there is a fix in progress...hope we get it soon :)

Revision history for this message
Lr5 (lrfive) wrote :

I have a similar problem when trying to resume from hibernate. It worked in the last kernel, but with the -17 one it doesn't work. I noticed that after resuming, ctrl+alt+f1 gets me to login, but trying to get to X doesn't work and freezes the system.

Revision history for this message
peter.maciocia (peter.maciocia) wrote :

Me too on a Sony Vaio VGN-N11S.

Everything working in -16 kernel (except fn-keys but thats Sony's fault), In -17 suspend works the first time, but not after that.

Revision history for this message
Charles Kung (ckung2005) wrote :

I have same problem and I have HP DV6324US laptop: AMD Turion 64x2 with Nvidia video.

I verified both disk and RAM suspense functions failed to resume with Kernel 2.6.24-17 generic.

Revision history for this message
William Grant (wgrant) wrote :

I'm similar to the rest: -16 resumes quickly, -17 doesn't, and neither does -19. However, -19 seems to recover in around one-third of the time that -17 takes, but I've only performed three trials on the new one.

Blacklisting ehci_hcd doesn't fix it, although both pm_trace and dmesg point to it being the culprit, as 1d.7 is the only EHCI controller in the system. Even removing all USB-related modules doesn't help.

Revision history for this message
Tim Gardner (timg-tpi) wrote :

Here is the next attempt to isolate the resume regression. This version has these 2 commits reverted:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commit;h=4b7c68904bf9ada8c4770ce5927e8ec71769ed92
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commit;h=850c3d6fed840a941727645767e5cf0e70ef59c4

echo "deb http://ppa.launchpad.net/timg-tpi/ubuntu hardy main" > /tmp/timg-tpi-ppa.list
sudo mv /tmp/timg-tpi-ppa.list /etc/apt/sources.list.d
sudo apt-get install linux-image-2.6.24-19-generic

If you need LUM, LRM, or LBM then install those packages from the same PPA source (amd64 was still building at the time of this note):

sudo apt-get install linux-ubuntu-modules-2.6.24-19-generic linux-restricted-modules-2.6.24-19-generic

Note: The nVidia and fglrx drivers for -19 are also in that PPA.

Revision history for this message
PM (pm77) wrote :

I have tried the kernel -19 fix, but had no luck. The suspend to ram still didn't work (haven't tried suspend to disk). My laptop HP nx9420 still hangs with a blank screen, unresponsive, on resume.

Revision history for this message
Jos Dehaes (jos-dehaes) wrote :

The -19 kernel and modules from Tim's PPA works for me, I successfully suspended/resumed 3 times in a row without problems.

This is without the ehci-hcd workaround, which only worked 2 times.

Revision history for this message
Nick B. (futurepilot) wrote :

The new -19 kernel did not work. Everything is still the same. Hard drive spins up and that's it. The screen still does not come back on and it's unresponsive to any input.

Revision history for this message
Thomas Pifer (zero456) wrote :

Same as PM and Nick B.: The proposed fix does not show any difference.

Revision history for this message
Tim Gardner (timg-tpi) wrote :

OK, I've about run out of ideas. One of you guys that can reproduce the problem are going to have to start a git-bisect to narrow down the commit between the -16 and -17 kernel.

Revision history for this message
Roberto Cássio Jr. (rcsdnj) wrote :

Tim, did you read comment #42?

Revision history for this message
albert fishnets (mateolingerhaus) wrote :

Tried -19 version 2.0. Still had the suspend error but did not have to jump cmos this time to reboot. behaves like -17. Thanks for trying Tim, let me know if i should send you any info to help.

Revision history for this message
Matthias (mgeenen) wrote :

Here it is the same bug since -17.

01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600M GS (rev a1)

Revision history for this message
Tim Gardner (timg-tpi) wrote :

Roberto - thats an interesting point. Commit 4d04686fe808ddc769c59771f5fd65672cfdf055 'Revert "UBUNTU: x86: tsc prevent time going backwards"' was reincarnated as commit 91d34e2c845a1c24a5802fd353165b1d68720a1a 'UBUNTU: TSC Clocksource can cause hangs and time jumps'. I reverted this in my PPA, so try linux_2.6.24-19.33ubuntu6 from http://ppa.launchpad.net/timg-tpi/ubuntu when its done building.

Revision history for this message
Nick Russell (thatnick) wrote :

I have this, but i'm wondering if its a separate issue as I have intel 3100 not nvidia. Is this only an nvidia bug?

Revision history for this message
Thomas Pifer (zero456) wrote :

The new linux_2.6.24-19.33ubuntu6 seems to have the problem fixed. The only problem was that there was no modules or restricted-modules package to match.

Revision history for this message
pfeels (pfeels) wrote :

I'm a noob, how can I upgrade to the fix ...

PS I hate being a noob ...

Revision history for this message
pfeels (pfeels) wrote :

I tried doing software update and only got up to 18, so i imagine 19 will be available in a few days

Revision history for this message
Tim Gardner (timg-tpi) wrote :

Thomas, pfeels: follow the directions in comment 59.

Revision history for this message
pfeels (pfeels) wrote :

The comments are not numbered so i counted them out, if this is 59

********************************************************************************

 Tim Gardner wrote on 2008-06-02: (permalink)

Here is the next attempt to isolate the resume regression. This version has these 2 commits reverted:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commit;h=4b7c68904bf9ada8c4770ce5927e8ec71769ed92
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commit;h=850c3d6fed840a941727645767e5cf0e70ef59c4

echo "deb http://ppa.launchpad.net/timg-tpi/ubuntu hardy main" > /tmp/timg-tpi-ppa.list
sudo mv /tmp/timg-tpi-ppa.list /etc/apt/sources.list.d
sudo apt-get install linux-image-2.6.24-19-generic

If you need LUM, LRM, or LBM then install those packages from the same PPA source (amd64 was still building at the time of this note):

sudo apt-get install linux-ubuntu-modules-2.6.24-19-generic linux-restricted-modules-2.6.24-19-generic

Note: The nVidia and fglrx drivers for -19 are also in that PPA.

********************************************************************

I tried it in terminal and I keep getting:

Couldn't find package linux-image-2.6.24-19-generic

Revision history for this message
martywd (martywd) wrote :

Running hardy on an older laptop: HP M2108US w/celeron proc. Suspend has not work on this machine since 2.6.24-16

Following instruction in comment #59 and did a:
apt-get install linux-image-2.6.24-19-generic linux-ubuntu-modules-2.6.24-19-generic linux-restricted-modules-2.6.24-19-generic

In 2.6.24-19 suspend functionality works!

Downside sound now does not work, although for the first time the system 'beep' works?

attached is lspci -v in text file for this HP M2108

Revision history for this message
jperry (ubuntubugzilla) wrote :

I notice there is a new rev of the NVIDIA driver which may (or may not) help people.
The Nvidia driver is at version 173.14.05 as of May 28,2008

This won't help me - I am running Hardy Heron as shipped with kernel 2.6.24-16 and was careful enough
to read about reports of this regression before deciding to accept the latest kernel update to -17.
My suspend to ram is not working at -16 and the release notes for the nvidia driver seem to indicate
a problem has been fixed relayed to the 6150 Go chipset and DPMS not restoring the screen - sounds
like the problem many are seeing here. I wonder if this recent update broke some people and helped others.

I just tried to install the new nvidia driver and it failed to build a the needed kernel module
so I thought no problem I will use the -uninstall feature. It uninstalled all right - everything.
It did not restore the old kernel module. Now I'm really stuck since for some bizarre reason
the -16 kernel no longer is in the official Ubuntu repository!???

Anyone know why this is? I can look at the repository in a web browser and see even
older kernel builds but why did they remove "-16"??

Any ideas on how I can get back to an official Hardy Ubuntu "-16" kernel??

Thank you!

Revision history for this message
Thomas Pifer (zero456) wrote :

Tim: I just double-checked by uninstalling and reinstalling the packages per comment #59. The modules and restricted-modules packages do not seem to work with the latest 2.6.24-19.33ubuntu6. The version numbers also do not seem to match (2.6.24.13-19.41ubuntu1 vs. 2.6.24-19.33ubuntu6).

Revision history for this message
Elim Garak (nightflyer-71) wrote :

Just in case anyone was wondering, 2.6.24-18, which just showed up on my repositories, does not fix the problem, either. I am running an Acer Aspire T690 (AST690-EP925A) with dual Pentium D 3.0 Ghz and 2.0 Gb RAM.

jperry: I have -16, -17, and -18 on my machine, but still use -16 because of this issue. 2.6.24-16 still shows up in my repositories in aptitude. Does 16 still show up in your grub list?

Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 226279] Re: Kernel 2.6.24-17 - broken resume from suspend to RAM

pfeels [2008-06-04 1:23 -0000]:
> The comments are not numbered so i counted them out, if this is 59

You can see them in the "Permalink" link address.

> echo "deb http://ppa.launchpad.net/timg-tpi/ubuntu hardy main" > /tmp/timg-tpi-ppa.list
> sudo mv /tmp/timg-tpi-ppa.list /etc/apt/sources.list.d

Here is a step missing: "sudo apt-get update".

> sudo apt-get install linux-image-2.6.24-19-generic

> I tried it in terminal and I keep getting:
>
> Couldn't find package linux-image-2.6.24-19-generic

If you do the apt-get update, it will work.

Revision history for this message
Gianluca Masci (g-masci) wrote : Re: [Bug 226279] Re: Kernel 2.6.24-17 - broken resume from suspend to RAM

kernel 2.6.24-18 non solve the problem for me, in the attack file the
kernel log after resume.

Il giorno mer, 04/06/2008 alle 05.34 +0000, Martin Pitt ha scritto:
> pfeels [2008-06-04 1:23 -0000]:
> > The comments are not numbered so i counted them out, if this is 59
>
> You can see them in the "Permalink" link address.
>
> > echo "deb http://ppa.launchpad.net/timg-tpi/ubuntu hardy main" > /tmp/timg-tpi-ppa.list
> > sudo mv /tmp/timg-tpi-ppa.list /etc/apt/sources.list.d
>
> Here is a step missing: "sudo apt-get update".
>
> > sudo apt-get install linux-image-2.6.24-19-generic
>
> > I tried it in terminal and I keep getting:
> >
> > Couldn't find package linux-image-2.6.24-19-generic
>
> If you do the apt-get update, it will work.
>
--
--
Gianluca Masci
Giano Solutions S.r.l.
Via Filippo Tommaso Marinetti, 221 - 00143 Roma (RM) - Italy

* Cell: +39 338 7309546
* Tel: +39 06 64530348 / 06 62279572
* Fax: +39 06 64530348
* e-mail: <email address hidden>
* web: www.giano-solutions.com
_______________________________________________

Le informazioni contenute in questa comunicazione e gli eventuali
documenti allegati hanno carattere confidenziale e sono a uso esclusivo
del destinatario.
Nel caso questa comunicazione vi sia pervenuta per errore, Vi informiamo
che la sua diffusione e riproduzione è contraria alla legge e preghiamo
di darci prontamente avviso e di cancellare quanto ricevuto. Grazie.

This e-mail message and any files transmitted with it contain
confidential information intended only for the person(s) to whom it is
addressed. If you are not the intended recipient, you are hereby
notified that any use or distribution of this e-mail is strictly
prohibited: please notify the sender and delete the original
message. Thank you.

Revision history for this message
Danny Wood (danwood76) wrote :

Tim the -19 kernel (v2) worked perfectly on mine, with both suspend to RAM and suspend to disk.
You're a star.

Revision history for this message
pfeels (pfeels) wrote :

Thanks Martin And everybody else for their hard work ...

So to make it easier for the other noobs below is what you put into Terminal (at least thats what I think Martin was saying)

echo "deb http://ppa.launchpad.net/timg-tpi/ubuntu hardy main" > /tmp/timg-tpi-ppa.list
sudo mv /tmp/timg-tpi-ppa.list /etc/apt/sources.list.d
sudo apt-get install linux-image-2.6.24-19-generic
sudo apt-get update

I'll try it, thanks again

Revision history for this message
Yann (lostec) wrote :

If -19 suspends works, when will this new one be released? -17 did not last very long (about 1 week!)...
Or at least be in "proposed" for easy installation/try?

As well, as we have a suspend debugging star, there is lots of concerns (in launchpad as well as in ubuuntu forums around the world) with sound not recovering from suspend (since pulseaudio?): Any idea for this one?

Regards!

Revision history for this message
pfeels (pfeels) wrote :

It went through the motions and the downloading and installing but Start-Up Manager does not give me 19 as an option and as it did the downloading not once did it mention 19, it did show 17 & 18

Revision history for this message
Joss Winn (josswinn) wrote :

Yesterday's timg -19 update did nothing for me. -16 is the last kernel to have suspend working.

Lenovo 3000 N100 0768-FPG Core Duo.

Thanks for your efforts to fix this.

Revision history for this message
pfeels (pfeels) wrote :

Ok, I think I got it ... after doing everything in post #82 and letting the computer run through the updates I then put this line in terminal (which I got from post #59)

sudo apt-get install linux-ubuntu-modules-2.6.24-19-generic linux-restricted-modules-2.6.24-19-generic

Now the restart

Revision history for this message
albert fishnets (mateolingerhaus) wrote :

"I have this, but i'm wondering if its a separate issue as I have intel 3100 not nvidia. Is this only an nvidia bug?"

This is not esculisive to nvidia chipsets. I have an ATI radeon card and intel 3100 graphics on board and I'm havint the same problem with both GPU's. Just did -18 upgrade via reposiories today, did not fix the problem. I will try -19 again but didn't work last time on my system. This may have to do with my ATI card.

Revision history for this message
pfeels (pfeels) wrote :

Video settings are on what looks like Safe Mode and no sound ... No volume control or GStream plug ins detected ... maybe I'll just go back to 16 and wait a month, lol

Revision history for this message
jperry (ubuntubugzilla) wrote :

@Jason Roth: Thanks for the offer. I did get back to a working nvidia proprietary driver by finding a repository which still has linux-restricted-modules-2.6.24-16 and installing it, then going to the hardware control app and checking the box to be sure it was activated. Once I re-copied my xconf.org file with "nvidia" as the driver setting and restarted X I was back in business :-) Pretty stressful though. I took note of the locations of the the two key
files the nvidia installer installs and when I next attempt this upgrade I will back up these locations.
The kernel module is nvidia.mod.o and the X module is nvidia_drv.so (remember to do an updatedb , then use
the locate command to tell you where to find them)

Revision history for this message
jperry (ubuntubugzilla) wrote :

Lack of sound may just mean you need to re-compile the sound modules for this new kernel you just installed.
Failing that perhaps try a newer version of the alsa sound drivers. I had to use the absolute latest recently on a laptop I was configuring with Ubuntu 8.04

Revision history for this message
Nick B. (futurepilot) wrote :

Ok suspend is working for me again with linux-image-2.6.24-19.33ubuntu6. But I can't be 100% sure because there was no LRM so I was running in safe mode.

Revision history for this message
Tim Gardner (timg-tpi) wrote :

SRU Justification:

Impact: Hardy commit d617b07f7e8b465f29c82d84fbc12febf43b2900 caused suspend to RAM regressions.

Patch Description: Reverted commit d617b07f7e8b465f29c82d84fbc12febf43b2900

patch: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commit;h=d617b07f7e8b465f29c82d84fbc12febf43b2900

TEST CASE: See bug description.

Revision history for this message
martywd (martywd) wrote :

Just to clarify my earlier comment (#75). The suspend/resume functionality _work_ on my machine (HP Compaq M2108US) when booted into 2.6.24-16. For me the resume from suspend issue started with -17, continuing with -18.

Today I re-read "APavlov's" comment #6 and decided to test. I booted into 2.6.24-18, initiated suspend, then resume. Hard drive spins up, but no display, no prompt, no keyboard or mouse function. I wait. ~2 mins later, display lights up, keyboard and mouse function return, log in, all is well. Second test still in 2.6.24-18, initiate suspend, then resume, wait, ~4 mins after resume, again, display lights, keyboard and mouse function returns, etc.

Attached is my syslog during the time frame of the two 'tests' described above.

I'm not a developer or a programmer. I don't know what's up here?

Revision history for this message
Tim Gardner (timg-tpi) wrote :
Changed in linux:
status: In Progress → Fix Committed
Revision history for this message
John Stultz (jstultz) wrote :

Looking at the commit being reverted, its broken because the fix is not complete compared to mainline.

Compare the original Ubuntu commit-diff here:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commitdiff;h=52339c46c30f69ceafce1b3d9f87d04d02e3aa05

With the upstream commit here:
http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=d8bb6f4c1670c8324e4135c61ef07486f7f17379;hp=f1326973262382150c26bf4dfccd0fce310c4a9c

Noting especially the changes made upstream to kernel/time/timekeeping.c

Revision history for this message
Guido Jäkel (guido-jaekel) wrote :

Dear Tim,

i wonder about this TSC issue the patch was designed for happens on my (and the other) machines, because it's have a single CPU without HT.

The patch says "return some last value until the normal used one is higher than". From that: Will the TSC reset, if the CPU is suspended (powered down?). Then, after resume, the two calls will return the "last" values forever and *all* loops driven by that will hang.

If this is the core reason, maybe the TSC value should be compared with some low value indicating that the CPU have a low uptime yet. And the "last" value should be lowered (or zeroed) in this case before the committed compare. Or -- even better, but may be more difficult -- the "last" value should be zeroed on some early initialisation stage of the CPU(s)

greetings

Guido

Revision history for this message
Guido Jäkel (guido-jaekel) wrote :

Dear john and Tim

john> Looking at the commit being reverted, its broken because the fix is not complete compared to mainline.
john> [...]
john> Noting especially the changes made upstream to kernel/time/timekeeping.c

> @@ -178,6 +178,7 @@ static void change_clocksource(void)
> + new->cycle_last = 0;
> @@ -295,6 +296,7 @@ static int timekeeping_resume(struct sys_device *dev)
> + clock->cycle_last = 0;

Good or bad -- I didn't take a look on that clash before my guesses at #96. But it seems perfectly(?) match to my theory and -- if it holds -- to the proposed idea of a solution. It also matches some statements, that after waiting a longer time the system will continue to resume. This period might be the elapsed uptime until first suspend, because the TSC must at least re-incement to this uptime to "break" a delay loop somewhere.

greetings

Guido

Revision history for this message
pfeels (pfeels) wrote :

Can anyone help me on getting my screen resolution back to normal, I'm stuck in 640 X 480 ... This happened after I got 19 to work, my sound on the other hand came back after a reboot ... I have nVidea GeForce 7300 LE ...

Should I try and download the latest driver for it?

Revision history for this message
pfeels (pfeels) wrote :

I take it back, my sound went away again ...

Revision history for this message
Thomas Pifer (zero456) wrote :

pfeels: As per my previous comment, the linux-ubuntu-modules-2.6.24-19-generic and linux-restricted-modules-2.6.24-19-generic packages do not work with Tim's latest linux-image-2.6.24-19-generic, so you'll need to wait until they are rebuilt.

Revision history for this message
pfeels (pfeels) wrote :

Oh sorry, I'm out of my league here ... I've reverted back to 16 and still have no idea how to get my screen resolution back to normal but I'll search, thanks again guys and sorry, but I'm new ...

Revision history for this message
mazerj (james-mazer) wrote :

Just tried 2.6.24-18-generic on my Vaio -- still no joy -- back to 16 again for me..

Revision history for this message
gasman (gaspasser) wrote :

Also confirm that -17 and -18 fail to resume from suspend on my Dell smartstep 250N laptop. No idea what to do beside use -16 kernel. Looking forward to a fix soon! Bon chance to those in the know.

Revision history for this message
Ohb01 (ohb01) wrote :

I confirm that both 2.6.24-17-generic and 2.6.24-18-generic fail to resume from suspend on Dell Dimension 4700 with BIOS Rev. A10. None of the older kernels in my GRUB list help to solve this problem, either. I am not using the restricted ATI driver, only the restricted Atheros driver for my wireless card.

It had all worked so well in Gutsy, but stopped working after upgrading to Hardy. I really want Suspend/Resume (and Hibernate/Resume) to work again.

I would try the PPA kernel 2.6.25 method that is suggested in Bug #221213 (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/221213/comments/8 ) but I'm awaiting clarification on how to do it.

Please let me know if there is anything I can do to help fix this. Detailed instructions would be great, as I'm quite new at this. Thanks in advance for your help.

Revision history for this message
Ohb01 (ohb01) wrote :

I've just tried the above linux-image-2.6.24-19-generic solution (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/226279/comments/59 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/226279/comments/82 ). But as noted by Thomas Pifer (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/226279/comments/100 ), the modules do not seem to work. Despite my best efforts, after rebooting with the 2.6.24-19 kernel, I had no sound and no wireless (Atheros).

Is it safe to just do sudo apt-get --purge remove linux-image-2.6.24-19-generic linux-ubuntu-modules-2.6.24-19-generic linux-restricted-modules-2.6.24-19-generic ?

Should I also delete timg-tpi-ppa.list from /etc/apt/sources.list.d to avoid the above items being reinstalled with the update?

Thanks in advance for your help.

Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 226279] Re: Kernel 2.6.24-17 - broken resume from suspend to RAM

Ohb01 [2008-06-05 6:08 -0000]:
> I've just tried the above linux-image-2.6.24-19-generic solution (see
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/226279/comments/59
> and
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/226279/comments/82
> ). But as noted by Thomas Pifer
> (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/226279/comments/100
> ), the modules do not seem to work. Despite my best efforts, after
> rebooting with the 2.6.24-19 kernel, I had no sound and no wireless
> (Atheros).

This is because you did not have the corresponding
linux-ubuntu-modules. Sorry for the hassle.

> Is it safe to just do sudo apt-get --purge remove linux-
> image-2.6.24-19-generic linux-ubuntu-modules-2.6.24-19-generic linux-
> restricted-modules-2.6.24-19-generic ?

Yes. Your system should boot into -18 again by default (you can select
this in the boot manager). Please note that you can only do the above
if you are not actually *running* this kernel at the moment. Otherwise
you'll get a big fat warning (which you can override, though).

> Should I also delete timg-tpi-ppa.list from /etc/apt/sources.list.d to
> avoid the above items being reinstalled with the update?

Yes, please do so.

The official -19 kernel has been uploaded to hardy-proposed now. The
corresponding linux-ubuntu and linux-restricted-modules should be
available by the end of the day. Testing that kernel would be great,
it should fix the suspend issue without breaking wifi, etc.

Revision history for this message
Yann (lostec) wrote :

As we are on suspend issues with some competent kernel people in this thread, another delay issue at suspend (depending on network interfaces/configuration, this can lead to >30sec delay with a black screen) could be considered.

A configuration ack can be done, but wired network modules could integrate a link-up check before trying to setup interfaces so that this issue could be solved in direct configurations as well as in every network managers.

See:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/236066

It have been assigned to pm-utils by someone but to my mind this is really a kernel/network driver modules issue that clearly show at resume... but not only.

Regards

Revision history for this message
Valentin Longchamp (longfield) wrote :

I just want to add a "me too" post on my Thinkpad T60p. Suspend/resume (by the way, that's resume that hangs, being VERY long) has stopped working since -17 and does not work with -18.

It looks like -19 proposed by Tim has corrected the bug, but since this laptop is my work computer and I need it rather stable, I don't feel like installing something from PPA (or don't have time to do it).

When can we expect the -19 to be released on the official package sources ?

Revision history for this message
pfeels (pfeels) wrote :

After some tense hours working at getting everything back to normal it's all working good and then I notice I'm using the 16 kernel, I downloaded todays update and my only worry is I'll get stuck in 640x480 video again with my nvidea driver ... question, did todays updates take care of the video card getting stuck in 640x480 or should I keep using 16 ...

It's amazing the time and energy you guys put in for open source and the time you take to teach ...

Revision history for this message
Pascal-J (jacquin-pascal) wrote :

Thanks Martin. :-)
Resume from suspend to ram is working back using -19 you have summited in hardy-proposed.
Tested on HP Compaq nc2400 with last BIOS from HP.

Revision history for this message
pfeels (pfeels) wrote :

Went over to 19 with all the updates and everything is working including the suspend, thanks guys

Revision history for this message
martywd (martywd) wrote :

From hardy-proposed, installed linux-image-2.6.24-19-generic linux-ubuntu-modules-2.6.24-19-generic linux-restricted-modules-2.6.24-19-generic

Rebooted into -19. Sound works at gui logon. Broadcom wireless card working.

Put the machine into suspend for 25 mins. Next resume. Display immediately lights up, keyboard and mouse functioning as expected. All seems well thus far?

Thank you kernel guys et al.

Revision history for this message
Ohb01 (ohb01) wrote :

Good news: The -19 kernel in hardy-proposed fixed Resume from Hibernate for me (though it is slow, and progress bar looks frozen, it works). Bad news: Resume from Suspend is still broken for me.

Details of what I did:

I have a Dimension 4700 - BIOS Rev. A10, Atheros-based wireless card with restricted driver, no restricted ATI driver used.

I removed previous version of -19 kernel and repository as per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/226279/comments/106

Figured out how to add hardy-proposed repository, (GUI method, but based on repository listing in http://ph.ubuntuforums.com/showpost.php?s=0d6286ee06bc8596c8a856a2247212e3&p=4846197&postcount=8 ), i.e.: System > Administration > Software Sources > [administrator password] > Third-Party Software tab > Add > deb http://archive.ubuntu.com/ubuntu hardy-proposed main restricted universe multiverse

Let Update Manager update the list of files. Ignored suggested application updates for now -- wanted to try new kernel first. So:

Applications > Accessories > Terminal > sudo apt-get install linux-image-2.6.24-19-generic linux-ubuntu-modules-2.6.24-19-generic linux-restricted-modules-2.6.24-19-generic

Restarted computer.

Selected the -19 kernel in GRUB

Logged into my account and waited for GNOME to finish loading. Wireless and sound seemed to work this time.

Tried System > Quit > Suspend

Suspended quickly, but pressing Power button on computer to resume resulted in a blank screen with a blinking cursor, no keyboard, no mouse, no GUI, no Login. I waited a few minutes, but nothing was happening, not even disk activity.
Restarted computer.

Selected the -19 kernel in GRUB

Logged into my account and waited for GNOME to finish loading.

Tried System > Quit > Hibernate

Shut down fairly quickly with a couple of error messages (sorry, they went by too fast -- are they saved in a log somewhere?).

Pressing Power button on computer to resume resulted in a slow process to get the splash screen up, the progress bar moved back and forth a bit and then seemed to freeze, there was still sporadic disk activity, and then finally the Password prompt for my account came up, and I was able to log back into the GNOME GUI. It was slower than in Gutsy, and the frozen progress bar was not reassuring. On the plus side, wireless networking worked right away after the Resume.

There is definite improvement overall, with at least Hibernate being possible again. Thanks you very much or all your work on this, and thanks in advance for looking into the Suspend issue further if possible.

Revision history for this message
Thomas Pifer (zero456) wrote :

Installed the update from hardy-proposed and everything seems to be in working order (including working modules and restricted-modules). Well done all.

Revision history for this message
APavlov (pavlov81) wrote :

Thanks folks, the STR in the -19 kernel works great, but it seems to cause a regression: when trying to "sudo reboot" after a suspend-to-RAM - resume cycle, the machine hangs at the splash screen, just after the keyboard LEDs blink. Any clues?

Revision history for this message
Matthias Jordan (matthiasjordan) wrote :

For me, this issue is fixed in Linux version 2.6.24-19-powerpc (buildd@ross) (gcc version 4.1.3 20080308 (prerelease) (Ubuntu 4.1.2-21ubuntu1)) #1 Wed Jun 4 15:27:43 UTC 2008

Also the reboot issue mentioned by APavlov doesn't show up on my machine. Thanks a million for fixing this!

Revision history for this message
Nick B. (futurepilot) wrote :

Tested again with -19 kernel and LRM this time, suspend still working perfectly. I wasn't able to reproduce the sudo reboot issue either.

Revision history for this message
martywd (martywd) wrote :

Re: APavlov's recent comment.

Just tried suspend, then resume, then 'sudo reboot' on my machine. My machine rebooted without the hang described by APavlov.

To be clear. I _only_ installed the -19 linux-image*-generic, linux-ubuntu-modules*, linux-restricted-modules* debs using 'apt-get install'. I did not install any of the other suggested updates showing in 'update-manager' with the 'deb http://us.archive.ubuntu.com/ubuntu/ hardy-proposed main restricted universe multiverse' repository active.

Other than the three -19 packages listed above, my machine running on all currently released updates.

Revision history for this message
richr (richspamtrap-internet) wrote :

-19 kernel from the ubuntu repositories: suspend works. hibernate doesn't work. But, if i suspend, resume, then hibernate without having rebooted, hibernate works.

Revision history for this message
Xandros Pilosa (folivora) wrote :

Resume from STR and hibernation is back with 2.6.24-19 in my case. No other issues so far with this Kernel version.
Thanks to Tim and to all of you who contributed.
Regards!

Revision history for this message
Jan Rathmann (kaiserclaudius) wrote :

On my system suspend to disk also seems to work again with 2.6.24.19. Thanks alot!

Kind regards,
Jan

Revision history for this message
Ivan Kravchenko (iv-kravchenko) wrote :

2.6.24-19 works well for me. Fine!

Revision history for this message
Ohb01 (ohb01) wrote :

Update to my previous post (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/226279/comments/113 ): This morning, there were a number of items related to kernel 2.6.24-19-generic in my automated Update Manager list. I'm not sure which repository they were from (hardy-proposed or a more regular repository). I told the system to download and install all the updated. Oddly, there was no automated request to restart the computer. I restarted anyway, using the 2.6.24-19-generic entry in GRUB. Same result as before, though: Suspend/Resume does not work. Hibernate works but very slowly (not sure if there is a real advantage compared to full Shutdown/restart).

Kernel 2.6.20-16-generic allows me to Resume from both Suspend and Hibernate, but again very slowly: see my post at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/221213/comments/18

Revision history for this message
mtb-cliff (pagedynamix) wrote :

Hi Folks, I just ran in to this thread. I am running on a Toshiba A210 using the generic kernel (restricted drivers for the wireless {ndiswrapper} and the ATI chipset). I tried using the -19 kernel with modules and LRM. rebooted and invoked suspend (from menu). Resume did not work. following from the syslog file. I don't know if there is something different than the issue that is in this thread.

Jun 7 22:38:33 laptop kernel: [ 33.445269] Attempting manual resume
Jun 7 22:38:33 laptop kernel: [ 33.445273] swsusp: Resume From Partition 8:6
Jun 7 22:38:33 laptop kernel: [ 33.445275] PM: Checking swsusp image.
Jun 7 22:38:33 laptop kernel: [ 33.445757] PM: Resume from disk failed.

I am going to attempt again, but using update manager (only selecting linux* and pm-utils) to see if it improves my luck.

Revision history for this message
mtb-cliff (pagedynamix) wrote :

No luck. Same activity. I noticed something different. I tried going to terminal using ALT-F2 and trying to start gdm manually using sudo /etc/init.d/gdm restart and so long as I was in the non-X11 session, my Caps Lock key would light. As soon as I switched to ALT-F7, I lost the Caps Lock key (and entire keyboard - can't use sysreq r,s,b to recover).

Revision history for this message
pfeels (pfeels) wrote :

Downloaded this mornings update to the kernel (19, there were 2) and now Ubuntu won't start ... any idea's, I'm stuck using windows, this stinks ...

Revision history for this message
pfeels (pfeels) wrote :

Tried reboot and computer went into checking hard drive mode, "60 reparse records processed" and a bunch of something about missing and deleted files, any help guys?

Revision history for this message
pfeels (pfeels) wrote :

My grub folder is empty ... and these are the files my computer can't find to load, is mt only option a reinstall?

Revision history for this message
albert fishnets (mateolingerhaus) wrote :

Hey pfeels, you want to download and burn a copy of the ubuntu alternate cd from here: http://www.ubuntu.com/getubuntu/download

Make sure the check the box under the green start download button to get the alternate disc.
(For futre reference, keep this disc handy as it's the only version of Ubuntu that has all the repare tools you need in one place)

Once you have downloaded and burned the .iso boot from the disk and select the "repair broken system" option. Once in that list select the option to reinstall Grub and all the kernal modules (this will revert your system back to the -16 kernel. You may just be able to reinstall Grub and be fine, so try that first.

Now you should be able to just reboot your system and all should be good. Keep this disc around and always burn the new version of this disc with each ubuntu flavor ubgrade. It's insanly handy for stuff like kernel tweaking (ie what you just did ;-)) and changing xorg.conf files, stuff that can bork your system to the point were it won't even boot anymore.

Hope that helps.

Revision history for this message
pfeels (pfeels) wrote :

Thanks a ton, I'm already downloading it and I checked the box for the alternate ... So many people are so helpful on these forums, thanks again

Revision history for this message
Tim Gardner (timg-tpi) wrote :

I don't think this issue exists for Intrepid since the upstream patch was implemented correctly.

Changed in linux:
status: In Progress → Invalid
assignee: timg-tpi → nobody
importance: High → Undecided
Revision history for this message
Yann (lostec) wrote :

So, in the next -19 that will probably soon come out of proposed, what will be implemented:
-Problematic patch removed (what possible issues?).
-Patch correction to match upstream one (should probably be tested by some volunteers in this report?).

Regards

Revision history for this message
cyoo (cyoo96) wrote :

I can confirm this bug too: hibernate works with 2.6.24-16, but not with -17 and -18 (not tried -19 and above). I am using -18 because -16 has sound problems (however, I still can't make -18 recognize my system's microphone).
My computer is:
Toshiba A205-S5825 laptop
upgraded to 2GB RAM

Revision history for this message
Richard Elkins (texadactyl) wrote :

I have an iMac Core2Duo circa October 2007. I attached output of lspci.

I had the 'cannot resume after suspend' issue consistently. I fell back to 2.6.24-12-generic #1 SMP. The issue disappeared -- progress! It is a little slow at waking up but it definitely wakes up.

I did try the -19 in hardy-proposed. Unfortunately, this had the side effect of a Gnome pure white screen (literally) after the normal Ubuntu pale orange background is displayed. Nothing will get me the desktop (shaking mouse, tapping keyboard keys, waiting 10 minutes). Fortunately, I was able to bust into to a login prompt, login as the root, and reboot.

So, it looks like -19 needs some testing with iMacs and other Macs.

If you would like me to test a patch, email me with instructions ==> <email address hidden>

Revision history for this message
Richard Elkins (texadactyl) wrote :

And here is a dmesg log too

Revision history for this message
Peter Marks (peter-indigomail) wrote :

Richard, did you try typing your password and hitting return? My machine always used to restore to a white screen, but gnome was actually running with the locked screen. Typing my password and hitting return always brought it back... of course it is completely broken now, but that is why I'm following this thread.

Revision history for this message
Richard Elkins (texadactyl) wrote : Re: [Bug 226279] Re: Kernel 2.6.24-17 - broken resume from suspend to RAM

Thanks for the idea.&nbsp; I have my system configured to auto login to a particular user.&nbsp; I smashed [(:] the enter key, moved the mouse all over the place, pressed every other key combo I could think of.&nbsp; The only thing that worked was the normal 3-key escape sequence to the text login prompt.

I need the suspend (sleep) turned on because iMacs tend to get a bit hot around the disk drive area.

It'll get fixed eventually:&nbsp; -12 was working so -19 or -20 will probably do the trick.

It may seem silly but I missed Ubuntu and see no advantage for me with MACOSX.

-Richard

--- On Tue, 6/10/08, Peter Marks &lt;<email address hidden>&gt; wrote:
From: Peter Marks &lt;<email address hidden>&gt;
Subject: [Bug 226279] Re: Kernel 2.6.24-17 - broken resume from suspend to RAM
To: <email address hidden>
Date: Tuesday, June 10, 2008, 5:42 PM

Richard, did you try typing your password and hitting return? My machine
always used to restore to a white screen, but gnome was actually running
with the locked screen. Typing my password and hitting return always
brought it back... of course it is completely broken now, but that is
why I'm following this thread.

--
Kernel 2.6.24-17 - broken resume from suspend to RAM
https://bugs.launchpad.net/bugs/226279
You received this bug notification because you are a direct subscriber
of the bug.

Revision history for this message
Ohb01 (ohb01) wrote :

Another problem with my work-around using kernel 2.6.20-16-generic (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/221213/comments/18): computer goes back into Suspend if I try to Switch user after resuming from Suspend! I have to resume from Suspend again, wait a few more minutes, and then I can log into the other account. By that time, it would have been faster to use regular Shut Down and power up.

Revision history for this message
Ohb01 (ohb01) wrote :

I would test any proposed solutions / new kernel versions as time and connectivity permit. Detailed download/install/test/report instructions would make it easier for me, as I'm still quite new at this. Thanks to everyone who is working on fixing this issue.

Revision history for this message
Andy Walker (walkeraj) wrote :

I have attempted to use 2.6.24-19 from this thread and from hardy-upstream. Neither solves this issue for me. What information can I provide to help fix this bug?

Revision history for this message
Martin Pitt (pitti) wrote :

Andy, and other reporters here for whom -19 does not work: did the original kernel -16 actually work with suspend/resume? If not, then this is no surprise, as this bug is merely about the regression between -16 and -19. -19 will not magically fix resume on machines where -16 failed.

Revision history for this message
ddumanis (dave-davedumanis) wrote :

To Martin Pitt's question: 16 suspends and resumes beautifully, with networking.

All later kernels, including 19, suspend, then resume with no networking (wired nor wireless).

Revision history for this message
Paul Weaver (paul-weaver-uk) wrote :

Unfortunately it's not all roses on my HP nc2400. Sleep works, and works well, however a couple of times wireless (iwl3945) hasn't returned after sleep. I *think* this is after an extended period of sleep (a few hours), rather than 20 minutes.

rmmodding iwl3945, iwlwifi_mac80211 and cfg80211 and re modprobing didn't help. dmesg reported that the RF kill switch was off, when it wasn't. Turning it off and back on didn't help. It's a soft-switch with two leds (front and button), the switch appeared to work. ifconfig -a didn't show the eth1 interface (or wlan0), iwconfig reported no interfaces with wireless extensions.

It seems the nic goes into a deep sleep and doesn't recover, shown from this snippet of dmesg:
[ 566.057603] iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection
[ 566.134658] iwl3945: Radio Frequency Kill Switch is On:
[ 566.134665] Kill switch must be turned off for wireless networking to work.
[ 566.141865] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC
[ 566.151904] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC
[ 566.171864] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC
[ 566.199436] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC
[ 566.219415] iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels
[ 578.170956] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC
[ 578.220662] iwl3945: MAC is in deep sleep!
[ 578.220807] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC
[ 578.280439] iwl3945: MAC is in deep sleep!
[ 578.280524] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC
[ 578.340155] iwl3945: MAC is in deep sleep!
[ 578.449917] iwl3945: WARNING: Requesting MAC access during RFKILL wakes up NIC

Revision history for this message
albert fishnets (mateolingerhaus) wrote :

Richard: Whit Screen of Death

What's happening is your graphics driver was not updated with -19 kernel. If you can try and go into graphics safe mode/recovery mode from the grub menu and see if you can enable your graphics card from there. Your going to want to go into the restricted drivers manager/hardware manager and enable it from there. I had to do this as well as I had not updated envy to envyng.

For all others: I could not get the orginal -19 kernel to work for suspend but the one in proposed updates fixed my system (don't really know why as I'm sure they're the same but it may be the other updates it offered) I suggest enabling proposed in the updates section of software sources and trying the update from there. If that doesn't work then post your out puts.

Thanks again to to Tom and everyone for their fast and diligent work on this issue. My power bill and the electrical grid of WA state thank you!

Revision history for this message
ddumanis (dave-davedumanis) wrote :

Here's my dmesg output from when I resume from suspend and network-manager becomes useless, with no wired or wireless networks in the dropdown list (all in kernel -19):

[ 6.098851] b43legacy-phy0: Broadcom 4306 WLAN found
[ 6.120545] b43legacy-phy0 debug: Found PHY: Analog 1, Type 2, Revision 1
[ 6.120574] b43legacy-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
[ 6.144519] b43legacy-phy0 debug: Radio initialized
[ 6.157428] phy0: Selected rate control algorithm 'simple'
[ 6.158087] b43legacy-phy0 debug: Ignoring unconnected 802.11 core
[ 6.192526] tg3.c:v3.86 (November 9, 2007)
[ 6.192564] ACPI: PCI Interrupt 0000:02:00.0[A] -> Link [LNKC] -> GSI 11 (level, low) -> IRQ 11
[ 6.280666] eth0: Tigon3 [partno(BCM95705A50) rev 3001 PHY(5705)] (PCI:33MHz:32-bit) 10/100/1000Base-T Ethernet 00:0d:56:e6:f8:50
[ 6.280681] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
[ 6.280685] eth0: dma_rwctrl[763f0000] dma_mask[64-bit]
[ 6.610381] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 7.308405] b43legacy-phy0 debug: Loading firmware version 0x127, patch level 14 (2005-04-18 02:36:27)
[ 7.431745] b43legacy-phy0 debug: Chip initialized
[ 7.432114] b43legacy-phy0 debug: 30-bit DMA initialized
[ 7.432232] b43legacy-phy0 debug: Wireless interface started
[ 7.432238] b43legacy-phy0 debug: Adding Interface type 2
[ 7.435297] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 21.128329] agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
[ 21.128365] agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
[ 21.128412] agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
[ 21.128461] [drm] Loading R200 Microcode
[ 21.243677] tg3: eth0: Link is up at 100 Mbps, full duplex.
[ 21.243691] tg3: eth0: Flow control is off for TX and off for RX.
[ 21.251335] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Thanks again for looking into this. I can't believe it's just me having this exact issue--most everyone else posting on this bug seems not to be able to resume at all--but let me know if this is just due to having kluge left over from the upgrade from Gutsy and a fresh install will solve it.

Revision history for this message
ddumanis (dave-davedumanis) wrote :

P.S. Same thing happens in -18 and -17--but not -16, where resume worked fine including wired and wireless networking.

Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 226279] Re: Kernel 2.6.24-17 - broken resume from suspend to RAM

ddumanis [2008-06-12 7:33 -0000]:
> Here's my dmesg output from when I resume from suspend and network-
> manager becomes useless, with no wired or wireless networks in the
> dropdown list (all in kernel -19):

Can you please give me the output of "ifconfig" and "ifconfig -a"
after resume? The dmesg log shows that the network devices are
detected properly.

Do you have an /etc/network/interfaces? If so, can you please attach
it?

Revision history for this message
Richard Coates (ihateemael) wrote :

I have just installed the "19" kernel from "Hardy proposed".
Initial testing on my Dell system has suspend working again. But now sound doesn't work....
...."No volume control GStreamer plugins and/or devices found"

Revision history for this message
Martin Pitt (pitti) wrote :

Richard Coates [2008-06-12 10:45 -0000]:
> I have just installed the "19" kernel from "Hardy proposed".
> Initial testing on my Dell system has suspend working again. But now sound doesn't work....
> ...."No volume control GStreamer plugins and/or devices found"

Just to make sure, did you upgrade linux-ubuntu-modules and
linux-restricted-modules to 2.6.24-19, too?

Revision history for this message
richardg1952 (richardg1952) wrote :

I tried upgrading the kernel, linbux-ubuntu-modules and linux-restricted-modules to 2.6.24-19 from hardy-proposed on my Dell D630. Suspend still takes around 45s to resume. I haven't tried resume enough times to confirm that it no longer fails to resume.

Revision history for this message
ddumanis (dave-davedumanis) wrote :

Here you go, Martin. ifconfig and ifconfig -a are below; /etc/network/interfaces is attached. (Laptop is a Dell D600 by the way.) Good luck and thanks.

$ ifconfig
lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:5829 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5829 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:235527 (230.0 KB) TX bytes:235527 (230.0 KB)

wlan0 Link encap:Ethernet HWaddr 00:90:4b:7b:27:6d
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wmaster0 Link encap:UNSPEC HWaddr 00-90-4B-7B-27-6D-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:0d:56:e6:f8:50
          BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:11

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:5829 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5829 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:235527 (230.0 KB) TX bytes:235527 (230.0 KB)

wlan0 Link encap:Ethernet HWaddr 00:90:4b:7b:27:6d
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wmaster0 Link encap:UNSPEC HWaddr 00-90-4B-7B-27-6D-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Revision history for this message
Richard Coates (ihateemael) wrote : Re: [Bug 226279] Re: Kernel 2.6.24-17 - broken resume from suspend to RAM
Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 226279] Re: Kernel 2.6.24-17 - broken resume from suspend to RAM

Hi ddumanis,

ddumanis [2008-06-12 17:21 -0000]:
> $ ifconfig
> ifconfig -a

Those look good, the interfaces are present. So this is mainly a
network-manager bug. You said this worked fine with -16? Can you
reboot into -16 to verify this? It might have been broken by another
update in hardy.

> ** Attachment added: "etc/network/interfaces file"

Nothing there, so they should all be handled by network-manager.

Revision history for this message
Yann (lostec) wrote :

@Richardg1952:

Look at your logs to see if you're not concerned by dhcp timeouts problems on network interface(s) if you've got them configured manually (or by a GUI != NM, using /etc/network/interfaces) and you're not using the first one.

If so, take a look at this:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/236066

Revision history for this message
ddumanis (dave-davedumanis) wrote :

Yes, -16 works fine--in fact, I'm using it as my main kernel! I edited grub/menu.lst to default to -16 since I can't get network joy from any kernel later than that.

So, if it is a bug in network-manager, it has to do with how network-manager interacts with the various kernels--as I get good wired and wireless networking after suspend with kernel -16.

Any further info/fixes much appreciated.

Revision history for this message
ddumanis (dave-davedumanis) wrote :

Purged and reinstalled network-manager and network-manager-gnome (?). Now all is well, suspend works great with kernel -19. THANK YOU to Martin for correctly pegging this as a network-manager issue.

Or, more likely, an upgrade issue, since network-manager wasn't properly upgrade when going from gutsy to hardy... but that's a different story.

Now unsubscribing from this bug.

Revision history for this message
Guido Jäkel (guido-jaekel) wrote :

As expected, 2.6.24-19 solves the issue and related artefacts for me, too.

Thank you, John for discovering the core reason at #96. Two missing statements, and we are lost in space ;)

Guido

Revision history for this message
Richard Elkins (texadactyl) wrote : Proposed Kernel 2.6.24-19 does not resume from suspend

Subject machine: iMac Core2Duo circa October 2007. The details are in the attachment machine.log:

   uname -a
   lspci -v
   lsmod
   lshw
   xorg.conf

Albert: My fgrlx driver is enabled. It works fine. It might be this driver that is not letting me see the display after resume. Its hard to tell when you are flying blind.

In a nutshell, -12 suspends/resumes correctly with this iMac and every kernel after that does not work with this iMac, including the proposed -19.
I have no idea what is going wrong but I am quite willing to be a guinea pig [(:].

-Richard

Revision history for this message
Richard Elkins (texadactyl) wrote : Proposed Kernel 2.6.24-19 was always fine. Driver fglxr was the issue.

Again, my current machine is an iMac Core2Duo circa October 2007.

I have resolved my suspend/resume issue thanks to the Hardy proposed -19 kernel, the EnvNG utility, and a web page (URL below).
For me, all 3 were necessary. Now, I can report that:

   -12 worked in the past (we all know that)
   -17 failed as reported by lots of folks
   -18 ditto
   -19 (proposed) fixes my iMac suspend/resume issues in -17 and -18

The kernel needed a cooperative video driver. Given that Intel-ish iMacs require the proprietary ATI driver (fglxr), there is no automatic way to know that your current driver will not work with newer kernels 100% (E.g. resume after suspend fails while everything else works). There are similar issues with nVidia.

Lesson learned:
1 - Run EnvyNG after every kernel upgrade *until* (hopefully) fglxr (or an equivalent) becomes part of the ubuntu family.
2 - Check ACPI configuration to see if a driver is stubborn and not letting go and force it to let go.

Packages needed envng-core, envng-gtk [or envng-qt]
Quote: "install the ATI or the NVIDIA driver EnvyNG is an application written in Python which will download the latest ATI or NVIDIA driver or the Legacy driver (for older cards) (according to the model of your card) from ATI or Nvidia's website and set it up for you handling dependencies (compilers, OpenGL,
etc.) which are required in order to build and use the driver."

ACPI configuration: I also needed the procedure at

   http://ubuntulinuxtipstricks.blogspot.com/2008/03/ati-nvidia-resume-good-news-bad-news.html

which, in a nutshell, contains a procedure to have ACPI to unload the ATI (fglxr) driver on suspend and reload on resume. Intel iMac users, do not set SAVE_VIDEO_PCI_STATE=true in /etc/default/acpi-support or you will probably be sorry [E.g. lock up].

One minor annoyance remains in ACPI. LOCK_SCREEN=false in /etc/default/acpi-support (or just commenting out the original LOCK_SCREEN=true) doesn't seem to work. It still locks the screen no matter what the LOCK_SCREEN condition is.

Sorry if I unnecessarily bothered any of the kernel folks. Our time is precious.

-Richard,
Dating myself: BSD 4.1 driver development on Vaxen 30 years ago just because it was fun

Revision history for this message
Richard Elkins (texadactyl) wrote : Solved my one minor annoyance too (LOCK_SCREEN=false in /etc/default/acpi-support)

I looked in the gnome-power-manager section of gconf-editor again and what did I find?
The lock screen boxes were now all checked.
I unchecked the box for Suspend and then tried manual suspend.

Problem solved.

But why oh why do we have "lock screen" settings at different levels? It was challenging enough with one place to find by googling.
History, I guess.

The desktop folks need a better human interface to take care of both the desktop level and the ACPI level in a single operation to ensure consistency.

-Richard

Revision history for this message
Pirouette Cacahuète (lissyx) wrote :

Finally got this 2.6.24-19, and it works for me !

Suspend/Resume is good.

Revision history for this message
Roberto Cássio Jr. (rcsdnj) wrote : Re: [Bug 226279] Re: Kernel 2.6.24-17 - broken resume from suspend to RAM

2.6.24-19 also fixes the Suspend/Resume regression for me. Thank you :)

On Tue, Jun 17, 2008 at 6:05 PM, Pirouette Cacahuète <email address hidden>
wrote:

> Finally got this 2.6.24-19, and it works for me !
>
> Suspend/Resume is good.
>
> --
> Kernel 2.6.24-17 - broken resume from suspend to RAM
> https://bugs.launchpad.net/bugs/226279
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Steve Langasek (vorlon) wrote :

Package is copied to hardy-updates. Thanks, all!

Changed in linux:
status: Fix Committed → Fix Released
Revision history for this message
Ohb01 (ohb01) wrote :

Unfortunately, 2.6.24-19 still does not work for me. Now what?

I applied all the available updates that came up in Update Manager today (including all the items related to kernel 2.6.24-19), rebooted, selected 2.6.24-19 kernel in GRUB, and logged into my user account in GNOME. Alas, I had no Wireless, as the system did not connect with my Atheros-based card.
I had to restart right away and go back to kernel 2.6.20-16, which is the last kernel that does both Wireless and Suspend/Hibernate (though the latter two are often very slow).

I would appreciate any suggestions on what to try next.

Revision history for this message
Ohb01 (ohb01) wrote :

Synaptic shows that I have installed linux-restricted-modules-2.6.24-19-generic (installed version 2.6.24.13-19.42 from Hardy-updates, which is the only one showing as available).

But if I restart with 2.6.24-19-generic, then:

I have no Wireless as mentioned above. Also, clicking on Network Monitor applet on the GNOME panel shows only "SIOCGIFFLAGS error: No such device".

And System > Administration > Hardware Drivers shows only

"Support for Atheros 802.11 wireless LAN cards. Enabled [v]. Status: Not in Use."

Not even listed in Hardware Drivers under 2.6.24-19-generic:

- "Atheros Hardware Access Layer (HAL)" (which is listed and shown as "In use" when I restart with kernel 2.6.20-16-generic)

- "ATI accelerated graphics driver" (which is listed when I restart with kernel 2.6.20-16-generic, though I choose not to use this driver as it prevents Suspend/Hibernate, which is a different story, I think.)

Revision history for this message
Ohb01 (ohb01) wrote :

Synaptic also shows that I have installed the following:

linux-image-2.6.24-19-generic (installed version 2.6.24-19.34 from Hardy-updates, which is the only one showing as available).

linux-ubuntu-modules-2.6.24-19-generic (installed version 2.6.24-19.28 from Hardy-proposed; also available but not installed: version 2.6.24-19.27 from Hardy-updates).

There are also two related Headers items installed, though I assume that they should not matter unless you are compiling anything, which I am not. Therefore, I am not bothering to list the details of these items here.

I would be happy to provide any additional info or try anything else that could fix this issue.

Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 226279] Re: Kernel 2.6.24-17 - broken resume from suspend to RAM

Ohb01 [2008-06-19 4:06 -0000]:
> I have no Wireless as mentioned above. Also, clicking on Network Monitor
> applet on the GNOME panel shows only "SIOCGIFFLAGS error: No such
> device".

Do you have the corresponding linux-ubuntu-modules and
linux-restricted-modules as well? Do you have "linux-generic"
installed? (That will pull in everything required)

Revision history for this message
Steve Langasek (vorlon) wrote :

Ohb01,

Can you please confirm whether it's 2.6.20-16, as opposed to 2.6.24-16, that you're using with success? 2.6.20-16 is a kernel from Ubuntu 7.04; this bug is about a suspend/resume regression introduced after the release of 8.04. If the only kernel you have working is the one from 7.04, then you should definitely open a new bug report since the issues are unlikely to be related.

Revision history for this message
Richard Coates (ihateemael) wrote : Re: [Bug 226279] Re: Kernel 2.6.24-17 - broken resume from suspend to RAM

I fixed wifi on an Acer laptop with madwifi drivers.
try madwifi.org and google your chipset.
its a bit of a convoluted process but it worked ok in the end.

Ohb01 wrote:
> Synaptic shows that I have installed linux-restricted-
> modules-2.6.24-19-generic (installed version 2.6.24.13-19.42 from Hardy-
> updates, which is the only one showing as available).
>
> But if I restart with 2.6.24-19-generic, then:
>
> I have no Wireless as mentioned above. Also, clicking on Network Monitor
> applet on the GNOME panel shows only "SIOCGIFFLAGS error: No such
> device".
>
> And System > Administration > Hardware Drivers shows only
>
> "Support for Atheros 802.11 wireless LAN cards. Enabled [v]. Status: Not
> in Use."
>
> Not even listed in Hardware Drivers under 2.6.24-19-generic:
>
> - "Atheros Hardware Access Layer (HAL)" (which is listed and shown as
> "In use" when I restart with kernel 2.6.20-16-generic)
>
> - "ATI accelerated graphics driver" (which is listed when I restart with
> kernel 2.6.20-16-generic, though I choose not to use this driver as it
> prevents Suspend/Hibernate, which is a different story, I think.)
>
>

Revision history for this message
Ohb01 (ohb01) wrote :

Steve Langasek, I confirm that I am forced to use 2.6.20-16 (I looked again: the last digit before the "-" is a 0, not a 4). All I know is that Suspend and Hibernate worked well in 7.10 (not just 7.04), but broke only after upgrading to Hardy. So if this is not a Hardy issue, then what is it?

I just went back through every kernel in the GRUB menu until I found the latest one that still mostly worked for me, which happened to be 2.6.20-16 (though it does have some issues, like auto-rebooting after resume from suspend and Switch User -- plus today, refusing to mount USB storage devices like standard 2 GB SD cards from a card reader).

I would like to ensure that this really is not a duplicate before opening another bug report. I don't even have 2.6.24-16 in my GRUB menu -- where would I get it so I can test it?

Revision history for this message
Ohb01 (ohb01) wrote :

Richard Coates, thanks for the tip. Having said this, I chose Ubuntu largely because I had hoped to avoid "googling my chipset" and other "convoluted processes" just to restore my network work after a kernel upgrade. I'm not a software engineer, just a home user hoping for a secure and stable alternative to Windows. I would be happy to try anything within reason, but I would really appreciate detailed, reproducible instructions. Thanks in advance for your help.

Revision history for this message
Richard Coates (ihateemael) wrote :

There is a detailed step by step howto on the ubuntu forum.
sorry I dont have the link its on my friends laptop.
thats why I suggested googling for ..ubuntu, wifi-chipset-name to bring
it up.

Ohb01 wrote:
> Richard Coates, thanks for the tip. Having said this, I chose Ubuntu
> largely because I had hoped to avoid "googling my chipset" and other
> "convoluted processes" just to restore my network work after a kernel
> upgrade. I'm not a software engineer, just a home user hoping for a
> secure and stable alternative to Windows. I would be happy to try
> anything within reason, but I would really appreciate detailed,
> reproducible instructions. Thanks in advance for your help.
>
>

Revision history for this message
Steve Langasek (vorlon) wrote :

Ohb01,

Thanks for your willingness to help get to the bottom of this problem!

The 2.6.24-16 kernel was the kernel included when Ubuntu 8.04 released. If you don't already have it installed, you should be able to install it from the command line using 'sudo apt-get install linux-image-2.6.24-16-generic linux-restricted-modules-2.6.24-16-generic', or by selecting the packages of the same names in synaptic (System -> Administration -> Synaptic Package Manager).

If 2.6.24-16 also doesn't work for you, then your problems are unrelated to this bug report. Actually, any problems you're experiencing with wireless are probably unrelated anyway, since this bug report is specifically about suspend/resume issues.

Revision history for this message
Martin Pitt (pitti) wrote : Re: [Bug 226279] Re: Kernel 2.6.24-17 - broken resume from suspend to RAM

For your interest, if suspend/resume does not work on your computer
with 2.6.24-19 (i. e. Hardy fully up to date), then you might try
finding a set of "quirks" which makes it work for you. I recommend
taking a look at
http://people.freedesktop.org/~hughsient/quirk/quirk-suspend-debug.html.

If you find a set of quirks, please open a bug against hal-info,
attach your lshal output, and the set of quirks you discovered.

Revision history for this message
Ohb01 (ohb01) wrote :

Steve Langasek,

Thanks for your detailed instructions. I installed linux-image-2.6.24-16-generic and linux-restricted-modules-2.6.24-16-generic. Wireless works, as does Resume from Suspend/Hibernate (and it's fast!), even wireless after resume works - reconnects to my wireless network within a minute.

BUT: No sound. (Speaker icon is crossed out in GNOME top panel; trying to open Volume Control, I get "No GStreamer plugin and/or devices found".) Also, still no mounting of SD card from USB-based card reader. And it detects my camera but then f-spot does nothing to actually download photos.

Now what?

Revision history for this message
Ohb01 (ohb01) wrote :

I've tried to fix the lack of Sound myself, following the "Comprehensive Sound Problem Solutions Guide" at http://ubuntuforums.org/showpost.php?p=1191847&postcount=1 , but the result was a messed-up GNOME (no Face Browser to select user at Login, and no way to fix this without editing /etc/gdm/gdm.conf manually. In addition, sudo nautilus has also stopped working. Details in my Forum post at http://ubuntuforums.org/showpost.php?p=5229702&postcount=11 . <sigh> <getting discouraged>

Revision history for this message
Steve Langasek (vorlon) wrote :

Ohb01,

I'm sorry, sound debugging questions are definitely out of scope for this bug report. It sounds like the forums are the right place to continue debugging this (in spite of some setbacks with GDM!).

Revision history for this message
Grazieno Pellegrino (grazieno) wrote :

Hi,

The suspend/resume problem continues in Intrepid.

Revision history for this message
Grazieno Pellegrino (grazieno) wrote :
Revision history for this message
Grazieno Pellegrino (grazieno) wrote :
Revision history for this message
Grazieno Pellegrino (grazieno) wrote :
Revision history for this message
Grazieno Pellegrino (grazieno) wrote :
Revision history for this message
Grazieno Pellegrino (grazieno) wrote :
Revision history for this message
Grazieno Pellegrino (grazieno) wrote :
Revision history for this message
dvo (mueller8) wrote : Kernel 2.6.24-* - broken resume from suspend to RAM

For Asus M2NPV-VM, nVidia GeForce 6150, I found the following solution - maybe it helps:
Simply update the BIOS (from revision 0504 to revision 1301) as recommended at
http://fixunix.com/kernel/337502-swsusp-amd-x2-64-2-6-24-regression.html

BTW, on that machine I still have problems with pm-utils, therefore I use acpi-support:
In /usr/lib/hal/scripts/linux/hal-system-power-hibernate-linux
replace /usr/sbin/pm-hibernate $QUIRKS
by /etc/acpi/hibernate.sh force
In /usr/lib/hal/scripts/linux/hal-system-power-suspend-linux
replace /usr/sbin/pm-suspend $QUIRKS
by /etc/acpi/sleep.sh force

I use these settings in /etc/defaul/acpi-support:
ACPI_SLEEP=true
ACPI_SLEEP_MODE=mem
SAVE_VBE_STATE=false
POST_VIDEO=false
SAVE_VIDEO_PCI_STATE=true
USE_DPMS=false

Revision history for this message
Radu Cristian Fotescu (beranger) wrote :

This bug is officially also acts in the name of bug #226279. What to do when this bug is officially fixed, but MY BUG #226279 is still a bug for me! The kernel that's said to fix bug #226279 does NOT fix bug #221213, which is the situation reported by me!

So: as long as bug #221213 is concerned, and for my Acer, Hardy is broken, only Gutsy and Intrepid have working kernels.

HOW CAN THIS BUG REPORT READ "FIX RELEASED" WHEN NOT ALL OF ITS 15 "DUPLICATES" ARE CONFIRMED TO BE FIXED TOO?

(Sorry for shouting, but the policy of marking bugs as "duplicates" is too lax.)

ArheoN (arheon)
Changed in linux:
status: Invalid → Confirmed
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi All,

I'm closing the Intrepid nomination because there has been no reference that this is an issue with the 2.6.27 Intrepid kernel. This bug should have been resolved in Hardy. If this is not the case for you please open a new report. Additionally, if your bug was marked a duplicate of this report and your bug is not yet resolved, please undup your bug from this one.

Another thing to note about suspend/resume issues is that even though you may be experiencing the same symptom as everyone else, it really is usually hardware specific. For that reason, it's helpful that when subscribing to existing bug reports, or marking bugs as a duplicate of another, you should make sure you have the same hardware as the original bug reporter. If this is not the case it is best to open a new bug report (or not mark a bug as a duplicate). Otherwise bug reports become bloated and hard to follow with subscribers reporting against multiple pieces of hardware which are likely running different drivers and will be requiring different fixes. Thanks again for your cooperation, we really appreciate it.

Changed in linux:
status: Confirmed → Invalid
To post a comment you must log in.