Ubiquity freezes during nfs-based desktop install from recent live destkop images on physical hardware

[Max Brustkern]

I'm attempting to do automated installs of raring live desktop images over a network on physical machines using a combination of cobbler and NFS. Since December 20, these installs have failed on i386 and amd64. DI installs from current server images work, and old images work fine for ubiquity installs. At some point during the installation, video stops updating. I started an install with an active SSH server and I was able to run apport that way, but the local video still does not update. This is on a machine Canonical's magners lab. I've looked at lp:1080701 but removing all partitions before installing doesn't seem to help. Please let me know what other information I can gather.

[ 2049.152080] INFO: task Xorg:5770 blocked for more than 120 seconds.
[ 2049.152087] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 2049.152091] Xorg D ffff88007e293e40 0 5770 5758 0x00400004
[ 2049.152100] ffff880074c5bc60 0000000000000002 ffff880073e98000 ffff880074c5bfd8
[ 2049.152109] ffff880074c5bfd8 ffff880074c5bfd8 ffff88007ac21700 ffff880073e98000
[ 2049.152117] ffff880076b70800 ffff880076afae68 ffff88007a42e800 0000000000000001
Call Trace:
schedule+0x29/0x70
intel_crtc_wait_for_pending_flips+0x75/0xd0 [i915]
? finish_wait+0x80/0x80
i9xx_crtc_disable+0x87/0x180 [i915]
intel_crtc_update_dpms+0x6f/0xa0 [i915]
intel_encoder_dpms+0x1a/0x30 [i915]
intel_connector_dpms+0x38/0x70 [i915]
drm_mode_obj_set_property_ioctl+0x320/0x330 [drm]
drm_mode_connector_property_set_ioctl+0x30/0x40 [drm]
drm_ioctl+0x4d3/0x580 [drm]
? drm_mode_obj_set_property_ioctl+0x330/0x330 [drm]
do_vfs_ioctl+0x99/0x590
sys_ioctl+0x91/0xb0
system_call_fastpath+0x1a/0x1f

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: ubiquity 2.13.7
ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
Uname: Linux 3.7.0-7-generic x86_64
ApportVersion: 2.7-0ubuntu2
Architecture: amd64
CasperVersion: 1.330
Date: Mon Jan 7 11:17:14 2013
InstallCmdLine: initrd=/images/acer-veriton-04-x86_64/initrd.lz ksdevice=bootif lang= log_host=10.97.0.1 keyboard-configuration/layoutcode=us locale=en_US automatic-ubiquity netboot=nfs boot=casper noprompt priority=critical log_port=514 root=/dev/nfs netcfg/choose_interface=auto nfsroot=10.97.4.1:/tmp/acer-veriton-04_PpQJb0 ks=http://10.128.92.2/cblr/svc/op/ks/system/acer-veriton-04 BOOT_IMAGE=/images/acer-veriton-04-x86_64/kernel BOOTIF=01-d0-27-88-9b-84-5b
LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130107)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[Max Brustkern (nuclearbob)]

Here are some additional logs.

[Dimitri John Ledkov (xnox)]

From additional logs tarball -> syslog:
Jan 7 16:11:20 ubuntu ubiquity[7196]: debconffilter_done: ubiquity.components.plugininstall (current: None)
Jan 7 16:11:20 ubuntu ubiquity[7196]: Reverting lockdown of the desktop environment.
Jan 7 16:15:20 ubuntu kernel: [ 2049.152080] INFO: task Xorg:5770 blocked for more than 120 seconds.
Jan 7 16:15:20 ubuntu kernel: [ 2049.152087] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 7 16:15:20 ubuntu kernel: [ 2049.152091] Xorg D ffff88007e293e40 0 5770 5758 0x00400004
Jan 7 16:15:20 ubuntu kernel: [ 2049.152100] ffff880074c5bc60 0000000000000002 ffff880073e98000 ffff880074c5bfd8
Jan 7 16:15:20 ubuntu kernel: [ 2049.152109] ffff880074c5bfd8 ffff880074c5bfd8 ffff88007ac21700 ffff880073e98000
Jan 7 16:15:20 ubuntu kernel: [ 2049.152117] ffff880076b70800 ffff880076afae68 ffff88007a42e800 0000000000000001
Jan 7 16:15:20 ubuntu kernel: [ 2049.152125] Call Trace:
Jan 7 16:15:20 ubuntu kernel: [ 2049.152139] [<ffffffff816a4ee9>] schedule+0x29/0x70
Jan 7 16:15:20 ubuntu kernel: [ 2049.152196] [<ffffffffa00a3fe5>] intel_crtc_wait_for_pending_flips+0x75/0xd0 [i915]
Jan 7 16:15:20 ubuntu kernel: [ 2049.152204] [<ffffffff8107c6c0>] ? finish_wait+0x80/0x80
Jan 7 16:15:20 ubuntu kernel: [ 2049.152236] [<ffffffffa00a6647>] i9xx_crtc_disable+0x87/0x180 [i915]
Jan 7 16:15:20 ubuntu kernel: [ 2049.152268] [<ffffffffa00ab39f>] intel_crtc_update_dpms+0x6f/0xa0 [i915]
Jan 7 16:15:20 ubuntu kernel: [ 2049.152300] [<ffffffffa00ab47a>] intel_encoder_dpms+0x1a/0x30 [i915]
Jan 7 16:15:20 ubuntu kernel: [ 2049.152332] [<ffffffffa00ad248>] intel_connector_dpms+0x38/0x70 [i915]
Jan 7 16:15:20 ubuntu kernel: [ 2049.152363] [<ffffffffa001fdd0>] drm_mode_obj_set_property_ioctl+0x320/0x330 [drm]
Jan 7 16:15:20 ubuntu kernel: [ 2049.152389] [<ffffffffa001fe10>] drm_mode_connector_property_set_ioctl+0x30/0x40 [drm]
Jan 7 16:15:20 ubuntu kernel: [ 2049.152412] [<ffffffffa000e553>] drm_ioctl+0x4d3/0x580 [drm]
Jan 7 16:15:20 ubuntu kernel: [ 2049.152440] [<ffffffffa001fde0>] ? drm_mode_obj_set_property_ioctl+0x330/0x330 [drm]
Jan 7 16:15:20 ubuntu kernel: [ 2049.152449] [<ffffffff8119d0c9>] do_vfs_ioctl+0x99/0x590
Jan 7 16:15:20 ubuntu kernel: [ 2049.152455] [<ffffffff8119d651>] sys_ioctl+0x91/0xb0
Jan 7 16:15:20 ubuntu kernel: [ 2049.152463] [<ffffffff816ae75d>] system_call_fastpath+0x1a/0x1f
Jan 7 16:17:01 ubuntu CRON[31885]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Jan 7 16:17:20 ubuntu kernel: [ 2169.152131] INFO: task Xorg:5770 blocked for more than 120 seconds.
Jan 7 16:17:20 ubuntu kernel: [ 2169.152141] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jan 7 16:17:20 ubuntu kernel: [ 2169.152148] Xorg D ffff88007e293e40 0 5770 5758 0x00400004
Jan 7 16:17:20 ubuntu kernel: [ 2169.152160] ffff880074c5bc60 0000000000000002 ffff880073e98000 ffff880074c5bfd8
Jan 7 16:17:20 ubuntu kernel: [ 2169.152174] ffff880074c5bfd8 ffff880074c5bfd8 ffff88007ac21700 ffff880073e98000
Jan 7 16:17:20 ubuntu kernel: [ 2169.152185] ffff880076b70800 ffff880076afae68 ffff88007a42e800 0000000000000001
...

[Gema Gomez (gema)]

bumping the criticality of the bug, because of the impact it is having on all the automated testing on HW.

[Jean-Baptiste Lallement (jibel)]

output of lspci -vvnn from one of the box

[Jean-Baptiste Lallement (jibel)]

dmesg of a successful boot just in case it contains useful system informations.

[Timo Aaltonen (tjaalton)]

So the veriton is a gen3 machine (atom D425) while the other one mentioned on irc (HP Pavilion Slimline s5-1224) is gen7 (ivybridge). Still can't see what broke them after Dec 20th, highly unlikely it was the driver upload on 17th.

[Timo Aaltonen (tjaalton)]

this should be fixed now, reopen if it breaks again

[Max Brustkern (nuclearbob)]

This seemed to be fixed in images up to 20130201. amd64 images on and after that date have been freezing during the install. i386 images were okay prior to 20130204, and I've had failures on today's i386 image, but I've also had successes.

[Timo Aaltonen (tjaalton)]

in that case it's not the driver at fault but something else, since there were no updates to it.. (before today)

[Max Brustkern (nuclearbob)]

This happens during the install, and the mouse cursor does not move when it occurs. If you still think it's a duplicate of the other one, that's fine, I just want to be clear that some of the symptoms appear to be different.