mmc1: Card stuck in programming state!

Test and fix the Kernel 4.14 features
Post Reply
rncwnd
Posts: 34
Joined: Tue Apr 11, 2017 11:18 pm
languages_spoken: english, german
ODROIDs: XU4
Contact:

mmc1: Card stuck in programming state!

Unread post by rncwnd » Fri Aug 18, 2017 8:01 pm

Hi,

I get this in syslog, is it critical? Does someone know how to resolve that?

Code: Select all

[ 1727.305319] mmc1: Card stuck in programming state! mmc_do_erase
[ 1727.331561] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[ 1727.378854] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[ 1743.975308] mmc1: Card stuck in programming state! mmc_do_erase
[ 1744.006524] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[ 1744.048830] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[ 1748.410310] mmc1: Card stuck in programming state! mmc_do_erase
[ 1748.531584] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[ 1748.573962] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[ 1753.360312] mmc1: Card stuck in programming state! mmc_do_erase
[ 1753.865344] dwmmc_exynos 12220000.mmc:: Busy; trying anyway
[ 1753.865356] mmc_host mmc1: Timeout sending command (cmd 0x202000 arg 0x0 status 0x0)
[ 1753.886598] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[ 1754.108911] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[ 1757.840308] mmc1: Card stuck in programming state! mmc_do_erase
[ 1758.345309] dwmmc_exynos 12220000.mmc:: Busy; trying anyway
[ 1758.345318] mmc_host mmc1: Timeout sending command (cmd 0x202000 arg 0x0 status 0x0)
[ 1758.371611] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[ 1758.419004] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
Now running

Code: Select all

Linux odroid 4.9.43+ #1 SMP PREEMPT Thu Aug 17 17:21:31 UTC 2017 armv7l GNU/Linux
These errors appear in older versions too.

Initialization during boot

Code: Select all

[    0.936906] sdhci: Secure Digital Host Controller Interface driver
[    0.936920] sdhci: Copyright(c) Pierre Ossman
[    0.937136] Synopsys Designware Multimedia Card Interface Driver
[    0.937691] dwmmc_exynos 12200000.mmc:: IDMAC supports 32-bit address mode.
[    0.937765] dwmmc_exynos 12200000.mmc:: Using internal DMA controller.
[    0.937783] dwmmc_exynos 12200000.mmc:: Version ID is 250a
[    0.937824] dwmmc_exynos 12200000.mmc:: DW MMC controller at irq 93,64 bit host data width,64 deep fifo
[    0.937970] dwmmc_exynos 12200000.mmc:: Got CD GPIO
[    0.938033] dwmmc_exynos 12200000.mmc:: allocated mmc-pwrseq
[    0.960988] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    0.980551] dwmmc_exynos 12200000.mmc:: 1 slots initialized
[    0.980777] dwmmc_exynos 12220000.mmc:: IDMAC supports 32-bit address mode.
[    0.980818] dwmmc_exynos 12220000.mmc:: Using internal DMA controller.
[    0.980835] dwmmc_exynos 12220000.mmc:: Version ID is 250a
[    0.980872] dwmmc_exynos 12220000.mmc:: DW MMC controller at irq 94,64 bit host data width,64 deep fifo
[    1.005780] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    1.025372] dwmmc_exynos 12220000.mmc:: 1 slots initialized
...
[    1.084351] mmc_host mmc1: Bus speed (slot 0) = 200000000Hz (slot req 200000000Hz, actual 200000000HZ div = 0)
[    1.085040] mmc1: new ultra high speed SDR104 SDXC card at address 0001
[    1.085629] mmcblk1: mmc1:0001 00000 59.6 GiB
[    1.086334]  mmcblk1: p1 p2

User avatar
odroid
Site Admin
Posts: 30028
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by odroid » Sat Aug 19, 2017 12:44 am

Which OS image did you flash??
Do you use a UHS-1 capable SD card? or an eMMC module?

rncwnd
Posts: 34
Joined: Tue Apr 11, 2017 11:18 pm
languages_spoken: english, german
ODROIDs: XU4
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by rncwnd » Sat Aug 19, 2017 3:55 am

I'm using a Samsung SDXC 64GB PRO Plus (UHS-I, U3, Class 10).
And the image is DietPi based on mevericks debian jessie.

User avatar
odroid
Site Admin
Posts: 30028
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by odroid » Sat Aug 19, 2017 6:08 am

We will try to reproduce the issue with Kernel 4.9.43.

crashoverride
Posts: 4317
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by crashoverride » Sat Aug 19, 2017 6:24 am

I have seen that error when using custom parameters to format the EXT4 rootfs. Try the official Ubuntu image and see if the issue persists.

[edit]
The second log posted does not indicate any error.

rncwnd
Posts: 34
Joined: Tue Apr 11, 2017 11:18 pm
languages_spoken: english, german
ODROIDs: XU4
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by rncwnd » Mon Aug 21, 2017 11:16 pm

crashoverride wrote: [edit]
The second log posted does not indicate any error.
That's what I thought too. Wanted to provide this info just for completeness.

cpuandnet
Posts: 6
Joined: Sat Sep 23, 2017 12:40 am
languages_spoken: english
ODROIDs: XU4
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by cpuandnet » Mon Sep 25, 2017 1:06 pm

I too have been struggling with this issue on several of my Odroid XU4s. I have the Ubuntu image installed on Micro SD UHS1 and updated to the following kernel: Linux odroid 4.9.50-63 #1 SMP PREEMPT Fri Sep 15 16:30:44 UTC 2017 armv7l armv7l armv7l GNU/Linux.

Has there been any progress made on this issue?

rncwnd
Posts: 34
Joined: Tue Apr 11, 2017 11:18 pm
languages_spoken: english, german
ODROIDs: XU4
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by rncwnd » Mon Sep 25, 2017 5:06 pm

cpuandnet wrote:I too have been struggling with this issue on several of my Odroid XU4s. I have the Ubuntu image installed on Micro SD UHS1 and updated to the following kernel: Linux odroid 4.9.50-63 #1 SMP PREEMPT Fri Sep 15 16:30:44 UTC 2017 armv7l armv7l armv7l GNU/Linux.

Has there been any progress made on this issue?
I am running now (latest kernel - edit: 4.9.51+ is now recent!):

Code: Select all

Linux odroid 4.9.50+ #1 SMP PREEMPT Mon Sep 18 15:27:16 UTC 2017 armv7l GNU/Linux
The error message vanished from syslog.

BUT: because I have the Cloudshell 1 with an internal HDD and an additional external HDD and am also suffering the famous "underpowering" problem* (regardless of powering the external HDD separately!) I changed also the CPU max freq down to 1.7 GHz.
The solution might be the combination of the new kernel and limitting the CPU freq.

*) The underpowering problem seems to be the root of all past, recent and future bugs and problems appearing on the XU4! Also in other communitites. So I wonder if we all bought a defective product and should all return our XU4s... :twisted:

User avatar
odroid
Site Admin
Posts: 30028
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by odroid » Mon Sep 25, 2017 6:14 pm

We couldn't reproduce the issue with Samsung EVO Plus 16GB on Kernel 4.9.51-60 while we compiled full Kernel source with -j8 option.
We will buy a PRO Plus card and test it soon.

rncwnd
Posts: 34
Joined: Tue Apr 11, 2017 11:18 pm
languages_spoken: english, german
ODROIDs: XU4
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by rncwnd » Wed Sep 27, 2017 6:41 pm

Unfortunately the problem still persists with latest kernel.

Code: Select all

Linux odroid 4.9.51+ #1 SMP PREEMPT Sun Sep 24 07:20:19 UTC 2017 armv7l GNU/Linux
The error reappeared today after last reboot 2 days ago (when I updated the kernel).
What I did is syncing latest version of btrfs-progs from github and compiling / installing it. Before that, I uninstalled the installed version and deleted the old source folder.
Maybe the problem appears when there's "heavy" load on the mmc. My sources folder (/usr/src) is located on the mmc.

Code: Select all

[164672.905755] mmc1: Card stuck in programming state! mmc_do_erase
[164673.057008] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[164673.099733] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[164675.300761] mmc1: Card stuck in programming state! mmc_do_erase
[164675.331950] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[164675.374293] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[164676.740752] mmc1: Card stuck in programming state! mmc_do_erase
[164676.776990] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[164676.819280] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)

User avatar
odroid
Site Admin
Posts: 30028
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by odroid » Wed Sep 27, 2017 11:34 pm

Which file system do you use on your SD card?

cpuandnet
Posts: 6
Joined: Sat Sep 23, 2017 12:40 am
languages_spoken: english
ODROIDs: XU4
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by cpuandnet » Thu Sep 28, 2017 12:59 am

After reading rncwnd's post about the kernel and cpu frequency, I decided to make a few changes and post an update. I started typing this in a paragraph but then i got confused :shock: , so i broke it down.

All 4 XU4s are as follows:
* Using the official Odroid release of Ubuntu 16.04
* Used SD Formatter followed by Etcher without error to prepare the cards and OS
* Upgraded the kernels to Linux odroid 4.9.51-64
* These systems are not, nor will be, under heavy load
* Using the 5V 6A P/S from Ameridroid

The 2 XU4s with which I experienced the problem:
* Changed the governor to ondemand to lower the cpu frequencies
* Both are using Sandisk UHS 32GB
* One XU4 is hosting Samba with a USB3 hard drive and the other XU4 is hosting MySQL with no USB3 hard drive

The two XU4s with which there have been no problems:
* Left governor at performance
* One XU4 is using Sandisk UHS 16GB and the other XU4 is using Sandisk UHS 8GB
* One XU4 is hosting Apache/Owncloud with a USB3 hard drive and the other XU4 is hosting Asterisk

None of the systems have experienced this issue since I have made these previous changes. My thought process at this point is as follows:
* Eliminate the P/S as the source of the problem because they are the same on all systems. If the problem persists, I will rotate the P/S to the systems that do not have the problem and see what happens
* Eliminate the load factor because the average load is never more than 0.35 on any XU4 at any given time...even during peak usage hours
* It is possible that there is a combination of factors at play here with the cpu frequencies, SD cards and/or applications hosted. So, my next step is to put only 1 of the problematic XU4s governor back to performance and see what happens.

I am going to make this single change on Sunday evening but any thoughts or suggestions before I do would be welcomed. I would think It should be sufficient time to see if this issue occurs with the current configuration. I will report back at the end of next week or when/if I experience the issue.

User avatar
odroid
Site Admin
Posts: 30028
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by odroid » Thu Sep 28, 2017 3:40 pm

We've just received the Samsung Pro Plus 32GB UHS-1 U3 cards.
We've run Kernel compiling with -j8 option on Ubuntu 16.04 Kernel 4.9.51-64 but there was no issue.

We are running 1GB of IOZONE r/w test to make much more stress to the SD interface.
iozone -e -I -a -s 1000M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2


Edit: We couldn't reproduce the issue even we did the heavy iozone test over 20 hours.

rncwnd
Posts: 34
Joined: Tue Apr 11, 2017 11:18 pm
languages_spoken: english, german
ODROIDs: XU4
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by rncwnd » Thu Sep 28, 2017 8:16 pm

It got worse.

After writing the the post yesterday I didn't do anything special with the XU4.

This is what I found today in the syslog:

Code: Select all

[209108.830583] mmc1: Card stuck in programming state! mmc_do_erase
[209108.876920] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[209108.919187] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[209109.920574] mmc1: Card stuck in programming state! mmc_do_erase
[209109.920583] blk_update_request: I/O error, dev mmcblk1, sector 23781378
[209109.920616] EXT4-fs (mmcblk1p2): discard request in group:1442 block:4096 count:4096 failed with -5
[209109.920713] mmcblk1: timed out sending SET_BLOCK_COUNT command, card status 0x400e00
[209109.920718] mmcblk1: command error, retrying timeout
[209109.920790] mmcblk1: timed out sending SET_BLOCK_COUNT command, card status 0x400e00
[209109.920794] mmcblk1: command error, retrying timeout
[209109.920864] mmcblk1: timed out sending SET_BLOCK_COUNT command, card status 0x400e00
[209109.920868] mmcblk1: command error, retrying timeout
[209109.920938] mmcblk1: timed out sending SET_BLOCK_COUNT command, card status 0x400e00
[209109.920943] mmcblk1: command error, retrying timeout
[209109.921013] mmcblk1: timed out sending SET_BLOCK_COUNT command, card status 0x400e00
[209109.921017] mmcblk1: command error, retrying timeout
[209109.921087] mmcblk1: timed out sending SET_BLOCK_COUNT command, card status 0x400e00
[209109.921091] mmcblk1: command error, retrying timeout
[209109.946877] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[209109.989277] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[209116.720588] mmc1: Card stuck in programming state! mmc_do_erase
[209116.781845] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[209116.824161] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[209121.670595] mmc1: Card stuck in programming state! mmc_do_erase
[209121.731871] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[209121.784271] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[225725.032515] BTRFS info (device sdb1): relocating block group 5446047891456 flags 18
[225727.629428] BTRFS info (device sdb1): found 2 extents
[225734.495299] BTRFS info (device sdb1): relocating block group 5446081445888 flags 17
[225743.846884] BTRFS info (device sdb1): found 434 extents
[225748.327004] BTRFS info (device sdb1): found 434 extents
[230918.405500] mmc1: Card stuck in programming state! mmc_do_erase
[230918.486767] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[230918.534022] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[230922.910491] mmc1: Card stuck in programming state! mmc_do_erase
[230923.415487] dwmmc_exynos 12220000.mmc:: Busy; trying anyway
[230923.415496] mmc_host mmc1: Timeout sending command (cmd 0x202000 arg 0x0 status 0x0)
[230923.436763] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[230923.704183] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[230930.295494] mmc1: Card stuck in programming state! mmc_do_erase
[230930.391742] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[230930.434079] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[252768.180431] mmc1: Card stuck in programming state! mmc_do_erase
[252768.266688] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[252768.308956] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
I already posted it in some other thread, this is my setup (in case that this is helpful):
- Cloudshell 1
- Internal HDD connected to CS1 SATA interface: WD Red 1 TB
- External HDD connected to USB3 interface: WD Red 1 TB, powered externally
- P/S with 4Ah (from german reseller, came with the Cloudshell 1)

Software
- DietPi with kernel 4.9.51+ from hardkernel
- Nextcloud 12
- Nginx
- PHP5
- MySQL
- Redis Cache
- Samba

Other
- Both HDDs are a BTRFS Raid 1 hosting MySQL DBs, Nextcloud Data Directory, Samba Shares
- On Demand Scheduler
- CPU max freq limitted to 1.7 GHz

rncwnd
Posts: 34
Joined: Tue Apr 11, 2017 11:18 pm
languages_spoken: english, german
ODROIDs: XU4
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by rncwnd » Thu Sep 28, 2017 9:00 pm

How can I fsck the root partition (located on mmc)?
I tried:

Code: Select all

touch /forcefsck
followed by shutdown and boot. But that did do nothing. ('reboot' command doesn't work correctly as the external USB HDD doesn't get recognized during warm reboot, that's why I have to shutdown followed by unplug/plug power).

Then I tried it the hard way:

Code: Select all

mount /dev/mmcblk1p2 -f -v -n -o remount,ro
But that didn't remount / readonly. therefore fsck didn't work.

I also tried this:

Code: Select all

umount -f -r /dev/mmcblk1p2
Which also didn't result in an unmounted or readonly remounted /.

Little challenge: My XU4 is running headless, so init 1 is no option for now.

cpuandnet
Posts: 6
Joined: Sat Sep 23, 2017 12:40 am
languages_spoken: english
ODROIDs: XU4
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by cpuandnet » Fri Sep 29, 2017 1:46 am

rncwnd wrote:How can I fsck the root partition (located on mmc)?
I tried:

Code: Select all

touch /forcefsck
followed by shutdown and boot. But that did do nothing. ('reboot' command doesn't work correctly as the external USB HDD doesn't get recognized during warm reboot, that's why I have to shutdown followed by unplug/plug power).

Then I tried it the hard way:

Code: Select all

mount /dev/mmcblk1p2 -f -v -n -o remount,ro
But that didn't remount / readonly. therefore fsck didn't work.

I also tried this:

Code: Select all

umount -f -r /dev/mmcblk1p2
Which also didn't result in an unmounted or readonly remounted /.

Little challenge: My XU4 is running headless, so init 1 is no option for now.
The easiest way is to check it is from another linux type system via a card reader. If you don't have another system, just use another card to boot from and use the card reader to check the problematic card. I keep a 8GB microsd card handy for just this purpose. I have done this in the past and it works every time. Although, the partition in the card reader device will not be /dev/mmcblk1p2...it will be some other partition name like /dev/sda2. You can use fdisk -l to find out the device name.

User avatar
odroid
Site Admin
Posts: 30028
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by odroid » Fri Sep 29, 2017 10:26 am

NextCloud seems to cause the problem.
viewtopic.php?f=97&t=28372

cpuandnet
Posts: 6
Joined: Sat Sep 23, 2017 12:40 am
languages_spoken: english
ODROIDs: XU4
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by cpuandnet » Mon Oct 02, 2017 12:49 am

Unfortunately, I woke this morning to find the following error after the changes I previously made. This time, it looks like there is a voltage switch and now file system corruption. I suppose my next step is to swap power supplies with a system that does not appear to have the same problem as of yet. This is becoming frustrating. Any other thoughts or suggestions?

[Sun Oct 1 06:47:08 2017] mmc1: Card stuck in programming state! mmc_do_erase
[Sun Oct 1 06:47:09 2017] dwmmc_exynos 12220000.mmc:: Busy; trying anyway
[Sun Oct 1 06:47:09 2017] mmc_host mmc1: Timeout sending command (cmd 0x202000 arg 0x0 status 0x0)
[Sun Oct 1 06:47:09 2017] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[Sun Oct 1 06:47:11 2017] mmc1: Skipping voltage switch
[Sun Oct 1 06:47:11 2017] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[Sun Oct 1 06:47:13 2017] mmc1: Card stuck in programming state! mmc_do_erase
[Sun Oct 1 06:47:13 2017] blk_update_request: I/O error, dev mmcblk1, sector 5174328
[Sun Oct 1 06:47:13 2017] mmcblk1: timed out sending SET_BLOCK_COUNT command, card status 0x400e00
[Sun Oct 1 06:47:13 2017] mmcblk1: command error, retrying timeout
[Sun Oct 1 06:47:13 2017] mmcblk1: timed out sending SET_BLOCK_COUNT command, card status 0x400e00
[Sun Oct 1 06:47:13 2017] mmcblk1: command error, retrying timeout
[Sun Oct 1 06:47:13 2017] mmcblk1: timed out sending SET_BLOCK_COUNT command, card status 0x400e00
[Sun Oct 1 06:47:13 2017] mmcblk1: command error, retrying timeout
[Sun Oct 1 06:47:13 2017] mmcblk1: timed out sending SET_BLOCK_COUNT command, card status 0x400e00
[Sun Oct 1 06:47:13 2017] mmcblk1: command error, retrying timeout
[Sun Oct 1 06:47:13 2017] mmcblk1: timed out sending SET_BLOCK_COUNT command, card status 0x400e00
[Sun Oct 1 06:47:13 2017] mmcblk1: command error, retrying timeout
[Sun Oct 1 06:47:13 2017] mmcblk1: timed out sending SET_BLOCK_COUNT command, card status 0x400e00
[Sun Oct 1 06:47:13 2017] mmcblk1: command error, retrying timeout
[Sun Oct 1 06:47:13 2017] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[Sun Oct 1 06:47:13 2017] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)

rncwnd
Posts: 34
Joined: Tue Apr 11, 2017 11:18 pm
languages_spoken: english, german
ODROIDs: XU4
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by rncwnd » Mon Oct 02, 2017 5:51 pm

Same here. Only that I cannot imagine that this was due to a voltage drop.

Code: Select all

[Mo Okt  2 01:30:04 2017] BTRFS info (device sdb1): relocating block group 5450477076480 flags 18
[Mo Okt  2 01:30:07 2017] BTRFS info (device sdb1): found 2 extents
[Mo Okt  2 01:30:15 2017] BTRFS info (device sdb1): relocating block group 5450510630912 flags 17
[Mo Okt  2 01:30:22 2017] BTRFS info (device sdb1): found 305 extents
[Mo Okt  2 01:30:27 2017] BTRFS info (device sdb1): found 305 extents
[Mo Okt  2 04:01:00 2017] mmc1: Card stuck in programming state! mmc_do_erase
[Mo Okt  2 04:01:00 2017] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[Mo Okt  2 04:01:00 2017] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[Mo Okt  2 04:01:04 2017] mmc1: Card stuck in programming state! mmc_do_erase
[Mo Okt  2 04:01:04 2017] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[Mo Okt  2 04:01:04 2017] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[Mo Okt  2 04:01:08 2017] mmc1: Card stuck in programming state! mmc_do_erase
[Mo Okt  2 04:01:08 2017] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[Mo Okt  2 04:01:08 2017] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[Mo Okt  2 04:02:00 2017] mmc1: Card stuck in programming state! mmc_do_erase
[Mo Okt  2 04:02:00 2017] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[Mo Okt  2 04:02:00 2017] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[Mo Okt  2 10:04:49 2017] mmc1: Card stuck in programming state! mmc_do_erase
[Mo Okt  2 10:04:50 2017] dwmmc_exynos 12220000.mmc:: Busy; trying anyway
[Mo Okt  2 10:04:50 2017] mmc_host mmc1: Timeout sending command (cmd 0x202000 arg 0x0 status 0x0)
[Mo Okt  2 10:04:50 2017] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[Mo Okt  2 10:04:50 2017] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
At around 1:30 am I am running a BTRFS scrub which is quite I/O intensive. So I would have expected the voltage drop then.
At around 4:01 am no cron job is running and I was asleep and did not mess around with my odroid nor with nextcloud.
I also wonder why this could have something to do with owncloud/nextcloud anyway because I have my nextcloud userdata and database on the USB drives and not on the MMC!
Maybe I'll move the nginx web folder also to the USB drives later this week. Just in case some secret nextcloud job does mysterious things at night that the MMC couldn't cope with... :roll:

cpuandnet
Posts: 6
Joined: Sat Sep 23, 2017 12:40 am
languages_spoken: english
ODROIDs: XU4
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by cpuandnet » Thu Oct 05, 2017 12:53 am

rncwnd wrote:Same here. Only that I cannot imagine that this was due to a voltage drop.

...

At around 1:30 am I am running a BTRFS scrub which is quite I/O intensive. So I would have expected the voltage drop then.
At around 4:01 am no cron job is running and I was asleep and did not mess around with my odroid nor with nextcloud.
I also wonder why this could have something to do with owncloud/nextcloud anyway because I have my nextcloud userdata and database on the USB drives and not on the MMC!
Maybe I'll move the nginx web folder also to the USB drives later this week. Just in case some secret nextcloud job does mysterious things at night that the MMC couldn't cope with... :roll:
While swapping power supplies on 2 of my XU4s, I decided to connect them to a UPS instead of just using a surge protector. I left them on the surge protector too so I can at least rule that out. After almost 3 days, I have not had the same problem. If this holds, it would indicate either inferior or defective power supplies.

I'll be hiking the Grand Canyon for the next 4 days so I won't be able to check the status of my XU4s. I'll provide an update over the weekend.

rncwnd, are you using a UPS? I'm just trying to add more pieces to our puzzle.

rncwnd
Posts: 34
Joined: Tue Apr 11, 2017 11:18 pm
languages_spoken: english, german
ODROIDs: XU4
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by rncwnd » Thu Oct 05, 2017 6:51 pm

cpuandnet wrote:rncwnd, are you using a UPS? I'm just trying to add more pieces to our puzzle.
No I don't. Current is very stable in Germany. If there were real power surges, the Odroid would turn off after power went away.

cpuandnet
Posts: 6
Joined: Sat Sep 23, 2017 12:40 am
languages_spoken: english
ODROIDs: XU4
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by cpuandnet » Tue Oct 10, 2017 1:07 am

Well, unfortunately that didn't work either. Current is stable in the US as well but that doesn't mean that some heavy load on a transformer in the vicinity or the same building couldn't cause some issues now and then. But, a UPS should clean that up. The only things left are the applications and the boards themselves. However, I'm only running the applications that are packaged with the official Ubuntu release. So, now I suspect it is the boards themselves.

ehoffman
Posts: 4
Joined: Sun Sep 17, 2017 11:31 am
languages_spoken: english, french
ODROIDs: ODROID C2
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by ehoffman » Sun May 20, 2018 8:57 pm

I too have the same issue. But here are some more info...

I have 3 Odroid HC2, 2 of them have Sandisk Ultra 16GB cards, and one have Lexmark 300x 64GB card.

All 3 systems have plain un-costomized Odroid image with kernel 4.14.5-92. Basically there were build at the same time, with the same set of options, to each handle a 3TB HD.

Both of the HC2 which have Sandisk never get any errors, they are rock stable. The one with Lexmark give the issue. This may be related or not, as you'll see in a moment...

I've checked this morning and the issue appeared the moment I tried to access the HD via Samba.

Now, I've set the HD to spin down after 5 minute inactivity (on all 3 Odroid). So, when accessing the SAMBA share, the disk have to spin-up (3~5 second delay).

Now, both units that give no problems also happen to have Tosiba drives (DT01ACA300). The unit that give issue have Seagate drive (ST3000DM001-1ER166).


Here's an log when this occurred. Note that the only thing that got saved in syslog (since the SD is no longer working at that point, and ca't write back syslog, until reboot), are the first 4 lines (the syslog HUPed did not get saved). This log was retrieved when the system was in the 'bad state', so most probably from filesystem uncommitted memory cache.

Code: Select all

May 20 06:25:01 nas-data systemd[1]: Reloading LSB: start Samba SMB/CIFS daemon (smbd).
May 20 06:25:01 nas-data smbd[3573]:  * Reloading /etc/samba/smb.conf smbd
May 20 06:25:01 nas-data smbd[3573]:    ...done.
May 20 06:25:01 nas-data systemd[1]: Reloaded LSB: start Samba SMB/CIFS daemon (smbd).
May 20 06:25:01 nas-data rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="561" x-info="http://www.rsyslog.com"] rsyslogd was HUPed
May 20 06:47:01 nas-data rsyslogd-2007: action 'action 9' suspended, next retry is Sun May 20 06:48:31 2018 [v8.16.0 try http://www.rsyslog.com/e/2007 ]
May 20 06:47:01 nas-data CRON[7295]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ))
May 20 06:47:04 nas-data kernel: [62051.726911] mmc1: Card stuck in programming state! mmc_do_erase
May 20 06:47:04 nas-data kernel: [62052.231383] dwmmc_exynos 12220000.mmc: Busy; trying anyway
May 20 06:47:05 nas-data kernel: [62052.735417] mmc_host mmc1: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000)
May 20 06:47:05 nas-data kernel: [62052.768126] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
May 20 06:47:07 nas-data kernel: [62054.790927] mmc1: card never left busy state
May 20 06:47:07 nas-data kernel: [62054.793710] mmc1: tried to reset card, got error -110
May 20 06:47:07 nas-data kernel: [62054.793717] print_req_error: I/O error, dev mmcblk1, sector 499784
May 20 06:47:07 nas-data kernel: [62054.803362] mmcblk1: error -110 sending status command, retrying
May 20 06:47:07 nas-data kernel: [62054.808729] mmcblk1: error -110 sending status command, retrying
May 20 06:47:07 nas-data kernel: [62054.814733] mmcblk1: error -110 sending status command, aborting
May 20 06:47:09 nas-data kernel: [62056.866929] mmc1: card never left busy state
May 20 06:47:09 nas-data kernel: [62056.869719] mmc1: tried to reset card, got error -110
May 20 06:47:09 nas-data kernel: [62056.869725] print_req_error: I/O error, dev mmcblk1, sector 1571616
May 20 06:47:09 nas-data kernel: [62056.877728] mmcblk1: error -110 sending status command, retrying
May 20 06:47:09 nas-data kernel: [62056.883120] mmcblk1: error -110 sending status command, retrying
May 20 06:47:09 nas-data kernel: [62056.889083] mmcblk1: error -110 sending status command, aborting
May 20 06:47:09 nas-data kernel: [62056.894258] print_req_error: I/O error, dev mmcblk1, sector 1571616
May 20 06:47:09 nas-data CRON[7294]: (CRON) info (No MTA installed, discarding output)
May 20 06:47:32 nas-data kernel: [62079.964848] mmcblk1: error -110 sending status command, retrying
May 20 06:47:32 nas-data kernel: [62079.970220] mmcblk1: error -110 sending status command, retrying
May 20 06:47:32 nas-data kernel: [62079.976228] mmcblk1: error -110 sending status command, aborting
May 20 06:47:34 nas-data kernel: [62082.026953] mmc1: card never left busy state
May 20 06:47:34 nas-data kernel: [62082.029737] mmc1: tried to reset card, got error -110
May 20 06:47:34 nas-data kernel: [62082.029744] print_req_error: I/O error, dev mmcblk1, sector 264200
May 20 06:47:34 nas-data kernel: [62082.035940] Buffer I/O error on dev mmcblk1p2, logical block 1, lost async page write
May 20 06:47:34 nas-data kernel: [62082.045405] mmcblk1: error -110 sending status command, retrying
May 20 06:47:34 nas-data kernel: [62082.050796] mmcblk1: error -110 sending status command, retrying
May 20 06:47:34 nas-data kernel: [62082.056773] mmcblk1: error -110 sending status command, aborting
May 20 06:47:34 nas-data kernel: [62082.061932] print_req_error: I/O error, dev mmcblk1, sector 268360
May 20 06:47:34 nas-data kernel: [62082.068084] Buffer I/O error on dev mmcblk1p2, logical block 521, lost async page write
I will try to swap out the SD card for another Sandisk, to see if this resolve the issue...

Regards,
Eric

renegat
Posts: 7
Joined: Wed Oct 23, 2013 2:47 am
languages_spoken: english german
ODROIDs: U2
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by renegat » Wed Nov 21, 2018 1:29 am

Any solution on this?

Same issue here with
Odroid U3+

Linux odu3p 4.19.1-1-ARCH #1 SMP PREEMPT Thu Nov 8 03:29:30 UTC 2018 armv7l GNU/Linux
256GB Samsung EVO Plus 2018 Modell
Filesystem: F2FS

Code: Select all

[268006.690274] mmc0: Card stuck in programming state! mmc_do_erase
[268012.198958] mmc0: Card stuck in programming state! mmc_do_erase
[268014.278939] mmc0: Card stuck in programming state! mmc_do_erase

midtskogen
Posts: 94
Joined: Mon Jul 27, 2015 3:57 am
languages_spoken: english norwegian
ODROIDs: U3 XU3-Lite XU4
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by midtskogen » Wed Jan 02, 2019 3:11 pm

I'll add that I've also seen this issue Ubuntu 18.04 on an XU4. ext4. Happened when weekly cron job started fstrim. Both partitions on SD card became unreadable (I/O errors). Reboot resolved the problem.

Code: Select all

Dec 17 00:00:11 odroid kernel: [821873.419751] mmc1: Card stuck in programming state! mmc_do_erase
Dec 17 00:00:12 odroid kernel: [821873.924957] dwmmc_exynos 12220000.mmc: Busy; trying anyway
Dec 17 00:00:12 odroid kernel: [821874.429647] mmc_host mmc1: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000)
Dec 17 00:00:12 odroid kernel: [821874.461692] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
Dec 17 00:00:13 odroid console: console: terminating too quickly, waiting 300 seconds
Dec 17 00:00:14 odroid kernel: [821876.491966] mmc1: card never left busy state
Dec 17 00:00:14 odroid kernel: [821876.499332] mmc1: tried to reset card, got error -110
Dec 17 00:00:14 odroid kernel: [821876.499377] print_req_error: I/O error, dev mmcblk1, sector 34834432
Dec 17 00:00:14 odroid kernel: [821876.511756] mmcblk1: error -110 sending status command, retrying
Dec 17 00:00:14 odroid kernel: [821876.522639] mmcblk1: error -110 sending status command, retrying
Dec 17 00:00:14 odroid kernel: [821876.529112] mmcblk1: error -110 sending status command, aborting
Dec 17 00:00:14 odroid fstrim[26318]: fstrim: /meteor: FITRIM ioctl failed: Input/output error
Dec 17 00:00:15 odroid fstrim[26318]: /: 147.8 MiB (154943488 bytes) trimmed
Dec 17 00:00:15 odroid systemd[1]: fstrim.service: Main process exited, code=exited, status=64/n/a
Dec 17 00:00:15 odroid systemd[1]: fstrim.service: Failed with result 'exit-code'.
Dec 17 00:00:15 odroid systemd[1]: Failed to start Discard unused blocks.
Dec 17 00:00:16 odroid kernel: [821878.584306] mmc1: card never left busy state
Dec 17 00:00:16 odroid kernel: [821878.590700] mmc1: tried to reset card, got error -110
Dec 17 00:00:16 odroid kernel: [821878.590732] print_req_error: I/O error, dev mmcblk1, sector 264505368
Dec 17 00:00:16 odroid kernel: [821878.599715] Buffer I/O error on dev mmcblk1p2, logical block 33030147, lost async page write
Dec 17 00:00:16 odroid kernel: [821878.613676] mmcblk1: error -110 sending status command, retrying
Dec 17 00:00:17 odroid kernel: [821878.620028] mmcblk1: error -110 sending status command, retrying
Dec 17 00:00:17 odroid kernel: [821878.626431] mmcblk1: error -110 sending status command, aborting

midtskogen
Posts: 94
Joined: Mon Jul 27, 2015 3:57 am
languages_spoken: english norwegian
ODROIDs: U3 XU3-Lite XU4
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by midtskogen » Sat Jan 19, 2019 3:20 pm

Happened again, this time without fstrim running. My setup has a lot of writing to the SD card anyway.

Code: Select all

Jan 19 01:51:29 odroid kernel: [3085456.304471] mmc1: Card stuck in programming state! mmc_do_erase
Jan 19 01:51:30 odroid kernel: [3085456.809176] dwmmc_exynos 12220000.mmc: Busy; trying anyway
Jan 19 01:51:30 odroid kernel: [3085457.313437] mmc_host mmc1: Timeout sending command (cmd 0x202000 arg 0x0 status 0x80202000)
Jan 19 01:51:30 odroid kernel: [3085457.345840] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
Jan 19 01:51:32 odroid kernel: [3085459.536500] mmc1: card never left busy state
Jan 19 01:51:32 odroid kernel: [3085459.539477] mmc1: tried to reset card, got error -110
Jan 19 01:51:32 odroid kernel: [3085459.539489] print_req_error: 11 callbacks suppressed
Jan 19 01:51:32 odroid kernel: [3085459.539494] print_req_error: I/O error, dev mmcblk1, sector 496788096
Jan 19 01:51:32 odroid kernel: [3085459.548142] mmcblk1: error -110 sending status command, retrying
Jan 19 01:51:32 odroid kernel: [3085459.553774] mmcblk1: error -110 sending status command, retrying
Jan 19 01:51:32 odroid kernel: [3085459.559952] mmcblk1: error -110 sending status command, aborting
Jan 19 01:51:35 odroid kernel: [3085461.628709] mmc1: card never left busy state
Jan 19 01:51:35 odroid kernel: [3085461.631763] mmc1: tried to reset card, got error -110
Jan 19 01:51:35 odroid kernel: [3085461.631810] print_req_error: I/O error, dev mmcblk1, sector 342050304
Jan 19 01:51:35 odroid kernel: [3085461.638594] print_req_error: I/O error, dev mmcblk1, sector 342050312
Jan 19 01:51:35 odroid kernel: [3085461.645124] print_req_error: I/O error, dev mmcblk1, sector 342050320
Jan 19 01:51:35 odroid kernel: [3085461.652160] print_req_error: I/O error, dev mmcblk1, sector 342050328
Jan 19 01:51:35 odroid kernel: [3085461.658212] print_req_error: I/O error, dev mmcblk1, sector 342050336
Jan 19 01:51:35 odroid kernel: [3085461.665074] print_req_error: I/O error, dev mmcblk1, sector 342050344
Jan 19 01:51:35 odroid kernel: [3085461.671344] print_req_error: I/O error, dev mmcblk1, sector 342050352
Jan 19 01:51:35 odroid kernel: [3085461.678136] print_req_error: I/O error, dev mmcblk1, sector 342050360
Jan 19 01:51:35 odroid kernel: [3085461.684513] print_req_error: I/O error, dev mmcblk1, sector 342050368
Jan 19 01:51:35 odroid kernel: [3085461.691153] EXT4-fs warning (device mmcblk1p2): ext4_end_bio:323: I/O error 10 writing to inode 3014840 (offset 0 size 176128 starting block 42756331)
Jan 19 01:51:35 odroid kernel: [3085461.691174] Buffer I/O error on device mmcblk1p2, logical block 42723264
Jan 19 01:51:35 odroid kernel: [3085461.697931] Buffer I/O error on device mmcblk1p2, logical block 42723265
Jan 19 01:51:35 odroid kernel: [3085461.704743] Buffer I/O error on device mmcblk1p2, logical block 42723266
Jan 19 01:51:35 odroid kernel: [3085461.711657] Buffer I/O error on device mmcblk1p2, logical block 42723267
Jan 19 01:51:35 odroid kernel: [3085461.718437] Buffer I/O error on device mmcblk1p2, logical block 42723268
Jan 19 01:51:35 odroid kernel: [3085461.725446] Buffer I/O error on device mmcblk1p2, logical block 42723269
Jan 19 01:51:35 odroid kernel: [3085461.732119] Buffer I/O error on device mmcblk1p2, logical block 42723270
Jan 19 01:51:35 odroid kernel: [3085461.738956] Buffer I/O error on device mmcblk1p2, logical block 42723271
Jan 19 01:51:35 odroid kernel: [3085461.745803] Buffer I/O error on device mmcblk1p2, logical block 42723272
Jan 19 01:51:35 odroid kernel: [3085461.752637] Buffer I/O error on device mmcblk1p2, logical block 42723273
Jan 19 01:51:35 odroid kernel: [3085461.761700] mmcblk1: error -110 sending status command, retrying
Jan 19 01:51:35 odroid kernel: [3085461.767346] mmcblk1: error -110 sending status command, retrying
Jan 19 01:51:35 odroid kernel: [3085461.773503] mmcblk1: error -110 sending status command, aborting
Jan 19 01:51:35 odroid kernel: [3085461.778769] EXT4-fs warning (device mmcblk1p2): ext4_end_bio:323: I/O error 10 writing to inode 3007 (offset 0 size 4096 starting block 3519997)
Jan 19 01:51:35 odroid kernel: [3085461.778824] JBD2: Detected IO errors while flushing file data on mmcblk1p2-8
Jan 19 01:51:35 odroid kernel: [3085461.780733] mmcblk1: error -110 sending status command, retrying
Jan 19 01:51:35 odroid kernel: [3085461.786349] mmcblk1: error -110 sending status command, retrying
Jan 19 01:51:35 odroid kernel: [3085461.792549] mmcblk1: error -110 sending status command, aborting
Jan 19 01:51:35 odroid kernel: [3085461.798043] Aborting journal on device mmcblk1p2-8.
Jan 19 01:51:35 odroid kernel: [3085461.802637] EXT4-fs error (device mmcblk1p2) in ext4_setattr:5498: Readonly filesystem
Jan 19 01:51:35 odroid kernel: [3085461.804724] mmcblk1: error -110 sending status command, retrying
Jan 19 01:51:35 odroid kernel: [3085461.805648] mmcblk1: error -110 sending status command, retrying
Jan 19 01:51:35 odroid kernel: [3085461.806672] mmcblk1: error -110 sending status command, aborting
Jan 19 01:51:35 odroid kernel: [3085461.806705] Buffer I/O error on dev mmcblk1p2, logical block 0, lost sync page write
Jan 19 01:51:35 odroid kernel: [3085461.839101] mmcblk1: error -110 sending status command, retrying
Jan 19 01:51:35 odroid kernel: [3085461.844752] mmcblk1: error -110 sending status command, retrying
Jan 19 01:51:35 odroid kernel: [3085461.850858] mmcblk1: error -110 sending status command, aborting
Jan 19 01:51:35 odroid kernel: [3085461.856160] Buffer I/O error on dev mmcblk1p2, logical block 30965760, lost sync page write
Jan 19 01:51:35 odroid kernel: [3085461.864751] JBD2: Error -5 detected when updating journal superblock for mmcblk1p2-8.
Jan 19 01:51:35 odroid kernel: [3085461.877075] mmc_erase: group start error -110, status 0x40ff8080

User avatar
odroid
Site Admin
Posts: 30028
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Contact:

Re: mmc1: Card stuck in programming state!

Unread post by odroid » Mon Jan 21, 2019 9:52 am

@midtskogen,
We need further information.
Kernel version?
SD card brand/model name?
File system?

Post Reply

Return to “Linux Kernel 4.14 Debugging Party”

Who is online

Users browsing this forum: No registered users and 0 guests