From: Borislav Petkov <bp@alien8.de>
To: Johannes Stezenbach <js@sig21.net>
Cc: Daniel Vetter <daniel@ffwll.ch>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: i915 INFO: trying to register non-static key.
Date: Mon, 5 Aug 2013 15:27:29 +0200 [thread overview]
Message-ID: <20130805132728.GC31845@pd.tnic> (raw)
In-Reply-To: <20130805132353.GA4678@sig21.net>
On Mon, Aug 05, 2013 at 03:23:53PM +0200, Johannes Stezenbach wrote:
> wrt to $Subject, I get this with 3.10.5:
>
> [ 4.342638] i915 0000:00:02.0: setting latency timer to 64
> [ 4.409045] INFO: trying to register non-static key.
> [ 4.409164] the code is fine but needs lockdep annotation.
> [ 4.409278] turning off the locking correctness validator.
> [ 4.409396] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 3.10.5 #1
> [ 4.409514] Hardware name: LENOVO 2320CTO/2320CTO, BIOS G2ET82WW (2.02 ) 09/11/2012
> [ 4.409690] 0000000000000001 ffff8802121559e0 ffffffff816b265c ffff880212155a50
> [ 4.410050] ffffffff8109ba03 ffffffff822cd1c0 0000000000000000 0000000100000006
> [ 4.410408] 0000000000000000 0000000000000000 0000000000000000 ffff8802121587a8
Looks similar to what I'm seeing. Can you cherry-pick
commit e1b4d3036c07ff137955fb1c0197ab62534f46ec
Author: Ben Widawsky <ben@bwidawsk.net>
Date: Tue Jul 30 16:27:57 2013 -0700
drm/i915: fix missed hunk after GT access breakage
ontop of 3.10-stable?
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2013-08-05 13:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 16:22 i915 INFO: trying to register non-static key Borislav Petkov
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-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-05 9:26 ` Borislav Petkov
2013-08-05 13:23 ` Johannes Stezenbach
2013-08-05 13:27 ` Borislav Petkov [this message]
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=20130805132728.GC31845@pd.tnic \
--to=bp@alien8.de \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=js@sig21.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox