[Bug 1247905] Re: update-grub fails in the face of overlayroot
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: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1247905/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816954] Re: Unable to show Info nor Set static IP during install
@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 during install To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1816954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1780867] Re: hostname unchangeable / some daemon changes and resets /etc/hostname
@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 Ubuntu. https://bugs.launchpad.net/bugs/1780867 Title: hostname unchangeable / some daemon changes and resets /etc/hostname To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1780867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736794] [NEW] iwlwifi driver for Intel 7260 crashing
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 linux-firmware xenial: 1.157.14 The wireless driver will crash at least daily, if not multiple times in a day depending on the machine. Swapping the chipset out for an Atheros works just fine. I have followed the many other bug reports related to this same chipset and they are either marked incomplete, refer to hardware we aren't running or have been marked as fix released. The latest linux-firmware did not resolve or change the behavior of the issue. Output from dmesg when the crash occurs: [Wed Dec 6 18:56:38 2017] iwlwifi :02:00.0: Queue 16 stuck for 1 ms. [Wed Dec 6 18:56:38 2017] iwlwifi :02:00.0: Current SW read_ptr 236 write_ptr 88 [Wed Dec 6 18:56:38 2017] [ cut here ] [Wed Dec 6 18:56:38 2017] WARNING: CPU: 3 PID: 0 at /build/linux-lts-xenial-CtFtiH/linux-lts-xenial-4.4.0/drivers/net/wireless/iwlwifi/pcie/trans.c:1552 iwl_trans_pcie_grab_nic_access+0xf5/0x100 [iwlwifi]() [Wed Dec 6 18:56:38 2017] Timeout waiting for hardware access (CSR_GP_CNTRL 0x) [Wed Dec 6 18:56:38 2017] Modules linked in: drbg ansi_cprng ctr ccm uvcvideo videobuf2_vmalloc btusb videobuf2_memops btrtl videobuf2_v4l2 btbcm btintel videobuf2_core hid_generic bluetooth v4l2_common videodev usbhid media arc4 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic iwlmvm mac80211 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass iwlwifi crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cfg80211 aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd snd_soc_rt5640 snd_soc_rl6231 snd_soc_ssm4567 serio_raw lpc_ich i915 shpchp binfmt_misc snd_hda_intel snd_soc_core snd_compress snd_hda_codec ac97_bus snd_seq_midi snd_seq_midi_event snd_rawmidi snd_pcm_dmaengine snd_hda_core snd_hwdep snd_pcm 8250_fintek snd_seq video snd_seq_device snd_timer drm_kms_helper snd elan_i2c 8250_dw drm dw_dmac i2c_hid hid dw_dmac_core mei_me fb_sys_fops syscopyarea snd_soc_sst_acpi i2c_designware_platform mac_hid sysfillrect spi_pxa2xx_platform mei i2c_designware_core soundcore acpi_pad sysimgblt acpi_als kfifo_buf industrialio lp parport igb psmouse ahci e1000e i2c_algo_bit libahci dca ptp pps_core fjes sdhci_acpi sdhci [Wed Dec 6 18:56:38 2017] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.4.0-101-generic #124~14.04.1-Ubuntu [Wed Dec 6 18:56:38 2017] Hardware name: To be filled by O.E.M. To be filled by O.E.M./CRESCENTBAY, BIOS 5.6.5 12/14/2016 [Wed Dec 6 18:56:38 2017] 88012dd83d00 813dfc6c 88012dd83d48 [Wed Dec 6 18:56:38 2017] c07ca6e0 88012dd83d38 8107ea26 8800ca47 [Wed Dec 6 18:56:38 2017] 8800ca4735f0 88012dd83dd8 880128108bc0 [Wed Dec 6 18:56:38 2017] Call Trace: [Wed Dec 6 18:56:38 2017][] dump_stack+0x63/0x87 [Wed Dec 6 18:56:38 2017] [] warn_slowpath_common+0x86/0xc0 [Wed Dec 6 18:56:38 2017] [] warn_slowpath_fmt+0x4c/0x50 [Wed Dec 6 18:56:38 2017] [] ? iwl_read32+0x1f/0x90 [iwlwifi] [Wed Dec 6 18:56:38 2017] [] iwl_trans_pcie_grab_nic_access+0xf5/0x100 [iwlwifi] [Wed Dec 6 18:56:38 2017] [] iwl_trans_pcie_read_mem+0x2f/0xa0 [iwlwifi] [Wed Dec 6 18:56:38 2017] [] iwl_pcie_txq_stuck_timer+0xd8/0x390 [iwlwifi] [Wed Dec 6 18:56:38 2017] [] ? intel_pstate_timer_func+0x2db/0x3a0 [Wed Dec 6 18:56:38 2017] [] ? iwl_pcie_enqueue_hcmd+0xa90/0xa90 [iwlwifi] [Wed Dec 6 18:56:38 2017] [] call_timer_fn+0x35/0x130 [Wed Dec 6 18:56:38 2017] [] ? iwl_pcie_enqueue_hcmd+0xa90/0xa90 [iwlwifi] [Wed Dec 6 18:56:38 2017] [] run_timer_softirq+0x20e/0x2c0 [Wed Dec 6 18:56:38 2017] [] __do_softirq+0xdd/0x290 [Wed Dec 6 18:56:38 2017] [] irq_exit+0x95/0xa0 [Wed Dec 6 18:56:38 2017] [] smp_apic_timer_interrupt+0x42/0x50 [Wed Dec 6 18:56:38 2017] [] apic_timer_interrupt+0x82/0x90 [Wed Dec 6 18:56:38 2017][] ? cpuidle_enter_state+0xd8/0x250 [Wed Dec 6 18:56:38 2017] [] ? cpuidle_enter_state+0xb4/0x250 [Wed Dec 6 18:56:38 2017] [] cpuidle_enter+0x17/0x20 [Wed Dec 6 18:56:38 2017] [] call_cpuidle+0x32/0x60 [Wed Dec 6 18:56:38 2017] [] ? cpuidle_select+0x13/0x20 [Wed Dec 6 18:56:38 2017] [] cpu_startup_entry+0x289/0x350 [Wed Dec 6 18:56:38 2017] [] start_secondary+0x149/0x170 [Wed Dec 6 18:56:38 2017] ---[ end trace ad9659e8d87e5230 ]--- [Wed Dec 6 18:56:38 2017] iwl data: : b0 68 00 00 14 00 00 00 b8 8a 5c 00 00 00 00 00 .h\. [Wed Dec 6 18:56:38 2017] iwlwifi :02:00.0: FH TRBs(0) = 0x5a5a5a5a [Wed Dec 6 18:56:38 2017] iwlwifi :02:00.0: FH TRBs(1) = 0x5a5a5a5a [Wed Dec 6 18:56:38 2017] iwlwifi :02:00.0: FH TRBs(2) = 0x5a5a5a5a [Wed Dec 6 18:56:38 2017] iwlwifi
[Bug 1565275] Re: [SRU] Add support to import multiple keys
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: https://bugs.launchpad.net/ssh-import-id/+bug/1565275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed
$ 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 major problems with Ubuntu if it is installed for any reason. I feel these problems should be fixed in the dbus-user-session package or in the packages it affects (gnome-keyring) when installed. -- 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 unlocked on xenial when dbus-user-session is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed
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. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on xenial when dbus-user-session is installed To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652270] Re: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2
@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 somewhere. Bottom line, Ubuntu server on the Raspberry Pi 3 is not a viable option for anyone at this point in time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652270 Title: Could not boot into RPi3 with kernel 4.4.0-1038-raspi2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1652270/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed
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 when dbus-user-session is installed -- 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 unlocked on xenial when dbus-user-session is installed To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
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 Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
@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 --components=ssh Some people put a new gnome-keyring startup file in ~/.config/autostart/ Remove that. Then a complete reboot. -- 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 unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
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. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1689825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
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 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 unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1689825] Re: gnome-keyring not unlocked on boot
** 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 unlocked on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1689825] Re: ubuntu 16.04 Chrome and Chromium asking for keyring.
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 https://askubuntu.com/questions/912275/chrome-firefox-chromium-vivaldi- starts-up-slow-and-greys-out-online-passwords ** Description changed: 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 days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "-- login" as a parameter. Then the "login" section shows up which I'm able - to unlock. From there chrome starts up instantly and with all of it's - sync and secure features functional. + to unlock. From there chrome starts up instantly but asks the following: + + Enter password to unlock your login keyring + The login keyring did not get unlocked when you logged into your computer + + After that, all of it's sync and secure features are functional. + + Starting google-chrome-stable from a command line at boot without + running the above workaround shows the following error messages: + + Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. + Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. + [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 + [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) -- 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: ubuntu 16.04 Chrome and Chromium asking for keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1689825] [NEW] ubuntu 16.04 Chrome and Chromium asking for keyring.
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 days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "-- login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly and with all of it's sync and secure features functional. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- 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: ubuntu 16.04 Chrome and Chromium asking for keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656112] Re: Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu failed: Invalid argument
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 with kvm_init_vcpu failed: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677337] Re: Mellanox Technologies MT27500 Family [ConnectX-3] no network connectivity
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 up and down seems to intermittently bring about the issue of not being able to ping the interfaces. I cannot seem to find a pattern of replicated it breaking or even resolving. Sometimes rebooting is required and even then, sometimes rebooting twice. Other times bringing up and down the 2 interfaces in some random pattern will allow both interfaces to be pinged. One scenario I can replicate is if both enP8p1s0 and enP8p1s0d1 are up and pingable, if I bring down enP8p1s0, both will become unpingable. Bringing enP8p1s0 back up does not resolve anything. Bringing enP8p1s0 up and then enP8p1s0d1 down will allow enP8p1s0 to be pingable. Bringing enP8p1s0d1 up does not make it become bootable. Only after bringing enP8p1s0 down, then back up, then bringing enP8p1s0d1 up will both become pingable. I do not think it is possible to have enP8p1s0d1 up and pingable by itself. It almost acts like a slave to enP8p1s0. -- 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677337] Re: Mellanox Technologies MT27500 Family [ConnectX-3] no network connectivity
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677337] Re: 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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677337] Re: 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 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677337] [NEW] 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 directly(no switch) fails. There's no traffic from tcpdump. linux-image-generic-hwe-16.04 4.8.0.44.16 fails mainline kernel 4.10.0-041000-generic fails mainline kernel 4.11.0-041100rc1-generic resolves the issue. Both the test server (ppc64le) and MAAS server(amd64) need the upgraded kernel to work. === 4.4.0-70-generic === lspci -v 0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family [ConnectX-3] Subsystem: IBM MT27500 Family [ConnectX-3] Flags: bus master, fast devsel, latency 0, IRQ 473 Memory at 3fe2 (64-bit, non-prefetchable) [size=1M] Memory at 2400 (64-bit, prefetchable) [size=128M] [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M] Capabilities: Kernel driver in use: mlx4_core Kernel modules: mlx4_core ethtool enP8p1s0 Settings for enP8p1s0: Supported ports: [ FIBRE ] Supported link modes: 1000baseKX/Full 1baseKX4/Full 1baseKR/Full 4baseCR4/Full 4baseSR4/Full 56000baseCR4/Full 56000baseSR4/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Advertised link modes: 1000baseKX/Full 1baseKX4/Full 1baseKR/Full 4baseCR4/Full 4baseSR4/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Link partner advertised link modes: 4baseCR4/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: Yes Speed: 4Mb/s Duplex: Full Port: Direct Attach Copper PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: d Wake-on: d Current message level: 0x0014 (20) link ifdown Link detected: yes dmesg [3.494435] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014) [3.494624] mlx4_core: Initializing 0008:01:00.0 [3.494760] mlx4_core 0008:01:00.0: Using 64-bit DMA iommu bypass [8.294713] mlx4_core 0008:01:00.0: PCIe link speed is 8.0GT/s, device supports 8.0GT/s [8.294897] mlx4_core 0008:01:00.0: PCIe link width is x8, device supports x8 [8.472682] mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.2-1 (Feb 2014) [8.472907] mlx4_en 0008:01:00.0: Activating port:1 [8.481531] mlx4_en: 0008:01:00.0: Port 1: Using 256 TX rings [8.481661] mlx4_en: 0008:01:00.0: Port 1: Using 8 RX rings [8.481694] mlx4_en: 0008:01:00.0: Port 1: frag:0 - size:1522 prefix:0 stride:1536 [8.481899] mlx4_en: 0008:01:00.0: Port 1: Initializing port [8.482320] mlx4_en 0008:01:00.0: registered PHC clock [8.485058] mlx4_en 0008:01:00.0: Activating port:2 [8.491716] mlx4_en: 0008:01:00.0: Port 2: Using 256 TX rings [8.491760] mlx4_en: 0008:01:00.0: Port 2: Using 8 RX rings [8.491791] mlx4_en: 0008:01:00.0: Port 2: frag:0 - size:1522 prefix:0 stride:1536 [8.503650] mlx4_en: 0008:01:00.0: Port 2: Initializing port [8.511021] mlx4_core 0008:01:00.0 enP8p1s0: renamed from eth0 [8.530146] mlx4_core 0008:01:00.0 enP8p1s0d1: renamed from eth1 === 4.11.0-041100rc1-generic === lspci -v 0008:01:00.0 Ethernet controller: Mellanox Technologies MT27500 Family [ConnectX-3] Subsystem: IBM MT27500 Family [ConnectX-3] Flags: bus master, fast devsel, latency 0, IRQ 473 Memory at 3fe2 (64-bit, non-prefetchable) [size=1M] Memory at 2400 (64-bit, prefetchable) [size=128M] [virtual] Expansion ROM at 3fe20010 [disabled] [size=1M] Capabilities: Kernel driver in use: mlx4_core Kernel modules: mlx4_core ethtool enP8p1s0 Settings for enP8p1s0: Supported ports: [ FIBRE ] Supported link modes: 1000baseKX/Full 1baseKX4/Full 1baseKR/Full 4baseCR4/Full 4baseSR4/Full 56000baseCR4/Full 56000baseSR4/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Advertised link modes: 1000baseKX/Full 1baseKX4/Full 1baseKR/Full 4baseCR4/Full 4baseSR4/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Link partner advertised link modes: 4baseCR4/Full Link partner advertised pause frame use: No Link partner advertised auto-negotiation: Yes Speed: 4Mb/s Duplex: Full Port: Direct Attach Copper PHYAD: 0
[Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04
** 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. https://bugs.launchpad.net/bugs/1573062 Title: memory_stress_ng failing for Power architecture for 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656112] Re: Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu failed: Invalid argument
** 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 kvm_init_vcpu failed: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656112] Re: Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu failed: Invalid argument
** 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, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) fails KVM guest cert test with kvm_init_vcpu failed: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675091] Re: Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev
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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/checkbox/+bug/1675091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675091] Re: 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 detected by udev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/checkbox/+bug/1675091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675091] [NEW] Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev
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
UdevadmParser.
ERROR: devices missing - udev showed 7 NETWORK devices, but NetworkManager saw
8 devices in ('Ethernet', 'Modem')
---[ Devices found by udev ]
Category: NETWORK
Interface: enP1p1s0f0
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.0
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f1
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.1
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f2
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.2
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f3
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.3
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP8p1s0d1
Product: MT27500 Family [ConnectX-3]
Vendor: Mellanox Technologies
Driver: mlx4_core (ver: 2.2-1)
Path: /devices/pci0008:00/0008:00:00.0/0008:01:00.0
Category: NETWORK
Interface: enP9p7s0f0
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.0
ID: [14e4:1657]
Subsystem ID: [14e4:1981]
Category: NETWORK
Interface: enP9p7s0f1
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.1
ID: [14e4:1657]
Subsystem ID: [14e4:1657]
--[ Devices found by Network Manager ]--
Category: Ethernet
Interface: enP1p1s0f3
IP: 10.20.30.54
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP9p7s0f0
IP: 10.20.30.52
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP9p7s0f1
IP: 10.20.30.53
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP8p1s0
IP: 10.20.30.5
Driver: mlx4_core (ver: 2.2-1)
State: Unmanaged
Category: Ethernet
Interface: enP1p1s0f0
IP: 10.20.30.56
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP8p1s0d1
IP: 10.20.30.6
Driver: mlx4_core (ver: 2.2-1)
State: Unmanaged
Category: Ethernet
Interface: enP1p1s0f1
IP: 10.20.30.57
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP1p1s0f2
IP: 10.20.30.55
Driver: tg3 (ver: Unknown)
State: Unmanaged
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-66-generic 4.4.0-66.87
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Mar 21 17:00 seq
crw-rw 1 root audio 116, 33 Mar 21 17:00 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Mar 22 15:59:40 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=a287c2bd-7e5a-488c-8921-5cf86aed177a ro
ProcLoadAvg: 5.79 2.74 1.02 1/1261 881
ProcLocks:
1: POSIX ADVISORY WRITE 4149 00:14:817 0 EOF
2: POSIX ADVISORY WRITE 1701 00:14:477 0 EOF
3: POSIX ADVISORY WRITE 4014 00:14:789 0 EOF
4: POSIX ADVISORY WRITE 4033 00:14:802 0 EOF
5: FLOCK ADVISORY WRITE 4012 00:14:798 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -1
ProcVersion: Linux version 4.4.0-66-generic (buildd@bos01-ppc64el-025) (gcc
version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #87-Ubuntu SMP Fri
Mar 3 15:30:20 UTC 2017
RelatedPackageVersions:
linux-restricted-modules-4.4.0-66-generic N/A
linux-backports-modules-4.4.0-66-generic N/A
linux-firmware1.157.8
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh
[Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04
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 stress-ng Version: 0.07.21-1~ppa ** Attachment added: "FAIL-2017-03-09-15-21-47.dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4837690/+files/FAIL-2017-03-09-15-21-47.dmesg -- 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 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/plainbox-provider-checkbox/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
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 (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
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: 1:2.5+dfsg-5ubuntu10.10 Version table: *** 1:2.5+dfsg-5ubuntu10.10 500 500 http://ppa.launchpad.net/ci-train-ppa-service/2502/ubuntu xenial/main ppc64el Packages 100 /var/lib/dpkg/status 1:2.5+dfsg-5ubuntu10.9 500 500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main ppc64el Packages 1:2.5+dfsg-5ubuntu10.6 500 500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main ppc64el Packages 1:2.5+dfsg-5ubuntu10 500 500 http://ports.ubuntu.com/ubuntu-ports xenial/main ppc64el Packages $ uname -a Linux fesenkov 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:30:20 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux -- 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: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
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: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640547] Re: stress-ng based disk tests failing
** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640547 Title: stress-ng based disk tests failing To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1640547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640547] Re: stress-ng based disk tests failing
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 kernel, colins changes to disk_stress_ng script PASS,2017-02-21-21-45-09,disk_stress_ng,01:43:45,4.4.0-63-generic-84-Ubuntu,0.07.16-1ppa1,128,31G,Stock stress-ng, stock kernel, colins changes to disk_stress_ng script PASS,2017-02-22-15-22-25,disk_stress_ng,01:44:35,4.4.0-64-generic-85-Ubuntu,0.07.16-1ppa1,128,31G,Stock stress-ng, stock kernel, colins changes to disk_stress_ng script PASS,2017-02-27-17-51-38,disk_stress_ng,01:51:26,4.4.0-64-generic-85-Ubuntu,0.07.21-1~ppa,128,31G,Fresh Deployment PASS,2017-02-27-20-04-49,disk_stress_ng,01:51:38,4.4.0-64-generic-85-Ubuntu,0.07.21-1~ppa,128,31G,fresh deployment PASS,2017-02-27-22-44-36,disk_stress_ng,01:54:38,4.4.0-64-generic-85-Ubuntu,0.07.21-1~ppa,128,31G,fresh deployment -- 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 this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1640547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
@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. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
@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 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: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
@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 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: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
** 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: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659929] Re: virtualization script does not support POWER8NVL
** 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: virtualization script does not support POWER8NVL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plainbox-provider-checkbox/+bug/1659929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659929] Re: virtualization script does not support POWER8NVL
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,
'qemu_extra_args': [
'-enable-kvm',
'-machine', 'pseries,usb=off',
'-cpu', 'POWER8',
],
--
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:
virtualization script does not support POWER8NVL
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plainbox-provider-checkbox/+bug/1659929/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659929] [NEW] virtualization script does not support POWER8NVL
Public bug reported: The KVM virtualization script /usr/lib/plainbox-provider- checkbox/bin/virtualization does not support Power8NVL cpu type. This is due to the script assuming POWER8 when passing qemu the parameters for a ppc architecture. This is related to the following bug. https://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 (leftyfb) ** Changed in: plainbox-provider-checkbox (Ubuntu) Status: New => Confirmed ** Changed in: plainbox-provider-checkbox (Ubuntu) Status: Confirmed => 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/1659929 Title: virtualization script does not support POWER8NVL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plainbox-provider-checkbox/+bug/1659929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
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 Ubuntu. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
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. https://bugs.launchpad.net/bugs/1656112 Title: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
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] scsi host2: ahci [3.864715] scsi host3: ahci [3.864781] ata1: SATA max UDMA/133 abar m2048@0x3fe28081 port 0x3fe280810100 irq 447 [3.864826] ata2: SATA max UDMA/133 abar m2048@0x3fe28081 port 0x3fe280810180 irq 447 [3.864871] ata3: SATA max UDMA/133 abar m2048@0x3fe28081 port 0x3fe280810200 irq 447 [3.864917] ata4: SATA max UDMA/133 abar m2048@0x3fe28081 port 0x3fe280810280 irq 447 [3.869801] [drm] platform has no IO space, trying MMIO [3.869832] [drm] AST 2400 detected [3.869863] [drm] Analog VGA only [3.869896] [drm] dram 163200 7 16 00c0 [3.869970] [TTM] Zone kernel: Available graphics memory: 267838144 kiB [3.870007] [TTM] Zone dma32: Available graphics memory: 2097152 kiB [3.870044] [TTM] Initializing pool allocator [3.870076] [TTM] Initializing DMA pool allocator [3.874823] fb: switching to astdrmfb from OFfb vga [3.874938] Console: switching to colour dummy device 80x25 [3.899718] nouveau 0002:01:00.0: enabling device (0140 -> 0142) [3.928774] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: c02ad0d4 [3.928774] [3.928776] CPU: 11 PID: 1118 Comm: systemd-udevd Not tainted 4.10.0-041000r -- 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: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656112] Re: Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
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 dangerous for raw images, write operations on block 0 will be restricted. Specify the 'raw' format explicitly to remove the restrictions. kvm_init_vcpu failed: Invalid argument Also, KVM does in fact work with SMT enabled on ppc64el in PowerNV mode. KVM does not work with SMT enabled on a guest in PowerKVM mode. I have just run the test on the Power S822LC (8335-GTA Non-Virtualized) in PowerNV mode with SMT enabled and the guest booted fine. That said, to limit variables, I will run the tests on the current server with SMT disabled for the duration of the troubleshooting. -- 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: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
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 when testing fstat stressor on ppc64el with virtual keyboard and mouse present To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1652132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1656112] [NEW] Power S822LC (8335-GTB) failes KVM guest cert test with kvm_init_vcpu failed: Invalid argument
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 virtualization is supported. I have tried with SMT enabled and disabled. I have tried the latest cloud image as well as previous onces we had saved. I have tried running the qemu- system-ppc64 command found below manually with the same error. The full output from the test is as follows: Executing KVM Test DEBUG:root:Starting KVM Test DEBUG:root:Cloud image location specified: http://10.1.10.2/cloud/xenial-server-cloudimg-ppc64el-disk1.img. DEBUG:root:Downloading xenial-server-cloudimg-ppc64el-disk1.img, from http://10.1.10.2 DEBUG:root:Creating cloud user-data DEBUG:root:Creating cloud meta-data I: -input-charset not specified, using utf-8 (detected in locale settings) Total translation table size: 0 Total rockridge attributes bytes: 331 Total directory bytes: 0 Path table size(bytes): 10 Max brk space used 0 183 extents written (0 MB) DEBUG:root:Attempting boot for:xenial-server-cloudimg-ppc64el-disk1.img DEBUG:root:Attaching Cloud config disk DEBUG:root:Using params:qemu-system-ppc64 -m 1024 -display none -nographic -net nic -net user,net=10.0.0.0/8,host=10.0.0.1,hostfwd=tcp::-:22 -enable-kvm -machine pseries,usb=off -cpu POWER8 -drive file=xenial-server-cloudimg-ppc64el-disk1.img,if=virtio -drive file=seed.iso,if=virtio INFO:root:Storing VM console output in /home/ubuntu/.cache/plainbox/sessions/canonical-certification-server-2017-01-12T22.19.34.session/CHECKBOX_DATA/virt_debug ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 22:18 seq crw-rw 1 root audio 116, 33 Jan 12 22:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 12 22:45:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 125f:312b A-DATA Technology Co., Ltd. Superior S102 Pro Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Bus 001 Device 002: ID 046b:ff01 American Megatrends, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=a7ce18b4-4614-485f-9346-b19b0415db3a ro fips=1 ProcLoadAvg: 0.03 0.02 0.08 1/1288 11017 ProcLocks: 1: POSIX ADVISORY WRITE 3709 00:14:665 0 EOF 2: POSIX ADVISORY WRITE 3593 00:14:655 0 EOF 3: POSIX ADVISORY WRITE 1658 00:14:376 0 EOF 4: FLOCK ADVISORY WRITE 3560 00:14:637 0 EOF 5: POSIX ADVISORY WRITE 3571 00:14:640 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-59-generic (buildd@bos01-ppc64el-029) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.4) ) #80-Ubuntu SMP Fri Jan 6 17:35:59 UTC 2017 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.959 GHz (cpu 79) max: 3.988 GHz (cpu 81) avg: 3.974 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug blocks-hwcert-server ppc64el uec-images xenial -- 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: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
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 names tar: /var/log/opal-elog: Cannot stat: No such file or directory tar: Exiting with failure status due to previous errors ...dpkg-query: no packages found matching linux . The dots go on forever -- 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 when testing fstat stressor on ppc64el with virtual keyboard and mouse present To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1652132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
** 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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652132 Title: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse
** 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: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652132] [NEW] Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present
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 and Garrison) where there is a virtual USB keyboard and mouse built into the BMC. >From lsusb(before crashing): Bus 001 Device 004: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard and Mouse Another openpower server(Briggs) has no virtual usb devices and does not experience the failure. Please see attached kern.log and dmesg output for further details. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- 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 when testing fstat stressor on ppc64el with virtual keyboard and mouse present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652132] Re: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse
** 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: Call trace when testing fstat stressor on ppc64el with virtual keyboard and mouse present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652132/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573062 Title: memory_stress_ng failing for Power architecture for 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573062 Title: memory_stress_ng failing for Power architecture for 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04
`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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573062 Title: memory_stress_ng failing for Power architecture for 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640547] Re: stress-ng based disk tests failing
@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 to Ubuntu. https://bugs.launchpad.net/bugs/1640547 Title: stress-ng based disk tests failing To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1640547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640547] Re: stress-ng based disk tests failing
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 http://ports.ubuntu.com/ubuntu-ports zesty/universe ppc64el Packages 100 /var/lib/dpkg/status 0.05.23-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/universe ppc64el Packages 0.05.23-1 500 500 http://ports.ubuntu.com/ubuntu-ports xenial/universe ppc64el Packages $ sudo stress-ng --sync-file 1 stress-ng: info: [2626] defaulting to a 86400 second run per stressor stress-ng: info: [2626] dispatching hogs: 1 sync-file stress-ng: info: [2626] cache allocate: using built-in defaults as unable to determine cache details stress-ng: info: [2626] cache allocate: default cache size: 2048K stress-ng: info: [2627] stress-ng-sync-file: this stressor is not implemented on this system: ppc64le Linux 4.4.0-51-generic stress-ng: info: [2626] successful run completed in 0.00s Mind you, this sync-file stressor is more of a red herring and isn't the cause of the system lockups. I have also found that this bug shows up on all 3 open power servers running petitboot that I have access to at the moment. If I had access to a Tuleta, I'm going to guess this would also affect that as well. I have a good feeling this is just like the memory test[0] (still not resolved). As of now, the stress_ng memory and disk tests both fail with really similar results (system/session lockup). [0] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062 -- 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 this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1640547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640547] Re: stress-ng based disk tests failing
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 1 * ** Error 1 reported on stressor sync-file!) * Running stress-ng xattr stressor for 240 seconds stress-ng: info: [16158] dispatching hogs: 160 xattr stress-ng: info: [16158] cache allocate: using built-in defaults as unable to determine cache details stress-ng: info: [16158] cache allocate: default cache size: 2048K stress-ng: info: [16158] successful run completed in 240.17s (4 mins, 0.17 secs) return_code is 0 *** ** stress-ng disk test failed; most recent error was 1 *** This was still running after I hit CTRL+C on the test to grab the logs: root 12102 1 0 Dec01 pts/100:00:00 stress-ng --aggressive --verify --timeout 240 --temp-path /tmp/disk_stress_ng_4788 -- 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 this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1640547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640547] Re: stress-ng based disk tests failing
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640547 Title: stress-ng based disk tests failing To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1640547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640547] Re: stress-ng based disk tests failing
** 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. https://bugs.launchpad.net/bugs/1640547 Title: stress-ng based disk tests failing To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1640547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640547] Re: stress-ng based disk tests failing
** 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. https://bugs.launchpad.net/bugs/1640547 Title: stress-ng based disk tests failing To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1640547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640547] Re: stress-ng based disk tests failing
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: stress-ng based disk tests failing To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1640547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640547] Re: stress-ng based disk tests failing
** 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 this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1640547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640547] Re: stress-ng based disk tests failing
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 /var/lib/dpkg/status 0.05.23-1ubuntu2 500 500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/universe ppc64el Packages 0.05.23-1 500 500 http://ports.ubuntu.com/ubuntu-ports xenial/universe ppc64el Packages Below it thesbottom of the console messages from running the test suite. Currently it is frozen in this state and cannot CTRL+C out of it. I can ssh in to other sessions. stress-ng: info: [18442] stress-ng-sync-file: this stressor is not implemented on this system: ppc64le Linux 4.4.0-47-generic stress-ng: info: [18441] stress-ng-sync-file: this stressor is not implemented on this system: ppc64le Linux 4.4.0-47-generic stress-ng: info: [18443] stress-ng-sync-file: this stressor is not implemented on this system: ppc64le Linux 4.4.0-47-generic stress-ng: info: [18444] stress-ng-sync-file: this stressor is not implemented on this system: ppc64le Linux 4.4.0-47-generic stress-ng: info: [18284] successful run completed in 240.03s (4 mins, 0.03 secs) return_code is 0 Running stress-ng xattr stressor for 240 seconds stress-ng: info: [18450] dispatching hogs: 160 xattr stress-ng: info: [18450] cache allocate: using built-in defaults as unable to determine cache details stress-ng: info: [18450] cache allocate: default cache size: 2048K stress-ng: info: [18450] successful run completed in 240.15s (4 mins, 0.15 secs) return_code is 0 *** ** stress-ng disk test failed; most recent error was 137 *** -- 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 this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1640547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640547] Re: stress-ng tests failing
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640547 Title: stress-ng tests failing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plainbox-provider-checkbox/+bug/1640547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640547] Re: stress-ng tests failing
** 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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640547] Re: Disk test fails on IBM Power S822LC (8335-GTB)
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640547 Title: Disk test fails on IBM Power S822LC (8335-GTB) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1640547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1640547] [NEW] Disk test fails on IBM Power S822LC (8335-GTB)
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 4560 seconds Running stress-ng aio stressor for 240 seconds stress-ng: info: [4305] dispatching hogs: 160 aio stress-ng: info: [4305] cache allocate: using built-in defaults as unable to determine cache details stress-ng: info: [4305] cache allocate: default cache size: 2048K stress-ng: info: [4305] successful run completed in 240.27s (4 mins, 0.27 secs) return_code is 0 Running stress-ng aiol stressor for 240 seconds stress-ng: info: [4917] dispatching hogs: 160 aio-linux stress-ng: info: [4917] cache allocate: using built-in defaults as unable to determine cache details stress-ng: info: [4917] cache allocate: default cache size: 2048K stress-ng: fail: [5002] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5012] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5020] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5018] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5019] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5013] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [4959] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5032] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5041] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5017] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5022] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5016] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5038] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5040] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5026] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5027] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5031] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5049] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5021] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5045] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5047] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5044] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5052] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5029] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5015] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5053] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5051] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5063] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5058] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5054] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5061] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5059] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5055] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5023] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5036] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5030] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5060] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5046] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5066] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5050] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail: [5048] stress-ng-aio-linux: io_setup failed, errno=1 (Operation not permitted) stress-ng: fail:
[Bug 1623652] [NEW] terminator crashed with SIGSEGV
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 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed Sep 14 16:17:52 2016 InstallationDate: Installed on 2014-03-23 (906 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140322) PackageArchitecture: all SourcePackage: terminator UpgradeStatus: Upgraded to xenial on 2016-08-10 (34 days ago) ** Affects: terminator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "_usr_share_terminator_terminator.1000.crash" https://bugs.launchpad.net/bugs/1623652/+attachment/4741154/+files/_usr_share_terminator_terminator.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1623652 Title: terminator crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/terminator/+bug/1623652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04
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 find out from the summary? All failed tests failed with a complete system hang. The only way to recover would be to reboot. ** Attachment added: "binacle.xml" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4740351/+files/binacle.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: memory_stress_ng failing for Power architecture for 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04
** 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: memory_stress_ng failing for Power architecture for 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04
** 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: memory_stress_ng failing for Power architecture for 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04
** 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: memory_stress_ng failing for Power architecture for 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04
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: memory_stress_ng failing for Power architecture for 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573062 Title: memory_stress_ng failing for Power architecture for 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615716] Re: VPN profile grayed out
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615716 Title: VPN profile grayed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1615716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615716] [NEW] VPN profile grayed out
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 DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Mon Aug 22 12:02:05 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-03-23 (883 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140322) IpRoute: default via 192.168.0.1 dev wlan0 proto static metric 600 10.0.2.0/24 dev lxcbr0 proto kernel scope link src 10.0.2.1 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.108 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-08-10 (11 days ago) modified.conffile..etc.dnsmasq.d.network-manager: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-08-07T19:56:59.679956 mtime.conffile..etc.dnsmasq.d.network-manager: 2014-06-30T11:51:24.816947 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.0connecting starting none enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615716 Title: VPN profile grayed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1615716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for Power architecture for 16.04
** 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. https://bugs.launchpad.net/bugs/1573062 Title: memory_stress_ng failing for Power architecture for 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
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 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
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. https://bugs.launchpad.net/bugs/1573062 Title: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
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" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4723527/+files/FAIL-2016-08-18-03-25-32.log -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
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 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
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 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
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 212131 30918 Swap: 8191 08191 ** Attachment added: "FAIL-2016-08-17-17-12-46.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4723090/+files/FAIL-2016-08-17-17-12-46.log -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
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 201000 259938 Swap: 8191 08191 ** Attachment added: "FAIL-2016-08-17-17-49-41.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4723088/+files/FAIL-2016-08-17-17-49-41.log -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
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 is /usr/lib/plainbox- provider-checkbox/bin/memory_stress_ng -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
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 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
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 Ubuntu. https://bugs.launchpad.net/bugs/1573062 Title: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
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 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
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" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+attachment/4703165/+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/1573062 Title: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
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 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
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 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: 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 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: 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 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: 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: /usr/lib/plainbox-provider-checkbox/bin/memory_stress_ng -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
