You need to run off the panic events, the config flag IPMI_PANIC_EVENT, 
and it should compile fine.  This is a flag that causes the driver to 
put some information about the panic into an event log in the IPMI 
controller so it can be fetched later.

To do this, the driver needs a way to run each operation to completion 
without scheduling, interrupts. or the like.  It needs this to do send 
the panic event (since you cannot schedule during a panic), although it 
also really needs it to do things like extend the watchdog timer time at 
panic time.  The I2C driver does not currently have this, so it doesn't 
work with this option and the SMBus driver.

I have included a patch from Todd Davis at Intel that adds this function 
to the I2C driver.  I believe Todd has been working on getting this in 
through the I2C driver writers, although the patch is fairly non-intrusive.

However, I have no real way to test this patch.

-Corey

Adrian Bunk wrote:

>On Sun, Mar 07, 2004 at 10:32:21PM -0800, Andrew Morton wrote:
>  
>
>>... 
>>+ipmi-updates-3.patch
>>+ipmi-socket-interface.patch
>>
>> IPMI driver updates
>>...
>>    
>>
>
>This causes the following compile error:
>
><--  snip  -->
>
>...
>  CC      drivers/char/ipmi/ipmi_smb.o
>drivers/char/ipmi/ipmi_smb.c: In function `smbus_client_read_block_data':
>drivers/char/ipmi/ipmi_smb.c:224: warning: implicit declaration of 
>function `i2c_set_spin_delay'
>...
>  LD      .tmp_vmlinux1
>drivers/built-in.o(.text+0x1342eb): In function 
>`smbus_client_read_block_data':
>: undefined reference to `i2c_set_spin_delay'
>drivers/built-in.o(.text+0x13448d): In function 
>`smbus_client_write_block_data':
>: undefined reference to `i2c_set_spin_delay'
>drivers/built-in.o(.text+0x134b7f): In function `set_run_to_completion':
>: undefined reference to `i2c_set_spin_delay'
>make: *** [.tmp_vmlinux1] Error 1
>
><--  snip  -->
>
>
>cu
>Adrian
>
>  
>