10-06-2004
Ups...
O.S. : SCO Unix 3.2.5.0
Machine : PROLIANT ML370
Pentium 3 733
HD 18.2GB Ultra3 SCSI 10Krpm
HD 9.1GB Ultra3 SCSI 10Krpm
512 Ram
Informix Running
Sorry.
6 More Discussions You Might Find Interesting
1. SCO
My Unix Server with SCO Unix ver 5, display Watchdog error which reads,
Watchdog ReInitMemory 6 for board 0 Warning : eeE : Allocb failure in ReInitMemory.
My server has 98 dumb terminals connected. It has 5 Hard Disks (SCSI) of 9.1 GB each and 512 MB RAM. Uses RAID level 5
After this error... (1 Reply)
Discussion started by: V.V.KUMAR
1 Replies
2. Solaris
hi,
is it possible to disable the "hardware watchdog" on a V240 sol 10 server?
and how to?
this server freeze 9/10 during boot on this command...:mad:
thanks (3 Replies)
Discussion started by: guilik
3 Replies
3. Solaris
Hi,
is there something build in solaris that can act as "watchdog".
I have some process (service) running (e.g. Rhino). It can happen that if freezes totaly so I need to find this out and restart it totaly.
My vision is two possibilities.
1) there is some counter running and I will... (2 Replies)
Discussion started by: freeangel
2 Replies
4. Solaris
Hi,
Please let me know what is hardware watchdog enabled which we get when the solaris host is booting .As per my knowledge its the one states that the POST is enabled. correct me if am wrong. (1 Reply)
Discussion started by: rogerben
1 Replies
5. AIX
Hi All,
I am getting pages from EMS(Event Monitoring Servers) for "no watchdog notification"
I just wonder what cause this and what to look in the system.
this error was generated from production lpar which hosts p570
Thanks
Mann (4 Replies)
Discussion started by: chubby362002
4 Replies
6. Shell Programming and Scripting
Hi,
I am willing to build a script that does a "ps-ef" or "top" on a specific process, and if it finds it running to start another process.
Any suggestions to do this in a optimized way?
Thanks! (2 Replies)
Discussion started by: liviusbr
2 Replies
LEARN ABOUT CENTOS
i2c_register_board_info
I2C_REGISTER_BOARD_I(9) I2C and SMBus Subsystem I2C_REGISTER_BOARD_I(9)
NAME
i2c_register_board_info - statically declare I2C devices
SYNOPSIS
int i2c_register_board_info(int busnum, struct i2c_board_info const * info, unsigned len);
ARGUMENTS
busnum
identifies the bus to which these devices belong
info
vector of i2c device descriptors
len
how many descriptors in the vector; may be zero to reserve the specified bus number.
DESCRIPTION
Systems using the Linux I2C driver stack can declare tables of board info while they initialize. This should be done in board-specific init
code near arch_initcall time, or equivalent, before any I2C adapter driver is registered. For example, mainboard init code could define
several devices, as could the init code for each daughtercard in a board stack.
The I2C devices will be created later, after the adapter for the relevant bus has been registered. After that moment, standard driver model
tools are used to bind "new style" I2C drivers to the devices. The bus number for any device declared using this routine is not available
for dynamic allocation.
The board info passed can safely be __initdata, but be careful of embedded pointers (for platform_data, functions, etc) since that won't be
copied.
COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 I2C_REGISTER_BOARD_I(9)