Hi, I'm new to this forum and to the art of troubleshooting hardware/driver issues in general.

I have a Asus C302C Chromebook with an intel core m3 that I recently blew away Chrome OS on. I used https://mrchromebox.tech/#fwscript coupled with removing the RW screw in the laptop to get the SeaBIOS firmware installed, and then I installed Kali linux, as one does.

Kali works just fine with all the known issues with sound, touchscreen, key remapping, etc. The only problem that has stumped me so far is an issue with the storage that will, after a period of time, make the FS read only. If I try to remount it rw, it complains about disk errors on the root partition that need to be fixed with fsck, so I have to reboot and fix them when the fsck commandline comes up.

I will show you what I have so far, with the hopes that someone who knows how to debug these problems can help me gather the necessary information to fix the problem.

Dmesg error message:
multiple 'mmc0: mmc_hs400_to_hs200 failed, error -110'
sometimes: [ 718.127381] mmc0: switch to high-speed from hs200 failed, err:-110
~ a cache_flush error message
~ then it goes read only
There are more messages that don't get written down to disk but I'll try to capture them on a card next time around.

Dmesg boot info:
[ 4.271574] mmc0: new HS400 MMC card at address 0001
[ 4.275170] mmcblk0: mmc0:0001 DF4064 58.2 GiB
[ 4.275392] mmcblk0boot0: mmc0:0001 DF4064 partition 1 4.00 MiB
[ 4.275559] mmcblk0boot1: mmc0:0001 DF4064 partition 2 4.00 MiB
[ 4.275654] mmcblk0rpmb: mmc0:0001 DF4064 partition 3 4.00 MiB, chardev (248:0)
[ 4.288348] mmcblk0: p1 p2 p3

Some more interesting (possibly) dmesg output.

[ 1139.757261] iwlwifi 0000:01:00.0: firmware: direct-loading firmware iwlwifi-7265D-29.ucode
[ 1139.757625] iwlwifi 0000:01:00.0: loaded firmware version 29.198743027.0 7265D-29.ucode op_mode iwlmvm
[ 1139.757658] iwlwifi 0000:01:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
[ 1139.757753] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[ 1139.764731] HDMI HDA Codec ehdaudio0D2: Max dais supported: 3
[ 1139.767605] snd_soc_skl 0000:00:1f.3: firmware: failed to load 9d70-INTEL-SCRDMAX-0-tplg.bin (-2)
[ 1139.767608] snd_soc_skl 0000:00:1f.3: Direct firmware load for 9d70-INTEL-SCRDMAX-0-tplg.bin failed with error -2
[ 1139.767615] snd_soc_skl 0000:00:1f.3: tplg fw 9d70-INTEL-SCRDMAX-0-tplg.bin load failed with -2, trying alternative tplg name skl_n88l25_m98357a-tplg.bin
[ 1139.767633] snd_soc_skl 0000:00:1f.3: firmware: failed to load skl_n88l25_m98357a-tplg.bin (-2)
[ 1139.767635] snd_soc_skl 0000:00:1f.3: Direct firmware load for skl_n88l25_m98357a-tplg.bin failed with error -2
[ 1139.767637] snd_soc_skl 0000:00:1f.3: tplg skl_n88l25_m98357a-tplg.bin failed with -2, falling back to dfw_sst.bin
[ 1139.767657] snd_soc_skl 0000:00:1f.3: firmware: failed to load dfw_sst.bin (-2)
[ 1139.767658] snd_soc_skl 0000:00:1f.3: Direct firmware load for dfw_sst.bin failed with error -2
[ 1139.767661] snd_soc_skl 0000:00:1f.3: Fallback tplg fw dfw_sst.bin load failed with -2
[ 1139.767662] snd_soc_skl 0000:00:1f.3: Failed to init topology!
[ 1139.767665] snd_soc_skl 0000:00:1f.3: ASoC: error at snd_soc_component_probe on 0000:00:1f.3: -2
[ 1139.767666] snd_soc_skl 0000:00:1f.3: ASoC: failed to probe component -2
[ 1139.767693] skl_n88l25_m98357a skl_n88l25_m98357a: ASoC: failed to instantiate card -2
[ 1139.767899] skl_n88l25_m98357a: probe of skl_n88l25_m98357a failed with error -2
[ 1139.796821] Bluetooth: Core ver 2.22
[ 1139.796842] NET: Registered protocol family 31
[ 1139.796843] Bluetooth: HCI device and connection manager initialized
[ 1139.796848] Bluetooth: HCI socket layer initialized
[ 1139.796851] Bluetooth: L2CAP socket layer initialized
[ 1139.796857] Bluetooth: SCO socket layer initialized
[ 1139.802226] intel_pmc_core intel_pmc_core.0: initialized
[ 1139.874191] iwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless AC 7265, REV=0x210
[ 1139.897604] iwlwifi 0000:01:00.0: base HW address: 1c:4d:70:3f:bf:88
[ 1139.957176] usbcore: registered new interface driver btusb
[ 1139.968210] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 1139.969014] thermal thermal_zone8: failed to read out thermal zone (-61)
[ 1139.972312] Bluetooth: hci0: read Intel version: 370810225019140f00
[ 1139.978391] bluetooth hci0: firmware: direct-loading firmware intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq
[ 1139.978400] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.8.10-fw-22.50.19.14.f.bseq
[ 1140.329268] Bluetooth: hci0: Intel BT fw patch 0x41 completed & activated
[ 1146.464810] wlan0: authenticate with d8:0d:17:bc:4f:0b
[ 1146.468937] wlan0: send auth to d8:0d:17:bc:4f:0b (try 1/3)
[ 1146.470779] wlan0: authenticated
[ 1146.480636] wlan0: associate with d8:0d:17:bc:4f:0b (try 1/3)
[ 1146.482862] wlan0: RX AssocResp from d8:0d:17:bc:4f:0b (capab=0x511 status=0 aid=3)
[ 1146.489640] wlan0: associated
[ 1146.571622] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

[ 1202.715123] i915 0000:00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
[ 4995.950144] mmc0: mmc_hs400_to_hs200 failed, error -110
[ 5325.944199] mmc0: mmc_hs400_to_hs200 failed, error -110

/sys/bus/mmc/devices/mmc0:0001
name: DF4064

Where do I go from here?

I have the read-only issue with my SD card when resuming sometimes. That is due to the OS coming back up before the SD slot gets activated and causing /home to be RO, but the main drive with the OS is just fine.
I have not found any fix for this issue, so I just have to reboot when it happens.

But it looks like your issue is the main storage drive from the error message, which is odd. Is this after suspending the system?

That's interesting, and I think I had that issue as well in some capacity when I was playing around with the sd card before. In fact, I think it might have messed up my sdcard somehow because the card become permanently read only, or at least as far as I could tell using multiple tools.

My issue happens after the it's been on for a while. Usually 3-4 of the hs400_to_hs200 errors show up over the course of 1-3 days, then a cache flush and immediate ro-state. Sometimes I'll have to do an fsck on boot and it will fix orphaned nodes and a few other things, then I can exit and boot in like normal.

I wonder if the trim command that Cron runs every few hours might be the problem? Should be able to manually run it and see if error comes back.

Interesting, I hadn't cross referenced chron jobs with the errors yet.
I think it's interesting that it's the hs400_to_hs200_update function that fails because it sounds like something is trying to change the read frequency.

I'll take a look

Can't you remount it read-write instead?

I don't believe so.. I tried that if I remember correctly and it couldn't remount because it had errors. I couldn't fix the errors while logged in because they were on the boot partition. So I have to reboot and fix them when the fsck commandline pops up.