On Thu, 2011-08-18 at 10:30 +0100, Don O'Malley wrote: > Hi Loris/All, > > Firstly, apologies that you found this out the hard way. I am in the > process of getting a README note added to this KU to warn customers of > the issue. > > This is a late breaking issue that we are currently investigating in > partnership with EMC. > The cause of this issue is that EMC PowerPath is using private > interfaces in Solaris, which Oracle have changed in the latest KU > deliverables. While it is not strictly an Oracle problem, we are doing > everything we can to find a good solution for our customers that use > EMC PowerPath. > > I will keep the PCA alias in the loop as I know more. Please bear with > us. > > Best, > -Don > > > On 18/08/11 09:50, [email protected] wrote: > > Just FYI, > > > > Installing kernel patch 144500-19 on a system with PowerPath will > > throw the box in a CPU panic boot loop. > > (learned this the hard way) > > > > https://forums.oracle.com/forums/thread.jspa?messageID=9792685 > > Hello,
We too had the above problem on our two T2000 servers. After booting a BAD TRAP loop involving module 'unix' occurred. Fortunately we could boot into failsafe mode, and then backout the kernel patch. However, we do not use EMC powerpath, but do use Falcon IPStor with DynaPath. As such I would draw peoples attention to the comment (https://forums.oracle.com/forums/thread.jspa?messageID=9792685): Problem is that PowerPath and possible other multipath vendors are using a Solaris private interface which is just that, private. and 'possible other multipath vendors'. So just because EMC is mentioned, don't think it is only EMC and won't affect you :-) John. -- John Horne, University of Plymouth, UK Tel: +44 (0)1752 587287 Fax: +44 (0)1752 587001
