From: Tony Lindgren <tony@atomide.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: linux-omap@vger.kernel.org,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
dri-devel@lists.freedesktop.org
Subject: drm_modeset_lock oops in next
Date: Fri, 7 Apr 2017 08:56:50 -0700 [thread overview]
Message-ID: <20170407155649.GI13234@atomide.com> (raw)
Hi,
Looks like current next now oopses at least for omapdrm
when starting X. Reverting commit d20afeb3e2f9 ("Merge
remote-tracking branch 'drm-misc/for-linux-next'") makes
things work again.
Any ideas what might be causing the oops below?
Regards,
Tony
8< --------------------------
Internal error: Oops: 5 [#1] SMP ARM
...
CPU: 1 PID: 1637 Comm: X Not tainted 4.11.0-rc5-next-20170407+ #488
Hardware name: Generic OMAP4 (Flattened Device Tree)
task: ec873180 task.stack: ec8b8000
PC is at __ww_mutex_lock.constprop.0+0x34/0x1054
LR is at lock_is_held_type+0x60/0xa8
pc : [<c0833098>] lr : [<c0199abc>] psr: a0000013
sp : ec8b9d18 ip : 00000002 fp : edb2a800
r10: ec8b9dc0 r9 : edb2c800 r8 : ec88c400
r7 : ec8b9e1c r6 : bf70f648 r5 : ec8b9dd8 r4 : 00000010
r3 : 00400100 r2 : ec8b9cf8 r1 : ffffffff r0 : 00000000
Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment none
Control: 10c5387d Table: ac85c04a DAC: 00000051
Process X (pid: 1637, stack limit = 0xec8b8218)
...
[<c0833098>] (__ww_mutex_lock.constprop.0) from [<c0834150>] (ww_mutex_lock+0x44/0x54)
[<c0834150>] (ww_mutex_lock) from [<bf70f648>] (drm_modeset_lock+0x60/0x110 [drm])
[<bf70f648>] (drm_modeset_lock [drm]) from [<bf718740>] (drm_mode_cursor_common+0x98/0x1f0 [drm])
[<bf718740>] (drm_mode_cursor_common [drm]) from [<bf718f1c>] (drm_mode_cursor_ioctl+0x58/0x60 [drm])
[<bf718f1c>] (drm_mode_cursor_ioctl [drm]) from [<bf6fe5c8>] (drm_ioctl+0x1d4/0x404 [drm])
[<bf6fe5c8>] (drm_ioctl [drm]) from [<c02d3884>] (do_vfs_ioctl+0x90/0xa54)
[<c02d3884>] (do_vfs_ioctl) from [<c02d42b4>] (SyS_ioctl+0x6c/0x7c)
[<c02d42b4>] (SyS_ioctl) from [<c01077c0>] (ret_fast_syscall+0x0/0x1c)
Code: e58d3018 ebe4cd4e e35a0000 0a000002 (e5943044)
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2017-04-07 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 15:56 Tony Lindgren [this message]
2017-04-08 8:52 ` drm_modeset_lock oops in next Maarten Lankhorst
2017-04-08 16:46 ` Tony Lindgren
2017-04-10 7:02 ` Maarten Lankhorst
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=20170407155649.GI13234@atomide.com \
--to=tony@atomide.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-omap@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=tomi.valkeinen@ti.com \
/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.