git checkout 0414855fdc4a40da05221fc6062cccbc0c30f169 ls -a /kernel-tests/run-queue/kvm/i386-randconfig-r5-0307/linux-devel:devel-roam-i386-201403072151:0414855fdc4a40da05221fc6062cccbc0c30f169:bisect-linux5 2014-03-07-23:08:01 0414855fdc4a40da05221fc6062cccbc0c30f169 compiling 154 real 2679 user 220 sys 1877.05% cpu i386-randconfig-r5-0307 2014-03-07-23:11:00 detecting boot state 3.14.0-rc5... 6 17 20 SUCCESS bisect: good commit 0414855fdc4a40da05221fc6062cccbc0c30f169 git bisect start 05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0 0414855fdc4a40da05221fc6062cccbc0c30f169 -- /c/kernel-tests/linear-bisect: ["-b", "05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0", "-g", "0414855fdc4a40da05221fc6062cccbc0c30f169", "/c/kernel-tests/bisect-test-boot-failure.sh", "/kernel-tests/linux5/obj-bisect"] Bisecting: 558 revisions left to test after this (roughly 10 steps) [d6624f53631bba754e89f4d204c6248ee0d314f1] Merge 'dvdhrm/drm-log' into devel-roam-i386-201403072151 running /c/kernel-tests/bisect-test-boot-failure.sh /kernel-tests/linux5/obj-bisect ls -a /kernel-tests/run-queue/kvm/i386-randconfig-r5-0307/linux-devel:devel-roam-i386-201403072151:d6624f53631bba754e89f4d204c6248ee0d314f1:bisect-linux5 2014-03-07-23:14:08 d6624f53631bba754e89f4d204c6248ee0d314f1 compiling 75 real 357 user 36 sys 523.80% cpu i386-randconfig-r5-0307 2014-03-07-23:16:43 detecting boot state 3.14.0-rc5-00240-gd6624f5.. TEST FAILURE [ 14.330386] Write protecting the kernel text: 8824k [ 14.331900] Write protecting the kernel read-only data: 3472k [ 14.374062] random: init urandom read with 0 bits of entropy available [ 14.380039] BUG: sleeping function called from invalid context at /kernel-tests/linux5/kernel/locking/mutex.c:616 [ 14.380039] in_atomic(): 0, irqs_disabled(): 1, pid: 1, name: init [ 14.380039] no locks held by init/1. [ 14.380039] CPU: 1 PID: 1 Comm: init Not tainted 3.14.0-rc5-00240-gd6624f5 #103 [ 14.380039] 00000000 00000000 87c2ddd8 7988649c 00000001 87c2de00 7906d855 79b1f02c [ 14.380039] 00000000 00000001 00000001 87c1e29c 79c479a0 00000000 87c1e000 87c2de5c [ 14.380039] 7989232a 00000000 7fffffff fa2f2e3f 79b1a194 6c0a0100 ffff0006 7939d6d8 [ 14.380039] Call Trace: [ 14.380039] [<7988649c>] dump_stack+0x48/0x60 [ 14.380039] [<7906d855>] __might_sleep+0x105/0x110 [ 14.380039] [<7989232a>] mutex_lock_nested+0x2a/0x430 [ 14.380039] [<7939d6d8>] ? io_serial_in+0x8/0x20 [ 14.380039] [<7939e362>] ? wait_for_xmitr+0x22/0x90 [ 14.380039] [<79093b62>] ? do_raw_spin_unlock+0xb2/0xe0 [ 14.380039] [<793d7700>] ? drm_log_write+0x80/0xe0 [ 14.380039] [<793d7734>] drm_log_write+0xb4/0xe0 [ 14.380039] [<7939e4ca>] ? serial8250_console_write+0xfa/0x120 [ 14.380039] [<7939e4f0>] ? serial8250_console_write+0x120/0x120 [ 14.380039] [<793d7773>] dlog_con_write+0x13/0x20 [ 14.380039] [<79097af3>] call_console_drivers.constprop.8+0x133/0x1b0 [ 14.380039] [<790980c0>] console_unlock+0x330/0x4e0 [ 14.380039] [<790988ba>] vprintk_emit+0x64a/0x680 [ 14.380039] [<79882ae0>] printk+0x3d/0x3f [ 14.380039] [<793a519b>] urandom_read+0x6b/0x110 [ 14.380039] [<793a5130>] ? random_read+0x1c0/0x1c0 [ 14.380039] [<7914683b>] vfs_read+0xbb/0x150 [ 14.380039] [<79146f59>] SyS_read+0x49/0x80 [ 14.380039] [<7989cc8a>] sysenter_do_call+0x12/0x3c /bin/sh: /proc/self/fd/9: No such file or directory /bin/sh: /proc/self/fd/9: No such file or directory [ 14.832654] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3 /kernel/i386-randconfig-r5-0307/d6624f53631bba754e89f4d204c6248ee0d314f1/dmesg-quantal-snb-25:20140307231713:i386-randconfig-r5-0307:: /kernel/i386-randconfig-r5-0307/d6624f53631bba754e89f4d204c6248ee0d314f1/dmesg-quantal-snb-44:20140307231714:i386-randconfig-r5-0307:: /kernel/i386-randconfig-r5-0307/d6624f53631bba754e89f4d204c6248ee0d314f1/dmesg-quantal-snb-47:20140307231720:i386-randconfig-r5-0307:: /kernel/i386-randconfig-r5-0307/d6624f53631bba754e89f4d204c6248ee0d314f1/dmesg-quantal-bens-4:20140307231729:i386-randconfig-r5-0307:3.14.0-rc5-00240-gd6624f5:103 /kernel/i386-randconfig-r5-0307/d6624f53631bba754e89f4d204c6248ee0d314f1/dmesg-quantal-snb-25:20140307231733:i386-randconfig-r5-0307:: /kernel/i386-randconfig-r5-0307/d6624f53631bba754e89f4d204c6248ee0d314f1/dmesg-quantal-snb-44:20140307231739:i386-randconfig-r5-0307:: /kernel/i386-randconfig-r5-0307/d6624f53631bba754e89f4d204c6248ee0d314f1/dmesg-quantal-snb-47:20140307231740:i386-randconfig-r5-0307:: /kernel/i386-randconfig-r5-0307/d6624f53631bba754e89f4d204c6248ee0d314f1/dmesg-quantal-snb-4:20140307231740:i386-randconfig-r5-0307:: 0:8:8 all_good:bad:all_bad boots 2014-03-07 23:17:45 REPEAT COUNT: 20 # /kernel-tests/linux5/obj-bisect/.repeat Bisecting: 240 revisions left to test after this (roughly 8 steps) [5bbe2fa5f7e2c75a85348e0ae4a1cca7d2a0e4a8] 0day base guard for 'devel-roam-i386-201403072151' running /c/kernel-tests/bisect-test-boot-failure.sh /kernel-tests/linux5/obj-bisect ls -a /kernel-tests/run-queue/kvm/i386-randconfig-r5-0307/linux-devel:devel-roam-i386-201403072151:5bbe2fa5f7e2c75a85348e0ae4a1cca7d2a0e4a8:bisect-linux5 2014-03-07-23:17:46 5bbe2fa5f7e2c75a85348e0ae4a1cca7d2a0e4a8 compiling 46 real 366 user 38 sys 871.29% cpu i386-randconfig-r5-0307 2014-03-07-23:18:53 detecting boot state 3.14.0-rc5-00001-g5bbe2fa... 5 12 17 20 SUCCESS Bisecting: 239 revisions left to test after this (roughly 8 steps) [b82a37f7f077567a7f744a98040d2e566632e385] Merge 'gfs2/master' into devel-roam-i386-201403072151 running /c/kernel-tests/bisect-test-boot-failure.sh /kernel-tests/linux5/obj-bisect ls -a /kernel-tests/run-queue/kvm/i386-randconfig-r5-0307/linux-devel:devel-roam-i386-201403072151:b82a37f7f077567a7f744a98040d2e566632e385:bisect-linux5 2014-03-07-23:22:25 b82a37f7f077567a7f744a98040d2e566632e385 compiling 39 real 195 user 26 sys 562.38% cpu i386-randconfig-r5-0307 2014-03-07-23:23:30 detecting boot state 3.14.0-rc5-00022-gb82a37f7... 2 16 20 SUCCESS linear-bisect: bad branch may be dvdhrm/drm-log linear-bisect: handle over to git bisect linear-bisect: git bisect start d6624f53631bba754e89f4d204c6248ee0d314f1 b82a37f7f077567a7f744a98040d2e566632e385 -- Previous HEAD position was b82a37f7... Merge 'gfs2/master' into devel-roam-i386-201403072151 HEAD is now at c236e3c... Merge 'tip/x86/efi' into devel-hourly-2014030612 Bisecting: 108 revisions left to test after this (roughly 7 steps) [e81ca8076832ed2197a6bdb05dbc769dad159f7d] drm/i915: We implement WaDisableRCCUnitClockGating:snb linear-bisect: git bisect run /c/kernel-tests/bisect-test-boot-failure.sh /kernel-tests/linux5/obj-bisect running /c/kernel-tests/bisect-test-boot-failure.sh /kernel-tests/linux5/obj-bisect ls -a /kernel-tests/run-queue/kvm/i386-randconfig-r5-0307/linux-devel:devel-roam-i386-201403072151:e81ca8076832ed2197a6bdb05dbc769dad159f7d:bisect-linux5 2014-03-07-23:27:15 e81ca8076832ed2197a6bdb05dbc769dad159f7d compiling 175 real 2654 user 227 sys 1638.26% cpu i386-randconfig-r5-0307 2014-03-07-23:31:30 detecting boot state 3.13.0-rc8-00720-ge81ca80... 2 12 20 SUCCESS Bisecting: 54 revisions left to test after this (roughly 6 steps) [c1874ed7c987664176bd00301f844e91609fe535] drm/i915: factor out valleyview_pipestat_irq_handler running /c/kernel-tests/bisect-test-boot-failure.sh /kernel-tests/linux5/obj-bisect ls -a /kernel-tests/run-queue/kvm/i386-randconfig-r5-0307/linux-devel:devel-roam-i386-201403072151:c1874ed7c987664176bd00301f844e91609fe535:bisect-linux5 2014-03-07-23:34:39 c1874ed7c987664176bd00301f844e91609fe535 compiling 248 real 2663 user 228 sys 1165.80% cpu i386-randconfig-r5-0307 2014-03-07-23:40:38 detecting boot state 3.13.0-00880-gc1874ed... 2........... 3 5 8 11 12. 14 16. 17.. 19 20 SUCCESS Bisecting: 22 revisions left to test after this (roughly 5 steps) [c48cdd23ea5006c377b670bc3056fa7b63f92574] Merge branch 'tda998x-devel' of git://ftp.arm.linux.org.uk/~rmk/linux-cubox into drm-next running /c/kernel-tests/bisect-test-boot-failure.sh /kernel-tests/linux5/obj-bisect ls -a /kernel-tests/run-queue/kvm/i386-randconfig-r5-0307/linux-devel:devel-roam-i386-201403072151:c48cdd23ea5006c377b670bc3056fa7b63f92574:bisect-linux5 2014-03-07-23:55:11 c48cdd23ea5006c377b670bc3056fa7b63f92574 compiling 295 real 2702 user 219 sys 990.62% cpu i386-randconfig-r5-0307 2014-03-08-00:00:40 detecting boot state 3.14.0-rc4-00195-gc48cdd2....................... 1. 2... 3.... 4 5...... 6.. 8 9. 12.. 16 19.. 20 SUCCESS Bisecting: 11 revisions left to test after this (roughly 4 steps) [ee35b0024a9d85f9c8745e0481c09d65f2507bd3] drm/radeon: enable vce dpm on CI running /c/kernel-tests/bisect-test-boot-failure.sh /kernel-tests/linux5/obj-bisect ls -a /kernel-tests/run-queue/kvm/i386-randconfig-r5-0307/linux-devel:devel-roam-i386-201403072151:ee35b0024a9d85f9c8745e0481c09d65f2507bd3:bisect-linux5 2014-03-08-00:28:43 ee35b0024a9d85f9c8745e0481c09d65f2507bd3 compiling 170 real 2728 user 224 sys 1731.29% cpu i386-randconfig-r5-0307 2014-03-08-00:31:48 ee35b0024a9d85f9c8745e0481c09d65f2507bd3 SKIP BROKEN BUILD Check erros in /kernel-tests/linux5/obj-bisect and /tmp/kernel/i386-randconfig-r5-0307/ee35b0024a9d85f9c8745e0481c09d65f2507bd3 Bisecting: 10 revisions left to test after this (roughly 4 steps) [4233290519c779e44a01816cf825f6df067a0886] drm/radeon: add vce dpm support for KV/KB running /c/kernel-tests/bisect-test-boot-failure.sh /kernel-tests/linux5/obj-bisect ls -a /kernel-tests/run-queue/kvm/i386-randconfig-r5-0307/linux-devel:devel-roam-i386-201403072151:4233290519c779e44a01816cf825f6df067a0886:bisect-linux5 2014-03-08-00:31:49 4233290519c779e44a01816cf825f6df067a0886 compiling 35 real 73 user 9 sys 231.68% cpu i386-randconfig-r5-0307 2014-03-08-00:32:36 4233290519c779e44a01816cf825f6df067a0886 SKIP BROKEN BUILD Check erros in /kernel-tests/linux5/obj-bisect and /tmp/kernel/i386-randconfig-r5-0307/4233290519c779e44a01816cf825f6df067a0886 Bisecting: 10 revisions left to test after this (roughly 4 steps) [4d538b79197901fecc42e746d515d07fd1089b62] Merge branch 'drm-next-3.15' of git://people.freedesktop.org/~deathsimple/linux into drm-next running /c/kernel-tests/bisect-test-boot-failure.sh /kernel-tests/linux5/obj-bisect ls -a /kernel-tests/run-queue/kvm/i386-randconfig-r5-0307/linux-devel:devel-roam-i386-201403072151:4d538b79197901fecc42e746d515d07fd1089b62:bisect-linux5 2014-03-08-00:32:37 4d538b79197901fecc42e746d515d07fd1089b62 compiling 172 real 2894 user 249 sys 1819.29% cpu i386-randconfig-r5-0307 2014-03-08-00:35:53 detecting boot state 3.14.0-rc4-00215-g4d538b7... 2 8 14 18 20 SUCCESS Bisecting: 0 revisions left to test after this (roughly 1 step) [06bdc9aa3cd3a045b4a94bdc4c6c582338cf7992] drm: add kernel-log renderer running /c/kernel-tests/bisect-test-boot-failure.sh /kernel-tests/linux5/obj-bisect ls -a /kernel-tests/run-queue/kvm/i386-randconfig-r5-0307/linux-devel:devel-roam-i386-201403072151:06bdc9aa3cd3a045b4a94bdc4c6c582338cf7992:bisect-linux5 2014-03-08-00:39:54 06bdc9aa3cd3a045b4a94bdc4c6c582338cf7992 compiling 35 real 205 user 27 sys 664.00% cpu i386-randconfig-r5-0307 2014-03-08-00:40:47 detecting boot state 3.14.0-rc4-00217-g06bdc9a.. TEST FAILURE [ 15.183004] Write protecting the kernel text: 8824k [ 15.184326] Write protecting the kernel read-only data: 3472k [ 15.200494] random: init urandom read with 1 bits of entropy available [ 15.201415] BUG: sleeping function called from invalid context at /kernel-tests/linux5/kernel/locking/mutex.c:616 [ 15.201416] in_atomic(): 0, irqs_disabled(): 1, pid: 1, name: init [ 15.201418] no locks held by init/1. [ 15.201425] CPU: 1 PID: 1 Comm: init Not tainted 3.14.0-rc4-00217-g06bdc9a #112 [ 15.201433] 00000000 00000000 84023dd8 7988648c 00000001 84023e00 7906d825 79b1f01c [ 15.201439] 00000000 00000001 00000001 8401e29c 79c479a0 00000000 8401e000 84023e5c [ 15.201445] 7989231a 00000000 7fffffff fa2f2e3f 79b1a184 6c0a0100 ffff0006 7939d6c8 [ 15.201447] Call Trace: [ 15.201458] [<7988648c>] dump_stack+0x48/0x60 [ 15.201467] [<7906d825>] __might_sleep+0x105/0x110 [ 15.201473] [<7989231a>] mutex_lock_nested+0x2a/0x430 [ 15.201488] [<7939d6c8>] ? io_serial_in+0x8/0x20 [ 15.201492] [<7939e352>] ? wait_for_xmitr+0x22/0x90 [ 15.201500] [<79093b32>] ? do_raw_spin_unlock+0xb2/0xe0 [ 15.201513] [<793d7700>] ? drm_log_write+0x90/0xe0 [ 15.201516] [<793d7724>] drm_log_write+0xb4/0xe0 [ 15.201520] [<7939e4ba>] ? serial8250_console_write+0xfa/0x120 [ 15.201524] [<7939e4e0>] ? serial8250_console_write+0x120/0x120 [ 15.201527] [<793d7763>] dlog_con_write+0x13/0x20 [ 15.201531] [<79097ac3>] call_console_drivers.constprop.8+0x133/0x1b0 [ 15.201535] [<79098090>] console_unlock+0x330/0x4e0 [ 15.201539] [<7909888a>] vprintk_emit+0x64a/0x680 [ 15.201544] [<79882ad0>] printk+0x3d/0x3f [ 15.201549] [<793a518b>] urandom_read+0x6b/0x110 [ 15.201553] [<793a5120>] ? random_read+0x1c0/0x1c0 [ 15.201576] [<7914683b>] vfs_read+0xbb/0x150 [ 15.201580] [<79146f59>] SyS_read+0x49/0x80 [ 15.201585] [<7989cc8a>] sysenter_do_call+0x12/0x3c /bin/sh: /proc/self/fd/9: No such file or directory /bin/sh: /proc/self/fd/9: No such file or directory /bin/sh: /proc/self/fd/9: No such file or directory /kernel/i386-randconfig-r5-0307/06bdc9aa3cd3a045b4a94bdc4c6c582338cf7992/dmesg-quantal-snb-16:20140308004126:i386-randconfig-r5-0307:: 0:1:1 all_good:bad:all_bad boots 2014-03-08 00:41:48 REPEAT COUNT: 20 # /kernel-tests/linux5/obj-bisect/.repeat Bisecting: 0 revisions left to test after this (roughly 0 steps) [32afb1337bdffd1df2ac4ae749eace37528c747f] lib: remove FBCON dependency for fonts running /c/kernel-tests/bisect-test-boot-failure.sh /kernel-tests/linux5/obj-bisect ls -a /kernel-tests/run-queue/kvm/i386-randconfig-r5-0307/linux-devel:devel-roam-i386-201403072151:32afb1337bdffd1df2ac4ae749eace37528c747f:bisect-linux5 2014-03-08-00:41:49 32afb1337bdffd1df2ac4ae749eace37528c747f compiling 39 real 204 user 28 sys 594.24% cpu i386-randconfig-r5-0307 2014-03-08-00:42:50 detecting boot state 3.14.0-rc4-00216-g32afb13... 2 4 5......... 6. 8 11 12. 13 17 18 19 20 SUCCESS 06bdc9aa3cd3a045b4a94bdc4c6c582338cf7992 is the first bad commit commit 06bdc9aa3cd3a045b4a94bdc4c6c582338cf7992 Author: David Herrmann Date: Wed Mar 5 17:34:49 2014 +0100 drm: add kernel-log renderer On modern linux user-space, the VT subsystem is no longer needed for system consoles. Although most DEs will fail if VTs are disabled, there are several gfx-systems that support this mode. Especially the lower system stack has been extended to work without VTs. However, there is one major drawback if VTs are disabled: You don't get oops/panic-screens nor early boot-debugging. The VT subsystem registers a console-driver, thus displays the kernel log and oops/panic screens in those situations. This patch introduces a fallback for CONFIG_VT=n. A new DRM-Log core is added. At its heart, DRM-Log maintains a log-buffer of kernel-log messages. It registers a console-driver and pushes new messages into this buffer whenever they appear. The size of the log-buffer can be changed via drm_log_ensure_size(). Initially, a suitable buffer is chosen, but whenever drivers register high-res CRTCs, they ought to increase that buffer to guarantee there's always enough data to render the whole screen. This log-buffer is managed at the character-level, not pixel-level. It is shared across all users, supports parallel, atomic readers and writers and supports seamless resizing. Additionally to the log-buffer handling, a generic software renderer is introduced. drm_log_draw() renders the current log-buffer into any memory-mapped framebuffer you want. Note that it supports splitting lines in case your framebuffer is smaller than the log-buffer, but also merging continuation lines in case your framebuffer is wider. This allows rendering an 80x25 log-buffer in full-width on high-res displays. On the other hand, 800x250 log-buffers can be rendered without information loss (apart from a shorter backlog) on low-res displays. No high-level API is introduced, yet. So for now drivers need to decide when and where to render on their own. A generic interface with panic-handlers, scheduled redrawing and automatic modesetting will be added in follow-ups. A few more notes: - This is for *debugging*, and for debugging only! You can use this renderer to get a kernel-log onto your framebuffers. However, the renderer is horribly slow! There is no intention to speed it up. No-one cares whether it takes 500ms to render your panic-screen! - If you enable the log-renderer for a continous boot-log, you're supposed to redraw on vblanks. The renderer does not support damage-tracking as each new-line causes a scroll-up, anyway. - The renderer works bottom-up and right-to-left. This is required to avoid pre-calculating log sizes. - The renderer supports multiple columns. This is quite handy on high-res screens where you can get bigger backlogs this way. Usually 80% of the screen are black. Now you can reuse this for the next log-column. - The renderer supports integer-scaling for high-DPI screens. Instead of using high-res fonts we simply scale fonts. This is *not* intended to increase resolution but rather to make the log readable. - I have some wrappers to use this in user-space. I did several tests with resizing and different buffer-sizes and valgrind didn't complain. Results looked all fine. - The renderer supports *any* RGB target, from 8bit to 32bit with big-endian and little-endian support. The related pixel-renderer will probably never win a beauty-contest, but it works.. Again, who cares for debug-log rendering speed? - If you want a normal boot-log, use a user-space log-renderer (like experimential systemd-er (no merged, yet)). They can render with proper speed, can do hw-scrolling and more. Or: Enable VTs! Seriously, if you want all the VT features, use VTs! I will not tell you to disable them. On a last note: With this (and the high-level integration) in place, you can easily disable CONFIG_FB, CONFIG_VT and CONFIG_FRAMEBUFFER_CONSOLE. Combined with a proper user-space system-console, you will end up with more features, less bugs and definitely some happy kernel maintainers. Signed-off-by: David Herrmann :040000 040000 8ff60dba3c1a10f2477509ec1583862c7b5567da 29ceee0af250aaf0d1a3b7e4be307f93bf816b73 M drivers :040000 040000 8b90eb17484524e3b508bacf15c424781f112544 b98cbb6de1c9fd2d046f749a4b16836ae2a90ae3 M include bisect run success ls -a /kernel-tests/run-queue/kvm/i386-randconfig-r5-0307/linux-devel:devel-roam-i386-201403072151:32afb1337bdffd1df2ac4ae749eace37528c747f:bisect-linux5 2014-03-08-00:55:51 32afb1337bdffd1df2ac4ae749eace37528c747f reuse /kernel/i386-randconfig-r5-0307/32afb1337bdffd1df2ac4ae749eace37528c747f/vmlinuz-3.14.0-rc4-00216-g32afb13 2014-03-08-00:55:51 detecting boot state .................. 21 46 60 SUCCESS ls -a /kernel-tests/run-queue/kvm/i386-randconfig-r5-0307/linux-devel:devel-roam-i386-201403072151:05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0:bisect-linux5 TEST FAILURE [ 3.257076] ... PIC ELCR: 0c00 [ 3.250016] printing local APIC contents on CPU#0/0: [ 3.250016] ------------[ cut here ]------------ [ 3.250016] WARNING: CPU: 0 PID: 39 at kernel/locking/mutex.c:516 mutex_lock_nested+0xc7/0x430() [ 3.250016] DEBUG_LOCKS_WARN_ON(in_interrupt()) [ 3.250016] Modules linked in: [ 3.250016] CPU: 0 PID: 39 Comm: rb_consumer Not tainted 3.14.0-rc5-00558-g05ffd9c #230 [ 3.250016] 00000000 00000000 87853cb0 798860ec 87853cf0 87853ce0 790414ee 79b1a074 [ 3.250016] 87853d0c 00000027 79b1fbf8 00000204 79892017 79892017 79c499a0 00000001 [ 3.250016] 83f86000 87853cf8 79041543 00000009 87853cf0 79b1a074 87853d0c 87853d54 [ 3.250016] Call Trace: [ 3.250016] [<798860ec>] dump_stack+0x48/0x60 [ 3.250016] [<790414ee>] warn_slowpath_common+0x7e/0xa0 [ 3.250016] [<79892017>] ? mutex_lock_nested+0xc7/0x430 [ 3.250016] [<79892017>] ? mutex_lock_nested+0xc7/0x430 [ 3.250016] [<79041543>] warn_slowpath_fmt+0x33/0x40 [ 3.250016] [<79892017>] mutex_lock_nested+0xc7/0x430 [ 3.250016] [<7939d718>] ? io_serial_in+0x8/0x20 [ 3.250016] [<7939e3a2>] ? wait_for_xmitr+0x22/0x90 [ 3.250016] [<793d7744>] ? drm_log_write+0xb4/0xe0 [ 3.250016] [<79093ac2>] ? do_raw_spin_unlock+0xb2/0xe0 [ 3.250016] [<793d7700>] ? drm_log_write+0x70/0xe0 [ 3.250016] [<793d7744>] drm_log_write+0xb4/0xe0 [ 3.250016] [<7939e50a>] ? serial8250_console_write+0xfa/0x120 [ 3.250016] [<7939e530>] ? serial8250_console_write+0x120/0x120 [ 3.250016] [<793d7783>] dlog_con_write+0x13/0x20 [ 3.250016] [<79097a53>] call_console_drivers.constprop.8+0x133/0x1b0 [ 3.250016] [<79098018>] console_unlock+0x328/0x4c0 [ 3.250016] [<790987fa>] vprintk_emit+0x64a/0x680 [ 3.250016] [<79882730>] printk+0x3d/0x3f [ 3.250016] [<79d02f26>] print_local_APIC+0x29/0x3e6 [ 3.250016] [<790b8510>] generic_smp_call_function_single_interrupt+0xe0/0x230 [ 3.250016] [<7902aa35>] smp_call_function_single_interrupt+0x25/0x40 [ 3.250016] [<798966da>] call_function_single_interrupt+0x32/0x38 [ 3.250016] [<7909007b>] ? debug_show_all_locks+0xfb/0x190 [ 3.250016] [<790d90aa>] ? ring_buffer_consume+0x11a/0x150 [ 3.250016] [<790da6a3>] ring_buffer_consumer_thread+0x83/0x500 [ 3.250016] [<790da620>] ? ring_buffer_producer_thread+0x5a0/0x5a0 [ 3.250016] [<79064223>] kthread+0xb3/0xc0 [ 3.250016] [<7989c837>] ret_from_kernel_thread+0x1b/0x28 [ 3.250016] [<79064170>] ? __kthread_unpark+0x50/0x50 [ 3.250016] ---[ end trace ba17ce24efaa8896 ]--- [ 3.250016] ... APIC ID: 00000000 (0) /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-yocto-waimea-14:20140307231026:i386-randconfig-r5-0307:3.14.0-rc5-00558-g05ffd9c:230 /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-quantal-athens-43:20140307230858:i386-randconfig-r5-0307:3.14.0-rc5-00558-g05ffd9c:230 /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-yocto-xian-16:20140307222306:i386-randconfig-r5-0307:3.14.0-rc5-00558-g05ffd9c:230 /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-yocto-snb-32:20140307222331:i386-randconfig-r5-0307:: /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-quantal-snb-25:20140307222347:i386-randconfig-r5-0307:: /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-yocto-athens-11:20140307231009:i386-randconfig-r5-0307:3.14.0-rc5-00558-g05ffd9c:230 /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-yocto-athens-37:20140307230754:i386-randconfig-r5-0307:3.14.0-rc5-00558-g05ffd9c:230 /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-yocto-xian-16:20140307222135:i386-randconfig-r5-0307:3.14.0-rc5-00558-g05ffd9c:230 /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-yocto-roam-22:20140307230751:i386-randconfig-r5-0307:3.14.0-rc5-00558-g05ffd9c:230 /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-yocto-snb-17:20140307222330:i386-randconfig-r5-0307:: /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-yocto-xian-28:20140307222209:i386-randconfig-r5-0307:3.14.0-rc5-00558-g05ffd9c:230 /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-yocto-xian-47:20140307222313:i386-randconfig-r5-0307:3.14.0-rc5-00558-g05ffd9c:230 /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-quantal-inn-30:20140307230759:i386-randconfig-r5-0307:: /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-yocto-xian-45:20140307230808:i386-randconfig-r5-0307:3.14.0-rc5-00558-g05ffd9c:230 /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-yocto-xbm-1:20140307221733:i386-randconfig-r5-0307:3.14.0-rc5-00558-g05ffd9c:230 /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-yocto-waimea-10:20140307230958:i386-randconfig-r5-0307:3.14.0-rc5-00558-g05ffd9c:230 /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-quantal-snb-16:20140307222321:i386-randconfig-r5-0307:: /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-yocto-roam-42:20140307230756:i386-randconfig-r5-0307:3.14.0-rc5-00558-g05ffd9c:230 /kernel/i386-randconfig-r5-0307/05ffd9cb67c1bc9a4b4e3007df326e4e6f2d7db0/dmesg-yocto-stoakley-7:20140307230907:i386-randconfig-r5-0307:3.14.0-rc5-00558-g05ffd9c:230 0:19:19 all_good:bad:all_bad boots [detached HEAD 6c0eb64] Revert "drm: add kernel-log renderer" Committer: Wu Fengguang Your name and email address were configured automatically based on your username and hostname. Please check that they are accurate. You can suppress this message by setting them explicitly: git config --global user.name "Your Name" git config --global user.email you@example.com After doing this, you may fix the identity used for this commit with: git commit --amend --reset-author 5 files changed, 1252 deletions(-) delete mode 100644 drivers/gpu/drm/drm_log.c delete mode 100644 include/drm/drm_log.h ls -a /kernel-tests/run-queue/kvm/i386-randconfig-r5-0307/linux-devel:devel-roam-i386-201403072151:6c0eb6436ff95fbd405fd8ac292626247b1e0f96:bisect-linux5 2014-03-08-01:06:56 6c0eb6436ff95fbd405fd8ac292626247b1e0f96 compiling 2014-03-08-01:15:44 detecting boot state 3.14.0-rc5-00559-g6c0eb64............... 4 14 24 34 41 47 56 60 SUCCESS ========= upstream ========= Warning: you are leaving 1 commit behind, not connected to any of your branches: 6c0eb64 Revert "drm: add kernel-log renderer" If you want to keep them by creating a new branch, this may be a good time to do so with: git branch new_branch_name 6c0eb64 HEAD is now at c3bebc7... Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net ls -a /kernel-tests/run-queue/kvm/i386-randconfig-r5-0307/linux-devel:devel-roam-i386-201403072151:c3bebc71c4bcdafa24b506adf0c1de3c1f77e2e0:bisect-linux5 2014-03-08-01:27:22 c3bebc71c4bcdafa24b506adf0c1de3c1f77e2e0 compiling 2014-03-08-01:37:08 detecting boot state 3.14.0-rc5-00185-gc3bebc7.................................................................................................. 3 16 34 51 60 SUCCESS ========= linux-next ========= Previous HEAD position was c3bebc7... Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net HEAD is now at 1b0a7e3... Add linux-next specific files for 20140307 ls -a /kernel-tests/run-queue/kvm/i386-randconfig-r5-0307/linux-devel:devel-roam-i386-201403072151:1b0a7e3263168a06d3858798e48c5a21d1c78d3c:bisect-linux5 2014-03-08-02:28:42 1b0a7e3263168a06d3858798e48c5a21d1c78d3c compiling 2014-03-08-02:34:27 detecting boot state 3.14.0-rc5-next-20140307.. 2 9 16 24 33 36 41 50 53 60 SUCCESS