[Kernel-packages] [Bug 1819915] Re: s2disk freezes at saving image to disk (hibernation)

2019-03-22 Thread Matheus
Alright, today  finally had some time and installed older kernels.
4.15.0-42 , 4.15.0-44, 4.15.0-45 and on the last I had the same bug as
always. I installed the older linux images, with apt, and runed
initramfs:



# update-initramfs -k all -u
update-initramfs: Generating /boot/initrd.img-4.15.0-46-generic
I: The initramfs will attempt to resume from /dev/sda8
I: (UUID=70d967e6-ad52-4c21-baf0-01a813ccc6ac)
I: Set the RESUME variable to override this.
update-initramfs: Generating /boot/initrd.img-4.15.0-45-generic
I: The initramfs will attempt to resume from /dev/sda8
I: (UUID=70d967e6-ad52-4c21-baf0-01a813ccc6ac)
I: Set the RESUME variable to override this.
update-initramfs: Generating /boot/initrd.img-4.15.0-44-generic
I: The initramfs will attempt to resume from /dev/sda8
I: (UUID=70d967e6-ad52-4c21-baf0-01a813ccc6ac)
I: Set the RESUME variable to override this.
update-initramfs: Generating /boot/initrd.img-4.15.0-42-generic
I: The initramfs will attempt to resume from /dev/sda8
I: (UUID=70d967e6-ad52-4c21-baf0-01a813ccc6ac)
I: Set the RESUME variable to override this.



70d967e6-ad52-4c21-baf0-01a813ccc6ac is my real swap!


problem is, with the other two kernels I'm not able to boot up. I get
stuck on this screen: http://imgur.com/gallery/kLPMFhg

I'm sure that on those kernels I didn't have the issue!

Waited, hit ctrl+c, the tty worked (switchign with ctrl+alt+F2). But
there was no connection, ifconfig didn't show either my eth0 or
wlan0 well that was very buggy... and i was thinking on reinstalling
the nvidia kernels from there since it could be just a graphical glitch.
No clue how to test older kernels on ubuntu.

Also noticed that this 2gb thing I said is not totally right. Seems like
it's more likely it will happen if 2gb was used, but I still had the
problem randomly just after a boot and not even logged into a DE, just
from tty...

-- 
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/1819915

Title:
  s2disk freezes at saving image to disk (hibernation)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This started happening after I upgrade to ubuntu 18.04.2. In 18.04.1
  hibernation was working flawlessly on my machine. (with kernel
  4.15-46! not a kernel issue then?)

  Another thing that got updated recently was nvidia drivers which were
  known to cause hibernation issues, but those were on restoring the
  snapshot.

  http://imgur.com/gallery/jOyHEcL  --> I get stuck on this screen after
  running hibernate or pm-hibernate. (sys-req REISUB combination works
  there and is the only good way to restart I found)

  
  SPECS

  Laptop Dell Inspiron 7567 A30P
  Intel Core i7-7700HQ
  1x 16 GB DDR4 
  1 TB HDD + 256 GB SSD 
  Nvidia GeForce GTX 1050 
  Ti FHD display 
  Intel Dual Band Wireless AC 3165 
  1x1 Motherboard: 
  Intel HM175 Graphics adapter: 
  NVIDIA GeForce GTX 1050 Ti (Laptop) - 4096 MB, 
  Core: 1620 MHz, 
  Memory: 1752 MHz, 
  GDDR5, 21.21.13.7320 (ForceWare 373.20), 
  Nvidia Optimus

  nvidia driver: 415.27

  INFO

  # uname -a
  Linux matheus-Inspiron-15-7000-Gaming 4.15.0-46-generic #49-Ubuntu SMP Wed 
Feb 6 09:33:07 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

  # free -m
totalusedfree  shared  buff/cache   
available
  Mem:  1590629258742 1614238   
12485
  Swap: 16333   0   16333

  # cat /etc/fstab | grep swap
  # swap was on /dev/sda8 during installation
  UUID=70d967e6-ad52-4c21-baf0-01a813ccc6ac noneswapsw  
0   0
  n

  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep hibernate 
  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep hiber 
  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep s2disk
  root@matheus-Inspiron-15-7000-Gaming:/home/matheus# cat /var/log/syslog | 
grep hibernation

  
  I could find nothing scrolling up on syslog about the hibernation process or 
with grep 

  
  An interesting Note is that if I run hibernate just after I boot, it works 
and resumes perfectly! But after some system usage it randomly has that problem 
if I try. The percentage it freezes at is also random, sometimes 0, 1 even 30 
once.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   matheus   25949 F...m pulseaudio
   /dev/snd/pcmC0D0p:   matheus   25949 F...m pulseaudio
   /dev/snd/controlC0:  matheus   25949 F pulseaudio
   /dev/snd/seq:matheus4986 f qsynth
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: 

[Kernel-packages] [Bug 1690085]

2019-03-22 Thread zao
(In reply to Borislav Petkov from comment #571)
> (In reply to Lars Viklund from comment #570)
> > rdmsr yields 68010, which has bit 4 set.
> 
> Looks like your BIOS applies the fix. Now, does the patch in comment #526
> fix your freezes?

I'm sorry, I don't currently suffer from any significant hangs on my
machines when running stock Ubuntu 18.04.02 LTS (4.15.0-43-generic).

I mostly meant #570 to demonstrate that some firmware does indeed
implement the errata.

While I've had core hangs and hard freezes in the past, the machine has
enough workarounds applied to make it sufficiently stable. Current
uptime is something like 81 days since the last incident and I can
honestly not remember what it did then, but it's been used heavily as a
build machine.

>From my memory: sufficiently RMA:d CPUs, slight overclocking, change the
current idle setting in firmware, boot idle=nomwait.

Back when I had significant problems, the best way to mitigate them was
to disable SMT.

It's possible that my increased stability has come from firmware
implementing this errata, or it might be coincidental, I don't have
enough data to tell.

(You people should be happy you're not running FreeBSD, there I can
reasonably reliably hang Ryzens within hours by sending ZFS snapshots :D
)

-- 
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 

[Kernel-packages] [Bug 1690085]

2019-03-22 Thread devurandom
(In reply to Borislav Petkov from comment #574)
> (In reply to Dennis Schridde from comment #573)
> > 2068100
> 
> If this is correct:
> 
> http://www.cpu-world.com/CPUs/Zen/AMD-Ryzen%205%202400G.html
> 
> then you should have in /proc/cpuninfo something like this:
> 
> cpu family: 23
> model:  17
> stepping:   0
> 
> and if so, not affected.

A year ago I was affected by something (comment #295), but the issue
appears to have vanished within the last months (comment #547 and
comment #573).

-- 
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
   

[Kernel-packages] [Bug 1690085]

2019-03-22 Thread bp
(In reply to Dennis Schridde from comment #573)
> 2068100

If this is correct:

http://www.cpu-world.com/CPUs/Zen/AMD-Ryzen%205%202400G.html

then you should have in /proc/cpuninfo something like this:

cpu family: 23
model:  17
stepping:   0

and if so, not affected.

-- 
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 

[Kernel-packages] [Bug 1690085]

2019-03-22 Thread devurandom
(In reply to Borislav Petkov from comment #569)
> (In reply to Tolga Cakir from comment #568)
> > @Borislav has the fix for erratum 1033 "A Lock Operation May Cause the
> > System to Hang" been applied so far? The suggested workaround was "Program
> > MSRC001_1020[4] to 1b", but I couldn't find anything about it in master
> > branch. According to the document, 1033 only affects B1.
> 
> Such a "fix" does not exist. Possibly because it is unlikely this is causing
> it and BIOS might be applying the fix already. People with B1s (model 1,
> stepping 1) could test though by doing as root:
> 
> # modprobe msr
> # rdmsr -a 0xc0011020
> 
> and looking at bit 4 in the result.

2068100

CPU: AMD Ryzen 5 2400G
Motherboard: Asus ROG STRIX B350-F Gaming
Firmware version: 4207
Linux: 4.18.16-300.fc29 (Fedora 29 live system)

-- 
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...

  
  

[Kernel-packages] [Bug 1690085]

2019-03-22 Thread hexawolfie
I'm actually desperate about this issue. I'm looking forward to see
results of Boris' patch, though I really doubt it will solve this issue.
Needs explicit check against self-built kernel really.

Not all manufacturers are willing to fix this issue (especially when it
comes to laptops), as Windows seems to fix this inside it's kernel since
1709 I believe. I've made a post on HP forum about this, specifically
for my laptop:

https://h30434.www3.hp.com/t5/Notebook-Boot-and-Lockup/Random-Soft-Lock-
up-on-Ryzen/m-p/7062823

-- 
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:
   

[Kernel-packages] [Bug 1690085]

2019-03-22 Thread cevelnet
(In reply to Lars Viklund from comment #572)
> (You people should be happy you're not running FreeBSD, there I can
> reasonably reliably hang Ryzens within hours by sending ZFS snapshots :D )

Looks like they've addressed Ryzen errata issues around August 2018:

https://github.com/freebsd/freebsd/blob/75ee4f08d3acd4bf70f24b3203fa440255873973/sys/amd64/amd64/initcpu.c#L133

Also, they've made machdep.idle=hlt and machdep.idle_mwait=0 default for
Ryzen processors.

I've additionally checked the registers mentioned in FresBSD's source.
Latest BIOS 4406 (w/ AGESA 0070) for my ASUS A320M-K seems to apply
fixes for all affected errata.

Eventhough I can't reliably reproduce the stability issues anymore, I
think it's still good practice to have Boris' patch applied, since it's
addresses a known erratum. I'll test the patch and check for
regressions.

-- 
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 

[Kernel-packages] [Bug 1794055] Re: [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with nouveau errors; OS booted successfully

2019-03-22 Thread bugproxy
** Tags added: verification-needed-cosmic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1794055

Title:
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown
  with nouveau errors; OS booted successfully

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Won't Fix
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Missing firmware for nouveau is causing errors to appear in
  dmesg.

  Fix: Add missing firmware files from upstream linux-firmware.

  Test Case: Confirm that errors in dmesg are gone once new firmware
  files are present.

  Regression Potential: New and updated firmware always has potential to
  cause regressions, however this firmware has been in disco for several
  months with no reported issues.

  ---

  == Comment: #0 - Kalpana Shetty  - 2018-09-15 23:55:13 ==
  ---Problem Description---
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with 
nouveau errors

  Contact Information = kalsh...@in.ibm.com, preeti.tha...@in.ibm.com

  ---uname output---
  root@ltc-wcwsp3:~# uname -a Linux ltc-wcwsp3 4.18.0-7-generic #8-Ubuntu SMP 
Tue Aug 28 18:20:56 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = Witherspoon DD2.2 LC

  Steps:
  1. Netinstall Ubu 18.10 on Witherspoon-LC-DD2.2 6GPU system --> PASS
  2. Boot the OS ---> PASS but error thrown on the console related open source 
NVIDIA driver.

    [Disk: sdb2 / c0302064-c5a3-49a7-8bd4-402283e6fcbe]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu
    [Disk: nvme0n1p2 / c5d042f1-812e-49e0-94b2-ade477084061]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
   *  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu

    System information
    System configuration
    System status log
    Language
    Rescan devices
    Retrieve config from URL
    Plugins (0)
    Exit to shell
   
??
   Enter=accept, e=edit, n=new, x=exit, l=language, g=log, h=help
  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [   57.513329] kexec_core: Starting new kernel
  [  149.358703978,5] OPAL: Switch to big-endian OS
  [  153.355498935,5] OPAL: Switch to little-endian OS
  [2.943735] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  [2.943738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [3.132733] vio vio: uevent: failed to send synthetic uevent
  [4.058698] nouveau 0004:04:00.0: gr: failed to load gr/sw_nonctx
  [4.129215] nouveau 0004:04:00.0: DRM: failed to create kernel channel, -22
  [   19.126509] nouveau 0004:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   19.281450] nouveau 0004:05:00.0: gr: failed to load gr/sw_nonctx
  [   19.351322] nouveau 0004:05:00.0: DRM: failed to create kernel channel, -22
  [   34.350509] nouveau 0004:05:00.0: DRM: failed to idle channel 0 [DRM]
  [   34.502063] nouveau 0004:06:00.0: gr: failed to load gr/sw_nonctx
  [   34.572144] nouveau 0004:06:00.0: DRM: failed to create kernel channel, -22
  [   49.570509] nouveau 0004:06:00.0: DRM: failed to idle channel 0 [DRM]
  [   49.734754] nouveau 0035:03:00.0: gr: failed to load gr/sw_nonctx
  [   49.805057] nouveau 0035:03:00.0: DRM: failed to create kernel channel, -22
  [   64.802510] nouveau 0035:03:00.0: DRM: failed to idle channel 0 [DRM]
  [   64.955442] nouveau 0035:04:00.0: gr: failed to load gr/sw_nonctx
  [   65.025537] nouveau 0035:04:00.0: DRM: failed to create kernel channel, -22

  [   80.022509] nouveau 0035:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   80.181169] nouveau 0035:05:00.0: gr: failed to load gr/sw_nonctx
  [   80.251481] nouveau 0035:05:00.0: DRM: failed to create kernel channel, -22
  [   95.250509] nouveau 0035:05:00.0: DRM: failed to idle channel 0 [DRM]
  /dev/nvme0n1p2: recovering journal
  /dev/nvme0n1p2: clean, 72569/97681408 files, 7384418/390701312 blocks
  -.mount
  kmod-static-nodes.service
  dev-hugepages.mount
  dev-mqueue.mount
  sys-kernel-debug.mount
  ufw.service
  lvm2-lvmetad.service
  systemd-remount-fs.service
  systemd-random-seed.service
  systemd-sysusers.service
  keyboard-setup.service
  systemd-tmpfiles-setup-dev.service
  lvm2-monitor.service
  finalrd.service
  console-setup.service
  swapfile.swap
  ebtables.service
  systemd-udevd.service
  systemd-journald.service
  systemd-journal-flush.service
  systemd-tmpfiles-setup.service
  systemd-update-utmp.service
  [  

[Kernel-packages] [Bug 1690085]

2019-03-22 Thread bp
(In reply to Lars Viklund from comment #570)
> rdmsr yields 68010, which has bit 4 set.

Looks like your BIOS applies the fix. Now, does the patch in comment
#526 fix your freezes?

-- 
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 

[Kernel-packages] [Bug 1821413] Status changed to Confirmed

2019-03-22 Thread Ubuntu Kernel Bot
This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821413

Title:
  package linux-image-5.0.0-7-generic 5.0.0-7.8 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from Cosmic via do-release-upgrade -d.
  Original install 12.04.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-7-generic 5.0.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2279 F pulseaudio
  Date: Fri Mar 22 20:50:59 2019
  EcryptfsInUse: Yes
  ErrorMessage: triggers looping, abandoned
  HibernationDevice: RESUME=UUID=016d396c-0534-4a44-8eaa-4fe357d53df4
  InstallationDate: Installed on 2018-10-28 (145 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc7800p Small Form Factor
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=c285ab97-7e53-4db4-9e30-a274b6ea828b ro quiet splash vt.handoff=1
  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.
  Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-5.0.0-7-generic 5.0.0-7.8 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-03-22 (0 days ago)
  dmi.bios.date: 07/18/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F1 v01.04
  dmi.board.name: 0AA8h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F1v01.04:bd07/18/2007:svnHewlett-Packard:pnHPCompaqdc7800pSmallFormFactor:pvr:rvnHewlett-Packard:rn0AA8h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc7800p Small Form Factor
  dmi.product.sku: KB929ET#ABU
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821413/+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 1819707] Re: linux-fips: 4.15.0-1002.2 -proposed tracker

2019-03-22 Thread Brad Figg
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1819716
- phase: Ready for Packaging
- phase-changed: Wednesday, 13. March 2019 11:04 UTC
+ phase: Packaging
+ phase-changed: Friday, 22. March 2019 21:12 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded

-- 
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/1819707

Title:
  linux-fips: 4.15.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1819716
  phase: Packaging
  phase-changed: Friday, 22. March 2019 21:12 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819707/+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 1821413] Re: package linux-image-5.0.0-7-generic 5.0.0-7.8 failed to install/upgrade: triggers looping, abandoned

2019-03-22 Thread Apport retracing service
** Tags removed: need-duplicate-check

-- 
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/1821413

Title:
  package linux-image-5.0.0-7-generic 5.0.0-7.8 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  New

Bug description:
  Upgrading from Cosmic via do-release-upgrade -d.
  Original install 12.04.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-7-generic 5.0.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2279 F pulseaudio
  Date: Fri Mar 22 20:50:59 2019
  EcryptfsInUse: Yes
  ErrorMessage: triggers looping, abandoned
  HibernationDevice: RESUME=UUID=016d396c-0534-4a44-8eaa-4fe357d53df4
  InstallationDate: Installed on 2018-10-28 (145 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc7800p Small Form Factor
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=c285ab97-7e53-4db4-9e30-a274b6ea828b ro quiet splash vt.handoff=1
  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.
  Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-5.0.0-7-generic 5.0.0-7.8 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-03-22 (0 days ago)
  dmi.bios.date: 07/18/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F1 v01.04
  dmi.board.name: 0AA8h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F1v01.04:bd07/18/2007:svnHewlett-Packard:pnHPCompaqdc7800pSmallFormFactor:pvr:rvnHewlett-Packard:rn0AA8h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc7800p Small Form Factor
  dmi.product.sku: KB929ET#ABU
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821413/+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 1815831] Re: [ALSA] [PATCH] System76 darp5 and oryp5 fixups

2019-03-22 Thread Steven Clarkson
Any chance this could land in the xenial HWE kernel as well?

-- 
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/1815831

Title:
  [ALSA] [PATCH] System76 darp5 and oryp5 fixups

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: The System76 darp5 and oryp5 platforms need audio driverquirks
  to fix up the pin configuration.

  Fix: One backport from upstream, and one cherry pick from the upstream
  sound tree.

  Test Case: Backports have been tested on the affected hardware.

  Regression Potential: These are quirks for specific PCI device ids and
  thus are not expected to introduce regressions for any other hardware.

  ---

  Two fixups are needed to support the headset microphone on the
  System76 darp5 and oryp5. The darp5 patch is attached here, the oryp5
  patch will be attached on the next comment.

  On the System76 Darter Pro (darp5), there is a headset microphone
  input attached to 0x1a that does not have a jack detect. In order to
  get it working, the pin configuration needs to be set correctly, and
  the ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC fixup needs to be applied.
  This is similar to the MIC_NO_PRESENCE fixups for some Dell laptops,
  except we have a separate microphone jack that is already configured
  correctly.

  On the System76 Oryx Pro (oryp5), there is a headset microphone input
  attached to 0x19 that does not have a jack detect. In order to get it
  working, the pin configuration needs to be set correctly, and the
  ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC fixup needs to be applied. This is
  similar to the MIC_NO_PRESENCE fixups for some Dell laptops, except we
  have a separate microphone jack that is already configured correctly.
  Since the ALC1220 does not have a fixup similar to
  ALC269_FIXUP_HEADSET_MODE_NO_HP_MIC, I have exposed the fixup from the
  ALC269 in a way that it can be accessed from the
  alc1220_fixup_system76_oryp5 function. In addition, the
  alc1220_fixup_clevo_p950 needs to be applied to gain speaker output.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815831/+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 1821413] [NEW] package linux-image-5.0.0-7-generic 5.0.0-7.8 failed to install/upgrade: triggers looping, abandoned

2019-03-22 Thread 4AF4AF
Public bug reported:

Upgrading from Cosmic via do-release-upgrade -d.
Original install 12.04.

ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-7-generic 5.0.0-7.8
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm2279 F pulseaudio
Date: Fri Mar 22 20:50:59 2019
EcryptfsInUse: Yes
ErrorMessage: triggers looping, abandoned
HibernationDevice: RESUME=UUID=016d396c-0534-4a44-8eaa-4fe357d53df4
InstallationDate: Installed on 2018-10-28 (145 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
IwConfig:
 lono wireless extensions.
 
 eth0  no wireless extensions.
MachineType: Hewlett-Packard HP Compaq dc7800p Small Form Factor
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=c285ab97-7e53-4db4-9e30-a274b6ea828b ro quiet splash vt.handoff=1
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.
Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1
PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
RfKill:
 
SourcePackage: linux
Title: package linux-image-5.0.0-7-generic 5.0.0-7.8 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to disco on 2019-03-22 (0 days ago)
dmi.bios.date: 07/18/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786F1 v01.04
dmi.board.name: 0AA8h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F1v01.04:bd07/18/2007:svnHewlett-Packard:pnHPCompaqdc7800pSmallFormFactor:pvr:rvnHewlett-Packard:rn0AA8h:rvr:cvnHewlett-Packard:ct4:cvr:
dmi.product.family: 103C_53307F
dmi.product.name: HP Compaq dc7800p Small Form Factor
dmi.product.sku: KB929ET#ABU
dmi.sys.vendor: Hewlett-Packard

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package disco

-- 
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/1821413

Title:
  package linux-image-5.0.0-7-generic 5.0.0-7.8 failed to
  install/upgrade: triggers looping, abandoned

Status in linux package in Ubuntu:
  New

Bug description:
  Upgrading from Cosmic via do-release-upgrade -d.
  Original install 12.04.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-7-generic 5.0.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2279 F pulseaudio
  Date: Fri Mar 22 20:50:59 2019
  EcryptfsInUse: Yes
  ErrorMessage: triggers looping, abandoned
  HibernationDevice: RESUME=UUID=016d396c-0534-4a44-8eaa-4fe357d53df4
  InstallationDate: Installed on 2018-10-28 (145 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Hewlett-Packard HP Compaq dc7800p Small Form Factor
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=c285ab97-7e53-4db4-9e30-a274b6ea828b ro quiet splash vt.handoff=1
  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.
  Python3Details: /usr/bin/python3.7, Python 3.7.2+, python3-minimal, 3.7.2-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-5.0.0-7-generic 5.0.0-7.8 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-03-22 (0 days ago)
  dmi.bios.date: 07/18/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786F1 v01.04
  dmi.board.name: 0AA8h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F1v01.04:bd07/18/2007:svnHewlett-Packard:pnHPCompaqdc7800pSmallFormFactor:pvr:rvnHewlett-Packard:rn0AA8h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc7800p Small Form Factor
  dmi.product.sku: KB929ET#ABU
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821413/+subscriptions

-- 
Mailing list: 

[Kernel-packages] [Bug 1819653] Re: linux-aws: 4.4.0-1078.88 -proposed tracker

2019-03-22 Thread Brad Figg
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1819660
  phase: Testing
  phase-changed: Tuesday, 19. March 2019 13:31 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
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/1819653

Title:
  linux-aws: 4.4.0-1078.88 -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:
  Fix Released
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 verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1819660
  phase: Testing
  phase-changed: Tuesday, 19. March 2019 13:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
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/1819653/+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 1819653] Re: linux-aws: 4.4.0-1078.88 -proposed tracker

2019-03-22 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
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/1819653

Title:
  linux-aws: 4.4.0-1078.88 -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:
  Fix Released
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 verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1819660
  phase: Testing
  phase-changed: Tuesday, 19. March 2019 13:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
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/1819653/+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 1821390] Re: apic-split will fail in kvm_units_tests on aws i3.metal

2019-03-22 Thread Sean Feole
Also affects Xenial linux-aws 4.4.0-1078.88

** Tags added: 4.4 xenial

-- 
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/1821390

Title:
  apic-split will fail in kvm_units_tests on aws i3.metal

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make

  4.) TESTNAME=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat
  -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split

  root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=apic-split 
TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 
2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split # -initrd 
/tmp/tmp.ZHQwPUOuLD
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 459000
  cr4 = 20
  apic version: 1050014
  PASS: apic existence
  PASS: xapic id matches cpuid
  PASS: writeable xapic id
  PASS: non-writeable x2apic id
  PASS: sane x2apic id
  PASS: x2apic id matches cpuid
  PASS: correct xapic id after reset
  PASS: apic_disable: Local apic disabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  PASS: apic_disable: Local apic enabled in xAPIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 1050014
  PASS: apic_disable: *0xfee00080: 0
  PASS: apic_disable: *0xfee00080: f0
  PASS: apic_disable: Local apic enabled in x2APIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  x2apic enabled
  PASS: x2apic enabled to invalid state
  PASS: x2apic enabled to apic enabled
  PASS: x2apic enabled to disabled state
  PASS: disabled to invalid state
  PASS: disabled to x2apic enabled
  PASS: apic enabled to invalid state
  PASS: apicbase: relocate apic
  PASS: apicbase: reserved physaddr bits
  PASS: apicbase: reserved low bits
  PASS: self ipi
  starting broadcast (x2apic)
  PASS: APIC physical broadcast address
  PASS: APIC physical broadcast shorthand
  FAIL: PV IPIs testing
  PASS: nmi-after-sti
  PASS: multiple nmi
  PASS: APIC LVT timer one shot
  starting apic change mode
  PASS: TMICT value reset
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should have reached 0
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should not be reset to TMICT value
  PASS: TMCCT should be reset to the initial-count
  PASS: TMCCT should not be reset to init
  PASS: TMCCT should have reach zero
  PASS: TMCCT should stay at zero
  PASS: tsc deadline timer
  PASS: tsc deadline timer clearing
  SUMMARY: 51 tests, 1 unexpected failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821390/+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 1821393] Re: vmware_backdoors will fail on kvm_unit_tests on aws i3.metal

2019-03-22 Thread Sean Feole
Also affects Xenial linux-aws 4.4.0-1078.88


** Tags added: 4.4 xenial

-- 
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/1821393

Title:
  vmware_backdoors will fail on kvm_unit_tests on aws i3.metal

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmware_backdoors TIMEOUT=90s ACCEL= ./x86/run 
x86/vmware_backdoors.flat -smp 1 -machine vmport=on

  root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=vmware_backdoors 
TIMEOUT=90s ACCEL= ./x86/run x86/vmware_backdoors.flat -smp 1 -machine vmport=on
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel 
x86/vmware_backdoors.flat -smp 1 -machine vmport=on # -initrd 
/tmp/tmp.QldMaGLdve
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 45b000
  cr4 = 20
  PASS: vmware_backdoors: rdpmc_test: HOST_TSC kernel
  PASS: vmware_backdoors: rdpmc_test: REAL_TIME kernel
  PASS: vmware_backdoors: rdpmc_test: APPARENT_TIME kernel
  FAIL: vmware_backdoors: rdpmc_test: HOST_TSC user
  FAIL: vmware_backdoors: rdpmc_test: REAL_TIME user
  FAIL: vmware_backdoors: rdpmc_test: APPARENT_TIME user
  PASS: vmware_backdoors: rdpmc_test: RANDOM PMC user
  FAIL: vmware_backdoors: port_test: CMD_GETVERSION user
  PASS: vmware_backdoors: port_test: CMD_GETVERSION kernel
  FAIL: vmware_backdoors: port_test: CMD_ILLEGAL user
  PASS: vmware_backdoors: port_test: RANDOM port user
  SUMMARY: 11 tests, 5 unexpected failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821393/+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 1819707] Re: linux-fips: 4.15.0-1002.2 -proposed tracker

2019-03-22 Thread Marcelo Cerri
** Summary changed:

- linux-fips:  -proposed tracker
+ linux-fips: 4.15.0-1002.2 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

-- 
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/1819707

Title:
  linux-fips: 4.15.0-1002.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1819716
  phase: Ready for Packaging
  phase-changed: Wednesday, 13. March 2019 11:04 UTC
  reason:
prepare-package: Pending -- version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819707/+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 1821394] Re: vmx tests fail in kvm_unit_tests on aws i3.metal

2019-03-22 Thread Sean Feole
Also affects Xenial linux-aws 4.4.0-1078.88


** Tags added: 4.4 xenial

-- 
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/1821394

Title:
  vmx tests fail in kvm_unit_tests on aws i3.metal

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test"

  PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails
  PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails
  INFO: Processor supports accessed and dirty flag
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds
  PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails
  PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4096: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8192: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved 

[Kernel-packages] [Bug 1794055] Please test proposed package

2019-03-22 Thread Steve Langasek
Hello bugproxy, or anyone else affected,

Accepted linux-firmware into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.175.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1794055

Title:
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown
  with nouveau errors; OS booted successfully

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  Won't Fix
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in linux-firmware source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification

  Impact: Missing firmware for nouveau is causing errors to appear in
  dmesg.

  Fix: Add missing firmware files from upstream linux-firmware.

  Test Case: Confirm that errors in dmesg are gone once new firmware
  files are present.

  Regression Potential: New and updated firmware always has potential to
  cause regressions, however this firmware has been in disco for several
  months with no reported issues.

  ---

  == Comment: #0 - Kalpana Shetty  - 2018-09-15 23:55:13 ==
  ---Problem Description---
  [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with 
nouveau errors

  Contact Information = kalsh...@in.ibm.com, preeti.tha...@in.ibm.com

  ---uname output---
  root@ltc-wcwsp3:~# uname -a Linux ltc-wcwsp3 4.18.0-7-generic #8-Ubuntu SMP 
Tue Aug 28 18:20:56 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = Witherspoon DD2.2 LC

  Steps:
  1. Netinstall Ubu 18.10 on Witherspoon-LC-DD2.2 6GPU system --> PASS
  2. Boot the OS ---> PASS but error thrown on the console related open source 
NVIDIA driver.

    [Disk: sdb2 / c0302064-c5a3-49a7-8bd4-402283e6fcbe]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu
    [Disk: nvme0n1p2 / c5d042f1-812e-49e0-94b2-ade477084061]
  Ubuntu, with Linux 4.18.0-7-generic (recovery mode)
   *  Ubuntu, with Linux 4.18.0-7-generic
  Ubuntu

    System information
    System configuration
    System status log
    Language
    Rescan devices
    Retrieve config from URL
    Plugins (0)
    Exit to shell
   
??
   Enter=accept, e=edit, n=new, x=exit, l=language, g=log, h=help
  The system is going down NOW!
  Sent SIGTERM to all processes
  Sent SIGKILL to all processes
  [   57.513329] kexec_core: Starting new kernel
  [  149.358703978,5] OPAL: Switch to big-endian OS
  [  153.355498935,5] OPAL: Switch to little-endian OS
  [2.943735] integrity: Unable to open file: /etc/keys/x509_ima.der (-2)
  [2.943738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2)
  [3.132733] vio vio: uevent: failed to send synthetic uevent
  [4.058698] nouveau 0004:04:00.0: gr: failed to load gr/sw_nonctx
  [4.129215] nouveau 0004:04:00.0: DRM: failed to create kernel channel, -22
  [   19.126509] nouveau 0004:04:00.0: DRM: failed to idle channel 0 [DRM]
  [   19.281450] nouveau 0004:05:00.0: gr: failed to load gr/sw_nonctx
  [   19.351322] nouveau 0004:05:00.0: DRM: failed to create kernel channel, -22
  [   34.350509] nouveau 0004:05:00.0: DRM: failed to idle channel 0 [DRM]
  [   34.502063] nouveau 0004:06:00.0: gr: failed to load gr/sw_nonctx
  [   34.572144] nouveau 0004:06:00.0: DRM: failed to create kernel channel, -22
  [   49.570509] nouveau 0004:06:00.0: DRM: failed to idle channel 0 [DRM]
  [   49.734754] nouveau 0035:03:00.0: gr: failed to load gr/sw_nonctx
  [   49.805057] nouveau 0035:03:00.0: DRM: failed to create kernel channel, -22
  [   

[Kernel-packages] [Bug 1808389] Please test proposed package

2019-03-22 Thread Steve Langasek
Hello James, or anyone else affected,

Accepted linux-firmware into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.175.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1808389

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

Status in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  Fix Committed
Status in The Bionic Beaver:
  New
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in The Cosmic Cuttlefish:
  New
Status in linux-firmware source package in Cosmic:
  Fix Committed

Bug description:
  SRU Justification:
  ===
  [Impact]
  repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6.

  [Fix]
  New iwlwifi firmware fix it.

  [Test]
  Bug reporter verified with positive result.

  [Regression Potential]
  Upstream fix, low risk.
  Bug reporter confirms fix.

  
  Original bug report:
  =

  Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1
  Gen6.

  Firmware: 36.7596afd4.0

  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | 

[Kernel-packages] [Bug 1817817] Please test proposed package

2019-03-22 Thread Steve Langasek
Hello AceLan, or anyone else affected,

Accepted linux-firmware into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.175.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1817817

Title:
  To add power setting bin file for SAR support (QCA6174)

Status in HWE Next:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  To meet the policy requirement of the RF radiation, we need to reduce the 
power of the device.

  [Fix]
  Qualcomm provides a new firmware for this.
  97b1f938 ath10k: QCA6174 hw3.0: update board-2.bin

  [Test]
  We can't verify it.

  [Regression Potential]
  Low, it's a fix from upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1817817/+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 1801383] Re: the WifiSyslog apport hook (used in firefox/tb) includes SSID informations

2019-03-22 Thread Brian Murray
** Tags added: rls-ee-incoming

-- 
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/1801383

Title:
  the WifiSyslog apport hook (used in firefox/tb) includes SSID
  informations

Status in apport package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  New

Bug description:
  When I apport-bug certain packages such as firefox for example, it
  uploads the WifiSyslog.txt file.

  The WifiSyslog may contain a list of all system connections enumerated
  in /etc/NetworkManager/system-connections, i.e. all SSIDs the user has
  ever connected to that are found in the system-connections. This is a
  serious privacy risk and completely unnecessary information for most
  bug reports.

  Should either remove WifiSyslog as a requirement for packages that
  don't need it (should I report this to
  https://bugs.launchpad.net/ubuntu/+source/firefox/ ?), or redact
  information that may contain usernames and SSIDs from the log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.4
  ProcVersionSignature: User Name 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CrashReports: 640:1000:117:62475:2018-11-01 19:17:29.982295751 
-0400:2018-11-01 19:17:30.982295751 
-0400:/var/crash/_usr_bin_gnome-screenshot.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 11:24:20 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-09-12 (50 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-09-28 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1801383/+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 1821408] Re: scsi: libsas: Support SATA PHY connection rate unmatch fixing during discovery

2019-03-22 Thread dann frazier
This change should qualify for an SRU. However, Canonical does not have
the described hardware. We will need help from Huawei to test the SRU.
Can Huawei commit to the following steps?

 1) Test a PPA build with this fix (both 4.15 and 4.18) by 2019-03-27. 
Canonical can prepare this PPA.
 2) After official Ubuntu kernel build, re-test both kernels to verify the fix. 
During the week of 2019-04-08.

-- 
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/1821408

Title:
  scsi: libsas: Support SATA PHY connection rate unmatch fixing during
  discovery

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  In Progress

Bug description:
  [Impact]
  SATA disks may be unusable
  will not be usable when:
   - The disk is connected through a SAS expander
   - Controller uses a libsas-based driver (mvsas, aic94xx, hisi_sas)
   - link rate between expander & disk is greater than link between controller 
and expander

  [Test Case]
  See conditions in "Impact"

  [Fix]
  cec9771d2e954 scsi: libsas: Support SATA PHY connection rate unmatch fixing 
during discovery

  [Regression Risk]
  Impact is restricted to drivers that use libsas: mvsas, aic94xx & hisi_sas.
  Code change is all within an "if" statement that meets these restrictions.
  A bug in this code could possibly reduce the speed of an otherwise working 
disk connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821408/+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 1821395] Re: fscache: jobs might hang when fscache disk is full

2019-03-22 Thread Mauricio Faria de Oliveira
[B/C][PATCH 0/1] Fix for LP#1821395 (fscache: jobs might hang when fscache disk 
is full)
https://lists.ubuntu.com/archives/kernel-team/2019-March/099448.html

** Description changed:

- < NOTE: patches will be sent to kernel-team mailing list. >
- 
  [Impact]
  
-  * fscache issue where jobs get hung when fscache disk is full.
+  * fscache issue where jobs get hung when fscache disk is full.
  
-  * trivial upstream fix; already applied in X/D, required in B/C:
-commit c5a94f434c82 ("fscache: fix race between enablement and
-dropping of object").
+  * trivial upstream fix; already applied in X/D, required in B/C:
+    commit c5a94f434c82 ("fscache: fix race between enablement and
+    dropping of object").
  
  [Test Case]
  
-  * Test kernel verified / regression-tested by reporter.
+  * Test kernel verified / regression-tested by reporter.
  
-  * Apparently there's no simple test case, 
-but these are the conditions to hit the problem:
+  * Apparently there's no simple test case,
+    but these are the conditions to hit the problem:
  
-1) The active dataset size is equal to the cache disk size. 
-   The application reads the data over and over again.
-2) Disk is near full (90%+)
-3) cachefilesd in userspace is trying to cull the old objects
-   while new objects are being looked up.
-4) new cachefiles are created and some fail with no disk space.
-5) race in dropping object state machine and 
-   deferred lookup state machine causes the hang.
-6) HUNG in fscache_wait_for_deferred_lookup for
-   clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.
+    1) The active dataset size is equal to the cache disk size.
+   The application reads the data over and over again.
+    2) Disk is near full (90%+)
+    3) cachefilesd in userspace is trying to cull the old objects
+   while new objects are being looked up.
+    4) new cachefiles are created and some fail with no disk space.
+    5) race in dropping object state machine and
+   deferred lookup state machine causes the hang.
+    6) HUNG in fscache_wait_for_deferred_lookup for
+   clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.
  
  [Regression Potential]
  
-  * Low; contained in fscache; no further fixes applied upstream.
+  * Low; contained in fscache; no further fixes applied upstream.
  
-  * This patch is applied in a stable tree (linux-4.4.y).
+  * This patch is applied in a stable tree (linux-4.4.y).
  
  [Original Description]
  
  An user reported an fscache issue where jobs get hung when the fscache
  disk is full.
  
  After investigation, it's been found to be an issue already reported/fixed 
upstream,
  by commit c5a94f434c82 ("fscache: fix race between enablement and dropping of 
object").
  
  This patch is required in Bionic and Cosmic, and it's applied in Xenial
  (via stable) and Disco.
  
  Apparently there's no simple test case, but these are the conditions to
  hit the problem:
  
- 1) The active dataset size is equal to the cache disk size. 
-The application reads the data over and over again.
+ 1) The active dataset size is equal to the cache disk size.
+    The application reads the data over and over again.
  2) Disk is near full (90%+)
  3) cachefilesd in userspace is trying to cull the old objects
-while new objects are being looked up.
+    while new objects are being looked up.
  4) new cachefiles are created and some fail with no disk space.
- 5) race in dropping object state machine and 
-deferred lookup state machine causes the hang.
+ 5) race in dropping object state machine and
+    deferred lookup state machine causes the hang.
  6) HUNG in fscache_wait_for_deferred_lookup for
-clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.
+    clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.

-- 
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/1821395

Title:
  fscache: jobs might hang when fscache disk is full

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  [Impact]

   * fscache issue where jobs get hung when fscache disk is full.

   * trivial upstream fix; already applied in X/D, required in B/C:
     commit c5a94f434c82 ("fscache: fix race between enablement and
     dropping of object").

  [Test Case]

   * Test kernel verified / regression-tested by reporter.

   * Apparently there's no simple test case,
     but these are the conditions to hit the problem:

     1) The active dataset size is equal to the cache disk size.
    The application reads the data over and over again.
     2) Disk is near full (90%+)
     3) cachefilesd in userspace is trying to cull the old objects
    while new objects are being looked up.
     4) new cachefiles are created and some fail with no disk space.
     5) race in 

[Kernel-packages] [Bug 1821408] [NEW] scsi: libsas: Support SATA PHY connection rate unmatch fixing during discovery

2019-03-22 Thread dann frazier
Public bug reported:

[Impact]
SATA disks may be unusable
will not be usable when:
 - The disk is connected through a SAS expander
 - Controller uses a libsas-based driver (mvsas, aic94xx, hisi_sas)
 - link rate between expander & disk is greater than link between controller 
and expander

[Test Case]
See conditions in "Impact"

[Fix]
cec9771d2e954 scsi: libsas: Support SATA PHY connection rate unmatch fixing 
during discovery

[Regression Risk]
Impact is restricted to drivers that use libsas: mvsas, aic94xx & hisi_sas.
Code change is all within an "if" statement that meets these restrictions.
A bug in this code could possibly reduce the speed of an otherwise working disk 
connection.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Cosmic)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Disco)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Also affects: linux (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Disco)
   Status: New => In Progress

** Changed in: linux (Ubuntu Disco)
 Assignee: (unassigned) => dann frazier (dannf)

-- 
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/1821408

Title:
  scsi: libsas: Support SATA PHY connection rate unmatch fixing during
  discovery

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux source package in Disco:
  In Progress

Bug description:
  [Impact]
  SATA disks may be unusable
  will not be usable when:
   - The disk is connected through a SAS expander
   - Controller uses a libsas-based driver (mvsas, aic94xx, hisi_sas)
   - link rate between expander & disk is greater than link between controller 
and expander

  [Test Case]
  See conditions in "Impact"

  [Fix]
  cec9771d2e954 scsi: libsas: Support SATA PHY connection rate unmatch fixing 
during discovery

  [Regression Risk]
  Impact is restricted to drivers that use libsas: mvsas, aic94xx & hisi_sas.
  Code change is all within an "if" statement that meets these restrictions.
  A bug in this code could possibly reduce the speed of an otherwise working 
disk connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821408/+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 1819694] Re: linux-aws: 4.15.0-1035.37 -proposed tracker

2019-03-22 Thread Brad Figg
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1819693 (xenial/linux-aws-hwe)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Tuesday, 19. March 2019 14:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-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 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/1819694

Title:
  linux-aws: 4.15.0-1035.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:
  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:
  Fix Released
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 verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1819693 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Tuesday, 19. March 2019 14:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-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/1819694/+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 1819694] Re: linux-aws: 4.15.0-1035.37 -proposed tracker

2019-03-22 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
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/1819694

Title:
  linux-aws: 4.15.0-1035.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:
  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:
  Fix Released
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 verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1819693 (xenial/linux-aws-hwe)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819716
  phase: Testing
  phase-changed: Tuesday, 19. March 2019 14:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-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/1819694/+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 1814237] Re: ubuntu_nbd_smoke_test failed with I/O error on X-4.15

2019-03-22 Thread Sean Feole
This bug appeared to surface on aws Bionic linux-aws  kernel-version": 
"4.15.0-1035.37", AMD64
We also see this occurring on arm64 instances a1.medium so it does not appear 
to be arch specific. 

AMD64 Instances: c5.large , m4.large, m5a.large, r3.large , r5.large,
t2.small and t3.medium.

This is not 100% reproducible, if affects different instance types
during each SRU cycle and appears to be random. However the failure,
although not identical bit for bit, is a buffer I/O error

I restarted a select few of the failed tests some passed completely and
some failed again.

I attempted to reproduce on m5a.large.

1.) Deploy m5a.large using cloud prov script with Bionic, ensure kernel is 
4.15.0-1035.37 (in proposed at the time of writing this comment) 
2.) Clone autotest and autotest-client-tests: 
git clone https://github.com/autotest/autotest.git
git clone git://kernel.ubuntu.com/ubuntu/autotest-client-tests

3.) sudo apt-get update && sudo apt-get install python-pkg-resources
4.) 

untu@ip-172-31-10-8:~/autotest/client$ sudo ./autotest-local -d
~/autotest-client-tests/ ~/autotest-client-
tests/ubuntu_nbd_smoke_test/control


19:42:55 INFO | Writing results to /home/ubuntu/autotest/client/results/default
19:42:55 INFO | START   timestamp=1553283775localtime=Mar 
22 19:42:55   
19:42:55 INFO | START   ubuntu_nbd_smoke_test.nbd-smoke-test
ubuntu_nbd_smoke_test.nbd-smoke-testtimestamp=1553283775timeout=600 
localtime=Mar 22 19:42:55   
19:42:58 ERROR| [stderr] bs=1024, sz=134217728 bytes
19:42:58 ERROR| [stderr] timeout=30
19:42:58 ERROR| [stderr] e2fsck 1.44.1 (24-Mar-2018)
19:43:01 ERROR| Exception escaping from test:
Traceback (most recent call last):
  File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
return func(*args, **dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
  File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
self.run_once(*args, **dargs)
  File 
"/home/ubuntu/autotest-client-tests/ubuntu_nbd_smoke_test/ubuntu_nbd_smoke_test.py",
 line 51, in run_once
self.results = utils.system_output(cmd, retain_output=True)
  File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in 
system_output
verbose=verbose, args=args).stdout
  File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run
"Command returned non-zero exit status")
CmdError: Command 

 failed, rc=1, Command returned non-zero exit status
* Command: 
/home/ubuntu/autotest-client-
tests/ubuntu_nbd_smoke_test/ubuntu_nbd_smoke_test.sh
Exit status: 1
Duration: 6.14667606354

stdout:
creating backing nbd image /tmp/nbd_image.img
 

Image path:/tmp/nbd_image.img
Mount point:   /mnt/nbd-test-7736
Date:  Fri Mar 22 19:42:56 UTC 2019
Host:  ip-172-31-10-8
Kernel:4.15.0-1034-aws #36-Ubuntu SMP Tue Mar 5 23:17:16 UTC 2019
Machine:   ip-172-31-10-8 x86_64 x86_64
CPUs online:   2
CPUs total:2
Page size: 4096
Pages avail:   1641331
Pages total:   1977692
Free space:
Filesystem  Size  Used Avail Use% Mounted on
udev3.8G 0  3.8G   0% /dev
tmpfs   773M  800K  772M   1% /run
/dev/nvme0n1p1  7.7G  1.8G  6.0G  23% /
tmpfs   3.8G 0  3.8G   0% /dev/shm
tmpfs   5.0M 0  5.0M   0% /run/lock
tmpfs   3.8G 0  3.8G   0% /sys/fs/cgroup
/dev/loop0   92M   92M 0 100% /snap/core/6531
/dev/loop1   18M   18M 0 100% /snap/amazon-ssm-agent/1068
tmpfs   773M 0  773M   0% /run/user/1000

 
NBD device /dev/nbd0 created
found nbd export
NBD exports found:
test
starting client with NBD device /dev/nbd0
Negotiation: ..size = 128MB
creating ext4 on /dev/nbd0
mkfs on /dev/nbd0 succeeded after 0 attempt(s)
checking ext4 on /dev/nbd0
fsck from util-linux 2.31.1
/dev/nbd0: clean, 11/32768 files, 9787/131072 blocks

mount: 
/dev/nbd0 on /mnt/nbd-test-7736 type ext4 (rw,relatime,data=ordered)
mounted on /dev/nbd0

free: 
Filesystem 1K-blocks  Used Available Use% Mounted on
/dev/nbd0 122835  1550112111   2% /mnt/nbd-test-7736

creating large file /mnt/nbd-test-7736/largefile
-rw-r--r-- 1 root root 100M Mar 22 19:42 /mnt/nbd-test-7736/largefile

free: 
Filesystem 1K-blocks   Used Available Use% Mounted on
/dev/nbd0 122835 103951  9710  92% /mnt/nbd-test-7736

removing file /mnt/nbd-test-7736/largefile
unmounting /mnt/nbd-test-7736
stopping client
disconnect, sock, done
Found kernel warning, IO error and/or call trace
echo
[  703.195406] creating backing nbd image /tmp/nbd_image.img
[  

[Kernel-packages] [Bug 1820605] Re: linux-azure: 5.0.0-1001.1 -proposed tracker

2019-03-22 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Incomplete

** 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 --
  kernel-master-bug: 1819759
  phase: Promote to Proposed
  phase-changed: Wednesday, 20. March 2019 12:03 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed
+   promote-to-proposed: Stalled -- packages no longer available

-- 
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/1820605

Title:
  linux-azure: 5.0.0-1001.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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:
  Incomplete
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Disco:
  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 --
  kernel-master-bug: 1819759
  phase: Promote to Proposed
  phase-changed: Wednesday, 20. March 2019 12:03 UTC
  reason:
promote-to-proposed: Stalled -- packages no longer available

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820605/+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 1821395] Re: fscache: jobs might hang when fscache disk is full

2019-03-22 Thread Mauricio Faria de Oliveira
** Also affects: linux (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: linux (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: linux (Ubuntu Cosmic)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821395

Title:
  fscache: jobs might hang when fscache disk is full

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  < NOTE: patches will be sent to kernel-team mailing list. >

  [Impact]

   * fscache issue where jobs get hung when fscache disk is full.

   * trivial upstream fix; already applied in X/D, required in B/C:
 commit c5a94f434c82 ("fscache: fix race between enablement and
 dropping of object").

  [Test Case]

   * Test kernel verified / regression-tested by reporter.

   * Apparently there's no simple test case, 
 but these are the conditions to hit the problem:

 1) The active dataset size is equal to the cache disk size. 
The application reads the data over and over again.
 2) Disk is near full (90%+)
 3) cachefilesd in userspace is trying to cull the old objects
while new objects are being looked up.
 4) new cachefiles are created and some fail with no disk space.
 5) race in dropping object state machine and 
deferred lookup state machine causes the hang.
 6) HUNG in fscache_wait_for_deferred_lookup for
clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.

  [Regression Potential]

   * Low; contained in fscache; no further fixes applied upstream.

   * This patch is applied in a stable tree (linux-4.4.y).

  [Original Description]

  An user reported an fscache issue where jobs get hung when the fscache
  disk is full.

  After investigation, it's been found to be an issue already reported/fixed 
upstream,
  by commit c5a94f434c82 ("fscache: fix race between enablement and dropping of 
object").

  This patch is required in Bionic and Cosmic, and it's applied in
  Xenial (via stable) and Disco.

  Apparently there's no simple test case, but these are the conditions
  to hit the problem:

  1) The active dataset size is equal to the cache disk size. 
 The application reads the data over and over again.
  2) Disk is near full (90%+)
  3) cachefilesd in userspace is trying to cull the old objects
 while new objects are being looked up.
  4) new cachefiles are created and some fail with no disk space.
  5) race in dropping object state machine and 
 deferred lookup state machine causes the hang.
  6) HUNG in fscache_wait_for_deferred_lookup for
 clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821395/+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 1820310] Re: linux-gcp: 5.0.0-1001.1 -proposed tracker

2019-03-22 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Incomplete

** 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 --
  kernel-master-bug: 1819759
  phase: Promote to Proposed
  phase-changed: Wednesday, 20. March 2019 12:04 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed
+   promote-to-proposed: Stalled -- packages no longer available

-- 
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/1820310

Title:
  linux-gcp: 5.0.0-1001.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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:
  Incomplete
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Disco:
  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 --
  kernel-master-bug: 1819759
  phase: Promote to Proposed
  phase-changed: Wednesday, 20. March 2019 12:04 UTC
  reason:
promote-to-proposed: Stalled -- packages no longer available

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820310/+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 1821395] Missing required logs.

2019-03-22 Thread Ubuntu Kernel Bot
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1821395

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
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/1821395

Title:
  fscache: jobs might hang when fscache disk is full

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  < NOTE: patches will be sent to kernel-team mailing list. >

  [Impact]

   * fscache issue where jobs get hung when fscache disk is full.

   * trivial upstream fix; already applied in X/D, required in B/C:
 commit c5a94f434c82 ("fscache: fix race between enablement and
 dropping of object").

  [Test Case]

   * Test kernel verified / regression-tested by reporter.

   * Apparently there's no simple test case, 
 but these are the conditions to hit the problem:

 1) The active dataset size is equal to the cache disk size. 
The application reads the data over and over again.
 2) Disk is near full (90%+)
 3) cachefilesd in userspace is trying to cull the old objects
while new objects are being looked up.
 4) new cachefiles are created and some fail with no disk space.
 5) race in dropping object state machine and 
deferred lookup state machine causes the hang.
 6) HUNG in fscache_wait_for_deferred_lookup for
clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.

  [Regression Potential]

   * Low; contained in fscache; no further fixes applied upstream.

   * This patch is applied in a stable tree (linux-4.4.y).

  [Original Description]

  An user reported an fscache issue where jobs get hung when the fscache
  disk is full.

  After investigation, it's been found to be an issue already reported/fixed 
upstream,
  by commit c5a94f434c82 ("fscache: fix race between enablement and dropping of 
object").

  This patch is required in Bionic and Cosmic, and it's applied in
  Xenial (via stable) and Disco.

  Apparently there's no simple test case, but these are the conditions
  to hit the problem:

  1) The active dataset size is equal to the cache disk size. 
 The application reads the data over and over again.
  2) Disk is near full (90%+)
  3) cachefilesd in userspace is trying to cull the old objects
 while new objects are being looked up.
  4) new cachefiles are created and some fail with no disk space.
  5) race in dropping object state machine and 
 deferred lookup state machine causes the hang.
  6) HUNG in fscache_wait_for_deferred_lookup for
 clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821395/+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 1821393] Re: vmware_backdoors will fail on kvm_unit_tests on aws i3.metal

2019-03-22 Thread Sean Feole
Also affects Bionic linux-aws 4.15.1035.37

** Tags added: 4.15 4.18 bionic cosmic

-- 
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/1821393

Title:
  vmware_backdoors will fail on kvm_unit_tests on aws i3.metal

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmware_backdoors TIMEOUT=90s ACCEL= ./x86/run 
x86/vmware_backdoors.flat -smp 1 -machine vmport=on

  root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=vmware_backdoors 
TIMEOUT=90s ACCEL= ./x86/run x86/vmware_backdoors.flat -smp 1 -machine vmport=on
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel 
x86/vmware_backdoors.flat -smp 1 -machine vmport=on # -initrd 
/tmp/tmp.QldMaGLdve
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 45b000
  cr4 = 20
  PASS: vmware_backdoors: rdpmc_test: HOST_TSC kernel
  PASS: vmware_backdoors: rdpmc_test: REAL_TIME kernel
  PASS: vmware_backdoors: rdpmc_test: APPARENT_TIME kernel
  FAIL: vmware_backdoors: rdpmc_test: HOST_TSC user
  FAIL: vmware_backdoors: rdpmc_test: REAL_TIME user
  FAIL: vmware_backdoors: rdpmc_test: APPARENT_TIME user
  PASS: vmware_backdoors: rdpmc_test: RANDOM PMC user
  FAIL: vmware_backdoors: port_test: CMD_GETVERSION user
  PASS: vmware_backdoors: port_test: CMD_GETVERSION kernel
  FAIL: vmware_backdoors: port_test: CMD_ILLEGAL user
  PASS: vmware_backdoors: port_test: RANDOM port user
  SUMMARY: 11 tests, 5 unexpected failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821393/+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 1821390] Re: apic-split will fail in kvm_units_tests on aws i3.metal

2019-03-22 Thread Sean Feole
Also affects Bionic linux-aws 4.15.1035.37

** Tags added: 4.15 4.18 bionic cosmic

-- 
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/1821390

Title:
  apic-split will fail in kvm_units_tests on aws i3.metal

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make

  4.) TESTNAME=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat
  -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split

  root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=apic-split 
TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 
2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split # -initrd 
/tmp/tmp.ZHQwPUOuLD
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 459000
  cr4 = 20
  apic version: 1050014
  PASS: apic existence
  PASS: xapic id matches cpuid
  PASS: writeable xapic id
  PASS: non-writeable x2apic id
  PASS: sane x2apic id
  PASS: x2apic id matches cpuid
  PASS: correct xapic id after reset
  PASS: apic_disable: Local apic disabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  PASS: apic_disable: Local apic enabled in xAPIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 1050014
  PASS: apic_disable: *0xfee00080: 0
  PASS: apic_disable: *0xfee00080: f0
  PASS: apic_disable: Local apic enabled in x2APIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  x2apic enabled
  PASS: x2apic enabled to invalid state
  PASS: x2apic enabled to apic enabled
  PASS: x2apic enabled to disabled state
  PASS: disabled to invalid state
  PASS: disabled to x2apic enabled
  PASS: apic enabled to invalid state
  PASS: apicbase: relocate apic
  PASS: apicbase: reserved physaddr bits
  PASS: apicbase: reserved low bits
  PASS: self ipi
  starting broadcast (x2apic)
  PASS: APIC physical broadcast address
  PASS: APIC physical broadcast shorthand
  FAIL: PV IPIs testing
  PASS: nmi-after-sti
  PASS: multiple nmi
  PASS: APIC LVT timer one shot
  starting apic change mode
  PASS: TMICT value reset
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should have reached 0
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should not be reset to TMICT value
  PASS: TMCCT should be reset to the initial-count
  PASS: TMCCT should not be reset to init
  PASS: TMCCT should have reach zero
  PASS: TMCCT should stay at zero
  PASS: tsc deadline timer
  PASS: tsc deadline timer clearing
  SUMMARY: 51 tests, 1 unexpected failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821390/+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 1821394] [NEW] vmx tests fail in kvm_unit_tests on aws i3.metal

2019-03-22 Thread Sean Feole
Public bug reported:

Reproducible: Yes, every time.
Series: cosmic
Kernel: "linux-aws 4.18.0-1012.14"
Steps:

1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
3.) cd kvm-unit-tests; ./configure; make
4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test"

PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds
FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails
FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails
FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails
FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails
PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds
FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails
FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails
FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails
FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails
INFO: Processor supports accessed and dirty flag
PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds
PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds
PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds
FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails
PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds
FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 4096: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 8192: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 16384: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 32768: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 65536: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 131072: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 262144: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 524288: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 1048576: vmlaunch fails
FAIL: Enable-EPT enabled; reserved bits [63:N] 2097152: vmlaunch 

[Kernel-packages] [Bug 1819614] Re: linux-aws: 4.18.0-1012.14 -proposed tracker

2019-03-22 Thread Brad Figg
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1819613 (bionic/linux-aws-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819624
  phase: Testing
  phase-changed: Friday, 15. March 2019 18: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
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/1819614

Title:
  linux-aws: 4.18.0-1012.14 -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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1819613 (bionic/linux-aws-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819624
  phase: Testing
  phase-changed: Friday, 15. March 2019 18:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
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/1819614/+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 1821395] [NEW] fscache: jobs might hang when fscache disk is full

2019-03-22 Thread Mauricio Faria de Oliveira
Public bug reported:

< NOTE: patches will be sent to kernel-team mailing list. >

[Impact]

 * fscache issue where jobs get hung when fscache disk is full.

 * trivial upstream fix; already applied in X/D, required in B/C:
   commit c5a94f434c82 ("fscache: fix race between enablement and
   dropping of object").

[Test Case]

 * Test kernel verified / regression-tested by reporter.

 * Apparently there's no simple test case, 
   but these are the conditions to hit the problem:

   1) The active dataset size is equal to the cache disk size. 
  The application reads the data over and over again.
   2) Disk is near full (90%+)
   3) cachefilesd in userspace is trying to cull the old objects
  while new objects are being looked up.
   4) new cachefiles are created and some fail with no disk space.
   5) race in dropping object state machine and 
  deferred lookup state machine causes the hang.
   6) HUNG in fscache_wait_for_deferred_lookup for
  clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.

[Regression Potential]

 * Low; contained in fscache; no further fixes applied upstream.

 * This patch is applied in a stable tree (linux-4.4.y).

[Original Description]

An user reported an fscache issue where jobs get hung when the fscache
disk is full.

After investigation, it's been found to be an issue already reported/fixed 
upstream,
by commit c5a94f434c82 ("fscache: fix race between enablement and dropping of 
object").

This patch is required in Bionic and Cosmic, and it's applied in Xenial
(via stable) and Disco.

Apparently there's no simple test case, but these are the conditions to
hit the problem:

1) The active dataset size is equal to the cache disk size. 
   The application reads the data over and over again.
2) Disk is near full (90%+)
3) cachefilesd in userspace is trying to cull the old objects
   while new objects are being looked up.
4) new cachefiles are created and some fail with no disk space.
5) race in dropping object state machine and 
   deferred lookup state machine causes the hang.
6) HUNG in fscache_wait_for_deferred_lookup for
   clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1821395

Title:
  fscache: jobs might hang when fscache disk is full

Status in linux package in Ubuntu:
  New

Bug description:
  < NOTE: patches will be sent to kernel-team mailing list. >

  [Impact]

   * fscache issue where jobs get hung when fscache disk is full.

   * trivial upstream fix; already applied in X/D, required in B/C:
 commit c5a94f434c82 ("fscache: fix race between enablement and
 dropping of object").

  [Test Case]

   * Test kernel verified / regression-tested by reporter.

   * Apparently there's no simple test case, 
 but these are the conditions to hit the problem:

 1) The active dataset size is equal to the cache disk size. 
The application reads the data over and over again.
 2) Disk is near full (90%+)
 3) cachefilesd in userspace is trying to cull the old objects
while new objects are being looked up.
 4) new cachefiles are created and some fail with no disk space.
 5) race in dropping object state machine and 
deferred lookup state machine causes the hang.
 6) HUNG in fscache_wait_for_deferred_lookup for
clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.

  [Regression Potential]

   * Low; contained in fscache; no further fixes applied upstream.

   * This patch is applied in a stable tree (linux-4.4.y).

  [Original Description]

  An user reported an fscache issue where jobs get hung when the fscache
  disk is full.

  After investigation, it's been found to be an issue already reported/fixed 
upstream,
  by commit c5a94f434c82 ("fscache: fix race between enablement and dropping of 
object").

  This patch is required in Bionic and Cosmic, and it's applied in
  Xenial (via stable) and Disco.

  Apparently there's no simple test case, but these are the conditions
  to hit the problem:

  1) The active dataset size is equal to the cache disk size. 
 The application reads the data over and over again.
  2) Disk is near full (90%+)
  3) cachefilesd in userspace is trying to cull the old objects
 while new objects are being looked up.
  4) new cachefiles are created and some fail with no disk space.
  5) race in dropping object state machine and 
 deferred lookup state machine causes the hang.
  6) HUNG in fscache_wait_for_deferred_lookup for
 clear bit FSCACHE_COOKIE_LOOKING_UP cookie->flags.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821395/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : 

[Kernel-packages] [Bug 1821394] Re: vmx tests fail in kvm_unit_tests on aws i3.metal

2019-03-22 Thread Sean Feole
Also affects Bionic  linux-aws 4.15.1035.37

** Tags added: 4.15 4.18 bionic cosmic

-- 
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/1821394

Title:
  vmx tests fail in kvm_unit_tests on aws i3.metal

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu 
host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* 
-vmx_vmcs_shadow_test"

  PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails
  PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds
  FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails
  FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails
  INFO: Processor supports accessed and dirty flag
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds
  PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds
  PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails
  PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 4096: vmlaunch fails
  FAIL: Enable-EPT enabled; reserved bits [63:N] 8192: vmlaunch fails
  FAIL: Enable-EPT 

[Kernel-packages] [Bug 1819614] Re: linux-aws: 4.18.0-1012.14 -proposed tracker

2019-03-22 Thread Sean Feole
** Tags added: regression-testing-passed

-- 
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/1819614

Title:
  linux-aws: 4.18.0-1012.14 -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:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Cosmic:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: bug 1819613 (bionic/linux-aws-edge)

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1819624
  phase: Testing
  phase-changed: Friday, 15. March 2019 18:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
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/1819614/+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 1821390] Re: apic-split will fail in kvm_units_tests on aws i3.metal

2019-03-22 Thread Sean Feole
** Also affects: linux-aws (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1821390

Title:
  apic-split will fail in kvm_units_tests on aws i3.metal

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make

  4.) TESTNAME=apic-split TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat
  -smp 2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split

  root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=apic-split 
TIMEOUT=90s ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu 
qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 
2 -cpu qemu64,+x2apic,+tsc-deadline -machine kernel_irqchip=split # -initrd 
/tmp/tmp.ZHQwPUOuLD
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  enabling apic
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 459000
  cr4 = 20
  apic version: 1050014
  PASS: apic existence
  PASS: xapic id matches cpuid
  PASS: writeable xapic id
  PASS: non-writeable x2apic id
  PASS: sane x2apic id
  PASS: x2apic id matches cpuid
  PASS: correct xapic id after reset
  PASS: apic_disable: Local apic disabled
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  PASS: apic_disable: Local apic enabled in xAPIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 1050014
  PASS: apic_disable: *0xfee00080: 0
  PASS: apic_disable: *0xfee00080: f0
  PASS: apic_disable: Local apic enabled in x2APIC mode
  PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set
  PASS: apic_disable: *0xfee00030: 
  PASS: apic_disable: CR8: 0
  PASS: apic_disable: CR8: f
  PASS: apic_disable: *0xfee00080: 
  x2apic enabled
  PASS: x2apic enabled to invalid state
  PASS: x2apic enabled to apic enabled
  PASS: x2apic enabled to disabled state
  PASS: disabled to invalid state
  PASS: disabled to x2apic enabled
  PASS: apic enabled to invalid state
  PASS: apicbase: relocate apic
  PASS: apicbase: reserved physaddr bits
  PASS: apicbase: reserved low bits
  PASS: self ipi
  starting broadcast (x2apic)
  PASS: APIC physical broadcast address
  PASS: APIC physical broadcast shorthand
  FAIL: PV IPIs testing
  PASS: nmi-after-sti
  PASS: multiple nmi
  PASS: APIC LVT timer one shot
  starting apic change mode
  PASS: TMICT value reset
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should have reached 0
  PASS: TMCCT should have a non-zero value
  PASS: TMCCT should not be reset to TMICT value
  PASS: TMCCT should be reset to the initial-count
  PASS: TMCCT should not be reset to init
  PASS: TMCCT should have reach zero
  PASS: TMCCT should stay at zero
  PASS: tsc deadline timer
  PASS: tsc deadline timer clearing
  SUMMARY: 51 tests, 1 unexpected failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821390/+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 1821393] [NEW] vmware_backdoors will fail on kvm_unit_tests on aws i3.metal

2019-03-22 Thread Sean Feole
Public bug reported:

Reproducible: Yes, every time.
Series: cosmic
Kernel: "linux-aws 4.18.0-1012.14"
Steps:

1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
3.) cd kvm-unit-tests; ./configure; make
4.) TESTNAME=vmware_backdoors TIMEOUT=90s ACCEL= ./x86/run 
x86/vmware_backdoors.flat -smp 1 -machine vmport=on

root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=vmware_backdoors 
TIMEOUT=90s ACCEL= ./x86/run x86/vmware_backdoors.flat -smp 1 -machine vmport=on
timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device 
pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial 
stdio -device pci-testdev -machine accel=kvm -kernel x86/vmware_backdoors.flat 
-smp 1 -machine vmport=on # -initrd /tmp/tmp.QldMaGLdve
qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
enabling apic
paging enabled
cr0 = 80010011
cr3 = 45b000
cr4 = 20
PASS: vmware_backdoors: rdpmc_test: HOST_TSC kernel
PASS: vmware_backdoors: rdpmc_test: REAL_TIME kernel
PASS: vmware_backdoors: rdpmc_test: APPARENT_TIME kernel
FAIL: vmware_backdoors: rdpmc_test: HOST_TSC user
FAIL: vmware_backdoors: rdpmc_test: REAL_TIME user
FAIL: vmware_backdoors: rdpmc_test: APPARENT_TIME user
PASS: vmware_backdoors: rdpmc_test: RANDOM PMC user
FAIL: vmware_backdoors: port_test: CMD_GETVERSION user
PASS: vmware_backdoors: port_test: CMD_GETVERSION kernel
FAIL: vmware_backdoors: port_test: CMD_ILLEGAL user
PASS: vmware_backdoors: port_test: RANDOM port user
SUMMARY: 11 tests, 5 unexpected failures

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: aws i3.metal

** Also affects: linux-aws (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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/1821393

Title:
  vmware_backdoors will fail on kvm_unit_tests on aws i3.metal

Status in ubuntu-kernel-tests:
  New
Status in linux-aws package in Ubuntu:
  New

Bug description:
  Reproducible: Yes, every time.
  Series: cosmic
  Kernel: "linux-aws 4.18.0-1012.14"
  Steps:

  1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git 
gcc-multilib
  2.) git clone --depth=1 
https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
  3.) cd kvm-unit-tests; ./configure; make
  4.) TESTNAME=vmware_backdoors TIMEOUT=90s ACCEL= ./x86/run 
x86/vmware_backdoors.flat -smp 1 -machine vmport=on

  root@ip-172-31-5-254:/home/ubuntu/kvm-unit-tests# TESTNAME=vmware_backdoors 
TIMEOUT=90s ACCEL= ./x86/run x86/vmware_backdoors.flat -smp 1 -machine vmport=on
  timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults 
-device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none 
-serial stdio -device pci-testdev -machine accel=kvm -kernel 
x86/vmware_backdoors.flat -smp 1 -machine vmport=on # -initrd 
/tmp/tmp.QldMaGLdve
  qemu-system-x86_64: warning: host doesn't support requested feature: 
CPUID.8001H:ECX.svm [bit 2]
  enabling apic
  paging enabled
  cr0 = 80010011
  cr3 = 45b000
  cr4 = 20
  PASS: vmware_backdoors: rdpmc_test: HOST_TSC kernel
  PASS: vmware_backdoors: rdpmc_test: REAL_TIME kernel
  PASS: vmware_backdoors: rdpmc_test: APPARENT_TIME kernel
  FAIL: vmware_backdoors: rdpmc_test: HOST_TSC user
  FAIL: vmware_backdoors: rdpmc_test: REAL_TIME user
  FAIL: vmware_backdoors: rdpmc_test: APPARENT_TIME user
  PASS: vmware_backdoors: rdpmc_test: RANDOM PMC user
  FAIL: vmware_backdoors: port_test: CMD_GETVERSION user
  PASS: vmware_backdoors: port_test: CMD_GETVERSION kernel
  FAIL: vmware_backdoors: port_test: CMD_ILLEGAL user
  PASS: vmware_backdoors: port_test: RANDOM port user
  SUMMARY: 11 tests, 5 unexpected failures

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1821393/+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 1821271] Re: New Intel Wireless-AC 9260 [8086:2526] card not correctly probed in Ubuntu system

2019-03-22 Thread Seth Forshee
** Changed in: linux (Ubuntu Disco)
   Status: In Progress => Fix Committed

-- 
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/1821271

Title:
  New Intel Wireless-AC 9260 [8086:2526] card not correctly probed in
  Ubuntu system

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact] 
  New Intel Wireless-AC 9260 [8086:2526] card with subsystem id 4018 is not 
correctly probed without the corresponding id entry in kernel.

  [Fix]
  Upstream commit 3941310cf665 "iwlwifi: add new card for 9260 series".

  [Test Case]
  Verified on Intel 9260D2WL.

  [Regression Risk]
  Low. This patch effectively adds new id match for a unsupported (yet) device 
only.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1821271/+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 1821383] Status changed to Confirmed

2019-03-22 Thread Ubuntu Kernel Bot
This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821383

Title:
  synaptics touchpoint fails after resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To workaround bug #924648 I've installed the following:

  $ cat /etc/udev/rules.d/10-trackpoint.rules 
  ACTION=="add|change",
  SUBSYSTEM=="input",
  ATTR{name}=="TPPS/2 IBM TrackPoint",
  ATTR{device/sensitivity}="250",
  ATTR{device/speed}="250",

  While this works I now sometimes get a broken pointer after suspend.
  dmesg shows this at resume:

  [353671.884852] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
  [353672.381746] psmouse serio2: Failed to deactivate mouse on 
synaptics-pt/serio0
  [353672.845761] psmouse serio2: Failed to enable mouse on synaptics-pt/serio0

  After some time it resets and the pointer is back. Most of the time
  just this is shown:

  [353852.538962] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
  [353852.735990] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/serio2/input/input52

  But I did get a timeout call trace once:

  [ 5676.512616] psmouse serio2: Failed to enable mouse on synaptics-pt/serio0
  [ 5677.453153] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
  [ 5677.643970] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/serio2/input/input21
  [ 5800.035392] INFO: task kworker/0:2:9739 blocked for more than 120 seconds.
  [ 5800.035402]   Tainted: G   OE4.15.0-45-generic #48-Ubuntu
  [ 5800.035406] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [ 5800.035410] kworker/0:2 D0  9739  2 0x8000
  [ 5800.035424] Workqueue: events_long serio_handle_event
  [ 5800.035427] Call Trace:
  [ 5800.035439]  __schedule+0x291/0x8a0
  [ 5800.035445]  ? schedule_timeout+0x165/0x350
  [ 5800.035453]  schedule+0x2c/0x80
  [ 5800.035460]  __kernfs_remove.part.12+0x175/0x1f0
  [ 5800.035467]  ? wait_woken+0x80/0x80
  [ 5800.035474]  kernfs_remove_by_name_ns+0x54/0xa0
  [ 5800.035479]  remove_files.isra.1+0x35/0x70
  [ 5800.035484]  sysfs_remove_group+0x44/0x90
  [ 5800.035488]  sysfs_remove_groups+0x2e/0x50
  [ 5800.035493]  device_remove_groups+0x12/0x20
  [ 5800.035508]  trackpoint_disconnect+0x44/0x70 [psmouse]
  [ 5800.035517]  psmouse_disconnect+0xfe/0x190 [psmouse]
  [ 5800.035525]  serio_disconnect_driver+0x36/0x50
  [ 5800.035531]  serio_driver_remove+0x15/0x20
  [ 5800.035539]  device_release_driver_internal+0x15b/0x240
  [ 5800.035544]  device_release_driver+0x12/0x20
  [ 5800.035548]  serio_disconnect_port+0x98/0xb0
  [ 5800.035553]  serio_handle_event+0x18e/0x250
  [ 5800.035559]  process_one_work+0x1de/0x410
  [ 5800.035565]  worker_thread+0x32/0x410
  [ 5800.035572]  kthread+0x121/0x140
  [ 5800.035576]  ? process_one_work+0x410/0x410
  [ 5800.035582]  ? kthread_create_worker_on_cpu+0x70/0x70
  [ 5800.035589]  ? do_syscall_64+0x73/0x130
  [ 5800.035594]  ? SyS_exit+0x17/0x20
  [ 5800.035600]  ret_from_fork+0x35/0x40
  [ 5858.636930] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
  [ 5858.872453] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/serio2/input/input22

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pedrocr   26606 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Mar 22 18:20:56 2019
  InstallationDate: Installed on 2018-05-31 (295 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 004: ID 138a:0090 Validity Sensors, Inc. 
   Bus 001 Device 003: ID 5986:0706 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FAS5TS00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=0206141b-5758-4895-bbbd-8022b1e78519 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET66W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  

[Kernel-packages] [Bug 1821383] [NEW] synaptics touchpoint fails after resume

2019-03-22 Thread Pedro Côrte-Real
Public bug reported:

To workaround bug #924648 I've installed the following:

$ cat /etc/udev/rules.d/10-trackpoint.rules 
ACTION=="add|change",
SUBSYSTEM=="input",
ATTR{name}=="TPPS/2 IBM TrackPoint",
ATTR{device/sensitivity}="250",
ATTR{device/speed}="250",

While this works I now sometimes get a broken pointer after suspend.
dmesg shows this at resume:

[353671.884852] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
[353672.381746] psmouse serio2: Failed to deactivate mouse on 
synaptics-pt/serio0
[353672.845761] psmouse serio2: Failed to enable mouse on synaptics-pt/serio0

After some time it resets and the pointer is back. Most of the time just
this is shown:

[353852.538962] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
[353852.735990] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/serio2/input/input52

But I did get a timeout call trace once:

[ 5676.512616] psmouse serio2: Failed to enable mouse on synaptics-pt/serio0
[ 5677.453153] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
[ 5677.643970] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/serio2/input/input21
[ 5800.035392] INFO: task kworker/0:2:9739 blocked for more than 120 seconds.
[ 5800.035402]   Tainted: G   OE4.15.0-45-generic #48-Ubuntu
[ 5800.035406] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 5800.035410] kworker/0:2 D0  9739  2 0x8000
[ 5800.035424] Workqueue: events_long serio_handle_event
[ 5800.035427] Call Trace:
[ 5800.035439]  __schedule+0x291/0x8a0
[ 5800.035445]  ? schedule_timeout+0x165/0x350
[ 5800.035453]  schedule+0x2c/0x80
[ 5800.035460]  __kernfs_remove.part.12+0x175/0x1f0
[ 5800.035467]  ? wait_woken+0x80/0x80
[ 5800.035474]  kernfs_remove_by_name_ns+0x54/0xa0
[ 5800.035479]  remove_files.isra.1+0x35/0x70
[ 5800.035484]  sysfs_remove_group+0x44/0x90
[ 5800.035488]  sysfs_remove_groups+0x2e/0x50
[ 5800.035493]  device_remove_groups+0x12/0x20
[ 5800.035508]  trackpoint_disconnect+0x44/0x70 [psmouse]
[ 5800.035517]  psmouse_disconnect+0xfe/0x190 [psmouse]
[ 5800.035525]  serio_disconnect_driver+0x36/0x50
[ 5800.035531]  serio_driver_remove+0x15/0x20
[ 5800.035539]  device_release_driver_internal+0x15b/0x240
[ 5800.035544]  device_release_driver+0x12/0x20
[ 5800.035548]  serio_disconnect_port+0x98/0xb0
[ 5800.035553]  serio_handle_event+0x18e/0x250
[ 5800.035559]  process_one_work+0x1de/0x410
[ 5800.035565]  worker_thread+0x32/0x410
[ 5800.035572]  kthread+0x121/0x140
[ 5800.035576]  ? process_one_work+0x410/0x410
[ 5800.035582]  ? kthread_create_worker_on_cpu+0x70/0x70
[ 5800.035589]  ? do_syscall_64+0x73/0x130
[ 5800.035594]  ? SyS_exit+0x17/0x20
[ 5800.035600]  ret_from_fork+0x35/0x40
[ 5858.636930] psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
[ 5858.872453] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042/serio1/serio2/input/input22

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-45-generic 4.15.0-45.48
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pedrocr   26606 F pulseaudio
CurrentDesktop: GNOME
Date: Fri Mar 22 18:20:56 2019
InstallationDate: Installed on 2018-05-31 (295 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 004: ID 138a:0090 Validity Sensors, Inc. 
 Bus 001 Device 003: ID 5986:0706 Acer, Inc 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20FAS5TS00
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=0206141b-5758-4895-bbbd-8022b1e78519 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-45-generic N/A
 linux-backports-modules-4.15.0-45-generic  N/A
 linux-firmware 1.173.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/22/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1CET66W (1.34 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FAS5TS00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T460s
dmi.product.name: 20FAS5TS00
dmi.product.version: ThinkPad T460s
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a 

[Kernel-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp

2019-03-22 Thread Timo Aaltonen
please test on cosmic or disco

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => Incomplete

-- 
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/1817225

Title:
  18.04.2 breaks xrdp

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Incomplete
Status in xrdp package in Ubuntu:
  Confirmed

Bug description:
  I have observed the following on two different computers:

  On both computers, running Ubuntu 18.04, I am able to install xrdp and
  log in remotely using a third computer via Reminna or Windows RDP
  client without any problems.

  If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I
  update my working 18.04 installation by running

  sudo apt-get install --install-recommends linux-generic-hwe-18.04
  xserver-xorg-hwe-18.04

  then xrdp stops working. That is, when I login using an RDP client, I
  am presented with the xrdp login screen, but when I select xorg and
  try to login with my username and password, I see a blue screen for
  about a minute and then

  connecting to sesman ip 127.0.0.1
  sesman connect ok
  sending login info to session manager, please wait...
  login successful for display 10
  started connecting
  connection problem, giving up
  some problem

  The only difference between the working configuration and the broken
  one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above
  command).

  Out of the two computers I tried one has nvidia graphics and one has
  intel on-board graphics. For the nvidia computer, I tried both nvidia
  and nouveau drivers to no avail.

  Not sure if this is a problem with xrdp or xorg.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rushik 4016 F pulseaudio
   /dev/snd/controlC1:  rushik 4016 F pulseaudio
   /dev/snd/controlC0:  rushik 4016 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c
  InstallationDate: Installed on 2019-01-11 (41 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic 
root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0802
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX Z390-E GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: ASUS_MB_CNL
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+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 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

2019-03-22 Thread Brad Figg
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1819698
  phase: Packaging
  phase-changed: Friday, 22. March 2019 12:38 UTC
  reason:
prepare-package-meta: Pending -- package tag not yet published
-   promote-to-proposed: Ongoing -- builds not complete
+   promote-to-proposed: Pending -- source package tags missing

-- 
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/1819695

Title:
  linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1819698
  phase: Packaging
  phase-changed: Friday, 22. March 2019 12:38 UTC
  reason:
prepare-package-meta: Pending -- package tag not yet published
promote-to-proposed: Pending -- source package tags missing

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819695/+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 1789897] Re: snapcraft.yaml: skip non-existent firmware_install step

2019-03-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-raspi2 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1789897

Title:
  snapcraft.yaml: skip non-existent firmware_install step

Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Bionic:
  Fix Released

Bug description:
  [Impact]

  Linux kernel removed the 'firmware_install' step long ago (~4.13), so
  invoking it results in a broken kernel snap build:

  ...
  make -j4 CONFIG_PREFIX=/build/pc-kernel/parts/kernel/install modules_install 
INSTALL_MOD_PATH=/build/pc-kernel/parts/kernel/install dtbs_install 
INSTALL_DTBS_PATH=/build/pc-kernel/parts/kernel/install/dtbs firmware_install 
INSTALL_FW_PATH=/build/pc-kernel/parts/kernel/install/lib/firmware
  Failed to run 'make -j4 CONFIG_PREFIX=/build/pc-kernel/parts/kernel/install 
modules_install INSTALL_MOD_PATH=/build/pc-kernel/parts/kernel/install 
dtbs_install INSTALL_DTBS_PATH=/build/pc-kernel/parts/kernel/install/dtbs 
firmware_install 
INSTALL_FW_PATH=/build/pc-kernel/parts/kernel/install/lib/firmware' for 
'kernel': Exited with code 2.
  Verify that the part is using the correct parameters and try again.

  During the last snapcraft patch, i accidentally removed the directive
  to skip it.

  [Fix]

  Apply the attached patch

  [Test]

  Try to snap a kernel:

  $ snapcraft --target-arch=arm

  ...
  The version has been set to '4.15.0-1022.24'
  Snapping 'pi2-kernel' |   
   
  Snapped pi2-kernel_4.15.0-1022.24_armhf.snap

  [Regression]

  None, it actually fixes a regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1789897/+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 1818899] Re: [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login

2019-03-22 Thread Gerald
Hi, 
just an update, probably not related to the nvidia driver issue itself but 
perhaps useful for people that stumble upon this page for a similar problem. 

The startup hanging et ubuntu logo stopped without updating anything but
grub2 when i switched it to verbose mode.

method :

Edit /etc/default/grub and edit the following line:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

Change it to:
GRUB_CMDLINE_LINUX_DEFAULT="--verbose nosplash debug"

Then, run the following command in a terminal
sudo update-grub2


Regards

-- 
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/1818899

Title:
  [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer
  freezes after login

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  I can boot to login, but if I input correct information it freezes. If
  I boot in recovery mode and choose to resume boot, I can login. But my
  external display doesn't register. If I choose the failsafeX version
  there is an error text related to xorg.

  I have not had any problems before on this terminal. It came when I
  let the system update and reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 20:26:56 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:119b]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1197]
  InstallationDate: Installed on 2018-11-26 (100 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. 
   Bus 001 Device 004: ID 04f3:0c03 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A715-71G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=06e8310e-d1a9-42d8-a804-841358355e74 ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/22/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmeleon_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd08/22/2017:svnAcer:pnAspireA715-71G:pvrV1.10:rvnKBL:rnCharmeleon_KLS:rvrV1.10:cvnAcer:ct10:cvrV1.10:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-71G
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Wed Mar  6 20:16:01 2019
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  

[Kernel-packages] [Bug 1821378] [NEW] [linux-azure] Include mainline commits fc96df16a1ce and ba50bf1ce9a5 in Azure kernel

2019-03-22 Thread Joseph Salisbury
Public bug reported:

This is a request to include the following two commits in 16.04 and
18.04 linux-azure:

fc96df16a1ce ("Drivers: hv: vmbus: Return -EINVAL for the sys files for 
unopened channels")
ba50bf1ce9a5 ("Drivers: hv: vmbus: Check for ring when getting debug info")

Both commits are fixes to prior commits and have been cc'd to upstream
stable.

Commit fc96df16a1ce is in mainline as of v4.20
Commit ba50bf1ce9a5 is in mainline as of v5.0-rc4

The problem these commits fix is that some of the code for displaying
values for entries in /sys/bus/vmbus don't have appropriate locking to
prevent reading an entry while it is being created or being freed.   The
result is accessing a bogus memory address.

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: kernel-hyper-v

** Tags added: kernel-hyper-v

-- 
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/1821378

Title:
  [linux-azure] Include mainline commits fc96df16a1ce and ba50bf1ce9a5
  in Azure kernel

Status in linux-azure package in Ubuntu:
  New

Bug description:
  This is a request to include the following two commits in 16.04 and
  18.04 linux-azure:

  fc96df16a1ce ("Drivers: hv: vmbus: Return -EINVAL for the sys files for 
unopened channels")
  ba50bf1ce9a5 ("Drivers: hv: vmbus: Check for ring when getting debug info")

  Both commits are fixes to prior commits and have been cc'd to upstream
  stable.

  Commit fc96df16a1ce is in mainline as of v4.20
  Commit ba50bf1ce9a5 is in mainline as of v5.0-rc4

  The problem these commits fix is that some of the code for displaying
  values for entries in /sys/bus/vmbus don't have appropriate locking to
  prevent reading an entry while it is being created or being freed.
  The result is accessing a bogus memory address.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1821378/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


Re: [Kernel-packages] [Bug 1802283] Re: system freezes

2019-03-22 Thread jnns
Okay. Thanks for looking into it. Feel free to close the issue, please.

Kai-Heng Feng  schrieb am Fr., 22. März 2019,
16:55:

> I think it's different. Seems to be a gnome-shell issue according to the
> very limited log.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1802283
>
> Title:
>   system freezes
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   My system freezes once every second day or so.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.10
>   Package: linux-image-4.18.0-10-generic 4.18.0-10.11
>   ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
>   Uname: Linux 4.18.0-10-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu13
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  jnns   2519 F pulseaudio
>/dev/snd/controlC0:  jnns   2519 F pulseaudio
>   CurrentDesktop: GNOME
>   Date: Thu Nov  8 12:07:32 2018
>   HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327
>   InstallationDate: Installed on 2018-08-05 (95 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   MachineType: LENOVO 20KGS5DU00
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=de_DE.UTF-8
>SHELL=/usr/bin/fish
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic
> root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep
> vt.handoff=1
>   RelatedPackageVersions:
>linux-restricted-modules-4.18.0-10-generic N/A
>linux-backports-modules-4.18.0-10-generic  N/A
>linux-firmware 1.175
>   SourcePackage: linux
>   UpgradeStatus: Upgraded to cosmic on 2018-10-10 (29 days ago)
>   dmi.bios.date: 09/17/2018
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: N23ET56W (1.31 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 20KGS5DU00
>   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: None
>   dmi.modalias:
> dmi:bvnLENOVO:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
>   dmi.product.family: ThinkPad X1 Carbon 6th
>   dmi.product.name: 20KGS5DU00
>   dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
>   dmi.product.version: ThinkPad X1 Carbon 6th
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283/+subscriptions
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802283

Title:
  system freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My system freezes once every second day or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jnns   2519 F pulseaudio
   /dev/snd/controlC0:  jnns   2519 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Nov  8 12:07:32 2018
  HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327
  InstallationDate: Installed on 2018-08-05 (95 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KGS5DU00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-10 (29 days ago)
  dmi.bios.date: 09/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGS5DU00
  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: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGS5DU00
  dmi.product.sku: 

[Kernel-packages] [Bug 1820948] Re: i40e xps management broken when > 64 queues/cpus

2019-03-22 Thread Nivedita Singhvi
Will be submitting SRU request early next week; trying to get
it into this next kernel release cycle. 

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Nivedita Singhvi (niveditasinghvi)

** Changed in: linux (Ubuntu Bionic)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1820948

Title:
  i40e xps management broken when > 64 queues/cpus

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  [Impact]
  Transmit packet steering (xps) settings don't work when
  the number of queues (cpus) is higher than 64. This is
  currently still an issue on the 4.15 kernel (Xenial -hwe
  and Bionic kernels). 

  It was fixed in Intel's i40e driver version 2.7.11 and
  in 4.16-rc1 mainline Linux (i.e. Cosmic, Disco have fix).

  Fix
  -
  The following commit fixes this issue (as identified
  by Lihong Yang in discussion with Intel i40e team):

  "i40e: Fix the number of queues available to be mapped for use"
  Commit: bc6d33c8d93f520e97a8c6330b8910053d4f

  
  [Test Case]
  1. Kernel version: Bionic/Xenial -hwe: any 4.15 kernel
 i40e driver version: 2.1.14-k 
 Any system with > 64 CPUs

  2. For any queue 0 - 63, you can read/set tx xps:
 
  echo  > /sys/class/net/eth2/queues/tx-63/xps_cpus
  echo $?
  0
  cat /sys/class/net/eth2/queues/tx-63/xps_cpus
  00,, 

But for any queue number > 63, we see this error:

  echo  > /sys/class/net/eth2/queues/tx-64/xps_cpus
  echo: write error: Invalid argument

  cat /sys/class/net/eth2/queues/tx-64/xps_cpus
  cat: /sys/class/net/eth2/queues/tx-64/xps_cpus: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820948/+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 1820275] Re: btrfs-kernel oops from btrfs subvolume delete command

2019-03-22 Thread Andrea Righi
According to the trace reported in syslog the problem happened in
btrfs_get_or_create_delayed_node(), specifically the faulty function was
prefetch_freepointer() defined in mm/slub.c.

Considering that btrfs_get_or_create_delayed_node() is allocating a
"node" object using kmem_cache_zalloc() from a local kmem_cache pool
called "delayed_node_cache", I would say that most likely that pool was
corrupted due to a bug in btrfs (because only btrfs is using that pool).

If I understand correctly this problem can be reproduced fairly easily
(it's happening every few days running a specific test suite). It would
be interesting to understand if it is a regression or not. Do you know
if the problem started to happen recently from a specific kernel
version? Have you tried to run the same test suite on an older kernel?
Ideally if we can find a "good" kernel and a "bad" kernel we could try
to bisect the problem.

-- 
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/1820275

Title:
  btrfs-kernel oops from btrfs subvolume delete command

Status in Ubuntu on IBM z Systems:
  Triaged
Status in linux package in Ubuntu:
  New

Bug description:
  This report show a kernel oops in the btrfs lugin , happened every few
  days when running a test suite on a test system. It looks like their
  systemd/Journal failed to kick off a dump immediately following the
  panic.

  The exploiter is using the kernel 4.15.0-42

  We're not sure it's the btrfs subvolume delete that's causing it yet

  Following infos are attached: - syslog - sosreport - kdump output here
  : https://ibm.ent.box.com/folder/70219521934

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1820275/+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 1820326] Re: linux-fips: 4.4.0-1007.8 -proposed tracker

2019-03-22 Thread Brad Figg
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1819660
- phase: Ready for Promote to Proposed
- phase-changed: Friday, 22. March 2019 15:39 UTC
+ phase: Promote to Proposed
+ phase-changed: Friday, 22. March 2019 16:11 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Ongoing -- review 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/1820326

Title:
  linux-fips: 4.4.0-1007.8 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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:
  In Progress
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1819660
  phase: Promote to Proposed
  phase-changed: Friday, 22. March 2019 16:11 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820326/+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 1814095] Re: bnxt_en_po: TX timed out triggering Netdev Watchdog Timer

2019-03-22 Thread Nivedita Singhvi
Just briefly wanted to say that this is one we've discussed at 
length -- we may not be able to get someone who has the right
NIC to test with it in time. 

I'm sanity checking the kernel, but that is not exercising the 
key change here. 

If we could assume verification-done for our purposes here, 
that might be needed.

-- 
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/1814095

Title:
  bnxt_en_po: TX timed out triggering Netdev Watchdog Timer

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  The bnxt_en_bpo driver experienced tx timeouts causing the system to
  experience network stalls and fail to send data and heartbeat packets.

  The following 25Gb Broadcom NIC error was seen on Xenial
  running the 4.4.0-141-generic kernel on an amd64 host
  seeing moderate-heavy network traffic (just once):

  * The bnxt_en_po driver froze on a "TX timed out" error
    and triggered the Netdev Watchdog timer under load.

  * From kernel log:
    "NETDEV WATCHDOG: eno2d1 (bnxt_en_bpo): transmit queue 0 timed out"
    See attached kern.log excerpt file for full excerpt of error log.

  * Release = Xenial
    Kernel = 4.4.0-141-generic #167
    eno2d1 = Product Name: Broadcom Adv. Dual 25Gb Ethernet

  * This caused the driver to reset in order to recover:

    "bnxt_en_bpo :19:00.1 eno2d1: TX timeout detected, starting
  reset task!"

    driver: bnxt_en_bpo
    version: 1.8.1
    source: ubuntu/bnxt/bnxt.c: bnxt_tx_timeout()

  * The loss of connectivity and softirq stall caused other failures
    on the system.

  * The bnxt_en_po driver is the imported Broadcom driver
    pulled in to support newer Broadcom HW (specific boards)
    while the bnx_en module continues to support the older
    HW. The current Linux upstream driver does not compile
    easily with the 4.4 kernel (too many changes).

  * This upstream and bnxt_en driver fix is a likely solution:
     "bnxt_en: Fix TX timeout during netpoll"
     commit: 73f21c653f930f438d53eed29b5e4c65c8a0f906

    This fix has not been applied to the bnxt_en_po driver
    version, but review of the code indicates that it is
    susceptible to the bug, and the fix would be reasonable.

  [Test Case]

  * Unfortunately, this is not easy to reproduce. Also, it is only seen
  on 4.4 kernels with newer Broadcom NICs supported by the bnxt_en_bpo
  driver.

  [Regression Potential]

  * The patch is restricted to the bpo driver, with very constrained
  scope - just the newest Broadcom NICs being used by the Xenial 4.4
  kernel (as opposed to the hwe 4.15 etc. kernels, which would have the
  in-tree fixed driver).

  * The patch is very small and backport is fairly minimal and simple.

  * The fix has been running on the in-tree driver in upstream mainline
  as well as the Ubuntu Linux in-tree driver, although the Broadcom
  driver has a lot of lower level code that is different, this piece is
  still the same.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814095/+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 1802283] Re: system freezes

2019-03-22 Thread Kai-Heng Feng
I think it's different. Seems to be a gnome-shell issue according to the
very limited log.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1802283

Title:
  system freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My system freezes once every second day or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jnns   2519 F pulseaudio
   /dev/snd/controlC0:  jnns   2519 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Nov  8 12:07:32 2018
  HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327
  InstallationDate: Installed on 2018-08-05 (95 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KGS5DU00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-10 (29 days ago)
  dmi.bios.date: 09/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGS5DU00
  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: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGS5DU00
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283/+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 1820326] Re: linux-fips: 4.4.0-1007.8 -proposed tracker

2019-03-22 Thread Andy Whitcroft
** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => 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/1820326

Title:
  linux-fips: 4.4.0-1007.8 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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:
  In Progress
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1819660
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 22. March 2019 15:39 UTC
  reason:
promote-to-proposed: Pending -- ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820326/+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 1820326] Re: linux-fips: 4.4.0-1007.8 -proposed tracker

2019-03-22 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1819660
- phase: Packaging
- phase-changed: Wednesday, 20. March 2019 23:00 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Friday, 22. March 2019 15:39 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Pending -- ready for review

-- 
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/1820326

Title:
  linux-fips: 4.4.0-1007.8 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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:
  Confirmed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1819660
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 22. March 2019 15:39 UTC
  reason:
promote-to-proposed: Pending -- ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820326/+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 1757445] Re: Suspend does not always resume

2019-03-22 Thread Gary Kenneth Krueger
Err, the issue sounds a lot like Bug #1743094.  Maybe one should be
marked as a duplicate of the other.

-- 
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/1757445

Title:
  Suspend does not always resume

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Dell XPS 13 9350 on AC power left running overnight, suspends after a
  given timeout. When coming back the next morning sometimes the laptop
  resumes to an aubergine desktop (just the screen, no GDM) and cursor
  and sits there forever. Sometimes it resumes to a black screen and
  cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 14:15:04 2018
  InstallationDate: Installed on 2018-02-13 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=bc5b647b-38ca-4206-9e96-774a5ac6b833 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/18/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.family: NULL
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757445/+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 1757445] Re: Suspend does not always resume

2019-03-22 Thread Gary Kenneth Krueger
This issue sounds a lot like Bug #1757445.  Maybe one should be marked
as a duplicate of the other.

-- 
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/1757445

Title:
  Suspend does not always resume

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Dell XPS 13 9350 on AC power left running overnight, suspends after a
  given timeout. When coming back the next morning sometimes the laptop
  resumes to an aubergine desktop (just the screen, no GDM) and cursor
  and sits there forever. Sometimes it resumes to a black screen and
  cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 14:15:04 2018
  InstallationDate: Installed on 2018-02-13 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=bc5b647b-38ca-4206-9e96-774a5ac6b833 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/18/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.family: NULL
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757445/+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 1757445] Re: Suspend does not always resume

2019-03-22 Thread Gary Kenneth Krueger
I forgot to mention that before demonstrating that "Night Light" and
"Dim screen when inactive", I upgraded to the latest BIOS from Lenovo on
20 March (a day prior to posting #16 and before turning off the dimming
features).  It is the Lenovo 85UJ25US (1.46) BIOS, which is an upgrade
from 8BET55WW (1.35).  It was upgraded in hopes that it would resolve
the problem.

Right after the upgrade (and before turning off the dimming features), I
also turned off Security->Virtualization and Security->VT-d.  I don't
have a need for virtualization, and it was mentioned in posts elsewhere
that it may contribute to the hang on suspend 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/1757445

Title:
  Suspend does not always resume

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Dell XPS 13 9350 on AC power left running overnight, suspends after a
  given timeout. When coming back the next morning sometimes the laptop
  resumes to an aubergine desktop (just the screen, no GDM) and cursor
  and sits there forever. Sometimes it resumes to a black screen and
  cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 14:15:04 2018
  InstallationDate: Installed on 2018-02-13 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=bc5b647b-38ca-4206-9e96-774a5ac6b833 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/18/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.family: NULL
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757445/+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 1757445] Re: Suspend does not always resume

2019-03-22 Thread Gary Kenneth Krueger
By the way, this issue appeared on my machine, which is a Lenovo W520.

I have turned off automatic suspend while plugged in.  I need it to run
financial calculations overnight.  And, I have increased the battery
power delay to 30m.  Though that is neither here nor there.

With "Night Light" and "Dim screen when inactive" turned off, blanking
the screen works every time.  Suspending and restoring works every time.

I really want to get back to the "Night Light" feature, so I would like
to see the bug resolved.

-- 
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/1757445

Title:
  Suspend does not always resume

Status in linux package in Ubuntu:
  Confirmed
Status in linux-meta-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Dell XPS 13 9350 on AC power left running overnight, suspends after a
  given timeout. When coming back the next morning sometimes the laptop
  resumes to an aubergine desktop (just the screen, no GDM) and cursor
  and sits there forever. Sometimes it resumes to a black screen and
  cursor.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 21 14:15:04 2018
  InstallationDate: Installed on 2018-02-13 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=bc5b647b-38ca-4206-9e96-774a5ac6b833 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 07TYC2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/18/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.family: NULL
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757445/+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 1819759] Re: linux: 5.0.0-8.9 -proposed tracker

2019-03-22 Thread Brad Figg
** 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 1820315 (linux-hwe-edge)
  derivatives: bug 1820878 (linux-aws), bug 1820605 (linux-azure), bug 1820308 
(linux-raspi2), bug 1820310 (linux-gcp), bug 1820311 (linux-kvm)
  
  -- swm properties --
  phase: Ready for Release
  phase-changed: Thursday, 21. March 2019 16:59 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-release: Pending -- ready to copy
+   promote-to-release: Pending -- ready to copy

-- 
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/1819759

Title:
  linux: 5.0.0-8.9 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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-release series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  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 1820315 (linux-hwe-edge)
  derivatives: bug 1820878 (linux-aws), bug 1820605 (linux-azure), bug 1820308 
(linux-raspi2), bug 1820310 (linux-gcp), bug 1820311 (linux-kvm)

  -- swm properties --
  phase: Ready for Release
  phase-changed: Thursday, 21. March 2019 16:59 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Pending -- ready to copy

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819759/+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 1819759] Re: linux: 5.0.0-8.9 -proposed tracker

2019-03-22 Thread Stefan Bader
** 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 1820315 (linux-hwe-edge)
+ derivatives: bug 1820878 (linux-aws), bug 1820605 (linux-azure), bug 1820308 
(linux-raspi2), bug 1820310 (linux-gcp), bug 1820311 (linux-kvm)
+ 
  -- swm properties --
- backports: null
- derivatives: bug 1820878 (linux-aws)
  phase: Ready for Release
  phase-changed: Thursday, 21. March 2019 16:59 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-release: Pending -- ready to copy
+   promote-to-release: Pending -- ready to copy

-- 
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/1819759

Title:
  linux: 5.0.0-8.9 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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-release series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  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 1820315 (linux-hwe-edge)
  derivatives: bug 1820878 (linux-aws), bug 1820605 (linux-azure), bug 1820308 
(linux-raspi2), bug 1820310 (linux-gcp), bug 1820311 (linux-kvm)

  -- swm properties --
  phase: Ready for Release
  phase-changed: Thursday, 21. March 2019 16:59 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
    promote-to-release: Pending -- ready to copy

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819759/+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 1821350] Re: Lenovo X1: failing to resume from suspend after closing the lid

2019-03-22 Thread Matthias Klose
but apparently still an issue with the nouveau driver

-- 
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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Triaged

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1820409] Re: Audio stutter after update

2019-03-22 Thread Johnny Izzo
I would'nt say it happens, i'd say its always there constantly.

** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820409/+attachment/5248540/+files/dmesg.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/1820409

Title:
  Audio stutter after update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After some update:
  Audio stutters in VLC
  Video and audio stutters in Youtube

  I think cpu usage might be bigger in VLC too, over 20% vs. below 20%
  earlier (one thread gets full 100%?)

  Stuttering kernel at the moment is 4.15.0-46-generic.

  Kernel version 4.15.0-43-generic definitely worked good.
  Cant remember if i could get slight stutter from previous version version -45.

  
  Tried also lowlatency and 4.18 kernel, bad stuttering in those.

  (Distro is Lubuntu)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-46-generic.
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: PCH [HDA Intel PCH], device 0: CX20751/2 Analog [CX20751/2 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  meie855 F pulseaudio
   /dev/snd/controlC1:  meie855 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'HDMI'/'HDA Intel HDMI at 0xf711c000 irq 50'
 Mixer name : 'Intel Broadwell HDMI'
 Components : 'HDA:80862808,80860101,0010'
 Controls  : 35
 Simple ctrls  : 5
  Card1.Amixer.info:
   Card hw:1 'PCH'/'HDA Intel PCH at 0xf7118000 irq 47'
 Mixer name : 'Conexant CX20751/2'
 Components : 'HDA:14f1510f,1043181d,00100100'
 Controls  : 20
 Simple ctrls  : 9
  CurrentDesktop: LXDE
  Date: Sat Mar 16 18:02:18 2019
  InstallationDate: Installed on 2018-07-04 (255 days ago)
  InstallationMedia: Lubuntu 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 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305FA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=a032fe2a-8284-47a9-a0d1-cfa1f01a5812 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305FA.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305FA.210:bd05/19/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820409/+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 1821350] Re: Lenovo X1: failing to resume from suspend after closing the lid

2019-03-22 Thread Anthony Wong
Worked with doko on IRC and the nvidia 418 driver (currently in
-proposed) fixes this.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Triaged

-- 
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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Triaged

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

2019-03-22 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1819698
  phase: Packaging
  phase-changed: Friday, 22. March 2019 12:38 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package tag not yet published
+   promote-to-proposed: Ongoing -- builds not complete

-- 
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/1819695

Title:
  linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1819698
  phase: Packaging
  phase-changed: Friday, 22. March 2019 12:38 UTC
  reason:
prepare-package-meta: Pending -- package tag not yet published
promote-to-proposed: Ongoing -- builds not complete

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819695/+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 1819658] Re: linux-aws: 4.4.0-1040.43 -proposed tracker

2019-03-22 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-trusty

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  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: 1819660
- phase: Holding before Promote to Proposed
- phase-changed: Friday, 22. March 2019 12:43 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Friday, 22. March 2019 13:33 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete
+   promote-to-proposed: Pending -- ready for review

-- 
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/1819658

Title:
  linux-aws: 4.4.0-1040.43 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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:
  Confirmed
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  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: 1819660
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 22. March 2019 13:33 UTC
  reason:
promote-to-proposed: Pending -- ready for review

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819658/+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 1821350] CurrentDmesg.txt

2019-03-22 Thread Matthias Klose
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1821350/+attachment/5248505/+files/CurrentDmesg.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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1821350] ProcInterrupts.txt

2019-03-22 Thread Matthias Klose
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1821350/+attachment/5248512/+files/ProcInterrupts.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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1821350] ProcModules.txt

2019-03-22 Thread Matthias Klose
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1821350/+attachment/5248513/+files/ProcModules.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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1821350] Lspci.txt

2019-03-22 Thread Matthias Klose
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1821350/+attachment/5248507/+files/Lspci.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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1821350] UdevDb.txt

2019-03-22 Thread Matthias Klose
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1821350/+attachment/5248516/+files/UdevDb.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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1821350] PulseList.txt

2019-03-22 Thread Matthias Klose
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1821350/+attachment/5248514/+files/PulseList.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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1821350] ProcEnviron.txt

2019-03-22 Thread Matthias Klose
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1821350/+attachment/5248511/+files/ProcEnviron.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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1821350] Re: Lenovo X1: failing to resume from suspend after closing the lid

2019-03-22 Thread Matthias Klose
** Attachment added: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+attachment/5248518/+files/kern.log

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1821350] ProcCpuinfoMinimal.txt

2019-03-22 Thread Matthias Klose
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1821350/+attachment/5248510/+files/ProcCpuinfoMinimal.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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1821350] IwConfig.txt

2019-03-22 Thread Matthias Klose
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1821350/+attachment/5248506/+files/IwConfig.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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1821350] WifiSyslog.txt

2019-03-22 Thread Matthias Klose
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1821350/+attachment/5248517/+files/WifiSyslog.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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1821350] CRDA.txt

2019-03-22 Thread Matthias Klose
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1821350/+attachment/5248504/+files/CRDA.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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1821350] Lsusb.txt

2019-03-22 Thread Matthias Klose
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1821350/+attachment/5248508/+files/Lsusb.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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1821350] RfKill.txt

2019-03-22 Thread Matthias Klose
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1821350/+attachment/5248515/+files/RfKill.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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1821350] ProcCpuinfo.txt

2019-03-22 Thread Matthias Klose
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1821350/+attachment/5248509/+files/ProcCpuinfo.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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1821350] Re: Lenovo X1: failing to resume from suspend after closing the lid

2019-03-22 Thread Matthias Klose
apport information

** Tags added: apport-collected disco

** Description changed:

- On a Lenovo X1, running current disco, the machine fails to resume from
- suspend after closing the lid.  After closing the LID, you see the LED
- slowly flashing, and when again opening the lid, it changes to constant
- bright light. Nothing else happens.
+ On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu23
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  doko   2011 F pulseaudio
+  /dev/snd/controlC0:  doko   2011 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 19.04
+ InstallationDate: Installed on 2019-01-12 (68 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
+ MachineType: LENOVO 20MFCTO1WW
+ Package: linux (not installed)
+ ProcFB: 0 nouveaufb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
+ RelatedPackageVersions:
+  linux-restricted-modules-5.0.0-7-generic N/A
+  linux-backports-modules-5.0.0-7-generic  N/A
+  linux-firmware   1.178
+ Tags:  disco
+ Uname: Linux 5.0.0-7-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
+ _MarkForUpload: True
+ dmi.bios.date: 01/08/2019
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N2EET36W (1.18 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20MFCTO1WW
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40697 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
+ dmi.product.family: ThinkPad X1 Extreme
+ dmi.product.name: 20MFCTO1WW
+ dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
+ dmi.product.version: ThinkPad X1 Extreme
+ dmi.sys.vendor: LENOVO

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1821350/+attachment/5248503/+files/AlsaInfo.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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1821350] Missing required logs.

2019-03-22 Thread Ubuntu Kernel Bot
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1821350

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1821350] [NEW] Lenovo X1: failing to resume from suspend after closing the lid

2019-03-22 Thread Matthias Klose
Public bug reported:

On a Lenovo X1, running current disco, the machine fails to resume from suspend 
after closing the lid.  After closing the LID, you see the LED slowly flashing, 
and when again opening the lid, it changes to constant bright light. Nothing 
else happens.
--- 
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  doko   2011 F pulseaudio
 /dev/snd/controlC0:  doko   2011 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2019-01-12 (68 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: LENOVO 20MFCTO1WW
Package: linux (not installed)
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-7-generic N/A
 linux-backports-modules-5.0.0-7-generic  N/A
 linux-firmware   1.178
Tags:  disco
Uname: Linux 5.0.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
_MarkForUpload: True
dmi.bios.date: 01/08/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: N2EET36W (1.18 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20MFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Extreme
dmi.product.name: 20MFCTO1WW
dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
dmi.product.version: ThinkPad X1 Extreme
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: apport-collected disco

-- 
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/1821350

Title:
  Lenovo X1: failing to resume from suspend after closing the lid

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a Lenovo X1, running current disco, the machine fails to resume from 
suspend after closing the lid.  After closing the LID, you see the LED slowly 
flashing, and when again opening the lid, it changes to constant bright light. 
Nothing else happens.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  doko   2011 F pulseaudio
   /dev/snd/controlC0:  doko   2011 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-01-12 (68 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: LENOVO 20MFCTO1WW
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-7-generic N/A
   linux-backports-modules-5.0.0-7-generic  N/A
   linux-firmware   1.178
  Tags:  disco
  Uname: Linux 5.0.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 01/08/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2EET36W (1.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20MFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2EET36W(1.18):bd01/08/2019:svnLENOVO:pn20MFCTO1WW:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme
  dmi.product.name: 20MFCTO1WW
  dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme
  dmi.product.version: ThinkPad X1 Extreme
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821350/+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 1820311] Re: linux-kvm: 5.0.0-1001.1 -proposed tracker

2019-03-22 Thread Brad Figg
** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/promote-to-release
   Status: New => Confirmed

** Tags removed: block-proposed-disco

** Tags removed: block-proposed

** 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 --
  kernel-master-bug: 1819759
- phase: Ready for Testing
- phase-changed: Friday, 15. March 2019 20:31 UTC
+ phase: Ready for Release
+ phase-changed: Friday, 22. March 2019 13:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
+   promote-to-release: Pending -- ready to copy

-- 
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/1820311

Title:
  linux-kvm: 5.0.0-1001.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 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-release series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Disco:
  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 --
  kernel-master-bug: 1819759
  phase: Ready for Release
  phase-changed: Friday, 22. March 2019 13:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Pending -- ready to copy

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820311/+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 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found

2019-03-22 Thread Guillaume Penin
Hi,

We are also affected by this bug.

Adding linux-meta in the loop because a simple solution could be to now
add a tighter dependency on the linux-image-4.4.0-*-generic package,
that means linux-base (>= 4.5ubuntu1~16.04.1).

** Changed in: linux-meta (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1820755

Title:
  Netboot install fails due to linux-image-4.4.0-143-generic.postinst
  linux-update-symlinks not found

Status in Blue Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-base package in Ubuntu:
  Confirmed

Bug description:
  Using a netboot install of Ubuntu 16.04 LTS server, the install fails
  when configuring the kernel.  The failure will not let you move on.

  This seems to have happened after the release of 
  
https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html

  The error logs 
  Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic 
(4.4.0-143.169) ...
  Mar 18 17:09:50 in-target: ^M
  Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic 
(4.4.0-143.169) ...
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: 
/var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: 
/var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 
  Mar 18 17:09:51 in-target: linux-update-symlinks: not found
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: dpkg: error processing package 
linux-image-4.4.0-143-generic (--configure):
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:  subprocess installed post-installation script 
returned error exit status 127
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of 
linux-modules-extra-4.4.0-143-generic:
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:  linux-modules-extra-4.4.0-143-generic depends on 
linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however:
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:   Package linux-image-4.4.0-143-generic is not 
configured yet.
  Mar 18 17:09:51 in-target: ^M
  Mar

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluelinux/+bug/1820755/+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 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found

2019-03-22 Thread Ubuntu Kernel Bot
** Package changed: linux-meta (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-base in Ubuntu.
https://bugs.launchpad.net/bugs/1820755

Title:
  Netboot install fails due to linux-image-4.4.0-143-generic.postinst
  linux-update-symlinks not found

Status in Blue Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-base package in Ubuntu:
  Confirmed

Bug description:
  Using a netboot install of Ubuntu 16.04 LTS server, the install fails
  when configuring the kernel.  The failure will not let you move on.

  This seems to have happened after the release of 
  
https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html

  The error logs 
  Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic 
(4.4.0-143.169) ...
  Mar 18 17:09:50 in-target: ^M
  Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic 
(4.4.0-143.169) ...
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: 
/var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: 
/var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 
  Mar 18 17:09:51 in-target: linux-update-symlinks: not found
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: dpkg: error processing package 
linux-image-4.4.0-143-generic (--configure):
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:  subprocess installed post-installation script 
returned error exit status 127
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of 
linux-modules-extra-4.4.0-143-generic:
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:  linux-modules-extra-4.4.0-143-generic depends on 
linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however:
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:   Package linux-image-4.4.0-143-generic is not 
configured yet.
  Mar 18 17:09:51 in-target: ^M
  Mar

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluelinux/+bug/1820755/+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 1821345] Status changed to Confirmed

2019-03-22 Thread Ubuntu Kernel Bot
This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821345

Title:
  Mellanox MT27800 / mlx5_core : cannot bring up VFs if the total number
  of VFs is >= 64 : alloc irq vectors failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  For the Mellanox NIC MT27800 (MCX556M-ECAT-S25 to be precise), the
  maximum number of VF per PF can be configured in the firmware, by
  running e.g. :

  $ sudo mstconfig -d 32:00.1 set NUM_OF_VFS=127

  If I set this NUM_OF_VFS to 64 or more, the creation of even a single
  VF fails mid-way :

  $ echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs
  1

  dmesg shows :

  [101418.090970] (:32:00.0): E-Switch: E-Switch enable SRIOV: nvfs(1) mode 
(1)
  [101418.182736] (:32:00.0): E-Switch: SRIOV enabled: active vports(2)
  [101418.289642] pci :32:00.2: [15b3:1018] type 00 class 0x02
  [101418.290235] pci :32:00.2: Max Payload Size set to 512 (was 128, max 
512)
  [101418.290261] pci :32:00.2: enabling Extended Tags
  [101418.292432] iommu: Adding device :32:00.2 to group 139
  [101418.292580] iommu: Using direct mapping for device :32:00.2
  [101418.292979] mlx5_core :32:00.2: enabling device ( -> 0002)
  [101418.293719] mlx5_core :32:00.2: firmware version: 16.24.1000
  [101418.550589] mlx5_core :32:00.2: alloc irq vectors failed
  [101418.974082] mlx5_core :32:00.2: mlx5_load_one failed with error code 
-28
  [101418.981656] mlx5_core: probe of :32:00.2 failed with error -28

  This is a problem with both the Ubuntu kernel driver and the OFED
  driver.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 08:33 seq
   crw-rw 1 root audio 116, 33 Mar 21 08:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Mar 22 12:43:26 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Supermicro AS -2023US-TR4
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=52d72a05-517b-4c16-8dcb-486bdebcc695 ro console=ttyS1,115200 nosplash 
iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.1c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H11DSU-iN
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.02A
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: AS -2023US-TR4
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821345/+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 1821345] Re: Mellanox MT27800 / mlx5_core : cannot bring up VFs if the total number of VFs is >= 64 : alloc irq vectors failed

2019-03-22 Thread Junien Fridrick
Note : if NUM_OF_VFS is set to 32, VF creation works fine. If it's set
to 64 or above, VF creation fails. I haven't tested in between.

-- 
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/1821345

Title:
  Mellanox MT27800 / mlx5_core : cannot bring up VFs if the total number
  of VFs is >= 64 : alloc irq vectors failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  For the Mellanox NIC MT27800 (MCX556M-ECAT-S25 to be precise), the
  maximum number of VF per PF can be configured in the firmware, by
  running e.g. :

  $ sudo mstconfig -d 32:00.1 set NUM_OF_VFS=127

  If I set this NUM_OF_VFS to 64 or more, the creation of even a single
  VF fails mid-way :

  $ echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs
  1

  dmesg shows :

  [101418.090970] (:32:00.0): E-Switch: E-Switch enable SRIOV: nvfs(1) mode 
(1)
  [101418.182736] (:32:00.0): E-Switch: SRIOV enabled: active vports(2)
  [101418.289642] pci :32:00.2: [15b3:1018] type 00 class 0x02
  [101418.290235] pci :32:00.2: Max Payload Size set to 512 (was 128, max 
512)
  [101418.290261] pci :32:00.2: enabling Extended Tags
  [101418.292432] iommu: Adding device :32:00.2 to group 139
  [101418.292580] iommu: Using direct mapping for device :32:00.2
  [101418.292979] mlx5_core :32:00.2: enabling device ( -> 0002)
  [101418.293719] mlx5_core :32:00.2: firmware version: 16.24.1000
  [101418.550589] mlx5_core :32:00.2: alloc irq vectors failed
  [101418.974082] mlx5_core :32:00.2: mlx5_load_one failed with error code 
-28
  [101418.981656] mlx5_core: probe of :32:00.2 failed with error -28

  This is a problem with both the Ubuntu kernel driver and the OFED
  driver.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-46-generic 4.15.0-46.49
  ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 21 08:33 seq
   crw-rw 1 root audio 116, 33 Mar 21 08:33 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Mar 22 12:43:26 2019
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Supermicro AS -2023US-TR4
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=52d72a05-517b-4c16-8dcb-486bdebcc695 ro console=ttyS1,115200 nosplash 
iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-46-generic N/A
   linux-backports-modules-4.15.0-46-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.1c
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H11DSU-iN
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.02A
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 1
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: AS -2023US-TR4
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821345/+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 1821345] [NEW] Mellanox MT27800 / mlx5_core : cannot bring up VFs if the total number of VFs is >= 64 : alloc irq vectors failed

2019-03-22 Thread Junien Fridrick
Public bug reported:

Hi,

For the Mellanox NIC MT27800 (MCX556M-ECAT-S25 to be precise), the
maximum number of VF per PF can be configured in the firmware, by
running e.g. :

$ sudo mstconfig -d 32:00.1 set NUM_OF_VFS=127

If I set this NUM_OF_VFS to 64 or more, the creation of even a single VF
fails mid-way :

$ echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs
1

dmesg shows :

[101418.090970] (:32:00.0): E-Switch: E-Switch enable SRIOV: nvfs(1) mode 
(1)
[101418.182736] (:32:00.0): E-Switch: SRIOV enabled: active vports(2)
[101418.289642] pci :32:00.2: [15b3:1018] type 00 class 0x02
[101418.290235] pci :32:00.2: Max Payload Size set to 512 (was 128, max 512)
[101418.290261] pci :32:00.2: enabling Extended Tags
[101418.292432] iommu: Adding device :32:00.2 to group 139
[101418.292580] iommu: Using direct mapping for device :32:00.2
[101418.292979] mlx5_core :32:00.2: enabling device ( -> 0002)
[101418.293719] mlx5_core :32:00.2: firmware version: 16.24.1000
[101418.550589] mlx5_core :32:00.2: alloc irq vectors failed
[101418.974082] mlx5_core :32:00.2: mlx5_load_one failed with error code -28
[101418.981656] mlx5_core: probe of :32:00.2 failed with error -28

This is a problem with both the Ubuntu kernel driver and the OFED
driver.

Thanks

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-46-generic 4.15.0-46.49
ProcVersionSignature: User Name 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Mar 21 08:33 seq
 crw-rw 1 root audio 116, 33 Mar 21 08:33 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Fri Mar 22 12:43:26 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: Supermicro AS -2023US-TR4
PciMultimedia:
 
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=C.UTF-8
 SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=52d72a05-517b-4c16-8dcb-486bdebcc695 ro console=ttyS1,115200 nosplash 
iommu=pt amd_iommu=on processor.max_cstate=0 l1tf=full cpuidle.off=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-46-generic N/A
 linux-backports-modules-4.15.0-46-generic  N/A
 linux-firmware 1.173.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/04/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.1c
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H11DSU-iN
dmi.board.vendor: Supermicro
dmi.board.version: 1.02A
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 1
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.1c:bd10/04/2018:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: AS -2023US-TR4
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug bionic uec-images

-- 
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/1821345

Title:
  Mellanox MT27800 / mlx5_core : cannot bring up VFs if the total number
  of VFs is >= 64 : alloc irq vectors failed

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  For the Mellanox NIC MT27800 (MCX556M-ECAT-S25 to be precise), the
  maximum number of VF per PF can be configured in the firmware, by
  running e.g. :

  $ sudo mstconfig -d 32:00.1 set NUM_OF_VFS=127

  If I set this NUM_OF_VFS to 64 or more, the creation of even a single
  VF fails mid-way :

  $ echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs
  1

  dmesg shows :

  [101418.090970] (:32:00.0): E-Switch: E-Switch enable SRIOV: nvfs(1) mode 
(1)
  [101418.182736] (:32:00.0): E-Switch: SRIOV enabled: active vports(2)
  [101418.289642] pci :32:00.2: [15b3:1018] type 00 class 0x02
  [101418.290235] pci :32:00.2: Max Payload Size set to 512 (was 128, max 
512)
  [101418.290261] pci :32:00.2: enabling Extended Tags
  [101418.292432] iommu: Adding device :32:00.2 to group 139
  [101418.292580] iommu: Using direct mapping for device :32:00.2
  [101418.292979] mlx5_core :32:00.2: enabling device ( -> 0002)
  [101418.293719] mlx5_core :32:00.2: firmware version: 16.24.1000
  

[Kernel-packages] [Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found

2019-03-22 Thread Guillaume Penin
** Also affects: linux-meta (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1820755

Title:
  Netboot install fails due to linux-image-4.4.0-143-generic.postinst
  linux-update-symlinks not found

Status in Blue Linux:
  New
Status in linux-base package in Ubuntu:
  Confirmed
Status in linux-meta package in Ubuntu:
  New

Bug description:
  Using a netboot install of Ubuntu 16.04 LTS server, the install fails
  when configuring the kernel.  The failure will not let you move on.

  This seems to have happened after the release of 
  
https://lists.ubuntu.com/archives/ubuntu-security-announce/2019-March/004803.html

  The error logs 
  Mar 18 17:09:50 in-target: Setting up linux-modules-4.4.0-143-generic 
(4.4.0-143.169) ...
  Mar 18 17:09:50 in-target: ^M
  Mar 18 17:09:51 in-target: Setting up linux-image-4.4.0-143-generic 
(4.4.0-143.169) ...
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: 
/var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 50: 
/var/lib/dpkg/info/linux-image-4.4.0-143-generic.postinst: 
  Mar 18 17:09:51 in-target: linux-update-symlinks: not found
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: dpkg: error processing package 
linux-image-4.4.0-143-generic (--configure):
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:  subprocess installed post-installation script 
returned error exit status 127
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target: dpkg: dependency problems prevent configuration of 
linux-modules-extra-4.4.0-143-generic:
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:  linux-modules-extra-4.4.0-143-generic depends on 
linux-image-4.4.0-143-generic | linux-image-unsigned-4.4.0-143-generic; however:
  Mar 18 17:09:51 in-target: ^M
  Mar 18 17:09:51 in-target:   Package linux-image-4.4.0-143-generic is not 
configured yet.
  Mar 18 17:09:51 in-target: ^M
  Mar

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluelinux/+bug/1820755/+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 1819658] Re: linux-aws: 4.4.0-1040.43 -proposed tracker

2019-03-22 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Khaled El Mously (kmously) => (unassigned)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1819660
- phase: Packaging
- phase-changed: Friday, 15. March 2019 06:30 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Friday, 22. March 2019 12:43 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete

-- 
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/1819658

Title:
  linux-aws: 4.4.0-1040.43 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
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:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1819660
  phase: Holding before Promote to Proposed
  phase-changed: Friday, 22. March 2019 12:43 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819658/+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 1820311] Re: linux-kvm: 5.0.0-1001.1 -proposed tracker

2019-03-22 Thread Seth Forshee
** Tags added: regression-testing-passed

-- 
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/1820311

Title:
  linux-kvm: 5.0.0-1001.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 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-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Disco:
  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 --
  kernel-master-bug: 1819759
  phase: Ready for Testing
  phase-changed: Friday, 15. March 2019 20:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820311/+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 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

2019-03-22 Thread Brad Figg
** Changed in: kernel-sru-workflow/snap-release-to-stable
   Status: New => Invalid

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1819698
- phase: Ready for Packaging
- phase-changed: Thursday, 21. March 2019 10:32 UTC
+ phase: Packaging
+ phase-changed: Friday, 22. March 2019 12:38 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded

-- 
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/1819695

Title:
  linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1819698
  phase: Packaging
  phase-changed: Friday, 22. March 2019 12:38 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819695/+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 1820878] Re: linux-aws: 5.0.0-1001.1 -proposed tracker

2019-03-22 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-release
   Status: New => Confirmed

** Tags removed: block-proposed-disco

** Tags removed: block-proposed

** 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 --
  kernel-master-bug: 1819759
- phase: Ready for Testing
- phase-changed: Thursday, 21. March 2019 16:08 UTC
+ phase: Ready for Release
+ phase-changed: Friday, 22. March 2019 12:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Ongoing -- testing in progress
+   promote-to-release: Pending -- ready to copy

-- 
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/1820878

Title:
  linux-aws: 5.0.0-1001.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 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-release series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-aws source package in Disco:
  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 --
  kernel-master-bug: 1819759
  phase: Ready for Release
  phase-changed: Friday, 22. March 2019 12:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-release: Pending -- ready to copy

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820878/+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 1819695] Re: linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

2019-03-22 Thread Kleber Sacilotto de Souza
** Summary changed:

- linux-gcp:  -proposed tracker
+ linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

-- 
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/1819695

Title:
  linux-gcp: 4.15.0-1029.31~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  New

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  kernel-stable-master-bug: 1819698
  phase: Ready for Packaging
  phase-changed: Thursday, 21. March 2019 10:32 UTC
  reason:
prepare-package: Pending -- version not specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819695/+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


  1   2   >