From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752615AbcDKCQr (ORCPT ); Sun, 10 Apr 2016 22:16:47 -0400 Received: from mailout4.samsung.com ([203.254.224.34]:55644 "EHLO mailout4.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752026AbcDKCQo convert rfc822-to-8bit (ORCPT ); Sun, 10 Apr 2016 22:16:44 -0400 X-AuditID: cbfee68e-f79d96d0000012b1-71-570b08f3003b MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 8BIT Message-id: <570B08F2.50302@samsung.com> Date: Mon, 11 Apr 2016 11:16:18 +0900 From: Chanwoo Choi User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 To: Anand Moon Cc: "myungjoo.ham@samsung.com" , Kyungmin Park , =?UTF-8?B?S3J6eXN6dG9mIEtvesWCb3dza2k=?= , Kukjin Kim , Sylwester Nawrocki , Tomasz Figa , "Rafael J. Wysocki" , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , Russell King , Markus Reichl , Tobias Jakobi , "inki.dae@samsung.com" , Linux Kernel , Linux PM list , "linux-samsung-soc@vger.kernel.org" , linux-arm-kernel , devicetree Subject: Re: [PATCH 0/7] PM / devfreq: Add NoCP devfreq-event and support busfreq on exyno5422-odroidxu3 References: <1460091646-28701-1-git-send-email-cw00.choi@samsung.com> In-reply-to: X-Brightmail-Tracker: H4sIAAAAAAAAA02Sa0iTYRiGe/cd9m0pvC6nr+sEg1KMLOestwPmz0+kAxoUGumyD610jk2j orJabWRlVtJk2BGrbVnSkkrTsjVL8pC2NM8VmizdD2MVK83aoch/N8/hvp4bHoYQVVISZpey gFMrFblSWkhWhcpVS93M7C3L3dol+Iq9ncJnXdco3D5mBvj8+1ISjztj8dnhcQK3HXPxsXW4 m8KOugoau8/YAS5//YSH797r4+N+RzD+bPcAfONdJw/3HzXRuNRwh8StLW8ofKLBzsfPXXoK 625PUNhSNwUSw9iqy1WAPa49TbOOkjM8tm+giK01DvJZ862vNGu1nKTZ+5VF7PQLPlvTpSfZ khoLYN3WBZuC0oRrd3K5u/Zy6mUJmcKc0Y9aQlURvU83eIl3BDyUFgMBg6AcXT86QQR0GOoY qqaLgZARQRNAJ08biH9DTY1XeYGGEaC3n3poXyMYhiDPhSGyGDAMASNRWVmer0zAUNT+fZIO 6CXo5rVxIrD7AaDf9if8wG4Uanv2k/RpEi5Cg9o+v6ZhNHrq9PkzjBhuRaea9/vKoXCxF2ui fD4EfMVHBuc3P2AO3I3Mtk4qAHAAdHEkYCSAqWjSM+QnIzjBoG9jrSBAg+j7BZv/agTnI2vj 35QR6JmphywF4cYZ2Yz/sxlnZDPOyHYVkBYg5lRZKs2ObLUsRqPI0xQqs2Oy8vOswPs8LdOj JY9Ab+MaG4AMkAYFJ3YLt4goxV7N/jwbiPcedI6QiLPyvf+mLMiIjVshw/Hy+DjZylUrpOHB mZIfqSKYrSjg9nCcilNnqAtzOY0N8BiB5AhI6R390qrX6tIHUpIPqj3KjvL129uS0hzpqzsS ymm8oX7z4Y1JSDpi+fhyoeGWTlTh3rcHMnPxIfXj1BTDeRBUa4/6lfCgkr7UNd/SJNtg1Lui zPbmlRGx9fedkm10TLMh0tWwDsaFZAoOFClqqrPK5KrcebyM5NXijcunZklJTY4iNppQaxR/ AAzv9XA3AwAA X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrOKsWRmVeSWpSXmKPExsVy+t9jQd3PHNzhBs8+KlnMP3KO1aL/zUJW i3OvVjJaTLo/gcXi9QtDi/7Hr5ktzja9YbfY9Pgaq8XlXXPYLD73HmG0mHF+H5PFuo232C1u X+a1eHnkB6PF0usXmSxuN65gs5gwfS2LxZnTl1gtWvceYbc4/Kad1aJt9QdWi1W7/jA6iHms mbeG0aOluYfN43JfL5PHrTv1Hjtn3WX3WLn8C5vHplWdbB6bl9R7/DvG7rHlajuLR9+WVYwe nzfJBfBENTDaZKQmpqQWKaTmJeenZOal2yp5B8c7x5uaGRjqGlpamCsp5CXmptoqufgE6Lpl 5gA9rKRQlphTChQKSCwuVtK3wzQhNMRN1wKmMULXNyQIrsfIAA0krGHM6Nz4gLngn2ZF9+KL zA2MM5W6GDk5JARMJI4eWMAEYYtJXLi3nq2LkYtDSGAWo8SVpzfYQBK8AoISPybfY+li5OBg FpCXOHIpG8JUl5gyJRei/AGjxP8j+9ghyjUkzh78xQJiswioStxtvgVmswloSex/ATKSg0NU IEKi+0QlSFhEQA1o0wpWkDnMAqfYJaa/+Aq2VlggS2LloYusEAsuM0pMewIxiFMgWOL3j3vM ExiBrkQ4bxbCebMQzlvAyLyKUSK1ILmgOCk91ygvtVyvODG3uDQvXS85P3cTIzhRPZPewXh4 l/shRgEORiUe3heXucKFWBPLiitzDzFKcDArifD2snGHC/GmJFZWpRblxxeV5qQWH2I0Bfpv IrOUaHI+MInmlcQbGpuYGVkamRtaGBmbK4nzPv6/LkxIID2xJDU7NbUgtQimj4mDU6qB0fHG z9CcoJojjSbLPcIqbqvIJ6+X39IudKru64aNX3e+38p6zXPJtL//TiRtur6S60HuxKlRkpG3 2aMT10qcqJA5fKx7y4Zjx6LX+O1t+pB4tjpgqbPPfmG9woMx19pdXhl/NXsdsra48cu25vty Uqlqqfy/5866em+eRNTL0+ymW+RMlszkm6TEUpyRaKjFXFScCADT+VPJagMAAA== DLP-Filter: Pass X-MTR: 20000000000000000@CPGS X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Anand, On 2016년 04월 09일 03:24, Chanwoo Choi wrote: > Hi Anand, > > On Sat, Apr 9, 2016 at 3:11 AM, Anand Moon wrote: >> Hi Chanwoo, >> [snip] >>> >> >> I am observing following deadlock. Both on Odroid U3 and Odroid XU4. > > Thanks for your test. I'll test it again and fix it. This possible recursive locking is fixed with following diff: Thanks for your report. I'll fix it on next patchset[1] (v9). [1] https://lkml.org/lkml/2016/4/8/14 diff --git a/drivers/devfreq/governor_passive.c b/drivers/devfreq/governor_passive.c index 28a9ae32d330..a4b0b02ee797 100644 --- a/drivers/devfreq/governor_passive.c +++ b/drivers/devfreq/governor_passive.c @@ -102,7 +102,7 @@ static int update_devfreq_passive(struct devfreq *devfreq, unsigned long freq) if (!devfreq->governor) return -EINVAL; - mutex_lock(&devfreq->lock); + mutex_lock_nested(&devfreq->lock, SINGLE_DEPTH_NESTING); ret = devfreq->governor->get_target_freq(devfreq, &freq); if (ret < 0) Best Regards, Chanwoo Choi > >> >> [ 7.718372] [ INFO: possible recursive locking detected ] >> [ 7.723747] 4.6.0-rc2-xu4ml #4 Not tainted >> [ 7.727817] --------------------------------------------- >> [ 7.733190] kworker/u16:1/136 is trying to acquire lock: >> [ 7.738476] (&devfreq->lock){+.+.+.}, at: [] >> update_devfreq_passive+0x2c/0x88 >> [ 7.746534] >> [ 7.746534] but task is already holding lock: >> [ 7.752339] (&devfreq->lock){+.+.+.}, at: [] >> devfreq_monitor+0x1c/0x78 >> [ 7.759791] >> [ 7.759791] other info that might help us debug this: >> [ 7.766291] Possible unsafe locking scenario: >> [ 7.766291] >> [ 7.766307] usb 5-1: new high-speed USB device number 2 using xhci-hcd >> [ 7.778682] CPU0 >> [ 7.781107] ---- >> [ 7.783533] lock(&devfreq->lock); >> [ 7.786999] lock(&devfreq->lock); >> [ 7.790467] >> [ 7.790467] *** DEADLOCK *** >> [ 7.790467] >> [ 7.796359] May be due to missing lock nesting notation >> [ 7.796359] >> [ 7.803120] 4 locks held by kworker/u16:1/136: >> [ 7.807537] #0: ("%s"("devfreq_wq")){.+.+..}, at: [] >> process_one_work+0x13c/0x454 >> [ 7.816029] #1: ((&(&devfreq->work)->work)){+.+...}, at: >> [] process_one_work+0x13c/0x454 >> [ 7.825128] #2: (&devfreq->lock){+.+.+.}, at: [] >> devfreq_monitor+0x1c/0x78 >> [ 7.833013] #3: (&nh->srcu){......}, at: [] >> __srcu_notifier_call_chain+0x54/0xe0 >> [ 7.841419] >> [ 7.841419] stack backtrace: >> [ 7.845758] CPU: 1 PID: 136 Comm: kworker/u16:1 Not tainted >> 4.6.0-rc2-xu4ml #4 >> [ 7.852946] Hardware name: SAMSUNG EXYNOS (Flattened Device Tree) >> [ 7.859017] Workqueue: devfreq_wq devfreq_monitor >> [ 7.863717] [] (unwind_backtrace) from [] >> (show_stack+0x10/0x14) >> [ 7.871417] [] (show_stack) from [] >> (dump_stack+0xa4/0xd0) >> [ 7.878613] [] (dump_stack) from [] >> (__lock_acquire+0x1ce8/0x207c) >> [ 7.886492] [] (__lock_acquire) from [] >> (lock_acquire+0x90/0xd4) >> [ 7.892726] usb 5-1: New USB device found, idVendor=0bda, idProduct=8153 >> [ 7.892737] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6 >> [ 7.892745] usb 5-1: Product: USB 10/100/1000 LAN >> [ 7.892753] usb 5-1: Manufacturer: Realtek >> [ 7.892761] usb 5-1: SerialNumber: 000001000000 >> [ 7.921248] [] (lock_acquire) from [] >> (mutex_lock_nested+0x78/0x4ec) >> [ 7.929301] [] (mutex_lock_nested) from [] >> (update_devfreq_passive+0x2c/0x88) >> [ 7.938138] [] (update_devfreq_passive) from [] >> (devfreq_passive_notifier_call+0x48/0x50) >> [ 7.948016] [] (devfreq_passive_notifier_call) from >> [] (notifier_call_chain+0x54/0xa4) >> [ 7.957633] [] (notifier_call_chain) from [] >> (__srcu_notifier_call_chain+0x98/0xe0) >> [ 7.966991] [] (__srcu_notifier_call_chain) from >> [] (srcu_notifier_call_chain+0x18/0x20) >> [ 7.976783] [] (srcu_notifier_call_chain) from >> [] (update_devfreq+0xe4/0x18c) >> [ 7.985622] [] (update_devfreq) from [] >> (devfreq_monitor+0x24/0x78) >> [ 7.993595] [] (devfreq_monitor) from [] >> (process_one_work+0x1ac/0x454) >> [ 8.001913] [] (process_one_work) from [] >> (worker_thread+0x50/0x508) >> [ 8.009976] [] (worker_thread) from [] >> (kthread+0xf8/0x110) >> [ 8.017254] [] (kthread) from [] >> (ret_from_fork+0x14/0x24) >> >> Best Regards >> -Anand Moon >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html > -- > To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > >