From: Mel Gorman <mgorman@techsingularity.net>
To: Yury Norov <yury.norov@gmail.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>,
Catalin Marinas <catalin.marinas@arm.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: Re: 5.0-rc kernel hangs on early boot
Date: Wed, 13 Feb 2019 13:19:48 +0000 [thread overview]
Message-ID: <20190213131948.GR9565@techsingularity.net> (raw)
In-Reply-To: <20190213115115.GA8928@yury-thinkpad>
On Wed, Feb 13, 2019 at 02:51:15PM +0300, Yury Norov wrote:
> On Wed, Feb 13, 2019 at 11:14:09AM +0000, Mel Gorman wrote:
> > On Wed, Feb 13, 2019 at 11:25:40AM +0300, Yury Norov wrote:
> > > 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.
> > >
> >
> > Well, that's a bad start to any day. Thanks for tracking it down. Does
> > the following patch help? I can't test it properly as I didn't recreate
> > your boot image or initrd but this appears to get past the initial boot
> > phase at least.
>
> Hi Mel,
>
> The patch works for me. The day gets better indeed. :-)
>
> Tested-by: Yury Norov <yury.norov@gmail.com>
>
Thanks! I've resent the patch to Andrew so hopefully it'll be picked up
before 5.0 is released.
--
Mel Gorman
SUSE Labs
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mgorman@techsingularity.net>
To: Yury Norov <yury.norov@gmail.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Andrea Arcangeli <aarcange@redhat.com>,
David Rientjes <rientjes@google.com>,
Michal Hocko <mhocko@kernel.org>, Zi Yan <zi.yan@cs.rutgers.edu>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Will Deacon <will.deacon@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: 5.0-rc kernel hangs on early boot
Date: Wed, 13 Feb 2019 13:19:48 +0000 [thread overview]
Message-ID: <20190213131948.GR9565@techsingularity.net> (raw)
In-Reply-To: <20190213115115.GA8928@yury-thinkpad>
On Wed, Feb 13, 2019 at 02:51:15PM +0300, Yury Norov wrote:
> On Wed, Feb 13, 2019 at 11:14:09AM +0000, Mel Gorman wrote:
> > On Wed, Feb 13, 2019 at 11:25:40AM +0300, Yury Norov wrote:
> > > 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.
> > >
> >
> > Well, that's a bad start to any day. Thanks for tracking it down. Does
> > the following patch help? I can't test it properly as I didn't recreate
> > your boot image or initrd but this appears to get past the initial boot
> > phase at least.
>
> Hi Mel,
>
> The patch works for me. The day gets better indeed. :-)
>
> Tested-by: Yury Norov <yury.norov@gmail.com>
>
Thanks! I've resent the patch to Andrew so hopefully it'll be picked up
before 5.0 is released.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2019-02-13 13:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 8:25 5.0-rc kernel hangs on early boot Yury Norov
2019-02-13 8:25 ` Yury Norov
2019-02-13 11:14 ` Mel Gorman
2019-02-13 11:14 ` Mel Gorman
2019-02-13 11:51 ` Yury Norov
2019-02-13 11:51 ` Yury Norov
2019-02-13 13:19 ` Mel Gorman [this message]
2019-02-13 13:19 ` Mel Gorman
2019-02-13 11:18 ` Will Deacon
2019-02-13 11:18 ` Will Deacon
2019-02-13 11:21 ` Mel Gorman
2019-02-13 11:21 ` Mel Gorman
2019-02-13 11:25 ` Will Deacon
2019-02-13 11:25 ` Will Deacon
2019-02-13 11:29 ` Mel Gorman
2019-02-13 11:29 ` Mel Gorman
2019-02-13 11:55 ` Yury Norov
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=20190213131948.GR9565@techsingularity.net \
--to=mgorman@techsingularity.net \
--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=mhocko@kernel.org \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=will.deacon@arm.com \
--cc=yury.norov@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.