Hello, it says nothing to be worry about
10 input errors, 6 CRC, 0 frame, 0 overrun, 4 ignored
0 watchdog, 64973071 multicast, 0 pause input
0 input packets with dribble condition detected
4 output errors, 0 collisions, 2 interface resets
0 babbles, 0 late collision, 0 deferred
4 lost carrier, 0
On Mon, Oct 24, 2011 at 08:14:22AM -0400, John Baldwin wrote:
> On Sunday, October 23, 2011 11:58:28 am Pawel Jakub Dawidek wrote:
> > On Sun, Oct 23, 2011 at 11:44:45AM +0300, Kostik Belousov wrote:
> > > On Sun, Oct 23, 2011 at 08:10:38AM +0200, Pawel Jakub Dawidek wrote:
> > > > My suggestion wo
Hi Jason
Have you tried:
hw.em.fc_setting="0" (in loader.conf)
ifconfig emX -tso -lro -rxcsum -txcsum -vlanhwtag -wol
with MSIX and no multiqueue.
Advanced features has always been a source of problem.
It is worth a try and help to narrow down possibilities.
It would also be helpful if you pr
Hi !
vge0@pci0:2:0:0:class=0x02 card=0x01101106 chip=0x31191106 rev=0x82
hdr=0x00
vendor = 'VIA Technologies, Inc.'
device = 'VT6120/VT6121/VT6122 Gigabit Ethernet Adapter'
class = network
subclass = ethernet
bar [10] = type I/O Port, range 32, base
Hooman,
I have run with dev.em.X.flow_control=0, which should have the same result
as hw.em.fc_setting=0, and net.inet.tcp.tso is also 0. I'm not sure the
remaining options would be able to produce the scenario I'm seeing, but I'm
open to giving it a try with no options on the interfaces. I've a
On Wednesday, October 26, 2011 3:54:31 am Pawel Jakub Dawidek wrote:
> On Mon, Oct 24, 2011 at 08:14:22AM -0400, John Baldwin wrote:
> > On Sunday, October 23, 2011 11:58:28 am Pawel Jakub Dawidek wrote:
> > > On Sun, Oct 23, 2011 at 11:44:45AM +0300, Kostik Belousov wrote:
> > > > On Sun, Oct 23,
On 10/26/2011 7:33 AM, Jason Wolfe wrote:
> Hooman,
>
> I have run with dev.em.X.flow_control=0, which should have the same result
> as hw.em.fc_setting=0, and net.inet.tcp.tso is also 0. I'm not sure the
> remaining options would be able to produce the scenario I'm seeing, but I'm
> open to givi
Hooman,
I have run with dev.em.X.flow_control=0, which should have the same result
as hw.em.fc_setting=0, and net.inet.tcp.tso is also 0. I'm not sure the
remaining options would be able to produce the scenario I'm seeing, but I'm
open to giving it a try with no options on the interfaces. I'v
On 26 October 2011 21:47, Emil Muratov wrote:
> Hi All,
> I've got almost the same problem with intel 82574L based nic. My platform is
> nvidia ion running Atom 1.6 and nic is an external PCI-express adapter.
> Unlike Jason's case mine is always stuck in receiving traffic, it's Ierrs
> increasing
Dear Jason
I was actually interested in "status:" and "flags=" line from ifconfig output
_at_ the time problem happens.
From your previous post, it is clear that when the driver stops transmitting,
output errors are zero and "Drops" increasing. This happens when the stack uses
IFQ_ENQUEUE to pu
Hi,
Can yan you pls post the output of these command _when_ the problem happens?
uname -a
sysctl dev.em
netstat -ind
ifconfig
I've got almost the same problem with intel 82574L based nic. My platform is nvidia ion running Atom 1.6 and nic is an external PCI-express adapter. Unlike Jason's case
Hello networkers,
I've rolled out a new patch & README here:
http://people.freebsd.org/~glebius/newcarp/
The most important change since last version is not sending
spurious graturious ARP announce on startup.
--
Totus tuus, Glebius.
___
freeb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/25/2011 14:22, Qing Li wrote:
> Since I have been receiving private reports on the test failures, I
> thought I just post the test report as executed against the
> upcoming FreeBSD 9.0 release in my own setup, so you can see where
> the baseline
On Wed, Oct 26, 2011 at 01:49:14PM +0400, Andrey Smagin wrote:
> Hi !
> vge0@pci0:2:0:0:class=0x02 card=0x01101106 chip=0x31191106
> rev=0x82 hdr=0x00
> vendor = 'VIA Technologies, Inc.'
> device = 'VT6120/VT6121/VT6122 Gigabit Ethernet Adapter'
> class = netwo
On 10/26/11 12:54 AM, Pawel Jakub Dawidek wrote:
On Mon, Oct 24, 2011 at 08:14:22AM -0400, John Baldwin wrote:
On Sunday, October 23, 2011 11:58:28 am Pawel Jakub Dawidek wrote:
On Sun, Oct 23, 2011 at 11:44:45AM +0300, Kostik Belousov wrote:
On Sun, Oct 23, 2011 at 08:10:38AM +0200, Pawel Jak
Hooman,
I've added ifconfig to my collection script (as well as sysctl hw.em) that
will run at the time of the next wedge, the ifconfig lines in my email were
just to show the before and after as I've also modified the running options
on emX in this test group as you proposed.
Thank you for the d
On Wed, Oct 26, 2011 at 6:16 AM, Mike Tancsa wrote:
> On 10/26/2011 7:33 AM, Jason Wolfe wrote:
> > Hooman,
> >
> > I have run with dev.em.X.flow_control=0, which should have the same
> result
> > as hw.em.fc_setting=0, and net.inet.tcp.tso is also 0. I'm not sure the
> > remaining options would
Hi,
Can yan you pls post the output of these command _when_ the problem
happens?
uname -a
sysctl dev.em
netstat -ind
ifconfig
Hi Hooman
Here is what I've got when the script triggered just in time when the
interface was locked
11.10.26-23:39:10 ... interface em0 is down...
FreeBSD
18 matches
Mail list logo
