From: David Newall <davidn@davidnewall.com>
To: Gene Heskett <gene.heskett@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: I just got got another Oops
Date: Fri, 13 Mar 2009 15:25:01 +1030 [thread overview]
Message-ID: <49B9E725.3060103@davidnewall.com> (raw)
In-Reply-To: <200903121928.00746.gene.heskett@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
Gene,
I think it's a null page pointer passed to prep_new_page. It's
difficult to be certain, because it's compiled with -O2, but that's what
it looks like.
Let's test that hypothesis. Let's also compile page_alloc.c with
debugging. Do that by executing the commands in the attached file, and
then doing a make install (or whatever you do.)
But first, let's also sidestep the optimiser by making prep_new_page
public. Do that by changing:
static int prep_new_page(struct page *page, int order, gfp_t gfp_flags)**
in mm/page_alloc.c, near line 637, to:
int my_prep_new_page(struct page *page, int order, gfp_t gfp_flags)**
and by changing:
if (prep_new_page(page, order, gfp_flags))
near line 1137, to:
if (my_prep_new_page(page, order, gfp_flags))
This will prevent the optimiser from inlining that function, and we
would expect to see the error change from
"get_page_from_freelist+0x24b/0x4c0" to "my_prep_new_page+0x0yy/0x0zz".
David
[-- Attachment #2: compile_page_alloc --]
[-- Type: text/plain, Size: 993 bytes --]
gcc -g -Wp,-MD,mm/.page_alloc.o.d -nostdinc -isystem /usr/lib/gcc/i486-linux-gnu/4.1.3/include -Iinclude -I/home/davidn/NAS/linux.trees.git/arch/x86/include -include include/linux/autoconf.h -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -m32 -msoft-float -mregparm=3 -freg-struct-return -mpreferred-stack-boundary=2 -march=k8 -mtune=generic -Wa,-mtune=generic32 -ffreestanding -pipe -Wno-sign-compare -fno-asynchronous-unwind-tables -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -fno-stack-protector -fno-omit-frame-pointer -fno-optimize-sibling-calls -Wdeclaration-after-statement -Wno-pointer-sign -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(page_alloc)" -D"KBUILD_MODNAME=KBUILD_STR(page_alloc)" -c -o mm/page_alloc.o mm/page_alloc.c
scripts/basic/fixdep mm/.page_alloc.o.d mm/page_alloc.o 'gcc etc' > mm/.page_alloc.o.tmp
rm -f mm/.page_alloc.o.d
mv -f mm/.page_alloc.o.tmp mm/.page_alloc.o.cmd
next prev parent reply other threads:[~2009-03-13 4:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 5:33 I just got got another Oops Gene Heskett
2009-03-12 6:27 ` KAMEZAWA Hiroyuki
2009-03-12 8:36 ` David Newall
2009-03-12 17:28 ` Gene Heskett
2009-03-12 17:48 ` Gene Heskett
2009-03-12 19:37 ` David Newall
2009-03-12 23:28 ` Gene Heskett
2009-03-13 4:55 ` David Newall [this message]
2009-03-12 18:31 ` Gene Heskett
2009-03-16 2:55 ` KAMEZAWA Hiroyuki
2009-03-16 3:22 ` KAMEZAWA Hiroyuki
2009-03-16 8:03 ` BUG?: PAGE_FLAGS_CHECK_AT_PREP seems to be cleared too early (Was " KAMEZAWA Hiroyuki
2009-03-16 21:44 ` Hugh Dickins
2009-03-16 23:44 ` KAMEZAWA Hiroyuki
2009-03-20 15:23 ` Mel Gorman
2009-03-22 14:55 ` Hugh Dickins
2009-03-23 11:27 ` Mel Gorman
-- strict thread matches above, loose matches on Subject: below --
2009-03-12 5:33 Gene Heskett
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=49B9E725.3060103@davidnewall.com \
--to=davidn@davidnewall.com \
--cc=gene.heskett@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox