I'll have a go. In the mean time, here's some more info. System froze
twice yesterday, and I went and saved some logs. Here's what I wrote
yesterday with some syslog extracts:
1st time:
Again it froze. This time there was no wireless on. I was listening to music
again, and reading a man doc in a terminal. Firefox, two different profiles,
FreeCiv, and maybe something else (I think Document Viewer, looking at a PDF).
I was using Deja Dup to make backup (the first, so it was taking a
rather long time) to an external HD. After the system froze, I noticed
that the indicator light on the HD had stopped blinking. Suggesting that
there was no more activity, and thus that the backup program had also
frozen or had been killed.
-----
2nd time:
It froze again less than an hour after the last time. This time with just
FreeCiv, RhythemBox and DejaDup. 21:42 is what the clock said. I guess I also
have a bunch of other stuff (Apache, MySQL and PHP) running in the background.
I'm uninstalling indicator-cpufreq, though I doubt it's the problem.
------
OK, bizarre. I said the time said 21:42. Except that at around 22:05, I noticed
the time had jumped two hours forward! It was apparently now the 13, and the
time was 00:05. My clock is meant to be on network time, but the Internet has
been down most of the day, and I certainly haven't connected in the last 8
hours or so.
Interesting thing from the syslog from around the time of the problem:
Oct 12 21:37:19 Mayan-Pilot kernel: [10314.926725] CPU1: Package power limit
notification (total events = 923)
Oct 12 21:37:19 Mayan-Pilot kernel: [10314.926728] CPU0: Package power limit
notification (total events = 923)
Oct 12 21:37:19 Mayan-Pilot kernel: [10314.926751] CPU3: Package power limit
notification (total events = 923)
Oct 12 21:37:19 Mayan-Pilot kernel: [10314.926754] CPU2: Package power limit
notification (total events = 923)
Oct 12 21:37:19 Mayan-Pilot kernel: [10315.108358] CPU1: Package power limit
normal
Oct 12 21:37:19 Mayan-Pilot kernel: [10315.108363] CPU0: Package power limit
normal
Oct 12 21:37:19 Mayan-Pilot kernel: [10315.108382] CPU2: Package power limit
normal
Oct 12 21:37:19 Mayan-Pilot kernel: [10315.108387] CPU3: Package power limit
normal
Oct 12 21:39:01 Mayan-Pilot CRON[2971]: (root) CMD ( [ -x
/usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/
-depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) !
-execdir fuser -s {} 2>/dev/null \; -delete)
Oct 12 23:57:58 Mayan-Pilot kernel: imklog 5.8.6, log source = /proc/kmsg
started.
Here we see where the time has jumped forward. At 21:39 something
happened, the system froze about three minutes latter. Then, the time
jumps forward two hours. (Presumably after I had restarted the machine.)
After I changed the clock, here's the log:
Oct 12 23:59:11 Mayan-Pilot dbus[936]: [system] Activating service
name='com.ubuntu.SystemService' (using servicehelper)
Oct 12 23:59:11 Mayan-Pilot dbus[936]: [system] Successfully activated service
'com.ubuntu.SystemService'
Oct 13 00:01:32 Mayan-Pilot dbus[936]: [system] Reloaded configuration
Oct 13 00:03:16 Mayan-Pilot kernel: [ 338.435208] CPU0: Package power limit
notification (total events = 1577)
Oct 13 00:03:16 Mayan-Pilot kernel: [ 338.435216] CPU1: Package power limit
notification (total events = 1576)
Oct 13 00:03:16 Mayan-Pilot kernel: [ 338.435225] CPU2: Package power limit
notification (total events = 1577)
Oct 13 00:03:16 Mayan-Pilot kernel: [ 338.435233] CPU3: Package power limit
notification (total events = 1577)
Oct 13 00:03:16 Mayan-Pilot kernel: [ 338.437565] CPU0: Package power limit
normal
Oct 13 00:03:16 Mayan-Pilot kernel: [ 338.437571] CPU1: Package power limit
normal
Oct 13 00:03:16 Mayan-Pilot kernel: [ 338.437578] CPU3: Package power limit
normal
Oct 13 00:03:16 Mayan-Pilot kernel: [ 338.437584] CPU2: Package power limit
normal
Oct 13 00:05:09 Mayan-Pilot dbus[936]: [system] Activating service
name='org.gnome.SettingsDaemon.DateTimeMechanism' (using servicehelper)
Oct 13 00:05:09 Mayan-Pilot dbus[936]: [system] Successfully activated service
'org.gnome.SettingsDaemon.DateTimeMechanism'
Oct 12 22:08:08 Mayan-Pilot kernel: [ 642.210183] CPU2: Package power limit
notification (total events = 2521)
Oct 12 22:08:08 Mayan-Pilot kernel: [ 642.210190] CPU3: Package power limit
notification (total events = 2521)
Oct 12 22:08:08 Mayan-Pilot kernel: [ 642.210199] CPU1: Package power limit
notification (total events = 2520)
Oct 12 22:08:08 Mayan-Pilot kernel: [ 642.210206] CPU0: Package power limit
notification (total events = 2521)
Oct 12 22:08:09 Mayan-Pilot kernel: [ 642.449629] CPU1: Package power limit
normal
Oct 12 22:08:09 Mayan-Pilot kernel: [ 642.449635] CPU0: Package power limit
normal
Oct 12 22:08:09 Mayan-Pilot kernel: [ 642.449643] CPU2: Package power limit
normal
Oct 12 22:08:09 Mayan-Pilot kernel: [ 642.449649] CPU3: Package power limit
normal
Oct 12 22:09:01 Mayan-Pilot CRON[3109]: (root) CMD ( [ -x
/usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/
-depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) !
-execdir fuser -s {} 2>/dev/null \; -delete)
So I guess PHP is not the problem...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065490
Title:
total system freeze
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065490/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
