From: Jarek Poplawski <jarkao2@gmail.com>
To: denys@visp.net.lb
Cc: netdev@vger.kernel.org
Subject: Re: NMI lockup, 2.6.26 release
Date: Tue, 22 Jul 2008 23:36:03 +0200 [thread overview]
Message-ID: <20080722213603.GA3026@ami.dom.local> (raw)
In-Reply-To: <200807222346.36284.denys@visp.net.lb>
On Tue, Jul 22, 2008 at 11:46:36PM +0300, denys@visp.net.lb wrote:
> First patch - probably not related. Netconsole is on e100.
> Second patch looks reasonable, because there is external interface (it is router) and e1000e there, with enabled TSO. Maybe some scanning tools doing connect to SSH and... BOOM.. i will try to patch it, thanks a lot!
On the other hand, it seems the corruption of skbs fixed by this
second patch should probably show in some other places...
I wonder if you tried to run this without netconsole (or maybe
netconsole on another dev/driver) or without this NMI watchdog,
and similar lockups still happened?
Jarek P.
>
> On Tuesday 22 July 2008, Jarek Poplawski wrote:
> > Jarek Poplawski wrote, On 07/22/2008 10:13 PM:
> >
> > > denys@visp.net.lb wrote, On 07/22/2008 08:42 PM:
> > >
> > >> workload: ifb shapers, HTB, nat, 1 e1000, 3 e100 (heavily used only two e100)
> > >>
> > >
> > >
> > > Maybe it's unconnected but I'd recommend to try this fresh patch for
> > > possible problems with e1000e vs. netconsole:
> > >
> > > http://permalink.gmane.org/gmane.linux.network/100581
> >
> >
> > ...and if you have TSO enabled, here is another "maybe unconnected"
> > recommendation:
> >
> > http://permalink.gmane.org/gmane.linux.network/99585
> >
> > Jarek P.
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe netdev" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
>
>
next prev parent reply other threads:[~2008-07-22 21:35 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 [this message]
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
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=20080722213603.GA3026@ami.dom.local \
--to=jarkao2@gmail.com \
--cc=denys@visp.net.lb \
--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).