Re: [OpenIndiana-discuss] VirtualBox-6.1.16
Hi Carl! Thanks for your replay on this. As you see the weirdness in the gui it seems to be not a local issue on my machine - lucky me :-) I found it best when using full-frame, i could work with no issues there - if i start with full screen mode from the start. Any vm in a window will have issues - win 7/XP and linux, i don't have anything else right now. I have used the VMs in headless mod and VNC connect some time ago, i will try again as soon as i feel that i have to do so, but i hope that we can find the root of it. Is there anything i could provide to debug this? Is everyone seeing this who uses the gui? (a quick test is zo scroll the mouse over the list of installed VMs)) Stephan On 11/05/20 21:32, Carl Brewer wrote: I'm seeing similar issues to Stephan, VBox is working, my virtual servers are all running (they're all essentially headless, I don't use graphics on them). The VBox GUI is a bit weird, it's not working "properly", without a screenshot it's hard to describe. I'm using TightVNV and a VNC session, not a directly connected screen to run it too. This is from a BE I installed 15 minutes ago. Not sure how best to help sort this one out. It's not directly effecting me, my stuff works and I don't need the GUI to have all the icons looking right etc, as long as they're workable. Carl ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] VirtualBox-6.1.16
I'm seeing similar issues to Stephan, VBox is working, my virtual servers are all running (they're all essentially headless, I don't use graphics on them). The VBox GUI is a bit weird, it's not working "properly", without a screenshot it's hard to describe. I'm using TightVNV and a VNC session, not a directly connected screen to run it too. This is from a BE I installed 15 minutes ago. Not sure how best to help sort this one out. It's not directly effecting me, my stuff works and I don't need the GUI to have all the icons looking right etc, as long as they're workable. Carl ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ip_squeue_worker_wait is not defined in the ‘ip' module
Andreas - Many thanks for your quick reply. Turns out there’s a lot of long-forgotten vestigial stuff in my /etc/system file, some of it going back 10+ years! Was apparently having trouble some time back capturing dump files (Which seems on point as we speak, as the system is now not rebooting smoothly since most-recent pkg updates. How to make use of/interpret the crash dumps?) Any reason I should keep any of this stuff? - * LOUMOD per richlowe on #openindiana - this will ensure that dumps complete: * https://www.illumos.org/issues/1369 set dump_plat_mincpu=0 set dump_bzip2_level=1 * LOUMOD re notes on Oi list - https://www.illumos.org/issues/1333#note-21 * vmstat 5 (after about 2 days of running): * this did not seem to help (will try again): * set apix:apic_timer_preferred_mode = 0x0 * THIS note per Laurent Blume's email: http://tech.groups.yahoo.com/group/solarisx86/message/54377 * rmustacc: do # mdb -k, then: > setspl/p -- this PROVES I have the pcplusmp driver: set pcplusmp:apic_timer_preferred_mode = 0x0 set pcplusmp:apic_panic_on_nmi=1 * THIS per illumos Note #21 - adapted for apix driver set ip:ip_squeue_worker_wait=0 set snooping=1 > On Nov 5, 2020, at 12:27 PM, Andreas Wacknitz wrote: > > Am 05.11.20 um 18:20 schrieb Lou Picciano: >> Friends - >> >> After recent pkg update - to Hipster 2020.04 Version illumos-60de61ff53, am >> seeing at boot sequence - beyond this, system boots up fine: >> >> sorry, variable 'ip_squeue_worker_wait is not defined in the ‘ip' module >> ___ >> openindiana-discuss mailing list >> openindiana-discuss@openindiana.org >> https://openindiana.org/mailman/listinfo/openindiana-discuss > Did you set it in /etc/system? > It might have to do with https://www.illumos.org/issues/13148 > See also https://code.illumos.org/c/illumos-gate/+/926 > > Regards, > Andreas > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] ip_squeue_worker_wait is not defined in the ‘ip' module
Am 05.11.20 um 18:20 schrieb Lou Picciano: Friends - After recent pkg update - to Hipster 2020.04 Version illumos-60de61ff53, am seeing at boot sequence - beyond this, system boots up fine: sorry, variable 'ip_squeue_worker_wait is not defined in the ‘ip' module ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Did you set it in /etc/system? It might have to do with https://www.illumos.org/issues/13148 See also https://code.illumos.org/c/illumos-gate/+/926 Regards, Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] ip_squeue_worker_wait is not defined in the ‘ip' module
Friends - After recent pkg update - to Hipster 2020.04 Version illumos-60de61ff53, am seeing at boot sequence - beyond this, system boots up fine: sorry, variable 'ip_squeue_worker_wait is not defined in the ‘ip' module ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
[OpenIndiana-discuss] Lightdm starting using GTX1650
Hi
I noticed that in the /var/adm/messages that the panic always referenced
[cpu5], so I swapped CPU1 and CPU2 {Opteron 2389}
Nov 5 15:37:31 tesla ^Mpanic[cpu5]/thread=fe004db7bc20:
Nov 5 15:37:31 tesla genunix: [ID 647700 kern.notice] pcieb-2: PCI(-X)
Express Fatal Error. (0x41)
Nov 5 15:37:31 tesla unix: [ID 10 kern.notice]
Nov 5 15:37:31 tesla genunix: [ID 655072 kern.notice] fe004db7bb70
pcieb:pcieb_intr_handler+1dc ()
Nov 5 15:37:31 tesla genunix: [ID 655072 kern.notice] fe004db7bbc0
apix:apix_dispatch_by_vector+8c ()
Nov 5 15:37:31 tesla genunix: [ID 655072 kern.notice] fe004db7bc00
apix:apix_dispatch_lowlevel+1c ()
Nov 5 15:37:31 tesla genunix: [ID 655072 kern.notice] fe004db45a30
unix:switch_sp_and_call+15 ()
Nov 5 15:37:31 tesla genunix: [ID 655072 kern.notice] fe004db45aa0
apix:apix_do_interrupt+ec ()
Nov 5 15:37:31 tesla genunix: [ID 655072 kern.notice] fe004db45ab0
unix:cmnint+c3 ()
Nov 5 15:37:31 tesla genunix: [ID 655072 kern.notice] fe004db45ba0
unix:mach_cpu_idle+b ()
Nov 5 15:37:31 tesla genunix: [ID 655072 kern.notice] fe004db45bd0
unix:cpu_idle+10f ()
Nov 5 15:37:31 tesla genunix: [ID 655072 kern.notice] fe004db45be0
unix:cpu_idle_adaptive+19 ()
Nov 5 15:37:31 tesla genunix: [ID 655072 kern.notice] fe004db45c00
unix:idle+ae ()
Nov 5 15:37:31 tesla genunix: [ID 655072 kern.notice] fe004db45c10
unix:thread_start+b ()
Nov 5 15:37:31 tesla unix: [ID 10 kern.notice]
The panic occurred again on [cpu5]?
To try an eliminate both CPUs I swapped the Opteron 2389 {Quad Core} for
Opteron 2435 {Six Core}.
After swapping the panic again appeared on [cpu5], even after another
CPU swap.
Russell
___
openindiana-discuss mailing list
openindiana-discuss@openindiana.org
https://openindiana.org/mailman/listinfo/openindiana-discuss
