From: Joel Fernandes <joel@joelfernandes.org>
To: rcu@vger.kernel.org, Zqiang <qiang1.zhang@intel.com>
Cc: paulmck@kernel.org
Subject: [Report] v4.19 TREE03 splat (stable kernel with ChromeOS patches)
Date: Fri, 9 Dec 2022 23:34:10 +0000 [thread overview]
Message-ID: <Y5PF8vismgZLzFam@google.com> (raw)
Hello,
I see this an hour into the run for TREE03 on v4.19:
tools/testing/selftests/rcutorture/bin/kvm.sh --cpus 32 --duration 60
Checking to see if Qiang has any thoughts as I saw him comment about a similar
issue in [1].
[ 3243.844445] ------------[ cut here ]------------^M
[ 3243.847112] WARNING: CPU: 1 PID: 0 at kernel/kthread.c:411 __kthread_bind_mask+0x19/0x60^M
[ 3243.851585] Modules linked in:^M
[ 3243.853295] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.19.267+ #1^M
[ 3243.856699] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.0-debian-1.16.0-4 04/01/2014^M
[ 3243.860052] RIP: 0010:__kthread_bind_mask+0x19/0x60^M
[ 3243.861769] Code: 48 89 42 20 c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 41 55 41 54 55 48 89 f5 48 89 d6 53 48 89 fb e8 3c e9 00 00 48 85 c0 75 09 <0f> 0b 5b 5d 41 5c 41 5d c3 4c 8d ab b4 07 00 00 4c 89 ef e8 6f 28^M
[ 3243.867751] RSP: 0000:ffffa54b8014fec0 EFLAGS: 00010246^M
[ 3243.868959] RAX: 0000000000000000 RBX: ffff95555ee3c240 RCX: 0000000000000000^M
[ 3243.870606] RDX: ffff95555f063d80 RSI: 0000000000000246 RDI: 00000000ffffffff^M
[ 3243.872246] RBP: ffffffffb720a010 R08: af82bdcb11f9f4ff R09: 0000000000000000^M
[ 3243.873894] R10: ffffa54b8014fe70 R11: 00000000621ccdc2 R12: 0000000000000000^M
[ 3243.875538] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000^M
[ 3243.877181] FS: 0000000000000000(0000) GS:ffff95555f040000(0000) knlGS:0000000000000000^M
[ 3243.878698] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033^M
[ 3243.879747] CR2: 0000000000000000 CR3: 000000001300a000 CR4: 00000000000006e0^M
[ 3243.881050] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000^M
[ 3243.882358] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400^M
[ 3243.883660] Call Trace:^M
[ 3243.884925] kthread_unpark+0x52/0x60^M
[ 3243.885613] cpuhp_online_idle+0x31/0x50^M
[ 3243.886341] cpu_startup_entry+0x62/0x70^M
[ 3243.887063] start_secondary+0x186/0x1b0^M
[ 3243.887783] secondary_startup_64+0xa4/0xb0^M
[1] https://groups.google.com/g/syzkaller-bugs/c/w_LARy6pxvQ/m/dKjQyHAxAQAJ
thanks,
- Joel
next reply other threads:[~2022-12-09 23:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 23:34 Joel Fernandes [this message]
2022-12-10 3:22 ` [Report] v4.19 TREE03 splat (stable kernel with ChromeOS patches) Joel Fernandes
2022-12-12 11:45 ` Zhang, Qiang1
2022-12-12 14:05 ` Joel Fernandes
2022-12-13 13:21 ` Zhang, Qiang1
2022-12-13 15:54 ` Joel Fernandes
2022-12-14 8:33 ` Zhang, Qiang1
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=Y5PF8vismgZLzFam@google.com \
--to=joel@joelfernandes.org \
--cc=paulmck@kernel.org \
--cc=qiang1.zhang@intel.com \
--cc=rcu@vger.kernel.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 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.