IV48687: SYSTEM CAN HANG IN CASE OF MULTIPLE IO TO USB DEVICES 14/02/20 PTF PECHANGE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• System may hang incase of multiple raw io to USB devices
  
  
                         When raw multiple io is  done in USB
  device, the system can crash with following stack trace.
  4)> f
  pvthread+014C00 STACK:
  [00022080]abend_trap+000000 ()
  [005982AC]slock+00054C (??, ??)
  [00009558].simple_lock+000058 ()
  [0661CDE8]usbcd:raw_io_multiple+0002C8 (??, ??, ??)
  [0661C388]usbcd:mstor_rdwr+000348 (??, ??, ??, ??, ??)
  [0661A294]usbcd:mstor_write+0000F4 (??, ??, ??, ??)
  [005BB524]rdevwrite+0001C4 (??, ??, ??, ??, ??)
  [0083CBA4]cdev_rdwr+000224 (??, ??, ??, ??, ??, ??, ??, ??)
  [007AF9A0]spec_erdwr+0001C0 (??, ??, ??, ??, ??, ??, ??, ??)
  [007AFA44]spec_rdwr+000024 (??, ??, ??, ??, ??, ??, ??, ??)
  [005E8CF8]vnop_rdwr+0001B8 (??, ??, ??, ??, ??, ??, ??, ??)
  [006012F4]vno_rw+0000B4 (??, ??, ??, ??, ??)
  [005ADAC8]rwuio+000108 (??, ??, ??, ??, ??, ??)
  [005ADDE8]rdwr+000188 (??, ??, ??, ??, ??, ??)
  [005AD590]kewrite+000150 (??, ??, ??, ??)
  [000038A4]mfspurr_sc_flih01+0000E4 ()
  [kdb_get_virtual_memory] no real storage @ 2FF1DD88
  [D011FE00]D011FE00 ()
  [kdb_read_mem] no real storage @ FFFFFFFFFFF8D80
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:
  * Systems running the 6100-07 Technology Level with the
  * devices.usbif.08025002.rte fileset at the 6.1.7.15 through
  * 6.1.7.20 levels.
  ****************************************************************
  * PROBLEM DESCRIPTION:
  * System may hang incase of multiple raw io to USB devices
  *                        When raw multiple io is  done in USB
  * device, the system can crash with following stack trace.
  * 4)> f
  * pvthread+014C00 STACK:
  *  00022080 abend_trap+000000 ()
  *  005982AC slock+00054C (??, ??)
  *  00009558 .simple_lock+000058 ()
  *  0661CDE8 usbcd:raw_io_multiple+0002C8 (??, ??, ??)
  *  0661C388 usbcd:mstor_rdwr+000348 (??, ??, ??, ??, ??)
  *  0661A294 usbcd:mstor_write+0000F4 (??, ??, ??, ??)
  *  005BB524 rdevwrite+0001C4 (??, ??, ??, ??, ??)
  *  0083CBA4 cdev_rdwr+000224 (??, ??, ??, ??, ??, ??, ??, ??)
  *  007AF9A0 spec_erdwr+0001C0 (??, ??, ??, ??, ??, ??, ??, ??)
  *  007AFA44 spec_rdwr+000024 (??, ??, ??, ??, ??, ??, ??, ??)
  *  005E8CF8 vnop_rdwr+0001B8 (??, ??, ??, ??, ??, ??, ??, ??)
  *  006012F4 vno_rw+0000B4 (??, ??, ??, ??, ??)
  *  005ADAC8 rwuio+000108 (??, ??, ??, ??, ??, ??)
  *  005ADDE8 rdwr+000188 (??, ??, ??, ??, ??, ??)
  *  005AD590 kewrite+000150 (??, ??, ??, ??)
  *  000038A4 mfspurr_sc_flih01+0000E4 ()
  *  kdb_get_virtual_memory  no real storage @ 2FF1DD88
  *  D011FE00 D011FE00 ()
  *  kdb_read_mem  no real storage @ FFFFFFFFFFF8D80
  ****************************************************************
  * RECOMMENDATION:
  * Install APAR IV48687.
  ****************************************************************
  

Problem conclusion

• Fixed the problem by releasing the lock acquired in process.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  IV45342

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  AIX 610 STD EDI

• Fixed component ID

  5765G6200

Applicable component levels

• R610 PSY U859854

     UP14/02/17 I 1000

PTF to Fileset Mapping

• U859854 devices.usbif.08025002.rte 6.1.7.21