[openib-general] ofa_1_2_kernel 20070203-0200 daily build status

2007-02-03 Thread vlad
This email was generated automatically, please do not reply


Common build parameters:  --with-ipoib-mod --with-sdp-mod --with-srp-mod 
--with-user_mad-mod --with-user_access-mod --with-mthca-mod --with-core-mod 
--with-addr_trans-mod --with-cxgb3-mod 

Passed:
Passed on i686 with 2.6.15-23-server
Passed on i686 with linux-2.6.19
Passed on i686 with linux-2.6.17
Passed on i686 with linux-2.6.16
Passed on i686 with linux-2.6.15
Passed on i686 with linux-2.6.18
Passed on i686 with linux-2.6.14
Passed on i686 with linux-2.6.12
Passed on i686 with linux-2.6.13
Passed on x86_64 with linux-2.6.19
Passed on x86_64 with linux-2.6.17
Passed on ia64 with linux-2.6.18
Passed on powerpc with linux-2.6.17
Passed on x86_64 with linux-2.6.15
Passed on powerpc with linux-2.6.19
Passed on x86_64 with linux-2.6.18
Passed on x86_64 with linux-2.6.14
Passed on x86_64 with linux-2.6.12
Passed on x86_64 with linux-2.6.16
Passed on x86_64 with linux-2.6.13
Passed on ppc64 with linux-2.6.19
Passed on powerpc with linux-2.6.18
Passed on ia64 with linux-2.6.19
Passed on powerpc with linux-2.6.13
Passed on ppc64 with linux-2.6.12
Passed on ppc64 with linux-2.6.14
Passed on powerpc with linux-2.6.16
Passed on powerpc with linux-2.6.15
Passed on powerpc with linux-2.6.12
Passed on ia64 with linux-2.6.16
Passed on ppc64 with linux-2.6.16
Passed on powerpc with linux-2.6.14
Passed on ppc64 with linux-2.6.15
Passed on ppc64 with linux-2.6.17
Passed on ppc64 with linux-2.6.13
Passed on ia64 with linux-2.6.13
Passed on ppc64 with linux-2.6.18
Passed on ia64 with linux-2.6.12
Passed on ia64 with linux-2.6.17
Passed on ia64 with linux-2.6.14
Passed on ia64 with linux-2.6.15

Failed:
Build failed on ia64 with linux-2.6.16.21-0.8-default
Log:
/home/vlad/tmp/ofa_1_2_kernel-20070203-0200_linux-2.6.16.21-0.8-default_ia64_check/drivers/infiniband/core/addr.c:380:
 error: implicit declaration of function ‘register_netevent_notifier’
/home/vlad/tmp/ofa_1_2_kernel-20070203-0200_linux-2.6.16.21-0.8-default_ia64_check/drivers/infiniband/core/addr.c:
 In function ‘addr_cleanup’:
/home/vlad/tmp/ofa_1_2_kernel-20070203-0200_linux-2.6.16.21-0.8-default_ia64_check/drivers/infiniband/core/addr.c:386:
 error: implicit declaration of function ‘unregister_netevent_notifier’
make[4]: *** 
[/home/vlad/tmp/ofa_1_2_kernel-20070203-0200_linux-2.6.16.21-0.8-default_ia64_check/drivers/infiniband/core/addr.o]
 Error 1
make[3]: *** 
[/home/vlad/tmp/ofa_1_2_kernel-20070203-0200_linux-2.6.16.21-0.8-default_ia64_check/drivers/infiniband/core]
 Error 2
make[2]: *** 
[/home/vlad/tmp/ofa_1_2_kernel-20070203-0200_linux-2.6.16.21-0.8-default_ia64_check/drivers/infiniband]
 Error 2
make[1]: *** 
[_module_/home/vlad/tmp/ofa_1_2_kernel-20070203-0200_linux-2.6.16.21-0.8-default_ia64_check]
 Error 2
make[1]: Leaving directory 
`/home/vlad/kernel.org/ia64/linux-2.6.16.21-0.8-default'
make: *** [kernel] Error 2
--

___
openib-general mailing list
openib-general@openib.org
http://openib.org/mailman/listinfo/openib-general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general

[openib-general] OpenIB management libraries release 1.0.2

2007-02-03 Thread Hal Rosenstock
http://www.openfabrics.org/~halr/

md5sum
b9b4bdf899f1d0ff15e06915cd846a3a  libibcommon-1.0.2.tar.gz
2af3ff7e38a1f49fb7514660a9991c89  libibmad-1.0.2.tar.gz
7d7690abfe9b08c8240fbf0157653b90  libibumad-1.0.2.tar.gz




___
openib-general mailing list
openib-general@openib.org
http://openib.org/mailman/listinfo/openib-general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general



Re: [openib-general] Multicast join group failure prevents IPoIB performing

2007-02-03 Thread Shirley Ma





According to IPoIB RFC4391 section 5, once IPoIB broadcast group has been
joined, the IPoIB link should be UP, since it's ready for data transfer,
the interface should be able to run for broadcast and unicast, do not need
to wait for all multicast join successfully. Here is the patch to allow
IPoIB interface running without waiting for all multicast join succesful,
like all host group multicast join  Here is the patch:

diff -urpN ipoib/ipoib_multicast.c ipoib-patch/ipoib_multicast.c
--- ipoib/ipoib_multicast.c   2006-11-29 13:57:37.0 -0800
+++ ipoib-patch/ipoib_multicast.c   2007-02-03 00:52:23.0 -0800
@@ -566,6 +566,7 @@ void ipoib_mcast_join_task(void *dev_ptr

  if (!test_bit(IPOIB_MCAST_FLAG_ATTACHED, priv-broadcast-flags)) {
ipoib_mcast_join(dev, priv-broadcast, 0);
+   netif_carrier_on(dev);
return;
  }

@@ -599,7 +600,6 @@ void ipoib_mcast_join_task(void *dev_ptr
  ipoib_dbg_mcast(priv, successfully joined all multicast groups\n);

  clear_bit(IPOIB_MCAST_RUN, priv-flags);
- netif_carrier_on(dev);
 }

 int ipoib_mcast_start_thread(struct net_device *dev)

(See attached file: multicast.patch)

http://www.rfc-editor.org/rfc/rfc4391.txt

5.  Setting Up an IPoIB Link

   The broadcast-GID, as defined in the previous section, MUST be set up
   for an IPoIB subnet to be formed.  Every IPoIB interface MUST
   FullMember join the IB multicast group defined by the broadcast-
   GID.  This multicast group will henceforth be referred to as the
   broadcast group.  The join operation returns the MTU, the Q_Key, and
   other parameters associated with the broadcast group.  The node then
   associates the parameters received as a result of the join operation
   with its IPoIB interface.  The broadcast group also serves to provide
   a link-layer broadcast service for protocols like ARP, net-directed,
   subnet-directed, and all-subnets-directed broadcasts in IPv4 over IB
   networks.

   The join operation is successful only if the Subnet Manager (SM)
   determines that the joining node can support the MTU registered with
   the broadcast group [RFC4392] ensuring support for a common link MTU.
   The SM also ensures that all the nodes joining the broadcast-GID have
   paths to one another and can therefore send and receive unicast
   packets.  It further ensures that all the nodes do indeed form a
   multicast tree that allows packets sent from any member to be
   replicated to every other member.   Thus, the IPoIB link is formed by
   the IPoIB nodes joining the broadcast group.  There is no physical
   demarcation of the IPoIB link other than that determined by the
   broadcast group membership.


Shirley Ma




   
 Shirley   
 Ma/Beaverton/IBM@ 
 IBMUS  To
 Sent by:  openib-general@openib.org   
 openib-general-bo  cc
 [EMAIL PROTECTED]  
   Subject
   [openib-general] Multicast join 
 02/02/07 08:58 PM group failure prevents IPoIB
   performing  
   
   
   
   
   
   




When bringing IPoIB interface up, I hit default group multicast join
failure. (This could be fixed in SM set up?)
ib0: multicast join failed for , status -22
Then the interface was UP but not RUNNING. So the nodes couldn't ping each
other. I think the right behavior of the interface should be UP and RUNNING
even with some multicast join failure. I would like to provide a patch if
there is no problem. Please advise.

Thanks
Shirley Ma___
openib-general mailing list
openib-general@openib.org
http://openib.org/mailman/listinfo/openib-general

To unsubscribe, please visit
http://openib.org/mailman/listinfo/openib-general




multicast.patch
Description: Binary data
___
openib-general mailing list
openib-general@openib.org
http://openib.org/mailman/listinfo/openib-general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general

[openib-general] [Bug 334] Problems with build OFED-1.1.1-ib_local_sa

2007-02-03 Thread bugzilla-daemon
https://bugs.openfabrics.org/show_bug.cgi?id=334





--- Comment #14 from [EMAIL PROTECTED]  2007-02-03 23:07 ---
(In reply to comment #13)
 I want to ask someone how I can apply the patch during build.sh run script?
 As I know when I run build.sh my old files with patch always update throught
 run rpm -i openib-1.1.src.rpm. How I can do it (apply my patches) or I need to
 wait new releases?
 

(In reply to comment #11)
 (In reply to comment #10)
  What is the output of uname -r ? This is VERY important. Also, can you run 
 `cat /etc/issue` and send the results?
  
 
 As you can see my first message I wrote the my machine configuration:
 The machine configuration:
 Kernel: Linux 2.6.16.21-0.8-smp #1 SMP Mon Jul 3 18:25:39 UTC 2006 x86_64
 x86_64 x86_64 GNU/Linux
 OS: SUSE Linux Enterprise Server 10 (x86_64)
 gcc version: gcc (GCC) 4.1.0 (SUSE Linux)
 
 Unfortunately my machine didn't have the version of Linux in /etc/issue 
 because
 it is not right by IT requrements. 

Why? OFED 1.1 expects that you don't change this file. This is how SuSE ships
it with SLES 10.

I have saw the ofed_scripts/configure file
 and I saw that for right choice of patches configure needed the file
 /etc/issue. I think that not good idea because first of all need to run
 command:  cat /etc/*release* and find the version Linux in this file and after
 this check (if neccessary) file /etc/issue
 

I don't understand the problem.


-- 
Configure bugmail: https://bugs.openfabrics.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

___
openib-general mailing list
openib-general@openib.org
http://openib.org/mailman/listinfo/openib-general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general



[openib-general] [Bug 334] Problems with build OFED-1.1.1-ib_local_sa

2007-02-03 Thread bugzilla-daemon
https://bugs.openfabrics.org/show_bug.cgi?id=334


[EMAIL PROTECTED] changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution||INVALID




--- Comment #15 from [EMAIL PROTECTED]  2007-02-03 23:14 ---
(In reply to comment #13)
 I want to ask someone how I can apply the patch during build.sh run script?

I don't agree with your patch. It assumes that SLES 10 may be corrupted. OFED
should not try to support this. If you want to use this patch for your own
purposes, just apply it (manually) before running OFED build scripts. OFED's
backport patches mechanism is not suitable for such patches.

 As I know when I run build.sh my old files with patch always update throught
 run rpm -i openib-1.1.src.rpm. How I can do it (apply my patches) or I need to
 wait new releases?
 


-- 
Configure bugmail: https://bugs.openfabrics.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug, or are watching the assignee.

___
openib-general mailing list
openib-general@openib.org
http://openib.org/mailman/listinfo/openib-general

To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general