[Bug 128315] Re: Resume immediately after Suspend due to some WAKE event
This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/128315 Title: Resume immediately after Suspend due to some WAKE event To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/128315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128315] Re: Resume immediately after Suspend due to some WAKE event
** Changed in: linux (Ubuntu) Assignee: TJ (intuitivenipple) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/128315 Title: Resume immediately after Suspend due to some WAKE event -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128315] Re: Resume immediately after Suspend due to some WAKE event
I can confirm this also occurs in Jaunty with the 2.6.28-15-generic kernel on an HP Mini 311 netbook. This also appears similar to Bug #289252: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/289252 -- Resume immediately after Suspend due to some WAKE event https://bugs.launchpad.net/bugs/128315 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128315] Re: Resume immediately after Suspend due to some WAKE event
After reading a lot of comments on this 'bug', I found a way to fix it. Suspend started working after changing the USB from +5V to +5VSB. I do get a message about half the times that 1 application refused to freeze: Plasma. After the suspend attempt, I have to kill plasma and restart it. If I try suspending again it works most of the time. But this seems like an unrelated bug. Hibernation started working more or less after the USB trick as well. At least the machine did shut down instead of rebooting. But on wakeup I got no video. Reading some tips from the tuxonice website I got this fixed as well by changing from AGPGART (intel_agp) to NvAGP. Now both suspend and hibernate work. I do wonder why, if this is apparently a known issue, why ubuntu defaults to agpgart even when an nvidia card is installed. I think it would be way more userfriendly to switch to NvAGP when an nvidia card is detected. But I am not sure how this relates to the current bug, should this be reported separately/elsewhere? -- Resume immediately after Suspend due to some WAKE event https://bugs.launchpad.net/bugs/128315 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128315] Re: Resume immediately after Suspend due to some WAKE event
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-source-2.6.22 (Ubuntu) Assignee: Ubuntu Kernel ACPI Team (ubuntu-kernel-acpi) => (unassigned) Status: In Progress => Won't Fix ** Changed in: linux-source-2.6.20 (Ubuntu) Assignee: Ubuntu Kernel ACPI Team (ubuntu-kernel-acpi) => (unassigned) -- Resume immediately after Suspend due to some WAKE event https://bugs.launchpad.net/bugs/128315 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128315] Re: Resume immediately after Suspend due to some WAKE event
This issue is still evident with kernel 2.6.28-9. I'm revisiting it although it very much appears this could be due to a confluence of unique circumstances on particular hardware. The only reports I can identify seem to be with various Sony Vaio laptops/notebooks of differing ages and hardware. One was found to be a "...pcmcia express card reader disconnecting itself after suspend and thus triggering the wakeup". http://marc.info/?l=linux-acpi&m=118250426218485&w=2 I've used up all the user-space options for disabling wakeup events through /sys/devices/*/wakeup without solving it. What is interesting is it affects Windows XP too. It doesn't seem to affect all models since it doesn't affect an identical Vaio. I re-discovered an email I sent in 2007 in response to David Brownell on the linux-acpi mailing list: http://marc.info/?l=linux-acpi&m=118539846819353&w=2 "I'm not sure if this might inform your thinking here but today I've just tracked down a similar issue on another Sony Vaio (PCG-SRX51) where S3 STR immediately wakes. I enabled ACPI_FUTURE_USAGE and called acpi_get_event_status() immediately upon resume (before the wake flag is cleared) and iterated each wake event. I discovered that the PM timer event is the reason the system resumes but so far haven't discovered why. I have a tenuous theory it could be related to the kernel timer using the ACPI PM Timer. I tried disabling that with the boot parameter 'nopmtimer' but that didn't help. To test this I'm currently building a kernel that disables the PM Timer wake event during suspend and re-enables it on resume, something the ACPI specification hints at in section 4.7.2.1. I'm not sure if this problem occurs on a wider range of systems than the Sony since at present, without a debug kernel with ACPI_FUTURE_USAGE and specific additional checks, there is no way to know the reason a system resumed." ** Changed in: linux (Ubuntu) Importance: Undecided => Low Assignee: (unassigned) => TJ (intuitivenipple) Status: New => Confirmed -- Resume immediately after Suspend due to some WAKE event https://bugs.launchpad.net/bugs/128315 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128315] Re: Resume immediately after Suspend due to some WAKE event
it works for my M2N-1394 (M2N 1394, I write it like this, so the search engines can spot it for requests writting the name like this... there are very few post with this card). Bios is 0902. I also add the problem of the black screen, with the video not waking up. This was solve after installing the NVidia drivers. (using Fedora 10). Thanks a lot ! (long time looking around and configuring to have this work...) -- Resume immediately after Suspend due to some WAKE event https://bugs.launchpad.net/bugs/128315 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128315] Re: Resume immediately after Suspend due to some WAKE event
Thanks a lot chriskyman; the+5VSB trick also worked for my M2NPV-VM (BIOS version 1301). -- Resume immediately after Suspend due to some WAKE event https://bugs.launchpad.net/bugs/128315 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128315] Re: Resume immediately after Suspend due to some WAKE event
I can confirm this with 2.6.27 Intrepid Ibex 8.10 kernel on a Asus M2N4-SLI but can offer some help. After deciding it was USB hubs causing the problem I found this post; http://www.gossamer-threads.com/lists/mythtv/users/316830 and now have working suspend/hibernate. Basically, there are a bunch of jumpers on my motherboard to control USB wake-up behavior. Setting them to +5VSB (wake from S3 and S4) instead of +5V (wake from S1) gives me working suspend without the instant wake-up problem. It was great to quickly fix a fault by opening the case and moving a few jumpers after spending hours tinkering with such-and-such.sh Not sure if this could be considered purely a hardware related problem but it surely highlights a conflict between a particular motherboard configuration and the OS's handling of it. -- Resume immediately after Suspend due to some WAKE event https://bugs.launchpad.net/bugs/128315 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128315] Re: Resume immediately after Suspend due to some WAKE event
I can confirm the same behaviour but not on the same hardware. I'm running on a Asus P4P800 SE motherboard with Intel 865 PE chipset. I'm using the nvidia drivers for a GF 6800 Ultra. I tried both intel_agp/agpgart and NvAGP, both show the same problem. -- Resume immediately after Suspend due to some WAKE event https://bugs.launchpad.net/bugs/128315 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128315] Re: Resume immediately after Suspend due to some WAKE event
The 18 month support period for Feisty Fawn 6.10 has reached it's end of life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . As a result, we are closing the linux-source-2.6.20 kernel task. However, this will remain open against the actively developed kernel. If someone could confirm this with the 2.6.27 Intrepid Ibex 8.10 kernel that would be great. Thanks. ** Changed in: linux-source-2.6.20 (Ubuntu) Status: In Progress => Won't Fix -- Resume immediately after Suspend due to some WAKE event https://bugs.launchpad.net/bugs/128315 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128315] Re: Resume immediately after Suspend due to some WAKE event
I have a PCG SRX51P/B. I tried installing Gutsy on it a few days ago and that was a disaster -- it booted and worked except that the Xorg system refused to work in any thing other than 800x600 mode (cf. Bug#141646 and Bug #157077). I therefore reinstalled Feisty from my original install discs and network upgrades and it works fine. Before the attempt to use Gutsy, suspend simply failed for me on this machine (cf. Bug #135233) however since the complete reinstall suspend now works fine. I have no idea why, but I am now not unhappy. -- Resume immediately after Suspend due to some WAKE event https://bugs.launchpad.net/bugs/128315 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128315] Re: Resume immediately after Suspend due to some WAKE event
** Attachment added: "side-by-side diff (SRX41P, SRX51P) of dmesg" http://launchpadlibrarian.net/8732204/dmesg.diff.txt -- Resume immediately after Suspend due to some WAKE event https://bugs.launchpad.net/bugs/128315 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128315] Re: Resume immediately after Suspend due to some WAKE event
** Attachment added: "side-by-side diff (SRX41P, SRX51P) of suspend/resume" http://launchpadlibrarian.net/8732203/suspend.diff.txt -- Resume immediately after Suspend due to some WAKE event https://bugs.launchpad.net/bugs/128315 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128315] Re: Resume immediately after Suspend due to some WAKE event
** Summary changed: - Resume immediately after Suspend due to ACPI PM Timer event + Resume immediately after Suspend due to some WAKE event ** Description changed: - When suspending the PC resumes immediately. + When suspending (S3) the PC resumes immediately. - Using a custom-built debugging kernel reveals that the ACPI Power - Management Timer has generated a wake-up event. + This occurs on a Sony PCG-SRC51P with a fresh install of Feisty. It also + affects Gutsy up to and beyond tribe-3 at least (all 32-bit). - Investigation of this issue is ongoing. + On an identical model (SRX41P) the problem doesn't occur. Have tried + swapping the hard disks and memory modules between the two but the + problem persists on the SRX51P. + + Both models have identical hardware but the SRX51P CPU is 50MHz faster, + and it has 128MB more RAM (SRX41P = Intel P-III 800Mhz 256MB RAM, SRX51P + = Intel P-III 850MHz 384MB RAM). + + Using a custom-built debugging kernel reveals that some device has + generated a WAKE-UP event. + + Running a diff against the hardware profiles from lshal shows both + models are identical. Running diffs on their dmesg confirms this. + + A diff of the kern.log over a suspend/resume cycle is also identical. + + The additional debug-message reporting I added into hwsleep() and + acpi_pm_enter() show identical activity in both. Unfortunately, even + with ACPI_FUTURE_USAGE enabled reading the WAKE event on resume always + reports it as PM_TIMER, even on the 'good' PC so the wake-event code + doesn't appear reliable. + + When I thought PM_TIMER was correct I added code to disable the PM_TIMER + wake event just prior to suspend, and re-enabled it upon resume. That is + the reason for the debug messages below. + + Here's the output to kern.log from my debug code starting in hwsleep() + and continuing in acpi_pm_enter() on resume: + + agpgart-intel :00:00.0: LATE suspend +hwgpe-0343 [05] hw_enable_wakeup_gpe_b: Enable Wake-up GPE for _GPE +hwgpe-0344 [05] hw_enable_wakeup_gpe_b: register_info->enable_for_wake 0x20 +hwgpe-0345 [05] hw_enable_wakeup_gpe_b: event_info->register_bit 0x1 + hwsleep-0284 [03] enter_sleep_state : PM Timer Event Enable value: 0x0 + hwsleep-0285 [03] enter_sleep_state : PM1Enable Enable value: 0x20 + hwsleep-0286 [03] enter_sleep_state : Disabling PM Timer + hwsleep-0290 [03] enter_sleep_state : PM Timer Event Enable value: 0x0 + hwsleep-0301 [03] enter_sleep_state : Entering sleep state [S3] + hwsleep-0325 [03] enter_sleep_state : Writing PM1A (SLP_TYP data) 1401 + hwregs-0698 [04] hw_register_write : Writing PM1A_CONTROL @ 1004 + hwsleep-0336 [03] enter_sleep_state : Writing PM1B (SLP_TYP data) 1401 + hwregs-0708 [04] hw_register_write : Writing PM1B_CONTROL @ 0 + hwsleep-0354 [03] enter_sleep_state : Will write PM1A (SLP_TYP + SLP_EN) 3401 + hwsleep-0355 [03] enter_sleep_state : Will write PM1B (SLP_TYP + SLP_EN) 3401 + hwsleep-0358 [03] enter_sleep_state : About to flush CPU cache + Back to C! + Enabling PM Timer + Resume status=0 + Resume ACPI state=3 + Event 0=0x1 + Event 1=0x0 + Event 2=0x0 + Event 3=0x0 + agpgart-intel :00:00.0: EARLY resume ** Description changed: When suspending (S3) the PC resumes immediately. - This occurs on a Sony PCG-SRC51P with a fresh install of Feisty. It also + This occurs on a Sony PCG-SRX51P with a fresh install of Feisty. It also affects Gutsy up to and beyond tribe-3 at least (all 32-bit). On an identical model (SRX41P) the problem doesn't occur. Have tried swapping the hard disks and memory modules between the two but the problem persists on the SRX51P. Both models have identical hardware but the SRX51P CPU is 50MHz faster, and it has 128MB more RAM (SRX41P = Intel P-III 800Mhz 256MB RAM, SRX51P = Intel P-III 850MHz 384MB RAM). Using a custom-built debugging kernel reveals that some device has generated a WAKE-UP event. Running a diff against the hardware profiles from lshal shows both models are identical. Running diffs on their dmesg confirms this. A diff of the kern.log over a suspend/resume cycle is also identical. The additional debug-message reporting I added into hwsleep() and acpi_pm_enter() show identical activity in both. Unfortunately, even with ACPI_FUTURE_USAGE enabled reading the WAKE event on resume always reports it as PM_TIMER, even on the 'good' PC so the wake-event code doesn't appear reliable. When I thought PM_TIMER was correct I added code to disable the PM_TIMER wake event just prior to suspend, and re-enabled it upon resume. That is the reason for the debug messages below. + + If I disable *all* wake events just prior to suspend the PC doesn't + resume immediately, but of course a hard reset is required since the + PWRBTN has also been disabled! Here's the output to kern.log from my debug code starting in hwsleep() and continuing in acpi_pm_ente
