All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Brandewie <dirk.brandewie@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Dirk Brandewie <dirk.brandewie@gmail.com>, cpufreq@vger.kernel.org
Subject: Re: BUG in bleeding edge c560f3d
Date: Mon, 04 Feb 2013 16:05:27 -0800	[thread overview]
Message-ID: <51104CC7.8030800@gmail.com> (raw)
In-Reply-To: <3463348.tWNCISaOfi@vostro.rjw.lan>

On 02/04/2013 04:09 PM, Rafael J. Wysocki wrote:
> On Monday, February 04, 2013 02:19:22 PM Dirk Brandewie wrote:
>> Hi All,
>>
>> There is a bug in the bleeding-edge branch. Using the ondemand governor
>> and acpi_cpufreq scaling driver the system hangs while trying to reboot or
>> trying to offline a cpu manually.  The last call where I have tracing turned
>> on is __cpufreq_governor(data, CPUFREQ_GOV_STOP);
>>
>> [   38.138236] __cpufreq_remove_dev: cpufreq: __cpufreq_remove_dev:
>> unregistering CPU 1
>> [   38.146663] __cpufreq_governor: cpufreq: __cpufreq_governor for CPU 0, event 2
>> [   71.562262] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
>>
>>
>> It looks like the breakage comes from the removal of the sysfs files in the
>> incorrect order.  While rebasing my patches onto bleeding edge I found this
>> problem as well.  I have a couple of hack patches that workaround the issue
>> when using my driver if anyone would like to see them.
>
> There have been a few fixes since c560f3d, they are in linux-pm.git/linux-next
> now.  Can you please test that tree and see if the problem is still there?
>
Rebased a couple of hours ago testing now.  ATM it looks like it is related to
cpufreq_stats handling of the sysfs files


> Rafael
>
>


  reply	other threads:[~2013-02-05  0:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 22:19 BUG in bleeding edge c560f3d Dirk Brandewie
2013-02-05  0:09 ` Rafael J. Wysocki
2013-02-05  0:05   ` Dirk Brandewie [this message]
2013-02-05  2:43     ` Rafael J. Wysocki
2013-02-05  5:45       ` Viresh Kumar
2013-02-05  7:08         ` Viresh Kumar
2013-02-05 10:08           ` Rafael J. Wysocki
2013-02-05 18:45           ` Dirk Brandewie
2013-02-05 21:30             ` Rafael J. Wysocki
2013-02-06  1:34             ` Viresh Kumar
2013-02-05  2:47     ` Rafael J. Wysocki

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=51104CC7.8030800@gmail.com \
    --to=dirk.brandewie@gmail.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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.