[arch-general] kde44beta - Arch needs to disable powerdevil suspend default -> very hard shutdown...
Devs, I don't know whether this is something Arch can set or if it is kde that sets the powerdevil suspend default. We need to see if it is possible to disable the 'suspend' after 30 minutes on the first page of the powerdevil settings because many machines (mine included) do not suspend nicely and instead lock up tight. It took a while to find this issue on my x86_64 box, but after setting the default to 'Turn off Screen' instead of suspend, the lockups are gone. When the suspend lockups occurred, my box locked so badly I had to pull the power-cord and drain the residual power by depressing the 'on' button with the cord out before the box would POST again. That's a serious lock.... If possible, we may want to try and disable this default even if it is a kde default because it has some pretty bad implications.... -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On 02/03/2010 12:42 PM, David C. Rankin wrote:
Devs,
I don't know whether this is something Arch can set or if it is kde that sets the powerdevil suspend default. We need to see if it is possible to disable the 'suspend' after 30 minutes on the first page of the powerdevil settings because many machines (mine included) do not suspend nicely and instead lock up tight.
It took a while to find this issue on my x86_64 box, but after setting the default to 'Turn off Screen' instead of suspend, the lockups are gone.
When the suspend lockups occurred, my box locked so badly I had to pull the power-cord and drain the residual power by depressing the 'on' button with the cord out before the box would POST again. That's a serious lock....
If possible, we may want to try and disable this default even if it is a kde default because it has some pretty bad implications....
I disagree, I believe this should be an upstream fix. There is an workaround to those that have problems.
On 02/03/2010 11:44 AM, pyther wrote:
On 02/03/2010 12:42 PM, David C. Rankin wrote:
Devs,
I don't know whether this is something Arch can set or if it is kde that sets the powerdevil suspend default. We need to see if it is possible to disable the 'suspend' after 30 minutes on the first page of the powerdevil settings because many machines (mine included) do not suspend nicely and instead lock up tight.
It took a while to find this issue on my x86_64 box, but after setting the default to 'Turn off Screen' instead of suspend, the lockups are gone.
When the suspend lockups occurred, my box locked so badly I had to pull the power-cord and drain the residual power by depressing the 'on' button with the cord out before the box would POST again. That's a serious lock....
If possible, we may want to try and disable this default even if it is a kde default because it has some pretty bad implications....
I disagree, I believe this should be an upstream fix. There is an workaround to those that have problems.
I'm 60/40 in favor of disabling it. Any feature that can damage a system (ext4 hard shutdown corruption) should be disabled by default thus requiring the user to "pick his poison" rather than having it slipped into his glass. You guys are the decision makers, I can just call'em like I see'em and pass the info along. Either way, I know what poison to be on the lookout for now :p The situation is a bit more acute with the current possibility of differing power managers depending upon the history of the individual box. Just something else to consider. But, I'm really liking the beta release Arch put together. Best of any distros beta I have had the opportunity to mess with by far! -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Wed, Feb 3, 2010 at 13:02, David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
[stuff]
The bug tracker is probably a more appropriate place for all this.
Am Mittwoch, 3. Februar 2010 19:02:18 schrieb David C. Rankin:
Any feature that can damage a system (ext4 hard shutdown corruption) should be disabled by default thus requiring the user to "pick his poison" rather than having it slipped into his glass.
Suspend is not broken by itself, it's your BIOS (very likely) or maybe a kernel driver that is broken. So I don't see the point in disabling the feature here. According to your logic we might disabling sound because playing sound might crash systems with broken audio drivers. Or maybee we shsould also disable Kwin composite because it freezes system using broken dirver like my intel. I hope you get the idea. ;-) -- Pierre Schmitz, https://users.archlinux.de/~pierre
On 02/03/2010 01:53 PM, Pierre Schmitz wrote:
Am Mittwoch, 3. Februar 2010 19:02:18 schrieb David C. Rankin:
Any feature that can damage a system (ext4 hard shutdown corruption) should be disabled by default thus requiring the user to "pick his poison" rather than having it slipped into his glass.
Suspend is not broken by itself, it's your BIOS (very likely) or maybe a kernel driver that is broken. So I don't see the point in disabling the feature here. According to your logic we might disabling sound because playing sound might crash systems with broken audio drivers. Or maybee we shsould also disable Kwin composite because it freezes system using broken dirver like my intel. I hope you get the idea. ;-)
I get it, Pierre, what do you suggest as the best way to troubleshoot this issue. The board affected is a MSI K9N2 SLI Platinum with an AMD Phenom(tm) 9850 Quad-Core Processor. Is this something that should go through tracker, the forums, what?? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
participants (4)
-
Daenyth Blank
-
David C. Rankin
-
Pierre Schmitz
-
pyther