Editing Troubleshooting boot issues
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision |
Your text |
| Line 1: |
Line 1: |
| - | {{out of date}}
| + | When trying to debug boot problems, the following (or something simillar) may help you. |
| | | | |
| | You'll need bootmenu [http://fanoush.wz.cz/maemo/#initfs] with a telnet or ssh server installed. I'll suppose that a telnet server is used: | | You'll need bootmenu [http://fanoush.wz.cz/maemo/#initfs] with a telnet or ssh server installed. I'll suppose that a telnet server is used: |
| Line 37: |
Line 37: |
| | Don't forget that the watchdog will reboot the machine after a some time. | | Don't forget that the watchdog will reboot the machine after a some time. |
| | | | |
| - | == Reporting reboot issues ==
| |
| | | | |
| - | When reporting strange booting/rebooting issues here is a list of information that is helpful in debugging:
| + | [[Category:Users]] |
| - | | + | |
| - | * Output of <code>/proc/bootreason</code>
| + | |
| - | * Output of <code>/var/lib/dsme/stats/lifeguard_resets</code>
| + | |
| - | * Application running when the reboot occurred
| + | |
| - | * State of device - idle with cover, idle without cover, turned off, in use, etc.
| + | |
| - | * Mode of device - R&D or production mode
| + | |
| - | * <code>dmesg</code> after a successful boot. This will show whether the OOM (out of memory) killer is reaping processes.
| + | |
| - | | + | |
| - | <code>/proc/bootreason</code> can have the following values:
| + | |
| - | pwr_key Power key was pressed to switch on device
| + | |
| - | 32wd_to Watchdog reset - something was consuming too much CPU causing a watchdog reset, or kernel crashed
| + | |
| - | sw_rst Software reset (critical system application crashing or being killed by the kernel OOM-killer)
| + | |
| - | rtc_alarm An alarm woke up the device
| + | |
| - | | + | |
| - | You need to install XTerm or [[SSH]] to get a console. Then use <code>cat</code> to get the contents of a particular file.
| + | |
| - | | + | |
| - | You can create a <code>core-dumps</code> directory on the internal flash card, then crashing applications will leave core files in it. Use <code>file core.*</code> to find out the name of the crashed application. In theory, you can use <code>gdb</code> to get the stack trace, but without debug symbols it wont be any use. If you copy <code>*.core</code> files to your Linux PC you can use <code>gdb</code> see what program crashed, use <code>gdp -core core.xxxx</code> where <code>xxxx</code> is the number of the file.
| + | |
| - | | + | |
| - | And finally, file [http://bugs.maemo.org bugs] against the problem applications!
| + | |
| - | | + | |
| - | [[Category:N8x0]]
| + | |
| - | [[Category:Power users]] | + | |
Learn more about Contributing to the wiki.
