Bug 102960 - ERROR in Function initHal; line 38: could not init hal library: (null)
Summary: ERROR in Function initHal; line 38: could not init hal library: (null)
Status: VERIFIED FIXED
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Mobile Devices (show other bugs)
Version: Beta 1
Hardware: All All
: P5 - None : Normal
Target Milestone: ---
Assignee: Holger Macht
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-09 09:07 UTC by Klaus Kämpf
Modified: 2007-06-05 10:01 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Klaus Kämpf 2005-08-09 09:07:54 UTC 
besides $summary, /var/log/messages shows: 
Aug  8 18:02:10 heron kernel: powernow-k8: Power state transitions not 
supported 
Aug  8 18:02:10 heron rcpowersaved: CPU frequency scaling is not supported by 
your processor. 
Aug  8 18:02:10 heron rcpowersaved: enter 'CPUFREQD_MODULE=off' 
in /etc/sysconfig/powersave/cpufreq to avoid this warning. 
Aug  8 18:02:10 heron rcpowersaved: Cannot load cpufreq governors - No cpufreq 
driver available 
Aug  8 18:02:10 heron [powersave][14409]: ERROR in Function PM_Interface; line 
241: Cannot create cpufreq objects 
Aug  8 18:02:10 heron [powersave][14409]: ERROR in Function initHal; line 38: 
could not init hal library: (null) 
Aug  8 18:02:10 heron [powersave][14409]: ERROR in Function 
getACAdapterStatus; line 269: could not init hal 
Aug  8 18:02:12 heron [powersave][14409]: WARNING in Function filter_function; 
line 250: Received message from invalid interface 
Aug  8 18:02:12 heron [powersave][14409]: WARNING in Function filter_function; 
line 250: Received message from invalid interface
Comment 1 Danny Al-Gaaf 2005-08-09 11:34:32 UTC 
Holger: I think this is a bug in powersave. looks as powersave try to connect to 
HAL while HAL isn't ready.
Comment 2 Holger Macht 2005-08-09 11:43:01 UTC 
Yes, you ar e right. But what't the problem. I will remove the second error
message from getACAdapterStatus() and decrease severity from initHal from ERROR
to warning.

Tell me if there is another problem...
Comment 3 Andreas Jaeger 2005-08-10 19:54:12 UTC 
Is there a dependency of powersave on hal in the init scripts?  If it is, then
why is the start up script of hal finished before hal is ready?
Comment 4 Danny Al-Gaaf 2005-08-10 22:15:53 UTC 
Yes, there is a dependeny. If hal starts the init script is immediately back and 
return successful. HAL is started in this moment. This is the correct behavior. 

If hald starts, hal is "ready", but you can access the hal-service over DBUS 
first if hal ends the initial import of hardwareinformation and provides his 
services. 

To prevent such errors, you has to check if HAL provides his services over dbus 
currently or you must check the errorcode of the called function and retry 
later.
Comment 5 Holger Macht 2005-08-25 09:43:31 UTC 
reduced debug level and removed second error message
Comment 6 Holger Macht 2005-08-25 11:13:39 UTC 
This seems to happen on every boot. So we need a better solution.

Danny: How can I check if Hal is really ready? Is there a signal emitted over
dbus? Or any corresponing function?
Comment 7 Holger Macht 2005-08-25 12:46:51 UTC 
Ok, added check if hal service is registered with dbus. If not, proper warning
is thrown.