more info on kernel BUG at page_alloc.c:225

more info on kernel BUG at page_alloc.c:225

[ming lei]

I should have said my version of linux2.4.19 is
ppc440GP port, so the line number should be line 220
in original linux 2.4.19 from kernel.org website. Be
clear, I printed the lines here:


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

more info on kernel BUG at page_alloc.c:225

[ming lei]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 2034 bytes --]


I should have said my version of linux2.4.19 is
ppc440GP port, so the line number is line 220 in
original linux 2.4.19 from kernel.org website. Be
clear, I printed the lines which panic occured:

219->      if (PageLRU(page))
220->          BUG();


-----------------------------------------------
I searched the web, following is the patch I am
interested. Can it solve the above problem?

On 02:39, venerdì 18 ottobre 2002, Gadad, Vijay wrote:
> I'm seeing an intermittent oops on a heavily loaded
SMP system (Compaq
> DL360 G2).  I've read the messages suggesting this
is related to the nvidia
> driver, but I don't have that loaded.
>
> This is the vanilla 2.4.19 kernel, plus Intel's
e1000.o driver and the ipvs
> patch.
>
> Here's the ksymoops output:
>
> kernel BUG at page_alloc.c:220!
> invalid operand: 0000
> CPU:    1
> EIP:    0010:[rmqueue+509/592]    Not tainted

this may be a patch:

[albert@yoda albert]$ diff -ruN page_alloc.c
new_page_alloc.c
--- page_alloc.c
+++ new_page_alloc.c
@@ -167,7 +167,7 @@
 #define MARK_USED(index, order, area) \
        __change_bit((index) >> (1+(order)),
(area)->map)

-static inline struct page * expand (zone_t *zone,
struct page *page,
+static inline struct page * expand(zone_t *zone,
struct page *page,
         unsigned long index, int low, int high,
free_area_t * area)
 {
        unsigned long size = 1 << high;
@@ -215,7 +215,6 @@
                        zone->free_pages -= 1UL <<
order;

                        page = expand(zone, page,
index, order, curr_order,
area);
-
spin_unlock_irqrestore(&zone->lock, flags);

                        set_page_count(page, 1);
                        if (BAD_RANGE(zone,page))
@@ -224,6 +223,7 @@
                                BUG();
                        if (PageActive(page))
                                BUG();
+
spin_unlock_irqrestore(&zone->lock, flags);
                        return page;
                }
                curr_order++;


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: more info on kernel BUG at page_alloc.c:225

[Eugene Surovegin]

At 05:15 PM 8/22/2003, ming lei wrote:
>I should have said my version of linux2.4.19 is
>ppc440GP port, so the line number is line 220 in
>original linux 2.4.19 from kernel.org website. Be
>clear

Hmm, it's still not clear what version you are using.
kernel.org 2.4.19 doesn't have 440GP support.

Are you using devel_2_4 or linuxppc-2.4 BK trees or MVL ?

Another question, do you run your test on IBM reference platform (Ebony) or
on your custom hw ?

Thanks,
Eugene


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: more info on kernel BUG at page_alloc.c:225

[Eugene Surovegin]

At 06:30 PM 8/25/2003, Ming Lei wrote:
> > At 05:15 PM 8/22/2003, ming lei wrote:
> > >I should have said my version of linux2.4.19 is
> > >ppc440GP port, so the line number is line 220 in
> > >original linux 2.4.19 from kernel.org website. Be
> > >clear
> >
> > Hmm, it's still not clear what version you are using.
> > kernel.org 2.4.19 doesn't have 440GP support.
> > Are you using devel_2_4 or linuxppc-2.4 BK trees or MVL ?
>
>it's linuxppc-2.4.19 bk tree.

Hmm, URL ?

> > Another question, do you run your test on IBM reference
> > platform (Ebony) or
> > on your custom hw ?
>
>custom board for both 440 and 405.

Try your test on Ebony.
440GP uses DDR RAM which is very tricky to implement/layout correctly. It
looks like you have hardware problems.

Eugene.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/