Unable to boot a compiled kernel [on hold]

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I am working on a project where I have start of by adding some system calls to a kernel (Linux 3.13.11 to be particular), after adding the calls and writing their prototype in the correct locations across the kernel image.



When I boot enter image description here it I initially get stuck at:
Loading Linux 3.13.11-ckt39-custom..
Loading initial ramdisk



enter image description here I am by no means professional and unable to proceed from there. I tried removing splash and quiet it doesn't change a thing..and apparently after many tries (sometimes even 2nd try) I get kernel panic enter image description here



EDIT: I am running on VirtualBox, and I tried without adding systemcalls as default with same issue. Where do you think it is going wrong?










share|improve this question









New contributor




Ahmed Nader is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











put on hold as too broad by Romeo Ninov, JigglyNaga, Rui F Ribeiro, jimmij, RalfFriedl 2 days ago


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.














  • Welcome to U&L! If you build the same kernel version without your new system calls, does it boot OK?
    – JigglyNaga
    2 days ago










  • I just tried this out of curiosity and it turns out that I come across the same error while booting. That is same kernel with default settings. I have tried this multiple times with each time I get same results so what do you think this means?
    – Ahmed Nader
    6 hours ago














up vote
1
down vote

favorite












I am working on a project where I have start of by adding some system calls to a kernel (Linux 3.13.11 to be particular), after adding the calls and writing their prototype in the correct locations across the kernel image.



When I boot enter image description here it I initially get stuck at:
Loading Linux 3.13.11-ckt39-custom..
Loading initial ramdisk



enter image description here I am by no means professional and unable to proceed from there. I tried removing splash and quiet it doesn't change a thing..and apparently after many tries (sometimes even 2nd try) I get kernel panic enter image description here



EDIT: I am running on VirtualBox, and I tried without adding systemcalls as default with same issue. Where do you think it is going wrong?










share|improve this question









New contributor




Ahmed Nader is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











put on hold as too broad by Romeo Ninov, JigglyNaga, Rui F Ribeiro, jimmij, RalfFriedl 2 days ago


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.














  • Welcome to U&L! If you build the same kernel version without your new system calls, does it boot OK?
    – JigglyNaga
    2 days ago










  • I just tried this out of curiosity and it turns out that I come across the same error while booting. That is same kernel with default settings. I have tried this multiple times with each time I get same results so what do you think this means?
    – Ahmed Nader
    6 hours ago












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I am working on a project where I have start of by adding some system calls to a kernel (Linux 3.13.11 to be particular), after adding the calls and writing their prototype in the correct locations across the kernel image.



When I boot enter image description here it I initially get stuck at:
Loading Linux 3.13.11-ckt39-custom..
Loading initial ramdisk



enter image description here I am by no means professional and unable to proceed from there. I tried removing splash and quiet it doesn't change a thing..and apparently after many tries (sometimes even 2nd try) I get kernel panic enter image description here



EDIT: I am running on VirtualBox, and I tried without adding systemcalls as default with same issue. Where do you think it is going wrong?










share|improve this question









New contributor




Ahmed Nader is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











I am working on a project where I have start of by adding some system calls to a kernel (Linux 3.13.11 to be particular), after adding the calls and writing their prototype in the correct locations across the kernel image.



When I boot enter image description here it I initially get stuck at:
Loading Linux 3.13.11-ckt39-custom..
Loading initial ramdisk



enter image description here I am by no means professional and unable to proceed from there. I tried removing splash and quiet it doesn't change a thing..and apparently after many tries (sometimes even 2nd try) I get kernel panic enter image description here



EDIT: I am running on VirtualBox, and I tried without adding systemcalls as default with same issue. Where do you think it is going wrong?







boot linux-kernel grub2 virtual-machine kernel-panic






share|improve this question









New contributor




Ahmed Nader is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




Ahmed Nader is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 4 hours ago





















New contributor




Ahmed Nader is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 2 days ago









Ahmed Nader

62




62




New contributor




Ahmed Nader is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Ahmed Nader is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Ahmed Nader is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




put on hold as too broad by Romeo Ninov, JigglyNaga, Rui F Ribeiro, jimmij, RalfFriedl 2 days ago


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.






put on hold as too broad by Romeo Ninov, JigglyNaga, Rui F Ribeiro, jimmij, RalfFriedl 2 days ago


Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.













  • Welcome to U&L! If you build the same kernel version without your new system calls, does it boot OK?
    – JigglyNaga
    2 days ago










  • I just tried this out of curiosity and it turns out that I come across the same error while booting. That is same kernel with default settings. I have tried this multiple times with each time I get same results so what do you think this means?
    – Ahmed Nader
    6 hours ago
















  • Welcome to U&L! If you build the same kernel version without your new system calls, does it boot OK?
    – JigglyNaga
    2 days ago










  • I just tried this out of curiosity and it turns out that I come across the same error while booting. That is same kernel with default settings. I have tried this multiple times with each time I get same results so what do you think this means?
    – Ahmed Nader
    6 hours ago















Welcome to U&L! If you build the same kernel version without your new system calls, does it boot OK?
– JigglyNaga
2 days ago




Welcome to U&L! If you build the same kernel version without your new system calls, does it boot OK?
– JigglyNaga
2 days ago












I just tried this out of curiosity and it turns out that I come across the same error while booting. That is same kernel with default settings. I have tried this multiple times with each time I get same results so what do you think this means?
– Ahmed Nader
6 hours ago




I just tried this out of curiosity and it turns out that I come across the same error while booting. That is same kernel with default settings. I have tried this multiple times with each time I get same results so what do you think this means?
– Ahmed Nader
6 hours ago















active

oldest

votes






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay