Ferdinand Haselbacher (jr.) wrote:
On Tue, Nov 29, 2005 at 07:22:17PM -0500, Nicolas Blais wrote:
That's great. But as I said, there's nothing I can configure on my
switch's side.
Anyway, you and I aren't the only ones with the same problem, under the same
circonstances. My forcing of the
On Tue, Nov 29, 2005 at 07:22:17PM -0500, Nicolas Blais wrote:
That's great. But as I said, there's nothing I can configure on my
switch's side.
Anyway, you and I aren't the only ones with the same problem, under the same
circonstances. My forcing of the TX/RX mode does speed up
Bernhard Fischer wrote:
If you change hardware settings, you should also maintain the same
settings on both ends of the wire, i.e. at the computer *and* the
ethernet switch.
[SNIP]
I just forced it to use 100baseTX /
full-duplex which I think was used before I forced it as well.
That's
That's great. But as I said, there's nothing I can configure on my
switch's side.
Anyway, you and I aren't the only ones with the same problem, under the same
circonstances. My forcing of the TX/RX mode does speed up recovery, but
doesn't fix the actual issue.
The driver has a bug
Hans Nieser wrote:
Nicolas Blais wrote:
I have an sk0 too on one of my computer's onboard A8V-DX which will
timeout once in a while too. I found a way to reduce down time by
modifying my rc.conf to force 'full-duplex 100Mbps'. Now, even when
it goes into a watchdog timeout, I quickly get
ifconfig_sk0=inet 192.168.1.100 media 100baseTX mediaopt full-duplex
netmask 255.255.255.0
It appears the above hasn't helped me, it still goes down after copying
about 10-15GB of data and I still have to bring the interface down and up
again to regain connectivity. Thanks for the tip
Bernhard Fischer wrote:
ifconfig_sk0=inet 192.168.1.100 media 100baseTX mediaopt full-duplex
netmask 255.255.255.0
It appears the above hasn't helped me, it still goes down after copying
about 10-15GB of data and I still have to bring the interface down and up
again to regain connectivity.
If you change hardware settings, you should also maintain the same
settings on both ends of the wire, i.e. at the computer *and* the
ethernet switch.
[SNIP]
I just forced it to use 100baseTX /
full-duplex which I think was used before I forced it as well.
That's exactly what I ment. If
Bernhard Fischer wrote:
If you change hardware settings, you should also maintain the same
settings on both ends of the wire, i.e. at the computer *and* the
ethernet switch.
[SNIP]
I just forced it to use 100baseTX /
full-duplex which I think was used before I forced it as well.
--- Vladimir Dvorak [EMAIL PROTECTED] wrote:
Bernhard Fischer wrote:
If you change hardware settings, you should
also maintain the same
settings on both ends of the wire, i.e. at
the computer *and* the
ethernet switch.
[SNIP]
I just forced it to use 100baseTX /
Danial Thom wrote:
--- Vladimir Dvorak [EMAIL PROTECTED] wrote:
Bernhard Fischer wrote:
If you change hardware settings, you should
also maintain the same
settings on both ends of the wire, i.e. at
the computer *and* the
ethernet switch.
Hans Nieser wrote:
Nicolas Blais wrote:
On November 26, 2005 09:15 am, Hans Nieser wrote:
A long, long time ago Vladimir Dvorak wrote:
Hello,
I have a problem with network card. From time to time kernel says
sk0: watchdog timeout
I just ran into the same issue. I have an
Vladimir Dvorak wrote:
I found some other solution here:
http://sources.zabbadoz.net/freebsd/if_sk.html
There is recommended to use correct on-chip RAM size:
6. use correct on-chip RAM size; committed to HEAD
http://lists.freebsd.org/pipermail/cvs-src/2004-November/035293.html
Can some
A long, long time ago Vladimir Dvorak wrote:
Hello,
I have a problem with network card. From time to time kernel says
sk0: watchdog timeout
I just ran into the same issue. I have an ASUS A8N-SLI Deluxe in my
desktop machine which runs FreeBSD 6.0+Xorg+Gnome. It has two on-board
NICs, the
On November 26, 2005 09:15 am, Hans Nieser wrote:
A long, long time ago Vladimir Dvorak wrote:
Hello,
I have a problem with network card. From time to time kernel says
sk0: watchdog timeout
I just ran into the same issue. I have an ASUS A8N-SLI Deluxe in my
desktop machine which runs
Nicolas Blais wrote:
On November 26, 2005 09:15 am, Hans Nieser wrote:
A long, long time ago Vladimir Dvorak wrote:
Hello,
I have a problem with network card. From time to time kernel says
sk0: watchdog timeout
I just ran into the same issue. I have an ASUS A8N-SLI Deluxe in
Nicolas Blais wrote:
On November 3, 2005 06:37 pm, martinko wrote:
Vladimir Dvorak wrote:
Hello,
I have a problem with network card. From time to time kernel says
sk0: watchdog timeout
It has (probably) random behavior.
I use FreeBSD 5.4-RELEASE-p8, motherboard is ASUS A8V Deluxe
Vladimir Dvorak wrote:
Hello,
I have a problem with network card. From time to time kernel says
sk0: watchdog timeout
It has (probably) random behavior.
I use FreeBSD 5.4-RELEASE-p8, motherboard is ASUS A8V Deluxe (AMD64,
Athlon64XP 3200+) and internal network card from pciconf -v -l
Vladimir Dvorak wrote:
Hello,
I have a problem with network card. From time to time kernel says
sk0: watchdog timeout
It has (probably) random behavior.
I use FreeBSD 5.4-RELEASE-p8, motherboard is ASUS A8V Deluxe (AMD64,
Athlon64XP 3200+) and internal network card from pciconf -v -l
[EMAIL
On November 3, 2005 06:37 pm, martinko wrote:
Vladimir Dvorak wrote:
Hello,
I have a problem with network card. From time to time kernel says
sk0: watchdog timeout
It has (probably) random behavior.
I use FreeBSD 5.4-RELEASE-p8, motherboard is ASUS A8V Deluxe (AMD64,
20 matches
Mail list logo
