Bug 12849 - NanoPi R2S - Stuck during boot of CU 167 (testing)
Summary: NanoPi R2S - Stuck during boot of CU 167 (testing)
Status: CLOSED DUPLICATE of bug 12859
Alias: None
Product: IPFire
Classification: Unclassified
Component: --- (show other bugs)
Version: 2
Hardware: unspecified Unspecified
: - Unknown - Crash
Assignee: Arne.F
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-13 21:37 UTC by Jon
Modified: 2022-05-03 07:19 UTC (History)
3 users (show)

See Also:


Attachments
R2S log (77.17 KB, text/plain)
2022-04-14 14:45 UTC, Jon
Details
r2s messages log (15.95 KB, text/plain)
2022-04-14 20:54 UTC, Jon
Details
new log for R2S (12.48 KB, text/plain)
2022-04-24 21:00 UTC, Jon
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jon 2022-04-13 21:37:06 UTC
I updated a NanoPi R2S from CU 165 to 166 and all went A-OK.  But I tried to update from CU 166 to CU 167 testing but it failed during the reboot.

A power down/up did not help.

Here are the last few lines, but I can send the entire log if needed.


```
Waiting for root device UUID=1eb1207a-d1e3-4667-xxxxxxxxxxx...
random: fast init done
mmc_host mmc0: Bus speed (slot 0) = 100000000Hz (slot req 100000000Hz, actual 100000000HZ div = 0)
dwmmc_rockchip ff500000.mmc: Successfully tuned phase to 121
mmc0: new ultra high speed SDR50 SDHC card at address aaaa
mmcblk0: mmc0:aaaa SU08G 7.40 GiB 
 mmcblk0: p1 p2 p3
```
Comment 1 Michael Tremer 2022-04-14 07:12:16 UTC
(In reply to Jon from comment #0)
> Here are the last few lines, but I can send the entire log if needed.

Yes, please do.
Comment 2 Jon 2022-04-14 14:45:02 UTC
Created attachment 1036 [details]
R2S log
Comment 3 Jon 2022-04-14 20:54:14 UTC
Created attachment 1037 [details]
r2s messages log

I cleaned out all of the DROP_ entries.  And this is everything up until it all crashed.
Comment 4 Peter Müller 2022-04-24 14:39:39 UTC
Arne updated the kernel to 5.15.35 the other days, since that fixed a few particularly nasty crashes and instabilities with various network cards.

@Jon: Are you able to reproduce this crash with the very latest state of Core Update 167 (testing)?
Comment 5 Jon 2022-04-24 21:00:33 UTC
Created attachment 1039 [details]
new log for R2S

no joy...

Went through the update process and got to the "must restart" prompt.  The R2S never re-boots and just stops at:

```
md: ... autorun DONE.
Waiting for root device UUID=dd649bf0-0d54-4f8f-a8c5-d999dc0ab1c7...
random: fast init done
mmc_host mmc0: Bus speed (slot 0) = 100000000Hz (slot req 100000000Hz, actual 100000000HZ div = 0)
dwmmc_rockchip ff500000.mmc: Successfully tuned phase to 119
mmc0: new ultra high speed SDR50 SDHC card at address aaaa
mmcblk0: mmc0:aaaa SL08G 7.40 GiB 
 mmcblk0: p1 p2 p3
```


IPFire 2.27 (aarch64) - Core Update 167 Development Build: master/1bd22b04
Comment 6 Peter Müller 2022-05-03 07:17:22 UTC
https://community.ipfire.org/t/core-update-167-requires-additional-step-for-arm-users-before-rebooting/7852/2

Zut alors, this completely slipped through QA. :-/
Comment 7 Peter Müller 2022-05-03 07:19:06 UTC

*** This bug has been marked as a duplicate of bug 12859 ***