[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
USB-C dock is different to Thunderbolt Dock. Please file a new 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd [279389.949983] usb usb3: SerialNumber: :0e:00.0
[Kernel-packages] [Bug 1690085]
Created attachment 280601 My /proc/cpuinfo This is my ThreadRipper 2950X /proc/cpuinfo, as requested. -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscription
[Kernel-packages] [Bug 1690085]
(In reply to Borislav Petkov from comment #475) > (In reply to Aaron Muir Hamilton from comment #474) > > I just experienced this issue with a Threadripper 2950X on kernel 4.20.3 > > Anything in dmesg? > > Please upload full dmesg, /proc/cpuinfo and kernel .config. There is no header soldered on the board's UART, I do not have a normal serial port, and the logs would not write to disk (so I can't copy the dmesg from the incident). It amounted to: BUG: soft lockup - CPU#13 stuck for 22s! The config is here https://git.archlinux.org/svntogit/packages.git/tree/trunk/config?h=packages/linux > > Anything particular you did to reproduce it? Any correlation between what > the box does and occurrence of the lockup? Sadly no. The core happened to be running pulseaudio and upower, so my audio buffer started looping and eventually the watchdog timer timed out. I don't think any of that is particularly special though. > > Thx. No, thank you! I don't know what I'm doing, and maybe you do. :- ) For the time being, I've now added idle=nomwait to my kernel params, as it seems at least one of these issues is related to MWAIT (according to AMD's errata). -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchd
[Kernel-packages] [Bug 1690085]
(In reply to Aaron Muir Hamilton from comment #474) > I just experienced this issue with a Threadripper 2950X on kernel 4.20.3 Anything in dmesg? Please upload full dmesg, /proc/cpuinfo and kernel .config. Anything particular you did to reproduce it? Any correlation between what the box does and occurrence of the lockup? Thx. -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not
[Kernel-packages] [Bug 1690085]
I just experienced this issue with a Threadripper 2950X on kernel 4.20.3 -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1690085/+subscriptions -- Mailing list: https://l
[Kernel-packages] [Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140
** Attachment added: "Image of 5.0.0-rc2 showing dmesg error kernel write locking up. Page 5" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/5230629/+files/IMG_20190120_171250.jpg -- 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/1472832 Title: Suspend issue with Dell Venue 11 Pro 7140 Status in linux package in Ubuntu: Incomplete Bug description: Instead of suspending the machine into a state where it can be started quickly, it appears that suspend causes the system to end up in a state which requires a forced start. The power light is off, and the only way to start the machine again is to hold down the power button for more than 5 seconds. A quick check of uptime shows that it did, indeed, start again. I'm attaching a suspend log. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tudor 1785 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 9 10:57:38 2015 HibernationDevice: RESUME=UUID=3acb1340-1be5-453c-a918-25f6b6ff404e InstallationDate: Installed on 2015-07-06 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 114d:1002 Alpha Imaging Technology Corp. Bus 001 Device 002: ID 0bda:5757 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Venue 11 Pro 7140 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=f0dc97e1-7d1c-4d05-a7d8-3cfc8551bdc4 ro quiet splash i915.i915_enable_rc6=1 "acpi_osi=!Windows 2013" vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-07 (1 days ago) dmi.bios.date: 06/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd06/30/2015:svnDellInc.:pnVenue11Pro7140:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+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 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140
** Attachment added: "Image of 5.0.0-rc2 showing dmesg error kernel write locking up. Page 1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/5230625/+files/IMG_20190120_171139.jpg -- 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/1472832 Title: Suspend issue with Dell Venue 11 Pro 7140 Status in linux package in Ubuntu: Incomplete Bug description: Instead of suspending the machine into a state where it can be started quickly, it appears that suspend causes the system to end up in a state which requires a forced start. The power light is off, and the only way to start the machine again is to hold down the power button for more than 5 seconds. A quick check of uptime shows that it did, indeed, start again. I'm attaching a suspend log. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tudor 1785 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 9 10:57:38 2015 HibernationDevice: RESUME=UUID=3acb1340-1be5-453c-a918-25f6b6ff404e InstallationDate: Installed on 2015-07-06 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 114d:1002 Alpha Imaging Technology Corp. Bus 001 Device 002: ID 0bda:5757 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Venue 11 Pro 7140 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=f0dc97e1-7d1c-4d05-a7d8-3cfc8551bdc4 ro quiet splash i915.i915_enable_rc6=1 "acpi_osi=!Windows 2013" vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-07 (1 days ago) dmi.bios.date: 06/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd06/30/2015:svnDellInc.:pnVenue11Pro7140:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+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 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140
** Attachment added: "Image of 5.0.0-rc2 showing dmesg error kernel write locking up. Page 4" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/5230628/+files/IMG_20190120_171242.jpg -- 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/1472832 Title: Suspend issue with Dell Venue 11 Pro 7140 Status in linux package in Ubuntu: Incomplete Bug description: Instead of suspending the machine into a state where it can be started quickly, it appears that suspend causes the system to end up in a state which requires a forced start. The power light is off, and the only way to start the machine again is to hold down the power button for more than 5 seconds. A quick check of uptime shows that it did, indeed, start again. I'm attaching a suspend log. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tudor 1785 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 9 10:57:38 2015 HibernationDevice: RESUME=UUID=3acb1340-1be5-453c-a918-25f6b6ff404e InstallationDate: Installed on 2015-07-06 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 114d:1002 Alpha Imaging Technology Corp. Bus 001 Device 002: ID 0bda:5757 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Venue 11 Pro 7140 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=f0dc97e1-7d1c-4d05-a7d8-3cfc8551bdc4 ro quiet splash i915.i915_enable_rc6=1 "acpi_osi=!Windows 2013" vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-07 (1 days ago) dmi.bios.date: 06/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd06/30/2015:svnDellInc.:pnVenue11Pro7140:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+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 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140
** Attachment added: "Image of 4.20.3 showing dmesg error kernel write locking up. Page 1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/5230630/+files/IMG_20190120_171547.jpg -- 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/1472832 Title: Suspend issue with Dell Venue 11 Pro 7140 Status in linux package in Ubuntu: Incomplete Bug description: Instead of suspending the machine into a state where it can be started quickly, it appears that suspend causes the system to end up in a state which requires a forced start. The power light is off, and the only way to start the machine again is to hold down the power button for more than 5 seconds. A quick check of uptime shows that it did, indeed, start again. I'm attaching a suspend log. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tudor 1785 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 9 10:57:38 2015 HibernationDevice: RESUME=UUID=3acb1340-1be5-453c-a918-25f6b6ff404e InstallationDate: Installed on 2015-07-06 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 114d:1002 Alpha Imaging Technology Corp. Bus 001 Device 002: ID 0bda:5757 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Venue 11 Pro 7140 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=f0dc97e1-7d1c-4d05-a7d8-3cfc8551bdc4 ro quiet splash i915.i915_enable_rc6=1 "acpi_osi=!Windows 2013" vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-07 (1 days ago) dmi.bios.date: 06/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd06/30/2015:svnDellInc.:pnVenue11Pro7140:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+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 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140
** Attachment added: "Image of 4.20.3 showing dmesg error kernel write locking up. Page 2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/5230631/+files/IMG_20190120_171558.jpg -- 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/1472832 Title: Suspend issue with Dell Venue 11 Pro 7140 Status in linux package in Ubuntu: Incomplete Bug description: Instead of suspending the machine into a state where it can be started quickly, it appears that suspend causes the system to end up in a state which requires a forced start. The power light is off, and the only way to start the machine again is to hold down the power button for more than 5 seconds. A quick check of uptime shows that it did, indeed, start again. I'm attaching a suspend log. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tudor 1785 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 9 10:57:38 2015 HibernationDevice: RESUME=UUID=3acb1340-1be5-453c-a918-25f6b6ff404e InstallationDate: Installed on 2015-07-06 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 114d:1002 Alpha Imaging Technology Corp. Bus 001 Device 002: ID 0bda:5757 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Venue 11 Pro 7140 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=f0dc97e1-7d1c-4d05-a7d8-3cfc8551bdc4 ro quiet splash i915.i915_enable_rc6=1 "acpi_osi=!Windows 2013" vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-07 (1 days ago) dmi.bios.date: 06/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd06/30/2015:svnDellInc.:pnVenue11Pro7140:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+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 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140
** Attachment added: "Image of 4.20.3 showing dmesg error kernel write locking up. Page 3" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/5230632/+files/IMG_20190120_171610.jpg -- 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/1472832 Title: Suspend issue with Dell Venue 11 Pro 7140 Status in linux package in Ubuntu: Incomplete Bug description: Instead of suspending the machine into a state where it can be started quickly, it appears that suspend causes the system to end up in a state which requires a forced start. The power light is off, and the only way to start the machine again is to hold down the power button for more than 5 seconds. A quick check of uptime shows that it did, indeed, start again. I'm attaching a suspend log. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tudor 1785 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 9 10:57:38 2015 HibernationDevice: RESUME=UUID=3acb1340-1be5-453c-a918-25f6b6ff404e InstallationDate: Installed on 2015-07-06 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 114d:1002 Alpha Imaging Technology Corp. Bus 001 Device 002: ID 0bda:5757 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Venue 11 Pro 7140 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=f0dc97e1-7d1c-4d05-a7d8-3cfc8551bdc4 ro quiet splash i915.i915_enable_rc6=1 "acpi_osi=!Windows 2013" vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-07 (1 days ago) dmi.bios.date: 06/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd06/30/2015:svnDellInc.:pnVenue11Pro7140:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+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 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140
** Attachment added: "Image of 5.0.0-rc2 showing dmesg error kernel write locking up. Page 2" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/5230626/+files/IMG_20190120_171209.jpg -- 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/1472832 Title: Suspend issue with Dell Venue 11 Pro 7140 Status in linux package in Ubuntu: Incomplete Bug description: Instead of suspending the machine into a state where it can be started quickly, it appears that suspend causes the system to end up in a state which requires a forced start. The power light is off, and the only way to start the machine again is to hold down the power button for more than 5 seconds. A quick check of uptime shows that it did, indeed, start again. I'm attaching a suspend log. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tudor 1785 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 9 10:57:38 2015 HibernationDevice: RESUME=UUID=3acb1340-1be5-453c-a918-25f6b6ff404e InstallationDate: Installed on 2015-07-06 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 114d:1002 Alpha Imaging Technology Corp. Bus 001 Device 002: ID 0bda:5757 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Venue 11 Pro 7140 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=f0dc97e1-7d1c-4d05-a7d8-3cfc8551bdc4 ro quiet splash i915.i915_enable_rc6=1 "acpi_osi=!Windows 2013" vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-07 (1 days ago) dmi.bios.date: 06/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd06/30/2015:svnDellInc.:pnVenue11Pro7140:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+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 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140
** Attachment added: "Image of 5.0.0-rc2 showing dmesg error kernel write locking up. Page 3" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/5230627/+files/IMG_20190120_171227.jpg -- 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/1472832 Title: Suspend issue with Dell Venue 11 Pro 7140 Status in linux package in Ubuntu: Incomplete Bug description: Instead of suspending the machine into a state where it can be started quickly, it appears that suspend causes the system to end up in a state which requires a forced start. The power light is off, and the only way to start the machine again is to hold down the power button for more than 5 seconds. A quick check of uptime shows that it did, indeed, start again. I'm attaching a suspend log. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tudor 1785 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 9 10:57:38 2015 HibernationDevice: RESUME=UUID=3acb1340-1be5-453c-a918-25f6b6ff404e InstallationDate: Installed on 2015-07-06 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 114d:1002 Alpha Imaging Technology Corp. Bus 001 Device 002: ID 0bda:5757 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Venue 11 Pro 7140 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=f0dc97e1-7d1c-4d05-a7d8-3cfc8551bdc4 ro quiet splash i915.i915_enable_rc6=1 "acpi_osi=!Windows 2013" vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-07 (1 days ago) dmi.bios.date: 06/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd06/30/2015:svnDellInc.:pnVenue11Pro7140:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+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 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140
** Attachment added: "Image of 5.0.0-rc2 showing dmesg and sync locking up." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+attachment/5230624/+files/IMG_20190120_170833.jpg -- 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/1472832 Title: Suspend issue with Dell Venue 11 Pro 7140 Status in linux package in Ubuntu: Incomplete Bug description: Instead of suspending the machine into a state where it can be started quickly, it appears that suspend causes the system to end up in a state which requires a forced start. The power light is off, and the only way to start the machine again is to hold down the power button for more than 5 seconds. A quick check of uptime shows that it did, indeed, start again. I'm attaching a suspend log. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tudor 1785 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 9 10:57:38 2015 HibernationDevice: RESUME=UUID=3acb1340-1be5-453c-a918-25f6b6ff404e InstallationDate: Installed on 2015-07-06 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 114d:1002 Alpha Imaging Technology Corp. Bus 001 Device 002: ID 0bda:5757 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Venue 11 Pro 7140 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=f0dc97e1-7d1c-4d05-a7d8-3cfc8551bdc4 ro quiet splash i915.i915_enable_rc6=1 "acpi_osi=!Windows 2013" vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-07 (1 days ago) dmi.bios.date: 06/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd06/30/2015:svnDellInc.:pnVenue11Pro7140:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+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 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140
For @penalvch: 1) $ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date A17 09/10/2018 2) I tried with kernel 4.20.3 and got a similar result to above (with the "Not Tainted" Network Manager), however after suspending and resuming, the machine consistently locks up as soon as the disk is written to, meaning that I couldn't even get a copy of the report! In 5.0.0-rc2, there is no complaint from the kernel, however, the WiFi adapter still doesn't work and the machine also locks up consistently after the resume so I couldn't get a report from that either! :-( (I can probably grab a photo with my phone if you really need it.) If it had just been a case of the WiFi adapter not working, I'd say this was fixed, but I think the locking up in mainline kernels may indicate a deeper problem from the suspend. -- 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/1472832 Title: Suspend issue with Dell Venue 11 Pro 7140 Status in linux package in Ubuntu: Incomplete Bug description: Instead of suspending the machine into a state where it can be started quickly, it appears that suspend causes the system to end up in a state which requires a forced start. The power light is off, and the only way to start the machine again is to hold down the power button for more than 5 seconds. A quick check of uptime shows that it did, indeed, start again. I'm attaching a suspend log. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tudor 1785 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 9 10:57:38 2015 HibernationDevice: RESUME=UUID=3acb1340-1be5-453c-a918-25f6b6ff404e InstallationDate: Installed on 2015-07-06 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 114d:1002 Alpha Imaging Technology Corp. Bus 001 Device 002: ID 0bda:5757 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Venue 11 Pro 7140 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=f0dc97e1-7d1c-4d05-a7d8-3cfc8551bdc4 ro quiet splash i915.i915_enable_rc6=1 "acpi_osi=!Windows 2013" vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-07 (1 days ago) dmi.bios.date: 06/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd06/30/2015:svnDellInc.:pnVenue11Pro7140:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+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 1803830] Re: Mouse pointer trailing and disturbing the content that the pointer "touches"
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1803830 Title: Mouse pointer trailing and disturbing the content that the pointer "touches" Status in linux package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: So , when i attached second monitor HPL1706 to my laptop HP 250 g5, my mouse pointer started to leave trail that blinks. This trail disappears when the mouse pointer hits the "quick select bar?" on the left side of main screen, or when the pointer goes on the second monitor where it continues to leave this trail. Pointer also disturbs the content that it "hits" or it places small box of the area it was moment before - like if i take a peace of puzzle, copy it and place over some other peace of puzzle so that main picture is not clear. Right click also resets the bug. Pointer disappears and re-appears if it's not moving but when it's not visible, the trail is. This interval is around 1 second. This affects my, already weak, PC performance. 1 time, when i logged into my account after being afk, this bug was not present 100% until i tried to move sublime's window around the screen. When i disconnect the second monitor, the bug is present but in much smaller dose. Every edit on this message (every letter i enter etc.) affects this bug - it changes which pointers will be visible on the screen. Lets say there is 10 pointers on screen - now its visible pointers 1,4,8 and when i press a letter it changes to 2,5,9 etc. something like this. If there is no action this change is automatic after approx. 1 second. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_38_41_generic_45 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 17 16:42:58 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:81f1] InstallationDate: Installed on 2018-10-25 (22 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP 250 G5 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81F1 dmi.board.vendor: HP dmi.board.version: 64.31 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd08/01/2016:svnHP:pnHP250G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81F1:rvr64.31:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=250 dmi.product.name: HP 250 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803830/+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 1803830] Re: Mouse pointer trailing and disturbing the content that the pointer "touches"
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1803830 Title: Mouse pointer trailing and disturbing the content that the pointer "touches" Status in linux package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: So , when i attached second monitor HPL1706 to my laptop HP 250 g5, my mouse pointer started to leave trail that blinks. This trail disappears when the mouse pointer hits the "quick select bar?" on the left side of main screen, or when the pointer goes on the second monitor where it continues to leave this trail. Pointer also disturbs the content that it "hits" or it places small box of the area it was moment before - like if i take a peace of puzzle, copy it and place over some other peace of puzzle so that main picture is not clear. Right click also resets the bug. Pointer disappears and re-appears if it's not moving but when it's not visible, the trail is. This interval is around 1 second. This affects my, already weak, PC performance. 1 time, when i logged into my account after being afk, this bug was not present 100% until i tried to move sublime's window around the screen. When i disconnect the second monitor, the bug is present but in much smaller dose. Every edit on this message (every letter i enter etc.) affects this bug - it changes which pointers will be visible on the screen. Lets say there is 10 pointers on screen - now its visible pointers 1,4,8 and when i press a letter it changes to 2,5,9 etc. something like this. If there is no action this change is automatic after approx. 1 second. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_38_41_generic_45 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 17 16:42:58 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:81f1] InstallationDate: Installed on 2018-10-25 (22 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP 250 G5 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81F1 dmi.board.vendor: HP dmi.board.version: 64.31 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd08/01/2016:svnHP:pnHP250G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81F1:rvr64.31:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=250 dmi.product.name: HP 250 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803830/+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 1803830] Re: Mouse pointer trailing and disturbing the content that the pointer "touches"
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- 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/1803830 Title: Mouse pointer trailing and disturbing the content that the pointer "touches" Status in linux package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: So , when i attached second monitor HPL1706 to my laptop HP 250 g5, my mouse pointer started to leave trail that blinks. This trail disappears when the mouse pointer hits the "quick select bar?" on the left side of main screen, or when the pointer goes on the second monitor where it continues to leave this trail. Pointer also disturbs the content that it "hits" or it places small box of the area it was moment before - like if i take a peace of puzzle, copy it and place over some other peace of puzzle so that main picture is not clear. Right click also resets the bug. Pointer disappears and re-appears if it's not moving but when it's not visible, the trail is. This interval is around 1 second. This affects my, already weak, PC performance. 1 time, when i logged into my account after being afk, this bug was not present 100% until i tried to move sublime's window around the screen. When i disconnect the second monitor, the bug is present but in much smaller dose. Every edit on this message (every letter i enter etc.) affects this bug - it changes which pointers will be visible on the screen. Lets say there is 10 pointers on screen - now its visible pointers 1,4,8 and when i press a letter it changes to 2,5,9 etc. something like this. If there is no action this change is automatic after approx. 1 second. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_38_41_generic_45 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 17 16:42:58 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:81f1] InstallationDate: Installed on 2018-10-25 (22 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP 250 G5 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-38-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81F1 dmi.board.vendor: HP dmi.board.version: 64.31 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd08/01/2016:svnHP:pnHP250G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81F1:rvr64.31:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=250 dmi.product.name: HP 250 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803830/+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 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140
** Tags removed: bios-outdated-a17 ** Tags added: latest-bios-a17 -- 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/1472832 Title: Suspend issue with Dell Venue 11 Pro 7140 Status in linux package in Ubuntu: Incomplete Bug description: Instead of suspending the machine into a state where it can be started quickly, it appears that suspend causes the system to end up in a state which requires a forced start. The power light is off, and the only way to start the machine again is to hold down the power button for more than 5 seconds. A quick check of uptime shows that it did, indeed, start again. I'm attaching a suspend log. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-generic (not installed) ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1 Uname: Linux 3.19.0-22-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tudor 1785 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 9 10:57:38 2015 HibernationDevice: RESUME=UUID=3acb1340-1be5-453c-a918-25f6b6ff404e InstallationDate: Installed on 2015-07-06 (2 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 114d:1002 Alpha Imaging Technology Corp. Bus 001 Device 002: ID 0bda:5757 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Venue 11 Pro 7140 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic root=UUID=f0dc97e1-7d1c-4d05-a7d8-3cfc8551bdc4 ro quiet splash i915.i915_enable_rc6=1 "acpi_osi=!Windows 2013" vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-22-generic N/A linux-backports-modules-3.19.0-22-generic N/A linux-firmware 1.143.1 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-07-07 (1 days ago) dmi.bios.date: 06/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd06/30/2015:svnDellInc.:pnVenue11Pro7140:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1472832/+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 1751268] Re: bionic desktop does not boot with external monitor attached - [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck / vblank wait timed out on crt
** Changed in: linux (Ubuntu) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) ** Changed in: linux (Ubuntu Bionic) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) -- 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/1751268 Title: bionic desktop does not boot with external monitor attached - [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck / vblank wait timed out on crtc 1 Status in Linux: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Ubuntu Desktop Bionic up to date System doesn't boot with an external monitor attached. There is this message in the journal (full journal attached for this boot) fbcon: inteldrmfb (fb0) is primary device [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck vblank wait timed out on crtc 1 [ cut here ] WARNING: CPU: 3 PID: 201 at /build/linux-UKCsxy/linux-4.13.0/drivers/gpu/drm/drm_vblank.c:1090 drm_wait_one_vblank+0x19b/0x1b0 [drm] Modules linked in: hid_lenovo uas usb_storage rtsx_usb_sdmmc rtsx_usb hid_generic usbhid hid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse ahci libahci drm wmi video CPU: 3 PID: 201 Comm: kworker/u8:6 Tainted: G U 4.13.0-32-generic #35-Ubuntu Hardware name: ASUSTeK COMPUTER INC. UX32VD/UX32VD, BIOS UX32VD.214 01/29/2013 Workqueue: events_unbound async_run_entry_fn task: 9760d81cae80 task.stack: b01dc1fb8000 RIP: 0010:drm_wait_one_vblank+0x19b/0x1b0 [drm] RSP: 0018:b01dc1fbb7c8 EFLAGS: 00010282 RAX: 001f RBX: 9760d708 RCX: RDX: RSI: 0002 RDI: 0246 RBP: b01dc1fbb828 R08: 001f R09: 0002af84 R10: b01dc1fbb7c8 R11: 041b R12: 0001 R13: 0170 R14: 0001 R15: FS: () GS:9760eef8() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f156d6d68f0 CR3: 00024660a002 CR4: 001606e0 Call Trace: ? wait_woken+0x80/0x80 ironlake_crtc_enable+0x477/0xc00 [i915] ? gen6_write8+0x190/0x190 [i915] intel_update_crtc+0x4b/0xe0 [i915] intel_update_crtcs+0x5b/0x80 [i915] intel_atomic_commit_tail+0x254/0xf90 [i915] ? __schedule+0x293/0x880 intel_atomic_commit+0x3d5/0x490 [i915] ? drm_atomic_check_only+0x37b/0x540 [drm] drm_atomic_commit+0x4b/0x50 [drm] restore_fbdev_mode+0x15e/0x270 [drm_kms_helper] drm_fb_helper_restore_fbdev_mode_unlocked+0x2e/0x80 [drm_kms_helper] drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper] intel_fbdev_set_par+0x1a/0x70 [i915] fbcon_init+0x484/0x650 visual_init+0xd6/0x130 do_bind_con_driver+0x1fc/0x410 do_take_over_console+0x82/0x1a0 do_fbcon_takeover+0x5c/0xb0 fbcon_event_notify+0x587/0x780 notifier_call_chain+0x4a/0x70 blocking_notifier_call_chain+0x43/0x60 fb_notifier_call_chain+0x1b/0x20 register_framebuffer+0x24d/0x360 drm_fb_helper_initial_config+0x249/0x400 [drm_kms_helper] intel_fbdev_initial_config+0x18/0x30 [i915] async_run_entry_fn+0x36/0x150 process_one_work+0x1e7/0x410 worker_thread+0x4b/0x420 kthread+0x125/0x140 ? process_one_work+0x410/0x410 ? kthread_create_on_node+0x70/0x70 ret_from_fork+0x1f/0x30 Code: ff e8 da 3b 4c d6 48 8b 7d a0 48 8d 75 a8 e8 dd 93 50 d6 45 85 ff 0f 85 0c ff ff ff 44 89 e6 48 c7 c7 d8 eb 3d c0 e8 b6 46 52 d6 <0f> ff e9 f6 fe ff ff 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 ---[ end trace a1db7ccd0b5e4dfc ]--- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: j-lallement 3671 F pulseaudio /dev/snd/controlC0: j-lallement 3671 F pulseaudio /dev/snd/controlC1: j-lallement 3671 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Feb 23 13:58:39 2018 InstallationDate: Installed on 2013-09-03 (1633 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A
[Kernel-packages] [Bug 1472832] Re: Suspend issue with Dell Venue 11 Pro 7140
Ok. I've had some partial success with the addition of: [Sleep] SuspendState=freeze in /etc/systemd/sleep.conf However, I also lose the wifi in the process. The kernel reports: [ 69.744693] [ cut here ] [ 69.744695] Timeout waiting for hardware access (CSR_GP_CNTRL 0x) [ 69.744730] WARNING: CPU: 2 PID: 1323 at drivers/net/wireless/intel/iwlwifi/pcie/trans.c:2008 iwl_trans_pcie_grab_nic_access+0x1e8/0x220 [iwlwifi] [ 69.744731] Modules linked in: usbhid rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm cmac ipmi_devintf ipmi_msghandler bnep binfmt_misc nls_iso8859_1 snd_soc_sst_broadwell dell_wmi wmi_bmof snd_soc_sst_haswell_pcm snd_soc_sst_firmware snd_soc_sst_ipc snd_soc_sst_dsp intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel dell_laptop pcbc dell_smbios dell_wmi_descriptor dcdbas aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_rapl_perf joydev snd_hda_codec_hdmi cdc_mbim serio_raw cdc_acm btusb cdc_wdm uvcvideo btrtl arc4 cdc_ncm snd_soc_rt298 btbcm input_leds btintel videobuf2_vmalloc usbnet videobuf2_memops mii bluetooth videobuf2_v4l2 videobuf2_common snd_hda_intel videodev [ 69.744760] ecdh_generic media snd_hda_codec iwlmvm snd_hda_core mac80211 hid_sensor_incl_3d snd_soc_rt286 snd_hwdep hid_sensor_rotation i915 snd_soc_rl6347a snd_seq_midi snd_soc_core iwlwifi snd_compress snd_seq_midi_event ac97_bus snd_rawmidi snd_pcm_dmaengine snd_pcm hid_sensor_magn_3d hid_sensor_gyro_3d hid_sensor_als hid_sensor_accel_3d hid_sensor_trigger industrialio_triggered_buffer kfifo_buf snd_seq drm_kms_helper hid_sensor_iio_common hid_multitouch drm cfg80211 industrialio snd_seq_device snd_timer mac_hid wmi i2c_algo_bit fb_sys_fops mei_me snd dw_dmac syscopyarea intel_vbtn sysfillrect sysimgblt dw_dmac_core snd_soc_sst_acpi processor_thermal_device snd_soc_acpi soc_button_array int3400_thermal soundcore video int3403_thermal mei snd_soc_acpi_intel_match sparse_keymap acpi_thermal_rel [ 69.744786] int340x_thermal_zone intel_soc_dts_iosf acpi_pad sch_fq_codel parport_pc ppdev lp parport sunrpc ip_tables x_tables autofs4 mmc_block hid_sensor_custom hid_sensor_hub hid_generic sdhci_pci cqhci sdhci ahci i2c_i801 libahci lpc_ich i2c_hid hid [last unloaded: usbhid] [ 69.744801] CPU: 2 PID: 1323 Comm: NetworkManager Tainted: G OE 4.18.0-13-generic #14-Ubuntu [ 69.744801] Hardware name: Dell Inc. Venue 11 Pro 7140/0XMVMH, BIOS A17 09/10/2018 [ 69.744807] RIP: 0010:iwl_trans_pcie_grab_nic_access+0x1e8/0x220 [iwlwifi] [ 69.744807] Code: 2f f9 49 8d 56 08 bf 00 20 00 00 e8 d2 15 d2 f7 e9 31 ff ff ff 89 c6 48 c7 c7 50 b4 5a c0 c6 05 6f 6c 02 00 01 e8 ca 3c d0 f7 <0f> 0b e9 ec fe ff ff 48 8b 7b 30 48 c7 c1 b8 b4 5a c0 31 d2 31 f6 [ 69.744830] RSP: 0018:ba2501ecb190 EFLAGS: 00010086 [ 69.744831] RAX: RBX: 965a4f7f0018 RCX: 0006 [ 69.744832] RDX: 0007 RSI: 0086 RDI: 965a5e5164b0 [ 69.744833] RBP: ba2501ecb1b0 R08: 0001 R09: 03a9 [ 69.744834] R10: 0004 R11: R12: 965a4f7f8f50 [ 69.744834] R13: ba2501ecb1c0 R14: R15: 965a4f7f0220 [ 69.744836] FS: 7f8e1b5e5bc0() GS:965a5e50() knlGS: [ 69.744837] CS: 0010 DS: ES: CR0: 80050033 [ 69.744837] CR2: 55f0beff4010 CR3: 0001fd4e2001 CR4: 003606e0 [ 69.744838] DR0: DR1: DR2: [ 69.744839] DR3: DR6: fffe0ff0 DR7: 0400 [ 69.744840] Call Trace: [ 69.744846] iwl_write_prph+0x3d/0x90 [iwlwifi] [ 69.744852] iwl_pcie_apm_init+0x1db/0x240 [iwlwifi] [ 69.744858] iwl_trans_pcie_start_hw+0x52/0x1d0 [iwlwifi] [ 69.744864] iwl_mvm_up+0x3c/0x9c0 [iwlmvm] [ 69.744867] ? skb_dequeue+0x59/0x70 [ 69.744869] ? wireless_nlevent_flush+0x78/0x80 [ 69.744874] __iwl_mvm_mac_start+0x29b/0x300 [iwlmvm] [ 69.744880] iwl_mvm_mac_start+0x4c/0x130 [iwlmvm] [ 69.744882] ? inetdev_event+0x77/0x500 [ 69.744896] drv_start+0x48/0x100 [mac80211] [ 69.744909] ieee80211_do_open+0x436/0x840 [mac80211] [ 69.744922] ieee80211_open+0x52/0x60 [mac80211] [ 69.744924] __dev_open+0xd5/0x170 [ 69.744925] __dev_change_flags+0x184/0x1f0 [ 69.744926] dev_change_flags+0x27/0x60 [ 69.744928] do_setlink+0x307/0xe10 [ 69.744933] ? iwl_pcie_txq_inc_wr_ptr+0x97/0x110 [iwlwifi] [ 69.744936] ? nla_parse+0xbf/0xe0 [ 69.744938] ? inet6_validate_link_af+0x4f/0x70 [ 69.744939] ? nla_parse+0x35/0xe0 [ 69.744941] rtnl_newlink+0x511/0x8c0 [ 69.744943] ? __snmp6_fill_stats64.isra.57+0xf6/0x120 [ 69.744945] ? __nla_reserve+0x41/0x50 [ 69.744946] ? __nla_put+0x20/0x30 [ 69.744949] ? _raw_read_unlock_bh+0x20/0x30 [ 69.744950]
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
Hi, I have a similar problem with a Razer Blade 14 (2017). After returning from suspend the usb-c dock dies from time to time (display output via hdmi is still working, just the usb host is dead). If you need anymore information, please let me know. Matthias -- 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/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd
[Kernel-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
uname -a Linux one 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1789924] Re: Missing Intel GPU pci-id's
Clean install Ubuntu 18.04 Bionic on Asus Z390 Prime with Intel i5-9600K. - Enabled -proposed repo - apt update && apt upgrade Now graphics chip is correctly identified: $ glxinfo | grep OpenGL OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) HD Graphics (Coffeelake 3x8 GT2) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.2 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 18.2.2 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.2 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: -- 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/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1812514] [NEW] Sync cpu-checker 0.7-1 (main) from Debian unstable (main)
Public bug reported: Please sync cpu-checker 0.7-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: No Ubuntu delta. Debian uploaded the package exactly as it currently appears in Ubuntu. Changelog entries since current disco version 0.7-0ubuntu7: cpu-checker (0.7-1) unstable; urgency=medium [ Hans-Christoph Steiner ] * Upload to Debian, after approval from Kees Cook -- Kees Cook Thu, 10 Jan 2019 23:13:19 +0100 ** Affects: cpu-checker (Ubuntu) Importance: Wishlist Status: New ** Changed in: cpu-checker (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to cpu-checker in Ubuntu. https://bugs.launchpad.net/bugs/1812514 Title: Sync cpu-checker 0.7-1 (main) from Debian unstable (main) Status in cpu-checker package in Ubuntu: New Bug description: Please sync cpu-checker 0.7-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: No Ubuntu delta. Debian uploaded the package exactly as it currently appears in Ubuntu. Changelog entries since current disco version 0.7-0ubuntu7: cpu-checker (0.7-1) unstable; urgency=medium [ Hans-Christoph Steiner ] * Upload to Debian, after approval from Kees Cook -- Kees Cook Thu, 10 Jan 2019 23:13:19 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpu-checker/+bug/1812514/+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 1751268]
Sorry for the long silence. Going has been slow: it takes a while to do a tweak/test/reboot/hang cycle. Especially since the disk controller gets munged upon the bug happening, even persisting across a power cycle (!) about 50% of the time (I have no idea how such a thing is even possible). And, this device is my "get work done" laptop, using the 4.14 kernel which is perfectly happy. Anyway: tried a different approach. Threw in a spare disk, and tried a clean install of F29 and Kubuntu 18.04.1, in case cruft was to blame. F29 installed from dvd... but the kernel installed to disk didn't boot once the first install pass finished. Kubuntu's install dvd wouldn't even boot past the spinny "it's starting to boot" graphics screen. In both cases, since things are "graphical boot" and "quiet", there's no feedback as to exactly what went wrong, and the system hangs too hard to switch to a different vtty, but it felt the same as the hangs described above. Trying with the latest/last F27 kernel (yes, it's EOL now) 4.18.19-100, tried all permutations of integrated, discrete, and optimus bios settings, excluding nouveau drivers, and the nvidia proprietary blob. Sometimes it can get a clean boot - but then the sata controller goes out to lunch as soon as a write cache flush happens. Which makes me think the kms problem which started this thread is a symptom rather than the problem, just the one which usually triggers first. This is consistent with the problems getting log traces of the problems described above, because a lunched sata controller can't log errors. Went back to drm-tip. See that it's kernel 5.0 now, cool. This minimally configured kernel continues to work. I've enabled the extra features needed to run the laptop, no problems. So: the bug is at the very least triggered by one of the (myriad) of enabled kernel options in the distro stock kernels. It feels to me like the old days of unprotected flat memory space where you could POKE random values into random addresses and watch the system fall apart: with the initial kms call being the most sensitive to it, and things unravel into thrashing the disk controller. Parameter space is too vast for me to find the culprit with intermittent effort and a logging system that's often the first victim of the bug. So, I'm ready to punt, documenting this here in case someone else with more clues googles it is the only remaining thing I can do. Time to just return to the 1990's and compile my own kernel :( At least git now makes tracking updates easier than it used to be in the Bad Old Days. -- 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/1751268 Title: bionic desktop does not boot with external monitor attached - [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck / vblank wait timed out on crtc 1 Status in Linux: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Ubuntu Desktop Bionic up to date System doesn't boot with an external monitor attached. There is this message in the journal (full journal attached for this boot) fbcon: inteldrmfb (fb0) is primary device [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck vblank wait timed out on crtc 1 [ cut here ] WARNING: CPU: 3 PID: 201 at /build/linux-UKCsxy/linux-4.13.0/drivers/gpu/drm/drm_vblank.c:1090 drm_wait_one_vblank+0x19b/0x1b0 [drm] Modules linked in: hid_lenovo uas usb_storage rtsx_usb_sdmmc rtsx_usb hid_generic usbhid hid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse ahci libahci drm wmi video CPU: 3 PID: 201 Comm: kworker/u8:6 Tainted: G U 4.13.0-32-generic #35-Ubuntu Hardware name: ASUSTeK COMPUTER INC. UX32VD/UX32VD, BIOS UX32VD.214 01/29/2013 Workqueue: events_unbound async_run_entry_fn task: 9760d81cae80 task.stack: b01dc1fb8000 RIP: 0010:drm_wait_one_vblank+0x19b/0x1b0 [drm] RSP: 0018:b01dc1fbb7c8 EFLAGS: 00010282 RAX: 001f RBX: 9760d708 RCX: RDX: RSI: 0002 RDI: 0246 RBP: b01dc1fbb828 R08: 001f R09: 0002af84 R10: b01dc1fbb7c8 R11: 041b R12: 0001 R13: 0170 R14: 0001 R15: FS: () GS:9760eef8() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f156d6d68f0 CR3: 00024660a002 CR4: 001606e0 Call Trace: ? wait_woken+0x80/0x80 ironlake_crtc_enable+0x477/0xc00 [i915] ? gen6_write8+0x190/0x190 [i915] intel_update_crtc+0x4b/0xe0 [i915] intel_update_crtcs+0x5b/0x80 [i915] intel_atomic_commit_tail+0x254/0xf90 [i915] ? __schedule+0x293/0x880 inte
[Kernel-packages] [Bug 1798807] Re: bcmwl-kernel-source fails to install if Nvidia card present in the absence of a network connection
** Package changed: ubuntu => bcmwl (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1798807 Title: bcmwl-kernel-source fails to install if Nvidia card present in the absence of a network connection Status in bcmwl package in Ubuntu: New Bug description: When enabling the proprietary packages option on the Ubuntu installation of xenial, bionic or cosmic x86_64 on a machine with both a wireless card requiring the bcmwl-kernel-source package and an additional Nvidia card present, the installation of the bcmwl-kernel- source package doesn't occur. While the current installer doesn't allow the selected proprietary driver packages to be viewed priorto completing their installation, I assume the problem is, for a machine without a network connection, that only the bcmwl-kernel-source package is available on the Live iso image and that the absence of the nvidia packages is fouling the installation of the bcmwl-kernel-source package. This issue was discovered on a MacPro 3,1 which originally had a ATI HD2600-XT graphics card as well as an Airport Extreme card. For that combination, the xenial, bionic and cosmic installers all were able to install the bcmwl-kernel-source package when proprietary driver package installation was enabled in the installer. After swapping out that ATI graphics card for a Nvidia GTX-680, I found that the xenial, bionic and cosmic installers now failed to install the bcmwl-kernel- source package in the presence of the Nvidia card without access to a network connection during the installation. So I believe that the installer needs to be more careful not to demand installation of proprietary driver packages that are not present on the Live image in the absence of a network connection. Currently, one has to either connect the machine to the ethernet to allow for network access to the repos for the installation of the bcmwl-kernel-source package to succeed or manually install the bcmwl- kernel-source package and its dependencies from the appropriate sub- directories in the pool directory of the Live usb image afterwards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1798807/+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 1798807] [NEW] bcmwl-kernel-source fails to install if Nvidia card present in the absence of a network connection
You have been subscribed to a public bug: When enabling the proprietary packages option on the Ubuntu installation of xenial, bionic or cosmic x86_64 on a machine with both a wireless card requiring the bcmwl-kernel-source package and an additional Nvidia card present, the installation of the bcmwl-kernel-source package doesn't occur. While the current installer doesn't allow the selected proprietary driver packages to be viewed priorto completing their installation, I assume the problem is, for a machine without a network connection, that only the bcmwl-kernel-source package is available on the Live iso image and that the absence of the nvidia packages is fouling the installation of the bcmwl-kernel-source package. This issue was discovered on a MacPro 3,1 which originally had a ATI HD2600-XT graphics card as well as an Airport Extreme card. For that combination, the xenial, bionic and cosmic installers all were able to install the bcmwl-kernel-source package when proprietary driver package installation was enabled in the installer. After swapping out that ATI graphics card for a Nvidia GTX-680, I found that the xenial, bionic and cosmic installers now failed to install the bcmwl-kernel-source package in the presence of the Nvidia card without access to a network connection during the installation. So I believe that the installer needs to be more careful not to demand installation of proprietary driver packages that are not present on the Live image in the absence of a network connection. Currently, one has to either connect the machine to the ethernet to allow for network access to the repos for the installation of the bcmwl- kernel-source package to succeed or manually install the bcmwl-kernel- source package and its dependencies from the appropriate sub-directories in the pool directory of the Live usb image afterwards. ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- bcmwl-kernel-source fails to install if Nvidia card present in the absence of a network connection https://bugs.launchpad.net/bugs/1798807 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. -- 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 1507472] Re: [MacbookPro12, 1] Suspend resumes immediately due to xhci driver
Michael Gratton: 1) To keep this relevant to upstream, one would want to periodically check for, and test the latest mainline kernel (now 5.0-rc2) as it is released. Could you please advise to the results? 2) Did you contact upstream as noted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/comments/19 ? ** Changed in: linux (Ubuntu) Importance: Medium => Low ** Changed in: linux (Ubuntu) Status: Triaged => Incomplete ** Tags removed: kernel-bug-exists-upstream ** Tags added: needs-upstream-testing -- 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/1507472 Title: [MacbookPro12,1] Suspend resumes immediately due to xhci driver Status in linux package in Ubuntu: Incomplete Bug description: On my MacbookPro12,1 with Wily and Linux 4.2, by default the kernel successfully suspends but then immediately resumes again. The problem seems to be the XHCI controller causing spurious ACPI wakeups. Also, the Broadcom wifi module seems to have problems with suspend/resume, so I am also unloading the `brcmfmac` module prior to suspend and loading it again after resume. WORKAROUND: Disable XHC1 prior to sleeping: > # echo XHC1 > /proc/acpi/wakeup ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse:  USERPID ACCESS COMMAND  /dev/snd/controlC1: mjg1441 F pulseaudio  /dev/snd/controlC0: mjg1441 F pulseaudio CurrentDesktop: GNOME Date: Mon Oct 19 18:13:15 2015 HibernationDevice: RESUME=UUID=bc879a1f-ac27-48ae-82dd-3c81b7307dd0 InstallationDate: Installed on 2015-07-22 (89 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb:  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub  Bus 001 Device 003: ID 05ac:0273 Apple, Inc.  Bus 001 Device 002: ID 05ac:8290 Apple, Inc.  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions:  linux-restricted-modules-4.2.0-16-generic N/A  linux-backports-modules-4.2.0-16-generic N/A  linux-firmware1.149 RfKill:  3: phy0: Wireless LAN   Soft blocked: no   Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-08-27 (52 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B07.1506051617 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B07.1506051617:bd06/05/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/+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 1507472] Re: [MacbookPro12, 1] Suspend resumes immediately due to xhci driver
Selwyn (siilwyn), it will help immensely if you use Ubuntu with the computer the problem is reproducible with and file a new report via a terminal to provide necessary debugging logs: ubuntu-bug linux Please feel free to subscribe me to it. -- 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/1507472 Title: [MacbookPro12,1] Suspend resumes immediately due to xhci driver Status in linux package in Ubuntu: Incomplete Bug description: On my MacbookPro12,1 with Wily and Linux 4.2, by default the kernel successfully suspends but then immediately resumes again. The problem seems to be the XHCI controller causing spurious ACPI wakeups. Also, the Broadcom wifi module seems to have problems with suspend/resume, so I am also unloading the `brcmfmac` module prior to suspend and loading it again after resume. WORKAROUND: Disable XHC1 prior to sleeping: > # echo XHC1 > /proc/acpi/wakeup ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse:  USERPID ACCESS COMMAND  /dev/snd/controlC1: mjg1441 F pulseaudio  /dev/snd/controlC0: mjg1441 F pulseaudio CurrentDesktop: GNOME Date: Mon Oct 19 18:13:15 2015 HibernationDevice: RESUME=UUID=bc879a1f-ac27-48ae-82dd-3c81b7307dd0 InstallationDate: Installed on 2015-07-22 (89 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb:  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub  Bus 001 Device 003: ID 05ac:0273 Apple, Inc.  Bus 001 Device 002: ID 05ac:8290 Apple, Inc.  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions:  linux-restricted-modules-4.2.0-16-generic N/A  linux-backports-modules-4.2.0-16-generic N/A  linux-firmware1.149 RfKill:  3: phy0: Wireless LAN   Soft blocked: no   Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-08-27 (52 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B07.1506051617 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B07.1506051617:bd06/05/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/+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
** Changed in: linux (Ubuntu Trusty)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux (Ubuntu)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
--
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(&dc->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, &wait.wait, 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 1713576] Re: More migrations with constant load
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- 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/1713576 Title: More migrations with constant load Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: == SRU Justification == There is a significantly higher number of task migrations when the load is fixed and not balanced across cores. Benchmark results are posted in the bug description and in the commits git log. This bug is resolved by mainline commit 05b40e057734811ce452344fb3690d09965a7b6a, which is in mailine as of 4.12-rc1. == Fix == commit 05b40e057734811ce452344fb3690d09965a7b6a Author: Srikar Dronamraju Date: Wed Mar 22 23:27:50 2017 +0530 sched/fair: Prefer sibiling only if local group is under-utilized == Regression Potential == Medium, since this commit does touch the scheduler. However, the commit only makes a change to allow a local group to pull a task, if the source group has more number of tasks than the local group. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Comment: #0 - PUVICHAKRAVARTHY RAMACHANDRAN - 2017-08-06 13:44:45 == ---Problem Description--- Significantly higher number of task migrations when the load is fixed but not balanced across cores. ---uname output--- Linux isvbos3 4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- Power9 dd2.0 Machine Type = Power9 ---Steps to Reproduce--- Â Benchmark : Multithreaded - cpu intensive. The system had 2 socket/ 32 cores/ SMT4 mode. When 64 threads was run - the migrations were less over 10s interval. when 80 threads were run - the migrations were very high. Ideally, it should have been very minimal, as the over all load was constant == Comment: #3 - SRIKAR DRONAMRAJU - 2017-08-11 06:56:47 == As suspected (commit : 05b40e0577 : "sched/fair: Prefer sibiling only if local group is under-utilized") https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=05b40e0577 should fix the problem Ran ' perf stat -a -r 5 -e sched:sched_migrate_task /home/srikar/work/ebizzy-0.3/ebizzy -t 35 -S 100' to detect the problem and verify the fix Here is perf stat without fix. Performance counter stats for 'system wide' (5 runs): Â 7,758 sched:sched_migrate_task ( +- 1.28% ) Â 100.015658079 seconds time elapsed ( +- 0.00% ) perf stat with fix. Performance counter stats for 'system wide' (5 runs): Â Â Â 415 sched:sched_migrate_task ( +- 11.74% ) Â 100.016021787 seconds time elapsed ( +- 0.00% ) git describe on upstream kernel says v4.11-rc2 # git describe 05b40e0577 v4.11-rc2-227-g05b40e0 == Comment: #4 - SRIKAR DRONAMRAJU - 2017-08-11 07:05:37 == Attaching the patch that needs to be applied to fix this bug. Verified that patch fixes the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1713576/+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 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
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/1724911
Title:
text VTs are unavailable on desktop after upgrade to Ubuntu 17.10
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Artful:
Fix Released
Bug description:
== SRU Justification ==
After upgrading my laptop to Ubuntu 17.10, I am unable to access gettys on
any of the text-mode VTs on my system.
gdm3 is running on VT1, my user session is running on VT2. I can
switch between these. If I switch to VT3, I know that the VT switch
has happened in the kernel because the X cursor disappears; but the
display retains the output of my X session, and the text console with
getty never appears.
Switching back to VT2 works fine.
The same problem occurs with either Wayland or X.
My laptop is docked with an external monitor, which could be a factor.
(I also notice that during boot, plymouth is only rendered on the
internal monitor, not the external monitor; this may be related). I
have not yet tested whether this problem is reproducible if I undock.
The system is booting with vt.handoff=7, which I believe is still the
default in Ubuntu 17.10.
This bug is a regression in Artful introduced by mainline commit:
7581d5ca2bb ("drm/i915/fbdev: Check for existence of ifbdev->vma before
operations").
It was first found that this bug was fixed in v4.14-rc1. However, after a
lengthy
"Reverse" bisect, the exact commit could not be identified. This is because
the
fix came in via a merge base. A regular bisect was then done to identify
commit
7581d5ca2bb as the offending commit that introduced the bug. Using the file
that this commit touched, a "Reverse" bisect was done again between
7581d5ca2bb..v4.14-rc1. This identified the following commit 88be58be886f as
the fix to this regression.
== Fix ==
commit 88be58be886f1215cc73dc8c273c985eecd7385c
Author: Daniel Vetter
Date: Thu Jul 6 15:00:19 2017 +0200
drm/i915/fbdev: Always forward hotplug events
== Regression Potential ==
This patch fixes a current regression and is a minor one-liner.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1: vorlon24080 F pulseaudio
 /dev/snd/controlC0: vorlon24080 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 09:57:59 2017
HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
InstallationDate: Installed on 2010-09-24 (2582 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64
(20100816.1)
MachineType: LENOVO 2306CTO
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic N/A
 linux-firmware 1.169
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
dmi.bios.date: 10/25/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET97WW (2.57 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2306CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230
dmi.product.name: 2306CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724911/+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 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
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/1729337
Title:
CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Zesty:
Fix Released
Status in linux source package in Artful:
Won't Fix
Bug description:
== SRU Justification ==
The bug reporter stated they have a cluster of servers that applied Xenial
updates
and then were unable to mount CIFS shares after upgrading to 4.4.0-98. The
same machines on 4.4.0-97 do not hit the regression. It was found that the
regression is fixed by mainline commit:
4587eee04e2a ("SMB3: Validate negotiate request must always be signed").
This fix is required in all Ubuntu supported releases. Commit 4587eee04e2a
landed in mailine as of 4.14-rc7. It was also cc'd to upstream stable,
but it has not landed in any stable releases yet, which is the reason for
this SRU.
== Fix ==
commit 4587eee04e2ac7ac3ac9fa2bc164fb6e548f99cd
Author: Steve French
Date: Wed Oct 25 15:58:31 2017 -0500
SMB3: Validate negotiate request must always be signed
== Regression Potential ==
This patch is to fix a regression. It was also cc'd to upstream stable, so
it received addition review upstream.
We have a cluster of servers that applied a security update overnight
and were unable to mount CIFS shares after upgrading to 4.4.0-98. The
same machines on 4.4.0-97 were fine the night before, and are fine
after downgrading. The only error message CIFS would report, even on
verbose, was:
[ 257.089876] CIFS VFS: validate protocol negotiate failed: -11
[ 257.089964] CIFS VFS: cifs_mount failed w/return code = -5
Rebooting did not help. Nor did attempting to mount the share
manually using mount -t cifs.
Here's the offending line from our /etc/fstab (with hostnames
sanitized):
//server/share /mnt/share cifs
rw,user,credentials=/etc/samba/credentials.share,uid=33,gid=33,file_mode=0770,dir_mode=0770
,exec,soft,noserverino,vers=3.0 0 0
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-98-generic 4.4.0-98.121
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116, 1 Nov 1 07:56 seq
 crw-rw 1 root audio 116, 33 Nov 1 07:56 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.10
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: Wed Nov 1 08:49:47 2017
HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1
InstallationDate: Installed on 2016-12-16 (319 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
PciMultimedia:
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic
root=/dev/mapper/ubuntu--template--vg-root ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-98-generic N/A
 linux-backports-modules-4.4.0-98-generic N/A
 linux-firmware1.157.13
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/21/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729337/+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
[Kernel-packages] [Bug 1721065] Re: NULL pointer dereference in tty_write() in kernel 4.4.0-93.116+
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- 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/1721065 Title: NULL pointer dereference in tty_write() in kernel 4.4.0-93.116+ Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Sometimes an Ubuntu kernel 4.4.0-93+ panics in the following way: [ 11.185347] BUG: unable to handle kernel NULL pointer dereference at (null) [ 11.185778] IP: [] tty_write+0x83/0x2d0 [ 11.186115] PGD 0 [ 11.186270] Oops: [#1] SMP [ 11.186506] Modules linked in: prl_fs(POE) prl_eth(POE) gpio_ich ppdev snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm s nd_timer input_leds snd serio_raw soundcore lpc_ich shpchp sbs prl_tg(POE) sbshc pvpanic parport_pc parport mac_hid auto fs4 psmouse ahci libahci pata_acpi fjes [ 11.188034] CPU: 0 PID: 1 Comm: systemd Tainted: P OE 4.4.0-96-generic #119-Ubuntu [ 11.188482] Hardware name: Parallels Software International Inc. Parallels Virtual Platform/Parallels Virtual Platfor m, BIOS 13.1.0 (43104) 09/26/2017 [ 11.189156] task: 88003db8 ti: 88003db88000 task.ti: 88003db88000 [ 11.189546] RIP: 0010:[] [] tty_write+0x83/0x2d0 [ 11.189964] RSP: :88003db8bcc8 EFLAGS: 00010246 [ 11.190255] RAX: RBX: 8800392dd800 RCX: [ 11.190628] RDX: RSI: RDI: 8800392dd828 [ 11.191002] RBP: 88003db8bd18 R08: 88003db88000 R09: [ 11.191398] R10: 005c R11: 00401ce0 R12: 002f [ 11.191775] R13: 88003584ae70 R14: 55c8eab15f20 R15: 88003584ae00 [ 11.192152] FS: 7f649d1418c0() GS:88003de0() knlGS: [ 11.192573] CS: 0010 DS: ES: CR0: 80050033 [ 11.192882] CR2: CR3: 3d3b6000 CR4: 06f0 [ 11.193264] Stack: [ 11.193404] 813953ba 88003db8bd08 813493bd [ 11.193837] 002f 88003584ae00 55c8eab15f20 88003584ae70 [ 11.194267] 002f 88003db8bf18 88003db8bd28 8120f878 [ 11.194700] Call Trace: [ 11.194884] [] ? apparmor_file_permission+0x1a/0x20 [ 11.195248] [] ? security_file_permission+0x3d/0xc0 [ 11.195621] [] __vfs_write+0x18/0x40 [ 11.195916] [] vfs_write+0xa9/0x1a0 [ 11.196202] [] redirected_tty_write+0x60/0xa0 [ 11.196532] [] ? tty_write+0x2d0/0x2d0 [ 11.196830] [] do_loop_readv_writev+0x75/0xa0 [ 11.197160] [] ? tty_write+0x2d0/0x2d0 [ 11.197458] [] do_readv_writev+0x212/0x230 [ 11.198439] [] ? do_vfs_ioctl+0x29f/0x490 [ 11.199374] [] vfs_writev+0x39/0x50 [ 11.200268] [] SyS_writev+0x59/0xf0 [ 11.201144] [] ? SyS_ioctl+0x79/0x90 [ 11.202049] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 11.202980] Code: 47 02 00 00 48 8b 93 e0 01 00 00 83 e2 02 0f 85 37 02 00 00 48 83 78 50 00 0f 84 38 02 00 00 48 89 df e8 11 7f 00 00 48 89 45 b0 <48> 8b 00 48 8b 40 40 48 89 c2 48 89 45 c0 48 c7 c0 fb ff ff ff [ 11.208047] RIP [] tty_write+0x83/0x2d0 [ 11.208942] RSP [ 11.209713] CR2: [ 11.210517] ---[ end trace 3b933544655b49b8 ]--- [ 11.335210] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 [ 11.335210] [ 11.337095] Kernel Offset: disabled [ 11.338184] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0009 The crash occurs here 1227 static ssize_t tty_write(struct file *file, const char __user *buf, [...] 1243 ld = tty_ldisc_ref_wait(tty); 1244 if (!ld->ops->write) // <=== 1245 ret = -EIO; 1246 else 1247 ret = do_tty_write(ld->ops->write, tty, file, buf, count); because tty_ldisc_ref_wait() returned NULL. It seems the issue has been introduced into 4.4.0-93+ kernels by the fix for the bug #1709126: according to the version 4.4.0-93.116 changelog the patch "tty: Destroy ldisc instance on hangup" (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=892d1fa7eaaed9d3c04954cb140c34ebc3393932) that allowed tty_ldisc_ref_wait() to return NULL has been backported into the Ubuntu Linux kernel 4.4.0-93+. However, the patch "tty: Prepare for destroying line discipline on hangup" (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e55afd11a48354c810caf6b6ad4c103016a88230) from the same patchset (https://lkml.org/lkml/2015/11/27/476) that prepares tty_ldisc_ref_wait() callers for this hasn't been backported. Additional info: Kernel version: Linux version 4.4.0-96-generic (buildd@lgw0
[Kernel-packages] [Bug 1733901] Re: /build/linux-KM2a5S/linux-4.13.0/drivers/usb/core/devio.c is crashing on kvm / qemu machine bootup
** Changed in: linux (Ubuntu) Status: In Progress => Invalid -- 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/1733901 Title: /build/linux-KM2a5S/linux-4.13.0/drivers/usb/core/devio.c is crashing on kvm / qemu machine bootup Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Won't Fix Bug description: since the upgrade to kernel 4.13.0-17 on ubuntu mate 17.10 the usb module is crashing if I bootup my windows 10 kvm / qemu machine. Its managed via virtmanager. Here is the trace: Nov 22 16:37:24 octo kernel: [ 789.262361] [ cut here ] Nov 22 16:37:24 octo kernel: [ 789.262365] WARNING: CPU: 0 PID: 2978 at /build/linux-KM2a5S/linux-4.13.0/drivers/usb/core/devio.c:1583 proc_do_submiturb+0x993/0xd50 Nov 22 16:37:24 octo kernel: [ 789.262365] Modules linked in: vhost_net vhost macvtap macvlan tap bnep ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_co nntrack nf_conntrack xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter nls_iso8859_1 snd_hda_codec_hdmi snd_usb_audio snd_usbmidi_lib snd_seq_midi snd_hda_codec_realtek snd_seq_midi_event snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel uvcvideo kvm snd_rawmidi videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_hda_intel videobuf2_core intel_cstate snd_hda_codec videodev snd_seq intel_rapl_perf snd_hda_core snd_seq_device media snd_hwdep snd_pcm serio_raw snd_timer eeepc_wmi snd asus_wmi mei_me Nov 22 16:37:24 octo kernel: [ 789.262387] sparse_keymap wmi_bmof soundcore input_leds joydev shpchp mei hci_uart btbcm serdev btqca btintel bluetooth ecdh_generic intel_lpss_acpi intel_lpss acpi_als acpi_pad kfifo_buf mac_hid industrialio coretemp vfio_pci vfio_virqfd irqbypass vfio_iommu_type1 vfio parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 hid_generic usbhid mxm_wmi i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 i2c_alg o_bit crypto_simd drm_kms_helper glue_helper cryptd syscopyarea e1000e sysfillrect sysimgblt fb_sys_fops psmouse ptp drm pps_core ahci libahci wmi video pinctrl_sunrisepoint i2c_hid pinctrl_intel hid Nov 22 16:37:24 octo kernel: [ 789.262416] CPU: 0 PID: 2978 Comm: qemu-system-x86 Not tainted 4.13.0-17-generic #20-Ubuntu Nov 22 16:37:24 octo kernel: [ 789.262416] Hardware name: System manufacturer System Product Name/PRIME Z270-A, BIOS 0906 03/22/2017 Nov 22 16:37:24 octo kernel: [ 789.262417] task: 95633c5b5f00 task.stack: b6e844318000 Nov 22 16:37:24 octo kernel: [ 789.262418] RIP: 0010:proc_do_submiturb+0x993/0xd50 Nov 22 16:37:24 octo kernel: [ 789.262419] RSP: 0018:b6e84431bd38 EFLAGS: 00010282 Nov 22 16:37:24 octo kernel: [ 789.262420] RAX: 002a RBX: 9562b500c6c0 RCX: 8905fd08 Nov 22 16:37:24 octo kernel: [ 789.262420] RDX: RSI: 0092 RDI: 0247 Nov 22 16:37:24 octo kernel: [ 789.262421] RBP: b6e84431bdc0 R08: 002a R09: 040e Nov 22 16:37:24 octo kernel: [ 789.262421] R10: 0200 R11: R12: 0001 Nov 22 16:37:24 octo kernel: [ 789.262422] R13: 95659f8b3540 R14: 55ef781efcf8 R15: b6e84431be00 Nov 22 16:37:24 octo kernel: [ 789.262423] FS: 7f88e0b39c80() GS:9565bec0() knlGS: Nov 22 16:37:24 octo kernel: [ 789.262423] CS: 0010 DS: ES: CR0: 80050033 Nov 22 16:37:24 octo kernel: [ 789.262424] CR2: f80029b18800 CR3: 0001e146d000 CR4: 003426f0 Nov 22 16:37:24 octo kernel: [ 789.262424] DR0: DR1: DR2: Nov 22 16:37:24 octo kernel: [ 789.262425] DR3: DR6: fffe0ff0 DR7: 0400 Nov 22 16:37:24 octo kernel: [ 789.262425] Call Trace: Nov 22 16:37:24 octo kernel: [ 789.262429] ? compat_poll_select_copy_remaining+0x120/0x120 Nov 22 16:37:24 octo kernel: [ 789.262430] usbdev_do_ioctl+0xa34/0x1170 Nov 22 16:37:24 octo kernel: [ 789.262431] ? compat_poll_select_copy_remaining+0x120/0x120 Nov 22 16:37:24 octo kernel: [ 789.262433] usbdev_ioctl+0xe/0x20 Nov 22 16:37:24 octo kernel: [ 789.262434] do_vfs_ioctl+0xa5/0x610 Nov 22 16:37:24 octo kernel: [ 789.262435] SyS_ioctl+0x79/0x90 Nov 22 16:37:24 octo kernel: [ 789.262437] entry_SYSCALL_64_fastpath+0x1e/0xa9 Nov 22 16:37:24 octo kernel: [ 789.262438] RIP: 0033:0x7f88db2ffea7 Nov 22 16:37:24 octo kerne
[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386
** Changed in: linux (Ubuntu Bionic) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) ** Changed in: linux (Ubuntu Cosmic) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) ** Changed in: linux (Ubuntu Artful) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) ** Changed in: linux (Ubuntu) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) -- 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/1736390 Title: openvswitch: kernel oops destroying interfaces on i386 Status in linux package in Ubuntu: In Progress Status in openvswitch package in Ubuntu: Invalid Status in linux source package in Artful: Won't Fix Status in openvswitch source package in Artful: Invalid Status in linux source package in Bionic: In Progress Status in openvswitch source package in Bionic: Invalid Status in linux source package in Cosmic: In Progress Status in openvswitch source package in Cosmic: Invalid Bug description: Reproducable on bionic using the autopkgtest's from openvswitch on i386: [ 41.420568] BUG: unable to handle kernel NULL pointer dereference at (null) [ 41.421000] IP: igmp_group_dropped+0x21/0x220 [ 41.421246] *pdpt = 1d62c001 *pde = [ 41.421659] Oops: [#1] SMP [ 41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse virtio_blk virtio_net pata_acpi floppy [ 41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW 4.13.0-18-generic #21-Ubuntu [ 41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 41.424849] Workqueue: netns cleanup_net [ 41.425071] task: db8fba80 task.stack: dba1 [ 41.425346] EIP: igmp_group_dropped+0x21/0x220 [ 41.425656] EFLAGS: 00010202 CPU: 0 [ 41.425864] EAX: EBX: dd726360 ECX: dba11e6c EDX: 0002 [ 41.426335] ESI: EDI: dd4db500 EBP: dba11dcc ESP: dba11d94 [ 41.426687] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [ 41.426990] CR0: 80050033 CR2: CR3: 1e6d6d60 CR4: 06f0 [ 41.427340] Call Trace: [ 41.427485] ? __wake_up+0x36/0x40 [ 41.427680] ip_mc_down+0x27/0x90 [ 41.427869] inetdev_event+0x398/0x4e0 [ 41.428082] ? skb_dequeue+0x5b/0x70 [ 41.428286] ? wireless_nlevent_flush+0x4c/0x90 [ 41.428541] notifier_call_chain+0x4e/0x70 [ 41.428772] raw_notifier_call_chain+0x11/0x20 [ 41.429023] call_netdevice_notifiers_info+0x2a/0x60 [ 41.429301] dev_close_many+0x9d/0xe0 [ 41.429509] rollback_registered_many+0xd7/0x380 [ 41.429768] unregister_netdevice_many.part.102+0x10/0x80 [ 41.430075] default_device_exit_batch+0x134/0x160 [ 41.430344] ? do_wait_intr_irq+0x80/0x80 [ 41.430650] ops_exit_list.isra.8+0x4d/0x60 [ 41.430886] cleanup_net+0x18e/0x260 [ 41.431090] process_one_work+0x1a0/0x390 [ 41.431317] worker_thread+0x37/0x450 [ 41.431525] kthread+0xf3/0x110 [ 41.431714] ? process_one_work+0x390/0x390 [ 41.431941] ? kthread_create_on_node+0x20/0x20 [ 41.432187] ret_from_fork+0x19/0x24 [ 41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00 [ 41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94 [ 41.433750] CR2: [ 41.433961] ---[ end trace 595db54cab84070c ]--- system then becomes unresponsive; no further interfaces can be created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736390/+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 1761751] Re: Black screen on 18.04 + AMD RX460
** Changed in: linux (Ubuntu Bionic) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) ** Changed in: linux (Ubuntu) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) -- 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/1761751 Title: Black screen on 18.04 + AMD RX460 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I've been running 16.04 + hwe kernel 4.15 for a while now and recently I'm now having a black screen instead. I've also tried an 18.04 daily live USB stick, which has the same issue. It probably started during an upgrade this week or last week. As a start I'm blaming the Linux kernel since booting a 4.13 kernel works just fine. Known faulty kernel versions are: Â * linux-image-4.15.0-041500-generic (mainline kernel), Â * linux-image-4.16.0-041600-generic (mainline kernel), Â * linux-image-4.15.0-13-generic (Ubuntu kernel), Â * whatever comes with 18.04 daily live USB stick as of 20180404. Not sure how to best collect logs and system information for you since I'm not used to debugging black screens, so I'm just attaching lspci as a start. EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot parameters. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+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 1691899] Re: regression: the 4.8 hwe kernel does not create the /sys/block/*/device/enclosure_device:* symlinks
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- 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/1691899 Title: regression: the 4.8 hwe kernel does not create the /sys/block/*/device/enclosure_device:* symlinks Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: the 4.8 kernel does not create symlinks/sys/block/*/device/enclosure_device:*. this appears to have been resolved in 4.9+ what you expected to happen: with the ga 4.4 and hwe-edge 4.10 kernels the symlinks are created % ls -l /sys/block/*/device/enclosure* lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdaa/device/enclosure_device:013 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/013/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdab/device/enclosure_device:015 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/015/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdac/device/enclosure_device:016 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/016/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdad/device/enclosure_device:017 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/017/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdaf/device/enclosure_device:019 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/019/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdag/device/enclosure_device:020 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/020/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdah/device/enclosure_device:021 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/021/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdai/device/enclosure_device:022 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/022/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdaj/device/enclosure_device:023 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/023/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdc/device/enclosure_device:000 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/000/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdd/device/enclosure_device:001 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/001/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sde/device/enclosure_device:002 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/002/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdf/device/enclosure_device:003 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/003/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdg/device/enclosure_device:004 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/004/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdh/device/enclosure_device:005 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/005/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdi/device/enclosure_device:006 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/006/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdj/device/enclosure_device:007 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/007/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdk/device/enclosure_device:008 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/008/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdl/device/enclosure_device:010 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/010/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdm/device/enclosure_device:011 -> ../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/011/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdn/device/enclosure_device:000 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/000/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdo/device/enclosure_device:001 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/001/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdp/device/enclosure_device:002 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/002/ lrwxrwxrwx 1 root root 0 May 18 17:57 /sys/block/sdq/device/enclosure_device:003 -> ../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/003/ lrwxrwxrwx 1 roo
[Kernel-packages] [Bug 1687273] Re: Shared folder randomly not mounted
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1687273 Title: Shared folder randomly not mounted Status in Linux: Unknown Status in cifs-utils package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in cifs-utils source package in Xenial: Confirmed Status in linux source package in Xenial: Fix Released Status in linux package in Debian: Fix Released Bug description: Hello Everybody, since last update from ubuntu 16.04.2, last night, my servers are randomly not able to read and write from shared folders. I got this message: lsof: WARNING: can't stat() cifs file system /mnt/record   Output information may be incomplete. lsof: WARNING: can't stat() cifs file system /mnt/record   Output information may be incomplete. lsof: WARNING: can't stat() cifs file system /mnt/record   Output information may be incomplete. ... rsync: ERROR: cannot stat destination "/mnt/record/": Host is down (112) rsync error: errors selecting input/output files, dirs (code 3) at main.c(652) [Receiver=3.1.1] This comes from my cron script. When I type df -h it takes sometimes very long to get the list. And it also can be that the mounted share is disconnected and I have to mount -a (what also takes long) again. My fstab have this command: //address /mnt/storage cifs auto,nofail,iocharset=utf8,rw,credentials=/path/.smb,uid=1000,gid=1000,file_mode=0660,dir_mode=0770 0 0 My update list from last night was this: linux-image-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic) linux-image-extra-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic) linux-headers-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic) linux-headers-4.4.0-75:amd64 (4.4.0-75.96, automatic) Upgrade: libdns-export162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.5, 1:9.10.3.dfsg.P4-8ubuntu1.6) linux-headers-generic:amd64 (4.4.0.72.78, 4.4.0.75.81) linux-libc-dev:amd64 (4.4.0-72.93, 4.4.0-75.96) mysql-client-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) libapt-inst2.0:amd64 (1.2.19, 1.2.20) mysql-server-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) libsystemd0:amd64 (229-4ubuntu16, 229-4ubuntu17) linux-image-generic:amd64 (4.4.0.72.78, 4.4.0.75.81) apt:amd64 (1.2.19, 1.2.20) mysql-server:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) udev:amd64 (229-4ubuntu16, 229-4ubuntu17) libapt-pkg5.0:amd64 (1.2.19, 1.2.20) libudev1:amd64 (229-4ubuntu16, 229-4ubuntu17) cifs-utils:amd64 (2:6.4-1ubuntu1, 2:6.4-1ubuntu1.1) dpkg:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2) mysql-client-core-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) libisc-export160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.5, 1:9.10.3.dfsg.P4-8ubuntu1.6) linux-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81) systemd-sysv:amd64 (229-4ubuntu16, 229-4ubuntu17) distro-info-data:amd64 (0.28ubuntu0.2, 0.28ubuntu0.3) systemd:amd64 (229-4ubuntu16, 229-4ubuntu17) mysql-common:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) apt-utils:amd64 (1.2.19, 1.2.20) libmysqlclient20:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) linux-headers-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81) linux-image-extra-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81) thermald:amd64 (1.5-2ubuntu3, 1.5-2ubuntu4) qemu-guest-agent:amd64 (1:2.5+dfsg-5ubuntu10.10, 1:2.5+dfsg-5ubuntu10.11) libfreetype6:amd64 (2.6.1-0.1ubuntu2.1, 2.6.1-0.1ubuntu2.2) linux-image-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81) libdpkg-perl:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2) mysql-server-core-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1) libxslt1.1:amd64 (1.1.28-2.1, 1.1.28-2.1ubuntu0.1) dpkg-dev:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2) I saw that somebody else has the same problem: https://askubuntu.com/questions/910058/updates-broke-cifs-smb-mounts- in-16-04 I had to remove the latest kernel update, after that it works. Regards To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1687273/+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 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
I'll leave my hardware specs here, it could help pinning down the problem cause. I'm using NVidia driver 340.107. The overheating occurs under kernel 4.15, both in 16.04 and 18.04, *but* 18.04 runs about 8°C - 10°C hotter. Kernel 4.18 runs just as hot in 18.04. ** Attachment added: "lshw-ThinkPad-T410s.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768976/+attachment/5230584/+files/lshw-ThinkPad-T410s.txt -- 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/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 --- .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edir 2354 F pulseaudio CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0a5] Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5] HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 NonfreeKernelModules: wl Package: xserver-xorg-video-nouveau 1:1.0.15-2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic ubuntu Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 10HX.M034.20110426.SSH dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RF511/RF411/RF711 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 10HX dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRO
[Kernel-packages] [Bug 1507472] Re: [MacbookPro12, 1] Suspend resumes immediately due to xhci driver
Still happens on Ubuntu 18.10 (kernel 4.18.0-13) using a MacBook Pro 2015. -- 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/1507472 Title: [MacbookPro12,1] Suspend resumes immediately due to xhci driver Status in linux package in Ubuntu: Triaged Bug description: On my MacbookPro12,1 with Wily and Linux 4.2, by default the kernel successfully suspends but then immediately resumes again. The problem seems to be the XHCI controller causing spurious ACPI wakeups. Also, the Broadcom wifi module seems to have problems with suspend/resume, so I am also unloading the `brcmfmac` module prior to suspend and loading it again after resume. WORKAROUND: Disable XHC1 prior to sleeping: > # echo XHC1 > /proc/acpi/wakeup ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse:  USERPID ACCESS COMMAND  /dev/snd/controlC1: mjg1441 F pulseaudio  /dev/snd/controlC0: mjg1441 F pulseaudio CurrentDesktop: GNOME Date: Mon Oct 19 18:13:15 2015 HibernationDevice: RESUME=UUID=bc879a1f-ac27-48ae-82dd-3c81b7307dd0 InstallationDate: Installed on 2015-07-22 (89 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb:  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub  Bus 001 Device 003: ID 05ac:0273 Apple, Inc.  Bus 001 Device 002: ID 05ac:8290 Apple, Inc.  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions:  linux-restricted-modules-4.2.0-16-generic N/A  linux-backports-modules-4.2.0-16-generic N/A  linux-firmware1.149 RfKill:  3: phy0: Wireless LAN   Soft blocked: no   Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-08-27 (52 days ago) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0167.B07.1506051617 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B07.1506051617:bd06/05/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507472/+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 1803881] Re: thermal thermal_zone4: failed to read out thermal zone (-61)
These are kernel bugs, so better to file in kernel bugzilla.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1803881
Title:
thermal thermal_zone4: failed to read out thermal zone (-61)
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
Confirmed
Bug description:
Thermald can't read zone4. It's making my fan go crazy, this issue
seems to be a bit more controlled in 18.10.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
sudo apt-cache policy thermald
thermald:
Installed: 1.7.0-5ubuntu1
Candidate: 1.7.0-5ubuntu1
Version table:
*** 1.7.0-5ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
cat /sys/class/thermal/thermal_zone4/type
iwlwifi
find /sys/class/thermal/thermal_zone4/ -type f -print -exec cat {} \;
/sys/class/thermal/thermal_zone4/uevent
/sys/class/thermal/thermal_zone4/trip_point_5_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_3_type
passive
/sys/class/thermal/thermal_zone4/trip_point_4_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_2_type
passive
/sys/class/thermal/thermal_zone4/power/runtime_active_time
0
/sys/class/thermal/thermal_zone4/power/runtime_active_kids
0
/sys/class/thermal/thermal_zone4/power/runtime_usage
0
/sys/class/thermal/thermal_zone4/power/runtime_status
unsupported
/sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms
cat: /sys/class/thermal/thermal_zone4/power/autosuspend_delay_ms:
Input/output error
/sys/class/thermal/thermal_zone4/power/async
disabled
/sys/class/thermal/thermal_zone4/power/runtime_suspended_time
0
/sys/class/thermal/thermal_zone4/power/runtime_enabled
disabled
/sys/class/thermal/thermal_zone4/power/control
auto
/sys/class/thermal/thermal_zone4/available_policies
power_allocator user_space bang_bang fair_share step_wise
/sys/class/thermal/thermal_zone4/policy
step_wise
/sys/class/thermal/thermal_zone4/trip_point_3_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_1_type
passive
/sys/class/thermal/thermal_zone4/k_d
cat: /sys/class/thermal/thermal_zone4/k_d: Input/output error
/sys/class/thermal/thermal_zone4/sustainable_power
cat: /sys/class/thermal/thermal_zone4/sustainable_power: Input/output error
/sys/class/thermal/thermal_zone4/type
iwlwifi
/sys/class/thermal/thermal_zone4/trip_point_7_type
passive
/sys/class/thermal/thermal_zone4/offset
cat: /sys/class/thermal/thermal_zone4/offset: Input/output error
/sys/class/thermal/thermal_zone4/slope
cat: /sys/class/thermal/thermal_zone4/slope: Input/output error
/sys/class/thermal/thermal_zone4/trip_point_2_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_0_type
passive
/sys/class/thermal/thermal_zone4/trip_point_6_type
passive
/sys/class/thermal/thermal_zone4/emul_temp
cat: /sys/class/thermal/thermal_zone4/emul_temp: Permission denied
/sys/class/thermal/thermal_zone4/k_po
cat: /sys/class/thermal/thermal_zone4/k_po: Input/output error
/sys/class/thermal/thermal_zone4/integral_cutoff
cat: /sys/class/thermal/thermal_zone4/integral_cutoff: Input/output error
/sys/class/thermal/thermal_zone4/k_i
cat: /sys/class/thermal/thermal_zone4/k_i: Input/output error
/sys/class/thermal/thermal_zone4/trip_point_1_temp
-32768000
/sys/class/thermal/thermal_zone4/k_pu
cat: /sys/class/thermal/thermal_zone4/k_pu: Input/output error
/sys/class/thermal/thermal_zone4/temp
46000
/sys/class/thermal/thermal_zone4/trip_point_7_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_5_type
passive
/sys/class/thermal/thermal_zone4/trip_point_0_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_6_temp
-32768000
/sys/class/thermal/thermal_zone4/trip_point_4_type
passive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803881/+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 424215] Re: Bluetooth mouse usage makes A2DP audio stutter
Bug still exists in 18.10. How can you mark it fixed??? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/424215 Title: Bluetooth mouse usage makes A2DP audio stutter Status in bluez package in Ubuntu: Fix Released Bug description: Binary package hint: bluez When I use my Bluetooth A2DP headset (Philips SHB7102) together with my mouse (Lenovo Bluetooth Laser Mouse), I notice this: Whenever I leave the mouse still for a few seconds (it seems to enter some kind of lower-power-mode) and then start to move it, my music most of the time skips for a second. This makes using these two bluetooth devices together quite annoying... The adapter is a Lenovo "ThinkPad Bluetooth with Enhanced Data Rate II" (Bus 004 Device 005: ID 0a5c:2145 Broadcom Corp.) I am running current karmic amd64 (linux 2.6.31-9). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/424215/+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 1812502] [NEW] When I use my Bluetooth A2DP headset (Philips SHB7102) together with my mouse (Lenovo Bluetooth Laser Mouse), I notice this: Whenever I leave the mouse still for
Public bug reported: When I use my Bluetooth A2DP headset together with my mouse, I notice this: Whenever I leave the mouse still for a few seconds (it seems to enter some kind of lower-power-mode) and then start to move it, my music most of the time skips for a second. This makes using these two bluetooth devices together quite annoying... It exists with every bluetooth adapter and any mouse. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 18:59:22 2019 InstallationDate: Installed on 2019-01-19 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA Satellite Radius P55W-B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=c23973fb-1c63-4119-86be-0b17173e5a2a ro quiet splash acpi_osi=Linux "acpi_osi=!Windows 2012" acpi=force acpi_enforce_resources=lax i915.enable_rc6=1 i915.enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 drm.vblankoffdelay=1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.60 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr1.60:bd12/23/2014:svnTOSHIBA:pnSatelliteRadiusP55W-B:pvrPSVP2U-003004:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: Satellite Radius P55W-B dmi.product.sku: INVALID dmi.product.version: PSVP2U-003004 dmi.sys.vendor: TOSHIBA hciconfig: hci0: Type: Primary Bus: USB BD Address: E8:2A:EA:6E:E5:28 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:309822 acl:9284 sco:0 events:14449 errors:0 TX bytes:9130591 acl:13720 sco:0 commands:309 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812502 Title: When I use my Bluetooth A2DP headset (Philips SHB7102) together with my mouse (Lenovo Bluetooth Laser Mouse), I notice this: Whenever I leave the mouse still for a few seconds (it seems to enter some kind of lower-power-mode) and then start to move it, my music most of the time skips for a second. This makes using these two bluetooth devices together quite annoying... The adapter is a Lenovo "ThinkPad Bluetooth with Enhanced Data Rate II" (Bus 004 Device 005: ID 0a5c:2145 Broadcom Corp.) Status in bluez package in Ubuntu: New Bug description: When I use my Bluetooth A2DP headset together with my mouse, I notice this: Whenever I leave the mouse still for a few seconds (it seems to enter some kind of lower-power-mode) and then start to move it, my music most of the time skips for a second. This makes using these two bluetooth devices together quite annoying... It exists with every bluetooth adapter and any mouse. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: bluez 5.50-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 18:59:22 2019 InstallationDate: Installed on 2019-01-19 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA Satellite Radius P55W-B ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=c23973fb-1c63-4119-86be-0b17173e5a2a ro quiet splash acpi_osi=Linux "acpi_osi=!Windows 2012" acpi=force acpi_enforce_resources=lax i915.enable_rc6=1 i915.enable_fbc=1 i915.lvds_downclock=1 i915.semaphores=1 drm.vblankoffdelay=1 acpi_backlight=vendor vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2014 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.60 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
linux-headers of #94 ** Attachment added: "linux-headers-4.20.0-rc3+_4.20.0-rc3+-6_amd64.deb" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5230554/+files/linux-headers-4.20.0-rc3+_4.20.0-rc3+-6_amd64.deb -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
AaronMa Got kernel headers for that kernel, please? (I can boot from the kernel but Wireguard isn't working because of the lack of headers. Since the problem can take some time to manifest itself, I would not mind Internet during the testing phase. I write this from a different computer.) -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20K
[Kernel-packages] [Bug 1809586] Re: [ 14.259626] i2c_hid i2c-HTIX5288:00: i2c-HTIX5288:00 supply vddl not found, using dummy regulator
I am now running kernel 4.20.2 and I am still getting the same error. The trackpad freezes for 1 second after I lift my finger up from the trackpad and try to move it again. I need to be able to disable power saving on the trackpad so it won't lag anymore. When a USB mouse is plugged in it works just fine. -- 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/1809586 Title: [ 14.259626] i2c_hid i2c-HTIX5288:00: i2c-HTIX5288:00 supply vddl not found, using dummy regulator Status in linux package in Ubuntu: Incomplete Bug description: Missing i2c-HTIX5288 driver. Touch does work OK but sometimes it freezes at random times. When using a mouse the mouse works fine. Ubuntu 18.04 Kernel 4.18.0-13 Dual-Core Intel® Celeron® N4000 CPU @ 1.10GHz ~$ dmesg [ 14.259578] i2c_hid i2c-HTIX5288:00: i2c-HTIX5288:00 supply vdd not found, using dummy regulator [ 14.259622] i2c_hid i2c-HTIX5288:00: Linked as a consumer to regulator.0 [ 14.259626] i2c_hid i2c-HTIX5288:00: i2c-HTIX5288:00 supply vddl not found, using dummy regulator [ 14.296078] ahci :00:12.0: port does not support device sleep [ 14.421143] input: HTIX5288:00 0911:5288 Mouse as /devices/pci:00/:00:17.3/i2c_designware.7/i2c-12/i2c-HTIX5288:00/0018:0911:5288.0002/input/input17 [ 14.421507] input: HTIX5288:00 0911:5288 Touchpad as /devices/pci:00/:00:17.3/i2c_designware.7/i2c-12/i2c-HTIX5288:00/0018:0911:5288.0002/input/input18 [ 14.421715] hid-generic 0018:0911:5288.0002: input,hidraw1: I2C HID v1.00 Mouse [HTIX5288:00 0911:5288] on i2c-HTIX5288:00 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: juno 1113 F pulseaudio /dev/snd/controlC0: juno 1113 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-12-23 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Default string Default string Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=161d8da2-6b65-4a94-b327-82974d663e77 ro quiet splash acpi_osi=Linux i8042.nopnp vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL5-BIOS-4G-V3-002-A dmi.board.asset.tag: Default string dmi.board.name: Gemini II dmi.board.vendor: PC Specialist LTD dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL5-BIOS-4G-V3-002-A:bd11/28/2018:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnPCSpecialistLTD:rnGeminiII:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809586/+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 1810636] Re: Suspect QCA6174 btcoex | Ubuntu 18 Bluetooth Audio Skip/Stutter/Delay WiFi bandwidth conflict Dell XPS 9570 [Pending PulseAudio testing]
I'm happy this is pretty much solve. With the pulseaudio-modules-bt from comment 27 [2], I've experienced far less audio lag overall. Every now and again I get a small glitch that delays it 10ms or so, but it's so much better now I'm happy to close this and mark it as non-issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810636 Title: Suspect QCA6174 btcoex | Ubuntu 18 Bluetooth Audio Skip/Stutter/Delay WiFi bandwidth conflict Dell XPS 9570 [Pending PulseAudio testing] Status in linux package in Ubuntu: Confirmed Bug description: I'm running Linux 4.20.0-042000-generic #201812232030 x64 on a Dell XPS 9570 with QCA6174 chipset, and have had the problem with Bluetooth audio choppiness ever since I have owned this laptop. This problem has persisted for me with previous kernels. If I disable wifi and use media on machine locally, the problem doesn't occur. Note: I've reverted back v4.18.0-13-generic and reproduced the problem for the apport-collect report. It started with Ubuntu 18.04 and continues with 18.10. It's particularly noticeable when the when saturating the WLAN connection with throughput, i.e. copying a large file sequentially across from a samba share, but also streaming video online results in the audio progressively delaying over-time. Re-establishing the Bluetooth audio sync restores the sync, but slowly creeps out again. I've upgraded my linux-firmware package to disco 176 to match v4.20 kernel drivers ref: https://launchpad.net/ubuntu/+source/linux- firmware/1.176 The ath10k_core driver that supports this device has a reference for btcoex: ref https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath10k/core.c?h=v4.20#n2598 It's possible that the Bluetooth component firmware is not supporting or communicating btcoex compatibility, but this is starting to reach the edge of my ability to diagnose the problem. This btcoex support in ath9k has resolved/improved the Bluetooth bandwidth problem for older Qualcomm chipsets as shown in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746164 As a troubleshooting step, I've also tried the very latest firmware-6 file from, but I'm continuing to experience the problem ref: https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse:  USERPID ACCESS COMMAND  /dev/snd/controlC0: berg 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-07-02 (187 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcEnviron:  TERM=xterm-256color  PATH=(custom, no user)  XDG_RUNTIME_DIR=  LANG=en_AU.UTF-8  SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=c825a7b0-a5ac-41de-bd57-7663fef8a1f1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 RelatedPackageVersions:  linux-restricted-modules-4.18.0-13-generic N/A  linux-backports-modules-4.18.0-13-generic N/A  linux-firmware 1.176 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-18 (79 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 07GHH0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd11/02/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810636/+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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Finally, glad to hear it helps you. I will clear my patch and upstream them after more users confirm. nosleep mode means it should always work at runtime, it should not make more power consumption. When suspend it will go to sleep too. -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.versi
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Hi, I have performed 11 suspend/resumes and no issue! Big thanks for looking into it and fixing it! nosleep mode sounds like a mitigation so that the bug cannot occur but is not actually fixing it? Is the issue then in the firmware/bios and we have to contact lenovo or is it still there in the kernel? Moreover, nosleep mode of rmi sounds like this would come along with an increased power consumption during suspend? Is this neglectable? Could you maybe publish your patch already here, so that we can build patched kernels ourself until your patch lands? Your supplied kernel is based on 4.20.rc3 and is therefore not suited for every day use, or? -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4
[Kernel-packages] [Bug 1811846] Re: linux: 4.4.0-142.168 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Promote to Proposed -- snap release to edge ready - phase-changed: Saturday, 19. January 2019 09:03 UTC + phase: Promote to Proposed -- snap release to beta ready + phase-changed: Saturday, 19. January 2019 09:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811846 Title: linux: 4.4.0-142.168 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promote to Proposed -- snap release to beta ready phase-changed: Saturday, 19. January 2019 09:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811846/+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 1811417] Re: linux-kvm: 4.18.0-1007.7 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 - phase: Testing -- regression-testing in progress - phase-changed: Saturday, 19. January 2019 09:09 UTC + phase: Testing -- verification-testing in progress + phase-changed: Saturday, 19. January 2019 09:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1811417 Title: linux-kvm: 4.18.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Testing -- verification-testing in progress phase-changed: Saturday, 19. January 2019 09:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811417/+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 1811421] Re: linux-oem: 4.15.0-1032.37 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Testing -- regression-testing in progress - phase-changed: Saturday, 19. January 2019 09:12 UTC + phase: Testing -- certification-testing in progress + phase-changed: Saturday, 19. January 2019 09:40 UTC reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1811421 Title: linux-oem: 4.15.0-1032.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Testing -- certification-testing in progress phase-changed: Saturday, 19. January 2019 09:40 UTC reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811421/+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 1811431] Re: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Promote to Proposed -- snap release to edge ready - phase-changed: Saturday, 19. January 2019 09:10 UTC + phase: Promote to Proposed -- snap release to beta ready + phase-changed: Saturday, 19. January 2019 09:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1811431 Title: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Promote to Proposed -- snap release to beta ready phase-changed: Saturday, 19. January 2019 09:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811431/+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 1811851] Re: linux-aws: 4.4.0-1075.85 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 - phase: Promote to Proposed -- snap release to edge ready - phase-changed: Saturday, 19. January 2019 09:01 UTC + phase: Promote to Proposed -- snap release to beta ready + phase-changed: Saturday, 19. January 2019 09:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1811851 Title: linux-aws: 4.4.0-1075.85 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Promote to Proposed -- snap release to beta ready phase-changed: Saturday, 19. January 2019 09:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811851/+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 1811423] Re: linux-azure: 4.15.0-1037.39 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Promote to Proposed -- snap release to edge ready - phase-changed: Saturday, 19. January 2019 09:06 UTC + phase: Promote to Proposed -- snap release to beta ready + phase-changed: Saturday, 19. January 2019 09:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1811423 Title: linux-azure: 4.15.0-1037.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Promote to Proposed -- snap release to beta ready phase-changed: Saturday, 19. January 2019 09:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811423/+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 1811424] Re: linux-gcp: 4.15.0-1027.28 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Promote to Proposed -- snap release to edge ready - phase-changed: Saturday, 19. January 2019 09:11 UTC + phase: Promote to Proposed -- snap release to beta ready + phase-changed: Saturday, 19. January 2019 09:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1027 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1811424 Title: linux-gcp: 4.15.0-1027.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Promote to Proposed -- snap release to beta ready phase-changed: Saturday, 19. January 2019 09:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1027 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811424/+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 1811847] Re: linux-aws: 4.4.0-1038.41 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 - phase: Testing -- regression-testing in progress - phase-changed: Saturday, 19. January 2019 09:04 UTC + phase: Testing -- verification-testing in progress + phase-changed: Saturday, 19. January 2019 09:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1811847 Title: linux-aws: 4.4.0-1038.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Testing -- verification-testing in progress phase-changed: Saturday, 19. January 2019 09:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811847/+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 1811422] Re: linux-aws: 4.15.0-1032.34 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Promote to Proposed -- snap release to edge ready - phase-changed: Saturday, 19. January 2019 09:16 UTC + phase: Promote to Proposed -- snap release to beta ready + phase-changed: Saturday, 19. January 2019 09:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1811422 Title: linux-aws: 4.15.0-1032.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Promote to Proposed -- snap release to beta ready phase-changed: Saturday, 19. January 2019 09:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811422/+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 1811422] Re: linux-aws: 4.15.0-1032.34 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Promote to Proposed -- snap release to beta ready - phase-changed: Saturday, 19. January 2019 08:39 UTC + phase: Promote to Proposed -- snap release to edge ready + phase-changed: Saturday, 19. January 2019 09:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1811422 Title: linux-aws: 4.15.0-1032.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Promote to Proposed -- snap release to edge ready phase-changed: Saturday, 19. January 2019 09:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811422/+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 1811424] Re: linux-gcp: 4.15.0-1027.28 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Promote to Proposed -- snap release to beta ready - phase-changed: Saturday, 19. January 2019 08:32 UTC + phase: Promote to Proposed -- snap release to edge ready + phase-changed: Saturday, 19. January 2019 09:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1027 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1811424 Title: linux-gcp: 4.15.0-1027.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Promote to Proposed -- snap release to edge ready phase-changed: Saturday, 19. January 2019 09:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1027 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811424/+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 1811421] Re: linux-oem: 4.15.0-1032.37 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Testing -- verification-testing in progress - phase-changed: Saturday, 19. January 2019 08:45 UTC + phase: Testing -- regression-testing in progress + phase-changed: Saturday, 19. January 2019 09:12 UTC reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1811421 Title: linux-oem: 4.15.0-1032.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Testing -- regression-testing in progress phase-changed: Saturday, 19. January 2019 09:12 UTC reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811421/+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 1811431] Re: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Promote to Proposed -- snap release to beta ready - phase-changed: Saturday, 19. January 2019 08:36 UTC + phase: Promote to Proposed -- snap release to edge ready + phase-changed: Saturday, 19. January 2019 09:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1811431 Title: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Promote to Proposed -- snap release to edge ready phase-changed: Saturday, 19. January 2019 09:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811431/+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 1811423] Re: linux-azure: 4.15.0-1037.39 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Promote to Proposed -- snap release to beta ready - phase-changed: Saturday, 19. January 2019 08:38 UTC + phase: Promote to Proposed -- snap release to edge ready + phase-changed: Saturday, 19. January 2019 09:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1811423 Title: linux-azure: 4.15.0-1037.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Promote to Proposed -- snap release to edge ready phase-changed: Saturday, 19. January 2019 09:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811423/+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 1811417] Re: linux-kvm: 4.18.0-1007.7 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 - phase: Testing -- verification-testing in progress - phase-changed: Saturday, 19. January 2019 08:43 UTC + phase: Testing -- regression-testing in progress + phase-changed: Saturday, 19. January 2019 09:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1811417 Title: linux-kvm: 4.18.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Testing -- regression-testing in progress phase-changed: Saturday, 19. January 2019 09:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811417/+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 1811846] Re: linux: 4.4.0-142.168 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Promote to Proposed -- snap release to beta ready - phase-changed: Saturday, 19. January 2019 08:37 UTC + phase: Promote to Proposed -- snap release to edge ready + phase-changed: Saturday, 19. January 2019 09:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811846 Title: linux: 4.4.0-142.168 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promote to Proposed -- snap release to edge ready phase-changed: Saturday, 19. January 2019 09:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811846/+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 1811851] Re: linux-aws: 4.4.0-1075.85 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 - phase: Promote to Proposed -- snap release to beta ready - phase-changed: Saturday, 19. January 2019 08:35 UTC + phase: Promote to Proposed -- snap release to edge ready + phase-changed: Saturday, 19. January 2019 09:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1811851 Title: linux-aws: 4.4.0-1075.85 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Promote to Proposed -- snap release to edge ready phase-changed: Saturday, 19. January 2019 09:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811851/+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 1811847] Re: linux-aws: 4.4.0-1038.41 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 - phase: Testing -- verification-testing in progress - phase-changed: Saturday, 19. January 2019 08:35 UTC + phase: Testing -- regression-testing in progress + phase-changed: Saturday, 19. January 2019 09:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1811847 Title: linux-aws: 4.4.0-1038.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Testing -- regression-testing in progress phase-changed: Saturday, 19. January 2019 09:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811847/+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 1811421] Re: linux-oem: 4.15.0-1032.37 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Testing -- certification-testing in progress - phase-changed: Saturday, 19. January 2019 08:08 UTC + phase: Testing -- verification-testing in progress + phase-changed: Saturday, 19. January 2019 08:45 UTC reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1811421 Title: linux-oem: 4.15.0-1032.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Testing -- verification-testing in progress phase-changed: Saturday, 19. January 2019 08:45 UTC reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811421/+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 1811417] Re: linux-kvm: 4.18.0-1007.7 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 - phase: Testing -- regression-testing in progress - phase-changed: Saturday, 19. January 2019 08:09 UTC + phase: Testing -- verification-testing in progress + phase-changed: Saturday, 19. January 2019 08:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1811417 Title: linux-kvm: 4.18.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Testing -- verification-testing in progress phase-changed: Saturday, 19. January 2019 08:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811417/+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 1811846] Re: linux: 4.4.0-142.168 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Promote to Proposed -- snap release to edge ready - phase-changed: Saturday, 19. January 2019 08:14 UTC + phase: Promote to Proposed -- snap release to beta ready + phase-changed: Saturday, 19. January 2019 08:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811846 Title: linux: 4.4.0-142.168 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promote to Proposed -- snap release to beta ready phase-changed: Saturday, 19. January 2019 08:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811846/+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 1811847] Re: linux-aws: 4.4.0-1038.41 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 - phase: Testing -- regression-testing in progress - phase-changed: Saturday, 19. January 2019 08:05 UTC + phase: Testing -- verification-testing in progress + phase-changed: Saturday, 19. January 2019 08:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1811847 Title: linux-aws: 4.4.0-1038.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Testing -- verification-testing in progress phase-changed: Saturday, 19. January 2019 08:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811847/+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 1811423] Re: linux-azure: 4.15.0-1037.39 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Promote to Proposed -- snap release to edge ready - phase-changed: Saturday, 19. January 2019 08:12 UTC + phase: Promote to Proposed -- snap release to beta ready + phase-changed: Saturday, 19. January 2019 08:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1811423 Title: linux-azure: 4.15.0-1037.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Promote to Proposed -- snap release to beta ready phase-changed: Saturday, 19. January 2019 08:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811423/+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 1811431] Re: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Promote to Proposed -- snap release to edge ready - phase-changed: Saturday, 19. January 2019 08:03 UTC + phase: Promote to Proposed -- snap release to beta ready + phase-changed: Saturday, 19. January 2019 08:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1811431 Title: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Promote to Proposed -- snap release to beta ready phase-changed: Saturday, 19. January 2019 08:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811431/+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 1811422] Re: linux-aws: 4.15.0-1032.34 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Promote to Proposed -- snap release to edge ready - phase-changed: Saturday, 19. January 2019 08:03 UTC + phase: Promote to Proposed -- snap release to beta ready + phase-changed: Saturday, 19. January 2019 08:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1811422 Title: linux-aws: 4.15.0-1032.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Promote to Proposed -- snap release to beta ready phase-changed: Saturday, 19. January 2019 08:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811422/+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 1811424] Re: linux-gcp: 4.15.0-1027.28 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Promote to Proposed -- snap release to edge ready - phase-changed: Saturday, 19. January 2019 08:10 UTC + phase: Promote to Proposed -- snap release to beta ready + phase-changed: Saturday, 19. January 2019 08:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1027 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1811424 Title: linux-gcp: 4.15.0-1027.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Promote to Proposed -- snap release to beta ready phase-changed: Saturday, 19. January 2019 08:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1027 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811424/+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 1811851] Re: linux-aws: 4.4.0-1075.85 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 - phase: Promote to Proposed -- snap release to edge ready - phase-changed: Saturday, 19. January 2019 08:10 UTC + phase: Promote to Proposed -- snap release to beta ready + phase-changed: Saturday, 19. January 2019 08:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1811851 Title: linux-aws: 4.4.0-1075.85 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Promote to Proposed -- snap release to beta ready phase-changed: Saturday, 19. January 2019 08:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811851/+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 1811424] Re: linux-gcp: 4.15.0-1027.28 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Promote to Proposed -- snap release to beta ready - phase-changed: Saturday, 19. January 2019 07:09 UTC + phase: Promote to Proposed -- snap release to edge ready + phase-changed: Saturday, 19. January 2019 08:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1027 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1811424 Title: linux-gcp: 4.15.0-1027.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Promote to Proposed -- snap release to edge ready phase-changed: Saturday, 19. January 2019 08:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1027 regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811424/+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 1811423] Re: linux-azure: 4.15.0-1037.39 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Promote to Proposed -- snap release to beta ready - phase-changed: Saturday, 19. January 2019 07:16 UTC + phase: Promote to Proposed -- snap release to edge ready + phase-changed: Saturday, 19. January 2019 08:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1811423 Title: linux-azure: 4.15.0-1037.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Promote to Proposed -- snap release to edge ready phase-changed: Saturday, 19. January 2019 08:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811423/+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 1811846] Re: linux: 4.4.0-142.168 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Promote to Proposed -- snap release to beta ready - phase-changed: Saturday, 19. January 2019 07:05 UTC + phase: Promote to Proposed -- snap release to edge ready + phase-changed: Saturday, 19. January 2019 08:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811846 Title: linux: 4.4.0-142.168 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa-dnu series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1811847 (linux-aws), bug 1811848 (linux-lts-xenial) derivatives: bug 1811851 (linux-aws), bug 1811852 (linux-euclid), bug 1811853 (linux-kvm), bug 1811854 (linux-raspi2), bug 1811855 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promote to Proposed -- snap release to edge ready phase-changed: Saturday, 19. January 2019 08:14 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811846/+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 1811417] Re: linux-kvm: 4.18.0-1007.7 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 - phase: Testing -- verification-testing in progress - phase-changed: Saturday, 19. January 2019 07:40 UTC + phase: Testing -- regression-testing in progress + phase-changed: Saturday, 19. January 2019 08:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1811417 Title: linux-kvm: 4.18.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Cosmic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811406 phase: Testing -- regression-testing in progress phase-changed: Saturday, 19. January 2019 08:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811417/+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 1811431] Re: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Promote to Proposed -- snap release to beta ready - phase-changed: Saturday, 19. January 2019 07:15 UTC + phase: Promote to Proposed -- snap release to edge ready + phase-changed: Saturday, 19. January 2019 08:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1811431 Title: linux-azure: 4.15.0-1037.39~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Promote to Proposed -- snap release to edge ready phase-changed: Saturday, 19. January 2019 08:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811431/+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 1811421] Re: linux-oem: 4.15.0-1032.37 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Testing -- verification-testing in progress - phase-changed: Saturday, 19. January 2019 07:42 UTC + phase: Testing -- certification-testing in progress + phase-changed: Saturday, 19. January 2019 08:08 UTC reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1811421 Title: linux-oem: 4.15.0-1032.37 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Testing -- certification-testing in progress phase-changed: Saturday, 19. January 2019 08:08 UTC reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811421/+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 1811422] Re: linux-aws: 4.15.0-1032.34 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 - phase: Promote to Proposed -- snap release to beta ready - phase-changed: Saturday, 19. January 2019 07:17 UTC + phase: Promote to Proposed -- snap release to edge ready + phase-changed: Saturday, 19. January 2019 08:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1811422 Title: linux-aws: 4.15.0-1032.34 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811419 phase: Promote to Proposed -- snap release to edge ready phase-changed: Saturday, 19. January 2019 08:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in 18/beta channel snap-release-to-edge: Pending -- snap not in 18/edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811422/+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 1811851] Re: linux-aws: 4.4.0-1075.85 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 - phase: Promote to Proposed -- snap release to beta ready - phase-changed: Saturday, 19. January 2019 07:08 UTC + phase: Promote to Proposed -- snap release to edge ready + phase-changed: Saturday, 19. January 2019 08:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1811851 Title: linux-aws: 4.4.0-1075.85 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Promote to Proposed -- snap release to edge ready phase-changed: Saturday, 19. January 2019 08:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: Pending -- snap not in beta channel snap-release-to-edge: Pending -- snap not in edge channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811851/+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 1811847] Re: linux-aws: 4.4.0-1038.41 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 - phase: Testing -- verification-testing in progress - phase-changed: Saturday, 19. January 2019 07:30 UTC + phase: Testing -- regression-testing in progress + phase-changed: Saturday, 19. January 2019 08:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1811847 Title: linux-aws: 4.4.0-1038.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa-dnu series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1811846 phase: Testing -- regression-testing in progress phase-changed: Saturday, 19. January 2019 08:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1811847/+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
