From: "Alexander Y. Fomichev" <gluk@php4.ru>
To: "Nish Aravamudan" <nish.aravamudan@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
admin@list.net.ru
Subject: Re: kernel BUG at arch/x86_64/mm/../../i386/mm/hugetlbpage.c:140!
Date: Tue, 6 Mar 2007 15:16:53 +0300 [thread overview]
Message-ID: <200703061516.53928.gluk@php4.ru> (raw)
In-Reply-To: <29495f1d0703021338k41bad9d3teaf93c8abcbfc152@mail.gmail.com>
On Saturday 03 March 2007, Nish Aravamudan wrote:
> On 3/2/07, Alexander Y. Fomichev <gluk@php4.ru> wrote:
> > G'day
> >
> > I'm hit a bug on 2.6.21-rc1 at startup of mysql with 'large-pages' flag
> > set. (at this point mysql trying to allocate pages from hugetlb pool by
> > sysv shm syscalls). Seems like it could be triggered by previous badness
> > and probably hugetlb itself is not related. Anyway i couldn't reproduce
> > it by now with 2.6.21-rc2 git commit
> > 562aa1d4c6a874373f9a48ac184f662fbbb06a04. Very likely it has been fixed
> > somwhere between 2.6.21-rc1 and -rc2, but i couldn't find something
> > related by git log so any comments are welcome.
>
> Adam Litke posted a bug fix for hugetlb shm:
> http://lkml.org/lkml/2007/3/1/381.
>
> Does that help fix your problem too?
>
> Thanks,
> Nish
Yep, it is, though Adam address this patch powerpc and ia64 issue but
x86_64 (and probably i386) affected too.
--
Best regards.
Alexander Y. Fomichev <gluk@php4.ru>
Public PGP key: http://sysadminday.org.ru/gluk.asc
next prev parent reply other threads:[~2007-03-06 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-02 13:51 kernel BUG at arch/x86_64/mm/../../i386/mm/hugetlbpage.c:140! Alexander Y. Fomichev
2007-03-02 21:38 ` Nish Aravamudan
2007-03-06 12:16 ` Alexander Y. Fomichev [this message]
2007-03-02 21:41 ` Bill Irwin
2007-03-06 12:45 ` Alexander Y. Fomichev
2007-03-06 20:19 ` Bill Irwin
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=200703061516.53928.gluk@php4.ru \
--to=gluk@php4.ru \
--cc=admin@list.net.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=nish.aravamudan@gmail.com \
/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.