Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 15 Jan 2022 03:01:44 +0000
From:      Pau Amma <pauamma@gundo.com>
To:        freebsd-hackers@freebsd.org
Subject:   Suggestions for moving PR 248368 forward?
Message-ID:  <37d4d559ca295c68f474ab40838eab3a@gundo.com>
In-Reply-To: <f384f79e191da3e9615c315923ceff7a@gundo.com>
References:  <f384f79e191da3e9615c315923ceff7a@gundo.com>

next in thread | previous in thread | raw e-mail | index | archive | help
(Please cc: me in replies as I only subscribed to the list to ask this 
and may have to unsubscribe if it proves overwhelming.)

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248368 has been 
gathering dust for close to 1.5 year now and I'm trying to help moving 
it closer to resolution, because the VirtualBox part at least affects 
me. One thing I think would be good is for one or more people able to 
look closely at host and guest kernel behavior and at VirtualBox 
behavior to determine which contribute to that part of the symptoms. If 
someone can come up with hard evidence pointing to one of the above, 
maybe knowing where the problem may lie will help pinpointing it.

Figuring out the bare-metal part of the problem would be good too, but 
it's clearer that only FreeBSD (and maybe some of the computer's 
firmware) is a possible cause.

advTHANKSance.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37d4d559ca295c68f474ab40838eab3a>