I've been seeing these warnings for a couple of weeks now. Any
pointers on how to address this would be much appreciated.
[ 57.207457] ==
[ 57.207470] WARNING: possible circular locking dependency detected
[ 57.207483] 5.11.0-rc7
=====
[ 51.013875] WARNING: possible circular locking dependency detected
[ 51.014378] 5.2.0-rc2 #1 Not tainted
[ 51.014672] --
[ 51.015182] trinity-c2/886 is trying to acquire lock:
[ 51.015593] 000
image memory: 944K
> [ 15.393319] Run /init as init process
> [ 15.477473] random: init: uninitialized urandom read (12 bytes read)
> [ 15.558322]
> [ 15.559003] ==
> [ 15.561203] WARNING: possible circular locking depende
Compiling kernel on an aarch64 server with the latest mainline (rc2) generated
this,
[ 910.263839] WARNING: possible circular locking dependency detected
[ 910.263841] 4.20.0-rc2+ #4 Tainted: GWL
[ 910.263843] --
[ 910.263844
On Wed, 7 Nov 2018, Andrew Morton wrote:
> On Wed, 7 Nov 2018 15:43:36 -0800 Andrew Morton
> wrote:
>
> > On Tue, 23 Oct 2018 08:30:04 +0800 kernel test robot
> > wrote:
> >
> > > Greetings,
> > >
> > > 0day kernel testing robot got the below dmesg and the first bad commit is
> > >
> >
On Wed, 7 Nov 2018 15:43:36 -0800 Andrew Morton
wrote:
> On Tue, 23 Oct 2018 08:30:04 +0800 kernel test robot
> wrote:
>
> > Greetings,
> >
> > 0day kernel testing robot got the below dmesg and the first bad commit is
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.gi
--+---+---+
>
> [ 29.227068] random: get_random_bytes called from key_alloc+0x2b0/0x44d
> with crng_init=1
> [ 32.046253] random: get_random_bytes called from
> __ip_select_ident+0x45/0x93 with crng_init=1
> [ 33.592007] random: get_random_bytes called from key_alloc+0x2b0/0x44d
> with crng_init=1
] [ 57.651003] synth uevent: /module/pcmcia_core: unknown uevent action
string [ 71.189062] [ 71.191953]
== [ 71.192813] WARNING:
possible circular locking dependency detected [ 71.193664]
4.12.0-10480-g3f906ba #1 Not tainted [ 71.194355
> HI:3700] [ 57.651003] synth uevent: /module/pcmcia_core: unknown uevent
> action string [ 71.189062] [ 71.191953]
> ========== [ 71.192813] WARNING:
> possible circular locking dependency detected [ 71.193664]
&g
gt; | Kernel_panic-not_syncing:Fatal_exception | 0 | 15
>> |
>> +---+---++
>>
>> [3.252870] CPU feature 'AVX registers' is not supported.
>> [3.261404]
>|
> +---+---++
>
> [3.252870] CPU feature 'AVX registers' is not supported.
> [3.261404] AVX2 or AES-NI instructions are not detected.
> [3.262708] A
On Thu, Aug 31, 2017 at 11:24:13PM +0200, Thomas Gleixner wrote:
> On Thu, 31 Aug 2017, Thomas Gleixner wrote:
> > On Thu, 31 Aug 2017, Peter Zijlstra wrote:
> >
> > > On Thu, Aug 31, 2017 at 09:55:57AM +0200, Thomas Gleixner wrote:
> > > > > Arghh!!!
> > > > >
> > > > > And allowing us to create
On Thu, 31 Aug 2017, Thomas Gleixner wrote:
> On Thu, 31 Aug 2017, Peter Zijlstra wrote:
>
> > On Thu, Aug 31, 2017 at 09:55:57AM +0200, Thomas Gleixner wrote:
> > > > Arghh!!!
> > > >
> > > > And allowing us to create events for offline CPUs (possible I think, but
> > > > maybe slightly tricky)
On Thu, 31 Aug 2017, Peter Zijlstra wrote:
> On Thu, Aug 31, 2017 at 09:55:57AM +0200, Thomas Gleixner wrote:
> > > Arghh!!!
> > >
> > > And allowing us to create events for offline CPUs (possible I think, but
> > > maybe slightly tricky) won't solve that, because we're already holding
> > > the
On Thu, Aug 31, 2017 at 09:55:57AM +0200, Thomas Gleixner wrote:
> > Arghh!!!
> >
> > And allowing us to create events for offline CPUs (possible I think, but
> > maybe slightly tricky) won't solve that, because we're already holding
> > the hotplug_lock during PREPARE.
>
> There are two ways to
On Thu, 31 Aug 2017, Peter Zijlstra wrote:
> On Thu, Aug 31, 2017 at 09:08:05AM +0200, Thomas Gleixner wrote:
> > On Wed, 30 Aug 2017, Peter Zijlstra wrote:
> > > On offline it basically does perf_event_disable() for all CPU context
> > > events, and then adds HOTPLUG_OFFSET (-32) to arrive at: OFF
On Thu, Aug 31, 2017 at 09:08:05AM +0200, Thomas Gleixner wrote:
> On Wed, 30 Aug 2017, Peter Zijlstra wrote:
> > On offline it basically does perf_event_disable() for all CPU context
> > events, and then adds HOTPLUG_OFFSET (-32) to arrive at: OFF +
> > HOTPLUG_OFFSET = -33.
> >
> > That's smalle
On Wed, 30 Aug 2017, Peter Zijlstra wrote:
> On offline it basically does perf_event_disable() for all CPU context
> events, and then adds HOTPLUG_OFFSET (-32) to arrive at: OFF +
> HOTPLUG_OFFSET = -33.
>
> That's smaller than ERROR and thus perf_event_enable() no-ops on events
> for offline CPUs
On Tue, Aug 29, 2017 at 10:10:37PM +0200, Thomas Gleixner wrote:
> On Tue, 29 Aug 2017, Peter Zijlstra wrote:
> > So I have a patch _somewhere_ that preserves the event<->cpu relation
> > across hotplug and disable/enable would be sufficient. If you want I can
> > try and dig that out and make it w
On Tue, 29 Aug 2017, Peter Zijlstra wrote:
> On Tue, Aug 29, 2017 at 07:40:44PM +0200, Thomas Gleixner wrote:
>
> > One solution I'm looking into right now is to reverse the lock order and
> > actually make the hotplug code do:
> >
> > watchdog_lock();
> > cpu_write_lock();
> >
> >
On Tue, Aug 29, 2017 at 07:40:44PM +0200, Thomas Gleixner wrote:
> One solution I'm looking into right now is to reverse the lock order and
> actually make the hotplug code do:
>
>watchdog_lock();
>cpu_write_lock();
>
>
>cpu_write_unlock();
>watchdog_u
On Fri, Aug 25, 2017 at 04:47:55PM +0200, Sebastian Andrzej Siewior wrote:
> On 2017-08-25 12:03:04 [+0200], Borislav Petkov wrote:
> > ==
> > WARNING: possible circular locking dependency detected
> > 4.13.
On Mon, 28 Aug 2017, Peter Zijlstra wrote:
> What's worse, there's also:
>
> cpus_write_lock()
> ...
> takedown_cpu()
> smpboot_park_threads()
> smpboot_park_thread()
> kthread_park()
> ->park() := watchdog_disable()
> watchdog_nmi_di
t; tglx says I have something for ya :-)
> > >
> > > ==================
> > > WARNING: possible circular locking dependency detected
> > > 4.13.0-rc6+ #1 Not tainted
> > > --
> >
On Mon, Aug 28, 2017 at 04:58:08PM +0200, Peter Zijlstra wrote:
> On Fri, Aug 25, 2017 at 12:03:04PM +0200, Borislav Petkov wrote:
> > Hey,
> >
> > tglx says I have something for ya :-)
> >
> > ==========
>
On Fri, Aug 25, 2017 at 12:03:04PM +0200, Borislav Petkov wrote:
> Hey,
>
> tglx says I have something for ya :-)
>
> ==========
> WARNING: possible circular locking dependency detected
> 4.13.
On Fri, Aug 25, 2017 at 04:47:55PM +0200, Sebastian Andrzej Siewior wrote:
> On 2017-08-25 12:03:04 [+0200], Borislav Petkov wrote:
> | ==
> | WARNING: possible circular locking dependency detected
> | 4.13.0-rc6-00758-gd80d4177391
On Fri, Aug 25, 2017 at 04:47:55PM +0200, Sebastian Andrzej Siewior wrote:
> On 2017-08-25 12:03:04 [+0200], Borislav Petkov wrote:
> > ==
> > WARNING: possible circular locking dependency detected
> > 4.13.
On 2017-08-25 12:03:04 [+0200], Borislav Petkov wrote:
> Hey,
Hi Borislav,
> tglx says I have something for ya :-)
:)
> ==
> WARNING: possible circular locking dependency detected
> 4.13.0-rc6+
On Sat, 26 Aug 2017, Byungchul Park wrote:
> On Fri, Aug 25, 2017 at 11:47 PM, Sebastian Andrzej Siewior
> wrote:
> > We hold the sparse_irq_lock lock while waiting for the completion in the
> > CPU-down case and in the CPU-up case we acquire the sparse_irq_lock lock
> > while the other CPU is wai
On Fri, Aug 25, 2017 at 11:47 PM, Sebastian Andrzej Siewior
wrote:
> On 2017-08-25 12:03:04 [+0200], Borislav Petkov wrote:
>> ==
>> WARNING: possible circular locking dependency detected
>> 4.13.
On 2017-08-25 12:03:04 [+0200], Borislav Petkov wrote:
> ==
> WARNING: possible circular locking dependency detected
> 4.13.0-rc6+ #1 Not tainted
> --
While looking at this, I s
.config
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86 4.13.0-rc6 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="e
Hey,
tglx says I have something for ya :-)
==
WARNING: possible circular locking dependency detected
4.13.0-rc6+ #1 Not tainted
--
watchdog/3/27 is trying to acquire lock
4adfdd06f1-r0-hikey-20170515030615-10.uefi.img
>> Rootfs:
>>- rpb-console-image-hikey-20170515030615-10.rootfs.img.gz
>>
>> steps to reproduce:
>> --
>> - sudo fastboot flash boot
>> boot-0.0+AUTOINC+06e4def583-4adfdd06f1-r0-hikey-2017
On 18-05-17, 16:08, Viresh Kumar wrote:
> On 18 May 2017 at 16:05, Naresh Kamboju wrote:
> > Boot HiKey board.
> >
> > [ 76.039134] ==
> > [ 76.045319] WARNING: possible circular locking dependency detected
> &g
.uefi.img
> - sudo fastboot flash system
> rpb-console-image-hikey-20170515030615-10.rootfs.img
>
> Boot HiKey board.
>
> [ 76.039134] ======
> [ 76.045319] WARNING: p
-0.0+AUTOINC+06e4def583-4adfdd06f1-r0-hikey-20170515030615-10.uefi.img
- sudo fastboot flash system
rpb-console-image-hikey-20170515030615-10.rootfs.img
Boot HiKey board.
[ 76.039134] ==
[ 76.045319] WARNING: possible circular locking
38 matches
Mail list logo