On 2017/03/19 17:17, Gerhard Wiesinger wrote: > On 17.03.2017 21:08, Gerhard Wiesinger wrote: >> On 17.03.2017 18:13, Michal Hocko wrote: >>> On Fri 17-03-17 17:37:48, Gerhard Wiesinger wrote: >>> [...] > > 4.11.0-0.rc2.git4.1.fc27.x86_64 > > There are also lockups after some runtime hours to 1 day: > Message from syslogd@myserver Mar 19 08:22:33 ... > kernel:BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 18717s! > > Message from syslogd@myserver at Mar 19 08:22:33 ... > kernel:BUG: workqueue lockup - pool cpus=1 node=0 flags=0x0 nice=0 stuck for 18078s! > > repeated a lot of times .... > > Ciao, > Gerhard "kernel:BUG: workqueue lockup" lines alone do not help. It does not tell what work is stalling. Maybe stalling due to constant swapping while doing memory allocation when processing some work, but relevant lines are needed in order to know what is happening. You can try SysRq-t to dump what workqueue threads are doing when you encounter such lines. You might want to try kmallocwd at http://lkml.kernel.org/r/1489578541-81526-1-git-send-email-penguin-kernel@xxxxxxxxxxxxxxxxxxx . -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
