Public bug reported:
Intel NUC's from Axiomtek with Intel Corporation Wireless 7260 (rev bb)
chipsets. We have this running on almost 200 of these devices.
Ubuntu 16.04.3 as well as Ubuntu 14.04.5
"loaded firmware version 17.608620.0 op_mode iwlmvm"
linux-firmware trusty: 1.127.24
I have tested the qemu-system-ppc package from both PPA's and both work
without issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112
Title:
Power S822LC (8335-GTB) fails KVM
I tested 4.4.0-72 from above and got the same results as 4.4.0-71.
In the process of testing 4.4.0-71 more, I found all is not as well as
we assumed. At first deployment everything seems to be fine. And after
most reboots, we are still able to ping across both interfaces. But
bringing interfaces
4.4.0-71-generic is tested as working now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1677337
Title:
Mellanox Technologies MT27500 Family [ConnectX-3] no network
connectivity
4.8.0-45.48~16.04.1 from xenial updates works
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1677337
Title:
Mellanox Technologies MT27500 Family [ConnectX-3] no network
connectivity
linux-image-4.10.6-041006 has also failed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1677337
Title:
Mellanox Technologies MT27500 Family [ConnectX-3] no network
connectivity
Public bug reported:
After a fresh install of Ubuntu 16.04.2 with 4.4.0-70-generic, the
Mellanox Technologies MT27500 Family [ConnectX-3] card is detected,
brought up and assigned an ip via MAAS. This is where functionality
stops on this kernel. Pinging the MAAS server which is connected
** Changed in: plainbox-provider-checkbox
Status: Fix Released => Confirmed
** Changed in: plainbox-provider-checkbox
Assignee: Mike Rushton (leftyfb) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: qemu (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112
Title:
Power S822LC (8335-GTB) fails KVM guest cert test
** Summary changed:
- Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed:
Invalid argument
+ Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu failed:
Invalid argument
--
You received this bug notification because you are a member of Kernel
kernel 4.11.0-041100rc3-generic failed with the same symptoms.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1675091
Title:
Mellanox MT27500 Family [ConnectX-3] 40G NIC not being
** Also affects: checkbox (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1675091
Title:
Mellanox MT27500 Family [ConnectX-3] 40G NIC
Public bug reported:
During certification testing on Power8NVL, the network tests for the
Mellanox 40/56G network cards are failing. According to the failure
pasted below, udev/dbus isn't detecting the network card properly, but
NetworkManager is. My feeling is this might be an issue with
This issue, or similar symptoms doesn't seem to be fixed. This is with
stock kernel, stock stress-ng but with the suggested changes to the
memory_stress_ng test script. The machine locks up completely maybe 1
out of 5-10 runs. See attached dmesg for errors.
Kernel: 4.4.0-64-generic-85-Ubuntu
Just to be sure I installed qemu-system-ppc version 1:2.6.1+dfsg-
0ubuntu5.3 from yakkety-updates and the tests pass.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112
Title:
Power
We received the hardware back and have started testing all blockers
again. The latest test of the above mentioned PPA did not yield positive
results:
"Unable to find PowerPC CPU definition"
$ apt-cache policy qemu-system-ppc
qemu-system-ppc:
Installed: 1:2.5+dfsg-5ubuntu10.10
Candidate:
We still have not received the machine back from IBM.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1656112
Title:
Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
@paelzer the machine was sent out for repair/replacement. We expect it
to return later this week. I will test the package from the above PPA as
soon as it is back.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Christian
The qemu fix is still necessary in order to resolve the issue.
While I do have access to the hardware, it is currently having issues
booting. Once we resolve the issue with IBM, I plan on testing out the
qemu fix from the PPA.
--
You received this bug notification because you are a
@Christian The branch is for a fix in the plainbox-provider-checkbox
package which is part of the certification suite. It is not for qemu-
system-ppc but is a necessary part of the overall fix since the script
was originally assuming POWER8.
--
You received this bug notification because you are
** Merge proposal linked:
https://code.launchpad.net/~leftyfb/plainbox-provider-checkbox/+git/plainbox-provider-checkbox/+merge/315823
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
In my testing, only qemu-system-ppc version 1:2.6.1+dfsg-0ubuntu5.2
available in yakkety and the template to set -cpu POWER8NVL was needed
to resolve the issue. No kernel patches were necessary.
--
You received this bug notification because you are a member of Kernel
Packages, which is
KVM was never tested successfully on this particular model. The
virtualization test works fine on all other open power servers we have
in the labs.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
4.10 RC3 gives a kernel panic:
[3.863436] ahci 0009:04:00.0: AHCI 0001. 32 slots 4 ports 6 Gbps 0xf
impl SATA mode
[3.863631] ahci 0009:04:00.0: flags: 64bit ncq sntf led only pmp fbs pio
slum part sxs
[3.864221] scsi host0: ahci
[3.864404] scsi host1: ahci
[3.864562]
As mentioned above, I have run the test multiple times with SMT both
enabled and disabled. I get the same error. This is from running the
test just now with SMT disabled:
WARNING: Image format was not specified for 'seed.iso' and probing guessed raw.
Automatically detecting the format is
This test has been run dozens of times across multiple machines and
deployments and reboots. It is completely reproducible.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1652132
Title:
Public bug reported:
Upon running the virtualization test from the certification test suite,
the kvm guest test fails with the following error:
kvm_init_vcpu failed: Invalid argument
This same test works on multiple other IBM Power 8 and Openpower
servers. kvm-ok tells us that kvm
apport-collect is not functioning on this server:
The collected information can be sent to the developers to improve the
application. This might take a few minutes.
tar: Removing leading `/' from member names
tar: Removing leading `/' from member names
tar: Removing leading `/' from member
** Summary changed:
- Call trace when testing fstat stressor on ppc64el with virtual keyboard and
mouse
+ Call trace when testing fstat stressor on ppc64el with virtual keyboard and
mouse present
** Tags added: blocks-hwcert-server
--
You received this bug notification because you are a
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652132/+attachment/4795377/+files/kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1652132
** Attachment added: "dmesg1.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652132/+attachment/4795378/+files/dmesg1.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Ubuntu 16.04.1
Kernel = 4.4.0-53-generic-74-Ubuntu ppc64le
When running the stress-ng "fstat" stressor, it is trying to access the
USB bus and giving a call trace and locking up any further USB activity
(lsusb hangs). This only seems to occur so far on openpower(Firestone
dmesg output while stress_ng test was running on Power 8 Tuleta LPAR
** Attachment added: "dmesg2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4788537/+files/dmesg2
--
You received this bug notification because you are a member of Kernel
Packages, which is
output of stress_ng test running on Power 8 Tuleta LPAR
** Attachment added: "3.19.0-15-generic-15-Ubuntu.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4788536/+files/3.19.0-15-generic-15-Ubuntu.log
--
You received this bug notification because you are a
`ps -ax` output while stress_ng test was running on Power 8 Tuleta LPAR
** Attachment added: "ps2.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4788538/+files/ps2.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Also affects: plainbox-provider-checkbox (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
** Changed in: plainbox-provider-checkbox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
** Summary changed:
- Disk test fails on IBM Power S822LC (8335-GTB)
+ stress-ng tests failing
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1640547
Title:
stress-ng tests failing
Also seeing this problem on Dell PowerEdge with a xeon phi processor and
4.8 kernel on Ubuntu 16.10.
See attached.
** Attachment added: "disk_test.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640547/+attachment/4775439/+files/disk_test.txt
--
You received this bug
Public bug reported:
When running the stress-ng disk test, we are seeing the following
failures as well as I/O lockup:
/dev/sda is a block device
Found largest partition: "/dev/sda2"
Test will use /dev/sda2, mounted at "/", using "ext4"
test_dir is /tmp/disk_stress_ng
Estimated total run time is
** Attachment added: "alpine.xml"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4740352/+files/alpine.xml
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "gulpin.xml"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4740353/+files/gulpin.xml
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "tuleta.xml"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4740354/+files/tuleta.xml
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1. Can we get the configurations of the machines.
XML files for all 4 machines with hardware information from the
certification process will be attached in the next few comments
2. The first column is the number of times the test ran?
Yes
4. Did any of the tests result in system hang? Can we
Sorry, I should have taken out the 4.4.0-31 tests. That test was not
using stress-ng but our original memory stress test.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
Attached is the cultivation of all the kernel testing we have done.
** Attachment added: "Power Testing Result.pdf"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4732427/+files/Power%20Testing%20Result.pdf
--
You received this bug notification because you are a
** Summary changed:
- memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
+ memory_stress_ng failing for Power architecture for 16.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
dmesg from failed test on Firestone
** Attachment added: "dmesg1"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4723529/+files/dmesg1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Out of the 4 tests last night (Habanero(NV), Firstone(NV), Tuleta(NV),
Alpine(VM) only the Firestone failed. Attached is the output from the
test, kern.log and dmesg output I was running in a while loop during
testing.
** Attachment added: "FAIL-2016-08-18-03-25-32.log"
kern.log from failed test on Firestone
** Attachment added: "FAIL-2016-08-18-03-25-32.kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4723528/+files/FAIL-2016-08-18-03-25-32.kern.log
--
You received this bug notification because you are a member of Kernel
kern.log from the Habanero 4.4.0-34-generic-53~lp1573062PATCHED test
** Attachment added: "FAIL-2016-08-17-17-49-41.kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4723089/+files/FAIL-2016-08-17-17-49-41.kern.log
--
You received this bug notification
kern.log from the Firestone 4.4.0-34-generic-53~lp1573062PATCHED test
** Attachment added: "FAIL-2016-08-17-17-12-46.kern.log.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4723091/+files/FAIL-2016-08-17-17-12-46.kern.log.tar.gz
--
You received this bug
This is a failed test from today on the Firestone. Find the test output
and kern.log attached:
ubuntu@gulpin:~/4.4.0-34-generic-53~lp1573062PATCHED$ free -m
totalusedfree shared buff/cache available
Mem: 32565 342 30092 21
This is a failed test from today on the Habanero. Find the test output
and kern.log attached:
ubuntu@binacle:~/4.4.0-34-generic-53~lp1573062PATCHED$ free -m
totalusedfree shared buff/cache available
Mem: 261533 621 259912 20
Kalpana:
The above failed test was run on only 1 of the possible 4 machines we
have been testing with for months now. The other openpower server is a
Habanero with 256G. I am running tests on that as we speak and going to
include the kern.log as well.
Just to clarify, the memory test I'm running
I had this fail on 2 openpower boxes. I have attached the output from
the test.
** Attachment added: "4.4.0-34-generic-53~lp1573062PATCHED.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4722751/+files/4.4.0-34-generic-53~lp1573062PATCHED.log
--
You received
mainline kernel 4.7 failed.
** Attachment added: "kern.log from 4.7 testing failure"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4708871/+files/kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Output of 4.7 mainline kernel testing failure
** Attachment added: "4.7.0-040700-generic-201607241632.log from 4.7 testing
failure"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4708872/+files/4.7.0-040700-generic-201607241632.log
--
You received this bug
Attached is the kern.log from the Firestone PowerNV server. This one is
failing with stack traces which only started after we started testing
patched kernels.
The Habanero PowerNV failed with the typical locked up console and
OOM's.
** Attachment added: "kern.log"
I'm running the tests as we speak across 2 LPAR's and 2 openpower
PowerNV installations. One of the open power boxes has 256G of memory so
it takes up to 7 hours for a test to pass or to be determined failed.
--
You received this bug notification because you are a member of Kernel
Packages,
4.4.0-32-generic-51~lp1573062.1 failed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
Status in
kern.log attached to show additional failures with patched kernel
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4698878/+files/kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
Commit failed:
4f1b50c3e3082b31c94cee2b897bd9f5d0f3e7c8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
Commit failed:
ddc8f6feec76b5deea8090db015920a283006044
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
Commit failed:
ee61e95b6b33c82f6fa1382585faed66aa01245
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
The memory_stress_ng test is part of the plainbox-provider-checkbox
package which can be installed from the hardware-certification PPA:
https://code.launchpad.net/~hardware-
certification/+archive/ubuntu/public
The full path once installed is:
895a1067d5b83065afbad3bb02c3c464b71f1b3f failed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
Status
d9dddbf556674bf125ecd925b24e43a5cf2a568a failed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
Status
45996492e5c85aa0ac93a95d1b2d1ed56851c865 failed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
Status
8f40842e4260f73792c156aded004197a19135ee failed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
Status
4.5.0-040500-generic-201605251558 failed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
Status in
PASS,2016-05-23-13-21-37,4.5.0-040500-generic-201605230752
FAIL,2016-05-23-21-06-07,4.5.0-040500-generic-201605230752
PASS,2016-05-24-04-32-39,4.5.0-040500-generic-201605230752
FAIL,2016-05-24-13-31-01,4.5.0-040500-generic-201605230752
FAIL,2016-05-25-04-06-51,4.5.0-040500-generic-201605230752
--
4.5.0-040500.201605171117 failed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
Status in linux
I would go ahead and assume it's good. I haven't had 2 tests run good
twice in a row yet.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM
So far, after 2 runs, 4.5.0-040500-generic_4.5.0-040500.201605161244
seems to be working. I'm running it a 3rd time now just to be sure. It
takes about 7 hours to finish.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Testing now...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
Status in linux package in Ubuntu:
In
4.5.0-040500.201603140130_ppc64el - fail
4.6.0-040600rc1.201603261930_ppc64el - pass
4.6 was run twice and passed both times.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062
I have noticed only on the Alpine hardware within an LPAR that is has
been sporadic. I assume that is due to the additional hardware resources
that can better handle the memory/stress test. All other tests have been
2 or 3 times each. More more than that. I can run the above kernel
tests, but mind
Ubuntu 14.04
3.19.0-58-generic - pass
4.2.0-35-generic - fails
4.1.0-040100-generic - fail
4.6.0-040600rc6-generic - pass
Ubuntu 16.04
4.4.0-22-generic - fail
4.1.0-040100-generic - fail
4.6.0-040600rc6-generic - pass
--
You received this bug notification because you are a member of Kernel
Confirmed the above kernel fails in the same manner.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
Are there ppc64le versions of those kernels?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
Status in
The tests run manually above were NOT run as root. The test during
certification does run as root. I have run the test as root and as the
ubuntu user, both with the same results.
Also, as shown above, this test ran fine manually while running Ubuntu
14.04 without root and during proper
The very first line of the screen session shows how the test is being
run:
/usr/lib/plainbox-provider-checkbox/bin/memory_stress_ng
The machine is completely unresponsive. No ssh, no ping and the console
over ipmi is locked up. Hitting CTRL+C over the sol console does nothing
at all. This is
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power
screen session log from successful test on 14.04
** Attachment added: "screen session log from successful test on 14.04"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4641500/+files/14.04.log
--
You received this bug notification because you are a member of Kernel
screen session of failure
** Attachment added: "screen session of failure"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4641490/+files/screenlog.0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
kern.log from successful test on 14.04
** Attachment added: "kern.log from successful test on 14.04"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4641501/+files/1404-kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which
kern.log from failure
** Attachment added: "kern.log from failure"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4641492/+files/kern.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
memory_stress_ng, as part of server certification is failing for IBM
Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
defined by the test locking up the server in an unrecoverable state
which only a reboot will fix.
I will be attaching screen and kern
I have also shown that this issue has the exact same results on PowerNV
above.
** Changed in: qemu
Status: Invalid => Confirmed
** Changed in: qemu (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
1. the bug reporter is using a powervm partition. KVM cannot be used
there. This is not a KVM bug.
PowerVM mode is an LPAR. It is not a kvm instance trying to run an KVM
within. This was also working in 14.04 without issue and is being asked
of us from IBM to certify
2. the xenial cloud images
The PowerVM machine I've been using for these tests has the following
output:
ubuntu@alpine01:~/kvm$ cat /proc/cpuinfo | grep platform
platform: pSeries
The PowerNV server has the following output:
ubuntu@binacle:~$ cat /etc/issue; uname -a ; ppc64_cpu --smt ; cat
/proc/cpuinfo |grep
Sorry, I copied the wrong thing:
sudo qemu-system-ppc64 -enable-kvm -m 256 -display none -nographic -net nic
-net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries
-drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive
file=seed.iso,if=virtio
@mdroth
I don't think PPC supports kvm the same way as x86:
ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -enable-kvm -m 256 -display none
-nographic -net nic -net
user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -machine pseries -drive
@serge-hallyn
ubuntu@alpine01:~/kvm$ cat /etc/issue; uname -a ; ppc64_cpu --smt
Ubuntu Xenial Xerus (development branch) \n \l
Linux alpine01 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016
ppc64le ppc64le ppc64le GNU/Linux
SMT is off
ubuntu@alpine01:~/kvm$ qemu-system-ppc64 -m 256
ubuntu@alpine01:~$ sudo ppc64_cpu --smt=1
ubuntu@alpine01:~$ ppc64_cpu --info
Core 0:0*1 2 3 4 5 6 7
Core 1:8*9101112131415
Core 2: 16* 17181920212223
Core 3: 24* 25262728
ubuntu@alpine01:~$ ppc64_cpu --info
Core 0:0*1*2*3*4*5*6*7*
Core 1:8*9* 10* 11* 12* 13* 14* 15*
Core 2: 16* 17* 18* 19* 20* 21* 22* 23*
Core 3: 24* 25* 26* 27* 28* 29* 30* 31*
Core 4: 32* 33*
Due to the nature of no network connectivity, We cannot login (curtin
preseed didn't run to setup credentials) or submit logs.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Attachment added: "regiond.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563055/+attachment/4615238/+files/regiond.log
** Summary changed:
- IBM Power8 PPC MAAS images booting with no network
+ IBM ppc64le MAAS images booting with no network
--
You received this bug
** Attachment added: "sutboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563055/+attachment/4615236/+files/sutboot.txt
** Description changed:
The latest daily Xenial image for MAAS seems to lack network
connectivity. Tested with kernel version 4.4.0-15 from the 20160328
** Attachment added: "clusterd.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1563055/+attachment/4615237/+files/clusterd.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 140 matches
Mail list logo
