Re: Boot WARN with patch "regulator: core: Link consumer with regulator driver"
On Wed, Jul 11, 2018 at 01:08:14PM +0300, Mikko Perttunen wrote: > I'm seeing the following spew during boot with Tegra210 with the patch > "regulator: core: Link consumer with regulator driver", recently applied to > linux-next: Someone reported this already, it's a limitation of the device link API really but we've not seen much of a response from them. signature.asc Description: PGP signature
Re: Boot WARN with patch "regulator: core: Link consumer with regulator driver"
On Wed, Jul 11, 2018 at 01:08:14PM +0300, Mikko Perttunen wrote: > I'm seeing the following spew during boot with Tegra210 with the patch > "regulator: core: Link consumer with regulator driver", recently applied to > linux-next: Someone reported this already, it's a limitation of the device link API really but we've not seen much of a response from them. signature.asc Description: PGP signature
Boot WARN with patch "regulator: core: Link consumer with regulator driver"
Hi, I'm seeing the following spew during boot with Tegra210 with the patch "regulator: core: Link consumer with regulator driver", recently applied to linux-next: [1.196664] [ cut here ] [1.201480] kobject: '(null)' ((ptrval)): is not initialized, yet kobject_put() is being called. [1.219186] WARNING: CPU: 2 PID: 23 at lib/kobject.c:688 kobject_put+0xa4/0xe8 [1.230026] Modules linked in: [1.241081] CPU: 2 PID: 23 Comm: kworker/2:0 Not tainted 4.18.0-rc4-next-20180711 #66 [1.258637] Hardware name: NVIDIA Jetson TX1 Developer Kit (DT) [1.258651] Workqueue: rcu_gp srcu_invoke_callbacks [1.272055] pstate: 6005 (nZCv daif -PAN -UAO) [1.272064] pc : kobject_put+0xa4/0xe8 [1.272071] lr : kobject_put+0xa4/0xe8 [1.272078] sp : 09be3cf0 [1.279387] console [ttyS0] disabled [1.283662] x29: 09be3cf0 x28: [1.283673] x27: 8000fb30aeb8 x26: 08e20690 [1.283686] x25: 093e2118 x24: 8000fff7b480 [1.314668] x23: 08135358 x22: 8000fff7b4c0 [1.325719] x21: 8000fff7b4c8 x20: 8000fafae600 [1.325727] x19: 8000faa54850 x18: 0010 [1.346022] x17: x16: [1.346022] x17: x16: [1.356805] x15: x14: 75705f7463656a62 [1.356805] x15: x14: 75705f7463656a62 [1.356813] x13: 6f6b20746579202c x12: 64657a696c616974 [1.356813] x13: 6f6b20746579202c x12: 64657a696c616974 [1.374670] x11: 696e6920746f6e20 x10: 7369203a29295f5f [1.374670] x11: 696e6920746f6e20 x10: 7369203a29295f5f [1.374678] x9 : 5f5f6c6176727470 x8 : 085c9810 [1.404186] x7 : 6220736920292874 x6 : 000d [1.414785] x5 : x4 : [1.414793] x3 : x2 : 09301010 [1.414801] x1 : a7cf02699fb4fa00 x0 : [1.424623] Call trace: [1.424632] kobject_put+0xa4/0xe8 [1.424645] __device_link_free_srcu+0x24/0x48 [1.435235] srcu_invoke_callbacks+0xf0/0x170 [1.435242] process_one_work+0x1e0/0x318 [1.435247] worker_thread+0x40/0x428 [1.435259] kthread+0x124/0x128 [1.445628] loop: module loaded [1.449599] ---[ end trace ce0b4f0828c5eeaf ]--- [1.449619] [ cut here ] After reverting the patch, the kernel boots without the warning. Thanks, Mikko
Boot WARN with patch "regulator: core: Link consumer with regulator driver"
Hi, I'm seeing the following spew during boot with Tegra210 with the patch "regulator: core: Link consumer with regulator driver", recently applied to linux-next: [1.196664] [ cut here ] [1.201480] kobject: '(null)' ((ptrval)): is not initialized, yet kobject_put() is being called. [1.219186] WARNING: CPU: 2 PID: 23 at lib/kobject.c:688 kobject_put+0xa4/0xe8 [1.230026] Modules linked in: [1.241081] CPU: 2 PID: 23 Comm: kworker/2:0 Not tainted 4.18.0-rc4-next-20180711 #66 [1.258637] Hardware name: NVIDIA Jetson TX1 Developer Kit (DT) [1.258651] Workqueue: rcu_gp srcu_invoke_callbacks [1.272055] pstate: 6005 (nZCv daif -PAN -UAO) [1.272064] pc : kobject_put+0xa4/0xe8 [1.272071] lr : kobject_put+0xa4/0xe8 [1.272078] sp : 09be3cf0 [1.279387] console [ttyS0] disabled [1.283662] x29: 09be3cf0 x28: [1.283673] x27: 8000fb30aeb8 x26: 08e20690 [1.283686] x25: 093e2118 x24: 8000fff7b480 [1.314668] x23: 08135358 x22: 8000fff7b4c0 [1.325719] x21: 8000fff7b4c8 x20: 8000fafae600 [1.325727] x19: 8000faa54850 x18: 0010 [1.346022] x17: x16: [1.346022] x17: x16: [1.356805] x15: x14: 75705f7463656a62 [1.356805] x15: x14: 75705f7463656a62 [1.356813] x13: 6f6b20746579202c x12: 64657a696c616974 [1.356813] x13: 6f6b20746579202c x12: 64657a696c616974 [1.374670] x11: 696e6920746f6e20 x10: 7369203a29295f5f [1.374670] x11: 696e6920746f6e20 x10: 7369203a29295f5f [1.374678] x9 : 5f5f6c6176727470 x8 : 085c9810 [1.404186] x7 : 6220736920292874 x6 : 000d [1.414785] x5 : x4 : [1.414793] x3 : x2 : 09301010 [1.414801] x1 : a7cf02699fb4fa00 x0 : [1.424623] Call trace: [1.424632] kobject_put+0xa4/0xe8 [1.424645] __device_link_free_srcu+0x24/0x48 [1.435235] srcu_invoke_callbacks+0xf0/0x170 [1.435242] process_one_work+0x1e0/0x318 [1.435247] worker_thread+0x40/0x428 [1.435259] kthread+0x124/0x128 [1.445628] loop: module loaded [1.449599] ---[ end trace ce0b4f0828c5eeaf ]--- [1.449619] [ cut here ] After reverting the patch, the kernel boots without the warning. Thanks, Mikko
