On 2019-10-25 10:49 a.m., Michal Nowak wrote:
On 10/25/19 06:53 PM, Geoff Nordli wrote:
On 2019-10-23 10:31 p.m., Michal Nowak wrote:
Please, run the long mdb command on the dump file from the
https://illumos.org/docs/user-guide/debug-systems/#gathering-information-from-a-crash-dump
document
echo '::panicinfo\n::cpuinfo -v\n::threadlist -v
10\n::msgbuf\n*panic_thread::findstack -v\n::stacks' | mdb 0 >
~/crash.0
and attach the resulting text file somewhere. Email or some paste
service should do fine.
Thanks,
Michal
On 10/24/19 05:53 AM, Carl Brewer wrote:
On 24/10/2019 2:19 pm, Carl Brewer wrote:
I can pop these files on a webserver if that helps anyone to have
a look, and see what might be going wrong.
here they are :
http://nr1.aboc.net.au/testy/
Hi Michal.
We know that setting the disable_smap fixes the crash part.
I guess the part I don't understand is why some systems don't need to
disable smap. It concerns me that there is something wrong.
thanks,
Geoff
I don't know, but one possibility is that folks run OpenIndiana on
older systems where SMAP is not available, or do not run VirtualBox.
For example according to `cpuid` utility my Lenovo 230 laptop with Ivy
Bridge gen CPU does not have SMAP (Supervisor Mode Access Prevention),
only SMEP (Supervisor Mode Execution Protection) and I run VirtualBox
without problems.
Can someone who runs VirtualBox on Broadwell or newer CPU check
`cpuid`, if they have SMAP?
If there's something wrong it's likely something in the VirtualBox
kernel code trying to access memory the SMAP-aware kernel does not
want it to have.
I found a VirtualBox bug report on this topic but no response from
VirtualBox devs for more than a year:
https://www.virtualbox.org/ticket/17958. Even Oracle acknowledges this
problem with Solaris 11.4:
https://docs.oracle.com/cd/E37838_01/html/E60973/appcompat.html#SERNSgtaji.
Their workaround is to disable SMAP.
In the ticket 17958 I mention other SMAP fixes for Linux and macOS,
someone motivated enough might want to go thru them and have a look if
they are applicable to Solaris kernel code as well. Fixes went 4 years
ago to VirtualBox 5.0.2 and 5.0.4:
https://www.virtualbox.org/wiki/Changelog-5.0.
Hi Michal.
You could be on to something there. I don't have a cpuid tool. Any
suggestions on getting the cpu information.
thanks,
Geoff
_______________________________________________
openindiana-discuss mailing list
[email protected]
https://openindiana.org/mailman/listinfo/openindiana-discuss
