[Letux-kernel] 4.16 boot hickups

[H. Nikolaus Schaller]

Hi Marek,

> Am 13.04.2018 um 08:53 schrieb Belisko Marek <marek.belisko at gmail.com>:
> 
> Hi,
> 
> On Fri, Apr 13, 2018 at 8:41 AM, H. Nikolaus Schaller <hns at goldelico.com> wrote:
>> Hi Andreas,
>> 
>>> Am 12.04.2018 um 17:24 schrieb H. Nikolaus Schaller <hns at goldelico.com>:
>>> 
>>> 
>>>> Am 12.04.2018 um 17:02 schrieb Andreas Kemnade <andreas at kemnade.info>:
>>>> 
>>>> Hi,
>>>> 
>>>> 
>>>> On Thu, 12 Apr 2018 14:55:29 +0200
>>>> "H. Nikolaus Schaller" <hns at goldelico.com> wrote:
>>>> 
>>>>> And sometimes I see (on GTA04A4):
>>>>> 
>>>> I hate the word "sometimes" in this context...
>>> 
>>> Me too - but so far that describes our knowledge best :)
>>> 
>>> I didn't have it before 4.16.0. So it must be very new...
>>> 
>>>> 
>>>>> [    3.104858] omap2_set_init_voltage: unable to find boot up OPP for vdd_core
>>>>> [    3.112213] omap2_set_init_voltage: unable to set vdd_core
>>>> well, these messages are quite common.
>>> 
>>> Haven't seen them before. Especially as a prefix for:
>>> 
>>>> 
>>>>> --- nothing happens any more ----
>> 
>> Wel, I have now compared with the GTA04A5 board and there I have the same
>> messages - but boot works immediately.
>> 
>> [    2.170623] mmc0: new high speed SDHC card at address b368
>> [    2.176635] NET: Registered protocol family 17
>> [    2.181335] NET: Registered protocol family 15
>> [    2.187164] mmcblk0: mmc0:b368 USD   7.47 GiB
>> [    2.192993] Key type dns_resolver registered
>> [    2.198883] omap2_set_init_voltage: unable to find boot up OPP for vdd_core
>> [    2.206237] omap2_set_init_voltage: unable to set vdd_core
>> [    2.212829]  mmcblk0: p1
>> [    2.218170] ThumbEE CPU extension supported.
>> [    2.222656] Registering SWP/SWPB emulation handler
>> [    2.228332] SmartReflex Class3 initialized
>> 
>> Strange. Seems to need a deeper analysis why A4 and A5 are again different
>> here. Especially I have to compare if that is only for this A4 board and how
>> older kernels do.
> I think I was looking at those warnings some time ago but it was
> harmless (something with cpufreq or so).

Indeed. These warnings have nothing to do with the hickup I am facing.

Interestingly it does not appear on all GTA04A4 boards I have tried.
And not always.

What I now got was

[    3.080444] Initializing XFRM netlink socket
[    3.084930] NET: Registered protocol family 17
[    3.089904] NET: Registered protocol family 15
[    3.094635] Key type dns_resolver registered
[    3.100646] omap2_set_init_voltage: unable to find boot up OPP for vdd_core
[    3.107971] omap2_set_init_voltage: unable to set vdd_core
[    3.115722] ThumbEE CPU extension supported.
[    3.120788] Registering SWP/SWPB emulation handler
[    3.125854] mmc0: host does not support reading read-only switch, assuming write-enable
[    3.134307] SmartReflex Class3 initialized
[    3.139862] Loading compiled-in X.509 certificates
[    3.151763] mmc0: new high speed SDHC card at address b368
[    3.168395] mmcblk0: mmc0:b368 USD   7.47 GiB 
[    3.176116] ubi0: default fastmap pool size: 200
[    3.181640] ubi0: default fastmap WL pool size: 100
[    3.186767] ubi0: attaching mtd4
[    3.192413]  mmcblk0: p1
[    3.227783] ubi0: fixable bit-flip detected at PEB 113
[    3.233276] ubi0: fixable bit-flip detected at PEB 113
[    3.238922] ubi0: fixable bit-flip detected at PEB 114
[    3.244384] ubi0: fixable bit-flip detected at PEB 114
[    3.250061] ubi0: fixable bit-flip detected at PEB 115
[    3.255432] ubi0: fixable bit-flip detected at PEB 115
[    3.261108] ubi0: fixable bit-flip detected at PEB 116
[    3.266479] ubi0: fixable bit-flip detected at PEB 116
[    3.272460] ubi0: fixable bit-flip detected at PEB 118
[    3.277832] ubi0: fixable bit-flip detected at PEB 118
...
[    5.011779] ubi0: fixable bit-flip detected at PEB 479
[    5.017150] ubi0: fixable bit-flip detected at PEB 479
[    5.430328] ubi0: fixable bit-flip detected at PEB 1980
[    5.435821] ubi0 error: scan_peb: bad image sequence number 1311990011 in PEB 1980, expected 1795890576
[    5.445678] Erase counter header dump:
[    5.449645]  magic          0x55424923
[    5.453552]  version        1
[    5.456665]  ec             2
[    5.459808]  vid_hdr_offset 512
[    5.463073]  data_offset    2048
[    5.466461]  image_seq      1311990011
[    5.470397]  hdr_crc        0xf1ca49b7
[    5.474304] erase counter header hexdump:
[    5.478485] 00000000: 55 42 49 23 01 00 00 00 00 00 00 00 00 00 00 02 00 00 02 00 00 00 08 00 4e 33 60 fb 00 00 00 00  UBI#....................N3`.....
[    5.492706] 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 f1 ca 49 b7  ..............................I.
[    5.507537] ubi0 error: ubi_attach_mtd_dev: failed to attach mtd4, error -22
[    5.515045] UBI error: cannot attach mtd4
[    5.520446] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[    5.530426] input: gpio-keys-wwan-wakeup as /devices/platform/gpio-keys-wwan-wakeup/input/input1
...
letux login:

So I think it also *has* something to do with the new NAND/OneNAND code.
Maybe if the NAND isn't formatted correctly (I don't know how and when it was flashed last time).

I wasn't able to mount NAND on this device manually either.

So I'll reformat it and then let's see if the problem is still there.

BR,
Nikolaus