From: Arjan van de Ven <arjan@infradead.org>
To: zine el abidine Hamid <zine46@yahoo.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel BUG at page_alloc.c:117!
Date: Mon, 05 Dec 2005 15:04:03 +0100 [thread overview]
Message-ID: <1133791443.9356.23.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20051205135723.83840.qmail@web30602.mail.mud.yahoo.com>
On Mon, 2005-12-05 at 14:57 +0100, zine el abidine Hamid wrote:
> Hello Dirk,
>
> First, thank you for responding so fast.
> I have to use the kernel 2.4.18 (or at best the
> 2.4.22).
why?
> I want first understand what's appened;
something in the kernel did something wrong, which caused the VM to
notice the corruption
> Is-it a
> kernel
> problem or is-it a bug off our application which is
> written in C++.
it's probably a driver bug (at least that's most common)
> It seems like there a bug with the VM; is it true?
no it's something that went wrong and first got noticed in the VM,
that's different from being a bug in the VM.
which exactly modules were in use? Are there any modules that didn't
come with that kernel?
next prev parent reply other threads:[~2005-12-05 14:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051205133755.74679.qmail@web30613.mail.mud.yahoo.com>
2005-12-05 13:57 ` zine el abidine Hamid
2005-12-05 14:04 ` Arjan van de Ven [this message]
2005-12-05 14:25 ` zine el abidine Hamid
2005-12-05 14:28 ` Arjan van de Ven
2005-12-05 15:05 ` zine el abidine Hamid
2005-12-05 16:48 ` zine el abidine Hamid
2005-12-06 5:06 ` Rob Landley
2005-12-06 5:38 ` Keith Mannthey
2005-12-06 10:25 ` zine el abidine Hamid
2005-12-08 14:13 ` Nix
[not found] <1133870375.5334.9.camel@home.sweethome>
2005-12-07 9:40 ` zine el abidine Hamid
2005-12-07 10:10 ` Dirk Henning Gerdes
2005-12-05 13:16 zine el abidine Hamid
2005-12-05 13:25 ` Dirk Henning Gerdes
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=1133791443.9356.23.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zine46@yahoo.fr \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®