From: Andrew Morton <akpm@zip.com.au>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: Rik van Riel <riel@conectiva.com.br>,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: BUG at rmap.c:212
Date: Wed, 31 Jul 2002 10:03:17 -0700 [thread overview]
Message-ID: <3D481855.35A64873@zip.com.au> (raw)
In-Reply-To: AE2FE25828@vcnet.vc.cvut.cz
Petr Vandrovec wrote:
>
> ...
> > > Probably because of your code did not do anything special when
> > > 'Not found. This should NEVER happen!' code path triggers.
> > Of course, ntpd is probably running into a different problem,
> > but the printk's enabled with DEBUG_RMAP should give us some
> > hints.
>
> No nvidia here. Boot, start X, quit X, run updatedb, reboot...
> cat /proc/`pidof ntpd`/maps says that it has mmaped only ntpd and
> few libraries from /lib. I hope that printed values will have
> some value for you. And btw, ntpd uses some mlock*() call, it has status
> 'SL' in process list. Do you know how to find what memory it has locked?
It's good that this it nice and reproducible, thanks.
Linus, can we please not have that BUG() in 2.5.30?
--- 2.5.29/mm/rmap.c~no-bug Wed Jul 31 09:58:47 2002
+++ 2.5.29-akpm/mm/rmap.c Wed Jul 31 09:58:53 2002
@@ -205,8 +205,6 @@ void page_remove_rmap(struct page * page
}
printk("\n");
printk(KERN_ERR "page_remove_rmap: driver cleared PG_reserved ?\n");
-#else
- BUG();
#endif
out:
.
next prev parent reply other threads:[~2002-07-31 16:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 14:00 BUG at rmap.c:212 Petr Vandrovec
2002-07-31 17:03 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-31 13:03 Petr Vandrovec
2002-07-31 13:11 ` Rik van Riel
2002-07-31 10:06 Petr Vandrovec
2002-07-31 12:49 ` Rik van Riel
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=3D481855.35A64873@zip.com.au \
--to=akpm@zip.com.au \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.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