[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
Escalated to Field Critical as it now happens often enough to block our
ability to test proposed product releases. We are unable to test
openstack-next at the moment because our test runs fail behind this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend
It does seem to have improved in the last update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: Incomplete Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend
May 25 08:50:46 Thermia microk8s.daemon-apiserver[7167]: I0525 08:50:46.182335 7167 wrap.go:47] PUT /api/v1/namespaces/kube-system/endpoints/kube-controller-manager?timeout=10s: (3.332254ms) 200 [kube-controller-manager/v1.14.1 (linux/amd64) kubernetes/b739410/leader-election 127.0.0.1:56726] May 25 08:50:46 Thermia microk8s.daemon-apiserver[7167]: I0525 08:50:46.634891 7167 wrap.go:47] GET /api/v1/nodes?resourceVersion=5708807=450=true: (7m30.001685916s) 200 [heapster/v0.0.0 (linux/amd64) kubernetes/$Format 192.168.86.33:48032] May 25 08:50:46 Thermia microk8s.daemon-apiserver[7167]: I0525 08:50:46.637456 7167 get.go:251] Starting watch for /api/v1/nodes, rv=5709318 labels= fields= timeout=5m16s May 25 08:50:47 Thermia microk8s.daemon-apiserver[7167]: I0525 08:50:47.005793 7167 wrap.go:47] GET /api/v1/namespaces/kube-system/endpoints/kube-scheduler?timeout=10s: (2.286855ms) 200 [kube-scheduler/v1.14.1 (linux/amd64) kubernetes/b739410/leader-election 127.0.0.1:49932] May 25 08:50:47 Thermia microk8s.daemon-apiserver[7167]: I0525 08:50:47.010412 7167 wrap.go:47] PUT /api/v1/namespaces/kube-system/endpoints/kube-scheduler?timeout=10s: (3.348305ms) 200 [kube-scheduler/v1.14.1 (linux/amd64) kubernetes/b739410/leader-election 127.0.0.1:49932] May 25 08:50:47 Thermia systemd-logind[1166]: Lid closed. May 25 08:50:47 Thermia systemd-logind[1166]: Suspending... May 25 08:50:47 Thermia NetworkManager[1197]: [1558788647.9902] manager: sleep: sleep requested (sleeping: no enabled: yes) May 25 08:50:47 Thermia NetworkManager[1197]: [1558788647.9905] device (p2p-dev-wlp4s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed') May 25 08:50:47 Thermia NetworkManager[1197]: [1558788647.9931] manager: NetworkManager state is now ASLEEP May 25 08:50:48 Thermia systemd[1]: Reached target Sleep. -- May 25 14:41:02 Thermia kernel: Bluetooth: hci0: API lock is enabled May 25 14:41:02 Thermia kernel: Bluetooth: hci0: Debug lock is disabled May 25 14:41:02 Thermia kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 May 25 14:41:02 Thermia kernel: Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi May 25 14:41:02 Thermia kernel: done. May 25 14:41:01 Thermia systemd-logind[1166]: Lid opened. May 25 14:41:02 Thermia microk8s.daemon-apiserver[7167]: I0525 14:41:01.990168 7167 wrap.go:47] GET /apis/extensions/v1beta1/daemonsets?resourceVersion=5585151=5m26s=326=true: (5m26.091210748s) 200 [kube-controller-manager/v1.14.1 (linux/amd64) kubernetes/b739410/shared-informers 127.0.0.1:49858] May 25 14:41:02 Thermia microk8s.daemon-apiserver[7167]: I0525 14:41:01.993603 7167 wrap.go:47] GET /api/v1/namespaces/kube-system/endpoints/kube-scheduler?timeout=10s: (4.25ms) 200 [kube-scheduler/v1.14.1 (linux/amd64) kubernetes/b739410/leader-election 127.0.0.1:49932] May 25 14:41:02 Thermia microk8s.daemon-apiserver[7167]: I0525 14:41:01.993898 7167 wrap.go:47] GET /api/v1/namespaces/kube-system/endpoints/kube-controller-manager?timeout=10s: (4.104768ms) 200 [kube-controller-manager/v1.14.1 (linux/amd64) kubernetes/b739410/leader-election 127.0.0.1:56726] May 25 14:41:02 Thermia microk8s.daemon-apiserver[7167]: I0525 14:41:01.997048 7167 get.go:251] Starting watch for /apis/extensions/v1beta1/daemonsets, rv=5585151 labels= fields= timeout=6m15s May 25 14:41:02 Thermia microk8s.daemon-apiserver[7167]: I0525 14:41:01.999249 7167 wrap.go:47] GET /apis/coordination.k8s.io/v1beta1/namespaces/kube-node-lease/leases/thermia?timeout=10s: (8.048104ms) 200 [kubelet/v1.14.1 (linux/amd64) kubernetes/b739410 127.0.0.1:60774] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: Incomplete Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend
Looks like it was actually longer than 10 seconds as I opened the lid 1 sec after the power light began to pulse. Fri 17 May 2019 09:48:20 AM CEST - state: open Fri 17 May 2019 09:48:21 AM CEST - state: open Fri 17 May 2019 09:48:22 AM CEST - state: open Fri 17 May 2019 09:48:23 AM CEST - state: open Fri 17 May 2019 09:48:24 AM CEST - state: open Fri 17 May 2019 09:48:25 AM CEST - state: closed Fri 17 May 2019 09:48:26 AM CEST - state: closed Fri 17 May 2019 09:48:27 AM CEST - state: closed Fri 17 May 2019 09:48:28 AM CEST - state: closed Fri 17 May 2019 09:48:29 AM CEST - state: closed Fri 17 May 2019 09:48:30 AM CEST - state: closed Fri 17 May 2019 09:48:31 AM CEST - state: closed Fri 17 May 2019 09:48:33 AM CEST - state: closed Fri 17 May 2019 09:48:34 AM CEST - state: closed Fri 17 May 2019 09:48:35 AM CEST - state: closed Fri 17 May 2019 09:48:36 AM CEST - state: closed Fri 17 May 2019 09:48:37 AM CEST - state: closed Fri 17 May 2019 09:48:38 AM CEST - state: closed Fri 17 May 2019 09:48:39 AM CEST - state: closed Fri 17 May 2019 09:48:40 AM CEST - state: closed Fri 17 May 2019 09:48:41 AM CEST - state: closed Fri 17 May 2019 09:48:42 AM CEST - state: closed Fri 17 May 2019 09:48:43 AM CEST - state: closed Fri 17 May 2019 09:48:44 AM CEST - state: closed Fri 17 May 2019 09:48:45 AM CEST - state: closed Fri 17 May 2019 09:48:46 AM CEST - state: closed Fri 17 May 2019 09:48:47 AM CEST - state: closed Fri 17 May 2019 09:48:48 AM CEST - state: closed Fri 17 May 2019 09:48:49 AM CEST - state: closed Fri 17 May 2019 09:48:50 AM CEST - state: closed Fri 17 May 2019 09:48:51 AM CEST - state: closed Fri 17 May 2019 09:48:52 AM CEST - state: closed Fri 17 May 2019 09:48:53 AM CEST - state: closed Fri 17 May 2019 09:48:54 AM CEST - state: closed Fri 17 May 2019 09:48:55 AM CEST - state: closed Fri 17 May 2019 09:49:00 AM CEST - state: open Fri 17 May 2019 09:49:02 AM CEST - state: open Fri 17 May 2019 09:49:03 AM CEST - state: open ^C On Fri, May 17, 2019 at 9:52 AM Chris Gregan wrote: > This is interesting. > > `echo mem > /sys/power/state` > This command was instant S3. The screen went black and the power light > immediately began to blink. > > However...for lid switch the power light takes around 10 seconds to begin > to pulse, but the state immediately switches. > > Fri 17 May 2019 09:48:22 AM CEST - state: open > Fri 17 May 2019 09:48:23 AM CEST - state: open > Fri 17 May 2019 09:48:24 AM CEST - state: open > Fri 17 May 2019 09:48:25 AM CEST - state: closed > Fri 17 May 2019 09:48:26 AM CEST - state: closed > Fri 17 May 2019 09:48:27 AM CEST - state: closed > > It seems although detection if immediate, it takes 10 seconds to process? > > On Thu, May 16, 2019 at 6:05 PM Andrea Righi > wrote: > >> Hi Chris, just to make sure I understand (from a kernel perspective), >> can you confirm that `echo mem > /sys/power/state` is also fast at >> reaching the suspend state? >> >> In that case it would be interesting to check if there's a delay at >> detecting the state of the lid switch. For this, could you run the >> following command in a bash session: >> >> $ while :; do echo `date` - `cat /proc/acpi/button/lid/LID0/state`; >> sleep 1; done >> >> Close the lid, re-open it and you should notice something like this: >> >> Thu May 16 17:50:42 CEST 2019 - state: open >> Thu May 16 17:50:43 CEST 2019 - state: open >> Thu May 16 17:50:44 CEST 2019 - state: open >> Thu May 16 17:50:45 CEST 2019 - state: closed >> Thu May 16 17:50:46 CEST 2019 - state: closed >> Thu May 16 17:50:47 CEST 2019 - state: closed >> Thu May 16 17:50:48 CEST 2019 - state: open >> Thu May 16 17:50:49 CEST 2019 - state: open >> Thu May 16 17:50:50 CEST 2019 - state: open >> ^C >> >> Note that I have set the "lid close action" to do nothing, in this way >> we can better isolate the problem. Thanks. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1829399 >> >> Title: >> Lid switch triggered suspend takes much longer than UI triggered >> suspend >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+subscriptions >> > > > -- > > Chris Gregan > Engineering Manager > Solutions QA/Techops > cgre...@irc.canonical.com > -- Chris Gregan Engineering Manager Solutions QA/Techops cgre...@irc.canonical.com -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status
Re: [Kernel-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend
This is interesting. `echo mem > /sys/power/state` This command was instant S3. The screen went black and the power light immediately began to blink. However...for lid switch the power light takes around 10 seconds to begin to pulse, but the state immediately switches. Fri 17 May 2019 09:48:22 AM CEST - state: open Fri 17 May 2019 09:48:23 AM CEST - state: open Fri 17 May 2019 09:48:24 AM CEST - state: open Fri 17 May 2019 09:48:25 AM CEST - state: closed Fri 17 May 2019 09:48:26 AM CEST - state: closed Fri 17 May 2019 09:48:27 AM CEST - state: closed It seems although detection if immediate, it takes 10 seconds to process? On Thu, May 16, 2019 at 6:05 PM Andrea Righi wrote: > Hi Chris, just to make sure I understand (from a kernel perspective), > can you confirm that `echo mem > /sys/power/state` is also fast at > reaching the suspend state? > > In that case it would be interesting to check if there's a delay at > detecting the state of the lid switch. For this, could you run the > following command in a bash session: > > $ while :; do echo `date` - `cat /proc/acpi/button/lid/LID0/state`; > sleep 1; done > > Close the lid, re-open it and you should notice something like this: > > Thu May 16 17:50:42 CEST 2019 - state: open > Thu May 16 17:50:43 CEST 2019 - state: open > Thu May 16 17:50:44 CEST 2019 - state: open > Thu May 16 17:50:45 CEST 2019 - state: closed > Thu May 16 17:50:46 CEST 2019 - state: closed > Thu May 16 17:50:47 CEST 2019 - state: closed > Thu May 16 17:50:48 CEST 2019 - state: open > Thu May 16 17:50:49 CEST 2019 - state: open > Thu May 16 17:50:50 CEST 2019 - state: open > ^C > > Note that I have set the "lid close action" to do nothing, in this way > we can better isolate the problem. Thanks. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1829399 > > Title: > Lid switch triggered suspend takes much longer than UI triggered > suspend > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+subscriptions > -- Chris Gregan Engineering Manager Solutions QA/Techops cgre...@irc.canonical.com -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: Incomplete Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829399] [NEW] Lid switch triggered suspend takes much longer than UI triggered suspend
Public bug reported: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "version.log" https://bugs.launchpad.net/bugs/1829399/+attachment/5264255/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: New Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829399] Re: Lid switch triggered suspend takes much longer than UI triggered suspend
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+attachment/5264256/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: New Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773165] Re: openvswitch-datapath-dkms kernel module is not getting loaded
@Andrei Since the driver is now part of the kernel, any changes to the driver, and as a result, the kernel will need to follow the standard upstream kernel patch process found here: https://www.kernel.org/doc/html/v4.17/process/submitting-patches.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773165 Title: openvswitch-datapath-dkms kernel module is not getting loaded Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial Kernel version: 4.4.0-127-generic OVS version: 2.7.0 # Issue description openvswitch-datapath-dkms kernelmodule is not getting loaded # Error from dmesg [10863.380564] openvswitch: module verification failed: signature and/or required key missing - tainting kernel [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) #Error from syslog May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not insert 'openvswitch': Exec format error May 24 08:37:06 dev65 openvswitch-switch[18336]: * Inserting openvswitch module #installation logs: Selecting previously unselected package openvswitch-datapath-dkms. (Reading database ... 84707 files and directories currently installed.) Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ... Unpacking openvswitch-datapath-dkms (2.7.0-1) ... Setting up openvswitch-datapath-dkms (2.7.0-1) ... Creating symlink /var/lib/dkms/openvswitch/2.7.0/source -> /usr/src/openvswitch-2.7.0 DKMS: add completed. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area(bad exit status: 2) ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C datapath/linux.. cleaning build area(bad exit status: 2) DKMS: build completed. openvswitch: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-geneve.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-gre.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-lisp.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-stt.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-vxlan.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ depmod DKMS: install completed. #Dpkg status dpkg -l | grep openvswitch ii openvswitch-common 2.7.0-1 amd64Open vSwitch common components ii openvswitch-datapath-dkms2.7.0-1 all Open vSwitch datapath module source - DKMS version ii openvswitch-switch 2.7.0-1 amd64Open vSwitch switch implementations ii python-openvswitch 2.6.1-0ubuntu5.2~cloud0 all Python bindings for Open vSwitch #lsmod status No modules are listing for openvswitch-datapath-dkms #modprobe error modprobe openvswitch modprobe: ERROR: could not insert 'openvswitch': Exec format error --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-127-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004
[Kernel-packages] [Bug 1773165] Re: openvswitch-datapath-dkms kernel module is not getting loaded
@jsalsbury We are still seeing the issue, given ridsaim has not replied lets move forward. I'd like to get some movement on this issue without marking as a Field Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773165 Title: openvswitch-datapath-dkms kernel module is not getting loaded Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial Kernel version: 4.4.0-127-generic OVS version: 2.7.0 # Issue description openvswitch-datapath-dkms kernelmodule is not getting loaded # Error from dmesg [10863.380564] openvswitch: module verification failed: signature and/or required key missing - tainting kernel [10863.381804] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10863.517173] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) [10878.094250] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) #Error from syslog May 24 08:37:06 dev65 kernel: [76508.361496] openvswitch: exports duplicate symbol dst_cache_destroy (owned by kernel) May 24 08:37:06 dev65 openvswitch-switch[18336]: modprobe: ERROR: could not insert 'openvswitch': Exec format error May 24 08:37:06 dev65 openvswitch-switch[18336]: * Inserting openvswitch module #installation logs: Selecting previously unselected package openvswitch-datapath-dkms. (Reading database ... 84707 files and directories currently installed.) Preparing to unpack openvswitch-datapath-dkms_2.7.0-1_all.deb ... Unpacking openvswitch-datapath-dkms (2.7.0-1) ... Setting up openvswitch-datapath-dkms (2.7.0-1) ... Creating symlink /var/lib/dkms/openvswitch/2.7.0/source -> /usr/src/openvswitch-2.7.0 DKMS: add completed. Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area(bad exit status: 2) ./configure --with-linux='/lib/modules/4.4.0-127-generic/build' && make -C datapath/linux.. cleaning build area(bad exit status: 2) DKMS: build completed. openvswitch: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-geneve.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-gre.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-lisp.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-stt.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ vport-vxlan.ko: Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-127-generic/updates/dkms/ depmod DKMS: install completed. #Dpkg status dpkg -l | grep openvswitch ii openvswitch-common 2.7.0-1 amd64Open vSwitch common components ii openvswitch-datapath-dkms2.7.0-1 all Open vSwitch datapath module source - DKMS version ii openvswitch-switch 2.7.0-1 amd64Open vSwitch switch implementations ii python-openvswitch 2.6.1-0ubuntu5.2~cloud0 all Python bindings for Open vSwitch #lsmod status No modules are listing for openvswitch-datapath-dkms #modprobe error modprobe openvswitch modprobe: ERROR: could not insert 'openvswitch': Exec format error --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-127-generic. AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory Card0.Amixer.values: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID
[Kernel-packages] [Bug 1759445] Re: kernel panic when trying to reboot in bionic
Mark is pressing to potentially change dist upgrade to detect older firmware versions prior to upgrade to ensure the latest is in place before Ubuntu upgrade -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759445 Title: kernel panic when trying to reboot in bionic Status in MAAS: Invalid Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: cpe_foundation test deployment of Bionic failed. After some investigation, it looks like the nodes deployed and installed bionic, but never came back from a reboot. Accessing the ILO console of a node in question (all nodes failed), it revealed a kernel panic (attached) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1759445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1759445] Re: kernel panic when trying to reboot in bionic
We need to continue to investigate this issue as anyone upgrading a certified hardware with older firware will be stuck. This will be a bad user experience. ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1759445 Title: kernel panic when trying to reboot in bionic Status in MAAS: Invalid Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: cpe_foundation test deployment of Bionic failed. After some investigation, it looks like the nodes deployed and installed bionic, but never came back from a reboot. Accessing the ILO console of a node in question (all nodes failed), it revealed a kernel panic (attached) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1759445/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757277] Re: soft lockup from bcache leading to high load and lockup on trusty
@Drew
Do you have an update to the request above?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1757277
Title:
soft lockup from bcache leading to high load and lockup on trusty
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
In Progress
Bug description:
I have an environment with Dell R630 servers with RAID controllers
with two virtual disks and 22 passthru devices. 2 SAS SSDs and 20
HDDs are setup in 2 bcache cachesets with a resulting 20 mounted xfs
filesystems running bcache backending an 11 node swift cluster (one
zone has 1 fewer nodes). Two of the zones have these nodes as
described above and they appear to be exibiting soft lockups in the
bcache thread of the kernel causing other kernel threads to go into
i/o blocking state an keeping processes on any bcache from being
successful. disk access to the virtual disks mounted with out bcache
is still possible when this lockup occurs.
https://pastebin.ubuntu.com/p/mtn47QqBJ3/
There are several softlockup messages found in the dmesg and many of
the dumpstack are locked inside the bch_writeback_thread();
static int bch_writeback_thread(void *arg)
{
[...]
while (!kthread_should_stop()) {
down_write(>writeback_lock);
[...]
}
One coredump is found when the kswapd is doing the reclaim about the
xfs inode cache.
__xfs_iflock(
struct xfs_inode *ip)
{
do {
prepare_to_wait_exclusive(wq, , TASK_UNINTERRUPTIBLE);
if (xfs_isiflocked(ip))
io_schedule();
} while (!xfs_iflock_nowait(ip));
- Possible fix commits:
1). 9baf30972b55 bcache: fix for gc and write-back race
https://www.spinics.net/lists/linux-bcache/msg04713.html
- Related discussions:
1). Re: [PATCH] md/bcache: Fix a deadlock while calculating writeback rate
https://www.spinics.net/lists/linux-bcache/msg04617.html
2). Re: hang during suspend to RAM when bcache cache device is attached
https://www.spinics.net/lists/linux-bcache/msg04636.html
We are running trusty/mitaka swift storage on these nodes with
4.4.0-111 kernel (linux-image-generic-lts-xenial).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757277/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1753662] Re: [i40e] LACP bonding start up race conditions
** Tags added: cdo-qa-blocker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1753662 Title: [i40e] LACP bonding start up race conditions Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: When provisioning Ubuntu servers with MAAS at once, some bonding pairs will have unexpected LACP status such as "Expired". It randomly happens at each provisioning with the default xenial kernel(4.4), but not reproducible with HWE kernel(4.13). I'm using Intel X710 cards (Dell-branded). Using the HWE kernel works as a workaround for short term, but it's not ideal since 4.13 is not covered by Canonical Livepatch service. How to reproduce: 1. configure LACP bonding with MAAS 2. provision machines 3. check the bonding status in /proc/net/bonding/bond* frequency of occurrence: About 5 bond pairs in 22 pairs at each provisioning. [reproducible combination] $ uname -a Linux comp006 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 1.4.25-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes [non-reproducible combination] $ uname -a Linux comp006 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ sudo ethtool -i eno1 driver: i40e version: 2.1.14-k firmware-version: 6.00 0x800034e6 18.3.6 expansion-rom-version: bus-info: :01:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: yes supports-priv-flags: yes ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-116-generic 4.4.0-116.140 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 6 06:37 seq crw-rw 1 root audio 116, 33 Mar 6 06:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 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: Tue Mar 6 06:46:32 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:8002 Intel Corp. Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub Bus 001 Device 002: ID 8087:800a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R730 PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-116-generic.efi.signed root=UUID=0528f88e-cf1a-43e2-813a-e7261b88d460 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-116-generic N/A linux-backports-modules-4.4.0-116-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/16/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.5 dmi.board.name: 072T6D dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.asset.tag: 0018880 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.5:bd08/16/2017:svnDellInc.:pnPowerEdgeR730:pvr:rvnDellInc.:rn072T6D:rvrA08:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R730 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753662/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1737640] Re: bridge activaction error: bridge activation failed | unconfigured interfaces cause ifup failures
Moved to field critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1737640 Title: bridge activaction error: bridge activation failed | unconfigured interfaces cause ifup failures Status in juju: Triaged Status in ubuntu-fan package in Ubuntu: New Bug description: I'm seeing this error as the status of multiple containers in my deploy: http://paste.ubuntu.com/26166720/ I can't connect to the parent machines anymore either - it seems networking is totally hosed on the machines. This is with juju 2.3.1. To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1737640/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651602] Re: NVMe driver regression for non-smp/1-cpu systems
Kernel 4.4.0-59.80 pushed to cloud and MAAS images and retested on failing systems. Failing systems continue to fail Unexpected error while running command. Command: ['curtin', 'block-meta', 'custom'] Exit code: 3 Reason: - Stdout: b"no disk with serial 'CVMD51530020400AGN' found\n" Stderr: '' ** Changed in: linux (Ubuntu Xenial) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651602 Title: NVMe driver regression for non-smp/1-cpu systems Status in curtin: Invalid Status in MAAS: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: MAAS Version 2.1.1+bzr5544-0ubuntu1 (16.10.1) Deploying Xenial Nodes 1) Deploy MAAS 2.1.1 on Yakkety 2) Associate Juju 2.1 beta3 3) Juju deploy Kubernetes Core Nodes begin to deploy but fail Installation failed with exception: Unexpected error while running command. Command: ['curtin', 'block-meta', 'custom'] Exit code: 3 Reason: - Stdout: b"no disk with serial 'CVMD434500BN400AGN' found\n" Related bugs: * bug 1647485: NVMe symlinks broken by devices with spaces in model or serial strings * bug 1642903: introduce disk/by-id (model_serial) symlinks for NVMe drives To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1651602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651602] Re: [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails
Dan, Bug above, but since you say it is only happening to me, have other tests been run using MAAS 2.1.2? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651602 Title: [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails Status in MAAS: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: MAAS Version 2.1.1+bzr5544-0ubuntu1 (16.10.1) Deploying Xenial Nodes 1) Deploy MAAS 2.1.1 on Yakkety 2) Associate Juju 2.1 beta3 3) Juju deploy Kubernetes Core Nodes begin to deploy but fail Installation failed with exception: Unexpected error while running command. Command: ['curtin', 'block-meta', 'custom'] Exit code: 3 Reason: - Stdout: b"no disk with serial 'CVMD434500BN400AGN' found\n" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1651602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651602] Re: [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails
Additional bug opened: https://bugs.launchpad.net/maas/+bug/1653797 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651602 Title: [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails Status in MAAS: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: MAAS Version 2.1.1+bzr5544-0ubuntu1 (16.10.1) Deploying Xenial Nodes 1) Deploy MAAS 2.1.1 on Yakkety 2) Associate Juju 2.1 beta3 3) Juju deploy Kubernetes Core Nodes begin to deploy but fail Installation failed with exception: Unexpected error while running command. Command: ['curtin', 'block-meta', 'custom'] Exit code: 3 Reason: - Stdout: b"no disk with serial 'CVMD434500BN400AGN' found\n" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1651602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1651602] Re: [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails
Dan, What should be the focus of the new bug? Split off the fact that Denial cannot be deployed by MAAS? Or is it still related to nvme, just differently? On Dec 23, 2016 19:05, "Dan Streetman" < dan.streetman+launch...@canonical.com> wrote: > Chris, as your specific problem seems different than the 1-cpu NVMe bug > that the rest of this bug describes, and my patch fixes, can you open a > new bug please. > > ** Changed in: maas >Status: New => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1651602 > > Title: > [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails > > To manage notifications about this bug go to: > https://bugs.launchpad.net/maas/+bug/1651602/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651602 Title: [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails Status in MAAS: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: MAAS Version 2.1.1+bzr5544-0ubuntu1 (16.10.1) Deploying Xenial Nodes 1) Deploy MAAS 2.1.1 on Yakkety 2) Associate Juju 2.1 beta3 3) Juju deploy Kubernetes Core Nodes begin to deploy but fail Installation failed with exception: Unexpected error while running command. Command: ['curtin', 'block-meta', 'custom'] Exit code: 3 Reason: - Stdout: b"no disk with serial 'CVMD434500BN400AGN' found\n" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1651602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651602] Re: [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails
** Attachment added: "syslog_kern.tar.gz" https://bugs.launchpad.net/maas/+bug/1651602/+attachment/4795854/+files/syslog_kern.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651602 Title: [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails Status in MAAS: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: MAAS Version 2.1.1+bzr5544-0ubuntu1 (16.10.1) Deploying Xenial Nodes 1) Deploy MAAS 2.1.1 on Yakkety 2) Associate Juju 2.1 beta3 3) Juju deploy Kubernetes Core Nodes begin to deploy but fail Installation failed with exception: Unexpected error while running command. Command: ['curtin', 'block-meta', 'custom'] Exit code: 3 Reason: - Stdout: b"no disk with serial 'CVMD434500BN400AGN' found\n" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1651602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651602] Re: [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails
** Attachment added: "curtin_config.tar.gz" https://bugs.launchpad.net/maas/+bug/1651602/+attachment/4795743/+files/curtin_config.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651602 Title: [2.1.1] MAAS has nvme0n1 set as boot disk, curtin fails Status in MAAS: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: MAAS Version 2.1.1+bzr5544-0ubuntu1 (16.10.1) Deploying Xenial Nodes 1) Deploy MAAS 2.1.1 on Yakkety 2) Associate Juju 2.1 beta3 3) Juju deploy Kubernetes Core Nodes begin to deploy but fail Installation failed with exception: Unexpected error while running command. Command: ['curtin', 'block-meta', 'custom'] Exit code: 3 Reason: - Stdout: b"no disk with serial 'CVMD434500BN400AGN' found\n" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1651602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651602] Re: [2.1.1] Yakkety - MAAS has nvme0n1 set as boot disk, curtin fails
** Tags added: cdo-qa-blocker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651602 Title: [2.1.1] Yakkety - MAAS has nvme0n1 set as boot disk, curtin fails Status in MAAS: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Confirmed Status in linux source package in Yakkety: Incomplete Bug description: MAAS Version 2.1.1+bzr5544-0ubuntu1 (16.10.1) Deploying Xenial Nodes 1) Deploy MAAS 2.1.1 on Yakkety 2) Associate Juju 2.1 beta3 3) Juju deploy Kubernetes Core Nodes begin to deploy but fail Installation failed with exception: Unexpected error while running command. Command: ['curtin', 'block-meta', 'custom'] Exit code: 3 Reason: - Stdout: b"no disk with serial 'CVMD434500BN400AGN' found\n" To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1651602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1547507] [NEW] package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: Build Version/Date: Xenial upgraded on 19/2 Environment used for testing: Xenial upgraded from Wily Summary: Packages fail to install. The upgrade must be cleaned up manually. Steps to Reproduce: 1) Install Wily 2) Open terminal and type "update-manager -d" 3) Proceed with Xenial update Expected result: Upgrade successful Actual result: Package installation failures ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-6-generic 4.4.0-6.21 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 2773 F pulseaudio /dev/snd/controlC1: chris 2773 F pulseaudio Date: Thu Feb 18 17:57:18 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2013-09-18 (883 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130917) MachineType: Apple Inc. MacBookAir6,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic root=UUID=9985bed8-79ed-4d0b-8738-6d23d2c9dade ro pcie_aspm=force i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 acpi_backlight=vendor PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-02-18 (0 days ago) dmi.bios.date: 05/24/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0099.B00.1305241529 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-7DF21CB3ED6977E5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-7DF21CB3ED6977E5 dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B00.1305241529:bd05/24/2013:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5: dmi.product.name: MacBookAir6,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1547507 Title: package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in linux package in Ubuntu: Confirmed Bug description: Build Version/Date: Xenial upgraded on 19/2 Environment used for testing: Xenial upgraded from Wily Summary: Packages fail to install. The upgrade must be cleaned up manually. Steps to Reproduce: 1) Install Wily 2) Open terminal and type "update-manager -d" 3) Proceed with Xenial update Expected result: Upgrade successful Actual result: Package installation failures ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-6-generic 4.4.0-6.21 ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1 Uname: Linux 4.4.0-6-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 2773 F pulseaudio /dev/snd/controlC1: chris 2773 F pulseaudio Date: Thu Feb 18 17:57:18 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2013-09-18 (883 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130917) MachineType: Apple Inc. MacBookAir6,2 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic root=UUID=9985bed8-79ed-4d0b-8738-6d23d2c9dade ro pcie_aspm=force i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 acpi_backlight=vendor PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2016-02-18 (0 days ago) dmi.bios.date: 05/24/2013 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0099.B00.1305241529 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-7DF21CB3ED6977E5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,2
