[Bug 220735] New: YAST Power Management - Geld admits it fails under certain conditions.(common place situations) and is an enormous task.
33.5.4.3. Suspend and Standby Do Not Work There are several kernel-related problems that prevent the use of suspend and standby on ACPI systems: Currently, systems with more than 1 GB RAM do not support suspend. Currently, multiprocessor systems and systems with a P4 processor (with hyperthreading) do not support suspend. The error may also be due to a faulty DSDT implementation (BIOS). If this is
https://bugzilla.novell.com/show_bug.cgi?id=220735 Summary: YAST Power Management - Geld admits it fails under certain conditions.(common place situations) and is an enormous task. Product: SUSE Linux 10.1 Version: Final Platform: i586 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Major Priority: P5 - None Component: Usability AssignedTo: siegfried.olschner@novell.com ReportedBy: alpha096@tpg.com.au QAContact: siegfried.olschner@novell.com The Help Guide quested here on Power Management Quotes the case, install a new ??DSDT. Personally with a hight power CPU and a LOF of RAM the ability to suspend the RAM Disk would seems either. The concept of suspending to RAM only alarms me as the Power LED does not flash when there is a suspended session. IF spending to RAM only is chosen option and I would have thought that the More RAM the easier it would be to suspend the entire contents to session. I have difficulties why you want want to suspend to both. RAM and Disk as a user. Certainly this question needs further work. For instance, If a User had 2 GIG of RAM and chose suspend to RAM and during the process there was a problem of space - the application should then and advise the user that the session will be suspended to Disk. Once the bugs are ironed out I think there Fixed to be one option – Just suspend. Let the system do the rest. The original warning above about P4 HT - does it also apply to the new CPU origami Intel are now using to products and revise older processors which are essentially 2 Processors For pure cosmetic point and a user no being able to see what is actually hap pinging at a console view is very scary for a lot of users of view a splash screen would finish the job. Your thoughts -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=220735 ------- Comment #1 from alpha096@tpg.com.au 2006-11-14 08:56 MST ------- I see that you have changed the title somewhat and as I recall M$ took years to get it to work. In all my years of development work I would never let functionality that was faulty to be removed, however the potential for a power start to fail and the file system NOT get put back together in once piece the decision is a hard one. Particularly as the manual is so blunt about the issue. IF Intel's new origami chips are ALL going to be headaches a very lot will be sold to quench Vista's appetite and then if the move to Linux the consequences are frightening. Your call my friends ;-) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=220735 siegfried.olschner@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|siegfried.olschner@novell.co|bnc-team-screening@forge.provo.novell.com |m | Severity|Major |Normal ------- Comment #2 from siegfried.olschner@novell.com 2006-12-12 05:33 MST ------- Something for mobile devices? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=220735 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |seife@novell.com |screening@forge.provo.novell| |.com | -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=220735 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |alpha096@tpg.com.au ------- Comment #3 from seife@novell.com 2006-12-12 08:24 MST ------- is this still in the 10.2 documentation? I cannot find it there (i assume this is a bug against the documentation, or did i misunderstand this?) -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=220735 alpha096@tpg.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|alpha096@tpg.com.au | ------- Comment #4 from alpha096@tpg.com.au 2006-12-12 15:15 MST ------- I think this is both a functional AND documentation issue -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=220735 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |alpha096@tpg.com.au ------- Comment #5 from seife@novell.com 2006-12-13 06:45 MST ------- i believe the documentation is fixed already, since i did not find that stuff in the 10.2 docs. What exactly is the functional issue in your opinion? That we offer two ways of suspend? One, where you can safely remove the battery and AC power while suspended but that needs longer time to suspend and resume and one where you can't remove both battery and AC power while suspended, but that one is faster to suspend and resume? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=220735 alpha096@tpg.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|alpha096@tpg.com.au | ------- Comment #6 from alpha096@tpg.com.au 2006-12-13 15:13 MST ------- The issue is NOT with suspend to RAM OR suspend to disk. The functional issue it suspend to both. Current functionality permits selecting both which makes no real sense. I cannot think of any possible reason to suspend to both. There should be a choice of 1 or the other Besides as discussed here it most frequently fails see heading. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=220735 ------- Comment #7 from seife@novell.com 2006-12-16 02:41 MST ------- You can not select both t the same time. Suspend to disk and suspend to RAM serve different purposes, so it is quite important that the user can choose the one that fits his needs. The documentation is already "fixed" in that it no longer suggests that suspend to RAM is not working well. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=220735 ------- Comment #8 from alpha096@tpg.com.au 2006-12-16 15:17 MST ------- We are agreeing with each other re functionality - Therefore changes need to be made so that it is impossible to select both - Currently this is possible. Despite either selecting RAM OR Disk - the functionality most always fails on restore from suspense. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=220735 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fseidel@novell.com, behlert@novell.com, | |jjaeger@novell.com, hmacht@novell.com, | |seife@novell.com, dkukawka@novell.com AssignedTo|seife@novell.com |siegfried.olschner@novell.com Status|ASSIGNED |NEW ------- Comment #9 from seife@novell.com 2006-12-18 02:21 MST ------- (In reply to comment #8)
We are agreeing with each other re functionality - Therefore changes need to be made so that it is impossible to select both - Currently this is possible.
I don't think so. Once you selected "suspend to RAM", the frontends will not let you select anything else until you return from suspend. The same with "suspend to disk".
Despite either selecting RAM OR Disk - the functionality most always fails on restore from suspense.
This is hardware dependent. It works fine on all my machines. Suspend to disk should work on almost all desktop and notebook machines. Suspend to RAM is "protected" by a whitelist that only allows "known good" machines to suspend. We did, however, deliberately leave the "suspend to RAM" menu entry enabled for other machines also, to get people to actually try it, because it works on a much larger set of machines than those currently in our whitelist. If it does not work for you, this is a (different) bug that should be reported, but IMO the UI and the documentation (on openSUSE 10.2) are ok. Reassigning to Sigi to rule out usability issues, from the technical POV the bug is IMO fixed. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=220735 ------- Comment #10 from behlert@novell.com 2006-12-18 03:17 MST ------- It would be interesting to know where the initial comment is coming form. It contains a lot of wrong things that should be corrected. Regarding comment #6: suspend to both is useful if you want to have the advantages of both methods: - save restore if you run out of battery (s2disk) and - fast restore when resuming (s2ram) IBM had this (in hardware/BIOS) when APM was state of the art in their laptops. We will have something similar in future releases. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=220735 alpha096@tpg.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #11 from alpha096@tpg.com.au 2006-12-18 03:56 MST ------- The issue with respect to #10 is not the use of one method or the other - The issue is that functionally that the user can select both at the same time. Please advise under what condition suspend to RAM AND suspend to Disk should be both used together? With respect to the amount of times it fails - is as always not that the suspend action fails but moreover the resume actions almost always fails. This is probably why QA changed the initial BUG name to current. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=220735 ------- Comment #12 from behlert@novell.com 2006-12-18 09:53 MST ------- I explained that in comment 10: When you want both. Besides that, currently you cannot select both at the same time. I am not sure if we are talking about the same thing. It would be better to talk about 'suspend to disk'/'hibernate'/'s2disk' and 'suspend to ram'/'s2ram' and not simply 'suspend', because that makes it very hard to understand what you are referring to. s2disk e.g. is only failing if you have bad behaving modules, most of them being closed-source third party vendor modules that do not support suspend/resume. s2ram is failing on enough machines to justify that we check explicitly in a whitelist if problems are to be expected. All this does not explain where the initial comment comes from. I repeat, it contains a lot of wrong statements. This bug is about a wrong documentation. I don't see a change of bug name in the bug activity/history. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=220735 alpha096@tpg.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #13 from alpha096@tpg.com.au 2006-12-18 11:18 MST ------- Accept that IF in version 10.2 the current side help is not as above. Accept that in version 10.2 that you cannot select both -- 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.
participants (1)
-
bugzilla_noreply＠novell.com