From: Denys Fedoryshchenko <denys@visp.net.lb>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: NMI lockup, 2.6.26 release
Date: Tue, 12 Aug 2008 14:31:40 +0300 [thread overview]
Message-ID: <200808121431.40852.denys@visp.net.lb> (raw)
In-Reply-To: <20080802130740.GA2970@ami.dom.local>
On Saturday 02 August 2008, Jarek Poplawski wrote:
> On Sat, Aug 02, 2008 at 03:55:10PM +0300, Denys Fedoryshchenko wrote:
> > Sorry for long delay, i had to make sure that old change "fixed" the
> > problem.
> >
> > Now i am running second patch, it will take also around up to one week to
> > make sure, that it is also make (or doesn't make) any changes, because
> > sometimes it takes 3-4 days till crash happen.
>
> OK, don't hurry!
>
> Cheers,
> Jarek P.
With second patch it works fine, 9 days uptime now
next prev parent reply other threads:[~2008-08-12 11:32 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
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 [this message]
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=200808121431.40852.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).