On Fri, Jul 10, 2020 at 9:36 PM Vineeth Remanan Pillai <[email protected]> wrote: > > Hi Aubrey, > > On Fri, Jul 10, 2020 at 8:19 AM Li, Aubrey <[email protected]> wrote: > > > > Hi Joel/Vineeth, > > [...] > > The problem is gone when we reverted this patch. We are running multiple > > uperf threads(equal to cpu number) in a cgroup with coresched enabled. > > This is 100% reproducible on our side. > > > > Just wonder if anything already known before we dig into it. > > > Thanks for reporting this. We haven't seen any lockups like this > in our testing yet.
This is replicable on a bare metal machine. We tried to reproduce on a 8-cpus KVM vm but failed. > Could you please add more information on how to reproduce this? > Was it a simple uperf run without any options or was it running any > specific kind of network test? I put our scripts at here: https://github.com/aubreyli/uperf > > We shall also try to reproduce this and investigate. I'll try to see if I can narrow down the test case and grab some logs next week. Thanks, -Aubrey
