From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Thomas Huth <thuth@redhat.com>
Cc: linuxppc-dev@lists.ozlabs.org, anton@samba.org, kvm-ppc@vger.kernel.org
Subject: Re: BUG: sleeping function called from ras_epow_interrupt context
Date: Tue, 14 Jul 2015 21:22:57 +0000 [thread overview]
Message-ID: <1436908977.3948.266.camel@kernel.crashing.org> (raw)
In-Reply-To: <55A55846.5080904@redhat.com>
On Tue, 2015-07-14 at 20:43 +0200, Thomas Huth wrote:
> Any suggestions how to fix this? Simply revert 587f83e8dd50d? Use
> mdelay() instead of msleep() in rtas_busy_delay()? Something more
> fancy?
A proper fix would be more fancy, the get_sensor should happen in a
kernel thread instead.
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Thomas Huth <thuth@redhat.com>
Cc: linuxppc-dev@lists.ozlabs.org, anton@samba.org, kvm-ppc@vger.kernel.org
Subject: Re: BUG: sleeping function called from ras_epow_interrupt context
Date: Wed, 15 Jul 2015 07:22:57 +1000 [thread overview]
Message-ID: <1436908977.3948.266.camel@kernel.crashing.org> (raw)
In-Reply-To: <55A55846.5080904@redhat.com>
On Tue, 2015-07-14 at 20:43 +0200, Thomas Huth wrote:
> Any suggestions how to fix this? Simply revert 587f83e8dd50d? Use
> mdelay() instead of msleep() in rtas_busy_delay()? Something more
> fancy?
A proper fix would be more fancy, the get_sensor should happen in a
kernel thread instead.
Cheers,
Ben.
next prev parent reply other threads:[~2015-07-14 21:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 18:43 BUG: sleeping function called from ras_epow_interrupt context Thomas Huth
2015-07-14 18:43 ` Thomas Huth
2015-07-14 21:22 ` Benjamin Herrenschmidt [this message]
2015-07-14 21:22 ` Benjamin Herrenschmidt
2015-07-15 14:35 ` Thomas Huth
2015-07-15 14:35 ` Thomas Huth
2015-07-15 19:58 ` Nathan Fontenot
2015-07-15 19:58 ` Nathan Fontenot
2015-07-16 6:23 ` Thomas Huth
2015-07-16 6:23 ` Thomas Huth
2015-07-16 17:39 ` Nathan Fontenot
2015-07-16 17:39 ` Nathan Fontenot
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=1436908977.3948.266.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=anton@samba.org \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=thuth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.