Summary: | kernel BUG at mm/rrge, and...¿randomly?map.c:483!--> When I try to eme | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | José María (Spain) <man_jose> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED INVALID | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
José María (Spain)
2005-01-16 13:32:40 UTC
I post this error to the developers of the kernel and I have recived the next email:
>Your system is not broken, this is a known bug.
>Can you check whether 2.6.11-rc1-mm1-jedi1 fixes it?
> 2.6.11-rc1 : ftp://ftp.kernel.org:/pub/linux/kernel/v2.6/testing/
> -mm1 patch : ftp://ftp.kernel.org:/pub/linux/kernel/people/akpm/patches/2.6/
> -jedi1 : ftp://ftp.c9x.org/linux-kernel/
Jos
I post this error to the developers of the kernel and I have recived the next email:
>Your system is not broken, this is a known bug.
>Can you check whether 2.6.11-rc1-mm1-jedi1 fixes it?
> 2.6.11-rc1 : ftp://ftp.kernel.org:/pub/linux/kernel/v2.6/testing/
> -mm1 patch : ftp://ftp.kernel.org:/pub/linux/kernel/people/akpm/patches/2.6/
> -jedi1 : ftp://ftp.c9x.org/linux-kernel/
José María
Well..could you please try that? Tryed and.... crashed :o( Here you have another post from people who is fighting against this bug. He talks about another patch. I won't probe this patch against 2.6.9. I have asked him to make the patch for 2.9.11 so I can make probes with the two guys that are in contact with me trying to eliminate this bug. I'm not a programmer so what comes here is really chinese for me.
> We still do not know; we'd very much like to know.
>
> It would not be the fault of any userspace program
> (unless they corrupt via /dev/mem or something like that).
>
> It may be a core kernel problem, but I've searched repeatedly and
> failed. It may be a driver problem e.g. GregKH's incident suggested
> a problem in DRM, and Andrea has pointed to a worrying ioctl there
> (looks like it could ClearPageReserved too early): I've been halfway
> through following that up for a few weeks now. Are you using DRM?
> (but the hallmarks in your case are different.)
>
> It can be caused by somewhere freeing a page it no longer holds;
> but in that case we'd usually expect to see the Bad page state
> error coming from free_pages_check rather than prep_new_page,
> and to be followed by the rmap.c BUG rather than following it.
>
> It could easily be caused by bad memory bitflipping in a page table
> (but in general, we'd expect to be hearing of swap_free errors,
> or random corruption, if that were generally the case - I think).
> Please give memtest86 a good run to rule out that possibility.
>
> If memtest86 is satifisfied, would you mind running with the patch
> below (against 2.6.9, suitable for i386 or x86_64, but not suitable
> for the various architectures which use PG_arch_1)? To give us more
> debug info - it's unlikely to solve the mystery on it's own, but I
> hope it might help us to look in the right direction. And send me
> any "Bad rmap" and "Bad page state" log entries you find (but
> perhaps this was a one-off, and nothing more will appear).
Any progress on this? Is your discussion on a public mailing list? Please reopen when you reply to comment #5 Testing 2.6.11-rc3 might be an idea. Sorry me. I think I had posted here to close the bug :(. Finally someone told me to check the RAM and eureka!!!. My memory was buggy. Once I take out the SIMM I had no more problems with "2.6.11-rc1-mm1-jedi1". Later, I decide to prove the 2.6.10 from gentoo (gentoo-dev-sources) and everything works fine. I talk with kernel developers and they told me that they don't find no error in "rmap". They think that many of this bugs reported are due to buggy SIMMs. Jos Sorry me. I think I had posted here to close the bug :(. Finally someone told me to check the RAM and eureka!!!. My memory was buggy. Once I take out the SIMM I had no more problems with "2.6.11-rc1-mm1-jedi1". Later, I decide to prove the 2.6.10 from gentoo (gentoo-dev-sources) and everything works fine. I talk with kernel developers and they told me that they don't find no error in "rmap". They think that many of this bugs reported are due to buggy SIMMs. José María I think you should recommend to anyone with similar errors like me to make a HARD test (all the night?) to the memory with "memtest86": http://www.memtest86.com/memtest86-3.2.iso.zip (This is a bootable CDROM). I was I think you should recommend to anyone with similar errors like me to make a HARD test (all the night?) to the memory with "memtest86": http://www.memtest86.com/memtest86-3.2.iso.zip (This is a bootable CDROM). I was ¿lucky? because I found errors in 15min. See you José María Ok, thanks for letting us know. Bad memory is often a cause of these things. |