Davis, Arlin R wrote:
Looks like the spec file does the (for Fedora anyway) right thing and
includes a dist tag on the release, aka:
Release:1%{?dist}
which on Fedora 9 works out to be 1.fc9 unless you undefine the dist
macro. I'm guessing the install script doesn't know about the d
>
>Looks like the spec file does the (for Fedora anyway) right thing and
>includes a dist tag on the release, aka:
>
>Release: 1%{?dist}
>
>which on Fedora 9 works out to be 1.fc9 unless you undefine the dist
>macro. I'm guessing the install script doesn't know about the dist
>macro and i
There's at least one warning in OFED that Betsy mentioned today about
sched_setaffinity():
ch3_smp_progress.c:2427: warning: passing argument 3 of
'sched_setaffinity' from incompatible pointer type
Be advised that the prototypes for sched_setaffinity() and
sched_getaffinity() have ch
On Mon, Sep 08, 2008 at 10:08:29AM -0400, Jonathan Perkins wrote:
> On Mon, Sep 08, 2008 at 04:20:22PM +0300, Vladimir Sokolovsky wrote:
> > Jonathan Perkins wrote:
> >> Vlad:
> >> I've uploaded a new source rpm for mvapich2-1.2. It is identified
> >> latest.txt within the ofed_1_4 directory. Thi
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft CDO for Microsoft Exchange
VERSION:2.0
BEGIN:VTIMEZONE
TZID:GMT -0500 (Standard) / GMT -0400 (Daylight)
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=11;BYDAY=1SU
END:STANDARD
B
BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft CDO for Microsoft Exchange
VERSION:2.0
BEGIN:VEVENT
DTSTAMP:20080908T154300Z
DTSTART:20080915T16Z
SUMMARY:OFED v1.4 weekly teleconference
UID:04008200E00074C5B7101A82E00830D775F9A711C901000
010009F178F6870321140A394A9D
As of this meeting, we're starting weekly OFED teleconferences until
v1.4 is released (with the exception of Sep 29, which is New Year's
Eve in Israel). I'll shortly be sending 2 Outlook invites:
- A single meeting for 15 Sep
- Weekly meetings 6-27 Oct
This will mesh with the already-existi
Vlad,
1. What is the distro where you this error ?
2. > Parsing Configuration file [FAILED]
This is most likely because of no configuration file
(/etc/infiniband/qlgc_vnic.cfg)
being present.
When you see this, do you see a message in /var/log/messages saying
"/u
Ram,
There are following errors while loading VNIC (/etc/init.d/openibd start):
Starting QLogic Virtual NIC[ OK ]
Parsing Configuration file [FAILED]
Or
Parsing Configuration file/etc/init.d/qlgc_vnic: line 354: udevstart:
command
On Mon, Sep 08, 2008 at 04:20:22PM +0300, Vladimir Sokolovsky wrote:
> Jonathan Perkins wrote:
>> Vlad:
>> I've uploaded a new source rpm for mvapich2-1.2. It is identified
>> latest.txt within the ofed_1_4 directory. This upload addresses the
>> ppc64 issue reported on bugzilla.
>>
>
> Hi Jonath
Jonathan Perkins wrote:
Vlad:
I've uploaded a new source rpm for mvapich2-1.2. It is identified
latest.txt within the ofed_1_4 directory. This upload addresses the
ppc64 issue reported on bugzilla.
Hi Jonathan,
I see that mvapich2-1.2rc2-4.src.rpm rpmbuild still fails on PPC64.
configure: e
This is the agenda for the OFED meeting today (8-Sep):
1. RC1 status:
We have build RC1 today and will run testing today - should be
out tomorrow.
2. Missing features for RC2:
- NFS-RDMA over RHEL 5.1
- OSM: Cashed routing
3. Bug list review:
*bug_id**bug_severi
On Thu, Sep 04, 2008 at 10:38:34AM -0400, Doug Ledford wrote:
> First, in kernel_patches/backports/2.6.18-EL5.1 there are two patches
> that go together, they are the ipoib-0400... and ipoib-0410... Together
> they switch ipoib to use dev_set_mtu and rtnl_lock/rtnl_unlock.
> Unfortunately, these
13 matches
Mail list logo
