maemo.org Bugzilla – Bug 460
When forcing a reboot, write *something* *somewhere* as to why
Last modified: 2008-12-06 17:59:51 UTC
You need to
before you can comment on or make changes to this bug.
I'm having reboots after loading the latest code image - sometimes for no
I can explain, when the unit is idle, case closed, plugged-in to the charger,
the middle of the night, when one would think very little (other than
the battery charge) was going on. Other times the unit reboots when I try to
launch something e.g. start a network connection.
There is no way to find out exactly *why* these reboots are happening -
obviously something is deciding a reboot is needed, but who knows why?
It would be nice if that "something" would log why the reboot was fired -
to /var/log, or just leave a message at a given location in RAM that could be
picked up after reboot during system startup and written to /var/log, so that
could begin to get a handle on this.
Enhancement, will be forwarded to upstream maintainer ASAP.
Feature request has been forwarded to upstream maintainer.
In IT2006, if you add "core-dumps" directory to the MMC, you get a core dump of
the process(es) that crash.
Most of the apps in IT2006 are maemo-launched so you usually see two core dumps,
one of few hundred KBs (the launch wrapper) and one of few megs (the application
actually crashing). When looking at the latter with Gdb, you should give Gdb
/usr/bin/maemo-launcher as the binary.
I think this bug could be invalidated.
One more possibility could be to install syslogd, but I'm not sure whether SDK
repos offer that (and that much logging's a bit of Flash waste)...?
David, if this is still an issue, can you please post the data described at
http://maemo.org/community/wiki/ReportingRebootIssues/ ? Thanks in advance!
Doesn't "more /proc/bootreason" tell the reboot reason and fix this ticket?
Or am I too naïve?
(In reply to comment #9)
> Doesn't "more /proc/bootreason" tell the reboot reason and fix this ticket?
It tells the category (HW or SW watchdog), /var/lib/dsme tells for SW watchdog
resets which processes deaths have caused reboots (as explained in the wiki)
and if syslog is installed, it contains more details.
These were actually there already in 770 (syslog wasn't but could be built from
Debian source package), so this should be invalidated or at least worksforme.
HW watchdog is a problem, but there's not much that could be done except by
attaching serial console to the device before it reboots to see console
messages (if kernel freezes, you cannot get anything written to disk).
Closing as per last comment.