From: Ed Tomlinson <tomlins@cam.org>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.70-mm1
Date: Tue, 27 May 2003 19:05:24 -0400 [thread overview]
Message-ID: <200305271905.24181.tomlins@cam.org> (raw)
In-Reply-To: <20030527134946.7ffd524d.akpm@digeo.com>
On May 27, 2003 04:49 pm, Andrew Morton wrote:
> Ed Tomlinson <tomlins@cam.org> wrote:
> > Hi Andrew,
> >
> > This one oops on boot 2 out of 3 tries.
> >
> > ...
> > EIP is at load_module+0x7c5/0x800
>
> -mm has modules changes. Is CONFIG_DEBUG_PAGEALLOC enabled?
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_SLAB=y
# CONFIG_DEBUG_IOVIRT is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_SPINLINE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_KALLSYMS=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_KGDB is not set
CONFIG_DEBUG_INFO=y
CONFIG_FRAME_POINTER=y
No. I have been running 69-mm8 for several days without problems. It
would seem to be an initialization problem, 70-mm1 has now been 3 hours
here.
Ed
WARNING: multiple messages have this Message-ID (diff)
From: Ed Tomlinson <tomlins@cam.org>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.70-mm1
Date: Tue, 27 May 2003 19:05:24 -0400 [thread overview]
Message-ID: <200305271905.24181.tomlins@cam.org> (raw)
In-Reply-To: <20030527134946.7ffd524d.akpm@digeo.com>
On May 27, 2003 04:49 pm, Andrew Morton wrote:
> Ed Tomlinson <tomlins@cam.org> wrote:
> > Hi Andrew,
> >
> > This one oops on boot 2 out of 3 tries.
> >
> > ...
> > EIP is at load_module+0x7c5/0x800
>
> -mm has modules changes. Is CONFIG_DEBUG_PAGEALLOC enabled?
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_DEBUG_STACKOVERFLOW=y
CONFIG_DEBUG_SLAB=y
# CONFIG_DEBUG_IOVIRT is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_SPINLINE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
CONFIG_KALLSYMS=y
CONFIG_DEBUG_SPINLOCK_SLEEP=y
# CONFIG_KGDB is not set
CONFIG_DEBUG_INFO=y
CONFIG_FRAME_POINTER=y
No. I have been running 69-mm8 for several days without problems. It
would seem to be an initialization problem, 70-mm1 has now been 3 hours
here.
Ed
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-05-27 22:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 7:42 2.5.70-mm1 Andrew Morton
2003-05-27 7:42 ` 2.5.70-mm1 Andrew Morton
2003-05-27 10:38 ` 2.5.70-mm1 Marc-Christian Petersen
2003-05-27 10:38 ` 2.5.70-mm1 Marc-Christian Petersen
2003-05-27 20:33 ` 2.5.70-mm1 Ed Tomlinson
2003-05-27 20:33 ` 2.5.70-mm1 Ed Tomlinson
2003-05-27 20:49 ` 2.5.70-mm1 Andrew Morton
2003-05-27 20:49 ` 2.5.70-mm1 Andrew Morton
2003-05-27 23:05 ` Ed Tomlinson [this message]
2003-05-27 23:05 ` 2.5.70-mm1 Ed Tomlinson
2003-05-28 17:10 ` 2.5.70-mm1 Mingming Cao
2003-05-28 17:10 ` 2.5.70-mm1 Mingming Cao
2003-05-28 19:44 ` 2.5.70-mm1 Andrew Morton
2003-05-28 19:44 ` 2.5.70-mm1 Andrew Morton
2003-05-29 6:23 ` 2.5.70-mm1 Martin J. Bligh
2003-05-29 6:23 ` 2.5.70-mm1 Martin J. Bligh
2003-05-29 18:40 ` 2.5.70-mm1 Martin J. Bligh
2003-05-29 18:40 ` 2.5.70-mm1 Martin J. Bligh
2003-05-29 18:52 ` 2.5.70-mm1 Andrew Morton
2003-05-29 18:52 ` 2.5.70-mm1 Andrew Morton
2003-05-29 20:30 ` 2.5.70-mm1 Martin J. Bligh
2003-05-29 20:30 ` 2.5.70-mm1 Martin J. Bligh
2003-05-29 21:14 ` 2.5.70-mm1 Andrew Morton
2003-05-29 21:14 ` 2.5.70-mm1 Andrew Morton
2003-05-30 15:51 ` 2.5.70-mm1 Martin J. Bligh
2003-05-30 16:43 ` 2.5.70-mm1 Andrew Morton
2003-05-30 16:43 ` 2.5.70-mm1 Andrew Morton
2003-05-30 23:51 ` 2.5.70-mm1 Martin J. Bligh
2003-05-30 23:51 ` 2.5.70-mm1 Martin J. Bligh
2003-06-03 6:34 ` ext3 semaphore tracing Martin J. Bligh
2003-06-03 6:34 ` Martin J. Bligh
-- strict thread matches above, loose matches on Subject: below --
2003-05-28 13:26 2.5.70-mm1 Downing, Thomas
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=200305271905.24181.tomlins@cam.org \
--to=tomlins@cam.org \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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.