omreport returns nothing

Jesse Proudman j.list at blueboxdev.com
Wed Aug 2 11:12:26 CDT 2006


To provide more information, the whole reason I am attempting to do  
this is because the PowerEdge 850 has the orange blinking light on  
the front and I need to know what's causing it.

I believe I've gotten IPMI to install into my kernal and load on boot.

[root at vsh1 dev]# lsmod
Module                  Size  Used by
ipmi_watchdog          14784  0
ipmi_devintf            6148  0
ipmi_si                28125  1
ipmi_msghandler        40256  3 ipmi_watchdog,ipmi_devintf,ipmi_si
<snip>

---------

[root at vsh1 blueboxadmin]# /etc/init.d/ipmi start
Starting ipmi drivers:                                     [FAILED]
[root at vsh1 blueboxadmin]# modprobe ipmi_si addrs=0x0CA8
Segmentation fault
[root at vsh1 blueboxadmin]# modprobe ipmi_si addrs=0x0CA8
[root at vsh1 blueboxadmin]# /etc/init.d/ipmi start
Starting ipmi drivers:                                     [  OK  ]

----------

/dev shows:
crw-r--r--  1 root root 252,   0 Aug  2 08:52 ipmi0

----------

/var/log/messages has various entries:
Aug  2 08:45:04 vsh1 kernel: ipmi message handler version v32
Aug  2 08:45:04 vsh1 kernel: IPMI System Interface driver version  
v32, KCS version v32, SMIC version v32, BT version v32
Aug  2 08:45:04 vsh1 kernel: ipmi_si: Found SMBIOS-specified state  
machine at I/O address 0xca8
Aug  2 08:45:04 vsh1 kernel: ipmi_si: Unable to find any System  
Interface(s)
Aug  2 08:45:04 vsh1 lsb_log_message:  failed
Aug  2 08:48:08 vsh1 kernel: ipmi message handler version v32
Aug  2 08:48:08 vsh1 kernel: IPMI System Interface driver version  
v32, KCS version v32, SMIC version v32, BT version v32
Aug  2 08:48:08 vsh1 kernel: ipmi_si: Trying "kcs" at memory address  
0xca8
Aug  2 08:48:08 vsh1 kernel: Unable to handle kernel NULL pointer  
dereference at virtual address 00000ca8
Aug  2 08:48:08 vsh1 kernel:  printing eip:
Aug  2 08:48:08 vsh1 kernel: f4c7ce86
Aug  2 08:48:08 vsh1 kernel: *pde = 00000000
Aug  2 08:48:08 vsh1 kernel: Oops: 0000 [#1]
Aug  2 08:48:08 vsh1 kernel: SMP
Aug  2 08:48:08 vsh1 kernel: Modules linked in: ipmi_si  
ipmi_msghandler sg mptctl slm_dmprst vzrst iptable_nat vzcpt  
ip_conntrack slm_kill slm_nofork slm_core slm_if vztable  
vztable_trace ip_vzredir vzredir vzcom$
Aug  2 08:48:08 vsh1 kernel: CPU:    0, VCPU: 0:0
Aug  2 08:48:08 vsh1 kernel: EIP:    0060:[<f4c7ce86>]    Tainted:  P
Aug  2 08:48:08 vsh1 kernel: EFLAGS: 00010202   (2.6.8-022stab067.1-smp)
Aug  2 08:48:08 vsh1 kernel: EIP is at mem_setup+0x16/0xa0 [ipmi_si]
Aug  2 08:48:08 vsh1 kernel: eax: f3fb2680   ebx: 00000ca8   ecx:  
000f4240   edx: 000f4240
Aug  2 08:48:08 vsh1 kernel: esi: f3fb2680   edi: 000000d0   ebp:  
00000000   esp: f10d0f40
Aug  2 08:48:08 vsh1 kernel: ds: 007b   es: 007b   ss: 0068
Aug  2 08:48:08 vsh1 kernel: Process modprobe (pid: 10941, veid=0,  
threadinfo=f10d0000 task=f1000140)
Aug  2 08:48:08 vsh1 kernel:        f3fb26b0 f10d0000 c0488600  
00000000 c0489e44 f3fb2680 c0489e60 f4c82b00
Aug  2 08:48:08 vsh1 kernel:        00000000 c0489e44 f4b1d0d4  
00000000 f4c82b00 c0489e60 f4c82900 f10d0000
Aug  2 08:48:08 vsh1 kernel: Call Trace:
Aug  2 08:48:08 vsh1 kernel:  [<f4c7ded7>] init_one_smi+0x117/0x560  
[ipmi_si]
Aug  2 08:48:09 vsh1 kernel:  [<f4b1d0d4>] init_ipmi_si+0xd4/0x235  
[ipmi_si]
Aug  2 08:48:09 vsh1 kernel:  [<c01471b0>] sys_init_module+0x120/0x220
Aug  2 08:48:09 vsh1 kernel:  [<c040bd6f>] syscall_call+0x7/0xb
Aug  2 08:48:09 vsh1 kernel: Code: 8b 03 85 c0 75 14 ba ed ff ff ff  
8b 5c 24 10 89 d0 8b 74 24
Aug  2 08:49:41 vsh1 kernel: ipmi device interface version v32
Aug  2 08:49:56 vsh1 lsb_log_message:  succeeded
Aug  2 08:52:17 vsh1 kernel: IPMI watchdog driver version v32

----------------

Even with that above, I get the following:

[root at vsh1 dev]# ipmitool sdr list full -vvv
Querying SDR for sensor list
Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0:  
No such file or directory
Get Device ID command failed
Unable to open SDR for reading

All I need to know is why that warning light is blinking.  Can some  
one help?

--

Jesse Proudman,  Blue Box Group, LLC



More information about the Linux-PowerEdge mailing list