On 12/21/2015 04:14 PM, Christoph Lameter wrote: > On Mon, 21 Dec 2015, Sasha Levin wrote: > >> > I've also noticed a new warning from the workqueue code which my scripts >> > didn't pick up before: >> > >> > [ 3462.380681] BUG: workqueue lockup - pool cpus=2 node=2 flags=0x4 nice=0 stuck for 54s! >> > [ 3462.522041] workqueue vmstat: flags=0xc >> > [ 3462.527795] pwq 4: cpus=2 node=2 flags=0x0 nice=0 active=1/256 >> > [ 3462.554836] pending: vmstat_update > Does that mean that vmstat_update locks up or something that schedules it? I think it means that vmstat_update didn't finish running (working). > Also what workload triggers the BUG()? Fuzzing with trinity inside a KVM guest. I've attached my config. Thanks, Sasha
Attachment:
config-sasha.gz
Description: application/gzip