CI_DRM_3295 fi-bxt-dsi igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c first dmesg: <5>[ 39.739396] owatch: Using watchdog device /dev/watchdog0 <5>[ 39.740024] owatch: Watchdog /dev/watchdog0 is a software watchdog <5>[ 39.741998] owatch: timeout for /dev/watchdog0 set to 100 (requested 100) last dmesg: <7>[ 455.347495] [drm:gen9_enable_dc5 [i915]] Enabling DC5 <7>[ 455.347535] [drm:gen9_set_dc_state [i915]] Setting DC state from 00 to 01 <7>[ 455.348083] [drm:intel_power_well_disable [i915]] disabling always-on then "stray" run.log: [244/289] skip: 26, pass: 218 | FATAL: command execution failed java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2638) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3113) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:853) at java.io.ObjectInputStream.<init>(ObjectInputStream.java:349) at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:59) Caused: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:73) Caused: java.io.IOException: Backing channel 'fi-bxt-dsi' is disconnected. at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:193) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:260) at com.sun.proxy.$Proxy65.isAlive(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1138) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1130) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:736) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:496) at hudson.model.Run.execute(Run.java:1724) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:421) https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3295/fi-bxt-dsi/igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c.html Note: pm_runtime was broken during this run see bug 103522
This is interesting... My first question is: Did you recently upgraded the BIOS on this BXT? But I'm interested because it also happened on happened on drm-intel-fixes for 4.14-rc6 after applying: dc35b1129cc3 drm/i915: Hold rcu_read_lock when iterating over the radixtree (vma idr) 23e873389d84 drm/i915: Hold rcu_read_lock when iterating over the radixtree (objects) 7c838e2a9be5 drm/i915/edp: read edp display control registers unconditionally 8777b927b92c drm/i915: Do not rely on wm preservation for ILK watermarks 713946d16f45 drm/i915: Cancel the modeset retry work during modeset cleanup Is this 100% reproducible? I wonder if there is a quick way to bisect between these 5 patches at least. Also adding relevant people to cc here in case someone has any idea. Thanks, Rodrigo.
s/4.14-rc6/4.14-rc7. I meant that these patches are applied on top of 4.14-rc7 queued for 4.14-rc8.
I think no BIOS update was done, but Tomi to say for sure.
(In reply to Rodrigo Vivi from comment #1) > > Is this 100% reproducible? I wonder if there is a quick way to bisect between > these 5 patches at least. > If you check https://intel-gfx-ci.01.org/tree/drm-tip/ click on fi-bxt-dsi on: https://intel-gfx-ci.01.org/tree/drm-tip/fi-bxt-dsi.html you will see that this has only happened once since CI_DRM_3218.
To my knowledge, the BIOS for this machine has not been changed after it was added to the farm. Note that the BIOS version and settings have been handpicked and -tuned to support the DSI panel by Mika Kahola.
Last seen 2017-10-30 / 129 runs ago
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.