[Kernel-packages] [Bug 1799497] Re: 4.15 kernel hard lockup about once a week

[Luis Rodriguez]

OK.. it is been quite a while with no locks I had it once after the zram
config pacakge was removed,, but no other locks since then.

kernel version is  4.15.0-33 to 38 in different servers.. I am going to
update the servers to latest version reboot, and wait for a little
longer.

then I am going to install back zram-config on certain servers to see if
it shows up again.

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

Title:
  4.15 kernel hard lockup about once a week

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  My main server has been running into hard lockups about once a week
  ever since I switched to the 4.15 Ubuntu 18.04 kernel.

  When this happens, nothing is printed to the console, it's effectively
  stuck showing a login prompt. The system is running with panic=1 on
  the cmdline but isn't rebooting so the kernel isn't even processing
  this as a kernel panic.

  
  As this felt like a potential hardware issue, I had my hosting provider give 
me a completely different system, different motherboard, different CPU, 
different RAM and different storage, I installed that system on 18.04 and moved 
my data over, a week later, I hit the issue again.

  We've since also had a LXD user reporting similar symptoms here also on 
varying hardware:
https://github.com/lxc/lxd/issues/5197

  
  My system doesn't have a lot of memory pressure with about 50% of free memory:

  root@vorash:~# free -m
totalusedfree  shared  buff/cache   
available
  Mem:  31819   17574 402 513   13842   
13292
  Swap: 159092687   13222

  I will now try to increase console logging as much as possible on the
  system in the hopes that next time it hangs we can get a better idea
  of what happened but I'm not too hopeful given the complete silence on
  the console when this occurs.

  System is currently on:
Linux vorash 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  But I've seen this since the GA kernel on 4.15 so it's not a recent 
regression.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 23 16:12 seq
   crw-rw 1 root audio 116, 33 Oct 23 16:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.4
  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: Cannot stat file /proc/22822/fd/10: Permission denied
   Cannot stat file /proc/22831/fd/10: Permission denied
  DistroRelease: Ubuntu 18.04
  HibernationDevice:
   RESUME=none
   CRYPTSETUP=n
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046b:ff10 American Megatrends, Inc. Virtual Keyboard 
and Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Intel Corporation S1200SP
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=575c878a-0be6-4806-9c83-28f67aedea65 ro biosdevname=0 net.ifnames=0 
panic=1 verbose console=tty0 console=ttyS0,115200n8
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: False
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: S1200SP.86B.03.01.1029.012520180838
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: S1200SP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H57532-271
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 23
  dmi.chassis.vendor: ...
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrS1200SP.86B.03.01.1029.012520180838:bd01/25/2018:svnIntelCorporation:pnS1200SP:pvr:rvnIntelCorporation:rnS1200SP:rvrH57532-271:cvn...:ct23:cvr.

[Kernel-packages] [Bug 1805097] Re: A bunch of ACPI Errors

[Yoshiba]

** Description changed:

  [   12.867697] ACPI Error: No handler for Region [ECRM] (5c67776a) 
[EmbeddedControl] (20180531/evregion-132)
  [   12.867709] ACPI Error: Region EmbeddedControl (ID=3) has no handler 
(20180531/exfldio-265)
  [   12.867724] No Local Variables are initialized for Method [OBTS]
  [   12.867727] Initialized Arguments for Method [OBTS]:  (1 arguments defined 
for method invocation)
  [   12.867728]   Arg0:   fa7e36ecInteger 

  [   12.867739] ACPI Error: Method parse/execution failed \OBTS, AE_NOT_EXIST 
(20180531/psparse-516)
  [   12.867752] ACPI Error: Method parse/execution failed \AMW0.DEVS, 
AE_NOT_EXIST (20180531/psparse-516)
  [   12.867767] ACPI Error: Method parse/execution failed \AMW0.WMBC, 
AE_NOT_EXIST (20180531/psparse-516)
  [   12.920848] ACPI Error: No handler for Region [ECRM] (5c67776a) 
[EmbeddedControl] (20180531/evregion-132)
  [   12.920861] ACPI Error: Region EmbeddedControl (ID=3) has no handler 
(20180531/exfldio-265)
  [   12.920875] No Local Variables are initialized for Method [OBTS]
  [   12.920878] Initialized Arguments for Method [OBTS]:  (1 arguments defined 
for method invocation)
  [   12.920879]   Arg0:   ae4b9fc7Integer 

  [   12.920890] ACPI Error: Method parse/execution failed \OBTS, AE_NOT_EXIST 
(20180531/psparse-516)
  [   12.920903] ACPI Error: Method parse/execution failed \AMW0.DEVS, 
AE_NOT_EXIST (20180531/psparse-516)
  [   12.920918] ACPI Error: Method parse/execution failed \AMW0.WMBC, 
AE_NOT_EXIST (20180531/psparse-516)
- [   12.960632] rtl8192cu 1-2.4:1.0 wlx0013ef75041d: renamed from wlan0
+ [   12.960632] rtl8192cu 1-2.4:1.0 wlx: renamed from wlan0
  
  cpuinfo
  processor   : 0
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.996
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 0
  cpu cores   : 4
  apicid  : 0
  initial apicid  : 0
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp 
tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
  bugs: cpu_meltdown spectre_v1 spectre_v2
  bogomips: 4831.40
  clflush size: 64
  cache_alignment : 64
  address sizes   : 36 bits physical, 48 bits virtual
  power management:
  
  processor   : 1
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.896
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 1
  cpu cores   : 4
  apicid  : 2
  initial apicid  : 2
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp 
tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
  bugs: cpu_meltdown spectre_v1 spectre_v2
  bogomips: 4831.40
  clflush size: 64
  cache_alignment : 64
  address sizes   : 36 bits physical, 48 bits virtual
  power management:
  
  processor   : 2
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.828
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 2
  cpu cores   : 4
  apicid  : 4
  initial apicid  : 4
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dte

[Kernel-packages] [Bug 1805097] Re: A bunch of ACPI Errors

[Yoshiba]

wifisyslog

** Attachment added: "wifisyslog"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805097/+attachment/5223447/+files/wifisyslog

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

Title:
  A bunch of ACPI Errors

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [   12.867697] ACPI Error: No handler for Region [ECRM] (5c67776a) 
[EmbeddedControl] (20180531/evregion-132)
  [   12.867709] ACPI Error: Region EmbeddedControl (ID=3) has no handler 
(20180531/exfldio-265)
  [   12.867724] No Local Variables are initialized for Method [OBTS]
  [   12.867727] Initialized Arguments for Method [OBTS]:  (1 arguments defined 
for method invocation)
  [   12.867728]   Arg0:   fa7e36ecInteger 

  [   12.867739] ACPI Error: Method parse/execution failed \OBTS, AE_NOT_EXIST 
(20180531/psparse-516)
  [   12.867752] ACPI Error: Method parse/execution failed \AMW0.DEVS, 
AE_NOT_EXIST (20180531/psparse-516)
  [   12.867767] ACPI Error: Method parse/execution failed \AMW0.WMBC, 
AE_NOT_EXIST (20180531/psparse-516)
  [   12.920848] ACPI Error: No handler for Region [ECRM] (5c67776a) 
[EmbeddedControl] (20180531/evregion-132)
  [   12.920861] ACPI Error: Region EmbeddedControl (ID=3) has no handler 
(20180531/exfldio-265)
  [   12.920875] No Local Variables are initialized for Method [OBTS]
  [   12.920878] Initialized Arguments for Method [OBTS]:  (1 arguments defined 
for method invocation)
  [   12.920879]   Arg0:   ae4b9fc7Integer 

  [   12.920890] ACPI Error: Method parse/execution failed \OBTS, AE_NOT_EXIST 
(20180531/psparse-516)
  [   12.920903] ACPI Error: Method parse/execution failed \AMW0.DEVS, 
AE_NOT_EXIST (20180531/psparse-516)
  [   12.920918] ACPI Error: Method parse/execution failed \AMW0.WMBC, 
AE_NOT_EXIST (20180531/psparse-516)
  [   12.960632] rtl8192cu 1-2.4:1.0 wlx: renamed from wlan0

  cpuinfo
  processor   : 0
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.996
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 0
  cpu cores   : 4
  apicid  : 0
  initial apicid  : 0
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp 
tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
  bugs: cpu_meltdown spectre_v1 spectre_v2
  bogomips: 4831.40
  clflush size: 64
  cache_alignment : 64
  address sizes   : 36 bits physical, 48 bits virtual
  power management:

  processor   : 1
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.896
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 1
  cpu cores   : 4
  apicid  : 2
  initial apicid  : 2
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp 
tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
  bugs: cpu_meltdown spectre_v1 spectre_v2
  bogomips: 4831.40
  clflush size: 64
  cache_alignment : 64
  address sizes   : 36 bits physical, 48 bits virtual
  power management:

  processor   : 2
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.828
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 2
  cpu cores   : 4
  apicid  : 4
  initial apicid  : 4
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp

[Kernel-packages] [Bug 1805098] Re: failed to assign [mem size 0x00200000 64bit pref]

[Yoshiba]

More system info check this post below.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805097

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

** Tags added: kernel-bug-exists-upstream

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

Title:
  failed to assign [mem size 0x0020 64bit pref]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [0.270574] pci :00:1c.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [0.270577] pci :00:1c.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [0.270584] pci :00:1c.2: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [0.270587] pci :00:1c.2: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [0.270591] pci :00:1c.3: BAR 14: no space for [mem size 0x0020]
  [0.270594] pci :00:1c.3: BAR 14: failed to assign [mem size 
0x0020]
  [0.270600] pci :00:1c.3: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [0.270603] pci :00:1c.3: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [0.270608] pci :00:1c.3: BAR 13: assigned [io  0x1000-0x1fff]
  [0.270614] pci :00:1c.3: BAR 14: no space for [mem size 0x0020]
  [0.270617] pci :00:1c.3: BAR 14: failed to assign [mem size 
0x0020]
  [0.270623] pci :00:1c.3: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [0.270626] pci :00:1c.3: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [0.270633] pci :00:1c.2: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [0.270635] pci :00:1c.2: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [0.270642] pci :00:1c.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [0.270644] pci :00:1c.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [0.270648] pci :00:1c.0: PCI bridge to [bus 01]
  [0.270652] pci :00:1c.0:   bridge window [io  0xe000-0xefff]
  [0.270657] pci :00:1c.0:   bridge window [mem 0xa000-0xab0f]
  [0.270664] pci :00:1c.2: PCI bridge to [bus 02]
  [0.270666] pci :00:1c.2:   bridge window [io  0xd000-0xdfff]
  [0.270671] pci :00:1c.2:   bridge window [mem 0xab30-0xab3f]
  [0.270677] pci :00:1c.3: PCI bridge to [bus 03]

  cpuinfo
  processor   : 0
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.996
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 0
  cpu cores   : 4
  apicid  : 0
  initial apicid  : 0
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp 
tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
  bugs: cpu_meltdown spectre_v1 spectre_v2
  bogomips: 4831.40
  clflush size: 64
  cache_alignment : 64
  address sizes   : 36 bits physical, 48 bits virtual
  power management:

  processor   : 1
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.896
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 1
  cpu cores   : 4
  apicid  : 2
  initial apicid  : 2
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp 
tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
  bugs: cpu_meltdown spectre_v1 spectre_v2
  bogomips: 4831.40
  clflush size: 64
  cache_alignment : 64
  address sizes   : 36 bits physical, 48 bits virtual
  power management:

  processor   : 2
  vendor_id   : GenuineIntel
  cpu fa

[Kernel-packages] [Bug 1805097] Re: A bunch of ACPI Errors

[Yoshiba]

UdevDb

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805097/+attachment/5223191/+files/UdevDb.txt

** Attachment added: "UdevDb"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805097/+attachment/5223446/+files/UdevDb

** Tags added: kernel-bug-exists-upstream

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

Title:
  A bunch of ACPI Errors

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [   12.867697] ACPI Error: No handler for Region [ECRM] (5c67776a) 
[EmbeddedControl] (20180531/evregion-132)
  [   12.867709] ACPI Error: Region EmbeddedControl (ID=3) has no handler 
(20180531/exfldio-265)
  [   12.867724] No Local Variables are initialized for Method [OBTS]
  [   12.867727] Initialized Arguments for Method [OBTS]:  (1 arguments defined 
for method invocation)
  [   12.867728]   Arg0:   fa7e36ecInteger 

  [   12.867739] ACPI Error: Method parse/execution failed \OBTS, AE_NOT_EXIST 
(20180531/psparse-516)
  [   12.867752] ACPI Error: Method parse/execution failed \AMW0.DEVS, 
AE_NOT_EXIST (20180531/psparse-516)
  [   12.867767] ACPI Error: Method parse/execution failed \AMW0.WMBC, 
AE_NOT_EXIST (20180531/psparse-516)
  [   12.920848] ACPI Error: No handler for Region [ECRM] (5c67776a) 
[EmbeddedControl] (20180531/evregion-132)
  [   12.920861] ACPI Error: Region EmbeddedControl (ID=3) has no handler 
(20180531/exfldio-265)
  [   12.920875] No Local Variables are initialized for Method [OBTS]
  [   12.920878] Initialized Arguments for Method [OBTS]:  (1 arguments defined 
for method invocation)
  [   12.920879]   Arg0:   ae4b9fc7Integer 

  [   12.920890] ACPI Error: Method parse/execution failed \OBTS, AE_NOT_EXIST 
(20180531/psparse-516)
  [   12.920903] ACPI Error: Method parse/execution failed \AMW0.DEVS, 
AE_NOT_EXIST (20180531/psparse-516)
  [   12.920918] ACPI Error: Method parse/execution failed \AMW0.WMBC, 
AE_NOT_EXIST (20180531/psparse-516)
  [   12.960632] rtl8192cu 1-2.4:1.0 wlx: renamed from wlan0

  cpuinfo
  processor   : 0
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.996
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 0
  cpu cores   : 4
  apicid  : 0
  initial apicid  : 0
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp 
tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
  bugs: cpu_meltdown spectre_v1 spectre_v2
  bogomips: 4831.40
  clflush size: 64
  cache_alignment : 64
  address sizes   : 36 bits physical, 48 bits virtual
  power management:

  processor   : 1
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.896
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 1
  cpu cores   : 4
  apicid  : 2
  initial apicid  : 2
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp 
tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
  bugs: cpu_meltdown spectre_v1 spectre_v2
  bogomips: 4831.40
  clflush size: 64
  cache_alignment : 64
  address sizes   : 36 bits physical, 48 bits virtual
  power management:

  processor   : 2
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.828
  cache size  : 1024 KB
  physical id : 0
  siblings: 4

[Kernel-packages] [Bug 1805099] Re: nvidia: module verification failed: signature and/or required key missing - tainting kernel

[Yoshiba]

More system info check this post below.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805097

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

** Tags added: kernel-bug-exists-upstream

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

Title:
  nvidia: module verification failed: signature and/or required key
  missing - tainting kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [2.339868] nvidia: loading out-of-tree module taints kernel.
  [2.339881] nvidia: module license 'NVIDIA' taints kernel.
  [2.339882] Disabling lock debugging due to kernel taint
  [2.344554] usb 1-3: new high-speed USB device number 3 using xhci_hcd
  [2.354676] nvidia: module verification failed: signature and/or required 
key missing - tainting kernel
  [2.368949] nvidia-nvlink: Nvlink Core is being initialized, major device 
number 239
  [2.369522] nvidia :01:00.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=none:owns=io+mem
  [2.369735] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  390.87  Tue 
Aug 21 12:33:05 PDT 2018 (using threaded interrupts)
  [2.386968] PKCS#7 signature not signed with a trusted key
  [2.390444] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for 
UNIX platforms  390.87  Tue Aug 21 16:16:14 PDT 2018
  [2.391646] PKCS#7 signature not signed with a trusted key
  [2.394094] [drm] [nvidia-drm] [GPU ID 0x0100] Loading driver
  [2.394098] [drm] Initialized nvidia-drm 0.0.0 20160202 for :01:00.0 
on minor 0

  cpuinfo
  processor   : 0
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.996
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 0
  cpu cores   : 4
  apicid  : 0
  initial apicid  : 0
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp 
tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
  bugs: cpu_meltdown spectre_v1 spectre_v2
  bogomips: 4831.40
  clflush size: 64
  cache_alignment : 64
  address sizes   : 36 bits physical, 48 bits virtual
  power management:

  processor   : 1
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.896
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 1
  cpu cores   : 4
  apicid  : 2
  initial apicid  : 2
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp 
tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
  bugs: cpu_meltdown spectre_v1 spectre_v2
  bogomips: 4831.40
  clflush size: 64
  cache_alignment : 64
  address sizes   : 36 bits physical, 48 bits virtual
  power management:

  processor   : 2
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.828
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 2
  cpu cores   : 4
  apicid  : 4
  initial apicid  : 4
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2

[Kernel-packages] [Bug 1807974] Re: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic

[Kai-Heng Feng]

The firmware for this device got updated recently [1].
Please copy binary blobs in [2] to the same relative path under /lib/firmwares/.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=a87eb5f7bac0f70ade57da57d9126d14eee12336

[2] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/tree/ath10k/QCA6174/hw3.0

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

Title:
  Wireless regularly breaking (ath10k firmware crashed!) after upgrade
  to Cosmic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell XPS 13 9370 developer edition (Ubuntu version) running
  Cosmic. A handful of times per day, my wireless stops working ("?"
  appears in the icon in Network Manager). Turning wireless off and then
  on again, or suspending and waking the machine up, makes the wireless
  work again.

  dmesg output is as follows:

  $ dmesg | grep ath10k

  [ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid 
6317c652-4817-4fdd-b6d7-c7b8336e493f)
  [ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:143a
  [ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [ 6646.270369] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 
20d869c3
  [ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypto 1
  [ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for 
firmware address 4: -16
  [ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16
  [ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump:
  [ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400  14  14   3   3
  [ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800  29  29 106 107
  [ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00  20  19  18  19
  [ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000   8   8  10   8
  [ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103
  [ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800   0   0  64   0
  [ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00   0   0   6   6
  [ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000   0   1   0   1
  [ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address: 
-28
  [ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809
  [ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118
  [ 6647.239340] ath10k_pci :02:00.0: device successfully recovered

  
  [17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid 
03393f2f-0ce1-4017-b711-40dd14f2ec11)
  [17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:143a
  [17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [17641.848065] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [17641.848585] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 
20d869c3
  [17641.848593] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypto 1
  [17641.860559] ath10k_pci :02:00.0: failed to get memcpy hi address for 
firmware address 4: -16
  [17641.860587] ath10k_pci :02:00.0: failed to read firmware dump area: -16
  [17641.860595] ath10k_pci :02:00.0: Copy Engine register dump:
  [17641.860611] ath10k_pci :02:00.0: [00]: 0x00034400  14  14   3   3
  [17641.860624] ath10k_pci :02:00.0: [01]: 0x00034800   6   6 243 244
  [17641.860639] ath10k_pci :02:00.0: [02]: 0x00034c00  53  52  51  52
  [17641.860656] ath10k_pci :02:00.0: [03]: 0x00035000   5   5   7   5
  [17641.860669] ath10k_pci :02:00.0: [04]: 0x00035400 1231 1231 169 105
  [17641.860681] ath10k_pci :02:00.0: [05]: 0x00035800   0   0  64   0
  [17641.860693] ath10k_pci :02:00.0: [06]: 0x00035c00   0   0  30  30
  [17641.860706] ath10k_pci :02:00.0: [07]: 0x00036000   0   1   0   1
  [17641.890915] ath10k_pci :02:00.0: failed to read hi_board_data address: 
-28
  [17642.714052] ath10k_pci :02:00.0: Unknown eventid: 118809
  [17642.717154] ath10k_pci :02:00.0: Unknown eventid: 90118
  [17642.835601] ath10k_pci :02:00.0: device successfully recovered
  [17894.571696] ath10k_pci :02:00.0: Unknown eventid: 118809
  [17894.574764] ath10k_pci :02:00.0: Unknown eventid: 90118

  I do not recall having any wireless issues before I upgraded (when
  this machine was running Bionic).

  Bug #1730331 - ath10k_pci: firmware crashed!
  Bug #1627474 - ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [16.10]
  could

[Kernel-packages] [Bug 1805097] Re: A bunch of ACPI Errors

[Yoshiba]

dmesg

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805097/+attachment/5223438/+files/dmesg

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

Title:
  A bunch of ACPI Errors

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [   12.867697] ACPI Error: No handler for Region [ECRM] (5c67776a) 
[EmbeddedControl] (20180531/evregion-132)
  [   12.867709] ACPI Error: Region EmbeddedControl (ID=3) has no handler 
(20180531/exfldio-265)
  [   12.867724] No Local Variables are initialized for Method [OBTS]
  [   12.867727] Initialized Arguments for Method [OBTS]:  (1 arguments defined 
for method invocation)
  [   12.867728]   Arg0:   fa7e36ecInteger 

  [   12.867739] ACPI Error: Method parse/execution failed \OBTS, AE_NOT_EXIST 
(20180531/psparse-516)
  [   12.867752] ACPI Error: Method parse/execution failed \AMW0.DEVS, 
AE_NOT_EXIST (20180531/psparse-516)
  [   12.867767] ACPI Error: Method parse/execution failed \AMW0.WMBC, 
AE_NOT_EXIST (20180531/psparse-516)
  [   12.920848] ACPI Error: No handler for Region [ECRM] (5c67776a) 
[EmbeddedControl] (20180531/evregion-132)
  [   12.920861] ACPI Error: Region EmbeddedControl (ID=3) has no handler 
(20180531/exfldio-265)
  [   12.920875] No Local Variables are initialized for Method [OBTS]
  [   12.920878] Initialized Arguments for Method [OBTS]:  (1 arguments defined 
for method invocation)
  [   12.920879]   Arg0:   ae4b9fc7Integer 

  [   12.920890] ACPI Error: Method parse/execution failed \OBTS, AE_NOT_EXIST 
(20180531/psparse-516)
  [   12.920903] ACPI Error: Method parse/execution failed \AMW0.DEVS, 
AE_NOT_EXIST (20180531/psparse-516)
  [   12.920918] ACPI Error: Method parse/execution failed \AMW0.WMBC, 
AE_NOT_EXIST (20180531/psparse-516)
  [   12.960632] rtl8192cu 1-2.4:1.0 wlx0013ef75041d: renamed from wlan0

  cpuinfo
  processor   : 0
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.996
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 0
  cpu cores   : 4
  apicid  : 0
  initial apicid  : 0
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp 
tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
  bugs: cpu_meltdown spectre_v1 spectre_v2
  bogomips: 4831.40
  clflush size: 64
  cache_alignment : 64
  address sizes   : 36 bits physical, 48 bits virtual
  power management:

  processor   : 1
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.896
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 1
  cpu cores   : 4
  apicid  : 2
  initial apicid  : 2
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp 
tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
  bugs: cpu_meltdown spectre_v1 spectre_v2
  bogomips: 4831.40
  clflush size: 64
  cache_alignment : 64
  address sizes   : 36 bits physical, 48 bits virtual
  power management:

  processor   : 2
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.828
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 2
  cpu cores   : 4
  apicid  : 4
  initial apicid  : 4
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp   

[Kernel-packages] [Bug 1752437]

[obelisk]

I can confirm 4.19 from Ubuntu works well with Ubuntu 8.10, I've been
using it for a couple of days now, it's fast and stable as long as you
don't try to suspend (which freezes the machine).

I suspect that there is a long way to go for proper ACPI states support,
but that's a whole different ticket :-)

Thanks all!

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

Status in linux:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The touch screen on my HP ENVY x360 15-bq102ng does not work with
  stock kernel or with mainline kernel 4.16-rc3.

  marc@snapbug:~$ xinput
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=14   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=15   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP I id=11   [slave  
keyboard (3)]
  ↳ HP Wide Vision FHD Camera: HP W id=10   [slave  
keyboard (3)]

  WORKAROUND: Use the following patch with 4.17-rc3:
  https://bugzilla.kernel.org/attachment.cgi?id=275381

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  Uname: Linux 4.16.0-041600rc2-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  BootLog:
   No key available with this passphrase.
   /dev/mapper/nvme0n1p2_crypt: clean, 621596/15597568 files, 54013381/62389248 
blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:34:50 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15dd] (rev c4) (prog-if 
00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:83c6]
  InstallationDate: Installed on 2018-01-16 (42 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP ENVY x360 Convertible 15-bq1xx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.16.0-041600rc2-generic 
root=UUID=415eb027-1fd5-4b75-9860-5cac88a630db ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: AMI
  dmi.bios.version: F.16
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.18
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.16:bd01/26/2018:svnHP:pnHPENVYx360Convertible15-bq1xx:pvr:rvnHP:rn83C6:rvr63.18:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15-bq1xx
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.85-4~a~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 1:17.3.2-0~a~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.3.2-0~a~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel/+bug/1752437/+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 1806532] Re: The line-out on the Dell Dock station can't work

[Hui Wang]

This is the debdiff for bionic, it is not an incremental debdiff (since
the debdiff of #3 is not merged to bionic-proposed branch yet), this
debdiff will replace the one in the #3. It fixed the problem of
forgetting to add dir in the configure.ac.



** Patch added: "alsa-lib_1.1.3-5ubuntu0.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806532/+attachment/5223434/+files/alsa-lib_1.1.3-5ubuntu0.2.debdiff

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

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in alsa-lib source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  For Linux kernel: Cherry-picked 3 upstream patches, these patches add the 
longname of the sound card for the dock station.

  For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will
  add ucm configuration files for Dell WD15&19, and change the SPDIF conf
  in the USB-AUDIO.conf.

  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806532/+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 1781879] Re: Latest ASUS trackpad doesn't work in Ubuntu

[Kai-Heng Feng]

Oops, I forgot what commits I backported.

So please test the following kernels,
Bionic: https://people.canonical.com/~khfeng/lp1781879-bionic/
Cosmic: https://people.canonical.com/~khfeng/lp1781879-cosmic/

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

Title:
  Latest ASUS trackpad doesn't work in Ubuntu

Status in Linux:
  In Progress
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It seems there might be a new hardware variant of the elan trackpad in
  the newer ASUS machines.

  The issue is the shown here with some reasonably deep investigation.
  Is this something that I can do or am I reduced to having to find out
  a mouse if I want to use Linux?

  https://www.asus.com/us/Laptops/ASUS-TUF-Gaming-FX504/specifications/

  user@TUF-GAMING-FX504GD-FX80GD:~$ xinput
   Virtual core pointer  id=2[master pointer  (3)]
     ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
     ↳ Logitech USB Receiver id=12   [slave  pointer  (2)]
     ↳ Logitech USB Receiver id=13   [slave  pointer  (2)]
   Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Power Button  id=6[slave  keyboard (3)]
  ↳ Asus Wireless Radio Control   id=7[slave  keyboard (3)]
  ↳ Video Bus id=8[slave  keyboard (3)]
  ↳ Video Bus id=9[slave  keyboard (3)]
  ↳ Power Button  id=10   [slave  keyboard (3)]
  ↳ Sleep Button  id=11   [slave  keyboard (3)]
  ↳ USB2.0 HD UVC WebCam: USB2.0 HD   id=14   [slave  keyboard (3)]
  ↳ Asus WMI hotkeys  id=15   [slave  keyboard (3)]
  ↳ AT Translated Set 2 keyboard  id=16   [slave  keyboard (3)]
  ↳ Logitech USB Receiver id=17   [slave  keyboard (3)]

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1781879/+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 1798800] Re: Ubuntu 18.04->18.10 upgrade, blank screen on/before login

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Ubuntu 18.04->18.10 upgrade, blank screen on/before login

Status in linux package in Ubuntu:
  Expired

Bug description:
  I had been using ubuntu 18.04 with mainline 4.18.* kernel without any problem 
then I've upgraded to 18.10 and the screen is black now on login. I'm almost 
sure there shouldn't be modesetting problem on 4.18 with its default modules.
  What information, files, logs do you need to solve this problem? This is an 
AMD Ryzen based notebook with hybrid graphics.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798800/+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 1798462] Re: package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to install/upgrade: installed linux-image-4.15.0-36-generic package post-installation script subprocess re

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to
  install/upgrade: installed linux-image-4.15.0-36-generic package post-
  installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Expired

Bug description:
  Computer ran update, and this bug was shown. I did not find it nor did
  I look for it.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hristian   7202 F pulseaudio
  Date: Wed Oct 17 21:50:50 2018
  ErrorMessage: installed linux-image-4.15.0-36-generic package 
post-installation script subprocess returned error exit status 1
  InstallationDate: Installed on 2018-07-14 (95 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=adce9bb8-7c96-41ce-afef-62af861fa436 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python3.6, Python 3.6.6, python-minimal, 2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.4
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to 
install/upgrade: installed linux-image-4.15.0-36-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798462/+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 1798802] Re: package linux-headers-4.4.0-128-generic 4.4.0-128.154 failed to install/upgrade: package linux-headers-4.4.0-128-generic is not ready for configuration cannot confi

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package linux-headers-4.4.0-128-generic 4.4.0-128.154 failed to
  install/upgrade: package linux-headers-4.4.0-128-generic is not ready
  for configuration  cannot configure (current status 'half-installed')

Status in linux package in Ubuntu:
  Expired

Bug description:
  system detection failure in loading system. Ubuntu 16.04LS
  Unable to update to Ubuntu 18

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-headers-4.4.0-128-generic 4.4.0-128.154
  ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144
  Uname: Linux 4.4.0-137-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  christiner   1738 F pulseaudio
   /dev/snd/controlC0:  christiner   1738 F pulseaudio
  Date: Fri Oct 19 12:45:30 2018
  DuplicateSignature:
   package:linux-headers-4.4.0-128-generic:4.4.0-128.154
   Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
   dpkg: error processing package linux-headers-4.4.0-128-generic (--configure):
package linux-headers-4.4.0-128-generic is not ready for configuration
  ErrorMessage: package linux-headers-4.4.0-128-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  HibernationDevice: RESUME=UUID=b38ef07c-092d-46bb-8c7d-68c4bfb1e46f
  InstallationDate: Installed on 2015-07-01 (1206 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. X555LA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-137-generic.efi.signed 
root=UUID=9299c0fb-0e75-4d22-94b7-d4cd3041f72f ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-4.4.0-128-generic 4.4.0-128.154 failed to 
install/upgrade: package linux-headers-4.4.0-128-generic is not ready for 
configuration  cannot configure (current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LA.308
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LA
  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.:bvrX555LA.308:bd08/14/2014:svnASUSTeKCOMPUTERINC.:pnX555LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555LA
  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/1798802/+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 1798614] Re: It doesn't regonize my touchpad after automaticly closing screen (or maybe suspend)

[Launchpad Bug Tracker]

[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  It doesn't regonize my touchpad after automaticly closing screen (or
  maybe suspend)

Status in linux package in Ubuntu:
  Expired

Bug description:
  The touchpad doesn't appear in the Settings.But it works before turning off 
the screen.
  Maybe the system suspended it,i don't know.
  I tried suspend it and resume,uh,this didn't work.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  blurhy 5047 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 18 23:25:34 2018
  InstallationDate: Installed on 2018-10-10 (8 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  MachineType: ASUSTeK COMPUTER INC. FX503VD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro pcie_aspm=force
  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: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX503VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX503VD
  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.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: FX
  dmi.product.name: FX503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  blurhy 9433 F pulseaudio
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-10-10 (8 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  MachineType: ASUSTeK COMPUTER INC. FX503VD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro pcie_aspm=force
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX503VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX503VD
  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.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: FX
  dmi.product.name: FX503VD
  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/1798614/+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 1806532] Re: The line-out on the Dell Dock station can't work

[Hui Wang]

The build failure for cosmic and bionic (after applying the debdiff of
#2 and #3) is because I forgot to add one more patch to add this ucm to
configure.ac.

here I fixed it, and generate an incremental debdiff for cosmic (since
the debdiff of #2 is already merged to cosmic-proposed branch). If need
me put this debdiff and the debdiff of #2 into one debdiff, let me know.

thanks.

This is the incremental debdiff based on #2 for Cosmic.


** Patch added: "alsa-lib_1.1.6-1ubuntu1.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806532/+attachment/5223433/+files/alsa-lib_1.1.6-1ubuntu1.2.debdiff

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

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in alsa-lib source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  For Linux kernel: Cherry-picked 3 upstream patches, these patches add the 
longname of the sound card for the dock station.

  For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will
  add ucm configuration files for Dell WD15&19, and change the SPDIF conf
  in the USB-AUDIO.conf.

  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806532/+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 1806488] Re: Support non-strict iommu mode on arm64

[dann frazier]

** Description changed:

  [Impact]
- There's a significant performance gain to be had by removing the need to 
flush the IOMMU TLB on every unmap. I'm seeing a 25% performance gain w/ fio 
reads on a single NVMe device. This mode of operation is available for x86 via 
the "intel_iommu=strict" parameter. This support is now available upstream for 
ARM platforms via the "iommu.strict=[0|1]" parameter, while keeping the default 
in strict mode.
+ The Intel IOMMU driver provides an option for strict mode. When disabled, 
batching of IOTLB flush operations is permitted, allowing the user to trade-off 
isolation for improved performance. Ubuntu's kernel currently lacks a parity 
for this feature for ARM.
+ 
+ There's a significant performance gain to be had by removing the need to
+ flush the IOMMU TLB on every unmap on arm64. I'm seeing a 25%
+ performance gain w/ fio reads on a single NVMe device.
+ 
+ This mode of operation is available for x86 via the "intel_iommu=strict"
+ parameter. Upstream now exposes an equivalent feature for ARM platforms
+ via the "iommu.strict=[0|1]" parameter, while retaining the default
+ strict-enabled mode.
  
  [Test Case]
  $ cat fio.rc
  [global]
  rw=read
  direct=1
  ioengine=libaio
  iodepth=2048
  numjobs=10
  bs=4k
  group_reporting=1
  group_reporting=1
  cpumask=0xff
  runtime=100
  loops = 1
  
  [job1]
  filename=/dev/nvme0n1
  
  [Fix]
  44f6876a00e83 iommu/arm-smmu: Support non-strict mode
  b2dfeba654cb0 iommu/io-pgtable-arm-v7s: Add support for non-strict mode
  9662b99a19abc iommu/arm-smmu-v3: Add support for non-strict mode
  b6b65ca20bc93 iommu/io-pgtable-arm: Add support for non-strict mode
  68a6efe86f6a1 iommu: Add "iommu.strict" command line option
  2da274cdf998a iommu/dma: Add support for non-strict mode
  07fdef34d2be6 iommu/arm-smmu-v3: Implement flush_iotlb_all hook
  85c7a0f1ef624 iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
  
  [Regression Risk]
+ Most of these patches are specific to ARM, and have been regression tested on 
both arm64 (HiSilicon D06) and armhf (QEMU virt) using "stress-ng --vm $(nproc)"
+ 
+ 2 patches do touch arch-indep code however:
+ 
+ > 68a6efe86f6a1 iommu: Add "iommu.strict" command line option
+ Adds a new command line option and sets an attribute that iommu drivers can 
optionally react to. Doesn't change default behavior.
+ 
+ > 2da274cdf998a iommu/dma: Add support for non-strict mode
+ This driver is only built for arm64 and ppc64el (determined by looking at the 
build logs). Most of this patch only changes behavior in the non-default (and 
new) iommu.strict=0 case. The exception, which is called out in the commit 
message, is this hunk:
+ 
+ -   WARN_ON(iommu_unmap(domain, dma_addr, size) != size);
+ +   WARN_ON(iommu_unmap_fast(domain, dma_addr, size) != size);
+ +   if (!cookie->fq_domain)
+ +   iommu_tlb_sync(domain);
+ 
+ 
+ In the default case, where fq_domain will be NULl, we are now factoring 
iommu_unmap() into:
+   iommu_unmap_fast()
+   iommu_tlb_sync()
+ 
+ Looking at the source to iommu_unmap() confirms that this is
+ functionally equivalent.

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

Title:
  Support non-strict iommu mode on arm64

Status in linux package in Ubuntu:
  In Progress
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]
  The Intel IOMMU driver provides an option for strict mode. When disabled, 
batching of IOTLB flush operations is permitted, allowing the user to trade-off 
isolation for improved performance. Ubuntu's kernel currently lacks a parity 
for this feature for ARM.

  There's a significant performance gain to be had by removing the need
  to flush the IOMMU TLB on every unmap on arm64. I'm seeing a 25%
  performance gain w/ fio reads on a single NVMe device.

  This mode of operation is available for x86 via the
  "intel_iommu=strict" parameter. Upstream now exposes an equivalent
  feature for ARM platforms via the "iommu.strict=[0|1]" parameter,
  while retaining the default strict-enabled mode.

  [Test Case]
  $ cat fio.rc
  [global]
  rw=read
  direct=1
  ioengine=libaio
  iodepth=2048
  numjobs=10
  bs=4k
  group_reporting=1
  group_reporting=1
  cpumask=0xff
  runtime=100
  loops = 1

  [job1]
  filename=/dev/nvme0n1

  [Fix]
  44f6876a00e83 iommu/arm-smmu: Support non-strict mode
  b2dfeba654cb0 iommu/io-pgtable-arm-v7s: Add support for non-strict mode
  9662b99a19abc iommu/arm-smmu-v3: Add support for non-strict mode
  b6b65ca20bc93 iommu/io-pgtable-arm: Add support for non-strict mode
  68a6efe86f6a1 iommu: Add "iommu.strict" command line option
  2da274cdf998a iommu/dma: Add support for non-strict mode
  07fdef34d2be6 iommu/arm-smmu-v3: Implement flush_iotlb_all hook
  85c7a0f1ef62

[Kernel-packages] [Bug 1808588] Re: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

[Kai-Heng Feng]

Please attach output of `cat /sys/bus/serio/devices/serio1/firmware_id`,
thanks!

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

Title:
  Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my Ubuntu from Bionic Beaver to Cosmic Cuttlefish on my
  laptop. The installation process seemed to go well, but on reboot my
  trackpad and trackpoint no longer move the pointer, register taps or
  click buttons, and are seemingly unrecognized by the system.

  General information:
  Laptop make/model: Lenovo Thinkpad P72 TYPE 20MB-CT01WW 18/11  (that might be 
a 'O' rather than an '0' on the sticker)
  Touchpad maufacturer: (Lenovo?) UltraNav TrackPoint
  When symptoms first appeared: On first reboot after the change to Cosmic. 
Also on subsequent reboots and waking from sleep and suspend.

  
  No trackpad device is listed in /proc/bus/input/devices.

  
  The trackpad and trackpoint and buttons work if I boot into another OS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808588/+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 1808588] Re: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

[Alexis Dinno]

@kaihengfeng Your suggestion did the trick! I had tried a similar
parameter I found elsewhere on the web (I *think* it was something like
'psmouse.elantech=0') to no avail.

Thank you Kai-Heng Feng!

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

Title:
  Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I upgraded my Ubuntu from Bionic Beaver to Cosmic Cuttlefish on my
  laptop. The installation process seemed to go well, but on reboot my
  trackpad and trackpoint no longer move the pointer, register taps or
  click buttons, and are seemingly unrecognized by the system.

  General information:
  Laptop make/model: Lenovo Thinkpad P72 TYPE 20MB-CT01WW 18/11  (that might be 
a 'O' rather than an '0' on the sticker)
  Touchpad maufacturer: (Lenovo?) UltraNav TrackPoint
  When symptoms first appeared: On first reboot after the change to Cosmic. 
Also on subsequent reboots and waking from sleep and suspend.

  
  No trackpad device is listed in /proc/bus/input/devices.

  
  The trackpad and trackpoint and buttons work if I boot into another OS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808588/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[VanVan]

It's already commited, check here :
http://mailman.alsa-project.org/pipermail/alsa-devel/2018-December/143282.html

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  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/alsa-driver/+bug/1784485/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[VanVan]

** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Internal speaker - not sound at all
  Cable Headphonse - realy quiet disorted sound
  Bluetooth headphones - sound works fine

  On Windows 10 everything works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pmichalski   7964 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 30 22:32:10 2018
  InstallationDate: Installed on 2018-07-17 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Wbudowany dźwięk - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2988 F pulseaudio
pmichalski   7964 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX391UA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX391UA
  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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook S
  dmi.product.name: ZenBook S UX391UA
  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/alsa-driver/+bug/1784485/+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 1807250] Re: At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my system

[Your full name]

https://news.ycombinator.com/item?id=18711970

The sad state of being able to use Ubuntu on touch devices (hint: you
can't)

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807250

So, apparently support for an entire bus class has been missing since
ubuntu bionic (18.04 LTS) was released in april. Using kernels from
other distros or ubuntus old xenial 4.4.0-134 all provide access to
sensor data, suggesting the issue is with current (and shipped) kernels.
Three weeks into this not much is happening even though the issue also
affect canonical-specific 4,18 kernels.

This all suggests that pretty much no one has been using ubuntu on touch
devices otherwise i wouldn't be the first one to notice this. Now that
the devs know this they have no time for it...


** Also affects: gdm3 (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/1807250

Title:
  At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my
  system

Status in gdm3 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Yoga 900-13ISK and a Thinkpad T470s. Both have had working
  screen rotation in the past. However, I noticed today while supporting
  a user in #ubuntu, neither do now. No icon in the Gnome menu and:

  # G_MESSAGES_DEBUG=all iio-sensor-proxy 
  ** (process:14877): DEBUG: 12:31:21.603: Could not find any supported sensors

  Indeed, /sys/bus/iio does not exist! I believe this is distinct from
  LP: #1792813, as I have just tested mainline 4.19 and it also does not
  work.

  I am working on getting more data, including testing older kernels
  from 18.04, but it might take me some time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1807250/+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 1779640] Re: [Hyper-V] KVP daemon crashes at startup

[Dan Watkins]

Yep, I have now done so:

$ ls -la /dev/vmbus/hv_kvp
crw--- 1 root root 10, 55 Dec 18 22:31 /dev/vmbus/hv_kvp

Joe, I've also imported your SSH keys in to ubuntu@test-
slgyvlgaldgcyzqkzuoz.cloudapp.net if there's any other poking around you
want to do.

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

Title:
  [Hyper-V] KVP daemon crashes at startup

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

Bug description:
  While testing Bionic daily build with kernel 4.15.0-20-generic we saw
  the following issue with the KVP daemon:

  KVP daemon crashes after approximatively 2 minutes of uptime and it enters in 
a failed state. The daemon can be manually started and it enters back in active 
(running) state.
  The error messages from /var/log/syslog after the daemon enters the failed 
state are the following:

  Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with 
result 'exit-code'.
  Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon.

  Note: There was a simmilar issue discussed on this thread
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the
  fixing commit seems to be inclued in this Bionic build.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779640/+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 1779640] Re: [Hyper-V] KVP daemon crashes at startup

[Joseph Salisbury]

Do you have a way to pause a test, so you can access the instance?  It
would be good to know if the file actually exists:

ls -l /dev/vmbus/hv_kvp

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

Title:
  [Hyper-V] KVP daemon crashes at startup

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

Bug description:
  While testing Bionic daily build with kernel 4.15.0-20-generic we saw
  the following issue with the KVP daemon:

  KVP daemon crashes after approximatively 2 minutes of uptime and it enters in 
a failed state. The daemon can be manually started and it enters back in active 
(running) state.
  The error messages from /var/log/syslog after the daemon enters the failed 
state are the following:

  Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with 
result 'exit-code'.
  Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon.

  Note: There was a simmilar issue discussed on this thread
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the
  fixing commit seems to be inclued in this Bionic build.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779640/+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 1809046] [NEW] Cannot initialize ATA disk if IDENTIFY command fails

[dann frazier]

Public bug reported:

[Impact]
ATA disks attached to a SAS controller may not initialize if the initial 
IDENTIFY command fails.

[Test Case]
The positive test case would require a disk that fails to respond correctly to 
an IDENTIFY command. I don't have one of those, so can only regression test on 
a system w/ SAS connected disks.

[Fix]
437207d3697f5 scsi: libsas: check the ata device status by ata_dev_enabled()

[Regression Risk]
Clean cherry pick from upstream - any regressions will have upstream support.

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

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

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

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

** Also 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 Bionic)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: linux (Ubuntu Cosmic)
 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/1809046

Title:
  Cannot initialize ATA disk if IDENTIFY command fails

Status in linux package in Ubuntu:
  In Progress
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:
  In Progress

Bug description:
  [Impact]
  ATA disks attached to a SAS controller may not initialize if the initial 
IDENTIFY command fails.

  [Test Case]
  The positive test case would require a disk that fails to respond correctly 
to an IDENTIFY command. I don't have one of those, so can only regression test 
on a system w/ SAS connected disks.

  [Fix]
  437207d3697f5 scsi: libsas: check the ata device status by ata_dev_enabled()

  [Regression Risk]
  Clean cherry pick from upstream - any regressions will have upstream support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809046/+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 1799064] Re: Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade (works in kernel 4.15.0, but fails in 4.16 onward)

[yitzhaq]

Many thanks for the pointer - that workaround did indeed work!
If there's any detail I can provide to help fix this properly, do let me know.

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

Title:
  Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade
  (works in kernel 4.15.0, but fails in 4.16 onward)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from bionic to cosmic, Bluetooth has stopped working.
  It has worked fine for several versions before.

  Error message from syslog is:

  Failed to set mode: Failed (0x03)

  Which according to various random forum posts seems to suggest the
  device is not powering on.

  Powering on manually also does not work:

  % bluetoothctl
  Agent registered
  [bluetooth]# power on
  Failed to set power on: org.bluez.Error.Failed

  And results in the same set mode failure getting logged again in syslog.
  hciconfig reports the device as down:

  % sudo hciconfig
  hci0: Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:101 acl:0 sco:0 commands:24 errors:0

  And, again, it refuses to power on:

  % sudo hciconfig hci0 up
  Can't init device hci0: Connection timed out (110)

  rfkill does not appear to be blocking it:

  % rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  And systemd-rfkill.service is masked:

  ~ % sudo systemctl status systemd-rfkill.service
  ● systemd-rfkill.service
 Loaded: masked (Reason: Unit systemd-rfkill.service is masked.)
  [..]

  The system does not have tlp installed.

  I have tried numerous reboots, power offs, and moving the USB
  Bluetooth adapter to different ports, with no change in result. I have
  also tried unloading and loading btusb.

  The adapter is a cheap noname thing off of eBay, I trust the system
  report will provide every possibly interesting detail about it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Sun Oct 21 17:22:28 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK Computer INC. EB1501P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=515746f5-9b4c-4148-8e1e-012df202f447 ro splash quiet 
username=autostart,nodiskmount loglevel=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0501
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: EB1501P
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/02/2012:svnASUSTeKComputerINC.:pnEB1501P:pvrSystemVersion:rvnASUSTeKComputerINC.:rnEB1501P:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: Eee Family
  dmi.product.name: EB1501P
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK Computer INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:95 acl:0 sco:0 commands:22 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799064/+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 1779640] Re: [Hyper-V] KVP daemon crashes at startup

[Dan Watkins]

This was from our test suite, so I don't have direct access to an
instance, but using the manifest, it is:

$ grep tools ~/manifest.txt
bcache-tools 1.0.8-3
dosfstools   4.1-2
initramfs-tools  0.131ubuntu15
initramfs-tools-bin  0.131ubuntu15
initramfs-tools-core 0.131ubuntu15
linux-azure-cloud-tools-4.18.0-1006  4.18.0-1006.6
linux-azure-tools-4.18.0-10064.18.0-1006.6
linux-cloud-tools-4.18.0-1006-azure  4.18.0-1006.6
linux-cloud-tools-azure  4.18.0.1006.7
linux-cloud-tools-common 4.18.0-11.12
linux-tools-4.18.0-1006-azure4.18.0-1006.6
linux-tools-azure4.18.0.1006.7
linux-tools-common   4.18.0-11.12
net-tools1.60+git20161116.90da8a0-2ubuntu1
open-vm-tools2:10.3.5-3
squashfs-tools   1:4.3-6ubuntu2
ubuntu-advantage-tools   17

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

Title:
  [Hyper-V] KVP daemon crashes at startup

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

Bug description:
  While testing Bionic daily build with kernel 4.15.0-20-generic we saw
  the following issue with the KVP daemon:

  KVP daemon crashes after approximatively 2 minutes of uptime and it enters in 
a failed state. The daemon can be manually started and it enters back in active 
(running) state.
  The error messages from /var/log/syslog after the daemon enters the failed 
state are the following:

  Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with 
result 'exit-code'.
  Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon.

  Note: There was a simmilar issue discussed on this thread
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the
  fixing commit seems to be inclued in this Bionic build.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779640/+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 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected

[Chris]

I have the same issue. Running Linux Mint with latest kernel.
Kernel: Linux 4.19.9-041909-generic #201812130432 SMP Thu Dec 13 09:34:53 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

It takes me disabling bluetooth, deleting the profile, re-enabling
bluetooth, and putting the mouse back in pairing mode to fix.

Only began happening after updating from Linux Mint 19 from Linux Mint
18.3 (I assume due to the Bluez version)

dmesg:
[ 9094.174854] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9113.487898] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9129.243872] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9145.487806] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9155.351840] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9171.601996] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9187.474873] Bluetooth: hci0: last event is not cmd complete (0x0f)
[ 9193.843245] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 9193.843255] Bluetooth: HIDP socket layer initialized
[ 9194.686585] hid-generic 0005:046D:B016.0002: unknown main item tag 0x0
[ 9194.686700] input: Bluetooth Mouse M336/M337/M535 Mouse as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:046D:B016.0002/input/input27
[ 9194.687692] input: Bluetooth Mouse M336/M337/M535 Consumer Control as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:046D:B016.0002/input/input28
[ 9194.687919] input: Bluetooth Mouse M336/M337/M535 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:046D:B016.0002/input/input31
[ 9194.688328] hid-generic 0005:046D:B016.0002: input,hidraw1: BLUETOOTH HID 
v12.03 Mouse [Bluetooth Mouse M336/M337/M535] on a4:34:d9:e0:9c:d1

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

Title:
  [regression] Logitech M337 mice are automatically disconnected after
  connected

Status in Bluez Utilities:
  Confirmed
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1773897/+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

[Kernel-packages] [Bug 1771823] Re: Please include ax88179_178a and r8152 modules in d-i udeb

[Adam Conrad]

** Changed in: debian-installer (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please include ax88179_178a and r8152 modules in d-i udeb

Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  
  == SRU Justification ==
  The r8152 module is used in a thunderbolt-connected docking station and
  ax88179_178a by an external USB dongle.

  Despite having two nics connected the bug reporter can't install
  Bionic.

  This SRU request is to add the modules to the debian installer.

  == Fix ==
  UBUNTU: [Config:] d-i: Add ax88179_178a and r8152 to nic-modules

  == Regression Potential ==
  Low.  This is adding a module to the installer.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.





  r8152 is used in a thunderbolt-connected docking station and
  ax88179_178a by an external USB dongle.

  Despite having two nics connected i can't install Bionic. :-)

  This is probably a subset of the modules to be included when fixing
  LP: #1503218.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1771823/+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 1794836] Re: Update from 16.04 to 18.04 and serious screen lagging problems

[Yulay]

Still not working and no solution given :-(

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

Title:
  Update from 16.04 to 18.04 and serious screen lagging problems

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded from Ubuntu 16.04 to ubuntu 18.04, and the refreshing of the 
screen in browsers, videos, etc... is really annoying. I would like to solve 
this problem since this is provoking me constant headache
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   julia  3959 F...m pulseaudio
   /dev/snd/pcmC1D0p:   julia  3959 F...m pulseaudio
   /dev/snd/controlC1:  julia  3959 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=3bf717b5-f3c2-45da-9ec8-5926c846f3ea
  InstallationDate: Installed on 2014-09-30 (1458 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Gigabyte Technology Co., Ltd. H81M-D2V
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=34beca2c-8810-4dea-81c4-ea789864bd2f ro nomodeset quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/25/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FB
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-D2V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFB:bd06/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-D2V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: H81M-D2V
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794836/+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 1806422] Re: linux-azure: 4.18.0-1007.7 -proposed tracker

[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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 07:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release
-   stakeholder-signoff: Pending -- waiting for signoff

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

Title:
  linux-azure: 4.18.0-1007.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 07:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

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

[jasd666]

apport information

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

Title:
  Microcode SW error detected. Restarting 0x0.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  intel-microcode:
Installed: 3.20180807a.0ubuntu0.18.04.1
Candidate: 3.20180807a.0ubuntu0.18.04.1
Version table:
   *** 3.20180807a.0ubuntu0.18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20180312.0~ubuntu18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  Version:
  Ubuntu 4.15.0-42.45-generic 4.15.18

  Error:

  [ 3136.084499] rtsx_pci :06:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
  [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1
  [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 
source:0x
  [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: 
id=00e8
  [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e8(Transmitter ID)
  [ 3136.085694] pcieport :00:1d.0:   device [8086:a335] error 
status/mask=1101/2000
  [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First)
  [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover
  [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout  
  [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6
  [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0
  [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT  
  [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0
  [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1
  [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2
  [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1
  [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2
  [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1
  [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2
  [ 3166.625860] iwlwifi :00:14.3: 0x | data3
  [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time
  [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low
  [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi
  [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1
  [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2
  [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major
  [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor
  [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version
  [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version
  [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd
  [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0
  [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1
  [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2
  [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3
  [ 3166.625944] iwlwifi :00:14.3: 0x | isr4
  [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id
  [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event
  [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control
  [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration
  [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid
  [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match
  [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel
  [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp
  [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler
  [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7
  [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT
  [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1
  [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2
  [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1
  [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2
  [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1
  [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2
  [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [ 3166.626194] iwlwifi :00:14.3: 0x0022 | 

[Kernel-packages] [Bug 1808886] RfKill.txt

[jasd666]

apport information

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

Title:
  Microcode SW error detected. Restarting 0x0.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  intel-microcode:
Installed: 3.20180807a.0ubuntu0.18.04.1
Candidate: 3.20180807a.0ubuntu0.18.04.1
Version table:
   *** 3.20180807a.0ubuntu0.18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20180312.0~ubuntu18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  Version:
  Ubuntu 4.15.0-42.45-generic 4.15.18

  Error:

  [ 3136.084499] rtsx_pci :06:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
  [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1
  [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 
source:0x
  [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: 
id=00e8
  [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e8(Transmitter ID)
  [ 3136.085694] pcieport :00:1d.0:   device [8086:a335] error 
status/mask=1101/2000
  [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First)
  [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover
  [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout  
  [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6
  [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0
  [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT  
  [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0
  [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1
  [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2
  [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1
  [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2
  [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1
  [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2
  [ 3166.625860] iwlwifi :00:14.3: 0x | data3
  [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time
  [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low
  [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi
  [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1
  [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2
  [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major
  [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor
  [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version
  [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version
  [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd
  [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0
  [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1
  [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2
  [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3
  [ 3166.625944] iwlwifi :00:14.3: 0x | isr4
  [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id
  [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event
  [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control
  [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration
  [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid
  [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match
  [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel
  [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp
  [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler
  [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7
  [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT
  [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1
  [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2
  [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1
  [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2
  [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1
  [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2
  [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [ 3166.626194] iwlwifi :00:14.3: 0x0022 | 

[Kernel-packages] [Bug 1808886] WifiSyslog.txt

[jasd666]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1808886/+attachment/5223290/+files/WifiSyslog.txt

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

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

Title:
  Microcode SW error detected. Restarting 0x0.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  intel-microcode:
Installed: 3.20180807a.0ubuntu0.18.04.1
Candidate: 3.20180807a.0ubuntu0.18.04.1
Version table:
   *** 3.20180807a.0ubuntu0.18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20180312.0~ubuntu18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  Version:
  Ubuntu 4.15.0-42.45-generic 4.15.18

  Error:

  [ 3136.084499] rtsx_pci :06:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
  [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1
  [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 
source:0x
  [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: 
id=00e8
  [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e8(Transmitter ID)
  [ 3136.085694] pcieport :00:1d.0:   device [8086:a335] error 
status/mask=1101/2000
  [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First)
  [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover
  [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout  
  [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6
  [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0
  [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT  
  [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0
  [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1
  [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2
  [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1
  [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2
  [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1
  [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2
  [ 3166.625860] iwlwifi :00:14.3: 0x | data3
  [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time
  [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low
  [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi
  [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1
  [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2
  [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major
  [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor
  [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version
  [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version
  [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd
  [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0
  [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1
  [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2
  [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3
  [ 3166.625944] iwlwifi :00:14.3: 0x | isr4
  [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id
  [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event
  [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control
  [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration
  [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid
  [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match
  [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel
  [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp
  [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler
  [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7
  [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT
  [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1
  [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2
  [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1
  [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2
  [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1
  [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2
  [ 3166.626189] iwlwifi :00:14.

[Kernel-packages] [Bug 1808886] CurrentDmesg.txt

[jasd666]

apport information

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

Title:
  Microcode SW error detected. Restarting 0x0.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  intel-microcode:
Installed: 3.20180807a.0ubuntu0.18.04.1
Candidate: 3.20180807a.0ubuntu0.18.04.1
Version table:
   *** 3.20180807a.0ubuntu0.18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20180312.0~ubuntu18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  Version:
  Ubuntu 4.15.0-42.45-generic 4.15.18

  Error:

  [ 3136.084499] rtsx_pci :06:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
  [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1
  [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 
source:0x
  [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: 
id=00e8
  [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e8(Transmitter ID)
  [ 3136.085694] pcieport :00:1d.0:   device [8086:a335] error 
status/mask=1101/2000
  [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First)
  [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover
  [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout  
  [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6
  [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0
  [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT  
  [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0
  [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1
  [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2
  [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1
  [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2
  [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1
  [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2
  [ 3166.625860] iwlwifi :00:14.3: 0x | data3
  [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time
  [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low
  [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi
  [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1
  [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2
  [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major
  [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor
  [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version
  [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version
  [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd
  [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0
  [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1
  [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2
  [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3
  [ 3166.625944] iwlwifi :00:14.3: 0x | isr4
  [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id
  [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event
  [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control
  [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration
  [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid
  [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match
  [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel
  [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp
  [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler
  [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7
  [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT
  [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1
  [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2
  [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1
  [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2
  [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1
  [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2
  [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [ 3166.626194] iwlwifi :00:14.3: 

[Kernel-packages] [Bug 1808886] ProcModules.txt

[jasd666]

apport information

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

Title:
  Microcode SW error detected. Restarting 0x0.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  intel-microcode:
Installed: 3.20180807a.0ubuntu0.18.04.1
Candidate: 3.20180807a.0ubuntu0.18.04.1
Version table:
   *** 3.20180807a.0ubuntu0.18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20180312.0~ubuntu18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  Version:
  Ubuntu 4.15.0-42.45-generic 4.15.18

  Error:

  [ 3136.084499] rtsx_pci :06:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
  [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1
  [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 
source:0x
  [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: 
id=00e8
  [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e8(Transmitter ID)
  [ 3136.085694] pcieport :00:1d.0:   device [8086:a335] error 
status/mask=1101/2000
  [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First)
  [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover
  [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout  
  [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6
  [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0
  [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT  
  [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0
  [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1
  [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2
  [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1
  [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2
  [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1
  [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2
  [ 3166.625860] iwlwifi :00:14.3: 0x | data3
  [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time
  [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low
  [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi
  [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1
  [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2
  [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major
  [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor
  [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version
  [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version
  [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd
  [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0
  [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1
  [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2
  [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3
  [ 3166.625944] iwlwifi :00:14.3: 0x | isr4
  [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id
  [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event
  [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control
  [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration
  [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid
  [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match
  [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel
  [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp
  [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler
  [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7
  [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT
  [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1
  [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2
  [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1
  [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2
  [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1
  [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2
  [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [ 3166.626194] iwlwifi :00:14.3: 0x

[Kernel-packages] [Bug 1808886] CRDA.txt

[jasd666]

apport information

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

Title:
  Microcode SW error detected. Restarting 0x0.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  intel-microcode:
Installed: 3.20180807a.0ubuntu0.18.04.1
Candidate: 3.20180807a.0ubuntu0.18.04.1
Version table:
   *** 3.20180807a.0ubuntu0.18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20180312.0~ubuntu18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  Version:
  Ubuntu 4.15.0-42.45-generic 4.15.18

  Error:

  [ 3136.084499] rtsx_pci :06:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
  [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1
  [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 
source:0x
  [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: 
id=00e8
  [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e8(Transmitter ID)
  [ 3136.085694] pcieport :00:1d.0:   device [8086:a335] error 
status/mask=1101/2000
  [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First)
  [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover
  [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout  
  [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6
  [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0
  [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT  
  [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0
  [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1
  [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2
  [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1
  [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2
  [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1
  [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2
  [ 3166.625860] iwlwifi :00:14.3: 0x | data3
  [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time
  [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low
  [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi
  [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1
  [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2
  [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major
  [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor
  [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version
  [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version
  [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd
  [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0
  [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1
  [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2
  [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3
  [ 3166.625944] iwlwifi :00:14.3: 0x | isr4
  [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id
  [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event
  [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control
  [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration
  [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid
  [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match
  [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel
  [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp
  [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler
  [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7
  [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT
  [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1
  [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2
  [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1
  [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2
  [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1
  [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2
  [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [ 3166.626194] iwlwifi :00:14.3: 0x0022 | umac

[Kernel-packages] [Bug 1808886] IwConfig.txt

[jasd666]

apport information

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

Title:
  Microcode SW error detected. Restarting 0x0.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  intel-microcode:
Installed: 3.20180807a.0ubuntu0.18.04.1
Candidate: 3.20180807a.0ubuntu0.18.04.1
Version table:
   *** 3.20180807a.0ubuntu0.18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20180312.0~ubuntu18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  Version:
  Ubuntu 4.15.0-42.45-generic 4.15.18

  Error:

  [ 3136.084499] rtsx_pci :06:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
  [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1
  [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 
source:0x
  [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: 
id=00e8
  [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e8(Transmitter ID)
  [ 3136.085694] pcieport :00:1d.0:   device [8086:a335] error 
status/mask=1101/2000
  [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First)
  [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover
  [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout  
  [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6
  [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0
  [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT  
  [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0
  [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1
  [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2
  [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1
  [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2
  [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1
  [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2
  [ 3166.625860] iwlwifi :00:14.3: 0x | data3
  [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time
  [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low
  [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi
  [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1
  [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2
  [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major
  [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor
  [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version
  [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version
  [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd
  [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0
  [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1
  [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2
  [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3
  [ 3166.625944] iwlwifi :00:14.3: 0x | isr4
  [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id
  [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event
  [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control
  [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration
  [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid
  [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match
  [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel
  [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp
  [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler
  [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7
  [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT
  [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1
  [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2
  [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1
  [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2
  [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1
  [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2
  [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [ 3166.626194] iwlwifi :00:14.3: 0x00

[Kernel-packages] [Bug 1808886] ProcCpuinfo.txt

[jasd666]

apport information

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

Title:
  Microcode SW error detected. Restarting 0x0.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  intel-microcode:
Installed: 3.20180807a.0ubuntu0.18.04.1
Candidate: 3.20180807a.0ubuntu0.18.04.1
Version table:
   *** 3.20180807a.0ubuntu0.18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20180312.0~ubuntu18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  Version:
  Ubuntu 4.15.0-42.45-generic 4.15.18

  Error:

  [ 3136.084499] rtsx_pci :06:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
  [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1
  [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 
source:0x
  [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: 
id=00e8
  [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e8(Transmitter ID)
  [ 3136.085694] pcieport :00:1d.0:   device [8086:a335] error 
status/mask=1101/2000
  [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First)
  [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover
  [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout  
  [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6
  [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0
  [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT  
  [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0
  [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1
  [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2
  [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1
  [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2
  [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1
  [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2
  [ 3166.625860] iwlwifi :00:14.3: 0x | data3
  [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time
  [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low
  [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi
  [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1
  [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2
  [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major
  [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor
  [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version
  [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version
  [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd
  [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0
  [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1
  [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2
  [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3
  [ 3166.625944] iwlwifi :00:14.3: 0x | isr4
  [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id
  [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event
  [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control
  [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration
  [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid
  [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match
  [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel
  [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp
  [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler
  [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7
  [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT
  [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1
  [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2
  [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1
  [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2
  [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1
  [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2
  [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [ 3166.626194] iwlwifi :00:14.3: 0x

[Kernel-packages] [Bug 1808886] PulseList.txt

[jasd666]

apport information

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

Title:
  Microcode SW error detected. Restarting 0x0.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  intel-microcode:
Installed: 3.20180807a.0ubuntu0.18.04.1
Candidate: 3.20180807a.0ubuntu0.18.04.1
Version table:
   *** 3.20180807a.0ubuntu0.18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20180312.0~ubuntu18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  Version:
  Ubuntu 4.15.0-42.45-generic 4.15.18

  Error:

  [ 3136.084499] rtsx_pci :06:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
  [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1
  [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 
source:0x
  [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: 
id=00e8
  [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e8(Transmitter ID)
  [ 3136.085694] pcieport :00:1d.0:   device [8086:a335] error 
status/mask=1101/2000
  [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First)
  [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover
  [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout  
  [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6
  [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0
  [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT  
  [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0
  [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1
  [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2
  [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1
  [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2
  [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1
  [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2
  [ 3166.625860] iwlwifi :00:14.3: 0x | data3
  [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time
  [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low
  [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi
  [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1
  [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2
  [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major
  [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor
  [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version
  [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version
  [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd
  [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0
  [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1
  [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2
  [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3
  [ 3166.625944] iwlwifi :00:14.3: 0x | isr4
  [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id
  [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event
  [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control
  [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration
  [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid
  [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match
  [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel
  [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp
  [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler
  [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7
  [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT
  [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1
  [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2
  [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1
  [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2
  [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1
  [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2
  [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [ 3166.626194] iwlwifi :00:14.3: 0x

[Kernel-packages] [Bug 1808886] ProcInterrupts.txt

[jasd666]

apport information

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

Title:
  Microcode SW error detected. Restarting 0x0.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  intel-microcode:
Installed: 3.20180807a.0ubuntu0.18.04.1
Candidate: 3.20180807a.0ubuntu0.18.04.1
Version table:
   *** 3.20180807a.0ubuntu0.18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20180312.0~ubuntu18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  Version:
  Ubuntu 4.15.0-42.45-generic 4.15.18

  Error:

  [ 3136.084499] rtsx_pci :06:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
  [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1
  [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 
source:0x
  [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: 
id=00e8
  [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e8(Transmitter ID)
  [ 3136.085694] pcieport :00:1d.0:   device [8086:a335] error 
status/mask=1101/2000
  [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First)
  [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover
  [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout  
  [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6
  [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0
  [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT  
  [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0
  [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1
  [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2
  [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1
  [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2
  [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1
  [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2
  [ 3166.625860] iwlwifi :00:14.3: 0x | data3
  [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time
  [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low
  [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi
  [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1
  [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2
  [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major
  [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor
  [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version
  [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version
  [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd
  [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0
  [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1
  [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2
  [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3
  [ 3166.625944] iwlwifi :00:14.3: 0x | isr4
  [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id
  [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event
  [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control
  [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration
  [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid
  [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match
  [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel
  [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp
  [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler
  [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7
  [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT
  [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1
  [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2
  [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1
  [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2
  [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1
  [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2
  [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [ 3166.626194] iwlwifi :00:14

[Kernel-packages] [Bug 1808886] ProcCpuinfoMinimal.txt

[jasd666]

apport information

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

Title:
  Microcode SW error detected. Restarting 0x0.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  intel-microcode:
Installed: 3.20180807a.0ubuntu0.18.04.1
Candidate: 3.20180807a.0ubuntu0.18.04.1
Version table:
   *** 3.20180807a.0ubuntu0.18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20180312.0~ubuntu18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  Version:
  Ubuntu 4.15.0-42.45-generic 4.15.18

  Error:

  [ 3136.084499] rtsx_pci :06:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
  [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1
  [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 
source:0x
  [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: 
id=00e8
  [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e8(Transmitter ID)
  [ 3136.085694] pcieport :00:1d.0:   device [8086:a335] error 
status/mask=1101/2000
  [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First)
  [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover
  [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout  
  [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6
  [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0
  [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT  
  [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0
  [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1
  [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2
  [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1
  [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2
  [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1
  [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2
  [ 3166.625860] iwlwifi :00:14.3: 0x | data3
  [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time
  [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low
  [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi
  [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1
  [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2
  [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major
  [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor
  [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version
  [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version
  [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd
  [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0
  [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1
  [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2
  [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3
  [ 3166.625944] iwlwifi :00:14.3: 0x | isr4
  [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id
  [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event
  [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control
  [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration
  [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid
  [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match
  [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel
  [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp
  [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler
  [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7
  [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT
  [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1
  [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2
  [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1
  [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2
  [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1
  [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2
  [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [ 3166.626194] iwlwifi 00

[Kernel-packages] [Bug 1808886] ProcEnviron.txt

[jasd666]

apport information

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

Title:
  Microcode SW error detected. Restarting 0x0.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  intel-microcode:
Installed: 3.20180807a.0ubuntu0.18.04.1
Candidate: 3.20180807a.0ubuntu0.18.04.1
Version table:
   *** 3.20180807a.0ubuntu0.18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20180312.0~ubuntu18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  Version:
  Ubuntu 4.15.0-42.45-generic 4.15.18

  Error:

  [ 3136.084499] rtsx_pci :06:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
  [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1
  [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 
source:0x
  [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: 
id=00e8
  [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e8(Transmitter ID)
  [ 3136.085694] pcieport :00:1d.0:   device [8086:a335] error 
status/mask=1101/2000
  [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First)
  [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover
  [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout  
  [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6
  [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0
  [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT  
  [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0
  [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1
  [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2
  [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1
  [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2
  [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1
  [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2
  [ 3166.625860] iwlwifi :00:14.3: 0x | data3
  [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time
  [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low
  [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi
  [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1
  [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2
  [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major
  [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor
  [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version
  [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version
  [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd
  [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0
  [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1
  [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2
  [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3
  [ 3166.625944] iwlwifi :00:14.3: 0x | isr4
  [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id
  [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event
  [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control
  [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration
  [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid
  [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match
  [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel
  [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp
  [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler
  [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7
  [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT
  [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1
  [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2
  [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1
  [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2
  [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1
  [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2
  [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [ 3166.626194] iwlwifi :00:14.3: 0x

[Kernel-packages] [Bug 1808886] Lspci.txt

[jasd666]

apport information

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

Title:
  Microcode SW error detected. Restarting 0x0.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  intel-microcode:
Installed: 3.20180807a.0ubuntu0.18.04.1
Candidate: 3.20180807a.0ubuntu0.18.04.1
Version table:
   *** 3.20180807a.0ubuntu0.18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20180312.0~ubuntu18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  
  Version:
  Ubuntu 4.15.0-42.45-generic 4.15.18

  Error:

  [ 3136.084499] rtsx_pci :06:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
  [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1
  [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 
source:0x
  [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: 
id=00e8
  [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e8(Transmitter ID)
  [ 3136.085694] pcieport :00:1d.0:   device [8086:a335] error 
status/mask=1101/2000
  [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First)
  [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover
  [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout  
  [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6
  [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0
  [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT  
  [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0
  [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1
  [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2
  [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1
  [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2
  [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1
  [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2
  [ 3166.625860] iwlwifi :00:14.3: 0x | data3
  [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time
  [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low
  [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi
  [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1
  [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2
  [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major
  [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor
  [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version
  [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version
  [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd
  [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0
  [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1
  [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2
  [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3
  [ 3166.625944] iwlwifi :00:14.3: 0x | isr4
  [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id
  [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event
  [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control
  [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration
  [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid
  [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match
  [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel
  [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp
  [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler
  [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7
  [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT
  [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1
  [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2
  [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1
  [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2
  [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1
  [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2
  [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [ 3166.626194] iwlwifi :00:14.3: 0x0022 | um

[Kernel-packages] [Bug 1808886] Re: Microcode SW error detected. Restarting 0x0.

[jasd666]

apport information

** Tags added: apport-collected bionic

** Description changed:

  intel-microcode:
Installed: 3.20180807a.0ubuntu0.18.04.1
Candidate: 3.20180807a.0ubuntu0.18.04.1
Version table:
   *** 3.20180807a.0ubuntu0.18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.20180312.0~ubuntu18.04.1 500
  500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  
  
  Version:
  Ubuntu 4.15.0-42.45-generic 4.15.18
  
  Error:
  
  [ 3136.084499] rtsx_pci :06:00.0: VPD access failed.  This is likely a 
firmware bug on this device.  Contact the card vendor for a firmware update
  [ 3136.085614] r8169 :06:00.1: invalid short VPD tag 00 at offset 1
  [ 3136.085624] dpc :00:1d.0:pcie010: DPC containment event, status:0x1f00 
source:0x
  [ 3136.085662] pcieport :00:1d.0: AER: Multiple Corrected error received: 
id=00e8
  [ 3136.085683] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e8(Transmitter ID)
  [ 3136.085694] pcieport :00:1d.0:   device [8086:a335] error 
status/mask=1101/2000
  [ 3136.085701] pcieport :00:1d.0:[ 0] Receiver Error (First)
  [ 3136.085722] pcieport :00:1d.0:[ 8] RELAY_NUM Rollover
  [ 3136.085741] pcieport :00:1d.0:[12] Replay Timer Timeout  
  [ 3166.625429] iwlwifi :00:14.3: Microcode SW error detected. Restarting 
0x0.
  [ 3166.625797] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.625805] iwlwifi :00:14.3: Status: 0x0100, count: 6
  [ 3166.625810] iwlwifi :00:14.3: Loaded firmware version: 34.0.0
  [ 3166.625817] iwlwifi :00:14.3: 0x1007 | ADVANCED_SYSASSERT  
  [ 3166.625823] iwlwifi :00:14.3: 0x0080A614 | trm_hw_status0
  [ 3166.625828] iwlwifi :00:14.3: 0x | trm_hw_status1
  [ 3166.625834] iwlwifi :00:14.3: 0x00456D06 | branchlink2
  [ 3166.625839] iwlwifi :00:14.3: 0x0046064A | interruptlink1
  [ 3166.625844] iwlwifi :00:14.3: 0x | interruptlink2
  [ 3166.625850] iwlwifi :00:14.3: 0x00030400 | data1
  [ 3166.625855] iwlwifi :00:14.3: 0x040B | data2
  [ 3166.625860] iwlwifi :00:14.3: 0x | data3
  [ 3166.625866] iwlwifi :00:14.3: 0xAD418817 | beacon time
  [ 3166.625871] iwlwifi :00:14.3: 0x6A2317EF | tsf low
  [ 3166.625876] iwlwifi :00:14.3: 0x0184 | tsf hi
  [ 3166.625881] iwlwifi :00:14.3: 0x | time gp1
  [ 3166.625887] iwlwifi :00:14.3: 0x0ADF380D | time gp2
  [ 3166.625892] iwlwifi :00:14.3: 0x0001 | uCode revision type
  [ 3166.625897] iwlwifi :00:14.3: 0x0022 | uCode version major
  [ 3166.625903] iwlwifi :00:14.3: 0x | uCode version minor
  [ 3166.625908] iwlwifi :00:14.3: 0x0312 | hw version
  [ 3166.625913] iwlwifi :00:14.3: 0x00C89008 | board version
  [ 3166.625918] iwlwifi :00:14.3: 0x0A9E001C | hcmd
  [ 3166.625924] iwlwifi :00:14.3: 0xA4022002 | isr0
  [ 3166.625929] iwlwifi :00:14.3: 0x0100 | isr1
  [ 3166.625934] iwlwifi :00:14.3: 0x08001802 | isr2
  [ 3166.625939] iwlwifi :00:14.3: 0x0041B8C5 | isr3
  [ 3166.625944] iwlwifi :00:14.3: 0x | isr4
  [ 3166.625950] iwlwifi :00:14.3: 0x00EC019C | last cmd Id
  [ 3166.625955] iwlwifi :00:14.3: 0x | wait_event
  [ 3166.625960] iwlwifi :00:14.3: 0x0080 | l2p_control
  [ 3166.625965] iwlwifi :00:14.3: 0x00012034 | l2p_duration
  [ 3166.625971] iwlwifi :00:14.3: 0x003F | l2p_mhvalid
  [ 3166.625976] iwlwifi :00:14.3: 0x00CE | l2p_addr_match
  [ 3166.625981] iwlwifi :00:14.3: 0x000F | lmpm_pmg_sel
  [ 3166.625987] iwlwifi :00:14.3: 0x12111721 | timestamp
  [ 3166.625992] iwlwifi :00:14.3: 0x9090 | flow_handler
  [ 3166.626141] iwlwifi :00:14.3: Start IWL Error Log Dump:
  [ 3166.626147] iwlwifi :00:14.3: Status: 0x0100, count: 7
  [ 3166.626152] iwlwifi :00:14.3: 0x0070 | ADVANCED_SYSASSERT
  [ 3166.626158] iwlwifi :00:14.3: 0x | umac branchlink1
  [ 3166.626163] iwlwifi :00:14.3: 0xC0087D08 | umac branchlink2
  [ 3166.626168] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink1
  [ 3166.626173] iwlwifi :00:14.3: 0xC0083A08 | umac interruptlink2
  [ 3166.626178] iwlwifi :00:14.3: 0x0800 | umac data1
  [ 3166.626184] iwlwifi :00:14.3: 0xC0083A08 | umac data2
  [ 3166.626189] iwlwifi :00:14.3: 0xDEADBEEF | umac data3
  [ 3166.626194] iwlwifi :00:14.3: 0x0022 | umac major
  [ 3166.626199] iwlwifi :00:14.3: 0x | umac minor
  [ 3166.626204] iwlwifi :00:14.3: 0xC088628C | frame pointer
  [ 3166.626210] iwlwifi :00:14.3: 0xC088628C | stack pointer
  [ 3166.626215] iwlwifi :00:14.3: 0x00EC019C | last host cmd
  [ 3166.626220] iwlwifi :00:14.3: 0x | isr st

[Kernel-packages] [Bug 1806534] Re: Fix USB2 device wrongly detected as USB1

[Kleber Sacilotto de Souza]

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

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

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

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

** Changed in: linux (Ubuntu Cosmic)
   Status: New => 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/1806534

Title:
  Fix USB2 device wrongly detected as USB1

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

Bug description:
  [Impact]
  USB 2 device may come up as USB 1 if a connection to a USB 1 device is 
followed by another connection to a USB 2 device, the link will come up as USB 
1 for the USB 2 device.

  [Test Case]
  Insert 2 USB devices and they shall appear on lsusb with correct address

  [Fix]
  11644a76 xhci: Add quirk to workaround the errata seen on Cavium Thunder-X2 
Soc

  [Regression Risk]
  It only affect device PCI_VENDOR_ID_CAVIUM:0x9026 and 
PCI_VENDOR_ID_BROADCOM:0x9026.
  Low regression to other device.

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

[Joshua R. Poulson]

Why is this one blocked? I signed off on the 12th.

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

Title:
  linux-azure: 4.15.0-1036.38~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

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

[Joshua R. Poulson]

Why is this one delayed? I signed off on the 12th.

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

Title:
  linux-azure: 4.15.0-1036.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

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

[Joshua R. Poulson]

Test results look good.

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: Confirmed => Fix Released

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

Title:
  linux-azure: 4.18.0-1007.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 07:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release
stakeholder-signoff: Pending -- waiting for signoff

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806422/+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 1806670] Re: linux-azure: 4.15.0-1036.38~14.04.2 -proposed tracker

[Joshua R. Poulson]

Why is this one blocked? I signed off on the 12th.

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

Title:
  linux-azure: 4.15.0-1036.38~14.04.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

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

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

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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1781533

Title:
  SATA device is not going to DEVSLP

Status in HWE Next:
  Triaged
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  In Progress
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  In Progress
Status in linux-oem source package in Cosmic:
  Invalid

Bug description:
  [Impact]
  Any of the platforms we’ve been seeing SATA problems not going to deepest 
state leads to other devices not getting there during long idle or s2idle. And 
it also prevents the system from entering deeper PC state other than PC3.

  [Fix]
  Suggested from Intel and Dell to contains the following 4 commits,
  and all of 4 commits are in v4.19-rc1
  https://patchwork.kernel.org/patch/10502285/
  https://patchwork.kernel.org/patch/10502287/
  https://patchwork.kernel.org/patch/10535781/
  https://patchwork.kernel.org/patch/10535783/

  [Test]
  Verified the power consumption on some new platforms, it improves the SATA 
HDD power consumption around 0.5w during long idle.

  [Regression Potential]
  Low, the DEVSLP function is already validated when shipped with SLP_S0
  support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1781533/+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 1806532] Re: The line-out on the Dell Dock station can't work

[Brian Murray]

Hello Hui, or anyone else affected,

Accepted alsa-lib into cosmic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/alsa-
lib/1.1.6-1ubuntu1.1 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.

** Changed in: alsa-lib (Ubuntu Cosmic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-cosmic

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

Title:
  The line-out on the Dell Dock station can't work

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  New
Status in alsa-lib source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback
  devices, one is headphone, the other is line-out, but there is no UCM for
  these docks yet, so the pluseaudio only can handle the 1st playback device,
  need us to add the UCM for them, before adding UCM, we need to set the
  longname of the sound card in the linux kernel.

  [Fix]
  For Linux kernel: Cherry-picked 3 upstream patches, these patches add the 
longname of the sound card for the dock station.

  For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will
  add ucm configuration files for Dell WD15&19, and change the SPDIF conf
  in the USB-AUDIO.conf.

  [Test Case]
  Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from
  UI, and play sound via these devices

  [Regression Potential]
  Very low, these patches come from upstream, and the change is only specific
  to WD15 and WD19 dock station.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1806532/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[mariana]

I have the same problem very often during a day on a Lenovo ThinkCentre
M900 (see specs below).

Often this problem is preceded by Chrome tabs blinking or blacking out
but I can't be sure it is a related problem. In those cases, the only
solution is to kill Chrome and restart the application.

When Ubuntu freezes it starts with either a frozen cursor or unable to
use the cursor anywhere. Other times Ubuntu becomes very slow before
freezing.

product: 10FCS22R00 (LENOVO_MT_10FC_BU_LENOVO_FM_ThinkCentre M900)
   product: 30BC
  product: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
 product: M378A1K43CB2-CRC
 product: M378A1K43CB2-CRC
  product: Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host 
Bridge/DRAM Registers
 product: Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe 
Controller (x16)
product: GK208B [GeForce GT 720]
product: GK208 HDMI/DP Audio Controller
 product: 100 Series/C230 Series Chipset Family USB 3.0 xHCI 
Controller
 product: 100 Series/C230 Series Chipset Family MEI Controller #1
 product: Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA 
Controller [AHCI Mode]
 product: Q170 Chipset LPC/eSPI Controller
 product: 100 Series/C230 Series Chipset Family Power Management 
Controller
 product: 100 Series/C230 Series Chipset Family HD Audio Controller
 product: 100 Series/C230 Series Chipset Family SMBus
 product: Ethernet Connection (2) I219-LM
 product: SanDisk SD8SB8U5
 product: DVD-RW DH16AFSH
 product: BUP Slim RD
   product: To Be Filled By O.E.M.

** Attachment added: "Screenshot from 2018-12-18 09-42-02.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+attachment/5223255/+files/Screenshot%20from%202018-12-18%2009-42-02.png

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  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:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash 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
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1798961/+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 1781533] Re: SATA device is not going to DEVSLP

[Kleber Sacilotto de Souza]

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

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

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

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

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

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

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

** Changed in: linux-oem (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: linux-oem (Ubuntu Cosmic)
   Status: New => Invalid

** Changed in: linux (Ubuntu Cosmic)
   Status: Fix Committed => In Progress

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

Title:
  SATA device is not going to DEVSLP

Status in HWE Next:
  Triaged
Status in OEM Priority Project:
  Triaged
Status in linux package in Ubuntu:
  New
Status in linux-oem package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  In Progress
Status in linux-oem source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  In Progress
Status in linux-oem source package in Cosmic:
  Invalid

Bug description:
  [Impact]
  Any of the platforms we’ve been seeing SATA problems not going to deepest 
state leads to other devices not getting there during long idle or s2idle. And 
it also prevents the system from entering deeper PC state other than PC3.

  [Fix]
  Suggested from Intel and Dell to contains the following 4 commits,
  and all of 4 commits are in v4.19-rc1
  https://patchwork.kernel.org/patch/10502285/
  https://patchwork.kernel.org/patch/10502287/
  https://patchwork.kernel.org/patch/10535781/
  https://patchwork.kernel.org/patch/10535783/

  [Test]
  Verified the power consumption on some new platforms, it improves the SATA 
HDD power consumption around 0.5w during long idle.

  [Regression Potential]
  Low, the DEVSLP function is already validated when shipped with SLP_S0
  support.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1781533/+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 1762385] Re: dell_wmi: Unknown key codes

[Tom]

I still get this error in Cosmic on a Dell M6500.

The M6500 does not have a keyboard RFKILL shortcut - in only has a
physical switch. That switch correctly enables/disables WiFi.

Is this the same bug?

Dec 18 09:04:28 localhost kernel: [ 2706.037523] dell_wmi: Unknown key with 
type 0x0011 and code 0xffd0 pressed
Dec 18 09:04:28 localhost kernel: [ 2706.037526] dell_wmi: Unknown key with 
type 0x0011 and code 0xffd1 pressed
Dec 18 09:04:28 localhost kernel: [ 2706.037527] dell_wmi: Unknown key with 
type 0x0011 and code 0xffd0 pressed

Note that I never use the Fn-keys, so I have no idea which key(s) it
would be complaining about.

$ uname -a
Linux DellLaptop 4.18.0-12-generic #13-Ubuntu SMP Wed Nov 14 15:17:05 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

$ cat os-release 
NAME="Ubuntu"
VERSION="18.10 (Cosmic Cuttlefish)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.10"
VERSION_ID="18.10"
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
VERSION_CODENAME=cosmic
UBUNTU_CODENAME=cosmic

Here is the output from using the physical switch:

Dec 18 11:24:13 localhost kernel: [11090.779775] atkbd serio0: Unknown key 
pressed (translated set 2, code 0x88 on isa0060/serio0).
Dec 18 11:24:13 localhost kernel: [11090.779781] atkbd serio0: Use 'setkeycodes 
e008 ' to make it known.
Dec 18 11:24:13 localhost kernel: [11090.779888] iwlwifi :0c:00.0: RF_KILL 
bit toggled to disable radio.
Dec 18 11:24:13 localhost kernel: [11090.779899] iwlwifi :0c:00.0: 
reporting RF_KILL (radio disabled)
Dec 18 11:24:13 localhost kernel: [11090.780076] wlp12s0: deauthenticating from 
24:b6:57:f9:c6:9e by local choice (Reason: 3=DEAUTH_LEAVING)
Dec 18 11:24:13 localhost kernel: [11090.780986] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.780991] wlp12s0: HW problem - can not 
stop rx aggregation for 24:b6:57:f9:c6:9e tid 0
Dec 18 11:24:13 localhost kernel: [11090.781003] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781011] wlp12s0: HW problem - can not 
stop rx aggregation for 24:b6:57:f9:c6:9e tid 1
Dec 18 11:24:13 localhost kernel: [11090.781019] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781023] wlp12s0: HW problem - can not 
stop rx aggregation for 24:b6:57:f9:c6:9e tid 2
Dec 18 11:24:13 localhost kernel: [11090.781028] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781031] wlp12s0: HW problem - can not 
stop rx aggregation for 24:b6:57:f9:c6:9e tid 3
Dec 18 11:24:13 localhost kernel: [11090.781197] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781202] wlp12s0: failed to remove key 
(0, 24:b6:57:f9:c6:9e) from hardware (-5)
Dec 18 11:24:13 localhost kernel: [11090.781359] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781366] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781378] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781387] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781419] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781433] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781874] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.781882] wlp12s0: failed to remove key 
(1, ff:ff:ff:ff:ff:ff) from hardware (-5)
Dec 18 11:24:13 localhost kernel: [11090.782592] iwlwifi :0c:00.0: Not 
sending command - RF KILL
Dec 18 11:24:13 localhost kernel: [11090.795404] iwlwifi :0c:00.0: RF_KILL 
bit toggled to disable radio.
Dec 18 11:24:13 localhost wpa_supplicant[1107]: rfkill: WLAN hard blocked
Dec 18 11:24:13 localhost NetworkManager[1109]:   [1545150253.0043] 
sup-iface[0x557818a4da10,wlp12s0]: connection disconnected (reason -3)
Dec 18 11:24:13 localhost wpa_supplicant[1107]: wlp12s0: 
CTRL-EVENT-DISCONNECTED bssid=24:b6:57:f9:c6:9e reason=3 locally_generated=1
Dec 18 11:24:13 localhost systemd[1]: Starting Load/Save RF Kill Switch 
Status...
Dec 18 11:24:13 localhost avahi-daemon[1078]: Interface wlp12s0.IPv6 no longer 
relevant for mDNS.
Dec 18 11:24:13 localhost NetworkManager[1109]:   [1545150253.0065] 
manager: rfkill: WiFi now disabled by radio killswitch
Dec 18 11:24:13 localhost avahi-daemon[1078]: Leaving mDNS multicast group on 
interface wlp12s0.IPv6 with address fe80::44c3:6970:aa31:f9a2.
Dec 18 11:24:13 localhost NetworkManager[1109]:   [1545150253.0069] 
device (wlp12s0): state change: activated -> unavailable (reason 'none', 
sys-iface-state: 'managed')
Dec 18 11:24:13 localho

[Kernel-packages] [Bug 1765660] Re: Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid structure member offset" in crash prompt.

[Brian Murray]

** Description changed:

  [Impact]
  Some analysis won't be possible on new kernels. In this case, ipcs command 
could not be used with the bionic GA kernel on ppc64le.
  
  [Test Case]
  The ipcs command has been run after the fix was applied to crash, on a live 
amd64 system, with success.
- More tests have been done on amd64 and ppc64el, including memory commands, bt.
+ More tests will be done with the version of the package from -proposed on 
amd64 and ppc64el, including memory commands, and bt.
  
  [Regression Potential]
- New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.
+ New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing is desirable.
  
  In case of regressions, analysis of kernel dumps will require that the
  crash file be moved to a system where crash doesn't have the regression.
  But live analysis won't be possible in that case.
  
  -
  
  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2018-03-29 01:14:47 ==
  ---Problem Description---
  
  Ubuntu 18.04: "ipcs" command fails with error "invalid structure member
  offset" in crash prompt.
  
  ---Environment--
  
  System Name :  ltc-briggs2
  Model/Type  :  P8
  Platform:  BML
  
  ---Uname output---
  
  root@ltc-briggs2:~# uname -a
  Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
  
  ---Steps to reproduce--
  
  1. Configure kdump.
  2. Trigger crash
  3. run crash on captured dump
  
  ---Logs
  
  root@ltc-briggs2:~# dpkg -l|grep makedumpfile
  ii  makedumpfile   1:1.6.3-1  
  ppc64el  VMcore extraction tool
  root@ltc-briggs2:~# dpkg -l|grep crash
  ii  apport 2.20.9-0ubuntu1
  all  automatically generate crash reports for debugging
  ii  crash  7.2.1-1
  ppc64el  kernel debugging utility, allowing gdb like syntax
  ii  kdump-tools1:1.6.3-1  
  ppc64el  scripts and tools for automating kdump (Linux crash dumps)
  ii  python3-apport 2.20.9-0ubuntu1
  all  Python 3 library for Apport crash report handling
  root@ltc-briggs2:~# dpkg -l|grep kexec
  ii  kexec-tools1:2.0.16-1ubuntu1  
  ppc64el  tools to support fast kexec reboots
  root@ltc-briggs2:~#
  
  .0-13-generic dump.201803272257 03272257# crash
  /usr/lib/debug/boot/vmlinux-4.15.
  
  crash 7.2.1
  Copyright (C) 2002-2017  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.
  
  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...
  
    KERNEL: /usr/lib/debug/boot/vmlinux-4.15.0-13-generic
  DUMPFILE: dump.201803272257  [PARTIAL DUMP]
  CPUS: 160
  DATE: Tue Mar 27 22:56:58 2018
    UPTIME: 00:04:07
  LOAD AVERAGE: 1.06, 0.53, 0.20
     TASKS: 1734
  NODENAME: ltc-briggs2
   RELEASE: 4.15.0-13-generic
   VERSION: #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018
   MACHINE: ppc64le  (2926 Mhz)
    MEMORY: 512 GB
     PANIC: "sysrq: SysRq : Trigger a crash"
   PID: 7420
   COMMAND: "bash"
  TASK: c03e56c7c600  [THREAD_INFO: c03e56cb]
   CPU: 41
     STATE: TASK_RUNNING (SYSRQ)
  
  crash> ?
  
  *  files  mach   repeat timer
  alias  foreachmodrunq   tree
  ascii  fuser  mount  search union
  bt gdbnetsetvm
  btop   help   p  sigvtop
  devipcs   ps struct waitq
  disirqpte   

[Kernel-packages] [Bug 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

[Thadeu Lima de Souza Cascardo]

In summary, the xenial version should be able to analyze up to a 4.15
kernel. This is now about bringing that same version to bionic, so other
bugs in analyzing a 4.15 kernel are fixed.

Cascardo.

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Fix Released
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  In Progress

Bug description:
  [Impact]
  It won't be possible to analyze dumps produced by newer kernels (hwe on 
xenial, for example).

  [Test Case]
  Tested that this version of crash can analyze both GA (4.4) and hwe (4.15) 
kernels.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.


  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)

  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8001-22C

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows

  Once you generate the kdump
  use crash to analyze the vmcore and we get this error

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  WARNING: cannot access vmalloc'd module memory

  crash: invalid structure member offset: thread_info_task
     FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

    100833e0: (undetermined)
    1017d220: OFFSET_verify+80
    1011552c: task_init+5084
    1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

    commit c8178eca9c74f81a7f803a58d339635cc152e8d9
    Author: Dave Anderson 
    Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746088/+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 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

[Terry Rudd]

On 12/18/2018 06:36 AM, Thadeu Lima de Souza Cascardo wrote:
> Subscribed SRU team for their visibility, will ping them on IRC.
> 
So is this planned for SRU 19.04 or just fixed and enabled to be pulled
in for SRU?

Terry

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Fix Released
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  In Progress

Bug description:
  [Impact]
  It won't be possible to analyze dumps produced by newer kernels (hwe on 
xenial, for example).

  [Test Case]
  Tested that this version of crash can analyze both GA (4.4) and hwe (4.15) 
kernels.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.


  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)

  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8001-22C

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows

  Once you generate the kdump
  use crash to analyze the vmcore and we get this error

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  WARNING: cannot access vmalloc'd module memory

  crash: invalid structure member offset: thread_info_task
     FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

    100833e0: (undetermined)
    1017d220: OFFSET_verify+80
    1011552c: task_init+5084
    1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

    commit c8178eca9c74f81a7f803a58d339635cc152e8d9
    Author: Dave Anderson 
    Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746088/+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 1765660] Re: Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid structure member offset" in crash prompt.

[Terry Rudd]

On 12/18/2018 06:35 AM, Thadeu Lima de Souza Cascardo wrote:
> Can someone from the SRU team approve this package in the queue?
> 
> Cascardo.
> 
Thank you Thadeu!

Terry

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

Title:
  Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid
  structure member offset" in crash prompt.

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Won't Fix
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Confirmed
Status in crash source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Some analysis won't be possible on new kernels. In this case, ipcs command 
could not be used with the bionic GA kernel on ppc64le.

  [Test Case]
  The ipcs command has been run after the fix was applied to crash, on a live 
amd64 system, with success.
  More tests have been done on amd64 and ppc64el, including memory commands, bt.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.

  In case of regressions, analysis of kernel dumps will require that the
  crash file be moved to a system where crash doesn't have the
  regression. But live analysis won't be possible in that case.

  -

  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2018-03-29 01:14:47 ==
  ---Problem Description---

  Ubuntu 18.04: "ipcs" command fails with error "invalid structure
  member offset" in crash prompt.

  ---Environment--

  System Name :  ltc-briggs2
  Model/Type  :  P8
  Platform:  BML

  ---Uname output---

  root@ltc-briggs2:~# uname -a
  Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  ---Steps to reproduce--

  1. Configure kdump.
  2. Trigger crash
  3. run crash on captured dump

  ---Logs

  root@ltc-briggs2:~# dpkg -l|grep makedumpfile
  ii  makedumpfile   1:1.6.3-1  
  ppc64el  VMcore extraction tool
  root@ltc-briggs2:~# dpkg -l|grep crash
  ii  apport 2.20.9-0ubuntu1
  all  automatically generate crash reports for debugging
  ii  crash  7.2.1-1
  ppc64el  kernel debugging utility, allowing gdb like syntax
  ii  kdump-tools1:1.6.3-1  
  ppc64el  scripts and tools for automating kdump (Linux crash dumps)
  ii  python3-apport 2.20.9-0ubuntu1
  all  Python 3 library for Apport crash report handling
  root@ltc-briggs2:~# dpkg -l|grep kexec
  ii  kexec-tools1:2.0.16-1ubuntu1  
  ppc64el  tools to support fast kexec reboots
  root@ltc-briggs2:~#

  .0-13-generic dump.201803272257 03272257# crash
  /usr/lib/debug/boot/vmlinux-4.15.

  crash 7.2.1
  Copyright (C) 2002-2017  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

    KERNEL: /usr/lib/debug/boot/vmlinux-4.15.0-13-generic
  DUMPFILE: dump.201803272257  [PARTIAL DUMP]
  CPUS: 160
  DATE: Tue Mar 27 22:56:58 2018
    UPTIME: 00:04:07
  LOAD AVERAGE: 1.06, 0.53, 0.20
     TASKS: 1734
  NODENAME: ltc-briggs2
   RELEASE: 4.15.0-13-generic
   VERSION: #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018
   MACHINE: ppc64le  (2926 Mhz)
    MEMORY: 512 GB
     PANIC: "sysrq: SysRq : Trigger a crash"
   PID: 7420
   COMMAND: "bash"
  TASK: c03e56c7c600  [THREAD_INFO: c03e56cb]
   CPU: 41
     STATE: TASK_RUNNING (

[Kernel-packages] [Bug 1807702] Re: linux-oracle: 4.15.0-1007.9 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Incomplete

** Description changed:

  This bug is for tracking the 4.15.0-1007.7 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 14. December 2018 22:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
+   automated-testing: Stalled -- testing FAILED

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

Title:
  linux-oracle: 4.15.0-1007.9 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.15.0-1007.7 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 14. December 2018 22:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED

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

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => In Progress

** Description changed:

  This bug is for tracking the 4.15.0-1007.7 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 14. December 2018 22:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress

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

Title:
  linux-oracle: 4.15.0-1007.9 -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 prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.15.0-1007.7 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 14. December 2018 22:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1807702/+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 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => In Progress

** Description changed:

  This bug is for tracking the 4.15.0-1007.7~16.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 14. December 2018 21:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress

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

Title:
  linux-oracle: 4.15.0-1007.9~16.04.1 -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 prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.15.0-1007.7~16.04.1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 14. December 2018 21:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

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

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Confirmed

** 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: 
  derivatives:
  -- swm properties --
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 10:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
+   automated-testing: Ongoing -- testing in progress

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

Title:
  linux: 4.19.0-8.9 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
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: 
  derivatives:
  -- swm properties --
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 10:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806952/+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 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

[Thadeu Lima de Souza Cascardo]

I am working on the sync/merge from Debian to Ubuntu.

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Bionic:
  New
Status in makedumpfile source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid
Status in makedumpfile source package in Cosmic:
  In Progress

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1655280/+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 1746088] Re: [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel

[Thadeu Lima de Souza Cascardo]

Subscribed SRU team for their visibility, will ping them on IRC.

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

Title:
  [Ubuntu 16.04.4] Unable to analyze the vmcore generated by kdump on
  4.13.0-26-generic kernel

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Fix Released
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  In Progress

Bug description:
  [Impact]
  It won't be possible to analyze dumps produced by newer kernels (hwe on 
xenial, for example).

  [Test Case]
  Tested that this version of crash can analyze both GA (4.4) and hwe (4.15) 
kernels.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.


  ---Problem Description---
  Unable to analyze the vmcore generated by kdump on 4.13.0-26-generic kernel 
(Ubuntu 16.04.4)

  ---uname output---
  Linux ltc-briggs1 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 21:40:36 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = 8001-22C

  ---Steps to Reproduce---
   This bug follow up bug of 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=163565
  The steps to create dump is as follows

  Once you generate the kdump
  use crash to analyze the vmcore and we get this error

  console logs ==

  root@ltc-briggs1:/var/crash/201801150227# ls
  dmesg.201801150227  vmcore.201801150227
  .0-26-generic vmcore.2018011502271150227# crash 
/usr/lib/debug/boot/vmlinux-4.13.

  crash 7.1.4
  Copyright (C) 2002-2015  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

  please wait... (gathering module symbol data)
  WARNING: cannot access vmalloc'd module memory

  crash: invalid structure member offset: thread_info_task
     FILE: task.c  LINE: 598  FUNCTION: irqstacks_init()

  [/usr/bin/crash] error trace: 1008ade0 => 1011552c => 1017d220 =>
  100833e0

    100833e0: (undetermined)
    1017d220: OFFSET_verify+80
    1011552c: task_init+5084
    1008ade0: main_loop+336

  == Comment from Hari Krishna Bathini ==

  There are quite a few commits (all available upstream) that are needed for
  crash tool to work fine. I think the right thing to do here would be to use
  the latest crash tool version 7.2.0 to go with the kernel update. Also, the
  below commit would be needed on top of 7.2.0 crash utility:

    commit c8178eca9c74f81a7f803a58d339635cc152e8d9
    Author: Dave Anderson 
    Date:   Thu Nov 9 11:39:05 2017 -0500

  Update for support of Linux 4.14 and later PPC64 kernels where the
  hash page table geometry accomodates a larger virtual address range.
  Without the patch, the virtual-to-physical translation of user space
  virtual addresses by "vm -p", "vtop", and "rd -u" may generate an
  invalid translation or otherwise fail.
  (hbath...@linux.vnet.ibm.com)

  Similar thing holds true for makedumpfile tool..

  Thanks
  Hari

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1746088/+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 1790788] Re: Customize 'crashkernel' parameter is not properly working

[Thadeu Lima de Souza Cascardo]

I am working on the merge of Debian and Ubuntu changes to Disco.

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

Title:
  Customize 'crashkernel' parameter is not properly working

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

Bug description:
  Trying to use crashdump especially in a KVM machine.
  Installation looks fine and the reboot is triggered.
  But it does not work because the kernel does not have a 'crashkernel=' 
parameter.
  Nothing in /proc/cmdline:
  $ cat /proc/cmdline 
  root=LABEL=cloudimg-rootfs

  Issue seems to be in adding the crashkernel line in this snippet:
  # Customize crashkernel= value according to architecture
  ARCH="$(arch)"
  DEF_PRESET="384M-:128M"
  case "$ARCH" in
 s390x)
HAS_CRASHKERNEL="$(grep crashkernel /etc/zipl.conf)" || true
if test -z "$HAS_CRASHKERNEL"; then
   sed -i "/parameters/{s|\"$| crashkernel=${DEF_PRESET}\"|}" 
/etc/zipl.conf
   zipl
fi
   CIO_IGNORE="$(cio_ignore -u -k)"
   sed -i "s/\#KDUMP_CMDLINE_APPEND/KDUMP_CMDLINE_APPEND/" $INITCONFFILE
   sed -i "/KDUMP_CMDLINE_APPEND/{s|\"$| ${CIO_IGNORE}\"|}" 
$INITCONFFILE
  ;;
  esac

  (especially 1st sed stmt)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1790788/+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 1765660] Re: Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid structure member offset" in crash prompt.

[Thadeu Lima de Souza Cascardo]

Can someone from the SRU team approve this package in the queue?

Cascardo.

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

Title:
  Ubuntu 18.04 [ briggs ]: "ipcs" command fails with error "invalid
  structure member offset" in crash prompt.

Status in The Ubuntu-power-systems project:
  In Progress
Status in crash package in Ubuntu:
  Fix Released
Status in crash source package in Xenial:
  Won't Fix
Status in crash source package in Artful:
  Won't Fix
Status in crash source package in Bionic:
  Confirmed
Status in crash source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Some analysis won't be possible on new kernels. In this case, ipcs command 
could not be used with the bionic GA kernel on ppc64le.

  [Test Case]
  The ipcs command has been run after the fix was applied to crash, on a live 
amd64 system, with success.
  More tests have been done on amd64 and ppc64el, including memory commands, bt.

  [Regression Potential]
  New crash versions may have bugs and some commands not work with older 
kernels. The smoke test helps a little, but more testing may be desirable.

  In case of regressions, analysis of kernel dumps will require that the
  crash file be moved to a system where crash doesn't have the
  regression. But live analysis won't be possible in that case.

  -

  == Comment: #0 - PAVITHRA R. PRAKASH <> - 2018-03-29 01:14:47 ==
  ---Problem Description---

  Ubuntu 18.04: "ipcs" command fails with error "invalid structure
  member offset" in crash prompt.

  ---Environment--

  System Name :  ltc-briggs2
  Model/Type  :  P8
  Platform:  BML

  ---Uname output---

  root@ltc-briggs2:~# uname -a
  Linux ltc-briggs2 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

  ---Steps to reproduce--

  1. Configure kdump.
  2. Trigger crash
  3. run crash on captured dump

  ---Logs

  root@ltc-briggs2:~# dpkg -l|grep makedumpfile
  ii  makedumpfile   1:1.6.3-1  
  ppc64el  VMcore extraction tool
  root@ltc-briggs2:~# dpkg -l|grep crash
  ii  apport 2.20.9-0ubuntu1
  all  automatically generate crash reports for debugging
  ii  crash  7.2.1-1
  ppc64el  kernel debugging utility, allowing gdb like syntax
  ii  kdump-tools1:1.6.3-1  
  ppc64el  scripts and tools for automating kdump (Linux crash dumps)
  ii  python3-apport 2.20.9-0ubuntu1
  all  Python 3 library for Apport crash report handling
  root@ltc-briggs2:~# dpkg -l|grep kexec
  ii  kexec-tools1:2.0.16-1ubuntu1  
  ppc64el  tools to support fast kexec reboots
  root@ltc-briggs2:~#

  .0-13-generic dump.201803272257 03272257# crash
  /usr/lib/debug/boot/vmlinux-4.15.

  crash 7.2.1
  Copyright (C) 2002-2017  Red Hat, Inc.
  Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
  Copyright (C) 1999-2006  Hewlett-Packard Co
  Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
  Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
  Copyright (C) 2005, 2011  NEC Corporation
  Copyright (C) 1999, 2002, 2007  Silicon Graphics, Inc.
  Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
  This program is free software, covered by the GNU General Public License,
  and you are welcome to change it and/or distribute copies of it under
  certain conditions.  Enter "help copying" to see the conditions.
  This program has absolutely no warranty.  Enter "help warranty" for details.

  GNU gdb (GDB) 7.6
  Copyright (C) 2013 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "powerpc64le-unknown-linux-gnu"...

    KERNEL: /usr/lib/debug/boot/vmlinux-4.15.0-13-generic
  DUMPFILE: dump.201803272257  [PARTIAL DUMP]
  CPUS: 160
  DATE: Tue Mar 27 22:56:58 2018
    UPTIME: 00:04:07
  LOAD AVERAGE: 1.06, 0.53, 0.20
     TASKS: 1734
  NODENAME: ltc-briggs2
   RELEASE: 4.15.0-13-generic
   VERSION: #14-Ubuntu SMP Sat Mar 17 13:43:15 UTC 2018
   MACHINE: ppc64le  (2926 Mhz)
    MEMORY: 512 GB
     PANIC: "sysrq: SysRq : Trigger a crash"
   PID: 7420
   COMMAND: "bash"
  TASK: c03e56c7c600  [THREAD_INFO: c03e56cb]
   CPU: 41
     STATE: TASK_RUNNING (SYSRQ)

  crash> ?

  *  files  mach   repeat timer
  alias

[Kernel-packages] [Bug 1806429] Re: linux-lts-trusty: 3.13.0-164.214~precise1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Incomplete => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806428
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 02:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Stalled -- testing FAILED
+   promote-to-security: Holding -- master bug not ready for release
+   promote-to-updates: Holding -- master bug not ready for release

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

Title:
  linux-lts-trusty: 3.13.0-164.214~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806428
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 02:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806429/+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 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep

[Aaron Whitehouse]

Having looked into this in more detail, it sounds as though this is the 
intended behaviour for new laptops that declare ACPI_FADT_LOW_POWER_S0:
https://patchwork.kernel.org/patch/9433419/

This appears related to:
https://docs.microsoft.com/en-us/windows-hardware/design/device-experiences/behavior-differences-between-s3-and-modern-standby

If that is the case and this laptop is supposed to be able to do S2I
that is low power but quicker to suspend and resume, then I guess I can
understand Kai-Heng's comment (though the suspend/resume process is <
few seconds for me with S3).

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

Title:
  Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It seems that the Dell 9370 is set to go into s2idle mode rather than
  deep sleep, forgoing significant power savings.

  I have confirmed this by suspending and then checking:
  sudo journalctl | grep "PM: suspend" | tail -2. If the output is

  PM: suspend entry (s2idle)
  PM: suspend exit

  cat /sys/power/mem_sleep showed

  [s2idle] deep

  As a temporary fix, I typed 
  echo deep > /sys/power/mem_sleep 
  as a root user (sudo -i). 

  Then the output of cat /sys/power/mem_sleep was
  s2idle [deep]

  After suspending now, 
  sudo journalctl | grep "PM: suspend" | tail -2 returns

  PM: suspend entry (deep)
  PM: suspend exit

  I have made this permanent by editing 
  /etc/default/grub

  and replacing
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  with
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep"

  then regenerating my grub configuration (sudo grub-mkconfig -o
  /boot/grub/grub.cfg).

  This appears to be working with no ill effects.

  Credit to https://askubuntu.com/a/1036122/470077

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aaron-work   3672 F pulseaudio
   /dev/snd/pcmC0D0p:   aaron-work   3672 F...m pulseaudio
  Date: Tue Dec 18 09:52:44 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1
  InstallationDate: Installed on 2018-09-04 (104 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
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.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.175.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+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 1806429] Re: linux-lts-trusty: 3.13.0-164.214~precise1 -proposed tracker

[Sean Feole]

Please note we do not have i386 images due to bug 
https://bugs.launchpad.net/maas/+bug/1807820 
It appears that i386 precise support has been dropped in MAAS

** Tags added: regression-testing-passed

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

Title:
  linux-lts-trusty: 3.13.0-164.214~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Incomplete
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806428
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 02:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Stalled -- testing FAILED

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806429/+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 1805920] Re: iPXE ignores vlan 0 traffic

[Christian Ehrhardt ]

I'll upload once I get a confirmation that it will be tested on both
releases on the affected HW.

** Description changed:

  [Impact]
  
   * VLAN 0 is special (for QoS actually, not a real VLAN)
   * Some components in the stack accidentally strip it, so does ipxe in
     this case.
   * Fix by porting a fix that is carried by other distributions as upstream
     didn't follow the suggestion but it is needed for the use case affected
     by the bug here (Thanks Andres)
  
  [Test Case]
  
-  * TODO
+  * Comment #42 contains a virtual test setup to understand the case but it 
+does NOT trigger the isse. That requires special switch HW that adds 
+VLAN 0 tags for QoS. Therefore Vern (reporter) will test that on a 
+customer site with such hardware being affected by this issue.
  
  [Regression Potential]
  
   * The only reference to VLAN tags on iPXE boot that we found was on iBFT
     boot for SCSI, we tested that in comment #34 and it still worked fine.
   * We didn't see such cases on review, but there might be use cases that
     made some unexpected use of the headers which are now stripped. But
     that seems wrong.
  
  [Other Info]
  
   * n/a
  
  ---
  
  I have three MAAS rack/region nodes which are blades in a Cisco UCS
  chassis. This is an FCE deployment where MAAS has two DHCP servers,
  infra1 is the primary and infra3 is the secondary. The pod VMs on infra1
  and infra3 PXE boot fine but the pod VMs on infra2 fail to PXE boot. If
  I reconfigure the subnet to provide DHCP on infra2 (either as primary or
  secondary) then the pod VMs on infra2 will PXE boot but the pod VMs on
  the demoted infra node (that no longer serves DHCP) now fail to PXE
  boot.
  
  While commissioning a pod VM on infra2 I captured network traffic with
  tcpdump on the vnet interface.
  
  Here is the dump when the PXE boot fails (no dhcp server on infra2):
  https://pastebin.canonical.com/p/THW2gTSv4S/
  
  Here is the dump when PXE boot succeeds (when infra2 is serving dhcp):
  https://pastebin.canonical.com/p/HH3XvZtTGG/
  
  The only difference I can see is that in the unsuccessful scenario, the
  reply is an 802.1q packet -- it's got a vlan tag for vlan 0. Normally
  vlan 0 traffic is passed as if it is not tagged and indeed, I can ping
  between the blades with no problem. Outgoing packets are untagged but
  incoming packets are tagged vlan 0 -- but the ping works. It seems vlan
  0 is used as a part of 802.1p to set priority of packets. This is
  separate from vlan, it just happens to use that ethertype to do the
  priority tagging.
  
  Someone confirmed to me that, in the iPXE source, it drops all packets
  if they are vlan tagged.
  
  The customer is unable to figure out why the packets between blades is
  getting vlan tagged so we either need to figure out how to allow iPXE to
  accept vlan 0 or the customer will need to use different equipment for
  the MAAS nodes.
  
  I found a conversation on the ipxe-devel mailing list that suggested a
  commit was submitted and signed off but that was from 2016 so I'm not
  sure what became of it. Notable messages in the thread:
  
  http://lists.ipxe.org/pipermail/ipxe-devel/2016-April/004916.html
  http://lists.ipxe.org/pipermail/ipxe-devel/2016-July/005099.html
  
  Would it be possible to install a local patch as part of the FCE
  deployment? I suspect the patch(es) mentioned in the above thread would
  require some modification to apply properly.

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

Title:
  iPXE ignores vlan 0 traffic

Status in MAAS:
  Invalid
Status in ipxe package in Ubuntu:
  Fix Released
Status in ipxe-qemu-256k-compat package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in ipxe source package in Trusty:
  Won't Fix
Status in ipxe source package in Xenial:
  Won't Fix
Status in ipxe source package in Bionic:
  Incomplete
Status in ipxe source package in Cosmic:
  Incomplete
Status in ipxe source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * VLAN 0 is special (for QoS actually, not a real VLAN)
   * Some components in the stack accidentally strip it, so does ipxe in
     this case.
   * Fix by porting a fix that is carried by other distributions as upstream
     didn't follow the suggestion but it is needed for the use case affected
     by the bug here (Thanks Andres)

  [Test Case]

   * Comment #42 contains a virtual test setup to understand the case but it 
 does NOT trigger the isse. That requires special switch HW that adds 
 VLAN 0 tags for QoS. Therefore Vern (reporter) will test that on a 
 customer site with such hardware being affected by this issue.

  [Regression Potential]

   * The only reference to VLAN tags on iPXE boot that we found was on iBFT
     boot for SCSI, we tested that in comment #34 and it still worked fine.
   * We didn't s

[Kernel-packages] [Bug 1798776] Re: kvm_stat : missing python dependency

[Frank Heimes]

Yes, once it landed in 19.04,
it should be changed in 18.10 and 18.04, too.
All these have python3 per default.

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

Title:
  kvm_stat : missing python dependency

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  In Progress

Bug description:
  After installing linux-tools-host, the included kvm_stat utility won't
  work:

  root@ubuntu:~# kvm_stat 
  -bash: /usr/bin/kvm_stat: /usr/bin/python: bad interpreter: No such file or 
directory

  Reason is that there is apparently no dependency on a python package
  from the linux-tools-host package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1798776/+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 1678184] Re: APST quirk needed for Samsung 512GB NVMe drive

[Ian Ozsvald]

Hello Yingfag - can I check please - was it a 1TB Samsung SSD? Which
model of SSD (950? 960? 970? something else?). When you changed the SSD
- did you keep the same model? What was your final solution? Regards,
Ian.

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

Title:
  APST quirk needed for Samsung 512GB NVMe drive

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  APST support just landed in the latest Zesty kernel (4.10.0-14.16) as
  part of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664602.
  That patch has a quirk for certain 256GB Samsung drives found in Dell
  laptops that do not behave well when APST is enabled. I am
  experiencing the same symptoms with the same model laptop except with
  a 512GB Samsung. Prior to manually disabling APST the drive would die
  and system would go down in flames with I/O errors within 20 to 40
  minutes of boot.

  $ sudo nvme list
  Node SN   Model   
 Namespace Usage  Format   FW Rev  
    
 - -- 
 
  /dev/nvme0n1   ** PM951 NVMe SAMSUNG 512GB
 1 500.20  GB / 512.11  GB512   B +  0 B   BXV76D0Q

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-14-generic 4.10.0-14.16
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ajclayton   3305 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Fri Mar 31 09:42:38 2017
  InstallationDate: Installed on 2012-09-08 (1665 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic 
root=UUID=779e5929-5ffb-49b1-9786-1adcde824b7d ro rootflags=subvol=@ noprompt 
nouveau.modeset=0 log_buf_len=20M
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-14-generic N/A
   linux-backports-modules-4.10.0-14-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-03-07 (23 days ago)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184/+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 1808912] Re: scsi: libsas: fix a race condition when smp task timeout

[Joseph Salisbury]

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

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

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
 Assignee: Ike Panhc (ikepanhc)
   Status: Incomplete

** Changed in: linux (Ubuntu Disco)
   Status: Incomplete => 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/1808912

Title:
  scsi: libsas: fix a race condition when smp task timeout

Status in linux package in Ubuntu:
  In Progress
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]
  When the lldd is processing the complete sas task in interrupt and set the
  task stat as SAS_TASK_STATE_DONE, the smp timeout timer is able to be
  triggered at the same time. And smp_task_timedout() will complete the task
  wheter the SAS_TASK_STATE_DONE is set or not. Then the sas task may freed
  before lldd end the interrupt process. Thus a use-after-free will happen.

  [Test Case]
  This is hard to reproduce, so regression test only.

  [Fix]
  b90cd6f2b9 scsi: libsas: fix a race condition when smp task timeout

  [Regression Risk]
  Only 2 line moved in libsas and maintainer has reviewed/approved. I will say 
it's low.

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

[Po-Hsu Lin]

4.15.0-1007.9 - oci
Regression test CMPL, RTB.

Issue to note in gcp:  
  ubuntu_kvm_unit_tests - 24 failures
  ubunut_ltp - test should be disabled on clouds
  ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) 
fanotify10 (bug 1802454)

Skipped / blacklisted:
 * libhugetlbfs
 * ubuntu_ltp
 * ubuntu_seccomp

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

Title:
  linux-oracle: 4.15.0-1007.9 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.15.0-1007.7 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 14. December 2018 22:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED

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

[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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 06:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Master bug not ready for release
-   promote-to-updates: Master bug not ready for release
+   promote-to-security: Holding -- master bug not ready for release
+   promote-to-updates: Holding -- master bug not ready for release

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

Title:
  linux-aws: 4.18.0-1007.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 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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 06:39 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

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

[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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806569
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 15:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Master bug not ready for release
-   promote-to-updates: Master bug not ready for release
+   promote-to-security: Holding -- master bug not ready for release
+   promote-to-updates: Holding -- master bug not ready for release

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

Title:
  linux-aws: 4.4.0-1037.40 -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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806569
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 15:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806570/+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 1806670] Re: linux-azure: 4.15.0-1036.38~14.04.2 -proposed tracker

[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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Master bug not ready for release
-   promote-to-updates: Master bug not ready for release
+   promote-to-security: Holding -- master bug not ready for release
+   promote-to-updates: Holding -- master bug not ready for release

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

Title:
  linux-azure: 4.15.0-1036.38~14.04.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

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

[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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Master bug not ready for release
-   promote-to-updates: Master bug not ready for release
+   promote-to-security: Holding -- master bug not ready for release
+   promote-to-updates: Holding -- master bug not ready for release

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

Title:
  linux-gcp: 4.15.0-1026.27 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/180/+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 1806672] Re: linux-azure: 4.15.0-1036.38~16.04.1 -proposed tracker

[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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Master bug not ready for release
-   promote-to-updates: Master bug not ready for release
+   promote-to-security: Holding -- master bug not ready for release
+   promote-to-updates: Holding -- master bug not ready for release

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

Title:
  linux-azure: 4.15.0-1036.38~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

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

[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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 07:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Master bug not ready for release
-   promote-to-updates: Master bug not ready for release
-   stakeholder-signoff: Waiting for signoff
+   promote-to-security: Holding -- master bug not ready for release
+   promote-to-updates: Holding -- master bug not ready for release
+   stakeholder-signoff: Pending -- waiting for signoff

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

Title:
  linux-azure: 4.18.0-1007.7 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 07:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release
stakeholder-signoff: Pending -- waiting for signoff

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

[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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 11:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Master bug not ready for release
-   promote-to-updates: Master bug not ready for release
+   promote-to-security: Holding -- master bug not ready for release
+   promote-to-updates: Holding -- master bug not ready for release

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

Title:
  linux-gcp: 4.18.0-1005.6 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 11:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

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

[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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806569
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 15:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Master bug not ready for release
-   promote-to-updates: Master bug not ready for release
+   promote-to-security: Holding -- master bug not ready for release
+   promote-to-updates: Holding -- master bug not ready for release

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

Title:
  linux-kvm: 4.4.0-1039.45 -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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806569
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 15:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

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

[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 1806570 (linux-aws), bug 1806572 (linux-lts-xenial)
  derivatives: bug 1806573 (linux-aws), bug 1806575 (linux-euclid), bug 1806578 
(linux-kvm), bug 1806579 (linux-raspi2), bug 1806580 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 13:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Testing in progress
+   certification-testing: Ongoing -- testing in progress

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

Title:
  linux: 4.4.0-141.167 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: bug 1806570 (linux-aws), bug 1806572 (linux-lts-xenial)
  derivatives: bug 1806573 (linux-aws), bug 1806575 (linux-euclid), bug 1806578 
(linux-kvm), bug 1806579 (linux-raspi2), bug 1806580 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 13:40 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Ongoing -- testing in progress

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

[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 1806410 (linux-hwe), bug 1806413 (linux-hwe-edge), bug 1806414 
(linux-aws-edge), bug 1806416 (linux-azure-edge), bug 1806418 (linux-gcp-edge), 
bug 1806425 (linux-azure-edge)
  derivatives: bug 1806419 (linux-raspi2), bug 1806420 (linux-aws), bug 1806422 
(linux-azure), bug 1806423 (linux-gcp), bug 1806424 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 11:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Cycle not ready to release
-   promote-to-updates: Cycle not ready to release
+   promote-to-security: Holding -- cycle not ready to release
+   promote-to-updates: Holding -- cycle not ready to release

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

Title:
  linux: 4.18.0-13.14 -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:
  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-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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: bug 1806410 (linux-hwe), bug 1806413 (linux-hwe-edge), bug 1806414 
(linux-aws-edge), bug 1806416 (linux-azure-edge), bug 1806418 (linux-gcp-edge), 
bug 1806425 (linux-azure-edge)
  derivatives: bug 1806419 (linux-raspi2), bug 1806420 (linux-aws), bug 1806422 
(linux-azure), bug 1806423 (linux-gcp), bug 1806424 (linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 11:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- cycle not ready to release
promote-to-updates: Holding -- cycle not ready to release

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

[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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806569
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 13:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Master bug not ready for release
-   promote-to-updates: Master bug not ready for release
+   promote-to-security: Holding -- master bug not ready for release
+   promote-to-updates: Holding -- master bug not ready for release

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

Title:
  linux-aws: 4.4.0-1074.84 -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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806569
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 13:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

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

[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: 
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 13:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Testing FAILED
+   regression-testing: Stalled -- testing FAILED

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

Title:
  linux: 3.2.0-139.185 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
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-lbm 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:
  Incomplete
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Precise:
  Invalid

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: 
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 13:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Stalled -- testing FAILED

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

[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 1806429 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 13:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Cycle not ready to release
-   promote-to-updates: Cycle not ready to release
+   promote-to-security: Holding -- cycle not ready to release
+   promote-to-updates: Holding -- cycle not ready to release

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

Title:
  linux: 3.13.0-164.214 -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:
  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-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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: bug 1806429 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 13:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- cycle not ready to release
promote-to-updates: Holding -- cycle not ready to release

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806428/+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 1806429] Re: linux-lts-trusty: 3.13.0-164.214~precise1 -proposed tracker

[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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806428
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 02:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Testing FAILED
+   regression-testing: Stalled -- testing FAILED

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

Title:
  linux-lts-trusty: 3.13.0-164.214~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Incomplete
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806428
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 02:07 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Stalled -- testing FAILED

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

[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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 11:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Master bug not ready for release
-   promote-to-updates: Master bug not ready for release
+   promote-to-security: Holding -- master bug not ready for release
+   promote-to-updates: Holding -- master bug not ready for release

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

Title:
  linux-kvm: 4.18.0-1006.6 -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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 11:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

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

[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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Master bug not ready for release
-   promote-to-updates: Master bug not ready for release
+   promote-to-security: Holding -- master bug not ready for release
+   promote-to-updates: Holding -- master bug not ready for release

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

Title:
  linux-azure: 4.15.0-1036.38 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow stakeholder-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

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

[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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 23:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Master bug not ready for release
-   promote-to-updates: Master bug not ready for release
+   promote-to-security: Holding -- master bug not ready for release
+   promote-to-updates: Holding -- master bug not ready for release

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

Title:
  linux-kvm: 4.15.0-1028.28 -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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 23:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

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

[Brad Figg]

** Description changed:

  This bug is for tracking the 4.15.0-1007.7 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 14. December 2018 22:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Testing FAILED
+   automated-testing: Stalled -- testing FAILED

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

Title:
  linux-oracle: 4.15.0-1007.9 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.15.0-1007.7 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 14. December 2018 22:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED

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

[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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Saturday, 08. December 2018 12:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Master bug not ready for release
-   promote-to-updates: Master bug not ready for release
+   promote-to-security: Holding -- master bug not ready for release
+   promote-to-updates: Holding -- master bug not ready for release

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

Title:
  linux-oem: 4.15.0-1030.35 -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:
  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-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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux-oem source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Saturday, 08. December 2018 12:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

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

[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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 21:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Master bug not ready for release
-   promote-to-updates: Master bug not ready for release
+   promote-to-security: Holding -- master bug not ready for release
+   promote-to-updates: Holding -- master bug not ready for release

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

Title:
  linux-aws: 4.15.0-1031.33 -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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 21:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806664/+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 1806673] Re: linux-gcp: 4.15.0-1026.27~16.04.1 -proposed tracker

[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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Saturday, 08. December 2018 13:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Master bug not ready for release
-   promote-to-updates: Master bug not ready for release
+   promote-to-security: Holding -- master bug not ready for release
+   promote-to-updates: Holding -- master bug not ready for release

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-gcp package in Ubuntu:
  Invalid
Status in linux-gcp source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Saturday, 08. December 2018 13:34 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- master bug not ready for release
promote-to-updates: Holding -- master bug not ready for release

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1806673/+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 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the 4.15.0-1007.7~16.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 14. December 2018 21:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Testing FAILED
+   automated-testing: Stalled -- testing FAILED

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

Title:
  linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the 4.15.0-1007.7~16.04.1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 14. December 2018 21:38 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED

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

[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: 
  derivatives:
  -- swm properties --
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 10:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Testing FAILED
+   automated-testing: Stalled -- testing FAILED

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

Title:
  linux: 4.19.0-8.9 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
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:
  New
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: 
  derivatives:
  -- swm properties --
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 10:02 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED

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

[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 1806670 (linux-azure), bug 1806671 (linux-aws-hwe), bug 
1806672 (linux-azure), bug 1806673 (linux-gcp), bug 1806674 (linux-hwe), bug 
1806675 (linux-hwe-edge)
  derivatives: bug 1806661 (linux-raspi2), bug 1806663 (linux-oem), bug 1806664 
(linux-aws), bug 1806665 (linux-azure), bug 180 (linux-gcp), bug 1806667 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 12:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-security: Cycle not ready to release
-   promote-to-updates: Cycle not ready to release
+   promote-to-security: Holding -- cycle not ready to release
+   promote-to-updates: Holding -- cycle not ready to release

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

Title:
  linux: 4.15.0-43.46 -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:
  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-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:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: bug 1806670 (linux-azure), bug 1806671 (linux-aws-hwe), bug 
1806672 (linux-azure), bug 1806673 (linux-gcp), bug 1806674 (linux-hwe), bug 
1806675 (linux-hwe-edge)
  derivatives: bug 1806661 (linux-raspi2), bug 1806663 (linux-oem), bug 1806664 
(linux-aws), bug 1806665 (linux-azure), bug 180 (linux-gcp), bug 1806667 
(linux-kvm)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 12:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Holding -- cycle not ready to release
promote-to-updates: Holding -- cycle not ready to release

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

[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 1806429 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 13:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   certification-testing: Testing in progress
+   promote-to-security: Cycle not ready to release
+   promote-to-updates: Cycle not ready to release

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

Title:
  linux: 3.13.0-164.214 -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:
  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-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:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: bug 1806429 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 13:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-security: Cycle not ready to release
promote-to-updates: Cycle not ready to release

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