Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
On Wed, 18 Mar 2015, Steven Rostedt wrote: > On Tue, 17 Mar 2015 08:53:21 +0100 > Daniel Vetter wrote: > >> Can you please cherry pick 42a7b088127f (\"drm/i915: Make sure the primary >> plane is enabled before reading out the fb state\") from -next to 4.0-rc >> to test whether this is indeed the difference in ducttape? > > I cherry-picked that patch and the warning does go away. Cherry-picked to drm-intel-fixes to queue it to v4.0-rc. Thanks for the report and testing. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
On Wed, 18 Mar 2015, Steven Rostedt rost...@goodmis.org wrote: On Tue, 17 Mar 2015 08:53:21 +0100 Daniel Vetter dan...@ffwll.ch wrote: Can you please cherry pick 42a7b088127f (\drm/i915: Make sure the primary plane is enabled before reading out the fb state\) from -next to 4.0-rc to test whether this is indeed the difference in ducttape? I cherry-picked that patch and the warning does go away. Cherry-picked to drm-intel-fixes to queue it to v4.0-rc. Thanks for the report and testing. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
On Tue, 17 Mar 2015 08:53:21 +0100 Daniel Vetter wrote: > Can you please cherry pick 42a7b088127f (\"drm/i915: Make sure the primary > plane is enabled before reading out the fb state\") from -next to 4.0-rc > to test whether this is indeed the difference in ducttape? I cherry-picked that patch and the warning does go away. Thanks, -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
On Mon, Mar 16, 2015 at 01:21:58PM -0400, Steven Rostedt wrote: > On Mon, 16 Mar 2015 17:43:33 +0100 > Daniel Vetter wrote: > > > > Is linux-next also affected or is this just a case of i915 maintainers > > having failed to push the right patch to -fixes? > > I just confirmed, linux-next boots without the warning. > > > > > I'll try to figure out what fell apart here meanwhile. To help out, can > > you please boot with drm.debug=0xe and grab the full dmesg for booting? > > Looks like it falls over in the initial fbcon modeset, which is indeed > > strange ... > > Here they are: > > http://rostedt.homelinux.com/private/dmesg-next > > http://rostedt.homelinux.com/private/dmesg-4.0 The unnerving part is that I didn't find any patch not anything else that might fix this frontbuffer_bits leak. I also couldn't spot the bug. The real reason why -next works and 4.0 doesn't seems to be that 4.0 reconstructs a bogus initial framebuffer and then falls over when cleaning that up. -next just doesn't reconstruct that framebuffer and hence also can't fall over on cleanup. Can you please cherry pick 42a7b088127f (\"drm/i915: Make sure the primary plane is enabled before reading out the fb state\") from -next to 4.0-rc to test whether this is indeed the difference in ducttape? Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
On Mon, Mar 16, 2015 at 01:21:58PM -0400, Steven Rostedt wrote: On Mon, 16 Mar 2015 17:43:33 +0100 Daniel Vetter dan...@ffwll.ch wrote: Is linux-next also affected or is this just a case of i915 maintainers having failed to push the right patch to -fixes? I just confirmed, linux-next boots without the warning. I'll try to figure out what fell apart here meanwhile. To help out, can you please boot with drm.debug=0xe and grab the full dmesg for booting? Looks like it falls over in the initial fbcon modeset, which is indeed strange ... Here they are: http://rostedt.homelinux.com/private/dmesg-next http://rostedt.homelinux.com/private/dmesg-4.0 The unnerving part is that I didn't find any patch not anything else that might fix this frontbuffer_bits leak. I also couldn't spot the bug. The real reason why -next works and 4.0 doesn't seems to be that 4.0 reconstructs a bogus initial framebuffer and then falls over when cleaning that up. -next just doesn't reconstruct that framebuffer and hence also can't fall over on cleanup. Can you please cherry pick 42a7b088127f (\drm/i915: Make sure the primary plane is enabled before reading out the fb state\) from -next to 4.0-rc to test whether this is indeed the difference in ducttape? Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
On Tue, 17 Mar 2015 08:53:21 +0100 Daniel Vetter dan...@ffwll.ch wrote: Can you please cherry pick 42a7b088127f (\drm/i915: Make sure the primary plane is enabled before reading out the fb state\) from -next to 4.0-rc to test whether this is indeed the difference in ducttape? I cherry-picked that patch and the warning does go away. Thanks, -- Steve -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
On Mon, 16 Mar 2015 17:43:33 +0100 Daniel Vetter wrote: > Is linux-next also affected or is this just a case of i915 maintainers > having failed to push the right patch to -fixes? I just confirmed, linux-next boots without the warning. > > I'll try to figure out what fell apart here meanwhile. To help out, can > you please boot with drm.debug=0xe and grab the full dmesg for booting? > Looks like it falls over in the initial fbcon modeset, which is indeed > strange ... Here they are: http://rostedt.homelinux.com/private/dmesg-next http://rostedt.homelinux.com/private/dmesg-4.0 -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
On Mon, Mar 16, 2015 at 11:45:03AM -0400, Steven Rostedt wrote: > > Any movement on this? I still get this warning on 4.0-rc4. Sorry for not looking into this, I've thought we've addressed this already and the fix is simply still in-flight to 4.0-rc. Seems it's not :( Is linux-next also affected or is this just a case of i915 maintainers having failed to push the right patch to -fixes? I'll try to figure out what fell apart here meanwhile. To help out, can you please boot with drm.debug=0xe and grab the full dmesg for booting? Looks like it falls over in the initial fbcon modeset, which is indeed strange ... Thanks, Daniel > > -- Steve > > > On Thu, 5 Mar 2015 09:27:28 -0500 > Steven Rostedt wrote: > > > On Mon, Feb 23, 2015 at 11:12:39PM +0300, Andrey Skvortsov wrote: > > > > > > This warning is moved from linux-next to v4.0-rc1 now. After system boot > > > is just a black screen. > > > I ssh'ed into the machine and saved the log. I attached updated dmesg.log > > > with drm.debug=6. Hopefully it helps. > > > If you need any other debug information, traces, core dump or something > > > else. Feel free to ask. > > > > > > > I'm hitting this exact same warning on one of my test boxes. > > > > [drm] Initialized i915 1.6.0 20150130 for :00:02.0 on minor 0 > > [ cut here ] > > WARNING: CPU: 7 PID: 116 at > > /home/rostedt/work/git/linux-trace.git/drivers/gpu/drm/i915/i915_gem.c:4525 > > i915_gem_free_object+0x2de/0x300 [i915]() > > WARN_ON(obj->frontbuffer_bits) > > Modules linked in: i915 i2c_algo_bit e1000e drm_kms_helper ptp > > crc32c_intel drm pps_core i2c_core video sunrpc > > CPU: 7 PID: 116 Comm: kworker/u16:5 Not tainted 4.0.0-rc1-test #270 > > Hardware name: Hewlett-Packard HP Compaq Pro 6300 SFF/339A, BIOS K01 > > v02.05 05/07/2012 > > Workqueue: events_unbound async_run_entry_fn > > 11ad 88001fa837e8 816cc3cc d4d4 > > 88001fa83838 88001fa83828 8107b977 8800d4fd > > 88001f2b5800 8800d4f40040 8800d4f4 8800d4f400c0 > > Call Trace: > > [] dump_stack+0x4c/0x6e > > [] warn_slowpath_common+0x97/0xe0 > > [] warn_slowpath_fmt+0x46/0x50 > > [] i915_gem_free_object+0x2de/0x300 [i915] > > [] drm_gem_object_free+0x27/0x30 [drm] > > [] intel_user_framebuffer_destroy+0x75/0xa0 [i915] > > [] drm_framebuffer_free+0x5b/0x70 [drm] > > [] drm_framebuffer_unreference+0x39/0x70 [drm] > > [] drm_mode_set_config_internal+0xcc/0x110 [drm] > > [] restore_fbdev_mode+0xc8/0xf0 [drm_kms_helper] > > [] drm_fb_helper_restore_fbdev_mode_unlocked+0x30/0x80 > > [drm_kms_helper] > > [] drm_fb_helper_set_par+0x24/0x50 [drm_kms_helper] > > [] intel_fbdev_set_par+0x1a/0x60 [i915] > > [] fbcon_init+0x514/0x5a0 > > [] visual_init+0xbc/0x120 > > [] do_bind_con_driver+0x16a/0x320 > > [] do_take_over_console+0x124/0x1d0 > > [] do_fbcon_takeover+0x5b/0xb0 > > [] fbcon_event_notify+0x672/0x800 > > [] notifier_call_chain+0x4d/0x70 > > [] __blocking_notifier_call_chain+0x58/0x80 > > [] blocking_notifier_call_chain+0x16/0x20 > > [] fb_notifier_call_chain+0x1b/0x20 > > [] register_framebuffer+0x1eb/0x320 > > [] drm_fb_helper_initial_config+0x214/0x3a0 > > [drm_kms_helper] > > [] intel_fbdev_initial_config+0x1b/0x20 [i915] > > [] async_run_entry_fn+0x4c/0x160 > > [] process_one_work+0x14b/0x4a0 > > [] worker_thread+0x11b/0x480 > > [] ? rescuer_thread+0x310/0x310 > > [] kthread+0xc9/0xe0 > > [] ? wq_unbind_fn+0xa0/0x100 > > [] ? flush_kthread_worker+0x90/0x90 > > [] ret_from_fork+0x7c/0xb0 > > [] ? flush_kthread_worker+0x90/0x90 > > ---[ end trace 507288b4d65403f3 ]--- > > > > It's not connected to a monitor so I don't know if it has a blank screen or > > not. > > But because of the warning, it makes my tests fail (ktest fails or call > > traces > > like this). > > > > I bisected it down to this commit: > > > > commit 455a68086d1dfb801ad7c867d5ca0ed0e0f758b0 > > Author: Gustavo Padovan > > Date: Mon Dec 1 15:40:11 2014 -0800 > > > > drm/i915: remove intel_pipe_set_base() (v4) > > > > > > -- Steve > > ___ > Intel-gfx mailing list > intel-...@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/intel-gfx -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
Any movement on this? I still get this warning on 4.0-rc4. -- Steve On Thu, 5 Mar 2015 09:27:28 -0500 Steven Rostedt wrote: > On Mon, Feb 23, 2015 at 11:12:39PM +0300, Andrey Skvortsov wrote: > > > > This warning is moved from linux-next to v4.0-rc1 now. After system boot is > > just a black screen. > > I ssh'ed into the machine and saved the log. I attached updated dmesg.log > > with drm.debug=6. Hopefully it helps. > > If you need any other debug information, traces, core dump or something > > else. Feel free to ask. > > > > I'm hitting this exact same warning on one of my test boxes. > > [drm] Initialized i915 1.6.0 20150130 for :00:02.0 on minor 0 > [ cut here ] > WARNING: CPU: 7 PID: 116 at > /home/rostedt/work/git/linux-trace.git/drivers/gpu/drm/i915/i915_gem.c:4525 > i915_gem_free_object+0x2de/0x300 [i915]() > WARN_ON(obj->frontbuffer_bits) > Modules linked in: i915 i2c_algo_bit e1000e drm_kms_helper ptp crc32c_intel > drm pps_core i2c_core video sunrpc > CPU: 7 PID: 116 Comm: kworker/u16:5 Not tainted 4.0.0-rc1-test #270 > Hardware name: Hewlett-Packard HP Compaq Pro 6300 SFF/339A, BIOS K01 v02.05 > 05/07/2012 > Workqueue: events_unbound async_run_entry_fn > 11ad 88001fa837e8 816cc3cc d4d4 > 88001fa83838 88001fa83828 8107b977 8800d4fd > 88001f2b5800 8800d4f40040 8800d4f4 8800d4f400c0 > Call Trace: > [] dump_stack+0x4c/0x6e > [] warn_slowpath_common+0x97/0xe0 > [] warn_slowpath_fmt+0x46/0x50 > [] i915_gem_free_object+0x2de/0x300 [i915] > [] drm_gem_object_free+0x27/0x30 [drm] > [] intel_user_framebuffer_destroy+0x75/0xa0 [i915] > [] drm_framebuffer_free+0x5b/0x70 [drm] > [] drm_framebuffer_unreference+0x39/0x70 [drm] > [] drm_mode_set_config_internal+0xcc/0x110 [drm] > [] restore_fbdev_mode+0xc8/0xf0 [drm_kms_helper] > [] drm_fb_helper_restore_fbdev_mode_unlocked+0x30/0x80 > [drm_kms_helper] > [] drm_fb_helper_set_par+0x24/0x50 [drm_kms_helper] > [] intel_fbdev_set_par+0x1a/0x60 [i915] > [] fbcon_init+0x514/0x5a0 > [] visual_init+0xbc/0x120 > [] do_bind_con_driver+0x16a/0x320 > [] do_take_over_console+0x124/0x1d0 > [] do_fbcon_takeover+0x5b/0xb0 > [] fbcon_event_notify+0x672/0x800 > [] notifier_call_chain+0x4d/0x70 > [] __blocking_notifier_call_chain+0x58/0x80 > [] blocking_notifier_call_chain+0x16/0x20 > [] fb_notifier_call_chain+0x1b/0x20 > [] register_framebuffer+0x1eb/0x320 > [] drm_fb_helper_initial_config+0x214/0x3a0 > [drm_kms_helper] > [] intel_fbdev_initial_config+0x1b/0x20 [i915] > [] async_run_entry_fn+0x4c/0x160 > [] process_one_work+0x14b/0x4a0 > [] worker_thread+0x11b/0x480 > [] ? rescuer_thread+0x310/0x310 > [] kthread+0xc9/0xe0 > [] ? wq_unbind_fn+0xa0/0x100 > [] ? flush_kthread_worker+0x90/0x90 > [] ret_from_fork+0x7c/0xb0 > [] ? flush_kthread_worker+0x90/0x90 > ---[ end trace 507288b4d65403f3 ]--- > > It's not connected to a monitor so I don't know if it has a blank screen or > not. > But because of the warning, it makes my tests fail (ktest fails or call traces > like this). > > I bisected it down to this commit: > > commit 455a68086d1dfb801ad7c867d5ca0ed0e0f758b0 > Author: Gustavo Padovan > Date: Mon Dec 1 15:40:11 2014 -0800 > > drm/i915: remove intel_pipe_set_base() (v4) > > > -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
Any movement on this? I still get this warning on 4.0-rc4. -- Steve On Thu, 5 Mar 2015 09:27:28 -0500 Steven Rostedt rost...@goodmis.org wrote: On Mon, Feb 23, 2015 at 11:12:39PM +0300, Andrey Skvortsov wrote: This warning is moved from linux-next to v4.0-rc1 now. After system boot is just a black screen. I ssh'ed into the machine and saved the log. I attached updated dmesg.log with drm.debug=6. Hopefully it helps. If you need any other debug information, traces, core dump or something else. Feel free to ask. I'm hitting this exact same warning on one of my test boxes. [drm] Initialized i915 1.6.0 20150130 for :00:02.0 on minor 0 [ cut here ] WARNING: CPU: 7 PID: 116 at /home/rostedt/work/git/linux-trace.git/drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object+0x2de/0x300 [i915]() WARN_ON(obj-frontbuffer_bits) Modules linked in: i915 i2c_algo_bit e1000e drm_kms_helper ptp crc32c_intel drm pps_core i2c_core video sunrpc CPU: 7 PID: 116 Comm: kworker/u16:5 Not tainted 4.0.0-rc1-test #270 Hardware name: Hewlett-Packard HP Compaq Pro 6300 SFF/339A, BIOS K01 v02.05 05/07/2012 Workqueue: events_unbound async_run_entry_fn 11ad 88001fa837e8 816cc3cc d4d4 88001fa83838 88001fa83828 8107b977 8800d4fd 88001f2b5800 8800d4f40040 8800d4f4 8800d4f400c0 Call Trace: [816cc3cc] dump_stack+0x4c/0x6e [8107b977] warn_slowpath_common+0x97/0xe0 [8107ba76] warn_slowpath_fmt+0x46/0x50 [a01b513e] i915_gem_free_object+0x2de/0x300 [i915] [a0079797] drm_gem_object_free+0x27/0x30 [drm] [a01ebf55] intel_user_framebuffer_destroy+0x75/0xa0 [i915] [a0084b1b] drm_framebuffer_free+0x5b/0x70 [drm] [a00858f9] drm_framebuffer_unreference+0x39/0x70 [drm] [a00859fc] drm_mode_set_config_internal+0xcc/0x110 [drm] [a013dca8] restore_fbdev_mode+0xc8/0xf0 [drm_kms_helper] [a013f780] drm_fb_helper_restore_fbdev_mode_unlocked+0x30/0x80 [drm_kms_helper] [a013f7f4] drm_fb_helper_set_par+0x24/0x50 [drm_kms_helper] [a020bada] intel_fbdev_set_par+0x1a/0x60 [i915] [8139f9c4] fbcon_init+0x514/0x5a0 [8140f39c] visual_init+0xbc/0x120 [81411aea] do_bind_con_driver+0x16a/0x320 [81411dc4] do_take_over_console+0x124/0x1d0 [8139de6b] do_fbcon_takeover+0x5b/0xb0 [813a2bd2] fbcon_event_notify+0x672/0x800 [810997dd] notifier_call_chain+0x4d/0x70 [810999c8] __blocking_notifier_call_chain+0x58/0x80 [81099a06] blocking_notifier_call_chain+0x16/0x20 [813a970b] fb_notifier_call_chain+0x1b/0x20 [813ab96b] register_framebuffer+0x1eb/0x320 [a013fa34] drm_fb_helper_initial_config+0x214/0x3a0 [drm_kms_helper] [a020c64b] intel_fbdev_initial_config+0x1b/0x20 [i915] [8109b40c] async_run_entry_fn+0x4c/0x160 [81092bab] process_one_work+0x14b/0x4a0 [8109336b] worker_thread+0x11b/0x480 [81093250] ? rescuer_thread+0x310/0x310 [81098e89] kthread+0xc9/0xe0 [8109] ? wq_unbind_fn+0xa0/0x100 [81098dc0] ? flush_kthread_worker+0x90/0x90 [816d3aac] ret_from_fork+0x7c/0xb0 [81098dc0] ? flush_kthread_worker+0x90/0x90 ---[ end trace 507288b4d65403f3 ]--- It's not connected to a monitor so I don't know if it has a blank screen or not. But because of the warning, it makes my tests fail (ktest fails or call traces like this). I bisected it down to this commit: commit 455a68086d1dfb801ad7c867d5ca0ed0e0f758b0 Author: Gustavo Padovan gustavo.pado...@collabora.co.uk Date: Mon Dec 1 15:40:11 2014 -0800 drm/i915: remove intel_pipe_set_base() (v4) -- Steve -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
On Mon, Mar 16, 2015 at 11:45:03AM -0400, Steven Rostedt wrote: Any movement on this? I still get this warning on 4.0-rc4. Sorry for not looking into this, I've thought we've addressed this already and the fix is simply still in-flight to 4.0-rc. Seems it's not :( Is linux-next also affected or is this just a case of i915 maintainers having failed to push the right patch to -fixes? I'll try to figure out what fell apart here meanwhile. To help out, can you please boot with drm.debug=0xe and grab the full dmesg for booting? Looks like it falls over in the initial fbcon modeset, which is indeed strange ... Thanks, Daniel -- Steve On Thu, 5 Mar 2015 09:27:28 -0500 Steven Rostedt rost...@goodmis.org wrote: On Mon, Feb 23, 2015 at 11:12:39PM +0300, Andrey Skvortsov wrote: This warning is moved from linux-next to v4.0-rc1 now. After system boot is just a black screen. I ssh'ed into the machine and saved the log. I attached updated dmesg.log with drm.debug=6. Hopefully it helps. If you need any other debug information, traces, core dump or something else. Feel free to ask. I'm hitting this exact same warning on one of my test boxes. [drm] Initialized i915 1.6.0 20150130 for :00:02.0 on minor 0 [ cut here ] WARNING: CPU: 7 PID: 116 at /home/rostedt/work/git/linux-trace.git/drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object+0x2de/0x300 [i915]() WARN_ON(obj-frontbuffer_bits) Modules linked in: i915 i2c_algo_bit e1000e drm_kms_helper ptp crc32c_intel drm pps_core i2c_core video sunrpc CPU: 7 PID: 116 Comm: kworker/u16:5 Not tainted 4.0.0-rc1-test #270 Hardware name: Hewlett-Packard HP Compaq Pro 6300 SFF/339A, BIOS K01 v02.05 05/07/2012 Workqueue: events_unbound async_run_entry_fn 11ad 88001fa837e8 816cc3cc d4d4 88001fa83838 88001fa83828 8107b977 8800d4fd 88001f2b5800 8800d4f40040 8800d4f4 8800d4f400c0 Call Trace: [816cc3cc] dump_stack+0x4c/0x6e [8107b977] warn_slowpath_common+0x97/0xe0 [8107ba76] warn_slowpath_fmt+0x46/0x50 [a01b513e] i915_gem_free_object+0x2de/0x300 [i915] [a0079797] drm_gem_object_free+0x27/0x30 [drm] [a01ebf55] intel_user_framebuffer_destroy+0x75/0xa0 [i915] [a0084b1b] drm_framebuffer_free+0x5b/0x70 [drm] [a00858f9] drm_framebuffer_unreference+0x39/0x70 [drm] [a00859fc] drm_mode_set_config_internal+0xcc/0x110 [drm] [a013dca8] restore_fbdev_mode+0xc8/0xf0 [drm_kms_helper] [a013f780] drm_fb_helper_restore_fbdev_mode_unlocked+0x30/0x80 [drm_kms_helper] [a013f7f4] drm_fb_helper_set_par+0x24/0x50 [drm_kms_helper] [a020bada] intel_fbdev_set_par+0x1a/0x60 [i915] [8139f9c4] fbcon_init+0x514/0x5a0 [8140f39c] visual_init+0xbc/0x120 [81411aea] do_bind_con_driver+0x16a/0x320 [81411dc4] do_take_over_console+0x124/0x1d0 [8139de6b] do_fbcon_takeover+0x5b/0xb0 [813a2bd2] fbcon_event_notify+0x672/0x800 [810997dd] notifier_call_chain+0x4d/0x70 [810999c8] __blocking_notifier_call_chain+0x58/0x80 [81099a06] blocking_notifier_call_chain+0x16/0x20 [813a970b] fb_notifier_call_chain+0x1b/0x20 [813ab96b] register_framebuffer+0x1eb/0x320 [a013fa34] drm_fb_helper_initial_config+0x214/0x3a0 [drm_kms_helper] [a020c64b] intel_fbdev_initial_config+0x1b/0x20 [i915] [8109b40c] async_run_entry_fn+0x4c/0x160 [81092bab] process_one_work+0x14b/0x4a0 [8109336b] worker_thread+0x11b/0x480 [81093250] ? rescuer_thread+0x310/0x310 [81098e89] kthread+0xc9/0xe0 [8109] ? wq_unbind_fn+0xa0/0x100 [81098dc0] ? flush_kthread_worker+0x90/0x90 [816d3aac] ret_from_fork+0x7c/0xb0 [81098dc0] ? flush_kthread_worker+0x90/0x90 ---[ end trace 507288b4d65403f3 ]--- It's not connected to a monitor so I don't know if it has a blank screen or not. But because of the warning, it makes my tests fail (ktest fails or call traces like this). I bisected it down to this commit: commit 455a68086d1dfb801ad7c867d5ca0ed0e0f758b0 Author: Gustavo Padovan gustavo.pado...@collabora.co.uk Date: Mon Dec 1 15:40:11 2014 -0800 drm/i915: remove intel_pipe_set_base() (v4) -- Steve ___ Intel-gfx mailing list intel-...@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
On Mon, 16 Mar 2015 17:43:33 +0100 Daniel Vetter dan...@ffwll.ch wrote: Is linux-next also affected or is this just a case of i915 maintainers having failed to push the right patch to -fixes? I just confirmed, linux-next boots without the warning. I'll try to figure out what fell apart here meanwhile. To help out, can you please boot with drm.debug=0xe and grab the full dmesg for booting? Looks like it falls over in the initial fbcon modeset, which is indeed strange ... Here they are: http://rostedt.homelinux.com/private/dmesg-next http://rostedt.homelinux.com/private/dmesg-4.0 -- Steve -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
On Mon, Feb 23, 2015 at 11:12:39PM +0300, Andrey Skvortsov wrote: > > This warning is moved from linux-next to v4.0-rc1 now. After system boot is > just a black screen. > I ssh'ed into the machine and saved the log. I attached updated dmesg.log > with drm.debug=6. Hopefully it helps. > If you need any other debug information, traces, core dump or something else. > Feel free to ask. > I'm hitting this exact same warning on one of my test boxes. [drm] Initialized i915 1.6.0 20150130 for :00:02.0 on minor 0 [ cut here ] WARNING: CPU: 7 PID: 116 at /home/rostedt/work/git/linux-trace.git/drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object+0x2de/0x300 [i915]() WARN_ON(obj->frontbuffer_bits) Modules linked in: i915 i2c_algo_bit e1000e drm_kms_helper ptp crc32c_intel drm pps_core i2c_core video sunrpc CPU: 7 PID: 116 Comm: kworker/u16:5 Not tainted 4.0.0-rc1-test #270 Hardware name: Hewlett-Packard HP Compaq Pro 6300 SFF/339A, BIOS K01 v02.05 05/07/2012 Workqueue: events_unbound async_run_entry_fn 11ad 88001fa837e8 816cc3cc d4d4 88001fa83838 88001fa83828 8107b977 8800d4fd 88001f2b5800 8800d4f40040 8800d4f4 8800d4f400c0 Call Trace: [] dump_stack+0x4c/0x6e [] warn_slowpath_common+0x97/0xe0 [] warn_slowpath_fmt+0x46/0x50 [] i915_gem_free_object+0x2de/0x300 [i915] [] drm_gem_object_free+0x27/0x30 [drm] [] intel_user_framebuffer_destroy+0x75/0xa0 [i915] [] drm_framebuffer_free+0x5b/0x70 [drm] [] drm_framebuffer_unreference+0x39/0x70 [drm] [] drm_mode_set_config_internal+0xcc/0x110 [drm] [] restore_fbdev_mode+0xc8/0xf0 [drm_kms_helper] [] drm_fb_helper_restore_fbdev_mode_unlocked+0x30/0x80 [drm_kms_helper] [] drm_fb_helper_set_par+0x24/0x50 [drm_kms_helper] [] intel_fbdev_set_par+0x1a/0x60 [i915] [] fbcon_init+0x514/0x5a0 [] visual_init+0xbc/0x120 [] do_bind_con_driver+0x16a/0x320 [] do_take_over_console+0x124/0x1d0 [] do_fbcon_takeover+0x5b/0xb0 [] fbcon_event_notify+0x672/0x800 [] notifier_call_chain+0x4d/0x70 [] __blocking_notifier_call_chain+0x58/0x80 [] blocking_notifier_call_chain+0x16/0x20 [] fb_notifier_call_chain+0x1b/0x20 [] register_framebuffer+0x1eb/0x320 [] drm_fb_helper_initial_config+0x214/0x3a0 [drm_kms_helper] [] intel_fbdev_initial_config+0x1b/0x20 [i915] [] async_run_entry_fn+0x4c/0x160 [] process_one_work+0x14b/0x4a0 [] worker_thread+0x11b/0x480 [] ? rescuer_thread+0x310/0x310 [] kthread+0xc9/0xe0 [] ? wq_unbind_fn+0xa0/0x100 [] ? flush_kthread_worker+0x90/0x90 [] ret_from_fork+0x7c/0xb0 [] ? flush_kthread_worker+0x90/0x90 ---[ end trace 507288b4d65403f3 ]--- It's not connected to a monitor so I don't know if it has a blank screen or not. But because of the warning, it makes my tests fail (ktest fails or call traces like this). I bisected it down to this commit: commit 455a68086d1dfb801ad7c867d5ca0ed0e0f758b0 Author: Gustavo Padovan Date: Mon Dec 1 15:40:11 2014 -0800 drm/i915: remove intel_pipe_set_base() (v4) -- Steve -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
On Mon, Feb 23, 2015 at 11:12:39PM +0300, Andrey Skvortsov wrote: This warning is moved from linux-next to v4.0-rc1 now. After system boot is just a black screen. I ssh'ed into the machine and saved the log. I attached updated dmesg.log with drm.debug=6. Hopefully it helps. If you need any other debug information, traces, core dump or something else. Feel free to ask. I'm hitting this exact same warning on one of my test boxes. [drm] Initialized i915 1.6.0 20150130 for :00:02.0 on minor 0 [ cut here ] WARNING: CPU: 7 PID: 116 at /home/rostedt/work/git/linux-trace.git/drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object+0x2de/0x300 [i915]() WARN_ON(obj-frontbuffer_bits) Modules linked in: i915 i2c_algo_bit e1000e drm_kms_helper ptp crc32c_intel drm pps_core i2c_core video sunrpc CPU: 7 PID: 116 Comm: kworker/u16:5 Not tainted 4.0.0-rc1-test #270 Hardware name: Hewlett-Packard HP Compaq Pro 6300 SFF/339A, BIOS K01 v02.05 05/07/2012 Workqueue: events_unbound async_run_entry_fn 11ad 88001fa837e8 816cc3cc d4d4 88001fa83838 88001fa83828 8107b977 8800d4fd 88001f2b5800 8800d4f40040 8800d4f4 8800d4f400c0 Call Trace: [816cc3cc] dump_stack+0x4c/0x6e [8107b977] warn_slowpath_common+0x97/0xe0 [8107ba76] warn_slowpath_fmt+0x46/0x50 [a01b513e] i915_gem_free_object+0x2de/0x300 [i915] [a0079797] drm_gem_object_free+0x27/0x30 [drm] [a01ebf55] intel_user_framebuffer_destroy+0x75/0xa0 [i915] [a0084b1b] drm_framebuffer_free+0x5b/0x70 [drm] [a00858f9] drm_framebuffer_unreference+0x39/0x70 [drm] [a00859fc] drm_mode_set_config_internal+0xcc/0x110 [drm] [a013dca8] restore_fbdev_mode+0xc8/0xf0 [drm_kms_helper] [a013f780] drm_fb_helper_restore_fbdev_mode_unlocked+0x30/0x80 [drm_kms_helper] [a013f7f4] drm_fb_helper_set_par+0x24/0x50 [drm_kms_helper] [a020bada] intel_fbdev_set_par+0x1a/0x60 [i915] [8139f9c4] fbcon_init+0x514/0x5a0 [8140f39c] visual_init+0xbc/0x120 [81411aea] do_bind_con_driver+0x16a/0x320 [81411dc4] do_take_over_console+0x124/0x1d0 [8139de6b] do_fbcon_takeover+0x5b/0xb0 [813a2bd2] fbcon_event_notify+0x672/0x800 [810997dd] notifier_call_chain+0x4d/0x70 [810999c8] __blocking_notifier_call_chain+0x58/0x80 [81099a06] blocking_notifier_call_chain+0x16/0x20 [813a970b] fb_notifier_call_chain+0x1b/0x20 [813ab96b] register_framebuffer+0x1eb/0x320 [a013fa34] drm_fb_helper_initial_config+0x214/0x3a0 [drm_kms_helper] [a020c64b] intel_fbdev_initial_config+0x1b/0x20 [i915] [8109b40c] async_run_entry_fn+0x4c/0x160 [81092bab] process_one_work+0x14b/0x4a0 [8109336b] worker_thread+0x11b/0x480 [81093250] ? rescuer_thread+0x310/0x310 [81098e89] kthread+0xc9/0xe0 [8109] ? wq_unbind_fn+0xa0/0x100 [81098dc0] ? flush_kthread_worker+0x90/0x90 [816d3aac] ret_from_fork+0x7c/0xb0 [81098dc0] ? flush_kthread_worker+0x90/0x90 ---[ end trace 507288b4d65403f3 ]--- It's not connected to a monitor so I don't know if it has a blank screen or not. But because of the warning, it makes my tests fail (ktest fails or call traces like this). I bisected it down to this commit: commit 455a68086d1dfb801ad7c867d5ca0ed0e0f758b0 Author: Gustavo Padovan gustavo.pado...@collabora.co.uk Date: Mon Dec 1 15:40:11 2014 -0800 drm/i915: remove intel_pipe_set_base() (v4) -- Steve -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
On Sat, Feb 28, 2015 at 03:20:37PM +0300, Andrey Skvortsov wrote: > Unfortunately this is not the last bug, that breaks i915/drm working > on my laptop. Sometimes system successfully loads with couple warnings > mentioned in > previous mail: > > [ 26.922953] WARNING: CPU: 1 PID: 767 at > drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object+0x13f/0x288 [i915]() > [ 26.922954] WARN_ON(obj->frontbuffer_bits) That's inocuous, but for the serious hang, you may want to try video=SVIDEO-1:d on the kernel commandline to workaround the hang. (Check /sys/class/drm/card/ for the actual name of the connector for TV). I think Ville mentioned he was looking/looked at the atomic-vs-load_detect changes that is at the heart of the issue here. (Admittedly he did say it was worthy of a drink or two.) -Chris -- Chris Wilson, Intel Open Source Technology Centre -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
On Sat, Feb 28, 2015 at 03:20:37PM +0300, Andrey Skvortsov wrote: Unfortunately this is not the last bug, that breaks i915/drm working on my laptop. Sometimes system successfully loads with couple warnings mentioned in previous mail: [ 26.922953] WARNING: CPU: 1 PID: 767 at drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object+0x13f/0x288 [i915]() [ 26.922954] WARN_ON(obj-frontbuffer_bits) That's inocuous, but for the serious hang, you may want to try video=SVIDEO-1:d on the kernel commandline to workaround the hang. (Check /sys/class/drm/card/ for the actual name of the connector for TV). I think Ville mentioned he was looking/looked at the atomic-vs-load_detect changes that is at the heart of the issue here. (Admittedly he did say it was worthy of a drink or two.) -Chris -- Chris Wilson, Intel Open Source Technology Centre -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
On Mon, Feb 23, 2015 at 09:20:31PM +, Chris Wilson wrote: > On Mon, Feb 23, 2015 at 11:12:39PM +0300, Andrey Skvortsov wrote: > > Hi, > > > > This warning is moved from linux-next to v4.0-rc1 now. After system boot is > > just a black screen. > > I ssh'ed into the machine and saved the log. I attached updated dmesg.log > > with drm.debug=6. Hopefully it helps. > > If you need any other debug information, traces, core dump or something > > else. Feel free to ask. > > The warning from free_object is annoying (and quite possibly dangerous), > but the actual hang during boot is: > > [ 243.876375] INFO: task Xorg:2422 blocked for more than 120 seconds. > [ 243.876382] Tainted: GW E 4.0.0-rc1-150223- #2 > [ 243.876388] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables > this message. > [ 243.876393] XorgD 88019fc12dc0 0 2422 2180 > 0x0040 > [ 243.876404] 8800dabfe1a0 0002 880194537fd8 > 880194537ba0 > [ 243.876416] 8800dab9e22c 8800dabfe1a0 8800dab9e230 > > [ 243.876426] 813e2479 8800dab9e228 813e26a7 > > [ 243.876438] Call Trace: > [ 243.876449] [] ? schedule+0x6f/0x7c > [ 243.876459] [] ? schedule_preempt_disabled+0x15/0x21 > [ 243.876469] [] ? __ww_mutex_lock_slowpath+0xdf/0x1c2 > [ 243.876480] [] ? __ww_mutex_lock+0x1c/0x93 > [ 243.876541] [] ? modeset_lock+0x8f/0xf2 [drm] > [ 243.876632] [] ? intel_get_load_detect_pipe+0x80/0x427 > [i915] > [ 243.876674] [] ? drm_ut_debug_printk+0x5e/0x63 [drm] > [ 243.876771] [] ? intel_tv_detect+0x115/0x43a [i915] > [ 243.876783] [] ? preempt_count_sub+0xbf/0xca > [ 243.876809] [] ? > drm_helper_probe_single_connector_modes_merge_bits+0xc6/0x38d [drm_kms_helper] > [ 243.876860] [] ? drm_mode_getconnector+0xf4/0x2ac [drm] > [ 243.876900] [] ? drm_ioctl+0x338/0x3c5 [drm] > [ 243.876949] [] ? drm_mode_getcrtc+0xb3/0xb3 [drm] > [ 243.876961] [] ? fsnotify+0x314/0x35d > [ 243.876973] [] ? do_vfs_ioctl+0x379/0x431 > [ 243.876983] [] ? SyS_ioctl+0x56/0x7c > [ 243.876994] [] ? system_call_fastpath+0x12/0x17 > > i.e. it is a mutex deadlock inside tv detect. Daniel does that make sense? Botch locking rework for atomic. Fix is https://patchwork.kernel.org/patch/5861631/ and will land as soon as an affected user has provided a tested-by. Andrey, can you pls give this a spin? Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
On Mon, Feb 23, 2015 at 11:12:39PM +0300, Andrey Skvortsov wrote: > Hi, > > This warning is moved from linux-next to v4.0-rc1 now. After system boot is > just a black screen. > I ssh'ed into the machine and saved the log. I attached updated dmesg.log > with drm.debug=6. Hopefully it helps. > If you need any other debug information, traces, core dump or something else. > Feel free to ask. The warning from free_object is annoying (and quite possibly dangerous), but the actual hang during boot is: [ 243.876375] INFO: task Xorg:2422 blocked for more than 120 seconds. [ 243.876382] Tainted: GW E 4.0.0-rc1-150223- #2 [ 243.876388] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 243.876393] XorgD 88019fc12dc0 0 2422 2180 0x0040 [ 243.876404] 8800dabfe1a0 0002 880194537fd8 880194537ba0 [ 243.876416] 8800dab9e22c 8800dabfe1a0 8800dab9e230 [ 243.876426] 813e2479 8800dab9e228 813e26a7 [ 243.876438] Call Trace: [ 243.876449] [] ? schedule+0x6f/0x7c [ 243.876459] [] ? schedule_preempt_disabled+0x15/0x21 [ 243.876469] [] ? __ww_mutex_lock_slowpath+0xdf/0x1c2 [ 243.876480] [] ? __ww_mutex_lock+0x1c/0x93 [ 243.876541] [] ? modeset_lock+0x8f/0xf2 [drm] [ 243.876632] [] ? intel_get_load_detect_pipe+0x80/0x427 [i915] [ 243.876674] [] ? drm_ut_debug_printk+0x5e/0x63 [drm] [ 243.876771] [] ? intel_tv_detect+0x115/0x43a [i915] [ 243.876783] [] ? preempt_count_sub+0xbf/0xca [ 243.876809] [] ? drm_helper_probe_single_connector_modes_merge_bits+0xc6/0x38d [drm_kms_helper] [ 243.876860] [] ? drm_mode_getconnector+0xf4/0x2ac [drm] [ 243.876900] [] ? drm_ioctl+0x338/0x3c5 [drm] [ 243.876949] [] ? drm_mode_getcrtc+0xb3/0xb3 [drm] [ 243.876961] [] ? fsnotify+0x314/0x35d [ 243.876973] [] ? do_vfs_ioctl+0x379/0x431 [ 243.876983] [] ? SyS_ioctl+0x56/0x7c [ 243.876994] [] ? system_call_fastpath+0x12/0x17 i.e. it is a mutex deadlock inside tv detect. Daniel does that make sense? -Chris -- Chris Wilson, Intel Open Source Technology Centre -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
> > > Those two warnings are more or less symptoms of the black screen (well > > > the first is just overzealous). More important would be the drm.debug=6 > > > dmesg from boot along with the gdm.log (or equivalent) aned Xorg.0.log > > > as my guess is that X (or the display server) is crashing. > > > > Requested logs with drm.debug=6 are attached. lightdm was running after > > WARN_ON, but I couldn't restart it. > > The command hanged. > > > > As I booted next-20150202 system crashed several times with a lot of drm_ > > calls in the backtrace, but I couldn't catch kernel logs, > > because I have not serial port on the laptop. > > > > If you need to get other information or to test patches, I would be glad to > > help. > > Right, here it looks like it freezing in intel_get_load_detect_pipe() > during the initial configuration probe of X. Given the other crashes, > we're back to worring about memory corruption. > > > [ 29.292333] [drm:intel_tv_detect] [CONNECTOR:33:SVIDEO-1] force=1 > > [ 29.292336] [drm:intel_get_load_detect_pipe] [CONNECTOR:33:SVIDEO-1], > > [ENCODER:34:TV-34] > > [ 29.292339] [drm:intel_get_load_detect_pipe] creating tmp fb for > > load-detection > > [ 29.292396] [drm:intel_modeset_affected_pipes] set mode pipe masks: > > modeset: 1, prepare: 1, disable: 0 > > [ 29.292408] [drm:connected_sink_compute_bpp] [CONNECTOR:33:SVIDEO-1] > > checking for sink bpp constrains > > [ 29.292413] [drm:intel_tv_compute_config] forcing bpc to 8 for TV > > [ 29.292416] [drm:intel_modeset_pipe_config] plane bpp: 24, pipe bpp: 24, > > dithering: 0 > > [ 29.292418] [drm:intel_dump_pipe_config] [CRTC:20][modeset] config for > > pipe A > > [ 29.292419] [drm:intel_dump_pipe_config] cpu_transcoder: A > > [ 29.292421] [drm:intel_dump_pipe_config] pipe bpp: 24, dithering: 0 > > [ 29.292423] [drm:intel_dump_pipe_config] fdi/pch: 0, lanes: 0, gmch_m: > > 0, gmch_n: 0, link_m: 0, link_n: 0, tu: 0 > > [ 29.292425] [drm:intel_dump_pipe_config] dp: 0, gmch_m: 0, gmch_n: 0, > > link_m: 0, link_n: 0, tu: 0 > > [ 29.292428] [drm:intel_dump_pipe_config] dp: 0, gmch_m2: 0, gmch_n2: 0, > > link_m2: 0, link_n2: 0, tu2: 0 > > [ 29.292429] [drm:intel_dump_pipe_config] audio: 0, infoframes: 0 > > [ 29.292431] [drm:intel_dump_pipe_config] requested mode: > > [ 29.292433] [drm:drm_mode_debug_printmodeline] Modeline 0:"NTSC 480i" 0 > > 107520 1280 1368 1496 1712 1024 1027 1034 1104 0x40 0x0 > > [ 29.292435] [drm:intel_dump_pipe_config] adjusted mode: > > [ 29.292438] [drm:drm_mode_debug_printmodeline] Modeline 0:"NTSC 480i" 0 > > 107520 1280 1368 1496 1712 1024 1027 1034 1104 0x40 0x0 > > [ 29.292440] [drm:intel_dump_crtc_timings] crtc timings: 108000 1280 1368 > > 1496 1712 1024 1027 1034 1104, type: 0x40 flags: 0x0 > > [ 29.292442] [drm:intel_dump_pipe_config] port clock: 108000 > > [ 29.292444] [drm:intel_dump_pipe_config] pipe src size: 1280x1024 > > [ 29.292446] [drm:intel_dump_pipe_config] gmch pfit: control: 0x, > > ratios: 0x, lvds border: 0x > > [ 29.292447] [drm:intel_dump_pipe_config] pch pfit: pos: 0x, > > size: 0x, disabled > > [ 29.292449] [drm:intel_dump_pipe_config] ips: 0 > > [ 29.292451] [drm:intel_dump_pipe_config] double wide: 0 > > [ 29.292565] [ cut here ] > > [ 29.293785] WARNING: CPU: 0 PID: 53 at include/linux/kref.h:47 > > drm_framebuffer_reference+0x5b/0x64 [drm]() > > [ 29.295032] Modules linked in: bnep(E) cfg80211(E) cpufreq_stats(E) > > cpufreq_powersave(E) cpufreq_userspace(E) cpufreq_conservative(E) nfsd(E) > > auth_rpcgss(E) nfs_acl(E) lockd(E) grace(E) sunrpc(E) cdc_wdm(E) cdc_acm(E) > > cdc_ether(E) usbnet(E) joydev(E) coretemp(E) kvm_intel(E) kvm(E) i8k(E) > > btusb(E) psmouse(E) snd_pcsp(E) i915(E) evdev(E) bluetooth(E) i2c_i801(E) > > snd_hda_codec_generic(E) lpc_ich(E) mfd_core(E) xhci_pci(E) xhci_hcd(E) > > serio_raw(E) rfkill(E) drm_kms_helper(E) drm(E) i2c_algo_bit(E) i2c_core(E) > > snd_hda_intel(E) snd_hda_controller(E) snd_hda_codec(E) button(E) > > snd_hwdep(E) battery(E) snd_pcm(E) snd_timer(E) snd(E) soundcore(E) > > video(E) ac(E) acpi_cpufreq(E) processor(E) fuse(E) parport_pc(E) ppdev(E) > > lp(E) parport(E) autofs4(E) ext4(E) crc16(E) jbd2(E) mbcache(E) sd_mod(E) > > ata_generic(E) > > [ 29.295080] ahci(E) libahci(E) ata_piix(E) libata(E) scsi_mod(E) b44(E) > > firewire_ohci(E) sdhci_pci(E) sdhci(E) firewire_core(E) crc_itu_t(E) mii(E) > > ssb(E) mmc_core(E) libphy(E) uhci_hcd(E) ehci_pci(E) ehci_hcd(E) thermal(E) > > thermal_sys(E) usbcore(E) usb_common(E) > > [ 29.296301] CPU: 0 PID: 53 Comm: kworker/0:3 Tainted: GW E > > 3.19.0-rc6-next-20150202-150201- #4 > > [ 29.296303] Hardware name: Dell Inc. Vostro 1500 > > /0NX907, BIOS A06 04/21/2008 > > [ 29.296314] Workqueue: events output_poll_execute [drm_kms_helper] > > [ 29.296316] 0009
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
On Mon, Feb 23, 2015 at 11:12:39PM +0300, Andrey Skvortsov wrote: Hi, This warning is moved from linux-next to v4.0-rc1 now. After system boot is just a black screen. I ssh'ed into the machine and saved the log. I attached updated dmesg.log with drm.debug=6. Hopefully it helps. If you need any other debug information, traces, core dump or something else. Feel free to ask. The warning from free_object is annoying (and quite possibly dangerous), but the actual hang during boot is: [ 243.876375] INFO: task Xorg:2422 blocked for more than 120 seconds. [ 243.876382] Tainted: GW E 4.0.0-rc1-150223- #2 [ 243.876388] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 243.876393] XorgD 88019fc12dc0 0 2422 2180 0x0040 [ 243.876404] 8800dabfe1a0 0002 880194537fd8 880194537ba0 [ 243.876416] 8800dab9e22c 8800dabfe1a0 8800dab9e230 [ 243.876426] 813e2479 8800dab9e228 813e26a7 [ 243.876438] Call Trace: [ 243.876449] [813e2479] ? schedule+0x6f/0x7c [ 243.876459] [813e26a7] ? schedule_preempt_disabled+0x15/0x21 [ 243.876469] [813e3347] ? __ww_mutex_lock_slowpath+0xdf/0x1c2 [ 243.876480] [813e3446] ? __ww_mutex_lock+0x1c/0x93 [ 243.876541] [a050e70d] ? modeset_lock+0x8f/0xf2 [drm] [ 243.876632] [a09aa0b9] ? intel_get_load_detect_pipe+0x80/0x427 [i915] [ 243.876674] [a04fd42f] ? drm_ut_debug_printk+0x5e/0x63 [drm] [ 243.876771] [a09d4661] ? intel_tv_detect+0x115/0x43a [i915] [ 243.876783] [810608d9] ? preempt_count_sub+0xbf/0xca [ 243.876809] [a05d6f24] ? drm_helper_probe_single_connector_modes_merge_bits+0xc6/0x38d [drm_kms_helper] [ 243.876860] [a0505b5d] ? drm_mode_getconnector+0xf4/0x2ac [drm] [ 243.876900] [a04fa911] ? drm_ioctl+0x338/0x3c5 [drm] [ 243.876949] [a0505a69] ? drm_mode_getcrtc+0xb3/0xb3 [drm] [ 243.876961] [81167deb] ? fsnotify+0x314/0x35d [ 243.876973] [811487be] ? do_vfs_ioctl+0x379/0x431 [ 243.876983] [811488cc] ? SyS_ioctl+0x56/0x7c [ 243.876994] [813e5152] ? system_call_fastpath+0x12/0x17 i.e. it is a mutex deadlock inside tv detect. Daniel does that make sense? -Chris -- Chris Wilson, Intel Open Source Technology Centre -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
Those two warnings are more or less symptoms of the black screen (well the first is just overzealous). More important would be the drm.debug=6 dmesg from boot along with the gdm.log (or equivalent) aned Xorg.0.log as my guess is that X (or the display server) is crashing. Requested logs with drm.debug=6 are attached. lightdm was running after WARN_ON, but I couldn't restart it. The command hanged. As I booted next-20150202 system crashed several times with a lot of drm_ calls in the backtrace, but I couldn't catch kernel logs, because I have not serial port on the laptop. If you need to get other information or to test patches, I would be glad to help. Right, here it looks like it freezing in intel_get_load_detect_pipe() during the initial configuration probe of X. Given the other crashes, we're back to worring about memory corruption. [ 29.292333] [drm:intel_tv_detect] [CONNECTOR:33:SVIDEO-1] force=1 [ 29.292336] [drm:intel_get_load_detect_pipe] [CONNECTOR:33:SVIDEO-1], [ENCODER:34:TV-34] [ 29.292339] [drm:intel_get_load_detect_pipe] creating tmp fb for load-detection [ 29.292396] [drm:intel_modeset_affected_pipes] set mode pipe masks: modeset: 1, prepare: 1, disable: 0 [ 29.292408] [drm:connected_sink_compute_bpp] [CONNECTOR:33:SVIDEO-1] checking for sink bpp constrains [ 29.292413] [drm:intel_tv_compute_config] forcing bpc to 8 for TV [ 29.292416] [drm:intel_modeset_pipe_config] plane bpp: 24, pipe bpp: 24, dithering: 0 [ 29.292418] [drm:intel_dump_pipe_config] [CRTC:20][modeset] config for pipe A [ 29.292419] [drm:intel_dump_pipe_config] cpu_transcoder: A [ 29.292421] [drm:intel_dump_pipe_config] pipe bpp: 24, dithering: 0 [ 29.292423] [drm:intel_dump_pipe_config] fdi/pch: 0, lanes: 0, gmch_m: 0, gmch_n: 0, link_m: 0, link_n: 0, tu: 0 [ 29.292425] [drm:intel_dump_pipe_config] dp: 0, gmch_m: 0, gmch_n: 0, link_m: 0, link_n: 0, tu: 0 [ 29.292428] [drm:intel_dump_pipe_config] dp: 0, gmch_m2: 0, gmch_n2: 0, link_m2: 0, link_n2: 0, tu2: 0 [ 29.292429] [drm:intel_dump_pipe_config] audio: 0, infoframes: 0 [ 29.292431] [drm:intel_dump_pipe_config] requested mode: [ 29.292433] [drm:drm_mode_debug_printmodeline] Modeline 0:NTSC 480i 0 107520 1280 1368 1496 1712 1024 1027 1034 1104 0x40 0x0 [ 29.292435] [drm:intel_dump_pipe_config] adjusted mode: [ 29.292438] [drm:drm_mode_debug_printmodeline] Modeline 0:NTSC 480i 0 107520 1280 1368 1496 1712 1024 1027 1034 1104 0x40 0x0 [ 29.292440] [drm:intel_dump_crtc_timings] crtc timings: 108000 1280 1368 1496 1712 1024 1027 1034 1104, type: 0x40 flags: 0x0 [ 29.292442] [drm:intel_dump_pipe_config] port clock: 108000 [ 29.292444] [drm:intel_dump_pipe_config] pipe src size: 1280x1024 [ 29.292446] [drm:intel_dump_pipe_config] gmch pfit: control: 0x, ratios: 0x, lvds border: 0x [ 29.292447] [drm:intel_dump_pipe_config] pch pfit: pos: 0x, size: 0x, disabled [ 29.292449] [drm:intel_dump_pipe_config] ips: 0 [ 29.292451] [drm:intel_dump_pipe_config] double wide: 0 [ 29.292565] [ cut here ] [ 29.293785] WARNING: CPU: 0 PID: 53 at include/linux/kref.h:47 drm_framebuffer_reference+0x5b/0x64 [drm]() [ 29.295032] Modules linked in: bnep(E) cfg80211(E) cpufreq_stats(E) cpufreq_powersave(E) cpufreq_userspace(E) cpufreq_conservative(E) nfsd(E) auth_rpcgss(E) nfs_acl(E) lockd(E) grace(E) sunrpc(E) cdc_wdm(E) cdc_acm(E) cdc_ether(E) usbnet(E) joydev(E) coretemp(E) kvm_intel(E) kvm(E) i8k(E) btusb(E) psmouse(E) snd_pcsp(E) i915(E) evdev(E) bluetooth(E) i2c_i801(E) snd_hda_codec_generic(E) lpc_ich(E) mfd_core(E) xhci_pci(E) xhci_hcd(E) serio_raw(E) rfkill(E) drm_kms_helper(E) drm(E) i2c_algo_bit(E) i2c_core(E) snd_hda_intel(E) snd_hda_controller(E) snd_hda_codec(E) button(E) snd_hwdep(E) battery(E) snd_pcm(E) snd_timer(E) snd(E) soundcore(E) video(E) ac(E) acpi_cpufreq(E) processor(E) fuse(E) parport_pc(E) ppdev(E) lp(E) parport(E) autofs4(E) ext4(E) crc16(E) jbd2(E) mbcache(E) sd_mod(E) ata_generic(E) [ 29.295080] ahci(E) libahci(E) ata_piix(E) libata(E) scsi_mod(E) b44(E) firewire_ohci(E) sdhci_pci(E) sdhci(E) firewire_core(E) crc_itu_t(E) mii(E) ssb(E) mmc_core(E) libphy(E) uhci_hcd(E) ehci_pci(E) ehci_hcd(E) thermal(E) thermal_sys(E) usbcore(E) usb_common(E) [ 29.296301] CPU: 0 PID: 53 Comm: kworker/0:3 Tainted: GW E 3.19.0-rc6-next-20150202-150201- #4 [ 29.296303] Hardware name: Dell Inc. Vostro 1500 /0NX907, BIOS A06 04/21/2008 [ 29.296314] Workqueue: events output_poll_execute [drm_kms_helper] [ 29.296316] 0009 813e790a [ 29.296319] 8104178e 880197a38e40 a04eb56d [ 29.296323] 880195844d80 0500
Re: [Intel-gfx] [Regression] WARNING: drivers/gpu/drm/i915/i915_gem.c:4525 i915_gem_free_object
On Mon, Feb 23, 2015 at 09:20:31PM +, Chris Wilson wrote: On Mon, Feb 23, 2015 at 11:12:39PM +0300, Andrey Skvortsov wrote: Hi, This warning is moved from linux-next to v4.0-rc1 now. After system boot is just a black screen. I ssh'ed into the machine and saved the log. I attached updated dmesg.log with drm.debug=6. Hopefully it helps. If you need any other debug information, traces, core dump or something else. Feel free to ask. The warning from free_object is annoying (and quite possibly dangerous), but the actual hang during boot is: [ 243.876375] INFO: task Xorg:2422 blocked for more than 120 seconds. [ 243.876382] Tainted: GW E 4.0.0-rc1-150223- #2 [ 243.876388] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [ 243.876393] XorgD 88019fc12dc0 0 2422 2180 0x0040 [ 243.876404] 8800dabfe1a0 0002 880194537fd8 880194537ba0 [ 243.876416] 8800dab9e22c 8800dabfe1a0 8800dab9e230 [ 243.876426] 813e2479 8800dab9e228 813e26a7 [ 243.876438] Call Trace: [ 243.876449] [813e2479] ? schedule+0x6f/0x7c [ 243.876459] [813e26a7] ? schedule_preempt_disabled+0x15/0x21 [ 243.876469] [813e3347] ? __ww_mutex_lock_slowpath+0xdf/0x1c2 [ 243.876480] [813e3446] ? __ww_mutex_lock+0x1c/0x93 [ 243.876541] [a050e70d] ? modeset_lock+0x8f/0xf2 [drm] [ 243.876632] [a09aa0b9] ? intel_get_load_detect_pipe+0x80/0x427 [i915] [ 243.876674] [a04fd42f] ? drm_ut_debug_printk+0x5e/0x63 [drm] [ 243.876771] [a09d4661] ? intel_tv_detect+0x115/0x43a [i915] [ 243.876783] [810608d9] ? preempt_count_sub+0xbf/0xca [ 243.876809] [a05d6f24] ? drm_helper_probe_single_connector_modes_merge_bits+0xc6/0x38d [drm_kms_helper] [ 243.876860] [a0505b5d] ? drm_mode_getconnector+0xf4/0x2ac [drm] [ 243.876900] [a04fa911] ? drm_ioctl+0x338/0x3c5 [drm] [ 243.876949] [a0505a69] ? drm_mode_getcrtc+0xb3/0xb3 [drm] [ 243.876961] [81167deb] ? fsnotify+0x314/0x35d [ 243.876973] [811487be] ? do_vfs_ioctl+0x379/0x431 [ 243.876983] [811488cc] ? SyS_ioctl+0x56/0x7c [ 243.876994] [813e5152] ? system_call_fastpath+0x12/0x17 i.e. it is a mutex deadlock inside tv detect. Daniel does that make sense? Botch locking rework for atomic. Fix is https://patchwork.kernel.org/patch/5861631/ and will land as soon as an affected user has provided a tested-by. Andrey, can you pls give this a spin? Thanks, Daniel -- Daniel Vetter Software Engineer, Intel Corporation +41 (0) 79 365 57 48 - http://blog.ffwll.ch -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
