From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Giuseppe Sacco <giuseppe@eppesuigoccas.homedns.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: new kernel oops in recent kernels
Date: Sun, 16 Mar 2008 13:47:50 -0500 [thread overview]
Message-ID: <1205693270.6767.99.camel@localhost.localdomain> (raw)
In-Reply-To: <1205692360.5470.6.camel@localhost>
On Sun, 2008-03-16 at 19:32 +0100, Giuseppe Sacco wrote:
> Hi James,
>
> Il giorno dom, 16/03/2008 alle 11.39 -0500, James Bottomley ha scritto:
> > On Sun, 2008-03-16 at 16:19 +0100, Giuseppe Sacco wrote:
> [...]
> > This is a bit strange. It's obviously O2 specific, which makes it a lot
> > harder. Can you compile the kernel with CONFIG_DEBUG_INFO and reproduce
> > (just in case this changes the symbol layout). Then ask gdb where
> [...]
>
> I cannot find any CONFIG_DEBUG_INFO. Do you mean CONFIG_DEBUG_KERNEL?
This from lib/Kconfig.debug:
config DEBUG_INFO
bool "Compile the kernel with debug info"
depends on DEBUG_KERNEL
help
If you say Y here the resulting kernel image will include
debugging info resulting in a larger kernel image.
This adds debug symbols to the kernel and modules (gcc -g), and
is needed if you intend to use kernel crashdump or binary object
tools like crash, kgdb, LKCD, gdb, etc on the kernel.
Say Y here only if you plan to debug the kernel.
If unsure, say N.
It does depend on CONFIG_DEBUG_KERNEL according to the depends clause.
James
next prev parent reply other threads:[~2008-03-16 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-16 15:19 new kernel oops in recent kernels Giuseppe Sacco
2008-03-16 16:39 ` James Bottomley
2008-03-16 18:32 ` Giuseppe Sacco
2008-03-16 18:47 ` James Bottomley [this message]
2008-03-16 16:42 ` Matthew Wilcox
2008-03-16 18:29 ` Giuseppe Sacco
2008-03-17 3:58 ` Matthew Wilcox
2008-03-17 4:41 ` Matthew Wilcox
2008-03-17 8:17 ` Giuseppe Sacco
-- strict thread matches above, loose matches on Subject: below --
2008-03-16 10:49 Giuseppe Sacco
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=1205693270.6767.99.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=giuseppe@eppesuigoccas.homedns.org \
--cc=linux-scsi@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.