Messages in this thread | | | From | Oleksandr Natalenko <> | Subject | Re: New warning in nvme_setup_discard | Date | Sat, 17 Jul 2021 14:11:05 +0200 |
| |
On sobota 17. července 2021 11:35:32 CEST Ming Lei wrote: > Maybe you need to check if the build is OK, I can't reproduce it in my > VM, and BFQ is still builtin: > > [root@ktest-01 ~]# uname -a > Linux ktest-01 5.14.0-rc1+ #52 SMP Fri Jul 16 18:56:36 CST 2021 x86_64 > x86_64 x86_64 GNU/Linux [root@ktest-01 ~]# cat > /sys/block/nvme0n1/queue/scheduler > [none] mq-deadline kyber bfq
I don't think this is an issue with the build… BTW, with `initcall_debug`:
``` [ 0.902555] calling bfq_init+0x0/0x8b @ 1 [ 0.903448] initcall bfq_init+0x0/0x8b returned -28 after 507 usecs ```
-ENOSPC? Why? Also re-tested with the latest git tip, same result :(.
> > So far the issue is not reproducible with your patch + 5.13.2 as well as > > 5.14- rc1 (but I don't have BFQ either with v5.14-rc1). > > You have to verify it with BFQ applied, :-)
Understandable… BTW, I'm still running v5.13.2 with your patch applied and do not see the issue.
-- Oleksandr Natalenko (post-factum)
| |