reopen 395086 merge 395086 395089 thanks > From: maximilian attems <[EMAIL PROTECTED]> > Subject: Re: Bug#395086: linux-image-2.6.18-1-686: disable suspend to disk on > install > To: [EMAIL PROTECTED] > Date: Tue, 24 Oct 2006 23:33:51 +0200 > User-Agent: Mutt/1.5.9i > Message-ID: <[EMAIL PROTECTED]> > > 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.
And ? The kernel package has a check to warn the user he is installing the same kernel as the currently running one. It could disable suspend to disk at the same time. This *is* a kernel package 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. Are you closing every non-debian-specific bugs ? do you know there is an upstream tag for non-debian-specific bugs ? Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
