I'm having some problems with my Marwel NIC (msk0) and loss of connection.
I found a solution where one could use the settings below:
In
/etc/sysctl.conf
net.inet.tcp.tso=0
And in
/boot/loader.conf
hw.msk.msi_disable=1
This seems to work but the trade-off is that I now only have 100
...spelling correction
Should be Marvell
2013-05-13 09:48, Leslie Jensen skrev:
I'm having some problems with my Marvell NIC (msk0) and loss of connection.
I found a solution where one could use the settings below:
In
/etc/sysctl.conf
net.inet.tcp.tso=0
And in
/boot/loader.conf
. Looking at the machine, I see:
re0: watchdog timeout
re0: link state changed to DOWN
re0: link state changed to UP
every 5-15 seconds in the logs. I've tried disabling MSI/MSI-X, but
that didn't have an affect. The only way I've gotten connectivity back
was to reboot the machine. Has anyone
Somebody know how to fix this driver problem?
Dec 14 12:10:38 mouseoleum kernel: bge0: watchdog timeout -- resetting
Dec 14 12:10:38 mouseoleum kernel: bge0: link state changed to DOWN
Dec 14 12:10:42 mouseoleum kernel: bge0: link state changed to UP
Dec 14 12:13:33 mouseoleum kernel: bge0
On Friday 01 May 2009 16:12:50 Seur Bors wrote:
I'm constantly getting the following repeated in my /var/log/messages:
kernel: re0: watchdog timeout
kernel: re0: link state changed to DOWN
kernel: re0: link state changed to UP
This was happening right from the get-go on new hardware
Greetings,
I'm constantly getting the following repeated in my /var/log/messages:
kernel: re0: watchdog timeout
kernel: re0: link state changed to DOWN
kernel: re0: link state changed to UP
This was happening right from the get-go on new hardware running
7.1-Release-p4, but only happened
Fred wrote:
Hi,
I recently upgraded from 6.3 to 7.1 (7.1-RELEASE-p4) with freebsd-update,
and I now have problems with msk0 very often (which I did have before) :
Mar 30 20:14:19 blackbox kernel: msk0: watchdog timeout (missed Tx
interrupts) -- recovering
Mar 30 20:14:58 blackbox kernel
Hi,
I recently upgraded from 6.3 to 7.1 (7.1-RELEASE-p4) with freebsd-update,
and I now have problems with msk0 very often (which I did have before) :
Mar 30 20:14:19 blackbox kernel: msk0: watchdog timeout (missed Tx
interrupts) -- recovering
Mar 30 20:14:58 blackbox kernel: msk0: watchdog
Any mistake?
The rl driver supports some really terrible hardware, so I'm far from
convinced that your custom kernel is causing the problems. Perhaps you
could check by switching back to a GENERIC kernel for a while.
It works well with GENERIC when I'm simply serfing the net or
fetching
Hello, all!
I have Asus X51RL laptop with FreeBSD 7.1-RC1 installed.
There were no troubles with GENERIC kernel, but when I've compiled custom
kernel, rl ethernet driver tells to the console a lot of errors:
rl0: link state changed to UP
rl0: watchdog timeout
rl0: watchdog timeout
Any mistake
state changed to UP
rl0: watchdog timeout
rl0: watchdog timeout
Any mistake?
Have you looked at the manual page for this driver? (try running 'man
rl' in a (x-)terminal). I quote:
rl%d: watchdog timeout The device has stopped responding to the network,
or there is a problem
rl0: watchdog timeout
rl0: watchdog timeout
Any mistake?
The rl driver supports some really terrible hardware, so I'm far from
convinced that your custom kernel is causing the problems. Perhaps you
could check by switching back to a GENERIC kernel for a while.
--
Lowell Gilbert, embedded
From Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org:
rl0: link state changed to UP
rl0: watchdog timeout
rl0: watchdog timeout
Any mistake?
The rl driver supports some really terrible hardware, so I'm far from
convinced that your custom kernel is causing the problems
On Tuesday 03 June 2008, Jeremy Karlson wrote:
I'm still looking into my watchdog timeout with me re card. I'm
starting to wonder if my problem is in any way related to the
discussion back in September 2006 starting with this post:
6.2 SHOWSTOPPER - em completely unusable on 6.2
http
I'm still looking into my watchdog timeout with me re card. I'm
starting to wonder if my problem is in any way related to the
discussion back in September 2006 starting with this post:
6.2 SHOWSTOPPER - em completely unusable on 6.2
http://lists.freebsd.org/pipermail/freebsd-stable/2006
Jeremy,
Perhaps this link could give you the solution to your problem:
http://www.linuxquestions.org/questions/bsd-17/rl0-watchdog-timeout-519599/
regards,
Jos
Jeremy Karlson wrote:
Hi,
I'm in the process of moving a Subversion server from a 5-STABLE
machine to a freshly installed 7-STABLE
the
network card (a Linksys EG1032v3, RTL8169S/8110S/8211B based) from the
old machine (where it worked before) to this new machine. Now, I get:
re0: watchdog timeout
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman
, Jos Chrispijn wrote:
Jeremy,
Perhaps this link could give you the solution to your problem:
http://www.linuxquestions.org/questions/bsd-17/rl0-watchdog-timeout-519599/
regards,
Jos
Jeremy Karlson wrote:
Hi,
I'm in the process of moving a Subversion server from a 5-STABLE
machine
: watchdog timeout
Every time I attempt to check out a PARTICULAR path of my Subversion
repository. (That path does happen to contain a binary file, about 40
MB - probably the largest in the repository.) It works when I check
it out over the loopback (localhost) connection, but not when I check
, the first one, bge0 is OK!
Welcome to the world of Broadcom. Imagine our surprise when Dell
started shipping embedded bge(4) and bce(4).
~BAS
The result of this error is blackouts and instability of the Internet
connections!
May 2 14:09:48 GBRT2 kernel: bge1: watchdog timeout -- resetting
is blackouts and instability of the Internet
connections!
May 2 14:09:48 GBRT2 kernel: bge1: watchdog timeout -- resetting
May 2 14:09:48 GBRT2 kernel: bge1: link state changed to DOWN
May 2 14:09:51 GBRT2 kernel: bge1: link state changed to UP
May 2 14:38:53 GBRT2 kernel: bge1: watchdog timeout
Hi
I have a problen with FreeBSD 6.3. When I boot, I get the message
xl0: watchdog timeout
and I have no networking. I have 3com ethernet card.
If i make ping on localhost it works good. But if i try to ping anything
else it didn't work. When I plug the 3com ethernet card into other
El sábado 29 de marzo a las 19:07:37 CET
Hi
I have a problen with FreeBSD 6.3. When I boot, I get the message
xl0: watchdog timeout
and I have no networking. I have 3com ethernet card.
If i make ping on localhost it works good. But if i try to ping anything
else it didn't work. When I
7 16:34:40 kreacher em0: link state changed to UP
Mar 7 16:34:40 kreacher em0: link state changed to UP
Mar 7 16:37:52 kreacher em0: watchdog timeout -- resetting
Mar 7 16:37:52 kreacher em0: link state changed to DOWN
Mar 7 16:37:52 kreacher em0: link state changed to DOWN
Mar 7 16:37:56
On 11/23/07, Michael Hawkins [EMAIL PROTECTED] wrote:
I have been receiving the same error message from my NAS box as of late.
Until last week, I was been running Freebsd6.2, and I occassionally
received the message re0: watchdog timeout. It would happen about
once a week. Last week, I
: watchdog timeout -- resetting
Nov 20 10:22:42 techdesk kernel: bfe0: link state changed to DOWN
Nov 20 10:22:44 techdesk kernel: bfe0: link state changed to UP
It seems to happen every day or two and from time to time twice a day.
The bfe0 is my external interface connected to the internet (6Mb/s).
I
I have been receiving the same error message from my NAS box as of late.
Until last week, I was been running Freebsd6.2, and I occassionally
received the message re0: watchdog timeout. It would happen about
once a week. Last week, I installed freenas (which is based on
freebsd6.2), and now I
I'm seeing a lot of these:
nfe0: watchdog timeout (missed Tx interrupts) -- recovering
when the system is under heavy network load (my ports distfiles are NFS
mounted from another box, so trying to extract, e.g., the OpenOffice
source, is enough to cripple the box). When the demand for network
On 10/6/06, Kris Kennaway [EMAIL PROTECTED] wrote:
On Fri, Oct 06, 2006 at 10:08:27AM -0700, perikillo wrote:
change the scheduler to the old SCHED_4BSD and maxuser from 10 to 32
like chuck told me.
These are probably what fixed it.
I guess you've learned a Lesson: when you choose to use
from all my local clients,
without any message saying:
vr0: watchdog timeout
I did some changes, in kernel, bacula, and machine:
Machine
Disable the internal NIC(via) and install one Linksys which use the
same driver vr0.
Kernel:
change the scheduler to the old SCHED_4BSD and maxuser from 10
On Fri, Oct 06, 2006 at 10:08:27AM -0700, perikillo wrote:
change the scheduler to the old SCHED_4BSD and maxuser from 10 to 32
like chuck told me.
These are probably what fixed it.
I guess you've learned a Lesson: when you choose to use code marked as
experimental, a) don't be surprised when
On 10/3/06, Christopher Swingler [EMAIL PROTECTED] wrote:
On Oct 3, 2006, at 7:55 PM, perikillo wrote:
On 10/3/06, perikillo [EMAIL PROTECTED] wrote:
Hi people i have read a some mails about this problem, snip
Greetings.
Wow
snip again
To unsubscribe, send any mail to
In response to perikillo [EMAIL PROTECTED]:
[snip]
Right now my first backup again crash
xl0: watchdog timeout
Right now i change the cable from on port to another and see what happends.
Guy, please someone has something to tell me, this is critical for me.
This is my second NIC
On 10/4/06, Bill Moran [EMAIL PROTECTED] wrote:
In response to perikillo [EMAIL PROTECTED]:
[snip]
Right now my first backup again crash
xl0: watchdog timeout
Right now i change the cable from on port to another and see what
happends.
Guy, please someone has something to tell me
On Oct 4, 2006, at 10:32 AM, perikillo wrote:
My kernel file is this:
machine i386
cpu I686_CPU
You should also list cpu I586_CPU, otherwise you will not include
some optimizations intended for Pentium or higher processors.
ident BACULA
maxusers 10
--- Chuck Swiger [EMAIL PROTECTED] wrote:
On Oct 4, 2006, at 10:32 AM, perikillo wrote:
My kernel file is this:
machine i386
cpu I686_CPU
You should also list cpu I586_CPU, otherwise you
will not include
some optimizations intended for Pentium or higher
:28:48
FD termination status: Error
SD termination status: Error
Termination:*** Backup Error ***
I have no problem with the client, is running our ERP software and no
comment here.
In my freebsd console appear this:
vr0: watchdog timeout
I reset the server, and all
: watchdog timeout
I reset the server, and all the Differential backups has been working
good, i do the buildworld yesterday and let my bacula server ready to do a
full backup for all my clients and whops...
I lost 2 clients jobs:
Client 1:
02-Oct 18:30 bacula-dir: Start Backup JobId 176, Job=
PDC
From /var/log/messages:
Jun 19 10:43:35 freebsd kernel: ed0: device timeout
Jun 19 10:43:39 freebsd last message repeated 2 times
Jun 19 10:43:41 freebsd kernel: xl0: watchdog timeout
Jun 19 10:43:41 freebsd kernel: ed0: device timeout
Jun 19 10:43:41 freebsd kernel: xl0: link state changed
M. Parsons wrote:
From /var/log/messages:
Jun 19 10:43:35 freebsd kernel: ed0: device timeout
Jun 19 10:43:39 freebsd last message repeated 2 times
Jun 19 10:43:41 freebsd kernel: xl0: watchdog timeout
Jun 19 10:43:41 freebsd kernel: ed0: device timeout
Jun 19 10:43:41 freebsd kernel: xl0
Hello,
I had a Thinkpad 600 and a lot of problems too, especially with
networking and the cardbus. It received the impression that the chipset
of the 600 is totally broken. The revisited successor 600E doesn't make
so much trouble at all.
Add the following lines to /boot/loader.conf,
Thanks, Björn. Your information solved this problem, the networking works
correctly now.
Ah, well, I upgraded my other ThinkPad from 600 to 600E to get the 16M
colors. I guess I will have to do the same to this new machine for more
reasons...
Ad astra,
Fred Koschara
At 02:23 AM 6/6/2006,
, ping) I get dc0 watchdog timeout errors, and
most of the time nothing else. When I ping the network gateway, nothing
happens for several seconds, then ping reports response times of 8.77~,
7.77~, 6.77~, ..., 0.77~ seconds in a batch, then goes to sleep again,
repeating the sequence.
I made
I am seeing the following in my security logs. Can anybody tell me what
this means? Perhaps I should consider a new NIC?
+dc0: watchdog timeout
+dc0: link state changed to DOWN
+dc0: link state changed to UP
Thanks in advance,
Tom Veldhouse
It may be hardware related. Have you made any system changes lately?
How often does this occur?
On 1/13/06, Thomas T. Veldhouse [EMAIL PROTECTED] wrote:
I am seeing the following in my security logs. Can anybody tell me what
this means? Perhaps I should consider a new NIC?
+dc0: watchdog
Corey Brune wrote:
It may be hardware related. Have you made any system changes lately?
How often does this occur?
No changes since about last April. I did move from FBSD 5.x to FBSD 6.x
(RELENG_6_0) at the time that 6.0 was released. Nothing since.
I have seen the issue a couple of
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
.
Still getting (from time to time ):
sk0: watchdog timeout
sk0: link state changed to DOWN
sk0: watchdog timeout
sk0: link state changed to UP
sk0: watchdog timeout
sk0: link state changed to DOWN
sk0: watchdog timeout
sk0: link state changed to UP
sk0: watchdog timeout
sk0: link state changed to DOWN
server in two
different environments -
at home and now at serverhouse. No difference.
Still getting (from time to time ):
sk0: watchdog timeout
sk0: link state changed to DOWN
sk0: watchdog timeout
sk0: link state changed to UP
sk0: watchdog timeout
sk0: link state changed to DOWN
sk0
about
networking, but this is hardware/driver related
problem ( with the
highest probability ). I used my server in two
different environments -
at home and now at serverhouse. No difference.
Still getting (from time to time ):
sk0: watchdog timeout
sk0: link state changed to DOWN
sk0: watchdog
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
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
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
Since I upgraded to version 6, my server has frozen under heavy network
traffic three times. It ran happily for months on various versions of
5. Same hardware, same configuration.
There was never anything in /var/log/messages until this last time. This
time I found:
kernel: rl0: watchdog
. This
time I found:
kernel: rl0: watchdog timeout
I don't know what it's trying to tell me, and I don't know if it's a cause or
an effect.
This is 6.0-STABLE as of late Sunday night. i386. rl0 is my WAN-side
interface. vr0 is my internal interface. This machine runs DNS, email, web,
NFS host
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
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 PROTECTED]:10:0: class
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
DeadMan Xia [EMAIL PROTECTED] writes:
I m using FreeBSD 5.3, on Dell Power Edge 6650 Quad Processor Machine,
my system get stuck while i m accessing it through ssh. well after
some time , when i acces the machine check , /var/log/messages ,, i
can bge0: WatchDog Timedout -- resetting
I m using FreeBSD 5.3, on Dell Power Edge 6650 Quad Processor Machine,
my system get stuck while i m accessing it through ssh. well after
some time , when i acces the machine check , /var/log/messages ,, i
get bge1: WatchDog Timedout -- resetting error. Is there any one , to
tap my back get
I m using FreeBSD 5.3, on Dell Power Edge 6650 Quad Processor Machine,
my system get stuck while i m accessing it through ssh. well after
some time , when i acces the machine check , /var/log/messages ,, i
can bge0: WatchDog Timedout -- resetting error. Is there any one , to
tap my back get me
On Friday 17 December 2004 09:35, Nico Meijer wrote:
I don't (and won't, unless forced) use Intel NICs, so I cannot speak
of them. I've had the very unpleasant experience of having had to
deal with a fierce network boost on a RealTek 8139 (don't ask...) in
a linux box. It meant the nic (and
Hi Dmitry,
Are we straying OT yet? I guess so, you've been warned.
We have tons of them working on servers, routers and desktops because
they are cheap (some beers are more expensive).
You are comparing cheap nics with beer? I'll take that beer, thanks! ;-)
I like the analogy, btw. Cheap
On Thursday 16 December 2004 04:36, Mike Jeays wrote:
I have no first hand experience with this particular problem, but
it's almost common knowledge RealTek nics are great because they
are cheap, not because they are of good quality. The phrase piece
of crap has been uttered more than once
Good day!
I know, this question is famous, but i can't handle it myself. The problem is:
After some time my realtek card becomes unresponsible. It happens because of
buffer overflow. I tried ping -f xxx. 15 seconds later, the kernel says that
rl0: watchdog timeout. I can't send files more
Hi Andrew,
Warning: no definitive answer ahead.
After some time my realtek card becomes unresponsible. It happens
because of buffer overflow. I tried ping -f xxx. 15 seconds later, the
kernel says that rl0: watchdog timeout. I can't send files more then
100MB via network. This problem
I have no first hand experience with this particular problem, but it's
almost common knowledge RealTek nics are great because they are cheap,
not because they are of good quality. The phrase piece of crap has
been uttered more than once in relation to these nics.
I have three of them, and
, the kernel says that
rl0: watchdog timeout.
I can't send files more then 100MB via network. This problem
is because of my PC configuration - Motherboard GB K8N,
chipset nforce 3. Unfortunately, even FreeBSD 5.3 can't handle
it (but it's better then 5.2.1). Maybe someone has already met
Hi:
I'm using 5.2.1, and today when I was transferring files between two
different FreeBSD boxes, the 5.2.1 machine's network hung with the
following messages to /var/log/messages:
Jul 31 10:07:42 belle kernel: sk0: watchdog timeout
FWIW, the network is builtin ASUS P4P-800SE motherboard:
skc0
Hi all!
Installing 5.2 on my new box with an integraded Intel PRO 1000 CT NIC.
System detects it as em0 but I cant get it to work. I'm trying dhcp and
I have added the line: ifconfig_em0=DHCP in rc.conf but I still get
this problem.
em0: Watchdog Timeout ---Resetting
IF I disable ACPI it works
Henrik Zagerholm wrote:
Hi all!
Installing 5.2 on my new box with an integraded Intel PRO 1000 CT NIC.
System detects it as em0 but I cant get it to work. I'm trying dhcp
and I have added the line: ifconfig_em0=DHCP in rc.conf but I still
get this problem.
em0: Watchdog Timeout ---Resetting
.
em0: Watchdog Timeout ---Resetting
IF I disable ACPI it works perfectly so I think it's IRQ related or?
Please note that I am not associated with the Project
while you read this.
I think that this is a bug with the em driver on the 5.X
series. You did note that it's a new technology release
I recently posted about a bge0 watchdog timeout problem
at 5.2.1 but the problem seems more complicated and seems
to be in touch with the machine I use itself
as I have changed the ethernet board for a 3com
I have now the message
xl0 watchdog timeout
The machine is a HP xw 3100
--
Cordialement
Nelis Lamprecht a écrit :
On Mon, 2004-04-05 at 13:52, Frank Bonnet wrote:
Hi
I've recently installed a 5.2.1 on a HP box that use a Broadcom BCM570x
gigabit ethernet controller chips
When booting up the machine I have the following error message
to the console
bge0 Watchdog timeout
I know
Hi
I've recently installed a 5.2.1 on a HP box that use a Broadcom BCM570x
gigabit ethernet controller chips
When booting up the machine I have the following error message
to the console
bge0 Watchdog timeout
I am unable to use the network on this machine
I've reinstalled a 4.9-R
On Mon, 2004-04-05 at 13:52, Frank Bonnet wrote:
Hi
I've recently installed a 5.2.1 on a HP box that use a Broadcom BCM570x
gigabit ethernet controller chips
When booting up the machine I have the following error message
to the console
bge0 Watchdog timeout
I know the BCM5704 had
which
includes these errors), and I also get a watchdog timeout for all of the 4
different network cards I've used in the machine. I've used:
2x Linksys LNE100TX v4 (dc driver)
1x Generic Belkin card (rl driver)
1x Intel Pro/100 (fxp driver)
My guess is that these two problems are probably related
Hi!
Our Samba server (on a 4.8 -RELEASE machine) frequently freezes
with these error-messages:
rl0: watchdog timeout
ahc0: Timeout SCB already complete. Interrupts may not be
functioning
What does this mean?
Thanks for all answers, this is quite important.
Regards,
Uli
It means that your network card (rl0) is going (or has gone) bad.
Replace it, and it should go away.
Peter Elsner
At 08:23 AM 10/28/2003, you wrote:
Hi!
Our Samba server (on a 4.8 -RELEASE machine) frequently freezes
with these error-messages:
rl0: watchdog timeout
ahc0: Timeout SCB already
Peter Ulrich Kruppa [EMAIL PROTECTED] writes:
Our Samba server (on a 4.8 -RELEASE machine) frequently freezes
with these error-messages:
rl0: watchdog timeout
ahc0: Timeout SCB already complete. Interrupts may not be
functioning
What does this mean?
Thanks for all answers
What I do is hit Ctrl-C. This is probably not the best way but it works...
-Stephen
If I boot FreeBSD 5.1-RELEASE with no cable attached to the NIC, I get a
slew of dc0: watchdog timeout errors. Sometimes, I want to boot and
run the system without being physically connected to the network
If I boot FreeBSD 5.1-RELEASE with no cable attached to the NIC, I get a
slew of dc0: watchdog timeout errors. Sometimes, I want to boot and
run the system without being physically connected to the network. Is
there any way to get rid of the timeout errors short of disabling
networking all
/loader.conf file:
hw.pcic.irq=0
hw.pcic.intr_path=1
Now, FreeBSD boots very well, all others network cards are working properly
(1 NE2000 ISA card and 1 Realtek PCI card), but I always get the following
line
just after pccardd setups the card:
wi0: watchdog timeout.
I looked on the web
Hi,
I'm having some problems transferring large files at a high rate of
speed over my LAN. I can get about 8mb/sec for about 7 seconds or less,
then i get the following in console:
Nov 23 14:26:19 ns1 kernel: dc0: watchdog timeout
and the ethernet card freezes and my download stops.
Any ideas
seconds or less,
then i get the following in console:
Nov 23 14:26:19 ns1 kernel: dc0: watchdog timeout
and the ethernet card freezes and my download stops.
Any ideas?
Thanks,
Patrick Fish
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions
96 matches
Mail list logo
