Bug 131441 - powersaved crashes
Summary: powersaved crashes
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Mobile Devices (show other bugs)
Version: Final
Hardware: i686 Other
: P5 - None : Major
Target Milestone: ---
Assignee: Holger Macht
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-28 21:51 UTC by James Willcox
Modified: 2005-12-12 15:24 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Willcox 2005-10-28 21:51:02 UTC
powersaved crashes for me, after a bit of acpi activity.  Usually the way I notice is after plugging/unplugging my laptop and the CPU speed doesn't change, nor does the screen brightness.  I can reproduce it by simply [un]plugging the machine a few times.  The stack trace seems pretty useless (I didn't have debug symbols), but here it is:

Program received signal SIGSEGV, Segmentation fault.
0x080697bb in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*> ()
(gdb) bt
#0  0x080697bb in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*> ()
#1  0x0806c841 in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::basic_string<char*> ()
#2  0x401b5ea0 in __libc_start_main () from /lib/tls/libc.so.6
#3  0x0804bba1 in ?? ()

This is on an IBM ThinkPad T40p, running powersave-0.10.15-5 with ACPI.
Comment 1 Holger Macht 2005-11-02 11:51:44 UTC
Please increase the powersave debug level in /etc/sysconfig/powersave/common:
  DEBUG="" --> DEBUG="16"

Then please restart the powersave daemon and try to reproduce the segfault and send me your /var/log/messages beginning from the restart. Thanks.
Comment 2 Stefan Behlert 2005-11-24 11:26:30 UTC
Anything new here?
Comment 3 Holger Macht 2005-12-12 13:09:11 UTC
Still no answer. Sorry, closing as INVALID. Please reopen if you get the debugging output.
Comment 4 James Willcox 2005-12-12 15:24:17 UTC
Yeah I actually can't reproduce this anymore.  Will reopen if I can again.