All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: i915 INFO: trying to register non-static key.
Date: Wed, 31 Jul 2013 18:22:52 +0200	[thread overview]
Message-ID: <20130731162252.GC4724@pd.tnic> (raw)

Dudes,

has anyone already reported this (happens on Linus of today +
tip/master):

[    0.608465] Linux agpgart interface v0.103
[    0.608615] [drm] Initialized drm 1.1.0 20060810
[    0.612050] [drm] Memory usable by graphics device = 2048M
[    0.612212] i915 0000:00:02.0: setting latency timer to 64
[    0.674824] INFO: trying to register non-static key.
[    0.674904] the code is fine but needs lockdep annotation.
[    0.674983] turning off the locking correctness validator.
[    0.675063] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 3.11.0-rc3+ #1
[    0.675146] Hardware name: LENOVO 2320CTO/2320CTO, BIOS G2ET86WW (2.06 ) 11/13/2012
[    0.675244]  0000000000000002 ffff880213c9d708 ffffffff815bc9d4 0000000000000000
[    0.675539]  ffffffff82608750 ffff880213c9d808 ffffffff810aa864 ffff88021d283fc0
[    0.675828]  ffffffff82654e60 0000000000000000 ffffffff00000000 ffff880200000000
[    0.676116] Call Trace:
[    0.676194]  [<ffffffff815bc9d4>] dump_stack+0x4f/0x84
[    0.676281]  [<ffffffff810aa864>] __lock_acquire+0x1774/0x1d80
[    0.676366]  [<ffffffff81010d6f>] ? save_stack_trace+0x2f/0x50
[    0.676451]  [<ffffffff810a6d7f>] ? save_trace+0x3f/0xc0
[    0.676535]  [<ffffffff810aa36d>] ? __lock_acquire+0x127d/0x1d80
[    0.676621]  [<ffffffff810ab445>] lock_acquire+0x85/0x130
[    0.676705]  [<ffffffff810682f5>] ? flush_work+0x5/0x280
[    0.676787]  [<ffffffff8106833c>] flush_work+0x4c/0x280
[    0.676870]  [<ffffffff810682f5>] ? flush_work+0x5/0x280
[    0.676954]  [<ffffffff810abd8e>] ? mark_held_locks+0xae/0x120
[    0.677039]  [<ffffffff8106a961>] ? __cancel_work_timer+0x71/0x110
[    0.677125]  [<ffffffff8106a96d>] __cancel_work_timer+0x7d/0x110
[    0.677207]  [<ffffffff8106aa13>] cancel_delayed_work_sync+0x13/0x20
[    0.677292]  [<ffffffff813c1e15>] intel_disable_gt_powersave+0x65/0x410
[    0.677379]  [<ffffffff813c3b39>] intel_gt_sanitize+0x49/0xb0
[    0.677463]  [<ffffffff81372541>] i915_driver_load+0x611/0xe90
[    0.677550]  [<ffffffff8135acce>] drm_get_pci_dev+0x17e/0x2a0
[    0.677632]  [<ffffffff8136ddec>] i915_pci_probe+0x2c/0x70
[    0.677716]  [<ffffffff812b27fb>] local_pci_probe+0x4b/0x80
[    0.677798]  [<ffffffff812b2a61>] pci_device_probe+0x111/0x120
[    0.677885]  [<ffffffff813dc06b>] driver_probe_device+0x7b/0x240
[    0.677971]  [<ffffffff813dc2db>] __driver_attach+0xab/0xb0
[    0.678053]  [<ffffffff813dc230>] ? driver_probe_device+0x240/0x240
[    0.678138]  [<ffffffff813da0ed>] bus_for_each_dev+0x5d/0xa0
[    0.678222]  [<ffffffff813dbb2e>] driver_attach+0x1e/0x20
[    0.678304]  [<ffffffff813db64f>] bus_add_driver+0x10f/0x270
[    0.678390]  [<ffffffff813dc9ba>] driver_register+0x7a/0x170
[    0.678471]  [<ffffffff812b1874>] __pci_register_driver+0x64/0x70
[    0.678558]  [<ffffffff81b2b68a>] ? ftrace_define_fields_drm_vblank_event+0x6d/0x6d
[    0.678660]  [<ffffffff8135af05>] drm_pci_init+0x115/0x130
[    0.678740]  [<ffffffff81b2b68a>] ? ftrace_define_fields_drm_vblank_event+0x6d/0x6d
[    0.678843]  [<ffffffff81b2b6f0>] i915_init+0x66/0x68
[    0.678927]  [<ffffffff8100031a>] do_one_initcall+0x11a/0x170
[    0.679012]  [<ffffffff8106f800>] ? parse_args+0xa0/0x360
[    0.679096]  [<ffffffff81af2f92>] kernel_init_freeable+0x108/0x197
[    0.679182]  [<ffffffff81af283f>] ? do_early_param+0x8c/0x8c
[    0.679266]  [<ffffffff815b3350>] ? rest_init+0xd0/0xd0
[    0.679349]  [<ffffffff815b335e>] kernel_init+0xe/0xf0
[    0.679427]  [<ffffffff815cca5c>] ret_from_fork+0x7c/0xb0
[    0.679509]  [<ffffffff815b3350>] ? rest_init+0xd0/0xd0
[    0.680182] i915 0000:00:02.0: irq 42 for MSI/MSI-X
[    0.680278] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

             reply	other threads:[~2013-07-31 16:22 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31 16:22 Borislav Petkov [this message]
2013-07-31 16:36 ` i915 backlight Borislav Petkov
2013-07-31 21:16   ` Rafael J. Wysocki
2013-08-01  8:07     ` Borislav Petkov
2013-08-02  6:00       ` Aaron Lu
2013-08-02  6:25         ` Josep Lladonosa
2013-08-02  6:36           ` Aaron Lu
2013-08-02  7:25             ` Josep Lladonosa
2013-08-02  6:48           ` Felipe Contreras
2013-08-02 14:03             ` Rafael J. Wysocki
2013-08-02 18:58               ` Felipe Contreras
2013-08-02 20:03                 ` Josep Lladonosa
2013-08-02 20:08                   ` Felipe Contreras
2013-08-02 20:11                     ` Josep Lladonosa
2013-08-02 20:19                       ` Borislav Petkov
2013-08-02 21:25                       ` Felipe Contreras
2013-08-02 22:23                         ` Josep Lladonosa
2013-08-02 23:35                 ` Rafael J. Wysocki
2013-08-03  1:01                   ` Felipe Contreras
2013-08-02  8:16         ` Borislav Petkov
2013-08-01  1:13   ` Aaron Lu
2013-08-01  8:12     ` Borislav Petkov
2013-08-01  9:07       ` Aaron Lu
2013-08-01  9:07         ` Aaron Lu
2013-08-02  1:16         ` Aaron Lu
2013-08-02  8:34           ` Borislav Petkov
2013-08-05  7:34           ` Daniel Vetter
2013-08-04 23:06 ` i915 INFO: trying to register non-static key Daniel Vetter
2013-08-04 23:06   ` Daniel Vetter
2013-08-05  9:26   ` Borislav Petkov
2013-08-05 13:23     ` Johannes Stezenbach
2013-08-05 13:27       ` Borislav Petkov
2013-08-05 13:48         ` Johannes Stezenbach

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=20130731162252.GC4724@pd.tnic \
    --to=bp@alien8.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.