Bug#395086: marked as done (linux-image-2.6.18-1-686: disable suspend to disk on install)
Your message dated Tue, 24 Oct 2006 23:33:51 +0200
with message-id <20061024213351.GB13178@baikonur.stro.at>
and subject line Bug#395086: linux-image-2.6.18-1-686: disable suspend to disk on install
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: linux-image-2.6.18-1-686
Version: 2.6.18-3
Severity: wishlist
When installing a new kernel over the currently running one, and suspend to
disk is enabled, the system will fail to resume with the newer kernel at
resuming time. It would be safer if it was impossible to suspend to disk then.
I guess setting some value to /sys/power/resume would do the trick.
More generally, I think there is something wrong with Linux doing
suspend to disk in S5 instead of S4. It has great advantages, such as
being able to suspend to disk an OS and booting another one, but it very
risky when you use filesystems opened by the suspended OS with another
one. Another issue is that you have to resume with the exact same kernel
that suspended, which is the reason of this bug, but is also a problem
for people having more than one kernel installed... Interaction with the
bootloader may be something to be worked on...
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages linux-image-2.6.18-1-686 depends on:
ii initramfs-tools [linux-initra 0.84 tools for generating an initramfs
ii module-init-tools 3.2.2-3 tools for managing Linux kernel mo
ii yaird [linux-initramfs-tool] 0.0.12-18 Yet Another mkInitRD
Versions of packages linux-image-2.6.18-1-686 recommends:
ii libc6-i686 2.3.6.ds1-7 GNU C Library: Shared libraries [i
-- debconf information:
linux-image-2.6.18-1-686/postinst/bootloader-error-2.6.18-1-686:
shared/kernel-image/really-run-bootloader: true
linux-image-2.6.18-1-686/postinst/depmod-error-initrd-2.6.18-1-686: false
linux-image-2.6.18-1-686/postinst/create-kimage-link-2.6.18-1-686: true
linux-image-2.6.18-1-686/preinst/initrd-2.6.18-1-686:
linux-image-2.6.18-1-686/preinst/abort-overwrite-2.6.18-1-686:
linux-image-2.6.18-1-686/preinst/elilo-initrd-2.6.18-1-686: true
linux-image-2.6.18-1-686/postinst/old-initrd-link-2.6.18-1-686: true
* linux-image-2.6.18-1-686/preinst/already-running-this-2.6.18-1-686:
linux-image-2.6.18-1-686/preinst/lilo-has-ramdisk:
linux-image-2.6.18-1-686/postinst/bootloader-test-error-2.6.18-1-686:
linux-image-2.6.18-1-686/postinst/depmod-error-2.6.18-1-686: false
linux-image-2.6.18-1-686/postinst/old-dir-initrd-link-2.6.18-1-686: true
linux-image-2.6.18-1-686/preinst/overwriting-modules-2.6.18-1-686: true
linux-image-2.6.18-1-686/preinst/failed-to-move-modules-2.6.18-1-686:
linux-image-2.6.18-1-686/preinst/lilo-initrd-2.6.18-1-686: true
linux-image-2.6.18-1-686/prerm/removing-running-kernel-2.6.18-1-686: true
linux-image-2.6.18-1-686/postinst/old-system-map-link-2.6.18-1-686: true
linux-image-2.6.18-1-686/prerm/would-invalidate-boot-loader-2.6.18-1-686: true
linux-image-2.6.18-1-686/preinst/bootloader-initrd-2.6.18-1-686: true
linux-image-2.6.18-1-686/preinst/abort-install-2.6.18-1-686:
linux-image-2.6.18-1-686/postinst/kimage-is-a-directory:
--- End Message ---
--- Begin Message ---
On Tue, Oct 24, 2006 at 08:41:38PM +0200, Mike Hommey wrote:
>
> When installing a new kernel over the currently running one, and suspend to
> disk is enabled, the system will fail to resume with the newer kernel at
> resuming time. It would be safer if it was impossible to suspend to disk then.
> I guess setting some value to /sys/power/resume would do the trick.
this an userspace problem.
> More generally, I think there is something wrong with Linux doing
> suspend to disk in S5 instead of S4. It has great advantages, such as
> being able to suspend to disk an OS and booting another one, but it very
> risky when you use filesystems opened by the suspended OS with another
> one. Another issue is that you have to resume with the exact same kernel
> that suspended, which is the reason of this bug, but is also a problem
> for people having more than one kernel installed... Interaction with the
> bootloader may be something to be worked on...
feel free to submit a bug upstream or discuss that on lkml.
that is definetly not a debian specific bug.
so closing for now.
--
maks
--- End Message ---
Reply to: