From: Ramiro Voicu <Ramiro.Voicu@cern.ch>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-mm@kvack.org, bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 7645] New: Kernel BUG at mm/memory.c:1124
Date: Thu, 07 Dec 2006 15:54:42 +0100 [thread overview]
Message-ID: <45782B32.6040401@cern.ch> (raw)
In-Reply-To: <20061206230338.b0bf2b9e.akpm@osdl.org>
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 <Ramiro.Voicu@cern.ch> 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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-12-07 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200612070355.kB73tGf4021820@fire-2.osdl.org>
2006-12-07 4:12 ` [Bugme-new] [Bug 7645] New: Kernel BUG at mm/memory.c:1124 Andrew Morton
2006-12-07 5:15 ` Ramiro Voicu
2006-12-07 7:03 ` Andrew Morton
2006-12-07 14:54 ` Ramiro Voicu [this message]
2006-12-07 21:22 ` Hugh Dickins
2006-12-08 23:52 ` Andrew Morton
2006-12-09 4:34 ` Hugh Dickins
2006-12-09 17:24 ` Ramiro Voicu
2006-12-09 18:40 ` Hugh Dickins
2006-12-11 18:56 ` Ramiro Voicu
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=45782B32.6040401@cern.ch \
--to=ramiro.voicu@cern.ch \
--cc=akpm@osdl.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.