From: Emiliano Gabrielli <Emiliano.Gabrielli@roma2.infn.it>
To: "Gadad, Vijay" <vgadad@persistcorp.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel BUG at page_alloc.c:220 - oops in 2.4.19
Date: Fri, 18 Oct 2002 12:18:33 +0200 [thread overview]
Message-ID: <200210181218.33516.gabrielli@roma2.infn.it> (raw)
In-Reply-To: <AAE2EF2556DA3045830D8DFFD01C4AD103C035@athena.persistcorp.local>
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++;
__
Emiliano 'AlberT' Gabrielli
prev parent reply other threads:[~2002-10-18 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 0:39 Gadad, Vijay
2002-10-18 10:18 ` Emiliano Gabrielli [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=200210181218.33516.gabrielli@roma2.infn.it \
--to=emiliano.gabrielli@roma2.infn.it \
--cc=linux-kernel@vger.kernel.org \
--cc=vgadad@persistcorp.com \
/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
all inboxes | Powered by JetHome®