JeOS after zypper dup errors in console

English Install/Boot/Login
1

Hi!

Took my old TW JeOS from last year and burned it to SD-card, as officially proposed. After zypper dup and reboot the console is full of chatter:

ace for 397300 bytes
  313.191118] mmcblk1: error -22 transferring data, sector 1146312, nr 824, cmd response 0x900, card status 0x0
  313.376012] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 397300 bytes
  313.424444] mmcblk1: error -22 transferring data, sector 1146312, nr 824, cmd response 0x900, card status 0x0
  313.454270] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 397300 bytes
  313.502074] mmcblk1: error -22 transferring data, sector 1146313, nr 823, cmd response 0x900, card status 0x0
  313.686364] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 397300 bytes
  313.735480] mmcblk1: error -22 transferring data, sector 1146313, nr 823, cmd response 0x900, card status 0x0
  313.997476] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 331764 bytes
  314.047019] mmcblk1: error -22 transferring data, sector 1145456, nr 856, cmd response 0x900, card status 0x0
  314.225992] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 331764 bytes
  314.276565] mmcblk1: error -22 transferring data, sector 1145456, nr 856, cmd response 0x900, card status 0x0
  314.720324] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 380916 bytes
  314.766919] mmcblk1: error -22 transferring data, sector 3460168, nr 744, cmd response 0x900, card status 0x0
  314.946279] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 380916 bytes
  314.994032] mmcblk1: error -22 transferring data, sector 3460168, nr 744, cmd response 0x900, card status 0x0
  315.252334] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 454644 bytes
  315.305819] mmcblk1: error -22 transferring data, sector 3458720, nr 1024, cmd response 0x900, card status 0x0
  315.486041] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 454644 bytes
  315.540466] mmcblk1: error -22 transferring data, sector 3458720, nr 1024, cmd response 0x900, card status 0x0
  316.110132] mmcblk1: error -22 transferring data, sector 2467776, nr 992, cmd response 0x900, card status 0x0
  316.321869] mmcblk1: error -22 transferring data, sector 2467776, nr 992, cmd response 0x900, card status 0x0
  316.663284] mmcblk1: error -22 transferring data, sector 942112, nr 992, cmd response 0x900, card status 0x0
  316.871679] mmcblk1: error -22 transferring data, sector 942112, nr 992, cmd response 0x900, card status 0x0
  317.207447] mmcblk1: error -22 transferring data, sector 2468768, nr 656, cmd response 0x900, card status 0x0
  317.403486] mmcblk1: error -22 transferring data, sector 2468768, nr 656, cmd response 0x900, card status 0x0
  317.636639] mmcblk1: error -22 transferring data, sector 943104, nr 544, cmd response 0x900, card status 0x0
  317.830645] mmcblk1: error -22 transferring data, sector 943104, nr 544, cmd response 0x900, card status 0x0
  318.564371] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 376832 bytes
  318.627313] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 524288 bytes
  318.701852] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 524288 bytes
  319.008186] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 450560 bytes
  319.088672] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 524288 bytes
  319.282294] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 483328 bytes
  319.354521] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 499712 bytes
  319.645563] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 262132 bytes
  319.684107] mmcblk1: error -22 transferring data, sector 2593184, nr 512, cmd response 0x900, card status 0x0
  319.866256] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 262132 bytes
  319.906183] mmcblk1: error -22 transferring data, sector 2593184, nr 512, cmd response 0x900, card status 0x0
  320.077958] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 286708 bytes
  320.118625] mmcblk1: error -22 transferring data, sector 2593696, nr 560, cmd response 0x900, card status 0x0
  320.311163] mmcblk1: error -22 transferring data, sector 2593696, nr 560, cmd response 0x900, card status 0x0
Loading repository data...
  321.424433] mmcblk1: error -22 transferring data, sector 3380128, nr 1024, cmd response 0x900, card status 0x0
  321.632456] mmcblk1: error -22 transferring data, sector 3380128, nr 1024, cmd response 0x900, card status 0x0
  321.994765] mmcblk1: error -22 transferring data, sector 3381152, nr 1024, cmd response 0x900, card status 0x0
  322.202538] mmcblk1: error -22 transferring data, sector 3381152, nr 1024, cmd response 0x900, card status 0x0
  322.558138] mmcblk1: error -22 transferring data, sector 3382176, nr 1024, cmd response 0x900, card status 0x0
  322.762705] mmcblk1: error -22 transferring data, sector 3382176, nr 1024, cmd response 0x900, card status 0x0
  323.075921] mmcblk1: error -22 transferring data, sector 3383200, nr 1024, cmd response 0x900, card status 0x0
  323.283103] mmcblk1: error -22 transferring data, sector 3383200, nr 1024, cmd response 0x900, card status 0x0
  323.636554] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 524276 bytes
  323.686159] mmcblk1: error -22 transferring data, sector 3384224, nr 1024, cmd response 0x900, card status 0x0
  323.866305] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 524276 bytes
  323.917242] mmcblk1: error -22 transferring data, sector 3384224, nr 1024, cmd response 0x900, card status 0x0
  324.274831] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 417780 bytes
  324.332855] mmcblk1: error -22 transferring data, sector 3385248, nr 1024, cmd response 0x900, card status 0x0
  324.516422] bcm2835-dma 3f007000.dma: DMA: Out of SW-IOMMU space for 417780 bytes

Is this something to be scared? Or just ignore? Why is TW for raspi 3 so unstable? Older installs I don’t update at all because every time the whole install might crash on updating…

2

Hi
I don’t use a sd card, but that would indicate something not right with your sd card… if that’s pumping out sd card errors, then the other error is likely fallout from all the i/o going on…

I don’t see any chatter like that on my system;


NAME="openSUSE Tumbleweed"
# VERSION="20180104 "
uname -a
Linux hostname 4.14.11-1-default #1 SMP Thu Jan 4 11:32:07 UTC 2018 (c36893f) aarch64 aarch64 aarch64 GNU/Linux

Try a different SD card, or grab the latest JeOS image and burn that. From a different computer running linux do an fsck on the unmouted partitions.

3

The card was doing fine with the initial JeOS. And I copied the running SD-card to this card (with dd this time), it won’t boot, but no errors like in the output given above. So apparently no problem with the card…

4

Hi
Have you got (or can get) a serial cable to connect to the RPI so can see the u-boot output?

Do you get to grub and past it before it errors out?