From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <45782B32.6040401@cern.ch> Date: Thu, 07 Dec 2006 15:54:42 +0100 From: Ramiro Voicu MIME-Version: 1.0 Subject: Re: [Bugme-new] [Bug 7645] New: Kernel BUG at mm/memory.c:1124 References: <200612070355.kB73tGf4021820@fire-2.osdl.org> <20061206201246.be7fb860.akpm@osdl.org> <4577A36B.6090803@cern.ch> <20061206230338.b0bf2b9e.akpm@osdl.org> In-Reply-To: <20061206230338.b0bf2b9e.akpm@osdl.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Andrew Morton Cc: linux-mm@kvack.org, bugme-daemon@bugzilla.kernel.org List-ID: It depends ... It can take days or minutes until it happens. The program is a simple FTP-like using multiple TCP Streams, implemented with Java NIO. What I have noticed is that if a do a lot of connect/disconnect from the client the kernel on the server machine gets stuck. It never happens with the client, though. I will try if I can, somehow, to isolate the problem ... although I does not seem that there is a pattern for this Andrew Morton wrote: > On Thu, 07 Dec 2006 06:15:23 +0100 > Ramiro Voicu wrote: > >> Here is the stack trace after I've applied the patch >> >> >> Dec 7 06:12:11 xxxx kernel: [ 319.720340] pte_val: 629025 > > hm. A valid, read-only, accessed user page with a sane-looking pfn. > And this is repeatable, on two different machines. > > I don't know what to do, sorry. A bisection-search would have a good > chance of finding the bug, but that would be pretty painful. It looks like > you were able to hit the bug after five minutes uptime, which helps. Is it > always that easy to hit? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org