Patch Name: PHKL_30376 Patch Description: s700_800 11.00 FXE perf, server patch, cumulative graphics Creation Date: 04/02/23 Post Date: 04/04/05 Hardware Platforms - OS Releases: s700: 11.00 s800: 11.00 Products: N/A Filesets: OS-Core.CORE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP ProgSupport.C-INC,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP OS-Core.KERN2-RUN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP Automatic Reboot?: Yes Status: General Release Critical: Yes PHKL_30376: PANIC PHKL_26406: CORRUPTION The defect only occurs on systems with future graphics devices supported by the gvid driver. PHKL_25100: PANIC HANG PHKL_22976: PANIC PHKL_22070: PANIC HANG PHKL_21272: PANIC HANG PHKL_20159: PANIC HANG PHKL_16981: PANIC Category Tags: defect_repair hardware_enablement enhancement general_release critical panic halts_system corruption Path Name: /hp-ux_patches/s700_800/11.X/PHKL_30376 Symptoms: PHKL_30376: ( SR:8606339780 CR:JAGaf00708 ) Data page fault panic with "gvid_cfg_rw" and "suser" in the panic stack backtrace. The panic only occurs with a PCI Fire GL-UX graphics device (A7789A) installed in the system. The stack backtrack resulting from this panic will look similar to: panic+0x14 report_trap_or_int_and_panic+0x84 interrupt+0x1d4 ihandler+0x928 suser+0x8 gvid_cfg_rw+0x44 gvid_cfg_cwrap+0x98 gvid_cmd+0x154 gvid_sti_cmd+0xb4 PHKL_26832: ( SR:8606239639 CR:JAGae08116 ) This product update is an enhancement to pre-enable support for hardware accelerated graphics on the hp FireGL-UX graphics device. PHKL_26406: ( SR:8606248131 CR:JAGae14531 ) Kernel memory corruption can occur on systems with PHKL_26191 or PHKL_25100 installed if one of the future graphics devices that those patches support is in use. This memory corruption normally occurs during system boot as the itemap(1M) command is executed. This corruption could result in incorrect behavior or a system panic. PHKL_26191: ( SR:5003433599 CR:JAGaa51474 ) The Internal Terminal Emulator (ITE) may use the same color for both text and background, resulting in an unreadable display, after the X server has run. Additionally, the graphics display will often turn yellow at the Command Line Login (ITE login). Both symptoms are usually experienced on multiprocessor systems when the X server is configured in 24-bit True Color mode. ( SR:8606234904 CR:JAGae04089 ) This product update is an enhancement to pre-enable support for the X Window System on future graphics devices. PHKL_25100: ( SR:8606220611 CR:JAGad89748 ) A new graphics driver is needed to provide graphics console support for future graphics products. This patch will pre- enable the graphics console support for these future products. If any of these future products are used as the system console without first installing the new driver, a panic or system hang could result during boot. PHKL_22976: ( SR:8606173681 CR:JAGad42938 ) Enhancements to the graphics driver can improve 3D graphics performance on workstations using VISUALIZE-FXE (A4982B) graphics. ( SR:8606165678 CR:JAGad34969 ) On 64 bit systems, the kernel may panic on servers (L3000 only known case) with a VISUALIZE-FXE graphics card installed. The associated stack resulting from this panic may look similar to: panic+0x14 hdl_pfault+0x660 pfault+0x104 trap+0x4ec nokgdb+0x8 PHKL_22070: (SR: 8606129269 CR: JAGac86815) During system initialization, if the first key press to the Internal Terminal Emulator (ITE) occurs when there is no active process running, the system can panic with a data page fault in the function graph_slot_info_init(). This panic hasn't been observed on 11.00 but would result in a stack trace very similar to the following captured from a 10.20 system. panic+0x10 report_trap_or_int_and_panic+0xe8 interrupt+0x458 $ihndlr_rtn+0x0 graph_slot_info_init+0x8 framebuf_itelock+0x54 g3_service+0x658 g3_service_ext+0x3c sti_save+0xe0 scroller+0x84 ite_filter+0xb28 ite_queue+0x38 kbd_map_keys+0x5b0 ps2_map_keys+0x84 ps2_kbd_parsefunc+0x138 ps2_proc+0x74 sw_service+0xcc (SR: 8606134617 CR: JAGad03752) Messages written to the ITE while running X on uniprocessor systems with a FXE graphics console will cause a ghost image of text to appear on the X desktop. (SR: 8606137904 CR: JAGad07065) On multiprocessor systems, a defect in the graphics driver could cause the graphics system to hang. No such hangs were discovered prior to release, but the potential for the defect to cause a hang would still exist in the absence of this patch. PHKL_21272: ( SR: 8606103040 DTS: JAGab69222) On C3000, J5000, and J7000 systems, defects in graphics system libraries and drivers could cause the system to panic with a high priority machine check (HPMC), rather than being recovered in software. No such defects were discovered prior to release, but the potential for a defect to cause a HPMC would still exist. ( SR: 8606128261 DTS: JAGac79061 ) The VISUALIZE-fxe graphics card was not supported under 64 bit HP-UX 11.00 on L-class systems. ( SR: 8606105554 DTS: JAGab73714 ) The graphics driver does not allow support of level 2 threads with OpenGL on VISUALIZE-FX graphics cards. If one thread performs a GCDMA_ALLOC and another thread performs a GCDMA_SET with the buffer allocated by the first thread, the VISUALIZE-FX hardware could hang. PHKL_20159: ( SR: 8606107507 DTS: JAGab77743 ) The new HP VISUALIZE-fxe graphics card was not supported in HP-UX 11.00. In addition, HCRX and VISUALIZE-48 graphics cards were not supported with 64 bit HP-UX 11.00. ( SR: 8606104451 DTS: JAGab71994) Systems with more than 2 processors could experience graphics subsystem hangs with VISUALIZE-FX graphics under extreme I/O interrupt loads. ( SR: 8606103444 DTS: JAGab14299 ) The GCSETMONTYPE and GCGETMONTYPE ioctl calls were not supported on C360, J280, J282, J2240 and all current D-Class systems. ( SR: 1653253286 DTS: JAGaa51465 ) Systems with VISUALIZE-EG graphics could display a diagnostic message of the form "sti_unpack_routines: patch_init returned 3for rom at 0xf8000000" during system boot. ( SR: 8606114783 DTS: JAGac29544 ) If a HP VISUALIZE-FX graphics card is installed in a C3000, J5000 or J7000 within a PCI slot that shared a PCI bus with any other installed PCI card, the graphics subsystem could hang under 64 bit HP-UX. PHKL_16981: The problem occurs on 64-bit kernel with graphics console. System panics with following stack traces when scrolling text up or down on the ITE. panic+0x14 report_trap_or_int_and_panic+0x80 trap+0x500 nokgdb+0x8 scr_bltf+0x30 scr_movef+0x94 scr_insert_line+0xe4 scroller+0x6f0 ite_pars+0x3dc ... Under some circumstances, functions "scr_movef" and "scr_bltf" may be "scr_moveb" and "scr_bltb". Defect Description: PHKL_30376: ( SR:8606339780 CR:JAGaf00708 ) In certain circumstances, the routine "gvid_cfg_rw" is called when handling an I/O interrupt. In this case, the "suser" routine must not be called as it relies on data which may not be present when the kernel is handling an interrupt. Resolution: The "suser" routine should only be called when "gvid_cfg_rw" is handling a user I/O request. The routine "gvid_cfg_rw" has been modified to no longer call "suser" during interrupt handling. PHKL_26832: ( SR:8606239639 CR:JAGae08116 ) This product update delivers minor enhancements required to support hardware accelerated graphics on the hp FireGL-UX graphics device. Resolution: The gvid graphics driver was enhanced to support hardware accelerated graphics on the hp FireGL-UX graphics device. PHKL_26406: ( SR:8606248131 CR:JAGae14531 ) The existing framebuf and new gvid drivers both operate on the same driver class, and share the same instance number space. If a device special file is created that contains the major number of the framebuf driver, and has the instance number of a device claimed by gvid, the framebuf driver file operations will be called. These framebuf routines will then incorrectly access the gvid data structures, as specified by the gvid device instance number. Since the gvid data structure is smaller than the framebuf structure, the framebuf open routine will modify kernel memory beyond the structure's end. During system boot, the itemap(1M) command will first try to open the framebuf driver device special file /dev/crt. If this fails, it will create temporary device special files in an attempt to locate and access a framebuf graphics device. These device special files will have the framebuf major number and a series of minor numbers with increasing instance numbers. If a future graphics device exists on the system, it is very likely that itemap(1M), in its search for a framebuf device, will create and open a device special file having a framebuf major number and the minor number that corresponds to a device claimed by the gvid driver. This will then cause the data corruption described above. Resolution: The framebuf driver open routine was modified to return ENODEV when it has been handed a non framebuf data structure due to a device special file having the wrong instance number. PHKL_26191: ( SR:5003433599 CR:JAGaa51474 ) When the X server terminates it will reset the graphics device. However on multiprocessor systems this could fail and leave the graphics display in an unknown state for the ITE. When the ITE starts, the customer may see a screen of red, or yellow, or blue on black fonts. Resolution: Allow for resets of the graphics card on multiprocessor systems when the X server is terminated. ( SR:8606234904 CR:JAGae04089 ) This product update delivers minor enhancements required to support the X Window System on future graphics devices in addition to a text only display. Resolution: The kernel component of the gvid graphics driver was enhanced to pre-enable support for the X Window System on future graphics devices. Future product updates will deliver the additional driver support necessary to fully enable the X Window System on future graphics devices. PHKL_25100: ( SR:8606220611 CR:JAGad89748 ) Future graphics products will require a new graphics driver for graphics console support on HP-UX. Resolution: This patch adds the new 'gvid' graphics driver and slightly modifies the Internal Terminal Emulator (ITE) to provide graphics console support for future graphics products. PHKL_22976: ( SR:8606173681 CR:JAGad42938 ) DMA performance on workstations can be tuned to better match the DMA characteristics of VISUALIZE-FXE (A4982B) graphics. Resolution: A routine was added to the graphics driver to optimize DMA performance on the the VISUALIZE-FXE card (A4982B). It does this by adjusting "hint" bits in the I/O controller that affect how DMA transactions are handled. ( SR:8606165678 CR:JAGad34969 ) The kernel panic is due to the kernel incorrectly mapping the card's I/O memory below the architected 32-bit IO space (addresses below 0xF0000000). Other processes which allocate large amounts of shared memory may overlap with this misplaced I/O memory and cause a protection fault in the kernel. Resolution: The graphics system was changed to call a modified macro, supplied in a separate patch to the VM system (PHKL_22975), which properly maps I/O addresses back into the 32-bit I/O space. PHKL_22070: (SR: 8606129269 CR: JAGac86815) The Internal Terminal Emulator (ITE) initializes a data structure at the first time it obtains the graphics lock after the system has booted. Information about the currently running process is logged to this data structure. If the ITE obtains the lock as the result of a keyboard key being pressed, and there is no active process, a data page fault can occur. This problem can only occur with the first key press, as the data structure is only initialized once. Resolution: Information about the currently running process is no longer logged to the ITE data structure mentioned above. (SR: 8606134617 CR: JAGad03752) FXE graphics cards were not included in a list of cards which supported the GCNOITE ioctl. The X server uses this ioctl on uniprocessor systems to prevent ITE messages from being overlayed on top of the X desktop. Resolution: FXE was added to the list of cards which support the GCNOITE ioctl. (SR: 8606137904 CR: JAGad07065) It was discovered the GCSTI_UTIL ioctl held a spinlock across a function call that could sleep. It is possible that this could deadlock the graphics driver. Resolution: The ioctl was restructured to prevent holding the lock across any functions that may sleep. PHKL_21272: ( SR: 8606103040 DTS: JAGab69222) There was a problem between an early version of the PCI bus adaptor and VISUALIZE-FX graphics cards. As a workaround to this problem, the BE timer on the graphics card was disabled. With the BE timer disabled, if defects in system graphics drivers or libraries placed the graphics card in a hung state, a high priority machine check (HPMC) panic would occur. This workaround is not necessary on later versions of this PCI bus adaptor. Resolution: If the PCI bus adaptor is of a later revision, the VISUALIZE-FX BE timer circuit is not disabled. In this case, defective graphics system software will not cause a HPMC panic and recovery from the error condition is possible. ( SR: 8606128261 DTS: JAGac79061 ) HP VISUALIZE-fxe graphics cards were not supported on L-class ssytems. The graphics driver was F-extending the base address of the PCI expansion ROM before mapping it into kernel I/O space. This caused problems on L-class systems running 64 bit kernels. The F-extension was unnecessary, as the call to map_mem_to_host() does the correct thing. Resolution: The VISUALIZE-fxe graphics card is now supported on L-class. ( SR: 8606105554 DTS: JAGab73714 ) GCDMA_ALLOC should be context specific and not thread specific. Resolution: The data structures were modified to allow DMA buffers allocated by one thread in a process to be shared with other threads in that process. Also, performance enhancements were made regarding graphics lock contention on multiprocessor systems. A "lock queue" scheme was implemented which will result in a more equitable sharing of the graphics lock. PHKL_20159: ( SR: 8606107507 DTS: JAGab77743 ) HP-UX 11.00 did not support the new HP VISUALIZE-fxe graphics card, and did not support HCRX and VISUALIZE-48 graphics cards with a 64 bit kernel. Resolution: With this patch, new functionality to support the HP VISUALIZE-fxe graphics card was added. 64 bit kernel support was also added for HCRX and VISUALIZE-48 graphics. ( SR: 8606104451 DTS: JAGab71994) On systems with more than two processors and under a heavy loading of I/O device interrupts, interrupts from HP VISUALIZE-FX graphics cards were not processed correctly by the graphics driver. Resolution: The graphics driver interrupt service routine was fixed. ( SR: 8606103444 DTS: JAGab14299 ) The GCSETMONTYPE and GCGETMONTYPE ioctl calls were not supported on C360, J280, J282, J2240, and D-class systems. Resolution: Support was added for the GCSETMONTYPE and GCGETMONTYPE ioctl calls on C360, J280, J282, J2240 and all current D-class systems. This will allow utility programs to change the monitor type value in stable storage. ( SR: 1653253286 DTS: JAGaa51465 ) The routine sti_patch_init was logging a diagnostic message which could be mistaken for an error message. Resolution: The routine sti_patch_init was corrected to prevent an unexpected message in syslog.log. ( SR: 8606114783 DTS: JAGac29544 ) On C3000, J5000, and J7000 systems, some PCI slots share the same PCI bus. If a VISUALIZE-FX graphics card shared a PCI bus with another PCI card, the graphics card would not be programmed to generate interrupts correctly under 64 bit HP-UX. Note that any slot labeled as a primary graphics slot on these systems does not share its PCI bus with any other slot, so a VISUALIZE-FX card installed into a primary graphics slot will not have suffered this problem. Resolution: The graphics driver was modified to correctly program a VISUALIZE-FX card to interrupt under 64 bit HP-UX when the card shares a PCI bus with another installed PCI card. PHKL_16981: The problem only occurs on 64-bit kernel with graphics console. To reproduce: - on non-window graphics-console - run vi /etc/rc - scroll one or two page forward - yank one line (yy) - move the cursor to middle of the screen - paste the line yanked above (p) - system panic with "data memory protection fault" with the stack trace below. panic+0x14 report_trap_or_int_and_panic+0x80 trap+0x500 nokgdb+0x8 scr_bltf+0x30 scr_movef+0x94 scr_insert_line+0xe4 scroller+0x6f0 ite_pars+0x3dc ... The functions scr_movef()/scr_moveb() were assuming 32-bit addresses, but 64-bit kernel can put the ITE structure up above 4GB. When this happens, the calculated addresses used in these functions are invalid. To resolve this problem, the pointer arithmetic in scr_movef()/scr_moveb() has been corrected to handle 64-bit addresses properly. Enhancement: No (superseded patches contained enhancements) PHKL_30376: Enhancements were delivered in a patch this one has superseded. Please review the Defect Description text for more information. SR: 1653253286 1653284273 5003433599 8606103040 8606103444 8606104451 8606105554 8606107507 8606114783 8606128261 8606129269 8606134617 8606137904 8606165678 8606173681 8606220611 8606234904 8606239639 8606248131 8606339780 Patch Files: OS-Core.CORE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP: /usr/conf/graf/gpu_data.h /usr/conf/graf/graph02.h /usr/conf/graf/graph3.h /usr/conf/graf/ite.h /usr/conf/graf/ite1_spc.h /usr/conf/graf/ite_color.h /usr/conf/graf/kbd.h /usr/conf/graf/stirom.h /usr/conf/h/framebuf.h ProgSupport.C-INC,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP: /usr/include/sio/graph02.h /usr/include/sys/framebuf.h OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP: /usr/conf/lib/libhp-ux.a(framebuf.o) /usr/conf/lib/libhp-ux.a(graf.o) /usr/conf/lib/libhp-ux.a(graph3.o) /usr/conf/lib/libhp-ux.a(ite.o) /usr/conf/lib/libhp-ux.a(ite1.o) /usr/conf/lib/libhp-ux.a(ite1_sti.o) /usr/conf/lib/libhp-ux.a(ite_color.o) /usr/conf/lib/libhp-ux.a(ite_parse.o) /usr/conf/lib/libhp-ux.a(ite_scroll.o) /usr/conf/lib/libhp-ux.a(kbd_code.o) /usr/conf/lib/libhp-ux.a(sti_hcrx.o) /usr/conf/lib/libhp-ux.a(sti_vis48.o) /usr/conf/lib/libhp-ux.a(sti_viseg.o) /usr/conf/lib/libhp-ux.a(sti_visfx.o) /usr/conf/lib/libhp-ux.a(stilink.o) /usr/conf/lib/libhp-ux.a(stirom.o) OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: /usr/conf/lib/libhp-ux.a(framebuf.o) /usr/conf/lib/libhp-ux.a(graf.o) /usr/conf/lib/libhp-ux.a(graph3.o) /usr/conf/lib/libhp-ux.a(graphics_hooks.o) /usr/conf/lib/libhp-ux.a(gvid.o) /usr/conf/lib/libhp-ux.a(gvid_buf.o) /usr/conf/lib/libhp-ux.a(gvid_debug.o) /usr/conf/lib/libhp-ux.a(gvid_sti.o) /usr/conf/lib/libhp-ux.a(ite.o) /usr/conf/lib/libhp-ux.a(ite1.o) /usr/conf/lib/libhp-ux.a(ite1_sti.o) /usr/conf/lib/libhp-ux.a(ite_color.o) /usr/conf/lib/libhp-ux.a(ite_parse.o) /usr/conf/lib/libhp-ux.a(ite_scroll.o) /usr/conf/lib/libhp-ux.a(kbd_code.o) /usr/conf/lib/libhp-ux.a(sti_hcrx.o) /usr/conf/lib/libhp-ux.a(sti_vis48.o) /usr/conf/lib/libhp-ux.a(sti_viseg.o) /usr/conf/lib/libhp-ux.a(sti_visfx.o) /usr/conf/lib/libhp-ux.a(stilink.o) /usr/conf/lib/libhp-ux.a(stirom.o) OS-Core.KERN2-RUN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: /usr/conf/master.d/gvid what(1) Output: OS-Core.CORE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP: /usr/conf/graf/gpu_data.h: gpu_data.h $Date: 2002/02/04 17:02:06 $Revision: r11 ros/8 PATCH_11.00 (PHKL_26191) */ /usr/conf/graf/graph02.h: graph02.h $Date: 1999/10/22 16:07:25 $Revision: r11r os/1 PATCH_11.00 (PHKL_20159) /usr/conf/graf/graph3.h: graph3.h $Date: 2002/05/01 12:57:22 $Revision: r11ro s/5 PATCH_11.00 (PHKL_26832) */ /usr/conf/graf/ite.h: ite.h $Date: 2002/02/04 17:02:06 $Revision: r11ros/5 PATCH_11.00 (PHKL_26191) */ /usr/conf/graf/ite1_spc.h: ite1_spc.h $Date: 1999/10/22 16:07:25 $Revision: r11 ros/1 PATCH_11.00 (PHKL_20159) /usr/conf/graf/ite_color.h: ite_color.h $Date: 1999/10/22 16:07:25 $Revision: r1 1ros/1 PATCH_11.00 (PHKL_20159) /usr/conf/graf/kbd.h: kbd.h $Date: 1999/10/22 16:07:25 $Revision: r11ros/1 PATCH_11.00 (PHKL_20159) /usr/conf/graf/stirom.h: stirom.h $Date: 2001/10/08 17:20:10 $Revision: r11ro s/8 PATCH_11.00 (PHKL_25100) */ /usr/conf/h/framebuf.h: framebuf.h $Date: 2001/03/09 13:45:10 $Revision: r11 ros/3 PATCH_11.00 (PHKL_22976) ProgSupport.C-INC,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP: /usr/include/sio/graph02.h: graph02.h $Date: 1999/10/22 16:07:25 $Revision: r11r os/1 PATCH_11.00 (PHKL_20159) /usr/include/sys/framebuf.h: framebuf.h $Date: 2001/03/09 13:45:10 $Revision: r11 ros/3 PATCH_11.00 (PHKL_22976) OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP: /usr/conf/lib/libhp-ux.a(framebuf.o): framebuf.c $Date: 2002/05/01 12:57:22 $Revision: r11 ros/15 PATCH_11.00 (PHKL_26832) /usr/conf/lib/libhp-ux.a(graf.o): graf.c $Date: 2002/05/01 12:57:22 $Revision: r11ros/ 2 PATCH_11.00 (PHKL_26832) /usr/conf/lib/libhp-ux.a(graph3.o): graph3.c $Date: 2002/05/01 12:57:22 $Revision: r11ro s/13 PATCH_11.00 (PHKL_26832) /usr/conf/lib/libhp-ux.a(ite.o): ite.c $Date: 2002/02/04 17:02:06 $Revision: r11ros/3 PATCH_11.00 (PHKL_26191) /usr/conf/lib/libhp-ux.a(ite1.o): ite1.c $Date: 2002/02/04 17:02:06 $Revision: r11ros/ 8 PATCH_11.00 (PHKL_26191) /usr/conf/lib/libhp-ux.a(ite1_sti.o): ite1_sti.c $Date: 2001/10/08 17:04:40 $Revision: r11 ros/4 PATCH_11.00 (PHKL_25100) /usr/conf/lib/libhp-ux.a(ite_color.o): ite_color.c $Date: 1999/10/22 16:07:25 $Revision: r1 1ros/1 PATCH_11.00 (PHKL_20159) /usr/conf/lib/libhp-ux.a(ite_parse.o): ite_parse.c $Date: 1999/10/22 16:07:25 $Revision: r1 1ros/1 PATCH_11.00 (PHKL_20159) /usr/conf/lib/libhp-ux.a(ite_scroll.o): ite_scroll.c $Date: 1999/10/22 16:07:25 $Revision: r 11ros/2 PATCH_11.00 (PHKL_20159) /usr/conf/lib/libhp-ux.a(kbd_code.o): kbd_code.c $Date: 1999/10/22 16:07:25 $Revision: r11 ros/1 PATCH_11.00 (PHKL_20159) /usr/conf/lib/libhp-ux.a(sti_hcrx.o): sti_hcrx.c $Date: 1999/10/22 16:07:25 $Revision: r11 ros/1 PATCH_11.00 (PHKL_20159) /usr/conf/lib/libhp-ux.a(sti_vis48.o): sti_vis48.c $Date: 1999/10/22 16:07:25 $Revision: r1 1ros/1 PATCH_11.00 (PHKL_20159) /usr/conf/lib/libhp-ux.a(sti_viseg.o): sti_viseg.c $Date: 1999/10/22 16:07:25 $Revision: r1 1ros/1 PATCH_11.00 (PHKL_20159) /usr/conf/lib/libhp-ux.a(sti_visfx.o): sti_visfx.c $Date: 1999/10/22 16:07:25 $Revision: r1 1ros/1 PATCH_11.00 (PHKL_20159) /usr/conf/lib/libhp-ux.a(stilink.o): stilink.c $Date: 1999/10/22 16:07:25 $Revision: r11r os/1 PATCH_11.00 (PHKL_20159) /usr/conf/lib/libhp-ux.a(stirom.o): stirom.c $Date: 2001/10/08 17:01:49 $Revision: r11ro s/9 PATCH_11.00 (PHKL_25100) OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: /usr/conf/lib/libhp-ux.a(framebuf.o): framebuf.c $Date: 2002/05/01 12:57:22 $Revision: r11 ros/15 PATCH_11.00 (PHKL_26832) /usr/conf/lib/libhp-ux.a(graf.o): graf.c $Date: 2002/05/01 12:57:22 $Revision: r11ros/ 2 PATCH_11.00 (PHKL_26832) /usr/conf/lib/libhp-ux.a(graph3.o): graph3.c $Date: 2002/05/01 12:57:22 $Revision: r11ro s/13 PATCH_11.00 (PHKL_26832) /usr/conf/lib/libhp-ux.a(graphics_hooks.o): graphics_hooks.c $Date: 2002/05/01 12:57:22 $Revisio n: r11ros/2 PATCH_11.00 (PHKL_26832) /usr/conf/lib/libhp-ux.a(gvid.o): gvid.c $Date: 2004/01/27 15:45:39 $Revision: r11ros/ 4 PATCH_11.00 (PHKL_30376) /usr/conf/lib/libhp-ux.a(gvid_buf.o): gvid_buf.c $Date: 2002/05/01 12:57:22 $Revision: r11 ros/1 PATCH_11.00 (PHKL_26832) /usr/conf/lib/libhp-ux.a(gvid_debug.o): gvid_debug.c $Date: 2002/05/01 12:57:22 $Revision: r 11ros/2 PATCH_11.00 (PHKL_26832) /usr/conf/lib/libhp-ux.a(gvid_sti.o): gvid_sti.c $Date: 2001/10/08 17:08:11 $Revision: r11 ros/1 PATCH_11.00 (PHKL_25100) /usr/conf/lib/libhp-ux.a(ite.o): ite.c $Date: 2002/02/04 17:02:06 $Revision: r11ros/3 PATCH_11.00 (PHKL_26191) /usr/conf/lib/libhp-ux.a(ite1.o): ite1.c $Date: 2002/02/04 17:02:06 $Revision: r11ros/ 8 PATCH_11.00 (PHKL_26191) /usr/conf/lib/libhp-ux.a(ite1_sti.o): ite1_sti.c $Date: 2001/10/08 17:04:40 $Revision: r11 ros/4 PATCH_11.00 (PHKL_25100) /usr/conf/lib/libhp-ux.a(ite_color.o): ite_color.c $Date: 1999/10/22 16:07:25 $Revision: r1 1ros/1 PATCH_11.00 (PHKL_20159) /usr/conf/lib/libhp-ux.a(ite_parse.o): ite_parse.c $Date: 1999/10/22 16:07:25 $Revision: r1 1ros/1 PATCH_11.00 (PHKL_20159) /usr/conf/lib/libhp-ux.a(ite_scroll.o): ite_scroll.c $Date: 1999/10/22 16:07:25 $Revision: r 11ros/2 PATCH_11.00 (PHKL_20159) /usr/conf/lib/libhp-ux.a(kbd_code.o): kbd_code.c $Date: 1999/10/22 16:07:25 $Revision: r11 ros/1 PATCH_11.00 (PHKL_20159) /usr/conf/lib/libhp-ux.a(sti_hcrx.o): sti_hcrx.c $Date: 1999/10/22 16:07:25 $Revision: r11 ros/1 PATCH_11.00 (PHKL_20159) /usr/conf/lib/libhp-ux.a(sti_vis48.o): sti_vis48.c $Date: 1999/10/22 16:07:25 $Revision: r1 1ros/1 PATCH_11.00 (PHKL_20159) /usr/conf/lib/libhp-ux.a(sti_viseg.o): sti_viseg.c $Date: 1999/10/22 16:07:25 $Revision: r1 1ros/1 PATCH_11.00 (PHKL_20159) /usr/conf/lib/libhp-ux.a(sti_visfx.o): sti_visfx.c $Date: 1999/10/22 16:07:25 $Revision: r1 1ros/1 PATCH_11.00 (PHKL_20159) /usr/conf/lib/libhp-ux.a(stilink.o): stilink.c $Date: 1999/10/22 16:07:25 $Revision: r11r os/1 PATCH_11.00 (PHKL_20159) /usr/conf/lib/libhp-ux.a(stirom.o): stirom.c $Date: 2001/10/08 17:01:49 $Revision: r11ro s/9 PATCH_11.00 (PHKL_25100) OS-Core.KERN2-RUN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: /usr/conf/master.d/gvid: gvid $Date: 2001/10/08 17:27:40 $Revision: r11ros/1 PATCH_11.00 (PHKL_25100) cksum(1) Output: OS-Core.CORE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP: 2039293370 24926 /usr/conf/graf/gpu_data.h 1712270522 9214 /usr/conf/graf/graph02.h 1613750557 10022 /usr/conf/graf/graph3.h 2250176327 25318 /usr/conf/graf/ite.h 1382527106 1720 /usr/conf/graf/ite1_spc.h 635222961 2333 /usr/conf/graf/ite_color.h 355247326 30054 /usr/conf/graf/kbd.h 1154056765 44705 /usr/conf/graf/stirom.h 3699383047 26602 /usr/conf/h/framebuf.h ProgSupport.C-INC,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP: 1712270522 9214 /usr/include/sio/graph02.h 3699383047 26602 /usr/include/sys/framebuf.h OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP: 1943552596 73532 /usr/conf/lib/libhp-ux.a(framebuf.o) 919790407 265908 /usr/conf/lib/libhp-ux.a(graf.o) 748124996 47008 /usr/conf/lib/libhp-ux.a(graph3.o) 3406357438 18388 /usr/conf/lib/libhp-ux.a(ite.o) 1891724513 12884 /usr/conf/lib/libhp-ux.a(ite1.o) 2168993812 9260 /usr/conf/lib/libhp-ux.a(ite1_sti.o) 1694810833 2292 /usr/conf/lib/libhp-ux.a(ite_color.o) 2478482782 14016 /usr/conf/lib/libhp-ux.a(ite_parse.o) 382863799 44164 /usr/conf/lib/libhp-ux.a(ite_scroll.o) 1034929352 14372 /usr/conf/lib/libhp-ux.a(kbd_code.o) 402549901 888 /usr/conf/lib/libhp-ux.a(sti_hcrx.o) 735038505 888 /usr/conf/lib/libhp-ux.a(sti_vis48.o) 33058837 888 /usr/conf/lib/libhp-ux.a(sti_viseg.o) 1842828339 23696 /usr/conf/lib/libhp-ux.a(sti_visfx.o) 1179499036 840 /usr/conf/lib/libhp-ux.a(stilink.o) 2752592662 22416 /usr/conf/lib/libhp-ux.a(stirom.o) OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: 1987153423 169384 /usr/conf/lib/libhp-ux.a(framebuf.o) 1573118890 257424 /usr/conf/lib/libhp-ux.a(graf.o) 2003618278 112744 /usr/conf/lib/libhp-ux.a(graph3.o) 3505738446 19176 /usr/conf/lib/libhp-ux.a(graphics_hooks.o) 223273821 222008 /usr/conf/lib/libhp-ux.a(gvid.o) 3879440988 47968 /usr/conf/lib/libhp-ux.a(gvid_buf.o) 3825694178 160672 /usr/conf/lib/libhp-ux.a(gvid_debug.o) 667015847 9312 /usr/conf/lib/libhp-ux.a(gvid_sti.o) 2820160801 40728 /usr/conf/lib/libhp-ux.a(ite.o) 853508686 24176 /usr/conf/lib/libhp-ux.a(ite1.o) 252335516 19824 /usr/conf/lib/libhp-ux.a(ite1_sti.o) 2866063132 4976 /usr/conf/lib/libhp-ux.a(ite_color.o) 4103479389 28632 /usr/conf/lib/libhp-ux.a(ite_parse.o) 3984635619 92104 /usr/conf/lib/libhp-ux.a(ite_scroll.o) 3206948662 24392 /usr/conf/lib/libhp-ux.a(kbd_code.o) 3569065512 33792 /usr/conf/lib/libhp-ux.a(sti_hcrx.o) 1844001726 49832 /usr/conf/lib/libhp-ux.a(sti_vis48.o) 3875853673 45560 /usr/conf/lib/libhp-ux.a(sti_viseg.o) 1036634595 90056 /usr/conf/lib/libhp-ux.a(sti_visfx.o) 1961096219 1624 /usr/conf/lib/libhp-ux.a(stilink.o) 1024478307 37624 /usr/conf/lib/libhp-ux.a(stirom.o) OS-Core.KERN2-RUN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: 1890497891 4317 /usr/conf/master.d/gvid Patch Conflicts: None Patch Dependencies: s700: 11.00: PHKL_18543 PHKL_21532 PHKL_22975 PHKL_26737 s800: 11.00: PHKL_18543 PHKL_21532 PHKL_22975 PHKL_26737 Hardware Dependencies: None Other Dependencies: None Supersedes: PHKL_16981 PHKL_26832 PHKL_26406 PHKL_26191 PHKL_25100 PHKL_22976 PHKL_22070 PHKL_21272 PHKL_20159 Equivalent Patches: PHKL_30369: s700: 11.11 s800: 11.11 Patch Package Size: 870 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHKL_30376 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHKL_30376.depot By default swinstall will archive the original software in /var/adm/sw/save/PHKL_30376. If you do not wish to retain a copy of the original software, include the patch_save_files option in the swinstall command above: -x patch_save_files=false WARNING: If patch_save_files is false when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. For future reference, the contents of the PHKL_30376.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHKL_30376.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHKL_30376.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: PHKL_22976: This patch depends on a second patch, PHKL_22975, to fix a panic on L3000 systems. This defect only affects a specific set of customers (L3000), and other customers need not install patch PHKL_22975. Both patches may be installed in any order, or together, if desired.