From: Stephen Hemminger <shemminger@osdl.org>
To: Nivedita Singhvi <niv@us.ibm.com>
Cc: Andi Kleen <ak@suse.de>, davem@redhat.com, netdev@oss.sgi.com
Subject: Re: Hang when testing with AMD64 with Tg3
Date: Tue, 05 Oct 2004 10:06:15 -0700 [thread overview]
Message-ID: <1096995975.22947.7.camel@localhost.localdomain> (raw)
In-Reply-To: <4162B6B2.6030208@us.ibm.com>
On Tue, 2004-10-05 at 07:58 -0700, Nivedita Singhvi wrote:
> Stephen Hemminger wrote:
> > On Tue, 2004-10-05 at 02:15 +0200, Andi Kleen wrote:
> >
> >>On Mon, Oct 04, 2004 at 05:11:11PM -0700, Stephen Hemminger wrote:
> >>
> >>>Doing simple iperf test on new opteron with tg3 against existing Xeon
> >>>system. I am seeing something wierd, the connection hangs right away.
> >>>Is this a TSO bug.
> >>>
> >>>Sender: BK latest (2.6.9-rc3) Tg3 (XX.YY.250.3)
> >>>Receiver: BK + netdev(jeffm) + dave's latest e100 (XX.YY.1.73)
> >>>
> >>>Both machines are directly connected with a netgear 100mbit switch.
> >>
> >
> > IT ISN'T A NETWORK PROBLEM. The problem is that iperf uses posix
> > pthread mutex's to sychronize and it looks like a futex bug.
>
> might not be a futex bug - check to see if iperf does
> any writes, fflushes, etc, in a signal handler - i.e.
> that its signal handling is thread-safe. glibc now
> makes it a fatal bug..
It doesn't do I/O from signal handler, but the problem goes away when
not compiling with -O2.
prev parent reply other threads:[~2004-10-05 17:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 0:11 Hang when testing with AMD64 with Tg3 Stephen Hemminger
2004-10-05 0:15 ` Andi Kleen
2004-10-05 0:29 ` David S. Miller
2004-10-05 0:41 ` Andi Kleen
2004-10-05 0:47 ` Stephen Hemminger
2004-10-05 1:00 ` Stephen Hemminger
2004-10-05 1:05 ` Stephen Hemminger
2004-10-05 14:58 ` Nivedita Singhvi
2004-10-05 17:06 ` Stephen Hemminger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1096995975.22947.7.camel@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=ak@suse.de \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=niv@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.