Well, you see me glad that this fixes your problems.
You might want to see with Jack Vogel who maintains the Intel drivers,
if you can track down the issue and perhaps even find a fix for it.
Taking the liberty of CCing you Jack.
2012/4/18 Eugen Konkov kes-...@yandex.ru:
Hi, Damien.
With
Hi, Damien.
With this configuration works without reboots
ifconfig_igb0=-rxcsum -txcsum -lro -tso up
ifconfig_igb1=-rxcsum -txcsum -lro -tso up
ifconfig_igb2=-rxcsum -txcsum -lro -tso -vlanhwtag up
ifconfig_igb3=-rxcsum -txcsum -lro -tso up
igb0 has only one vlan
igb1 has two vlans
igb2 has 16
Здравствуйте, Damien.
Вы писали 13 апреля 2012 г., 4:42:31:
DF Yes, I suggest you try with -vlanhwtag as well.
DF If that stops your unwanted reboots, you may want to remove it and see
DF if the situation changes.
igb0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
Try disabling hardware VLAN tagging like so, I know we had problems a
few years back with it.
in /etc/rc.conf :
ifconfig_igb2= -vlanhwtag -tso -lro up
2012/4/11 KES kes-...@yandex.ua:
Пересылаемое сообщение
11.04.2012, 13:14, KES kes-...@yandex.ua:
10.04.2012, 08:50, Da
Now i350 is configured as:
/etc/rc.conf
## TCP/IP
ifconfig_igb0=-rxcsum -txcsum -lro -tso up
ifconfig_igb1=-rxcsum -txcsum -lro -tso up
ifconfig_igb2=-rxcsum -txcsum -lro -tso up
ifconfig_igb3=-rxcsum -txcsum -lro -tso up
# ifconfig -m igb1
igb1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST
Yes, I suggest you try with -vlanhwtag as well.
If that stops your unwanted reboots, you may want to remove it and see
if the situation changes.
2012/4/12 Коньков Евгений kes-...@yandex.ru:
Now i350 is configured as:
/etc/rc.conf
## TCP/IP
ifconfig_igb0=-rxcsum -txcsum -lro -tso up
Пересылаемое сообщение
11.04.2012, 13:14, KES kes-...@yandex.ua:
10.04.2012, 08:50, Da Rock freebsd-questi...@herveybayaustralia.com.au:
On 04/10/12 05:02, Коньков Евгений wrote:
Yes, I have tested.
and on this hardware on this OS it works from Fri Feb 24 17:07:48
