Jesse Barnes writes: > Set the IRQ handling functions in driver load so they'll just be used > directly, rather than branching over most of the code in the chipset > functions.
I'm seeing a kernel panic on my SNB i7-2600K with keithp/drm-intel-next (61e499b). I've bisected to 4697995 -- the commit mentioned in the subject. My photo of the stack trace is a bit blurry, but below is my attempted transcription of the the stack. I can't read the addresses at all; please let me know if you'd like me to obtain a better dump. Call Trace: <IRQ> queue_work_op+0x1d/0x30 queue_work+0x35/0x50 ironlake_irq_handler+0xec9/0xfa0 [i915] handle_irq_event_percpu+0x75/0x260 handle_edge_irq+0x6f/0x110 handle_irq+0x1d/0x30 do_IRQ+0x58/0xe9 common_interrupt+0x13/0x13 ... more stuff that I assume is irrelevent ... Please let me know if I can provide additional useful information. Thanks, -Ted _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx
