Crash after 'reboot' due to 9be4fd2c7723a

[Fabio Estevam]

Hi Rafael,

On Fri, May 20, 2016 at 9:56 PM, Rafael J. Wysocki <rjw at rjwysocki.net> wrote:

> If I'm not mistaken, the patch below should allow irq_work to make forward
> progress for you, so please check if it makes any difference.
....

> Index: linux-pm/drivers/cpufreq/cpufreq_governor.c
> ===================================================================
> --- linux-pm.orig/drivers/cpufreq/cpufreq_governor.c
> +++ linux-pm/drivers/cpufreq/cpufreq_governor.c
> @@ -362,6 +362,7 @@ static struct policy_dbs_info *alloc_pol
>         mutex_init(&policy_dbs->timer_mutex);
>         atomic_set(&policy_dbs->work_count, 0);
>         init_irq_work(&policy_dbs->irq_work, dbs_irq_work);
> +       policy_dbs->irq_work.flags = IRQ_WORK_LAZY;
>         INIT_WORK(&policy_dbs->work, dbs_work_handler);
>
>         /* Set policy_dbs for all CPUs, online+offline */

Running a 4.6 kernel with this patch applied allows me to reboot the
system, thanks.

'echo performance >
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor' works fine now.