On Friday, I installed the 11.4 update from 2.6.36.1 to 2.6.36.6.
Seemed to go fine, until the first time I put to Sleep mode, from which it would not wake up.
This system slept and woke well with 11.3 and initial 11.4.
ATI video, sleep worked with radeon driver and fglrx until this update.
Now neither radeon nor fglrx will wake, but both boot and perform OK.
Any solutions or suggestions ?
Pointers to how to back out this kernel upgrade ?
I thought sleep mess had finally been resolved with 11.3…
Thanks caf4926, works well as you knew it would.
Alas, apparently that is not my problem.
Just prior to upgrade, I moved my /home to a new RAID 1 disk, set up in Yast (mdadm, I assume). The new /home seemed to work fine before and after the kernel update, but I probably did not try suspend so can’t say that 2.6.36.1 with /home on RAID1 worked well before the update to 2.6.36.6.
I am, at the moment, back at 2.6.36.1 with /home(RAID1).
Will not recover from suspend, no obvious issues in /var/log/pm-suspend.log
Is there some magic to get mdadm to cooperate with S2RAM ?
I don’t know
Never use RAID and generally advise against it. Though I guess for some situations it might be seen as necessary.
Sorry I can’t offer an further advice
I am looking for a good way to automatically (or periodically, automatically or semi-automatically) replicate (back-up) my photo and database files, which I keep in /home.
I am very open to alternative suggestions, RAID 1 mirror seemed painless and out of sight, but it seems to have side affects.
Personally I don’t have massive amounts of data to back up, maybe only 150GB
grsync is what I use
Note RAID is not a backup system. It is an availability system. They really provide different things. Don’t use RAID as a Backup.
On 2011-05-02 20:36, cmcgrath5035 wrote:
>
> I am looking for a good way to automatically (or periodically,
> automatically or semi-automatically) replicate (back-up) my photo and
> database files, which I keep in /home.
>
> I am very open to alternative suggestions, RAID 1 mirror seemed
> painless and out of sight, but it seems to have side affects.
RAID is not a backup system, it just protects you against one type of
problem: that one hard disk has a hardware problem and breaks down, you can
continue without powering down. It is for systems that must be up full time.
It does not protect you against software breakdown. For example, konqueror
goes mad and deletes a bunch of files. Or finger error. Or filesystem crash.
You get a lot more protection by making a second copy of your files on
that same disk you were to use for a mirror.
About the failure of sleep… maybe you have discovered a bug, that you
could report on bugzilla. Possibly few people test that feature, sleep on a
system with raid.
You mean suspend to ram or to disk?
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
Carlos - thanks for comments; understand.
My intention was to specifically guard against HDD failure.
I decided to remove the RAID1, now have one disk as /home and other disk mounted as /backup and will use rsync/grsync to perform a backup periodically.
With RAID1 removed, sleep (suspend is what I normally use) working once again.
But suspend to where? You can suspend to RAM or suspend to disk.
This looks like something that should be reported to bugzilla. I doubt that many that use RAID also suspend to any where since RAID is mostly used in a production situations where 99.999% uptime is required.
On 2011-05-03 17:06, cmcgrath5035 wrote:
> I decided to remove the RAID1, now have one disk as /home and other
> disk mounted as /backup and will use rsync/grsync to perform a backup
> periodically.
A precaution is mount it only at backup time.
> With RAID1 removed, sleep (suspend is what I normally use) working once
> again.
It would have been interesting to report first the failure.
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
Unfortunately, I was not convinced that the RAID install was the issue until I backed it out and re-upgraded to 2.6.36.
If I get a chance, I’ll try to reproduce and generate some useful info.
As I indicated, /var/log/pm-suspend.log looked OK going into suspend, nothing logged when wake up was attempted.
Sorry for the language difficulty - I think in terms of suspend(to ram) and hibernate(to disk).
On 2011-05-04 02:06, cmcgrath5035 wrote:
>
> Unfortunately, I was not convinced that the RAID install was the issue
> until I backed it out and re-upgraded to 2.6.36.
Understandable.
> If I get a chance, I’ll try to reproduce and generate some useful info.
> As I indicated, /var/log/pm-suspend.log looked OK going into suspend,
> nothing logged when wake up was attempted.
Yes, if it fails nothing gets written.
However, you can disable the splash display, so you can see the progress in
text.
> Sorry for the language difficulty - I think in terms of suspend(to ram)
> and hibernate(to disk).
Well, yes, that’s the correct wording. But it is sometimes difficult to
know if your correspondent is using that nomenclature or not 
–
Cheers / Saludos,
Carlos E. R.
(from 11.2 x86_64 “Emerald” at Telcontar)
