From: denys@visp.net.lb
To: denys@visp.net.lb
Cc: Jarek Poplawski <jarkao2@gmail.com>, netdev@vger.kernel.org
Subject: Re: NMI lockup, 2.6.26 release
Date: Thu, 24 Jul 2008 17:56:43 +0300 [thread overview]
Message-ID: <200807241756.43595.denys@visp.net.lb> (raw)
In-Reply-To: <200807240256.36098.denys@visp.net.lb>
Nothing yet. Still waiting, in 6 hours i will have "peak time".
But yesterday with same settings(without patch) it crashed 3 times.
It is Core2Duo E6750 CPU, clocksource is TSC.
TSC synchronization is always passed. HPET is available, so in case... i can try it too.
It was crashing with nmi_watchdog=1(at least it brings crash message) and without it (hard lockup).
Fishy point is ifb, but i have few hundreds of NAS servers with ifb + htb
(but sure not 300-400 Mbps like on this host) and i check weekly log on all of them - none of them crashed.
So it is or hardware specific (but it is crashing always in same point),
even maybe memory corruption, it is not a server-grade equipment, but it crashes always in same place, same way.
I have running MCE, so if there is thermal events - it must catch it.
But sure there is large list of errata for this hardware :-)
On Thursday 24 July 2008, denys@visp.net.lb wrote:
> I dont have any problem to restart :-)
> Build system and restart (over kexec) is automated..
> Rebooting now.
next prev parent reply other threads:[~2008-07-24 14:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 18:42 NMI lockup, 2.6.26 release denys
2008-07-22 20:13 ` Jarek Poplawski
2008-07-22 20:35 ` Jarek Poplawski
2008-07-22 20:46 ` denys
2008-07-22 21:36 ` Jarek Poplawski
2008-07-22 21:45 ` denys
2008-07-23 19:47 ` denys
2008-07-23 21:09 ` Jarek Poplawski
2008-07-23 22:26 ` Jarek Poplawski
2008-07-23 23:24 ` Jarek Poplawski
2008-07-23 23:56 ` denys
2008-07-24 14:56 ` denys [this message]
2008-07-24 17:45 ` Jarek Poplawski
2008-07-25 7:36 ` Jarek Poplawski
2008-07-25 21:09 ` denys
2008-07-25 22:31 ` hrtimers lockups " Jarek Poplawski
2008-08-02 12:55 ` Denys Fedoryshchenko
2008-08-02 13:07 ` Jarek Poplawski
2008-08-12 11:31 ` Denys Fedoryshchenko
2008-08-12 12:40 ` Jarek Poplawski
2008-08-13 7:28 ` Denys Fedoryshchenko
2008-08-13 7:43 ` Jarek Poplawski
2008-08-13 8:02 ` Denys Fedoryshchenko
2008-08-13 8:49 ` Jarek Poplawski
2008-08-13 9:08 ` Denys Fedoryshchenko
2008-08-14 15:07 ` Denys Fedoryshchenko
2008-08-14 15:10 ` New: softlockup in 2.6.27-rc3-git2 Denys Fedoryshchenko
2008-08-15 13:13 ` NMI lockup, 2.6.26 release Denys Fedoryshchenko
2008-08-15 14:16 ` 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=200807241756.43595.denys@visp.net.lb \
--to=denys@visp.net.lb \
--cc=jarkao2@gmail.com \
--cc=netdev@vger.kernel.org \
/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).