Debian OMSA

Sean McAvoy sean.mcavoy at megawheels.com
Tue May 18 15:53:00 CDT 2004


Well this is quite odd then. Is anyone successfully running the latest 
OMSA on Debian?
And if so, what kernel (from where) have you had success with?
Thanks



On 18-May-04, at 4:41 PM, <Abhay_Salunke at Dell.com> wrote:

> local_bh_enable() macro is used by another kernel macro
> spin_unlock_bh().
> which is used up by the esm.o driver kernel function. If the
> local_bh_enable() is defined then I dont see any reason why it wont
> work.
>
> Abhay
>
> -----Original Message-----
> From: Sean McAvoy [mailto:sean.mcavoy at megawheels.com]
> Sent: Tuesday, May 18, 2004 2:09 PM
> To: Salunke, Abhay
> Cc: linux-poweredge at dell.com
> Subject: Re: Debian OMSA
>
>
> I found the file in /include/asm/ which is symlinked to
> /include/asm-i386
>
>
>
>
> On 18-May-04, at 3:02 PM, <Abhay_Salunke at Dell.com> wrote:
>
>> where is it located on your machine?
>> It usually is in /include/asm asm is a softlink pointing to
> appropriate
>> asm-XXXX directory which has the file.
>> Abhay Salunke
>>
>> -----Original Message-----
>> From: Sean McAvoy [mailto:sean.mcavoy at megawheels.com]
>> Sent: Tuesday, May 18, 2004 1:57 PM
>> To: Salunke, Abhay
>> Cc: <linux-poweredge at dell.com>
>> Subject: Re: Debian OMSA
>>
>>
>> Hello,
>> Thank you for your reply. I located the softirq.h file and it does
>> contain
>> --CUT--
>> #define local_bh_enable()
>> do {
>> \
>>          unsigned int *ptr = &local_bh_count(smp_processor_id());
>>
>> \
>>
>>
>> \
>>          barrier();
>>
>> \
>>          if (!--*ptr)
>>
>> \
>>                  __asm__ __volatile__ (
>>
>> \
>>                          "cmpl $0, -8(%0);"
>>
>> \
>>                          "jnz 2f;"
>>
>> \
>>                          "1:;"
>>
>> \
>>
>>
>> \
>>                          LOCK_SECTION_START("")
>>
>> \
>>                          "2: pushl %%eax; pushl %%ecx; pushl %%edx;"
>>
>> \
>>                          "call %c1;"
>>
>> \
>>                          "popl %%edx; popl %%ecx; popl %%eax;"
>>
>> \
>>                          "jmp 1b;"
>>
>> \
>>                          LOCK_SECTION_END
>>
>> \
>>
>>
>> \
>>                  : /* no output */
>>
>> \
>>                  : "r" (ptr), "i" (do_softirq)
>>
>> \
>>                  /* no registers clobbered */ );
>>
>> \
>> } while (0)
>> --CUT--
>>
>> Can you offer any further direction in how I might resolve this?
>> Thanks.
>>
>>
>>
>> On 18-May-04, at 2:27 PM, <Abhay_Salunke at Dell.com> wrote:
>>
>>> local_bh_enable() is a macro defined in the linux kernel and is
>>> specific
>>> to the CPU arch type for e.g. for I386 it is defined in the
>>> /include/asm-i386/softirq.h file.
>>> I think the OMSA DKS build is not able to find that macro and thinks
>> it
>>> is a function call and builds without any errors. This causes a
>> failure
>>> during the load time as the symbol for local_bh_enable does not
>> exists.
>>> Please check if the kernel source has the softirq.h and defines the
>>> local_bh_enable macro.
>>> Abhay Salunke
>>>
>>> -----Original Message-----
>>> From: linux-poweredge-admin at dell.com
>>> [mailto:linux-poweredge-admin at dell.com]On Behalf Of Sean McAvoy
>>> Sent: Tuesday, May 18, 2004 10:57 AM
>>> To: linux-poweredge at dell.com
>>> Subject: Debian OMSA
>>>
>>>
>>> Hello,
>>> I am attempting to get OMSA running on Debian. I've run into a
> problem
>>> that has been encountered on the list before (titled "OMSA :
>> unresolved
>>> symbol local_bh_enable) , but there doesn't seem to be a solution.
>>> It is mentioned in the thread that using backports.org's kernels
>>> (2.4.24 and 2.4.25) solved the issue.
>>> I've used both 2.4.25 from backports.org as well as 2.4.26 from
> Debian
>>> (unstable), no luck with either.
>>> I get the messages below:
>>> Setting up dellomsa-drivers (4.120-3925) ...
>>>
>>> Building device driver for running kernel:                 [OK]
>>>
>>> Loading Server Administrator Device Drivers:               [FAILED]
>>>
>>> Running kernel is not supported.
>>> See Dynamic Kernel Support in the Server Administrator readme.txt
>> file.
>>>
>>> Run rpm using the -e option to clean up the RPM database. Enter:
>>> rpm -e dellomsa-drivers-4.120-3924
>>>
>>> dellomsa-drivers-4.120-3924.i386.rpm: Upgrade was NOT successful!
>> ERROR
>>> 44
>>>
>>> dpkg: error processing dellomsa-drivers (--configure):
>>>   subprocess post-installation script returned error exit status 44
>>> Errors were encountered while processing:
>>>   dellomsa-drivers
>>> E: Sub-process /usr/bin/dpkg returned an error code (1)
>>>
>>> ouput from `modprobe esm`:
>>> unresolved symbol local_bh_enable
>>>
>>> Any suggestions as to why it's not working?
>>> Thanks.
>>>
>>> Sean McAvoy
>>> Network Analyst
>>> Megawheels Technologies Inc.
>>>
>>> Phone:	416.360-8211 x242
>>> Fax:		416.360.1403
>>> Cell:	416.616.6599
>>>
>>> _______________________________________________
>>> Linux-PowerEdge mailing list
>>> Linux-PowerEdge at dell.com
>>> http://lists.us.dell.com/mailman/listinfo/linux-poweredge
>>> Please read the FAQ at http://lists.us.dell.com/faq or search the
> list
>>> archives at http://lists.us.dell.com/htdig/
>>>
>> Sean McAvoy
>> Network Analyst
>> Megawheels Technologies Inc.
>>
>> Phone:	416.360-8211 x242
>> Fax:		416.360.1403
>> Cell:		416.616.6599
>>
>>
> Sean McAvoy
> Network Analyst
> Megawheels Technologies Inc.
>
> Phone:	416.360-8211 x242
> Fax:		416.360.1403
> Cell:		416.616.6599
>
>
Sean McAvoy
Network Analyst
Megawheels Technologies Inc.

Phone:	416.360-8211 x242
Fax:		416.360.1403
Cell:		416.616.6599




More information about the Linux-PowerEdge mailing list