resume from disk "scheduling while atomic" on K7-based hardware:

[Jeff Trull]

hibernate.sh dies upon resume due to "scheduling while atomic", causing a variety of problems (e.g., network drivers stay unloaded). See bug 59077 for details. It appears that the use of a 3DNOW-based memcpy in the suspend code causes preempt_count to be improperly incremented. All K7-based hardware is affected since CONFIG_X86_USE_3DNOW is on even for 386 kernels. This problem was found a few months back and fixed in 2.6.18. The patch commit message is attached.

Can this patch be applied in a Dapper kernel update? K7-based laptops cannot hibernate successfully without it.

[Jeff Trull (jetrull)]

If you diff kernel/power/snapshot.c between Dapper and Edgy you will see the patch has been applied. I verified that this problem is absent on my hardware in Edgy. Can it be done as a Dapper update?

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

Setting as "incomplete" as Kernel Team needs to action this as "Won't Fix" or otherwise.
[Note: fixed in 2.6.17]

[Gareth Fitzworthington (mapping-gp-deactivatedaccount)]

Sorry, that was a mistake. Setting as "confirmed" as Kernel Team needs to action this as "Won't Fix" or otherwise.
[Note: fixed in 2.6.17]

[Launchpad Janitor (janitor)]

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.

[Sergio Zanchetta (primes2h)]

Thank you for reporting this bug to Ubuntu. Dapper reached EOL, please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

Feel free to report any other bugs you may find.