[Bug 1760937] Re: [Feature Freeze Exception]Update Ledmon in Ubuntu 18.04 05 new upstream 0.90

Thanks Jeremy, this is the first package I've ever built for Ubuntu, before they've always been for PPAs so versioning wasn't super critical. because the version regressed, I've had to start a new PPA and 0.90-0ubuntu1 is building now:

[Bug 1760937] Re: [Feature Freeze Exception]Update Ledmon in Ubuntu 18.04 05 new upstream 0.90

Upgrade test: bladernr@bionic-buildtest:~$ apt-cache policy ledmon ledmon: Installed: 0.79-2build1 Candidate: 0.90-1 Version table: 0.90-1 500 500 http://ppa.launchpad.net/bladernr/final-builds/ubuntu bionic/main amd64 Packages *** 0.79-2build1 500 500

[Bug 1760937] Re: [Feature Freeze Exception]Update Ledmon in Ubuntu 18.04 05 new upstream 0.90

whoops... build log for Power ** Attachment added: "buildlog_ubuntu-bionic-ppc64el.ledmon_0.90-1_BUILDING.txt.gz" https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1760937/+attachment/5109625/+files/buildlog_ubuntu-bionic-ppc64el.ledmon_0.90-1_BUILDING.txt.gz -- You received this bug

[Bug 1760937] Re: [Feature Freeze Exception]Update Ledmon in Ubuntu 18.04 05 new upstream 0.90

Build Log for armhf ** Attachment added: "buildlog_ubuntu-bionic-armhf.ledmon_0.90-1_BUILDING.txt.gz" https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1760937/+attachment/5109624/+files/buildlog_ubuntu-bionic-armhf.ledmon_0.90-1_BUILDING.txt.gz -- You received this bug notification

[Bug 1760937] Re: [Feature Freeze Exception]Update Ledmon in Ubuntu 18.04 05 new upstream 0.90

Build Log for arm64 ** Attachment added: "buildlog_ubuntu-bionic-arm64.ledmon_0.90-1_BUILDING.txt.gz" https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1760937/+attachment/5109623/+files/buildlog_ubuntu-bionic-arm64.ledmon_0.90-1_BUILDING.txt.gz -- You received this bug notification

[Bug 1760937] Re: [Feature Freeze Exception]Update Ledmon in Ubuntu 18.04 05 new upstream 0.90

Build log for s390x ** Attachment added: "buildlog_ubuntu-bionic-s390x.ledmon_0.90-1_BUILDING.txt.gz" https://bugs.launchpad.net/ubuntu/+source/ledmon/+bug/1760937/+attachment/5109618/+files/buildlog_ubuntu-bionic-s390x.ledmon_0.90-1_BUILDING.txt.gz -- You received this bug notification

[Bug 1760937] Re: [Feature Freeze Exception]Update Ledmon in Ubuntu 18.04 05 new upstream 0.90

Build log for Power -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760937 Title: [Feature Freeze Exception]Update Ledmon in Ubuntu 18.04 05 new upstream 0.90 To manage notifications about this

[Bug 1760937] Re: [Feature Freeze Exception]Update Ledmon in Ubuntu 18.04 05 new upstream 0.90

** Description changed: Please update ledmon in Bionic to the latest upstream version 0.90. + 0.90 is necessary as the updates to ledmon enable monitoring of Intel + VROC[1] (Virtual Raid on CPU) and RSTe[2] (Rapid Storage Technologies + enterprise) by enabling the use of the drive LEDs to

[Bug 1757191] Re: Intel NICs not properly reporting link speed in SysFS in Xenial

It looks like this happened perhaps sometime between 4.10 and 4.13: 4.4.0-112: https://certification.canonical.com/hardware/201802-26096/submission/127640/ Driver: ixgbe (ver: 4.2.1-k) Shows proper speed for both ports 4.10.0-42:

[Bug 1760937] Re: [Feature Freeze Exception]Update Ledmon in Ubuntu 18.04 05 new upstream 0.90

Install Log: Reading package lists... Building dependency tree... Reading state information... The following package was automatically installed and is no longer required: grub-pc-bin Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: libsgutils2-2

[Bug 1760937] [NEW] [Feature Freeze Exception]Update Ledmon in Ubuntu 18.04 05 new upstream 0.90

Public bug reported: Please update ledmon in Bionic to the latest upstream version 0.90. Currently, ledmon in Bionic is version 0.79-2. This is pulled from Debian[1] however the debian package is grossly out of date and the Debian maintainer has been radio silent since last year. Attempts to

[Bug 1760937] Re: [Feature Freeze Exception]Update Ledmon in Ubuntu 18.04 05 new upstream 0.90

buildlog (built in a PPA) ** Attachment added: "buildlog_ubuntu-bionic-amd64.ledmon_0.90-1_BUILDING.txt.gz" https://bugs.launchpad.net/ubuntu/+bug/1760937/+attachment/5100159/+files/buildlog_ubuntu-bionic-amd64.ledmon_0.90-1_BUILDING.txt.gz -- You received this bug notification because you

[Bug 1760937] Re: [Feature Freeze Exception]Update Ledmon in Ubuntu 18.04 05 new upstream 0.90

Changelog (Note, there is no CHANGES in the source prior to this release (0.79 does not have this file) ** Attachment added: "CHANGELOG.md" https://bugs.launchpad.net/ubuntu/+bug/1760937/+attachment/5100160/+files/CHANGELOG.md -- You received this bug notification because you are a member

[Bug 1760937] Re: [Feature Freeze Exception]Update Ledmon in Ubuntu 18.04 05 new upstream 0.90

Testing: I've tested only installation of the package. Functional testing performed/validated by an engineer at Intel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760937 Title: [Feature Freeze

[Bug 1760651] Re: Please add package for invm-frameworks

Hold off on this for now. It's not necessary currently to get the NVDIMM support in, and there's a good chance this build dependency will disappear soon anyway. ** Changed in: ubuntu Importance: Undecided => Wishlist ** Summary changed: - Please add package for invm-frameworks + [Feature]

[Bug 1760651] [NEW] Please add package for invm-frameworks

Public bug reported: IN order to build ipxdimm_sw (LP: #1752378), there is a build dependency on invm-frameworks. The source can be found here: https://github.com/intel/invm-frameworks >From the ipxdimm_sw page (https://github.com/intel/ixpdimm_sw): Build Linux Kernel 4.12 or newer is

[Bug 1746666] Re: lspci fails with 'Error reading sysfs label: Operation not permitted'

Michael, can you verify and handle the bug appropriately? ** Changed in: dellserver Assignee: Jeff Lane (bladernr) => Michael Reed (mreed8855) ** Tags added: tpp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. ht

[Bug 1757191] Re: Intel NICs not properly reporting link speed in SysFS in Xenial

Hi Joeseph, I got the tester to try 4.16 and the tests still fail for the same reason. This is the test output indicating that /sys/class/net/DEVICENAME/speed still reports a -1 for the second port. ERROR:root:Detected link speed (-1) is lower than detected max speed (1) ERROR:root:Check

[Bug 1757217] Re: Behaviour change in reading /proc/modules could cause issues in userspace tools

Hi Joeseph, I tried 4.15.12 mainline and it also does not have the null reference problem: ubuntu@xwing:~$ uname -r 4.15.12-041512-generic ubuntu@xwing:~$ cat /proc/modules |grep multipath multipath 16384 0 - Live 0x ubuntu@xwing:~$ sudo cat /proc/modules |grep multipath

[Bug 1731382] Re: [needs-packaging] [Feature] DPTF binary tools

In Bionic at version 1.2 ** Changed in: intel Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731382 Title: [needs-packaging] [Feature] DPTF binary tools To

[Bug 1757217] Re: Behaviour change in reading /proc/modules could cause issues in userspace tools

I tried 4.16 and the behaviour there seems to follow the old experiences: ubuntu@xwing:~$ uname -a Linux xwing 4.16.0-041600rc6-generic #201803182230 SMP Mon Mar 19 02:32:18 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ubuntu@xwing:~$ cat /proc/modules |grep megaraid megaraid_sas 139264 2 - Live

[Bug 1757217] [NEW] Behaviour change in reading /proc/modules could cause issues in userspace tools

Public bug reported: This was discovered while investigating tracebacks in the cert suite. We have a script that parses /proc/modules and returns the information in a more human-readable format as part of the info gathering we do during cert testing. On 4.13 and older kernels, this script was

[Bug 1757143] Re: /proc/modules has Null references causing python parsing issues

I'm going to go ahead and mark the kernel task as invalid as the workaround is to read /proc/modules as root. ** Merge proposal linked: https://code.launchpad.net/~bladernr/plainbox-provider-resource/+git/plainbox-provider-resource/+merge/341752 ** Changed in: plainbox-provider-checkbox

[Bug 1757143] Re: /proc/modules has Null references causing python parsing issues

After chatting with xnox on IRC, he discovered that the output of catting /proc/modules in 4.15 now depends on who is doing the catting. So `cat /proc/modules` as a normal user will return null references while `sudo cat /proc/modules` will return the actual memory offsets, accurately. For

[Bug 1757143] Re: Problem with plainbox-provider while running canonical-certification-server on 18.04 / s390x

esource-generic/bin/module_resource", line 49, in get_module "offset": int(offset, 16)} ValueError: invalid literal for int() with base 16: '0x' result file is attached to the ticket, as well as the console log ... ** Changed in: plainbox-provider-checkbox (Ubuntu)

[Bug 1757143] Re: Problem with plainbox-provider while running canonical-certification-server on 18.04 / s390x

Ahhh, thanks Frank. I was a bit confused initially :) Frank, could you also add a dump of /proc/modules to this bug? @xnox, this is a traceback occurring in a script in the certification suite. This bug is not an s390x issue, but more one involving the /proc/modules file on 18.04 and our

[Bug 1757191] Re: Intel NICs not properly reporting link speed in SysFS in Xenial

** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757191 Title: Intel NICs not properly reporting link speed in SysFS in Xenial To manage notifications

[Bug 1757191] [NEW] Intel NICs not properly reporting link speed in SysFS in Xenial

Public bug reported: This was discovered during certification testing of 16.04.4 (I've now seen this behaviour at least 2 times) A system under test has a 2 port Intel X550 NIC (10Gb) Udev reports the NIC as this: Category: NETWORK Interface: enp94s0f0 Product: Ethernet Controller 10G X550T

[Bug 1757143] Re: Problem with plainbox-provider while running canonical-certification-server on 18.04 / s390x

Frank, Are you able to run the command directly from the shell? Does it produce any output at all other than the traceback? THe command to run is: /usr/lib/plainbox-provider-resource-generic/bin/module_resource ** Changed in: plainbox-provider-checkbox (Ubuntu) Importance: Undecided => High

[Bug 1752687] Re: Quanta D52B-1U unable to PXE-boot in EFI mode

I got into the system for a bit and tried forcing it to PXE off of each NIC, both cases resulted in the same thing... PXE request for bootx64.efi is made (and apparently succeeds), and then request for grubx64.efi happens and we eventually get dumped to a grub prompt. I did notice this, though,

[Bug 1752687] Re: Quanta D52B-1U unable to PXE-boot in EFI mode

Rod said this might be critical, so I'll add it for reference... >From what I could tell in rackd.log, every EFI boot always comes from a8:1e:84:f2:96:c6 and every BIOS PXE boot comes from a8:1e:84:f2:96:c5. rackd.log:2018-03-01 12:32:26 provisioningserver.rackdservices.tftp: [info]

[Bug 1752378] [NEW] Please add Userspace Packages for NVDIMM support

Public bug reported: The support for Intel NVDIMM technology requires both kernel and userspace components. The kernel components have landed in 4.15 and will be available in Bionic. In order for users to take advantage of NVDIMMs in their deployments, the following userspace packages are also

[Bug 1752182] Re: Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes

This is a feature request, logs for debugging are not necessary. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes + [Feature]Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA

[Bug 1752182] Re: Update Ubuntu 18.04 lpfc FC driver with 32/64GB HBA support and bug fixes

Moved this to a kernel bug as these are driver patches that go into the kernel, not the open-iscsi package. ** Package changed: open-iscsi (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

Re: [Bug 1711203] Re: Deployments fail when Secure Boot enabled

On Thu, Feb 22, 2018 at 6:28 PM, Steve Langasek <steve.langa...@canonical.com> wrote: > On Thu, Feb 22, 2018 at 11:06:51PM -0000, Jeff Lane wrote: >> > Is /efi/ubuntu/grubx64.efi on your EFI System Partition definitely the >> > Canonical-signed image from grub-efi-amd6

[Bug 1711203] Re: Deployments fail when Secure Boot enabled

> Is /efi/ubuntu/grubx64.efi on your EFI System Partition definitely the > Canonical-signed image from grub-efi-amd64-signed? I presume so? dpkg says it is: ubuntu@xwing:/boot/efi/EFI/ubuntu$ dpkg -S grubx64.efi grub-efi-amd64-signed: /usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed That's

[Bug 1711203] Re: Deployments fail when Secure Boot enabled

Can we please verify that with one of the original failing systems (Cisco UCS C-240 M4) as well? Because that supermicro system works, my Lenovo fails even with the workaround (comments #48 and #49). Unless I somehow mangled the workaround (see comment #48) and should re- try with slightly

[Bug 1751111] Re: [Bionic] Unable to deploy BIonic via MAAS due to kernel dependency issues

Marking this as Invalid. I've tried a few more times and have been unable to reproduce this myself, so I'm going to chalk it up to "incompatible bit-registration operators" (Per the BOFH excuses generator). If this happens again, I'll revisit it at that time, but for now, the issues seem

[Bug 1711203] Re: Deployments fail when Secure Boot enabled

Now, at this point, I'm stuck unbooted on the initial post-deployment reboot. So I reset the node by hand (poked the reset button) and disabled SecureBoot in the config and rebooted it again. This time, the node booted, pxe booted, got the edict to boot local, and successfully booted locally.

[Bug 1711203] Re: Deployments fail when Secure Boot enabled

MAAS version: 2.3.0 (6434-gd354690-0ubuntu1~16.04.1) This is my observation on a Lenovo RS140 with workaround enabled from comment #36: Also, to be sure it's not something we've injected, I am using the default curtin_userdata, NOT our customized cert one. 1: edit:

[Bug 1751111] [NEW] [Bionic] Unable to deploy BIonic via MAAS due to kernel dependency issues

Public bug reported: I'm trying to deploy Bionic on a MAAS node today and this is failing with the following dependency errors in the logs. The node in question is booting in EFI mode with Secure Boot enabled. curtin: Installation started. (17.1-11-ga4c9636b-0ubuntu1~16.04.1) third party

[Bug 1711203] Re: Deployments fail when Secure Boot enabled

and Xenial ** Attachment added: "grub-fail-xenial.log" https://bugs.launchpad.net/maas/+bug/1711203/+attachment/5056017/+files/grub-fail-xenial.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1711203] Re: Deployments fail when Secure Boot enabled

Just as an update, this is still an issue with Grub in Bionic... ** Attachment added: "grub-fail-bionic.log" https://bugs.launchpad.net/maas/+bug/1711203/+attachment/5056013/+files/grub-fail-bionic.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1749774] [NEW] include fwupd packages in Server Seed

Public bug reported: fwupd is the closest we have to a standard mechanism currently for doing in-band firmware updates in a vendor agnostic way. As long as the vendors provide firmware blobs in an appropriately formatted package, fwupd (or fwupdate) can install those firmware blobs from within

[Bug 1711203] Re: Deployments fail when Secure Boot enabled

Hi Matthieu, Any update on this? I'm also getting reports on this same issue from one of the hardware partners as well who is unable to deploy nodes and perform cert testing while Secure Boot is enabled. ** Tags added: blocks-hwcert-server -- You received this bug notification because you are

[Bug 1746085] [NEW] tp-smapi-dkms 0.41-1: tp-smapi kernel module failed to build

*** This bug is a duplicate of bug 1744891 *** https://bugs.launchpad.net/bugs/1744891 Public bug reported: This failed... it caused a crash. I'm being inundated with offers to file the bug, so I'm filing the bug. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tp-smapi-dkms

[Bug 1437024] Re: Failure to PXE-boot from secondary NIC

This is a three year old bug that is still causing issues when booting certain systems in MAAS. My understanding is that this is fixable/fixed in Grub2 upstream (per Andres comments), so what do we need to do to fix this in 14.04 and 16.04? I presume 18.04 won't be affected... is that true?

[Bug 1594913] Re: Checkbox's test hangs when using the Back button

Is this still happening with the latest Checkbox packages? ** Changed in: checkbox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594913 Title: Checkbox's

[Bug 1675091] Re: Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev

** Package changed: checkbox (Ubuntu) => checkbox-support (Ubuntu) -- 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

[Bug 1492535] Re: Can't save/upload the results. 'output_file' parameter lacking default value

Checkbox was removed from Ubuntu installs and this is now out of scope. ** Changed in: checkbox (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1492535

[Bug 1594918] Re: checkbox should show what equipment is required

Setting to invalid, this is no longer in scope. ** Changed in: checkbox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594918 Title: checkbox should show

[Bug 980052] Re: Checkbox: Using wrong language for welcome screen when locale and keyoard layout don't match

This should have been set to Wont Fix along with the Legacy task. ** Changed in: checkbox (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980052 Title:

[Bug 1243315] Re: launchpad misidentifies % as string formatting code

Setting to Wont Fix as checkbox is no longer part of the desktop install and this is now out of scope. ** Changed in: checkbox (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1184061] Re: checkbox does not accept my valid (for everything else) password

Checkbox in this for no longer exists, so I'm closing this. The Next Gen version does not have this problem. ** Changed in: checkbox (Ubuntu) Status: Confirmed => Incomplete ** Changed in: checkbox (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification

[Bug 1226581] Re: No confirmation on submission of System Testing Results report

Marking invalid, System Testing no longer exists in Ubuntu. ** Changed in: checkbox (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1226581 Title: No

[Bug 1539989] Re: System Testing doesn't work, as well audio, recording and DVD player.

Closing, this is no longer in scope (as checkbox has been removed from Ubuntu installs) ** Changed in: checkbox (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

Re: [Bug 30910] Re: Hardware Database not browseable

On Tue, Nov 28, 2017 at 9:54 AM, Kip Warner wrote: > I agree with the concerns of some of those above. If the hardware > database is no longer maintained, closing the bug as a wishlist is less > than ideal because it doesn't actually address the OP's original > concern. But

[Bug 30910] Re: Hardware Database not browseable

@Tero As Adam indicated, hwdb no longer exists and hasn't for some time. The bug can not and will not ever be resolved as none of the component parts (especially the projects the duplicates were filed against) exist any longer. They have either been abandoned, or transitioned to newer projects.

[Bug 30910] Re: Hardware Database not browseable

@Tero As Adam indicated, hwdb no longer exists and hasn't for some time. The bug can not and will not ever be resolved as none of the component parts (especially the projects the duplicates were filed against) exist any longer. They have either been abandoned, or transitioned to newer projects.

[Bug 527972] Re: [Lucid Alpha 3] usb-creator.exe does not accept ISO selection on Windows XP system

** Changed in: usb-creator (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/527972 Title: [Lucid Alpha 3] usb-creator.exe does not accept ISO selection

[Bug 494563] Re: Lucid "Free Software Only" fails to restart after installation.

** Changed in: ubiquity (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/494563 Title: Lucid "Free Software Only" fails to restart after installation.

[Bug 30910] Re: Hardware Database not browseable

** Changed in: launchpad Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/30910 Title: Hardware Database not browseable To manage notifications about this

[Bug 1729878] Re: stress-ng triggering oomkiller running brk and stack stressors on all arches.

** Tags added: hwcert-server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729878 Title: stress-ng triggering oomkiller running brk and stack stressors on all arches. To manage notifications

[Bug 1729878] Re: stress-ng triggering oomkiller running brk and stack stressors on all arches.

Because of the above, I've re-opened the kernel tasks :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729878 Title: stress-ng triggering oomkiller running brk and stack stressors on all arches.

[Bug 1729878] Re: stress-ng triggering oomkiller running brk and stack stressors on all arches.

I'm not able to recreate this on a smaller generic amd64 machine: ubuntu@xwing:~$ free totalusedfree shared buff/cache available Mem:3930172 133912 33192006124 477060 3500044 Swap: 100040060 0 100040060

[Bug 1729878] Re: stress-ng triggering oomkiller running brk and stack stressors on all arches.

I'm still able to trigger problems with the "stack" stressor on the Xeon Phi... ubuntu@lalande:~$ sudo ./memory_stress_ng Total memory is 63 GiB Constant run time is 300 seconds per stressor Variable run time is 930 seconds per stressor Estimated total run time is 20 minutes Running stress-ng

[Bug 1729878] Re: stress-ng triggering oomkiller running brk and stack stressors on all arches.

Also retried on amd64 and the effect was the same: ubuntu@xwing:~$ free -lm totalusedfree shared buff/cache available Mem: 3838 1203601 0 1153510 Low: 3838 2363601 High:

[Bug 1729878] Re: stress-ng triggering oomkiller running brk and stack stressors on all arches.

Given that, I'm marking the kernel tasks as invalid as this appears to be stress-ng being over aggressive. MAAS deployments (and I presume server installs in general) only provide about 4 - 8GB swap max in a swap file created in the root filesystem (no swap partition anymore). It is not

[Bug 1729878] Re: stress-ng triggering oomkiller running brk and stack stressors on all arches.

So I did this on 4.4 on ppc64le with 32GB RAM and 96GB Swap: ubuntu@entei:~$ free -lm totalusedfree shared buff/cache available Mem: 32565 656 30603 21304 30503 Low: 325651961 30603 High:

[Bug 1729878] Re: stress-ng triggering oomkiller running brk and stack stressors on all arches.

Ok, I've narrowed it down to the brk and stack stressors in stress-ng. I've recreated this on amd64, ppc64el and s390x across 4.4, 4.10 and 4.13 kernels. Stress-NG reports the tests as successful so I guess now the only thing remaining is to confirm that hitting OOM killer is expected behaviour

[Bug 1729878] Re: stress-ng triggering oomkiller running brk and stack stressors on all arches.

** Summary changed: - stress-ng triggering call-traces on s390x z/VM instances + stress-ng triggering oomkiller running brk and stack stressors on all arches. ** Also affects: stress-ng Importance: Undecided Status: New -- You received this bug notification because you are a member

[Bug 1729878] Re: stress-ng triggering call-traces on s390x z/VM instances

Ok, so a little bit further. This seems to be that stress-ng is triggering OOMkiller which I'm not sure it should be, unless it's just really writing a LOT of data to memory. My setup has been the same on all architectures and I've seen the same behaviour on Artful deployments on amd64 (Xeon

[Bug 1729878] Re: stress-ng triggering call-traces on s390x z/VM instances

The call that invokes stress-ng looks like this: timeout -s 14 $end_time stress-ng -k --aggressive --verify --timeout $runtime --$1 0 Where $end_time is the max time before killing stress-ng IF stress-ng runs longer than the --timeout value. $1, is the stressor invoked, and as I said above, we

Re: [Bug 1729878] Re: stress-ng triggering call-traces on s390x z/VM instances

So over the weekend, I retried with 4.14.0-041400rc6-generic (since rc7 was not successfully built when I tried this). This too ended with call traces in the kernel log after runs of stress- ng. I only ran our memory stress and system-wide CPU stress tests, both tests indicated that they passed

Re: [Bug 1729878] Re: stress-ng triggering call-traces on s390x z/VM instances

On Fri, Nov 3, 2017 at 1:13 PM, Joseph Salisbury wrote: > Do you know which prior kernels did not exhibit this bug? Was it 4.12 > or earlier? I "think" it happened with 4.10 as well, but I'm not positive, I ran some tests before realizing I was still on 17.04 and

[Bug 1729878] Re: stress-ng triggering call-traces on s390x z/VM instances

Fix your bot, guys... it tells me logs are missing and to run apport- collect which just collects the exact same logs ubuntu-bug collected the first time. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of

[Bug 1729878] WifiSyslog.txt

apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1729878/+attachment/5003086/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729878

[Bug 1729878] UdevDb.txt

apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1729878/+attachment/5003085/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729878 Title:

[Bug 1729878] JournalErrors.txt

apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1729878/+attachment/5003080/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1729878] ProcInterrupts.txt

apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1729878/+attachment/5003083/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1729878] ProcModules.txt

apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1729878/+attachment/5003084/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729878

[Bug 1729878] ProcCpuinfo.txt

apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1729878/+attachment/5003081/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729878

[Bug 1729878] ProcCpuinfoMinimal.txt

apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1729878/+attachment/5003082/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1729878] CurrentDmesg.txt

apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1729878/+attachment/5003079/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1729878] Re: stress-ng triggering call-traces on s390x z/VM instances

apport information ** Tags added: apport-collected ** Description changed: During regression testing on a z/VM instance, I noticed call traces being dumped to dmesg that seem to be related to stress-ng. The stress-ng invocation we're using is: stress-ng --aggressive --verify

[Bug 1729878] Re: stress-ng triggering call-traces on s390x z/VM instances

I'm also not sure why we're hitting the OOM killer either, the memory config is light, but not light enough that we'd trigger this sort of thing on other systems, perhaps its s390x specific: ubuntu@hwe0008:~$ free -m totalusedfree shared buff/cache available

[Bug 1729878] Re: stress-ng triggering call-traces on s390x z/VM instances

It's possible these are just OOMkiller related, but the first few call traces seem centered around snapd and I don't notice any OOMKiller messages until towards the end of the dmesg log. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1729878] [NEW] stress-ng triggering call-traces on s390x z/VM instances

Public bug reported: During regression testing on a z/VM instance, I noticed call traces being dumped to dmesg that seem to be related to stress-ng. The stress-ng invocation we're using is: stress-ng --aggressive --verify --timeout $runtime \ --metrics-brief --tz

[Bug 1437024] Re: Failure to PXE-boot from secondary NIC

@cyphermox, any update on this? I believe we have run into this in the field as well with a customer lab doing certification testing for 16.04.3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1437024

[Bug 1533721] Re: Ethtool didn't support link speed 25Gb 56Gb 100Gb 200Gb

This is over a year and a half old at this point. IS there a status update for this issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533721 Title: Ethtool didn't support link speed 25Gb 56Gb

[Bug 1716492] Re: maas-dns floods syslog by reloading all zones every 2 seconds

** Tags added: hwcert-server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716492 Title: maas-dns floods syslog by reloading all zones every 2 seconds To manage notifications about this bug go

[Bug 1716498] Re: maas reloads bind9 every 2 seconds, bind keeps becoming unresponsive

*** This bug is a duplicate of bug 1711700 *** https://bugs.launchpad.net/bugs/1711700 ** Tags added: hwcert-server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716498 Title: maas reloads

[Bug 1716498] [NEW] maas reloads bind9 every 2 seconds, bind keeps becoming unresponsive

Public bug reported: On the maas server, bind is being reloaded by MAAS every 2 seconds. This has several detrimental effects: 1: Bind becomes unresponsive and because of this name resolution on both the MAAS server and all nodes stops, and things break 2: Syslog is flooded by all the

[Bug 1716492] [NEW] maas-dns floods syslog by reloading all zones every 2 seconds

Public bug reported: bind is reloading every zone every 2 - 3 seconds with a new serial number. It basically updates every zone, reloads, then updates every zone and reloads again. These lines are from syslog over 5 minutes showing the reload message for just one zone:

[Bug 1711203] Re: Deployments fail when Secure Boot enabled

Set the Grub2 task to High to grab attention (and because it's at least a High, if not Critical, bug). My gut says this should be critical as it's blocking the deployment of systems from multiple vendors in multiple datacenter and lab environments anytime SecureBoot is enabled. ** Changed in:

[Bug 1437024] Re: Failure to PXE-boot from secondary NIC

@Mathieu is this a grub package only problem that can be SRU'd relatively easy, or is it something more complicated that will really require respins (and probably not be released until 16.04.4)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04

** Changed in: plainbox-provider-checkbox Status: Confirmed => Fix Committed -- 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 Power architecture for

[Bug 1711254] Re: 16.04.3 deployments include non-existent directories in $PATH

@Steve, I don't disagree, and I've already merged a patch to fix that issue in the cert suite. For context, what happens isn't a test case, but a resource that enumerates the binaries in the system so that the suite can validate requirements for executing the tests. e.g., it enumerates a list

[Bug 1711254] [NEW] 16.04.3 deployments include non-existent directories in $PATH

Public bug reported: Noticed this while doing regression testing on 16.04.3, and a number of customers have asked with concerns as well during their testing. I don't know exactly when this started, but we just started noticing it with 16.04.3 (4.10) but $PATH by default now includes several

[Bug 1704232] Re: Halt doesn't power system down

So tested it, it works in 4.12, and 4.10 and 4.8. something else is going on though, I think I was just not patient enough, but IMO the power off shouldn't take 5 minutes to accomplish. So where I thought the power off just wasn't happening, I was incorrect, it does happen, it just took several

<    2   3   4   5   6   7   8   9   10   11   >