From: Keith Owens <kaos@ocs.com.au>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Dave Jones <davej@redhat.com>, Andrew Morton <akpm@osdl.org>,
Chuck Ebbert <76306.1226@compuserve.com>,
linux-kernel@vger.kernel.org, torvalds@osdl.org,
mita@miraclelinux.com
Subject: Re: [patch 2.6.15-current] i386: multi-column stack backtraces
Date: Wed, 18 Jan 2006 16:23:37 +1100 [thread overview]
Message-ID: <9836.1137561817@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Tue, 17 Jan 2006 18:12:20 BST." <Pine.LNX.4.61.0601171811530.18569@yvahk01.tjqt.qr>
Jan Engelhardt (on Tue, 17 Jan 2006 18:12:20 +0100 (MET)) wrote:
>> > Presumably this is going to bust ksymoops.
>>
>>Do people actually still use ksymoops for 2.6 kernels ?
>
>I think it was said often enough that people _should not_ use it for 2.6.
>Unfortunately, there are still some who do.
Some people use ksymoops because the kernel oops does not decode the
instructions. Some people use ksymoops because they run embedded
systems and cannot afford the kallsyms data. Others just use ksymoops
out of habit.
next prev parent reply other threads:[~2006-01-18 5:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 6:23 [patch 2.6.15-current] i386: multi-column stack backtraces Chuck Ebbert
2006-01-17 6:39 ` Dave Jones
2006-01-17 6:42 ` Andrew Morton
2006-01-17 7:58 ` Dave Jones
2006-01-17 8:20 ` Andrew Morton
2006-01-17 10:26 ` Keith Owens
2006-01-17 17:12 ` Jan Engelhardt
2006-01-18 5:23 ` Keith Owens [this message]
2006-01-17 10:22 ` Keith Owens
2006-01-17 18:14 ` Sam Ravnborg
2006-01-18 22:47 ` Pavel Machek
2006-01-18 3:05 Chuck Ebbert
2006-01-19 0:36 Chuck Ebbert
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=9836.1137561817@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mita@miraclelinux.com \
--cc=torvalds@osdl.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).