From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Christoph Mathys <eraserix@gmail.com>
Cc: Linux RT Users <linux-rt-users@vger.kernel.org>
Subject: Re: Hung task for proc_cgroup_show
Date: Tue, 22 Dec 2015 14:51:53 +0100 [thread overview]
Message-ID: <20151222135153.GB27274@linutronix.de> (raw)
In-Reply-To: <CALqGcGrzpA_95LiL+4dHKX6xf7iwz-uL0_y8BtnQJgKLkZD-4w@mail.gmail.com>
* Christoph Mathys | 2015-12-22 13:36:19 [+0100]:
>I tried to reproduce this bug in kvm, hoping to get copy/pastable
>dumps. The test didn't run at all, instead I got a stunning number of
>the following slowpath warning (seem like it was repeated over 100
>times during 9ms). I see them occasionally (less than once every few
>minutes) on real hardware as well. I don't know what to make of them
>and if they can help in any way. Here is the repeated message:
>
>[ 63.141432] WARNING: CPU: 0 PID: 54 at kernel/res_counter.c:28
>res_counter_uncharge_until+0x98/0xa0()
It seems the ressource counter code is somehow unbalanced. It has its
own lock but you see what you see.
You could try without CONFIG_RESOURCE_COUNTERS or switch to v4.1 instead
since it has the file in question removed as per 5b1efc027c0b ("kernel:
res_counter: remove the unused API").
Sebastian
next prev parent reply other threads:[~2015-12-22 13:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 14:40 Hung task for proc_cgroup_show Christoph Mathys
2015-07-14 14:45 ` Christoph Mathys
2015-07-14 15:00 ` Sebastian Andrzej Siewior
2015-08-03 6:19 ` Christoph Mathys
2015-12-11 16:14 ` Sebastian Andrzej Siewior
2015-12-21 8:58 ` Christoph Mathys
2015-12-21 9:49 ` Christoph Mathys
2015-12-21 17:59 ` Sebastian Andrzej Siewior
2015-12-21 18:11 ` Sebastian Andrzej Siewior
2015-12-22 12:36 ` Christoph Mathys
2015-12-22 13:51 ` Sebastian Andrzej Siewior [this message]
2015-12-23 6:53 ` Christoph Mathys
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151222135153.GB27274@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=eraserix@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).