I've seen a similar problem when the boot archive was not updated prior to 
reboot.  If this was being patched on a liveupgrade created ABE then the boot 
archive on the ABE must be updated prior to booting.

/sbin/bootadm update-archive 

This generally occurs when a server that never had the boot archive was patched 
to a kernel level that introduce the boot archive and it hasn't' been updated.

-----Original Message-----
From: pca-boun...@lists.univie.ac.at [mailto:pca-boun...@lists.univie.ac.at] On 
Behalf Of Martin Paul
Sent: Tuesday, October 05, 2010 10:02 AM
To: PCA (Patch Check Advanced) Discussion
Subject: [pca] Kernel Patch 141444-09 and undefined symbols

A PCA user reported problems with kernel patch 141444-09 and "undefined symbol" 
errors on reboot after patch installation. The problem seems to be reproducible:

# patchadd 141444-09
# init 6
...
SunOS Release 5.10 Version Generic_141444-09 64-bit Copyright 1983-2009 Sun 
Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
/kernel/drv/sparcv9/usbsprl: undefined symbol 'usb_lookup_ep_data'
/kernel/drv/sparcv9/usbsprl: undefined symbol 'usb_dprintf0'
/kernel/drv/sparcv9/usbsprl: undefined symbol 'usb_dprintf2'
/kernel/drv/sparcv9/usbsprl: undefined symbol 'usb_pipe_ctrl_xfer_wait'
/kernel/drv/sparcv9/usbsprl: undefined symbol 'usbser_close'
/kernel/drv/sparcv9/usbsprl: undefined symbol 'usbser_power'
/kernel/drv/sparcv9/usbsprl: undefined symbol 'usbser_getinfo'
/kernel/drv/sparcv9/usbsprl: undefined symbol 'usb_pipe_close'
/kernel/drv/sparcv9/usbsprl: undefined symbol 'usb_unregister_event_cbs'
/kernel/drv/sparcv9/usbsprl: undefined symbol 'usb_pipe_bulk_xfer'
/kernel/drv/sparcv9/usbsprl: undefined symbol 'usb_free_bulk_req'
/kernel/drv/sparcv9/usbsprl: undefined symbol 'usb_register_event_cbs'
/kernel/drv/sparcv9/usbsprl: undefined symbol 'usb_free_log_hdl'
/kernel/drv/sparcv9/usbsprl: undefined symbol 'usbser_attach'
...

I couldn't find this problem mentioned on SunSolve or Google. Maybe one of you 
has seen it before?

Martin.


Reply via email to