hotplugd(1M)															      hotplugd(1M)

NAME

       hotplugd - PCI I/O hotplug (attention button) events daemon

SYNOPSIS

       logfile openmode

DESCRIPTION

       The  daemon  handles  PCI I/O hotplug (also known as attention button, AB, or doorbell) events that are generated by pressing the attention
       button corresponding to a PCI I/O slot.

       Only one attention button event is processed by the system at any point in time.  If more than one attention button is pressed, the  events
       are put in a queue within the kernel.

       This  daemon invokes to perform the various online addition or replacement operations (OLAR, OL*) on the slot on which the attention button
       has been pressed.  The daemon does not use the (override CRA results) option of

       Normally, this daemon is started by the startup script at boot time.  See the subsection for details.

       If an attention button is pressed before the startup of the daemon, the event is dropped and no messages are logged.  Also see the  section
       for messages that are logged in the system log file or the log file.

       Only users with superuser privileges may use this command to perform OL* functions.

       Currently, only the online addition and replacement functions are supported.  Online deletion is not supported.

       The blinking of the power LED is not supported on all hardware platforms.

   Operands
       The following operands are required.  See also the subsection.

       logfile	      Log file where the daemon will log its messages.	The standard output and standard error of the command are also captured in
		      this log file.

       openmode       Mode in which to open the logfile.  It can be one of the following:

		      Open the file in append mode.
				New log information is appended at the end of logfile.

		      Open the file and truncate it.
				If the logfile exists, its length is truncated to 0 and the mode and owner are unchanged.

   Daemon Startup
       In the normal (and recommended) operation is invoked at boot time through the startup script, The startup script  reads	the  configuration
       file,  for  the	configuration  file variables, and which are assigned to the logfile and openmode parameters, respectively.  The installed
       default values are:

       To start a new instance of with new values for logfile and mode, you can do so by stopping the running instance of and manually starting it
       with the new values.

       To  have always invoked on startup with the new values, change the values of the and variables in the configuration file, At the next boot,
       will be invoked with these new values.

DIAGNOSTICS

   Messages in the System Log File
       The following messages are logged in the system log file, If an attention button event occurs after the daemon has been terminated  follow-
       ing a successful start of the daemon, the messages are logged in the system log file.

	      A chunk of memory, used for storing the attention button event information, could not be allocated.

	      The  event  is dropped after the power LED is set to mode.  That is, the power LED will be set to ON if the power to the slot is ON,
	      or the power LED will be set to OFF if the power to the slot is OFF.

	      The queue has not been initialized (daemon not running) or the queue is under flow control.  The queue can go into flow  control	if
	      the queue already has maximum number of events.  Currently the maximum is 128.

	      The  event  is  dropped  after setting the power LED to mode (see previous message).  Wait till the attention button events are pro-
	      cessed by the daemon.

	      The attention button event was received on a slot ID that has not been registered (during the system bootup) with  the  kernel  OLAR
	      module.

	      The event is dropped after setting the power LED to mode (see previous message).	Contact your HP response center.

	      The call to get the slot information failed.  olarErrMsg gives the reason for the error.

	      This results in an invalid PCI OL* event to the daemon.

	      The system is clearing the attention button events in the queue due to the abnormal termination of the daemon (for example, with the
	      signal (see kill(1)) and there are pending attention button events in the queue.

	      While clearing the events from the queue, the system sets the power LED corresponding to the slotId, to mode (see previous message).

	      Setting the power LED to mode failed.  The system sets the power LED to mode while clearing attention button events from the  queue,
	      triggered by the abnormal termination of the hotplugd daemon (for example, with the signal (see kill(1)).

   Messages in the hotplugd Daemon Log File
       The following messages are logged in the daemon log file, defined by logfile.

	      An  error  has  occurred	on  the  call to get attention button events from the kernel in the mode.  errMsg gives the reason for the
	      error.

	      An error has occurred on the call to get attention button events from the kernel in the mode.   errMsg  gives  the  reason  for  the
	      error.

	      An  error  has  occurred	on  the  call to get attention button events from the kernel in the mode.  errMsg gives the reason for the
	      error.  This error occurred within 1 second of the previous error.  The daemon will sleep for n seconds before making another call.

	      The specified oprn PCI OL* operation failed.  oprn may be one of the following:

	      Could not open the device in the read-write mode.  errMsg gives the reason for the error.

	      Setting the close-on-exec flag on using failed.  errMsg gives the reason for the error.  At times, terminating the daemon  with  may
	      not  clear  all kernel data structures.  If you try to restart the daemon, it may report an error, In such circumstances, the system
	      must be rebooted to start the daemon successfully.

	      The initialization of for getting attention button events failed.  olarErrMsg gives the reason for the error.

	      The initialization of for getting attention button events failed.  errMsg gives the reason for the error.

	      The shutdown of failed.  olarErrMsg gives the reason for the error.

	      The shutdown of failed.  errMsg gives the reason for the error.

	      is dropping oprn PCI OL* operation on the slotId slot because it is shutting down.  time gives the time at which the attention  but-
	      ton was pressed.

	      has received an invalid PCI OL* operation on slot slotId.  oprn can be one of the following: time is the time at which the attention
	      button was pressed.

	      This could happen if or is received and the slot is not in the right state.  For example, if is received, and the slot is  not  sus-
	      pended, and the driver is attached, then it is an invalid PCI OL* operation.  Or, it is invalid if is received, and the slot is sus-
	      pended.

	      This could also happen if the call to get the slot status information fails.

	      received a PCI OL* operation which it does not understand on slot slotId.  oprnCode is the integer representation  of  the  PCI  OL*
	      operation.  time is the time at which the attention button was pressed.

	      Contact your HP response center.

	      The  attention button event has been dropped because it was received while another event was being processed or pending for the same
	      slotId.  olarIoEvent is the event that was received.  It can be one of the following: time gives the time at  which  the	event  was
	      received.

	      Wait for the attention button processing on a slot to complete before pressing the attention button again on that slot.

	      The power LED could not be set to mode for the given slotId.  errMsg gives the reason for the error.

	      The power LED could not be set to mode for the given slotId.  olarErrMsg gives the reason for the error.

	      The program was invoked with an invalid set of parameters.

	      could not fork itself.  errMsg gives the reason for the error.

	      could not open the given logFile in write mode.  errMsg gives the reason for the error.

	      could not get the lock on the logFile.  errMsg gives the reason for the error.

	      It could be because another instance of is running.

FILES

       Configuration file for PCI I/O OLAR operations.

       Startup script, used at boot time to start the daemon.

       Installed default name of file where the daemon logs messages.
		      See the section and the subsection for details.

       System log file.
		      See the section for details.

SEE ALSO

       olrad(1M), pdweb(1M), syslogd(1M), errno(2), fcntl(2), ioctl(2)

																      hotplugd(1M)