This bug is still present in Ubuntu 16.04.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1247905
Title:
update-grub fails in the face of overlayroot
To manage notifications about this bug go to:
@modiford
http://cdimage.ubuntu.com/releases/18.04.2/release/ubuntu-18.04.2
-server-amd64.iso
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816954
Title:
Unable to show Info nor Set static IP
@chad.smith Why should subiquity change the default setting of cloud-
init as opposed to just fixing the default setting in cloud-init? I feel
the bug is in cloud-init and not in subiquity.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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 noticed this never got SRU'd. Oversight?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565275
Title:
[SRU] Add support to import multiple keys
To manage notifications about this bug go to:
$ apt rdepends dbus-user-session
dbus-user-session
Reverse Depends:
|Suggests: dbus
Depends: anbox-common
|Suggests: dbus
|Suggests: dbus
Which I understand is not an official package and in my case, is no
longer installed. The point is, dbus-user-session is an official package
and causes
This bug was not only related to Flatpak. I have never
installed/used/heard of Flapak before I filed this bug. Maybe this bug
should be filed against dbus-user-session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@adamsmith
The patch you mention might be in image we download, but as soon as we
upgrade to a newer kernel with sudo apt-get dist-upgrade, this is when
we have the issue.
You say we shouldn't blame Ubuntu or Ryan, but someone is dropping the
ball on fixing this issue or submitting a patch
Since there are multiple packages that depend on dbus-user-session,
there's really no need to mention a single package in the title.
** Summary changed:
- gnome-keyring not unlocked on xenial when dbus-user-session is installed,
which flatpak depends on
+ gnome-keyring not unlocked on xenial
All I have running is /usr/bin/gnome-keyring-daemon --daemonize --login
The files in your /etc/xdg/autostart look fine
Just need to make sure you're not starting gnome-keyring anywhere else.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@antonioshadji
I had to undo the workarounds in order for it to stop asking for
passwords at login:
In /etc/xdg/autostart/gnome-keyring-ssh.desktop
I originally replaced:
Exec=/usr/bin/gnome-keyring-daemon --start --components=ssh
with
#Exec=/usr/bin/gnome-keyring-daemon --daemonize
Removing dbus-user-session resolved my issue. It got added when I
temporarily installed anbox. There was no xdg-desktop-portal or xdg-
desktop-portal-gtk installed or available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It does not have anything to do with flatpack or pitivi. I have several
machines experiencing this issue and have never installed either of the
mentioned packages on any of them in any point in time.
** Changed in: flatpak (Ubuntu)
Status: New => Invalid
--
You received this bug
This has manifested itself on a machine with a fresh install of 16.04.2
with nothing installed but google chrome. I have 2 other machines with
this issue and neither have ever had the flatpak PPA enabled or anything
installed from it.
--
You received this bug notification because you are a
That is not a fix. It is a workaround. On boot, my system has gnome-
keyring-daemon running which needs to be killed and restarted without
--login in order to function. This was working a couple weeks ago. There
should be no "fixes" the user need to do to regain this functionality.
--
You
** Summary changed:
- ubuntu 16.04 Chrome and Chromium asking for keyring.
+ gnome-keyring not unlocked on boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689825
Title:
gnome-keyring not
Links to other users with the same or similar issue within the past 2
days:
https://askubuntu.com/questions/911877/chrome-and-chromium-are-taking-a
-long-time-to-load
https://askubuntu.com/questions/913756/xubuntu-16-04-chrome-and-
chromium-asking-for-keyring-i-want-this-right-not-del/913766
Public bug reported:
1) Release: 16.04.2
2) gnome-keyring: 3.18.3-0ubuntu2
3) Login. gnome-keyring unlocks "login" features including for google chrome
4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no
secure password features(sync) functioning.
For the past couple
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656112
Title:
Power S822LC (8335-GTB) fails KVM guest cert test
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677337
Title:
Mellanox Technologies MT27500 Family [ConnectX-3] no network
connectivity
To manage
4.8.0-45.48~16.04.1 from xenial updates works
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677337
Title:
Mellanox Technologies MT27500 Family [ConnectX-3] no network
connectivity
To manage
linux-image-4.10.6-041006 has also failed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677337
Title:
Mellanox Technologies MT27500 Family [ConnectX-3] no network
connectivity
To manage
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: qemu (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656112
Title:
Power S822LC (8335-GTB) fails KVM guest cert test with
** 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 Ubuntu
Bugs,
kernel 4.11.0-041100rc3-generic failed with the same symptoms.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675091
Title:
Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by
udev
** Also affects: checkbox (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1675091
Title:
Mellanox MT27500 Family [ConnectX-3] 40G NIC not being
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656112
Title:
Power S822LC
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656112
Title:
Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu
failed:
** Tags removed: blocks-hwcert-server
** Changed in: plainbox-provider-checkbox (Ubuntu)
Status: Triaged => Fix Released
** Changed in: plainbox-provider-checkbox (Ubuntu Xenial)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of
Looks like this one is finally resolved. These are the results from my
recent testing:
Result,Timestamp,Test Name,Duration,kernel,Package
version,CPU's,Memory,Package,Note
PASS,2017-02-21-19-39-20,disk_stress_ng,01:48:24,4.4.0-63-generic-84-Ubuntu,0.07.16-1ppa1,128,31G,Stock
stress-ng, stock
@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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656112
Title:
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1659929
Title:
The specific lines in /usr/lib/plainbox-provider-
checkbox/bin/virtualization are
'ppc64el': {
'cloudimg_type': CLOUD_IMAGE_TYPE_DISK,
'cloudimg_arch': 'ppc64el',
'qemu_bin': 'qemu-system-ppc64',
'qemu_disk_type': QEMU_DISK_TYPE_VIRTIO,
://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656112
** Affects: plainbox-provider-checkbox (Ubuntu)
Importance: Undecided
Assignee: Mike Rushton (leftyfb)
Status: In Progress
** Changed in: plainbox-provider-checkbox (Ubuntu)
Assignee: (unassigned) => Mike Rushton (left
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 Ubuntu
Bugs, which is subscribed to
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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652132
Title:
Call trace
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652132
Title:
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1652132
Title:
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
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 Ubuntu
Bugs, which is
`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 Ubuntu
Bugs, which is
@mark when/if it eventually gets fixed, it might be the same issue. We
won't know until we get it resolved.
@colin confirmed stress-ng 0.07.08-1 on a different power 8 server still
has the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
stress-ng was at 0.05.23-1ubuntu2 for the above tests.
I have now upgraded stress-ng from the package in Xenial to that from
Zesty:
$ sudo apt-cache policy stress-ng
stress-ng:
Installed: 0.07.08-1
Candidate: 0.07.08-1
Version table:
*** 0.07.08-1 500
500
Attached is another run of the test with
test_dir="/tmp/disk_stress_ng_$(uuidgen)"
The test was hung with the following on the screen:
Running stress-ng sync-file stressor for 240 seconds
stress-ng: unrecognized option '--sync-file'
Try 'stress-ng --help' for more information.
return_code is
It seems to be stuck on:
root 10664 1 0 18:28 pts/300:00:00 stress-ng --aggressive
--verify --timeout 240 --temp-path /tmp/disk_stress_ng --fstat 0
Though /tmp/disk_stress_ng doesn't exist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "screenlog.1"
https://bugs.launchpad.net/ubuntu/+source/plainbox-provider-checkbox/+bug/1640547/+attachment/4778821/+files/screenlog.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "ps.log"
https://bugs.launchpad.net/ubuntu/+source/plainbox-provider-checkbox/+bug/1640547/+attachment/4778822/+files/ps.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I had to run the test again. It's been running for about an hour now. I
will post the logs and full screen output when it is finished.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640547
Title:
** Changed in: stress-ng
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640547
Title:
stress-ng based disk tests failing
To manage notifications about
Still getting the same issues with stress-ng 0.07.04
ubuntu@fesenkov:~$ apt-cache policy stress-ng
stress-ng:
Installed: 0.07.04-1
Candidate: 0.07.04-1
Version table:
*** 0.07.04-1 500
500 http://ports.ubuntu.com/ubuntu-ports zesty/universe ppc64el Packages
100
** 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 Ubuntu
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640547
Title:
stress-ng tests failing
To manage
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
Public bug reported:
Terminator crashes randomly.
Attached is the .crash file from /var/crash/
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: terminator 0.98-1
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
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
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
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 Ubuntu
Bugs, which is subscribed to 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
Screenshot showing VPN profile grayed out.
** Attachment added: "Screenshot from 2016-08-22 11-58-21.png"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1615716/+attachment/4725843/+files/Screenshot%20from%202016-08-22%2011-58-21.png
--
You received this bug notification
Public bug reported:
After upgrading from Ubuntu 14.04 to 16.04, the VPN profile which was
used daily is now grayed out on boot. See attached screenshot.
After restarting the network-manager service, the profile is then active
and can be selected and connects without issue.
ProblemType: Bug
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
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 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 Ubuntu
Bugs, which is subscribed to 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 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
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
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 Ubuntu
Bugs, 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 Ubuntu
Bugs, which is
4.4.0-32-generic-51~lp1573062.1 failed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
To manage notifications
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 Ubuntu
Bugs, which is
Commit failed:
4f1b50c3e3082b31c94cee2b897bd9f5d0f3e7c8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
To manage
Commit failed:
ddc8f6feec76b5deea8090db015920a283006044
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
To manage
Commit failed:
ee61e95b6b33c82f6fa1382585faed66aa01245
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
To manage
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573062
Title:
memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
To manage
1 - 100 of 269 matches
Mail list logo
