Skip to content. | Skip to navigation

Personal tools

Navigation

You are here: Home / Wiki / Kb135

Kb135

Emulab FAQ: Testbed Operations: What if "node health monitoring" complains at boot time?

Emulab FAQ: Testbed Operations: What if "node health monitoring" complains at boot time?

> When I boot up:
>
> > Starting node health monitoring ...
> > i2c-core.o: i2c core module
> > i2c-piix4.o version 2.6.3 (20020322)
> > i2c-piix4.o: Error: Can't detect PIIX4 or compatible device!
> > i2c-piix4.o: Device not detected, module not inserted.
> > /lib/modules/2.4.18-27.7.x/kernel/drivers/i2c/i2c-piix4.o: init_module: No such device
> > Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
> > 	You may find more information in syslog or the output from dmesg
> > /lib/modules/2.4.18-27.7.x/kernel/drivers/i2c/i2c-piix4.o: insmod /lib/modules/2.4.18-27.7.x/kernel/drivers/i2c/i2c-piix4.o failed
> > /lib/modules/2.4.18-27.7.x/kernel/drivers/i2c/i2c-piix4.o: insmod i2c-piix4 failed
>
> Anything to worry about?

No - it just means that healthd won't run on that machine. This happens on machines that don't have lmsensors support or where its not setup correctly (we have a pretty naive method of loading lmsensors/i2c modules).