[Kernel-packages] [Bug 1808318] Re: powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9

2018-12-13 Thread Po-Hsu Lin
For comment #5,
I know why it's not failing in the previous cycle.

We clone the kernel source tree with master branch, not the master-next
branch with -proposed kernel.

Therefore in 4.18.0-12, the branch we use for testing is 4.18.0-11, and
it does not include this patch.

But now with 4.18.0-13, we're using 4.18.0-12 for the test, that's how
it gets this confusing result.

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

Title:
  powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9

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

Bug description:
  This test passed with 4.18.0-12 on the last cycle [1]
  But failed with the proposed 4.18.0-13 this time.

  Test failed to build because of a missing include file:
  50.   ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or 
directory

  Tried to reproduce this cycle with 4.18.0-12 first and this can be
  reproduced as well.

  
  39.   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc'
  40.   
BUILD_TARGET=/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment;
 mkdir -p $BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all
  41.   make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment'
  42.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 copy_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_unaligned
  43.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 copy_first_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c 
-o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_first_unaligned
  44.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 paste_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_unaligned
  45.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 paste_last_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c 
-o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_last_unaligned
  46.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 alignment_handler.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/alignment_handler
  47.   make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment'
  48.   make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc'
  49.   stderr:
  50.   ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or 
directory
  51.   make[1]: *** No rule to make target 
'../../../../scripts/subarch.include'.
  52.   make[1]: Failed to remake makefile 
'../../../../scripts/subarch.include'.
  53.   make: *** [Makefile:38: alignment] Error 2

  
  [1] 
http://10.246.72.4/test-results/4.18.0-12.13-generic/entei__4.18.0-12.13__2018-11-15_16-03-00/ubuntu_kernel_selftests/results/ubuntu_kernel_selftests.powerpc/debug/ubuntu_kernel_selftests.powerpc.DEBUG.html

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-12-generic 4.18.0-12.13
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 13 10:20 seq
   crw-rw 1 root audio 116, 33 Dec 13 10:20 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 

[Kernel-packages] [Bug 1808318] Re: powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9

2018-12-13 Thread Po-Hsu Lin
The following patch can fix this build issue:

diff --git a/tools/testing/selftests/lib.mk b/tools/testing/selftests/lib.mk
index 0a8e75886..afd384ed8 100644
--- a/tools/testing/selftests/lib.mk
+++ b/tools/testing/selftests/lib.mk
@@ -16,7 +16,7 @@ TEST_GEN_PROGS := $(patsubst %,$(OUTPUT)/%,$(TEST_GEN_PROGS))
 TEST_GEN_PROGS_EXTENDED := $(patsubst %,$(OUTPUT)/%,$(TEST_GEN_PROGS_EXTENDED))
 TEST_GEN_FILES := $(patsubst %,$(OUTPUT)/%,$(TEST_GEN_FILES))
 
-top_srcdir ?= ../../../..
+top_srcdir ?= $(abspath $(dir $(lastword $(MAKEFILE_LIST)))/../../..)
 include $(top_srcdir)/scripts/subarch.include
 ARCH   ?= $(SUBARCH)

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

Title:
  powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9

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

Bug description:
  This test passed with 4.18.0-12 on the last cycle [1]
  But failed with the proposed 4.18.0-13 this time.

  Test failed to build because of a missing include file:
  50.   ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or 
directory

  Tried to reproduce this cycle with 4.18.0-12 first and this can be
  reproduced as well.

  
  39.   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc'
  40.   
BUILD_TARGET=/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment;
 mkdir -p $BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all
  41.   make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment'
  42.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 copy_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_unaligned
  43.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 copy_first_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c 
-o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_first_unaligned
  44.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 paste_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_unaligned
  45.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 paste_last_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c 
-o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_last_unaligned
  46.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 alignment_handler.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/alignment_handler
  47.   make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment'
  48.   make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc'
  49.   stderr:
  50.   ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or 
directory
  51.   make[1]: *** No rule to make target 
'../../../../scripts/subarch.include'.
  52.   make[1]: Failed to remake makefile 
'../../../../scripts/subarch.include'.
  53.   make: *** [Makefile:38: alignment] Error 2

  
  [1] 
http://10.246.72.4/test-results/4.18.0-12.13-generic/entei__4.18.0-12.13__2018-11-15_16-03-00/ubuntu_kernel_selftests/results/ubuntu_kernel_selftests.powerpc/debug/ubuntu_kernel_selftests.powerpc.DEBUG.html

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-12-generic 4.18.0-12.13
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 13 10:20 seq
   

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

2018-12-13 Thread Christian Ehrhardt 
Thanks for the Details, but that means that even the MAAS Team might
have enough systems, but not the right special HW.
Therefore @Vern could you do the pre-checks with your associated
customer that you can verify the bug on their setup before we push it
as SRU?
As I said, you only need to have Bionic/Cosmic on the target KVM Host
that is supposed to spawn the Pod and currently fails.
IMHO all other components can stay as-is.

Please let me know if that would be possible

-- 
You 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 1759836] Re: systemd-udevd consumes 100% of CPU

2018-12-13 Thread Kai-Heng Feng
Can you try comment out this section helps:
ATTR{bInterfaceClass}=="03", ATTR{bInterfaceSubClass}=="01", 
ATTR{bInterfaceProtocol}=="02", \
  ATTRS{bDeviceClass}=="00", ATTRS{idVendor}=="413c", 
ATTRS{bmAttributes}=="e0", \
  RUN+="hid2hci --method=dell --devpath=%p", ENV{HID2HCI_SWITCH}="1"

and this section:
ATTR{bDeviceClass}=="e0", ATTR{bDeviceSubClass}=="01", 
ATTR{bDeviceProtocol}=="01", ATTR{idVendor}=="413c", \
  ENV{REMOVE_CMD}="/sbin/udevadm trigger --action=change --subsystem-match=usb 
--property-match=HID2HCI_SWITCH=1"

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

Title:
  systemd-udevd consumes 100% of CPU

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The systemd-udevd proccess consumes 100% of a thread everytime, but
  i'm not noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions

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


[Kernel-packages] [Bug 1766176] Re: initramfs-tools returns error while installing the proposed Bionic kernel

2018-12-13 Thread Po-Hsu Lin
Works well in the recent SRU cycles.
I'm gonna to close this bug.

denning, please open a new bug if you're still seeing this issue.

Thank you.

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

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

Title:
  initramfs-tools returns error while installing the proposed Bionic
  kernel

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

Bug description:
  This issue was spotted on a ThunderX ARM64 system and s390x, AMD64
  system does not have this issue

  Steps:
1. Deploy a ThunderX ARM64 node
2. Enable -proposed, commence apt update and dist-upgrade

  Result:
  Setting up linux-generic (4.15.0.19.20) ...
  Processing triggers for initramfs-tools (0.130ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-15-generic
  W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast
  Ignoring old or unknown version 4.15.0-15-generic (latest is 
4.15.0-19-generic)
  Use --force if you want version 4.15.0-15-generic.
  run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 
2
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
  Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic
  W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast
  flash-kernel: deferring update (trigger activated)
  /etc/kernel/postinst.d/zz-flash-kernel:
  flash-kernel: deferring update (trigger activated)
  /etc/kernel/postinst.d/zz-update-grub:
  Generating grub configuration file ...
  Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is 
set is no longer supported.
  Found linux image: /boot/vmlinuz-4.15.0-19-generic
  Found initrd image: /boot/initrd.img-4.15.0-19-generic
  Found linux image: /boot/vmlinuz-4.15.0-15-generic
  Found initrd image: /boot/initrd.img-4.15.0-15-generic
  Adding boot menu entry for EFI firmware configuration
  done
  Processing triggers for systemd (237-3ubuntu10) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  Errors were encountered while processing:
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  ubuntu@starmie-kernel:~$ 

  
  For error on s390x:
  Setting up linux-modules-extra-4.15.0-19-generic (4.15.0-19.20) ...
  Setting up linux-image-generic (4.15.0.19.20) ...
  Setting up linux-headers-generic (4.15.0.19.20) ...
  Setting up linux-generic (4.15.0.19.20) ...
  Processing triggers for initramfs-tools (0.130ubuntu3) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-17-generic
  Using config file '/etc/zipl.conf'
  Error: Ramdisk file '/boot/initrd.img' in section 'ubuntu': No such file or 
directory
  run-parts: /etc/initramfs/post-update.d//zz-zipl exited with return code 1
  dpkg: error processing package initramfs-tools (--configure):
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Processing triggers for linux-image-4.15.0-19-generic (4.15.0-19.20) ...
  /etc/kernel/postinst.d/initramfs-tools:
  update-initramfs: Generating /boot/initrd.img-4.15.0-19-generic
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasda (0200).
  Done.
  /etc/kernel/postinst.d/zz-zipl:
  Using config file '/etc/zipl.conf'
  Building bootmap in '/boot'
  Building menu 'menu'
  Adding #1: IPL section 'ubuntu' (default)
  Adding #2: IPL section 'old'
  Preparing boot device: dasda (0200).
  Done.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: User Name 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 23 04:36 seq
   crw-rw 1 root audio 116, 33 Apr 23 04:36 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu6
  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: Mon Apr 23 06:00:17 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   

[Kernel-packages] [Bug 1808318] Re: powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9

2018-12-13 Thread Po-Hsu Lin
Hmm, it looks like this patch landed in 4.18.0-12

I wonder why it's not failing in the previous cycle with 4.18.0-12

phlin@tangerine:~/ubuntu-cosmic/tools/testing/selftests$ git tag --contains 
aa435326c92082700fdb89e767b90b9735e78d94
Ubuntu-4.18.0-12.13
Ubuntu-4.18.0-13.14
Ubuntu-raspi2-4.18.0-1007.9
Ubuntu-raspi2-4.18.0-1008.10

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

Title:
  powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9

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

Bug description:
  This test passed with 4.18.0-12 on the last cycle [1]
  But failed with the proposed 4.18.0-13 this time.

  Test failed to build because of a missing include file:
  50.   ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or 
directory

  Tried to reproduce this cycle with 4.18.0-12 first and this can be
  reproduced as well.

  
  39.   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc'
  40.   
BUILD_TARGET=/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment;
 mkdir -p $BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all
  41.   make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment'
  42.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 copy_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_unaligned
  43.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 copy_first_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c 
-o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_first_unaligned
  44.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 paste_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_unaligned
  45.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 paste_last_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c 
-o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_last_unaligned
  46.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 alignment_handler.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/alignment_handler
  47.   make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment'
  48.   make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc'
  49.   stderr:
  50.   ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or 
directory
  51.   make[1]: *** No rule to make target 
'../../../../scripts/subarch.include'.
  52.   make[1]: Failed to remake makefile 
'../../../../scripts/subarch.include'.
  53.   make: *** [Makefile:38: alignment] Error 2

  
  [1] 
http://10.246.72.4/test-results/4.18.0-12.13-generic/entei__4.18.0-12.13__2018-11-15_16-03-00/ubuntu_kernel_selftests/results/ubuntu_kernel_selftests.powerpc/debug/ubuntu_kernel_selftests.powerpc.DEBUG.html

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-12-generic 4.18.0-12.13
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 13 10:20 seq
   crw-rw 1 root audio 116, 33 Dec 13 10:20 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: 

[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

2018-12-13 Thread Kai-Heng Feng
The package C-State somehow fails to enter deeper states after S3.
System firmware (BIOS) touches a lots of things during S3, and it's a
blackbox to us.

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

Title:
  CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

Status in linux package in Ubuntu:
  Incomplete
Status in thermald package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
  GPU fans suddenly go full throttle. It doesn't seem to depend on
  temperature, could happen when 32 °C reported, sometimes the laptop
  can work for day or two without this issue, but eventually it happens.
  The only way to stop fans is to power off the laptop, power on (fans
  go 100% at this point again), power off during BIOS splash screen and
  power on again. Seems to happen more often after waking up from a
  sleep.

  Things tried:

  Upgrading BIOS to latest available on ASUS site to the date of
  writing. No change.

  asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
  both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
  does not seem to control it and does not prevent going full throttle.

  4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
  issue.

  Userspace fan control software (https://github.com/hirschmann/nbfc).
  Can control speed of both fans to the point where they go full
  throttle, after that has no effect on them.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1804594] Re: fanotify09 in LTP failed with first group got more than 2 events

2018-12-13 Thread Po-Hsu Lin
** Also affects: ubuntu-kernel-tests
   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/1804594

Title:
  fanotify09 in LTP failed with first group got more than 2 events

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

Bug description:
  There is a new test cases added into fanotify09:
  457e13c (fanotify09: check merging of events on child subdir)

   tag=fanotify09 stime=1542775332
   cmdline="fanotify09"
   contacts=""
   analysis=exit
   <<>>
   tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s
   fanotify09.c:161: INFO: Test #0: Events on children with both inode and 
mount marks
   fanotify09.c:150: PASS: group 0 got event: mask 2 pid=19769 fd=23 
path=/tmp/ltp-2Jj8lWaBTL/UT3GCK/mntpoint/tfile_19769
   fanotify09.c:234: PASS: group 1 got no event
   fanotify09.c:234: PASS: group 2 got no event
   fanotify09.c:161: INFO: Test #1: Events on children and subdirs with both 
inode and mount marks
   fanotify09.c:150: PASS: group 0 got event: mask 2 pid=19769 fd=23 
path=/tmp/ltp-2Jj8lWaBTL/UT3GCK/mntpoint/tfile_19769
   fanotify09.c:150: PASS: group 0 got event: mask 10 pid=19769 fd=24 
path=/tmp/ltp-2Jj8lWaBTL/UT3GCK/mntpoint/testdir
   fanotify09.c:202: FAIL: first group got more than 2 events (72 > 48)
   fanotify09.c:234: PASS: group 1 got no event
   fanotify09.c:234: PASS: group 2 got no event

   Summary:
   passed 7
   failed 1
   skipped 0
   warnings 0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 22 06:27 seq
   crw-rw 1 root audio 116, 33 Nov 22 06:27 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Nov 22 06:45:22 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: Dell Inc. PowerEdge R320
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=7e417b15-9c42-401c-b706-06eb693e6d19 ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 0DY523
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1804594/+subscriptions

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


[Kernel-packages] [Bug 1808353] Re: Blacklist Realtek Virtual IPMI device

2018-12-13 Thread AceLan Kao
** Tags added: originate-from-1807080 stella

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

Title:
  Blacklist Realtek Virtual IPMI device

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  New

Bug description:
  [Impact]
  System fails to do system suspend because of a non-working Realtek IPMI 
device.

  [Fix]
  Quote from the patch:
  "
  Realtek has some sort of "Virtual" IPMI device on the PCI bus as a
  KCS controller, but whatever it is, it's not one.  Ignore it if seen.
  "

  [Test]
  System suspend works after blacklisting the device.

  [Regression Potential]
  None. The driver has never worked for the device.

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

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


[Kernel-packages] [Bug 1808465] Re: The mute led can't work anymore on the lenovo x1 carbon

2018-12-13 Thread Hui Wang
** Description changed:

- I'm on Lenovo ThinkPad X1 Carbon 6th, model 20KH006JGE. After upgrading
- to Linux 4.19.7, the audio mute and microphone mute LEDs (on F1 and F4
- keys) stopped working. They do work if I remove the line:
  
- {0x12, 0x90a60130},
+ [Impact]
+ The mute led can't work on several lenovo laptop models after applying the
+ patch of #1805079, this is a regression introduced by that patch.
+ 
+ [Fix]
+ chanin the ALC269_FIXUP_THINKPAD_ACPI, this will make the led work again.
+ 
+ 
+ [Test Case]
+ press F1 and F4, the mute led and micmute led work well.
+ 
+ 
+ [Regression Potential]
+ Very low, this patch is specific to ALC285_FIXUP_LENOVO_HEADPHONE_NOISE, and
+ this FIXUP is specific several lenovo laptop models. I have tested audio and
+ led functions on those machines.

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

Title:
  The mute led can't work anymore on the lenovo x1 carbon

Status in linux package in Ubuntu:
  Incomplete

Bug description:

  [Impact]
  The mute led can't work on several lenovo laptop models after applying the
  patch of #1805079, this is a regression introduced by that patch.

  [Fix]
  chanin the ALC269_FIXUP_THINKPAD_ACPI, this will make the led work again.

  
  [Test Case]
  press F1 and F4, the mute led and micmute led work well.

  
  [Regression Potential]
  Very low, this patch is specific to ALC285_FIXUP_LENOVO_HEADPHONE_NOISE, and
  this FIXUP is specific several lenovo laptop models. I have tested audio and
  led functions on those machines.

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

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


[Kernel-packages] [Bug 1808465] Re: The mute led can't work anymore on the lenovo x1 carbon

2018-12-13 Thread Hui Wang
This is a regression of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805079

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

Title:
  The mute led can't work anymore on the lenovo x1 carbon

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm on Lenovo ThinkPad X1 Carbon 6th, model 20KH006JGE. After
  upgrading to Linux 4.19.7, the audio mute and microphone mute LEDs (on
  F1 and F4 keys) stopped working. They do work if I remove the line:

  {0x12, 0x90a60130},

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

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


[Kernel-packages] [Bug 1808465] [NEW] The mute led can't work anymore on the lenovo x1 carbon

2018-12-13 Thread Hui Wang
Public bug reported:

I'm on Lenovo ThinkPad X1 Carbon 6th, model 20KH006JGE. After upgrading
to Linux 4.19.7, the audio mute and microphone mute LEDs (on F1 and F4
keys) stopped working. They do work if I remove the line:

{0x12, 0x90a60130},

** Affects: linux (Ubuntu)
 Importance: Critical
 Assignee: Hui Wang (hui.wang)
 Status: Incomplete

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Changed in: linux (Ubuntu)
   Importance: High => Critical

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

Title:
  The mute led can't work anymore on the lenovo x1 carbon

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm on Lenovo ThinkPad X1 Carbon 6th, model 20KH006JGE. After
  upgrading to Linux 4.19.7, the audio mute and microphone mute LEDs (on
  F1 and F4 keys) stopped working. They do work if I remove the line:

  {0x12, 0x90a60130},

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

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


[Kernel-packages] [Bug 1801743] Re: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10

2018-12-13 Thread Nadi
I updated the BIOS but it did not help

but I SOLVED my problem, and perhaps yours as well Magnus! 
The problem was with the LID upon waking up from sleep S3. 
I found it after hours of googling and eventually debugging using this link:
https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues

I cancelled the ACPI that enables the lid:
echo LID0 > /proc/acpi/wakeup
which turns the disabels the lid signal to the ACPI. It is problably doing 
something wrong, I will try to file a new bug soon. 

This is the relevant output of the wakeup file:

XHC   S0*enabled   pci::00:14.0
XDCI  S4*disabled
HDAS  S4*disabled  pci::00:1f.3
LID0  S3*disabled  platform:PNP0C0D:00
PBTN  S3*enabled   platform:PNP0C0C:00

Every boot I have to re-disable it, so I make a small script and used crontab 
-e, and added the this line to the end of the script:
@reboot /usr/local/bin/myFixScript.sh
see the link
https://www.kompulsa.com/run-a-program-on-startup-console-on-ubuntu-18-04/

Lets see how long it will be stable :-)
Cheers... 
Nadi

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

Title:
  Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to kubuntu 18.04 resuming from suspend fails in most
  cases on my laptop. When trying to resume the power LED is turned on,
  but the screen stays black and the system does not respond at all.
  Switching to another virtual terminal is not possible and closing the
  lid again does not show any effect. The hardware is a Dell Latitude
  e7440 with core i7 4600U and intel graphics only. The only way to
  change the status is a hard shut-down by long pressing the power
  button. The last message in kern.log is:

  PM: suspend entry (deep)

  The described problem is similar to bug #1774950. However, the latter
  is considered to be fixed with kernel 4.15.0-38 while my problem
  persists with this kernel.

  Output of 'sudo lspci -vnvn' is attached, the result of 'cat
  /proc/version_signature' is:

  Ubuntu 4.15.0-38.41-generic 4.15.18
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  graeser2116 F pulseaudio
   /dev/snd/controlC0:  graeser2116 F pulseaudio
  CurrentDesktop: KDE
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2014-03-20 (1690 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  MachineType: Dell Inc. Latitude E7440
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=25e09413-4977-401f-a034-0465b444518b ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-10-15 (20 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/02/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0WK2DM
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


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

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

apport-collect 1808465

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

Title:
  The mute led can't work anymore on the lenovo x1 carbon

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm on Lenovo ThinkPad X1 Carbon 6th, model 20KH006JGE. After
  upgrading to Linux 4.19.7, the audio mute and microphone mute LEDs (on
  F1 and F4 keys) stopped working. They do work if I remove the line:

  {0x12, 0x90a60130},

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

-- 
Mailing list: https://launchpad.net/~kernel-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

2018-12-13 Thread Po-Hsu Lin
4.4.0-141.167 - lowlatency
Regression test CMPL, RTB.

44 / 52 tests were run, missing: ubuntu_bpf_jit, ubuntu_cts_kernel, 
ubuntu_cve_kernel, ubuntu_ecryptfs, ubuntu_ltp_syscalls, ubuntu_zfs_fstest, 
ubuntu_zfs_xfs_generic, xfstests
Issue to note in amd64:
  libhugetlbfs - failed 1 killed by signal 1 bad config 3
  ubuntu_kvm_unit_tests - 30 failed on KVM nodes

4.4.0-141.167 - generic
Regression test CMPL, RTB.

Issue to note in amd64:
  monotonic_time - tsc failed on gonzo
  ubuntu_kvm_unit_tests - 32 failed on amaura, 31 failed on pepe, 30 failed on 
KVM nodes
  ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) 
fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 
1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107)
  xfstests - xfs xfs/438 timed out

Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427)
  ubuntu_kvm_unit_tests - pmu on ms10-34-mcdivittB0-kernel (bug 1751000) 
gicv2-ipi and gicv2-active on starmie
  ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) 
fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 
1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107)
  xfstests - xfs xfs/438 timed out

Issue to note in i386:
  ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007)
  ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) 
fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 
1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107)
  xfstests - xfs generic/308 timed out (bug 1738152)

Issue to note in ppc64le (P8):
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool, bug 1755118
  ubuntu_kvm_unit_tests - sprs timed out (bug 1740017)
  ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) 
fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 
1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107)
  xfstests - btrfs generic/176 timed out

Issue to note in s390x (KVM):
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_kvm_unit_tests - 12 failed
  ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) 
fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 
1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107)

Issue to note in s390x (Ubuntu on LPAR):
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) 
fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 
1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107)
  ubuntu_lxc - lxc-test-ubuntu failed (Failed to start networking in 
ubuntu-cloud container)

Issue to note in s390x (zVM):
  libhugetlbfs - failed 11 killed by signal 7 bad config 1
  ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_kvm_unit_tests - skey failed on zVM (bug 1778705)
  ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) 
fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 
1775153) fanotify10 (bug 1802454) fanotify11 timeouted (bug 1808107)

Note: missing test cases in lowlatency kernel need to be investigated
(bug 1791016)

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

[Kernel-packages] [Bug 1808183] Re: ASPEED server console output extremely slow after upgrade to 18.04

2018-12-13 Thread Daniel van Vugt
Can you please also run 'lsmod' and send us the output?

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

Title:
  ASPEED server console output extremely slow after upgrade to 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After the upgrade from 16.04 to 18.04 my server console is extremely slow.
  It looks similar to the youtube clips mentioned in the problem described 
here: https://ubuntuforums.org/showthread.php?t=2399941
  My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD.
  It runs on an ASUS P9D-X board.
  Before the upgrade everything was fine.
  Now it is so slow that it sometimes even hangs during boot and goes into an 
emergency console where I just can do a ctrl-alt-delete as described in bug 
1802469

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Dec 12 17:07:48 2018
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago)

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

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


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

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

apport-collect 1808183

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

Title:
  ASPEED server console output extremely slow after upgrade to 18.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After the upgrade from 16.04 to 18.04 my server console is extremely slow.
  It looks similar to the youtube clips mentioned in the problem described 
here: https://ubuntuforums.org/showthread.php?t=2399941
  My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD.
  It runs on an ASUS P9D-X board.
  Before the upgrade everything was fine.
  Now it is so slow that it sometimes even hangs during boot and goes into an 
emergency console where I just can do a ctrl-alt-delete as described in bug 
1802469

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Dec 12 17:07:48 2018
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago)

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

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


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

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

apport-collect 1808193

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

Title:
  Battery percentage changes suddenly depending on whether AC is plugged
  in

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in upower package in Ubuntu:
  New

Bug description:
  The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% 
(Fully charged when plugged in) but when plugged out the battery shows 94%. 
Batteries are fine, no issues whatsoever with batteries.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-10 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808193/+subscriptions

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


[Kernel-packages] [Bug 1808193] Re: Battery indicator shows false reading

2018-12-13 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

** Summary changed:

- Battery indicator shows false reading
+ Battery percentage changes suddenly depending on whether AC is plugged in

** Also 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/1808193

Title:
  Battery percentage changes suddenly depending on whether AC is plugged
  in

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% 
(Fully charged when plugged in) but when plugged out the battery shows 94%. 
Batteries are fine, no issues whatsoever with batteries.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-10 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808193/+subscriptions

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


[Kernel-packages] [Bug 1808183] Re: server console output extremely slow after upgrade to 18.04

2018-12-13 Thread Daniel van Vugt
I see now, thanks.

This appears to be a kernel regression relating to 'ast' performance:

04:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics 
Family (rev 21)
Subsystem: ASUSTeK Computer Inc. ASPEED Graphics Family
Kernel driver in use: ast
Kernel modules: ast


** Summary changed:

- server console output extremely slow after upgrade to 18.04
+ ASPEED server console output extremely slow after upgrade to 18.04

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

** Tags added: regression-release

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

Title:
  ASPEED server console output extremely slow after upgrade to 18.04

Status in linux package in Ubuntu:
  New

Bug description:
  After the upgrade from 16.04 to 18.04 my server console is extremely slow.
  It looks similar to the youtube clips mentioned in the problem described 
here: https://ubuntuforums.org/showthread.php?t=2399941
  My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD.
  It runs on an ASUS P9D-X board.
  Before the upgrade everything was fine.
  Now it is so slow that it sometimes even hangs during boot and goes into an 
emergency console where I just can do a ctrl-alt-delete as described in bug 
1802469

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Wed Dec 12 17:07:48 2018
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago)

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

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


[Kernel-packages] [Bug 1808183] [NEW] ASPEED server console output extremely slow after upgrade to 18.04

2018-12-13 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After the upgrade from 16.04 to 18.04 my server console is extremely slow.
It looks similar to the youtube clips mentioned in the problem described here: 
https://ubuntuforums.org/showthread.php?t=2399941
My server is attached to a KVM switch with VGA cable to a 1920x1080 LCD.
It runs on an ASUS P9D-X board.
Before the upgrade everything was fine.
Now it is so slow that it sometimes even hangs during boot and goes into an 
emergency console where I just can do a ctrl-alt-delete as described in bug 
1802469

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Wed Dec 12 17:07:48 2018
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-10-11 (62 days ago)

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


** Tags: amd64 apport-bug bionic performance
-- 
ASPEED server console output extremely slow after upgrade to 18.04
https://bugs.launchpad.net/bugs/1808183
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 1778476] Re: [bionic] high cpu load HP probook iio-sensor-proxy

2018-12-13 Thread Your full name
is /dev/bus/iio even properly populated?
See LP: #1807250 LP: #1804804 LP: #1792813

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

Title:
  [bionic] high cpu load HP probook  iio-sensor-proxy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a many HP ProBook 450 G1 and HP ProBook 650 G3 with fresh
  install of Ubuntu Desktop.

  They all have a load average of 1.0 when idle (no graphical session
  opened).

  vmstat shows idle =~ 100%

  The process which uses most CPU time is iio-sensor-proxy (about 1%)
  and it's constantly in D state (uninterruptible sleep).

  Manually starting this command shows that the sensor (lis3lv02d on
  both products) is constantly sending garbage informations (see
  attachment).

  With iio-sensor-proxy service stopped, the CPU load is ~ 0%

  As the service is 'static' and can not be disabled, the only workaround is to 
remove the 'iios-sensor-proxy' package.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1371 F pulseaudio
    ljanvier   2104 F pulseaudio
   /dev/snd/controlC0:  gdm1371 F pulseaudio
    ljanvier   2104 F pulseaudio
  DistroRelease: Ubuntu 18.04
  MachineType: Hewlett-Packard HP ProBook 650 G1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=e375b9cb-3776-455a-bb2e-24f826528047 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UnreportableReason: Ce rapport concerne un paquet qui n'est pas installé.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: False
  dmi.bios.date: 12/24/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L77 Ver. 01.31
  dmi.board.name: 1993
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3A
  dmi.chassis.asset.tag: 5CG5124FWZ
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL77Ver.01.31:bd12/24/2014:svnHewlett-Packard:pnHPProBook650G1:pvrA3009DD10303:rvnHewlett-Packard:rn1993:rvrKBCVersion16.3A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP ProBook 650 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2018-12-13 Thread Daniel van Vugt
It appears the gnome-shell!278 fix is only in future version 3.31.3 at
the moment.

I've had the same issue with other laptops and would be surprised if
this was the only bug report.

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => 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/1745032

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions

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


[Kernel-packages] [Bug 1804804] Re: Screen rotation does not rotate all input devices and needs custom user commands (iio-sensor-proxy or libinput should probably handle this?)

2018-12-13 Thread Your full name
Confirmed in LP: #1807250 and LP: #1792813̈́

Ubuntu kernels >=4.15 are the culprit, does not affect debian 4.18.20

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

Title:
  Screen rotation does not rotate all input devices and needs custom
  user commands (iio-sensor-proxy or libinput should probably handle
  this?)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 18.10
  GNOME Shell 3.30.1
  Cinnamon 3.8.8

  Hardware: ASUS Transformer Mini.

  Also confirmed problematic for Yoga Series tablet/laptop hybrids.
  (https://github.com/linuxmint/cinnamon-settings-daemon/issues/188)

  Screen rotation works fine, but tablet coords including touch screen
  and pen coords do not rotate with it.

  Gnome gets touch screen rotation correct, but not pen coords
  Cinnamon gets touch screen rotation and peen coords wrong

  User can correct using convoluted xinput commands like:
  xinput set-prop "ELAN22A6:00 04F3:22A6" --type=float "Coordinate 
Transformation Matrix" 0 1 0 -1 0 1 0 0 1

  I spoke with Mint devs who said I should file it against iio-sensor-
  proxy or libinput, which I assume is a better solution that asking
  various wm developers to fix it individually.

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

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


[Kernel-packages] [Bug 1792813] Re: iio-sensor-proxy says: "Could not find any supported sensors" on Dell XPS 15 9575 2-in-1 on Cosmic 18.10

2018-12-13 Thread Your full name
LP: #1807250

Xenials kernel 4.4.0-134, debian stable kernel 4.9.8, debian testing
kernel 4.18.20 are all working when booted with bionic userspace.
According to nacc upcoming cosmic 4.18 is also affected.

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

Title:
  iio-sensor-proxy says: "Could not find any supported sensors" on Dell
  XPS 15 9575 2-in-1 on Cosmic 18.10

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

Bug description:
  On Cosmic, iio-sensor-proxy 2.4, with default 4.18 kernel as well as
  latest mainline 4.19.0-041900rc3-generic.

  There is no rotation lock button in the gnome-shell panel menu.
  Gnome Settings > Device Display shows rotation buttons
  There is no directory /sys/bus/iio

  Reproduction:
  1. Rotate device, fold display back to tent and tablet modes:

  -> Rotation is not detected. When folding to tablet mode, device goes
  to suspend as if display had been closed normally.

  iio-sensor-proxy finds no sensors:
  ~$ systemctl status iio-sensor-proxy.service
  ● iio-sensor-proxy.service - IIO Sensor Proxy service
  Loaded: loaded (/lib/systemd/system/iio-sensor-proxy.service; static; vendor 
preset: enabled)
  Active: inactive (dead)

  I reported issue as https://github.com/hadess/iio-sensor-
  proxy/issues/236 and was advised:

  "Looks like there's no supported sensors, or just no sensors inside
  this machine. Nothing that we can do about it, except asking your
  vendor for support (eg. is there one or multiple sensors, and if so,
  why aren't they supported in the kernel)"

  I posted the issue in Dell's Project Sputnik's Google+ community

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mario  2139 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 16 20:20:48 2018
  InstallationDate: Installed on 2018-09-13 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 004: ID 27c6:5395  
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9575
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash pcie_aspm=force 
drm.vblankoffdelay=1 i915.fastboot=1 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.9
  dmi.board.name: 0C32VW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9575
  dmi.product.sku: 080D
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2018-12-13 Thread Alexandre Forte
This issue also affects Asus Vivobook 15 X510UR.

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions

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


[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

2018-12-13 Thread James Turnbull
I am on 4.18.0-12-generic and I've tried 4.19.6 without joy.

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

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

Status in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  New

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

  Firmware: 36.7596afd4.0

  
  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | isr2
  Dec 13 11:53:36 james-x1 kernel: [  856.845080] iwlwifi :02:00.0: 
0x0041FDC0 | isr3
  Dec 13 11:53:36 james-x1 kernel: [  856.845082] iwlwifi :02:00.0: 
0x | isr4
  Dec 13 11:53:36 james-x1 kernel: [  856.845084] iwlwifi :02:00.0: 
0x00580118 | last cmd Id
  Dec 13 11:53:36 james-x1 kernel: [  856.845087] iwlwifi :02:00.0: 
0x | wait_event
  Dec 13 11:53:36 james-x1 kernel: [  856.845089] iwlwifi :02:00.0: 
0x76DD | l2p_control
  Dec 13 11:53:36 james-x1 kernel: [  856.845091] iwlwifi :02:00.0: 
0x0020 | l2p_duration
  Dec 13 11:53:36 james-x1 kernel: [  856.845094] iwlwifi :02:00.0: 
0x | l2p_mhvalid
  Dec 13 11:53:36 james-x1 kernel: [  856.845096] iwlwifi :02:00.0: 
0x00A0 | l2p_addr_match
  Dec 13 11:53:36 james-x1 kernel: [  856.845099] iwlwifi :02:00.0: 
0x000D | lmpm_pmg_sel
  Dec 13 11:53:36 james-x1 kernel: [  856.845101] iwlwifi :02:00.0: 
0x22040707 | timestamp
  Dec 13 11:53:36 james-x1 kernel: [  856.845103] iwlwifi :02:00.0: 
0x6070 | flow_handler
  Dec 13 11:53:36 james-x1 kernel: [  856.845170] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845173] iwlwifi :02:00.0: Status: 
0x0100, count: 7
  Dec 13 11:53:36 james-x1 kernel: [  856.845176] iwlwifi :02:00.0: 
0x0070 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845178] iwlwifi :02:00.0: 
0x | umac branchlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845181] iwlwifi :02:00.0: 
0xC00868A4 | umac branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845183] iwlwifi :02:00.0: 
0xC0083A94 | umac interruptlink1
  Dec 13 11:53:36 james-x1 

[Kernel-packages] [Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

2018-12-13 Thread AaronMa
It looks like bug:
https://bugs.launchpad.net/bugs/1805088

Could you try 4.15.0-1029.34 kernel or 4.17+ mainline kernel?

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

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

Status in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  New

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

  Firmware: 36.7596afd4.0

  
  Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
  Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: 
Microcode SW error detected.  Restarting 0x200.
  Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
  Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
  Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
  Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
  Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
  Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
  Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
  Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
  Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
  Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
  Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
  Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
  Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
  Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
  Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
  Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
  Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
  Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
  Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
  Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
  Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | isr2
  Dec 13 11:53:36 james-x1 kernel: [  856.845080] iwlwifi :02:00.0: 
0x0041FDC0 | isr3
  Dec 13 11:53:36 james-x1 kernel: [  856.845082] iwlwifi :02:00.0: 
0x | isr4
  Dec 13 11:53:36 james-x1 kernel: [  856.845084] iwlwifi :02:00.0: 
0x00580118 | last cmd Id
  Dec 13 11:53:36 james-x1 kernel: [  856.845087] iwlwifi :02:00.0: 
0x | wait_event
  Dec 13 11:53:36 james-x1 kernel: [  856.845089] iwlwifi :02:00.0: 
0x76DD | l2p_control
  Dec 13 11:53:36 james-x1 kernel: [  856.845091] iwlwifi :02:00.0: 
0x0020 | l2p_duration
  Dec 13 11:53:36 james-x1 kernel: [  856.845094] iwlwifi :02:00.0: 
0x | l2p_mhvalid
  Dec 13 11:53:36 james-x1 kernel: [  856.845096] iwlwifi :02:00.0: 
0x00A0 | l2p_addr_match
  Dec 13 11:53:36 james-x1 kernel: [  856.845099] iwlwifi :02:00.0: 
0x000D | lmpm_pmg_sel
  Dec 13 11:53:36 james-x1 kernel: [  856.845101] iwlwifi :02:00.0: 
0x22040707 | timestamp
  Dec 13 11:53:36 james-x1 kernel: [  856.845103] iwlwifi :02:00.0: 
0x6070 | flow_handler
  Dec 13 11:53:36 james-x1 kernel: [  856.845170] iwlwifi :02:00.0: Start 
IWL Error Log Dump:
  Dec 13 11:53:36 james-x1 kernel: [  856.845173] iwlwifi :02:00.0: Status: 
0x0100, count: 7
  Dec 13 11:53:36 james-x1 kernel: [  856.845176] iwlwifi :02:00.0: 
0x0070 | ADVANCED_SYSASSERT
  Dec 13 11:53:36 james-x1 kernel: [  856.845178] iwlwifi :02:00.0: 
0x | umac branchlink1
  Dec 13 11:53:36 james-x1 kernel: [  856.845181] iwlwifi :02:00.0: 
0xC00868A4 | umac branchlink2
  Dec 13 11:53:36 james-x1 kernel: [  856.845183] iwlwifi :02:00.0: 

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

2018-12-13 Thread Patrik Nilsson
apport information

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

Title:
  Freeze when usb-data-collision with usb-mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To my computer I have connected a USB-hub and to that I have attached
  a USB-mouse and a USB-to-Ehternet adapter. The computer sometimes
  freezes completely and power button is the only escape. This happens
  when I scroll the mouse, press a button or moves the mouse (any event
  from the mouse).

  This can happen in any running program: Firefox, pdf-viewer,
  Libreoffice Writer...

  Most often this comes with my usb-to-ethernet LEDs switch off (during
  blink), but not always.

  Seems to be a collision event between my USB-mouse and USB-to-ethernet
  adapter, i.e mutex. An other computer without the USB-to-ethernet
  adapter never freezes. Configured in the same way.

  (I used Ubuntu 14.04 for a long time and this freeze never happened.
  In 18.04 this happens at least every two weeks. It is the same
  hardware.)

  $ uname -a
  Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   5276 F pulseaudio
   /dev/snd/controlC0:  user   5276 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: TOSHIBA SATELLITE Z30-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/hostname--vg--1542473018588400299-root ro quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxusers wireshark
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 04/09/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.20
  dmi.board.asset.tag: 00
  dmi.board.name: SATELLITE Z30-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnSATELLITEZ30-B:pvrPT258E-007015N5:rvnTOSHIBA:rnSATELLITEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: SATELLITE Z30-B
  dmi.product.version: PT258E-007015N5
  dmi.sys.vendor: TOSHIBA

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

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


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

2018-12-13 Thread Patrik Nilsson
apport information

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

Title:
  Freeze when usb-data-collision with usb-mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To my computer I have connected a USB-hub and to that I have attached
  a USB-mouse and a USB-to-Ehternet adapter. The computer sometimes
  freezes completely and power button is the only escape. This happens
  when I scroll the mouse, press a button or moves the mouse (any event
  from the mouse).

  This can happen in any running program: Firefox, pdf-viewer,
  Libreoffice Writer...

  Most often this comes with my usb-to-ethernet LEDs switch off (during
  blink), but not always.

  Seems to be a collision event between my USB-mouse and USB-to-ethernet
  adapter, i.e mutex. An other computer without the USB-to-ethernet
  adapter never freezes. Configured in the same way.

  (I used Ubuntu 14.04 for a long time and this freeze never happened.
  In 18.04 this happens at least every two weeks. It is the same
  hardware.)

  $ uname -a
  Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   5276 F pulseaudio
   /dev/snd/controlC0:  user   5276 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: TOSHIBA SATELLITE Z30-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/hostname--vg--1542473018588400299-root ro quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxusers wireshark
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 04/09/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.20
  dmi.board.asset.tag: 00
  dmi.board.name: SATELLITE Z30-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnSATELLITEZ30-B:pvrPT258E-007015N5:rvnTOSHIBA:rnSATELLITEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: SATELLITE Z30-B
  dmi.product.version: PT258E-007015N5
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 1805631] Lsusb.txt

2018-12-13 Thread Patrik Nilsson
apport information

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

Title:
  Freeze when usb-data-collision with usb-mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To my computer I have connected a USB-hub and to that I have attached
  a USB-mouse and a USB-to-Ehternet adapter. The computer sometimes
  freezes completely and power button is the only escape. This happens
  when I scroll the mouse, press a button or moves the mouse (any event
  from the mouse).

  This can happen in any running program: Firefox, pdf-viewer,
  Libreoffice Writer...

  Most often this comes with my usb-to-ethernet LEDs switch off (during
  blink), but not always.

  Seems to be a collision event between my USB-mouse and USB-to-ethernet
  adapter, i.e mutex. An other computer without the USB-to-ethernet
  adapter never freezes. Configured in the same way.

  (I used Ubuntu 14.04 for a long time and this freeze never happened.
  In 18.04 this happens at least every two weeks. It is the same
  hardware.)

  $ uname -a
  Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   5276 F pulseaudio
   /dev/snd/controlC0:  user   5276 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: TOSHIBA SATELLITE Z30-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/hostname--vg--1542473018588400299-root ro quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxusers wireshark
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 04/09/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.20
  dmi.board.asset.tag: 00
  dmi.board.name: SATELLITE Z30-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnSATELLITEZ30-B:pvrPT258E-007015N5:rvnTOSHIBA:rnSATELLITEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: SATELLITE Z30-B
  dmi.product.version: PT258E-007015N5
  dmi.sys.vendor: TOSHIBA

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

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


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

2018-12-13 Thread Patrik Nilsson
apport information

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

Title:
  Freeze when usb-data-collision with usb-mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To my computer I have connected a USB-hub and to that I have attached
  a USB-mouse and a USB-to-Ehternet adapter. The computer sometimes
  freezes completely and power button is the only escape. This happens
  when I scroll the mouse, press a button or moves the mouse (any event
  from the mouse).

  This can happen in any running program: Firefox, pdf-viewer,
  Libreoffice Writer...

  Most often this comes with my usb-to-ethernet LEDs switch off (during
  blink), but not always.

  Seems to be a collision event between my USB-mouse and USB-to-ethernet
  adapter, i.e mutex. An other computer without the USB-to-ethernet
  adapter never freezes. Configured in the same way.

  (I used Ubuntu 14.04 for a long time and this freeze never happened.
  In 18.04 this happens at least every two weeks. It is the same
  hardware.)

  $ uname -a
  Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   5276 F pulseaudio
   /dev/snd/controlC0:  user   5276 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: TOSHIBA SATELLITE Z30-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/hostname--vg--1542473018588400299-root ro quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxusers wireshark
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 04/09/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.20
  dmi.board.asset.tag: 00
  dmi.board.name: SATELLITE Z30-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnSATELLITEZ30-B:pvrPT258E-007015N5:rvnTOSHIBA:rnSATELLITEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: SATELLITE Z30-B
  dmi.product.version: PT258E-007015N5
  dmi.sys.vendor: TOSHIBA

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

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


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

2018-12-13 Thread Patrik Nilsson
apport information

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

Title:
  Freeze when usb-data-collision with usb-mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To my computer I have connected a USB-hub and to that I have attached
  a USB-mouse and a USB-to-Ehternet adapter. The computer sometimes
  freezes completely and power button is the only escape. This happens
  when I scroll the mouse, press a button or moves the mouse (any event
  from the mouse).

  This can happen in any running program: Firefox, pdf-viewer,
  Libreoffice Writer...

  Most often this comes with my usb-to-ethernet LEDs switch off (during
  blink), but not always.

  Seems to be a collision event between my USB-mouse and USB-to-ethernet
  adapter, i.e mutex. An other computer without the USB-to-ethernet
  adapter never freezes. Configured in the same way.

  (I used Ubuntu 14.04 for a long time and this freeze never happened.
  In 18.04 this happens at least every two weeks. It is the same
  hardware.)

  $ uname -a
  Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   5276 F pulseaudio
   /dev/snd/controlC0:  user   5276 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: TOSHIBA SATELLITE Z30-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/hostname--vg--1542473018588400299-root ro quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxusers wireshark
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 04/09/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.20
  dmi.board.asset.tag: 00
  dmi.board.name: SATELLITE Z30-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnSATELLITEZ30-B:pvrPT258E-007015N5:rvnTOSHIBA:rnSATELLITEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: SATELLITE Z30-B
  dmi.product.version: PT258E-007015N5
  dmi.sys.vendor: TOSHIBA

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

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


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

2018-12-13 Thread Patrik Nilsson
apport information

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

Title:
  Freeze when usb-data-collision with usb-mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To my computer I have connected a USB-hub and to that I have attached
  a USB-mouse and a USB-to-Ehternet adapter. The computer sometimes
  freezes completely and power button is the only escape. This happens
  when I scroll the mouse, press a button or moves the mouse (any event
  from the mouse).

  This can happen in any running program: Firefox, pdf-viewer,
  Libreoffice Writer...

  Most often this comes with my usb-to-ethernet LEDs switch off (during
  blink), but not always.

  Seems to be a collision event between my USB-mouse and USB-to-ethernet
  adapter, i.e mutex. An other computer without the USB-to-ethernet
  adapter never freezes. Configured in the same way.

  (I used Ubuntu 14.04 for a long time and this freeze never happened.
  In 18.04 this happens at least every two weeks. It is the same
  hardware.)

  $ uname -a
  Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   5276 F pulseaudio
   /dev/snd/controlC0:  user   5276 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: TOSHIBA SATELLITE Z30-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/hostname--vg--1542473018588400299-root ro quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxusers wireshark
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 04/09/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.20
  dmi.board.asset.tag: 00
  dmi.board.name: SATELLITE Z30-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnSATELLITEZ30-B:pvrPT258E-007015N5:rvnTOSHIBA:rnSATELLITEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: SATELLITE Z30-B
  dmi.product.version: PT258E-007015N5
  dmi.sys.vendor: TOSHIBA

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

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


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

2018-12-13 Thread Patrik Nilsson
apport information

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

Title:
  Freeze when usb-data-collision with usb-mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To my computer I have connected a USB-hub and to that I have attached
  a USB-mouse and a USB-to-Ehternet adapter. The computer sometimes
  freezes completely and power button is the only escape. This happens
  when I scroll the mouse, press a button or moves the mouse (any event
  from the mouse).

  This can happen in any running program: Firefox, pdf-viewer,
  Libreoffice Writer...

  Most often this comes with my usb-to-ethernet LEDs switch off (during
  blink), but not always.

  Seems to be a collision event between my USB-mouse and USB-to-ethernet
  adapter, i.e mutex. An other computer without the USB-to-ethernet
  adapter never freezes. Configured in the same way.

  (I used Ubuntu 14.04 for a long time and this freeze never happened.
  In 18.04 this happens at least every two weeks. It is the same
  hardware.)

  $ uname -a
  Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   5276 F pulseaudio
   /dev/snd/controlC0:  user   5276 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: TOSHIBA SATELLITE Z30-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/hostname--vg--1542473018588400299-root ro quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxusers wireshark
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 04/09/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.20
  dmi.board.asset.tag: 00
  dmi.board.name: SATELLITE Z30-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnSATELLITEZ30-B:pvrPT258E-007015N5:rvnTOSHIBA:rnSATELLITEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: SATELLITE Z30-B
  dmi.product.version: PT258E-007015N5
  dmi.sys.vendor: TOSHIBA

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

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


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

2018-12-13 Thread Patrik Nilsson
apport information

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

Title:
  Freeze when usb-data-collision with usb-mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To my computer I have connected a USB-hub and to that I have attached
  a USB-mouse and a USB-to-Ehternet adapter. The computer sometimes
  freezes completely and power button is the only escape. This happens
  when I scroll the mouse, press a button or moves the mouse (any event
  from the mouse).

  This can happen in any running program: Firefox, pdf-viewer,
  Libreoffice Writer...

  Most often this comes with my usb-to-ethernet LEDs switch off (during
  blink), but not always.

  Seems to be a collision event between my USB-mouse and USB-to-ethernet
  adapter, i.e mutex. An other computer without the USB-to-ethernet
  adapter never freezes. Configured in the same way.

  (I used Ubuntu 14.04 for a long time and this freeze never happened.
  In 18.04 this happens at least every two weeks. It is the same
  hardware.)

  $ uname -a
  Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   5276 F pulseaudio
   /dev/snd/controlC0:  user   5276 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: TOSHIBA SATELLITE Z30-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/hostname--vg--1542473018588400299-root ro quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxusers wireshark
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 04/09/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.20
  dmi.board.asset.tag: 00
  dmi.board.name: SATELLITE Z30-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnSATELLITEZ30-B:pvrPT258E-007015N5:rvnTOSHIBA:rnSATELLITEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: SATELLITE Z30-B
  dmi.product.version: PT258E-007015N5
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 1805631] Re: Freeze when usb-data-collision with usb-mouse

2018-12-13 Thread Patrik Nilsson
apport information

** Tags added: apport-collected

** Description changed:

  To my computer I have connected a USB-hub and to that I have attached a
  USB-mouse and a USB-to-Ehternet adapter. The computer sometimes freezes
  completely and power button is the only escape. This happens when I
  scroll the mouse, press a button or moves the mouse (any event from the
  mouse).
  
  This can happen in any running program: Firefox, pdf-viewer, Libreoffice
  Writer...
  
  Most often this comes with my usb-to-ethernet LEDs switch off (during
  blink), but not always.
  
  Seems to be a collision event between my USB-mouse and USB-to-ethernet
  adapter, i.e mutex. An other computer without the USB-to-ethernet
  adapter never freezes. Configured in the same way.
  
  (I used Ubuntu 14.04 for a long time and this freeze never happened. In
  18.04 this happens at least every two weeks. It is the same hardware.)
  
  $ uname -a
  Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  user   5276 F pulseaudio
+  /dev/snd/controlC0:  user   5276 F pulseaudio
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 18.04
+ MachineType: TOSHIBA SATELLITE Z30-B
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/hostname--vg--1542473018588400299-root ro quiet splash 
vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-42-generic N/A
+  linux-backports-modules-4.15.0-42-generic  N/A
+  linux-firmware 1.173.2
+ RfKill:
+  0: phy0: Wireless LAN
+   Soft blocked: yes
+   Hard blocked: no
+ Tags:  bionic
+ Uname: Linux 4.15.0-42-generic x86_64
+ UnreportableReason: This report is about a package that is not installed.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: sudo vboxusers wireshark
+ WifiSyslog:
+  
+ _MarkForUpload: False
+ dmi.bios.date: 04/09/2015
+ dmi.bios.vendor: TOSHIBA
+ dmi.bios.version: Version 3.20
+ dmi.board.asset.tag: 00
+ dmi.board.name: SATELLITE Z30-B
+ dmi.board.vendor: TOSHIBA
+ dmi.board.version: Version A0
+ dmi.chassis.asset.tag: 00
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: TOSHIBA
+ dmi.chassis.version: Version 1.0
+ dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnSATELLITEZ30-B:pvrPT258E-007015N5:rvnTOSHIBA:rnSATELLITEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
+ dmi.product.family: 00
+ dmi.product.name: SATELLITE Z30-B
+ dmi.product.version: PT258E-007015N5
+ dmi.sys.vendor: TOSHIBA

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

Title:
  Freeze when usb-data-collision with usb-mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To my computer I have connected a USB-hub and to that I have attached
  a USB-mouse and a USB-to-Ehternet adapter. The computer sometimes
  freezes completely and power button is the only escape. This happens
  when I scroll the mouse, press a button or moves the mouse (any event
  from the mouse).

  This can happen in any running program: Firefox, pdf-viewer,
  Libreoffice Writer...

  Most often this comes with my usb-to-ethernet LEDs switch off (during
  blink), but not always.

  Seems to be a collision event between my USB-mouse and USB-to-ethernet
  adapter, i.e mutex. An other computer without the USB-to-ethernet
  adapter never freezes. Configured in the same way.

  (I used Ubuntu 14.04 for a long time and this freeze never happened.
  In 18.04 this happens at least every two weeks. It is the same
  hardware.)

  $ uname -a
  Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   5276 F pulseaudio
   /dev/snd/controlC0:  user   5276 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: TOSHIBA SATELLITE Z30-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/hostname--vg--1542473018588400299-root ro quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
  

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

2018-12-13 Thread Patrik Nilsson
apport information

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

Title:
  Freeze when usb-data-collision with usb-mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To my computer I have connected a USB-hub and to that I have attached
  a USB-mouse and a USB-to-Ehternet adapter. The computer sometimes
  freezes completely and power button is the only escape. This happens
  when I scroll the mouse, press a button or moves the mouse (any event
  from the mouse).

  This can happen in any running program: Firefox, pdf-viewer,
  Libreoffice Writer...

  Most often this comes with my usb-to-ethernet LEDs switch off (during
  blink), but not always.

  Seems to be a collision event between my USB-mouse and USB-to-ethernet
  adapter, i.e mutex. An other computer without the USB-to-ethernet
  adapter never freezes. Configured in the same way.

  (I used Ubuntu 14.04 for a long time and this freeze never happened.
  In 18.04 this happens at least every two weeks. It is the same
  hardware.)

  $ uname -a
  Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   5276 F pulseaudio
   /dev/snd/controlC0:  user   5276 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: TOSHIBA SATELLITE Z30-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/hostname--vg--1542473018588400299-root ro quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxusers wireshark
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 04/09/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.20
  dmi.board.asset.tag: 00
  dmi.board.name: SATELLITE Z30-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnSATELLITEZ30-B:pvrPT258E-007015N5:rvnTOSHIBA:rnSATELLITEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: SATELLITE Z30-B
  dmi.product.version: PT258E-007015N5
  dmi.sys.vendor: TOSHIBA

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

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


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

2018-12-13 Thread Patrik Nilsson
apport information

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

Title:
  Freeze when usb-data-collision with usb-mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To my computer I have connected a USB-hub and to that I have attached
  a USB-mouse and a USB-to-Ehternet adapter. The computer sometimes
  freezes completely and power button is the only escape. This happens
  when I scroll the mouse, press a button or moves the mouse (any event
  from the mouse).

  This can happen in any running program: Firefox, pdf-viewer,
  Libreoffice Writer...

  Most often this comes with my usb-to-ethernet LEDs switch off (during
  blink), but not always.

  Seems to be a collision event between my USB-mouse and USB-to-ethernet
  adapter, i.e mutex. An other computer without the USB-to-ethernet
  adapter never freezes. Configured in the same way.

  (I used Ubuntu 14.04 for a long time and this freeze never happened.
  In 18.04 this happens at least every two weeks. It is the same
  hardware.)

  $ uname -a
  Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   5276 F pulseaudio
   /dev/snd/controlC0:  user   5276 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: TOSHIBA SATELLITE Z30-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/hostname--vg--1542473018588400299-root ro quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxusers wireshark
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 04/09/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.20
  dmi.board.asset.tag: 00
  dmi.board.name: SATELLITE Z30-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnSATELLITEZ30-B:pvrPT258E-007015N5:rvnTOSHIBA:rnSATELLITEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: SATELLITE Z30-B
  dmi.product.version: PT258E-007015N5
  dmi.sys.vendor: TOSHIBA

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

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


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

2018-12-13 Thread Patrik Nilsson
apport information

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

Title:
  Freeze when usb-data-collision with usb-mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To my computer I have connected a USB-hub and to that I have attached
  a USB-mouse and a USB-to-Ehternet adapter. The computer sometimes
  freezes completely and power button is the only escape. This happens
  when I scroll the mouse, press a button or moves the mouse (any event
  from the mouse).

  This can happen in any running program: Firefox, pdf-viewer,
  Libreoffice Writer...

  Most often this comes with my usb-to-ethernet LEDs switch off (during
  blink), but not always.

  Seems to be a collision event between my USB-mouse and USB-to-ethernet
  adapter, i.e mutex. An other computer without the USB-to-ethernet
  adapter never freezes. Configured in the same way.

  (I used Ubuntu 14.04 for a long time and this freeze never happened.
  In 18.04 this happens at least every two weeks. It is the same
  hardware.)

  $ uname -a
  Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   5276 F pulseaudio
   /dev/snd/controlC0:  user   5276 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  MachineType: TOSHIBA SATELLITE Z30-B
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic 
root=/dev/mapper/hostname--vg--1542473018588400299-root ro quiet splash 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-42-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo vboxusers wireshark
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 04/09/2015
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.20
  dmi.board.asset.tag: 00
  dmi.board.name: SATELLITE Z30-B
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnSATELLITEZ30-B:pvrPT258E-007015N5:rvnTOSHIBA:rnSATELLITEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: SATELLITE Z30-B
  dmi.product.version: PT258E-007015N5
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

2018-12-13 Thread AaronMa
@ALinuxUser,

What is the issue on your laptop.
1, You use "psmouse.synaptics_intertouch=0" in 4.19 kenrel, Does touchpad work 
well?

2, Not fully dmesg uploaded after S3 resume, does touchpad work after
resume?

Could you upload dmesg after touchpad lost ?

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

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

  Terminology in case we use different terms:
  touchpad - just the rectangular touch-sensitive surface below the keyboard 
(xinput lists it as Synaptics TM3288-011)
  trackpoint - the red thingy built into the keyboard + 3 physical buttons 
below the keyboard (trackpoint and buttons are integrated together; listed in 
xinput as TPPS/2 Elan TrackPoint)

  On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
  enables proper S3 deep sleep state - users no longer have to patch
  DSDT tables to get it. It can be enabled in the BIOS settings. In X1
  carbon 6th generation models that have NFC, when laptop wakes from
  suspend by opening the lid, in most cases both touchpad and trackpoint
  stop working completely. They are also no longer listed when running
  xinput command. Sometimes just one of them stops working, usually the
  trackpoint. In some rare cases it is possible to bring them back by
  using these commands:

  echo -n none > /sys/devices/platform/i8042/serio1/drvctl
  echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
  rmmod psmouse
  modprobe psmouse

  These worked properly when waking up from S2Idle sleep state (had
  these in a script that runs after waking the machine from suspend),
  but with S3 deep sleep these rarely work and the only way to bring
  back touchpad and/or trackpoint is turning off the machine and turning
  it on (restart does not help).

  I could not find any pattern that would show when the input devices
  stop working or start working again using the commands mentioned
  above. It's completely random from my perspective.

  This is happening on the standard issue 4.15.0-33-generic kernel that
  shipped with my Ubuntu 18.04 (with updates), as well as with newer
  mainline kernels, such as the newest point versions of 4.17, 4.18 and
  4.19 RC2.

  This happens regardless of whether "blacklist i2c_i801" is commented
  out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
  whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
  Presence of TLP does not make it better, nor worse.

  It appears that non-NFC models are not affected. I know at least one
  Arch Linux user who has the exact same model, but without this issue.
  I'm using synaptics driver (no libinput installed), he uses libinput
  and doesn't have synaptics, if that information is of any use.
  Libinput does not seem to help.

  This forum thread also has more details from users who updated their
  BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
  Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
  Suspend-to/td-p/3998182/page/27

  Another related thread:
  https://bbs.archlinux.org/viewtopic.php?id=236367

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maciej 2651 F...m pulseaudio
   /dev/snd/controlC0:  maciej 2651 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Sep  8 13:45:43 2018
  HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET55W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KH006KPB
  dmi.board.vendor: 

[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

2018-12-13 Thread AaronMa
@Pietari,

Please booting with "psmouse.synaptics_intertouch=0" to enforce PS/2 mode.
And upload dmesg after S3/resume when touchpad lost.

your log shown rmi_smbus is still in use.

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

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

  Terminology in case we use different terms:
  touchpad - just the rectangular touch-sensitive surface below the keyboard 
(xinput lists it as Synaptics TM3288-011)
  trackpoint - the red thingy built into the keyboard + 3 physical buttons 
below the keyboard (trackpoint and buttons are integrated together; listed in 
xinput as TPPS/2 Elan TrackPoint)

  On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
  enables proper S3 deep sleep state - users no longer have to patch
  DSDT tables to get it. It can be enabled in the BIOS settings. In X1
  carbon 6th generation models that have NFC, when laptop wakes from
  suspend by opening the lid, in most cases both touchpad and trackpoint
  stop working completely. They are also no longer listed when running
  xinput command. Sometimes just one of them stops working, usually the
  trackpoint. In some rare cases it is possible to bring them back by
  using these commands:

  echo -n none > /sys/devices/platform/i8042/serio1/drvctl
  echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
  rmmod psmouse
  modprobe psmouse

  These worked properly when waking up from S2Idle sleep state (had
  these in a script that runs after waking the machine from suspend),
  but with S3 deep sleep these rarely work and the only way to bring
  back touchpad and/or trackpoint is turning off the machine and turning
  it on (restart does not help).

  I could not find any pattern that would show when the input devices
  stop working or start working again using the commands mentioned
  above. It's completely random from my perspective.

  This is happening on the standard issue 4.15.0-33-generic kernel that
  shipped with my Ubuntu 18.04 (with updates), as well as with newer
  mainline kernels, such as the newest point versions of 4.17, 4.18 and
  4.19 RC2.

  This happens regardless of whether "blacklist i2c_i801" is commented
  out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
  whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
  Presence of TLP does not make it better, nor worse.

  It appears that non-NFC models are not affected. I know at least one
  Arch Linux user who has the exact same model, but without this issue.
  I'm using synaptics driver (no libinput installed), he uses libinput
  and doesn't have synaptics, if that information is of any use.
  Libinput does not seem to help.

  This forum thread also has more details from users who updated their
  BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
  Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
  Suspend-to/td-p/3998182/page/27

  Another related thread:
  https://bbs.archlinux.org/viewtopic.php?id=236367

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maciej 2651 F...m pulseaudio
   /dev/snd/controlC0:  maciej 2651 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Sep  8 13:45:43 2018
  HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET55W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KH006KPB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset 

[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2018-12-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions

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


[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2018-12-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-control-center (Ubuntu)
   Status: New => Confirmed

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions

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


[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2018-12-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+subscriptions

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


[Kernel-packages] [Bug 1808437] [NEW] Unable to obtain an Emulex LPe35000 series adapter firmware dump in 18.04 - impacts end customer supportability

2018-12-13 Thread laurie barry
Public bug reported:

We are unable to obtain a LPe35000 adapter firmware dump in Ubuntu
18.04.  This prevents our debugging customer firmware related issues.
This patch was missed during upstream and inbox integration.

Our testing for months appeared to have succeeded due to invalid test
case.   Test case have been corrected to validate fw dump was correctly
provided.

This fix is very straightforward.

Reference upstream submit:
James Smart 2018-12-10 19:43:42 PST
The patch has been pushed upstream:
https://marc.info/?l=linux-scsi=154449943301058=2

Commit is pending from the upstream maintainer.

---
 Management support for IF_TYPE=6

 Symptoms: Firmware dump, loopback, etc are not working on Prism

 Cause: The driver has a strict check for SLI_INTF_IF_TYPE_2

 Fix: Extend the management support for SLI_INTF_IF_TYPE_6

 Unit Testing: Ran Onekat and captured firmware dump on Prism

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

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

Title:
  Unable to obtain an Emulex LPe35000 series adapter firmware dump in
  18.04 - impacts end customer supportability

Status in linux-aws package in Ubuntu:
  New

Bug description:
  We are unable to obtain a LPe35000 adapter firmware dump in Ubuntu
  18.04.  This prevents our debugging customer firmware related issues.
  This patch was missed during upstream and inbox integration.

  Our testing for months appeared to have succeeded due to invalid test
  case.   Test case have been corrected to validate fw dump was
  correctly provided.

  This fix is very straightforward.

  Reference upstream submit:
  James Smart 2018-12-10 19:43:42 PST
  The patch has been pushed upstream:
  https://marc.info/?l=linux-scsi=154449943301058=2

  Commit is pending from the upstream maintainer.

  ---
   Management support for IF_TYPE=6

   Symptoms: Firmware dump, loopback, etc are not working on Prism

   Cause: The driver has a strict check for SLI_INTF_IF_TYPE_2

   Fix: Extend the management support for SLI_INTF_IF_TYPE_6

   Unit Testing: Ran Onekat and captured firmware dump on Prism

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

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


[Kernel-packages] [Bug 1767808] Re: "drm timed out" with driver i915 + Intel Mobile GM965/GL960 Integrated Graphics with Kernel 4.15

2018-12-13 Thread David VANTYGHEM
Same bug with Linux Mint MATE, kernel 4.15.0-42, GPU Intel Mobile GM965/960, 
module i915.
Adding "video=SVIDEO-1:d" works.

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

Title:
  "drm timed out" with driver i915 + Intel Mobile GM965/GL960 Integrated
  Graphics with Kernel 4.15

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With Ubuntu 18.04 + Kernel 4.15, at boot time there are many periods when the 
boot freezes before the timeout of 10 seconds with Intel Mobile GM965/GL960 
Integrated Graphics (driver i915).
  In total it is 198 seconds that are lost in these timeouts during boot, more 
than 3 minutes!

  Regression is present since linux kernel 4.8 (with Ubuntu 16.04).

  To fix, explicitly disable the port with an i915 module setting with 
video=SVIDEO-1:d in the kernel command line parameter in the bootloader.
  1/ sudo gedit /etc/default/grub
  2/ add "video=SVIDEO-1:d" to "GRUB_CMDLINE_LINUX_DEFAULT" line
  3/ sudo update-grub

  After applying this, the system boots up much faster, there are no
  "drm ... timed out" messages.

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

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


[Kernel-packages] [Bug 1802821] Re: Serious design flaw using large external drives.

2018-12-13 Thread Robert Pearson
After a month of waiting for confirmation of the bug, I have reformatted
the partition as ext4. If this works (can copy 1.5TB in less than 2
days) the bug is in the NTFS support in Ubuntu. If it doesn't, I will
return the drive (Seagate says it is in warranty but refuses to provide
any support to Linux users) and chalk up another Ubuntu bug that is
being ignored by the Ubuntu community.

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

Title:
  Serious design flaw using large external drives.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am trying to recover data from an HFS+ files system on a 4TB
  external USB 3 drive. Copying 3TB from the 4TB HFS+ drive to a 4TB
  NTFS drive using MATE Terminal cp -anR from to took 2 days.

  When I try to copy the same data to a 6TB NTFS USB 3 drive the results
  are glacial. 750GB has taken over 6 days. Obviously there is a problem
  of scale drive in Ubuntu MATE. I invite the developers to plug in a
  12TB drive and see just how glacial (no - not glacial, more on the
  order of plate techtonics) slow their design is.

  Robert Pearson

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-38-generic 4.15.0-38.41
  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/controlC1:  robert 2102 F pulseaudio
   /dev/snd/controlC0:  robert 2102 F pulseaudio
  CurrentDesktop: MATE
  Date: Sun Nov 11 23:50:13 2018
  HibernationDevice: RESUME=UUID=aa95f07d-f769-44ca-8b33-0c5b3c78bdeb
  InstallationDate: Installed on 2018-10-25 (18 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=26dc3ca5-f3ae-47eb-92b6-4f02ed5ba4f0 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A88XM-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

2018-12-13 Thread bmaupin
** Description changed:

  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot, hanging
  at various screens:
  
  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked
  
  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
+ 
+ I'm running the latest BIOS.
  
  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:
  
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"
  
  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.
  
  This bug seems very similar to what's described here for the Thinkpad
  E485/E585:
  https://web.archive.org/web/20180919160303/https://evilazrael.de/content
  /getting-linux-boot-lenovo-thinkpad-e485e585
  
  I'll attach screenshots of various times I've encountered this bug over
  the last year.
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  
  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
-   Installed: 4.15.0-42.45
-   Candidate: 4.15.0-42.45
-   Version table:
-  *** 4.15.0-42.45 500
- 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
- 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
- 100 /var/lib/dpkg/status
+   Installed: 4.15.0-42.45
+   Candidate: 4.15.0-42.45
+   Version table:
+  *** 4.15.0-42.45 500
+ 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
+ 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
+ 100 /var/lib/dpkg/status
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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

Title:
  Thinkpad T430u won't boot without noapic workaround

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38

  I'm running the latest BIOS.

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the 

[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

2018-12-13 Thread bmaupin
** Attachment added: "IMG_20181028_141659821.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+attachment/5222108/+files/IMG_20181028_141659821.jpg

** Description changed:

  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot, hanging
  at various screens:
  
  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked
  
  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  
  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:
  
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"
  
  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.
  
+ This bug seems very similar to what's described here for the Thinkpad
+ E485/E585:
+ https://web.archive.org/web/20180919160303/https://evilazrael.de/content
+ /getting-linux-boot-lenovo-thinkpad-e485e585
+ 
  I'll attach screenshots of various times I've encountered this bug over
  the last year.
+ 
+ $ lsb_release -rd
+ Description:  Ubuntu 18.04.1 LTS
+ Release:  18.04
+ 
+ $ apt-cache policy linux-image-4.15.0-42-generic
+ linux-image-4.15.0-42-generic:
+   Installed: 4.15.0-42.45
+   Candidate: 4.15.0-42.45
+   Version table:
+  *** 4.15.0-42.45 500
+ 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
+ 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
+ 100 /var/lib/dpkg/status
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  bryan  2349 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
-  linux-restricted-modules-4.15.0-42-generic N/A
-  linux-backports-modules-4.15.0-42-generic  N/A
-  linux-firmware 1.173.2
+  linux-restricted-modules-4.15.0-42-generic N/A
+  linux-backports-modules-4.15.0-42-generic  N/A
+  linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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

Title:
  Thinkpad T430u won't boot without noapic workaround

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38

  I'm running the latest BIOS.

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  

[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

2018-12-13 Thread bmaupin
** Attachment added: "IMG_20180225_083323505.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+attachment/5222107/+files/IMG_20180225_083323505.jpg

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

Title:
  Thinkpad T430u won't boot without noapic workaround

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38

  I'm running the latest BIOS.

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585:
  https://web.archive.org/web/20180919160303/https://evilazrael.de/content
  /getting-linux-boot-lenovo-thinkpad-e485e585

  I'll attach screenshots of various times I've encountered this bug
  over the last year.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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

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


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

2018-12-13 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Thinkpad T430u won't boot without noapic workaround

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38

  I'm running the latest BIOS.

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585:
  https://web.archive.org/web/20180919160303/https://evilazrael.de/content
  /getting-linux-boot-lenovo-thinkpad-e485e585

  I'll attach screenshots of various times I've encountered this bug
  over the last year.

  $ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  $ apt-cache policy linux-image-4.15.0-42-generic
  linux-image-4.15.0-42-generic:
    Installed: 4.15.0-42.45
    Candidate: 4.15.0-42.45
    Version table:
   *** 4.15.0-42.45 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1751584] Re: Ubuntu doesn't boot with 4.13.0 kernels

2018-12-13 Thread bmaupin
I went ahead and filed this new bug that's more specific to my hardware:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418

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

Title:
  Ubuntu doesn't boot with 4.13.0 kernels

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Edit: the 4.13.0.37 kernel doesn't boot either.

  My system won't boot with the 4.13.0.36 kernel. Yesterday it hung at a
  flashing cursor screen. I updated a few packages yesterday (see below)
  and today it hangs at this screen:

  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  _

  Booting to the previous kernel (4.13.0-32) seems to work just fine.

  I'm using Ubuntu 16.04.3 on a Thinkpad T430u with an Intel i5-3317U.

  Is this possibly related to this bug?:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675

  $ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  $ apt-cache policy linux-image-4.13.0-36-generic
  linux-image-4.13.0-36-generic:
    Installed: 4.13.0-36.40~16.04.1
    Candidate: 4.13.0-36.40~16.04.1
    Version table:
   *** 4.13.0-36.40~16.04.1 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

  $ tail -n 2 /var/log/apt/history.log
  Upgrade: libpulsedsp:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
grub-common:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), 
pulseaudio:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
google-chrome-stable:amd64 (64.0.3282.167-1, 64.0.3282.186-1), 
python-apt-common:amd64 (1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), 
grub2-common:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), 
grub-pc:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), 
grub-pc-bin:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), 
ntpdate:amd64 (1:4.2.8p4+dfsg-3ubuntu5.7, 1:4.2.8p4+dfsg-3ubuntu5.8), 
ubuntu-drivers-common:amd64 (1:0.4.17.3, 1:0.4.17.6), python3-distupgrade:amd64 
(1:16.04.23, 1:16.04.24), libpulse0:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
libpulse0:i386 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
ubuntu-release-upgrader-core:amd64 (1:16.04.23, 1:16.04.24), 
libpulse-mainloop-glib0:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
python-apt:amd64 (1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), 
pulseaudio-module-x11:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
ubuntu-release-upgrader-gtk:amd64 (1:16.04.23, 1:16.04.24), 
pulseaudio-utils:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), python3-apt:amd64 
(1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), base-files:amd64 
(9.4ubuntu4.5, 9.4ubuntu4.6)
  End-Date: 2018-02-24  10:22:59

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Feb 25 08:37:33 2018
  InstallationDate: Installed on 2014-05-08 (1388 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: linux-hwe
  UpgradeStatus: Upgraded to xenial on 2016-08-05 (568 days ago)

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

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


[Kernel-packages] [Bug 1808418] [NEW] Thinkpad T430u won't boot without noapic workaround

2018-12-13 Thread bmaupin
Public bug reported:

I've used Ubuntu on this specific machine for years without problems,
but starting with the 4.13 kernel that came with the 17.10 HWE and
continuing into 18.04 kernels my computer would no longer boot, hanging
at various screens:

- A blank screen with a flashing cursor
- A screen with this message:
Loading Linux 4.13.0.36-generic ...
Loading initial ramdisk ...
- A screen with kernel messages, ending in:
APCI: EC: interrupt blocked

I've encountered the bug in a number of kernels, including:
- 4.13.0-32
- 4.13.0-36
- 4.13.0-37
- 4.15.0-24
- 4.15.0-34
- 4.15.0-36
- 4.15.0-38

I'm running the latest BIOS.

I was able to work around the issue by adding noapic to
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

I'm not entirely sure of the consequences of this workaround, but one
thing I've noticed is significantly reduced battery life.

This bug seems very similar to what's described here for the Thinkpad
E485/E585:
https://web.archive.org/web/20180919160303/https://evilazrael.de/content
/getting-linux-boot-lenovo-thinkpad-e485e585

I'll attach screenshots of various times I've encountered this bug over
the last year.

$ lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04

$ apt-cache policy linux-image-4.15.0-42-generic
linux-image-4.15.0-42-generic:
  Installed: 4.15.0-42.45
  Candidate: 4.15.0-42.45
  Version table:
 *** 4.15.0-42.45 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-42-generic 4.15.0-42.45
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bryan  2349 F pulseaudio
CurrentDesktop: XFCE
Date: Thu Dec 13 15:31:15 2018
HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
InstallationDate: Installed on 2014-05-08 (1680 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: LENOVO 3351CTO
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-42-generic N/A
 linux-backports-modules-4.15.0-42-generic  N/A
 linux-firmware 1.173.2
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
dmi.bios.date: 06/01/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: H6ETA0WW (2.18 )
dmi.board.asset.tag: Not Available
dmi.board.name: 3351CTO
dmi.board.vendor: LENOVO
dmi.board.version: Win8 STD DPK TPG
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T430u
dmi.product.name: 3351CTO
dmi.product.version: ThinkPad T430u
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug bionic

** Attachment added: "IMG_20180323_185926318.jpg"
   
https://bugs.launchpad.net/bugs/1808418/+attachment/5222090/+files/IMG_20180323_185926318.jpg

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

Title:
  Thinkpad T430u won't boot without noapic workaround

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot,
  hanging at various screens:

  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked

  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38

  I'm running the latest BIOS.

  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.

  This bug seems very similar to what's described here for the Thinkpad
  E485/E585:
  

[Kernel-packages] [Bug 1808412] Re: 4.15.0 memory allocation issue

2018-12-13 Thread Marc Gariépy
u cannot run the apport-collect script, but if there is something that
is really needed, please ask me and i will do my best give the
information.

thanks

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

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

Title:
  4.15.0 memory allocation issue

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My server is : 
  PowerEdge T630
  2x Intel(R) Xeon(R) CPU E5-2623 v4 @ 2.60GHz
  128G of ram
  4x VGA compatible controller [0300]: NVIDIA Corporation GP102 [TITAN X] 
[10de:1b00] (rev a1)

  Starting 116G ram 16vcpus + 4 pci passthrough allocating memory stops
  after about half of the memory.

  When upgrading from kernel 4.13.0 to 4.15.0 starting a vm takes a long
  time.

  I tested kernel : 
  linux-image-4.13.0-37 not affected
  linux-image-4.13.0-45 not affected
  linux-image-4.15.0-34 affected
  linux-image-4.15.0-42 affected

  After disabling transparent_hugepage on 4.15 everything seems to work
  correctly.

  cat /proc/cmdline 
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID= ro 
intel_iommu=on transparent_hugepage=never splash quiet vt.handoff=7

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

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


[Kernel-packages] [Bug 1751584] Re: Ubuntu doesn't boot with 4.13.0 kernels

2018-12-13 Thread bmaupin
...on second thought, I'm not sure updating it would be the best idea
since the end problem appears to be specific to my hardware. I think
it's probably better to mark this bug as invalid and create a new one.

** 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/1751584

Title:
  Ubuntu doesn't boot with 4.13.0 kernels

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Edit: the 4.13.0.37 kernel doesn't boot either.

  My system won't boot with the 4.13.0.36 kernel. Yesterday it hung at a
  flashing cursor screen. I updated a few packages yesterday (see below)
  and today it hangs at this screen:

  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  _

  Booting to the previous kernel (4.13.0-32) seems to work just fine.

  I'm using Ubuntu 16.04.3 on a Thinkpad T430u with an Intel i5-3317U.

  Is this possibly related to this bug?:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675

  $ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  $ apt-cache policy linux-image-4.13.0-36-generic
  linux-image-4.13.0-36-generic:
    Installed: 4.13.0-36.40~16.04.1
    Candidate: 4.13.0-36.40~16.04.1
    Version table:
   *** 4.13.0-36.40~16.04.1 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

  $ tail -n 2 /var/log/apt/history.log
  Upgrade: libpulsedsp:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
grub-common:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), 
pulseaudio:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
google-chrome-stable:amd64 (64.0.3282.167-1, 64.0.3282.186-1), 
python-apt-common:amd64 (1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), 
grub2-common:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), 
grub-pc:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), 
grub-pc-bin:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), 
ntpdate:amd64 (1:4.2.8p4+dfsg-3ubuntu5.7, 1:4.2.8p4+dfsg-3ubuntu5.8), 
ubuntu-drivers-common:amd64 (1:0.4.17.3, 1:0.4.17.6), python3-distupgrade:amd64 
(1:16.04.23, 1:16.04.24), libpulse0:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
libpulse0:i386 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
ubuntu-release-upgrader-core:amd64 (1:16.04.23, 1:16.04.24), 
libpulse-mainloop-glib0:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
python-apt:amd64 (1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), 
pulseaudio-module-x11:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
ubuntu-release-upgrader-gtk:amd64 (1:16.04.23, 1:16.04.24), 
pulseaudio-utils:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), python3-apt:amd64 
(1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), base-files:amd64 
(9.4ubuntu4.5, 9.4ubuntu4.6)
  End-Date: 2018-02-24  10:22:59

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Feb 25 08:37:33 2018
  InstallationDate: Installed on 2014-05-08 (1388 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: linux-hwe
  UpgradeStatus: Upgraded to xenial on 2016-08-05 (568 days ago)

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

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


[Kernel-packages] [Bug 1751584] Re: Ubuntu doesn't boot with 4.13.0 kernels

2018-12-13 Thread bmaupin
After upgrading my BIOS the problem came back again with the 4.15
kernels. I was able to solve the issue by adding noapic to
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

Once I did that, the kernels worked fine as did intel-microcode.

I'll update the description and details of the ticket to reflect my
findings.

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

Title:
  Ubuntu doesn't boot with 4.13.0 kernels

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Edit: the 4.13.0.37 kernel doesn't boot either.

  My system won't boot with the 4.13.0.36 kernel. Yesterday it hung at a
  flashing cursor screen. I updated a few packages yesterday (see below)
  and today it hangs at this screen:

  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  _

  Booting to the previous kernel (4.13.0-32) seems to work just fine.

  I'm using Ubuntu 16.04.3 on a Thinkpad T430u with an Intel i5-3317U.

  Is this possibly related to this bug?:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675

  $ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  $ apt-cache policy linux-image-4.13.0-36-generic
  linux-image-4.13.0-36-generic:
    Installed: 4.13.0-36.40~16.04.1
    Candidate: 4.13.0-36.40~16.04.1
    Version table:
   *** 4.13.0-36.40~16.04.1 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

  $ tail -n 2 /var/log/apt/history.log
  Upgrade: libpulsedsp:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
grub-common:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), 
pulseaudio:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
google-chrome-stable:amd64 (64.0.3282.167-1, 64.0.3282.186-1), 
python-apt-common:amd64 (1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), 
grub2-common:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), 
grub-pc:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), 
grub-pc-bin:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), 
ntpdate:amd64 (1:4.2.8p4+dfsg-3ubuntu5.7, 1:4.2.8p4+dfsg-3ubuntu5.8), 
ubuntu-drivers-common:amd64 (1:0.4.17.3, 1:0.4.17.6), python3-distupgrade:amd64 
(1:16.04.23, 1:16.04.24), libpulse0:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
libpulse0:i386 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
ubuntu-release-upgrader-core:amd64 (1:16.04.23, 1:16.04.24), 
libpulse-mainloop-glib0:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
python-apt:amd64 (1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), 
pulseaudio-module-x11:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
ubuntu-release-upgrader-gtk:amd64 (1:16.04.23, 1:16.04.24), 
pulseaudio-utils:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), python3-apt:amd64 
(1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), base-files:amd64 
(9.4ubuntu4.5, 9.4ubuntu4.6)
  End-Date: 2018-02-24  10:22:59

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Feb 25 08:37:33 2018
  InstallationDate: Installed on 2014-05-08 (1388 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: linux-hwe
  UpgradeStatus: Upgraded to xenial on 2016-08-05 (568 days ago)

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

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


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

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

apport-collect 1808412

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

** Tags added: bionic

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

Title:
  4.15.0 memory allocation issue

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My server is : 
  PowerEdge T630
  2x Intel(R) Xeon(R) CPU E5-2623 v4 @ 2.60GHz
  128G of ram
  4x VGA compatible controller [0300]: NVIDIA Corporation GP102 [TITAN X] 
[10de:1b00] (rev a1)

  Starting 116G ram 16vcpus + 4 pci passthrough allocating memory stops
  after about half of the memory.

  When upgrading from kernel 4.13.0 to 4.15.0 starting a vm takes a long
  time.

  I tested kernel : 
  linux-image-4.13.0-37 not affected
  linux-image-4.13.0-45 not affected
  linux-image-4.15.0-34 affected
  linux-image-4.15.0-42 affected

  After disabling transparent_hugepage on 4.15 everything seems to work
  correctly.

  cat /proc/cmdline 
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID= ro 
intel_iommu=on transparent_hugepage=never splash quiet vt.handoff=7

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

-- 
Mailing list: https://launchpad.net/~kernel-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

2018-12-13 Thread Kalin Stoyanov
Hi all, I decided to try "ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=0:00.2"
and it actually worked for me. It is possible that I am a complete idiot
and misspelled it 5 times in a row before, but I could have sworn it did
nothing before. Now suspend and brightness keys work..:

k@k-Aspire-A315-41:~$ journalctl -b | grep AMD-Vi
Dec 13 21:57:49 k-Aspire-A315-41 kernel: AMD-Vi: IOMMU performance counters 
supported
Dec 13 21:57:49 k-Aspire-A315-41 kernel: AMD-Vi: Found IOMMU at :00:00.2 
cap 0x40
Dec 13 21:57:49 k-Aspire-A315-41 kernel: AMD-Vi: Extended features 
(0x4f77ef22294ada):
Dec 13 21:57:49 k-Aspire-A315-41 kernel: AMD-Vi: Interrupt remapping enabled
Dec 13 21:57:49 k-Aspire-A315-41 kernel: AMD-Vi: virtual APIC enabled
Dec 13 21:57:49 k-Aspire-A315-41 kernel: AMD-Vi: Lazy IO/TLB flushing enabled

However it the sensors are still not working:
(this is exactly the same as before)
k@k-Aspire-A315-41:~$ sensors
amdgpu-pci-0300
Adapter: PCI adapter
fan1: N/A
temp1: +0.0°C  (crit =  +0.0°C, hyst =  +0.0°C)

k10temp-pci-00c3
Adapter: PCI adapter
temp1:+44.2°C  (high = +70.0°C)

I am still running Ubuntu 18.04 with the oldest bios. Full model is A315-41-R88G
dmesg: https://paste.ubuntu.com/p/vmPdsQSRt4/
lspci: https://paste.ubuntu.com/p/g5NPcBhFpw/

-- 
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 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

2018-12-13 Thread whl2
> So I guess C-State failed to enter deeper state after suspend? Please
let ASUS know the issue.

Sorry, I certainly miss the point here. Could you please be a little bit
more specific - what exactly should I let ASUS know, if it was addressed
to me after all?

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

Title:
  CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT

Status in linux package in Ubuntu:
  Incomplete
Status in thermald package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
  GPU fans suddenly go full throttle. It doesn't seem to depend on
  temperature, could happen when 32 °C reported, sometimes the laptop
  can work for day or two without this issue, but eventually it happens.
  The only way to stop fans is to power off the laptop, power on (fans
  go 100% at this point again), power off during BIOS splash screen and
  power on again. Seems to happen more often after waking up from a
  sleep.

  Things tried:

  Upgrading BIOS to latest available on ASUS site to the date of
  writing. No change.

  asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
  both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
  does not seem to control it and does not prevent going full throttle.

  4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
  issue.

  Userspace fan control software (https://github.com/hirschmann/nbfc).
  Can control speed of both fans to the point where they go full
  throttle, after that has no effect on them.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  whale  3068 F pulseaudio
   /dev/snd/controlC0:  whale  3068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
  InstallationDate: Installed on 2014-10-20 (1333 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac 
(20140722.2)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia_modeset nvidia wl
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty 
video
  _MarkForUpload: True
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: G
  dmi.product.name: G752VT
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1808412] Re: 4.15.0 memory allocation issue

2018-12-13 Thread Marc Gariépy
4.18.0 is also affected.
Installed the pkg on xenial, and the same issue was present, i didn't tested 
disabling the transparent_hugepage tho.

(wget http://security.ubuntu.com/ubuntu/pool/main/l/linux-signed/linux-
image-4.18.0-12-generic_4.18.0-12.13_amd64.deb
http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-
modules-4.18.0-12-generic_4.18.0-12.13_amd64.deb
http://security.ubuntu.com/ubuntu/pool/main/l/linux/linux-modules-
extra-4.18.0-12-generic_4.18.0-12.13_amd64.deb )

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

Title:
  4.15.0 memory allocation issue

Status in linux package in Ubuntu:
  New

Bug description:
  My server is : 
  PowerEdge T630
  2x Intel(R) Xeon(R) CPU E5-2623 v4 @ 2.60GHz
  128G of ram
  4x VGA compatible controller [0300]: NVIDIA Corporation GP102 [TITAN X] 
[10de:1b00] (rev a1)

  Starting 116G ram 16vcpus + 4 pci passthrough allocating memory stops
  after about half of the memory.

  When upgrading from kernel 4.13.0 to 4.15.0 starting a vm takes a long
  time.

  I tested kernel : 
  linux-image-4.13.0-37 not affected
  linux-image-4.13.0-45 not affected
  linux-image-4.15.0-34 affected
  linux-image-4.15.0-42 affected

  After disabling transparent_hugepage on 4.15 everything seems to work
  correctly.

  cat /proc/cmdline 
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID= ro 
intel_iommu=on transparent_hugepage=never splash quiet vt.handoff=7

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

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


[Kernel-packages] [Bug 1803206] Re: Please enable CONFIG_DMA_CMA=y on arm64

2018-12-13 Thread CodeExecution
Same issue here. Apps like Chromium freeze the Pi, and the display
output also goes off screen.

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

Title:
  Please enable CONFIG_DMA_CMA=y on arm64

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

Bug description:
  Using the generic arm64 kernel on my raspberry pi 3 it seems
  impossible to use any apps that require 3D graphics.  The X session
  crashes and a reboot is needed to make it bootable again.

  Inspecting dmesg, there are a lot of "failed to allocate CMA"
  messages.  Adding cma=256M to the kernel command line has no effect.
  Dropping resolution allows firefox to start, but 3D apps still fail.

  I believe the vc4 driver needs CONFIG_DMA_CMA=y, which currently the
  generic kernel does not set.  The raspi2 kernel has this and 3D
  graphics works.

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

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


[Kernel-packages] [Bug 1808412] [NEW] 4.15.0 memory allocation issue

2018-12-13 Thread Marc Gariépy
Public bug reported:

My server is : 
PowerEdge T630
2x Intel(R) Xeon(R) CPU E5-2623 v4 @ 2.60GHz
128G of ram
4x VGA compatible controller [0300]: NVIDIA Corporation GP102 [TITAN X] 
[10de:1b00] (rev a1)

Starting 116G ram 16vcpus + 4 pci passthrough allocating memory stops
after about half of the memory.

When upgrading from kernel 4.13.0 to 4.15.0 starting a vm takes a long
time.

I tested kernel : 
linux-image-4.13.0-37 not affected
linux-image-4.13.0-45 not affected
linux-image-4.15.0-34 affected
linux-image-4.15.0-42 affected

After disabling transparent_hugepage on 4.15 everything seems to work
correctly.

cat /proc/cmdline 
BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID= ro 
intel_iommu=on transparent_hugepage=never splash quiet vt.handoff=7

** 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/1808412

Title:
  4.15.0 memory allocation issue

Status in linux package in Ubuntu:
  New

Bug description:
  My server is : 
  PowerEdge T630
  2x Intel(R) Xeon(R) CPU E5-2623 v4 @ 2.60GHz
  128G of ram
  4x VGA compatible controller [0300]: NVIDIA Corporation GP102 [TITAN X] 
[10de:1b00] (rev a1)

  Starting 116G ram 16vcpus + 4 pci passthrough allocating memory stops
  after about half of the memory.

  When upgrading from kernel 4.13.0 to 4.15.0 starting a vm takes a long
  time.

  I tested kernel : 
  linux-image-4.13.0-37 not affected
  linux-image-4.13.0-45 not affected
  linux-image-4.15.0-34 affected
  linux-image-4.15.0-42 affected

  After disabling transparent_hugepage on 4.15 everything seems to work
  correctly.

  cat /proc/cmdline 
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID= ro 
intel_iommu=on transparent_hugepage=never splash quiet vt.handoff=7

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

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


[Kernel-packages] [Bug 1807250] Re: At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my system

2018-12-13 Thread Your full name
Yeah, so this is like the person who started complaining about this
stuff which was totally confirmed by nacc.

Exceedingly fun fact: current bionic userspace/install booted with
debian stable kernel 4.9, debian testing kernel 4.18 and ye olde xenial
4.4.0-134 is working just fine *indicating* that support for an entire
bus class has been missing/faulty in ubuntu >=4.15 since bionic launch
like way back before everyone knew the name Cambridge Analytica and that
girl with the weird teeth from "Smallville" was charged with human
trafficking or whatever. I realize that people have selfies to take and
like totally have to spend a lot of time placating their friends about
their issues and stuff but that no one noticed this until now is kinda
disturbing and I like totally have to resist the urge to somehow
implicate Kylie Jenner in this.

The reason for the attitude is that i had to complete a friggin js-
required Scroogle puzzle to state the obvious.

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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

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

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

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


[Kernel-packages] [Bug 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

2018-12-13 Thread Michael J
FWIW...Last night, I upgraded Debian9 from stock kernel 4.9 -> 4.18
using debian-backports. Very important, forced the amd-gpu firmware to
the backported version also. Have ivrs_ioapic[4]=00:14.0
ivrs_ioapic[5]=0:00.2 added to my grub config permanently. No boot
errors and it is using the raven ridge dgpu drivers [DRM]. Suspend works
a treat and left it on for almost 24hrs, no lockups. Runs cool, with the
fan hardly coming on [low RPM]. Seems quite stable. This may be of help
to anyone that needs a distro to use for the time being. According to my
research, seems a lot of these issues are due to buggy BIOS acpi tables
and lack of raven ridge dgpu support in the kernel.

-- 
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 1805920] Re: iPXE ignores vlan 0 traffic

2018-12-13 Thread Andres Rodriguez
FWIW, Cisco documentation here states that priority tagging is enabled
by default:

https://www.cisco.com/c/en/us/td/docs/switches/connectedgrid/cg-switch-
sw-master/software/configuration/guide/vlan0/b_vlan_0.html

"Default Settings
VLAN 0 priority tagging is enabled by default."

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

2018-12-13 Thread caravena
!!
!!ALSA Information Script v 0.4.64
!!

!!Script ran on: Wed Dec 12 18:48:09 UTC 2018

http://www.alsa-
project.org/db/?f=697ac07e0a3265eb4d04b32bc0114e1eaf1119ee

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

2018-12-13 Thread caravena
I really do not know. In Windows 10 it works well.

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

2018-12-13 Thread Richard Baka
yep, I'm trying to make a better patch, please be patient :D

-- 
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 1805920] Re: iPXE ignores vlan 0 traffic

2018-12-13 Thread Vern Hart
It seems an important component to the failure scenario is the hardware.
The customer equipment is a Cisco UCS chassis and the MAAS nodes are
blades in that chassis. Even though we cannot find anything in
configuration that specifically adds the vlan-0 tag (or priority tag),
traffic between the blades goes out one node untagged and shows up
tagged on the other node.

Some bugs/discussions around vlan-0 and UCS:

  https://quickview.cloudapps.cisco.com/quickview/bug/CSCuu29425
  https://quickview.cloudapps.cisco.com/quickview/bug/CSCuz83183
  https://bugs.launchpad.net/opencontrail/+bug/1457805
  https://arstechnica.com/civis/viewtopic.php?f=10=1442797
  https://lists.linuxfoundation.org/pipermail/fds-dev/2017-May/000710.html
  
http://lists.openstack.org/pipermail/openstack-operators/2013-April/002777.html
  https://linux.oracle.com/pls/apex/f?p=102:2:::NO::P2_VC_ID,P2_VERSION:606,1.0

As a note, Cisco seems to suggest it's a bug in Linux, citing these two
old posts:

  https://lists.openwall.net/netdev/2013/09/10/30
  https://lists.linuxfoundation.org/pipermail/bridge/2015-July/009630.html

But I'm not convinced they are valid since this vlan-0 tag problem only
shows up with this specific Cisco hardware. It seems like there are
multiple network related software projects (like ipxe, vpp, probably
others) that are forced to deal with the special case of vlan 0
(priority tagging) being added by Cisco UCS switches because Cisco's
stance is that they're not adding the tags.

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

  

[Kernel-packages] [Bug 1781879] Re: Latest ASUS trackpad doesn't work in Ubuntu

2018-12-13 Thread Kieran Robinson
FIX

wget -c http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19/linux-
headers-4.19.0-041900_4.19.0-041900.201810221809_all.deb

wget -c http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19/linux-
headers-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb

wget -c http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19/linux-image-
unsigned-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb

wget -c http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19/linux-
modules-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb

sudo dpkg -i *.deb

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1808399] [NEW] Bionic update: upstream stable patchset 2018-12-13

2018-12-13 Thread 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-13 (ported from v4.14.55 and v4.17.6)
   from git://git.kernel.org/

i2c: core: smbus: fix a potential missing-check bug
drm/amdgpu: Dynamically probe for ATIF handle (v2)
drm/amdgpu: Add amdgpu_atpx_get_dhandle()
ARM: dts: imx51-zii-rdu1: fix touchscreen pinctrl
scsi: aacraid: Fix PD performance regression over incorrect qd being set
drm/amdgpu: Make struct amdgpu_atif private to amdgpu_acpi.c
PCI / ACPI / PM: Resume bridges w/o drivers on suspend-to-RAM
sched, tracing: Fix trace_sched_pi_setprio() for deboosting
staging: comedi: quatech_daqp_cs: fix no-op loop daqp_ao_insn_write()
netfilter: nf_log: don't hold nf_log_mutex during user access
mtd: cfi_cmdset_0002: Change erase functions to check chip good only
mtd: cfi_cmdset_0002: Change erase functions to retry for error
mtd: cfi_cmdset_0002: Change definition naming to retry write operation
dm: prevent DAX mounts if not supported
dm: set QUEUE_FLAG_DAX accordingly in dm_table_set_restrictions()
dax: check for QUEUE_FLAG_DAX in bdev_dax_supported()
dax: change bdev_dax_supported() to support boolean returns
fs: allow per-device dax status checking for filesystems
media: cx25840: Use subdev host data for PLL override
Kbuild: fix # escaping in .cmd files for future Make
Revert "dpaa_eth: fix error in dpaa_remove()"
f2fs: truncate preallocated blocks in error case
media: vb2: core: Finish buffers at the end of the stream
HID: debug: check length before copy_to_user()
HID: hiddev: fix potential Spectre v1
HID: i2c-hid: Fix "incomplete report" noise
ext4: check superblock mapped prior to committing
ext4: add more mount time checks of the superblock
ext4: add more inode number paranoia checks
ext4: avoid running out of journal credits when appending to an inline file
ext4: never move the system.data xattr out of the inode body
ext4: include the illegal physical block in the bad map ext4_error msg
ext4: verify the depth of extent tree in ext4_find_extent()
ext4: only look at the bg_flags field if it is valid
ext4: always check block group bounds in ext4_init_block_bitmap()
ext4: make sure bitmaps and the inode table don't overlap with bg descriptors
ext4: always verify the magic number in xattr blocks
ext4: add corruption check in ext4_xattr_set_entry()
jbd2: don't mark block as modified if the handle is out of credits
drm/udl: fix display corruption of the last line
drm: Use kvzalloc for allocating blob property memory
cifs: Fix infinite loop when using hard mount option
cifs: Fix memory leak in smb2_set_ea()
cifs: Fix use after free of a mid_q_entry
vfio: Use get_user_pages_longterm correctly
drbd: fix access after free
s390: Correct register corruption in critical section cleanup
scsi: target: Fix truncated PR-in ReadKeys response
tracing: Fix missing return symbol in function_graph output
mm: hugetlb: yield when prepping struct pages
userfaultfd: hugetlbfs: fix userfaultfd_huge_must_wait() pte access

** 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 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:
  
- 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-13 (ported from v4.14.55 and 

[Kernel-packages] [Bug 1806569] Re: linux: 4.4.0-141.167 -proposed tracker

2018-12-13 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 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 FAILED

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1802481] Re: cryptsetup waits for zvol /dev/zvol/rpool/swap with no zpool imported during boot. Timing problem?

2018-12-13 Thread Richard Laager
I really don’t know what to suggest here. As you mentioned, this used to
work. If you are only using LUKS for swap, maybe you could just remove
it from crypttab and run the appropriate commands manually in rc.local
or a custom systemd unit.

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

Title:
  cryptsetup waits for zvol /dev/zvol/rpool/swap with no zpool imported
  during boot. Timing problem?

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Hi,
  first of all: I don't know if it is a bug in cryptsetup-initramfs or 
zfs-initramfs or another one.

  The problem is that since my upgrade from bionic to cosmic the
  cryptsetup tries too early to setup my cryptswap device which is on a
  zvol.

cryptsetup: Waiting for encrypted source device /dev/zvol/rpool/swap...
 ALERT! encrypted source device /dev/zvol/rpool/swap does not exist, 
can't unlock cryptswap1.
...

  After timeout I find myself in a initramfs-shell (initramfs).
  When I do zpool list there is no zpool importet.
  After

zpool import -N rpool
^D

  the cryptsetup succeeds.
  Greetings,

 Lars

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: cryptsetup-initramfs 2:2.0.4-2ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov  9 10:01:19 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.logrotate.d.apport: [modified]
  mtime.conffile..etc.default.apport: 2015-03-15T20:01:19.851334
  mtime.conffile..etc.logrotate.d.apport: 2018-05-18T08:58:12.902005

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

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


[Kernel-packages] [Bug 1757435] Re: Redpine: WiFi scan stopping issue observed with BLE

2018-12-13 Thread RITIK RAWAT
** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => RITIK RAWAT (ritikrawat04)

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

Title:
  Redpine: WiFi scan stopping issue observed with BLE

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Fix Released

Bug description:
  SRU Justification:
  --

  Impact:
     WiFi scan stopping issue observed with BLE

  Test case:
     1)  Any PC (Ubuntu Desktop): setup iBeacon advertiser
     2)  Caracalla 3003 (Ubuntu Server/Core) run:
  ./scan.sh
   By default WiFi supplicant will run on Caracalla
   You can check the WiFi scan results by using below command
  iw dev wlan0 scan

   After 24hrs successful regression, we are unable to get the
  WiFi scan results by giving the above command

  Fix:
     Resolve this by waiting for the confirmation for a management packet from 
firmware.

  Regression potential:
  Below stress tests are conducted to ensure there is no issue in WiFi scan
  BLE Scan + WLAN scan
  BT Scan + WLAN scan
  BLE scan + WLAN connected

  Attached are BLE scripts.

  This bug is for tracking purposes only, please don't triage.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

2018-12-13 Thread Po-Hsu Lin
ecryptfs passed on s390x zVM (kernel01), issue caused by insufficient disk 
space.
Make this green again.

** Tags added: regression-testing-passed

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

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 1808389] [NEW] iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

2018-12-13 Thread James Turnbull
Public bug reported:

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

Firmware: 36.7596afd4.0


Dec 13 11:53:36 james-x1 kernel: [  856.840159] wlp2s0: send auth to 
60:38:e0:70:a2:11 (try 1/3)
Dec 13 11:53:36 james-x1 kernel: [  856.844875] iwlwifi :02:00.0: Microcode 
SW error detected.  Restarting 0x200.
Dec 13 11:53:36 james-x1 kernel: [  856.845015] iwlwifi :02:00.0: Start IWL 
Error Log Dump:
Dec 13 11:53:36 james-x1 kernel: [  856.845018] iwlwifi :02:00.0: Status: 
0x0100, count: 6
Dec 13 11:53:36 james-x1 kernel: [  856.845021] iwlwifi :02:00.0: Loaded 
firmware version: 36.7596afd4.0
Dec 13 11:53:36 james-x1 kernel: [  856.845024] iwlwifi :02:00.0: 
0x1006 | ADVANCED_SYSASSERT
Dec 13 11:53:36 james-x1 kernel: [  856.845026] iwlwifi :02:00.0: 
0x02F0 | trm_hw_status0
Dec 13 11:53:36 james-x1 kernel: [  856.845029] iwlwifi :02:00.0: 
0x | trm_hw_status1
Dec 13 11:53:36 james-x1 kernel: [  856.845031] iwlwifi :02:00.0: 
0x000248DC | branchlink2
Dec 13 11:53:36 james-x1 kernel: [  856.845034] iwlwifi :02:00.0: 
0x0003A7DA | interruptlink1
Dec 13 11:53:36 james-x1 kernel: [  856.845036] iwlwifi :02:00.0: 
0x | interruptlink2
Dec 13 11:53:36 james-x1 kernel: [  856.845039] iwlwifi :02:00.0: 
0xFEDA | data1
Dec 13 11:53:36 james-x1 kernel: [  856.845041] iwlwifi :02:00.0: 
0xDEADBEEF | data2
Dec 13 11:53:36 james-x1 kernel: [  856.845044] iwlwifi :02:00.0: 
0xDEADBEEF | data3
Dec 13 11:53:36 james-x1 kernel: [  856.845046] iwlwifi :02:00.0: 
0x0007E1DC | beacon time
Dec 13 11:53:36 james-x1 kernel: [  856.845048] iwlwifi :02:00.0: 
0x003B0850 | tsf low
Dec 13 11:53:36 james-x1 kernel: [  856.845051] iwlwifi :02:00.0: 
0x | tsf hi
Dec 13 11:53:36 james-x1 kernel: [  856.845053] iwlwifi :02:00.0: 
0x | time gp1
Dec 13 11:53:36 james-x1 kernel: [  856.845055] iwlwifi :02:00.0: 
0x003B0852 | time gp2
Dec 13 11:53:36 james-x1 kernel: [  856.845058] iwlwifi :02:00.0: 
0x0001 | uCode revision type
Dec 13 11:53:36 james-x1 kernel: [  856.845060] iwlwifi :02:00.0: 
0x0024 | uCode version major
Dec 13 11:53:36 james-x1 kernel: [  856.845063] iwlwifi :02:00.0: 
0x7596AFD4 | uCode version minor
Dec 13 11:53:36 james-x1 kernel: [  856.845065] iwlwifi :02:00.0: 
0x0230 | hw version
Dec 13 11:53:36 james-x1 kernel: [  856.845068] iwlwifi :02:00.0: 
0x18489000 | board version
Dec 13 11:53:36 james-x1 kernel: [  856.845070] iwlwifi :02:00.0: 
0x0501001C | hcmd
Dec 13 11:53:36 james-x1 kernel: [  856.845072] iwlwifi :02:00.0: 
0x00023008 | isr0
Dec 13 11:53:36 james-x1 kernel: [  856.845075] iwlwifi :02:00.0: 
0x000D | isr1
Dec 13 11:53:36 james-x1 kernel: [  856.845077] iwlwifi :02:00.0: 
0x08001802 | isr2
Dec 13 11:53:36 james-x1 kernel: [  856.845080] iwlwifi :02:00.0: 
0x0041FDC0 | isr3
Dec 13 11:53:36 james-x1 kernel: [  856.845082] iwlwifi :02:00.0: 
0x | isr4
Dec 13 11:53:36 james-x1 kernel: [  856.845084] iwlwifi :02:00.0: 
0x00580118 | last cmd Id
Dec 13 11:53:36 james-x1 kernel: [  856.845087] iwlwifi :02:00.0: 
0x | wait_event
Dec 13 11:53:36 james-x1 kernel: [  856.845089] iwlwifi :02:00.0: 
0x76DD | l2p_control
Dec 13 11:53:36 james-x1 kernel: [  856.845091] iwlwifi :02:00.0: 
0x0020 | l2p_duration
Dec 13 11:53:36 james-x1 kernel: [  856.845094] iwlwifi :02:00.0: 
0x | l2p_mhvalid
Dec 13 11:53:36 james-x1 kernel: [  856.845096] iwlwifi :02:00.0: 
0x00A0 | l2p_addr_match
Dec 13 11:53:36 james-x1 kernel: [  856.845099] iwlwifi :02:00.0: 
0x000D | lmpm_pmg_sel
Dec 13 11:53:36 james-x1 kernel: [  856.845101] iwlwifi :02:00.0: 
0x22040707 | timestamp
Dec 13 11:53:36 james-x1 kernel: [  856.845103] iwlwifi :02:00.0: 
0x6070 | flow_handler
Dec 13 11:53:36 james-x1 kernel: [  856.845170] iwlwifi :02:00.0: Start IWL 
Error Log Dump:
Dec 13 11:53:36 james-x1 kernel: [  856.845173] iwlwifi :02:00.0: Status: 
0x0100, count: 7
Dec 13 11:53:36 james-x1 kernel: [  856.845176] iwlwifi :02:00.0: 
0x0070 | ADVANCED_SYSASSERT
Dec 13 11:53:36 james-x1 kernel: [  856.845178] iwlwifi :02:00.0: 
0x | umac branchlink1
Dec 13 11:53:36 james-x1 kernel: [  856.845181] iwlwifi :02:00.0: 
0xC00868A4 | umac branchlink2
Dec 13 11:53:36 james-x1 kernel: [  856.845183] iwlwifi :02:00.0: 
0xC0083A94 | umac interruptlink1
Dec 13 11:53:36 james-x1 kernel: [  856.845186] iwlwifi :02:00.0: 
0xC0083A94 | umac interruptlink2
Dec 13 11:53:36 james-x1 kernel: [  856.845188] iwlwifi :02:00.0: 
0x0800 | umac data1
Dec 13 11:53:36 james-x1 kernel: [  856.845191] iwlwifi :02:00.0: 
0xC0083A94 | umac data2
Dec 13 11:53:36 james-x1 kernel: [  856.845193] iwlwifi :02:00.0: 
0xDEADBEEF | umac data3
Dec 13 11:53:36 james-x1 kernel: [  856.845196] iwlwifi :02:00.0: 
0x0024 | umac major
Dec 13 11:53:36 

[Kernel-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

2018-12-13 Thread Torsten Römer
I just would like to add that I have the same problem about once a day
on a DELL Latitude E5550, usually a relatively short while after
resuming from standby. It never happens when I boot into the older
4.15.0-39-generic kernel.

On a Lenovo L420 that I have updated at the same time, I never had the
problem so far.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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


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

2018-12-13 Thread Łukasz Zemczak
Hello Daniel, or anyone else affected,

Accepted unattended-upgrades into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.7~16.04.1 in a few hours, and then
in the -proposed repository.

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

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

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

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

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

Title:
  removing kernels should not require a restart afterward

Status in unattended-upgrades:
  New
Status in update notifier:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-notifier package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in update-notifier source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Won't Fix
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-notifier source package in Artful:
  Won't Fix

Bug description:
  [Impact]

  The rationale behind the SRU to Xenial is that with latest unattended-
  upgrades SRU it starts removing unused kernels, but all older kernels
  are not removed in a single run. With update-notifier and u-u not
  fixed they place /var/run/reboot-required asking for a reboot when it
  is not needed.

  
  [Test Case]

  1. Perform a kernel upgrade normally via "apt-get dist-upgrade".
  2. Reboot.
  3. Run "apt-get autoremove" to delete the old kernel packages.
  4. "System Notification Helper" now reports that the computer requires a 
reboot.

  The "autoremove" operation shouldn't require a reboot, logically
  speaking, because it's just removing files that are unused by the OS.

  [ Regression Potential ]

  If the check for skipping placing the /var/run/reboot-required file is too 
broad it may make kernel upgrades fail to ask for reboot. The fix changes a 
hook called by maintainer scripts and a failure in the hook can make kernel 
package installations fail.
  The fix is simple and was tested in several releases thus regressing in these 
ways is unlikely.

  [ Original Bug Text ]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: apt 1.0.1ubuntu2.7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May 23 12:47:15 2015
  InstallationDate: Installed on 2013-08-31 (629 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: apt
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago)
  ---
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308
  InstallationDate: Installed on 2013-08-31 (632 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic 
root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-53-generic N/A
   linux-backports-modules-3.13.0-53-generic  N/A
   linux-firmware 1.127.12
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-53-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago)
  UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 08/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4210
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79
  dmi.board.vendor: ASUSTeK 

[Kernel-packages] [Bug 1805433] Re: Call trace in dmesg (need to specify later what this is)

2018-12-13 Thread flip101
Well i was able to get the patches with

git clone https://git.kernel.org/ linux-13122018
cd linux-13122018
git remote add freedesktop git://people.freedesktop.org/~agd5f/linux
git fetch freedesktop amd-staging-drm-next
git checkout freedesktop/amd-staging-drm-next

Now i'm trying to follow this guide
https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel#Modifying_the_configuration
but i'm not sure if configuration changes are needed

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

Title:
  Call trace in dmesg (need to specify later what this is)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, I get a few call traces in my dmesg log which seems to indicate
  some problem. I'm trying to get my hardware better compatible with
  Ubuntu 18.10 therefor i report this bug. Actually i have no idea what
  this is about so i'll be happy to provide more information on request.

  There are actually a few call traces so i will upload the entire output from 
dmesg together with information on my system. Possibly the issues should be 
separated into several bug reports.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  philippe   4375 F pulseaudio
   /dev/snd/controlC0:  philippe   4375 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-05-14 (198 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=5ef6da7b-eb86-45bd-ad30-df7141164c79 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.175.1
  Tags:  cosmic
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-11-16 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/23/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.70
  dmi.board.name: AB350 Gaming-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.70:bd07/23/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Kernel-packages] [Bug 1808353] Re: Blacklist Realtek Virtual IPMI device

2018-12-13 Thread Kai-Heng Feng
** Also affects: linux-oem (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/1808353

Title:
  Blacklist Realtek Virtual IPMI device

Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  New

Bug description:
  [Impact]
  System fails to do system suspend because of a non-working Realtek IPMI 
device.

  [Fix]
  Quote from the patch:
  "
  Realtek has some sort of "Virtual" IPMI device on the PCI bus as a
  KCS controller, but whatever it is, it's not one.  Ignore it if seen.
  "

  [Test]
  System suspend works after blacklisting the device.

  [Regression Potential]
  None. The driver has never worked for the device.

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

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


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

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

apport-collect 1808353

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

Title:
  Blacklist Realtek Virtual IPMI device

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  System fails to do system suspend because of a non-working Realtek IPMI 
device.

  [Fix]
  Quote from the patch:
  "
  Realtek has some sort of "Virtual" IPMI device on the PCI bus as a
  KCS controller, but whatever it is, it's not one.  Ignore it if seen.
  "

  [Test]
  System suspend works after blacklisting the device.

  [Regression Potential]
  None. The driver has never worked for the device.

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

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


[Kernel-packages] [Bug 1808353] [NEW] Blacklist Realtek Virtual IPMI device

2018-12-13 Thread Kai-Heng Feng
Public bug reported:

[Impact]
System fails to do system suspend because of a non-working Realtek IPMI device.

[Fix]
Quote from the patch:
"
Realtek has some sort of "Virtual" IPMI device on the PCI bus as a
KCS controller, but whatever it is, it's not one.  Ignore it if seen.
"

[Test]
System suspend works after blacklisting the device.

[Regression Potential]
None. The driver has never worked for the device.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1808353

Title:
  Blacklist Realtek Virtual IPMI device

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [Impact]
  System fails to do system suspend because of a non-working Realtek IPMI 
device.

  [Fix]
  Quote from the patch:
  "
  Realtek has some sort of "Virtual" IPMI device on the PCI bus as a
  KCS controller, but whatever it is, it's not one.  Ignore it if seen.
  "

  [Test]
  System suspend works after blacklisting the device.

  [Regression Potential]
  None. The driver has never worked for the device.

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

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


[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

2018-12-13 Thread Kai-Heng Feng
Olivers, please file a new bug as r8151 is a completely different
device.

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

Title:
  r8169 ethernet card don't work after returning from suspension

Status in Linux:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

  ===Original Bug Report===
  I have noticed that the network stopped working on my desktop after I've 
suspended the system and woke it up. On dmesg there are messages like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity:
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled 

[Kernel-packages] [Bug 1633839] Re: No symbol table. Press any key to continue

2018-12-13 Thread Alex N.
*** This bug is a duplicate of bug 1620678 ***
https://bugs.launchpad.net/bugs/1620678

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633839/+attachment/4761889/+files/CurrentDmesg.txt

** Attachment removed: "ProcModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633839/+attachment/4761898/+files/ProcModules.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633839/+attachment/4761890/+files/Dependencies.txt

** Attachment removed: "IwConfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633839/+attachment/4761891/+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/1633839

Title:
  No symbol table. Press any key to continue

Status in grub2 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.10. shows "error: no symbol table. Press any key to
  continue..." after Kernel boot and before login screen. After pressing
  a key or waiting a few seconds, the boot process continues and login
  screen appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:     7722 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct 16 13:25:22 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=9d3bac9d-90f6-4fb6-ba39-e08ea2c3aa19
  InstallationDate: Installed on 2013-10-28 (1083 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 23255B2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA6WW (2.66 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23255B2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: CS023589
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn23255B2:pvrThinkPadX230:rvnLENOVO:rn23255B2:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 23255B2
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-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

2018-12-13 Thread Frank Heimes
** Changed in: ubuntu-power-systems
   Status: Triaged => 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/1788549

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

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

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 1633839] Re: No symbol table. Press any key to continue

2018-12-13 Thread Ashok
*** This bug is a duplicate of bug 1620678 ***
https://bugs.launchpad.net/bugs/1620678

Thanks. This solution worked for me..

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

Title:
  No symbol table. Press any key to continue

Status in grub2 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.10. shows "error: no symbol table. Press any key to
  continue..." after Kernel boot and before login screen. After pressing
  a key or waiting a few seconds, the boot process continues and login
  screen appears.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:     7722 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Oct 16 13:25:22 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=9d3bac9d-90f6-4fb6-ba39-e08ea2c3aa19
  InstallationDate: Installed on 2013-10-28 (1083 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 23255B2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=3b21f524-fe80-4ab0-8b84-c03e44abcd8b ro elevator=deadline
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago)
  dmi.bios.date: 03/03/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETA6WW (2.66 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23255B2
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: CS023589
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETA6WW(2.66):bd03/03/2016:svnLENOVO:pn23255B2:pvrThinkPadX230:rvnLENOVO:rn23255B2:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 23255B2
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1802481] Re: cryptsetup waits for zvol /dev/zvol/rpool/swap with no zpool imported during boot. Timing problem?

2018-12-13 Thread Lars
Hey Richard,
OK I understand why this order has to be kept dunring boot amd I understand it 
is a personal problem and this bug can be closed.

It would be nice if you could point me to a workaround for my
installation as I would love to only encrypt swap and home as we have no
native zfs encryption right now.

Greetings,

   Lars

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

Title:
  cryptsetup waits for zvol /dev/zvol/rpool/swap with no zpool imported
  during boot. Timing problem?

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Hi,
  first of all: I don't know if it is a bug in cryptsetup-initramfs or 
zfs-initramfs or another one.

  The problem is that since my upgrade from bionic to cosmic the
  cryptsetup tries too early to setup my cryptswap device which is on a
  zvol.

cryptsetup: Waiting for encrypted source device /dev/zvol/rpool/swap...
 ALERT! encrypted source device /dev/zvol/rpool/swap does not exist, 
can't unlock cryptswap1.
...

  After timeout I find myself in a initramfs-shell (initramfs).
  When I do zpool list there is no zpool importet.
  After

zpool import -N rpool
^D

  the cryptsetup succeeds.
  Greetings,

 Lars

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: cryptsetup-initramfs 2:2.0.4-2ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Nov  9 10:01:19 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport: [modified]
  modified.conffile..etc.logrotate.d.apport: [modified]
  mtime.conffile..etc.default.apport: 2015-03-15T20:01:19.851334
  mtime.conffile..etc.logrotate.d.apport: 2018-05-18T08:58:12.902005

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

-- 
Mailing list: https://launchpad.net/~kernel-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

2018-12-13 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: Incomplete => In Progress

** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => In Progress

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

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

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

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

2018-12-13 Thread siyia
you only use ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=0:00.2 and load your
tables, is this right?

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

2018-12-13 Thread siyia
they seem alright, send me your patched tables or send them to my email
please i want to test them again.

-- 
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 1752772] Re: r8169 ethernet card don't work after returning from suspension

2018-12-13 Thread Oliver Valls
Also happens with driver=r8152 driverversion=v1.09.9. I'm on an Ubuntu
dell xps-13 and I'm using a dock station where the ehternet cable is
wired.

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

Title:
  r8169 ethernet card don't work after returning from suspension

Status in Linux:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

  ===Original Bug Report===
  I have noticed that the network stopped working on my desktop after I've 
suspended the system and woke it up. On dmesg there are messages like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity:
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Kernel-packages] [Bug 1805433] Re: Call trace in dmesg (need to specify later what this is)

2018-12-13 Thread flip101
I can try to build a kernel. How can i download all the patches and
apply them at the same time?

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

Title:
  Call trace in dmesg (need to specify later what this is)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello, I get a few call traces in my dmesg log which seems to indicate
  some problem. I'm trying to get my hardware better compatible with
  Ubuntu 18.10 therefor i report this bug. Actually i have no idea what
  this is about so i'll be happy to provide more information on request.

  There are actually a few call traces so i will upload the entire output from 
dmesg together with information on my system. Possibly the issues should be 
separated into several bug reports.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  philippe   4375 F pulseaudio
   /dev/snd/controlC0:  philippe   4375 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-05-14 (198 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=5ef6da7b-eb86-45bd-ad30-df7141164c79 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.175.1
  Tags:  cosmic
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-11-16 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/23/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P4.70
  dmi.board.name: AB350 Gaming-ITX/ac
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP4.70:bd07/23/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Gaming-ITX/ac:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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


[Kernel-packages] [Bug 1800649] Re: Add support for NVIDIA GPU passthrough

2018-12-13 Thread Jose Ricardo Ziviani
Hi Christian,

You're right, we're going to use our customized QEMU.

Thank you!!

Jose

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

Title:
  Add support for NVIDIA GPU passthrough

Status in linux package in Ubuntu:
  Won't Fix
Status in qemu package in Ubuntu:
  Won't Fix
Status in linux source package in Bionic:
  Won't Fix
Status in qemu source package in Bionic:
  Won't Fix

Bug description:
  This bug will keep track of an important feature that is being
  developed upstream and need to be backported to Ubuntu 18.04 PPC64.
  The feature allows QEMU/KVM guests to have NVIDIA GPUs passed-through.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

2018-12-13 Thread Richard Baka
Vendor ID:   AuthenticAMD
CPU family:  23
Model:   17
Model name:  AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx
Stepping:0
CPU MHz: 1402.460
CPU max MHz: 2000,
CPU min MHz: 1600,
BogoMIPS:3992.22
Virtualization:  AMD-V

acpitool -c
ű  CPU type   : AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx 
  Min/Max frequency  : 1600/2000 MHz
  Current frequency  : 1466 MHz
  Frequency governor : ondemand 
  Freq. scaling driver   : acpi-cpufreq 
  Cache size : 1466.690 KB
  Bogomips   : 3992.22 
  Bogomips   : 3992.22 
  Bogomips   : 3992.22 
  Bogomips   : 3992.22 
  Bogomips   : 3992.22 
  Bogomips   : 3992.22 
  Bogomips   : 3992.22 
  Bogomips   : 3992.22 
  Function Show_CPU_Info : could not read directory /proc/acpi/processor/
  Make sure your kernel has ACPI processor support enabled.


cpufreq: CPU frequency scaling tests.

Test 1 of 7: CPU frequency table consistency
PASSED: Test 1, CPU frequency tables are consistent

Test 2 of 7: CPU frequency table duplicates
PASSED: Test 2, No duplicates in CPU frequency table

Test 3 of 7: CPU frequency firmware limits
PASSED: Test 3, CPU BIOS limit OK

Test 4 of 7: CPU frequency claimed maximum
PASSED: Test 4, CPU max frequencies OK

Test 5 of 7: CPU frequency SW_ANY control
PASSED: Test 5, P-state coordination under hardware control.

Test 6 of 7: CPU frequency SW_ALL control
PASSED: Test 6, Firmware SW_ALL OK

Test 7 of 7: CPU frequency performance tests.
PASSED: Test 7, CPU performance scaling OK

maxfreq: Test max CPU frequencies against max scaling frequency.

Test 1 of 1: Maximum CPU frequency test.
This test checks the maximum CPU frequency as detected by the kernel for each
CPU against maxiumum frequency as specified by the BIOS frequency scaling
settings.
SKIPPED: Test 1, Cannot read CPU frequencies from /proc/cpuinfo, this generally
happens on AMD CPUs, skipping test.

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

2018-12-13 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 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 FAILED

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

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

2018-12-13 Thread Po-Hsu Lin
The ecryptfs test is constantly failing on kernel01.
Might be a disk space issue, put this on hold.

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

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

2018-12-13 Thread Po-Hsu Lin
4.18.0-13.14 - generic
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_kvm_unit_tests - 24 failed on amaura, 4 failed on gonzo, 22 failed on 
pepe, 20 failed on KVM nodes
  ubuntu_ltp - ar test failed with 4.15 KVM (bug 1765331)
  ubuntu_ltp_syscalls - getrandom02 timed out (bug 1797327) fanotify09-2 (bug 
1804594) msgstress03 (bug 1797341)
  xfstests - failed to build on C (bug 1802486)

Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  ubuntu_bpf - Failed sockmap unexpected timeout on ARM64 (bug 1805806)
  ubuntu_kvm_smoke_test - Unable to boot Xenial cloud image on Bionic ARM64 
ThunderX / Azure (bug 1765668)
  ubuntu_kvm_unit_tests - gicv2-mmio-up and gicv2-mmio-3p failed on Moonshot 
ARM64 (bug 1802492)
  ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594)
  xfstests - failed to build on C (bug 1802486)

44 / 46 tests were run, missing: ubuntu_blkdev_directio, 
ubuntu_unionmount_overlayfs_suite
Issue to note in i386:
  ubuntu_bpf - Some test in test_verifier failed on i386 Bionic (bug 1788578)
  ubuntu_kvm_unit_tests - 29 failed on pepe
  ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594)
  ubuntu_lttng_smoke_test - lttng-smoke test failed on i386 Cosmic (bug 1802495)
  xfstests - failed to build on C (bug 1802486)

Issue to note in ppc64le (P8):
  ubuntu_bpf - test_map failed on PowerPC (bug 1802474)
  ubuntu_kernel_selftests - powerpc build issue (bug 1808318)
  ubuntu_kvm_smoke_test - failed to start KVM with uvtool on P8 Bionic (bug 
1798358)
  ubuntu_kvm_unit_tests - sprs timed out (bug 1740017)
  ubuntu_ltp_syscalls - fallocate05 (bug 1783880) fanotify09-2 (bug 1804594)
  xfstests - failed to build on C (bug 1802486)

46 / 47 tests were run, missing: xfstests
Issue to note in ppc64le (P9):
  hwclock - hwclock test failed on PowerPC due to 0.x sec difference (bug 
1802233)
  ubuntu_bpf - test_map failed on PowerPC (bug 1802474)
  ubuntu_kernel_selftests - powerpc build issue (bug 1808318)
  ubuntu_kvm_unit_tests - sprs timed out (bug 1740017)
  ubuntu_ltp_syscalls - fallocate05 (bug 1783880) fanotify09-2 (bug 1804594)

Issue to note in s390x (KVM):
  ubuntu_bpf - test_verifier in ubuntu_bpf test failed with 'Failed to load 
prog' on Cosmic s390x (bug 1801033)
  ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) msgstress03 (bug 1797341)
  ubuntu_lxc - Container "reboot" is defined (bug 1788574)

Issue to note in s390x (Ubuntu on LPAR):
  ubuntu_bpf - test_verifier in ubuntu_bpf test failed with 'Failed to load 
prog' on Cosmic s390x (bug 1801033)
  ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594)
  ubuntu_lxc - lxc-test-api-reboot failed (bug 1776381) Container "reboot" is 
defined (bug 1788574)

Issue to note in s390x (zVM):
  ubuntu_bpf - test_verifier in ubuntu_bpf test failed with 'Failed to load 
prog' on Cosmic s390x (bug 1801033)
  ubuntu_kvm_unit_tests - skey failed (bug 1778705)
  ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) msgstress03 (bug 1797341)
  ubuntu_lxc - Container "reboot" is defined (bug 1788574)

Note: No xfstests for P9 as it does not have a scratch drive

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

[Kernel-packages] [Bug 1808318] Re: powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9

2018-12-13 Thread Po-Hsu Lin
** Also affects: ubuntu-kernel-tests
   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/1808318

Title:
  powerpc test in ubuntu_kernel_selftest failed on Cosmic P8/P9

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

Bug description:
  This test passed with 4.18.0-12 on the last cycle [1]
  But failed with the proposed 4.18.0-13 this time.

  Test failed to build because of a missing include file:
  50.   ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or 
directory

  Tried to reproduce this cycle with 4.18.0-12 first and this can be
  reproduced as well.

  
  39.   make: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc'
  40.   
BUILD_TARGET=/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment;
 mkdir -p $BUILD_TARGET; make OUTPUT=$BUILD_TARGET -k -C alignment all
  41.   make[1]: Entering directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment'
  42.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 copy_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_unaligned
  43.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 copy_first_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c 
-o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/copy_first_unaligned
  44.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 paste_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_unaligned
  45.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 paste_last_unaligned.c ../harness.c ../utils.c copy_paste_unaligned_common.c 
-o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/paste_last_unaligned
  46.   gcc -std=gnu99 -O2 -Wall -Werror 
-DGIT_VERSION='"Ubuntu-4.18.0-12.13-0-g3d21f8e15-dirty"' 
-I/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/include
 alignment_handler.c ../harness.c ../utils.c copy_paste_unaligned_common.c -o 
/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment/alignment_handler
  47.   make[1]: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc/alignment'
  48.   make: Leaving directory 
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/powerpc'
  49.   stderr:
  50.   ../../lib.mk:20: ../../../../scripts/subarch.include: No such file or 
directory
  51.   make[1]: *** No rule to make target 
'../../../../scripts/subarch.include'.
  52.   make[1]: Failed to remake makefile 
'../../../../scripts/subarch.include'.
  53.   make: *** [Makefile:38: alignment] Error 2

  
  [1] 
http://10.246.72.4/test-results/4.18.0-12.13-generic/entei__4.18.0-12.13__2018-11-15_16-03-00/ubuntu_kernel_selftests/results/ubuntu_kernel_selftests.powerpc/debug/ubuntu_kernel_selftests.powerpc.DEBUG.html

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-12-generic 4.18.0-12.13
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 13 10:20 seq
   crw-rw 1 root audio 116, 33 Dec 13 10:20 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: ppc64el
  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:
   [ 1446.852560] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
   [ 1446.855825] cfg80211: Loaded X.509 cert 'sforshee: 

[Kernel-packages] [Bug 1808321] [NEW] I plug in USB sound device. It worked, but then it stopped

2018-12-13 Thread Cristian Aravena Romero
Public bug reported:

Hello,

I plug in USB sound device. It worked, but then it stopped.

Best regards,
--
Cristian Aravena Romero (caravena)

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-4.19.0-9-generic 4.19.0-9.10
ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
Uname: Linux 4.19.0-9-generic x86_64
ApportVersion: 2.20.10-0ubuntu14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  caravena   2681 F pulseaudio
 /dev/snd/pcmC1D0c:   caravena   2681 F...m pulseaudio
 /dev/snd/pcmC1D0p:   caravena   2681 F...m pulseaudio
 /dev/snd/controlC0:  caravena   2681 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 13 08:22:23 2018
HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
InstallationDate: Installed on 2018-12-02 (10 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.19.0-9-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.19.0-9-generic N/A
 linux-backports-modules-4.19.0-9-generic  N/A
 linux-firmware1.176
SourcePackage: linux
UpgradeStatus: Upgraded to disco on 2018-12-02 (10 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

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


** Tags: 3px63la amd64 apport-bug disco hp hp-pavilion-x360-14-cd0008la 
package-from-proposed wayland-session

** Attachment added: "Captura de pantalla de 2018-12-13 08-26-46.png"
   
https://bugs.launchpad.net/bugs/1808321/+attachment/5221909/+files/Captura%20de%20pantalla%20de%202018-12-13%2008-26-46.png

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

Title:
  I plug in USB sound device. It worked, but then it stopped

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I plug in USB sound device. It worked, but then it stopped.

  Best regards,
  --
  Cristian Aravena Romero (caravena)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-9-generic 4.19.0-9.10
  ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
  Uname: Linux 4.19.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  caravena   2681 F pulseaudio
   /dev/snd/pcmC1D0c:   caravena   2681 F...m pulseaudio
   /dev/snd/pcmC1D0p:   caravena   2681 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2681 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 13 08:22:23 2018
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (10 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.19.0-9-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-9-generic N/A
   linux-backports-modules-4.19.0-9-generic  N/A
   linux-firmware1.176
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2018-12-02 (10 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:

  1   2   >