-
Notifications
You must be signed in to change notification settings - Fork 585
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Can't dump file 12 of that type" upon dumping a simple test.sh #1112
Comments
Can you try on a non-btrfs based system: https://criu.org/Filesystems_pecularities |
Hmm… Okay, though I'm unsure on one detail. I reproduce it in $ mount | grep /tmp
tmpfs on /tmp type tmpfs (rw,nosuid,nodev) I do it on tmpfs, not on btrfs. Do I need to completely exclude btrfs from mount points? If so, that would be problematic as both computers I have have use it as their root filesystem. |
The log says that criu had troubles with a chardev:
Can you check what is this device? |
It is $ grep 226 /proc/devices
226 drm If that matters, I have two GPUs, Intel and AMD. |
criu cannot handle open |
Oh, this is sad. I was mainly interested in criu to save state of a wine game. Oh, well…
|
Btw, I confirm that running the test.sh and looking through file descriptors there's $ ll /proc/$(pgrep test.sh)/fd
total 0
lrwx------ 1 constantine constantine 64 июн 21 12:39 0 -> /dev/pts/4
lrwx------ 1 constantine constantine 64 июн 21 12:39 1 -> /dev/pts/4
lrwx------ 1 constantine constantine 64 июн 21 12:39 12 -> /dev/dri/card0
lrwx------ 1 constantine constantine 64 июн 21 12:39 2 -> /dev/pts/4
lr-x------ 1 constantine constantine 64 июн 21 12:39 255 -> /tmp/test.sh Indeed this is odd.
Thanks! |
Okay, so I figured the Okay, so, since it all comes down to a DRM device being opened, and there already are issues for this, current one would be a duplicate, so I'm closing it |
I'm following this tutorial, and the dumping step fails for me. Error in description is the first one I see.
Steps to reproduce
Expected
A print "OK"
Actual
Nothing printed
Additional information
The text was updated successfully, but these errors were encountered: