Thanks for your interest in the Intel Joule Platform.
I'm sorry to hear that you are having problems with your SD card. Now I have a couple of questions, before we start looking for a solution to your issue:
1) Was your issue solved when you use the command fsck?
2) Which guide did you follow? I would recommend to follow this guide Intel Joule | Developer , also check this thread Re: Installing Ubuntu on Intel Joule 570x and follow the recommendations given by the users.
I will be waiting for your reply, have a nice day!
(1) I ran fsck before and after rebooting and it did not mention any error. However, the error 'Volume was not properly unmounted. Some data may be corrupt. Please run fsck' still can be found the kernel log.
(2) I followed the instructions for 'Alternative install: Ubuntu Desktop 16.04 LTS'. Apart from the SD card issue, the system runs as expected.
I just found a related topic, where the same issue was mentioned: Ubuntu/Other Linux distros not properly recognising external SD?
To me, the problem described by McCool is the same I encounter. Unfortunately, no solution was given.
Reading through the thread Ubuntu/Other Linux distros not properly recognising external SD? , I see that this is an issue with Ubuntu not of the Intel Joule, I would encourage you to contact the Ubuntu Community, they might be able to better assist with this issue.
Ubuntu Community: https://developer.ubuntu.com/en/community/
Also, I saw McCool posts and he said that there is a workaround to this issue: "However, the SD card is just not recognized at boot. If I pop it out and push it back in, it is however recognized and mounted". Additionally, he recommends to use the command lsblk like this: "Then you can clearly see this behaviour (reboot, run lsblk... no card..., then pop the card out and push it back it, run lsblk... there it is!)".
Hope you find this information useful, have a nice day!
after purchasing a further Intel Joule, installing the latest BIOS (FW 1H3) together with the Ref-OS-IoT version 1705, the very same error is still valid.
That is, after boot procedure, SD cards are not mounted and the error in the syslog still is mmc0: error -110 whilst initialising SD card.
Only by popping the card out and in again, the card can be used, which is clearly no solution at all, if the joule is for example covered.
Furthermore, the issue is clearly not limited to Ubuntu.
That's weird, I just tested it in my Joule and it detects the SD card in /dev/ after the reboot. Just to be sure, have you test it with different SD cards?
Could you also provide us the "dmesg" file to check it?
We will be waiting for your reply.
Have a nice day.
I can replicate.
Board is Intel Joule 570x on development expansion board, running Ref-os-iot version 1.0+snapshot-20170622.
Steps to replicate:
- Insert SD card
- Shut down Joule
- Pull DC Power
- Reapply DC Power
- Check dmesg | grep mmc0. Dmesg should report error -110 whilst initializing SD Card
Same steps to replicate on Ubuntu.
This problem not always present. If you do a reboot without removing power, the system has no problem recognizing the device. To replicate:
- Clean boot the Joule with no SD card inserted
- Insert SD Card
- Reboot the Joule from command line
- Check /dev and dmesg. /dev/ should have mmcblk0 and whatever partitions are on disk, and dmesg should report detecting the SD card.
Thanks for your interest in the Intel® Joule™ Platform.
Please let me replicate this issue, we will contact you back as soon as we have some useful information.
Have a nice day!
Yes, I have tried multiple SD cards. I did notice, though, that your SD card is at a different address. Mine always say "new high speed SDHC card at address aaaa". I wonder if this is the issue?
Please let me investigate more and we will get back to you as soon as we have some relevant information.
Have a nice day!
Are there any other specific steps that you took in order to get this issue? You mention that your SD card address is "aaaa" is this the case with all the SD cards that you have tested?
We will be waiting for your reply, have a great day!
Were you able to fix your SD card issue? Please let us know in order to assist you.
Hope you find this information useful, have a nice day!
No, there are no other steps to replicate this issue. This is the case with all the SD cards and all of the Joules I have tested. The issue still is not resolved.
I'm also having the same issue, with both the reference OS and Ubuntu 16.04.
I've also noticed that if I boot the system with a microSD card plugged in, and then remove the microSD card while watching the dmesg output, I get the following kernel warning (below). I'm not sure what to make of it, but it happens consistently. I'd love to hear if anyone has found a fix for this issue.
[ 71.035940] ------------[ cut here ]------------
[ 71.035963] WARNING: CPU: 2 PID: 42 at /build/linux-joule-lGwnUP/linux-joule-4.4.0/kernel/irq/handle.c:150 handle_irq_event_percpu+0x1f0/0x200()
[ 71.035970] irq 338 handler irq_default_primary_handler+0x0/0x10 enabled interrupts
[ 71.035974] Modules linked in: rfcomm cmac bnep nls_iso8859_1 gpio_keys intel_rapl intel_telemetry_debugfs intel_telemetry_pltdrv intel_punit_ipc intel_telemetry_core x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul snd_hda_codec_hdmi ghash_clmulni_intel snd_hda_intel aesni_intel aes_x86_64 lrw gf128mul snd_soc_skl glue_helper snd_soc_skl_ipc snd_soc_sst_ipc ablk_helper snd_soc_sst_dsp snd_hda_ext_core cryptd snd_soc_sst_match snd_soc_core snd_compress typec_wcove ac97_bus intel_pmic_thermal snd_pcm_dmaengine pwm_lpss_pci pwm_lpss spi_pxa2xx_platform snd_hda_codec joydev snd_hda_core snd_hwdep input_leds snd_pcm_oss snd_mixer_oss i2c_designware_platform i2c_designware_core snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi btusb snd_seq btrtl snd_seq_device
[ 71.036072] snd_timer snd hci_uart btbcm btqca mei_me btintel soundcore mei processor_thermal_device dwc3_pci bluetooth intel_soc_dts_iosf fdp_i2c fdp nci nfc bq25890_charger mac_hid int3400_thermal int3403_thermal intel_hid acpi_thermal_rel soc_button_array sparse_keymap int340x_thermal_zone fixed parport_pc ppdev lp parport intel_ipu4_isys_mod_bxtB0 videobuf2_v4l2 videobuf2_core intel_ipu4_psys_mod_bxtB0 intel_ipu4_mmu_bxtB0 intel_ipu4_mod_bxtB0 intel_ipu4_acpi videobuf2_dma_contig videobuf2_memops videobuf_core dw9714 crlmodule v4l2_common videodev media arizona_i2c autofs4 btrfs xor raid6_pq dm_mirror dm_region_hash dm_log hid_generic uas usbhid hid usb_storage mmc_block i915 gpio_wcove i2c_algo_bit sdhci_pci drm_kms_helper sdhci syscopyarea sysfillrect sysimgblt fb_sys_fops drm video fjes
[ 71.036192] CPU: 2 PID: 42 Comm: irq/14-INT34D1: Tainted: G U 4.4.0-1000-joule #0+joule21-Ubuntu
[ 71.036196] Hardware name: Intel Corp. 570x DVT3/SDS, BIOS GTPP1F1A.X64.0143.B30.1704132245 04/13/2017
[ 71.036200] 0000000000000286 00000000cafaa41a ffff88017a03bc80 ffffffff81400e61
[ 71.036208] ffff88017a03bcc8 ffffffff81cc3858 ffff88017a03bcb8 ffffffff81081d42
[ 71.036215] ffff88017a5c7500 0000000000000152 0000000000000002 0000000000000000
[ 71.036222] Call Trace:
[ 71.036233] [<ffffffff81400e61>] dump_stack+0x63/0x82
[ 71.036241] [<ffffffff81081d42>] warn_slowpath_common+0x82/0xc0
[ 71.036247] [<ffffffff81081ddc>] warn_slowpath_fmt+0x5c/0x80
[ 71.036253] [<ffffffff810dccb0>] ? __synchronize_hardirq+0x60/0x60
[ 71.036259] [<ffffffff810dcbe0>] handle_irq_event_percpu+0x1f0/0x200
[ 71.036264] [<ffffffff810dcc2c>] handle_irq_event+0x3c/0x60
[ 71.036270] [<ffffffff810e017d>] handle_edge_irq+0x7d/0x150
[ 71.036275] [<ffffffff810dc162>] generic_handle_irq+0x22/0x30
[ 71.036282] [<ffffffff8143be5b>] intel_gpio_irq+0xeb/0x170
[ 71.036288] [<ffffffff810dd6f0>] ? irq_finalize_oneshot.part.35+0xd0/0xd0
[ 71.036293] [<ffffffff810dd719>] irq_forced_thread_fn+0x29/0x70
[ 71.036299] [<ffffffff810dda78>] irq_thread+0x138/0x1b0
[ 71.036304] [<ffffffff810dd890>] ? wake_threads_waitq+0x30/0x30
[ 71.036310] [<ffffffff810dd940>] ? irq_thread_dtor+0xb0/0xb0
[ 71.036316] [<ffffffff810a1a98>] kthread+0xd8/0xf0
[ 71.036321] [<ffffffff810a19c0>] ? kthread_worker_fn+0x170/0x170
[ 71.036329] [<ffffffff8184e00f>] ret_from_fork+0x3f/0x70
[ 71.036334] [<ffffffff810a19c0>] ? kthread_worker_fn+0x170/0x170
[ 71.036339] ---[ end trace 721a2cde9e5b6fb2 ]---