nouveau framebuffer crashed : [TTM] DRM memory manager type 2 is not clean. kernel BUG at /build/buildd/linux-backports-modules-2.6.32-2.6.32/debian/build/build-generic/nouveau/ttm/ttm_bo.c:1475!

[Michael Evans]

The 20100224 daily alternate installs and boots successfully to X.

Install SSH server before rebooting.

After applying the latest updates to the system/X upon reboot the laptop's screen is back-light off and the system non-navigable.

ps axf
  PID TTY STAT TIME COMMAND
    2 ? S 0:00 [kthreadd]
    1 ? Ss 0:00 /sbin/init
  456 ? S 0:00 upstart-udev-bridge --daemon
  458 ? S<s 0:00 udevd --daemon
  843 ? S< 0:00 \_ udevd --daemon
  846 ? S< 0:00 \_ udevd --daemon
  859 ? Sl 0:00 rsyslogd -c4
  867 ? Ss 0:00 /usr/sbin/sshd
  898 ? Ss 0:00 dbus-daemon --system --fork
  912 ? Ssl 0:00 NetworkManager
 1001 ? S 0:00 \_ /sbin/dhclient -d -sf /usr/lib/NetworkManager/nm-dhcp-client.action -pf /var/run/dhclient-eth0.pid -lf /var/lib/dhcp3/dhclient-cd965b0e-944b-452e-af86-1d
  919 ? S 0:00 avahi-daemon: registering [drpepper.local]
  920 ? Ss 0:00 \_ avahi-daemon: chroot helper
  921 ? S 0:00 /usr/sbin/modem-manager
  923 ? Sl 0:00 /usr/sbin/console-kit-daemon --no-daemon
 1003 ? S 0:00 /sbin/wpa_supplicant -u -s
 1112 tty4 Ss+ 0:00 /sbin/getty -8 38400 tty4
 1116 tty5 Ss+ 0:00 /sbin/getty -8 38400 tty5
 1124 tty2 Ss+ 0:00 /sbin/getty -8 38400 tty2
 1127 tty3 Ss+ 0:00 /sbin/getty -8 38400 tty3
 1129 ? Ss 0:00 /usr/sbin/kerneloops
 1131 tty6 Ss+ 0:00 /sbin/getty -8 38400 tty6
 1134 ? Ss 0:00 /usr/sbin/irqbalance
 1136 ? Ss 0:00 acpid -c /etc/acpi/events -s /var/run/acpid.socket
 1155 ? Ss 0:00 atd
 1156 ? Ss 0:00 cron
 1173 ? Ss 0:00 /usr/sbin/cupsd -C /etc/cups/cupsd.conf
 1296 tty1 Ss+ 0:00 /sbin/getty -8 38400 tty1
 1743 ? Ss 0:00 portmap
 1965 ? Ss 0:00 rpc.statd -L
 2250 ? Ss 0:00 /usr/sbin/rpc.mountd --manage-gids

I've backed up /var/log to a network location and can attach any additional logs requested.

[Michael Evans (mjevans1983)]

Almost inexplicably after leaving the laptop turned off over-night and turning it back on (without first booting any other install on it) the system loaded without further issue. I have no idea if it is a race condition or some other cause.

I'll keep updating and testing as normal. If I am unable to duplicate the error again within a week the bug is probably outdated.

[Andy Whitcroft (apw)]

[This is an automated message. Apologies if it has reached you inappropriately.]

This bug was reported against the linux-meta package when it likely should have been reported against the linux package instead. We are automatically transitioning this to the linux kernel package so that the appropriate teams are notified and made aware of this issue.

If this bug really is a bug in the linux-meta package you can move it back to linux-meta and tag it kj-linux-meta, or contact us on the #ubuntu-kernel channel on the FreeNode IRC server. Thanks.