View Single Post
int_ua's Avatar
Posts: 676 | Thanked: 1,067 times | Joined on Jul 2010 @ Kyiv, Ukraine
#295
Another two reboots in one day. This time reports extended with the syslog. I hope it doesn't contain any confidential info (looks like it includes GSM CellIDs, but it's just from the first glance, didn't have time to check). The second one is not kernel oops but reboot-32wd_to crash 0_o. Maybe it's hardware failures, after all?

At 22:22 I just closed Marble which was the only opened application. And at 00:32 IIRC I was playing with dpkg -S / dpkg -L / fileorphan.sh in terminal + a couple of windows in the background.

Edit: checking syslog, it looks like nothing there:
22:20:14kernel: [89844.591369] kb_lock (GPIO 113) is now closed
22:20:15 kernel: [89844.864715] kb_lock (GPIO 113) is now open
22:20:29 syslogd 1.5.0#5maemo7+0m5: restart.
...
00:29:00cellular: csd[824]: ISI_SMS .160766> incoming_cell_broadcast(): Incoming cell broadcast
00:29:03 cellular: csd[824]: ISI_SMS .553009> ind_reg_status(): Net registration (ind) status:1 rc:0
00:29:03 cellular: csd[824]: ISI_SMS .554199> set_timeout(): Timeout 3587 s event type:-1
00:30:28 syslogd 1.5.0#5maemo7+0m5: restart.
Attached Files
File Type: gz oopslog-and-reboot-crash-with-syslog.tar.gz (266.4 KB, 82 views)

Last edited by int_ua; 2012-12-20 at 13:34.
 

The Following 6 Users Say Thank You to int_ua For This Useful Post: