On Sat, Sep 04, 2021 at 06:50:16PM +0100, Steve McIntyre wrote:
>
>I have a synquacer here still and I'll take a look. I noticed on
>bullseye release day that USB stuff didn't seem to work in the
>installer on the synquacer either. Maybe there's been a regression in
>config. :-/
>
>I'll take a look...

Hmmm, booting 5.10.0-0.bpo.8-arm64 here does not work at all. I'm
seeing a lot of errors around DMA setup, e.g.:

[    0.142797] OF: translation of DMA address(0) to CPU address failed node()
[    0.142824] sram 45200000.sram: Invalid size 0x1 for dma-range(s)
[    0.142991] OF: translation of DMA address(0) to CPU address failed node()
[    0.143008] uart-pl011 2a400000.uart: Invalid size 0x1 for dma-range(s)
...
[    3.843964] OF: translation of DMA address(0) to CPU address failed node()
[    3.850875] armv8-pmu pmu: Invalid size 0x1 for dma-range(s)
[    3.857518] hw perfevents: enabled with armv8_pmuv3 PMU driver, 7 counters 
available
...
[    3.954986] OF: translation of DMA address(0) to CPU address failed node()
...
[    4.391564] OF: translation of DMA address(0) to CPU address failed node()
[    4.398449] pcieport 0000:00:00.0: Invalid size 0x1 for dma-range(s)
[    4.405253] OF: translation of DMA address(0) to CPU address failed node()
[    4.412161] pcieport 0000:01:01.0: Invalid size 0x1 for dma-range(s)
[    4.418885] OF: translation of DMA address(0) to CPU address failed node()
[    4.425778] pcieport 0000:01:03.0: Invalid size 0x1 for dma-range(s)
[    4.432487] OF: translation of DMA address(0) to CPU address failed node()
[    4.439385] pcieport 0000:01:05.0: Invalid size 0x1 for dma-range(s)
[    4.446095] OF: translation of DMA address(0) to CPU address failed node()
[    4.452988] pcieport 0000:01:07.0: Invalid size 0x1 for dma-range(s)
[    4.459693] pci 0000:04:00.0: enabling device (0000 -> 0002)
[    4.465488] OF: translation of DMA address(0) to CPU address failed node()
...
[    4.472385] pci-host-generic 70000000.pcie: Invalid size 0x1 for dma-range(s)

Shortly after this, I see looping errors in the sdhci driver:
[    5.728589] xhci_hcd: probe of 0000:04:00.0 failed with error -12
[    5.734347] sp : ffff8000142bbb10
[    5.734351] x29: ffff8000142bbb10 x28: 0000000000000000 
[    5.734358] x27: ffff000801ebf848 x26: ffffffffffffffff 
[    5.768201] x25: 0000000000000080 x24: 0000000000010000 
[    5.773514] x23: ffff00080176ac10 x22: 0000000889b60080 
[    5.778826] x21: 0000000000000000 x20: 0000000000000000 
[    5.784139] x19: ffff8000117c9788 x18: 0000000000000020 
[    5.789451] x17: ffff00080833da00 x16: 0000000000000080 
[    5.794763] x15: ffffffffffffffff x14: 2820776f6c667265 
[    5.800076] x13: 766f203633353536 x12: 2b66666666666666 
[    5.805389] x11: 6666666666666666 x10: 6678302072646461 
[    5.810701] x9 : ffff80001011159c x8 : 62202c6666666666 
[    5.816013] x7 : 666666206b73616d x6 : ffff00087f4647c0 
[    5.821325] x5 : ffff8000142bb828 x4 : 0000000000000000 
[    5.826637] x3 : 0000000000000000 x2 : 00000000ffffffff 
[    5.831949] x1 : 3082d45f0379e900 x0 : 0000000000000000 
[    5.837262] Call trace:
[    5.839708]  swiotlb_map+0x294/0x2a8
[    5.843281]  dma_map_page_attrs+0xec/0x228
[    5.847382]  sdhci_setup_host+0xa8c/0xee8 [sdhci]
[    5.852086]  sdhci_add_host+0x20/0x58 [sdhci]
[    5.856444]  sdhci_f_sdh30_probe+0x2a8/0x380 [sdhci_f_sdh30]
[    5.862104]  platform_drv_probe+0x5c/0xb0
[    5.866113]  really_probe+0xf0/0x4d8
[    5.869686]  driver_probe_device+0xfc/0x168
[    5.873868]  __driver_attach_async_helper+0xbc/0xc8
[    5.878743]  async_run_entry_fn+0x50/0x218
[    5.882837]  process_one_work+0x1bc/0x480
[    5.886843]  worker_thread+0x158/0x4e0
[    5.890590]  kthread+0x12c/0x130
[    5.893817]  ret_from_fork+0x10/0x30
[    5.897389] ---[ end trace 986b9b1a11578595 ]---

Longer log attached. I'm wondering if there's a DTB mismatch or
something - my system here is still using the built-in DTB from the
EFI firmware, and I don't see a newer DTB available in the debian
package nor in upstream git.

@Arnd any clues please?

-- 
Steve McIntyre, Cambridge, UK.                                st...@einval.com
“Changing random stuff until your program works is bad coding
 practice, but if you do it fast enough it’s Machine Learning.”
   -- https://twitter.com/manisha72617183

Attachment: synquacer.log.gz
Description: application/gzip

Reply via email to