Latest round of patches on fabric booted system causes Solaris 10 to hang

I have a fairly stock install of Solaris 10 6/06 on a T2000 which uses a Emulex HBA to boot from Xiotech SAN attached disks.

I installed the following patches:

118712 14 < 16 R-- 24 SunOS 5.10: Sun XVR-100 Graphics Accelerator Patch

120050 05 < 06 RS- 28 SunOS 5.10: usermod patch

120222 16 < 17 R-- 19 SunOS 5.10: Emulex-Sun LightPulse Fibre Channel Adapter driver

120629 02 < 08 R-- 24 SunOS 5.10: libpool patch

120824 08 < 09 R-- 39 SunOS 5.10: SunBlade T6300 & Sun Fire (T1000, T2000) platform patc

121118 11 < 12 R-- 21 SunOS 5.10: Sun Update Connection System Client 1.0.9

122660 08 < 09 R-- 17 SunOS 5.10: zones patch

124258 03 < 05 RS- 19 SunOS 5.10: ufs and nfs driver patch

124327 -- < 04 R-- 34 SunOS 5.10: libpcp patch

120222 16 < 17 R-- 19 SunOS 5.10: Emulex-Sun LightPulse Fibre Channel Adapter driver

When I rebooted the system it will no longer boot up.

If I do a {ok} boot -m milestone=none and attempt to start all the services by hand, I see:

svc:/platform/sun4u/mpxio-upgrade:default (Multipath upgrade)

State: offline since June 4, 2007 4:05:58 PM CDT

Reason: Start method is running.

See: http://sun.com/msg/SMF-8000-C4

See: man -M /usr/share/man -s 1M stmsboot

See: /etc/svc/volatile/platform-sun4u-mpxio-upgrade:default.log

It appears the mpxio-upgrade script is failing to start.

If I run /lib/svc/method/mpxio-upgrade by hand the script hangs and can not be killed. Since I am on console the only want to recover is to send-brk and reboot.I truss'ed it and the last device it was trying to read is:

82:open("/devices/pseudo/devinfo@0:devinfo", O_RDONLY) = 5

82:ioctl(5, 0xDF82, 0x00000000)= 57311

This is the second time this has happened in the last 2 months. The first time the problem was resolved with a new kernel patch. However Sun could not tell me what the exact problem was.

Has anyone else run into SAN/Fabric booted servers failing to boot after various patches?

[2096 byte] By [jemurraya] at [2007-11-27 6:30:40]
# 1

We have discovered the problem. It has nothing to do with SAN booting at all. It has to do with having a device plugged into the serial port. I was using this system to act as serial console for another device in the same rack. When the Sun kernel engineering asked me to unplug the serial cable and reboot I was skeptical, but it worked.

Sun has filed this as a bug. The only work around right now is to make sure you have nothing plugged into the serial port.

jemurraya at 2007-7-12 17:55:18 > top of Java-index,Solaris Operating System,Solaris 10 Features...