From: Ben Greear <greearb@candelatech.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: BUG: Invalid wait context, related to serial console?
Date: Tue, 22 Sep 2020 11:19:06 -0700 [thread overview]
Message-ID: <f575655b-92cf-b59f-659a-3d649a8a5713@candelatech.com> (raw)
I saw this booting yesterday's 5.9.0-rc6+. I have one small patch applied, quite unlikely
to cause any problems I think. Platform is apu2, fedora-27 linux, with serial console attached.
[ 0.624831] =============================
[ 0.624831] [ BUG: Invalid wait context ]
[ 0.624831] 5.9.0-rc6+ #1 Not tainted
[ 0.624831] -----------------------------
[ 0.624831] swapper/1/0 is trying to lock:
[ 0.624831] ffffffff85523218 (&port_lock_key){....}-{3:3}, at: serial8250_console_write+0xfd/0x520
[ 0.624831] other info that might help us debug this:
[ 0.624831] context-{2:2}
[ 0.624831] 2 locks held by swapper/1/0:
[ 0.624831] #0: ffffffff83338a60 (console_lock){+.+.}-{0:0}, at: printk+0xad/0xde
[ 0.624831] #1: ffffffff83338820 (console_owner){-...}-{0:0}, at: console_unlock+0x291/0x840
[ 0.624831] stack backtrace:
[ 0.624831] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.9.0-rc6+ #1
[ 0.624831] Hardware name: PC Engines APU2/APU2, BIOS 4.0.7 02/28/2017
[ 0.624831] Call Trace:
[ 0.624831] dump_stack+0xae/0xe8
[ 0.624831] __lock_acquire.cold+0x1b9/0x34d
[ 0.624831] ? save_trace+0x345/0x440
[ 0.624831] ? lockdep_hardirqs_on_prepare+0x260/0x260
[ 0.624831] ? mark_lock+0x90/0xb00
[ 0.624831] lock_acquire+0x14f/0x5f0
[ 0.624831] ? serial8250_console_write+0xfd/0x520
[ 0.624831] ? lock_release+0x440/0x440
[ 0.624831] ? lockdep_hardirqs_on_prepare+0x260/0x260
[ 0.624831] ? __lock_acquire+0x85c/0x2f10
[ 0.624831] _raw_spin_lock_irqsave+0x43/0x60
[ 0.624831] ? serial8250_console_write+0xfd/0x520
[ 0.624831] serial8250_console_write+0xfd/0x520
[ 0.624831] ? serial8250_config_port+0x1630/0x1630
[ 0.624831] ? lock_downgrade+0x3a0/0x3a0
[ 0.624831] ? do_raw_spin_lock+0x114/0x1a0
[ 0.624831] ? rwlock_bug.part.0+0x50/0x50
[ 0.624831] console_unlock+0x582/0x840
[ 0.624831] ? devkmsg_open+0x170/0x170
[ 0.624831] ? do_raw_spin_unlock+0x8e/0xe0
[ 0.624831] ? printk+0xad/0xde
[ 0.624831] vprintk_emit+0x165/0x3e0
[ 0.624831] printk+0xad/0xde
[ 0.624831] ? kmsg_dump_rewind_nolock+0x54/0x54
[ 0.624831] ? lock_acquire+0x14f/0x5f0
[ 0.624831] ? do_raw_spin_unlock+0x8e/0xe0
[ 0.624831] ? do_raw_spin_unlock+0x7f/0xe0
[ 0.624831] common_interrupt+0x16c/0x180
[ 0.624831] asm_common_interrupt+0x1e/0x40
[ 0.624831] RIP: 0010:start_secondary+0x1b6/0x230
[ 0.624831] Code: 65 8b 3d 1d 97 f7 7e e8 48 f0 14 00 48 c7 c7 d0 d4 04 83 e8 4c 15 45 00 ff 15 76 d8 fa 01 e8 31 6f 2b 00 fb 66 0f 1f 44 00 00 <48> c7 c7 40
33 29 83 e8 2e 15 45 00 ff 15 c8 36 1f 02 0f ae f8 bf
[ 0.624831] RSP: 0000:ffff8880cda3fed8 EFLAGS: 00000202
[ 0.624831] RAX: 0000000000000001 RBX: 0000000000000001 RCX: dffffc0000000000
[ 0.624831] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffffffff8109fc5f
[ 0.624831] RBP: 1ffff11019b47fdb R08: 0000000000000001 R09: 0000000000000001
[ 0.624831] R10: ffffed101a494179 R11: 0000000000000001 R12: 00000000000f3aac
[ 0.624831] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[ 0.624831] ? start_secondary+0x1af/0x230
[ 0.624831] ? start_secondary+0x1af/0x230
[ 0.624831] ? set_cpu_sibling_map+0xc70/0xc70
[ 0.624831] secondary_startup_64+0xa4/0xb0
[ 2.531065] #2
[ 0.624831] __common_interrupt: 2.55 No irq handler for vector
[ 2.542389] #3
[ 0.624831] __common_interrupt: 3.55 No irq handler for vector
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
reply other threads:[~2020-09-22 18:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f575655b-92cf-b59f-659a-3d649a8a5713@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®