From: Dmitry Vyukov <dvyukov@google.com>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Alexander Potapenko <glider@google.com>,
Marco Elver <elver@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jann Horn <jannh@google.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for Nov 5
Date: Tue, 10 Nov 2020 10:17:11 +0100 [thread overview]
Message-ID: <CACT4Y+ZA5tv4siG7JsXqmrk2J5WOQOtW51g0DPNMPSGHKkixDw@mail.gmail.com> (raw)
In-Reply-To: <CADYN=9J0DQhizAGB0-jz4HOBBh+05kMBXb4c0cXMS7Qi5NAJiw@mail.gmail.com>
On Tue, Nov 10, 2020 at 8:50 AM Anders Roxell <anders.roxell@linaro.org> wrote:
>
> On Thu, 5 Nov 2020 at 07:06, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Hi all,
> >
> > Changes since 20201104:
>
> When building an arm64 allmodconfig and booting up that in qemu I see
>
> [10011.092394][ T28] task:kworker/0:2 state:D stack:26896 pid:
> 1840 ppid: 2 flags:0x00000428
> [10022.368093][ T28] Workqueue: events toggle_allocation_gate
> [10024.827549][ T28] Call trace:
> [10027.152494][ T28] __switch_to+0x1cc/0x1e0
> [10031.378073][ T28] __schedule+0x730/0x800
> [10032.164468][ T28] schedule+0xd8/0x160
> [10033.886807][ T28] toggle_allocation_gate+0x16c/0x220
> [10038.477987][ T28] process_one_work+0x5c0/0x980
> [10039.900075][ T28] worker_thread+0x428/0x720
> [10042.782911][ T28] kthread+0x23c/0x260
> [10043.171725][ T28] ret_from_fork+0x10/0x18
> [10046.227741][ T28] INFO: lockdep is turned off.
> [10047.732220][ T28] Kernel panic - not syncing: hung_task: blocked tasks
> [10047.741785][ T28] CPU: 0 PID: 28 Comm: khungtaskd Tainted: G
> W 5.10.0-rc2-next-20201105-00006-g7af110e4d8ed #1
> [10047.755348][ T28] Hardware name: linux,dummy-virt (DT)
> [10047.763476][ T28] Call trace:
> [10047.769802][ T28] dump_backtrace+0x0/0x420
> [10047.777104][ T28] show_stack+0x38/0xa0
> [10047.784177][ T28] dump_stack+0x1d4/0x278
> [10047.791362][ T28] panic+0x304/0x5d8
> [10047.798202][ T28] check_hung_uninterruptible_tasks+0x5e4/0x640
> [10047.807056][ T28] watchdog+0x138/0x160
> [10047.814140][ T28] kthread+0x23c/0x260
> [10047.821130][ T28] ret_from_fork+0x10/0x18
> [10047.829181][ T28] Kernel Offset: disabled
> [10047.836274][ T28] CPU features: 0x0240002,20002004
> [10047.844070][ T28] Memory Limit: none
> [10047.853599][ T28] ---[ end Kernel panic - not syncing: hung_task:
> blocked tasks ]---
>
> if I build with KFENCE=n it boots up eventually, here's my .config file [2].
>
> Any idea what may happen?
>
> it happens on next-20201109 also, but it takes longer until we get the
> "Call trace:".
>
> Cheers,
> Anders
> [1] http://ix.io/2Ddv
> [2] https://people.linaro.org/~anders.roxell/allmodconfig-next-20201105.config
Hi Anders,
Does it happen during boot or afterwards?
10047 are seconds after boot, right? So this is like 3 hours after boot, no?
Also, is there anything useful before that part of the log? It seems
that at least the bug type header is stripped.
next prev parent reply other threads:[~2020-11-10 9:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 6:06 linux-next: Tree for Nov 5 Stephen Rothwell
2020-11-05 16:34 ` linux-next: Tree for Nov 5 [drivers/auxdisplay/hd44780_common.ko] Randy Dunlap
2020-11-05 20:29 ` linux-next: Tree for Nov 5 [drivers/net/ethernet/stmicro/stmmac/dwmac-thead.ko] Randy Dunlap
2020-11-10 7:50 ` linux-next: Tree for Nov 5 Anders Roxell
2020-11-10 9:17 ` Dmitry Vyukov [this message]
2020-11-10 9:25 ` Anders Roxell
2020-11-10 9:36 ` Dmitry Vyukov
2020-11-10 13:54 ` Marco Elver
2020-11-10 15:42 ` Anders Roxell
-- strict thread matches above, loose matches on Subject: below --
2021-11-05 3:39 Stephen Rothwell
2019-11-05 10:43 Stephen Rothwell
2018-11-05 5:51 Stephen Rothwell
2015-11-05 5:51 Stephen Rothwell
2014-11-05 6:53 Stephen Rothwell
2014-11-05 10:47 ` Guenter Roeck
2013-11-05 7:16 Stephen Rothwell
2012-11-05 5:49 Stephen Rothwell
2011-11-07 3:13 Stephen Rothwell
2011-11-07 5:52 ` Stephen Rothwell
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=CACT4Y+ZA5tv4siG7JsXqmrk2J5WOQOtW51g0DPNMPSGHKkixDw@mail.gmail.com \
--to=dvyukov@google.com \
--cc=akpm@linux-foundation.org \
--cc=anders.roxell@linaro.org \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).