[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-390
Subject:    Re: Suse failed boot after move to new DS8000
From:       Mike Walter <walterthepennyless () hotmail ! com>
Date:       2022-02-25 23:00:05
Message-ID: CY4PR0401MB35704FA6E9D8110983A86370CA3E9 () CY4PR0401MB3570 ! namprd04 ! prod ! outlook ! com
[Download RAW message or body]

> "
The restored system was being tested not on their current CPU, but the
one they have in their DR site. The invalid instruction is valid on
their production machine, but is invalid on their DR machine. Z114 vs Z10."

Gee... that brings back memories of the classic response: "I only changed this ONE \
card."  With that 'one card' being a punch card, but only one of the multiple cards \
that they also changed.

Mike Walter
-Retired-
________________________________
From: Linux on 390 Port <LINUX-390@VM.MARIST.EDU> on behalf of Tony Thigpen \
                <tony@vse2pdf.com>
Sent: Friday, February 25, 2022 3:21 PM
To: LINUX-390@VM.MARIST.EDU <LINUX-390@VM.MARIST.EDU>
Subject: Re: Suse failed boot after move to new DS8000

Mark,

Since I responded, I had him do a complete trace of the ipl until it
started looping. I have already reviewed the trace and found that not
long after IPL, there was an invalid instruction.

After asking more questions, I found out that he was doing something I
did not know about.

The restored system was being tested not on their current CPU, but the
one they have in their DR site. The invalid instruction is valid on
their production machine, but is invalid on their DR machine. Z114 vs Z10.

Sometimes I just want to reach though the phone lines and see if I can
relocate their head to a lower orifice.

Tony Thigpen

Mark Post wrote on 2/25/22 17:13:
> On 2/25/22 16:40, Tony Thigpen wrote:
> > Mark,
> > 
> > I did not think of tracing. Yes, it is in a tight loop. Here is a bit of
> > the log:
> > 
> > -> 00000000000039D0   STMG    EB0F02000024 >> 0000000000000200     CC 0
> > 00000000000039D6   AGHI    A7FBFF38    CC 1
> > 00000000000039DA   LARL    C0E0FFFFF9FB    CC 1
> > 00000000000039E0   BASR    0DEE     -> 0000000000002DD0     CC 1
> > -> 0000000000002DD0   STMG    EBDFF0880024 >> FFFFFFFFFB274FB8     CC 1
> > ** 0000000000002DD0       PROG    0005 -> 00000000000039D0
> > ADDRESSING
> > -> 00000000000039D0   STMG    EB0F02000024 >> 0000000000000200     CC 0
> > 00000000000039D6   AGHI    A7FBFF38    CC 1
> > 00000000000039DA   LARL    C0E0FFFFF9FB    CC 1
> > 00000000000039E0   BASR    0DEE     -> 0000000000002DD0     CC 1
> > -> 0000000000002DD0   STMG    EBDFF0880024 >> FFFFFFFFFB274EF0     CC 1
> > ** 0000000000002DD0       PROG    0005 -> 00000000000039D0
> > ADDRESSING
> > -> 00000000000039D0   STMG    EB0F02000024 >> 0000000000000200     CC 0
> > 00000000000039D6   AGHI    A7FBFF38    CC 1
> > 00000000000039DA   LARL    C0E0FFFFF9FB    CC 1
> > 00000000000039E0   BASR    0DEE     -> 0000000000002DD0     CC 1
> > -> 0000000000002DD0   STMG    EBDFF0880024 >> FFFFFFFFFB274E28     CC 1
> > ** 0000000000002DD0       PROG    0005 -> 00000000000039D0
> > ADDRESSING
> 
> Yeah, that's going to be a pain to debug. The System.map file in /boot
> would indicate what routine that's in, but after that it's most likely
> going to require a kernel expert to figure out. You can tell that the
> STMG instruction is trying to address what appears to be a negative (or
> extremely large) address and getting an addressing exception. But how it
> got there is a much bigger problem to figure out.
> 
> What version of SLES is this? What model machine is this running on? I'm
> assuming it's the same machine as before, and just the DASD was swapped
> out, but you never know.
> 
> 
> Mark Post
> 
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to LISTSERV@VM.MARIST.EDU with the message: INFO LINUX-390 or
> visit
> https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fh \
> tbin%2Fwlvindex%3FLINUX-390&amp;data=04%7C01%7C%7Cccb51049e505476be8ee08d9f8ad6c3e%7 \
> C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637814245993135936%7CUnknown%7CTWFpbGZsb \
> 3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=xhJFKRWappFlbnYv%2FPECJ3K3e2XrVWsnv23pxrVVJ%2BA%3D&amp;reserved=0
> 

----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to LISTSERV@VM.MARIST.EDU with the message: INFO LINUX-390 or visit
https://nam12.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww2.marist.edu%2Fhtb \
in%2Fwlvindex%3FLINUX-390&amp;data=04%7C01%7C%7Cccb51049e505476be8ee08d9f8ad6c3e%7C84d \
f9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637814245993135936%7CUnknown%7CTWFpbGZsb3d8eyJ \
WIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=xhJFKRWappFlbnYv%2FPECJ3K3e2XrVWsnv23pxrVVJ%2BA%3D&amp;reserved=0


----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to LISTSERV@VM.MARIST.EDU with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390


[prev in list] [next in list] [prev in thread] [next in thread]