[Kernel-packages] [Bug 1805920] Re: iPXE ignores vlan 0 traffic

[Christian Ehrhardt ]

virt stack tests are successful on 1.0.0+git-20180124.fbe8c52d-0ubuntu2.2 and 
1.0.0+git-20180124.fbe8c52d-0ubuntu4.1 from the PPA.
Including various others tests, but mostly related migrations and upgrades 
between those versions.
Everything fine on that end ...

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

   * TODO

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

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

Thank Vern for outlining your testcase.

@Vern
Doesn't that also have to include some component that does QoS management 
adding the VLAN-0 tag?

I don't have the systems to verify this case on Bionic and Cosmic.
As I read it from Vern he can only test Bionic at the Customer and is unsure he 
can test Cosmic the same way.

@MAAS team - Would you have a MAAS tets environment that you can re-use to 
verify this?
If so could you confirm that you can locally trigger the bug as it is today so 
that we can rely on it on SRU processing?

@Vern - if above is Nack'ed by the MAAS team could you ask if you could
if could get nodes to verify that on Cosmic as well. As I read your test
description I think it would be enough to bump the node that is supposed
to start the guest to Cosmic+Proposed then - no need to update all
systems to 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/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]

   * TODO

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1805920/+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 1788549] Re: powerpc/powernv/pci: Work around races in PCI bridge enabling

[Andrew Cloke]

** Changed in: ubuntu-power-systems
   Status: Incomplete => Triaged

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

Title:
  powerpc/powernv/pci: Work around races in PCI bridge enabling

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2018-08-21 
13:52:03 ==
  +++ This bug was initially created as a clone of Bug #170766 +++

  Please apply the following kernel patch:

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=db2173198b9513f7add8009f225afa1f1c79bcc6

  powerpc/powernv/pci: Work around races in PCI bridge enabling

  The generic code is racy when multiple children of a PCI bridge try to
  enable it simultaneously.

  This leads to drivers trying to access a device through a
  not-yet-enabled bridge, and this EEH errors under various
  circumstances when using parallel driver probing.

  There is work going on to fix that properly in the PCI core but it
  will take some time.

  x86 gets away with it because (outside of hotplug), the BIOS enables
  all the bridges at boot time.

  This patch does the same thing on powernv by enabling all bridges that
  have child devices at boot time, thus avoiding subsequent races. It's
  suitable for backporting to stable and distros, while the proper PCI
  fix will probably be significantly more invasive.

  Signed-off-by: Benjamin Herrenschmidt 
  Cc: sta...@vger.kernel.org
  Signed-off-by: Michael Ellerman 

  == Comment: #2 - Michael Ranweiler  - 2018-08-21 
18:23:35 ==
  This has some fuzz and also move it back from the pci macro to dev_err so 
we'll attach the backported patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788549/+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 1788549] Re: powerpc/powernv/pci: Work around races in PCI bridge enabling

[Mike Ranweiler]

I've tried this on two systems and tried some different testing - I
can't recreate the original problem that is is intermittent and can
require quite a few devices, but I did not see any regressions.

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

Title:
  powerpc/powernv/pci: Work around races in PCI bridge enabling

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Incomplete
Status in linux source package in Bionic:
  Incomplete
Status in linux source package in Cosmic:
  Incomplete

Bug description:
  == Comment: #0 - Michael Ranweiler  - 2018-08-21 
13:52:03 ==
  +++ This bug was initially created as a clone of Bug #170766 +++

  Please apply the following kernel patch:

  
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?h=next=db2173198b9513f7add8009f225afa1f1c79bcc6

  powerpc/powernv/pci: Work around races in PCI bridge enabling

  The generic code is racy when multiple children of a PCI bridge try to
  enable it simultaneously.

  This leads to drivers trying to access a device through a
  not-yet-enabled bridge, and this EEH errors under various
  circumstances when using parallel driver probing.

  There is work going on to fix that properly in the PCI core but it
  will take some time.

  x86 gets away with it because (outside of hotplug), the BIOS enables
  all the bridges at boot time.

  This patch does the same thing on powernv by enabling all bridges that
  have child devices at boot time, thus avoiding subsequent races. It's
  suitable for backporting to stable and distros, while the proper PCI
  fix will probably be significantly more invasive.

  Signed-off-by: Benjamin Herrenschmidt 
  Cc: sta...@vger.kernel.org
  Signed-off-by: Michael Ellerman 

  == Comment: #2 - Michael Ranweiler  - 2018-08-21 
18:23:35 ==
  This has some fuzz and also move it back from the pci macro to dev_err so 
we'll attach the backported patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788549/+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 1803600] Re: Elantech - Touchpad not working after upgrading to 18.10 from 18.04

[Kai-Heng Feng]

Upstream maintainer wants to know the firmware information of your
touchpad, can you provide it?

https://lore.kernel.org/lkml/CAO-
hwj+fshpj7xbjobvk8ugrhfkcdfsmzicmmoymjs0cdza...@mail.gmail.com/

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

Title:
  Elantech - Touchpad not working after upgrading to 18.10 from 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Confirmed affected laptops:
  ThinkPad: 
  L480
  L580
  P72
  P52

  
  When updating from 18.04 to 18.10 on a ThinkPad L480 the Elantech touchpad 
stopped working. This means it is not recognized at all. This problem occured 
after the first boot in 18.10

  `dmesg | grep -i elantech` shows the following errors:

  [3.409043] psmouse serio1: elantech: assuming hardware version 4 
(with firmware version 0x5f3001)
  [3.427372] psmouse serio1: elantech: Synaptics capabilities query 
result 0x90, 0x18, 0x10.
  [3.447275] psmouse serio1: elantech: Elan sample query result 00, 23, 
c8
  [3.464905] psmouse serio1: elantech: Trying to set up SMBus access
  [5.576149] elan_i2c 0-0015: 0-0015 supply vcc not found, using dummy 
regulator
  [5.586505] elan_i2c 0-0015: failed to get resolution: -71
  [5.586527] elan_i2c: probe of 0-0015 failed with error -71

  uname:

  $ uname -a
  Linux test 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  I found the following thread which solves the problem temporarly (and reports 
the same problem in Arch):
  https://bugs.archlinux.org/task/59714

  Running the following command enables it again for the current
  session:

  sudo sh -c 'echo -n "elantech">
  /sys/bus/serio/devices/serio1/protocol'

  dmesg afterwards:

  [  569.522490] psmouse serio1: elantech: assuming hardware version 4 
(with firmware version 0x5f3001)
  [  569.544584] psmouse serio1: elantech: Synaptics capabilities query 
result 0x90, 0x18, 0x10.
  [  569.565939] psmouse serio1: elantech: Elan sample query result 00, 23, 
c8

  Before running the fix:

  $ cat /sys/bus/serio/devices/serio1/protocol
  ETSMBus

  and after:

  $ cat /sys/bus/serio/devices/serio1/protocol
  ETPS/2

  After reboot the command has to be run again, of course.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Nov 15 20:59:36 2018
  DistUpgraded: 2018-11-10 09:56:53,358 DEBUG icon theme changed, re-reading
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.18, 4.15.0-38-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:506a]
  InstallationDate: Installed on 2018-08-06 (101 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20LS001AGE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=a1f97298-a2b8-469d-80ed-7497c6e6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-11-10 (5 days ago)
  dmi.bios.date: 02/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0QET37W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LS001AGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0QET37W(1.14):bd02/09/2018:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L480
  dmi.product.name: 20LS001AGE
  dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480
  dmi.product.version: ThinkPad L480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.4-0~b~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.4-0~b~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  

[Kernel-packages] [Bug 1807334] Re: Add support for ALC3277 codec on new Dell edge gateways

[Hui Wang]

** Description changed:

- There are two audio jacks on the device, one for Line-in and the other
- for Line-out.
  
- Audio over these jacks is supported through Realtek ALC3277 (RT5660)
- audio codec connected to the Processor/SoC over I2C. While the kernel
- already has the driver for the Codec, we still need a machine driver to
- connect audio FrontEnds provided by the Codec to the Intel SST Audio
- BackEnds.
+ [Impact]
+ The Dell Edge IoT Gateway is based on kabylake, and the audio codec is alc3277
+ which is connected to kabylake PCH via SSP0, there is no ASoC machine driver
+ for this board, so the audio (line-out and line-in) can't work.
+ 
+ 
+ [Fix]
+ write a ASoC machine driver for this board, and this driver is based on
+ the existing driver kbl_rt5663_max98927.c
+ 
+ 
+ [Test Case]
+ play sound via line-out jack, record sound via line-in jack, all work well.
+ 
+ 
+ [Regression Potential]
+ Very low, this machine driver is specific to Dell Edge IoT Gateway. Only
+ the machine with the HID:10EC3277 in the BIOS can use this driver.

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

Title:
  Add support for ALC3277 codec on new Dell edge gateways

Status in HWE Next:
  In Progress
Status in linux-oem package in Ubuntu:
  In Progress

Bug description:
  
  [Impact]
  The Dell Edge IoT Gateway is based on kabylake, and the audio codec is alc3277
  which is connected to kabylake PCH via SSP0, there is no ASoC machine driver
  for this board, so the audio (line-out and line-in) can't work.

  
  [Fix]
  write a ASoC machine driver for this board, and this driver is based on
  the existing driver kbl_rt5663_max98927.c

  
  [Test Case]
  play sound via line-out jack, record sound via line-in jack, all work well.

  
  [Regression Potential]
  Very low, this machine driver is specific to Dell Edge IoT Gateway. Only
  the machine with the HID:10EC3277 in the BIOS can use this driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1807334/+subscriptions

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

[Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460

[Kai-Heng Feng]

Seems to be another AMDGPU DC issue...

Please try mainline kernel v4.20-rc6.
If it doesn't solve the issue, please file an upstream bug at
https://bugs.freedesktop.org/
Product: DRI
Component: DRM/amdgpu

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

Title:
  Black screen on 18.04 + AMD RX460

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

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

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

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

[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects

[Erick Geidellman]

I have also noticed this error on a gl-702vm on archlinux with the 4.19
kernel. I have the same error, with the touchpad jumping around, being
super slow, and getting a repeated error message that says: i2c_hid i2c-
ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535). I can try
the latest ubuntu release and post the error message from that as well
if nessacary.

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

Title:
  ELAN1200 touchpad jumps around and disconnects

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on an ASUS GL503VD laptop and would probably affect other ASUS
  laptops equipped with the ELAN1200 touchpad.

  I am on Kernel 4.17.2 because older kernels did not enable the
  touchpad at all(It was just unrecognized or i2c-hid stopped the
  computer from booting)

  The touchpad works but it has erratic behaviour and disconnects
  randomly. After it disconnects the only way to bring it back is to
  `modprobe -r hid-multitouch && modprobe hid-multitouch`

  Libinput and synaptics can handle the touchpad though I found
  synaptics to be more stable.

  dmesg gets spammed with this whenever I move the touchpad:
  [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report 
(16/65535)

  I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad
  Because from what I understand the "jumpy/disconnect" problem is associated 
to the incomplete reports and Mishurov managed to mitigate those. Unfortunately 
some symbols were deprecated in kernel 4.17.2 and it did not compile for my 
system.

  While I can use my touchpad as is right now, and "restart" it with
  modprobe when needed, it would be nice to have it function bug-free.
  (Right after I typed this my touchpad disconnected and I needed to
  modprobe again, I am considering making a cronjob for that)

  Let me know if anything else is needed. Will wait for an apport collection to 
add log files.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-10 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.17.2 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+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 1791193] Re: errores dmesg

[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/1791193

Title:
  errores dmesg

Status in linux package in Ubuntu:
  Expired

Bug description:
  HP-Pavilion-dv6-Notebook-PC:~$ dmesg | grep 'ERROR'

  [0.314854] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM

  HP-Pavilion-dv6-Notebook-PC:~$ dmesg | grep 'error'

  [2.210335] rtc_cmos: probe of 00:01 failed with error -16
  [8.740655] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro
  [   14.065747] hp_wmi: query 0xd returned error 0x5

  HP-Pavilion-dv6-Notebook-PC:~$ dmesg | grep 'Error'

  [2.228970] RAS: Correctable Errors collector initialized.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jdaniel1   2175 F pulseaudio
   /dev/snd/controlC1:  jdaniel1   2175 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  7 02:04:05 2018
  HibernationDevice: RESUME=UUID=8e4040b1-92e2-4966-85b4-cd96d821b8b7
  InstallationDate: Installed on 2018-06-12 (86 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=6386aebd-7d3c-4128-9e45-2a0adc183b79 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.29
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1448
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 65.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.29:bd11/07/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr048E10242B102:rvnHewlett-Packard:rn1448:rvr65.38:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 048E10242B102
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791193/+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 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055)

[Michael Conrad]

i have the same problem.
but mine is on a standard machine, no laptop.
connection is being lost after suspend.
running on linux mint 18.3
i try out the new kernels as they com in.
all the same.
kernel version 13.x and below work fine.
please fix this problem.

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

Title:
  sky2 gigabit ethernet driver sometimes stops working after lid-open
  resume from sleep (88E8055)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  sky2 ethernet stops working after system resume from suspend.

  [Fix]
  Increase the PCI D3 delay can workaround the issue.

  [Test]
  User responded that the D3 delay increase can solve the issue.

  [Regression Potential]
  Low. It only affects one device. The fix only increase the delay timer,
  without any functional change.

  ===Original Bug Report===
  After resuming from sleep using the lid-open event, OFTEN (60% replicable, 
usually after 2nd or later resume) the NIC is not functional, and reloading the 
sky2 module does not help. Relevant parts from dmesg:

  [  582.852065] sky2 :04:00.0: Refused to change power state, currently in 
D3
  ...
  [  827.613729] sky2 :04:00.0: ignoring stuck error report bit
  [  827.613748] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613750] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613752] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613754] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613756] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613759] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613761] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613763] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613765] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613767] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613769] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613772] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613774] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613776] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613778] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613780] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613782] sky2 :04:00.0: enp4s0: phy I/O error

  And after reloading the module:
  [ 1421.781480] sky2: driver version 1.30
  [ 1421.781533] sky2 :04:00.0: enabling device ( -> 0003)
  [ 1421.781667] sky2 :04:00.0: unsupported chip type 0xff
  [ 1421.782292] sky2: probe of :04:00.0 failed with error -95

  Possibly relevant:
  [ 1235.944086] ACPI: button: The lid device is not compliant to SW_LID.

  Replicability: When it happens once, further suspend-resume cycles (tried ~5) 
don't fix it. Reboot fixes the NIC, and it often survives first resume after 
that, but 1-2 suspend-resume cycles later the issue WILL occur again.
  Per-boot chance of encountering the issue - so far 2/5.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-12-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Sat Mar 24 09:54:10 2018
  HibernationDevice: RESUME=UUID=02d18685-fc92-4ebe-a43e-34d1e52a26b1
  InstallationDate: Installed on 2018-03-21 (3 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180319)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=bc171dce-b703-44f6-8244-22b6b3b1dc33 ro video=SVIDEO-1:d 
consoleblank=300
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 

[Kernel-packages] [Bug 1758507] Re: sky2 gigabit ethernet driver sometimes stops working after lid-open resume from sleep (88E8055)

[Michael Conrad]

i agree with kris,
all new kernels have his bug.
i keep trying out the new ones as they come in.
all the same.
4.13 an below kernels are fine!
please fix this problem.

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

Title:
  sky2 gigabit ethernet driver sometimes stops working after lid-open
  resume from sleep (88E8055)

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  sky2 ethernet stops working after system resume from suspend.

  [Fix]
  Increase the PCI D3 delay can workaround the issue.

  [Test]
  User responded that the D3 delay increase can solve the issue.

  [Regression Potential]
  Low. It only affects one device. The fix only increase the delay timer,
  without any functional change.

  ===Original Bug Report===
  After resuming from sleep using the lid-open event, OFTEN (60% replicable, 
usually after 2nd or later resume) the NIC is not functional, and reloading the 
sky2 module does not help. Relevant parts from dmesg:

  [  582.852065] sky2 :04:00.0: Refused to change power state, currently in 
D3
  ...
  [  827.613729] sky2 :04:00.0: ignoring stuck error report bit
  [  827.613748] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613750] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613752] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613754] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613756] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613759] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613761] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613763] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613765] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613767] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613769] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613772] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613774] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613776] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613778] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613780] sky2 :04:00.0: enp4s0: phy I/O error
  [  827.613782] sky2 :04:00.0: enp4s0: phy I/O error

  And after reloading the module:
  [ 1421.781480] sky2: driver version 1.30
  [ 1421.781533] sky2 :04:00.0: enabling device ( -> 0003)
  [ 1421.781667] sky2 :04:00.0: unsupported chip type 0xff
  [ 1421.782292] sky2: probe of :04:00.0 failed with error -95

  Possibly relevant:
  [ 1235.944086] ACPI: button: The lid device is not compliant to SW_LID.

  Replicability: When it happens once, further suspend-resume cycles (tried ~5) 
don't fix it. Reboot fixes the NIC, and it often survives first resume after 
that, but 1-2 suspend-resume cycles later the issue WILL occur again.
  Per-boot chance of encountering the issue - so far 2/5.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-12-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Date: Sat Mar 24 09:54:10 2018
  HibernationDevice: RESUME=UUID=02d18685-fc92-4ebe-a43e-34d1e52a26b1
  InstallationDate: Installed on 2018-03-21 (3 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180319)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: FUJITSU SIEMENS ESPRIMO Mobile U9200
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=bc171dce-b703-44f6-8244-22b6b3b1dc33 ro video=SVIDEO-1:d 
consoleblank=300
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Kernel-packages] [Bug 1802350] Re: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem

[Daniel van Vugt]

*** This bug is a duplicate of bug 1711101 ***
https://bugs.launchpad.net/bugs/1711101

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1711101, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1711101
   Audio doesn't auto switch away from HDMI after unplugging HDMI

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

Title:
  [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  On a fresh install of ubutu 18.04 all sound work (youtube and system
  sounds) I connected external hdmi monitor with speakers. I switched
  audio output to hdmi in settings

  Then all audio was channeled to external monitor speakers (youtube and
  system sounds)

  Then I disconnected external monitor and did not touch the audio
  output

  Now only system sounds are working. Youtube in chrome does not work.
  Audio settings says internal speakers.

  Firefox youtube has audio normally

  After reboot same issue

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ed 1412 F pulseaudio
   /dev/snd/controlC1:  ed 1412 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  8 12:28:37 2018
  InstallationDate: Installed on 2018-11-01 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [Inspiron 5547, Realtek ALC3234, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0598GM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd01/24/2018:svnDellInc.:pnInspiron5547:pvrA11:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA11:
  dmi.product.family: 00
  dmi.product.name: Inspiron 5547
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1802350/+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 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

[Michael J]

Hi All...Have A315-41-R8UU Bios v. 1.11. What I have tested: Debian 9
Stretch [with firmware] kernel 4.9x, xfce4...This boots, without issue,
but haven't tested out it's stability long-term. No boot args needed.
Brightness controls do not work. Also tested openSUSE Leap 15, no boot
args, KDE edition. Brightness controls do not work. Will eventually
freeze after some time idle. On both distros, get the same acpi bugs
during boot. To try and mitigate some of the BIOS bugs, I turned off
WoL, SATA ch1, Open Lid resume, Disable TPM (would get tpm errors on
boot), D2D Recovery disabled, secure boot disabled, and basic touchpad.
Oddly, when attempting to install xubuntu 18 LTS or debian 9 testing,
that's when I get all the errors described above. I have added the
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=0:00.2 to grub when trying to run
the installers, and they will indeed run, at low resolution. Why would
older kernels run without the boot params for acpi, while these newer
kernels will not? Maybe this can help someone? This thing so far, is a
paperweight.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1776563/+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 1808251] Re: systemctl disable fails to clean up override

[Edward Gow]

No applicable logs

** Package changed: linux (Ubuntu) => systemd (Ubuntu)

** Changed in: systemd (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/1808251

Title:
  systemctl disable fails to clean up override

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu 16.04.4 LTS  and package version

  systemd:
Installed: 229-4ubuntu21.10
Candidate: 229-4ubuntu21.10
Version table:
   *** 229-4ubuntu21.10 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  When a unit is enabled with 

  systemctl enable 

  and overrides are applied with

  systemctl edit 

  and subsequently the unit is disabled with

  systemctl disable 

  the override file that is created and its directory

  /etc/systemd/system/.d/override.conf

  is not removed.  Subsequent attempts to enable the same unit will fail
  with the misleading and unhelpful error message

  Failed to execute operation: Invalid argument

  Removing the override file and directory will fix the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1808251/+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 1808251] Re: systemctl disable fails to clean up override

[Edward Gow]

This bug is easily reproduced and will not leave any meaningful log
entries.

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

Title:
  systemctl disable fails to clean up override

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu 16.04.4 LTS  and package version

  systemd:
Installed: 229-4ubuntu21.10
Candidate: 229-4ubuntu21.10
Version table:
   *** 229-4ubuntu21.10 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  When a unit is enabled with 

  systemctl enable 

  and overrides are applied with

  systemctl edit 

  and subsequently the unit is disabled with

  systemctl disable 

  the override file that is created and its directory

  /etc/systemd/system/.d/override.conf

  is not removed.  Subsequent attempts to enable the same unit will fail
  with the misleading and unhelpful error message

  Failed to execute operation: Invalid argument

  Removing the override file and directory will fix the problem.

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

** Changed in: kernel-sru-workflow/automated-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
  
  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:
-   automated-testing: Testing FAILED
certification-testing: Testing in progress
verification-testing: 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/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:
  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-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:
  Confirmed
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:
certification-testing: Testing in progress
verification-testing: Testing in progress

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

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

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

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

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

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

Title:
  systemctl disable fails to clean up override

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu 16.04.4 LTS  and package version

  systemd:
Installed: 229-4ubuntu21.10
Candidate: 229-4ubuntu21.10
Version table:
   *** 229-4ubuntu21.10 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  When a unit is enabled with 

  systemctl enable 

  and overrides are applied with

  systemctl edit 

  and subsequently the unit is disabled with

  systemctl disable 

  the override file that is created and its directory

  /etc/systemd/system/.d/override.conf

  is not removed.  Subsequent attempts to enable the same unit will fail
  with the misleading and unhelpful error message

  Failed to execute operation: Invalid argument

  Removing the override file and directory will fix the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808251/+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 1808251] [NEW] systemctl disable fails to clean up override

[Edward Gow]

Public bug reported:

I am using Ubuntu 16.04.4 LTS  and package version

systemd:
  Installed: 229-4ubuntu21.10
  Candidate: 229-4ubuntu21.10
  Version table:
 *** 229-4ubuntu21.10 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status
 229-4ubuntu4 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages


When a unit is enabled with 

systemctl enable 

and overrides are applied with

systemctl edit 

and subsequently the unit is disabled with

systemctl disable 

the override file that is created and its directory

/etc/systemd/system/.d/override.conf

is not removed.  Subsequent attempts to enable the same unit will fail
with the misleading and unhelpful error message

Failed to execute operation: Invalid argument

Removing the override file and directory will fix the problem.

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

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

Title:
  systemctl disable fails to clean up override

Status in linux package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 16.04.4 LTS  and package version

  systemd:
Installed: 229-4ubuntu21.10
Candidate: 229-4ubuntu21.10
Version table:
   *** 229-4ubuntu21.10 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  
  When a unit is enabled with 

  systemctl enable 

  and overrides are applied with

  systemctl edit 

  and subsequently the unit is disabled with

  systemctl disable 

  the override file that is created and its directory

  /etc/systemd/system/.d/override.conf

  is not removed.  Subsequent attempts to enable the same unit will fail
  with the misleading and unhelpful error message

  Failed to execute operation: Invalid argument

  Removing the override file and directory will fix the problem.

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

[hexawolfie]

Let's face it: I really, really don't think measuring time before a
freeze makes any sense. It just occurs under certain circumstances or
even randomly due to some hardware bug - 4.19 will work 4 days for the
first time, 3 hours for the second time and 23 hours for the third.
That's for sure - it's not related to a specific version, it just
persists across all kernel versions.

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64

[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: Uploaded
  phase-changed: Wednesday, 12. December 2018 20:11 UTC
  reason:
-   promote-to-proposed: Builds not complete
+   promote-to-proposed: Manual kernel-block/kernel-block-ppa present

-- 
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:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

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: Uploaded
  phase-changed: Wednesday, 12. December 2018 20:11 UTC
  reason:
promote-to-proposed: Manual kernel-block/kernel-block-ppa present

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 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: Uploaded
  phase-changed: Wednesday, 12. December 2018 19:38 UTC
  reason:
-   promote-to-proposed: Builds not complete
+   promote-to-proposed: Manual kernel-block/kernel-block-ppa present

-- 
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:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

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: Uploaded
  phase-changed: Wednesday, 12. December 2018 19:38 UTC
  reason:
promote-to-proposed: Manual kernel-block/kernel-block-ppa present

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 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

[siyia]

"ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=0:00.2" why are you using ioapic
remapping if they work?what exactly did your patched tables fixed?

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1776563/+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 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

[Richard Baka]

siyia, you have exactly the same laptop model as I have, they should
work. You do something wrong. Maybe you use an incorrect grub or kernel
parameter.

this a section of my /boot/grub/grub.cfg. Yours should look like this.
### BEGIN /etc/grub.d/40_custom_proxy ###
menuentry "Ubuntu" --class ubuntu --class gnu-linux --class gnu --class os 
$menuentry_id_option 'gnulinux-simple-0986d268-5f46-4555-9214-1d9dffa79286' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
set root='hd0,gpt2'
acpi /boot/amls/ssdt10.aml
acpi /boot/amls/ssdt11.aml
acpi /boot/amls/ssdt13.aml
acpi /boot/amls/ssdt14.aml
acpi /boot/amls/ssdt1.aml
acpi /boot/amls/ssdt2.aml
acpi /boot/amls/ssdt3.aml
acpi /boot/amls/ssdt4.aml
acpi /boot/amls/ssdt5.aml
acpi /boot/amls/ssdt6.aml
acpi /boot/amls/ssdt8.aml
acpi /boot/amls/ssdt9.aml
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 
--hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2  
0986d268-5f46-4555-9214-1d9dffa79286
else
  search --no-floppy --fs-uuid --set=root 
0986d268-5f46-4555-9214-1d9dffa79286
fi
linux   /boot/vmlinuz-4.18.0-10-generic 
root=UUID=0986d268-5f46-4555-9214-1d9dffa79286 ro ivrs_ioapic[4]=00:14.0 
ivrs_ioapic[5]=0:00.2 quiet splash $vt_handoff
initrd  /boot/initrd.img-4.18.0-10-generic


Additional kernel parameters aren't needed. Don't change iommu settings or 
anything else. Iommu should be enabled in bios menu.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 23:05 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Testing in progress
verification-testing: Testing in progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Confirmed
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:
verification-testing: Testing in progress

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 1806667] Re: linux-kvm: 4.15.0-1028.28 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-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:
  Confirmed
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:
verification-testing: Testing in progress

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 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker

[Brad Figg]

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

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

** Description changed:

  This bug 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: Packaging
- phase-changed: Wednesday, 12. December 2018 19:33 UTC
+ phase: Uploaded
+ phase-changed: Wednesday, 12. December 2018 20:11 UTC
  reason:
-   prepare-package: Package not yet uploaded
-   prepare-package-signed: Package not yet uploaded
+   promote-to-proposed: Builds not complete

-- 
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:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

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: Uploaded
  phase-changed: Wednesday, 12. December 2018 20:11 UTC
  reason:
promote-to-proposed: Builds not complete

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 1808069] Re: Init corrupted when running 4.15.0-42

[RS]

All apport information from last working kernel -39

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

Title:
  Init corrupted when running 4.15.0-42

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):

  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 

  So apparently the init is broken.

  My solution was to remove 4.15.0-42

  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove

  and, thus, automatically go back to 4.15.0-39 which works fine.

  The autoremove removed amd64-microcode, intel-microcode iucode-tool
  and thermald which appear to be needed by -42 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Dec 12 00:36:04 2018
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeAptlog:
   Log time: 2018-12-12 00:10:47.798784
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: GIGABYTE GB-BPCE-3350C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro video=LVDS-1:d
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: MZAPLCP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/28/2017:svnGIGABYTE:pnGB-BPCE-3350C:pvr1.x:rvnGIGABYTE:rnMZAPLCP-00:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: BRIX
  dmi.product.name: GB-BPCE-3350C
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

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

[RS]

apport information

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

Title:
  Init corrupted when running 4.15.0-42

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):

  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 

  So apparently the init is broken.

  My solution was to remove 4.15.0-42

  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove

  and, thus, automatically go back to 4.15.0-39 which works fine.

  The autoremove removed amd64-microcode, intel-microcode iucode-tool
  and thermald which appear to be needed by -42 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Dec 12 00:36:04 2018
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeAptlog:
   Log time: 2018-12-12 00:10:47.798784
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: GIGABYTE GB-BPCE-3350C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro video=LVDS-1:d
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: MZAPLCP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/28/2017:svnGIGABYTE:pnGB-BPCE-3350C:pvr1.x:rvnGIGABYTE:rnMZAPLCP-00:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: BRIX
  dmi.product.name: GB-BPCE-3350C
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

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

[RS]

apport information

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

Title:
  Init corrupted when running 4.15.0-42

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):

  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 

  So apparently the init is broken.

  My solution was to remove 4.15.0-42

  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove

  and, thus, automatically go back to 4.15.0-39 which works fine.

  The autoremove removed amd64-microcode, intel-microcode iucode-tool
  and thermald which appear to be needed by -42 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Dec 12 00:36:04 2018
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeAptlog:
   Log time: 2018-12-12 00:10:47.798784
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: GIGABYTE GB-BPCE-3350C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro video=LVDS-1:d
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: MZAPLCP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/28/2017:svnGIGABYTE:pnGB-BPCE-3350C:pvr1.x:rvnGIGABYTE:rnMZAPLCP-00:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: BRIX
  dmi.product.name: GB-BPCE-3350C
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

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

[RS]

apport information

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

Title:
  Init corrupted when running 4.15.0-42

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):

  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 

  So apparently the init is broken.

  My solution was to remove 4.15.0-42

  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove

  and, thus, automatically go back to 4.15.0-39 which works fine.

  The autoremove removed amd64-microcode, intel-microcode iucode-tool
  and thermald which appear to be needed by -42 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Dec 12 00:36:04 2018
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeAptlog:
   Log time: 2018-12-12 00:10:47.798784
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: GIGABYTE GB-BPCE-3350C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro video=LVDS-1:d
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: MZAPLCP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/28/2017:svnGIGABYTE:pnGB-BPCE-3350C:pvr1.x:rvnGIGABYTE:rnMZAPLCP-00:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: BRIX
  dmi.product.name: GB-BPCE-3350C
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

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

[RS]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1808069/+attachment/5221748/+files/Lsusb.txt

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

Title:
  Init corrupted when running 4.15.0-42

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):

  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 

  So apparently the init is broken.

  My solution was to remove 4.15.0-42

  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove

  and, thus, automatically go back to 4.15.0-39 which works fine.

  The autoremove removed amd64-microcode, intel-microcode iucode-tool
  and thermald which appear to be needed by -42 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Dec 12 00:36:04 2018
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeAptlog:
   Log time: 2018-12-12 00:10:47.798784
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: GIGABYTE GB-BPCE-3350C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro video=LVDS-1:d
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: MZAPLCP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/28/2017:svnGIGABYTE:pnGB-BPCE-3350C:pvr1.x:rvnGIGABYTE:rnMZAPLCP-00:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: BRIX
  dmi.product.name: GB-BPCE-3350C
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

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

[RS]

apport information

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

Title:
  Init corrupted when running 4.15.0-42

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):

  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 

  So apparently the init is broken.

  My solution was to remove 4.15.0-42

  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove

  and, thus, automatically go back to 4.15.0-39 which works fine.

  The autoremove removed amd64-microcode, intel-microcode iucode-tool
  and thermald which appear to be needed by -42 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Dec 12 00:36:04 2018
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeAptlog:
   Log time: 2018-12-12 00:10:47.798784
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: GIGABYTE GB-BPCE-3350C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro video=LVDS-1:d
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: MZAPLCP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/28/2017:svnGIGABYTE:pnGB-BPCE-3350C:pvr1.x:rvnGIGABYTE:rnMZAPLCP-00:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: BRIX
  dmi.product.name: GB-BPCE-3350C
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808069/+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 1808069] Re: Init corrupted when running 4.15.0-42

[RS]

apport information

** Tags added: apport-collected

** Description changed:

  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):
  
  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 
  
  So apparently the init is broken.
  
  My solution was to remove 4.15.0-42
  
  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove
  
  and, thus, automatically go back to 4.15.0-39 which works fine.
  
  The autoremove removed amd64-microcode, intel-microcode iucode-tool and
  thermald which appear to be needed by -42 only.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Dec 12 00:36:04 2018
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeAptlog:
   Log time: 2018-12-12 00:10:47.798784
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: RESUME=none
+ InstallationDate: Installed on 2013-06-03 (2017 days ago)
+ InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
+ MachineType: GIGABYTE GB-BPCE-3350C
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro video=LVDS-1:d
+ ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-39-generic N/A
+  linux-backports-modules-4.15.0-39-generic  N/A
+  linux-firmware 1.173.2
+ Tags:  bionic
+ Uname: Linux 4.15.0-39-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/28/2017
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: F7
+ dmi.board.asset.tag: Default string
+ dmi.board.name: MZAPLCP-00
+ dmi.board.vendor: GIGABYTE
+ dmi.board.version: 1.x
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Default string
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/28/2017:svnGIGABYTE:pnGB-BPCE-3350C:pvr1.x:rvnGIGABYTE:rnMZAPLCP-00:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:
+ dmi.product.family: BRIX
+ dmi.product.name: GB-BPCE-3350C
+ dmi.product.version: 1.x
+ dmi.sys.vendor: GIGABYTE

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1808069/+attachment/5221743/+files/AlsaInfo.txt

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

Title:
  Init corrupted when running 4.15.0-42

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):

  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 

  So apparently the init is broken.

  My solution was to remove 4.15.0-42

  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove

  and, thus, automatically go back to 4.15.0-39 which works fine.

  The autoremove removed amd64-microcode, intel-microcode iucode-tool
  and thermald which appear to be needed by -42 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 

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

[RS]

apport information

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

Title:
  Init corrupted when running 4.15.0-42

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):

  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 

  So apparently the init is broken.

  My solution was to remove 4.15.0-42

  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove

  and, thus, automatically go back to 4.15.0-39 which works fine.

  The autoremove removed amd64-microcode, intel-microcode iucode-tool
  and thermald which appear to be needed by -42 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Dec 12 00:36:04 2018
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeAptlog:
   Log time: 2018-12-12 00:10:47.798784
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: GIGABYTE GB-BPCE-3350C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro video=LVDS-1:d
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: MZAPLCP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/28/2017:svnGIGABYTE:pnGB-BPCE-3350C:pvr1.x:rvnGIGABYTE:rnMZAPLCP-00:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: BRIX
  dmi.product.name: GB-BPCE-3350C
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

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

[RS]

apport information

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

Title:
  Init corrupted when running 4.15.0-42

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):

  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 

  So apparently the init is broken.

  My solution was to remove 4.15.0-42

  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove

  and, thus, automatically go back to 4.15.0-39 which works fine.

  The autoremove removed amd64-microcode, intel-microcode iucode-tool
  and thermald which appear to be needed by -42 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Dec 12 00:36:04 2018
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeAptlog:
   Log time: 2018-12-12 00:10:47.798784
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: GIGABYTE GB-BPCE-3350C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro video=LVDS-1:d
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: MZAPLCP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/28/2017:svnGIGABYTE:pnGB-BPCE-3350C:pvr1.x:rvnGIGABYTE:rnMZAPLCP-00:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: BRIX
  dmi.product.name: GB-BPCE-3350C
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

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

[RS]

apport information

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

Title:
  Init corrupted when running 4.15.0-42

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):

  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 

  So apparently the init is broken.

  My solution was to remove 4.15.0-42

  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove

  and, thus, automatically go back to 4.15.0-39 which works fine.

  The autoremove removed amd64-microcode, intel-microcode iucode-tool
  and thermald which appear to be needed by -42 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Dec 12 00:36:04 2018
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeAptlog:
   Log time: 2018-12-12 00:10:47.798784
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: GIGABYTE GB-BPCE-3350C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro video=LVDS-1:d
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: MZAPLCP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/28/2017:svnGIGABYTE:pnGB-BPCE-3350C:pvr1.x:rvnGIGABYTE:rnMZAPLCP-00:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: BRIX
  dmi.product.name: GB-BPCE-3350C
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

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

[RS]

apport information

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

Title:
  Init corrupted when running 4.15.0-42

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):

  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 

  So apparently the init is broken.

  My solution was to remove 4.15.0-42

  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove

  and, thus, automatically go back to 4.15.0-39 which works fine.

  The autoremove removed amd64-microcode, intel-microcode iucode-tool
  and thermald which appear to be needed by -42 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Dec 12 00:36:04 2018
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeAptlog:
   Log time: 2018-12-12 00:10:47.798784
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: GIGABYTE GB-BPCE-3350C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro video=LVDS-1:d
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: MZAPLCP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/28/2017:svnGIGABYTE:pnGB-BPCE-3350C:pvr1.x:rvnGIGABYTE:rnMZAPLCP-00:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: BRIX
  dmi.product.name: GB-BPCE-3350C
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

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

[RS]

apport information

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

Title:
  Init corrupted when running 4.15.0-42

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):

  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 

  So apparently the init is broken.

  My solution was to remove 4.15.0-42

  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove

  and, thus, automatically go back to 4.15.0-39 which works fine.

  The autoremove removed amd64-microcode, intel-microcode iucode-tool
  and thermald which appear to be needed by -42 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Dec 12 00:36:04 2018
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeAptlog:
   Log time: 2018-12-12 00:10:47.798784
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: GIGABYTE GB-BPCE-3350C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro video=LVDS-1:d
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: MZAPLCP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/28/2017:svnGIGABYTE:pnGB-BPCE-3350C:pvr1.x:rvnGIGABYTE:rnMZAPLCP-00:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: BRIX
  dmi.product.name: GB-BPCE-3350C
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

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

[RS]

apport information

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

Title:
  Init corrupted when running 4.15.0-42

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):

  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 

  So apparently the init is broken.

  My solution was to remove 4.15.0-42

  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove

  and, thus, automatically go back to 4.15.0-39 which works fine.

  The autoremove removed amd64-microcode, intel-microcode iucode-tool
  and thermald which appear to be needed by -42 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Dec 12 00:36:04 2018
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeAptlog:
   Log time: 2018-12-12 00:10:47.798784
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: GIGABYTE GB-BPCE-3350C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro video=LVDS-1:d
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: MZAPLCP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/28/2017:svnGIGABYTE:pnGB-BPCE-3350C:pvr1.x:rvnGIGABYTE:rnMZAPLCP-00:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: BRIX
  dmi.product.name: GB-BPCE-3350C
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

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

[RS]

apport information

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

Title:
  Init corrupted when running 4.15.0-42

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):

  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 

  So apparently the init is broken.

  My solution was to remove 4.15.0-42

  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove

  and, thus, automatically go back to 4.15.0-39 which works fine.

  The autoremove removed amd64-microcode, intel-microcode iucode-tool
  and thermald which appear to be needed by -42 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Dec 12 00:36:04 2018
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeAptlog:
   Log time: 2018-12-12 00:10:47.798784
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: GIGABYTE GB-BPCE-3350C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro video=LVDS-1:d
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: MZAPLCP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/28/2017:svnGIGABYTE:pnGB-BPCE-3350C:pvr1.x:rvnGIGABYTE:rnMZAPLCP-00:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: BRIX
  dmi.product.name: GB-BPCE-3350C
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

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

[RS]

apport information

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

Title:
  Init corrupted when running 4.15.0-42

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):

  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 

  So apparently the init is broken.

  My solution was to remove 4.15.0-42

  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove

  and, thus, automatically go back to 4.15.0-39 which works fine.

  The autoremove removed amd64-microcode, intel-microcode iucode-tool
  and thermald which appear to be needed by -42 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Dec 12 00:36:04 2018
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeAptlog:
   Log time: 2018-12-12 00:10:47.798784
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: GIGABYTE GB-BPCE-3350C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro video=LVDS-1:d
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: MZAPLCP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/28/2017:svnGIGABYTE:pnGB-BPCE-3350C:pvr1.x:rvnGIGABYTE:rnMZAPLCP-00:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: BRIX
  dmi.product.name: GB-BPCE-3350C
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

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

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

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

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

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

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

Title:
  Init corrupted when running 4.15.0-42

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):

  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 

  So apparently the init is broken.

  My solution was to remove 4.15.0-42

  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove

  and, thus, automatically go back to 4.15.0-39 which works fine.

  The autoremove removed amd64-microcode, intel-microcode iucode-tool
  and thermald which appear to be needed by -42 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Dec 12 00:36:04 2018
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeAptlog:
   Log time: 2018-12-12 00:10:47.798784
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: GIGABYTE GB-BPCE-3350C
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/ubuntu--vg-root ro video=LVDS-1:d
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-39-generic N/A
   linux-backports-modules-4.15.0-39-generic  N/A
   linux-firmware 1.173.2
  Tags:  bionic
  Uname: Linux 4.15.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: MZAPLCP-00
  dmi.board.vendor: GIGABYTE
  dmi.board.version: 1.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd12/28/2017:svnGIGABYTE:pnGB-BPCE-3350C:pvr1.x:rvnGIGABYTE:rnMZAPLCP-00:rvr1.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: BRIX
  dmi.product.name: GB-BPCE-3350C
  dmi.product.version: 1.x
  dmi.sys.vendor: GIGABYTE

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

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

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

[Brad Figg]

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

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

** Description changed:

  This bug 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: Packaging
- phase-changed: Wednesday, 12. December 2018 19:02 UTC
+ phase: Uploaded
+ phase-changed: Wednesday, 12. December 2018 19:38 UTC
  reason:
-   prepare-package: Package not yet uploaded
-   prepare-package-signed: Package not yet uploaded
+   promote-to-proposed: Builds not complete

-- 
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:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

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: Uploaded
  phase-changed: Wednesday, 12. December 2018 19:38 UTC
  reason:
promote-to-proposed: Builds not complete

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 1808069] Re: Init corrupted when upgrading to 4.15.0-42

[Brian Murray]

** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu)

** Summary changed:

- Init corrupted when upgrading to 4.15.0-42
+ Init corrupted when running 4.15.0-42

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

Title:
  Init corrupted when running 4.15.0-42

Status in linux package in Ubuntu:
  New

Bug description:
  When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
  (x86_64) I get the following error on system bootup (freeze):

  Failed to execute /init (error -2)
  Kernel panic - not syncing: no working init found. 

  So apparently the init is broken.

  My solution was to remove 4.15.0-42

  sudo apt remove linux-image-4.15.0-42 
  sudo apt autoremove

  and, thus, automatically go back to 4.15.0-39 which works fine.

  The autoremove removed amd64-microcode, intel-microcode iucode-tool
  and thermald which appear to be needed by -42 only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.29
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CrashDB: ubuntu
  Date: Wed Dec 12 00:36:04 2018
  InstallationDate: Installed on 2013-06-03 (2017 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptclonesystemstate.tar.gz:
   Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  VarLogDistupgradeAptlog:
   Log time: 2018-12-12 00:10:47.798784
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808069/+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 1808069] [NEW] Init corrupted when upgrading to 4.15.0-42

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When upgrading from 4.15.0-39 to 4.15.0-42 on my Ubuntu 18.04.1 NAS
(x86_64) I get the following error on system bootup (freeze):

Failed to execute /init (error -2)
Kernel panic - not syncing: no working init found. 

So apparently the init is broken.

My solution was to remove 4.15.0-42

sudo apt remove linux-image-4.15.0-42 
sudo apt autoremove

and, thus, automatically go back to 4.15.0-39 which works fine.

The autoremove removed amd64-microcode, intel-microcode iucode-tool and
thermald which appear to be needed by -42 only.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.29
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CrashDB: ubuntu
Date: Wed Dec 12 00:36:04 2018
InstallationDate: Installed on 2013-06-03 (2017 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptclonesystemstate.tar.gz:
 Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
 Error executing command as another user: Not authorized
 
 This incident has been reported.
VarLogDistupgradeAptlog:
 Log time: 2018-12-12 00:10:47.798784
 Starting pkgProblemResolver with broken count: 0
 Starting 2 pkgProblemResolver with broken count: 0
 Done

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


** Tags: amd64 apport-bug bionic dist-upgrade
-- 
Init corrupted when upgrading to 4.15.0-42
https://bugs.launchpad.net/bugs/1808069
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker

[Brad Figg]

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

** 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: Uploaded
- phase-changed: Tuesday, 11. December 2018 22:04 UTC
+ phase: Packaging
+ phase-changed: Wednesday, 12. December 2018 19:33 UTC
+ reason:
+   prepare-package: Package not yet uploaded
+   prepare-package-signed: Package not yet uploaded

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

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: Packaging
  phase-changed: Wednesday, 12. December 2018 19:33 UTC
  reason:
prepare-package: Package not yet uploaded
prepare-package-signed: Package not yet uploaded

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 1781879] Re: Latest ASUS trackpad doesn't work in Ubuntu

[Kieran Robinson]

What did you run to get it to work in some fashion ?

-- 
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 1806660] Re: The sound from the notebook speakers sounds randomly. However, you can always listen with hearing aids

[Cristian Aravena Romero]

** Also affects: alsa-lib (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  The sound from the notebook speakers sounds randomly. However, you can
  always listen with hearing aids

Status in Linux:
  Confirmed
Status in alsa-lib package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  The sound from the notebook speakers sounds randomly. However, you can
  always listen with hearing aids.

  In the upper part of gnome-shell it appears that they are with the
  headphones, and it is not like that.

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  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
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   2784 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   2784 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec  4 07:59:27 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (1 days ago)
  dmi.bios.date: 06/14/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.13
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.19
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

[Marcelo Cerri]

** Summary changed:

- linux-oracle: 4.15.0-1007.7~16.04.1 -proposed tracker
+ linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker

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

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Fix Released => 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:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

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: Uploaded
  phase-changed: Tuesday, 11. December 2018 22:04 UTC

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 1807702] Re: linux-oracle: 4.15.0-1007.9 -proposed tracker

[Brad Figg]

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

** 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: Packaging
- phase-changed: Wednesday, 12. December 2018 17:09 UTC
+ phase-changed: Wednesday, 12. December 2018 19:02 UTC
  reason:
+   prepare-package: Package not yet uploaded
prepare-package-signed: Package not yet uploaded

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

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: Packaging
  phase-changed: Wednesday, 12. December 2018 19:02 UTC
  reason:
prepare-package: Package not yet uploaded
prepare-package-signed: Package not yet uploaded

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

[Marcelo Cerri]

** Summary changed:

- linux-oracle: 4.15.0-1007.8 -proposed tracker
+ linux-oracle: 4.15.0-1007.9 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Fix Released => 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:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid

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: Packaging
  phase-changed: Wednesday, 12. December 2018 17:09 UTC
  reason:
prepare-package-signed: Package not yet uploaded

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 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:
-   stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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

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

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 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
-   stakeholder-signoff: 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/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: Master bug not ready for release
promote-to-updates: 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 1805920] Re: iPXE ignores vlan 0 traffic

[Vern Hart]

The customer has bionic installed on 3 of the blades and I have
installed MAAS 2.4.3 on them using the Foundation Cloud Engine. I don't
have access to do the OS install myself. I could request a pair of
blades installed with cosmic but I'm unsure if I need all 3 or if I can
get by with just 2. Easiest would probably be all 3 so that I can be
sure at least one is not running dhcpd.

The test would consist of:
# Install MAAS on 3 nodes
# Install ipxe to be tested on all three nodes
# Configure subnet for PXE booting to have primary dhcp on first node and 
secondary on second node
# Provision Pods on each maas node
# Create and commission a VM on each pod
# The VMs on first and second will commission successfully
# The VM on the third node will fail DHCP/PXE
# You can use virt-viewer to view the console of the VM to verify PXE failure

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

   * TODO

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1805920/+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:
-   stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

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

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

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 1806672] Re: linux-azure: 4.15.0-1036.38~16.04.1 -proposed tracker

[Joshua R. Poulson]

Testing complete.

** 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/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:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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

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

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]

Testing complete.

** 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/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:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

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

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

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 1806670] Re: linux-azure: 4.15.0-1036.38~14.04.2 -proposed tracker

[Joshua R. Poulson]

Testing complete.

** 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/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: Master bug not ready for release
promote-to-updates: 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 1806569] Re: linux: 4.4.0-141.167 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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: 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 1806424] Re: linux-kvm: 4.18.0-1006.6 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-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:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 11:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Testing in progress

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 1806424] Re: linux-kvm: 4.18.0-1006.6 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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: 1806409
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 11:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Testing in progress
verification-testing: Testing in progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Confirmed
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux-kvm source package in Cosmic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806409
  phase: Promoted to proposed
  phase-changed: Thursday, 06. December 2018 11:06 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Testing in progress

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 1806569] Re: linux: 4.4.0-141.167 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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
  
  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
-   regression-testing: 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: 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 1806670] Re: linux-azure: 4.15.0-1036.38~14.04.2 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:32 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Testing in progress
+   promote-to-security: Master bug not ready for release
+   promote-to-updates: Master bug not ready for release
stakeholder-signoff: 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/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:
  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 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: Master bug not ready for release
promote-to-updates: Master bug not ready for release
stakeholder-signoff: Waiting for signoff

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 1806409] Re: linux: 4.18.0-13.14 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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:
  Incomplete
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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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:
automated-testing: Testing FAILED
certification-testing: Testing in progress
verification-testing: Testing in progress

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 1806409] Re: linux: 4.18.0-13.14 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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
  
  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:
automated-testing: Testing FAILED
certification-testing: Testing in progress
-   regression-testing: Testing in progress
verification-testing: 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/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:
  Incomplete
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 upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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:
automated-testing: Testing FAILED
certification-testing: Testing in progress
verification-testing: Testing in progress

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 1806670] Re: linux-azure: 4.15.0-1036.38~14.04.2 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-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:
  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 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: Master bug not ready for release
promote-to-updates: Master bug not ready for release
stakeholder-signoff: Waiting for signoff

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 1805556] Re: package nvidia-utils-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package nvidia-340 340.107

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Confirmed

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

Title:
  package nvidia-utils-390 (not installed) failed to install/upgrade:
  trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in
  package nvidia-340 340.107-0ubuntu0.18.04.1

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to get 2nd video card to work GT710B Nvidia card. I'm
  trying everything that I can find on te Internet from Google. Lots of
  info - just can't seem to get it to work. Sometimes it has worked on
  other installations that I have done from scratch - just not from my
  main Ubuntu that I have been upgrading from 14.04, 16.04, 18.04 etc.
  not including a valid xorg.conf has helped in some situations. When I
  load the driver from Other Drivers, it loadsa, and ten doesn't sart up
  until I go into repair mode and delete the nvidia drives completely.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-utils-390 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  AptOrdering:
   libcuda1-340:amd64: Remove
   nvidia-opencl-icd-340:amd64: Remove
   libnvidia-compute-390:amd64: Install
   nvidia-utils-390:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Tue Nov 27 22:49:53 2018
  ErrorMessage: trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is 
also in package nvidia-340 340.107-0ubuntu0.18.04.1
  InstallationDate: Installed on 2018-05-18 (193 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-utils-390 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/bin/nvidia-bug-report.sh', which is also in package 
nvidia-340 340.107-0ubuntu0.18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1805556/+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 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

[siyia]

all i did differently was load my own dsdt with your ssdts tables, with
your dsdt table and your ssdts my pc wouldnt boot,please post them here
as attachments so everyone can test please

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1776563/+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.8 -proposed tracker

[Brad Figg]

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

** 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: Packaging
- phase-changed: Wednesday, 12. December 2018 14:10 UTC
+ phase-changed: Wednesday, 12. December 2018 17:09 UTC
  reason:
-   prepare-package: Package not yet uploaded
prepare-package-signed: Package not yet uploaded

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

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

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

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: Packaging
  phase-changed: Wednesday, 12. December 2018 17:09 UTC
  reason:
prepare-package-signed: Package not yet uploaded

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.7~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: Uploaded
  phase-changed: Tuesday, 11. December 2018 22:04 UTC
- reason:
-   promote-to-proposed: Manual kernel-block/kernel-block-ppa present

-- 
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.7~16.04.1 -proposed tracker

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

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: Uploaded
  phase-changed: Tuesday, 11. December 2018 22:04 UTC

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 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

[Richard Baka]

siyia, why would I ask it if they didn't worked well? They work
correctly so you did something wrong. Show me a dmesg with custom table
loading.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

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

[Sean Feole]

** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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:
  Incomplete
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-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:
  Confirmed
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:
automated-testing: Testing FAILED
certification-testing: Testing in progress
verification-testing: Testing in progress

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 1806659] Re: linux: 4.15.0-43.46 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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
  
  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:
automated-testing: Testing FAILED
certification-testing: Testing in progress
-   regression-testing: Testing in progress
verification-testing: 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/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:
  Incomplete
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-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:
  Confirmed
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:
automated-testing: Testing FAILED
certification-testing: Testing in progress
verification-testing: Testing in progress

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 1808185] [NEW] Bionic update: upstream stable patchset 2018-12-12

[Kamal Mostafa]

Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2018-12-12 (ported from v4.14.54 and v4.17.5)
   from git://git.kernel.org/

x86/mm: Don't free P4D table when it is folded at runtime
ARM64: dts: meson-gxl-s905x-p212: Add phy-supply for usb0
drm/i915: Fix PIPESTAT irq ack on i965/g4x
drm/amd/display: release spinlock before committing updates to stream
drm/amdgpu: GPU vs CPU page size fixes in amdgpu_vm_bo_split_mapping
drm/amdgpu: Don't default to DC support for Kaveri and older
drm/amdgpu: remove DC special casing for KB/ML
drm/i915/dp: Send DPCD ON for MST before phy_up
drm/amd/display: Clear connector's edid pointer
drm/amdgpu: fix clear_all and replace handling in the VM (v2)
iio: mma8452: Fix ignoring MMA8452_INT_DRDY
usb: typec: tcpm: fix logbuffer index is wrong if _tcpm_log is re-entered
net: dsa: b53: Add BCM5389 support
net/sonic: Use dma_mapping_error()
platform/x86: asus-wmi: Fix NULL pointer dereference
sched/core: Require cpu_active() in select_task_rq(), for user tasks
sched/core: Fix rules for running on online && !active CPUs
fs: clear writeback errors in inode_init_always
perf bpf: Fix NULL return handling in bpf__prepare_load()
perf test: "Session topology" dumps core on s390
net: qmi_wwan: Add Netgear Aircard 779S
atm: zatm: fix memcmp casting
iwlwifi: pcie: compare with number of IRQs requested for, not number of CPUs
ipvs: fix buffer overflow with sync daemon and service
netfilter: nft_limit: fix packet ratelimiting
s390/dasd: use blk_mq_rq_from_pdu for per request data
netfilter: ebtables: handle string from userspace with care
afs: Fix directory permissions check
xfrm6: avoid potential infinite loop in _decode_session6()
ARM: dts: imx6q: Use correct SDMA script for SPI5 core
netfilter: nf_tables: use WARN_ON_ONCE instead of BUG_ON in nft_do_chain()
netfilter: ip6t_rpfilter: provide input interface for route lookup
netfilter: don't set F_IFACE on ipv6 fib lookups
netfilter: nf_tables: fix NULL-ptr in nf_tables_dump_obj()
netfilter: nf_tables: add missing netlink attrs to policies
netfilter: nf_tables: fix memory leak on error exit return
netfilter: nf_tables: increase nft_counters_enabled in nft_chain_stats_replace()
netfilter: nf_tables: disable preemption in nft_update_chain_stats()
netfilter: nft_meta: fix wrong value dereference in nft_meta_set_eval
netfilter: nf_tables: bogus EBUSY in chain deletions
netfilter: nf_tables: don't assume chain stats are set when jumplabel is set
netfilter: nft_compat: fix handling of large matchinfo size
netfilter: nft_compat: prepare for indirect info storage
netfilter: nf_tables: nft_compat: fix refcount leak on xt module
drm/i915: Enable provoking vertex fix on Gen9 systems.
drm/amdgpu: Refactor amdgpu_vram_mgr_bo_invisible_size helper
drm/amdgpu: Use kvmalloc_array for allocating VRAM manager nodes array
drm/atmel-hlcdc: check stride values in the first plane
drm/qxl: Call qxl_bo_unref outside atomic context
drm/amdgpu: fix the missed vcn fw version report
drm/amdgpu: Add APU support in vi_set_vce_clocks
drm/amdgpu: Add APU support in vi_set_uvd_clocks
vt: prevent leaking uninitialized data to userspace via /dev/vcs*
serdev: fix memleak on module unload
serial: 8250_pci: Remove stalled entries in blacklist
staging: android: ion: Return an ERR_PTR in ion_map_kernel
n_tty: Access echo_* variables carefully.
n_tty: Fix stall at n_tty_receive_char_special().
xhci: Fix kernel oops in trace_xhci_free_virt_device
usb: typec: ucsi: Fix for incorrect status data issue
usb: typec: ucsi: acpi: Workaround for cache mode issue
acpi: Add helper for deactivating memory region
usb: dwc2: fix the incorrect bitmaps for the ports of multi_tt hub
USB: serial: cp210x: add Silicon Labs IDs for Windows Update
USB: serial: cp210x: add CESINEL device ids
usb: cdc_acm: Add quirk for Uniden UBC125 scanner

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the 

[Kernel-packages] [Bug 1785171] Re: Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver keeps Dropping Internet Connection

[og11]

Some update comments on the issue with the Ubuntu 18.04 network
connectivity that started as soon as I installed Ubuntu Server 18.04
with the motherboard using this Intel i219-v network adapter.

The issue is getting worse, not better.  Previously the "drop" of the
network connection with Ubuntu Server 18.04 would occur every 2 or 3
days. But now the drops are occurring multiple times daily.  I don't
even need to be using/doing anything on the machine anymore.  The
network connection will be fine once second and then down a minute
later. The only way to get it back is to "disconnect" manually (in the
Ubuntu software setting for the adapter) and then reconnect manually.

No dual boot system, etc. It's a plain as can be Linux server that right
now is not of much use because the network connectivity (something that
should be 100% stable) keeps cutting out.

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

Title:
  Intel I219-V Ethernet Interface on Ubuntu Linux Using e1000e Driver
  keeps Dropping Internet Connection

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

Bug description:
  I've turned up many, many new server and workstation systems over the
  years on both Linux and Windows. Never seen anything like this
  behaviour I'm witnessing on Ubuntu Server 18.04 before where I simply
  lose Internet connectivity while using a browser.  Ethernet interfaces
  usually either work or they don't work.

  I've configured the Intel I219-V Ethernet interface (wired Ethernet
  connection, there is no wifi on this system) using the e1000e driver
  for Ubuntu.  The Ethernet connection is configured to use
  NetworkManager via Netplan on Ubuntu 18.04 LTS Server version.  ASRock
  Z370m Pro4 motherboard.

  The Ethernet interface will drop the Internet connectivity when I'm
  using either the Firefox or Chrome browser.  It usually happens when
  I'm using the search features of the browser. I can't figure out what
  would cause this type of behaviour.  When the Internet connection
  drops, the only way to get back Internet connectivity is to disconnect
  the wired connection using the Ubuntu features and then re-connect
  (this restarts the NetworkManager service I notice).

  In the NetworkManager logs I do notice an "auth" error about a file or
  directory not found. I've never seen that before.

  Note:  The auth error does not coincide with the loss of Internet
  connectivity, but it does proceed it.  Often there can be many hours
  between the auth error and the actual loss of Internet connectivity.

  After I reconnect the connection (via re-starting the NetworkManager
  service) all will be fine for up to a day or so, but then I stress
  test it with a bunch of searches using the browser and usually I can
  get the Internet connectivity to drop again.  Repeat the disconnect
  and reconnect process again (aka re-start NetworkManager) and the
  Internet connectivity will be fine again.  The longest I've seen it go
  without an "Internet connectivity drop" issue is about 36 hours.

  I notice that the e1000e driver does not list the I219-V as a
  supported Ethernet interface in the Intel documentation for the Linux
  version of the driver.  I'm not sure why that is.  The I219-V is
  supposed to used another driver, but it's not clear there's a Linux
  version for of the driver for the I219-V.

  I'm really disappointed that I've run into this issue with Ubuntu
  Server LTS 18.04 on this motherboard.  I had CentOS Server 7.4 (my
  standard server OS, a great Linux distro) on this same motherboard for
  a week with no issues, so I know the motherboard and the I219-V
  Ethernet interface are 100% good hardware wise and can work properly.
  CentOS 7.4 uses NetworkManager as the default for managing the
  Ethernet interface.

  The only reason I'm using Ubuntu Server 18.04 on this motherboard is
  because of a specific package that Ubuntu has a newer packaged version
  than CentOS. CentOS is extremely stable when it comes to basic server
  functionality.

  Hopefully, this bug with the I219-V Ethernet interface using the
  e1000e drive for Linux can be verified and a fix rolled out.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785171/+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 1775732] Re: arm64 soft lock crashes on nova-compute charm running

[Junien Fridrick]

4.19 appears to fix this problem

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

Title:
  arm64 soft lock crashes on nova-compute charm running

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

Bug description:
  Discovered on bionic, arm64 (Moonshot, verified on multiple swirlix
  cartridges), 4.15.0-22-generic.

  After deploying the nova-compute Juju charm, on subsequent reboots,
  within a few seconds after complete boot, everything will freeze and
  eventually display on the serial console (just these, no traces):

  [  188.010510] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! 
[juju-log:2272]
  [  216.010292] watchdog: BUG: soft lockup - CPU#1 stuck for 23s! 
[juju-log:2272]

  (From here on, "lock up" refers to that sequence: boot a kernel, it
  completes boot to login prompt, then everything freezes a few seconds
  later, then BUGs.)

  It's usually but not always juju-log, sometimes a relation-ids or
  similar.  I was able to briefly notice that it was in its startup
  config-changed hook.

  I've separated out and tested nearly everything it does during its
  startup config-changed (sets up bridging, writes some config files,
  restarts libvirtd/nova-compute/etc) without being able to trigger the
  bug, but I suspect proximity to boot is a factor.  If I disable jujud-
  unit-nova-compute startup, boot, log in, re-enable and start (by which
  time over a minute or so has elapsed from boot finish), it will not
  lock up.  Similarly, if I wrap the jujud startup in a `strace -Ff -o
  /var/log/strace.log` (which slows it down massively), it will not lock
  up.  Watched pot syndrome.

  I've tried kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/
  .  I noticed most of the recent arm64 mainline kernels had failed
  builds, notified the kernel team channel and apw fixed the issue and
  started some rebuilds.

  What I've discovered (after many dead ends and a futile bisection) is
  that mainline builds before the rebuilds lock up, but fixed mainline
  builds initiated by apw DO NOT lock up.  e.g.
  4.16.3-041603.201804190730 locks up, but 4.16.6-041606.201806042022
  does not lock up.  (4.16.4 and 4.16.5 appear to have never been
  rebuilt and don't have arm64 debs, and that period is what I tried to
  bisect after figuring a fix must be in there.)

  But when I try to compile any of these recent kernels myself, they
  lock up when booted.  Same kernel configs, tried on both bionic and in
  a cosmic chroot, tried both native arm64 compile and cross-compile
  from amd64. e.g. 4.16.6-041606.201806042022 from k.u.c does not lock
  up, but when I build it myself, it does.

  TBC, I've verified lock ups on the following kernels (all assume
  kernel configs from their respective Ubuntu or k.u.c mainline builds):

  - 4.15.0-22-generic from bionic (both Ubuntu-provided and my own recompile)
  - v4.16 (and all point releases)
  - v4.17

  As I write this, my compiled v4.10 DOES NOT appear to lock up.  I will
  attempt to bisect at a macro level from 4.10..4.15 and dig deeper.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun  2 04:22 seq
   crw-rw 1 root audio 116, 33 Jun  2 04:22 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Jun  8 00:13:05 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Sean Feole]

** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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: 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 1806665] Re: linux-azure: 4.15.0-1036.38 -proposed tracker

[Sean Feole]

** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

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 1806665] Re: linux-azure: 4.15.0-1036.38 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Testing in progress
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Bionic:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 11:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

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 1806952] Re: linux: 4.19.0-8.9 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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
  
  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
-   regression-testing: 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:
  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: 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 1724068] Re: Ralink Bluetooth is not recognized on Ubuntu 17.10

[Sebastien Bacher]

** Package changed: gnome-control-center (Ubuntu) => linux (Ubuntu)

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

Title:
  Ralink Bluetooth is not recognized on Ubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, hello, I have a problem with my ASUS k550DP and my integrated 
Bluetooth Ralink device, with Ubuntu 17.10
  the rfkill list all command does not show me the Bluetooth device

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

[Sean Feole]

** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

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 1806672] Re: linux-azure: 4.15.0-1036.38~16.04.1 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => 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: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Testing in progress
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Promoted to proposed
  phase-changed: Friday, 07. December 2018 15:03 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

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 1724068] [NEW] Ralink Bluetooth is not recognized on Ubuntu 17.10

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hello, hello, I have a problem with my ASUS k550DP and my integrated Bluetooth 
Ralink device, with Ubuntu 17.10
the rfkill list all command does not show me the Bluetooth device

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


** Tags: 17.10 artful bluetooth ubuntu unrecognized
-- 
Ralink Bluetooth is not recognized on Ubuntu 17.10
https://bugs.launchpad.net/bugs/1724068
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

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

[Brad Figg]

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

** 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: Uploaded
- phase-changed: Monday, 10. December 2018 20:39 UTC
+ phase: Packaging
+ phase-changed: Wednesday, 12. December 2018 14:10 UTC
  reason:
-   promote-to-proposed: Manual kernel-block/kernel-block-ppa present
+   prepare-package: Package not yet uploaded
+   prepare-package-signed: Package not yet uploaded

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

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

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

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: Packaging
  phase-changed: Wednesday, 12. December 2018 14:10 UTC
  reason:
prepare-package: Package not yet uploaded
prepare-package-signed: Package not yet uploaded

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 1805849] Re: apt repository in proposed packages availability issue

[Joseph Salisbury]

I received information that this is how -proposed works for kernels.  It
appears you are trying to install the kernel before the signing bits are
done.

What needs to be done, is to wait until all of the consistent sets are
published.  Waiting for linux-signed-azure to be completely published
for _binaries_ would work.

Does this help?

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

Title:
  apt repository in proposed packages availability issue

Status in linux package in Ubuntu:
  Triaged
Status in linux-azure package in Ubuntu:
  Triaged

Bug description:
  We have a watcher that does the following:
  - verifies if any linux-azure kernels have been published in proposed repo.
  - if it detects one, it will install.

  The problem we have is that even though we detect a new kernel in proposed, 
the installation of it will fail as there are unmet package dependencies not 
being available.
  This does resolve after several hours, but the way it works is not reliable 
that we see the main package being available, but the packages in the repo are 
not ready yet.
  So it seems to be a timing issue from the time the kernel is released, and 
the time the packages actual get on the repo.

  Can you please suggest on some methods to better handle the detect &
  install for these, or some suggestions to how we do this from below.

  How we search for new kernel availability from proposed:
  #apt-cache madison linux-azure | grep ${release}-proposed

  But doing an install right after that will fail most of the times if the 
kernel was just published:
  #apt clean all
  #apt -y update
  #apt install linux-azure/$release
  ^ this is after we add the proposed repo in sources.list.

  Actual error in the end:
  linux-azure : Depends: linux-image-azure (= 4.15.0.1034.34) but 4.15.0.1030.30
  E: Unable to correct problems, you have held broken packages.

  This is observed on all LTS versions.

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

[Michał Sawicz]

I'm back to having to re-pair a handful of times each boot. It seems
every once in a while the pairing "sticks" and works until I have to
reconnect it again.

-- 
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.net/ListHelp

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

[Marcelo Cerri]

** Summary changed:

- linux-oracle: 4.15.0-1007.7 -proposed tracker
+ linux-oracle: 4.15.0-1007.8 -proposed tracker

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

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Fix Released => 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.8 -proposed tracker

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

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: Uploaded
  phase-changed: Monday, 10. December 2018 20:39 UTC
  reason:
promote-to-proposed: Manual kernel-block/kernel-block-ppa present

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 1805821] Re: [amdgpu] GUI performance is poor

[Timo Aaltonen]

you are using a dkms from 'amdgpu-pro', so you should report the bug to
AMD, we don't support it

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: New => Invalid

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

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

Title:
  [amdgpu] GUI performance is poor

Status in linux package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid

Bug description:
  Response is slow, amdgpu driver gives warning in dmesg which is below

  [0.00] Linux version 4.15.0-36-generic (buildd@lgw01-amd64-031) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 
2018 (Ubuntu 4.15.0-36.39-generic 4.15.18)
  [0.00] random: get_random_u32 called from bsp_init_amd+0x255/0x2a0 
with crng_init=0
  [0.966765] amd_uncore: AMD NB counters detected
  [1.165305] pcie_mp2_amd: AMD(R) PCI-E MP2 Communication Driver Version: 
1.0
  [1.716922] amdkcl: loading out-of-tree module taints kernel.
  [1.716947] amdkcl: module verification failed: signature and/or required 
key missing - tainting kernel
  [1.827886] [drm] amdgpu kernel modesetting enabled.
  [1.827887] [drm] amdgpu version: 18.30.2.15
  [1.833528] fb: switching to amdgpudrmfb from EFI VGA
  [1.850977] amdgpu :00:01.0: VRAM: 1024M 0x00F4 - 
0x00F43FFF (1024M used)
  [1.850979] amdgpu :00:01.0: GTT: 1024M 0x - 
0x3FFF
  [1.851137] [drm] amdgpu: 1024M of VRAM memory ready
  [1.851139] [drm] amdgpu: 14975M of GTT memory ready.
  [1.851291] [drm] amdgpu: dpm initialized
  [1.853722] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:1! type 0 expected 3
  [1.853779] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:3! type 0 expected 3
  [1.853825] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:4! type 0 expected 3
  [1.853872] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector 
ObjectID from Adapter Service for connector index:5! type 0 expected 3
  [2.064038] fbcon: amdgpudrmfb (fb0) is primary device
  [2.128334] amdgpu :00:01.0: fb0: amdgpudrmfb frame buffer device
  [2.145953] [drm] Initialized amdgpu 3.26.0 20150101 for :00:01.0 on 
minor 0
  [5.265031] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [6.277293] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [7.289439] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [8.301565] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [9.313691] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [   10.325849] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [   11.338007] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [   12.350159] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [   13.362305] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [   14.374463] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
trying to reset the ECPU!!!
  [   14.394355] [drm:vce_v2_0_start [amdgpu]] *ERROR* VCE not responding, 
giving up!!!
  [   14.394396] [drm:amdgpu_device_ip_set_powergating_state [amdgpu]] *ERROR* 
set_powergating_state of IP block  failed -110
  [   15.420234] [drm:amdgpu_vce_ring_test_ib [amdgpu]] *ERROR* amdgpu: IB test 
timed out.
  [   15.420321] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed 
testing IB on ring 12 (-110).
  [   15.420369] [drm:amdgpu_device_ip_late_init_func_handler [amdgpu]] *ERROR* 
ib ring test failed (-110).
  [   23.736730] EDAC amd64: Node 0: DRAM ECC disabled.
  [   23.736731] EDAC amd64: ECC disabled in the BIOS or no ECC capability, 
module will not load.
  [ 1566.370793] audit: type=1400 audit(1543500426.678:40): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/usr/share/libdrm/amdgpu.ids" pid=7169 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  
  Takes too for software center to install .deb package where as it happens in 
a few seconds in terminal via dpkg -i.

  Problems are after installation of amdgpu.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  

[Kernel-packages] [Bug 1802021] Re: [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

[Joseph Salisbury]

Hi Joshua,

I will touched base with Gavin to compare our trees.  My test kernel is the 
current Azure kernel with two commits applied: d633198088bd9 and 
eb4c2382272ae7.  Commit eb4c2382272ae7 being the patch from 
Dennis Krein in linux-next:

eb4c2382272a ("srcu: Lock srcu_data structure in srcu_gp_start()")

Gavin and I both had the same set of commits.  I can submit and SRU
request for this if you don't want to wait for the testing, since it
could take a long time.  If I submit it this week, it won't land in the
Azure kernel until the next SRU cycle in the new year.  Just let us know
what you think.

Here are the dates for the next cycle:

cycle: 14-Jan through 03-Feb

 11-Jan   Last day for kernel commits for this cycle.
14-Jan - 18-Jan   Kernel prep week.
21-Jan - 01-Feb   Bug verification & Regression testing.
 31-Jan   Release 18.04.2 kernels to -updates
 04-Feb   Release remaining kernels to -updates.

Looking at these dates, we may want to SRU it this week, due to a
Company shutdown between 24-Dec and 06-Jan.

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

Title:
  [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start()

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  We had a customer seeing traces like the following:

  tack trace from kern.log:
  2018-10-10T04:43:08.542464+00:00 hbp2ann-2 kernel: INFO: task 
kworker/u16:0:16678 blocked for more than 120 seconds.
  2018-10-10T04:43:08.542503+00:00 hbp2ann-2 kernel: Not tainted 
4.15.0-1023-azure #24~16.04.1-Ubuntu
  2018-10-10T04:43:08.542513+00:00 hbp2ann-2 kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  2018-10-10T04:43:08.547366+00:00 hbp2ann-2 kernel: kworker/u16:0 D 0 16678 2 
0x8000
  2018-10-10T04:43:08.547386+00:00 hbp2ann-2 kernel: Workqueue: events_unbound 
fsnotify_mark_destroy_workfn
  2018-10-10T04:43:08.547395+00:00 hbp2ann-2 kernel: Call Trace:
  2018-10-10T04:43:08.547413+00:00 hbp2ann-2 kernel: __schedule+0x3d6/0x8b0
  2018-10-10T04:43:08.547422+00:00 hbp2ann-2 kernel: ? 
check_preempt_wakeup+0xfb/0x240
  2018-10-10T04:43:08.547431+00:00 hbp2ann-2 kernel: ? 
sched_clock_local+0x17/0x90
  2018-10-10T04:43:08.547440+00:00 hbp2ann-2 kernel: schedule+0x36/0x80
  2018-10-10T04:43:08.547448+00:00 hbp2ann-2 kernel: 
schedule_timeout+0x1db/0x370
  2018-10-10T04:43:08.547458+00:00 hbp2ann-2 kernel: ? 
__enqueue_entity+0x5c/0x60
  2018-10-10T04:43:08.547467+00:00 hbp2ann-2 kernel: ? 
enqueue_entity+0x112/0x670
  2018-10-10T04:43:08.547477+00:00 hbp2ann-2 kernel: 
wait_for_completion+0xb4/0x140
  2018-10-10T04:43:08.547486+00:00 hbp2ann-2 kernel: ? wake_up_q+0x70/0x70
  2018-10-10T04:43:08.547510+00:00 hbp2ann-2 kernel: 
__synchronize_srcu.part.13+0x85/0xb0
  2018-10-10T04:43:08.547535+00:00 hbp2ann-2 kernel: ? 
trace_raw_output_rcu_utilization+0x50/0x50
  2018-10-10T04:43:08.547560+00:00 hbp2ann-2 kernel: synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547594+00:00 hbp2ann-2 kernel: ? 
synchronize_srcu+0xd3/0xe0
  2018-10-10T04:43:08.547604+00:00 hbp2ann-2 kernel: 
fsnotify_mark_destroy_workfn+0x7c/0xe0
  2018-10-10T04:43:08.547612+00:00 hbp2ann-2 kernel: 
process_one_work+0x14d/0x410
  2018-10-10T04:43:08.547620+00:00 hbp2ann-2 kernel: worker_thread+0x4b/0x460
  2018-10-10T04:43:08.547628+00:00 hbp2ann-2 kernel: kthread+0x105/0x140
  2018-10-10T04:43:08.547637+00:00 hbp2ann-2 kernel: ? 
process_one_work+0x410/0x410
  2018-10-10T04:43:08.547645+00:00 hbp2ann-2 kernel: ? 
kthread_destroy_worker+0x50/0x50
  2018-10-10T04:43:08.547654+00:00 hbp2ann-2 kernel: ? do_syscall_64+0x73/0x130
  2018-10-10T04:43:08.547677+00:00 hbp2ann-2 kernel: ? SyS_exit_group+0x14/0x20
  2018-10-10T04:43:08.547685+00:00 hbp2ann-2 kernel: ret_from_fork+0x35/0x40

  Error Code: INFO: task kworker/u16:0:16678 blocked for more than 120
  seconds.

  We are seeing more issue with fsnotify related callbacks. These are
  not a soft/hard lockup but seem to significantly degrade the
  responsiveness of systemd (and from there everything else).

  The following upstream commit may fix this issue, but it is in Paul's
  RCU tree and not in linux-next or upstream yet:

  https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-
  rcu.git/commit/?h=dev=1a05c0cd2fee234a10362cc8f66057557cbb291f

  srcu: Lock srcu_data structure in srcu_gp_start()
  The srcu_gp_start() function is called with the srcu_struct structure's
  ->lock held, but not with the srcu_data structure's ->lock.  This is
  problematic because this function accesses and updates the srcu_data
  structure's ->srcu_cblist, which is protected by that lock.  Failing to
  hold this lock can result in corruption of the SRCU callback lists,
  which in turn can result in arbitrarily bad results.

  This commit therefore makes 

[Kernel-packages] [Bug 1804149] Re: Kernel panic, Oops: 0004 ilc:3 [#1] SMP, iscsi_q_20 iscsi_xmitworker [libiscsi]

[Frank Heimes]

Having a look at the new logs it shows that there are many different disks and 
disk systems in use.
I see DASDs, that get partly unhappy, like:
Dec  8 07:43:29 ilabg3 kernel: [651348.534047] dasd(eckd): I/O status report 
for device 0.0.248b:
Dec  8 07:43:29 ilabg3 kernel: [651348.534047] dasd(eckd): in req: 
6004d11c CC:00 FC:01 AC:00 SC:01 DS:00 CS:00 RC:0
Dec  8 07:43:29 ilabg3 kernel: [651348.534047] dasd(eckd): device 0.0.248b: 
Failing CCW:   (null)
Dec  8 07:43:29 ilabg3 kernel: [651348.534047] dasd(eckd): SORRY - NO VALID 
SENSE AVAILABLE
Dec  8 07:43:29 ilabg3 kernel: [651348.534072] dasd(eckd): Related CP in req: 
6004d11c
Dec  8 07:43:29 ilabg3 kernel: [651348.534072] dasd(eckd): CCW 
584ecfe4: 274C 7FE86BC0 DAT:  1800 0e00  
Dec  8 07:43:29 ilabg3 kernel: [651348.534072] dasd(eckd): CCW 
a235ae5d: 3E000200 7FEDD400 DAT:     
(of course not related to the reported issue)
I see 'local' scsi disks:
scsi 3:0:12:0: Direct-Access IBM  FlashSystem-9840 1600 PQ: 0 ANSI: 5
and I see XIV Storage as well.

I noticed a lot of 'Power-on or device reset's, as well as many 'LUN scan's and 
multipath path failures on a single day on that environment, like:
sd 9:0:0:1: tag#58 Add. Sense: Power on, reset, or bus device reset occurred
...
Dec  8 14:01:07 ilabg3 kernel: [2.127745] sd 3:0:0:0: scsi scan: REPORT LUN 
scan
...
[458582.527232] device-mapper: multipath: Failing path 66:112.
[458582.527234] print_req_error: I/O error, dev sdan, sector 15001576
That seems to be very odd and points to an issue with the SAN infrastructure 
and/or setup...

The error messages that belong to the Ops seem to be known and points to a 
potential race discussed here:
[RFC,1/1] libiscsi: Fix race between iscsi_xmit_task and iscsi_complete_task
https://patchwork.kernel.org/patch/10501773/
Well, the situation above may even favor a race condition like this ...

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

Title:
  Kernel panic,Oops: 0004 ilc:3 [#1] SMP,  iscsi_q_20 iscsi_xmitworker
  [libiscsi]

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

Bug description:
  == Comment: #0 - Michael Finnegan  - 2018-11-19 14:14:40 
==
  ---Problem Description---
  Kernel panic,Oops: 0004 ilc:3 [#1] SMP,  iscsi_q_20 iscsi_xmitworker 
[libiscsi]
   
  ---uname output---
  Linux ilabg3 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:13:24 UTC 2018 
s390x s390x s390x GNU/Linux
   
  Machine Type = IBM 3906 M05 7G4 (z/VM 7.1.0) 
   
  ---Debugger---
  A debugger is not configured
   
  Contact Information = Michael Finnegan/finne...@us.ibm.com 
   
  Stack trace output:
   dmesg.201811161956
  [1363037.322472] Unable to handle kernel pointer dereference in virtual 
kernel address space
  [1363037.322481] Failing address:  TEID: 0483
  [1363037.322483] Fault in home space mode while using kernel ASCE.
  [1363037.322486] AS:00ea0007 R3:f37d0007 S:f37ff000 
P:013d
  [1363037.322524] Oops: 0004 ilc:3 [#1] SMP
  [1363037.322529] Modules linked in: iptable_filter binfmt_misc 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache qeth_l3 qeth_l2 
s390_trng ghash_s390 prng aes_s390 des_s390 des_generic sha512_s390 sha256_s390 
sha1_s390 sha_common qeth vmur ccwgroup vfio_ccw vfio_mdev mdev 
vfio_iommu_type1 vfio sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core sunrpc 
iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables 
dm_round_robin dm_service_time crc32_vx_s390 dasd_eckd_mod zfcp qdio 
scsi_transport_fc dasd_fba_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua 
dm_multipath
  [1363037.322567] CPU: 3 PID: 37970 Comm: kworker/u128:19 Not tainted 
4.15.0-36-generic #39-Ubuntu
  [1363037.322573] Hardware name: IBM 3906 M05 7G4 (z/VM 7.1.0)
  [1363037.322581] Workqueue: iscsi_q_20 iscsi_xmitworker [libiscsi]
  [1363037.322583] Krnl PSW : c8051cf6 e49a28f4 
(__iscsi_get_task+0x6/0x18 [libiscsi])
  [1363037.322587]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 
PM:0 RI:0 EA:3
  [1363037.322589] Krnl GPRS:  02923ce0 
 0400
  [1363037.322591]03ff80277640 0008 
788efc00 03ff802777cc
  [1363037.322592]03ff8027769c  
 78ce8310
  [1363037.322594]f3689800 78ce83a2 
03ff80272e8e 02923c90
  [1363037.322601] Krnl Code: 03ff80272624: c0f4fcf6  brcl
15,3ff80272010
  03ff8027262a: c0f4377b  brcl
15,3ff80279520
 #03ff80272630: c004  brcl
0,3ff80272630
 >03ff80272636: eb012078006a  

[Kernel-packages] [Bug 1807869] Re: ubuntu_nbd_smoke_test failed with Xenial

[Po-Hsu Lin]

Passed with kernel01, daedalus is still occupied with other jobs, mark
this as fix released.

** Changed in: ubuntu-kernel-tests
   Status: Fix Committed => 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/1807869

Title:
  ubuntu_nbd_smoke_test failed with Xenial

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Spotted in this cycle with node:
   * daedalus (amd64-lowlatency) - https://pastebin.ubuntu.com/p/JxYNh9JPJd/
   * daedalus (amd64-generic) - https://pastebin.ubuntu.com/p/4W8gDSDVqm/
   * kernel01 (s390x.zVM) - https://pastebin.ubuntu.com/p/kFW7KQbbkf/
   
  Error log from kernel01:
  creating backing nbd image /tmp/nbd_image.img
   
  

  Image path:/tmp/nbd_image.img
  Mount point:   /mnt/nbd-test-22282
  Date:  Mon Dec 10 05:22:47 EST 2018
  Host:  kernel01
  Kernel:4.4.0-141-generic #167-Ubuntu SMP Wed Dec 5 10:32:22 UTC 2018
  Machine:   kernel01 s390x s390x
  CPUs online:   8
  CPUs total:8
  Page size: 4096
  Pages avail:   641567
  Pages total:   977383
  Free space:
  Filesystem   Size  Used Avail Use% 
Mounted on
  udev 1.9G 0  1.9G   0% 
/dev
  tmpfs382M   39M  344M  11% 
/run
  /dev/dasda1  6.7G  6.2G  187M  98% /
  tmpfs1.9G  4.0K  1.9G   1% 
/dev/shm
  tmpfs5.0M 0  5.0M   0% 
/run/lock
  tmpfs1.9G 0  1.9G   0% 
/sys/fs/cgroup
  /dev/mapper/datavg-home   21G  3.1G   17G  17% 
/home
  testpool.3622624G  128K   24G   1% 
/testpool.36226
  testpool.36226/testfs.36226   24G  128K   24G   1% 
/var/tmp/testdir36226
  testpool.36226/testfs.36226/clone 24G  128K   24G   1% 
/var/tmp/testdir36226/clone
  testpool.36226/testfs.36226/renameme  24G  128K   24G   1% 
/var/tmp/testdir36226/renameme
  testpool.36226/testfs.36226/shared24G  128K   24G   1% 
/var/tmp/testdir36226/shared
  testpool.36226/testfs.36226/testfs2.36226 24G  128K   24G   1% 
/var/tmp/testdir36226/testfs2.36226
  testpool.36226/testfs.36226/testfs2.36226.unmounted   24G  128K   24G   1% 
/var/tmp/testdir36226/testfs2.36226.unmounted
  testpool.36226/testfs.36226/unshared  24G  128K   24G   1% 
/var/tmp/testdir36226/unshared
  tmpfs382M 0  382M   0% 
/run/user/1000
  tmpfs100K 0  100K   0% 
/var/lib/lxd/shmounts
  tmpfs100K 0  100K   0% 
/var/lib/lxd/devlxd
  

   
  NBD device /dev/nbd0 created
  found nbd export
  NBD exports found:
  test
  starting clien with NBD device /dev/nbd0
  Negotiation: ..size = 128MB
  creating ext4 on /dev/nbd0
  mkfs on /dev/nbd0 failed
  unmounting /mnt/nbd-test-22282
  stopping client
  disconnect, sock, done
  killing server
  stderr:
  bs=1024, sz=134217728 bytes
  timeout=30
  umount: /mnt/nbd-test-22282: mountpoint not found

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-141-generic 4.4.0-141.167
  ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
  Uname: Linux 4.4.0-141-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Tue Dec 11 04:08:37 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M nobp=1 BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-141-generic N/A
   linux-backports-modules-4.4.0-141-generic  N/A
   linux-firmware 1.157.21
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log 

[Kernel-packages] [Bug 1805920] Re: iPXE ignores vlan 0 traffic

[Christian Ehrhardt ]

FYI: virt stack regression tests started but will still take a while.

To make it very very clear, this is incomplete until some path to test was 
provided.
Marking the bug that way, waiting on that.

Worst case (and only then) describe the test setup that you have on the 
customer site and volunteer to be willing and able to verify both Bionic and 
Cosmic on that setup.
While writing remember the intention is to make the SRU team feel confident 
about the change and the checks.

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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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]

   * TODO

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

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

[Po-Hsu Lin]

** Tags added: regression-testing-passed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/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: Master bug not ready for release
promote-to-updates: 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 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:
-   regression-testing: Testing in progress
+   promote-to-security: Master bug not ready for release
+   promote-to-updates: 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: Master bug not ready for release
promote-to-updates: 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 1806578] Re: linux-kvm: 4.4.0-1039.45 -proposed tracker

[Po-Hsu Lin]

4.4.0-1039.45 - kvm
Regression test CMPL, RTB.

42 / 43 tests were run, missing: ubuntu_boot
Issue to note in amd64:
  ubuntu_fan_smoke_test - ubuntu_fan_smoke_test failed on 4.4 X-kvm kernel (bug 
1763323)
  ubuntu_kvm_unit_tests - 45 failed on KVM nodes
  ubuntu_ltp_syscalls - getrandom02 timed out (bug 1797327) inotify07 (bug 
1774387) inotify08 (bug 1775784) fanotify09-2 (bug 1804594) fanotify10 (bug 
1802454) msgstress03 (bug 1797341) quotactl01, quotactl02, quotactl03 (bug 
1797325)
  ubuntu_lxc - python3 API failed (bug 1764618)
  ubuntu_quota_smoke_test - failed with KVM kernel (bug 1784535)


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

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

-- 
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:
regression-testing: Testing in progress

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 1808116] PulseList.txt

[Andrzej]

apport information

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

Title:
  4.15 and higher kernels do not read the SD card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  4.15 and higher kernels do not read the SD card.
  kernel 4.13 reads the SD card.

  Checked with a 64GB Samsung and 16 GB card from another manufacturer.
  Also 4.19.8 kernel does not read cards

  
  inxi -Fxz 
  System:    Host: ASUS Kernel: 4.13.0-45-generic x86_64 (64 bit gcc: 5.4.0) 
Desktop: KDE Plasma 5.8.9 (Qt 5.6.1) 
    Distro: Linux Mint 18.3 Sylvia 
  Machine:   Mobo: ASUSTeK model: E200HA v: 1.0 Bios: American Megatrends v: 
E200HA.303 date: 12/21/2016 
  CPU:   Quad core Intel Atom x5-Z8350 (-MCP-) cache: 1024 KB 
    flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11520 
    clock speeds: max: 1920 MHz 1: 1920 MHz 2: 1920 MHz 3: 486 MHz 4: 
505 MHz 
  Graphics:  Card: Intel Device 22b0 bus-ID: 00:02.0 
    Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) 
Resolution: 1366x768@60.06hz 
    GLX Renderer: Mesa DRI Intel HD Graphics (Cherrytrail) 
    GLX Version: 3.0 Mesa 18.0.5 Direct Rendering: Yes 
  Audio: Card Intel HDMI/DP LPE Audio driver: HdmiLpeAudio Sound: ALSA v: 
k4.13.0-45-generic 
  Network:   Card: Qualcomm Atheros Device 0042 driver: ath10k_pci bus-ID: 
01:00.0 
    IF: wlp1s0 state: up speed: N/A duplex: N/A mac:  
  Drives:    HDD Total Size: NA (-) ID-1: /dev/mmcblk0 model: N/A size: 31.3GB 
  Partition: ID-1: / size: 25G used: 21G (89%) fs: ext4 dev: /dev/mmcblk0p2 
    ID-2: swap-1 size: 4.18GB used: 0.00GB (0%) fs: swap dev: 
/dev/mmcblk0p3 
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present 
  Sensors:   System Temperatures: cpu: 40.0C mobo: N/A 
    Fan Speeds (in rpm): cpu: 0 
  Info:  Processes: 225 Uptime: 1 min Memory: 1101.6/3839.9MB Init: systemd 
runlevel: 5 Gcc sys: 5.4.0 
    Client: Shell (bash 4.3.481) inxi: 2.2.35 


  without a SD card inserted

  dmesg | grep mmc 
  [    2.994522] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA 
  [    3.013437] mmc1: SDHCI controller on ACPI [80860F14:03] using ADMA 
  [    3.323762] mmc0: new HS200 MMC card at address 0001 
  [    3.330155] mmcblk0: mmc0:0001 BJNB4R 29.1 GiB  
  [    3.330320] mmcblk0boot0: mmc0:0001 BJNB4R partition 1 4.00 MiB 
  [    3.330482] mmcblk0boot1: mmc0:0001 BJNB4R partition 2 4.00 MiB 
  [    3.330641] mmcblk0rpmb: mmc0:0001 BJNB4R partition 3 4.00 MiB 
  [    3.334332]  mmcblk0: p1 p2 p3 
  [    4.495608] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data 
mode. Opts: (null) 
  [    5.863405] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro 
  [    6.827393] Adding 4085756k swap on /dev/mmcblk0p3.  Priority:-1 extents:1 
across:4085756k SSFS

  
  with inserted SD card

  dmesg | grep mmc 
  [    2.994522] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA 
  [    3.013437] mmc1: SDHCI controller on ACPI [80860F14:03] using ADMA 
  [    3.323762] mmc0: new HS200 MMC card at address 0001 
  [    3.330155] mmcblk0: mmc0:0001 BJNB4R 29.1 GiB  
  [    3.330320] mmcblk0boot0: mmc0:0001 BJNB4R partition 1 4.00 MiB 
  [    3.330482] mmcblk0boot1: mmc0:0001 BJNB4R partition 2 4.00 MiB 
  [    3.330641] mmcblk0rpmb: mmc0:0001 BJNB4R partition 3 4.00 MiB 
  [    3.334332]  mmcblk0: p1 p2 p3 
  [    4.495608] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data 
mode. Opts: (null) 
  [    5.863405] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro 
  [    6.827393] Adding 4085756k swap on /dev/mmcblk0p3.  Priority:-1 extents:1 
across:4085756k SSFS 
  [  216.577900] mmc1: new ultra high speed SDR104 SDXC card at address 59b4 
  [  216.578575] mmcblk1: mmc1:59b4 0 59.7 GiB  
  [  216.580031]  mmcblk1: p1 
  [  216.857616] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some 
data may be corrupt. Please run fsck.

  
===

  inxi -Fxz 
  System:    Host: ASUS Kernel: 4.15.0-42-generic x86_64 (64 bit gcc: 5.4.0) 
Desktop: KDE Plasma 5.8.9 (Qt 5.6.1) 
    Distro: Linux Mint 18.3 Sylvia 
  Machine:   Mobo: ASUSTeK model: E200HA v: 1.0 Bios: American Megatrends v: 
E200HA.303 date: 12/21/2016 
  CPU:   Quad core Intel Atom x5-Z8350 (-MCP-) cache: 1024 KB 
    flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11520 
    clock speeds: max: 1920 MHz 1: 839 MHz 2: 816 MHz 3: 480 MHz 4: 480 
MHz 
  Graphics:  Card: Intel Device 22b0 bus-ID: 00:02.0 
    Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) 
Resolution: 1366x768@60.06hz 
    GLX 

[Kernel-packages] [Bug 1807341] Re: ubuntu_squashfs_smoke_test failed with Disco

[Po-Hsu Lin]

Passed on another node (the original node is busy), so I think this patch works.
Thanks!

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

** Changed in: ubuntu-kernel-tests
   Status: Fix Committed => 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/1807341

Title:
  ubuntu_squashfs_smoke_test failed with Disco

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  Tested on a KVM node with generic kernel.

  $ sudo 
/home/ubuntu/autotest/client/tests/ubuntu_squashfs_smoke_test/ubuntu_squashfs_smoke_test.sh
 
  Testing with compression method gzip
  Testing mount of squashfs: PASSED (gzip)
  Testing umount of squashfs: PASSED (gzip)
  Checking data integrity: FAILED (squashed /bin different from original /bin, 
gzip)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: User Name 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec  7 07:39 seq
   crw-rw 1 root audio 116, 33 Dec  7 07:39 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu14
  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:
  CurrentDmesg:
   
  Date: Fri Dec  7 07:44:11 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 cirrusdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.176
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

[Andrzej]

apport information

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

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

Title:
  4.15 and higher kernels do not read the SD card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  4.15 and higher kernels do not read the SD card.
  kernel 4.13 reads the SD card.

  Checked with a 64GB Samsung and 16 GB card from another manufacturer.
  Also 4.19.8 kernel does not read cards

  
  inxi -Fxz 
  System:    Host: ASUS Kernel: 4.13.0-45-generic x86_64 (64 bit gcc: 5.4.0) 
Desktop: KDE Plasma 5.8.9 (Qt 5.6.1) 
    Distro: Linux Mint 18.3 Sylvia 
  Machine:   Mobo: ASUSTeK model: E200HA v: 1.0 Bios: American Megatrends v: 
E200HA.303 date: 12/21/2016 
  CPU:   Quad core Intel Atom x5-Z8350 (-MCP-) cache: 1024 KB 
    flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11520 
    clock speeds: max: 1920 MHz 1: 1920 MHz 2: 1920 MHz 3: 486 MHz 4: 
505 MHz 
  Graphics:  Card: Intel Device 22b0 bus-ID: 00:02.0 
    Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) 
Resolution: 1366x768@60.06hz 
    GLX Renderer: Mesa DRI Intel HD Graphics (Cherrytrail) 
    GLX Version: 3.0 Mesa 18.0.5 Direct Rendering: Yes 
  Audio: Card Intel HDMI/DP LPE Audio driver: HdmiLpeAudio Sound: ALSA v: 
k4.13.0-45-generic 
  Network:   Card: Qualcomm Atheros Device 0042 driver: ath10k_pci bus-ID: 
01:00.0 
    IF: wlp1s0 state: up speed: N/A duplex: N/A mac:  
  Drives:    HDD Total Size: NA (-) ID-1: /dev/mmcblk0 model: N/A size: 31.3GB 
  Partition: ID-1: / size: 25G used: 21G (89%) fs: ext4 dev: /dev/mmcblk0p2 
    ID-2: swap-1 size: 4.18GB used: 0.00GB (0%) fs: swap dev: 
/dev/mmcblk0p3 
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present 
  Sensors:   System Temperatures: cpu: 40.0C mobo: N/A 
    Fan Speeds (in rpm): cpu: 0 
  Info:  Processes: 225 Uptime: 1 min Memory: 1101.6/3839.9MB Init: systemd 
runlevel: 5 Gcc sys: 5.4.0 
    Client: Shell (bash 4.3.481) inxi: 2.2.35 


  without a SD card inserted

  dmesg | grep mmc 
  [    2.994522] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA 
  [    3.013437] mmc1: SDHCI controller on ACPI [80860F14:03] using ADMA 
  [    3.323762] mmc0: new HS200 MMC card at address 0001 
  [    3.330155] mmcblk0: mmc0:0001 BJNB4R 29.1 GiB  
  [    3.330320] mmcblk0boot0: mmc0:0001 BJNB4R partition 1 4.00 MiB 
  [    3.330482] mmcblk0boot1: mmc0:0001 BJNB4R partition 2 4.00 MiB 
  [    3.330641] mmcblk0rpmb: mmc0:0001 BJNB4R partition 3 4.00 MiB 
  [    3.334332]  mmcblk0: p1 p2 p3 
  [    4.495608] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data 
mode. Opts: (null) 
  [    5.863405] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro 
  [    6.827393] Adding 4085756k swap on /dev/mmcblk0p3.  Priority:-1 extents:1 
across:4085756k SSFS

  
  with inserted SD card

  dmesg | grep mmc 
  [    2.994522] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA 
  [    3.013437] mmc1: SDHCI controller on ACPI [80860F14:03] using ADMA 
  [    3.323762] mmc0: new HS200 MMC card at address 0001 
  [    3.330155] mmcblk0: mmc0:0001 BJNB4R 29.1 GiB  
  [    3.330320] mmcblk0boot0: mmc0:0001 BJNB4R partition 1 4.00 MiB 
  [    3.330482] mmcblk0boot1: mmc0:0001 BJNB4R partition 2 4.00 MiB 
  [    3.330641] mmcblk0rpmb: mmc0:0001 BJNB4R partition 3 4.00 MiB 
  [    3.334332]  mmcblk0: p1 p2 p3 
  [    4.495608] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data 
mode. Opts: (null) 
  [    5.863405] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro 
  [    6.827393] Adding 4085756k swap on /dev/mmcblk0p3.  Priority:-1 extents:1 
across:4085756k SSFS 
  [  216.577900] mmc1: new ultra high speed SDR104 SDXC card at address 59b4 
  [  216.578575] mmcblk1: mmc1:59b4 0 59.7 GiB  
  [  216.580031]  mmcblk1: p1 
  [  216.857616] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some 
data may be corrupt. Please run fsck.

  
===

  inxi -Fxz 
  System:    Host: ASUS Kernel: 4.15.0-42-generic x86_64 (64 bit gcc: 5.4.0) 
Desktop: KDE Plasma 5.8.9 (Qt 5.6.1) 
    Distro: Linux Mint 18.3 Sylvia 
  Machine:   Mobo: ASUSTeK model: E200HA v: 1.0 Bios: American Megatrends v: 
E200HA.303 date: 12/21/2016 
  CPU:   Quad core Intel Atom x5-Z8350 (-MCP-) cache: 1024 KB 
    flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11520 
    clock speeds: max: 1920 MHz 1: 839 MHz 2: 816 MHz 3: 480 MHz 4: 480 
MHz 
  Graphics:  Card: Intel Device 22b0 bus-ID: 00:02.0 
    Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) 
Resolution: 1366x768@60.06hz 
    GLX 

[Kernel-packages] [Bug 1808116] UdevDb.txt

[Andrzej]

apport information

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

Title:
  4.15 and higher kernels do not read the SD card

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  4.15 and higher kernels do not read the SD card.
  kernel 4.13 reads the SD card.

  Checked with a 64GB Samsung and 16 GB card from another manufacturer.
  Also 4.19.8 kernel does not read cards

  
  inxi -Fxz 
  System:    Host: ASUS Kernel: 4.13.0-45-generic x86_64 (64 bit gcc: 5.4.0) 
Desktop: KDE Plasma 5.8.9 (Qt 5.6.1) 
    Distro: Linux Mint 18.3 Sylvia 
  Machine:   Mobo: ASUSTeK model: E200HA v: 1.0 Bios: American Megatrends v: 
E200HA.303 date: 12/21/2016 
  CPU:   Quad core Intel Atom x5-Z8350 (-MCP-) cache: 1024 KB 
    flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11520 
    clock speeds: max: 1920 MHz 1: 1920 MHz 2: 1920 MHz 3: 486 MHz 4: 
505 MHz 
  Graphics:  Card: Intel Device 22b0 bus-ID: 00:02.0 
    Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) 
Resolution: 1366x768@60.06hz 
    GLX Renderer: Mesa DRI Intel HD Graphics (Cherrytrail) 
    GLX Version: 3.0 Mesa 18.0.5 Direct Rendering: Yes 
  Audio: Card Intel HDMI/DP LPE Audio driver: HdmiLpeAudio Sound: ALSA v: 
k4.13.0-45-generic 
  Network:   Card: Qualcomm Atheros Device 0042 driver: ath10k_pci bus-ID: 
01:00.0 
    IF: wlp1s0 state: up speed: N/A duplex: N/A mac:  
  Drives:    HDD Total Size: NA (-) ID-1: /dev/mmcblk0 model: N/A size: 31.3GB 
  Partition: ID-1: / size: 25G used: 21G (89%) fs: ext4 dev: /dev/mmcblk0p2 
    ID-2: swap-1 size: 4.18GB used: 0.00GB (0%) fs: swap dev: 
/dev/mmcblk0p3 
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present 
  Sensors:   System Temperatures: cpu: 40.0C mobo: N/A 
    Fan Speeds (in rpm): cpu: 0 
  Info:  Processes: 225 Uptime: 1 min Memory: 1101.6/3839.9MB Init: systemd 
runlevel: 5 Gcc sys: 5.4.0 
    Client: Shell (bash 4.3.481) inxi: 2.2.35 


  without a SD card inserted

  dmesg | grep mmc 
  [    2.994522] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA 
  [    3.013437] mmc1: SDHCI controller on ACPI [80860F14:03] using ADMA 
  [    3.323762] mmc0: new HS200 MMC card at address 0001 
  [    3.330155] mmcblk0: mmc0:0001 BJNB4R 29.1 GiB  
  [    3.330320] mmcblk0boot0: mmc0:0001 BJNB4R partition 1 4.00 MiB 
  [    3.330482] mmcblk0boot1: mmc0:0001 BJNB4R partition 2 4.00 MiB 
  [    3.330641] mmcblk0rpmb: mmc0:0001 BJNB4R partition 3 4.00 MiB 
  [    3.334332]  mmcblk0: p1 p2 p3 
  [    4.495608] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data 
mode. Opts: (null) 
  [    5.863405] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro 
  [    6.827393] Adding 4085756k swap on /dev/mmcblk0p3.  Priority:-1 extents:1 
across:4085756k SSFS

  
  with inserted SD card

  dmesg | grep mmc 
  [    2.994522] mmc0: SDHCI controller on ACPI [80860F14:00] using ADMA 
  [    3.013437] mmc1: SDHCI controller on ACPI [80860F14:03] using ADMA 
  [    3.323762] mmc0: new HS200 MMC card at address 0001 
  [    3.330155] mmcblk0: mmc0:0001 BJNB4R 29.1 GiB  
  [    3.330320] mmcblk0boot0: mmc0:0001 BJNB4R partition 1 4.00 MiB 
  [    3.330482] mmcblk0boot1: mmc0:0001 BJNB4R partition 2 4.00 MiB 
  [    3.330641] mmcblk0rpmb: mmc0:0001 BJNB4R partition 3 4.00 MiB 
  [    3.334332]  mmcblk0: p1 p2 p3 
  [    4.495608] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data 
mode. Opts: (null) 
  [    5.863405] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro 
  [    6.827393] Adding 4085756k swap on /dev/mmcblk0p3.  Priority:-1 extents:1 
across:4085756k SSFS 
  [  216.577900] mmc1: new ultra high speed SDR104 SDXC card at address 59b4 
  [  216.578575] mmcblk1: mmc1:59b4 0 59.7 GiB  
  [  216.580031]  mmcblk1: p1 
  [  216.857616] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some 
data may be corrupt. Please run fsck.

  
===

  inxi -Fxz 
  System:    Host: ASUS Kernel: 4.15.0-42-generic x86_64 (64 bit gcc: 5.4.0) 
Desktop: KDE Plasma 5.8.9 (Qt 5.6.1) 
    Distro: Linux Mint 18.3 Sylvia 
  Machine:   Mobo: ASUSTeK model: E200HA v: 1.0 Bios: American Megatrends v: 
E200HA.303 date: 12/21/2016 
  CPU:   Quad core Intel Atom x5-Z8350 (-MCP-) cache: 1024 KB 
    flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 11520 
    clock speeds: max: 1920 MHz 1: 839 MHz 2: 816 MHz 3: 480 MHz 4: 480 
MHz 
  Graphics:  Card: Intel Device 22b0 bus-ID: 00:02.0 
    Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa) 
Resolution: 1366x768@60.06hz 
    GLX Renderer: