| To: | Stephen Hemminger <shemminger@xxxxxxxx> |
|---|---|
| Subject: | Re: Hang when testing with AMD64 with Tg3 |
| From: | Nivedita Singhvi <niv@xxxxxxxxxx> |
| Date: | Tue, 05 Oct 2004 07:58:58 -0700 |
| Cc: | Andi Kleen <ak@xxxxxxx>, davem@xxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <1096938308.22947.3.camel@xxxxxxxxxxxxxxxxxxxxx> |
| References: | <1096935071.22155.6.camel@xxxxxxxxxxxxxxxxxxxxx> <20041005001527.GB13106@xxxxxxxxxxxxx> <1096938308.22947.3.camel@xxxxxxxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4.1) Gecko/20031008 |
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.. thanks, Nivedita |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 2.6.9-rc3-mm2] 3c59x: support more ethtool_ops, Jeff Garzik |
|---|---|
| Next by Date: | Re: [PATCH 2.6.9-rc3-mm2] 3c59x: support more ethtool_ops, Steffen Klassert |
| Previous by Thread: | Re: Hang when testing with AMD64 with Tg3, Stephen Hemminger |
| Next by Thread: | Re: Hang when testing with AMD64 with Tg3, Stephen Hemminger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |