On Mon, Aug 30, 2010 at 11:46:20PM +, Thordur I Bjornsson wrote:
Hi Thib!
I have two machines with vr(4) interfaces running 4.7, and I can't seem
to find any problem running ping -f against them.
vr0 at pci0 dev 12 function 0 VIA VT6105 RhineIII rev 0x86: apic 2 int
19 (irq 10),
On 2010/08/30 20:20, Marco Peereboom wrote:
My vr on my firewall hangs for a while until the watchdog kicks it in
the pants every time I push a little traffic through it. I'd love to
see thibs thing go in.
Does thib's diff help this?
On 2010/08/30 23:46, Thordur I Bjornsson wrote:
On Mon, Aug 30, 2010 at 06:46:53PM -0400, Brynet wrote:
Evening,
I have two machines with vr(4) interfaces running 4.7, and I can't seem
to find any problem running ping -f against them.
vr0 at pci0 dev 12 function 0 VIA VT6105
running with this seems to help.
Index: if_vr.c
===
RCS file: /cvs/src/sys/dev/pci/if_vr.c,v
retrieving revision 1.105
diff -u -p -r1.105 if_vr.c
--- if_vr.c 19 May 2010 15:27:35 - 1.105
+++ if_vr.c 31 Aug 2010
Date: Tue, 31 Aug 2010 22:30:42 +0100
From: Stuart Henderson s...@spacehopper.org
running with this seems to help.
Can you try this diff instead?
Index: if_vr.c
===
RCS file: /cvs/src/sys/dev/pci/if_vr.c,v
retrieving
Evening,
I have two machines with vr(4) interfaces running 4.7, and I can't seem
to find any problem running ping -f against them.
vr0 at pci0 dev 12 function 0 VIA VT6105 RhineIII rev 0x86: apic 2 int
19 (irq 10), address 00:19:5b:82:a1:e0
vr0 at pci0 dev 16 function 0 VIA Rhine/RhineII rev
On Mon, Aug 30, 2010 at 06:46:53PM -0400, Brynet wrote:
Evening,
I have two machines with vr(4) interfaces running 4.7, and I can't seem
to find any problem running ping -f against them.
vr0 at pci0 dev 12 function 0 VIA VT6105 RhineIII rev 0x86: apic 2 int
19 (irq 10), address
unless someone fixes mclgeti in this driver in the next 24 hours, this should
go in.
this has my ok on august 31.
On 28/08/2010, at 4:07 AM, Thordur I Bjornsson wrote:
As seen on misc@, and also by myself sometime ago, but I forgot about
it as work got hectic and I was moving.
Anyways,
unless someone fixes mclgeti in this driver in the next 24 hours, this should
go in.
this has my ok on august 31.
It is a very nasty bug.
But we should also remember that machines with vr(4) interfaces
are pretty slow, and benefit tremendously from MCLGETI. So it is
a crying shame to see
As seen on misc@, and also by myself sometime ago, but I forgot about
it as work got hectic and I was moving.
Anyways, vr(4) will not even surivie a few ping -f's, before the pools
become corrupt, this has (obviously) something todo with how MCLGETI
takes and puts buf's of the rings;
Reverting
10 matches
Mail list logo
