From: "Robert Schöne" <robert.schoene@tu-dresden.de>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Srivatsa S. Bhat" <srivatsa@mit.edu>,
Prarit Bhargava <prarit@redhat.com>,
Saravana Kannan <skannan@codeaurora.org>,
Stephen Boyd <sboyd@codeaurora.org>
Subject: Re: PROBLEM: Kernel OOPS and possible system freeze after concurrent writing to cpufreq/scaling_governor (Resend)
Date: Mon, 08 Sep 2014 14:28:42 +0200 [thread overview]
Message-ID: <1410179322.25768.7.camel@x200t> (raw)
In-Reply-To: <CAKohpo=DeQQq505U_EDsJ+5dPGPuSOypx_YbTYW5owj4FDYLpA@mail.gmail.com>
Am Montag, den 08.09.2014, 16:26 +0530 schrieb Viresh Kumar:
> Can you please try attached patch with the revert earlier suggested?
> To make it clear again, cherry-pick: 19c7630 and then apply this
> patch.
The patch works for me.
Thank you!
PS: With this patch I get an EINVAL when writing fails (instead of an
EBUSY). Is this intended?
next prev parent reply other threads:[~2014-09-08 12:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 14:53 PROBLEM: Kernel OOPS and possible system freeze after concurrent writing to cpufreq/scaling_governor Robert Schöne
2014-07-24 7:11 ` PROBLEM: Kernel OOPS and possible system freeze after concurrent writing to cpufreq/scaling_governor (Resend) Robert Schöne
2014-07-24 9:42 ` Viresh Kumar
2014-07-25 8:42 ` Robert Schöne
2014-07-25 9:03 ` Viresh Kumar
2014-07-25 13:19 ` Robert Schöne
2014-09-08 8:13 ` Robert Schöne
2014-09-08 8:16 ` Robert Schöne
2014-09-08 10:56 ` Viresh Kumar
2014-09-08 12:28 ` Robert Schöne [this message]
2014-09-08 12:57 ` Viresh Kumar
2014-09-08 21:14 ` Rafael J. Wysocki
2014-09-09 4:18 ` Viresh Kumar
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=1410179322.25768.7.camel@x200t \
--to=robert.schoene@tu-dresden.de \
--cc=linux-pm@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.org \
--cc=skannan@codeaurora.org \
--cc=srivatsa@mit.edu \
--cc=viresh.kumar@linaro.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).