Hi,
i have a Intel SE7520JR2 Motherboard running Linux fedora core 4
with 2.6.15 kernel. i have applied the following ipmi patches to the
kernel in the same order.
1. linux-base-2.6.15-v38.0.diff
2. linux-emu-2.6.15-v38.0.diff
3. linux-i2c-2.6.15-v38.0.diff
4. linux-i2c-i801-2.6.15-v38.0.diff
5. linux-smb-2.6.15-v38.0.diff
I am using ipmitool to view sensor values. The problem is ipmitool is
inconsistent. some times it works and some times it doesn't. some times
ipmitool reports "Unable to get SDR info" after a while.
I had ipmi drivers up and running fine on 2.6.13.2. only when i changed
to 2.6.15 i am facing this problem. it would be great if anyone could
help me out.
I see the following when I look at dmesg.
------------------------------------------------------------------------
ipmi message handler version 38.0
ipmi device interface
IPMI SMB Interface driver
ipmi_smb: DMI specifies SSIF @ 0x42
ipmi_smb: DMI specifies slave address at 0x20
invalid operand: 0000 [1]
SMP
CPU 1
Modules linked in: ipmi_smb ipmi_devintf ipmi_msghandler i2c_i801
i2c_core
Pid: 3231, comm: modprobe Not tainted 2.6.15.2 #3
RIP: 0010:[<ffff81003cc8b583>] [<ffff81003cc8b583>]
RSP: 0018:ffff81003d7f9c48 EFLAGS: 00010282
RAX: ffff81003cc8b580 RBX: ffff81003e272080 RCX: 00000000c0000100
RDX: 0000000000000fa1 RSI: ffff81003e272080 RDI: ffffffff8800bcc0
RBP: ffff81003e272080 R08: ffff81003d7f8000 R09: 0000000000000000
R10: ffff810001e139e0 R11: 0000000000000000 R12: ffffffff8800bcc0
R13: ffffffff8800bd40 R14: ffffffff8800bcc0 R15: ffffffff8800c120
FS: 00002aaaaaab93c0(0000) GS:ffffffff805d4880(0000)
knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000003af6c928f0 CR3: 000000003dde9000 CR4: 00000000000006e0
Process modprobe (pid: 3231, threadinfo ffff81003d7f8000, task
ffff81003ef7ef80)
Stack: ffff81003d7f9c50 ffffffff880028e1 0000000000000001
0000000000000001
ffff81003e272080 ffff81003e2720d8 ffffffff8800bd40
ffffffff880032cf
ffff81003c489200 0000000000000020
Call Trace:<ffffffff880028e1>{:i2c_core:i2c_op_done+105}
<ffffffff880032cf>{:i2c_core:i2c_perform_op_wait+407}
<ffffffff803e0dab>{thread_return+0}
<ffffffff88003417>{:i2c_core:i2c_smbus_xfer+152}
<ffffffff8800355a>{:i2c_core:i2c_smbus_read_block_data+47}
<ffffffff8013fc59>{process_timeout+0} <ffffffff8014038b>{msleep
+47}
<ffffffff8801d74b>{:ipmi_smb:smb_found_addr_proc+922}
<ffffffff8801d3b1>{:ipmi_smb:smb_found_addr_proc+0}
<ffffffff8801d3b1>{:ipmi_smb:smb_found_addr_proc+0}
<ffffffff880037f7>{:i2c_core:i2c_probe_address+177}
<ffffffff8800385c>{:i2c_core:i2c_probe+85}
<ffffffff8801d312>{:ipmi_smb:attach_adapter+152}
<ffffffff88002b37>{:i2c_core:i2c_add_driver+155}
<ffffffff88023271>{:ipmi_smb:init_ipmi_smb+625}
<ffffffff801507cc>{sys_init_module+246}
<ffffffff8010f816>{system_call+126}
Code: 3f 00
81 ff ff bb d7 07 00
05 00
00 00
75 04 00
00 00
00 00
RIP
[<ffff81003cc8b583>] RSP <ffff81003d7f9c48>
------------------------------------------------------------------------
Regards
Anupama.
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Openipmi-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openipmi-developer
