From: Greg Ungerer <gerg@snapgear.com>
To: uClinux development list <uclinux-dev@uclinux.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [uClinux-dev] Coldfire 5271 hitting BUG_ON(page_count(buddy) != 0);
Date: Fri, 26 Jun 2009 13:21:25 +1000 [thread overview]
Message-ID: <4A443EB5.40300@snapgear.com> (raw)
In-Reply-To: <20090625154343.GA10189@csclub.uwaterloo.ca>
Hi Lennart,
Lennart Sorensen wrote:
> I am hitting a memory management bug and I would love some hints as to
> how to track down the bug and fix it.
>
> The bug hit is line 423 of page_alloc.c which is:
>
> BUG_ON(page_count(buddy) != 0);
>
> The function it is part of is:
>
> static inline int page_is_buddy(struct page *page, struct page *buddy,
> int order)
> {
> if (!pfn_valid_within(page_to_pfn(buddy)))
> return 0;
>
> if (page_zone_id(page) != page_zone_id(buddy))
> return 0;
>
> if (PageBuddy(buddy) && page_order(buddy) == order) {
> BUG_ON(page_count(buddy) != 0);
> return 1;
> }
> return 0;
> }
>
> I am seeing this both with 2.6.29.1 and 2.6.30 so far. I unfortunately
> haven't poked much at the memory management code, so I am not even sure
> what this is supposed to be doing. The cpu us a coldfire 5271.
>
> I also see crashes causing the kernel to dump lots of hex values.
> Building the kernel with debug enabled unfortunately seems to move things
> around enough to make it just lock up instead without any output.
What are you doing at the time you get this?
Or is it at bootup?
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
825 Stanley St, FAX: +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia WEB: http://www.SnapGear.com
next prev parent reply other threads:[~2009-06-26 3:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-25 15:43 Coldfire 5271 hitting BUG_ON(page_count(buddy) != 0); Lennart Sorensen
2009-06-26 3:21 ` Greg Ungerer [this message]
2009-06-26 15:23 ` [uClinux-dev] " Lennart Sorensen
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=4A443EB5.40300@snapgear.com \
--to=gerg@snapgear.com \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-dev@uclinux.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