linux-kernel - Re: [REGRESSION] opp: Allow dev_pm_opp_get_opp_table() to return -EPROBE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20201106041441.uuz5vrtqeyn6ijdv@vireshk-i7>
Date:   Fri, 6 Nov 2020 09:44:41 +0530
From:   Viresh Kumar <viresh.kumar@...aro.org>
To:     Andreas Kemnade <andreas@...nade.info>
Cc:     stephan@...hold.net, rjw@...ysocki.net, khilman@...nel.org,
        ulf.hansson@...aro.org, vireshk@...nel.org, nm@...com,
        sboyd@...nel.org, linux-pm@...r.kernel.org,
        linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, letux-kernel@...nphoenux.org
Subject: Re: [REGRESSION] opp: Allow dev_pm_opp_get_opp_table() to return
 -EPROBE_DEFER

On 06-11-20, 00:10, Andreas Kemnade wrote:
> Hi,
> 
> On the GTA04 (DM3730, devicetree omap3-gta04*) I get my console flooded
> up with the following:
> [   24.517211] cpu cpu0: multiple regulators are not supported
> [   24.523040] cpufreq: __target_index: Failed to change cpu frequency: -22
> [   24.537231] ------------[ cut here ]------------
> [   24.542083] WARNING: CPU: 0 PID: 5 at drivers/opp/core.c:678 dev_pm_opp_set_rate+0x23c/0x494
> [   24.551086] Modules linked in: usb_f_ecm g_ether usb_f_rndis u_ether libcomposite configfs phy_twl4030_usb omap2430 musb_hdrc overlay
> [   24.563842] CPU: 0 PID: 5 Comm: kworker/0:0 Tainted: G        W         5.9.0-rc1-00008-g629238068eb9 #14
> [   24.573852] Hardware name: Generic OMAP36xx (Flattened Device Tree)
> [   24.580413] Workqueue: events dbs_work_handler
> [   24.585083] [<c010e6b4>] (unwind_backtrace) from [<c010a194>] (show_stack+0x10/0x14)
> [   24.593200] [<c010a194>] (show_stack) from [<c0464ad0>] (dump_stack+0x8c/0xac)
> [   24.600769] [<c0464ad0>] (dump_stack) from [<c01276a8>] (__warn+0xcc/0xe4)
> [   24.608001] [<c01276a8>] (__warn) from [<c0127a3c>] (warn_slowpath_fmt+0x74/0xa0)
> [   24.615844] [<c0127a3c>] (warn_slowpath_fmt) from [<c06364ac>] (dev_pm_opp_set_rate+0x23c/0x494)
> [   24.625061] [<c06364ac>] (dev_pm_opp_set_rate) from [<c063ec08>] (set_target+0x2c/0x4c)
> [   24.633453] [<c063ec08>] (set_target) from [<c063a950>] (__cpufreq_driver_target+0x190/0x22c)
> [   24.642395] [<c063a950>] (__cpufreq_driver_target) from [<c063d4e0>] (od_dbs_update+0xcc/0x158)
> [   24.651489] [<c063d4e0>] (od_dbs_update) from [<c063e090>] (dbs_work_handler+0x2c/0x54)
> [   24.659881] [<c063e090>] (dbs_work_handler) from [<c013f71c>] (process_one_work+0x210/0x358)
> [   24.668731] [<c013f71c>] (process_one_work) from [<c0140014>] (worker_thread+0x22c/0x2d0)
> [   24.677307] [<c0140014>] (worker_thread) from [<c0144eac>] (kthread+0x140/0x14c)
> [   24.685058] [<c0144eac>] (kthread) from [<c0100148>] (ret_from_fork+0x14/0x2c)
> [   24.692626] Exception stack(0xde4b7fb0 to 0xde4b7ff8)
> [   24.697906] 7fa0:                                     00000000 00000000 00000000 00000000
> [   24.706481] 7fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> [   24.715057] 7fe0: 00000000 00000000 00000000 00000000 00000013 00000000
> [   24.722198] ---[ end trace 038b3f231fae6f81 ]---
> 
> endlessly after the $subject commit. Any hints?

The fix for this has been in linux-next for a couple of days and it
made it to linus/master yesterday.

47efcbcb340c opp: Fix early exit from dev_pm_opp_register_set_opp_helper()

-- 
viresh