From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965173AbVJUV3U (ORCPT ); Fri, 21 Oct 2005 17:29:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965176AbVJUV3U (ORCPT ); Fri, 21 Oct 2005 17:29:20 -0400 Received: from CPE-61-9-212-151.qld.bigpond.net.au ([61.9.212.151]:10303 "EHLO bastard.youngs.au.com") by vger.kernel.org with ESMTP id S965173AbVJUV3T (ORCPT ); Fri, 21 Oct 2005 17:29:19 -0400 From: Steve Youngs To: Linux Kernel List Cc: Hugh Dickins Subject: Re: 2.6.13.4 After increasing RAM, I'm getting Bad page state at prep_new_page Keywords: page,new,memory,state,run,ram,hugh Organization: Linux Users - Fanatics Dept. References: X-Face: #/1'_-|5_1$xjR,mVKhpfMJcRh8"k}_a{EkIO:Ox<]@zl/Yr|H,qH#3jJi6Aw(Mg@"!+Z"C N_S3!3jzW^FnPeumv4l#,E}J.+e%0q(U>#b-#`~>l^A!_j5AEgpU)>t+VYZ$:El7hLa1:%%L=3%B>n K{^jU_{& Mail-Followup-To: Linux Kernel List , steve@youngs.au.com X-X-Day: Only 2430946 days till X-Day. Got Slack? X-URL: X-Request-PGP: X-OpenPGP-Fingerprint: 1659 2093 19D5 C06E D320 3A20 1D27 DB4B A94B 3003 X-Discordian-Date: Setting Orange, the 3rd day of The Aftermath, 3171. X-Attribution: SY Date: Sat, 22 Oct 2005 07:29:11 +1000 In-Reply-To: (Hugh Dickins's message of "Wed, 19 Oct 2005 17:59:33 +0100 (BST)") Message-ID: User-Agent: Gnus/5.110004 (No Gnus v0.4) SXEmacs/22.1.3 (BMW, linux) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org --=-=-= Content-Transfer-Encoding: quoted-printable * Hugh Dickins writes: > On Thu, 20 Oct 2005, Steve Youngs wrote: >>=20 >> A few days ago I increased my RAM from 0.5Gb to 3Gb and since then >> I've been getting `Bad page state at prep_new_page' errors at odd >> times. Here is a typical backtrace from my logs: >>=20 >> Bad page state at prep_new_page (in process 'X', page c1f7bde0) >> flags:0x80000004 mapping:00000000 mapcount:-262144 count:0 > The bad memory in question (the struct page at 0xc1f7bde0) is quite > low down, just below 32MB. Would I be right to guess that that you > inserted the new cards in such a way that the low memory is new RAM? No. All the memory is new RAM. I originally had 2x256MB, and I replaced those with 3x1GB. Sorry if the Subject header was a bit misleading.=20 > I suggest you try taking out that lowest card, and see what happens > then. Sometimes the kernel these days seems to find memory problems > that memtest86 does not (how long did you run it? overnight?). When I had posted the message I had only let it run through all tests once. I have since let it run for about 18 hours, where it came up with a single error (as reported in my reply to Ken). > You could try sending me all your "Bad page state" messages, > to check for correlations. OK, I'll send those to you off-list. Thanks very much, Hugh. =2D-=20 |---------------------| | Te audire no possum. | | Musa sapientum fixa est in aure. | |-------------------------------------| --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Eicq - The XEmacs ICQ Client iEYEABECAAYFAkNZXacACgkQHSfbS6lLMAM/MwCgzu3Ox0kdAZ067vjOTIh1MfkU mZ0An1612u5MEwoXXaBOh4QadTJfbbvp =nMQi -----END PGP SIGNATURE----- --=-=-=--