Skip to content
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

NOVA: Vancouver gets stuck #283

Closed
nfeske opened this issue Jul 18, 2012 · 1 comment
Closed

NOVA: Vancouver gets stuck #283

nfeske opened this issue Jul 18, 2012 · 1 comment
Assignees

Comments

@nfeske
Copy link
Member

nfeske commented Jul 18, 2012

With recent versions of base-nova, the port of the Vancouver VMM is not working any longer. At the startup, it gets stuck with the following error:

[init -> vancouver] VMM: RESET device state
[init -> vancouver] VMM: MessageLegacy::RESET requested
[init -> vancouver] VMM: OP_VCPU_RELEASE
[init -> vancouver] VMM: INIT done
[init -> vancouver] VMM: reset CPU from c mtr_in effff
[ 0] Killed EC:0xc1380660 SC:0xc13ef380 V:0xff CR0:0x10 CR3:0x0 CR4:0x0 (PT not found)

I was able to pinpoint the problem to commit a4cac75. Prior this commit, Vancouver booted up fine. Reverting this commit from current genodelabs/master (b2478ae) seems to solve the problem.

@udosteinberg
Copy link

The bug is not in the pinpointed commit. That commit fixes the binding to correctly issue a RECALL hypercall. What the kill message says is that there is no recall portal established; therefore the EC must die.
The correct fix is to establish a portal for the RECALL event and to handle the event properly.

@ghost ghost assigned alex-ab Jul 19, 2012
cproc pushed a commit to cproc/genode that referenced this issue May 12, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants