From: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
To: Dale Blount <linux-kernel@dale.us>, linux-kernel@vger.kernel.org
Subject: Re: Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction)
Date: Thu, 17 Feb 2005 17:00:00 +0100 [thread overview]
Message-ID: <20050217160000.GA6680@charite.de> (raw)
In-Reply-To: <4214BD6F.7080203@osdl.org>
* Randy.Dunlap <rddunlap@osdl.org>:
> >Is it normal that the kernel with debugging enabled is not larger than
> >the normal kernel?
> >-
>
> No, it should be much larger. Recheck the .config file
> for CONFIG_DEBUG_INFO=y. Maybe you need to do 'make clean'
> first.
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_KOBJECT is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_DEBUG_INFO=y
# CONFIG_FRAME_POINTER is not set
CONFIG_EARLY_PRINTK=y
I built that using "make-kpkg"
make-kpkg clean
CONCURRENCY_LEVEL=4 MAKEFLAGS="CC=gcc-3.4" make-kpkg --revision=20050217 kernel_image
--
Ralf Hildebrandt (i.A. des IT-Zentrum) Ralf.Hildebrandt@charite.de
Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155
Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962
IT-Zentrum Standort CBF send no mail to spamtrap@charite.de
prev parent reply other threads:[~2005-02-17 16:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 14:56 Oops in 2.6.10-ac12 in kjournald (journal_commit_transaction) Ralf Hildebrandt
2005-02-16 15:33 ` Jan Kara
2005-02-16 20:04 ` Ralf Hildebrandt
2005-02-16 21:54 ` Dale Blount
2005-02-16 22:00 ` Ralf Hildebrandt
2005-02-16 22:55 ` Andrew Morton
2005-02-17 10:58 ` Ralf Hildebrandt
2005-02-17 13:21 ` Ralf Hildebrandt
2005-02-17 15:51 ` Randy.Dunlap
2005-02-17 16:00 ` Ralf Hildebrandt [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=20050217160000.GA6680@charite.de \
--to=ralf.hildebrandt@charite.de \
--cc=linux-kernel@dale.us \
--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.