From: Jay Roplekar <jay_roplekar@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel bug: mm/rmap.c:483 and related {now 2.6.8}
Date: Mon, 31 Jan 2005 20:19:54 -0600 [thread overview]
Message-ID: <200501312019.54250.jay_roplekar@hotmail.com> (raw)
>Thanks for giving that a thorough run, memory seems exonerated... yet I
>don't trust this machine at all: have you tried manufacturer diagnostics?
Ouch, that hurts. This is a machine I built myself over three years ago. Ran
very stably with 2.4.*. may be it is the age of the machine. The recent
hardware changes are additions of a dvd writer, a hdd and a pci wireless
card. Which seem to work ok until recently. What other diagnostics would
make sense?
>> Jan 29 08:25:02 Bad page state at prep_new_page ('X', page c1251ae0)
>> Jan 29 08:25:02 flags:0x20000004 mapping:00006a00 mapcount:0 count:0
>Again, something I've not seen reported before: mapping:00006a00, when
>mapping should be NULL (or at least a pointer into kernel memory). You
>say message reappeared twice with identical addresses: was that mapping
>the same each time?
Hmm, it is different one time, as shown below.. I guess should have looked
carefully. Although it means nothing to me.. FWIW, please note that in all
these cases ndiswrapper (windows driver loader) is being used. Thanks, Jay
Jan 29 08:27:03 localhost kernel: Bad page state at prep_new_page (in process
'X', page c1253a60)
Jan 29 08:27:03 localhost kernel: flags:0x20000004 mapping:00006a00 mapcount:0
count:0
Jan 29 08:27:08 localhost kernel: Bad page state at prep_new_page (in process
'X', page c12965e0)
Jan 29 08:27:08 localhost kernel: flags:0x20000004 mapping:00006600 mapcount:0
count:0
next reply other threads:[~2005-02-01 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 2:19 Jay Roplekar [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-31 16:03 Jayant Roplekar
2005-01-31 20:49 ` 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=200501312019.54250.jay_roplekar@hotmail.com \
--to=jay_roplekar@hotmail.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
Powered by JetHome