On Sat, Dec 17, 2011 at 06:49:48PM +0200, Sami Halabi wrote:
Hi,
I've moved to a new server with bge card driver, similar configuration:
/etc/sysctl.conf
net.inet.flowtable.enable=0
net.inet.ip.fastforwarding=1
kern.ipc.somaxconn=8192
kern.ipc.shmmax=2147483648
kern.ipc.maxsockets=204800
Hi,
It seems you have really complex network configuration(ipfw(4),
lagg(4), dummynet(4), bridge(4) and ipsec(4) etc). Finding out
simplest network setup that shows the issue would be required here.
hmm.. i actually don't use lagg nor bridge nor ipsec, i compile them for
any future use that might
Hi,
I've moved to a new server with bge card driver, similar configuration:
/etc/sysctl.conf
net.inet.flowtable.enable=0
net.inet.ip.fastforwarding=1
kern.ipc.somaxconn=8192
kern.ipc.shmmax=2147483648
kern.ipc.maxsockets=204800
kern.ipc.maxsockbuf=2097152
hw.intr_storm_threshold=9000
Hi,
here is # pciconf -lv | grep -A4 bge\[0-9]\@
bge0@pci0:2:0:0:class=0x02 card=0x03781014 chip=0x165a14e4
rev=0x00 hdr=0x00
vendor = 'Broadcom Corporation'
device = 'Broadcom NetXtreme BCM5722 Gigabit (94309)'
class = network
subclass = ethernet
--
updated sysctl:
dev.bge.1.stats.FramesDroppedDueToFilters: 0
dev.bge.1.stats.DmaWriteQueueFull: 2291364
dev.bge.1.stats.DmaWriteHighPriQueueFull: 0
dev.bge.1.stats.NoMoreRxBDs: 0
dev.bge.1.stats.InputDiscards: 0
dev.bge.1.stats.InputErrors: 0
dev.bge.1.stats.RecvThresholdHit: 124125195
hi,
i can see what it does.
how do i compile the driver and load it instead of the running driver
without restarting? its a production server.
Thanks,
Sami
On Thu, Dec 8, 2011 at 1:58 AM, YongHyeon PYUN pyu...@gmail.com wrote:
On Wed, Dec 07, 2011 at 09:55:22AM +0200, Sami Halabi wrote:
Hi,
On Thu, Dec 08, 2011 at 11:56:51AM +0200, Sami Halabi wrote:
hi,
i can see what it does.
how do i compile the driver and load it instead of the running driver
without restarting? its a production server.
There is no such way. You have to rebuild/install kernel and
reboot.
Thanks,
Sami
Hi,
On Thu, Dec 8, 2011 at 4:52 PM, YongHyeon PYUN pyu...@gmail.com wrote:
On Thu, Dec 08, 2011 at 11:56:51AM +0200, Sami Halabi wrote:
hi,
i can see what it does.
how do i compile the driver and load it instead of the running driver
without restarting? its a production server.
There is no
On Wed, Dec 07, 2011 at 09:55:22AM +0200, Sami Halabi wrote:
Hi,
the patch failed, As i see /usr/src/dev/re/if_re.c has the following at
line 1943:
if (rxstat RL_RDESC_STAT_RXERRSUM !(total_len 8191
(rxstat RL_RDESC_STAT_ERRS) ==
On Mon, Dec 05, 2011 at 01:53:03PM +0200, Sami Halabi wrote:
Hi,
Dmesg:
re0: RealTek 8169/8169S/8169SB(L)/8110S/8110SB(L) Gigabit Ethernet port
0x9000-0x90ff mem 0xf400-0xf4ff irq 16 at device 6.0 on pci1
re0: Chip rev. 0x1000
re0: MAC rev. 0x
miibus0: MII bus on re0
Hi,
the patch failed, As i see /usr/src/dev/re/if_re.c has the following at
line 1943:
if (rxstat RL_RDESC_STAT_RXERRSUM !(total_len 8191
(rxstat RL_RDESC_STAT_ERRS) == RL_RDESC_STAT_GIANT)) {
ifp-if_ierrors++;
Hi,
Dmesg:
re0: RealTek 8169/8169S/8169SB(L)/8110S/8110SB(L) Gigabit Ethernet port
0x9000-0x90ff mem 0xf400-0xf4ff irq 16 at device 6.0 on pci1
re0: Chip rev. 0x1000
re0: MAC rev. 0x
miibus0: MII bus on re0
rgephy0: RTL8169S/8110S/8211B media interface PHY 1 on miibus0
Hi,
I have a desktop on which being used as a MPD server.
the server isn't that loaded, and the cpu is highly idel 90-92% of the time.
My problem is in the network card connected to the cables provider.
in a random manner ot stops working whith no notice, and all l2tp/pptp
users disconnect,
also
04.12.2011 19:33, Sami Halabi wrote:
here is the plot of lspci:
Please, show the output:
#pciconf -lv | grep -A4 re\[0-9]\@
--
Vladislav V. Prodan
System Network Administrator
http://support.od.ua
+380 67 4584408, +380 99 4060508
VVP88-RIPE
___
Hi,
%pciconf -lv | grep -A4 re\[0-9]\@
re0@pci0:1:6:0: class=0x02 card=0x816910ec chip=0x816910ec rev=0x10
hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'Single Gigabit LOM Ethernet Controller (RTL8110)'
class = network
subclass = ethernet
re1@pci0:1:7:0:
On Sun, Dec 04, 2011 at 07:33:01PM +0200, Sami Halabi wrote:
Hi,
I have a desktop on which being used as a MPD server.
the server isn't that loaded, and the cpu is highly idel 90-92% of the time.
My problem is in the network card connected to the cables provider.
in a random manner ot stops
Both the em and re drivers have had a lot of work done recently. Are
you trying with 8.2RC1 ?
Tried with 8.2RC2 (via fixit shell with em): the same symptoms sadly.
Card recognized, driver loaded as a result ifconfig reports it as
available interface. Though neither static IP addressing nor
Pyun YongHyeon (pyu...@gmail.com) [11.01.31 23:14] wrote:
Then I have no idea. Does other OS work with your hardware without
issues? As last resort, could you try vendor's FreeBSD driver? The
vendor's driver applies a bunch of magic DSP fixups which re(4)
does not have. I don't know whether
Pyun YongHyeon (pyu...@gmail.com) [11.01.31 04:08] wrote:
The RTL8168/8111D sample board I have does not show this kind of
issue. This happens only when established link is 1000baseT, right?
I slightly changed PHY's link detection code so would you try that
patch at the following URL?
On Monday 31 January 2011 03:07:02 Pyun YongHyeon wrote:
On Sun, Jan 30, 2011 at 05:15:10PM -0800, Pyun YongHyeon wrote:
On Sun, Jan 30, 2011 at 02:53:15PM +0100, Milan Obuch wrote:
On Sunday 30 January 2011 07:40:48 Zeus V Panchenko wrote:
another detail for this nic
dmidecode
Milan Obuch (freebsd-...@dino.sk) [11.01.31 17:31] wrote:
I checked my cables and one of them had bad pairing. Worked in 100 Mb mode,
but not in 1 Gb mode. After I replaced it I check with flood ping, 1472 bytes
packets again and no sign of problem here - one reply missing in almost 21
On Mon, Jan 31, 2011 at 02:15:09PM +0200, Zeus V Panchenko wrote:
Pyun YongHyeon (pyu...@gmail.com) [11.01.31 04:08] wrote:
The RTL8168/8111D sample board I have does not show this kind of
issue. This happens only when established link is 1000baseT, right?
I slightly changed PHY's link
On Sunday 30 January 2011 07:40:48 Zeus V Panchenko wrote:
another detail for this nic
dmidecode
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: AT5NM10-I
Version: Rev x.0x
Serial Number: MT7006K15200322
I did not followed this
On Sun, Jan 30, 2011 at 02:53:15PM +0100, Milan Obuch wrote:
On Sunday 30 January 2011 07:40:48 Zeus V Panchenko wrote:
another detail for this nic
dmidecode
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: AT5NM10-I
Version: Rev x.0x
On Sun, Jan 30, 2011 at 08:40:48AM +0200, Zeus V Panchenko wrote:
another detail for this nic
dmidecode
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: AT5NM10-I
Version: Rev x.0x
Serial Number: MT7006K15200322
uname -a
FreeBSD
On Sun, Jan 30, 2011 at 05:15:10PM -0800, Pyun YongHyeon wrote:
On Sun, Jan 30, 2011 at 02:53:15PM +0100, Milan Obuch wrote:
On Sunday 30 January 2011 07:40:48 Zeus V Panchenko wrote:
another detail for this nic
dmidecode
Base Board Information
Manufacturer: ASUSTeK
On Sun, Jan 30, 2011 at 05:20:32PM -0800, Pyun YongHyeon wrote:
On Sun, Jan 30, 2011 at 08:40:48AM +0200, Zeus V Panchenko wrote:
another detail for this nic
dmidecode
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: AT5NM10-I
another detail for this nic
dmidecode
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: AT5NM10-I
Version: Rev x.0x
Serial Number: MT7006K15200322
uname -a
FreeBSD 8.2-PRERELEASE amd64
system was cvsup-ed 2011.01.20
if_re.c,v 1.160.2.17
Hi all,
the same problem i wrote in the first posts about year ago :(
onboard re(4) tremendous flapping
while ( cable connects nic and switch )
{
re0: link state changed to UP
re0: link state changed to DOWN
}
here the details:
dmidecode
Base Board Information
Manufacturer: ASUSTeK
The question has come up several times. What should be changed in
re(4) to cover this?
Well, if this question has come up several times a) it has a reason:
same chip works for some but not for others b) description is not
clear that driver is only supporting this chip if and when ...
Anyhow, one
On 1/2/2011 4:20 PM, Gabor Radnai wrote:
The question has come up several times. What should be changed in
re(4) to cover this?
Both the em and re drivers have had a lot of work done recently. Are
you trying with 8.2RC1 ?
---Mike
___
Realtek 8111 is not supported - that's the final conclusion? If so can this
be made clear in re driver manual?
Thanks.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to
On Dec 13, 2010, at 11:54 AM, Gabor Radnai wrote:
Realtek 8111 is not supported - that's the final conclusion? If so can this
be made clear in re driver manual?
At least some people have reported the Realtek 8111 working for them.
This said, Realtek's older 10/100 NICs were infamous for being
On Mon, Dec 13, 2010 at 3:26 PM, Chuck Swiger cswi...@mac.com wrote:
On Dec 13, 2010, at 11:54 AM, Gabor Radnai wrote:
Realtek 8111 is not supported - that's the final conclusion? If so can
this be made clear in re driver manual?
At least some people have reported the Realtek 8111 working
On Mon, 13 Dec 2010, Gabor Radnai wrote:
Realtek 8111 is not supported - that's the final conclusion? If so can this
be made clear in re driver manual?
r...@pci0:4:0:0:class=0x02 card=0x514c1462 chip=0x816810ec rev=0x02
hdr=0x00
vendor = 'Realtek Semiconductor'
device
Hi,
On Thu, Dec 2, 2010 at 10:30 PM, Pyun YongHyeon pyu...@gmail.com wrote:
On Thu, Dec 02, 2010 at 09:56:42PM +0100, Gabor Radnai wrote:
Hi,
Could someone pls advise how to inject HEAD driver to stable release without
full kernel rebuild (if possible)?
If you have updated to
Hi,
Could someone pls advise how to inject HEAD driver to stable release without
full kernel rebuild (if possible)?
I tried this way but found no assurance/evidence actually kernel using the
new driver:
1. download full HEAD source with help of csup
2. in /usr/src/sys/modules/re did make install
On Thu, Dec 02, 2010 at 09:56:42PM +0100, Gabor Radnai wrote:
Hi,
Could someone pls advise how to inject HEAD driver to stable release without
full kernel rebuild (if possible)?
If you have updated to stable/8, the driver code would be the same.
So need to replace driver with HEAD version.
Just a me too to echo Gabor's request for guidance for checking out
and using new drivers from HEAD.
In my case I'd like to try the new em(4) Jack's been talking about.
I've been running FreeBSD machines for several years, but this is the
first time I've found myself having driver problems
On
re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
options=389bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_UCAST,WOL_MCAST,WOL_MAGIC
ether d8:5d:4c:80:b4:88
inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255
media: Ethernet autoselect (1000baseT
On Sat, Nov 13, 2010 at 09:09:18AM +0200, Zeus V Panchenko wrote:
Pyun YongHyeon (pyu...@gmail.com) [10.11.13 01:01] wrote:
Please be more specific for the issue. Your description is hard to
narrow down possible cause.
i was sure it is the problem of the onboard rt nics ...
Hi,
I hope you are interested in inet section it looks like this (will able to
send the exact output only a bit later unfortunately as removed the card) :
inet 0.0.0.0 netmask 255.255.255.255
Thanks,
Gabor
On Thu, Nov 11, 2010 at 10:26 PM, Pyun YongHyeon pyu...@gmail.com wrote:
On Thu, Nov
On Fri, Nov 12, 2010 at 10:18:40PM +0100, Gabor Radnai wrote:
Hi,
I hope you are interested in inet section it looks like this (will able to
send the exact output only a bit later unfortunately as removed the card) :
inet 0.0.0.0 netmask 255.255.255.255
This might be caused by
On Fri, Nov 12, 2010 at 09:07:59AM +0200, Zeus V Panchenko wrote:
Hi,
Gabor Radnai (gabor.rad...@gmail.com) [10.11.11 23:22] wrote:
pciconf:
n...@pci0:0:20:0:class=0x068000 card=0x816a1043 chip=0x026910de rev=0xa3
hdr=0x00
vendor = 'NVIDIA Corporation'
device =
Pyun YongHyeon (pyu...@gmail.com) [10.11.13 01:01] wrote:
Please be more specific for the issue. Your description is hard to
narrow down possible cause.
i was sure it is the problem of the onboard rt nics ...
pciconf output of all re(4) controllers are useless because the
vendor
Hi,
Gabor Radnai (gabor.rad...@gmail.com) [10.11.11 23:22] wrote:
pciconf:
n...@pci0:0:20:0:class=0x068000 card=0x816a1043 chip=0x026910de rev=0xa3
hdr=0x00
vendor = 'NVIDIA Corporation'
device = 'MCP51 Network Bus Enumerator'
class = bridge
r...@pci0:1:0:0:
46 matches
Mail list logo
