apt-get update fails on ppc64le virtual machine

Bug #1866314 reported by Chris Ward
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apt (Ubuntu)
New
Undecided
Unassigned

Bug Description

I am trying to install Ubuntu 20.04 for ppc64le in a virtual machine. (The host is x86-64 running OpenSUSE Tumbleweed). The install works, but on reboot when I attempt to install updates with 'apt-get update' and 'apt-get upgrade', the update command fails with a segmentation violation. It indicates that core is dumped but I don't see a core dump in my current directory. I will add a screenshot of the problem.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apt 1.9.7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic ppc64le
.var.log.platform: Error: [Errno 13] Permission denied: '/var/log/platform'
ApportVersion: 2.20.11-0ubuntu15
Architecture: ppc64el
Date: Fri Mar 6 08:57:02 2020
InstallationDate: Installed on 2020-03-06 (0 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha ppc64el (20200124)
ProcLoadAvg: 1.00 0.98 1.72 1/104 2304
ProcLocks:
 1: POSIX ADVISORY WRITE 868 00:19:478 0 EOF
 2: FLOCK ADVISORY WRITE 832 00:19:506 0 EOF
 3: POSIX ADVISORY WRITE 773 00:19:462 0 EOF
ProcSwaps:
 Filename Type Size Used Priority
 /swapfile file 969536 0 -2
ProcVersion: Linux version 5.4.0-9-generic (buildd@bos02-ppc64el-004) (gcc version 9.2.1 20191130 (Ubuntu 9.2.1-21ubuntu1)) #12-Ubuntu SMP Mon Dec 16 22:32:07 UTC 2019
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
cpu_cores: Number of cores present = 1
cpu_coreson: Number of cores online = 1
cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: Machine is not SMT capable

Revision history for this message
Chris Ward (tjcw) wrote :
Revision history for this message
Chris Ward (tjcw) wrote :
Revision history for this message
Chris Guiver (guiverc) wrote :

Did you look in /var/crash/ ?

Revision history for this message
Chris Ward (tjcw) wrote :

I tried this on another x86-64 machine, and the apt-get update and apt-get upgrade commands are running normally. I will have access to the machine which failed again on Monday; I will look in /var/crash then.

Revision history for this message
Chris Ward (tjcw) wrote :

This didn't reproduce on the machine which initially showed the problem. So this bug can be closed 'worksforme'.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.