Need info on ESM driver and 1950

[Naidu Bollineni]

Thanks for the response.
Our functional needs are - IPMI, Component recognition and failure
reporting, and dmidecode working.

What I didn't report last time was about dmidecode failing on 1950 with
the following set of errors repeatedly: I hope this can give any clues.

	DMI 2.4 present.
	62 structures occupying 3131 bytes.
	DMI table at 0xCFFBC000.
	dmi: read: Illegal seek

I am hoping IPMI will work as openIPMI says with PE1950. I need
dmidecode to work, and I am not sure why it is failing. And I need to
know how to track all components and their failures.

Thanks,
Naidu Bollineni
Senior Member Technical Staff
Kazeon Systems
naidu at kazeon.com
www.kazeon.com

-----Original Message-----
From: Matt Domsch [mailto:Matt_Domsch at dell.com] 
Sent: Monday, August 28, 2006 6:13 AM
To: Naidu Bollineni
Cc: Adam Williams; linux-poweredge at dell.com
Subject: Re: Need info on ESM driver and 1950

On Mon, Aug 28, 2006 at 12:20:55AM -0700, Naidu Bollineni wrote:
>    Wondering if there is any info on esm driver module(source)
supplied by
>    DELL, and if I can get hold of
>    the latest copy which could work on 1950.
> 
>    Currently I have this module that is running on 1850s with RH9
flavor, but
>    when I use the same on 1950,
>    it is not able to load, and is crashing in init time. (rest of the
system
>    is functioning, but lsmod shows esm.o in initializing state
forever.
> 
>    A brief look at the crash stakc is below:
> 
>     [<f8af346d>] .rodata.str1.1+0x0/0xe7 [esm]
>     [<f8af65e0>] esm_fops+0x0/0x48 [esm]
>     [<f8ae64e5>] init_module+0x5/0x10 [esm]
>     [<c01200b4>] sys_init_module+0x5f4/0x760 [kernel]
>     [<f8ae4060>] EsmIsDevAttnCmd+0x0/0x3c [esm]
> 
>    I am suspecting this is to support the SMBUS, and IPMI eventually.

Starting with OpenManage 5.0 and the PowerEdge x9xx servers, Dell no
longer has a driver called 'esm.o'.  Instead, there are 3 completely
open source (GPL licensed) kernel modules which are included in the
standard kernel.org kernels, and/or bundled with OMSA.  Those are
called 'openipmi' which accesses the IPMI controller, 'dell_rbu' for
BIOS updates, and 'dcdbas' for making proper Systems Management
Interrupt calls into the BIOS.  So, there's no esm.o driver at all
anymore.

What are you trying to do, and can one of the above 3 drivers do it?

Thanks,
Matt

-- 
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com