From: Denys Fedoryshchenko <denys@visp.net.lb>
To: Badalian Vyacheslav <slavon@bigtelecom.ru>
Cc: netdev@vger.kernel.org
Subject: Re: NetDev! Please help!
Date: Sat, 20 Sep 2008 21:11:01 +0300 [thread overview]
Message-ID: <200809202111.01256.denys@visp.net.lb> (raw)
In-Reply-To: <48D4F85C.8090709@bigtelecom.ru>
On Saturday 20 September 2008, Badalian Vyacheslav wrote:
> Hello all.
>
> We buy 10 Intel servers and paste it to shape traffic. After 5-15 hours
> all PC is was freeze! Kernel not see TCO watchdog at this platform and
> can't reboot it!. Soft Watchdog not reboot pc in this situation. =(
>
> At screen we see messages like this (when it freeze and i was near
> monitor):
Maybe try nmi_watchdog=1 ?
Also try http://www.nongnu.org/dmidecode/ - to check if it has IPMI.
Mine for example:
....
Handle 0x003F, DMI type 38, 16 bytes
IPMI Device Information
Interface Type: KCS (Keyboard Control Style)
Specification Version: 2.0
I2C Slave Address: 0x10
NV Storage Device Address: 0
Base Address: 0x0000000000000CA2 (I/O)
Also important to change it to newer 2.6.26.5 , because for example 2.6.26.4
have fix:
http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.26.4
....
commit 685f605a498b73759cbcbc816089e804710fcc48
Author: David S. Miller <davem@davemloft.net>
Date: Wed Aug 27 22:35:56 2008 -0700
pkt_sched: Fix return value corruption in HTB and TBF.
[ Upstream commit 69747650c814a8a79fef412c7416adf823293a3e ]
Based upon a bug report by Josip Rodin.
Packet schedulers should only return NET_XMIT_DROP iff
the packet really was dropped. If the packet does reach
the device after we return NET_XMIT_DROP then TCP can
crash because it depends upon the enqueue path return
values being accurate.
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
....
P.S. For netdev, i have one more friend - who is complaining that shapers is
crashing on Intel machines (who uses TSC, he have two different "Core" based
servers, and both is crashing). With HPET i dont have any problem on high
performance shapers (except, that it is CPU expensive). It happens on latest
2.6.26.5 too. Machine getting hard lockup, and nothing than hardware watchdog
able to recover it. They dont have experience to get actual reason of this
issue and they dont know english well to report this issue.
next prev parent reply other threads:[~2008-09-20 18:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-20 13:19 NetDev! Please help! Badalian Vyacheslav
2008-09-20 13:38 ` Badalian Vyacheslav
2008-09-20 18:11 ` Denys Fedoryshchenko [this message]
2008-09-21 16:11 ` Jarek Poplawski
[not found] ` <48D7385D.40107@bigtelecom.ru>
2008-09-22 6:53 ` Machine Check Exception " Jarek Poplawski
2008-09-22 8:05 ` Jarek Poplawski
2008-09-22 9:40 ` Badalian Vyacheslav
2008-09-22 11:24 ` Jarek Poplawski
2008-09-22 13:00 ` Badalian Vyacheslav
2008-09-22 17:23 ` Jarek Poplawski
2008-09-23 7:43 ` Badalian Vyacheslav
2008-09-23 9:25 ` Jarek Poplawski
2008-09-23 10:36 ` Badalian Vyacheslav
2008-09-23 11:57 ` Jarek Poplawski
2008-09-23 12:06 ` Jarek Poplawski
2008-09-23 12:16 ` Badalian Vyacheslav
2008-09-23 18:26 ` Jarek Poplawski
2008-09-20 18:31 ` Machine Check Exception Was: " Jarek Poplawski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200809202111.01256.denys@visp.net.lb \
--to=denys@visp.net.lb \
--cc=netdev@vger.kernel.org \
--cc=slavon@bigtelecom.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).