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

Unsupported function kill called in Mini-OS kernel #44

Open
belsholff opened this issue Nov 23, 2017 · 0 comments
Open

Unsupported function kill called in Mini-OS kernel #44

belsholff opened this issue Nov 23, 2017 · 0 comments

Comments

@belsholff
Copy link

belsholff commented Nov 23, 2017

People,

I'm experiencing a problem that kills/stops Mini-OS execution. It just manifests when clickOS instance is in "standby". It happens when the system execute the following line.

assert(p >= buffer() && p + len <= end_buffer());

The console's output is:

assertion "p >= buffer() && p + len <= end_buffer()" failed: file "/path/to/clickos/include/click/packet.hh", line 1844, function: void Packet::set_network_header(const unsigned char*, uint32_t)
Unsupported function kill called in Mini-OS kernel
Do_exit called!
base is 0x36fe38 caller is 0xb01e9
base is 0x36fe58 caller is 0xb95a5
base is 0x36fe68 caller is 0xa0851
base is 0x36fe88 caller is 0x9e6fe
base is 0x36fe98 caller is 0x9e76f
base is 0x36fee8 caller is 0x78e1d
base is 0x36fef8 caller is 0x192e0
base is 0x36ff18 caller is 0x7dc43
base is 0x36ff48 caller is 0x48435
base is 0x36ff98 caller is 0x391d
base is 0x36ffe8 caller is 0x35a6`

xl list output shows something this:

Name ID Mem VCPUs State Time(s)
Domain-0 0 750 4 r----- 11794.3
router 1 18 1 ---sc- 0.3
linux 2 1024 2 r----- 5624.2

'sc' means shutdown and crashed.

I used these packets to compile clickOS/miniOS kernel from this tutorial:

http://people.cs.clemson.edu/~hongdal/clickos.tar
http://people.cs.clemson.edu/~hongdal/mini-os.tar
http://people.cs.clemson.edu/~hongdal/cosmos.tar
http://people.cs.clemson.edu/~hongdal/toolchain.tar

Would it be outdated and so already fixed?
Have you ever seen this before? Maybe it would be a kind of "hibernation" not handled in development?

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant