Skip to contentSkip to conversation

n900 in 4.1-rc0

DISCUSSION Pavel Machek 5 participants 22 messages Apr 16, 2015 – Jul 28, 2015 Device tree bindings

lore
Share & tools
lore

Pavel Machek

author
#0 lore raw

Hi!

Just tried booting 4.1-rc0 on n900 (commit 34c9a0ffc75ad25b6a60f61e27c4a4b1189b8085) and it is broken.

Any ideas?
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#1 lore raw
Quoted 6 lines · Pavel Machek

Hi!

Just tried booting 4.1-rc0 on n900 (commit 34c9a0ffc75ad25b6a60f61e27c4a4b1189b8085) and it is broken.

Any ideas?

To such a question, the only answer I have is "Yes".

For a more useful reply, I'm afraid you'll have to ask a better question.

Thanks,

	M.
Signature · 1 line
Jazz is not dead. It just smells funny...
#2 lore raw
Quoted 11 lines · Marc Zyngier
Quoted 6 lines · Pavel Machek

Hi!

Just tried booting 4.1-rc0 on n900 (commit 34c9a0ffc75ad25b6a60f61e27c4a4b1189b8085) and it is broken.

Any ideas?

To such a question, the only answer I have is "Yes".

For a more useful reply, I'm afraid you'll have to ask a better question.

Just tried it at 34c9a0ffc75ad25b6a60f61e27c4a4b1189b8085 and it boots just fine on my n900.

Regards,

Tony

author
#3 lore raw
Quoted 7 lines · Tony Lindgren
Quoted 6 lines · Marc Zyngier
Quoted 5 lines · Pavel Machek

Hi!

Just tried booting 4.1-rc0 on n900 (commit 34c9a0ffc75ad25b6a60f61e27c4a4b1189b8085) and it is broken.

Quoted 8 lines
Quoted 5 lines
Quoted 1 line

Any ideas?

To such a question, the only answer I have is "Yes".

For a more useful reply, I'm afraid you'll have to ask a better question.

Just tried it at 34c9a0ffc75ad25b6a60f61e27c4a4b1189b8085 and it boots just fine on my n900.

Thanks for testing. I did some investigation, and found that twl4030 charger (that is not useful on n900) was breaking my boot. (And it may be interaction with some of my local changes).

Best regards (and sorry for the noise),
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#4 lore raw
In reply to Pavel Machek
Quoted 6 lines · Pavel Machek

Hi!

Just tried booting 4.1-rc0 on n900 (commit 34c9a0ffc75ad25b6a60f61e27c4a4b1189b8085) and it is broken.

Any ideas?

Looks like DT and legacy booting are working fine in our labs. [0][1]

Quoted 9 lines

Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

Tyler

[0] http://kernelci.org/boot/omap3-n900/
[1] http://kernelci.org/boot/omap3-n900,legacy/

author
#5 lore raw

Hi!

Quoted 7 lines
Quoted 4 lines

Just tried booting 4.1-rc0 on n900 (commit 34c9a0ffc75ad25b6a60f61e27c4a4b1189b8085) and it is broken.

Any ideas?

Looks like DT and legacy booting are working fine in our labs. [0][1]

Interesting web pages, thanks.

I noticed that legacy booting indicates broken today, but... Is there list of your targets somewhere?

Best regards,
Pavel

Quoted 2 lines

[0] http://kernelci.org/boot/omap3-n900/
[1] http://kernelci.org/boot/omap3-n900,legacy/

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#6 lore raw

Hi Pavel,

Quoted 11 lines · Pavel Machek

Hi!

Quoted 7 lines
Quoted 4 lines

Just tried booting 4.1-rc0 on n900 (commit 34c9a0ffc75ad25b6a60f61e27c4a4b1189b8085) and it is broken.

Any ideas?

Looks like DT and legacy booting are working fine in our labs. [0][1]

Interesting web pages, thanks.

No problem.

Quoted 3 lines

I noticed that legacy booting indicates broken today, but... Is there list of your targets somewhere?

It looks to have failed it's boot test on the stable v3.14 based LSK today, however it is booting fine still on the upstream development trees. You can also use a query[0] to refine your view if you would like. The up to date list of targets can be found here[1] and if interested in receiving email reports you can subscribe here[2].

Quoted 6 lines

Best regards,
Pavel

Quoted 6 lines
Quoted 2 lines

[0] http://kernelci.org/boot/omap3-n900/
[1] http://kernelci.org/boot/omap3-n900,legacy/

--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Cheers,

Tyler

[0] http://kernelci.org/boot/?n900&fail
[1] https://wiki.linaro.org/ProductTechnology/kernelci.org
[2] https://lists.linaro.org/mailman/listinfo/kernel-build-reports

author
#7 lore raw

n900 in 4.2-rc0: repeating oopses

In reply to Pavel Machek

Hi!

Just tried booting 4.2-rc0 on n900 (commit 4a10a91756ef381bced7b88cfb9232f660b92d93) and it is broken. Previous -rc0 version worked. This time, there's some output on console, but too fast for me to read.

It seems oopses happen before mounting root. If you have serial console, they should be easy to see.

I tried booting same kernel in qemu, but it seems to work ok there.

Any ideas? Thanks,
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#8 lore raw

Re: n900 in 4.2-rc0: repeating oopses

Hi!

Quoted 7 lines · On Monday 29 June 2015 11:11:46 Pavel Machek wrote:

Hi!

Just tried booting 4.2-rc0 on n900 (commit 4a10a91756ef381bced7b88cfb9232f660b92d93) and it is broken. Previous -rc0 version worked. This time, there's some output on console, but too fast for me to read.

What happen after errors are reported? Maybe you can enable R&D mode and disable HW watchdogs to prevent device reboots...

Quoted 5 lines

It seems oopses happen before mounting root. If you have serial console, they should be easy to see.

I tried booting same kernel in qemu, but it seems to work ok there.

Hm... Maybe problem with HS code?

By chance, can you try to disable (omap) sham node in n900 DT file? (same way like omap aes is disabled)

Quoted 2 lines

Any ideas? Thanks,
Pavel

Signature · 2 lines
Pali Roh?r
pali.rohar at gmail.com
author
#9 lore raw

Re: n900 in 4.2-rc0: repeating oopses

In reply to Pavel Machek

Hi!

Quoted 7 lines

Just tried booting 4.2-rc0 on n900 (commit 4a10a91756ef381bced7b88cfb9232f660b92d93) and it is broken. Previous -rc0 version worked. This time, there's some output on console, but too fast for me to read.

It seems oopses happen before mounting root. If you have serial console, they should be easy to see.

I tried again according to pali's instructions, and it is still broken the same way. Any other ideas? Does it work for you?

arch/arm/boot/dts/omap3.dtsi +1 -0
index 69a40cf..ff6f2bf 100644
@@ -570,6 +570,7 @@
 			interrupts = <49>;
 			dmas = <&sdma 69>;
 			dma-names = "rx";
+			status = "disabled";
 		};
 
 		smartreflex_core: smartreflex at 480cb000 {

Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#10 lore raw

Re: n900 in 4.2-rc0: repeating oopses

Quoted 26 lines · On Tuesday 30 June 2015 11:24:04 Pavel Machek wrote:

Hi!

Quoted 7 lines

Just tried booting 4.2-rc0 on n900 (commit 4a10a91756ef381bced7b88cfb9232f660b92d93) and it is broken. Previous -rc0 version worked. This time, there's some output on console, but too fast for me to read.

It seems oopses happen before mounting root. If you have serial console, they should be easy to see.

I tried again according to pali's instructions, and it is still broken the same way. Any other ideas? Does it work for you?

arch/arm/boot/dts/omap3.dtsi +1 -0
index 69a40cf..ff6f2bf 100644
@@ -570,6 +570,7 @@
 			interrupts = <49>;
 			dmas = <&sdma 69>;
 			dma-names = "rx";
+			status = "disabled";
 		};
 
 		smartreflex_core: smartreflex at 480cb000 {
Quoted 2 lines

Pavel

Ok, then it is not problem with omap crypto and HS device...

I will try 4.2 at the end of week.

Signature · 2 lines
Pali Roh?r
pali.rohar at gmail.com
#11 lore raw

Re: n900 in 4.2-rc0: repeating oopses

Quoted 2 lines · Pali Roh?r

I will try 4.2 at the end of week.

At least today's 4.1.0-11549-g05a8256 boots just fine on my n900.

Regards,

Tony

#12 lore raw

Re: n900 in 4.2-rc0: repeating oopses

Quoted 9 lines · On Tuesday 30 June 2015 23:59:33 Tony Lindgren wrote:
Quoted 2 lines · Pali Roh?r

I will try 4.2 at the end of week.

At least today's 4.1.0-11549-g05a8256 boots just fine on my n900.

Regards,

Tony

So, Pavel can you re-test? Maybe there can be problem with some driver which Tony did not compiled into zImage? Just speculation...

Signature · 2 lines
Pali Roh?r
pali.rohar at gmail.com
author
#13 lore raw

Re: n900 in 4.2-rc0: repeating oopses

Quoted 5 lines · Pali Roh?r
Quoted 4 lines · On Tuesday 30 June 2015 23:59:33 Tony Lindgren wrote:
Quoted 2 lines · Pali Roh?r

I will try 4.2 at the end of week.

Quoted 8 lines
Quoted 5 lines

At least today's 4.1.0-11549-g05a8256 boots just fine on my n900.

Regards,

Tony

So, Pavel can you re-test? Maybe there can be problem with some driver which Tony did not compiled into zImage? Just speculation...

I re-tested with today's git, and it seems to boot. Thanks for help...

Now. "echo mem > /sys/power/state" is broken, as in "returns immediately in about 50% cases". The messages are

Powerdomain (per_pwrdm) didn't enter target state 1 Powerdomain (core_pwerdm) didn't enter target state 1

Any ideas? Thanks,

Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#14 lore raw

Re: n900 in 4.2-rc0: repeating oopses

Quoted 8 lines · Pavel Machek
Quoted 7 lines · Pali Roh?r
Quoted 6 lines · On Tuesday 30 June 2015 23:59:33 Tony Lindgren wrote:
Quoted 2 lines · Pali Roh?r

I will try 4.2 at the end of week.

At least today's 4.1.0-11549-g05a8256 boots just fine on my n900.

Quoted 8 lines
Quoted 6 lines
Quoted 3 lines

Regards,

Tony

So, Pavel can you re-test? Maybe there can be problem with some driver which Tony did not compiled into zImage? Just speculation...

I re-tested with today's git, and it seems to boot. Thanks for help...

OK good to hear.

Quoted 7 lines

Now. "echo mem > /sys/power/state" is broken, as in "returns immediately in about 50% cases". The messages are

Powerdomain (per_pwrdm) didn't enter target state 1 Powerdomain (core_pwerdm) didn't enter target state 1

Any ideas? Thanks,

Works for me after enabling the idle timeouts with the following script and blanking the screen and disconnecting USB:

Also both keyboard LEDs should start blinking after the idle timeout with screen blanked and USB disconnected. If not, you have some module loaded that blocks the deeper idle states.

Regrads,

Tony

8< ----
#!/bin/bash

modprobe leds-gpio
modprobe ledtrig-default-on

uarts=$(find /sys/class/tty/ttyO*/device/power/ -type d) for uart in $uarts; do
echo 3000 > $uart/autosuspend_delay_ms #echo -1 > $uart/autosuspend_delay_ms
done

uarts=$(find /sys/class/tty/ttyO*/power/ -type d) for uart in $uarts; do
echo enabled > $uart/wakeup
echo auto > $uart/control
done

echo 255 > /sys/class/backlight/acx565akm/brightness echo 1 > /sys/devices/platform/omapfb/graphics/fb0/blank

echo 1 > /sys/kernel/debug/pm_debug/enable_off_mode

author
#15 lore raw

Re: n900 in 4.2-rc0: repeating oopses

Quoted 23 lines · Tony Lindgren
Quoted 8 lines · Pavel Machek
Quoted 7 lines · Pali Roh?r
Quoted 6 lines · On Tuesday 30 June 2015 23:59:33 Tony Lindgren wrote:
Quoted 2 lines · Pali Roh?r

I will try 4.2 at the end of week.

At least today's 4.1.0-11549-g05a8256 boots just fine on my n900.

Quoted 8 lines
Quoted 6 lines
Quoted 3 lines

Regards,

Tony

So, Pavel can you re-test? Maybe there can be problem with some driver which Tony did not compiled into zImage? Just speculation...

I re-tested with today's git, and it seems to boot. Thanks for help...

OK good to hear.

Quoted 3 lines

Now. "echo mem > /sys/power/state" is broken, as in "returns immediately in about 50% cases". The messages are

Quoted 7 lines
Quoted 4 lines

Powerdomain (per_pwrdm) didn't enter target state 1 Powerdomain (core_pwerdm) didn't enter target state 1

Any ideas? Thanks,

Works for me after enabling the idle timeouts with the following script and blanking the screen and disconnecting USB:

Um. I'm forcing suspend with "echo mem > /sys/power/state" . (It worked in 4.1). That should just make it sleep, no autosuspend-related trickery... (But yes, I guess I should set up the leds and try autosuspend, too.)

Regards,
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#16 lore raw

Re: n900 in 4.2-rc0: repeating oopses

Quoted 9 lines · Pavel Machek
Quoted 3 lines · Tony Lindgren

Works for me after enabling the idle timeouts with the following script and blanking the screen and disconnecting USB:

Um. I'm forcing suspend with "echo mem > /sys/power/state" . (It worked in 4.1). That should just make it sleep, no autosuspend-related trickery... (But yes, I guess I should set up the leds and try autosuspend, too.)

That too works just fine for me with omap2plus_defconfig after echo enabled > /sys/class/tty/ttyO2/power/wakeup as I have n900 in my test rack.

You probably have some additional drivers enabled?

Regards,

Tony

author
#17 lore raw

Re: n900 in 4.2-rc0: repeating oopses

Quoted 6 lines · Tony Lindgren
Quoted 5 lines · Pavel Machek
Quoted 3 lines · Tony Lindgren

Works for me after enabling the idle timeouts with the following script and blanking the screen and disconnecting USB:

Quoted 8 lines
Quoted 4 lines

Um. I'm forcing suspend with "echo mem > /sys/power/state" . (It worked in 4.1). That should just make it sleep, no autosuspend-related trickery... (But yes, I guess I should set up the leds and try autosuspend, too.)

That too works just fine for me with omap2plus_defconfig after echo enabled > /sys/class/tty/ttyO2/power/wakeup as I have n900 in my test rack.

Going through that. AFAICT, you are not using devicetree on n900?

CONFIG_MACH_NOKIA_RX51=y

Unfortunately, not having serials, it is tricky to get any output from that cnofiguration, so I don't know what I got wrong...
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#18 lore raw

Re: n900 in 4.2-rc0: repeating oopses

Quoted 16 lines · On Monday 27 July 2015 00:31:19 Pavel Machek wrote:
Quoted 6 lines · Tony Lindgren
Quoted 5 lines · Pavel Machek
Quoted 3 lines · Tony Lindgren

Works for me after enabling the idle timeouts with the following script and blanking the screen and disconnecting USB:

Quoted 8 lines
Quoted 4 lines

Um. I'm forcing suspend with "echo mem > /sys/power/state" . (It worked in 4.1). That should just make it sleep, no autosuspend-related trickery... (But yes, I guess I should set up the leds and try autosuspend, too.)

That too works just fine for me with omap2plus_defconfig after echo enabled > /sys/class/tty/ttyO2/power/wakeup as I have n900 in my test rack.

Quoted 7 lines

Going through that. AFAICT, you are not using devicetree on n900?

CONFIG_MACH_NOKIA_RX51=y

Unfortunately, not having serials, it is tricky to get any output from that cnofiguration, so I don't know what I got wrong...
Pavel

You can try to test it in qemu. It has emulation also of serial.

Signature · 2 lines
Pali Roh?r
pali.rohar at gmail.com
author
#19 lore raw

Re: n900 in 4.2-rc0: repeating oopses

In reply to Tony Lindgren
Quoted 11 lines · Tony Lindgren
Quoted 10 lines · Pavel Machek
Quoted 9 lines · Pali Roh?r
Quoted 8 lines · On Tuesday 30 June 2015 23:59:33 Tony Lindgren wrote:
Quoted 2 lines · Pali Roh?r

I will try 4.2 at the end of week.

At least today's 4.1.0-11549-g05a8256 boots just fine on my n900.

Regards,

Quoted 8 lines
Quoted 6 lines
Quoted 4 lines
Quoted 1 line

Tony

So, Pavel can you re-test? Maybe there can be problem with some driver which Tony did not compiled into zImage? Just speculation...

I re-tested with today's git, and it seems to boot. Thanks for help...

OK good to hear.

Hmm. Tried to toggle brightness on 4.1, and after few changes:

root at n900:~# echo 255 > /sys/class/backlight/acx565akm/brightness root at n900:~# echo 120 > /sys/class/backlight/acx565akm/brightness root at n900:~# echo 10 > /sys/class/backlight/acx565akm/brightness root at n900:~# echo 1 > /sys/class/backlight/acx565akm/brightness

^C^C
^Z

seems like acx565akm hung :-(.
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
author
#20 lore raw

Re: n900 in 4.2-rc0: repeating oopses

In reply to Tony Lindgren

Hi!

Quoted 13 lines
Quoted 4 lines
Quoted 2 lines

So, Pavel can you re-test? Maybe there can be problem with some driver which Tony did not compiled into zImage? Just speculation...

I re-tested with today's git, and it seems to boot. Thanks for help...

OK good to hear.

Quoted 6 lines

Now. "echo mem > /sys/power/state" is broken, as in "returns immediately in about 50% cases". The messages are

Powerdomain (per_pwrdm) didn't enter target state 1 Powerdomain (core_pwerdm) didn't enter target state 1

Quoted 8 lines
Quoted 1 line

Any ideas? Thanks,

Works for me after enabling the idle timeouts with the following script and blanking the screen and disconnecting USB:

Also both keyboard LEDs should start blinking after the idle timeout with screen blanked and USB disconnected. If not, you have some module loaded that blocks the deeper idle states.

Ok, tried that, I had to do:

cd /sys/class/gpio
echo 162 > export
cd gpio162
echo out > direction
echo 1 > value

to get the debug lights to work. But I could not get those leds to blink.

Quoted 2 lines

modprobe leds-gpio
modprobe ledtrig-default-on

Is this actually neccessary/relevant?

Quoted 1 line

echo 255 > /sys/class/backlight/acx565akm/brightness

And this?

Thanks,
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#21 lore raw

Re: n900 in 4.2-rc0: repeating oopses

Quoted 26 lines · Pavel Machek

Hi!

Quoted 13 lines
Quoted 4 lines
Quoted 2 lines

So, Pavel can you re-test? Maybe there can be problem with some driver which Tony did not compiled into zImage? Just speculation...

I re-tested with today's git, and it seems to boot. Thanks for help...

OK good to hear.

Quoted 6 lines

Now. "echo mem > /sys/power/state" is broken, as in "returns immediately in about 50% cases". The messages are

Powerdomain (per_pwrdm) didn't enter target state 1 Powerdomain (core_pwerdm) didn't enter target state 1

Quoted 8 lines
Quoted 1 line

Any ideas? Thanks,

Works for me after enabling the idle timeouts with the following script and blanking the screen and disconnecting USB:

Also both keyboard LEDs should start blinking after the idle timeout with screen blanked and USB disconnected. If not, you have some module loaded that blocks the deeper idle states.

Ok, tried that, I had to do:

Quoted 8 lines

cd /sys/class/gpio
echo 162 > export
cd gpio162
echo out > direction
echo 1 > value

to get the debug lights to work. But I could not get those leds to blink.

I think that's the GPIO override for them? And in that case the PMIC sys_clkreq and sys_off_mode signals are not cutting off the LEDs I believe.

Also not that any driver blocking the deeper idle states will also cause the LEDs to stay on. And USB cable being plugged in too at least for core off.. So you if you're using NFSroot over USB Ethernet, you probably can only see the left LED ever go off.

Quoted 4 lines
Quoted 2 lines

modprobe leds-gpio
modprobe ledtrig-default-on

Is this actually neccessary/relevant?

Yes at least with omap2plus_defconfig.

Quoted 3 lines
Quoted 1 line

echo 255 > /sys/class/backlight/acx565akm/brightness

And this?

It used to be the backlight did not come on initially as modules or something.. May not be needed any longer.

Regards,

Tony