I have found that running the command "fio --name=basic --directory=/path/to/empty/directory --size=1G --rw=randrw --numjobs=4 --loops=5" runs fine on linux-image-5.4.0-59-generic but when trying with linux-image-5.8.0-36-generic it would freeze the system in the "Laying out IO file" stage. I checked with two subsequent boots that the 5.8 does fail like this on an empty directory and will now use this as my "test" if a kernel works or not.
I have installed the 5.11 rc3 mainline kernel you linked, note I have had to disable secure boot to be able to use it. But this kernel worked successfully on two boots with the fio test above.
So in summary so far on my system with the fio test:
linux-image-5.4.0-59-generic: PASS
linux-image-5.8.0-36-generic: FAIL
linux-image-unsigned-5.11.0-051100rc3-generic: PASS
Please advise how to proceed here, should I start manually picking (by bisecting) kernels between 5.8 and 5.11 or between 5.4 and 5.8 ?
Also I guess I should also try 5.8 mainline to ensure that any Ubuntu patches aren't causing an issue?
@kaihengfeng
I have found that running the command "fio --name=basic --directory= /path/to/ empty/directory --size=1G --rw=randrw --numjobs=4 --loops=5" runs fine on linux-image- 5.4.0-59- generic but when trying with linux-image- 5.8.0-36- generic it would freeze the system in the "Laying out IO file" stage. I checked with two subsequent boots that the 5.8 does fail like this on an empty directory and will now use this as my "test" if a kernel works or not.
I have installed the 5.11 rc3 mainline kernel you linked, note I have had to disable secure boot to be able to use it. But this kernel worked successfully on two boots with the fio test above.
So in summary so far on my system with the fio test: 5.4.0-59- generic: PASS 5.8.0-36- generic: FAIL unsigned- 5.11.0- 051100rc3- generic: PASS
linux-image-
linux-image-
linux-image-
Please advise how to proceed here, should I start manually picking (by bisecting) kernels between 5.8 and 5.11 or between 5.4 and 5.8 ?
Also I guess I should also try 5.8 mainline to ensure that any Ubuntu patches aren't causing an issue?