| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAKMK7uFsYUYuvWu2tWNc6+soPJpsJt6pz-A5EePc9oF7fG6uAA@mail.gmail.com> Date: Thu, 4 Oct 2012 16:56:06 +0200 From: Daniel Vetter <daniel.vetter@...ll.ch> To: Miles Lane <miles.lane@...il.com> Cc: LKML <linux-kernel@...r.kernel.org>, Eric Anholt <eric@...olt.net> Subject: Re: 3.6.0+ (GIT) -- WARNING: at drivers/gpu/drm/i915/intel_display.c:1271 intel_disable_pipe+0xab/0x12e() -- plane B assertion failure, should be off on pipe B but is still active This should help: https://patchwork.kernel.org/patch/1436231/ It's not merged yet since it cause a black screen on resume on one of my really old machines. Issue isn't new at all, but the new modeset code is _much_ more anal about cross-checking the hw state with what we expect to be there. Thanks, Daniel On Thu, Oct 4, 2012 at 4:18 PM, Miles Lane <miles.lane@...il.com> wrote: > [ 4.266874] WARNING: at drivers/gpu/drm/i915/intel_display.c:1271 > intel_disable_pipe+0xab/0x12e() > [ 4.266877] Hardware name: UL50VT > [ 4.266880] plane B assertion failure, should be off on pipe B but > is still active > [ 4.266882] Modules linked in: > [ 4.266888] Pid: 1, comm: swapper/0 Not tainted 3.6.0+ #27 > [ 4.266891] Call Trace: > [ 4.266899] [<ffffffff8102dd26>] warn_slowpath_common+0x7e/0x97 > [ 4.266905] [<ffffffff8102ddd3>] warn_slowpath_fmt+0x41/0x43 > [ 4.266911] [<ffffffff8129404c>] intel_disable_pipe+0xab/0x12e > [ 4.266917] [<ffffffff812945d9>] i9xx_crtc_disable+0xd1/0x144 > [ 4.266923] [<ffffffff8129c112>] intel_modeset_setup_hw_state+0x438/0x69f > [ 4.266929] [<ffffffff8129c398>] intel_modeset_gem_init+0x1f/0x24 > [ 4.266936] [<ffffffff8127bf37>] i915_driver_load+0xada/0xcde > [ 4.266945] [<ffffffff812628f0>] drm_get_pci_dev+0x16d/0x266 > [ 4.266951] [<ffffffff8106bc63>] ? trace_hardirqs_on+0xd/0xf > [ 4.266957] [<ffffffff81454392>] i915_pci_probe+0x4d/0x57 > [ 4.266964] [<ffffffff811e4844>] local_pci_probe+0x5b/0xa2 > [ 4.266969] [<ffffffff811e494b>] pci_device_probe+0xc0/0xed > [ 4.266976] [<ffffffff8133bb44>] ? driver_probe_device+0x1b5/0x1b5 > [ 4.266981] [<ffffffff8133ba29>] driver_probe_device+0x9a/0x1b5 > [ 4.266987] [<ffffffff8133bb92>] __driver_attach+0x4e/0x6f > [ 4.266992] [<ffffffff8133a175>] bus_for_each_dev+0x52/0x84 > [ 4.266998] [<ffffffff8133b542>] driver_attach+0x19/0x1b > [ 4.267003] [<ffffffff8133b1e3>] bus_add_driver+0xf4/0x219 > [ 4.267009] [<ffffffff8133c0ef>] driver_register+0x8e/0x114 > [ 4.267014] [<ffffffff811e3d09>] __pci_register_driver+0x5a/0x5f > [ 4.267020] [<ffffffff81262a6a>] drm_pci_init+0x81/0xe7 > [ 4.267027] [<ffffffff81ac109d>] ? ttm_init+0x62/0x62 > [ 4.267033] [<ffffffff81ac1103>] i915_init+0x66/0x68 > [ 4.267039] [<ffffffff810001fa>] do_one_initcall+0x7a/0x130 > [ 4.267045] [<ffffffff81a97c3f>] kernel_init+0x10b/0x18f > [ 4.267051] [<ffffffff81a9752f>] ? do_early_param+0x8c/0x8c > [ 4.267058] [<ffffffff81471334>] kernel_thread_helper+0x4/0x10 > [ 4.267065] [<ffffffff8104f6a5>] ? finish_task_switch+0x38/0xb0 > [ 4.267070] [<ffffffff81000c71>] ? __switch_to+0x19c/0x426 > [ 4.267076] [<ffffffff8146b7a0>] ? retint_restore_args+0xe/0xe > [ 4.267082] [<ffffffff81a97b34>] ? start_kernel+0x3b3/0x3b3 > [ 4.267087] [<ffffffff81471330>] ? gs_change+0xb/0xb -- 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 majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists