* blktests 002/029/030 error report
@ 2022-11-15 0:41 Chaitanya Kulkarni
2022-11-15 19:48 ` Chaitanya Kulkarni
0 siblings, 1 reply; 3+ messages in thread
From: Chaitanya Kulkarni @ 2022-11-15 0:41 UTC (permalink / raw)
To: linux-block
Hi,
blktests on latest linux-block/for-next are failing:-
blktests (master) # ./check block/002
block/002 (remove a device while running blktrace) [failed]
runtime 1.258s ... 1.236s
--- tests/block/002.out 2021-08-29 01:09:20.280901669 -0700
+++ /mnt/data/blktests/results/nodev/block/002.out.bad 2022-11-14
16:34:15.048665046 -0800
@@ -1,2 +1,3 @@
Running block/002
+debugfs directory deleted with blktrace active
Test complete
------------------------------------------------------------------------
blktests (master) # ./check block/029
block/029 (trigger blk_mq_update_nr_hw_queues()) [failed]
runtime 30.301s ... 30.320s
--- tests/block/029.out 2021-08-29 01:09:20.283901718 -0700
+++ /mnt/data/blktests/results/nodev/block/029.out.bad 2022-11-14
16:35:11.317963411 -0800
@@ -1 +1,125 @@
+tests/block/029: line 24: echo: write error: Cannot allocate memory
+tests/block/029: line 24: echo: write error: Cannot allocate memory
+tests/block/029: line 24: echo: write error: Cannot allocate memory
+tests/block/029: line 24: echo: write error: Cannot allocate memory
+tests/block/029: line 24: echo: write error: Cannot allocate memory
+tests/block/029: line 24: echo: write error: Cannot allocate memory
+tests/block/029: line 24: echo: write error: Cannot allocate memory
...
(Run 'diff -u tests/block/029.out
/mnt/data/blktests/results/nodev/block/029.out.bad' to see the entire diff)
blktests (master) # dmesg -c
[ 1303.394737] run blktests block/029 at 2022-11-14 16:37:06
[ 1303.413642] null_blk: module loaded
[ 1303.427029] null_blk: disk nullb0 created
---------------------------------------------------------------------------
blktests (master) # ./check block/030
block/030 (trigger the blk_mq_realloc_hw_ctxs() error path) [failed]
runtime 3.027s ... 3.042s
--- tests/block/030.out 2021-08-29 01:09:20.283901718 -0700
+++ /mnt/data/blktests/results/nodev/block/030.out.bad 2022-11-14
16:35:20.290162139 -0800
@@ -1 +1,101 @@
+tests/block/030: line 44: echo: write error: Cannot allocate memory
+tests/block/030: line 44: echo: write error: Cannot allocate memory
+tests/block/030: line 44: echo: write error: Cannot allocate memory
+tests/block/030: line 44: echo: write error: Cannot allocate memory
+tests/block/030: line 44: echo: write error: Cannot allocate memory
+tests/block/030: line 44: echo: write error: Cannot allocate memory
+tests/block/030: line 44: echo: write error: Cannot allocate memory
...
(Run 'diff -u tests/block/030.out
/mnt/data/blktests/results/nodev/block/030.out.bad' to see the entire diff)
blktests (master) # dmesg -c
1365.624495] run blktests block/030 at 2022-11-14 16:38:08
[ 1365.647898] null_blk: module loaded
[ 1365.667866] null_blk: disk nullb0 created
[ 1365.682877] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.696026] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.714468] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.729365] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.748381] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.763305] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.777343] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.789284] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.807357] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.820338] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.834399] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.847307] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.861327] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.874379] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.889348] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.903330] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.916317] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.929265] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.942338] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.957293] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.971316] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1365.988176] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.002268] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.015251] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.015346] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.035426] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.051339] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.064433] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.080314] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.097333] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.110269] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.125388] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.139331] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.152449] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.172338] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.186332] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.202201] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.213239] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.229313] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.243247] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.258335] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.271312] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.285251] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.298447] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.310253] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.324285] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
[ 1366.338172] Allocate new hctx on node 0 fails, fallback to previous
one on node 0
-ck
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: blktests 002/029/030 error report
2022-11-15 0:41 blktests 002/029/030 error report Chaitanya Kulkarni
@ 2022-11-15 19:48 ` Chaitanya Kulkarni
2022-11-16 8:42 ` Shinichiro Kawasaki
0 siblings, 1 reply; 3+ messages in thread
From: Chaitanya Kulkarni @ 2022-11-15 19:48 UTC (permalink / raw)
To: shinichiro.kawasaki; +Cc: linux-block
Shinichiro,
On 11/14/22 16:41, Chaitanya Kulkarni wrote:
> Hi,
>
> blktests on latest linux-block/for-next are failing:-
>
Do you also see similar failures when running blktests block
category ?
-ck
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: blktests 002/029/030 error report
2022-11-15 19:48 ` Chaitanya Kulkarni
@ 2022-11-16 8:42 ` Shinichiro Kawasaki
0 siblings, 0 replies; 3+ messages in thread
From: Shinichiro Kawasaki @ 2022-11-16 8:42 UTC (permalink / raw)
To: Chaitanya Kulkarni; +Cc: linux-block
On Nov 15, 2022 / 19:48, Chaitanya Kulkarni wrote:
> Shinichiro,
>
> On 11/14/22 16:41, Chaitanya Kulkarni wrote:
> > Hi,
> >
> > blktests on latest linux-block/for-next are failing:-
> >
>
> Do you also see similar failures when running blktests block
> category ?
I've tried with linux-block/for-next branch tip at git hash 067707e91646. To
compile kernel, I needed to revert the commit 958bfdd734b6 ("io_uring: uapi:
Don't force linux/time_types.h for userspace"). With this kernel and my test
machine,
- the block/002 failure was not recreated
- the block/029,030 failures were recreated
- another failure was observed at block/017 [1]
Will take closer look in the problems, as much as I can.
[1]
block/017 (do I/O and check the inflight counter) [failed]
runtime ... 1.854s
--- tests/block/017.out 2022-11-14 16:40:48.486495344 +0900
+++ /home/shin/kts/kernel-test-suite/sets/blktests/log/runlog/nodev/block/017.out.bad 2022-11-16 17:36:33.028161082 +0900
@@ -5,8 +5,8 @@
diskstats 1
sysfs inflight reads 1
sysfs inflight writes 1
-sysfs stat 2
-diskstats 2
+sysfs stat 1
+diskstats 1
...
(Run 'diff -u tests/block/017.out /home/shin/kts/kernel-test-suite/sets/blktests/log/runlog/nodev/block/017.out.bad' to see the entire diff)
--
Shin'ichiro Kawasaki
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-11-16 8:42 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-11-15 0:41 blktests 002/029/030 error report Chaitanya Kulkarni
2022-11-15 19:48 ` Chaitanya Kulkarni
2022-11-16 8:42 ` Shinichiro Kawasaki
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.