mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Frederic Weisbecker <frederic@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Al Viro <viro@zeniv.linux.org.uk>, Ingo Molnar <mingo@kernel.org>,
	Deepa Dinamani <deepa.kernel@gmail.com>,
	Marc Zyngier <marc.zyngier@arm.com>,
	Kees Cook <keescook@chromium.org>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@01.org, Tejun Heo <tj@kernel.org>
Subject: Re: [hrtimer_active ^W ata_port_wait_eh] INFO: trying to register non-static key.
Date: Wed, 22 Nov 2017 15:37:45 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1711221522260.1751@nanos> (raw)
In-Reply-To: <20171121130118.2ckjorhwztxa7awu@wfg-t540p.sh.intel.com>

On Tue, 21 Nov 2017, Fengguang Wu wrote:

> Hello,
> 
> FYI this happens in mainline kernel 4.14.0-12872-g020aae3.
> It looks like a new regression after 4.14.
> 
> It occurs in 126 out of 945 boots.
> 
> [   33.016892] INFO: trying to register non-static key.
> [   33.017745] the code is fine but needs lockdep annotation.
> [   33.018798] turning off the locking correctness validator.
> [   33.019713] CPU: 0 PID: 72 Comm: kworker/u4:5 Not tainted 4.14.0-12872-g020aae3 #1
> [   33.020085] scsi host0: ata_piix
> [   33.020729] Workqueue: events_unbound async_run_entry_fn
> [   33.020729] Call Trace:
> [   33.020729]  dump_stack+0x7b/0xa9:
> 						dump_stack at lib/dump_stack.c:55
> [   33.020729]  register_lock_class+0x3bb/0x583:
> 						register_lock_class at kernel/locking/lockdep.c:782
> [   33.020729]  ? hrtimer_active+0x92/0x99:
> 						hrtimer_active at kernel/time/hrtimer.c:1151
> [   33.020729]  ? hrtimer_try_to_cancel+0x23/0xb6:
> 						hrtimer_try_to_cancel at kernel/time/hrtimer.c:1016

hrtimer_active() does not contain anything which might register a lock
class. And that calltrace continues:

[   33.020729] Call Trace:
[   33.020729]  dump_stack+0x7b/0xa9
[   33.020729]  register_lock_class+0x3bb/0x583
[   33.020729]  ? hrtimer_active+0x92/0x99
[   33.020729]  ? hrtimer_try_to_cancel+0x23/0xb6
[   33.026718] scsi host1: ata_piix
[   33.027134] ata3: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc040 irq 14
[   33.027138] ata4: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc048 irq 15
[   33.028426] Error: Driver 'pata_platform' is already registered, aborting...
[   33.033725] Rounding down aligned max_sectors from 4294967295 to 4294967288
[   33.040417]  __lock_acquire+0x58/0x86c
[   33.048261] SSFDC read-only Flash Translation layer
[   33.048264] mtdoops: mtd device (mtddev=name/number) must be supplied
[   33.048276] device id = 2440
[   33.048280] device id = 2480
[   33.048283] device id = 24c0
[   33.048286] device id = 24d0
[   33.048289] device id = 25a1
[   33.048292] device id = 2670
[   33.048413] platform physmap-flash.0: failed to claim resource 0: [mem 0x08000000-0x07ffffff]
[   33.048781] Ramix PMC551 PCI Mezzanine Ram Driver. (C) 1999,2000 Nortel Networks.
[   33.048784] pmc551: not detected
[   33.060052]  lock_acquire+0x61/0x7c
[   33.060052]  ? ata_port_wait_eh+0x7b/0xe1
[   33.060052]  _raw_spin_lock_irqsave+0x47/0x81
[   33.060052]  ? ata_port_wait_eh+0x7b/0xe1
[   33.060052]  ata_port_wait_eh+0x7b/0xe1
[   33.060052]  ? print_dl_stats+0x27/0x27
[   33.060052]  ata_port_probe+0x2c/0x4f
[   33.060052]  async_port_probe+0x33/0x59
[   33.060052]  async_run_entry_fn+0x3d/0x127
[   33.060052]  process_one_work+0x244/0x529
[   33.060052]  ? process_one_work+0x216/0x529
[   33.060052]  worker_thread+0x56/0x4d9
[   33.060052]  kthread+0x115/0x152
[   33.060052]  ? process_one_work+0x529/0x529
[   33.060052]  ? __kthread_create_on_node+0x190/0x190
[   33.060052]  ret_from_fork+0x1f/0x30

And looking at the calltrace entries which have no '?' in front you should
look at ata_port_wait_eh() which makes a lot more sense.

Thanks,

	tglx

  reply	other threads:[~2017-11-22 14:38 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-21  9:05 active bugs in the first week of 4.15 merge window Fengguang Wu
2017-11-21 10:04 ` [test_abba] WARNING: possible circular locking dependency detected Fengguang Wu
2017-11-21 10:54 ` [ata_port_detach] WARNING: CPU: 0 PID: 1 at drivers/ata/libata-core.c:6613 ata_port_detach+0x9b/0x180 Fengguang Wu
2017-11-21 11:30   ` Arnd Bergmann
2017-11-21 11:07 ` [tracer_init_tracefs] watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:1] Fengguang Wu
2017-11-21 12:27   ` Fengguang Wu
2017-11-21 13:55     ` Thomas Gleixner
2017-11-21 11:10 ` [rbtree_test_init] watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper:1] Fengguang Wu
2017-11-21 21:59   ` Andrew Morton
2017-11-22  2:15     ` Fengguang Wu
2017-11-21 11:19 ` [rht_deferred_worker] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 62s! Fengguang Wu
2017-11-21 11:52   ` [test_rht_init] INFO: task swapper/0:1 blocked for more than 120 seconds Fengguang Wu
2017-11-27 21:34     ` Linus Torvalds
2017-11-27 21:32   ` [rht_deferred_worker] BUG: workqueue lockup - pool cpus=0 node=0 flags=0x0 nice=0 stuck for 62s! Linus Torvalds
2017-11-21 11:53 ` [vga_arb_device_init] WARNING: possible circular locking dependency detected Fengguang Wu
2017-11-21 16:52   ` Lukas Wunner
2017-11-22  9:07     ` Daniel Vetter
2017-11-21 17:08   ` [char-misc] " Daniel Vetter
2017-11-21 12:04 ` [migration_cpu_stop] WARNING: CPU: 0 PID: 11 at kernel/sched/core.c:1187 set_task_cpu+0x257/0x6b6 Fengguang Wu
2017-11-21 13:34   ` Peter Zijlstra
2017-11-21 13:51     ` Fengguang Wu
2017-11-21 16:13       ` Paul E. McKenney
2017-11-22 12:18         ` Fengguang Wu
2017-11-21 14:01     ` Rafael J. Wysocki
2017-11-21 12:09 ` [ata_port_probe] BUG: unable to handle kernel NULL pointer dereference at 0000000000000350 Fengguang Wu
2017-11-21 12:19   ` Fengguang Wu
2017-11-21 12:54     ` Arnd Bergmann
2017-11-21 14:57       ` Tejun Heo
2017-11-21 15:30         ` Arnd Bergmann
2017-11-21 12:33 ` [serial8250_interrupt] RIP: 0010:arch_local_irq_restore+0x2/0x8 Fengguang Wu
2017-11-21 13:31   ` Fengguang Wu
2017-11-21 14:39     ` Andy Shevchenko
2017-11-21 21:14       ` Andy Shevchenko
2017-11-22 23:36       ` Fengguang Wu
2017-11-22 23:43         ` Fengguang Wu
2017-11-21 12:41 ` [e1000_shutdown] e1000 0000:00:03.0: disabling already-disabled device Fengguang Wu
2017-11-21 22:10   ` Tushar Dave
2017-11-22 23:13     ` Fengguang Wu
2017-11-27 19:31       ` Tushar Dave
2017-12-04 11:33         ` Fengguang Wu
2017-12-05 19:19           ` Tushar Dave
2017-11-21 12:50 ` [test_cycle_work] WARNING: possible circular locking dependency detected Fengguang Wu
2017-11-21 13:01 ` [hrtimer_active] INFO: trying to register non-static key Fengguang Wu
2017-11-22 14:37   ` Thomas Gleixner [this message]
2017-11-24 12:49     ` [hrtimer_active ^W ata_port_wait_eh] " Tejun Heo
2017-11-24 13:41       ` Fengguang Wu
     [not found] ` <20171121121233.3pvkb34tci47n634@wfg-t540p.sh.intel.com>
2017-11-21 13:28   ` [RING_BUFFER_BENCHMARK] INFO: task rb_producer:73 blocked for more than 120 seconds Fengguang Wu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.20.1711221522260.1751@nanos \
    --to=tglx@linutronix.de \
    --cc=deepa.kernel@gmail.com \
    --cc=fengguang.wu@intel.com \
    --cc=frederic@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=marc.zyngier@arm.com \
    --cc=mingo@kernel.org \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®