Open yashlala opened 1 year ago
Hi Yash,
I haven't encountered such issue before and it seems the error is not quite related to Hermit's logic. My current guess is that Hermit changed the cgroup struct definition and there may be some mismatches in your kernel header files and the compiled kernel image. Anyways, I will double check it soon and get back to you.
Thanks, Yifan
Dear Yifan,
Thank you for the quick response!
That's a good hypothesis. I've tested it and a few other potential causes. Here are my test notes, hopefully they can help:
Possible Causes to Investigate:
insmod
=> false premise; It's unlikely the issue is in the client module. hmt_async_reclaim+0x1fd/0x2e0
, and similar error messages have been caused by double-unlocks. TODO start debugging Hermit.
Dear Yifan,
When installing the Hermit kernel as described in the README, the kernel ring buffer fills up with warnings about corrupted spinlocks. I wanted to check whether these messages are known issues w/ Hermit, or indicative of a larger problem (I was having issues w/ setup otherwise).
Environment
(identical to the Hermit README)
To Reproduce
Follow the README for the following steps:
dmesg
.dmesg
will show that the kernel ring buffer is full of corrupted spinlock related messages. Eg:A more complete
dmesg
log is linked hereRegards,
Yash