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 :
> Hi, Damien.
>
> With this configurat
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
Здравствуйте, 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=8843 metric 0 mtu 1500
options=400b8
ether a0:36:
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 Коньков Евгений :
> Now i350 is configured as:
>
> /etc/rc.conf
> ## TCP/IP
> ifconfig_igb0="-rxcsum -txcsum -lro -tso up"
> ifconfig_igb1="
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=8843 metric 0 mtu 1500
optio
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 :
>
>
> Пересылаемое сообщение
> 11.04.2012, 13:14, "KES" :
>
> 10.04.2012, 08:50, "Da Rock" :
>
>> On 04/10/
Пересылаемое сообщение
11.04.2012, 13:14, "KES" :
10.04.2012, 08:50, "Da Rock" :
> 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 UTC 2012
>> but last two days:
>> reboot
12.04.2012 00:05, Коньков Евгений пишет:
> Здравствуйте, Eugene.
>
> Вы писали 10 апреля 2012 г., 0:39:52:
>
> EG> 10.04.2012 01:36, Коньков Евгений пишет:
>>> Hi.
>>>
>>> Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN
>>> FAST FSCK
>>> Apr 9 19:51:58 fsck:
>>> Apr 9 1
Здравствуйте, Eugene.
Вы писали 10 апреля 2012 г., 0:39:52:
EG> 10.04.2012 01:36, Коньков Евгений пишет:
>> Hi.
>>
>> Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST
>> FSCK
>> Apr 9 19:51:58 fsck:
>> Apr 9 19:51:58 fsck:
>> Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEX
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 UTC 2012
but last two days:
reboot ~ Mon Apr 9 19:50
reboot ~ Mon Apr 9 18:30
reboot ~
10.04.2012 01:36, Коньков Евгений пишет:
> Hi.
>
> Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST
> FSCK
> Apr 9 19:51:58 fsck:
> Apr 9 19:51:58 fsck:
> Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck
> MANUALLY.
> Apr 9 19:51:58 fsck: /dev/
Yes, I have tested.
and on this hardware on this OS it works from Fri Feb 24 17:07:48 UTC 2012
but last two days:
reboot ~ Mon Apr 9 19:50
reboot ~ Mon Apr 9 18:30
reboot ~ Sun Apr 8 20:55
rebo
Nothing logged in /var/log/* or crashes that exist in /var/crash would indicate
to me some sort of hardware related problem.
Have you tested your hardware lately and know that it is in operational order?
~Paul
On Mon, Apr 09, 2012 at 09:36:54PM +0300, ??? ??? wrote:
> Hi.
>
> Apr 9 19:5
Hi.
Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY, CANNOT RUN FAST
FSCK
Apr 9 19:51:58 fsck:
Apr 9 19:51:58 fsck:
Apr 9 19:51:58 fsck: /dev/ad8s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
Apr 9 19:51:58 fsck: /dev/ad8s1e: CANNOT SET FS_NEEDSFSCK FLAG
Apr 9 20:09:22 kernel:
14 matches
Mail list logo
