lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 12 Oct 2006 09:19:03 -0500
From:	Michael Harris <googlegroups@...arris.com>
To:	Nick Piggin <nickpiggin@...oo.com.au>
Cc:	Michael Harris <googlegroups@...arris.com>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.18: Kernel BUG at mm/rmap.c:522

> Michael Harris wrote:
> >Hi, I can readily reproduce this with 2.6.18 doing 4 simultanous kernel 
> >compiles on two disks to load test a P4 3.2 HT with 2GB. I have SMP and 
> >SMT scheduling enabled, and the 4GB memory option. Here is output with 
> >CONFIG_DEBUG_VM enabled followed by another crash before CONFIG_DEBUG_VM 
> >was enabled.
> 
> >Oct 11 04:53:35 hen kernel: swap_free: Unused swap offset entry 00004000
> >Oct 11 04:53:35 hen kernel: Eeek! page_mapcount(page) went negative! (-1)
> >Oct 11 04:53:35 hen kernel:   page->flags = c0080014
> >Oct 11 04:53:35 hen kernel:   page->count = 0
> >Oct 11 04:53:35 hen kernel:   page->mapping = 00000000
> 
> Hmm, this is a new one. The page is free and not reserved, wheras we are
> used to seeing them reserved here.
> 
> >Oct 11 04:54:31 hen kernel: Bad page state in process 'tripwire'
> >Oct 11 04:54:31 hen kernel: page:c1b5cd80 flags:0xc0000014 
> >mapping:00000000 mapcount:-1 count:0
> 
> >Another crash from a day earlier before enabling DEBUG_VM
> >Oct 10 05:19:43 hen kernel: VM: killing process cc1
> >Oct 10 05:19:43 hen kernel: swap_free: Unused swap offset entry 00002000
> >Oct 10 05:19:56 hen kernel: swap_free: Unused swap offset entry 00000400
> 
> These unused swap offset entry messages seem to indicate extensive memory
> corruption in your page tables. Probably bad RAM, or system overheating
> when you load it up :(
> 
> Can you run a good memory tester like memtest86+ overnight?


Hi, I think this is the case, a stick of ram gone bad. It had worked 
testing under 2.4 but coincidentally failed about the time I upgraded
to 2.6. memtest86 uncovered it at once. Sorry for the trouble and thanks
for the help.
Mike

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ