[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#475267: marked as done ([linux-image-2.6] don't allow suspend to disk after updating the kernel image)



Your message dated Tue, 13 May 2008 01:24:41 +0200
with message-id <20080512232441.GB11899@stro.at>
and subject line Re: [linux-image-2.6] don't allow suspend to disk after updating the kernel image
has caused the Debian Bug report #475267,
regarding [linux-image-2.6] don't allow suspend to disk after updating the kernel image
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
475267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475267
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6
Severity: critical

--- Please enter the report below this line. ---
Hi,

Please don't allow suspend to disk after updating the kernel image since it can't resume and there is the risk of data corruption. This is of special concern when the update is within one version number (like it happend 2 days ago) since you have no choice of booting the right kernel.
Thanks,
Sebastian


--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.24-1-686

Debian Release: lenny/sid
  500 testing         www.debian-multimedia.org
  500 testing         security.debian.org
  500 testing         ftp2.de.debian.org


--- Package information. ---
Depends       (Version) | Installed
=======================-+-===========
                        |




--- End Message ---
--- Begin Message ---
first please learn to set proper severities.
this is *not* critical.

second of all this "bug" is fixed upstream i can suspend to disk
with 2.6.25 and reboot into 2.6.26-rc2 happily continuing real work.

be happy and learn to use your box.
debian user mailing list support seems more adequate then random
bug filling.

-- 
maks


--- End Message ---

Reply to: