Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#45796 - [virtualbox] development kernel 4.2rc2 panic with vbox 5.0.0
Attached to Project:
Community Packages
Opened by Robert Navarro (cr0ntab) - Monday, 27 July 2015, 15:31 GMT
Last edited by Sébastien Luttringer (seblu) - Monday, 03 August 2015, 22:06 GMT
Opened by Robert Navarro (cr0ntab) - Monday, 27 July 2015, 15:31 GMT
Last edited by Sébastien Luttringer (seblu) - Monday, 03 August 2015, 22:06 GMT
|
DetailsDescription:
I am getting a kernel panic and full lockup (caps lock key blinking) of my system when trying to run a virtual machine under the latest virtualbox. Note, this is a lockup of the host system not the VM. The VM doesn't even get to boot. I'm not sure where to find the actual kernel output from the panic. Additional info: This is using the latest 5.0.0-1 virtualbox on 4.2.0-rc4-mainline kernel. I'm led to believe this is an issue with Virtualbox as everything else works on my system with the mainline kernel. rnavarro-thinkpad:~$ uname -a Linux rnavarro-thinkpad 4.2.0-rc4-mainline #1 SMP PREEMPT Thu Jul 23 10:24:45 CEST 2015 x86_64 GNU/Linux Let me know what other information I can get to help debug this, I'm new to submitting bugs and such on Arch linux. Steps to reproduce: 1) Start virtualbox VM 
IMG_20150727_081754.jpg
(1.89 MiB)
|
This task depends upon
Closed by Sébastien Luttringer (seblu)
Monday, 03 August 2015, 22:06 GMT
Reason for closing: Not a bug
Monday, 03 August 2015, 22:06 GMT
Reason for closing: Not a bug
Do you need more information from me to help debug? I'm more than happy to do some extra legwork on this to figure it out.
I don't know where to start. You are reporting a bug because a kernel freeze when you are running an out-of-tree module.
This kernel is not the Arch one, so we will not debug it for you.
Moreover, you are using a development kernel, which targets developers and testers which works with upstream.
As you claim to be a newbie, you may find people willing to help you with your exotic setup on bbs or irc, or directly upstream.
Or you can just come back to a stable setup.
Thanks for the response Sébastien. I hadn't considered testing on the stock kernel, I jumped to conclusions when I figured it was a VirtualBox bug.
When booting into the stock kernel things work great, so it's definitely something wrong with the kernel.
We can close this one out and I'll engage with the linux-mainline kernel maintainer.
Good luck.