I did some more investigation, this is what I came up with:
It seems to be depending on the kernel and the type of hibernate/resume that is used.
- For stock kernels from Karmic with swsusp it does NOT happen - For TuxOnIce-enalbed kernels from the TuxOnIce PPA it HAPPENS - If I download pre-kernel 2.6.31-16.51~pre2 from the PPA at https://launchpad.net/~stefan-bader-canonical/+archive/karmic, it does NOT happen - If I patch pre-kernel 2.6.31-16.51~pre2 from the PPA at https://launchpad.net/~stefan-bader-canonical/+archive/karmic with TuxOnIce patches from 20091009, it does NOT happen
so it seems to be introduced in the TuxOnIce sources between the patch-release 20091009 and the version of TuxOnIce used for building the kernel on the TuxOnIce-PPA.
I did some more investigation, this is what I came up with:
It seems to be depending on the kernel and the type of hibernate/resume that is used.
- For stock kernels from Karmic with swsusp it does NOT happen /launchpad. net/~stefan- bader-canonical /+archive/ karmic, it does NOT happen /launchpad. net/~stefan- bader-canonical /+archive/ karmic with TuxOnIce patches from 20091009, it does NOT happen
- For TuxOnIce-enalbed kernels from the TuxOnIce PPA it HAPPENS
- If I download pre-kernel 2.6.31-16.51~pre2 from the PPA at https:/
- If I patch pre-kernel 2.6.31-16.51~pre2 from the PPA at https:/
so it seems to be introduced in the TuxOnIce sources between the patch-release 20091009 and the version of TuxOnIce used for building the kernel on the TuxOnIce-PPA.