Re: potential deadlock in cpufreq-dt

2018-07-23 Thread Eugeniu Rosca
Hi all, [since Jiada's initial report was based on 4.14.50+] FWIW, I can consistently reproduce this lockdep issue on 4.18.0-rc6: [ 17.119559] == [ 17.119571] WARNING: possible circular locking dependency detected [ 17.119589] 4.18.0-rc6

Re: potential deadlock in cpufreq-dt

2018-07-23 Thread Eugeniu Rosca
Hi all, [since Jiada's initial report was based on 4.14.50+] FWIW, I can consistently reproduce this lockdep issue on 4.18.0-rc6: [ 17.119559] == [ 17.119571] WARNING: possible circular locking dependency detected [ 17.119589] 4.18.0-rc6

Re: potential deadlock in cpufreq-dt

2018-07-19 Thread Viresh Kumar
+ linux-pm list. On 19-07-18, 16:44, Jiada Wang wrote: > Hello all > > After enable lockdep, by poking /sys/kernel/debug/sched_features, > I triggered the following lockdep report: > > [ 34.410559] == > [ 34.416766] WARNING: possible

Re: potential deadlock in cpufreq-dt

2018-07-19 Thread Viresh Kumar
+ linux-pm list. On 19-07-18, 16:44, Jiada Wang wrote: > Hello all > > After enable lockdep, by poking /sys/kernel/debug/sched_features, > I triggered the following lockdep report: > > [ 34.410559] == > [ 34.416766] WARNING: possible

potential deadlock in cpufreq-dt

2018-07-19 Thread Jiada Wang
Hello all After enable lockdep, by poking /sys/kernel/debug/sched_features, I triggered the following lockdep report: [ 34.410559] == [ 34.416766] WARNING: possible circular locking dependency detected [ 34.422987]

potential deadlock in cpufreq-dt

2018-07-19 Thread Jiada Wang
Hello all After enable lockdep, by poking /sys/kernel/debug/sched_features, I triggered the following lockdep report: [ 34.410559] == [ 34.416766] WARNING: possible circular locking dependency detected [ 34.422987]