Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!paperboy!hsdndev!rutgers!mcnc!ncsuvx!news From: henkel%nepjt@ncsuvx.ncsu.edu (Chuck Henkel) Newsgroups: comp.unix.aix Subject: Re: Flaky behavior after installing 3002 upgrade Message-ID: Date: 17 Jan 91 22:49:43 GMT References: <127@edi386.UUCP> <3149.276bd842@miavx1.acs.muohio.edu> Sender: news@ncsuvx.ncsu.edu (USENET News System) Reply-To: henkel@nepjt.ncsu.edu (Chuck Henkel) Organization: North Carolina State University, Raleigh Lines: 60 In-reply-to: pemurray@miavx1.acs.muohio.edu's message of 17 Dec 90 01:25:38 GMT In article <3149.276bd842@miavx1.acs.muohio.edu> pemurray@miavx1.acs.muohio.edu (Peter Murray) writes: > We're running the "September Update" (that's 3001, isn't it?) and we see > the machine crashing with the 102 300 0c0 message. We happened to narrow > it down to a MS-DOS file being served to a PC over NFS (and it's > reproducable), but IBM hasn't come up to look at it yet. Here's what IBM came up with re my original problem with machine crashing when I invoke dbx: It turned out that I had a hardware bug on the sysplanar0 board. This was discovered by examining the output of the lscfg command: % lscfg -v | head -30 INSTALLED RESOURCE LIST WITH VPD The following resources are installed on your machine. sysunit0 00-00 RISC System/6000 System Unit sysplanar0 00-00 CPU Planar Part Number.................81F7774 EC Level....................2604441 Processor Identification....00015223 ROS Level and ID............IPLVER0.0 LVL0.00,81F7775 Processor Component ID......0000003100000031 Device Specific.(Z0)........01250B Device Specific.(Z1)........02FF02 Device Specific.(Z2)........032001 Device Specific.(Z3)........042104 Device Specific.(Z4)........1D2006 Device Specific.(Z5)........FFFFFF Device Specific.(Z6)........0A3005 Device Specific.(Z7)........2A3005 Device Specific.(Z8)........FFFFFF Device Specific.(Z9)........FFFFFF ROS Level and ID............OCS(05000000) ROS Level and ID............SEEDS(05000000) The line: Device Specific.(Z1)........02FF02 ^^^^ apparently means that hardware component "02" is at firmware revision "FF", but the highest revision level is only supposed to be "21", so this suggested to the IBMer in Austin that I had a hardware problem in the planar. So I called 1-800-IBM-SERV and arranged for a service guy to come out and replace the board. He agreed to come out the next day only after I insisted that, no, immediately wasn't a good time for me. _Chuck -- | Chuck Henkel | | | Department of Nuclear Engineering | Your tax dollars at work. | | N.C. State University | | | henkel%nepjt@ncsuvx.ncsu.edu | |