On Wednesday 18 January 2006 00:36, Pyun YongHyeon wrote:
> > >
> > >atm I have no clue. How about updated sk(4)?
> > >http://people.freebsd.org/~yongari/sk/if_sk.c
> > >http://people.freebsd.org/~yongari/sk/if_skreg.h
> >
Hi again
I am running your both versions (UP and SMP) now for almost
On Thu, Jan 19, 2006 at 06:35:38PM +0800, Ganbold wrote:
[...]
>
> >My servers are now almost 24h up with the new sk driver and none of them is
> >having the problem any more until now. Until this I had crontab run
> >"ifconfig
> >sk0 up" all 10 minutes what helped me so long.
>
> ifconf
At 06:08 PM 1/19/2006, you wrote:
hi
maybe a stupid hint but did you checked the TP cable and pin order? I often
saw such problems when a gigabit connected to an older /10 HUB or when using
incorrect pin orders on the cables or even to long cables
I will ask person to check the cables.
Appear
On Thursday 19 January 2006 04:14, Ganbold wrote:
> I have same problem even after updating the sk code to the latest:
>
> Jan 19 12:58:53 gw kernel: fxp0: device timeout
> Jan 19 12:59:10 gw kernel: sk0: watchdog timeout
> Jan 19 12:59:10 gw kernel: sk0: link state changed to DOWN
> Jan 19 12:59:2
On Thu, Jan 19, 2006 at 03:52:58PM +0800, Ganbold wrote:
> Hi,
>
> At 03:16 PM 1/19/2006, you wrote:
> >On Thu, Jan 19, 2006 at 02:14:13PM +0800, Ganbold wrote:
> > > I have same problem even after updating the sk code to the latest:
> > >
> > > Jan 19 12:58:53 gw kernel: fxp0: device timeo
Hi,
At 03:16 PM 1/19/2006, you wrote:
On Thu, Jan 19, 2006 at 02:14:13PM +0800, Ganbold wrote:
> I have same problem even after updating the sk code to the latest:
>
> Jan 19 12:58:53 gw kernel: fxp0: device timeout
> Jan 19 12:59:10 gw kernel: sk0: watchdog timeout
> Jan 19 12:59:10 gw ker
On Thu, Jan 19, 2006 at 02:14:13PM +0800, Ganbold wrote:
> I have same problem even after updating the sk code to the latest:
>
> Jan 19 12:58:53 gw kernel: fxp0: device timeout
> Jan 19 12:59:10 gw kernel: sk0: watchdog timeout
> Jan 19 12:59:10 gw kernel: sk0: link state changed to DOWN
>
I have same problem even after updating the sk code to the latest:
Jan 19 12:58:53 gw kernel: fxp0: device timeout
Jan 19 12:59:10 gw kernel: sk0: watchdog timeout
Jan 19 12:59:10 gw kernel: sk0: link state changed to DOWN
Jan 19 12:59:20 gw kernel: fxp0: device timeout
Jan 19 12:59:52 gw kernel:
On Wed, Jan 18, 2006 at 11:36:46AM +0900, Pyun YongHyeon wrote:
P> > > > same problem device timeout.
P> > > > fxp is also timing out and I don't know why.
P> > > > Any idea?
P> > > >
P> > >
P> > >If sk(4) is the cause of problem fxp wouldn't be affected.
P> >
P> > I guess so. But fxp also
On Wed, Jan 18, 2006 at 10:28:43AM +0800, Ganbold wrote:
> At 09:55 AM 1/18/2006, you wrote:
> > > inet 127.0.0.1 netmask 0xff00
> > >
> > > I used new if_sk codes from Pyun YongHyeon but after 2 days I got
> > > same problem device timeout.
> > > fxp is also timing out and I don'
At 09:55 AM 1/18/2006, you wrote:
> inet 127.0.0.1 netmask 0xff00
>
> I used new if_sk codes from Pyun YongHyeon but after 2 days I got
> same problem device timeout.
> fxp is also timing out and I don't know why.
> Any idea?
>
If sk(4) is the cause of problem fxp wouldn't be
On Wed, Jan 18, 2006 at 09:27:09AM +0800, Ganbold wrote:
> Hi,
>
> I'm having problem with sk and fxp NIC. I get fxp0: device timeout
> and sk0: watchdog timeout problems and network stops responding.
>
> gw# uname -an
> FreeBSD xx.xx.xx 6.0-STABLE FreeBSD
Hi,
I'm having problem with sk and fxp NIC. I get fxp0: device timeout
and sk0: watchdog timeout problems and network stops responding.
gw# uname -an
FreeBSD xx.xx.xx 6.0-STABLE FreeBSD 6.0-STABLE #2: Mon Jan 16
12:09:59 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GATEWAY
13 matches
Mail list logo
