From: Martin Lorenz <martin@lorenz.eu.org>
To: Jan Beulich <jbeulich@novell.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc3: more DWARFs and strange messages
Date: Thu, 2 Nov 2006 10:48:50 +0100 [thread overview]
Message-ID: <20061102094850.GC6299@gimli> (raw)
In-Reply-To: <4549CA86.76E4.0078.0@novell.com>
On Thu, Nov 02, 2006 at 09:37:58AM +0000, Jan Beulich wrote:
> >what is a reasonable kstack parameter to be informative for you?
>
> This unfortunately depends on the depth of the stack that is in use
> at the point the dump is taken. The only safe value would be to
> dump the full stack size (kstack=1024 for 4k stack, kstack=2048
> for 8k ones), but since it'll stop at a stack boundary perhaps that's
> what you should go with.
>
> As to Andi's remark regarding WARN_ON() - you'd have to address
> that issue in a private patch first, or the addition of the kstack=
> parameter will be useless. I presume it's likely you don't have the
> time to do that...
well...
to be honest, I need my computer to work during usual daily business
at the moment I can afford to do a compile and test a new kernel once a day,
but if it introduces instabilities that make my computer unusable for
productive work (which means programming, running heavy java applications
and and TeXing) I can't run it for more than a few minutes.
I started a bisection last weekend but had to give up after three
compile-reboot cycles.
so, please don't expect too much, but I will do my best to help
gruss
mlo
--
Dipl.-Ing. Martin Lorenz
They that can give up essential liberty
to obtain a little temporary safety
deserve neither liberty nor safety.
Benjamin Franklin
please encrypt your mail to me
GnuPG key-ID: F1AAD37D
get it here:
http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0xF1AAD37D
ICQ UIN: 33588107
next prev parent reply other threads:[~2006-11-02 9:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-28 20:01 2.6.19-rc3: more DWARFs and strange messages Martin Lorenz
2006-10-31 14:31 ` Andi Kleen
2006-10-31 16:08 ` Martin Lorenz
2006-10-31 16:28 ` Jan Beulich
2006-10-31 17:28 ` Andi Kleen
2006-11-01 15:27 ` Martin Lorenz
2006-11-02 9:37 ` Jan Beulich
2006-11-02 9:48 ` Martin Lorenz [this message]
[not found] ` <20061031170320.GA6227@gimli>
2006-11-02 10:56 ` Jan Beulich
2006-11-08 16:19 ` Jan Beulich
2006-11-06 10:54 ` Adrian Bunk
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=20061102094850.GC6299@gimli \
--to=martin@lorenz.eu.org \
--cc=ak@suse.de \
--cc=jbeulich@novell.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.