All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert Schöne" <robert.schoene@tu-dresden.de>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: PROBLEM: Kernel OOPS and possible system freeze after concurrent writing to cpufreq/scaling_governor (Resend)
Date: Fri, 25 Jul 2014 10:42:49 +0200	[thread overview]
Message-ID: <1406277769.2399.4.camel@x200t> (raw)
In-Reply-To: <CAKohpomo_Qoc-ioC-L-n6z19SLMgCfzebec7pqkq9y86gt61HA@mail.gmail.com>

The bug is still there. Here's my bash history, so that you can be sure I checked it correctly:

git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git linux-git
cd linux-git/
git show 56d07db 
git branch --contains 19c7630
git branch --contains 56d07db
git revert -n 56d07db
make oldconfig
make clean
make -j9 deb-pkg
cd ..
sudo dpkg -i linux-libc-dev_3.16.0-rc6+-2_amd64.deb
sudo dpkg -i linux-image-3.16.0-rc6+_3.16.0-rc6+-2_amd64.deb
sudo dpkg -i linux-headers-3.16.0-rc6+_3.16.0-rc6+-2_amd64.deb
sudo dpkg -i linux-firmware-image-3.16.0-rc6+_3.16.0-rc6+-2_amd64.deb
sudo update-grub2
sudo reboot

Again, I didn't get a backtrace for the error, but only this:

...
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
...


Robert


Am Donnerstag, den 24.07.2014, 15:12 +0530 schrieb Viresh Kumar:
> On 24 July 2014 12:41, Robert Schöne <robert.schoene@tu-dresden.de> wrote:
> > (Resend, because there hasn't been a reply within the last week)
> 
> How did I miss it? Yes its in my inbox. Sorry buddy..
> 
> > crash_governor.sh:
> > #!/bin/sh
> > # this is called concurrently via runme.sh
> > for I in `seq 1000`
> > do
> >         echo ondemand | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
> >         echo userspace | sudo tee /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
> > done
> >
> > runme.sh:
> > #!/bin/sh
> > # run 8 concurrent instances
> > for I in `seq 8`
> > do
> >         ./crash_governor.sh &
> > done
> >
> > Just run runme.sh and crash your system :)
> 
> Oh, yes. Quite easily I could see that happening :)
> 
> I have pushed a fix earlier for similar issues:
> 19c7630 cpufreq: serialize calls to __cpufreq_governor()
> 
> but was later reverted by Srivatsa:
> 56d07db cpufreq: Remove temporary fix for race between CPU hotplug and
> sysfs-writes
> 
> because we didn't thought about this usecase.
> 
> I propose we get that back. I have tested a revert of 56d07db on
> my setup and didn't see any crash..
> 
> Please see if that works for you as well..
> 
> --
> viresh

-- 

Dipl.-Inf. Robert Schoene
Computer Scientist - R&D Energy Efficient Computing

Technische Universitaet Dresden
Center for Information Services and High Performance Computing
Distributed and Data Intensive Computing
01062 Dresden
Tel.: +49 (351) 463-42483
Fax : +49 (351) 463-37773
E-Mail: Robert.Schoene@tu-dresden.de


  reply	other threads:[~2014-07-25  8:42 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 [this message]
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
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=1406277769.2399.4.camel@x200t \
    --to=robert.schoene@tu-dresden.de \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=srivatsa.bhat@linux.vnet.ibm.com \
    --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 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.