Patch-ID# 106387-05 Keywords: SunVTS security env2/env/socal/ffb/ena/pmem/atm/ftcputest/tape vtsk vtsui vtstty vtsui.online Sheffield Synopsis: SunVTS 2.1.3: security,Sheffield support,pmem panic, test fixed and tty ui core dump. Date: Jul/20/00 Solaris Release: 2.6 SunOS Release: 5.6 Unbundled Product: SunVTS Unbundled Release: 2.1.3 Relevant Architectures: sparc NOTE: sun4u-ft BugId's fixed with this patch: 4127310 4130881 4134320 4131221 4100883 4134806 4130178 4138884 4157773 4154981 4163201 4167827 4169913 4181086 4171288 4176804 4182754 4180290 4128744 4171682 4196008 4173086 4153352 4165796 4176493 4191289 4148477 4199391 4201984 4207208 4211740 4220233 4207851 4227807 4230733 4226927 4342039 4257528 4208149 4240072 4122829 4318966 4157741 4346984 4344099 Changes incorporated in this version: 4342039 4257528 4208149 4240072 4122829 4318966 4157741 4346984 4344099 Patches accumulated and obsoleted by this patch: 107135-02 Patches which conflict with this patch: Patches required with this patch: 105633-22 Obsoleted by: Files included with this patch: atmtest atmtest.msg atmtest_info.o disk_info.o enatest enatest_info.o env2test env2test.msg envtest ffbtest ftcputest ftcputest.msg ftcputest_info.o fttest/b2sync.csh fttest/force_oos.csh fttest/ftcpu_clean_up fttest/get_cpusets.csh fttest/set_pri4sync fttest/set_prid4 fttest/vts_cmsconfig msgdump nettest nettest.conf nettest_info.o pmem pmem.msg pstest saiptest saiptest.msg saip_info.o socaltest socaltest_info.o sptest sptest.msg sptest_info.o tape_info.o testadd testrm vts_msgmon vtsk vtstty vtsui vtsui.ol vtsui.online Problem Description: 4127310: SunVTS causes security leak 4130881: UI does not handle inclusive choice options properly 4134320: SunVTS env2test fails on Enterprise 250 after power supply fault 4131221: second vtsk process appears and hangs 4100883: workaround for - socaltest fails internal loopback on sunfire IO+ 4134806: SunVTS fails ffbtest on single buffer ffb2+ 4130178: Online UI misplaces schedule pop-up windows 4138884: SunVTS envtest fails on LOW fanspeed corner 4157773: SunVTS should apply automatically to set BYPASS_FS_PROBE to 1 for DiskSuite 4154981: disktest option window frozen after clicking the apply button 4163201: increase in fanspeed readback margin is required to prevent false failures 4167827: sptest probe can cause vtsk core when unexpected zs device links exist 4169913: enatest fails with SEGV when run on system with both photon and dilbert 4176804: sptest needs to be ported to sheffield platform 4171288: saip test fails in external loopback mode 4182754: SunVTS does not probe for network interfaces correctly 4180290: scsi disk devices show up on the same side of glm because of info from DKIOCINF 4128744: atmdriver does not clear existing VCs when put in internal loopback mod 4171682: atmtest in Solaris 2.6 does not work on SunATM 2.1 4196008: 1) atmtest fails on sheffield in internal loopback mode 2) add ftcputest 4173086: Support for HiPPI in nettest 4176493: SunVTS fails to start (hanging) 4153352: SunVTS would not come up with S7 4165796: vtsk hangs after taking a libthread panic 4181086: pmem test is not reading ce error info correctly 4191289: atmtest output "VC30 failed to rcv a packet" with SunATM 3.0 4148477: SUNWvts.nettest.8003 failures on back-to-back system configurations 4199391: sptest z FATAL: "Invalid device name 'z',..." 4201984: SunVTS dumps core on start via command or gui 4207208: pmem test can cause system panic 4207851: sunvts is detecting cdroms as IDE devices 4211740: sunvts atmtest does not work on a sheffield in external loopback mode 4220233: atmtest fails to receive a packet under heavy load 4227807: SunVTS 2.1.3 and 106387-03 is detecting SCSI cdrom as IDE device 4230733: socaltest 2.1.3 needs to turn off loopback after operation 4226927: SunVTS 2.1.3: patch 106810-01 cannot be applied if 106387-03 has been applied This rev fixed: 4342039: problem with SunVTS and the pmem test. 4257528: problem with system performance and SunVTS is initialize across a network. 4208149: the tty ui in SunVTS core dumps when selecting the fputest test_options submenu on some configurations. 4240072: vtstty would produce a core with entry to "cpudatest" and then the targeted cpu "Test_Parameter" or "Test_Execution" submenu. 4122829: vtsui disappears with no core. 4318966: SunVTS hangs or dies on large E10K configuration. 4157741: when SunVTS is installed with a different base directory from the default, the VTS GUI does not start. 4346984: tape test failed for Tandberg SLR tape drive. 4344099: vtstty processor affinity option fails to attach tests to processors. Patch Installation Instructions: -------------------------------- Refer to the Install.info file for instructions on using the generic 'installpatch' and 'backoutpatch' scripts provided with each patch. Any other special or non-generic installation instructions should be described below as special instructions. Special Install Instructions: ----------------------------- None. Special Instructions to run sptest on Ultra-4FT (Sheffield) platforms: ---------------------------------------------------------------------- This is extracted from the README.107135-02 file. The default option for sptest will fail potentially because the available port(a/b/c/d) changes dynamically. It is necessary for the user to manually select the correct "Test_Type" and the correct "Loopback_Type" for devices "se0" and "se2" under the Comm.Ports category on the user interface of SUNWvts. If an option selected is invalid, an error message will be displayed upon selecting "Apply." It is an important step to be followed when running sptest on Sheffield platform. User can also identify which ports are available by executing the utility /sbin/ttymuxadm. The output from this utility follows: # /sbin/ttymuxadm -i -1 A-CAF:0 20:2 /dev/term/c 3 (45:0 0) A-CAF:1 20:3 /dev/term/d 0 (-1:-1 0) B-CAF:0 20:0 /dev/term/a 2 (45:0 0) B-CAF:1 20:1 /dev/term/b 0 (-1:-1 0) A-CPU:0 -1:-1 /dev/term/ 0 (-1:-1 0) B-CPU:0 -1:-1 /dev/term/ 0 (-1:-1 0) # The port is avaiable only if the corresponding line is ended with (-1:-1 0). In this case, the user will select the following "Test Options" on the user interface: for both se0 and se2 Test_Type: b Loopback_Type: Internal_a_to_a__b_to_b or Test_Type: b Loopback_Type: Plug_a_to_a__b_to_b