From: "J. R. Okajima" <hooanon05@yahoo.co.jp>
To: "Emmanuel V." <antro5@free.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bug in 2.6.32-5-amd64 : aufs/memory management related?
Date: Sat, 26 Feb 2011 01:36:22 +0900 [thread overview]
Message-ID: <9665.1298651782@jrobl> (raw)
In-Reply-To: <4D67CAE4.2060909@free.fr>
"Emmanuel V.":
> $ cat /proc/version
> Linux version 2.6.32-5-amd64 (Debian 2.6.32-30) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 03:40:32 UTC 2011
>
> $ dmesg
>
> [...]
> [10688.154693] ------------[ cut here ]------------
> [10688.154741] kernel BUG at /build/buildd-linux-2.6_2.6.32-30-amd64-d4MbNM/linux-2.6-2.6.32/debian/build/source_amd64_none/mm/mmap.c:873!
:::
According to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607879,
Debian people already fixed this problem (although I am afraid they are
still using an obsoleted version of aufs).
And this is debian specific problem and aufs is not in mainline. I don't
think this ML is appropriate for such problem.
J. R. Okajima
prev parent reply other threads:[~2011-02-25 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 15:29 bug in 2.6.32-5-amd64 : aufs/memory management related? Emmanuel V.
2011-02-25 16:36 ` J. R. Okajima [this message]
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=9665.1298651782@jrobl \
--to=hooanon05@yahoo.co.jp \
--cc=antro5@free.fr \
--cc=linux-kernel@vger.kernel.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.