From: Harvey Harrison <harvey.harrison@gmail.com>
To: airlied <airlied@linux.ie>, Andrew Morton <akpm@linux-foundation.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: DRM warnings in current -git
Date: Tue, 06 Jan 2009 23:05:24 -0800 [thread overview]
Message-ID: <1231311924.5586.1.camel@brick> (raw)
Just started seeing (many of) these in dmesg:
[ 2.843845] WARNING: at drivers/gpu/drm/drm_crtc.c:213 drm_mode_object_get+0xaa/0xb0()
[ 2.843931] Hardware name: TravelMate 2480
[ 2.843989] drm_mode_object_get called w/o mode_config lock
[ 2.844062] Modules linked in:
[ 2.844151] Pid: 1, comm: swapper Tainted: G W 2.6.28 #1
[ 2.844215] Call Trace:
[ 2.844271] [<c012f1a3>] warn_slowpath+0x73/0xd0
[ 2.844333] [<c0481fa9>] ? printk+0x18/0x1f
[ 2.844393] [<c012f1cc>] ? warn_slowpath+0x9c/0xd0
[ 2.844456] [<c04824dc>] ? schedule+0x3dc/0x9f0
[ 2.844518] [<c02505ef>] ? __udelay+0x2f/0x40
[ 2.844579] [<c0354f32>] ? bit_xfer+0x1a2/0x4d0
[ 2.844641] [<c0249b62>] ? idr_get_empty_slot+0xe2/0x270
[ 2.844705] [<c02cd93a>] drm_mode_object_get+0xaa/0xb0
[ 2.844768] [<c02cf603>] drm_mode_create+0x33/0x40
[ 2.844830] [<c02d24bf>] drm_add_edid_modes+0x3df/0x6b0
[ 2.844893] [<c0249f78>] ? idr_get_new_above+0x8/0x30
[ 2.844957] [<c02cd9da>] ? drm_mode_connector_update_edid_property+0x9a/0x190
[ 2.845043] [<c02e2bcb>] intel_ddc_get_modes+0x3b/0x60
[ 2.845106] [<c02e0d82>] intel_lvds_init+0xd2/0x2d0
[ 2.845169] [<c02e0641>] ? intel_crt_init+0xb1/0xf0
[ 2.845231] [<c02dfb95>] intel_modeset_init+0x395/0x8a0
[ 2.845295] [<c02d530b>] ? i915_driver_irq_postinstall+0xab/0xb0
[ 2.845360] [<c02d3cc1>] i915_driver_load+0x851/0x9a0
[ 2.845423] [<c02c9622>] drm_get_dev+0x262/0x400
[ 2.845484] [<c0263e7b>] ? pci_get_dev_by_id+0x3b/0x80
[ 2.845547] [<c0263d30>] ? match_pci_dev_by_id+0x0/0x70
[ 2.845609] [<c0263f98>] ? pci_get_subsys+0x58/0x70
[ 2.845672] [<c02c475b>] drm_init+0x8b/0xd0
[ 2.845732] [<c06dd743>] ? i915_init+0x0/0x48
[ 2.845792] [<c06dd789>] i915_init+0x46/0x48
[ 2.845853] [<c010111b>] _stext+0x2b/0x150
[ 2.845913] [<c01f23a4>] ? create_proc_entry+0x54/0xa0
[ 2.845977] [<c0174c24>] ? register_irq_proc+0xa4/0xc0
[ 2.846039] [<c0174ca7>] ? init_irq_proc+0x67/0x80
[ 2.846101] [<c06ba35d>] kernel_init+0x12b/0x185
[ 2.846163] [<c06ba232>] ? kernel_init+0x0/0x185
[ 2.846224] [<c0103e87>] kernel_thread_helper+0x7/0x10
[ 2.846287] ---[ end trace 755cc3f36cfb0784 ]---
next reply other threads:[~2009-01-07 7:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 7:05 Harvey Harrison [this message]
2009-01-07 9:01 ` DRM warnings in current -git Eric Anholt
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=1231311924.5586.1.camel@brick \
--to=harvey.harrison@gmail.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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