-
Notifications
You must be signed in to change notification settings - Fork 23
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
'get_page_from_freelist' general protection fault #75
Comments
get_page_from_freelist
general protection fault
I am not seeing this issue but I am seeing deadlock when I run |
|
Hey @bxatnarf . I guess the benchmarks in popcorn-kern-lib should work fine now. Since I saw your reply under this issue, just make sure we are talking the same benchmark. I guess the failed benchmark I used was https://github.com/ssrg-vt/SNU_NPB-1.0.3/tree/make-popcorn-explicit/NPB3.3-SER-C-FLAT/bt. I realize that I may not add you to the repo. here is the invitation link: https://github.com/ssrg-vt/SNU_NPB-1.0.3/invitations |
Woops, I spaced out and thought that We don't want the kernel to be spitting out errors because there is something wrong with the userland binary. We should keep copies of the binaries that cause errors so we can be sure to address these problems. Of course our first priority is make sure all of the examples that work on the |
Please take a look at this NPB/BT binary, it has migration pointer inserted. I look at it in my popcorn VM, seems that is the only BT binary. Try to run it about 10 times, to see whether you could observe that issue. https://github.com/ssrg-vt/popcorn-kernel/blob/arm64-mt/bt.W.x |
I have noticed that when I have popcorn's debugging enabled, I'm more likely to achieve deadlock. @xjtuwxg, what popcorn config options do you have set when you get this GPF? Could you paste the output of |
I can't remember what is the configuration when I got this error message. Here is what I get from my current popcorn kernel configuration. While, I think if we could observe this bug, we may want to know why this is happened and should solve it. (although it might be hard)
|
@xjtuwxg I want to see if I can reproduce this on arm. Do you remember what changes you made to bt and what your build configuration for it is? Or do you have a copy of the equivalent arm binary? My tries thus far have only retriggered issue #80 |
I can reproduce it on x86, I'd just like to know if it is also a problem on
arm for the sake of debugging and patching.
…On Wed, Mar 27, 2019 at 4:14 PM Xiaoguang Wang ***@***.***> wrote:
Hi @bxatnarf <https://github.com/bxatnarf>, I can't remember what I
changed the code. It has been a long time. Maybe we should try to solve
issue #80 <#80> if we
cannot reproduce this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#75 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AkuD_IopFUPqPUwsNdzoFV5q5JTu8tMCks5va9EUgaJpZM4ZZGDW>
.
|
After running NPB/BT (x86 homogeneous setting), the remote node waits for about 600s and generates a general protection fault.
I only modified NPB/BT slightly, so it might also have this issue for other simpler benchmark.
The text was updated successfully, but these errors were encountered: