rcu_sched Error on Host Registration - PC Tablet w/ Dock

[explosivo98]

@george1421 !! holy cow, that actually got me past the rcu_sched error! This is farther than I’ve ever gotten with this. Everything looked like it was going to work and I was ready to throw a party but it failed the getHardDisk check, it can’t detect the hard drive on here now for some reason. The storage on this is a Sandisk DF4064 which is an eMMC drive if that matters. I tried single disk resizable mode as well as multi partition non resizeable and neither worked. Running the compatibility test does show a Fail for the hard drive check as well. Are there special considerations I need to make when dealing with one of these drives?

[george1421]

@explosivo98 What version of the FOS Linux kernel are you using?

Also which kernel parameter did the trick?

[explosivo98]

@george1421 Looks like it was the ACPI toggle that did it, I switched back to the newest production kernel after getting it working on the newest dev build and it worked there so right now I’m using 4.19.64

[george1421]

@explosivo98 OK so now that this point you are still stuck with the missing disk?

[explosivo98]

@george1421 yeah I am, like I said I tried switching between some of the hard drive types but nothing made a difference, but I assume since running the compatibility test returns a similar error that it probably doesn’t have anything to do with that anyway.

[george1421]

@explosivo98 Ok lets collect some data on 2 fronts.

1. From a running Windows computer. Can you get the hardware IDs of that storage device. It will be in the device manager. I need both the vendor and device ID.

2. This one will be a bit more involved. Reschedule a capture/deploy to that target computer, but before you hit the schedule task button, check the debug checkbox. Then pxe boot the target computer. After a few screens of text where you will have to clear with the enter key you should be dropped to the FOS Linux command prompt. At the fos linux command prompt key in lsblk and post the output here (you may need to take a clear picture with a mobile phone to get what we need). Keep this session running because we may need you to look at a startup log file… while you are at it getting screen shots does this return anything grep /var/log/messages mc0 or grep /var/log/messages mmc?

[george1421]

Doing a bit more research on this and there are several linux distros that have the same issue with this hardware. I did find a reference to it being fixed in Linux 5.3.x series. I have a one off kernel that I complied for working around the T2 chip in a 2018 mac that should be 5.3.(something)
https://drive.google.com/open?id=12St-Wix1io0s0oXhgxAuLlQOVoT9548L

[explosivo98]

@george1421
hm, the hardware ID for this looks like it’s just a generic driver, it shows as SD\GenDisk in the device manager. I’m on the command prompt now but lsblk returns nothing and the grep commands returned “no such file” when ran.

Edit: Trying the kernel now!

[explosivo98]

@george1421 would I need a new init file for this as well or no? I tried rebooting with the same debug task in queue from last time and it just froze after loading (successfully) the init file. I rebooted with the task canceled and selected the system compatibility check option and it just went to a black screen after that.

[george1421]

@explosivo98 You should not need the new init for this. That kernel should work with FOG 1.5.7. Now is that tablet a 32 bit machine or a 64 bit?

[explosivo98]

@george1421 okay, thought I’d check. This is an x64 device.

[george1421]

@explosivo98 Strange that kernel should boot because the only thing added was some apple hardware IDs and an apple disk patch. Nothing for non-apples should be impacted.