Per Jessen wrote:

I'm trying to use the 15.2 JeOS image for Nanopi Neo on my Nanopi Neo Air - I have done this before with 15.0, but now it just grinds to a halt. After creating an SD card (16Gb) and booting it, the nano just appears to, well, not do very much. An hour in and the H3 cpu has gotten hot enough, burns your finger. Surely it can't take an hour to expand the initial filesystem to a 16Gb card ?

Confirm - with the 15.1 JeOS image, it take only minutes. Clearly 15.2 is borked. -- Per Jessen, Zürich (0.8°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland.

Guillaume Gardet wrote:

Hi,

Would you have a serial cable to check early boot messages?

Yep, once it starts booting, this is what I get - Booting `openSUSE Leap 15.2' Loading Linux 5.3.18-lp152.47-lpae ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... EHCI failed to shut down host controller. I can probably get the output before that by running a capture, if it is interesting.

Could you also test the Tumbleweed image, please?

Willdo. -- Per Jessen, Zürich (0.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland.

-----Original Message----- From: Per Jessen Sent: 04 January 2021 09:41 To: arm@lists.opensuse.org Subject: RE: Leap 15.2 on Nanopi Neo Air ?

Guillaume Gardet wrote:

...

Hi,

Would you have a serial cable to check early boot messages?

Yep, once it starts booting, this is what I get -

Booting `openSUSE Leap 15.2'

Loading Linux 5.3.18-lp152.47-lpae ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... EHCI failed to shut down host controller.

Ok, so u-boot/grub2 started and loaded kernel/initrd. Could you create a bug report on bugzilla.opensuse.org so that we can track this problem properly, please?

I can probably get the output before that by running a capture, if it is interesting.

...

Could you also test the Tumbleweed image, please?

Willdo.

Great, thanks! Guillaume

-- Per Jessen, Zürich (0.4°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland.

Hi Per, On 04.01.21 09:40, Per Jessen wrote:

Guillaume Gardet wrote:

...

Hi,

Would you have a serial cable to check early boot messages?

Yep, once it starts booting, this is what I get -

Booting `openSUSE Leap 15.2'

Loading Linux 5.3.18-lp152.47-lpae ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... EHCI failed to shut down host controller.

I can probably get the output before that by running a capture, if it is interesting.

In my experience the things after that are more interesting ;-) In grub, edit the command line, put "console=ttyS0..." last (after "console=tty") and maybe add "earlyprintk=serial,ttyS0,115200", then remove the "loglevel=...", "splash=..." and instead add "debug" to get as much output from the kernel as early as possible. Good luck :-) -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman

Per Jessen wrote:

Stefan Seyfried wrote:

...

Hi Per,

On 04.01.21 09:40, Per Jessen wrote:

...

I can probably get the output before that by running a capture, if it is interesting.

In my experience the things after that are more interesting ;-)

Hi Stefan

Yeah, I think you might be right :-)

...

In grub, edit the command line, put "console=ttyS0..." last (after "console=tty") and maybe add "earlyprintk=serial,ttyS0,115200", then remove the "loglevel=...", "splash=..." and instead add "debug" to get as much output from the kernel as early as possible.

I tried that, still no more output after this line: EHCI failed to shut down host controller. -- Per Jessen, Zürich (0.7°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland.

Stefan Seyfried wrote:

Hi Per,

On 04.01.21 14:13, Per Jessen wrote:

...

...

...

In grub, edit the command line, put "console=ttyS0..." last (after "console=tty") and maybe add "earlyprintk=serial,ttyS0,115200", then remove the "loglevel=...", "splash=..." and instead add "debug" to get as much output from the kernel as early as possible.

I tried that, still no more output after this line:

OK, then it is of course possible that the kernel just does not start at all.

If you'd want to give it another try, one method to verify that your command line is actually working for early kernel debugging

I tried the same options with the TW jeOS image, works fine: Loading Linux 5.8.15-1-lpae ... mods Loading initial ramdisk ... EFI stub: Entering in HYP mode with MMU enabled EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... EHCI failed to shut down host controller. [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.8.15-1-lpae (geeko@buildhost) (gcc (SUSE Linux) 10.2.1 20200825 [revision c0746a1beb1ba073c7981eb09f55b3d993b32e5c], GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.34.0.20200325-1) #1 SMP Thu Oct 15 08:10:08 UTC 2020 (c680e93) [ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=30c5387d [ 0.000000] CPU: div instructions available: patching division code [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [ 0.000000] OF: fdt: Machine model: FriendlyARM NanoPi NEO [ 0.000000] Memory policy: Data cache writealloc [ 0.000000] efi: EFI v2.80 by Das U-Boot [ 0.000000] efi: RTPROP=0x5af49040 SMBIOS=0x5af48000 MEMRESERVE=0x512a7040 [ 0.000000] efi: [Firmware Bug]: ExitBootServices() returned with MMU and Dcache disabled, please fix your firmware! [ 0.000000] efi: CPSR at EFI stub entry : 0x600001da [ 0.000000] efi: SCTLR at EFI stub entry : 0x30c5087d [ 0.000000] efi: CPSR after ExitBootServices() : 0x600001da [ 0.000000] efi: SCTLR after ExitBootServices(): 0x30c50878 [ 0.000000] cma: Reserved 64 MiB at 0x000000005bc00000 Kernel command line: BOOT_IMAGE=/boot/zImage-5.8.15-1-lpae root=UUID=32ca1b87-ae87-4304-8a89-754e69244b54 rw debug earlyprintk=serial,ttyS0,115200 console=ttyS0,115200,8n1 plymouth.enable=0 -- Per Jessen, Zürich (-0.6°C)

Lubos Kocman wrote:

Hello,

that sounds clearly as regresssion to me, can you please make sure to open a tracker for it?

Hi Lubos, yep, I did so yesterday - https://bugzilla.suse.com/show_bug.cgi?id=1180508 -- Per Jessen, Zürich (-0.1°C)

Hello Per and Guillaume what do you suggest as next steps? Do we have already a tracker for the Nanopi Neo regression? Lubos On Sun, 2021-01-03 at 20:13 +0100, Per Jessen wrote:

Per Jessen wrote:

...

I'm trying to use the 15.2 JeOS image for Nanopi Neo on my Nanopi Neo Air - I have done this before with 15.0, but now it just grinds to a halt.  After creating an SD card (16Gb) and booting it, the nano just appears to, well, not do very much.  An hour in and the H3 cpu has gotten hot enough, burns your finger.  Surely it can't take an hour to expand the initial filesystem to a 16Gb card ?

Confirm - with the 15.1 JeOS image, it take only minutes.  Clearly 15.2 is borked.

-- Lubos Kocman Release Manager openSUSE Leap SUSE LINUX, s.r.o. Krizikova 148/34 tel: +49 173 5876850 186 00 Praha 8 http://www.suse.com Czech Republic

-----Original Message----- From: Per Jessen Sent: 12 January 2021 17:41 To: arm@lists.opensuse.org Subject: Re: Leap 15.2 on Nanopi Neo Air ?

Per Jessen wrote:

...

Per Jessen wrote:

...

I'm trying to use the 15.2 JeOS image for Nanopi Neo on my Nanopi Neo Air - I have done this before with 15.0, but now it just grinds to a halt. After creating an SD card (16Gb) and booting it, the nano just appears to, well, not do very much. An hour in and the H3 cpu has gotten hot enough, burns your finger. Surely it can't take an hour to expand the initial filesystem to a 16Gb card ?

Confirm - with the 15.1 JeOS image, it take only minutes. Clearly 15.2 is borked.

For the record, it appears to be the JeOS image that has a problem, I have just today zypper dupped three boards to 15.2, works just fine.

This suggest a problem with u-boot which is the only part which is not upgraded. Guillaume

-- Per Jessen, Zürich (1.7°C) Member, openSUSE Heroes

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.