From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Peter Hurley <peter@hurleysoftware.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Peter Zijlstra <peterz@infradead.org>
Cc: "Bruno Prémont" <bonbons@linux-vserver.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
tglx@linutronix.de, ilya.dryomov@inktank.com,
umgwanakikbuti@gmail.com, oleg@redhat.com
Subject: Re: Linux 3.19-rc5
Date: Fri, 30 Jan 2015 02:22:58 +0100 [thread overview]
Message-ID: <1861286.x5DC37NGWz@vostro.rjw.lan> (raw)
In-Reply-To: <54C02E08.4080405@hurleysoftware.com>
On Wednesday, January 21, 2015 05:54:00 PM Peter Hurley wrote:
> On 01/21/2015 05:12 PM, Davidlohr Bueso wrote:
> > On Wed, 2015-01-21 at 22:37 +0100, Bruno Prémont wrote:
> >> On Wed, 21 January 2015 Bruno Prémont wrote:
> >>> On Tue, 20 January 2015 Linus Torvalds wrote:
> >>>> On Tue, Jan 20, 2015 at 6:02 AM, Bruno Prémont wrote:
> >>>>>
> >>>>> No idea yet which rc is the offender (nor exact patch), but on my not
> >>>>> so recent UP laptop with a pccard slot I have 2 pccardd kernel threads
> >>>>> converting my laptop into a heater.
>
> [...]
>
> >> Bisecting to the end did point me at (the warning traces produced in great
> >> quantities might not be the very same issue as the abusive CPU usage, but
> >> certainly look very related):
> >> [CCing people on CC for the patch]
> >>
> >> commit 8eb23b9f35aae413140d3fda766a98092c21e9b0
> >> Author: Peter Zijlstra <peterz@infradead.org>
> >> Date: Wed Sep 24 10:18:55 2014 +0200
>
> [...]
>
> >> Which does produce the following trace (hand-copied most important parts of it):
> >> Warning: CPU 0 PID: 68 at kernel/sched/core.c:7311 __might_sleep+0x143/0x170
> >> do not call blocking ops when !TASK_RUNNING; state=1 set at [<c1436390>] pccardd+0xa0/0x3e0
> >> ...
> >> Call trace:
> >> ...
> >> __might_sleep+0x143/0x170
> >> ? pccardd+0xa0/0x3e0
> >> ? pccardd+0xa0/0x3e0
> >> mutex_lock+0x17/0x2a
> >> pccardd+0xe9/0x3e0
> >> ? pcmcia_socket_uevent+0x30/0x30
> >>
> >> pccardd() is located in drivers/pcmcia/cs.c and seems to be of the structure
> >> Peter's patch wants to warn about.
> >
> > Yeah setting current to interruptable so early in the game is bogus. It
> > should be set after unlocking the skt_mutex.
>
> Yeah, but the debug check is triggering worse behavior, requiring
> bisecting back to the debug commit.
Yes, it is.
So I'm wondering is anyone is working on fixing this in any way?
It kind of sucks when this is happening on an otherwise perfectly usable
old(ish) machine ...
Rafael
next prev parent reply other threads:[~2015-01-30 1:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 9:17 Linus Torvalds
2015-01-19 18:02 ` Bruno Prémont
2015-01-20 6:24 ` Linus Torvalds
2015-01-21 20:37 ` Bruno Prémont
2015-01-21 21:37 ` Bruno Prémont
2015-01-21 22:12 ` Davidlohr Bueso
2015-01-21 22:54 ` Peter Hurley
2015-01-30 1:22 ` Rafael J. Wysocki [this message]
2015-01-30 1:12 ` Linus Torvalds
2015-01-30 1:25 ` Linus Torvalds
2015-01-30 1:35 ` Linus Torvalds
2015-01-30 2:06 ` Rafael J. Wysocki
2015-01-30 15:47 ` Oleg Nesterov
2015-01-31 18:32 ` Linus Torvalds
2015-01-31 20:16 ` Peter Zijlstra
2015-01-31 21:54 ` Linus Torvalds
2015-02-02 13:19 ` Peter Zijlstra
2015-02-01 19:43 ` Oleg Nesterov
2015-02-01 20:09 ` Linus Torvalds
2015-02-01 20:19 ` Oleg Nesterov
2015-02-02 15:34 ` Peter Zijlstra
2015-01-31 9:16 ` Bruno Prémont
2015-01-31 9:48 ` Peter Zijlstra
2015-02-03 11:18 ` Ingo Molnar
2015-02-05 21:14 ` Bruno Prémont
2015-02-06 11:50 ` Peter Zijlstra
2015-02-06 16:02 ` Linus Torvalds
2015-02-06 16:39 ` Peter Zijlstra
2015-02-06 16:46 ` Linus Torvalds
2015-01-30 1:49 ` Rafael J. Wysocki
2015-02-02 9:48 ` Zdenek Kabelac
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=1861286.x5DC37NGWz@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=bonbons@linux-vserver.org \
--cc=dave@stgolabs.net \
--cc=ilya.dryomov@inktank.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peter@hurleysoftware.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=umgwanakikbuti@gmail.com \
/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
all inboxes | Powered by JetHome®