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
Здравствуйте, 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: UNEXPECTED
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 19:51:58 fsck:
Apr 9
Пересылаемое сообщение
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
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
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
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
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/ad8s1e:
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 ~
Greetings, fellow FreeBSD users!
Everything so far works fine for me, until I drop into single-
user mode to prep for making world. Even then, it seems OK,
except for this alarming output of fsck -p:
/dev/da0s1a: NO WRITE ACCESS
/dev/da0s1a: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
I run
On Friday 26 March 2004 10:06 am, Richard Dawes wrote:
Greetings, fellow FreeBSD users!
Everything so far works fine for me, until I drop into single-
user mode to prep for making world. Even then, it seems OK,
except for this alarming output of fsck -p:
Well, you missed reading something
On Fri, Mar 26, 2004 at 11:55:06AM -0800, Kent Stewart wrote:
On Friday 26 March 2004 10:06 am, Richard Dawes wrote:
Greetings, fellow FreeBSD users!
Everything so far works fine for me, until I drop into single-
user mode to prep for making world. Even then, it seems OK,
except for
On Friday 26 March 2004 01:02 pm, Richard Dawes wrote:
On Fri, Mar 26, 2004 at 11:55:06AM -0800, Kent Stewart wrote:
On Friday 26 March 2004 10:06 am, Richard Dawes wrote:
Greetings, fellow FreeBSD users!
Everything so far works fine for me, until I drop into single-
user mode to
On Fri, Mar 26, 2004 at 02:09:35PM -0800, Kent Stewart wrote:
The sequence that is designed to keep your out of trouble is buildworld,
buildkernel, installkernel, boot -s, and installworld, followed by a
mergemaster.
There are times as the statfs change to current that would render your
Dear FreeBSD people
I started to learn and used FreeBSD from last year. And I found FreeBSD is
really very powerful and lovely. But I am also a little scared of it, for
then it has problem, I just do not know how to fix it.
Here I came up a big emergent problem this morning, and I wish you can
I have a RAID-5 array on /home via vinum. This morning, the
server (running 4.8-PRERELEASE, compiled last week) wouldn't allow anyone
to login via ssh, imap, or console. So I had someone reboot the server
via control-alt-delete. Then it said that not all processes would dia,
use ps axl.
On Mon, 24 Feb 2003 [EMAIL PROTECTED] wrote:
As I type, the server is in single user mode. The fsck commands
result in:
CAN NOT READ: BLK 16
Try starting vinum.
--
:{ [EMAIL PROTECTED]
Andy Farkas
System Administrator
Speednet Communications
22 matches
Mail list logo
