Mailinglist Archive: opensuse-bugs (5398 mails)
| < Previous | Next > |
[Bug 269741] Normal boot procedure altered by presence past Suspend to Disk Operation
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Fri, 1 Jun 2007 22:50:30 -0600 (MDT)
- Message-id: <20070602045030.6B6E310D6@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=269741
------- Comment #15 from alpha096@xxxxxxxxxx 2007-06-01 22:50 MST -------
G'day frank. I am really very sorry cannot provide output of "/sbin/swapon -s"
after such a resume?" Pulling the plug on a production system I fear. Yesterday
I have a power outage and all PC recovered file journal's except 1 PC which
holds the IDS Management system SQL database for many clients data. I lost over
120 Days of History and can only restore to last backup 7 days ago which I am
still having trouble with indexing of the SQL database. Yes I know I should
have a UPS. (And to cap the day off Novell called me from the US and told me I
did not win the SLED Laptop)
I have tried every means I know of capturing a screen image (SHFT+Print
Screen), (ALT+Print Screen), CTRL+Print Screen) without any joy. I cannot even
lock the image.
Just to be really clear about the boot process difference I see but cannot
capture.
Normal boot after normal shut-down (1)
1. Loading Grub....
2. Blue splash screen to select Kernel
3. Open Suse Splash screen.
If you pull the plug on a PC that has had a previous Suspend to Disk I see.(2)
1. Loading Grub.
2. Text screen (the same screen you see in a normal resume)
3. Open Suse Splash screen
4. Further text screen
5. GUI KDE session as normal.
I am also a little confused at comment #6 contradicting itself.
>> Every time suspend to disk is used an image file is created
>wrong.
>We suspend into the swap partition, so if you have a working swap after
>resetting your machine hard, the suspend image is deleted.
Anyway As has been stated by fears of the suspend to disk file(image) written
to swap is deleted. Re-iterating comment #1Whilst the absence of the normal
resume after shut down sequence is not present if you re-start after pulling
the plug, it appears that there is little if no consequence apart from the user
not being presented with the boot options screen as in example 1 item 2. The
rest of the scenario I presented as possible is excluded as the image file is
deleted so the rest of the scenario's logic is not founded.
If there is a bug here its is only that if the user suspend and resume and the
plug is pulled after such a resumption, the user misses out is the boot options
selection screen. The subsequent session that is established after such an
event is one of a normal O/S boot procedure including fschk.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Comment #15 from alpha096@xxxxxxxxxx 2007-06-01 22:50 MST -------
G'day frank. I am really very sorry cannot provide output of "/sbin/swapon -s"
after such a resume?" Pulling the plug on a production system I fear. Yesterday
I have a power outage and all PC recovered file journal's except 1 PC which
holds the IDS Management system SQL database for many clients data. I lost over
120 Days of History and can only restore to last backup 7 days ago which I am
still having trouble with indexing of the SQL database. Yes I know I should
have a UPS. (And to cap the day off Novell called me from the US and told me I
did not win the SLED Laptop)
I have tried every means I know of capturing a screen image (SHFT+Print
Screen), (ALT+Print Screen), CTRL+Print Screen) without any joy. I cannot even
lock the image.
Just to be really clear about the boot process difference I see but cannot
capture.
Normal boot after normal shut-down (1)
1. Loading Grub....
2. Blue splash screen to select Kernel
3. Open Suse Splash screen.
If you pull the plug on a PC that has had a previous Suspend to Disk I see.(2)
1. Loading Grub.
2. Text screen (the same screen you see in a normal resume)
3. Open Suse Splash screen
4. Further text screen
5. GUI KDE session as normal.
I am also a little confused at comment #6 contradicting itself.
>> Every time suspend to disk is used an image file is created
>wrong.
>We suspend into the swap partition, so if you have a working swap after
>resetting your machine hard, the suspend image is deleted.
Anyway As has been stated by fears of the suspend to disk file(image) written
to swap is deleted. Re-iterating comment #1Whilst the absence of the normal
resume after shut down sequence is not present if you re-start after pulling
the plug, it appears that there is little if no consequence apart from the user
not being presented with the boot options screen as in example 1 item 2. The
rest of the scenario I presented as possible is excluded as the image file is
deleted so the rest of the scenario's logic is not founded.
If there is a bug here its is only that if the user suspend and resume and the
plug is pulled after such a resumption, the user misses out is the boot options
selection screen. The subsequent session that is established after such an
event is one of a normal O/S boot procedure including fschk.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
| < Previous | Next > |