[openib-general] [HELP] Encounter Kernel Panic when Add MellanoxHCA Supporting on 2.6.9 Kernel

[Cong, Lenber]

I tried the patches (2.6.12-to-2.6.9, not svn backport) on an EM64T desktop (without HCA card). The kernel can be installed successfully.

I still can't reboot the kernel on Xeon SMP server, even with the new patches (svn backport). The same error was encountered.

Then I disabled the option CONFIG_DEBUG_SPINLOCK.
The error message disappeared, but the kernel still can't be booted.

Can I assume it is the problem of HCA card? Or the issue is relative with the SMP platform? So strange.. 

Thanks - Lenber

-----Original Message-----
From: Woodruff, Robert J 
Sent: 2005年5月25日 6:34
To: Cong, Lenber; openib-general at openib.org
Cc: 'Roland Dreier'
Subject: RE: [openib-general] [HELP] Encounter Kernel Panic when Add MellanoxHCA Supporting on 2.6.9 Kernel

Roland wrote,  
>I just tried the latest svn on 2.6.11 with CONFIG_DEBUG_SPINLOCK
>turned on, and I didn't see any problems.  The message

>    driver/infiniband/hw/mthca/mthca_allocator.c: 46: spin_is_locked on 
>uninitialized spinlock: f70f7dac

>is coming from CHECK_LOCK, which is turned on with
>CONFIG_DEBUG_SPINLOCK.  However there should be more traceback
>information printed to the console as well... did that get dumped as
>well?

    Bob> Roland, has anything been fixed since the 2.6.12 drop in
    Bob> mthca that could account for this panic ?

>Not that I know of...

> - R.

I just installed the 

infiniband-backport-2.6.12-to-2.6.9-kernel-fixups-01.diff   
infiniband-backport-2.6.12-to-2.6.9-openib-drivers-02.diff  
infiniband-backport-2.6.12-to-2.6.9-openib-fixups-03.diff  

backport patches on a couple of old 900Mhz IA32 Xeon boxes 
and was able to build the kernel, load IPoIB and ping another node.
I used the Redhat configuration file /boot/config-2.6.9-5.ELsmp,
did a make oldconfig and selected modules for all of the infiniband drivers.
Then I built and installed the kernel with no problems. 

Maybe it is the platform (I have seen problems in the past with
the BIOS on some platforms being able to map the Mellanox H/W correctly)
or could bad Mellanox H/W cause this ?

Do you have any other platforms that you could try it on ?

woody