On 24/10/2019 4:31 pm, 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\
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
Thank you Geoff Nordli, setting
set disable_smap=1
in /etc/system
stopped the host server crash.
Carl
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
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/
___
openindiana-discuss mailing list
openindiana-d
On 24/10/2019 1:53 pm, Carl Brewer wrote:
Doing that now, but the log file is too large to go flinging around in
emails on lists. What's the best way to share it here?
i did a pkg update -v today, then retried running virtualbox through a
VNC session to the console of the server.
It crash
Hey Michal,
On 20/10/2019 7:12 am, Michal Nowak wrote:
If it crashes, can you gather more information from the crash dump? How
to do it is described here:
https://illumos.org/docs/user-guide/debug-systems/#gathering-information-from-a-crash-dump.
It could be the same thing Geoff reported
