Equipment checks coming from DASD. It was something called a flapping link condition- whatever that means. Microcode patches to the z9 were required, but we were told it could happen on other processors as well (not that anyone here seemed to believe that ;).
Unfortunately, we didn't have the time to get the appropriate doc. What you should do is open a ticket with Novell and ask them what they need should it happen again. (my intentions too - too little time ...). Marcy Cortes This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Yu Safin Sent: Thursday, July 27, 2006 14:47 To: [email protected] Subject: Re: [LINUX-390] dasd over run messages On 7/27/06, Marcy Cortes <[EMAIL PROTECTED]> wrote: > Did you find any equipment checks on the VM console? We had a > situation were Linux didn't do well at all under equipment checks (some > looped, some hung, some crashed). I will ask the VM guy. He said that he could not see any messages but he was not specific about the console. When you talk about equipment checks, who is doing it? is it Linux or zVM? How can I do more trouble shooting? My Linux was locked, could not sign on even from the zVM user-id for my Linux. The indicate command was showing 100% cpu but nothing else out of the ordinary. > > > Marcy Cortes > > > This message may contain confidential and/or privileged information. If > you are not the addressee or authorized to receive this for the > addressee, you must not use, copy, disclose, or take any action based on > this message or any information herein. If you have received this > message in error, please advise the sender immediately by reply e-mail > and delete this message. Thank you for your cooperation." > > -----Original Message----- > From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Yu > Safin > Sent: Thursday, July 27, 2006 14:25 > To: [email protected] > Subject: [LINUX-390] dasd over run messages > > We are running zVM 5.2, SLES 9, Oracle 10.2 G and EMC/Symmetric. > > Our SLES reported the following errors. The two DASD volumes are > DEDICATED, we use LVM without striping on ext3 mounted points used by > Oracle. > > Jul 24 21:50:13 lnoaesd kernel: dasd_erp(3990): 0.0.2537: Overrun - > service overrun or overrun error requested by channel > Jul 24 21:50:13 lnoaesd kernel: dasd_erp(3990): 0.0.2532: Overrun - > service overrun or overrun error requested by channel > Jul 24 21:50:13 lnoaesd kernel: klogd 1.4.1, ---------- state change > ---------- > Jul 24 21:59:01 lnoaesd /USR/SBIN/CRON[16103]: (root) CMD ( rm -f > /var/spool/cron/lastrun/cron.hourly) > Jul 24 22:24:04 lnoaesd -- MARK -- > Jul 24 22:44:08 lnoaesd -- MARK -- > > > After those messages, the system went to 100% CPU and stayed there. > No more hourly cron jobs ran again and no one could log on so we had > to reboot after 12 hours of no activity (we did not notice that it was > not working, it is a test system). > > Last night (Jul 26), the system went to 100% CPU again but no dasd_erp > messages were reported and cron jobs stopped running. We had to > reboot again. > > Has anybody had any incidents with this type of configuration. > I could not find messages on the EMC console. > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
