linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Yury Norov <yury.norov@gmail.com>
To: Mel Gorman <mgorman@techsingularity.net>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	yury.norov@gmail.com,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Will Deacon <will.deacon@arm.com>,
	linux-kernel@vger.kernel.org, Michal Hocko <mhocko@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	David Rientjes <rientjes@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Zi Yan <zi.yan@cs.rutgers.edu>, Vlastimil Babka <vbabka@suse.cz>
Subject: 5.0-rc kernel hangs on early boot
Date: Wed, 13 Feb 2019 11:25:40 +0300	[thread overview]
Message-ID: <20190213082134.GA21834@yury-thinkpad> (raw)

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

Hi Mel, all,

My kernel on qemu/arm64 setup hangs at early boot since v5.0-rc1.
Backtrace is not too verbose:
(gdb) i threads
  Id   Target Id         Frame
* 1    Thread 1 (CPU#0 [running]) 0xffff000010a49b74 in __delay (cycles=4096)
    at arch/arm64/lib/delay.c:49
  2    Thread 2 (CPU#1 [halted ]) 0x0000000000000000 in ?? ()
  3    Thread 3 (CPU#2 [halted ]) 0x0000000000000000 in ?? ()
  4    Thread 4 (CPU#3 [halted ]) 0x0000000000000000 in ?? ()
(gdb) bt
#0  0xffff000010a49b74 in __delay (cycles=4096) at arch/arm64/lib/delay.c:49
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Reverting the patch
1c30844d2dfe272d58c ("mm: reclaim small amounts of memory when an external
fragmentation event occurs") together with following patch
73444bc4d8f92e46a20 ("mm, page_alloc: do not wake kswapd with zone lock held")
helps me to boot normally. 

Some system information is below, and config is attached.

Thanks,
Yury

$ qemu-system-aarch64 --version
QEMU emulator version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.9)
Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers

$ cat runlinux.sh
TAP=tap0
BRIDGE=br0
NETWORK="-device virtio-net-device,netdev=netdev0 -netdev tap,ifname=$TAP,script=no,id=netdev0"

sudo ip tuntap add mode tap dev $TAP
sudo ip link set dev $TAP promisc on
sudo ip link set dev $TAP up
sudo ip link set dev $TAP master $BRIDGE

qemu-system-aarch64 -machine virt -cpu cortex-a57 -nographic -smp 4 -m 1024 \
	-machine virt -cpu cortex-a57 -nographic -smp 4 -m 1024 \
	-machine virt -cpu cortex-a57 -nographic -smp 4  -m 1024 \
	-global virtio-blk-device.scsi=off -device virtio-scsi-device,id=scsi \
	-drive file=img/ubuntu-core-14.04.1-core-arm64.img,id=coreimg,cache=unsafe,if=none -device scsi-hd,drive=coreimg \
	-kernel /home/yury/work/linux/arch/arm64/boot/Image \
	--append "rcu_nocbs=2-3 irqaffinity=0 task_isolation_debug console=ttyAMA0 root=/dev/sda nohz_full=2-3 isolcpus=2-3 task_isolation=2-3" \
	-initrd initrd.img-3.13.0-62-generic \
	$NETWORK \
	-redir tcp:2222::22 \
	-s \
	$@

sudo ip link set dev $TAP nomaster
sudo ip link set dev $TAP down
sudo ip link set dev $TAP promisc off
sudo ip tuntap del mode tap dev $TAP

[-- Attachment #2: congig.tar.gz --]
[-- Type: application/gzip, Size: 35647 bytes --]

[-- Attachment #3: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2019-02-13  8:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13  8:25 Yury Norov [this message]
2019-02-13 11:14 ` 5.0-rc kernel hangs on early boot Mel Gorman
2019-02-13 11:51   ` Yury Norov
2019-02-13 13:19     ` Mel Gorman
2019-02-13 11:18 ` Will Deacon
2019-02-13 11:21   ` Mel Gorman
2019-02-13 11:25     ` Will Deacon
2019-02-13 11:29       ` Mel Gorman
2019-02-13 11:55   ` Yury Norov

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=20190213082134.GA21834@yury-thinkpad \
    --to=yury.norov@gmail.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@kernel.org \
    --cc=rientjes@google.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vbabka@suse.cz \
    --cc=will.deacon@arm.com \
    --cc=zi.yan@cs.rutgers.edu \
    /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;
as well as URLs for NNTP newsgroup(s).