From: Jarek Poplawski <jarkao2@gmail.com>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: netdev@vger.kernel.org
Subject: Re: RESEND, HTB(?) softlockup, vanilla 2.6.24
Date: Sun, 17 Feb 2008 10:11:47 +0100 [thread overview]
Message-ID: <20080217091147.GA6093@ami.dom.local> (raw)
In-Reply-To: <20080216235419.M80874@visp.net.lb>
On Sun, Feb 17, 2008 at 02:03:33AM +0200, Denys Fedoryshchenko wrote:
> 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.
I guess you mean the patches mentioned in the "BUG/ spinlock lockup";
they could be useful, but we are not sure this is the same problem.
Anyway, if there are really stack overflows then we don't need any
bug report after this: with stack data corrupted they would show some
"false" problems. We need to find which code overflows and why. If you
want to debug this, then try to make this more reproducible e.g. with
CONFIG_4KSTACKS; anyway you should always turn on these options with
such problems: CONFIG_DEBUG_STACKOVERFLOW CONFIG_DEBUG_STACK_USAGE.
> Is there any project to dump console messages/kernel dump to disk? For
...
I don't know, but there is probably something better: a project by
Intel to save this in some cpu memory (or something...). But again:
we don't need corrupted messages after stack overflow, and, if we
don't let for this, maybe these netconsole messages would be properly
printed and quite enough...
> 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.
I'm not sure what do you mean by MTD emulation: it should be used with
MTD devices only, I presume?
Regards,
Jarek P.
PS: BTW, for HTB with actions I recommend my "sch_htb: htb_requeue fix",
available in 2.6.25-rc.
prev parent reply other threads:[~2008-02-17 9:08 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
2008-02-17 9:11 ` Jarek Poplawski [this message]
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=20080217091147.GA6093@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).