Mike Coleman: This is not a valid excuse. If they can get it working, we should be able to get it working. Even if it were true that there is corner-cutting in implementing ACPI, the unpredictability of this bug and that it works most of the time would indicate a race condition or other improbable event. This is indicated in the attached log. If this were a problem of compatibility, it would not work AT ALL. It's not as if my computer is performing voodoo and deciding whether to resume based on the alignment of certain planets.
Attached is a portion of my messages log that points indicates a problem with suspend/resume on two different dates, each with the same call trace. The call trace is below: [<ffffffff80250927>] warn_slowpath+0xb7/0xf0 [<ffffffff8026d478>] ? down_trylock+0x38/0x50 [<ffffffff80251040>] ? try_acquire_console_sem+0x10/0x40 [<ffffffff8025c676>] ? lock_timer_base+0x36/0x70 [<ffffffff80531f3f>] ? usb_suspend_both+0x26f/0x310 [<ffffffff8069bf26>] ? printk+0x67/0x69 [<ffffffff80418867>] ? kobject_put+0x27/0x60 [<ffffffff804b6035>] ? put_device+0x15/0x20 [<ffffffff804be05a>] ? dpm_complete+0x18a/0x1a0 [<ffffffff8028003c>] suspend_test_finish+0x7c/0x80 [<ffffffff80280124>] suspend_devices_and_enter+0xe4/0x180 [<ffffffff802803d9>] enter_state+0xe9/0x120 [<ffffffff802804ca>] state_store+0xba/0x100 [<ffffffff80418707>] kobj_attr_store+0x17/0x20 [<ffffffff80347675>] sysfs_write_file+0xc5/0x140 [<ffffffff802e7eeb>] vfs_write+0xcb/0x130 [<ffffffff802e8040>] sys_write+0x50/0x90 [<ffffffff8021253a>] system_call_fastpath+0x16/0x1b [ end trace 673b03a7eaa85470 ]--- ** Attachment added: "message_excerpt.log" http://launchpadlibrarian.net/25041735/message_excerpt.log -- [Dell Inc. Inspiron 1420] suspend/resume failure https://bugs.launchpad.net/bugs/351840 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
