Suspend debugging - История изменений

Stuw в 16:11, 17 сентября 2017

2017-09-17T16:11:37Z

← Предыдущая версия		Версия от 16:11, 17 сентября 2017
Строка 16:		Строка 16:
	[http://elinux.org/Android_Power_Management Android Power Management]		[http://elinux.org/Android_Power_Management Android Power Management]

			===EC overview===
	===~~Doesn't want to wake up?~~===		[[Файл:AC100_EC_to_Tegra_connectivity.png\|800px]]
	~~'''NOTE:''' looks like pm_trace is x68/64 only.<br />~~
	~~OK. With that understood.... In order to simulate your suspend/resume process, enter the following commands:~~
	~~<pre>~~
	~~sudo sh -c "sync; echo 1 > /sys/power/pm_trace; pm-suspend"~~
	~~</pre>~~
	At this point your computer should enter the suspend state within a few seconds. Usually the power LED will slowly flash when in the suspended state. When that has happened, initiate the resume process by pressing the power button. Observe closely if the disk light comes on briefly. This indicates that resume has begun. If resume fails to complete, then press the power button until the computer turns off. Power on your computer making sure that it loads the same kernel that exhibited the resume problem. You have about 3 minutes to start this boot process before the information saved in the RTC gets corrupted.

	~~Start a console and enter~~:
	~~<pre>~~
	~~dmesg > dmesg~~.~~txt~~
	~~</pre>~~
	~~You can edit this file and find lines similar to these:~~
	~~<pre>~~
	~~[ 11.323206~~] ~~Magic number: 0:798:264~~
	~~[ 11.323257~~] ~~hash matches drivers/base/power/resume.c:46~~
	~~</pre>~~
	~~There may well be another 'hash matches' line beyond that. If so, then you are in luck because the last one is the likely culprit. For example:~~
	~~<pre>~~
	~~hash matches device i2c-9191~~
	~~</pre>~~
	~~The only way to prove this is to remove the module prior to initiating suspend. Repeat as needed...~~

	~~If you get a device number rather than name, lspci and /sys/devices/pci* are your friends.~~

	===Logs===		===Logs===
Строка 58:		Строка 35:
	https://gitorious.org/ac100/kernel/commit/1d0d7ff80526d0f6451d230a81349dac01b466c1		https://gitorious.org/ac100/kernel/commit/1d0d7ff80526d0f6451d230a81349dac01b466c1

	===~~Code~~ analysis===		===Suspend code analysis===
	Call stack (based on sources):		Call stack (based on sources):
	<pre>		<pre>
Строка 124:		Строка 101:
	This logic works only if '''CONFIG_PM_DEBUG''' is enabled.		This logic works only if '''CONFIG_PM_DEBUG''' is enabled.

	===~~Magic~~===		===Tracing===
	There is PM_TRACE support for x86 architecture. The main idea is to keep some values between reboots. For x86 the data is saved in RTC.		There is PM_TRACE support for x86 architecture. The main idea is to keep some values between reboots. For x86 the data is saved in RTC.
	PM_TRACE is not implemented for ARM.		PM_TRACE is not implemented for ARM.
			'''NOTE:''' looks like pm_trace is x68/64 only.<br />

	===Tests===		===Tests===

Stuw: /* Tests */

2016-12-26T09:56:28Z

Tests

← Предыдущая версия		Версия от 09:56, 26 декабря 2016
Строка 133:		Строка 133:

	Looks like AC100 failes to resume from devices state.		Looks like AC100 failes to resume from devices state.
	<~~pre~~>		<syntaxhighlight lang="bash">
	cat /sys/power/pm_test		cat /sys/power/pm_test
	# here will be available values		# here will be available values
Строка 142:		Строка 142:
	echo mem > /sys/power/state		echo mem > /sys/power/state
	# Fail (usually, wake up 1 time of 7)		# Fail (usually, wake up 1 time of 7)
	</~~pre~~>		</syntaxhighlight>


	===Plan===		===Plan===

Stuw: /* Doesn't want to wake up? */

2016-06-28T19:21:04Z

Doesn't want to wake up?

← Предыдущая версия		Версия от 19:21, 28 июня 2016
Строка 18:		Строка 18:

	===Doesn't want to wake up?===		===Doesn't want to wake up?===
			'''NOTE:''' looks like pm_trace is x68/64 only.<br />
	OK. With that understood.... In order to simulate your suspend/resume process, enter the following commands:		OK. With that understood.... In order to simulate your suspend/resume process, enter the following commands:
	<pre>		<pre>

Stuw: /* Plan */

2015-09-25T12:39:03Z

Plan

← Предыдущая версия		Версия от 12:39, 25 сентября 2015
Строка 146:		Строка 146:
	===Plan===		===Plan===
	* set up tftpboot (for easier boot process between dev kernels)		* set up tftpboot (for easier boot process between dev kernels)
	* check devices suspend resume on latest NVEC patches for mainline		* check devices suspend/resume on latest NVEC patches for mainline
			* check suspend/resume with disabled PM for nvec
			* check suspend/resume with disabled PM for i2c-2 (where nvec is placed)
	* try to implement trace logic for suspend		* try to implement trace logic for suspend

Stuw в 11:21, 25 сентября 2015

2015-09-25T11:21:18Z

← Предыдущая версия		Версия от 11:21, 25 сентября 2015
Строка 142:		Строка 142:
	# Fail (usually, wake up 1 time of 7)		# Fail (usually, wake up 1 time of 7)
	</pre>		</pre>


			===Plan===
			* set up tftpboot (for easier boot process between dev kernels)
			* check devices suspend resume on latest NVEC patches for mainline
			* try to implement trace logic for suspend

Stuw в 11:04, 25 сентября 2015

2015-09-25T11:04:54Z

← Предыдущая версия		Версия от 11:04, 25 сентября 2015
Строка 123:		Строка 123:
	This logic works only if '''CONFIG_PM_DEBUG''' is enabled.		This logic works only if '''CONFIG_PM_DEBUG''' is enabled.

			===Magic===
			There is PM_TRACE support for x86 architecture. The main idea is to keep some values between reboots. For x86 the data is saved in RTC.
			PM_TRACE is not implemented for ARM.

	===Tests===		===Tests===

Stuw в 10:57, 25 сентября 2015

2015-09-25T10:57:44Z

← Предыдущая версия		Версия от 10:57, 25 сентября 2015
Строка 2:		Строка 2:
	[http://lists.infradead.org/pipermail/linux-arm-kernel/2011-January/039696.html [PATCH v3 13/28] ARM: tegra: Add suspend and hotplug support]		[http://lists.infradead.org/pipermail/linux-arm-kernel/2011-January/039696.html [PATCH v3 13/28] ARM: tegra: Add suspend and hotplug support]

	http://~~www.~~thinksrc.com/~~2010/11/20~~/~~suspend-en.html~~		[http://thinksrc.com/?p=173001 Linux Kernel and Android Suspend/Resume]

	[http://www.kernel.org/doc/Documentation/power/s2ram.txt How to get s2ram working]		[http://www.kernel.org/doc/Documentation/power/s2ram.txt How to get s2ram working]

Stuw: /* Tests */ Fix typo

2015-06-26T10:45:26Z

Tests: Fix typo

← Предыдущая версия		Версия от 10:45, 26 июня 2015
Строка 130:		Строка 130:
	Looks like AC100 failes to resume from devices state.		Looks like AC100 failes to resume from devices state.
	<pre>		<pre>
	cat /sys/power/~~pm_tests~~		cat /sys/power/pm_test
	# here will be available values		# here will be available values
	echo freezer > /sys/power/~~pm_tests~~		echo freezer > /sys/power/pm_test
	echo mem > /sys/power/state		echo mem > /sys/power/state
	# OK		# OK
	echo devices > /sys/power/~~pm_tests~~		echo devices > /sys/power/pm_test
	echo mem > /sys/power/state		echo mem > /sys/power/state
	# Fail (usually, wake up 1 time of 7)		# Fail (usually, wake up 1 time of 7)
	</pre>		</pre>

Stuw: /* Tests */

2015-06-26T07:23:58Z

Tests

← Предыдущая версия		Версия от 07:23, 26 июня 2015
Строка 137:		Строка 137:
	echo devices > /sys/power/pm_tests		echo devices > /sys/power/pm_tests
	echo mem > /sys/power/state		echo mem > /sys/power/state
	# Fail (usually, ~~woked~~ up 1 time of 7)		# Fail (usually, wake up 1 time of 7)
	</pre>		</pre>

Stuw в 07:23, 26 июня 2015

2015-06-26T07:23:06Z

← Предыдущая версия		Версия от 07:23, 26 июня 2015
Строка 16:		Строка 16:
	[http://elinux.org/Android_Power_Management Android Power Management]		[http://elinux.org/Android_Power_Management Android Power Management]

	~~===Ideas===~~
	* don't disable serial console during suspend - no_console_suspend=1 (в cmdline)
	* enable kernel locks cheks
	* enable PM_DEBUG and PM_TRACE

	===Doesn't want to wake up?===		===Doesn't want to wake up?===
Строка 129:		Строка 125:

	===Tests===		===Tests===
			* don't disable serial console during suspend - no_console_suspend=1 (in cmdline)
			* PM_DEBUG and PM_TRACE must be enabled

	Looks like AC100 failes to resume from devices state.		Looks like AC100 failes to resume from devices state.
	<pre>		<pre>