Bug 129297

Summary:	Fujitsu-Siemens S7010 Laptop. ACPI no longer works since last online update
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Charles Gardiner <gardiner.charles>
Component:	Mobile Devices	Assignee:	Holger Macht <hmacht>
Status:	VERIFIED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	i686
OS:	SuSE Linux 10.0
Whiteboard:
Found By:	Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Charles Gardiner 2005-10-19 08:03:12 UTC

OT: Fujitsu-Siemens S7010 Laptop. ACPI no longer works since last online update

Hi,

a few days age I updated acpid and powersave using YaST online update. Since
then, the acpi daemon fails to start (ans as a consequence powersaved). I can
find no reason in /var/log/messages. There is just a simple 'failed' message in
red in the xterm window where I try to start it. The same happens of course on
boot which now takes considerably longer.

Interesstingly, if I start acpid with the debug option (i.e. acpid -d)
everything seems to work. I can then also start powersaved. As an interim
solution I have modified my rcacpid file to issue '/usr/sbin/acpid -d' when
starting.

I have also tried removing everything from the system which has to do with acpi
or powersave and reinstalling the original acpi/powersave from the 10.0 DVD but
it didn't fix anything. I assume it's a configuration setting somewhere but I
can't for the life of me find where.

Regards,
Charles

Comment 1 Holger Macht 2005-10-25 13:07:10 UTC

Hi. Did you also update ial via you? Please stop ial if it is running(rcial stop) and try to start acpid again.

Comment 2 Charles Gardiner 2005-10-25 14:07:48 UTC

I don't have ial installed at all. (My install path was initially an upgrade from 9.3)
I do however have hal installed and I see that the daemon is running (rchal status)

From my you/installed list, I see that hal-52547 has been fetched by the online update and that it does actually have the same date as the acpid (52496) and powersave (52499) patches.

Does your suggestion (stopping the daemon) apply to hal as well?

Regards,
Charles

Comment 3 Forgotten User ZhJd0F0L3x 2005-10-25 15:07:33 UTC

check how big /var/log/acpid is - if it is around 2GB, just remove it and try again. The old (fixed) acpid bug caused it to write a huge logfile (2G) and after hitting the 2g limit it crashed. It cannot be started as on start it writes to the logfile and crashes :-( In debug mode it might work since it does not write to the logfile but to the terminal instead.

Comment 4 Charles Gardiner 2005-10-25 15:30:03 UTC

Yes that's it.

Did as you suggested. The daemon now starts fine without debug-mode switch

Thanks,
Charles

Comment 5 Forgotten User ZhJd0F0L3x 2005-10-25 17:10:48 UTC

ok, so let's consider this _fixed_ :-)