v 06)
>
> By a heavy traffic i get the following error:
> NETDEV WATCHDOG: eth1 (r8169): transmit queue 0 timed out
>
> As a workaround a turned off jumbo frames support. Is there any other
> solution making it possible to use jumbo frames??
>
> Thanks for any help in advance.
On Mon, Aug 20, 2018 at 05:57:16PM +, Grzegorz Sójka wrote:
By a heavy traffic i get the following error:
NETDEV WATCHDOG: eth1 (r8169): transmit queue 0 timed out
As a workaround a turned off jumbo frames support. Is there any other
solution making it possible to use jumbo frames
(rev 06)
By a heavy traffic i get the following error:
NETDEV WATCHDOG: eth1 (r8169): transmit queue 0 timed out
As a workaround a turned off jumbo frames support. Is there any other
solution making it possible to use jumbo frames??
Thanks for any help in advance.
Looks like this:
https
v 06)
>
> By a heavy traffic i get the following error:
> NETDEV WATCHDOG: eth1 (r8169): transmit queue 0 timed out
>
> As a workaround a turned off jumbo frames support. Is there any other
> solution making it possible to use jumbo frames??
>
> Thanks for any
Hi there,
I have following integrated network adapter:
# lspci -s 02:00
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
By a heavy traffic i get the following error:
NETDEV WATCHDOG: eth1 (r8169): transmit queue
On 06/07/2017 07:33 PM, Dekks Herton wrote:
If you have a thinkpad and use tlp you can set the NMI watchdog to off
in /etc/default/tlp
I do have tlp installed. Here's what is in the file. Looks like it's
already disabled:
# Kernel NMI Watchdog:
# 0=disable (default, saves
If you have a thinkpad and use tlp you can set the NMI watchdog to off
in /etc/default/tlp
also look at /proc/sys/kernel/nmi_watchdog to see the state
RavenLX writes:
> I was trying to find a way to fix this warning on my Thinkpad. I have
> found out that it is normal for this to
I was trying to find a way to fix this warning on my Thinkpad. I have
found out that it is normal for this to happen and can safely be ignored.
Reference links:
https://bbs.archlinux.org/viewtopic.php?id=153205
https://unix.stackexchange.com/questions/249654/message-at-shutdown-watchdog-did
nfusion. I didn't mean to be rude by replying here,
where I should have posted in the first place.
...To get back on topic, I am happy to give any suggestion a shot and am
anxious to get Hardware Watchdog up and running.
Thanks,
Azeem
On 2/15/2015 1:21 PM, Lisi Reisz wrote:
On Sunday 1
gt;).
Why not just reply to me and leave your reply in the thread my original was
in?? You're using Thunderbird, which replies just fine.
Lisi
>
> ***
>
> More info:
>
> Initially I tried 'freeipmi' that also installs 'freeipmi-bmc-watchdog';
> however, th
ard.
Thanks Lisi. I am still trying to figure all of this out. In responding
I have picked the primary thread (Message ID: <54e0d884.1040...@gmail.com>).
***
More info:
Initially I tried 'freeipmi' that also installs 'freeipmi-bmc-watchdog';
however, the same issues re
ything I can think of to
> > get hardware watchdog setup but the server keeps rebooting after 5
> > minutes. Please help.
> >
> > Motherboard: X9DRH-7TF
You created a new thread in the first place. (According to KMail, and even to
Gmail.) That is three times that we have
Sorry Jack for posting under your thread. Please disregard this email. I
have created a new thread. Once again my apologies.
On 2/14/2015 11:46 PM, Azeem Esmail wrote:
I have been searching google and trying everything I can think of to
get hardware watchdog setup but the server keeps
(Sorry my previous message did not create a new thread.)
I have been searching google and trying everything I can think of to get
hardware watchdog setup but the server keeps rebooting after 5 minutes.
What am I doing wrong, and what do I need to do to get hardware watchdog
working in Debian
I have been searching google and trying everything I can think of to get
hardware watchdog setup but the server keeps rebooting after 5 minutes.
What am I doing wrong, and what do I need to do to get hardware watchdog
working in Debian Jessie. Please help.
Motherboard: X9DRH-7TF
***
List
Hello,
we operate a server running wheezy and with a SuperMicro BMC¹ and
experience random reboots.
¹) http://www.supermicro.com/products/motherboard/Xeon/C600/X9DRW-iF.cfm
I think I traced them back to the BMC watchdog, which we have
enabled:
ipmitool> bmc watchdog get
Watchdog Timer
I'dd suggest you look at monit.
"monit is a utility for monitoring and managing daemons or similar
programs running on a Unix system. It will start specified programs if
they are not running and restart programs not responding."
http://packages.debian.org/squeeze/monit
it is a quite popular tool
Hi all,
I am looking for a debian package, which can do the following:
- supervision of other background processes
- taking actions when the other background process dies (i.e.
restarting, starting recovery procedures, sending email, etc ... )
Is there another package doing similar things for fi
Is there a good howto for it?
Did anyone tried building one?
thanks
Hello,
I am using Lenny (kernel : 2.6.26-2-686).
After I start my computer, in a few minutes, I lose my Network connection
with a kernel failure. In the error logs, it is saying that:
" r8169: eth0: link up
[ 3129.367003] NETDEV WATCHDOG: eth0: transmit timed out"
However, more interes
Hi to all,
I am running some older Fujitsu Primergy Servers (RX300 S2 and RX100 S3).
All these servers have an activated hardware watchdog (IPMI watchdog) and
the Debian package watchdog is installed. Sometimes these servers just
reboot without any reason. The times of these reboots differ and
look okay to me...]
...
Freeing unused kernel memory: 140k freed
Watchdog Reset
At that point the boot process apparently stops, and I am dumped back into
Sun's BIOS console. What is a "watchdog reset?"
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "u
Sven Arvidsson wrote:
On Wed, 2007-01-24 at 11:13 +0100, Serban Udrea wrote:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status , PHY status 786d, resetting...
eth0: Setting full-duplex based on MII #1 link partner capability of 41e1
The box is running an uptodate
On Wed, 2007-01-24 at 11:13 +0100, Serban Udrea wrote:
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out, status , PHY status 786d, resetting...
> eth0: Setting full-duplex based on MII #1 link partner capability of 41e1
>
> The box is running an uptodate
Hello!
Since about one week I receive at irregular intervals messages like the
following at the console (tty1) and in kern.log:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status , PHY status 786d, resetting...
eth0: Setting full-duplex based on MII #1 link partner
Lately I am getting kernel messages like this:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status , resetting...
They appear in /var/log/messages and also at the console where I am
working, even being inserted into text I am editing.
My kernel is 2.6.11, my
On Mon, 2004-06-14 at 03:53, Henrique de Moraes Holschuh wrote:
> On Sun, 13 Jun 2004, Henrique de Moraes Holschuh wrote:
> > > i8xx TCO timer: initialized (0x1060). heartbeat=30 sec (nowayout=0)
> >
> > nowayout=0 means it should shutdown the watchdog on close. Y
On Sun, 13 Jun 2004, Henrique de Moraes Holschuh wrote:
> > i8xx TCO timer: initialized (0x1060). heartbeat=30 sec (nowayout=0)
>
> nowayout=0 means it should shutdown the watchdog on close. You have
> a kernel bug. Someone else reported the same problem here. You're the
image 2.6.6-1-686-smp). No problems with a 2.4
> kernel.
This is a severe hint of a terminally defective i810_tco module in the
2.6 kernel. It must *NOT* activate the watchdog, for whatever reason,
unless someone opens /dev/watchdog.
> Installing the watchdog package didn't help. In
ernel.
I finally discovered it was the i810 watchdog timer on the motherboard,
that I hadn't been aware of previously. When the watchdog module was
loaded it probably started the timer and since there was no program that
wrote to /dev/watchdog the system would hard reset a minute later.
I had recently the same problem
I have a very old system and I had a find & grep over / so I forgot to
exclude /dev as I did with /var/log and got some
grep: /dev/kmem: Bad address
grep: memory exhausted
grep: memory exhausted
after this I looked over the log files and found the message from the
On Tue, 28 Oct 2003, ScruLoose wrote:
> On Mon, Oct 27, 2003 at 10:06:18PM -0500, ScruLoose wrote:
> > Hi all,
>
> Still pluggin' away at this problem with my D-Link DFE-530TX NIC.
>
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out,
I have since tried specifying an IP and netmask on the ifconfig command
line, and adding a route to my gateway.
These seem to work fine, according to the output of ifconfig and route.
But then when I try to ping the gateway, I get this:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit ti
GROUP securiQ.Watchdog
Server: KTC_HQ2
---
Your mail item contained attachments that have been infected with a virus.
Please contact your administrator
---
Mail-
On Sun, Feb 23, 2003 at 12:27:20AM +0100, Ulf Janitschke wrote:
> Hi,
>
> i had the same problem. First with a 'D-Link'-card with Via-Rhine Chipset.
> With a 2.2 kernel everything was fine. With the 2.4 i got 'netdev watchdog
> eth0 transmit timed out'. T
Hi,
i had the same problem. First with a 'D-Link'-card with Via-Rhine Chipset.
With a 2.2 kernel everything was fine. With the 2.4 i got 'netdev watchdog
eth0 transmit timed out'. The problem showed up with both, the 2.4.16 and
2.4.18 kernel.
Same thing with a RTL8139-ca
ing woody.
> > everything has gone well apart from this message which keeps coming
> > through every now and then:
> >
> > netdev watchdog eth0 transmit timed out
> >
> > i used the 2.4 kernel which came with the disks - 2.4.18-bf2.4. the
> > network cards
On Sun, Feb 02, 2003 at 11:42:58AM +1100, Sam Varghese wrote:
> g'day all,
>
> i've just set up a debian box for use as a server, using woody.
> everything has gone well apart from this message which keeps coming
> through every now and then:
>
> netdev watchdog
;ve just set up a debian box for use as a server, using woody.
> > everything has gone well apart from this message which keeps coming
> > through every now and then:
> >
> > netdev watchdog eth0 transmit timed out
> >
> > i used the 2.4 kernel which came
gh every now and then:
>
> netdev watchdog eth0 transmit timed out
>
> i used the 2.4 kernel which came with the disks - 2.4.18-bf2.4. the
> network cards on the box both use the rtl8139 module.
just found out and confirmed w/ other mb/systems ... that
the onboard rtl (phy) chip
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
g'day all,
i've just set up a debian box for use as a server, using woody.
everything has gone well apart from this message which keeps coming
through every now and then:
netdev watchdog eth0 transmit timed out
i used the 2.4 kernel which
I'm getting thousands of these all the time and the network keeps
stopping.
--
This is on a DWL-650 network card. I have also seen this on an
ISA 3com 905 card as well.
What is NETDEV WATCHDOG?
How can this get fixed?
--
Dec 7 15:45:32 thorin last message repeated 8 times
Dec 7 15:
On Mon, 17 Dec 2001, David Z Maze wrote:
> temperature from one line at a time. It doesn't look like lm-sensors
> exports such a special file; it's not clear what this support in
> watchdog was supposed to be used with. (If nothing else, there's the
> question of &quo
Paul Johnson <[EMAIL PROTECTED]> writes:
PJ> When using sensord/lm-sensors, what device should the software watchdog
PJ> check to see what the CPU temperature is?
*looks at watchdog source* Hmm. It looks like watchdog expects there
to be a character device (or maybe a pipe) that it
When using sensord/lm-sensors, what device should the software watchdog
check to see what the CPU temperature is?
--
Baloo
On Oct 09 2001, rogério wrote:
> isto só tem ocorrido porqeu ao fazer uma atualização para o kernel
> 2.4.9-k6 do kernel.2.2.18 não consegui que o módulo ne2k-pci seja
> carregado pelo kernel o único que eu consegui foi o tulip
You can't just load the tulip module and expect it to w
o módulo do kernel2.4.9-k6 carregado no boot é o tulip e após um pequeno
tempo de uso aparece o seguinte informe:
METDEV WATCHDOG: eth0: transmit time out
isto só tem ocorrido porqeu ao fazer uma atualização para o kernel
2.4.9-k6 do kernel.2.2.18 não consegui que o módulo ne2k-pci seja
WATCHDOG: eth1: transmit timed out
Mar 10 00:38:33 maniac kernel: eth1: Tx timed out, lost interrupt?
TSR=0x3, ISR=0x3, t=112.
How comes? The interface is an ne2k-pci (as is the other one to the
internet).
--
Tschoe,Get my gpg-public-key here
Jens http
Please forward to my attention any information that you have on the purchase
price of a firewall called Watchdog FB @fAST VPN.I NEED TO KNOW WHERE I CAN
PURCHASE THE HARDWARE AND THE OPTION FOR THE ANTI-VIRUS SOFTWARE THAT CAN BE
USED ON THIS SYSTEM!!!
PLEASE E-MAIL ME AT [EMAIL PROTECTED]
Thank
rozen, neither mouse nor keyboard will generate any
> event.
>
> I´ve already tried changing all I have on spare (read RAM and graphics
> adapter).
>
> Since there´s not even a single syslog-entry, I don´t really know where
> to start debugging. Would it make sense if I
On Sat, 08 Jul 2000 12:32:32 +1200, "C. Falconer" writes:
>1) Temperature... has a CPU fan, case fan, or PSU fan seized up and
>died?
no, all fans running fine (see
<[EMAIL PROTECTED]>)
>2) Have you changed anything recently? moved it, rebooted it, run a
>new kernel?
no, the hardw
imply get a new used PC (used
P1´s are for sale at about $ 100) when I´m back from the trip, what I
need for the time being is a solution where it would simply reboot
when having trouble, and I _guess_ the software watchdog _may_ be what
I´m looking for in this case.
tia,
&rw
keyboard will generate any
event.
I´ve already tried changing all I have on spare (read RAM and graphics
adapter).
Since there´s not even a single syslog-entry, I don´t really know where
to start debugging. Would it make sense if I installed the "software
watchdog" into the kernel in thi
&rw wrote:
>
> Hi!
>
> My home-debian-box starts to behave rather odd lately, now and then it
> will freeze completely.
>
Is there anything consistent about the behavior? How long between reboot
and freeze? Are there any error messages during startup? What
applications are running when the
rozen, neither mouse nor keyboard will generate any
> event.
>
> I´ve already tried changing all I have on spare (read RAM and graphics
> adapter).
>
> Since there´s not even a single syslog-entry, I don´t really know where
> to start debugging. Would it make sense if I installed
spare (read RAM and graphics
adapter).
Since there´s not even a single syslog-entry, I don´t really know where
to start debugging. Would it make sense if I installed the "software
watchdog" into the kernel in this case, so that the machine would
(eventually) reboot when it hangs? Thi
Hi,
Today watchdog restarted my machine:
Sep 24 09:02:16 xxx watchdog[911]: test binary returned 247
Sep 24 09:02:25 xxx watchdog[911]: shutting down the system because of error 247
[...]
Sep 24 09:06:14 xxx watchdog[308]: starting daemon (4.5): int=10s
realtime=no sync=no soft=no mla=25 ping
-BEGIN PGP SIGNED MESSAGE-
Hello!
On Wed, 16 Sep 1998, Pere Camps wrote:
> Hi!
>
> Anybody know a good (cheap too!) UPS that can also work as a UPS
> for debian?
>
> I guess 400W would do it. It's only a K6 and a 15" monitor.
I would like to suggest you to buy a BestPower
Hi!
Anybody know a good (cheap too!) UPS that can also work as a UPS
for debian?
I guess 400W would do it. It's only a K6 and a 15" monitor.
TIA!
Salutacions, Pere __oUltima Ratio Regum
2:343/108.91 - _`\<;_mailto:[EMAIL PROTE
>
> Hi,
>
> One of our network servers went down for reboot in the middle of last
> night, which was done by the software watchdog.
>
> The log message was as follows:
>
> daemon.log:Apr 10 03:15:44 seldon watchdog[102]: process table is full!
> daemon.log:Apr 1
On Fri, Apr 10, 1998 at 12:02:28PM +1000, Chris wrote:
>
> Hi,
>
> One of our network servers went down for reboot in the middle of last
> night, which was done by the software watchdog.
>
> The log message was as follows:
>
> daemon.log:Apr 10 03:15:44 seldon watc
Hi,
One of our network servers went down for reboot in the middle of last
night, which was done by the software watchdog.
The log message was as follows:
daemon.log:Apr 10 03:15:44 seldon watchdog[102]: process table is full!
daemon.log:Apr 10 03:15:44 seldon watchdog[102]: shutting down the
-BEGIN PGP SIGNED MESSAGE-
Hi all again!
Anybody here uses this kind of cards?
Are they "reliable"?
Are you satisfied with it?
Any kind comment about it will be greatly appreciated,
Ulisses
- -
"Compute
Maybe your program that opens the watchdog device is running before the
watchdog file get loaded. Look through your logs for load order. You may
need to edit your /etc/init.d/boot or modules file.
Good luck,
Al Youngwerth
[EMAIL PROTECTED]
--
> From: Stefan Baums <[EMAIL PRO
Bruce Perens wrote:
>
> It sounds as if the watchdog daemon tries to start before the software
> watchdog kernel module is loaded. Is watchdog in /etc/modules?
Yup, you're right. In /etc/modules, I activated "auto" (letting kerneld
take care of things) and deactivate
>>>>> "SB" == Stefan Baums <[EMAIL PROTECTED]> writes:
SB> I'm running Debian 1.3.0, kernel 2.0.30, and my software watchdog
SB> timer is having trouble starting getting started at boot time. The
SB> .deb installed all right, my kerne
It sounds as if the watchdog daemon tries to start before the software
watchdog kernel module is loaded. Is watchdog in /etc/modules?
Thanks
Bruce
--
Bruce Perens K6BP [EMAIL PROTECTED] 510-215-3502
Finger [EMAIL PROTECTED] for PGP public key.
PGP fingerprint = 88 6A 15 D0
Hello,
I'm running Debian 1.3.0, kernel 2.0.30, and my software watchdog timer
is having trouble starting getting started at boot time. The .deb
installed all right, my kernel is configured
CONFIG_WATCHDOG=y
CONFIG_WATCHDOG_NOWAYOUT=y
# CONFIG_WDT is no
Fooling around yesterday with the 2000 date, I managed to send
the system into a tailspin which caused the installed watchdog
to reboot due to a high load. No, I wasn't expecting this. ;-)
It would be nice if watchdog would run the shutdown scripts and
reboot cleanly, is there a way to do
69 matches
Mail list logo
