Re: SLES10 Abend During Install
"Post, Mark K" <[EMAIL PROTECTED]> wrote on 01.08.2006 19:20:36: > I have a z/VM 4.4 64-bit guest on a z900 that I'm trying to install > SLES10 GA on. Things seem to go along fine, until I SSH in and start > YaST. At that point, I get a the following messages on my terminal, > followed by a kernel panic on the z/VM console: [...} A similar symptom has been seen during SLES10 beta testing. The source of the problem has been tracked to z/VM, resulting in the following addition to the release notes file: == Patches required for SLES 10 on z/VM If SLES 10 should should run on z/VM it is required that the following APARs and patches are installed: * VM63771 o z/VM 4.4 UM31479 o z/VM 5.1 UM31501 == See also: http://www-1.ibm.com/support/docview.wss?uid=isg1VM63771 Does this apply to your system? Regards, Peter Oberparleiter -- Peter Oberparleiter Linux on zSeries Development IBM Development Lab, Boeblingen/Germany -- 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
Re: SLES10 Abend During Install
On Tuesday 01 August 2006 19:20, Post, Mark K wrote: > I have a z/VM 4.4 64-bit guest on a z900 that I'm trying to install > SLES10 GA on. Things seem to go along fine, until I SSH in and start > YaST. At that point, I get a the following messages on my terminal, > followed by a kernel panic on the z/VM console: [...] > *** Preparing SSH installation for reboot *** [...] > Krnl PSW : 070420018000 0002 (0x2) [...] > ([<00259434>] mpage_writepages+0x23c/0xb40) > [<001b07ca>] do_writepages+0x5a/0x74 > [<00256a8c>] sync_inodes+0x540/0x1204 > [<001fdad4>] sys_sync+0x30/0x84 > [<0010f774>] sysc_noemu+0x10/0x16 > [<021464aa>] 0x21464aa > Q CPLEVEL > z/VM Version 4 Release 4.0, service level 0403 (64-bit) > Generated at 11/19/04 15:43:15 CDT > IPL at 04/09/06 04:13:05 CDT This problem looks like it will disappear when you install APAR VM63771 Release 440 : UM31479 available 05/11/09 (0601 ) Release 510 : UM31501 available 05/11/09 (5105 ). Without that PTF, z/VM sometimes sets the changed bit when it moves a page from DPA to XST and back(overidication). This is normally not a problem, as Linux calls the writepage function for that page and write the page back. Problem is, the root file system of the installer is cramfs, which is readonly and, therefore, no writepage function is available. If the problem still appears with the PTF feel free to open a problem report. -- Mit freundlichen Grüßen / Best Regards Christian Borntraeger Linux Software Engineer zSeries Linux & Virtualization -- 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
Re: SLES10 Abend During Install
Post, Mark K wrote: > illegal operation: 0001 [#1] > CPU:0Not tainted > Process init (pid: 1, task: 007c1748, ksp: 007c3ca0) > Krnl PSW : 070420018000 0002 (0x2) > Krnl GPRS: 0001 03cdb2a8 > 0085 >007c3cf0 0001 010c6160 > 0001 >03cdb3c8 000a3898 03cdb3c8 > >0085 00446888 0025970c > 007c3b38 > Krnl Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 > Call Trace: > ([<00259434>] mpage_writepages+0x23c/0xb40) > [<001b07ca>] do_writepages+0x5a/0x74 > [<00256a8c>] sync_inodes+0x540/0x1204 > [<001fdad4>] sys_sync+0x30/0x84 > [<0010f774>] sysc_noemu+0x10/0x16 > [<021464aa>] 0x21464aa > > <0>Kernel panic - not syncing: Attempted to kill init! > HCPGIR450W CP entered; disabled wait PSW 00020001 8000 > 0014259E *Ouch*. In mpage_writepages()? This is pretty much in the very core kernel near I/O page cache and file system, not somewhere near networking. Both CTC device driver and all user space components like Yast avert suspicion as far as I can tell. Is there another message right before "illegal operation: 0001 [#1]"? Probably one that says "kernel BUG" or "Ooops" or similar? Usually kernel traps use illegal opcodes to crash the thing on purpose, but they are supposed to print a useful message before that. cheers, Carsten -- 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
Re: SLES10 Abend During Install
I didn't say so, but it also happened before with 512M defined. As it turns out, the problem was related to the DISPLAY variable. I use PuTTY, which does X forwarding. I wasn't running an X server on my desktop when starting YaST. Normally, this just results in a error message, and YaST exits. For whatever reason, it was causing the kernel panic in this case. (Neale Ferguson noted off-list that the PSW indicated something in kernel space was taking a WAB (Wild Branch) into location 0.) Doing an "unset DISPLAY" then starting YaST seems to have corrected the problem. Pretty bizarre that an X error could cause this. Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Kyle Smith Sent: Tuesday, August 01, 2006 2:26 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 Abend During Install You'll want to up the storage for your guest to 512M. I've seen it panic fairly easily with less than that. Full reqs are listed in the preparation guide (docu/en/preparation.pdf). ks -- 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
Re: SLES10 Abend During Install
You'll want to up the storage for your guest to 512M. I've seen it panic fairly easily with less than that. Full reqs are listed in the preparation guide (docu/en/preparation.pdf). ks On 8/1/06, Post, Mark K <[EMAIL PROTECTED]> wrote: CTCs are not QDIO devices, but thanks anyway. (And I already checked, besides. It is off.) Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Nilson Vieira Sent: Tuesday, August 01, 2006 1:37 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 Abend During Install Try ' set QIOASSIST off' on the Virtual Machine Profile. I hope that help´s - Original Message - From: "Post, Mark K" <[EMAIL PROTECTED]> To: Sent: Tuesday, August 01, 2006 2:20 PM Subject: SLES10 Abend During Install I have a z/VM 4.4 64-bit guest on a z900 that I'm trying to install SLES10 GA on. Things seem to go along fine, until I SSH in and start YaST. At that point, I get a the following messages on my terminal, followed by a kernel panic on the z/VM console: # yast *** Starting YaST2 *** (-- fairly long pause ---) *** Preparing SSH installation for reboot *** *** NOTE: after reboot, you have to reconnect and call *** *** /usr/lib/YaST2/startup/YaST2.ssh *** illegal operation: 0001 [#1] CPU:0Not tainted Process init (pid: 1, task: 007c1748, ksp: 007c3ca0) Krnl PSW : 070420018000 0002 (0x2) Krnl GPRS: 0001 03cdb2a8 0085 007c3cf0 0001 010c6160 0001 03cdb3c8 000a3898 03cdb3c8 0085 00446888 0025970c 007c3b38 Krnl Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Call Trace: ([<00259434>] mpage_writepages+0x23c/0xb40) [<001b07ca>] do_writepages+0x5a/0x74 [<00256a8c>] sync_inodes+0x540/0x1204 [<001fdad4>] sys_sync+0x30/0x84 [<0010f774>] sysc_noemu+0x10/0x16 [<021464aa>] 0x21464aa <0>Kernel panic - not syncing: Attempted to kill init! HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0014259E Q CPLEVEL z/VM Version 4 Release 4.0, service level 0403 (64-bit) Generated at 11/19/04 15:43:15 CDT IPL at 04/09/06 04:13:05 CDT Q STOR STORAGE = 256M My network connections are via CTC to the z/VM TCP/IP SVM. (Which is no longer officially supported in SLES, unfortunately. There's also a bug in the installer regarding CTCs, but I doubt I'll be reporting the issue because of that.) Anyone have any ideas about this one? It looks like a S0C1 (illegal opcode), but I don't know what might be causing it. Mark Post -- 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
Re: SLES10 Abend During Install
CTCs are not QDIO devices, but thanks anyway. (And I already checked, besides. It is off.) Mark Post -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Nilson Vieira Sent: Tuesday, August 01, 2006 1:37 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: SLES10 Abend During Install Try ' set QIOASSIST off' on the Virtual Machine Profile. I hope that help´s - Original Message - From: "Post, Mark K" <[EMAIL PROTECTED]> To: Sent: Tuesday, August 01, 2006 2:20 PM Subject: SLES10 Abend During Install I have a z/VM 4.4 64-bit guest on a z900 that I'm trying to install SLES10 GA on. Things seem to go along fine, until I SSH in and start YaST. At that point, I get a the following messages on my terminal, followed by a kernel panic on the z/VM console: # yast *** Starting YaST2 *** (-- fairly long pause ---) *** Preparing SSH installation for reboot *** *** NOTE: after reboot, you have to reconnect and call *** *** /usr/lib/YaST2/startup/YaST2.ssh *** illegal operation: 0001 [#1] CPU:0Not tainted Process init (pid: 1, task: 007c1748, ksp: 007c3ca0) Krnl PSW : 070420018000 0002 (0x2) Krnl GPRS: 0001 03cdb2a8 0085 007c3cf0 0001 010c6160 0001 03cdb3c8 000a3898 03cdb3c8 0085 00446888 0025970c 007c3b38 Krnl Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Call Trace: ([<00259434>] mpage_writepages+0x23c/0xb40) [<001b07ca>] do_writepages+0x5a/0x74 [<00256a8c>] sync_inodes+0x540/0x1204 [<001fdad4>] sys_sync+0x30/0x84 [<0010f774>] sysc_noemu+0x10/0x16 [<021464aa>] 0x21464aa <0>Kernel panic - not syncing: Attempted to kill init! HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0014259E Q CPLEVEL z/VM Version 4 Release 4.0, service level 0403 (64-bit) Generated at 11/19/04 15:43:15 CDT IPL at 04/09/06 04:13:05 CDT Q STOR STORAGE = 256M My network connections are via CTC to the z/VM TCP/IP SVM. (Which is no longer officially supported in SLES, unfortunately. There's also a bug in the installer regarding CTCs, but I doubt I'll be reporting the issue because of that.) Anyone have any ideas about this one? It looks like a S0C1 (illegal opcode), but I don't know what might be causing it. Mark Post -- 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
Re: SLES10 Abend During Install
Try ' set QIOASSIST off' on the Virtual Machine Profile. I hope that help´s - Original Message - From: "Post, Mark K" <[EMAIL PROTECTED]> To: Sent: Tuesday, August 01, 2006 2:20 PM Subject: SLES10 Abend During Install I have a z/VM 4.4 64-bit guest on a z900 that I'm trying to install SLES10 GA on. Things seem to go along fine, until I SSH in and start YaST. At that point, I get a the following messages on my terminal, followed by a kernel panic on the z/VM console: # yast *** Starting YaST2 *** (-- fairly long pause ---) *** Preparing SSH installation for reboot *** *** NOTE: after reboot, you have to reconnect and call *** *** /usr/lib/YaST2/startup/YaST2.ssh *** illegal operation: 0001 [#1] CPU:0Not tainted Process init (pid: 1, task: 007c1748, ksp: 007c3ca0) Krnl PSW : 070420018000 0002 (0x2) Krnl GPRS: 0001 03cdb2a8 0085 007c3cf0 0001 010c6160 0001 03cdb3c8 000a3898 03cdb3c8 0085 00446888 0025970c 007c3b38 Krnl Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Call Trace: ([<00259434>] mpage_writepages+0x23c/0xb40) [<001b07ca>] do_writepages+0x5a/0x74 [<00256a8c>] sync_inodes+0x540/0x1204 [<001fdad4>] sys_sync+0x30/0x84 [<0010f774>] sysc_noemu+0x10/0x16 [<021464aa>] 0x21464aa <0>Kernel panic - not syncing: Attempted to kill init! HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0014259E Q CPLEVEL z/VM Version 4 Release 4.0, service level 0403 (64-bit) Generated at 11/19/04 15:43:15 CDT IPL at 04/09/06 04:13:05 CDT Q STOR STORAGE = 256M My network connections are via CTC to the z/VM TCP/IP SVM. (Which is no longer officially supported in SLES, unfortunately. There's also a bug in the installer regarding CTCs, but I doubt I'll be reporting the issue because of that.) Anyone have any ideas about this one? It looks like a S0C1 (illegal opcode), but I don't know what might be causing it. Mark Post -- 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
SLES10 Abend During Install
I have a z/VM 4.4 64-bit guest on a z900 that I'm trying to install SLES10 GA on. Things seem to go along fine, until I SSH in and start YaST. At that point, I get a the following messages on my terminal, followed by a kernel panic on the z/VM console: # yast *** Starting YaST2 *** (-- fairly long pause ---) *** Preparing SSH installation for reboot *** *** NOTE: after reboot, you have to reconnect and call *** *** /usr/lib/YaST2/startup/YaST2.ssh *** illegal operation: 0001 [#1] CPU:0Not tainted Process init (pid: 1, task: 007c1748, ksp: 007c3ca0) Krnl PSW : 070420018000 0002 (0x2) Krnl GPRS: 0001 03cdb2a8 0085 007c3cf0 0001 010c6160 0001 03cdb3c8 000a3898 03cdb3c8 0085 00446888 0025970c 007c3b38 Krnl Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Call Trace: ([<00259434>] mpage_writepages+0x23c/0xb40) [<001b07ca>] do_writepages+0x5a/0x74 [<00256a8c>] sync_inodes+0x540/0x1204 [<001fdad4>] sys_sync+0x30/0x84 [<0010f774>] sysc_noemu+0x10/0x16 [<021464aa>] 0x21464aa <0>Kernel panic - not syncing: Attempted to kill init! HCPGIR450W CP entered; disabled wait PSW 00020001 8000 0014259E Q CPLEVEL z/VM Version 4 Release 4.0, service level 0403 (64-bit) Generated at 11/19/04 15:43:15 CDT IPL at 04/09/06 04:13:05 CDT Q STOR STORAGE = 256M My network connections are via CTC to the z/VM TCP/IP SVM. (Which is no longer officially supported in SLES, unfortunately. There's also a bug in the installer regarding CTCs, but I doubt I'll be reporting the issue because of that.) Anyone have any ideas about this one? It looks like a S0C1 (illegal opcode), but I don't know what might be causing it. Mark Post -- 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
