HCPGIR450W CP entered; disabled wait PSW 00020000 80000000 00000000 00004502
Bug #1592990 reported by
Ron Argent
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on IBM z Systems |
Fix Released
|
Critical
|
Dimitri John Ledkov | ||
debian-installer (Ubuntu) |
Fix Released
|
Critical
|
Dimitri John Ledkov | ||
s390-tools (Ubuntu) |
Fix Released
|
Critical
|
Dimitri John Ledkov | ||
Xenial |
Fix Released
|
Critical
|
Dimitri John Ledkov |
Bug Description
zVM v6.3 zBC12 V7000 FICON SAN048B
Installed Ubuntu on zBC12 with FICON attached (via SAN048B switches) using instructions at https:/
Installation build completed OK but IPL fails (after initial boot options appear and timeout to default) with following error message:
HCPGIR450W CP entered; disabled wait PSW 00020000 80000000 00000000 00004502
A trace was taken using:
#CP TR SSCH RUN
#CP IPL <ipldev>
#cp tr end
The resulting trace appears to fail at the same point in the trace on every IPL.
Several builds have been attempted on different VMs with identical symptoms.
Related branches
lp:~xnox/debian-installer/xnox462
- Adam Conrad: Pending requested
- Ubuntu Core Development Team: Pending requested
-
Diff: 129 lines (+26/-8)9 files modifiedbuild/config/amd64.cfg (+1/-1)
build/config/arm64.cfg (+1/-1)
build/config/armel.cfg (+1/-1)
build/config/armhf.cfg (+1/-1)
build/config/i386.cfg (+1/-1)
build/config/powerpc.cfg (+1/-1)
build/config/ppc64el.cfg (+1/-1)
build/config/s390x.cfg (+1/-1)
debian/changelog (+18/-0)
tags: | added: s390x |
Changed in ubuntu-z-systems: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in ubuntu-z-systems: | |
status: | Triaged → Confirmed |
assignee: | nobody → Dimitri John Ledkov (xnox) |
Changed in s390-tools (Ubuntu): | |
status: | New → In Progress |
Changed in s390-tools (Ubuntu Xenial): | |
status: | New → In Progress |
Changed in s390-tools (Ubuntu): | |
importance: | Undecided → Critical |
Changed in s390-tools (Ubuntu Xenial): | |
importance: | Undecided → Critical |
Changed in s390-tools (Ubuntu): | |
assignee: | nobody → Dimitri John Ledkov (xnox) |
Changed in s390-tools (Ubuntu Xenial): | |
assignee: | nobody → Dimitri John Ledkov (xnox) |
Changed in debian-installer (Ubuntu): | |
status: | New → In Progress |
Changed in debian-installer (Ubuntu Xenial): | |
status: | New → In Progress |
Changed in debian-installer (Ubuntu): | |
importance: | Undecided → Critical |
Changed in debian-installer (Ubuntu Xenial): | |
importance: | Undecided → Critical |
Changed in debian-installer (Ubuntu): | |
assignee: | nobody → Dimitri John Ledkov (xnox) |
Changed in debian-installer (Ubuntu Xenial): | |
assignee: | nobody → Dimitri John Ledkov (xnox) |
Changed in ubuntu-z-systems: | |
importance: | High → Critical |
status: | Confirmed → In Progress |
Changed in ubuntu-z-systems: | |
status: | In Progress → Fix Committed |
Changed in ubuntu-z-systems: | |
status: | Fix Committed → Fix Released |
tags: |
added: targetmilestone-inin1604 removed: targetmilestone-inin1404 |
To post a comment you must log in.
Hi Ron, thanks for opening this ticket.
The wiki page you mentioned covers an installation with dasd disks, in this case it's a zFCP/SCSI installation, so some additional information would be helpful:
I assume SCSI disks are used directly and no emulated devices (EDEV), right?
Please can you provide the 'user direct' of the guest and the output of the following CP commands:
#CP Q V FCP
#CP Q LOADDEV
#CP Q V DA
And are there any special kernel boot / zipl parameters in use (like cio_ignore) ?