Re: broken re(4)

2008-06-12 Thread Gerrit Kühn
On Thu, 12 Jun 2008 16:01:26 +0900 Pyun YongHyeon <[EMAIL PROTECTED]> wrote about Re: broken re(4): PY> > I already did simple benchmarking by using "dd if=/dev/zero PY> > of=file" which gave me several 10s of MByte/s under all PY> > circumstances. Can you

Re: broken re(4)

2008-06-12 Thread Pyun YongHyeon
On Thu, Jun 12, 2008 at 08:58:10AM +0200, Gerrit K?hn wrote: > On Thu, 12 Jun 2008 12:22:28 +0900 Pyun YongHyeon <[EMAIL PROTECTED]> wrote > about Re: broken re(4): > > PY> Before checking performance of network controller you had to rule > PY> out other factor

Re: broken re(4)

2008-06-11 Thread Gerrit Kühn
On Thu, 12 Jun 2008 12:22:28 +0900 Pyun YongHyeon <[EMAIL PROTECTED]> wrote about Re: broken re(4): PY> Before checking performance of network controller you had to rule PY> out other factors like disk I/O. Use one of benchmark programs in PY> ports/benchmark. I already did simp

Re: broken re(4)

2008-06-11 Thread Pyun YongHyeon
On Wed, Jun 11, 2008 at 09:24:57AM +0200, Gerrit K?hn wrote: > On Tue, 10 Jun 2008 20:43:04 +0200 Daniele Bastianini > <[EMAIL PROTECTED]> wrote about Re: broken re(4): > > DB> > - copying large files (more than some 100MB) via ssh/scp drops the > DB> > co

Re: broken re(4)

2008-06-11 Thread Gerrit Kühn
On Wed, 11 Jun 2008 17:26:29 +0200 (CEST) Oliver Fromme <[EMAIL PROTECTED]> wrote about Re: broken re(4): OF> > On the other hand, I have not been able to get more than about OF> > 10MByte/s through the interfaces of this particular system. I have OF> > 1GBit-netwo

Re: broken re(4)

2008-06-11 Thread Oliver Fromme
Gerrit Kühn wrote: > On the other hand, I have not been able to get more than about 10MByte/s > through the interfaces of this particular system. I have 1GBit-networking > equipment, and the other systems (which are used as router) have no > problem doing a throughput of >20MB/s. Even bonding t

Re: broken re(4)

2008-06-11 Thread Gerrit Kühn
On Tue, 10 Jun 2008 20:43:04 +0200 Daniele Bastianini <[EMAIL PROTECTED]> wrote about Re: broken re(4): DB> > - copying large files (more than some 100MB) via ssh/scp drops the DB> > connection due to "corrupted MAC on input": DB> > Disconnecting: Corrupted MAC o

Re: broken re(4)

2008-06-10 Thread Pyun YongHyeon
On Tue, Jun 10, 2008 at 09:26:44PM +0200, Daniele Bastianini wrote: > > Il giorno 27/mag/08, alle ore 16:52, Gerrit K?hn ha scritto: > > >Hi folks, > > > >I have four identical ITX boards from Jetway here, each having two > >re(4) > >onboard nics: > > > >[EMAIL PROTECTED]:0:9:0: class

Re: broken re(4)

2008-06-10 Thread Daniele Bastianini
Il giorno 27/mag/08, alle ore 16:52, Gerrit Kühn ha scritto: Hi folks, I have four identical ITX boards from Jetway here, each having two re(4) onboard nics: [EMAIL PROTECTED]:0:9:0: class=0x02 card=0x10ec16f3 chip=0x816710ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor'

Re: broken re(4)

2008-05-30 Thread Wilko Bulte
Quoting Gerrit Khn, who wrote on Fri, May 30, 2008 at 02:47:59PM +0200 .. > On Fri, 30 May 2008 13:49:24 +0200 Wilko Bulte <[EMAIL PROTECTED]> > wrote about Re: broken re(4): > > WB> > Typing "pci riser card jumper" in Google will give you > WB> > many

Re: broken re(4)

2008-05-30 Thread Gerrit Kühn
On Fri, 30 May 2008 14:03:08 +0900 Pyun YongHyeon <[EMAIL PROTECTED]> wrote about Re: broken re(4): PY> Since you're running this patch would you post dmesg output related PY> with re(4)? Also please post the output of "devinfo -rv | grep PY> oui". Here is my ou

Re: broken re(4)

2008-05-30 Thread Gerrit Kühn
On Fri, 30 May 2008 13:44:43 +0200 (CEST) Oliver Fromme <[EMAIL PROTECTED]> wrote about Re: broken re(4): OF> That rings a bell ... OF> I remember reports of riser cards that apparently changed OF> the timing on the PCI bus so they were only marginally OF> compliant with the

Re: broken re(4)

2008-05-30 Thread Gerrit Kühn
On Fri, 30 May 2008 13:49:24 +0200 Wilko Bulte <[EMAIL PROTECTED]> wrote about Re: broken re(4): WB> > Typing "pci riser card jumper" in Google will give you WB> > many more pages with interesting (or frightening) stuff WB> > to read. WB> Well, if you know ho

Re: broken re(4)

2008-05-30 Thread Gerrit Kühn
On Fri, 30 May 2008 13:44:43 +0200 (CEST) Oliver Fromme <[EMAIL PROTECTED]> wrote about Re: broken re(4): OF> > Talking about this controller: This is also the only board I am OF> > using with PCI cards (and thus with a PCI riser) at all. I remember OF> > vaguely t

Re: broken re(4)

2008-05-30 Thread Wilko Bulte
Quoting Oliver Fromme, who wrote on Fri, May 30, 2008 at 01:44:43PM +0200 .. > Gerrit Kühn wrote: > > As Oliver already suggested, I will take out the controller and see what > > happens then. > > > > Talking about this controller: This is also the only board I am using with > > PCI cards (an

Re: broken re(4)

2008-05-30 Thread Oliver Fromme
Gerrit Kühn wrote: > As Oliver already suggested, I will take out the controller and see what > happens then. > > Talking about this controller: This is also the only board I am using with > PCI cards (and thus with a PCI riser) at all. I remember vaguely that I > had a few problems getting

Re: broken re(4)

2008-05-30 Thread Dimitry Andric
On 2008-05-30 07:03, Pyun YongHyeon wrote: > Since you're running this patch would you post dmesg output related > with re(4)? Also please post the output of "devinfo -rv | grep > oui". dmesg -- Copyright (c) 1992-2008 The FreeBSD

Re: broken re(4)

2008-05-29 Thread Pyun YongHyeon
On Thu, May 29, 2008 at 01:10:48PM +0200, Dimitry Andric wrote: > On 2008-05-29 11:58, Gerrit K?hn wrote: > > Can I do anything else? Is the newer patch (from yesterday) in your > > directory above worth giving a try? > > FYI, that patch doesn't compile, due to a typo... Fix below: > > ---

Re: broken re(4)

2008-05-29 Thread Gerrit Kühn
On Thu, 29 May 2008 19:09:12 +0200 Dimitry Andric <[EMAIL PROTECTED]> wrote about Re: broken re(4): DA> > I have 5 ITX systems, each with 2 re-NICs, and only one is behaving DA> > strange. DA> Just as a data point, my ITX board is a JetWay J7F4K1G2E. The ones I have are J

Re: broken re(4)

2008-05-29 Thread Gerrit Kühn
On Thu, 29 May 2008 18:52:55 +0200 (CEST) Oliver Fromme <[EMAIL PROTECTED]> wrote about Re: broken re(4): OF> In that case I would suspect that the one piece of hardware OF> that is misbehaving is broken and needs to be replaced. I agree. I just do not know yet which part is broken.

Re: broken re(4)

2008-05-29 Thread Dimitry Andric
On 2008-05-29 17:13, Gerrit Kühn wrote: > On Thu, 29 May 2008 13:10:48 +0200 Dimitry Andric <[EMAIL PROTECTED]> > Meanwhile I have set up two more machines. Now I have 5 ITX systems, each > with 2 re-NICs, and only one is behaving strange. Just as a data point, my ITX board is a JetWay J7F4K1G2E.

Re: broken re(4)

2008-05-29 Thread Oliver Fromme
Gerrit Kühn wrote: > Meanwhile I have set up two more machines. Now I have 5 ITX systems, > each with 2 re-NICs, and only one is behaving strange. In that case I would suspect that the one piece of hardware that is misbehaving is broken and needs to be replaced. > The only hardware thing that

RE: broken re(4)

2008-05-29 Thread Dewayne Geraghty
>-Original Message- >From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gerrit Kühn >Sent: Thursday, 29 May 2008 7:58 PM >To: Gerrit Kühn >Cc: [EMAIL PROTECTED]; freebsd-stable@freebsd.org >Subject: Re: broken re(4) > >On Wed, 28 May 2008 17:56:10 +

Re: broken re(4)

2008-05-29 Thread Michael Proto
Gerrit Kühn wrote: > On Tue, 27 May 2008 11:45:19 -0400 Michael Proto <[EMAIL PROTECTED]> > wrote about Re: broken re(4): > > MP> > Any hints what I should do next to find the culprit? > > MP> I'm running 6.3 on the exact same Jetway board at home, and wh

Re: broken re(4)

2008-05-29 Thread Gerrit Kühn
On Thu, 29 May 2008 13:10:48 +0200 Dimitry Andric <[EMAIL PROTECTED]> wrote about Re: broken re(4): DA> FYI, that patch doesn't compile, due to a typo... Fix below: Thanks, I will try that patch tomorrow. Meanwhile I have set up two more machines. Now I have 5 ITX systems, each

Re: broken re(4)

2008-05-29 Thread Gerrit Kühn
On Thu, 29 May 2008 23:03:01 +1000 "Dewayne Geraghty" <[EMAIL PROTECTED]> wrote about RE: broken re(4): DG> You might try, after rebooting, to physically unplug and replug your DG> networking cables. I already did try that one or twice, without any success. DG> I h

Re: broken re(4)

2008-05-29 Thread Dimitry Andric
On 2008-05-29 11:58, Gerrit Kühn wrote: > Can I do anything else? Is the newer patch (from yesterday) in your > directory above worth giving a try? FYI, that patch doesn't compile, due to a typo... Fix below: --- re.HEAD.20080528.orig 2008-05-29 13:08:15.0 +0200 +++ re.HEAD.20080528

Re: broken re(4)

2008-05-29 Thread Gerrit Kühn
On Wed, 28 May 2008 17:56:10 +0200 Gerrit Kühn <[EMAIL PROTECTED]> wrote about Re: broken re(4): GK> PY> http://people.freebsd.org/~yongari/re/re.HEAD.20080519 GK> Somehow the two interfaces seem to interfer with each other. Can I GK> provide further information for fixing

Re: broken re(4)

2008-05-29 Thread Gerrit Kühn
On Tue, 27 May 2008 11:45:19 -0400 Michael Proto <[EMAIL PROTECTED]> wrote about Re: broken re(4): MP> > Any hints what I should do next to find the culprit? MP> I'm running 6.3 on the exact same Jetway board at home, and while I MP> haven't been bitten by the D

Re: broken re(4)

2008-05-28 Thread Gerrit Kühn
On Wed, 28 May 2008 09:28:23 +0900 Pyun YongHyeon <[EMAIL PROTECTED]> wrote about Re: broken re(4): PY> > Any hints what I should do next to find the culprit? PY> There were similiar reports on this issue. It seems that it's very PY> hard to make re(4) work so many RTL8

Re: broken re(4)

2008-05-28 Thread Gerrit Kühn
On Wed, 28 May 2008 09:28:23 +0900 Pyun YongHyeon <[EMAIL PROTECTED]> wrote about Re: broken re(4): PY> > Any hints what I should do next to find the culprit? PY> There were similiar reports on this issue. It seems that it's very PY> hard to make re(4) work so many RTL8

Re: broken re(4)

2008-05-27 Thread Pyun YongHyeon
On Tue, May 27, 2008 at 04:52:32PM +0200, Gerrit K?hn wrote: > Hi folks, > > I have four identical ITX boards from Jetway here, each having two re(4) > onboard nics: > > [EMAIL PROTECTED]:0:9:0: class=0x02 card=0x10ec16f3 chip=0x816710ec > rev=0x10 > hdr=0x00 vendor = 'Realtek Se