On Wed, Dec 20, 2017 at 03:24:09PM -0800, Tejun Heo wrote:
> On Thu, Dec 21, 2017 at 12:59:23AM +0200, Dan Aloni wrote:
> > Hi,
> >
> > Using netconsole, I was able to capture a hard lockup that seems to be
> > related to cgroups, on a Fedora kernel based on v4.14.4.
> >
> > By my analysis, from
On Wed, Dec 20, 2017 at 03:24:09PM -0800, Tejun Heo wrote:
> On Thu, Dec 21, 2017 at 12:59:23AM +0200, Dan Aloni wrote:
> > Hi,
> >
> > Using netconsole, I was able to capture a hard lockup that seems to be
> > related to cgroups, on a Fedora kernel based on v4.14.4.
> >
> > By my analysis, from
On Thu, Dec 21, 2017 at 12:59:23AM +0200, Dan Aloni wrote:
> Hi,
>
> Using netconsole, I was able to capture a hard lockup that seems to be
> related to cgroups, on a Fedora kernel based on v4.14.4.
>
> By my analysis, from the 16 CPUs below, 14 are on css_set_lock, one is
> inside
On Thu, Dec 21, 2017 at 12:59:23AM +0200, Dan Aloni wrote:
> Hi,
>
> Using netconsole, I was able to capture a hard lockup that seems to be
> related to cgroups, on a Fedora kernel based on v4.14.4.
>
> By my analysis, from the 16 CPUs below, 14 are on css_set_lock, one is
> inside
Hi,
Using netconsole, I was able to capture a hard lockup that seems to be
related to cgroups, on a Fedora kernel based on v4.14.4.
By my analysis, from the 16 CPUs below, 14 are on css_set_lock, one is
inside css_task_iter_advance, and the last one stuck trying to send an
IPI, I guess because
Hi,
Using netconsole, I was able to capture a hard lockup that seems to be
related to cgroups, on a Fedora kernel based on v4.14.4.
By my analysis, from the 16 CPUs below, 14 are on css_set_lock, one is
inside css_task_iter_advance, and the last one stuck trying to send an
IPI, I guess because
6 matches
Mail list logo