From: Mike Galbraith <efault@gmx.de>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.18-rc1: slab BUG_ON(!PageSlab(page)) upon umount after failed suspend
Date: Mon, 10 Jul 2006 12:51:26 +0200 [thread overview]
Message-ID: <1152528686.9122.5.camel@Homer.TheSimpsons.net> (raw)
In-Reply-To: <84144f020607100333s57159d38ha1101c65e8c099b1@mail.gmail.com>
On Mon, 2006-07-10 at 13:33 +0300, Pekka Enberg wrote:
> On 7/10/06, Mike Galbraith <efault@gmx.de> wrote:
> > Hm. I've never _noticed_ gcc putting anything out there before. This
> > is gcc version 4.1.2 20060531 (prerelease) (SUSE Linux).
>
> [snip]
>
> Curious... GCC cuts line and file information after ud2a. Looking at
> your stack trace, I am wondering who calls free_block() as we don't
> see cache_flusharray() in the trace. Do you have CONFIG_NUMA enabled?
(gdb) list *__cache_free+0x86
0xb1068e39 is in __cache_free (slab.c:3152).
3147 shared_array->avail += batchcount;
3148 goto free_done;
3149 }
3150 }
3151
3152 free_block(cachep, ac->entry, batchcount, node);
3153 free_done:
3154 #if STATS
3155 {
3156 int i = 0;
(gdb)
It got inlined.
-Mike
next prev parent reply other threads:[~2006-07-10 10:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6wDCq-5xj-25@gated-at.bofh.it>
[not found] ` <6wM2X-1lt-7@gated-at.bofh.it>
[not found] ` <6wOxP-4QN-5@gated-at.bofh.it>
2006-07-09 22:57 ` 2.6.18-rc1-mm1: /sys/class/net/ethN becoming symlink befuddled /sbin/ifup Tilman Schmidt
2006-07-09 23:17 ` Andrew Morton
2006-07-10 6:31 ` 2.6.18-rc1: slab BUG_ON(!PageSlab(page)) upon umount after failed suspend Mike Galbraith
2006-07-10 8:42 ` Pekka Enberg
2006-07-10 10:25 ` Mike Galbraith
2006-07-10 10:33 ` Pekka Enberg
2006-07-10 10:42 ` Mike Galbraith
2006-07-10 10:51 ` Mike Galbraith [this message]
2006-07-10 11:40 ` Pekka Enberg
2006-07-12 8:55 ` Mike Galbraith
2006-07-10 18:28 ` 2.6.18-rc1-mm1: /sys/class/net/ethN becoming symlink befuddled /sbin/ifup Tilman Schmidt
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=1152528686.9122.5.camel@Homer.TheSimpsons.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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
Powered by JetHome