Troubleshooting boot issues - Revision history

amigadave: recategorize

2010-12-07T10:29:27Z

recategorize

← Older revision		Revision as of 10:29, 7 December 2010
Line 1:		Line 1:
		+	{{out of date}}
		+
	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 58:		Line 60:
	And finally, file [http://bugs.maemo.org bugs] against the problem applications!		And finally, file [http://bugs.maemo.org bugs] against the problem applications!

-		+	[[Category:N8x0]]
-	[[Category:~~Users~~]]	+
-		+
	[[Category:Power users]]		[[Category:Power users]]

ossipena at 12:06, 1 November 2009

2009-11-01T12:06:09Z

← Older revision		Revision as of 12:06, 1 November 2009
Line 60:		Line 60:

	[[Category:Users]]		[[Category:Users]]
		+
		+	[[Category:Power users]]

twaelti at 08:50, 22 October 2009

2009-10-22T08:50:18Z

← Older revision		Revision as of 08:50, 22 October 2009
Line 60:		Line 60:

	[[Category:Users]]		[[Category:Users]]
-	~~[[Category:Development]]~~

generalantilles: Cleanup and markup, still needs help

2009-04-19T07:38:09Z

Cleanup and markup, still needs help

← Older revision		Revision as of 07:38, 19 April 2009
Line 1:		Line 1:
-	~~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 36:		Line 34:

	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:
		+
		+	* 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:Users]]		[[Category:Users]]
		+	[[Category:Development]]

generalantilles: Categorization

2008-10-28T05:12:01Z

Categorization

← Older revision		Revision as of 05:12, 28 October 2008
Line 36:		Line 36:

	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.
		+
		+
		+	[[Category:Users]]

fanoush: bootmenu link added

2008-08-18T10:04:50Z

bootmenu link added

← Older revision		Revision as of 10:04, 18 August 2008
Line 1:		Line 1:
	When trying to debug boot problems, the following (or something simillar) may help you.		When trying to debug boot problems, the following (or something simillar) may help you.

-	You'll need ~~the initfs_flash~~ 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:

	* Boot Nxx0 and start the telnet/ssh server		* Boot Nxx0 and start the telnet/ssh server

79.103.206.179 at 23:29, 17 August 2008

2008-08-17T23:29:24Z

← Older revision		Revision as of 23:29, 17 August 2008
Line 5:		Line 5:
	* Boot Nxx0 and start the telnet/ssh server		* Boot Nxx0 and start the telnet/ssh server
	* Connect USB cable to PC		* Connect USB cable to PC
-	* ~~Run~~:	+	* In your Linux PC run:
	modprobe usbnet		modprobe usbnet
	ifconfig usb0 up		ifconfig usb0 up
	ip addr add dev usb0 192.168.10.2/24		ip addr add dev usb0 192.168.10.2/24
	telnet 192.168.10.1		telnet 192.168.10.1
		+	(where 192.168.10.1 is the IP address of the Nxx0 device and 192.168.10.2 is an IP address in the same subnet to be used by your PC)

-	* You're now connected. Load required modules for accessing your root partition:	+	* You're now connected. Load required modules for accessing your root partition (not all of them are required):
	insmod /lib/modules/2.6.21-omap1/jbd.ko		insmod /lib/modules/2.6.21-omap1/jbd.ko
	insmod /lib/modules/2.6.21-omap1/mbcache.ko		insmod /lib/modules/2.6.21-omap1/mbcache.ko
Line 17:		Line 18:
	insmod /lib/modules/2.6.21-omap1/ext3.ko		insmod /lib/modules/2.6.21-omap1/ext3.ko

-	* And mount the root partition:	+	* And mount the root partition (suppose it is /dev/mmcblk0p2):
	mount /dev/mmcblk0p2 /mnt/new_root -t ext3 -o noatime		mount /dev/mmcblk0p2 /mnt/new_root -t ext3 -o noatime

79.103.206.179: New page: When trying to debug boot problems, the following (or something simillar) may help you. You'll need the initfs_flash with a telnet or ssh server installed. I'll suppose that a telnet serv...

2008-08-17T23:15:55Z

New page: When trying to debug boot problems, the following (or something simillar) may help you. You'll need the initfs_flash with a telnet or ssh server installed. I'll suppose that a telnet serv...

New page

When trying to debug boot problems, the following (or something simillar) may help you.

You'll need the initfs_flash with a telnet or ssh server installed. I'll suppose that a telnet server is used:

* Boot Nxx0 and start the telnet/ssh server
* Connect USB cable to PC
* Run:
modprobe usbnet
ifconfig usb0 up
ip addr add dev usb0 192.168.10.2/24
telnet 192.168.10.1

* You're now connected. Load required modules for accessing your root partition:
insmod /lib/modules/2.6.21-omap1/jbd.ko
insmod /lib/modules/2.6.21-omap1/mbcache.ko
insmod /lib/modules/2.6.21-omap1/ext2.ko
insmod /lib/modules/2.6.21-omap1/ext3.ko

* And mount the root partition:
mount /dev/mmcblk0p2 /mnt/new_root -t ext3 -o noatime

* Now run:
cd /mnt/new_root
mount -obind /tmp /mnt/new_root/tmp
pivot_root . mnt/initfs

export OSSO_VERSION=$(cat /etc/osso_software_version)

* And you're ready to manually boot it:
cd /etc/init.d
./rcS
./rc 2

This will do the whole bootup procedure (not exactly, but the interresting part) and you'll be able to watch all bootup messages.

Don't forget that the watchdog will reboot the machine after a some time.