Summary: | app-emulation/virtualbox-modules-6.1.16-r1 at linux 5.10 - crashes | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexey Shevchuck <public.avatar> |
Component: | Current packages | Assignee: | Lars Wendler (Polynomial-C) <polynomial-c> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | adjudicatordarren, jstein, xavier.fim |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge --info |
Description
Alexey Shevchuck
2020-12-15 23:08:32 UTC
The log is from host? Tell us more about the VMs you tried. Try the patches for the VM side if it is a linux VM. https://www.virtualbox.org/ticket/20055 You have to adapt the path for gentoo packages in the patches. Yes, the log is from host. I'm starting Win10, and during VM loading host gets this crash. I.e. VM was not fully loaded when this crash happens (VBox load gauge was on 20%). Crash happens every time I'm trying to start VM. please provide output of emerge --info in the meantime you can search at https://www.virtualbox.org/wiki/Bugtracker Created attachment 678481 [details]
emerge --info
Yes, look like it's better to address problem to upstream. Initially I had an idea this may happen because of the patch, but the patch is identical to the one attached to the ticket. please add a link to the upstream report here I added comment to existing ticket => https://www.virtualbox.org/ticket/20055#comment:10 CONFIG_DEBUG_SPINLOCK=y is what's causing the crash, but it's unclear if it's a kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=211469 or a virtualbox bug: https://www.virtualbox.org/ticket/20163 So far, I'm using CONFIG_DEBUG_SPINLOCK=n to avoid the crash, but I'd like to have it be =y Any ideas on what to do next to figure out what's the cause? I have the time and willingness, just need the brains :D |