Pyun YongHyeon [EMAIL PROTECTED] wrote:
FYI: Fix committed to HEAD.
This happened nearly three weeks ago. When might this fix get into 6-STABLE?
I have also problems on my system which might be related to the sk-trouble,
so this fix might also help me. Or should I try to compile the new driver
On Sun, Jun 04, 2006 at 12:41:12PM +0200, Michael Gerhards wrote:
Pyun YongHyeon [EMAIL PROTECTED] wrote:
FYI: Fix committed to HEAD.
This happened nearly three weeks ago. When might this fix get into 6-STABLE?
Unfortunately sk(4) in HEAD has a known issue and I'm working
on it.
Pyun YongHyeon wrote:
On Mon, May 08, 2006 at 01:15:54PM +0900, Ganbold wrote:
Pyun,
Pyun YongHyeon wrote:
On Tue, Mar 28, 2006 at 04:22:15PM +0200, Wilko Bulte wrote:
On Mon, Mar 27, 2006 at 07:48:46PM -0800, Clint Olsen wrote..
On Mar 28, Pyun YongHyeon wrote:
and
On Mon, May 08, 2006 at 01:15:54PM +0900, Ganbold wrote:
Pyun,
Pyun YongHyeon wrote:
On Tue, Mar 28, 2006 at 04:22:15PM +0200, Wilko Bulte wrote:
On Mon, Mar 27, 2006 at 07:48:46PM -0800, Clint Olsen wrote..
On Mar 28, Pyun YongHyeon wrote:
and sparc64(SMP) and I never see
Pyun,
I can not apply the patch cleanly on
http://people.freebsd.org/~yongari/sk/sk_test2/if_sk.c
What version of sk driver should I use?
Ganbold
Pyun YongHyeon wrote:
On Mon, May 08, 2006 at 02:25:48PM +0900, Ganbold wrote:
Pyun YongHyeon wrote:
On Mon, May 08, 2006 at 01:15:54PM
On Mon, May 08, 2006 at 03:13:28PM +0900, Ganbold wrote:
Pyun,
I can not apply the patch cleanly on
http://people.freebsd.org/~yongari/sk/sk_test2/if_sk.c
What version of sk driver should I use?
The patch was generated against HEAD.
Ganbold
--
Regards,
Pyun YongHyeon
Pyun YongHyeon wrote:
On Mon, May 08, 2006 at 03:13:28PM +0900, Ganbold wrote:
Pyun,
I can not apply the patch cleanly on
http://people.freebsd.org/~yongari/sk/sk_test2/if_sk.c
What version of sk driver should I use?
The patch was generated against HEAD.
I see, but how can
On Mon, May 08, 2006 at 03:51:55PM +0900, Ganbold wrote:
Pyun YongHyeon wrote:
On Mon, May 08, 2006 at 03:13:28PM +0900, Ganbold wrote:
Pyun,
I can not apply the patch cleanly on
http://people.freebsd.org/~yongari/sk/sk_test2/if_sk.c
What version of sk driver should I
Pyun YongHyeon wrote:
On Mon, May 08, 2006 at 03:51:55PM +0900, Ganbold wrote:
Pyun YongHyeon wrote:
On Mon, May 08, 2006 at 03:13:28PM +0900, Ganbold wrote:
Pyun,
I can not apply the patch cleanly on
http://people.freebsd.org/~yongari/sk/sk_test2/if_sk.c
What version
On Mon, May 08, 2006 at 04:53:10PM +0900, Ganbold wrote:
Pyun YongHyeon wrote:
On Mon, May 08, 2006 at 03:51:55PM +0900, Ganbold wrote:
Pyun YongHyeon wrote:
On Mon, May 08, 2006 at 03:13:28PM +0900, Ganbold wrote:
Pyun,
I can not apply the patch cleanly on
Pyun YongHyeon wrote:
On Mon, May 08, 2006 at 04:53:10PM +0900, Ganbold wrote:
Pyun YongHyeon wrote:
On Mon, May 08, 2006 at 03:51:55PM +0900, Ganbold wrote:
Pyun YongHyeon wrote:
On Mon, May 08, 2006 at 03:13:28PM +0900, Ganbold wrote:
Pyun,
I can not apply the
Pyun,
Pyun YongHyeon wrote:
On Tue, Mar 28, 2006 at 04:22:15PM +0200, Wilko Bulte wrote:
On Mon, Mar 27, 2006 at 07:48:46PM -0800, Clint Olsen wrote..
On Mar 28, Pyun YongHyeon wrote:
and sparc64(SMP) and I never see above errors. The only issue known to
me is occasional watchdog
On Mon, May 08, 2006 at 01:15:54PM +0900, Ganbold wrote:
Pyun,
Pyun YongHyeon wrote:
On Tue, Mar 28, 2006 at 04:22:15PM +0200, Wilko Bulte wrote:
On Mon, Mar 27, 2006 at 07:48:46PM -0800, Clint Olsen wrote..
On Mar 28, Pyun YongHyeon wrote:
and sparc64(SMP) and I never see
Pyun YongHyeon wrote:
On Mon, May 08, 2006 at 01:15:54PM +0900, Ganbold wrote:
Pyun,
...
Is this NIC supported by if_sk driver?
Hmm, It seems that the NIC is SysKonnect V2.0(SK98XX2) which is
supposed to work with sk(4). Did it ever work with sk(4)?
No, it is new server and it
On Mon, May 08, 2006 at 02:25:48PM +0900, Ganbold wrote:
Pyun YongHyeon wrote:
On Mon, May 08, 2006 at 01:15:54PM +0900, Ganbold wrote:
Pyun,
...
Is this NIC supported by if_sk driver?
Hmm, It seems that the NIC is SysKonnect V2.0(SK98XX2) which is
supposed to work
On Tuesday 28 March 2006 20:37, you wrote:
On Tuesday 28 March 2006 11:38, Pieter de Goeje wrote:
I can't really tell if the performance is impaired by mpsafenet=0,
because the box is mostly busy doing userland stuff. Typical traffic
looks like this:
I'm going to test the new driver
On Saturday 01 April 2006 16:15, Pieter de Goeje wrote:
may be you consider to try Pyun's driver
http://people.freebsd.org/~yongari/sk/sk_test/if_sk.c
http://people.freebsd.org/~yongari/sk/sk_test/if_skreg.h
and run yours without mpsafenet ?
I have no clue what a game
My home-network is so simple I could just tie the desktop to the
server's NIC with a cross-cable (xl 3c905C to nve). Let's see if the
3Com 16-port switch is the culprit!
Spil.
On 24/03/06, Kevin Oberman [EMAIL PROTECTED] wrote:
Date: Fri, 24 Mar 2006 22:33:17 +0200
From: Ion-Mihai Tetcu
On Tue, Mar 28, 2006 at 04:22:15PM +0200, Wilko Bulte wrote:
On Mon, Mar 27, 2006 at 07:48:46PM -0800, Clint Olsen wrote..
On Mar 28, Pyun YongHyeon wrote:
and sparc64(SMP) and I never see above errors. The only issue known to
me is occasional watchdog timeout error which I really
On Monday 27 March 2006 23:08, Pyun YongHyeon wrote:
Jo?o
This is not quite true; I am running 2 systems with the sk driver. One
of them is a dual core athlon64, and it's network connection is indeed
flawed unless I change debug.mpsafenet to 0. The other machine is a
regular
On Monday 27 March 2006 21:21, Pieter de Goeje wrote:
IMO it would make sense to be replaced by Pyuns driver because the
original is not functional
kind of strange getting a new release with a known not functional driver
João
This is not quite true; I am running 2 systems with the
On Tuesday 28 March 2006 04:08, Pyun YongHyeon wrote:
On Tue, Mar 28, 2006 at 02:21:28AM +0200, Pieter de Goeje wrote:
On Monday 27 March 2006 23:48, JoaoBR wrote:
On Monday 27 March 2006 15:51, Mark Linimon wrote:
On Mon, Mar 27, 2006 at 12:15:55PM -0300, JoaoBR wrote:
well,
On Mon, Mar 27, 2006 at 07:48:46PM -0800, Clint Olsen wrote..
On Mar 28, Pyun YongHyeon wrote:
and sparc64(SMP) and I never see above errors. The only issue known to
me is occasional watchdog timeout error which I really want to fix. But
the watchdog timeout error is hard to reproduce and
On Tuesday 28 March 2006 12:40, you wrote:
snip
probably you do not have the traffic to make the box crash or less then
1/2GB of RAM in use
The box has 1GB RAM. Traffic is approx. 2-3Mbit/s.
in fact the problem does not happen on UP machines, only some times a
device timeout which only
On Tuesday 28 March 2006 11:38, Pieter de Goeje wrote:
I can't really tell if the performance is impaired by mpsafenet=0, because
the box is mostly busy doing userland stuff. Typical traffic looks like
this:
I'm going to test the new driver to see if I can disable mpsafenet. To be
specific
On Saturday 25 March 2006 08:55, Bjoern A. Zeeb wrote:
On Sat, 25 Mar 2006, David Xu wrote:
ÿÿ Saturday 25 March 2006 18:04ÿÿJoaoBR ÿÿ
It appears to be a point
the machines with problem are all SMP, UP do no show the nve timeout or
any other problem with it
alias, same with SK, on
On Mon, 27 Mar 2006, JoaoBR wrote:
On Saturday 25 March 2006 08:55, Bjoern A. Zeeb wrote:
On Sat, 25 Mar 2006, David Xu wrote:
ÿÿ Saturday 25 March 2006 18:04ÿÿJoaoBR ÿÿ
It appears to be a point
the machines with problem are all SMP, UP do no show the nve timeout or
any other problem
On Monday 27 March 2006 11:50, Bjoern A. Zeeb wrote:
so I reused it and my sk problem is gone, since friday the machines are
running fine again
why it will be in only after the release?
I guess for several reasons:
a) more testing
b) not confuse users with problem reports from the
On Mon, Mar 27, 2006 at 12:15:55PM -0300, JoaoBR wrote:
well, the actual driver is trash and unusable and overall crashes SMP
systems ... so more testing to see if it crashes more? ;)
As with any other software development project, you have to draw a line
somewhere and say these things will
On Monday 27 March 2006 15:51, Mark Linimon wrote:
On Mon, Mar 27, 2006 at 12:15:55PM -0300, JoaoBR wrote:
well, the actual driver is trash and unusable and overall crashes SMP
systems ... so more testing to see if it crashes more? ;)
As with any other software development project, you
On Monday 27 March 2006 23:48, JoaoBR wrote:
On Monday 27 March 2006 15:51, Mark Linimon wrote:
On Mon, Mar 27, 2006 at 12:15:55PM -0300, JoaoBR wrote:
well, the actual driver is trash and unusable and overall crashes SMP
systems ... so more testing to see if it crashes more? ;)
As
On Tue, Mar 28, 2006 at 02:21:28AM +0200, Pieter de Goeje wrote:
On Monday 27 March 2006 23:48, JoaoBR wrote:
On Monday 27 March 2006 15:51, Mark Linimon wrote:
On Mon, Mar 27, 2006 at 12:15:55PM -0300, JoaoBR wrote:
well, the actual driver is trash and unusable and overall crashes
On Mar 28, Pyun YongHyeon wrote:
and sparc64(SMP) and I never see above errors. The only issue known to
me is occasional watchdog timeout error which I really want to fix. But
the watchdog timeout error is hard to reproduce and I couldn't reproduce
the error on my system.
I'm still seeing
On Saturday 25 March 2006 02:29, Ion-Mihai Tetcu wrote:
I updated my system (which was happy on Feb. 15 code) to March 13 code
and I am still running fine. No errors at all. Also, another system was
updated to RELENG_6 yesterday and it is also running clean.
Again, all systems are
在 Saturday 25 March 2006 18:04，JoaoBR 写道：
It appears to be a point
the machines with problem are all SMP, UP do no show the nve timeout or any
other problem with it
alias, same with SK, on SMP the system crashes and with UP it's ok
João
Mine is UP, chipset is NForce3 250GB, current it
This happens w/o any real activity on that interface (which goes into
an Allied Telesyn switch):
...
Mar 24 19:39:54 worf kernel: nve0: device timeout (1)
Mar 24 19:39:54 worf kernel: nve0: link state changed to DOWN
Mar 24 19:39:55 worf kernel: nve0: link state changed to UP
Mar 24
On Sat, 25 Mar 2006, David Xu wrote:
ÿÿ Saturday 25 March 2006 18:04ÿÿJoaoBR ÿÿ
It appears to be a point
the machines with problem are all SMP, UP do no show the nve timeout or any
other problem with it
alias, same with SK, on SMP the system crashes and with UP it's ok
For sk please try
On Thu, 23 Mar 2006 14:34:24 -0800
Kevin Oberman [EMAIL PROTECTED] wrote:
Date: Thu, 23 Mar 2006 21:59:56 + (UTC)
From: Bjoern A. Zeeb [EMAIL PROTECTED]
On Thu, 23 Mar 2006, JoaoBR wrote:
On Thursday 23 March 2006 15:59, Bjoern A. Zeeb wrote:
nve did not worked on 6.0R
Date: Fri, 24 Mar 2006 22:33:17 +0200
From: Ion-Mihai Tetcu [EMAIL PROTECTED]
On Thu, 23 Mar 2006 14:34:24 -0800
Kevin Oberman [EMAIL PROTECTED] wrote:
Date: Thu, 23 Mar 2006 21:59:56 + (UTC)
From: Bjoern A. Zeeb [EMAIL PROTECTED]
On Thu, 23 Mar 2006, JoaoBR wrote:
On Fri, 24 Mar 2006 12:55:41 -0800
Kevin Oberman [EMAIL PROTECTED] wrote:
Date: Fri, 24 Mar 2006 22:33:17 +0200
From: Ion-Mihai Tetcu [EMAIL PROTECTED]
On Thu, 23 Mar 2006 14:34:24 -0800
Kevin Oberman [EMAIL PROTECTED] wrote:
Date: Thu, 23 Mar 2006 21:59:56 + (UTC)
From:
在 Friday 24 March 2006 02:40，JoaoBR 写道：
The other patch cited in the message has never been made:
diff -u -r1.7.2.4 if_nve.c
--- if_nve.c9 Oct 2005 04:18:17 - 1.7.2.4
+++ if_nve.c27 Oct 2005 09:58:45 -
@@ -727,7 +727,7 @@
DEBUGOUT(NVE_DEBUG_INIT, nve:
On recent releng_6 I have again nve timeouts and interface down status
Yesterday I found this thread
http://lists.freebsd.org/pipermail/freebsd-bugs/2005-October/015351.html
and the change in if_nve.c resolved my problem
still having lots of collisions coming from this NIC but it stays up and
I am a bit confused. The first addition of sc-pending_txs = 0; was
MFC'ed back in December by obrien.
Check around line 730 of if_nv.c (or whatever it's called in 6.0)
sc-linkup = 0;
sc-cur_rx = 0;
sc-pending_rxs = 0;
+ sc-pending_txs = 0;
This should mostly
On Thursday 23 March 2006 15:29, Kevin Oberman wrote:
I am a bit confused. The first addition of sc-pending_txs = 0; was
MFC'ed back in December by obrien.
Check around line 730 of if_nv.c (or whatever it's called in 6.0)
sc-linkup = 0;
sc-cur_rx = 0;
sc-pending_rxs
On Thu, 23 Mar 2006, JoaoBR wrote:
Hi,
The other patch cited in the message has never been made:
diff -u -r1.7.2.4 if_nve.c
--- if_nve.c9 Oct 2005 04:18:17 - 1.7.2.4
+++ if_nve.c27 Oct 2005 09:58:45 -
@@ -727,7 +727,7 @@
DEBUGOUT(NVE_DEBUG_INIT, nve:
On Thursday 23 March 2006 15:59, Bjoern A. Zeeb wrote:
If you have collisions you have most likeely a duplex mismatch.
yep, but I set manually matching with the switch and tried other speeds, no
change
If you read the code and I remember right the above change is a NOP.
anyway, resolved
On Thu, 23 Mar 2006, JoaoBR wrote:
On Thursday 23 March 2006 15:59, Bjoern A. Zeeb wrote:
nve did not worked on 6.0R (for me) but cvsup to stable resolved the case (for
me) in end of dezember
since a month or so with recent releng_6 the problem came back, timeouts and
stopping rx/tx
did you
On Thursday 23 March 2006 18:59, Bjoern A. Zeeb wrote:
On Thu, 23 Mar 2006, JoaoBR wrote:
On Thursday 23 March 2006 15:59, Bjoern A. Zeeb wrote:
nve did not worked on 6.0R (for me) but cvsup to stable resolved the case
(for me) in end of dezember
since a month or so with recent
Date: Thu, 23 Mar 2006 21:59:56 + (UTC)
From: Bjoern A. Zeeb [EMAIL PROTECTED]
On Thu, 23 Mar 2006, JoaoBR wrote:
On Thursday 23 March 2006 15:59, Bjoern A. Zeeb wrote:
nve did not worked on 6.0R (for me) but cvsup to stable resolved the case
(for
me) in end of dezember
49 matches
Mail list logo
