From: Andrea Arcangeli <aarcange@redhat.com>
To: ethan zhao <ethan.kernel@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Huge memory takes too long time to initialize on 4TB memory ?
Date: Thu, 24 May 2012 01:24:42 +0200 [thread overview]
Message-ID: <20120523232441.GC4071@redhat.com> (raw)
In-Reply-To: <CABawtvN4Cwm3iFBB9hkDREHgtVYTni93TQ4SqezyLMtVAqhqVA@mail.gmail.com>
Hi,
On Wed, May 23, 2012 at 10:36:01AM +0800, ethan zhao wrote:
> Hi, aarcange
>
> When I boot kernel 2.6.39-100.6.1.el6uek.x86_64(actually 3.0.26)on a 4TB
> machine, got following call trace,
> That shows huge memory take too long time to initialize ? any help ?, I
> compared the huge_memory.c code between 3.0.26 and the current 3.2.x, no
> change.
>
> Pid: 1, comm: swapper Not tainted 2.6.39-100.6.1.el6uek.x86_64 #1 Oracle
> Corporation Sun Fire X4800 M2 /
> RIP: 0010:[<ffffffff814fb2d9>] [<ffffffff814fb2d9>]
> _raw_spin_unlock_irqrestore+**0x19/0x30
Could you reproduce it with an upstream (or with RHEL) kernel? It may
be reproducible upstream, but it looks like some kind of memory
corruption or zone dangling pointer so it's hard to tell if it's
upstraem too or not, by just reading the oops.
Thanks,
Andrea
parent reply other threads:[~2012-05-23 23:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CABawtvN4Cwm3iFBB9hkDREHgtVYTni93TQ4SqezyLMtVAqhqVA@mail.gmail.com>]
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=20120523232441.GC4071@redhat.com \
--to=aarcange@redhat.com \
--cc=ethan.kernel@gmail.com \
--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