linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: linux-next crash during very early boot
Date: Wed, 13 Apr 2016 20:29:46 -0400	[thread overview]
Message-ID: <3689.1460593786@turing-police.cc.vt.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 897 bytes --]

I'm seeing my laptop crash/wedge up/something during very early
boot - before it can write anything to the console.  Nothing in pstore,
need to hold down the power button for 6 seconds and reboot.

git bisect points at:

commit 7a6bacb133752beacb76775797fd550417e9d3a2
Author: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Date:   Thu Apr 7 13:59:39 2016 +1000

    mm/slab: factor out kmem_cache_node initialization code

    It can be reused on other place, so factor out it.  Following patch will
    use it.


Not sure what the problem is - the logic *looks* ok at first read.  The
patch *does* remove a spin_lock_irq() - but I find it difficult to
believe that with it gone, my laptop is able to hit the race condition
the spinlock protects against *every single boot*.

The only other thing I see is that n->free_limit used to be assigned
every time, and now it's only assigned at initial creation.


[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]

             reply	other threads:[~2016-04-14  0:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14  0:29 Valdis Kletnieks [this message]
2016-04-14  1:35 ` Joonsoo Kim
2016-04-14 19:22   ` Valdis.Kletnieks
2016-04-15  1:25     ` Joonsoo Kim
2016-04-15 14:10   ` Valdis.Kletnieks
2016-04-20  8:13     ` Joonsoo Kim
2016-04-21  3:14     ` Valdis.Kletnieks

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=3689.1460593786@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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