From: Alexander Nyberg <alexn@telia.com>
To: Andrew Morton <akpm@osdl.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
ak@suse.de, linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc5-mm1: oops when starting nscd on AMD64
Date: Mon, 8 Aug 2005 12:38:31 +0200 [thread overview]
Message-ID: <20050808103831.GA1210@localhost.localdomain> (raw)
In-Reply-To: <20050808012809.2a708b3e.akpm@osdl.org>
> > > I don't think it was supposed to do that.
> > >
> > > Quite possibly it's something to do with the new debugging code - could you
> > > please take a copy of the offending config, send it over and then try
> > > removing debug options, see if the crash goes away? CONFIG_DEBUG_PREEMPT
> > > would be the first to try..
> >
> > The (offending) .config is attached and here's what happens without CONFIG_DEBUG_PREEMPT
> > (the other debug options being unchanged):
>
> Yes, my emt64 machine keels over with your .config too. Maybe it's due to
> CONFIG_SMP=n, not sure.
>
> Bisection searching shows that the bug was introduced by
> slab-leak-detector-give-longer-traces.patch.
>
I was afraid it was when I first saw it but I couldn't reproduce (and
still can't).
> Call Trace:<ffffffff801a17bb>{sys_epoll_create+568} <ffffffff8018b1f7>{vfs_readdir+167}
> <ffffffff80231000>{add_preempt_count+93} <ffffffff8010e8fa>{system_call+126}
>
For some reason your compilers inline heavier than mine do, which makes
this:
kmem_cache_alloc
sys_epoll_create (__builtin_return_address(0))
system_call (__builtin_return_address(1))
(__builtin_return_address(2))
and off the stack we go...
I guess it was naive to even try to use this for more than the first
caller, sorry. Please throw that thing away and I'll do some backtracing
similar to CONFIG_PAGE_OWNER
prev parent reply other threads:[~2005-08-08 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 16:51 2.6.13-rc5-mm1: oops when starting nscd on AMD64 Rafael J. Wysocki
2005-08-07 17:23 ` Andrew Morton
2005-08-07 21:16 ` Rafael J. Wysocki
2005-08-08 8:28 ` Andrew Morton
2005-08-08 10:38 ` Alexander Nyberg [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=20050808103831.GA1210@localhost.localdomain \
--to=alexn@telia.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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