[Fujitsu T4220] suspend only works once

Bug #206952 reported by Ryan Campbell
128
This bug affects 19 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned
Declined for Hardy by Sebastien Bacher
Declined for Intrepid by Sebastien Bacher
Declined for Karmic by Sebastien Bacher
Declined for Lucid by Sebastien Bacher
Declined for Maverick by Sebastien Bacher

Bug Description

I have a Fujitsu T4220 and in both gutsy and hardy I am able to suspend and resume fine the first time I attempt it, but after that It wont go into suspend again until I reboot. The screen blanks and it looks like it is going into suspend then resumes automatically.

I followed the Debugging section in https://wiki.ubuntu.com/UnderstandingSuspend and running '/etc/acpi/sleep.sh force' as root gives the following error:

/etc/acpi/sleep.sh: line 39: echo: write error: Resource temporarily unavailable

Line 39 is "echo -n $ACPI_SLEEP_MODE >/sys/power/state"

So, I checked out /sys/power/state

root@tablet:~# cat /sys/power/state
mem disk

but running 'echo mem >/sys/power/state' give the above error again and just freezes the computer for a few seconds.

 Also, running sleep.sh with /sys/power/pm_trace enabled doesnt give any 'hash matches' output in dmesg.

Revision history for this message
Ryan Campbell (rcampbell) wrote :

# uname -a
Linux tablet 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 GNU/Linux

Revision history for this message
Ryan Campbell (rcampbell) wrote :
Revision history for this message
Ryan Campbell (rcampbell) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Ryan,

Care to recapture your dmesg output immediately after your first suspend/resume cycle? Also, the dmesg you have currently attached has some interesting stack traces. It would be nice to capture the very first stack trace that gets dumped. Thanks.

Changed in linux:
status: New → Incomplete
Revision history for this message
Ryan Campbell (rcampbell) wrote :

OK, here's the dmesg output after the first suspend/resume cycle (running the command "sync; echo 1 > /sys/power/pm_trace; /etc/acpi/sleep.sh force
). I will attach the output after the second cycle as well.

Revision history for this message
Ryan Campbell (rcampbell) wrote :
Revision history for this message
Ryan Campbell (rcampbell) wrote :

Leann,

you mentioned that it would be nice to capture the very first stack trace that gets dumped. How would I go about doing that?
Thanks.

Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: Incomplete → Triaged
Revision history for this message
peddy (peddy22) wrote :

same problem here. Running 64-bit Gutsy with Nvidia Restricted drivers installed.

Any progress?

Revision history for this message
Laszlo Kupcsik (koopac) wrote :

Same problem on a Compaq nc6320, Ubuntu 8.04 RC1.
I also see a console message (the second time) saying something like Freezing of tasks failed after 20 seconds. The task it mentions is khubd. Accordingly, it is not possible to attach a new USB storage device, like flash drive, to the computer.

I attach two files. messages1.gz is /var/log/messages after reboot and suspend once. messages2.gz is the same after second reboot.

Revision history for this message
Laszlo Kupcsik (koopac) wrote :

Same problem on a Compaq nc6320, Ubuntu 8.04 RC1.
I also see a console message (the second time) saying something like Freezing of tasks failed after 20 seconds. The task it mentions is khubd. Accordingly, it is not possible to attach a new USB storage device, like flash drive, to the computer.

I attach two files. messages1.gz is /var/log/messages after reboot and suspend once. messages2.gz is the same after second suspend.

Revision history for this message
Georg Sauthoff (g-sauthoff) wrote :

same problem at Thinkpad r40-2722 with Hardy and

$ uname -a
Linux tp.private 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux

After failed suspend lsusb hangs forever.

Revision history for this message
fiskadoro (frank-joerdens) wrote :

same here:

Compaq Presario C700 with Hardy

frank@marvin:~$ uname -a
Linux marvin 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux

Revision history for this message
baekster (john-kh-baek) wrote :

same here:

Compaq/hp nc6320
Hardy

/var/log# uname -a
Linux hatchet 2.6.24-16-generic #1 SMP Thu Apr 10 12:47:45 UTC 2008 x86_64 GNU/Linux

Also
/var/log# cat pm-suspend.log
...
/usr/lib/pm-utils/functions: line 143: echo: write error: Resource temporarily unavailable
...

On line 143, there's a test function that checks whether /dev/pmu exists inside line 143:
[ -e /dev/pmu ] && /usr/lib/hal/hal-system-power-pmu sleep || echo -n "mem" > /sys/power/state

The entire function:

do_suspend()
{
        if [ -x /usr/sbin/s2ram ]; then
                if [ -n "$S2RAM_OPTS" ]; then
                        # Trust HAL or the user to pass the correct options
                        /usr/sbin/s2ram $S2RAM_OPTS
                elif /usr/sbin/s2ram --test > /dev/null ; then
                        # Trust s2ram's internal whitelist
                        /usr/sbin/s2ram
                else
                        # Unknown machine
                        echo "This machine is unkown, please try to find out how to suspend this machine. See s2ram(8)."
                fi
        else
                [ -e /dev/pmu ] && /usr/lib/hal/hal-system-power-pmu sleep || echo -n "mem" > /sys/power/state
        fi
}

Revision history for this message
baekster (john-kh-baek) wrote :

Sorry, forgot to add that /devpmu is gone after the first suspend.

Revision history for this message
baekster (john-kh-baek) wrote :

attached are the following:

dmesg after first suspend/resume
kern.log after 2nd suspend/resume (2nd time fails)
syslog after 2nd suspend/resume (2nd time fails)

Revision history for this message
André Carezia (carezia) wrote :

I have a Dell Latitude D510 and Ubuntu 8.04.

Suspend fails as described by OP (resource unavailable on writing to /sys/power/state) when I forget a rsync running to my server. When it happens, I just kill rsync and suspend is back to normal.

Revision history for this message
Dominic Buchstaller (dbuchstaller) wrote :

I have an Advent 4211 / MSI WIND

Same problem here - suspend to ram works exactly one time. Is there still activity on this one? (last post from 29.05)

Revision history for this message
sampattuzzi (sam-pattuzzi) wrote :

I am also affected by this bug on an Advent 4211.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
baekster (john-kh-baek) wrote :

I will be willing to test the new kernel (as long as it's a legitimate release and it's not going to rootkit my system), and I am comfortable. I recently was able to resolve this issue in Hardy Heron Linux kernel 2.6.24-19-generic by removing/restoring USB modules and wireless modules (I am not sure if removing/restoring wireless is necessary).

$> echo SUSPEND_MODULES=\"ehci_hcd uhci_hcd usbcore iwl3945\" >> /etc/pm/config.d/usb_suspend_workaround

Revision history for this message
nola mike (abatzis) wrote :

2.6.27 kernel (otherwise hardy), compaq c770, problem still present.

Revision history for this message
Dominic Buchstaller (dbuchstaller) wrote :

An least on the advent 4211/Msi Wind the solution was to set the right power management parameters for the HD.

see: http://forums.msiwind.net/default-msiwind/suspend-and-hibernate-working-with-sound-ubuntu-t1982.html

The connection with suspend is somewhat bizarre but it works.

Revision history for this message
Jason Smith (jassmith) wrote :

I have this behavior on a thinkpad T500 as well. Suspend only works right. Tried the power management thing from above with no effect.

Revision history for this message
Jason Smith (jassmith) wrote :

I meant to say "Suspend only works right once". Sorry, it's early.

Revision history for this message
baekster (john-kh-baek) wrote :

On my machine, it was the USB module problem. I noticed a kernel stack dump after first suspend that was referring to the USB subsystem modules.

Disabling the modules "ehci_hcd", "uhci_hcd", and "usbcore" make suspend to work

echo SUSPEND_MODULES=\"ehci_hcd uhci_hcd usbcore\" >> /etc/pm/config.d/usb_suspend_workaround

I have been able to suspend (I don't usually hibernate) fine since then.

I have HP Compaq nc6320

uname -a
Linux hatchet 2.6.24-19-generic #1 SMP Wed Aug 20 17:53:40 UTC 2008 x86_64 GNU/Linux

Ubuntu Hardy Heron

Revision history for this message
Jason Smith (jassmith) wrote :

Tried the above mentioned fix without success

Revision history for this message
nola mike (abatzis) wrote :

neither the updated kernel, nor power management, nor usb driver unloads is working for me.

Revision history for this message
peptide (nerd-nerd) wrote :

I have a Dell D620. This happens to me as well. I workaround-ed it by add the following into /etc/default/acpi-support

MODULES="ehci_hcd uhci_hcd usbcore iwl3945"

Don't know why put them under /etc/pm/config.d doesn't work.

Revision history for this message
nola mike (abatzis) wrote :

still no luck for me. i have ath5k for a wifi driver on the .27 kernel, and tried the above with/without unloading ath5k (didn't include iwl3945).

Revision history for this message
George Halkias (admin-dionic) wrote :

This works for me!!
MODULES="ehci_hcd uhci_hcd usbcore iwl3945"

Dell D430

Revision history for this message
Dmitri Medvedev (dmitri-medvedev) wrote :

On my thinkpad t61 running kernel 2.6.24-19
this behavior seems to be caused by suspending the laptop while in the docking station.
If laptop is booted up and never docked, and no USB devices are plugged in
this doesn't happen.

Steps to reproduce:
Boot up
Dock
Suspend -- works fine
Undock
Wake it up
At this point suspend never works again unless you reboot the laptop.

The reason is the khubd is having some issues: it's waking up a lot, according
to powertop, and lsusb hangs forever.

My guess is that since suspend was done while t61 was docked in a station with
USB keyboard and mouse, khubd is in a bad state, and after it's awaken it
never recovers, thinking there are some non-existing USB devices that it keeps polling.
At this point khubd prevents either suspend or hibernate from working.

Revision history for this message
Martin G Miller (mgmiller) wrote :

I have a 32 bit clean install of 8.10 rc1 that has updated itself to current with an ATI 9600 GPU running the stock open source driver.

Suspend/resume worked perfectly for me from day one with this machine until some recent updates. Now it suspends and resumes once per session. On the 2nd suspend attempt, I get a black screen with a blinking cursor near the upper left corner of the screen. There is no further response to keyboard or mouse. I Have to hit the reset button on the tower to reboot the machine.

If it's a clue, on the one successful suspend cycle per boot, the screen turns black with the cursor near the upper left corner for a few seconds. I then hear a faint "pop-pop" sound from the speakers, the cursor moves up 2 lines to the top left corner and then the machine goes into S3 sleep.

On the unsuccessful attempts, the cursor never moves up and there is no "pop-pop" sound.

Hibernate still works reliably, but I would prefer to use standby(suspend) on this machine.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Justin Newman (eqisow) wrote : Re: suspend only works once

I'm running Ubuntu minimal (Intrepid) as a stand alone xbmc box. Like everybody else, I get one successful suspend every reboot. On the second suspend the screen goes blank like it's going to suspend, but then immediately comes back. pm-suspend.log shows no error messages, but also shows no log for the second suspend attempt.

Adding the USB modules to /etc/default/acpi-support didn't help. Adding the lirc modules, on a hunch, just made the remote not work after suspend.

I should note that I have my own suspend/resume script for networking and lirc, but was having this issue before those were added.

Revision history for this message
Khaless (khaless) wrote :

I'm facing this as well on Karmic.

Interestingly, if I disable my USB 2.0 controller in BIOS everything works fine and I can suspend/resume more than once.

Revision history for this message
nola mike (abatzis) wrote :

@khaless: what model are you using? i don't have that (or really anything else) as an option in my bios, c700 series.

Revision history for this message
Hans van den Bogert (hbogert) wrote :

what hardware khaless? in particular hdd and graphics card?

Revision history for this message
Khaless (khaless) wrote :

@digandalf & nola: I'm running an Asus M3N78-EM Motherboard, this board has a built in GeForce 8200

My hdd is a 64gb Kindstong SSDNow V Series:
[ 1.376785] ata2.00: ATA-7: Kingston SSDNow V Series 64GB, B090522a, max UDMA/133

For more info, my dmesg is attached.

Revision history for this message
CutDaMuzik (samsharonizadeh) wrote :

Hello everyone,

Same issue with Asus M4N78 SE motherboard. I tried to disable 2.0 controller in BIOS, but it does not change anything...
I know it's not an hardware issue since I did trials on Windows and multiple resume is working...

Did anyone find a solution to this 2 years old bug ?

Revision history for this message
hansvschoot (hansvschoot) wrote :

Hi all,

Same issue here, but with some strange side-effects. i'm running karmic 64bit in an ION board (XBMC on top of a normal install). the OS is on a USB flash disk (16gb corsair flash foyager GT). with no additional hardware attached i only get one suspend per session, but plugging in a USB (optical) mouse on some of the USB ports fixes this. (with the mouse attached i can suspend as many times as i like. also just plugging it in and taking it out gives one additional suspend).
Only problem i have left is awaking the bluetooth usb dongle after a long suspend (it wakes up if i resume the machine within a couple of minutes, but doesn't awake after a long suspend (more than an hour). I'm going to play around a bit with the USB modules in acpi-support next week.

if i can help by providing system info, please tell me what commands to run and/or logfiles to submit ;-)

Revision history for this message
Romano Giannetti (romano-giannetti) wrote :

Similar thing happens to me. Normally suspend and resume works perfectly, but once in a while it resumes alone just after suspend, and after that trying to suspend locks the machine hard. I do not know if it's a coincidence, but locks occurs only when I have the ethernet cable plugged in. Never happened with Linus vanilla kernels, but could be another coincidence too. Nothing special in dmesg or in logs.

Toshiba Satellite U305-S5077, intel graphic chipset, Ubuntu karmic up-to-date, on-board eth0 RTL8101e (r8169 driver), ath5k wireless driver.

Revision history for this message
CutDaMuzik (samsharonizadeh) wrote :

Hello,

hansvschoot : plugging out and plugging in the usb mouse before asking for suspend to ram works for me too !
Using this trick I can go to suspend and resume as much as I want !
I'm sure a workaround can be done by creating a script disabling usb & enabling it back before going to sleep...
If anyone as an idea on how to do that...

Revision history for this message
hansvschoot (hansvschoot) wrote :

CutDaMuzik: nice to hear i'm not the only one with this strange behavior. what kind of hardware are you running? have you tried your usb mouse on another usb port? i get multiple suspends if the mouse is connected on some of the usb ports, but not if its connected to the others. (the plugging out&in trick works on all ports here, but can be avoided by finding the right usb port)
This problem happens to me on an Zotac ION board, nvidia chipset. i should also mention that i'm running the karmic installation from a USB drive. (not a live usb stick, but a normal installation)
I can do the scripting, but i don't know how and/or what usb modules to load/unload...

Revision history for this message
andrew1056 (andrew-oke) wrote :

I can also confirm this on a Zotac ION board.

I have no USB devices plugged in (HTPC). The only things are network and a serial cable to control the TV.

Using 64 bit lucid.

Going to try disabling the usb in bios and see if that works.

If you need any logs let me know.

Revision history for this message
jcarvalho (joaomcarvalho) wrote :

Same problem on Lucid with a fresh install on Asus 1201N. I found a forum that suggested the addition of he "usbcore.autosuspend=-1" to grub. In fact it works if I had that option.

Revision history for this message
Steve Farthing (s-farthing) wrote :

Same problem on Lucid. Completely disabling USB support in the BIOS does not fix it so must not be USB-related for me. I've also tried to suspend-resume on several other machines and not one can suspend resume properly although not necessarily this scenario. But suspend-resume in general seems to be a fairly problematic area.

Revision history for this message
timosha (timosha) wrote :

I have this bug now in Ubuntu 10.04 (Lucid) on my Thinkpad R51 since a so called "update" this week. After a reboot/login suspend works once. The next suspend doesn't work, the "moon" led keeps blinking and on only a power off/power on cycle can bring the R51 back to life.

I am getting a bit tired of this Ubuntu cycle of "works-broken-works-broken-works-broken". Is it so difficult to fix a bug once and for all?

In German there is a very nice word for this: "verschlimmbesseren" - Improvements (so called updates) brings the old bugs back.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Steve / timosha / others seemingly affected by this,

   Please file new bugs for your issues. I'd like for us to try to solve the original reporter's issue over any 'me too but different' comments that have a way of muddling the issue.

Thanks!

~JFo

Revision history for this message
timosha (timosha) wrote :

For me it is solved since I removed the so called updates in Lucid.

Revision history for this message
Steve Farthing (s-farthing) wrote :

This bug is now fixed for me with the following Kernel!

-Version-
Kernel : Linux 2.6.32-24-generic (i686)
Compiled : #40~pre201008060902-Ubuntu SMP Fri Aug 6 09:27:20 UTC 2010
C Library : GNU C Library version 2.11.1 (stable)
Default C Compiler : GNU C Compiler version 4.4.3 (Ubuntu 4.4.3-4ubuntu5)
Distribution : Linux Mint 9 Isadora
-Current Session-
Computer Name : mint-desktop
User Name : user (user)
Home Directory : /home/user
Desktop Environment : GNOME 2.30.2
-Misc-
Uptime : 10 minutes
Load Average : 2.47, 2.13, 1.04

Revision history for this message
Ryan Campbell (rcampbell) wrote :

I'm the original submitter, and after upgrading to Maverick suspend seems to finally work reliably on my system, at least.

Revision history for this message
Andreas Nilsson (andrnils) wrote :

Once in a while I see this bug on my Lenovo T510 laptop. Output from dmesg after first failed suspend attempt is attached.

Os is Ubuntu 10.10 amd64

Revision history for this message
FAJALOU (fajalou) wrote :

Same things as Andreas Nilsson. This used to work fine; every once and a while it would be weird, but it would always eventually suspend. Now I am not able to suspend a second time on a reboot. The first time works just fine. I will attempt to update a dmesg output after a successful and non-successful suspend.

Revision history for this message
FAJALOU (fajalou) wrote :

Here is a successful suspend, and a failed suspend.
I think I have narrowed the issue down to chromium-browser. Should I start a new thread?

Revision history for this message
hansvschoot (hansvschoot) wrote :

a new thread would be a wise thing to do, since this one isn't very active anymore. 10.10 fixed the single suspend bug for me and many others, so yours might not be related (also, i don't have chromium-browser)

Revision history for this message
Christophe Narbonne (christophe31) wrote :

I have this behaviour since 2 weeks (or more) on my HP dm1-1010EF.

I don't see previouslt mentioned usb modules in `lsmod` so I don't really know what to do.

Revision history for this message
vojtec (vojtec) wrote :

Same problem in Ubuntu 11.10 at Lenovo ThinkPad X200s laptop. This issue was also problem in 11.04, afterwards it was fixed, but in 11.10, second suspend again is not working.

uname -a
Linux vojtec-laptop 2.6.38-11-generic-pae #50-Ubuntu SMP Mon Sep 12 22:21:04 UTC 2011 i686 i686 i386 GNU/Linux

Revision history for this message
booble (yashin-vladimir) wrote :

I had the same problem on Lenovo Thinkpad Edge E320 on Ubuntu 12.04.
Nothing helped (module unloading).

But today I tried a new kernel (3.4.0-rc4) and it helped! My laptop had suspended/resumed multiple times in a row.
Try it: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc4-precise/ (download and install with dpkg -i)

Revision history for this message
daniel_L (daniel-das-grauen) wrote :

This problem just hit me with 12.04. With 10.04 I had no problems (at least I do not remember if I applied some workarounds 2 years ago). When trying to suspend my laptop the second time, the monitor just goes black (but is still on - the backlight won't go off) and then nothing happens. Only a cold restart makes the laptop usable again. Total showstopper.

Revision history for this message
FelipeC (fncaldas) wrote :

I'm having the same problem reported by daniel_L with 12.04 on a Toshiba Tecra A7. I had this problem in 11.10 but can't sleep in the second try. Now the system hangs with the monitor on, turn the cpu fan off and becomes unresponsive. I tried to find some erros in logs but didn't find nothing. I tested without any network or usb device connected.

The syslog just stops in line:

Jul 9 21:37:13 chapinha NetworkManager[749]: <info> sleep requested (sleeping: no enabled: no)
Jul 9 21:37:13 chapinha NetworkManager[749]: <info> sleeping or disabling...
Jul 9 21:37:14 chapinha anacron[2984]: Anacron 2.3 started on 2012-07-09
Jul 9 21:37:14 chapinha anacron[2984]: Normal exit (0 jobs run)

In the first sleep the next line is:

Jul 9 21:36:51 chapinha kernel: [ 1030.979341] PM: Syncing filesystems ... done.

And so on.

The pm_suspend.log is same for the both tries.

uname -a
Linux chapinha 3.2.0-26-generic-pae #41-Ubuntu SMP Thu Jun 14 16:45:14 UTC 2012 i686 i686 i386 GNU/Linux

Revision history for this message
truant (launchpad-ninj4) wrote :

OK, I think I have this bug although there are several similar bug reports here and there. Turning on/off bluetooth has no effect for me, neither does anything else. No logs show any errors or anything suspicious. Toshiba Satellite L830-114.

Latest mainline kernel build - 3.5.rc7-quantal - does not resolve it for me, but the daily build (as of 28 july) does. I can suspend/resume on demand, as many times as I like. Yay!

uname -a
Linux izumi 3.5.0-999-generic #201207280406 SMP Sat Jul 28 08:07:29 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2012-07-28-quantal/

Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Can you tell us if you still have problems please? Thank you!

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Laszlo Kupcsik (koopac) wrote : Re: [Bug 206952] Re: suspend only works once

I'm not affected by this bug anymore, because I went back to Debian :)

Revision history for this message
Mikael Niku (mikael-niku) wrote : Re: suspend only works once

I'm experiencing a somewhat similar problem on Samsung NF210 netbook (Ubuntu 12.04). Suspend works perfectly from the menu, but works only EVERY SECOND TIME by lid close. It works the first time after boot (OR after suspend from the menu), but doesn't if I try to suspend again. And then it again works. When it doesn't, screen goes off but nothing else happens. Viewing the syslog seems that it doesn't even try to suspend.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Lukas Bunsen (lukasbunsen) wrote :

I still have the problem, I am using Ubuntu 12.10.
uname -a : 3.5.0-24-generic #37-Ubuntu SMP Thu Feb 7 01:50:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message
Steve Farthing (s-farthing) wrote :

I still have this problem on a Toshiba L755 laptop. I have had it on other laptops. This problem has persisted for years. now on numerous devices. The ability to suspend is an important feature on portable devices. Yet another reason Linux is a poor fit for such devices.

Changed in linux (Ubuntu):
status: Expired → Confirmed
tags: added: gutsy hardy needs-kernel-logs needs-upstream-testing
summary: - suspend only works once
+ [Fujitsu T4220] suspend only works once
Revision history for this message
Christopher M. Peñalver (penalvch) wrote :

Ryan Campbell, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers