Op vrijdag 24 januari 2020 11:53:56 CET schreef Guillaume Gardet: > > However the system also reported ext4 errors and some commands crashed. > > Does dmesg show some errors regarding SD card? > > Guillaume
Installed JeOS image on SD card. Via ssh entered the RPi4 system. Installed u- boot-rpiarm64 and did a reboot. Entered the system again via ssh. This was extremely slow before a login prompt was shown and the prompt for the password. Saw with "top i" the amount of memory. Also hwinfo --memory reported: 01: None 00.0: 10102 Main Memory [Created at memory.74] Unique ID: rdCR.CxwsZFjVASF Hardware Class: memory Model: "Main Memory" Memory Range: 0x00000000-0xf1446fff (rw) Memory Size: 3 GB + 768 MB Config Status: cfg=new, avail=yes, need=no, active=unknown dmesg shows a lot of messages like below: [ 190.326171] ------------[ cut here ]------------ [ 190.326258] WARNING: CPU: 0 PID: 418 at ../drivers/mmc/host/sdhci.c:1094 sdhci_prepare_data+0x960/0x978 [sdhci] [ 190.326262] Modules linked in: af_packet iscsi_ibft iscsi_boot_sysfs nls_iso8859_1 nls_cp437 vfat fat btsdio bluetooth ecdh_generic ecc brcmfmac brcmutil cfg80211 broadcom xhci_pci bcm_phy_lib rfkill xhci_hcd mdio_bcm_unimac cpufreq_dt raspberrypi_hwmon raspberrypi_cpufreq iproc_rng200 bcm2835_wdt pcie_brcmstb genet uio_pdrv_genirq uio crct10dif_ce leds_gpio mmc_block dwc2 sdhci_iproc sdhci_pltfm sdhci udc_core usbcore gpio_raspberrypi_exp clk_raspberrypi mmc_core i2c_bcm2835 bcm2835_dma phy_generic gpio_regulator fixed dm_mirror dm_region_hash dm_log sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs [ 190.326353] CPU: 0 PID: 418 Comm: kworker/0:1H Tainted: G W 5.3.18-lp152.1-default #1 openSUSE Leap 15.2 (unreleased) [ 190.326358] Hardware name: raspberrypi rpi/rpi, BIOS 2019.10 12/20/2019 [ 190.326380] Workqueue: kblockd blk_mq_run_work_fn [ 190.326389] pstate: 40000085 (nZcv daIf -PAN -UAO) [ 190.326405] pc : sdhci_prepare_data+0x960/0x978 [sdhci] [ 190.326419] lr : sdhci_prepare_data+0x960/0x978 [sdhci] [ 190.326423] sp : ffff0000103939d0 [ 190.326428] x29: ffff0000103939d0 x28: ffffb30f6b188148 [ 190.326436] x27: 0000000000000002 x26: ffffb30f6c5e0800 [ 190.326444] x25: ffffb30f6cf05000 x24: 0000000000000001 [ 190.326450] x23: 0000000000418958 x22: ffffb30f6b1882e0 [ 190.326457] x21: ffff2327e5999000 x20: ffffb30f6b188360 [ 190.326463] x19: ffffb30f6cf05580 x18: ffffffffffffffff [ 190.326469] x17: 0000000000000001 x16: 0000000000000007 [ 190.326475] x15: ffff2327e5999708 x14: 6f74202c29736574 [ 190.326481] x13: 7962203633353536 x12: ffff2327e59c0000 [ 190.326487] x11: 0000000000000000 x10: ffff2327e5bd2000 [ 190.326494] x9 : 0000000000000000 x8 : 0000000000000003 [ 190.326500] x7 : 0000000000000461 x6 : 00000000536549d7 [ 190.326506] x5 : 0000000000000001 x4 : ffffb30f7b77f2c8 [ 190.326513] x3 : ffffb30f7b77f2c8 x2 : f19f862514c0b000 [ 190.326519] x1 : 0000000000000000 x0 : 0000000000000024 [ 190.326526] Call trace: [ 190.326541] sdhci_prepare_data+0x960/0x978 [sdhci] [ 190.326555] sdhci_send_command+0xf0/0x618 [sdhci] [ 190.326568] sdhci_request+0xe8/0x120 [sdhci] [ 190.326605] __mmc_start_request+0x88/0x1b0 [mmc_core] [ 190.326639] mmc_start_request+0x98/0xd0 [mmc_core] [ 190.326652] mmc_blk_mq_issue_rq+0x5d4/0x7d0 [mmc_block] [ 190.326662] mmc_mq_queue_rq+0x14c/0x328 [mmc_block] [ 190.326669] blk_mq_dispatch_rq_list+0xb0/0x440 [ 190.326676] blk_mq_do_dispatch_sched+0x6c/0x110 [ 190.326684] blk_mq_sched_dispatch_requests+0x128/0x1f0 [ 190.326693] __blk_mq_run_hw_queue+0xd0/0x138 [ 190.326701] blk_mq_run_work_fn+0x28/0x38 [ 190.326712] process_one_work+0x200/0x450 [ 190.326720] worker_thread+0x50/0x4d0 [ 190.326727] kthread+0x130/0x138 [ 190.326736] ret_from_fork+0x10/0x18 [ 190.326741] ---[ end trace 8235e3938456c6b5 ]--- Hope this is what you are looking for. Currently the system, after this last message of dmesg, is responsive and repeating dmesg does not show any additions to its output. Did again a reboot. The system was more responsive and less output from dmesg. The last message was about swiotlb buffer full. Remembered a recommendation to remove swiotlb=512 from the command line in grub. Did so and did a reboot. Access via ssh was fast. No obvious error messages in dmesg anymore. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
