Hi,
On Mon, Jan 29, 2007 at 01:00:39PM +0100, Michel Dänzer wrote:
> On Sun, 2007-01-28 at 22:14 -0500, Dominik Brodowski wrote:
> >
> > [...] I was able to "git bisect" it down to the drm patches which went in
> > after 2.6.19 and before 2.6.19-rc1 got released.
>
> Can you bisect it down to a single commit? If that's not possible with
> the kernel tree, you can try the drm git tree from
> git://git.freedesktop.org/git/mesa/drm .
The culprit is one of these (kernel git tree):
2228ed67223f3f22ea09df8854e6a31ea06d5619 - drm: i915 updates
a0b136bb696cfa744a79c4dbbbbd0c8f9f30fe3f - drm: i915: fix up irqflags arg
21fa60ed4eab5b3b28d05930bb086615ecc191b1 - drm: i915: Only return EBUSY...
2dbb232c4d6b6c89fc367f7566c7c87dd3b56cd7 - drm: i915: Fix 'sequence has...
376642cf2eb0f32d8502b0a2c4efd96a3f13a8b8 - drm: i915: Add SAREA fileds...
5b51694aff705c465ef5941a99073036f3e444d9 - drm: Make handling of...
2228ed72... has the issue, while
541f29aad766b6c7b911a7d900d952744369bf53 - drm: DRM_I915_VBLANK_SWAP
doesn't have it -- and all kernels in between crash during X startup, and
the last message in the X logs is
(II) I810(0): X context handle = 0x1
instead of:
(II) I810(0): X context handle = 0x1
(II) I810(0): [drm] installed DRM signal handler
(II) I810(0): [DRI] installation complete
(II) I810(0): direct rendering: Enabled
(II) I810(0): RandR enabled, ignore the following RandR disabled message.
(II) I810(0): Rotating to 0 degrees
(--) RandR disabled
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
drmOpenDevice: node name is /dev/dri/card0
As a sidenote, the last working kernel
541f29aad766b6c7b911a7d900d952744369bf53 - drm: DRM_I915_VBLANK_SWAP
returned this in dmesg when switching from console to terminal:
[ 108.905000] INFO: trying to register non-static key.
[ 108.905000] the code is fine but needs lockdep annotation.
[ 108.905000] turning off the locking correctness validator.
[ 108.905000] [<c01034ee>] dump_trace+0x64/0x1d0
[ 108.905000] [<c0103674>] show_trace_log_lvl+0x1a/0x2f
[ 108.905000] [<c0103d29>] show_trace+0x12/0x14
[ 108.905000] [<c0103dcc>] dump_stack+0x19/0x1b
[ 108.905000] [<c012df5f>] __lock_acquire+0x128/0x995
[ 108.905000] [<c012eae2>] lock_acquire+0x6e/0x8b
[ 108.905000] [<c039ced3>] _spin_lock_irqsave+0x3e/0x4e
[ 108.905000] [<c0268bbf>] i915_vblank_tasklet+0x3f/0x314
[ 108.905000] [<c0263482>] drm_unlock+0x8e/0x115
[ 108.905000] [<c0261ac0>] drm_ioctl+0x15b/0x19f
[ 108.905000] [<c0166780>] do_ioctl+0x50/0x67
[ 108.905000] [<c01669e3>] vfs_ioctl+0x24c/0x25f
[ 108.905000] [<c0166a27>] sys_ioctl+0x31/0x4a
[ 108.905000] [<c0102e4d>] sysenter_past_esp+0x56/0x8d
[ 108.905000] [<b7f1d410>] 0xb7f1d410
[ 108.905000] =======================
> > Any ideas? Any debugging you want me to do?
>
> echo 1 >/sys/module/drm/parameters/debug
>
> before switching to console might provide something interesting in the
> kernel output.
this is with 2.6.19-rc6-latest:
<lots of similar messages>
[ 1320.522000] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=00000000
[ 1320.527000] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=00000080
[ 1320.530000] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=00000000
[ 1320.538000] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=00000020
[ 1320.542000] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=00000080
[ 1320.546000] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=00000000
[ 1320.554000] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=00000020
[ 1320.557000] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=00000080
[ 1320.562000] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=00000000
[ 1320.570000] [drm:i915_driver_irq_handler] i915_driver_irq_handler
flag=00000020
[ 1320.571000] [drm:drm_ioctl] pid=6459, cmd=0x4004644d, nr=0x4d, dev 0xe200,
auth=1
[ 1320.571000] [drm:drm_ioctl] pid=6459, cmd=0x40086414, nr=0x14, dev 0xe200,
auth=1
[ 1320.571000] [drm:drm_irq_uninstall] drm_irq_uninstall: irq=10
[ 1322.474000] irq 10: nobody cared (try booting with the "irqpoll" option)
[ 1322.474000] [<c01034d9>] show_trace_log_lvl+0x1a/0x2f
[ 1322.474000] [<c0103b81>] show_trace+0x12/0x14
[ 1322.474000] [<c0103c33>] dump_stack+0x16/0x18
[ 1322.474000] [<c013fc74>] __report_bad_irq+0x39/0x81
[ 1322.474000] [<c013fe55>] note_interrupt+0x199/0x1d4
[ 1322.474000] [<c01406dd>] handle_level_irq+0xa3/0xde
[ 1322.474000] [<c0104d3a>] do_IRQ+0xc5/0xef
[ 1322.474000] =======================
[ 1322.474000] handlers:
[ 1322.474000] [<f006f4fe>] (yenta_interrupt+0x0/0xb7 [yenta_socket])
[ 1322.474000] [<f006f4fe>] (yenta_interrupt+0x0/0xb7 [yenta_socket])
[ 1322.474000] [<c02ad8b2>] (usb_hcd_irq+0x0/0x51)
[ 1322.474000] [<c02ad8b2>] (usb_hcd_irq+0x0/0x51)
[ 1322.474000] Disabling IRQ #10
Hope that helps in tracking this issue down.
Thanks,
Dominik
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
--
_______________________________________________
Dri-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-devel
