From: John David Anglin <dave.anglin@bell.net>
To: Jens Axboe <axboe@kernel.dk>, Helge Deller <deller@gmx.de>,
io-uring@vger.kernel.org, linux-parisc@vger.kernel.org,
James Bottomley <James.Bottomley@hansenpartnership.com>
Subject: Re: io_uring failure on parisc with VIPT caches
Date: Wed, 15 Feb 2023 16:39:22 -0500 [thread overview]
Message-ID: <5e72c1fc-1a7b-a4ed-4097-96816b802e6d@bell.net> (raw)
In-Reply-To: <c7725c80-ba8c-1182-7adc-bc107f4f5b75@bell.net>
On 2023-02-15 4:06 p.m., John David Anglin wrote:
> On 2023-02-15 3:37 p.m., Jens Axboe wrote:
>>> System crashes running test buf-ring.t.
>> Huh, what's the crash?
> Not much info. System log indicates an HPMC occurred. Unfortunately, recovery code doesn't work.
The following occurred running buf-ring.t under gdb:
INFO: task kworker/u64:9:18319 blocked for more than 123 seconds.
Not tainted 6.1.12+ #4
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u64:9 state:D stack:0 pid:18319 ppid:2 flags:0x00000000
Workqueue: events_unbound io_ring_exit_work
Backtrace:
[<0000000040b5c210>] __schedule+0x2e8/0x7f0
[<0000000040b5c7d0>] schedule+0xb8/0x1d0
[<0000000040b66534>] schedule_timeout+0x11c/0x1b0
[<0000000040b5d71c>] __wait_for_common+0x194/0x2e8
[<0000000040b5d8ac>] wait_for_completion+0x3c/0x50
[<0000000040b46508>] io_ring_exit_work+0x3d8/0x4d0
[<0000000040268da8>] process_one_work+0x238/0x520
[<00000000402692a4>] worker_thread+0x214/0x778
[<0000000040276f94>] kthread+0x24c/0x258
[<0000000040202020>] ret_from_kernel_thread+0x20/0x28
INFO: task kworker/u64:10:18320 blocked for more than 123 seconds.
Not tainted 6.1.12+ #4
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:kworker/u64:10 state:D stack:0 pid:18320 ppid:2 flags:0x00000000
Workqueue: events_unbound io_ring_exit_work
Backtrace:
[<0000000040b5c210>] __schedule+0x2e8/0x7f0
[<0000000040b5c7d0>] schedule+0xb8/0x1d0
[<0000000040b66534>] schedule_timeout+0x11c/0x1b0
[<0000000040b5d71c>] __wait_for_common+0x194/0x2e8
[<0000000040b5d8ac>] wait_for_completion+0x3c/0x50
[<0000000040b46508>] io_ring_exit_work+0x3d8/0x4d0
[<0000000040268da8>] process_one_work+0x238/0x520
[<00000000402692a4>] worker_thread+0x214/0x778
[<0000000040276f94>] kthread+0x24c/0x258
[<0000000040202020>] ret_from_kernel_thread+0x20/0x28
gdb was sitting at a break at line 328.
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2023-02-15 21:39 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 9:47 io_uring failure on parisc (32-bit userspace and 64-bit kernel) Helge Deller
2023-02-12 13:16 ` Jens Axboe
2023-02-12 13:28 ` Helge Deller
2023-02-12 13:35 ` Jens Axboe
2023-02-12 14:00 ` Jens Axboe
2023-02-12 14:03 ` Helge Deller
2023-02-12 19:35 ` Helge Deller
2023-02-12 19:42 ` Jens Axboe
2023-02-12 20:01 ` Helge Deller
2023-02-12 21:48 ` Jens Axboe
2023-02-12 22:20 ` Helge Deller
2023-02-12 22:31 ` Helge Deller
2023-02-13 16:15 ` Jens Axboe
2023-02-13 20:59 ` Helge Deller
2023-02-13 21:05 ` Jens Axboe
2023-02-13 22:05 ` Helge Deller
2023-02-13 22:50 ` John David Anglin
2023-02-14 23:09 ` io_uring failure on parisc with VIPT caches Helge Deller
2023-02-14 23:29 ` Jens Axboe
2023-02-15 2:12 ` John David Anglin
2023-02-15 15:16 ` Jens Axboe
2023-02-15 15:52 ` Helge Deller
2023-02-15 15:56 ` Jens Axboe
2023-02-15 16:02 ` Helge Deller
2023-02-15 16:04 ` Jens Axboe
2023-02-15 16:38 ` John David Anglin
2023-02-15 17:01 ` Jens Axboe
2023-02-15 19:00 ` Jens Axboe
2023-02-15 19:16 ` Jens Axboe
2023-02-15 20:27 ` John David Anglin
2023-02-15 20:37 ` Jens Axboe
2023-02-15 21:06 ` John David Anglin
2023-02-15 21:38 ` Jens Axboe
2023-02-15 21:39 ` John David Anglin [this message]
2023-02-15 22:10 ` John David Anglin
2023-02-15 23:02 ` Jens Axboe
2023-02-15 23:43 ` John David Anglin
2023-02-16 2:40 ` John David Anglin
2023-02-16 2:50 ` Jens Axboe
2023-02-16 8:24 ` Helge Deller
2023-02-16 15:22 ` Jens Axboe
2023-02-16 20:35 ` John David Anglin
2023-02-15 23:03 ` Jens Axboe
2023-02-15 19:20 ` John David Anglin
2023-02-15 19:24 ` Jens Axboe
2023-02-15 16:18 ` John David Anglin
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=5e72c1fc-1a7b-a4ed-4097-96816b802e6d@bell.net \
--to=dave.anglin@bell.net \
--cc=James.Bottomley@hansenpartnership.com \
--cc=axboe@kernel.dk \
--cc=deller@gmx.de \
--cc=io-uring@vger.kernel.org \
--cc=linux-parisc@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