netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Denys Fedoryshchenko" <denys@visp.net.lb>
To: Jarek Poplawski <jarkao2@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: RESEND, HTB(?) softlockup, vanilla 2.6.24
Date: Sun, 17 Feb 2008 02:03:33 +0200	[thread overview]
Message-ID: <20080216235419.M80874@visp.net.lb> (raw)
In-Reply-To: <20080216204519.GA2739@ami.dom.local>

Server is fully redundant now, so i apply patches (but i apply both, probably 
it will make system more reliable somehow) and i enable required debug 
options in kernel. So i will try to catch this bug few more times, probably 
if it will generate more detailed info over netconsole it will be useful.

Is there any project to dump console messages/kernel dump to disk? For 
example such issues related to networking, and i guess netconsole doesn't 
always work, especially when network driver is crashed, but tech's on 
location told there is some messages running non-stop on the screen. Probably 
some generic code writing such data over x86 INT 13 (or even kernel dump?) to 
separate partition will be useful to debug this problem. I know there is some 
3rd party patches(for example LKCD), but i prefer to not apply them to not 
add more bugs.

I notice some code in MTD(CONFIG_MTD_OOPS), but i am not sure it is correct 
and will work if i will setup MTD emulation for block device.
That just idea.

On Sat, 16 Feb 2008 21:45:19 +0100, Jarek Poplawski wrote
> On Sat, Feb 16, 2008 at 12:25:31PM +0200, Denys Fedoryshchenko wrote:
> > Thanks, i will try it.
> > You think lockdep can be buggy?
> 
> Just like every code... But the main reason is it has quite 
> meaningful overhead, so could be right "in production" only after 
> lockups happen. But if it doesn't report anything anyway...
> 
> Your report shows there are quite long paths of calls during softirqs
> with some actions (ipt + mirred here?) and qdiscs, so if I'm not 
> wrong with this stack problem, this would need some optimization. 
> And, of course, there could be some additional bugs involved around too:
> otherwise it seems this should happen more often. But I don't expect
> you would try to debug this on your servers, so I hope, it simply 
> will be found BTW some day...
> 
> Regards,
> 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


--
Denys Fedoryshchenko
Technical Manager
Virtual ISP S.A.L.


  reply	other threads:[~2008-02-17  0:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13  8:13 RESEND, HTB(?) softlockup, vanilla 2.6.24 Denys Fedoryshchenko
2008-02-13  8:43 ` Jarek Poplawski
2008-02-16  8:00 ` Jarek Poplawski
2008-02-16 10:25   ` Denys Fedoryshchenko
2008-02-16 20:45     ` Jarek Poplawski
2008-02-17  0:03       ` Denys Fedoryshchenko [this message]
2008-02-17  9:11         ` 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=20080216235419.M80874@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).