From: "Mike Black" <mblack@csihq.com>
To: "Hugh Dickins" <hugh@veritas.com>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: page_alloc bug in 2.4.17-pre8
Date: Thu, 23 May 2002 09:37:48 -0400 [thread overview]
Message-ID: <036901c2025f$0746e2f0$f6de11cc@black> (raw)
In-Reply-To: <Pine.LNX.4.21.0205231301100.1049-100000@localhost.localdomain>
Oops -- got the wrong version (head was in the wrong kernel space).
This occurred on 2.4.19-pre8
----- Original Message -----
From: "Hugh Dickins" <hugh@veritas.com>
To: "Mike Black" <mblack@csihq.com>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>
Sent: Thursday, May 23, 2002 8:12 AM
Subject: Re: page_alloc bug in 2.4.17-pre8
> On Thu, 23 May 2002, Mike Black wrote:
> > This machine had been up for 2-1/2 days and had run this backup (afio) twice successfully.
> >
> > Here's line 108 of page_alloc.c:
> > if (PageLRU(page))
> > BUG();
> >
> > Hopefully this doesn't indicate a CPU problem? The power supply on this thing blew Saturday but has run OK until now.
> >
> > May 22 00:51:01 picard kernel: kernel BUG at page_alloc.c:108!
> > May 22 00:51:01 picard kernel: invalid operand: 0000
> > May 22 00:51:01 picard kernel: CPU: 1
> > May 22 00:51:01 picard kernel: EIP: 0010:[swap_duplicate+82/192] Not tainted
>
> There were quite a number of reports of those PageLRU BUGs on 2.4.17.
> No idea what fixed them, but 2.4.18 (and 2.4.19-pre) has seemed free
> of them (Ben LaHaise made a plausible change, but closer analysis
> suggested it couldn't really be the fix). Suggest you upgrade.
>
> Your oops report, by the way, must have been using the wrong System.map:
> page_alloc.c:108 is in __free_pages_ok(), swap_duplicate() is over in
> swapfile.c. But no matter, page_alloc.c:108 identifies it well enough.
>
> Hugh
>
next prev parent reply other threads:[~2002-05-23 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-23 11:47 page_alloc bug in 2.4.17-pre8 Mike Black
2002-05-23 12:12 ` Hugh Dickins
2002-05-23 13:37 ` Mike Black [this message]
2002-05-23 14:03 ` Hugh Dickins
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='036901c2025f$0746e2f0$f6de11cc@black' \
--to=mblack@csihq.com \
--cc=hugh@veritas.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