Possible regression 2023.12 -> 2024.01

Possible regression 2023.12 -> 2024.01

[Alexander Shiyan]

Hello.

Here is an output with bb 2023.12.0:

barebox 2023.12.0-00134-gad7f545cf97d #6 Wed Jan 31 13:37:45 MSK 2024
Board: Diasom DS-IMX8M-EVB
deep-probe: supported due to diasom,ds-imx8m-evb
detected i.MX8MM revision 1.0
i.MX8MM unique ID: 1e0769aac2a3784a
netconsole: registered as netconsole-1
WARNING: imx-esdhc 30b40000.mmc@30b40000.of: Failed to get 'vmmc'
regulator (ignored).
imx-esdhc 30b40000.mmc@30b40000.of: registered as mmc0
mmc0: detected MMC card version 5.1
mmc0: registered mmc0.boot0
mmc0: registered mmc0.boot1
WARNING: mmc0: GPT:Primary header thinks Alt. header is not at the end
of the disk.
WARNING: mmc0: GPT:1040487 != 7634943
WARNING: mmc0: GPT:Alternate GPT header not at the end of the disk.
WARNING: mmc0: GPT:1040487 != 7634943
WARNING: mmc0: GPT: Use GNU Parted to correct GPT errors.
mmc0: registered mmc0
imx-esdhc 30b50000.mmc@30b50000.of: registered as mmc1
mmc1: detected SD card version 2.0
WARNING: mmc1: GPT:Primary header thinks Alt. header is not at the end
of the disk.
WARNING: mmc1: GPT:1757287 != 60579839
WARNING: mmc1: GPT:Alternate GPT header not at the end of the disk.
WARNING: mmc1: GPT:1757287 != 60579839
WARNING: mmc1: GPT: Use GNU Parted to correct GPT errors.
mmc1: registered mmc1
imx-usb 32e50000.usb@32e50000.of: USB EHCI 1.00
malloc space: 0x7fefe200 -> 0xbfdfc3ff (size 1023 MiB)
envfs: no envfs (magic mismatch) - envfs never written?
multi_bind: creating Fastboot function
multi_bind: creating USB Mass Storage function
multi_bind: creating ACM function
g_multi gadget0: Multifunction Composite Gadget
g_multi gadget0: g_multi ready
Hit m for menu or any to stop autoboot:    9

Here is an output with bb 2024.01.0:

barebox 2024.01.0-00135-g2449d030bcf1 #5 Wed Jan 31 12:43:50 MSK 2024
Board: Diasom DS-IMX8M-EVB
deep-probe: supported due to diasom,ds-imx8m-evb
detected i.MX8MM revision 1.0
i.MX8MM unique ID: 1e0769aac2a3784a
netconsole: registered as netconsole-1
WARNING: imx-esdhc 30b40000.mmc@30b40000.of: Failed to get 'vmmc'
regulator (ignored).
imx-esdhc 30b40000.mmc@30b40000.of: registered as mmc0
mmc0: detected MMC card version 5.1
mmc0: registered mmc0.boot0
mmc0: registered mmc0.boot1
WARNING: mmc0: GPT:Primary header thinks Alt. header is not at the end
of the disk.
WARNING: mmc0: GPT:1040487 != 7634943
WARNING: mmc0: GPT:Alternate GPT header not at the end of the disk.
WARNING: mmc0: GPT:1040487 != 7634943
WARNING: mmc0: GPT: Use GNU Parted to correct GPT errors.
mmc0: registered mmc0
imx-esdhc 30b50000.mmc@30b50000.of: registered as mmc1
mmc1: detected SD card version 2.0
ERROR: mmc1: Cannot read MBR/partition table: I/O error
mmc1: registered mmc1
imx-usb 32e50000.usb@32e50000.of: USB EHCI 1.00
malloc space: 0x7fefe200 -> 0xbfdfc3ff (size 1023 MiB)
ERROR: barebox-environment chosen:environment-sd.of: probe failed: No
such file or directory
environment load /dev/env0: No such file or directory
Maybe you have to create the partition.
multi_bind: creating Fastboot function
multi_bind: creating USB Mass Storage function
multi_bind: creating ACM function
g_multi gadget0: Multifunction Composite Gadget
g_multi gadget0: g_multi ready
Hit m for menu or any to stop autoboot:

The booting freezes (~5 s or so) during the mmc1 detection process.
Also, for reasons unknown to me, the kernel now throws an error when loading:

mmc1: Timeout waiting for hardware interrupt.
mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
mmc1: sdhci: Sys addr:  0x00000008 | Version:  0x00000002
mmc1: sdhci: Blk size:  0x00000200 | Blk cnt:  0x00000008
mmc1: sdhci: Argument:  0x00000000 | Trn mode: 0x0000003b
mmc1: sdhci: Present:   0x01f8820e | Host ctl: 0x00000013
mmc1: sdhci: Power:     0x00000002 | Blk gap:  0x00000080
mmc1: sdhci: Wake-up:   0x00000008 | Clock:    0x00000077
mmc1: sdhci: Timeout:   0x0000000f | Int stat: 0x00000000
mmc1: sdhci: Int enab:  0x117f100b | Sig enab: 0x117f100b
mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000502
mmc1: sdhci: Caps:      0x07eb0000 | Caps_1:   0x0000b407
mmc1: sdhci: Cmd:       0x0000123a | Max curr: 0x00ffffff
mmc1: sdhci: Resp[0]:   0x00000900 | Resp[1]:  0x00e7177f
mmc1: sdhci: Resp[2]:   0x325b5900 | Resp[3]:  0x00000900
mmc1: sdhci: Host ctl2: 0x00000000
mmc1: sdhci: ADMA Err:  0x00000003 | ADMA Ptr: 0x42133204
mmc1: sdhci-esdhc-imx: ========= ESDHC IMX DEBUG STATUS DUMP =========
mmc1: sdhci-esdhc-imx: cmd debug status:  0x3100
mmc1: sdhci-esdhc-imx: data debug status:  0x32a0
mmc1: sdhci-esdhc-imx: trans debug status:  0x33a0
mmc1: sdhci-esdhc-imx: dma debug status:  0x3400
mmc1: sdhci-esdhc-imx: adma debug status:  0x35b4
mmc1: sdhci-esdhc-imx: fifo debug status:  0x3680
mmc1: sdhci-esdhc-imx: async fifo debug status:  0x3750
mmc1: sdhci: ============================================

Any ideas?

Thanks!

Re: Possible regression 2023.12 -> 2024.01

[Ahmad Fatoum]

Hello Alexander,

On 31.01.24 12:03, Alexander Shiyan wrote:
> ERROR: mmc1: Cannot read MBR/partition table: I/O error
> mmc1: registered mmc1

I observe no such issues with v2024.01.0 on the NXP i.MX8MN EVK, which
has both SD-Card and eMMC (I booted from SD-Card).

Given that you have a known good, could you run git bisect and
see what commit is reported as introducing the regression?

> The booting freezes (~5 s or so) during the mmc1 detection process.
> Also, for reasons unknown to me, the kernel now throws an error when loading:

I'd assume these are consequences of the initial EIO.
Once we have the culprit commit, we may understand better what happens.

Let me know how it goes.

Cheers,
Ahmad

-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |