While this behavior continues, at least now there is a consistent (99%+guaranteed) workaround (with only one caveat...).
Two cases: 1) machine asleep for "a while"; 2) machine asleep "briefly". "A while" is on the order of hours; "briefly" is on the order of minutes (as much as an hour or two). Case 1: 1a. Put machine to sleep (S3 suspend to RAM; FN-F4 or lid close) 1b. Wake machine (FN or open lid) 1c. Network Manager applet "spins", trying to find network, clock takes noticeable time to adjust (several seconds), USB mouse is jittery. Network is never found, USB mouse remains jittery "forever". 1d. Once clock adjusts, screen locks (no surprise, really). Now begin the workaround.... 1e. Suspend again, then immediately wake the machine: Clock is OK, USB mouse is OK, network manager applet still spinning. In other words, all is well except no network. 1f. Right click on network manager applet, disable networking. Immediately right click again, enable networking: Network found! 1g. All is well. System perfectly useable (with one exception, below) Case 2: Very similar to case 1, basically pick up at 1d. In other words, 2a. Put machine to sleep (S3 suspend to RAM; FN-F4 or lid close) 2b. Wake machine (FN or open lid) 2c. Network Manager applet "spins". Clock adjusts quickly, USB mouse is OK. 2d. Once clock adjusts, screen locks (no surprise, really). Now begin the workaround.... 2e. Right click on network manager applet, disable networking. Immediately right click again, enable networking: Network found! 2f. All is well. System perfectly useable (with one exception, below) So the difference between 1 and 2 is that in 2 the USB mouse is OK from the beginning, the clock is OK from the beginning. But in both cases, network is never found unless I disable and re-enable. (Note: Net is always wired ethernet) The caveat: Once I wake the machine from sleep, I lose sound on WMV playback and all WMVs stop playing after 50 seconds, regardless of how much longer than 50s they are (less than 50s WMVs play fine, but without sound). I can close totem from the GUI, but there is still a process lying around that I have to find with ps and kill from CLI. If I don't do that, next WMV will be very jittery in playback (two totems arguing over the screen). I can describe more about how totem misbehaves after a sleep, if it is useful. Note: I have the universe totem with w32codecs installed. Final note: This is with APM, not ACPI. If I boot this machine with acpi=force (1999 BIOS, fails cutoff), performance seems better overall, but sleep is unreliable (in fact, never really sleeps, never returns). The package needs to change for this bug, please advise. ** Attachment added: "syslog from today (case 2)" http://librarian.launchpad.net/2669664/May16-syslog ** Attachment added: "kern log from today (case 2)" http://librarian.launchpad.net/2669665/May16-kern.log ** Attachment added: "daemon.log from today (case 2)" http://librarian.launchpad.net/2669666/May16-daemon.log ** Attachment added: "syslog from yesterday (case 1)" http://librarian.launchpad.net/2670217/May15-syslog ** Attachment added: "kern.log from yesterday (case 1)" http://librarian.launchpad.net/2670218/May15-kern.log ** Attachment added: "daemon.log from yesterday (case 1)" http://librarian.launchpad.net/2670223/May15-daemon.log -- Upon resume from sleep, USB mouse is "jittery" (Dapper) https://launchpad.net/bugs/31896 ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
