From: Russell King <rmk@arm.linux.org.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: Richard Purdie <rpurdie@rpsys.net>,
Wolfgang Wander <wwc@rentec.com>,
linux-mm@kvack.org
Subject: Re: 2.6.12-rc4-mm2
Date: Thu, 2 Jun 2005 22:02:13 +0100 [thread overview]
Message-ID: <20050602220213.D3468@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050516163900.6daedc40.akpm@osdl.org>; from akpm@osdl.org on Mon, May 16, 2005 at 04:39:00PM -0700
On Mon, May 16, 2005 at 04:39:00PM -0700, Andrew Morton wrote:
> (cc's added)
>
> "Richard Purdie" <rpurdie@rpsys.net> wrote:
> >
> > Russell King:
> > > On Mon, May 16, 2005 at 01:00:48PM -0700, Andrew Morton wrote:
> > >> Any idea why init is trying to exit?
> > >
> > > I was hoping you weren't going to ask me.
> > >
> > > Not really. My initial thoughts would be maybe init getting a SEGV
> > > or ILL, but normally when that happens the system is thrown into an
> > > infinite loop because of the "init is specal and doesn't get any
> > > signals it hasn't claimed" rule. Or at least that's what happens
> > > with conventional sysvinit. However, I've no idea what or how the
> > > embedded init program behaves in this respect - never had that
> > > experience yet.
> > >
> > > I guess Richard needs to work through the patch sets between the
> > > last version which worked and the next which didn't.
> >
> > After some investigation, the guilty patch is:
> > avoiding-mmap-fragmentation.patch
> > (and hence) avoiding-mmap-fragmentation-tidy.patch
> >
> > For reference, whilst debugging the error from init changed to:
> > "inconsistency detected by ld.so: ../sysdeps/generic/dl-cache.c: 235:
> > _dl_load_cache_lookup: Assertion `cache != ((void *)0)` failed!" which would
> > agree with some kind of memory corruption.
> >
> > Its a bit late for me to try and debug this further and I'm not sure I know
> > the mm layer well enough to do so anyway. With these patches removed, -mm1
> > boots fine. I'm confident the same will apply to -mm2.
>
> Great, thanks.
>
> Wolfgang, we broke ARM.
I'm not sure what happened with this, but there's someone reporting that
-rc5-mm1 doesn't work. Unfortunately, there's not a lot to go on:
http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2005-May/029188.html
Could be unrelated for all I know.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
--
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:[~2005-06-02 21:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050516130048.6f6947c1.akpm@osdl.org>
[not found] ` <20050516210655.E634@flint.arm.linux.org.uk>
[not found] ` <030401c55a6e$34e67cb0$0f01a8c0@max>
2005-05-16 23:39 ` 2.6.12-rc4-mm2 Andrew Morton
2005-05-17 0:13 ` 2.6.12-rc4-mm2 Wolfgang Wander
2005-05-17 8:38 ` 2.6.12-rc4-mm2 Richard Purdie
2005-06-02 21:02 ` Russell King [this message]
2005-06-02 22:20 ` 2.6.12-rc4-mm2 Wolfgang Wander
2005-06-02 22:28 ` 2.6.12-rc4-mm2 Richard Purdie
2005-06-04 14:18 ` 2.6.12-rc4-mm2 Richard Purdie
2005-06-04 14:43 ` 2.6.12-rc4-mm2 Richard Purdie
2005-06-05 11:39 ` 2.6.12-rc4-mm2 Richard Purdie
2005-06-05 11:45 ` 2.6.12-rc4-mm2 Russell King
2005-06-05 18:43 ` 2.6.12-rc4-mm2 Richard Purdie
2005-06-05 19:16 ` 2.6.12-rc4-mm2 Russell King
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=20050602220213.D3468@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=rpurdie@rpsys.net \
--cc=wwc@rentec.com \
/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