public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Irwin <bill.irwin@oracle.com>
To: "Alexander Y. Fomichev" <gluk@php4.ru>
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: Fri, 2 Mar 2007 13:41:11 -0800	[thread overview]
Message-ID: <20070302214111.GL10643@holomorphy.com> (raw)
In-Reply-To: <200703021651.16050.gluk@php4.ru>

On Fri, Mar 02, 2007 at 04:51:15PM +0300, Alexander Y. Fomichev wrote:
> 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.

If you have a known-working kernel version, git-bisect might help you
track down where it was introduced. Given the messages prior to the
hugetlbpage.c BUG_ON I'd say that this is something else besides the
specific code listed by line number, though I wouldn't rule out hugetlb
having tripped over itself before the actual BUG.


-- wli

  parent reply	other threads:[~2007-03-02 21:41 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
2007-03-02 21:41 ` Bill Irwin [this message]
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=20070302214111.GL10643@holomorphy.com \
    --to=bill.irwin@oracle.com \
    --cc=admin@list.net.ru \
    --cc=gluk@php4.ru \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox