← Back to team overview

kernel-packages team mailing list archive

  1. kernel-packages team
  2. Mailing list archive
  3. Message #41516

[Bug 1261308] Re: Intel ivy bridge crash on a CI machine executing autopilot tests

  Thread Previous • Date Previous • • Thread Next 
** Tags removed: kernel-key

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1261308

Title:
  Intel ivy bridge crash on a CI machine executing autopilot tests

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  A following crash was gotten in CI when running autopilot tests:

  /var/local/autopilot/autopilot.log: 06:25:06.559 DEBUG globals:155 - Starting: ['/usr/bin/recordmydesktop', '--fps=6', '--no-wm-check', '--no-sound', '--no-frame', '-o', '/var/local/autopilot//videos/autopilot.tests.functional.test_input_stack.TouchGesturesTests.test_pinch_gesture.ogv']
  /var/local/autopilot/autopilot.log: 06:25:06.569 INFO __init__:162 - Launching process: ['/usr/bin/qmlscene', '-qt=qt5', '-testability', '/tmp/tmpyErdkz.qml']
  /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22506.717922] kernel BUG at /build/buildd/linux-3.12.0/drivers/gpu/drm/i915/i915_gem.c:4839!
  /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22506.736780] Modules linked in: bluetooth veth squashfs aufs nls_utf8 isofs xt_CHECKSUM xt_tcpudp iptable_mangle ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc iptable_filter ip_tables x_tables x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crc32_pclmul aesni_intel aes_i586 xts lrw snd_hda_codec_hdmi gf128mul snd_hda_codec_realtek ablk_helper cryptd i915 drm_kms_helper snd_hda_intel snd_hda_codec drm snd_hwdep snd_pcm snd_page_alloc i2c_algo_bit mxm_wmi mei_me snd_timer snd mei soundcore psmouse serio_raw joydev lpc_ich microcode wmi mac_hid video lp parport hid_generic usbhid hid e1000e ahci ptp libahci pps_core
  /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22506.822345] Hardware name:                  /DZ77BH-55K, BIOS BHZ7710H.86A.0097.2012.1228.1346 12/28/2012
  /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22506.851440] EIP: 0060:[<f901d776>] EFLAGS: 00210246 CPU: 2
  /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22506.880754] EAX: e6b90270 EBX: e6b90270 ECX: ed4b4000 EDX: ed4b55e0
  /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22506.910940]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22506.941836] Stack:
  /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22506.973256]  e8921c00 00000000 00000000 00000000 000000b4 000000c0 e6b90294 00000000
  /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22507.005758] Call Trace:
  /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22507.037812]  [<c130a8ec>] ? _copy_from_user+0x2c/0x40
  /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22507.070637]  [<f9024990>] ? i915_gem_execbuffer+0x560/0x560 [i915]
  /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22507.104147]  [<f9024990>] ? i915_gem_execbuffer+0x560/0x560 [i915]
  /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22507.137652]  [<f8e2c430>] ? drm_copy_field+0x70/0x70 [drm]
  /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22507.171153]  [<c16561af>] ? __do_page_fault+0x24f/0x530
  /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22507.204938]  [<c11826c0>] SyS_ioctl+0x60/0x80
  /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22507.238719] Code: 39 50 f4 8d 48 cc 75 0a eb 1b 8d 76 00 39 50 f4 74 13 8b 41 34 39 c3 8d 48 cc 75 f1 b8 ff ff ff ff 5b 5d c3 90 8b 41 18 5b 5d c3 <0f> 0b 90 8d b4 26 00 00 00 00 55 89 e5 56 53 3e 8d 74 26 00 8b
  /var/log/syslog: Dec 16 06:25:07 trusty-i386-20131216-0008 kernel: [22507.367196] ---[ end trace d36900663c323dfa ]---
  /var/local/autopilot/autopilot.log: 06:25:33.001 ERROR proxies:410 - Introspect error on :1.180:/com/canonical/Autopilot/Introspection: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
  /var/local/autopilot/autopilot.log: 06:25:33.001 DEBUG proxies:413 - Executing introspect queue due to error
  /home/ubuntu/.cache/upstart/gnome-session.log: WARN  2013-12-16 06:25:32 unity <unknown>:0 Failed to fetch xid: Timeout was reached
  /home/ubuntu/.cache/upstart/gnome-session.log: WARN  2013-12-16 06:25:33 unity <unknown>:0 Failed to fetch type: Timeout was reached
  /home/ubuntu/.cache/upstart/gnome-session.log: WARN  2013-12-16 06:25:33 unity <unknown>:0 Failed to fetch monitor: Timeout was reached
  /home/ubuntu/.cache/upstart/gnome-session.log: WARN  2013-12-16 06:25:34 unity <unknown>:0 Failed to fetch maximized state: Timeout was reached
  /home/ubuntu/.cache/upstart/gnome-session.log: WARN  2013-12-16 06:25:34 unity <unknown>:0 Failed to fetch xid: Timeout was reached

  The machine in question - qa-intel-4000 - is experiencing this crasher
  a lot, with both current kernel (3.12.0-7-generic) and the previous
  update (3.12.0-5-generic).

  An URL to full log with 3.12.0-7-generic: http://q-jenkins.ubuntu-
  ci:8080/job/autopilot-trusty-daily_release/936/label=qa-
  intel-4000/consoleText and to 3.12.0-5-generic http://q-jenkins
  .ubuntu-ci:8080/job/autopilot-trusty-daily_release/label=qa-
  intel-4000/948/console

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261308/+subscriptions

References

  Thread Previous • Date Previous • • Thread Next