The latest 2.6.28-11-generic#37 kernel (amd64) has frozen twice in the last 24 hours on my PC, ie locked up completely (with indicator lights flashing) and needing a hard reset by holding down the power button.
The first time I was using it (I was moving the mouse), but the second time it was just idling when it locked some time between 3:50 and 7:44 am, as shown in the syslog:
This is on the latest Jaunty. It's a Dell XPS M1530 that was running nvidia 185.13 the first time it locked up, and 180.41 the second time. There's no information in any of the logs - syslog shows the last message at 3:50.
Prior to this, I haven't had any lockups for quite some time (it was the iwlagn driver causing it in Intrepid but that bug was fixed some time ago).
The latest 2.6.28- 11-generic# 37 kernel (amd64) has frozen twice in the last 24 hours on my PC, ie locked up completely (with indicator lights flashing) and needing a hard reset by holding down the power button.
The first time I was using it (I was moving the mouse), but the second time it was just idling when it locked some time between 3:50 and 7:44 am, as shown in the syslog:
Mar 26 03:29:14 pegasus-jaunty NetworkManager: <info> (wlan0): supplicant connection state: completed -> group handshake CRON[32557] : (root) CMD ([ -x /usr/sbin/ update- motd ] && /usr/sbin/ update- motd 2>/dev/null) CRON[487] : (root) CMD ( [ -x /usr/lib/ php5/maxlifetim e ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -type f -cmin +$(/usr/ lib/php5/ maxlifetime) -print0 | xargs -n 200 -r -0 rm) CRON[587] : (root) CMD ([ -x /usr/sbin/ update- motd ] && /usr/sbin/ update- motd 2>/dev/null) CRON[1017] : (root) CMD ([ -x /usr/sbin/ update- motd ] && /usr/sbin/ update- motd 2>/dev/null)
Mar 26 03:29:14 pegasus-jaunty NetworkManager: <info> (wlan0): supplicant connection state: group handshake -> completed
Mar 26 03:30:01 pegasus-jaunty /USR/SBIN/
Mar 26 03:39:01 pegasus-jaunty /USR/SBIN/
Mar 26 03:40:01 pegasus-jaunty /USR/SBIN/
Mar 26 03:50:01 pegasus-jaunty /USR/SBIN/
Mar 26 07:44:10 pegasus-jaunty syslogd 1.5.0#5ubuntu3: restart.
This is on the latest Jaunty. It's a Dell XPS M1530 that was running nvidia 185.13 the first time it locked up, and 180.41 the second time. There's no information in any of the logs - syslog shows the last message at 3:50.
Prior to this, I haven't had any lockups for quite some time (it was the iwlagn driver causing it in Intrepid but that bug was fixed some time ago).