linux-kernel - Re: Huge memory takes too long time to initialize on 4TB memory ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20120523232441.GC4071@redhat.com>
Date:	Thu, 24 May 2012 01:24:42 +0200
From:	Andrea Arcangeli <aarcange@...hat.com>
To:	ethan zhao <ethan.kernel@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Huge memory takes too long time to initialize on 4TB memory ?

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/