date:20180213

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

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1749089
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1749093/+subscriptions

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

[Kernel-packages] [Bug 1749221] Re: kernel crash / BUG: unable to handle kernel paging request at fffffe3ed8000020

2018-02-13 Thread Tetsuo Handa

Since you are using apparmor=0 parameter,
this will be a duplicate of bug 1734327.

Try removing apparmor=0 parameter for now.

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

Title:
   kernel crash / BUG: unable to handle kernel paging request at
  fe3ed820

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

Bug description:
  Booted under maas in rescue mode system console has the attached failure.
  First bit is

  [ 440.196466] BUG: unable to handle kernel paging request at
  fe3ed820

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic (not installed)
  ProcVersionSignature: User Name 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116, 33 Feb 13 15:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed 
with exit code 1:
  CRDA: N/A
  Date: Tue Feb 13 15:34:40 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=username/amd64/generic/xenial/daily/boot-kernel 
nomodeset 
root=squash:http://10.247.16.6:5248/images/username/amd64/generic/xenial/daily/squashfs
 ro ip=hostname:BOOTIF ip6=off overlayroot=tmpfs 
overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc 
cloud-config-url=http://10.247.16.6:5240/MAAS/metadata/latest/by-id/sbgyxn/?op=get_preseed
 apparmor=0 log_host=10.247.16.6 log_port=514 --- console=ttyS1 
BOOTIF=01-ec:b1:d7:7f:2a:6c
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd03/05/2015:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1676912] Re: Kernel 4.9+ regression: Suspend - Freezing of tasks failed

2018-02-13 Thread Jason Smith

Yea except "4.9+" meant it was still present in 4.10 (and 13 as well)

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

Title:
  Kernel 4.9+ regression: Suspend - Freezing of tasks failed

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu
  Gnome 17.04 and since then sometimes my Laptop won't suspend when I
  close the lid. The power led does not blink like it is supposed to do
  and when I open the Laptop the lockscreen appears but freezes after a
  short time, followed by a blackscreen until eventually it reappears
  and allows me to unlock it. After that certain application can not be
  started anymore and would freeze if they were running before. These
  include Chrome, Gedit and Gnome System Monitor for example. Also my
  Laptop will not connect to my WLAN until I restart it.

  In syslog I found the line:

  "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to
  freeze, wq_busy=0):"

  According to syslog

  network-nanaeger
  whoopsie
  cups-browsed
  wpa-supplicant
  geoclue
  packagekitd
  several evolution-related processes
  goa-daemon
  gnome-software
  geary
  dropbox
  deja-dup-monitor

  are responsible.
  I tried disabling some of them, but it did not solve the problem.

  Update: I tested different Kernel versions in the last days. So far
  there were no issues with suspend/resume using Kernel 4.8 and 4.9. The
  problem is present in 4.10 and 4.11.

  Update 2: I just encountered this issue with Kernel 4.9.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 28 16:27:34 2017
  InstallationDate: Installed on 2017-03-24 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 80J8
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed 
root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B8CN31WW(V2.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Paganini
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 3 11
  dmi.modalias: 
dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311:
  dmi.product.name: 80J8
  dmi.product.version: Lenovo Yoga 3 11
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

2018-02-13 Thread Bug Watch Updater

** Changed in: libinput
   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/1746740

Title:
  XPS13 L322X Bionic (daily dev) touchpad laggy

Status in libinput:
  Confirmed
Status in libinput package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Also, all function keys work as expected, even F6 (keyboard 3-states
  backlight), but OSD picture for this last feature randomly auto-
  triggers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1876 F pulseaudio
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 14:05:22 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr 
keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.

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

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

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

2018-02-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/1749329

Title:
  BUG: Bad rss-counter state mm:9ac8374f39c0 idx:1 val:1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No additional information.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1204 F pulseaudio
bertadmin   1928 F pulseaudio
  Date: Tue Feb 13 20:59:15 2018
  Failure: oops
  InstallationDate: Installed on 2017-12-22 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: Bad rss-counter state mm:9ac8374f39c0 idx:1 val:1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1749329] [NEW] BUG: Bad rss-counter state mm:ffff9ac8374f39c0 idx:1 val:1

2018-02-13 Thread BertN45

Public bug reported:

No additional information.

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.13.0-32-generic 4.13.0-32.35
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1204 F pulseaudio
  bertadmin   1928 F pulseaudio
Date: Tue Feb 13 20:59:15 2018
Failure: oops
InstallationDate: Installed on 2017-12-22 (53 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
IwConfig:
 lono wireless extensions.
 
 enp0s3no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcFB: 0 vboxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
RfKill:
 
SourcePackage: linux
Title: BUG: Bad rss-counter state mm:9ac8374f39c0 idx:1 val:1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-kerneloops bionic kernel-oops

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

Title:
  BUG: Bad rss-counter state mm:9ac8374f39c0 idx:1 val:1

Status in linux package in Ubuntu:
  New

Bug description:
  No additional information.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1204 F pulseaudio
bertadmin   1928 F pulseaudio
  Date: Tue Feb 13 20:59:15 2018
  Failure: oops
  InstallationDate: Installed on 2017-12-22 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=f3311827-9a0c-490d-a707-d4d037152c4d ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: BUG: Bad rss-counter state mm:9ac8374f39c0 idx:1 val:1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1748768] Re: System won't boot 4.13.0-32 kernel

2018-02-13 Thread Jim Carey

4.16 kernel booted fine.

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

Title:
  System won't boot 4.13.0-32 kernel

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

Bug description:
  Ever since the update to the 4.13.0-32 kernel, my system won't boot.
  When I turn off the splash screen and quiet, I see repeated messages
  about not connecting to lvmetad and falling back to device scanning.

  The disk has a boot partition and a logical volume partition.  The
  logical volume partition is encrypted with LUKS.

  I can boot the 4.13.0-31 kernel with no problems (that's where the
  data for this bug was collected).  I'm not sure how to troubleshoot
  this further.

  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:  jim5303 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Feb 11 11:01:02 2018
  HibernationDevice: RESUME=UUID=ff4e1c78-1dec-4f38-8cc2-e28a35635b6b
  InstallationDate: Installed on 2017-01-16 (391 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 2436CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-31-generic 
root=/dev/mapper/ubuntu--vg-root 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.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-31 (103 days ago)
  dmi.bios.date: 02/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ET92WW (2.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2436CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W530
  dmi.product.name: 2436CTO
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1748768] Re: System won't boot 4.13.0-32 kernel

2018-02-13 Thread Jim Carey

** Tags added: kernel-fixed-upstream

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

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

Title:
  System won't boot 4.13.0-32 kernel

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

Bug description:
  Ever since the update to the 4.13.0-32 kernel, my system won't boot.
  When I turn off the splash screen and quiet, I see repeated messages
  about not connecting to lvmetad and falling back to device scanning.

  The disk has a boot partition and a logical volume partition.  The
  logical volume partition is encrypted with LUKS.

  I can boot the 4.13.0-31 kernel with no problems (that's where the
  data for this bug was collected).  I'm not sure how to troubleshoot
  this further.

  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:  jim5303 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Feb 11 11:01:02 2018
  HibernationDevice: RESUME=UUID=ff4e1c78-1dec-4f38-8cc2-e28a35635b6b
  InstallationDate: Installed on 2017-01-16 (391 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 2436CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-31-generic 
root=/dev/mapper/ubuntu--vg-root 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.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-31 (103 days ago)
  dmi.bios.date: 02/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ET92WW (2.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2436CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W530
  dmi.product.name: 2436CTO
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1746848] Re: Ubuntu 17.10 keeps comming back after suspended on a Macbook Pro 15 retina 2013 late

2018-02-13 Thread Otto Julio Ahlert Pinno

Yes, I copied and pasted the text. However, I double checked it now.

I inserted the code, executed the commands and tried to suspend right
after. It seems that it worked, all quiet and cool. Even with
consecutive suspensions. When I tried to suspend it from the login
screen after the wake-up, it turned the screen black, turned the screen
on, turned it black again and, finally, all quiet and cool.

But, when I restarted the Ubuntu, it didn't worked anymore.

After, I tried to:
1 - Remove the text, execute the 2 commands, insert the text, execute the 
commands and suspend it.
2 - Remove the text, execute the 2 commands, restart the Ubuntu, insert the 
text, execute the commands and suspend it.
but it didn't worked again.

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

Title:
  Ubuntu 17.10 keeps comming back after suspended on a Macbook Pro 15
  retina 2013 late

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When I click on the suspend button (alternative of power off button)
  in the menu or I click the power button, the Ubuntu seems like will be
  suspended (with a black screen) and, after 5-10 seconds, come back to
  the login screen.

  Closing the lid also doesn't take effect. It doesn't even turn off the
  display.

  I found that clicking on the suspend button and very quickly closing
  the lid seems to make it stays suspended.

  I'm having this trouble in a Macbook Pro 15 retina 2013 late running a
  Ubuntu 17.10 in the most recent version.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  otto   1600 F pulseaudio
   /dev/snd/controlC0:  otto   1600 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 22:58:16 2018
  InstallationDate: Installed on 2018-01-26 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Apple Inc. MacBookPro10,1
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=b05cd5cb-c451-4546-a9e0-377ae91a2e44 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-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: Apple Inc.
  dmi.bios.version: MBP101.88Z.00F2.B00.1708080809
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00F2.B00.1708080809:bd08/08/2017:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1749089] Re: linux: 4.4.0-116.140 -proposed tracker

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

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

Title:
  linux: 4.4.0-116.140 -proposed tracker

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

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

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

  backports: bug 1749090 (linux-aws), bug 1749091 (linux-lts-xenial)
  derivatives: bug 1749092 (linux-kvm), bug 1749093 (linux-aws), bug 1749094 
(linux-raspi2), bug 1749095 (linux-euclid), bug 1749096 (linux-snapdragon), bug 
1749097 (linux-gke)
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1749089/+subscriptions

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

[Kernel-packages] [Bug 1748743] Re: linux: 4.13.0-35.39 -proposed tracker

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

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

Title:
  linux: 4.13.0-35.39 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  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 Artful:
  Confirmed

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1748743/+subscriptions

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

[Kernel-packages] [Bug 1741081] Re: zfs-import-cache.service fails on startup

2018-02-13 Thread Scott Emmons

Let me know what I can do to help move this forward. The ubuntu-load-
zfs-unconditionally patch was not a great solution as it results in
systems that install zfsutils-linux to come up in a failed state when
there are no ZFS pools present:

$ systemctl --failed
  UNIT LOAD   ACTIVE SUBDESCRIPTION   
* zfs-import-cache.service loaded failed failed Import ZFS pools by cache file

We use a common system image across a large fleet, some with ZFS pools,
most without - and would prefer not having to do a local override.conf
in our image.

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

Title:
  zfs-import-cache.service fails on startup

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  I just noticed on my test VM of artful that zfs-import-cache.service
  does not have a ConditionPathExists=/etc/zfs/zpool.cache. Because of
  that, it fails on startup, since the cache file does not exist.

  This line is being deleted by 
debian/patches/ubuntu-load-zfs-unconditionally.patch. This patch seems to exist 
per:
  https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1672749

  This patch still exists in bionic, so I assume it will be similarly
  broken.

  If the goal of the patch is to load the module (and only that), I
  think it should create a third unit instead:

  zfs-load-module.service
   ^^ runs modprobe zfs

  zfs-import-cache.service & zfs-import-scan.service
    ^^ per upstream minus modprobe plus Requires=zfs-load-module.service

  I have tested this manually and it works. I can submit a package patch
  if this is the desired solution.

  Interestingly, before this change, zfs-import-scan.service wasn't
  starting. If started manually, it worked. I had to give it a
  `systemctl enable zfs-import-scan.service` to create the Wants
  symlinks. Looking at the zfsutils-linux.postinst, I see the correct
  boilerplate from dh_systemd, so I'm not sure why this wasn't already
  done. Can anyone confirm or deny whether zfs-import-scan.service is
  enabled out-of-the-box on their system?

  Is the zfs-import-scan.service not starting actually the cause of the
  original bug? The design is that *either* zfs-import-cache.service or
  zfs-import-scan.service starts. They both call modprobe zfs.

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

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

[Kernel-packages] [Bug 1749207] Re: kernel is reporting Nintendo USB microphone as an output device

apport information

** Tags added: apport-collected bionic

** Description changed:

  Kernel is reporting Nintendo USB microphone as an output device.And
  because that alsa will use every time as a output device
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  a  1438 F pulseaudio
   /dev/snd/controlC0:  a  1438 F pulseaudio
   /dev/snd/controlC1:  a  1438 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 13 16:48:49 2018
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180212)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e1fa3a67-c257-4f26-b6fc-b72b872c2370 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: A88M-G/3.1
  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.40:bd05/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA88M-G/3.1: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.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
+ --- 
+ ApportVersion: 2.20.8-0ubuntu9
+ Architecture: amd64
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-02-13 (0 days ago)
+ InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180213)
+ Package: linux (not installed)
+ Tags:  bionic
+ Uname: Linux 4.16.0-041600rc1-generic x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1749207/+attachment/5054626/+files/JournalErrors.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/1749207

Title:
  kernel is reporting Nintendo USB microphone as an output device

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel is reporting Nintendo USB microphone as an output device.And
  because that alsa will use every time as a output device

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  a  1438 F pulseaudio
   /dev/snd/controlC0:  a  1438 F pulseaudio
   /dev/snd/controlC1:  a  1438 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 13 16:48:49 2018
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180212)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e1fa3a67-c257-4f26-b6fc-b72b872c2370 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: A88M-G/3.1
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  d

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

apport information

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

Title:
  kernel is reporting Nintendo USB microphone as an output device

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel is reporting Nintendo USB microphone as an output device.And
  because that alsa will use every time as a output device

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  a  1438 F pulseaudio
   /dev/snd/controlC0:  a  1438 F pulseaudio
   /dev/snd/controlC1:  a  1438 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 13 16:48:49 2018
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180212)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e1fa3a67-c257-4f26-b6fc-b72b872c2370 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: A88M-G/3.1
  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.40:bd05/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA88M-G/3.1: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.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ApportVersion: 2.20.8-0ubuntu9
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-02-13 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180213)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.16.0-041600rc1-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  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/linux/+bug/1749207/+subscriptions

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

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

apport information

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

Title:
  kernel is reporting Nintendo USB microphone as an output device

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel is reporting Nintendo USB microphone as an output device.And
  because that alsa will use every time as a output device

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  a  1438 F pulseaudio
   /dev/snd/controlC0:  a  1438 F pulseaudio
   /dev/snd/controlC1:  a  1438 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 13 16:48:49 2018
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180212)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e1fa3a67-c257-4f26-b6fc-b72b872c2370 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: A88M-G/3.1
  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.40:bd05/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA88M-G/3.1: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.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  --- 
  ApportVersion: 2.20.8-0ubuntu9
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-02-13 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180213)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.16.0-041600rc1-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  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/linux/+bug/1749207/+subscriptions

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

Re: [Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

2018-02-13 Thread Thomas Bielawski

On Feb 13, 2018 14:15, "redx" <1745...@bugs.launchpad.net> wrote:

> I have tested the patch and the touch is detected correctly, but if I
> detach and then reattach the dock keyboard, the keyboard stops working
> until i reboot the tablet.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1722677).
> https://bugs.launchpad.net/bugs/1745342
>
> Title:
>   touchscreen that worked in artful with 4.12 no longer works with 4.13
>
> Status in linux package in Ubuntu:
>   In Progress
> Status in linux source package in Artful:
>   In Progress
> Status in linux source package in Bionic:
>   In Progress
>
> Bug description:
>   I have a Dell Venue 11 Pro 7139, and when I installed artful on it
>   (before release) it worked fine. Recently (over the xmas break I think
>   but I'm not sure; this is not a machine I intended to pay too much
>   attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
>   has stopped working.
>
>   I _think_ the last kernel to work was 4.12.0-13. I haven't done any
>   sort of bisection though.
>
>   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:  john   1041 F pulseaudio
>/dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
>/dev/snd/controlC1:  john   1041 F pulseaudio
>   Date: Thu Jan 25 10:18:51 2018
>   InstallationDate: Installed on 2017-07-10 (198 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170709)
>   MachineType: Dell Inc. Venue 11 Pro 7139
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed
> root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 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: 06/15/2015
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: A16
>   dmi.board.name: 0Y4RMT
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 8
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias: dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:
> pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
>   dmi.product.name: Venue 11 Pro 7139
>   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/
> 1745342/+subscriptions
>

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  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:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 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: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

2018-02-13 Thread Jiri Horky

Hi again,

so for the second kernel (), was able to reproduce it in ~same time. The
messages are:

Feb 13 23:04:23 prg41-004 kernel: [  650.285711] unregister_netdevice: waiting 
for lo (netns 943cfe8ce000) to become free. Usage count = 1
Feb 13 23:04:23 prg41-004 kernel: [  650.285736](netns 
943cfe8ce000): dst 943d18ac4200 expires 0 error 0 obsolete 2 flags 0 
refcnt 2 ops ipv4_dst_ops+0x0/0xc0 creator 
ip_route_output_key_hash_rcu+0x355/0xa20

root@prg41-004:~# grep 943d18ac4200 /var/log/syslog
Feb 13 23:02:14 prg41-004 kernel: [  521.458077] dst_init: dst 943d18ac4200 
refcnt 1 from __dst_alloc+0x7e/0x100
Feb 13 23:02:14 prg41-004 kernel: [  521.458085] dst_hold: dst 943d18ac4200 
refcnt 2 from rt_cache_route+0x54/0xe0
Feb 13 23:02:14 prg41-004 kernel: [  521.634088] dst_hold_safe: dst 
943d18ac4200 refcnt 3 from ip_route_output_key_hash_rcu+0x8a1/0xa20
Feb 13 23:02:14 prg41-004 kernel: [  521.778104] dst_release_immediate: dst 
943d18ac4200 refcnt 2 from free_fib_info_rcu+0x146/0x1c0
Feb 13 23:04:23 prg41-004 kernel: [  650.285736](netns 
943cfe8ce000): dst 943d18ac4200 expires 0 error 0 obsolete 2 flags 0 
refcnt 2 ops ipv4_dst_ops+0x0/0xc0 creator 
ip_route_output_key_hash_rcu+0x355/0xa20
Feb 13 23:04:33 prg41-004 kernel: [  660.525715](netns 
943cfe8ce000): dst 943d18ac4200 expires 0 error 0 obsolete 2 flags 0 
refcnt 2 ops ipv4_dst_ops+0x0/0xc0 creator 
ip_route_output_key_hash_rcu+0x355/0xa20
Feb 13 23:04:43 prg41-004 kernel: [  670.669641](netns 
943cfe8ce000): dst 943d18ac4200 expires 0 error 0 obsolete 2 flags 0 
refcnt 2 ops ipv4_dst_ops+0x0/0xc0 creator 
ip_route_output_key_hash_rcu+0x355/0xa20

etc.

I hope it helps!

Regards
Jirka H.

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

2018-02-13 Thread Jiri Horky

Forgot to paste the second kernel version. The previous message was
obtained using 4.13.13-00941-gf382397cf315 kernel (the one with
ipsec/xfrm dst leak patch).

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1696541] Re: orangefs kernel module not compiled for amd64, i386

2018-02-13 Thread James Burton

Yes, enable in all post 4.6 kernel packages.

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

Title:
  orangefs kernel module not compiled for amd64, i386

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

Bug description:
  The OrangeFS kernel module
  (/lib/modules//kernel/fs/orangefs/orangefs.ko) has been
  available as part of the Linux kernel since version 4.6, but has not
  been compiled as part of the ubuntu kernel-image package or any other
  package for the amd64 and i386 architectures. According to Ubuntu
  Package Search, it is being compiled for the arm64, armhf, and powerpc
  architectures.

  This bug report is to add support for OrangeFS by compiling the
  orangefs module and including it with the all kernel packages >= 4.6.
  This can be done by enabling CONFIG_ORANGEFS_FS as a module in the
  kernel config file.

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

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

[Kernel-packages] [Bug 1748505] Re: Boot failed with hard LOCKUP linux-image-4.4.0-112

2018-02-13 Thread Dash

Hello Joseph, fixed in mainline kernel. Thanks for your support.


** Tags added: kernel-fixed-upstream

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

Title:
  Boot failed with hard LOCKUP linux-image-4.4.0-112

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Booting this kernel ended with

  [35.111831] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1
  [36.073026] NMI watchdog: Watchdog detected hard LOCKUP on cpu 2
  [36.153549] NMI watchdog: Watchdog detected hard LOCKUP on cpu 0
  [36.451526] NMI watchdog: Watchdog detected hard LOCKUP on cpu 3 

  Booting previous kernel linux-image-4.4.0-109-generic is working
  smoothly as well as previous ones.

  cat /proc/version_signature = Ubuntu 4.4.0-109.132-generic 4.4.98

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dh 2583 F pulseaudio
   /dev/snd/controlC1:  dh 2583 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb  9 19:02:26 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  HibernationDevice: RESUME=UUID=103ed14e-e6b6-49d5-a28f-020343e6a118
  InstallationDate: Installed on 2013-10-13 (1580 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  MachineType: Dell Inc. Latitude E7440
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=8a01ac20-42e5-49f3-b385-674e05cd8d7c ro quiet splash 
acpi_rev_override=1
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-10-05 (491 days ago)
  dmi.bios.date: 12/15/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A23
  dmi.board.name: 0JNYGR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA23:bd12/15/2017:svnDellInc.:pnLatitudeE7440:pvr00:rvnDellInc.:rn0JNYGR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1735713] Comment bridged from LTC Bugzilla

2018-02-13 Thread bugproxy

--- Comment From bar...@us.ibm.com 2018-02-13 16:52 EDT---
This bug is closed as unreproducible and will be reopened if it occurs again.

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

Title:
  Ubuntu16.04.03: Kernel Oops on targetcli

Status in The Ubuntu-power-systems project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - RAHUL CHANDRAKAR  - 2017-12-01 03:26:31 
==
  ---Problem Description---
  Error while running targetcli command on Ubuntu 16.04
   
  ---uname output---
  Linux alpvm2nova 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:23:01 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8408-44E 
   
  ---System Hang---
   gpfs is stuck because of this
   
  ---Debugger---
  A debugger is not configured
   
  Contact Information = rahch...@in.ibm.com 
   
  Stack trace output:
   [Fri Dec  1 03:05:12 2017] Unable to handle kernel paging request for data 
at address 0x010d0688
  [Fri Dec  1 03:05:12 2017] Faulting instruction address: 0xd7570a30
  [Fri Dec  1 03:05:12 2017] Oops: Kernel access of bad area, sig: 11 [#2]
  [Fri Dec  1 03:05:12 2017] SMP NR_CPUS=2048 NUMA pSeries
  [Fri Dec  1 03:05:12 2017] Modules linked in: hvcs(OE) hvcserver rpadlpar_io 
rpaphp xt_tcpudp xt_nat target_core_pscsi(OE) target_core_file(OE) 
target_core_iblock(OE) target_core_user(OE) uio iscsi_target_mod(OE) mmfs26(OE) 
mmfslinux(OE) tracedev(OE) dccp_diag dccp tcp_diag udp_diag inet_diag unix_diag 
af_packet_diag netlink_diag openvswitch binfmt_misc pseries_rng ibmvmc(OE) 
vmx_crypto rtc_generic xt_conntrack nf_nat_ftp nf_conntrack_ftp 
nf_conntrack_netlink nfnetlink nf_conntrack_netbios_ns nf_conntrack_broadcast 
nf_conntrack_ipv6 nf_defrag_ipv6 nbd br_netfilter bridge ib_iser rdma_cm iw_cm 
ib_cm ib_sa ib_mad ib_core ib_addr vhost_net vhost macvtap macvlan iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi ip_vs libcrc32c iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_mangle iptable_filter
  [Fri Dec  1 03:05:12 2017]  ipt_REJECT nf_reject_ipv4 ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_nat nf_conntrack ip_tables ip6table_filter ip6_tables 
ebtables x_tables dm_snapshot dm_bufio 8021q garp mrp stp llc autofs4 
dm_round_robin ses enclosure scsi_transport_sas be2net ibmvscsis(OE) 
target_core_mod(OE) configfs(OE) ibmveth(OE) lpfc vxlan ip6_udp_tunnel 
udp_tunnel scsi_transport_fc ipr scsi_dh_emc scsi_dh_rdac scsi_dh_alua 
dm_multipath
  [Fri Dec  1 03:05:12 2017] CPU: 13 PID: 178523 Comm: targetcli Tainted: G 
 D W  OE   4.4.0-98-generic #121-Ubuntu
  [Fri Dec  1 03:05:12 2017] task: c007d399cf60 ti: c007e4a84000 
task.ti: c007e4a84000
  [Fri Dec  1 03:05:12 2017] NIP: d7570a30 LR: d75709c4 CTR: 
c016e220
  [Fri Dec  1 03:05:12 2017] REGS: c007e4a87820 TRAP: 0300   Tainted: G 
 D W  OE(4.4.0-98-generic)
  [Fri Dec  1 03:05:12 2017] MSR: 80009033   CR: 
4248  XER: 
  [Fri Dec  1 03:05:12 2017] CFAR: c0008468 DAR: 010d0688 
DSISR: 4000 SOFTE: 1 
 GPR00: d75709c4 c007e4a87aa0 
d757fdf8 0001 
 GPR04: 0240 c007e8739b10 
0001  
 GPR08: 010d0680 d7f61d50 
d757fdf8 d75765f0 
 GPR12: c016e220 cfb47b80 
3fffc86beb50  
 GPR16:  103b7d00 
  
 GPR20: c007d5379aa0 c004d39b5280 
 0024 
 GPR24: c007e8739b00 c004d39b5280 
d7570910 c00516f61d00 
 GPR28: c00518b7e488 c007a6367810 
c007e8739b00 d7f6db50 
  [Fri Dec  1 03:05:12 2017] NIP [d7570a30] 
configfs_open_file+0x120/0x260 [configfs]
  [Fri Dec  1 03:05:12 2017] LR [d75709c4] 
configfs_open_file+0xb4/0x260 [configfs]
  [Fri Dec  1 03:05:12 2017] Call Trace:
  [Fri Dec  1 03:05:12 2017] [c007e4a87aa0] [d75709c4] 
configfs_open_file+0xb4/0x260 [configfs] (unreliable)
  [Fri Dec  1 03:05:12 2017] [c007e4a87af0] [c02e2d40] 
do_dentry_open+0x2c0/0x460
  [Fri Dec  1 03:05:12 2017] [c007e4a87b50] [c02fb388] 
do_last+0x178/0xff0
  [Fri Dec  1 03:05:12 2017] [c007e4a87c10] [c02fc41c] 
path_openat+0xcc/0x3c0
  [Fri Dec  1 03:05:12 2017] [c007e4a87c90] [c02fe33c] 
do_filp_open+0xfc/0x170
  [Fri Dec  1 03:05:12 2017] [c007e4a87db0] [c02e4b30] 
do_sys_open+0x1c0/0x3b0
  [Fri Dec  1 03:05:12 2017] [c007e4a87e30] [c0009204] 
system_call+0x38/0xb4
  [Fri Dec  1

[Kernel-packages] [Bug 1749207] Re: kernel is reporting Nintendo USB microphone as an output device

Tested 4.16.0-041600rc1-generic but the problem persists


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

** Tags removed: amd64 apport-bug bionic
** Tags added: kernel-bug-exists-upstream

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

Title:
  kernel is reporting Nintendo USB microphone as an output device

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel is reporting Nintendo USB microphone as an output device.And
  because that alsa will use every time as a output device

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  a  1438 F pulseaudio
   /dev/snd/controlC0:  a  1438 F pulseaudio
   /dev/snd/controlC1:  a  1438 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 13 16:48:49 2018
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180212)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e1fa3a67-c257-4f26-b6fc-b72b872c2370 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: A88M-G/3.1
  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.40:bd05/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA88M-G/3.1: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.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/1749207/+subscriptions

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

2018-02-13 Thread Jiri Horky

Hi Dan,

so for the first kernel (linux-
image-4.13.13-00940-gf16e2bbbddee_4.13.13-00940-gf16e2bbbddee-
24_amd64.deb), it failed after some 10 minutes. The outputs are:

Feb 13 22:35:54 prg41-004 kernel: [  736.399342] unregister_netdevice: waiting 
for lo (netns 9adbfbebb000) to become free. Usage count = 1
Feb 13 22:35:54 prg41-004 kernel: [  736.399376](netns 
9adbfbebb000): dst 9ae3fee51f00 expires 0 error 0 obsolete 2 flags 0 
refcnt 2 ops ipv4_dst_ops+0x0/0xc0 creator 
ip_route_output_key_hash_rcu+0x355/0xa20

And then:
root@prg41-004:~# grep 9ae3fee51f00 /var/log/syslog
Feb 13 22:33:33 prg41-004 kernel: [  595.493003] dst_init: dst 9ae3fee51f00 
refcnt 1 from __dst_alloc+0x7e/0x100
Feb 13 22:33:33 prg41-004 kernel: [  595.493009] dst_hold: dst 9ae3fee51f00 
refcnt 2 from rt_cache_route+0x54/0xe0
Feb 13 22:33:33 prg41-004 kernel: [  595.648996] dst_hold_safe: dst 
9ae3fee51f00 refcnt 3 from ip_route_output_key_hash_rcu+0x8a1/0xa20
Feb 13 22:33:33 prg41-004 kernel: [  595.689067] dst_release_immediate: dst 
9ae3fee51f00 refcnt 2 from free_fib_info_rcu+0x146/0x1c0
Feb 13 22:35:54 prg41-004 kernel: [  736.399376](netns 
9adbfbebb000): dst 9ae3fee51f00 expires 0 error 0 obsolete 2 flags 0 
refcnt 2 ops ipv4_dst_ops+0x0/0xc0 creator 
ip_route_output_key_hash_rcu+0x355/0xa20
Feb 13 22:36:04 prg41-004 kernel: [  746.447322](netns 
9adbfbebb000): dst 9ae3fee51f00 expires 0 error 0 obsolete 2 flags 0 
refcnt 2 ops ipv4_dst_ops+0x0/0xc0 creator 
ip_route_output_key_hash_rcu+0x355/0xa20
Feb 13 22:36:14 prg41-004 kernel: [  756.527237](netns 
9adbfbebb000): dst 9ae3fee51f00 expires 0 error 0 obsolete 2 flags 0 
refcnt 2 ops ipv4_dst_ops+0x0/0xc0 creator 
ip_route_output_key_hash_rcu+0x355/0xa20
Feb 13 22:36:24 prg41-004 kernel: [  766.639159](netns 
9adbfbebb000): dst 9ae3fee51f00 expires 0 error 0 obsolete 2 flags 0 
refcnt 2 ops ipv4_dst_ops+0x0/0xc0 creator 
ip_route_output_key_hash_rcu+0x355/0xa20
Feb 13 22:36:34 prg41-004 kernel: [  776.815056](netns 
9adbfbebb000): dst 9ae3fee51f00 expires 0 error 0 obsolete 2 flags 0 
refcnt 2 ops ipv4_dst_ops+0x0/0xc0 creator 
ip_route_output_key_hash_rcu+0x355/0xa20
Feb 13 22:36:45 prg41-004 kernel: [  786.958967](netns 
9adbfbebb000): dst 9ae3fee51f00 expires 0 error 0 obsolete 2 flags 0 
refcnt 2 ops ipv4_dst_ops+0x0/0xc0 creator 
ip_route_output_key_hash_rcu+0x355/0xa20
Feb 13 22:36:55 prg41-004 kernel: [  797.070875](netns 
9adbfbebb000): dst 9ae3fee51f00 expires 0 error 0 obsolete 2 flags 0 
refcnt 2 ops ipv4_dst_ops+0x0/0xc0 creator 
ip_route_output_key_hash_rcu+0x355/0xa20

(and obviously more of such messages every 10 seconds)

BTW from the timing it seems that the docker image who produced this
error might be interrupted with timeout (normally, the dockers images we
run on the machine live for few seconds only).

Will post the second kernel soon.

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1746970] Re: lpfc.ko module doesn't work

I built a test kernel with commit 2877cbffb79.  The test kernel can be 
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1746970

Can you test this kernel and see if it resolves this bug?

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!

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

Title:
  lpfc.ko module doesn't work

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Hi.

  I have problem with HBA Emulex LPe12000 Fibre channel adapter. It
  doesn't see disk on direct attach.

  [4.015493] lpfc :04:00.0: 0:1303 Link Up Event x1 received Data: x1 
x1 x10 x2 x0 x0 0
  [4.015570] lpfc :04:00.0: 0:1309 Link Up Event npiv not supported in 
loop topology
  [4.016671] lpfc :04:00.0: 0:(0):2858 FLOGI failure Status:x3/x18 
TMO:x0 Data x1000 x0
  [4.017627] lpfc :04:00.0: 0:(0):2858 FLOGI failure Status:x3/x18 
TMO:x0 Data x1000 x0
  [4.018561] lpfc :04:00.0: 0:(0):2858 FLOGI failure Status:x3/x18 
TMO:x0 Data x1000 x0
  [4.018636] lpfc :04:00.0: 0:(0):0100 FLOGI failure Status:x3/x18 
TMO:x0
  [4.019713] lpfc :04:00.0: 0:(0):0266 Issue NameServer Req x117 err 1 
Data: x8 x0

  I have made a little investigation.

  Ubuntu 16.04.3 LTS, kernel 4.10.0-28, lpfc 11.2.0.2 - no problem.
  Ubuntu 17.10.1, kernel 4.13.0-21, lpfc 11.4.0.1 - problem.
  Debian 9.3, kernel 4.9.0-4, lpfc 11.2.0.0 - no problem.
  Fedora 27, kernel 4.13.9-300, lpfc 11.4.0.1 - problem.
  Proxmox 5.0, kernel 4.10.15-1, lpfc 11.2.0.2 - no problem.
  Proxmox 5.1, kernel 4.13.13-5, lpfc 11.4.0.1 - problem.

  Another user with this problem said that if fiber switch is added
  between the server and the storage it's working as expected.

  I think problem is in lpfc.ko 11.4.0.1. Any kernel (4.13 now) that has
  this module version is affected. Broadcom support confirmed that bug
  and suggested to update module. But Broadcom supports only RHEL and
  SLES. I tried to compile, but no luck. Please, could you update
  lpfc.ko module in linux-image-generic package?

  There are version 11.4.142.21 for SLES 12 and 11.4.204.11 for RHEL 6
  and 7 on Broadcom site.

  Thanks.

  ---

  04:00.0 Fibre Channel [0c04]: Emulex Corporation Saturn-X: LightPulse Fibre 
Channel Host Adapter [10df:f100] (rev 03)
Subsystem: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host 
Adapter [10df:f100]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel modules: lpfc
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP ProLiant DL160 G6
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=ru 
keyboard-configuration/layoutcode?=ru
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  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.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/19/2010
  dmi.bios.vendor: HP
  dmi.bios.version: O33
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrO33:bd05/19/2010:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL160 G6
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1677319] Re: Support low-pin-count devices on Hisilicon SoCs

2018-02-13 Thread dann frazier

** Also affects: linux (Ubuntu Bionic)
   Importance: High
 Assignee: dann frazier (dannf)
   Status: Fix Released

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

** Changed in: linux (Ubuntu Bionic)
   Status: Fix Released => Triaged

** Changed in: linux (Ubuntu Artful)
   Status: New => Fix Released

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

Title:
  Support low-pin-count devices on Hisilicon SoCs

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Triaged

Bug description:
  [Impact]
  The HiSilicon Hip06/Hip07 SoCs include a low-pin-count (LPC) host controller. 
The Linux kernel needs support for this interface to use attached devices, such 
as a UART and the IPMI system interface.

  [Test Case]
  Boot up a HiSilicon D05 system, confirm that the following command returns 
w/o error:

  $ sudo ipmitool lan print

  [Regression Risk]
  The proposed patchset only enables LIBIO for arm64, so the greatest 
regression risk is to other arm64 systems. We have mitigated that by testing on 
a wide range of hardware (all certified arm64 servers + some in-devel systems). 
There remains some arch-independent changes to the generic PCI code. The patch 
"PCI: Restore codepath for !CONFIG_LIBIO" was added to mitigate the risk to 
other architectures by restoring the previous code for those architectures.

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

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

[Kernel-packages] [Bug 1748979] Re: When playing a video, the whole screen will freeze (incl. Ubuntu itself) until the video is done playing

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/

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

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

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

Title:
  When playing a video, the whole screen will freeze (incl. Ubuntu
  itself) until the video is done playing

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With some videos, it freezes VLC (windowed) and the whole computer. I
  can still hear the sound playing, and the computer operates normally
  again after the video is done playing.

  While it's frozen, I can't move the mouse, none of the hotkeys work
  (ctrl alt t, alt tab, etc), and none of the screen updates. Even the
  vol up/down keys on my Thinkpad don't do anything anymore.

  Once the video is done playing in VLC, everything is back to normal.

  It doesn't always happen with the same video, and it's not always at
  the same point in the video.

  Description:  Ubuntu 17.10
  Release:  17.10

  vlc:
Installed: 2.2.6-6
Candidate: 2.2.6-6
Version table:
   *** 2.2.6-6 500
  500 http://ca.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   coaxial6258 F...m pulseaudio
   /dev/snd/controlC0:  coaxial6258 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 12 14:56:28 2018
  HibernationDevice: RESUME=UUID=7d31-ad44-46d0-bfcc-dba92785b74e
  InstallationDate: Installed on 2017-05-15 (273 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 23243YU
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-27 (108 days ago)
  dmi.bios.date: 10/08/2017
  dmi.bios.vendor: coreboot
  dmi.bios.version: CBET4000 4.6-1715-gef1a5ede6c
  dmi.board.name: 23243YU
  dmi.board.vendor: LENOVO
  dmi.board.version: ThinkPad X230
  dmi.chassis.type: 9
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvncoreboot:bvrCBET40004.6-1715-gef1a5ede6c:bd10/08/2017:svnLENOVO:pn23243YU:pvrThinkPadX230:rvnLENOVO:rn23243YU:rvrThinkPadX230:cvnLENOVO:ct9:cvr:
  dmi.product.name: 23243YU
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1748936] Re: kASLR: unable to boot Linux v4.4.0-113.136 - v4.4.0-115.139 kernels ("Spectre & Meltdown" patches.)

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

** Tags added: pti

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

Title:
  kASLR: unable to boot Linux v4.4.0-113.136 - v4.4.0-115.139 kernels
  ("Spectre & Meltdown" patches.)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello.

  It seems, that 'kaslr' option is responsible for issues with system
  booting. The latest working kernel is v4.4.0-112.135. Every next
  release: v4.4.0-113.136 and v4.4.0-115.139 are unable to boot if
  'kaslr' option is in use etc. Everything is described in my previous
  bug report (please see 1.), but I've decided to create a new one,
  because it seems, that some of the "Spectre & Meltdown" patches are
  not compatible with kASLR and are responsible for this regressions.

  Thanks, best regards.

  [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748710

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

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

[Kernel-packages] [Bug 1749089] Re: linux: 4.4.0-116.140 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.4.0-116.140 -proposed tracker

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

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

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

  backports: bug 1749090 (linux-aws), bug 1749091 (linux-lts-xenial)
  derivatives: bug 1749092 (linux-kvm), bug 1749093 (linux-aws), bug 1749094 
(linux-raspi2), bug 1749095 (linux-euclid), bug 1749096 (linux-snapdragon), bug 
1749097 (linux-gke)
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1749089/+subscriptions

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

[Kernel-packages] [Bug 1748988] Re: Random total system freezes (resolved)

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

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

Title:
  Random total system freezes (resolved)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an Intel 7260 WiFi card in my desktop (lspci output: 09:00.0
  Network controller: Intel Corporation Wireless 7260 (rev bb)), running
  18.04. All the way since 17.04 I have experienced random freezes,
  where the entire system would be unresponsive, I was unable to
  Ctrl+Alt+F1 to a different console, and I couldn't connect to it via
  ssh. After upgrading to 17.10 (and a fresh install of 17.10), and
  subsequently upgrading to 18.04, the issue intensified, appearing at
  least hourly, often quicker than that, and only a hard reset would let
  me access my system again. The issue is also present in Linux Mint
  18.3. Freezes could happen at any time, regardless of usage (or just
  idling).

  After getting a tip that this might be caused by the WiFi card, I
  looked at the provided firmware from Intel's site, and compared the
  files to the files present in /lib/firmware/. The file provided by
  Intel for my specific card is iwlwifi-7260-14.ucode, but the files
  present in the folder were the numbers 7, 8, 9, 10, 12, 13, 16, and
  17. Downloading the firmware from Intel, and adding the -14 file to
  the folder solved the issue of the screen freezing, and the issue has
  not appeared for the ten hours I've been running since applying the
  fix.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sten   2687 F pulseaudio
   /dev/snd/controlC1:  sten   2687 F pulseaudio
  CurrentDesktop: KDE
  Date: Mon Feb 12 21:18:57 2018
  HibernationDevice: RESUME=UUID=96fd0755-bbbc-43ce-9174-b4de65ea2e26
  InstallationDate: Installed on 2017-10-27 (107 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=b3449b90-a2aa-4c46-8837-574f25841071 ro quiet splash 
intel_idle.max_cstate=1 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-02-05 (7 days ago)
  dmi.bios.date: 01/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3803
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B350-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3803:bd01/22/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1748988/+subscriptions

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

[Kernel-packages] [Bug 1749093] Re: linux-aws: 4.4.0-1052.61 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1749089
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1749093/+subscriptions

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

[Kernel-packages] [Bug 1748380] Re: [Notebook W65_67SF] hibernate/resume failure

2018-02-13 Thread Jhonny Oliveira

I tested it, but the problem persists.

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

Title:
  [Notebook W65_67SF] hibernate/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  .

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1443 F pulseaudio
jwp1996 F pulseaudio
   /dev/snd/controlC1:  gdm1443 F pulseaudio
jwp1996 F pulseaudio
  Date: Fri Feb  9 08:11:57 2018
  DuplicateSignature: hibernate/resume:Notebook W65_67SF:1.05.01
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=2f57605b-1746-435c-a0af-9242a675f7e8
  InstallationDate: Installed on 2018-02-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
  InterpreterPath: /usr/bin/python3.6
  MachineType: Notebook W65_67SF
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  Title: [Notebook W65_67SF] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.01
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SF
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.01:bd07/24/2015:svnNotebook:pnW65_67SF:pvrNotApplicable:rvnNotebook:rnW65_67SF:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W65_67SF
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Kernel-packages] [Bug 1748520] Re: SDXC card reader not recognized

2018-02-13 Thread Wolf Rogner

I have tried this in advance.
The new kernel does not fix this issue.
How do I add the tag?

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

Title:
  SDXC card reader not recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Macbook Pro 13" Retina (MacbookPro12,1 mid 2015) the SDXC card slot
  is non-responsive.

  uname -a
  Linux mbpr13b 4.13.0-33-generic #36-Ubuntu SMP Tue Feb 6 20:30:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Installing sdhci and sdhci-pci modules (with or without adding a
  /etc/modprobe.d/sdhci.conf to configure option debug_quirks2) does not
  work.

  After a reboot, the drivers are not installed.
  A device /dev/mmcblk0 is missing.

  This used to be different in previous kernels 4.13... (although I have
  no record when last I tested).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-33-generic 4.13.0-33.36
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1055 F pulseaudio
wolf   1399 F pulseaudio
   /dev/snd/controlC0:  gdm1055 F pulseaudio
wolf   1399 F pulseaudio
  Date: Fri Feb  9 20:25:21 2018
  HibernationDevice: RESUME=UUID=e0d91223-651f-43b1-bb25-12794e7155d4
  InstallationDate: Installed on 2017-10-20 (112 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 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  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.13.0-33-generic N/A
   linux-backports-modules-4.13.0-33-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1749221] Re: kernel crash / BUG: unable to handle kernel paging request at fffffe3ed8000020

2018-02-13 Thread Scott Moser

It happens within 3 minutes of system boot into 4.13 kernel.
2 systems reproduced this.  You're lucky to be able to log in before it crashes.

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

Title:
   kernel crash / BUG: unable to handle kernel paging request at
  fe3ed820

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

Bug description:
  Booted under maas in rescue mode system console has the attached failure.
  First bit is

  [ 440.196466] BUG: unable to handle kernel paging request at
  fe3ed820

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic (not installed)
  ProcVersionSignature: User Name 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116, 33 Feb 13 15:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed 
with exit code 1:
  CRDA: N/A
  Date: Tue Feb 13 15:34:40 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=username/amd64/generic/xenial/daily/boot-kernel 
nomodeset 
root=squash:http://10.247.16.6:5248/images/username/amd64/generic/xenial/daily/squashfs
 ro ip=hostname:BOOTIF ip6=off overlayroot=tmpfs 
overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc 
cloud-config-url=http://10.247.16.6:5240/MAAS/metadata/latest/by-id/sbgyxn/?op=get_preseed
 apparmor=0 log_host=10.247.16.6 log_port=514 --- console=ttyS1 
BOOTIF=01-ec:b1:d7:7f:2a:6c
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd03/05/2015:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

2018-02-13 Thread redx

I have tested the patch and the touch is detected correctly, but if I
detach and then reattach the dock keyboard, the keyboard stops working
until i reboot the tablet.

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  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:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 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: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  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/1745342/+subscriptions

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

[Kernel-packages] [Bug 1748669] Re: New kernel update cause seriouse video problems.

** Changed in: linux (Ubuntu)
 Assignee: Várkuli Miklós Gábor (e3c15) => (unassigned)

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

Title:
  New kernel update cause seriouse video problems.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Test machine:

  Asus   Eee PC 1000H
  CPU:   Intel Atom N270 1,6 GHz
  Video: Intel GMA950

  no proprietary drivers in use

  Last stable kernel without the error: 4.4.0-112  
  System: current Xubuntu 16.04 LTSpreviously Lubuntu 16.4 LTS 

  After this kernel was updated 4/5 of the desktop disappear or filled
  with random pixels and only a small portion is rendered normally. This
  problem is not occuring when switching back to the older kerrnel
  mentioned above. I tried this with fresh install and with old install
  upgraded. Results were the same. I can't provide data from the faulty
  state since I can't see enough from the desktop to send or even start
  a report. The current bug report is from the properly working, stable
  system .

  Lubuntu, debian and xubuntu is making the same error after kernel
  update. We have 2 stronger notebook an asus and a fujitsu siemens
  business class. They both using proprietary drivers: Nvidia and Intel
  microcode and the error doesn't occured there. I didn't tried to
  switch back to free drivers. They both use lubuntu 16.04 LTS with
  newest kernel and drivers.

  Thanks for your help and the great operating system you all created.
  Sincerely. Miklós Várkuli.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Sat Feb 10 21:03:44 2018
  ProcEnviron:
   LANGUAGE=hu
   TERM=xterm
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1748903] Re: linux 4.13.0-32 version freezes screen before end of boot for X60 lenovo laptop

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/

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

** Tags added: needs-bisect

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

Title:
  linux 4.13.0-32 version freezes screen before end of boot for X60
  lenovo laptop

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ubuntu 16.04.3 on x60 lenovo laptop

  previous version of linux 4.10.0-42 works without problems.
  as well older versions linux 4.10.0-38 works without problems.
  even the 4.4.0-96 works without problems.

  at linux 4.13.0-32 the display freezes with 2 top lines fixed.
  however the login greeter still works, you can even login. but you 
  cannot see anything you typed. alt-ctrl-f1 will work. and you can
  see the display working again, however the top 2 lines remain fixed.
  you can do ls and clear, etc. however no gui display. 
  i only installed the linux-*4.13.0-32 packages and it freezes the
  display when you reboot. 7 packages in all. 

  hope you guys fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Feb 12 22:05:17 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1748669] Re: New kernel update cause seriouse video problems.

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/

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

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

Title:
  New kernel update cause seriouse video problems.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Test machine:

  Asus   Eee PC 1000H
  CPU:   Intel Atom N270 1,6 GHz
  Video: Intel GMA950

  no proprietary drivers in use

  Last stable kernel without the error: 4.4.0-112  
  System: current Xubuntu 16.04 LTSpreviously Lubuntu 16.4 LTS 

  After this kernel was updated 4/5 of the desktop disappear or filled
  with random pixels and only a small portion is rendered normally. This
  problem is not occuring when switching back to the older kerrnel
  mentioned above. I tried this with fresh install and with old install
  upgraded. Results were the same. I can't provide data from the faulty
  state since I can't see enough from the desktop to send or even start
  a report. The current bug report is from the properly working, stable
  system .

  Lubuntu, debian and xubuntu is making the same error after kernel
  update. We have 2 stronger notebook an asus and a fujitsu siemens
  business class. They both using proprietary drivers: Nvidia and Intel
  microcode and the error doesn't occured there. I didn't tried to
  switch back to free drivers. They both use lubuntu 16.04 LTS with
  newest kernel and drivers.

  Thanks for your help and the great operating system you all created.
  Sincerely. Miklós Várkuli.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Sat Feb 10 21:03:44 2018
  ProcEnviron:
   LANGUAGE=hu
   TERM=xterm
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1749015] Re: 4.16 - VBOXGUEST not built

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

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
   Status: Triaged

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

Title:
  4.16 - VBOXGUEST not built

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

Bug description:
  Reporting by recommendation by apw on #ubuntu-kernel

  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/ refers to
  0006-configs-based-on-Ubuntu-4.15.0-9.10.patch which, at line 1771 has

  +# CONFIG_VBOXGUEST is not set

  I am not in any position to demand a rebuild ahead of next upstream
  RC, but I *was* looking forward to the support.

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

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

[Kernel-packages] [Bug 1746970] Re: lpfc.ko module doesn't work

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

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

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

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

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  lpfc.ko module doesn't work

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Hi.

  I have problem with HBA Emulex LPe12000 Fibre channel adapter. It
  doesn't see disk on direct attach.

  [4.015493] lpfc :04:00.0: 0:1303 Link Up Event x1 received Data: x1 
x1 x10 x2 x0 x0 0
  [4.015570] lpfc :04:00.0: 0:1309 Link Up Event npiv not supported in 
loop topology
  [4.016671] lpfc :04:00.0: 0:(0):2858 FLOGI failure Status:x3/x18 
TMO:x0 Data x1000 x0
  [4.017627] lpfc :04:00.0: 0:(0):2858 FLOGI failure Status:x3/x18 
TMO:x0 Data x1000 x0
  [4.018561] lpfc :04:00.0: 0:(0):2858 FLOGI failure Status:x3/x18 
TMO:x0 Data x1000 x0
  [4.018636] lpfc :04:00.0: 0:(0):0100 FLOGI failure Status:x3/x18 
TMO:x0
  [4.019713] lpfc :04:00.0: 0:(0):0266 Issue NameServer Req x117 err 1 
Data: x8 x0

  I have made a little investigation.

  Ubuntu 16.04.3 LTS, kernel 4.10.0-28, lpfc 11.2.0.2 - no problem.
  Ubuntu 17.10.1, kernel 4.13.0-21, lpfc 11.4.0.1 - problem.
  Debian 9.3, kernel 4.9.0-4, lpfc 11.2.0.0 - no problem.
  Fedora 27, kernel 4.13.9-300, lpfc 11.4.0.1 - problem.
  Proxmox 5.0, kernel 4.10.15-1, lpfc 11.2.0.2 - no problem.
  Proxmox 5.1, kernel 4.13.13-5, lpfc 11.4.0.1 - problem.

  Another user with this problem said that if fiber switch is added
  between the server and the storage it's working as expected.

  I think problem is in lpfc.ko 11.4.0.1. Any kernel (4.13 now) that has
  this module version is affected. Broadcom support confirmed that bug
  and suggested to update module. But Broadcom supports only RHEL and
  SLES. I tried to compile, but no luck. Please, could you update
  lpfc.ko module in linux-image-generic package?

  There are version 11.4.142.21 for SLES 12 and 11.4.204.11 for RHEL 6
  and 7 on Broadcom site.

  Thanks.

  ---

  04:00.0 Fibre Channel [0c04]: Emulex Corporation Saturn-X: LightPulse Fibre 
Channel Host Adapter [10df:f100] (rev 03)
Subsystem: Emulex Corporation Saturn-X: LightPulse Fibre Channel Host 
Adapter [10df:f100]
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel modules: lpfc
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.387
  DistroRelease: Ubuntu 17.10
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP ProLiant DL160 G6
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=ru 
keyboard-configuration/layoutcode?=ru
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  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.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   
  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/19/2010
  dmi.bios.vendor: HP
  dmi.bios.version: O33
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrO33:bd05/19/2010:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr:
  dmi.product.name: ProLiant DL160 G6
  dmi.sys.vendor: HP

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

-- 
Mailing list:

[Kernel-packages] [Bug 1749214] Re: default vers value when mounting cifs shares with mount.cifs not working

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/


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

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

** Tags added: needs-bisect

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

Title:
  default vers value when mounting cifs shares with mount.cifs not
  working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Firstly, apologies if this isn't a bug in cifs.mount - I know it's
  intimitly connected to a recent kernel updates which changed the
  default SMB version cifs connects with, but I'm having trouble
  distinguishing whether this behaviour is caused by the kernel change
  or a problem with cifs.

  On a recently built 16.04.3 LTS box with kernel 4.4.0-109, I was able
  to mount to a network DFS share with the following

  mount.cifs -o user=username //pathto/share /mountpoint

  and after doing so, I was able to navigate through the mounted share,
  and through the underlying DFS structure with no problems.  The mount
  command notably contained 'vers=1.0' - which was expected.

  After updating the kernel to 4.13.0.32, if I run the same command, the
  share appears to mount, but I get a 'cannot access ...: Input/Output
  error' when trying to move through a DFS mount within the mounted
  filesystem.

  Notably, the output from the mount command has 'vers=default'.

  I understand from various sources, that the default SMB vers is now
  3.0 - and if I mount this share explicitly with

  mount.cifs -o user=username,vers=3.0 //pathto/share /mountpoint

  Then I see 'vers=3' on the output from mount, and am able to use the
  share as expected.

  The man page for the cifs.mount cmd still says the default is SMB1.0
  (this appeared to be the case with a kernel previous to 4.13).  The
  kernel sources now say the default is SMB 3.0 - which would also be
  find, if the share is mounted with vers=3.0.

  But instead I'm seeing 'vers=default' - and I'm unsure as to what
  version of SMB it's actually trying to use (if any) - whatever it is,
  it doesn't work unless I explicitly set vers=3.0.

  Thanks
  Dave
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 13 12:02 seq
   crw-rw 1 root audio 116, 33 Feb 13 12:02 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=4d912473-ae08-4591-886b-eff2cb5edfd9
  InstallationDate: Installed on 2017-07-11 (217 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d702a195-430c-4bf2-9753-6618837863dc ro
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.15
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: oracle
  _MarkForUpload: True
  dmi.bios.date: 04/05/2016
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/05/2016:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about

[Kernel-packages] [Bug 1749058] Re: incorrect source address in IGMP Membership Report messages

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/


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

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

** Tags added: kernel-da-key

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

Title:
  incorrect source address in IGMP Membership Report messages

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I found that linux kernel had had a bug in the implementation of IGMP
  membership report packet generation. the RFC documents for IGMP version 2
  and 3 says that you must ignore the reports with a source ip address that
  you can't identify as belonging to a network assigned to the interface on
  which the packet was received. and the networking OS in the ToR switch,
  Force10 OS 9 does ignore it.

  I've also figured out a patch has been made for this bug in Linus's Github.
  and there was a mark on Github that reads "v4.16-rc1". (
  
https://github.com/torvalds/linux/commit/a46182b00290839fa3fa159d54fd3237bd8669f0
   )

  I honestly have no idea how Ubuntu LTS team works with regard to this kind
  of patches from the fresh new upstream version of linux kernel. hope you
  guys will easily fix it for people like me who has no experience at
  building and distributing custom built kernels over a few servers.

  Test environment:
  I used two ToR switches and one linux machine for this test.
  I only used 2 ethernet ports on the linux machine.
  There was a recent version of Ubuntu with HWE kernel. I'm not sure if
  no-HWE one would be the same case - the version of linux-generic-hwe-16.04
  was 4.13.0.32.52 -
  To test networking router stuff, I used the quagga from Cumulus Routing on
  the Host 3.3.2 (
  
https://cumulusnetworks.com/products/cumulus-routing-on-the-host/#roh-download-section
   )

  What I did and saw in my case:
  1. set a network interface (A) so it gets an IPv4 address, but also in vain
  issue "ip link set ${if_name} multicast off"
  2. assign an IPv4 address to another network interface (B), but in this
  case with a 31-bit-long subnet mask length.
  3. install quagga from cumulus, launch zebra and pimd, issue "ip pim sm" in
  the interface configuration mode for the interface (B) with a 31-bit-long
  subnet mask length
  4. I checked that the source IP address part of the IGMP membership report
  packets from the linux machine is the address I assigned to the network
  interface (A) with 27-bit-long subnet mask -using dumpcap and tshark-, and
  that the PIM service on the switch ignored the Reports printing debugging
  messages including : "Invalid sender address"

   affects ubuntu

  Regards,
  Gunwoo
  -- 
  You can find my PGP public key here: https://google.com/+DewrKim/about

  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb 12 15:36 seq
   crw-rw 1 root audio 116, 33 Feb 12 15:36 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/peta--0001--01--vg-swap_1
  InstallationDate: Installed on 2017-07-05 (223 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: HP ProLiant DL360 G6
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=/dev/mapper/peta--0001--01--vg-root ro 
isolcpus=4,8,12,16,20,24,28,6,10,14,18,22,26,30 hugepagesz=1G hugepages=0 
hugepagesz=2M hugepages=2048
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.13.0-32-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh

[Kernel-packages] [Bug 1749143] Re: BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad address

Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.115


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

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

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

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

** Tags added: performing-bisect

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

Title:
  BUG: unable to use fping: 127.0.0.1: error while sending ping: Bad
  address

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

Bug description:
  Hello,

  We test the -proposed packages before our ±25000 user servers get a
  chance to download it when it's in stable and we have an issue since
  the package linux-image-4.4.0-113-generic and linux-
  image-4.4.0-115-generic.

  We tried on KVM virtual machines

  To reproduce the problem, execute:

  # fping -t50 -r2 127.0.0.1
  127.0.0.1: error while sending ping: Bad address
  127.0.0.1: error while sending ping: Bad address
  127.0.0.1: error while sending ping: Bad address
  127.0.0.1 is unreachable

  We have no problem with ping:

  # ping -c 1 127.0.0.1
  PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
  64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.046 ms
  
  --- 127.0.0.1 ping statistics ---
  1 packets transmitted, 1 received, 0% packet loss, time 0ms
  rtt min/avg/max/mdev = 0.046/0.046/0.046/0.000 ms

  fping is working fine under kernel 4.4.0-112:

  # fping -t50 -r2 127.0.0.1
  127.0.0.1 is alive

  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 févr. 13 16:40 seq
   crw-rw 1 root audio 116, 33 févr. 13 16:40 timer
  AplayDevices: Error: [Errno 2] Aucun fichier ou dossier de ce type
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] Aucun fichier ou dossier de ce type
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/eolebase--vg-swap_1
  IwConfig: Error: [Errno 2] Aucun fichier ou dossier de ce type
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-115-generic 
root=/dev/mapper/hostname--vg-root ro rootdelay=90
  ProcVersionSignature: Ubuntu 4.4.0-115.139-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-115-generic N/A
   linux-backports-modules-4.4.0-115-generic  N/A
   linux-firmware 1.157.16
  RfKill: Error: [Errno 2] Aucun fichier ou dossier de ce type
  Tags:  xenial
  Uname: Linux 4.4.0-115-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1749207] Re: kernel is reporting Nintendo USB microphone as an output device

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/


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

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

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

Title:
  kernel is reporting Nintendo USB microphone as an output device

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kernel is reporting Nintendo USB microphone as an output device.And
  because that alsa will use every time as a output device

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  a  1438 F pulseaudio
   /dev/snd/controlC0:  a  1438 F pulseaudio
   /dev/snd/controlC1:  a  1438 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb 13 16:48:49 2018
  InstallationDate: Installed on 2018-02-12 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180212)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=e1fa3a67-c257-4f26-b6fc-b72b872c2370 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: A88M-G/3.1
  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.40:bd05/05/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA88M-G/3.1: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.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/1749207/+subscriptions

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

[Kernel-packages] [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking

2018-02-13 Thread Bug Watch Updater

** Changed in: systemd (Debian)
   Status: Unknown => 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/1436945

Title:
  devel: consider fq_codel as the default qdisc for networking

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  New

Bug description:
  This was raised on the kernel-team@ mailing list, we should look at
  this if other distros are starting to move.

  ===

  Date: Tue, 24 Mar 2015 10:54:37 -0700 
 
  From: Dave Taht  
 
  To: Joseph Salisbury  
 
  Cc: Kernel Team , ubuntu-de...@lists.ubuntu.com 
 
  Subject: Re: Minutes from the Ubuntu Kernel Team meeting, 2015-03-24  
 

 
  I must confess I had hoped ubuntu would adopt fq_codel as the default 
 
  qdisc in this go-around. It is still not quite part of fedora´s   
 
  default either, but is now in arch, (and nearly everyone else 
 
  downstream from systemd), and has long been the default in openwrt,   
 
  and at this point, just requires a single sysctl to enable.   
 

 
  It certainly could use more widespread testing, perhaps in the next release?  
 

 
  d@nuc-client:~$ cat /etc/sysctl.d/10-bufferbloat.conf 
 
  net.core.default_qdisc=fq_codel

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

** Attachment added: "/sys/firmware/acpi/tables/DSDT for 7140"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+attachment/5054509/+files/DSDT.7140.feuille

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  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:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 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: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  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/1745342/+subscriptions

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

[Kernel-packages] [Bug 1748901] Re: System hang with Virtualbox & kernel 4.13.0-32-generic

2018-02-13 Thread Rod Smith

Joseph, I'm having problems doing that because of the VirtualBox kernel
modules, which don't want to compile for the 4.16 kernel. Here's what I
get why I try to re-install dkms and virtualbox-dkms:

$ sudo apt-get install dkms virtualbox-dkms
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-4.13.0-26 linux-headers-4.13.0-26-generic
  linux-image-4.13.0-26-generic linux-image-extra-4.13.0-26-generic
  linux-signed-image-4.13.0-26-generic
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
  dkms virtualbox-dkms
0 upgraded, 2 newly installed, 0 to remove and 11 not upgraded.
Need to get 690 kB of archives.
After this operation, 5,319 kB of additional disk space will be used.
Get:1 http://nessus.rodsbooks.com/ubuntu xenial-updates/main amd64 dkms all 
2.2.0.3-2ubuntu11.5 [66.3 kB]
Get:2 http://nessus.rodsbooks.com/ubuntu xenial-updates/multiverse amd64 
virtualbox-dkms all 5.0.40-dfsg-0ubuntu1.16.04.2 [624 kB]
Fetched 690 kB in 0s (1,499 kB/s)
Selecting previously unselected package dkms.
(Reading database ... 550655 files and directories currently installed.)
Preparing to unpack .../dkms_2.2.0.3-2ubuntu11.5_all.deb ...
Unpacking dkms (2.2.0.3-2ubuntu11.5) ...
Selecting previously unselected package virtualbox-dkms.
Preparing to unpack .../virtualbox-dkms_5.0.40-dfsg-0ubuntu1.16.04.2_all.deb ...
Unpacking virtualbox-dkms (5.0.40-dfsg-0ubuntu1.16.04.2) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up dkms (2.2.0.3-2ubuntu11.5) ...
Setting up virtualbox-dkms (5.0.40-dfsg-0ubuntu1.16.04.2) ...
Loading new virtualbox-5.0.40 DKMS files...
First Installation: checking all kernels...
Building only for 4.16.0-041600rc1-generic
Building initial module for 4.16.0-041600rc1-generic
ERROR (dkms apport): kernel package linux-headers-4.16.0-041600rc1-generic is 
not supported
Error! Bad return status for module build on kernel: 4.16.0-041600rc1-generic 
(x86_64)
Consult /var/lib/dkms/virtualbox/5.0.40/build/make.log for more information.
Job for virtualbox.service failed because the control process exited with error 
code. See "systemctl status virtualbox.service" and "journalctl -xe" for 
details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
● virtualbox.service - LSB: VirtualBox Linux kernel module
   Loaded: loaded (/etc/init.d/virtualbox; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2018-02-13 13:30:45 EST; 3ms ago
 Docs: man:systemd-sysv-generator(8)
  Process: 9835 ExecStart=/etc/init.d/virtualbox start (code=exited, 
status=1/FAILURE)

Feb 13 13:30:45 louiswu systemd[1]: Starting LSB: VirtualBox Linux kernel m.
Feb 13 13:30:45 louiswu virtualbox[9835]:  * Loading VirtualBox kernel modul
Feb 13 13:30:45 louiswu virtualbox[9835]:  * No suitable module for running ...d
Feb 13 13:30:45 louiswu virtualbox[9835]:...fail!
Feb 13 13:30:45 louiswu systemd[1]: virtualbox.service: Control process exi...=1
Feb 13 13:30:45 louiswu systemd[1]: Failed to start LSB: VirtualBox Linux k...e.
Feb 13 13:30:45 louiswu systemd[1]: virtualbox.service: Unit entered failed...e.
Feb 13 13:30:45 louiswu systemd[1]: virtualbox.service: Failed with result ...'.
Hint: Some lines were ellipsized, use -l to show in full.

Is there an updated dkms and/or virtualbox-dkms to go along with the
4.16 kernel?

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

Title:
  System hang with Virtualbox & kernel 4.13.0-32-generic

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

Bug description:
  Some (maybe all) kernels in the 4.13.0 series are hanging with
  Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a
  Virtualbox VM, the VM's window appears, clears to black, and then the
  mouse freezes. I do NOT see any BIOS/EFI information or boot loader in
  the VM; the hang occurs before those messages appear. (I've tried this
  with the VM set for both BIOS and EFI booting with no difference.) The
  host computer also stops responding to pings or anything else; the
  only solution seems to be to do a cold reset. I've tested this on a
  different computer running the same kernel and the latest Ubuntu 18.04
  alpha and had no problems there. Here's some data from the affected
  computer:

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

  $ cat /proc/version_signature 
  Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13

  $ dpkg -s virtualbox | grep Version
  Version: 5.0.40-dfsg-0ubuntu1.16.04.2

  This problem does NOT occur with earlier kernels, such as those in the 4.4.0 
series.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

The 7139 came back from suspend ~20 minutes later just fine.


** Attachment added: "/sys/firmware/acpi/tables/DSDT for 7139"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+attachment/5054510/+files/DSDT.7139.flimsy

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  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:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 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: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  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/1745342/+subscriptions

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

[Kernel-packages] [Bug 1748673] Re: package linux-image-4.13.0-32-generic 4.13.0-32.35 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

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

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

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

Title:
  package linux-image-4.13.0-32-generic 4.13.0-32.35 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I tried to update the linux image normally this morning (paris time).
  However it hanged, so I had to kill the process from the command line.
  After that I tried to remove the offending package so I could run apt
  again. That did not work, and after a reboot a few hours later, I had
  to go into an old kernel and run dpkg --configure -a to fix things.
  This time it worked.

  After that I gave this linux image another shot by running apt install
  linux-image-generic. This seemed to work, but after a reboot I got a
  request for a bug report. After that I filed this bug.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1132 F pulseaudio
rob1575 F pulseaudio
  Date: Sat Feb 10 13:01:38 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  InstallationDate: Installed on 2018-01-19 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57f5 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 0b05:1854 ASUSTek Computer, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL553VD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-32-generic 
root=UUID=28c8e634-053c-484d-bdf1-b90493b2f7ee ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.13.0-32-generic 4.13.0-32.35 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL553VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL553VD
  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.:bvrGL553VD.302:bd03/06/2017:svnASUSTeKCOMPUTERINC.:pnGL553VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL553VD
  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/1748673/+subscriptions

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

[Kernel-packages] [Bug 1748675] Re: Laptop freezes seconds after displaying the login screen

We can perform a "Reverse" bisect to identify the commit that fixes this
bug in 4.15.  We first need to identify the last kernel version that had
the bug and the first that did not.  Can you try the following two
kernels:

v4.14-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc1/
v4.15-rc1:http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/

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

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

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

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

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

** Tags added: kernel-da-key needs-bisect

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

** Tags removed: needs-bisect
** Tags added: performing-bisect

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

Title:
  Laptop freezes seconds after displaying the login screen

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

Bug description:
  My Dell Precision Laptop 5520 freezes seconds after displaying the
  login screen when using linux-image-4.13.0-32-generic (Includes 31,
  30).

  Selecting 4.13.0-17-generic allows for stable operation. I am still
  currently installing the main line series and will report if the issue
  is resolved once that is installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   rhianresnick   3057 F...m pulseaudio
   /dev/snd/controlC0:  rhianresnick   3057 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 10 18:12:26 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  HibernationDevice: RESUME=UUID=d22435f8-1e7b-46d7-b6bf-9722c30e05c1
  InstallationDate: Installed on 2016-11-22 (445 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  MachineType: Dell Inc. Precision 5510
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=5f8e45d9-71ed-4a72-9380-ac204117e9cd ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.1
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd12/11/2017:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1748671] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000009

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

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

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

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

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

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

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  0009

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

Bug description:
  Got this bug/oops while running with the linux-image-4.4.0-113-generic
  (4.4.0-113.136) kernel from -proposed:

  BUG: unable to handle kernel NULL pointer dereference at 0009
  IP: [] csum_and_copy_from_iter+0x55/0x4c0
  PGD 0 
  Oops:  [#1] SMP 
  Modules linked in: ctr ccm veth xt_CHECKSUM iptable_mangle xt_comment ec_sys 
bridge stp llc nf_log_ipv6 ip6table_filter ip6t_MASQUERADE 
nf_nat_masquerade_ipv6 ip6table_nat nf_nat_ipv6 ip6_tables nf_log_ip
   snd ghash_clmulni_intel soundcore r8169 psmouse input_leds cfg80211 rtsx_pci 
mii vhost_net vhost media ahci libahci macvtap macvlan mei_me mei kvm_intel kvm 
irqbypass tpm_crb i2c_hid intel_lpss_acpi inte
  CPU: 2 PID: 3997 Comm: dnsmasq Tainted: PW  O4.4.0-113-generic 
#136-Ubuntu
  Hardware name: System76Lemur/Lemur, BIOS 5.12 
02/17/2017
  task: 880830269e00 ti: 880035c44000 task.ti: 880035c44000
  RIP: 0010:[]  [] 
csum_and_copy_from_iter+0x55/0x4c0
  RSP: 0018:880035c47a18  EFLAGS: 00010246
  RAX: ab729fd0 RBX: 001c RCX: 880035c47e98
  RDX: 880035c47a94 RSI: 001c RDI: 8807ef1a7424
  RBP: 880035c47a80 R08:  R09: 8807ef1a7424
  R10: 8807ef1a7424 R11: 8807ef1a7400 R12: 880035c47e98
  R13:  R14: 00ffabea6920 R15: 0001
  FS:  7ff2b234d880() GS:88086ed0() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 0009 CR3: 35c1e000 CR4: 00360670
  Stack:
   88084e001600 ab72d1d7 880830f18500 880035c47aaf
   880035c47a94 01c0  b0f4001fc4815eea
   001c 880830f18500  880035c47d30
  Call Trace:
   [] ? __alloc_skb+0x87/0x1f0
   [] ip_generic_getfrag+0x56/0xe0
   [] raw_getfrag+0xaf/0x100
   [] __ip_append_data.isra.45+0x98a/0xb90
   [] ? raw_recvmsg+0x1c0/0x1c0
   [] ? raw_recvmsg+0x1c0/0x1c0
   [] ip_append_data.part.46+0x7a/0xe0
   [] ip_append_data+0x34/0x40
   [] raw_sendmsg+0x724/0xc00
   [] ? aa_sk_perm+0x70/0x210
   [] ? aa_sock_msg_perm+0x61/0x150
   [] inet_sendmsg+0x6b/0xa0
   [] sock_sendmsg+0x3e/0x50
   [] SYSC_sendto+0x101/0x190
   [] ? sock_setsockopt+0x180/0x830
   [] ? apparmor_socket_setsockopt+0x22/0x30
   [] SyS_sendto+0xe/0x10
   [] entry_SYSCALL_64_fastpath+0x1c/0x93
  Code: f3 48 0f 47 de 48 85 db 0f 84 8b 01 00 00 8b 02 49 89 f9 49 89 cc 4c 8b 
71 08 89 45 c4 8b 01 a8 04 0f 85 79 01 00 00 4c 8b 79 18 <4d> 8b 6f 08 4d 29 f5 
49 39 dd 4c 0f 47 eb a8 02 0f 85 36 02 00 
  RIP  [] csum_and_copy_from_iter+0x55/0x4c0
   RSP 
  CR2: 0009
  ---[ end trace bdd9157c94a456b6 ]---

  The trigger is when I start an artful lxd container and it tries to
  get an IPv4/IPv6. Oddly enough, the same thing works perfectly for my
  xenial container. My lxd-bridge has dnsmasq contained by Apparmor
  which is non standard but always worked flawlessly.

  I can trigger the bug 100% of the time so validating any tentative fix
  should be easy.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-113-generic 4.4.0-113.136
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon  7244 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Sat Feb 10 16:45:26 2018
  HibernationDevice: RESUME=/dev/mapper/nvme0n1p3_crypt
  InstallationDate: Installed on 2016-12-06 (431 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161206)
  MachineType: System76 Lemur
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-112-generic.efi.signed 
root=UUID=49432620-38ed-44bd-912a-7bc51eec3a35 ro quiet splash possible_cpus=4 
nmi_watchdog=0 kaslr vsyscall=none vt.handoff=7
  RelatedPackageVersions:

[Kernel-packages] [Bug 1609601] Re: i2c_hid: probe of i2c-ELAN0732:00 failed with error -61

2018-02-13 Thread Kai-Heng Feng

It could be. Can you file a separate bug? Because yours is a different
model.

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

Title:
  i2c_hid: probe of i2c-ELAN0732:00 failed with error -61

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm using an HP Envy x360 M6-ar004dx with an AMD 7th-gen FX APU, and
  the touchscreen will not work. Dmesg shows i2c_hid reporting multiple
  "failed to reset device" error messages before finally failing to add
  it as an HID device with error -61. As far as I can tell, it's being
  detected as an ELAN touchscreen. I've seen reports that this error can
  be fixed in newer kernels, as the touchscreen uses GPIO interrupts
  which are fixed in versions 4.6 and later. Most of the information I
  can find indicates that 4.7 includes improved AMD support, but the
  mainline kernel build appears to be missing the AMD GPIO drivers,
  since I get a "failed to get GPIO interrupt" error. I've compiled my
  own 4.7 kernel from the mainline GIT, including the patches used in
  kernel-ppa/mainline and setting the right config flags for AMD GPIO,
  but that just gets me the same errors I'm seeing in 4.4.0-31-generic.
  For additional info, I'm attaching my dmesg output in its entirety.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: 
boot/vmlinuz-4.4.0-31-generic]
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  colin  3591 F pulseaudio
   /dev/snd/controlC0:  colin  3591 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Aug  3 21:51:47 2016
  HibernationDevice: RESUME=UUID=1875834b-d1ff-4b97-a9b8-44afb056c592
  InstallationDate: Installed on 2016-08-03 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  MachineType: HP HP ENVY x360 m6 Convertible
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81AA
  dmi.board.vendor: HP
  dmi.board.version: 59.42
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.10:bd06/29/2016:svnHP:pnHPENVYx360m6Convertible:pvrType1ProductConfigId:rvnHP:rn81AA:rvr59.42:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY x360 m6 Convertible
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

2018-02-13 Thread Kai-Heng Feng

Please attach the output of `cat /sys/firmware/acpi/tables/DSDT` for
both 7139 and 7140, so we can see what their _STA methods look like.

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  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:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 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: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  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/1745342/+subscriptions

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

[Kernel-packages] [Bug 1748678] Re: Intel graphics timeout, possibly caused wifi network to fail

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/


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

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

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

Title:
  Intel graphics timeout, possibly caused wifi network to fail

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My wifi network device stopped responding, unable to list any local
  wifi networks, which required turning off the adapter in settings and
  back-on again. while investigating I found the following in the dmesg
  output from the time the network device stopped responding. This is
  the only relevant message in recent history so I'm working on the
  assumption that somehow the intel gfx timeout knocked-onto the wifi
  device or the pci bus.

  === lcpsi of wifi card ===
  03:00.0 Network controller: Broadcom Limited BCM4331 802.11a/b/g/n (rev 02)
   Subsystem: Apple Inc. AirPort Extreme
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: wl
   Kernel modules: bcma, wl

  === lspci of gfx ===
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
   Kernel driver in use: i915
   Kernel modules: i915

  === relevant dmesg output ===
  [ 7450.338278] pipe A vblank wait timed out
  [ 7450.338321] [ cut here ]
  [ 7450.338380] WARNING: CPU: 2 PID: 29153 at 
/build/linux-UKCsxy/linux-4.13.0/drivers/gpu/drm/i915/intel_display.c:12848 
intel_atomic_commit_tail+0xf7d/0xf90 [i915]
  [ 7450.338380] Modules linked in: rfcomm scsi_transport_iscsi binfmt_misc 
veth ebtable_filter ebtables ip6t_MASQUERADE nf_nat_masquerade_ipv6 
ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_CHECKSUM 
xt_comment xt_tcpudp iptable_mangle unix_diag ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
xt_conntrack nf_nat nf_conntrack libcrc32c l2tp_ppp l2tp_netlink l2tp_core 
ip6_udp_tunnel udp_tunnel pppox mmc_block cmac bnep joydev applesmc 
input_polldev snd_hda_codec_hdmi snd_hda_codec_cirrus snd_hda_codec_generic 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_seq_midi snd_seq_midi_event 
snd_rawmidi bcm5974 kvm_intel
  [ 7450.338405]  btusb btrtl uvcvideo btbcm btintel kvm bluetooth irqbypass 
videobuf2_vmalloc videobuf2_memops snd_seq ecdh_generic videobuf2_v4l2 
videobuf2_core videodev intel_cstate intel_rapl_perf media wl(POE) input_leds 
snd_seq_device snd_timer mei_me lpc_ich cfg80211 mei snd soundcore thunderbolt 
sbs shpchp sbshc apple_gmux acpi_als kfifo_buf industrialio apple_bl mac_hid 
iptable_filter ip6table_filter ip6_tables br_netfilter bridge stp llc 
arp_tables parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor 
raid6_pq algif_skcipher af_alg hid_generic hid_apple usbhid hid dm_crypt 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 sdhci_pci ahci 
aesni_intel libahci sdhci i2c_algo_bit aes_x86_64 drm_kms_helper crypto_simd 
glue_helper syscopyarea cryptd sysfillrect sysimgblt fb_sys_fops
  [ 7450.338442]  drm video
  [ 7450.338445] CPU: 2 PID: 29153 Comm: kworker/u8:6 Tainted: P   OE   
4.13.0-32-generic #35-Ubuntu
  [ 7450.338446] Hardware name: Apple Inc. MacBookPro10,2/Mac-AFD8A9D944EA4843, 
BIOS MBP102.88Z.010B.B00.1708080805 08/08/2017
  [ 7450.338478] Workqueue: events_unbound intel_atomic_commit_work [i915]
  [ 7450.338479] task: 9873194445c0 task.stack: b24909028000
  [ 7450.338506] RIP: 0010:intel_atomic_commit_tail+0xf7d/0xf90 [i915]
  [ 7450.338507] RSP: 0018:b2490902bd90 EFLAGS: 00010286
  [ 7450.338508] RAX: 001c RBX:  RCX: 

  [ 7450.338509] RDX:  RSI: 98732f316578 RDI: 
98732f316578
  [ 7450.338509] RBP: b2490902be48 R08: 0001 R09:

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

[  +0.00] Linux version 4.15.0-9-generic (root@Ryzen) (gcc version
7.2.0 (Ubuntu 7.2.0-18ubuntu2)) #10~lp1745342+3 SMP Wed Feb 14 00:02:23
CST 2018

it worked!

I also suspended it, and it comes back fine from a short suspend; I'll
leave it for a while to see if it also comes back ok from a longer one.

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  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:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 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: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  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/1745342/+subscriptions

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

[Kernel-packages] [Bug 1748651] Re: Some function keys not working

2018-02-13 Thread Lev Kokotov

This bug was "fixed" by re-installing Ubuntu 16.04.3 (downloaded from
ubuntu.com a few days ago).

The buttons did not work initially when I installed the original 16.04
LTS version released in April 2016, so I'm guessing that version of the
kernel did not have that fix.

The current version of the kernel used in 16.04.3 fixed this issue. So
the bug should probably be with the upgrade mechanism of the kernel.

Thank you.

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

Title:
  Some function keys not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an ASUS UX305C laptop, and some of the function keys do not
  work.

  The keys in question:

  fn - airplane mode (f2)
  fn - brightness down (f5)
  fn - brightness up (f6)

  
  I followed the troubleshooting guide at 
https://wiki.ubuntu.com/Hotkeys/Troubleshooting with the following results:

  1. acpi_listen gives no output when those keys are pressed
  2. xev gives no output when those keys are pressed

  The keys work on Windows 10. On a more recent version of the similar
  laptop UX430UA-DH74, using the same version of Ubuntu 16.04.3, the
  same keys work properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lev2926 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Feb 10 11:47:39 2018
  HibernationDevice: RESUME=UUID=4a4d8024-561e-4d5e-882c-9f75d26c69fd
  InstallationDate: Installed on 2016-09-11 (516 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed 
root=UUID=ce463230-5723-4211-9d44-d18e3f30c695 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.15
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.201
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  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.:bvrUX305CA.201:bd09/11/2015:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX305CA
  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/1748651/+subscriptions

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

I'll try that in a moment.

For what it's worth I've also got a 7140, running 16.04. That one's
running 4.13.0-32 just fine. If there's anything you want me to try on
it, just let me know.

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  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:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 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: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  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/1745342/+subscriptions

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

[Kernel-packages] [Bug 1748747] Re: Laptop turns of when secondary battery is empty while main battery is still charged.

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/


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

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

Title:
  Laptop turns of when secondary battery is empty while main battery is
  still charged.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using a Lenovo T460s with two batteries running Ubuntu 17.10.

  The indicator shows the combined charge of both batteries and I was at
  40% when the laptop simply turned off. After the reboot I saw that the
  main battery was at 88% while the extra battery was at 0%. For some
  reason the OS deemed it necessary to perform an emergency shutdown
  without any warning.

  I don't know whether this is a problem in gnome power management or
  the kernel but please, please find a fix for this! Or provide some
  workaround.

  Best regards

  Christoph Grimmer-Dietrich

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

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

[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

2018-02-13 Thread Kamal Mostafa

The linux-aws (4.4.0-1052.xx) release has been delayed by the merge of
additional necessary retpoline fixes.  The packages have now been built
and are available in the -proposed archive; current ETA for final
release of this kernel is early next week.  In the meantime, the .deb
package from -proposed is available here:

http://launchpadlibrarian.net/356804492/linux-
image-4.4.0-1052-aws_4.4.0-1052.61_amd64.deb

Folks affected by this bug: Please verify that this kernel still
resolves the problem and post your results here.  Thanks for your
patience!

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Committed

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1746806/+subscriptions

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

[Kernel-packages] [Bug 1748710] Re: Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1 built-in shell (initramfs).

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/


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

** Tags added: pti

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

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

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

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

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

Title:
  Linux 4.4.0-113.136 (i386/x86_32): failed to boot and BusyBox v1.22.1
  built-in shell (initramfs).

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

Bug description:
  Hello.

  On Thu Feb 8, Linux kernel for Ubuntu 16.04.3 LTS has been updated to
  the 4.4.0-113.136 version (xenial-proposed). However, after reboot,
  plymouth freezes during start, and keys on an USB keyboard were in-
  active. After several seconds, the BusyBox shell screen appeared. It
  looks this way:

  ,--
  | BusyBox v1.22.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
  | Enter 'help' for a list of built-in commands.
  |
  | (initramfs) _ 
  `--

  Unfortunately, the USB keyboard does not work and does not respond.
  The only way to solve this issue is a "hard reset" and in GRUB menu
  choosing an earlier kernel, which is linux 4.4.0-112.135. Now,
  everything works okay.

  Proposed update to the Linux 4.4.0-113.136 contains many new updates
  (please see 1.) It's an i386/x86_32 architecture, which does not
  contain PTI yet, right? I'm asking, because mentioned -proposed
  updates contains a couple of PTI-related patches and bugs in PTI can
  cause a few different signatures of crashes etc. For example:

  → Crashes in early boot, especially around CPU bringup.  Bugs in the 
trampoline code or mappings cause these. 
  → Userspace segfaults early in boot, sometimes manifesting as mount(8) 
failing to mount the rootfs.  These have tended to be TLB invalidation issues. 
Usually invalidating the wrong PCID, or otherwise missing an invalidation. 

  NOTE: if it's about PCID, which is mentioned in a second point, there
  is one patch in -proposed update: "x86/mm/32: Move
  setup_clear_cpu_cap(X86_FEATURE_PCID) earlier". Maybe that's is the
  cause of a boot failure? There are no errors in log files, such as
  '/var/log/syslog' or '/var/log/kern.log'. However, it's a Celeron, "E"
  series. So, I don't know if mentioned patches are good for this type
  of processor etc.? Especially on i386/x86_32 architecture.

  ● UPDATE/WARNING: It seems, that 'kaslr' option is responsible for
  this issue. After booting the latest v4.4.0-115.139 kernel, I've had
  the same problems as described above. However, after removing 'kaslr'
  option from a command line via GRUB menu, system started normally etc.
  The latest, working kernel with 'kaslr' option is v4.4.0-112.135.
  According to all of this I think, that 'kaslr' is not compatible with
  some "Spectre & Meltdown" mitigation patches and fixes etc.

  ✗ Release ('/proc/version_signature'): Ubuntu 4.4.0-112.135-generic 4.4.98
  ✗ Architecture: i386/x86_32
  ✗ PCI ('lspci -vnvn'): 00:0a.0 PCI bridge [0604]: NVIDIA Corporation MCP73 
PCI Express bridge [10de:056d] (rev a1) (prog-if 01 [Subtractive decode]) 
Capabilities: [b8] Subsystem: Gigabyte Technology Co., Ltd MCP73 PCI Express 
bridge [1458:026f] 

  Thanks, regards.
  

  1. https://lists.ubuntu.com/archives/xenial-
  changes/2018-February/020108.html

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

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

[Kernel-packages] [Bug 1748689] Re: Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in smb2_get_dfs_refer rc=-2"

Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/

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

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

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

Title:
Mounting SMB shares with vers=3.0 in fstab gives "ioctl error in
smb2_get_dfs_refer rc=-2"

Status in linux package in Ubuntu:
Incomplete

Bug description:
Xubuntu 17.10 artful
Kernel: x86_64 Linux 4.13.0-32.35-generic
cifs-utils 2:6.7-1
smbclient 2:4.6.7+dfsg-1ubuntu3.1

Mounting an SMB share with

sec=ntlmssp,vers=3.0,credentials=/home/.smbcredentials,dir_mode=0777,file_mode=0777

in /etc/fstab gives the error: "CIFS VFS: ioctl error in
smb2_get_dfs_refer rc=-2" in dmesg.

Shares mounted this way are readable, but writing data to them (or using
programs such as EasyTAG to write to them) ultimately fails. This bug did not
occur in kernel 4.10. Mounting the share(s) with vers=1.0 does not give the
error, but this is a haphazard fix as SMB v3.0 carries many security features
with it not avaliable in SMB 1.0.
---
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: XFCE
DistroRelease: Ubuntu 17.10
HibernationDevice: RESUME=/dev/mapper/DeusVitam--vg-swap_1
JournalErrors:
Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000']
failed with exit code 1: Hint: You are currently not seeing messages from other
users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
No journal files were opened due to insufficient permissions.
MachineType: ASUS All Series
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic
root=/dev/mapper/hostname--vg-root ro splash quiet amdgpu.cik_support=1
vt.handoff=7
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
RelatedPackageVersions:
linux-restricted-modules-4.13.0-32-generic N/A
linux-backports-modules-4.13.0-32-generic N/A
linux-firmware 1.169.3
RfKill:

Tags: artful
Uname: Linux 4.13.0-32-generic x86_64
UpgradeStatus: Upgraded to artful on 2018-02-05 (7 days ago)
UserGroups: libvirt libvirtd sudo wireshark
WifiSyslog:

_MarkForUpload: True
dmi.bios.date: 03/16/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0701
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-E/USB 3.1
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
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.:bvr0701:bd03/16/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-E/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

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

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

[Kernel-packages] [Bug 1748768] Re: System won't boot 4.13.0-32 kernel

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/

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

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

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

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

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

** Tags added: kernel-da-key needs-bisect

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

Title:
  System won't boot 4.13.0-32 kernel

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

Bug description:
  Ever since the update to the 4.13.0-32 kernel, my system won't boot.
  When I turn off the splash screen and quiet, I see repeated messages
  about not connecting to lvmetad and falling back to device scanning.

  The disk has a boot partition and a logical volume partition.  The
  logical volume partition is encrypted with LUKS.

  I can boot the 4.13.0-31 kernel with no problems (that's where the
  data for this bug was collected).  I'm not sure how to troubleshoot
  this further.

  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:  jim5303 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Feb 11 11:01:02 2018
  HibernationDevice: RESUME=UUID=ff4e1c78-1dec-4f38-8cc2-e28a35635b6b
  InstallationDate: Installed on 2017-01-16 (391 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 2436CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-31-generic 
root=/dev/mapper/ubuntu--vg-root 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.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-31 (103 days ago)
  dmi.bios.date: 02/27/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ET92WW (2.52 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2436CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn2436CTO:pvrThinkPadW530:rvnLENOVO:rn2436CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W530
  dmi.product.name: 2436CTO
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1748805] Re: package linux-firmware 1.157.15 failed to install/upgrade: package linux-firmware is not ready for configuration cannot configure (current status 'half-installed')

** Changed in: linux-firmware (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  package linux-firmware 1.157.15 failed to install/upgrade: package
  linux-firmware is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  recommended updates failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.15
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  AptOrdering:
   cups-backend-bjnp: Install
   linux-firmware: Configure
   cups-backend-bjnp: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Feb 11 20:36:53 2018
  Dependencies:
   
  DuplicateSignature:
   package:linux-firmware:1.157.15
   Unpacking cups-backend-bjnp (2.0-0ubuntu2) ...
   dpkg: error processing package linux-firmware (--configure):
package linux-firmware is not ready for configuration
  ErrorMessage: package linux-firmware is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2013-12-15 (1519 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.157.15 failed to install/upgrade: package 
linux-firmware is not ready for configuration  cannot configure (current status 
'half-installed')
  UpgradeStatus: Upgraded to xenial on 2016-11-24 (444 days ago)

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

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

[Kernel-packages] [Bug 1748801] Re: Sometimes Freezes

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/

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

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

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

Title:
  Sometimes Freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Sometimes freezes, i have 8gb of ram, i don't understand... Goodbye!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nixon  2430 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 11 21:27:10 2018
  HibernationDevice: RESUME=UUID=85d90702-6bb1-41d7-9ef9-776d17077151
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: VIT VIT P3400
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d5a5f05f-a5a2-48d2-ae69-e6620f8a2f34 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 2.00.01.IP_T4
  dmi.board.asset.tag: NULL
  dmi.board.name: VIT P3400
  dmi.board.vendor: VIT
  dmi.board.version: Not applicable
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: VIT
  dmi.chassis.version: Not applicable
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr2.00.01.IP_T4:bd03/25/2013:svnVIT:pnVITP3400:pvr1.0:rvnVIT:rnVITP3400:rvrNotapplicable:cvnVIT:ct9:cvrNotapplicable:
  dmi.product.family: ChiefRiver System
  dmi.product.name: VIT P3400
  dmi.product.version: 1.0
  dmi.sys.vendor: VIT

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

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

[Kernel-packages] [Bug 1748373] Re: Resume from hibernate fails on latest kernels

2018-02-13 Thread John Smith

Done. The upstream kernel appears to have fixed this bug. Thank you!

** Tags added: kernel-fixed-upstream

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

Title:
  Resume from hibernate fails on latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell Inspiron 15 laptop (Intel Core i3-6006U) running Ubuntu
  17.10. Kernel 4.13.0.21 hibernates and resumes without problems, but
  the three more recent kernels (4.13.0.25, 4.13.0.31 and 4.13.0.32)
  fail: hibernate appears to succeed, but resume stops dead part-way
  through. This happens whether I use the built-in hibernate capability
  or usw-susp, and whether my Gnome session uses xorg or Wayland.

  /var/log/kern.log doesn't seem to help much. A typical record of the failed 
attempt to resume is as follows:
  Jan 23 21:10:13 bombay kernel: [ 98.197921] Bluetooth: RFCOMM TTY layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197937] Bluetooth: RFCOMM socket layer 
initialized
  Jan 23 21:10:13 bombay kernel: [ 98.197954] Bluetooth: RFCOMM ver 1.11
  Jan 23 21:10:19 bombay kernel: [ 104.454231] rfkill: input handler disabled
  Jan 23 21:10:23 bombay kernel: [ 108.416251] EXT4-fs (sda1): mounted 
filesystem with ordered data mode. Opts: (null)
  Jan 23 21:10:41 bombay kernel: [ 126.528680] usbcore: deregistering interface 
driver uvcvideo
  Jan 23 21:10:42 bombay kernel: [ 126.919415] rfkill: input handler enabled
  Jan 23 21:10:42 bombay kernel: [ 127.240559] PM: Syncing filesystems ... 

  Several other people have reported similar behaviour: 
https://ubuntuforums.org/showthread.php?t=2382336. (This report is an edited 
version of what I say there.)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2636 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=54d8b4c5-8ff7-40c6-ba9c-00e3af6b7b68
  InstallationDate: Installed on 2017-03-25 (321 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. Inspiron 15-3567
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=c1b9dad0-3a0f-4e2c-90ee-160cd1a445a8 ro quiet splash mce=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.3
  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-24 (108 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.3
  dmi.board.name: 0JVG7J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.3:bd12/12/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0JVG7J:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1749250] Re: linux: 4.15.0-10.11 -proposed tracker

2018-02-13 Thread Brad Figg

** Changed in: kernel-development-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.15.0-10.11 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
+ 
+ kernel-phase-changed:Tuesday, 13. February 2018 17:46 UTC
+ kernel-phase:Packaging

** Description changed:

  This bug is for tracking the 4.15.0-10.11 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
  
  kernel-phase-changed:Tuesday, 13. February 2018 17:46 UTC
  kernel-phase:Packaging
+ 
+ -- swm properties --
+ phase: Packaging

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

Title:
  linux: 4.15.0-10.11 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.15.0-10.11 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

  kernel-phase-changed:Tuesday, 13. February 2018 17:46 UTC
  kernel-phase:Packaging

  -- swm properties --
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1749250/+subscriptions

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

[Kernel-packages] [Bug 1748520] Re: SDXC card reader not recognized

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/

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

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

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

Title:
  SDXC card reader not recognized

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Macbook Pro 13" Retina (MacbookPro12,1 mid 2015) the SDXC card slot
  is non-responsive.

  uname -a
  Linux mbpr13b 4.13.0-33-generic #36-Ubuntu SMP Tue Feb 6 20:30:50 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Installing sdhci and sdhci-pci modules (with or without adding a
  /etc/modprobe.d/sdhci.conf to configure option debug_quirks2) does not
  work.

  After a reboot, the drivers are not installed.
  A device /dev/mmcblk0 is missing.

  This used to be different in previous kernels 4.13... (although I have
  no record when last I tested).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-33-generic 4.13.0-33.36
  ProcVersionSignature: Ubuntu 4.13.0-33.36-generic 4.13.13
  Uname: Linux 4.13.0-33-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm1055 F pulseaudio
wolf   1399 F pulseaudio
   /dev/snd/controlC0:  gdm1055 F pulseaudio
wolf   1399 F pulseaudio
  Date: Fri Feb  9 20:25:21 2018
  HibernationDevice: RESUME=UUID=e0d91223-651f-43b1-bb25-12794e7155d4
  InstallationDate: Installed on 2017-10-20 (112 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 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  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.13.0-33-generic N/A
   linux-backports-modules-4.13.0-33-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0171.B00.1708080033
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1748901] Re: System hang with Virtualbox & kernel 4.13.0-32-generic

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/


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

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  System hang with Virtualbox & kernel 4.13.0-32-generic

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

Bug description:
  Some (maybe all) kernels in the 4.13.0 series are hanging with
  Virtualbox on my Ubuntu 16.04 laptop. When I try to launch a
  Virtualbox VM, the VM's window appears, clears to black, and then the
  mouse freezes. I do NOT see any BIOS/EFI information or boot loader in
  the VM; the hang occurs before those messages appear. (I've tried this
  with the VM set for both BIOS and EFI booting with no difference.) The
  host computer also stops responding to pings or anything else; the
  only solution seems to be to do a cold reset. I've tested this on a
  different computer running the same kernel and the latest Ubuntu 18.04
  alpha and had no problems there. Here's some data from the affected
  computer:

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

  $ cat /proc/version_signature 
  Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13

  $ dpkg -s virtualbox | grep Version
  Version: 5.0.40-dfsg-0ubuntu1.16.04.2

  This problem does NOT occur with earlier kernels, such as those in the 4.4.0 
series.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rodsmith   2661 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2014-05-02 (1382 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 740U5M
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: \vmlinuz-4.13.0-32-generic.efi.signed ro 
root=/dev/mapper/hostname-trusty_crypt  quiet splash  
initrd=\initrd.img-4.13.0-32-generic
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.15
  Tags:  xenial
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-09-03 (526 days ago)
  UserGroups: adm cdrom dialout dip disk libvirtd lpadmin plugdev sambashare 
sbuild sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 12/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02AFZ.015.161206.KS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP740U5M-X01US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL8815A0I-C01-G001-S0001+10.0.14393
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02AFZ.015.161206.KS:bd12/06/2016:svnSAMSUNGELECTRONICSCO.,LTD.:pn740U5M:pvrP02AFZ:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP740U5M-X01US:rvrSGL8815A0I-C01-G001-S0001+10.0.14393:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:
  dmi.product.family: SAMSUNG ATIV
  dmi.product.name: 740U5M
  dmi.product.version: P02AFZ
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

2018-02-13 Thread Kai-Heng Feng

Actually, there's a great hint:

commit b5cc1699191829cda2dd9447210e1e801e2082c9
Author: Hans de Goede 
Date:   Sun Jul 9 21:05:13 2017 +0200

ACPI / x86: Add Dell Venue 11 Pro 7130 touchscreen to
always_present_ids

Let's do that same for 7139.

http://people.canonical.com/~khfeng/lp1745342-3/

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  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:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 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: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  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/1745342/+subscriptions

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

[Kernel-packages] [Bug 1748604] Re: Ubuntu randomly freezes

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/

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

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

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

Title:
  Ubuntu randomly freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu randomly freezes, sometimes after 30 minutes, sometimes after 3h, 
sometimes not at all.
  I don't know what it can come from, I think it's PHP 7.2 or Nvidia drivers 
but I'm not sure.
  I've a AMD Ryzen, perhaps it's here ?...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cyp1659 F pulseaudio
   /dev/snd/controlC1:  cyp1659 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Sat Feb 10 11:24:11 2018
  InstallationDate: Installed on 2018-01-12 (28 days ago)
  InstallationMedia: Ubuntu-Budgie 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  IwConfig:
   enp6s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=0c8e65ac-58cb-4665-a7ec-ecfd44afa886 ro quiet splash acpi=force 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2018-01-21 (19 days ago)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.40
  dmi.board.name: AB350M Pro4
  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.:bvrP3.40:bd12/27/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4: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.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/1748604/+subscriptions

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

[Kernel-packages] [Bug 1748565] Re: Bluetooth: hci0: last event is not cmd complete (0x0f)

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

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

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

Title:
  Bluetooth: hci0: last event is not cmd complete (0x0f)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  dmesg:
  [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1811 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 20:35:29 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1733230] Re: 'zfs recv' hangs when receiving from a FreeBSD zfs

2018-02-13 Thread Launchpad Bug Tracker

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

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

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

Title:
  'zfs recv' hangs when receiving from a FreeBSD zfs

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  When creating a pool snapshot on a freenas/freebsd like this:

  ```
  root@freenas:~ # uname -a
  FreeBSD freenas.local 11.0-STABLE FreeBSD 11.0-STABLE #0 
r321665+25fe8ba8d06(freenas/11.0-stable): Mon Sep 25 06:24:11 UTC 2017 
root@gauntlet:/freenas-11-releng/freenas/_BE/objs/freenas-11-releng/freenas/_BE/os/sys/FreeNAS.amd64
  amd64
  freenas# zpool create tank gptid/62a26be7-cd4a-11e7-927b-0800278dcda9
  freenas# dd if=/dev/zero of=/tank/ur.bin bs=64K count=1
  freenas# zfs snap tank@example
  ```

  And trying to `zfs send | zfs recv` it to an ubuntu zfs like this:
  ```
  space@ubuntu:~$ apt-cache policy zfsutils-linux
  zfsutils-linux:
Installed: 0.6.5.11-1ubuntu3
Candidate: 0.6.5.11-1ubuntu3
Version table:
   *** 0.6.5.11-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status
  space@ubuntu:~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  root@ubuntu:~$ ssh root@freenas zfs send tank@example > freenas11.zfssend
  root@ubuntu:~# cat ./freenas11.zfssend | zfs recv tank/something
  ```

  The `zfs recv` process burns 100% CPU and hangs forever. I have
  attached an example freenas11.zfssend file, though it's easily
  reproduced.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: zfsutils-linux 0.6.5.11-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Sun Nov 19 22:10:15 2017
  ExecutablePath: /sbin/zfs
  InstallationDate: Installed on 2017-11-17 (2 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   PATH=(custom, no user)
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

2018-02-13 Thread Kamal Mostafa

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

** Changed in: linux-aws (Ubuntu Xenial)
   Status: In Progress => Fix Committed

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux-aws source package in Xenial:
  Fix Committed

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1746806/+subscriptions

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

[Kernel-packages] [Bug 1748670] Re: iwlwifi 0000:01:00.0: Microcode SW error detected. Restarting 0x2000000.

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

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

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

Title:
  iwlwifi :01:00.0: Microcode SW error detected.  Restarting
  0x200.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello,

  dmesg:
  [ 6329.117564] iwlwifi :01:00.0: Microcode SW error detected.  Restarting 
0x200.
  [ 6329.117581] iwlwifi :01:00.0: Loaded firmware version: 18.168.6.1
  [ 6329.117709] iwlwifi :01:00.0: Start IWL Error Log Dump:
  [ 6329.117716] iwlwifi :01:00.0: Status: 0x02CC, count: 6
  [ 6329.117724] iwlwifi :01:00.0: 0x198A | ADVANCED_SYSASSERT  
  [ 6329.117730] iwlwifi :01:00.0: 0x00015920 | uPc
  [ 6329.117737] iwlwifi :01:00.0: 0x00015910 | branchlink1
  [ 6329.117743] iwlwifi :01:00.0: 0x00015910 | branchlink2
  [ 6329.117749] iwlwifi :01:00.0: 0xDBEA | interruptlink1
  [ 6329.117755] iwlwifi :01:00.0: 0x | interruptlink2
  [ 6329.117761] iwlwifi :01:00.0: 0x118B | data1
  [ 6329.117767] iwlwifi :01:00.0: 0x000A | data2
  [ 6329.117773] iwlwifi :01:00.0: 0x01DC | line
  [ 6329.117780] iwlwifi :01:00.0: 0x258090C1 | beacon time
  [ 6329.117786] iwlwifi :01:00.0: 0x169CDB3F | tsf low
  [ 6329.117792] iwlwifi :01:00.0: 0x0058 | tsf hi
  [ 6329.117798] iwlwifi :01:00.0: 0x | time gp1
  [ 6329.117804] iwlwifi :01:00.0: 0x78A30020 | time gp2
  [ 6329.117810] iwlwifi :01:00.0: 0x | time gp3
  [ 6329.117816] iwlwifi :01:00.0: 0x754312A8 | uCode version
  [ 6329.117822] iwlwifi :01:00.0: 0x00B0 | hw version
  [ 6329.117828] iwlwifi :01:00.0: 0x00484B00 | board version
  [ 6329.117834] iwlwifi :01:00.0: 0x001C | hcmd
  [ 6329.117840] iwlwifi :01:00.0: 0x2F963840 | isr0
  [ 6329.117847] iwlwifi :01:00.0: 0x1189F800 | isr1
  [ 6329.117853] iwlwifi :01:00.0: 0x0E1F | isr2
  [ 6329.117859] iwlwifi :01:00.0: 0x0147FCC3 | isr3
  [ 6329.117865] iwlwifi :01:00.0: 0x | isr4
  [ 6329.117871] iwlwifi :01:00.0: 0x0110 | isr_pref
  [ 6329.117877] iwlwifi :01:00.0: 0x000260A4 | wait_event
  [ 6329.117883] iwlwifi :01:00.0: 0x00D4 | l2p_control
  [ 6329.117890] iwlwifi :01:00.0: 0x | l2p_duration
  [ 6329.117896] iwlwifi :01:00.0: 0x0007 | l2p_mhvalid
  [ 6329.117902] iwlwifi :01:00.0: 0x00101042 | l2p_addr_match
  [ 6329.117908] iwlwifi :01:00.0: 0x0005 | lmpm_pmg_sel
  [ 6329.117914] iwlwifi :01:00.0: 0x13011136 | timestamp
  [ 6329.117920] iwlwifi :01:00.0: 0xC0D0 | flow_handler
  [ 6329.117982] iwlwifi :01:00.0: Start IWL Event Log Dump: nothing in log
  [ 6329.130217] ieee80211 phy0: Hardware restart was requested
  [ 6329.143138] iwlwifi :01:00.0: Radio type=0x2-0x1-0x0
  [ 6329.446667] iwlwifi :01:00.0: Radio type=0x2-0x1-0x0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   1721 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Sat Feb 10 18:36:30 2018
  InstallationDate: Installed on 2017-10-13 (120 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage

[Kernel-packages] [Bug 1748638] Re: System freezing

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/

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

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

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

Title:
  System freezing

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  System completely freezes quite frequently, not responding to any
  action nor key combination. I have to long press the power button to
  reboot the system or remove the battery.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ondra  1891 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Feb 10 15:56:56 2018
  HibernationDevice: RESUME=UUID=5e25406d-d414-dbcf-2b96-f5139433cc2b
  InstallationDate: Installed on 2017-12-26 (45 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 20F1001YMC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=871d7486-df77-4e2e-a7d2-47938e1b1773 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2018-01-12 (28 days ago)
  dmi.bios.date: 11/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1HET70W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20F1001YMC
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1HET70W(1.34):bd11/13/2017:svnLENOVO:pn20F1001YMC:pvrThinkPadL560:rvnLENOVO:rn20F1001YMC:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L560
  dmi.product.name: 20F1001YMC
  dmi.product.version: ThinkPad L560
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1748651] Re: Some function keys not working

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/

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

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

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

Title:
  Some function keys not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have an ASUS UX305C laptop, and some of the function keys do not
  work.

  The keys in question:

  fn - airplane mode (f2)
  fn - brightness down (f5)
  fn - brightness up (f6)

  
  I followed the troubleshooting guide at 
https://wiki.ubuntu.com/Hotkeys/Troubleshooting with the following results:

  1. acpi_listen gives no output when those keys are pressed
  2. xev gives no output when those keys are pressed

  The keys work on Windows 10. On a more recent version of the similar
  laptop UX430UA-DH74, using the same version of Ubuntu 16.04.3, the
  same keys work properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lev2926 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Feb 10 11:47:39 2018
  HibernationDevice: RESUME=UUID=4a4d8024-561e-4d5e-882c-9f75d26c69fd
  InstallationDate: Installed on 2016-09-11 (516 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic.efi.signed 
root=UUID=ce463230-5723-4211-9d44-d18e3f30c695 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-112-generic N/A
   linux-backports-modules-4.4.0-112-generic  N/A
   linux-firmware 1.157.15
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.201
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  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.:bvrUX305CA.201:bd09/11/2015:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX305CA
  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/1748651/+subscriptions

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

[Kernel-packages] [Bug 1749202] Re: "swiotlb: coherent allocation failed" dmesg spam with linux 4.15.0-9.10

2018-02-13 Thread Seth Forshee

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

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

Title:
  "swiotlb: coherent allocation failed" dmesg spam with linux
  4.15.0-9.10

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  I'm seeing this appear fairly regularly in dmesg:

  [23630.791701] nouveau :02:00.0: swiotlb buffer is full (sz: 2097152 
bytes)
  [23630.791703] swiotlb: coherent allocation failed for device :02:00.0 
size=2097152
  [23630.791706] CPU: 12 PID: 2609 Comm: gnome-shell Not tainted 
4.15.0-9-generic #10-Ubuntu
  [23630.791709] Hardware name: Intel Corp. GRANTLEY/GRANTLEY, BIOS 
GRNDCRB1.86B.0032.R02.1405090848 05/09/2014
  [23630.791710] Call Trace:
  [23630.791718]  dump_stack+0x63/0x8b
  [23630.791723]  swiotlb_alloc_coherent+0xe8/0x160
  [23630.791728]  x86_swiotlb_alloc_coherent+0x43/0x50
  [23630.791734]  ttm_dma_pool_get_pages+0x1f1/0x5b0 [ttm]
  [23630.791737]  ttm_dma_populate+0x249/0x330 [ttm]
  [23630.791770]  nouveau_ttm_tt_populate+0x156/0x1f0 [nouveau]
  [23630.791773]  ttm_tt_bind+0x2e/0x60 [ttm]
  [23630.791776]  ttm_bo_handle_move_mem+0x589/0x5c0 [ttm]
  [23630.791779]  ? ttm_bo_mem_space+0x39d/0x470 [ttm]
  [23630.791782]  ttm_bo_validate+0x144/0x160 [ttm]
  [23630.791784]  ttm_bo_init_reserved+0x393/0x430 [ttm]
  [23630.791787]  ttm_bo_init+0x2d/0x90 [ttm]
  [23630.791808]  ? nouveau_bo_invalidate_caches+0x10/0x10 [nouveau]
  [23630.791827]  nouveau_bo_new+0x40c/0x580 [nouveau]
  [23630.791847]  ? nouveau_bo_invalidate_caches+0x10/0x10 [nouveau]
  [23630.791866]  nouveau_gem_new+0x60/0x130 [nouveau]
  [23630.791883]  nouveau_gem_ioctl_new+0x59/0xe0 [nouveau]
  [23630.791899]  ? nouveau_gem_new+0x130/0x130 [nouveau]
  [23630.791912]  drm_ioctl_kernel+0x5f/0xb0 [drm]
  [23630.791919]  drm_ioctl+0x31b/0x3d0 [drm]
  [23630.791936]  ? nouveau_gem_new+0x130/0x130 [nouveau]
  [23630.791954]  nouveau_drm_ioctl+0x72/0xc0 [nouveau]
  [23630.791957]  do_vfs_ioctl+0xa8/0x630
  [23630.791961]  ? __sys_recvmsg+0x80/0x90
  [23630.791964]  SyS_ioctl+0x79/0x90
  [23630.791967]  do_syscall_64+0x76/0x130
  [23630.791971]  entry_SYSCALL_64_after_hwframe+0x21/0x86
  [23630.791972] RIP: 0033:0x7f26f5357ea7
  [23630.791973] RSP: 002b:7ffe50c20ee8 EFLAGS: 0246 ORIG_RAX: 
0010
  [23630.791975] RAX: ffda RBX: 5570b6b1b490 RCX: 
7f26f5357ea7
  [23630.791975] RDX: 7ffe50c20f40 RSI: c0306480 RDI: 
000b
  [23630.791976] RBP: 7ffe50c20f40 R08: 0004 R09: 
5570b6b1b490
  [23630.791977] R10: 0030 R11: 0246 R12: 
c0306480
  [23630.791977] R13: 000b R14: 5570b6ad5b88 R15: 
5570b0ad0690

  This seems to be due to an attempt to allocate using huge pages, which
  has a fallback to allocating normal pages. There are patches in
  4.16-rc1 to suppress this spam; backport them to bionic.

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

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

[Kernel-packages] [Bug 1749250] [NEW] linux: 4.15.0-10.11 -proposed tracker

2018-02-13 Thread Seth Forshee

Public bug reported:

This bug is for tracking the 4.15.0-10.11 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

** Affects: kernel-development-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-development-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-development-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live

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

** Tags added: kernel-release-tracking-bug-live

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

** Tags added: bionic

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

** Also affects: kernel-development-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/regression-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-development-workflow
   Status: New => In Progress

** Changed in: kernel-development-workflow
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-development-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

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

Title:
  linux: 4.15.0-10.11 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status

[Kernel-packages] [Bug 1748513] Re: BUG: unable to handle kernel paging request at 00007f29ec101010

2018-02-13 Thread Simon Déziel

Unfortunately, no and this only occurred once. I'll be testing with
4.4.0-116.140 that includes a fix related to raw_sendmsg so hopefully
this will correct the problem.

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

Title:
  BUG: unable to handle kernel paging request at 7f29ec101010

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Got this bug/oops while running with the linux-image-4.4.0-113-generic
  (4.4.0-113.136) kernel from -proposed:

  BUG: unable to handle kernel paging request at 7f29ec101010
  IP: [] csum_and_copy_from_iter+0x55/0x4c0
  PGD 82fcef6f9067 PUD 2fd1615e067 PMD 2fcef77e067 PTE 82fd0009f867
  Oops: 0001 [#1] SMP 
  Modules linked in: binfmt_misc nf_log_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 
ip6table_filter ip6_tables nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_
   fjes wmi
  CPU: 39 PID: 27347 Comm: fping Not tainted 4.4.0-113-generic #136-Ubuntu
  Hardware name: Dell Inc. PowerEdge R830/0VVT0H, BIOS 1.3.4 11/09/2016
  task: 88bd1125e200 ti: 897d0285 task.ti: 897d0285
  RIP: 0010:[]  [] 
csum_and_copy_from_iter+0x55/0x4c0
  RSP: 0018:897d02853a18  EFLAGS: 00010246
  RAX: 0018 RBX: 0006 RCX: 897d02853e98
  RDX: 897d02853a94 RSI: 0040 RDI: 8afcfba4ea24
  RBP: 897d02853a80 R08:  R09: 8afcfba4ea24
  R10: 8afcfba4ea24 R11: 8afcfba4ea00 R12: 897d02853e98
  R13:  R14: 1ee730fc3e9fb34c R15: 7f29ec101008
  FS:  7f29ec282700() GS:8afd7ec4() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f29ec101010 CR3: 02fce5462000 CR4: 00360670
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Stack:
   88bd7ec07340 9772d1d7 8afcf02d8f00 897d02853aaf
   897d02853a94 01c0  1ee730fc3e9fb34c
   0040 8afcf02d8f00  897d02853d30
  Call Trace:
   [] ? __alloc_skb+0x87/0x1f0
   [] ip_generic_getfrag+0x56/0xe0
   [] raw_getfrag+0xaf/0x100
   [] __ip_append_data.isra.45+0x98a/0xb90
   [] ? raw_recvmsg+0x1c0/0x1c0
   [] ? raw_recvmsg+0x1c0/0x1c0
   [] ip_append_data.part.46+0x7a/0xe0
   [] ip_append_data+0x34/0x40
   [] raw_sendmsg+0x724/0xc00
   [] ? aa_sk_perm+0x70/0x210
   [] ? aa_sock_msg_perm+0x61/0x150
   [] inet_sendmsg+0x6b/0xa0
   [] sock_sendmsg+0x3e/0x50
   [] SYSC_sendto+0x101/0x190
   [] ? vm_mmap_pgoff+0xbb/0xe0
   [] ? __do_page_fault+0x1b4/0x400
   [] SyS_sendto+0xe/0x10
   [] entry_SYSCALL_64_fastpath+0x1c/0x93
  Code: f3 48 0f 47 de 48 85 db 0f 84 8b 01 00 00 8b 02 49 89 f9 49 89 cc 4c 8b 
71 08 89 45 c4 8b 01 a8 04 0f 85 79 01 00 00 4c 8b 79 18 <4d> 8b 6f 08 4d 29 f5 
49 39 dd 4c 0f 47 eb a8 02 0f 85 36 02 00 
  RIP  [] csum_and_copy_from_iter+0x55/0x4c0
   RSP 
  CR2: 7f29ec101010
  ---[ end trace 48102008d03cb384 ]---

  This is something new with the -proposed kernel.

  Additional information:

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

  $ apt-cache policy linux-image-4.4.0-113-generic
  linux-image-4.4.0-113-generic:
Installed: 4.4.0-113.136
Candidate: 4.4.0-113.136
Version table:
   *** 4.4.0-113.136 500
  500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-113-generic 4.4.0-113.136
  ProcVersionSignature: Ubuntu 4.4.0-113.136-generic 4.4.98
  Uname: Linux 4.4.0-113-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb  9 10:45 seq
   crw-rw 1 root audio 116, 33 Feb  9 10:45 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Fri Feb  9 13:41:20 2018
  HibernationDevice: RESUME=/dev/mapper/vghost-swap
  InstallationDate: Installed on 2017-04-01 (314 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R830
  PciMultimedia:
   
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-113-generic.efi.signed

[Kernel-packages] [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking

2018-02-13 Thread Laurent Bonnaud

** Bug watch added: Debian Bug tracker #890343
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890343

** Also affects: systemd (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890343
   Importance: Unknown
   Status: Unknown

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

Title:
  devel: consider fq_codel as the default qdisc for networking

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Unknown

Bug description:
  This was raised on the kernel-team@ mailing list, we should look at
  this if other distros are starting to move.

  ===

  Date: Tue, 24 Mar 2015 10:54:37 -0700 
 
  From: Dave Taht  
 
  To: Joseph Salisbury  
 
  Cc: Kernel Team , ubuntu-de...@lists.ubuntu.com 
 
  Subject: Re: Minutes from the Ubuntu Kernel Team meeting, 2015-03-24  
 

 
  I must confess I had hoped ubuntu would adopt fq_codel as the default 
 
  qdisc in this go-around. It is still not quite part of fedora´s   
 
  default either, but is now in arch, (and nearly everyone else 
 
  downstream from systemd), and has long been the default in openwrt,   
 
  and at this point, just requires a single sysctl to enable.   
 

 
  It certainly could use more widespread testing, perhaps in the next release?  
 

 
  d@nuc-client:~$ cat /etc/sysctl.d/10-bufferbloat.conf 
 
  net.core.default_qdisc=fq_codel

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

2018-02-13 Thread Dan Streetman

Can you also test with this kernel please:
http://people.canonical.com/~ddstreet/lp1711407/linux-image-4.13.13-00941-gf382397cf315_4.13.13-00941-gf382397cf315-26_amd64.deb

It's the same as the last one, with a ipsec/xfrm dst leak patch.

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1732990] Re: [Artful/Zesty] ACPI APEI error handling bug fixes

2018-02-13 Thread Manoj Iyer

** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Won't Fix

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

Title:
  [Artful/Zesty] ACPI APEI error handling bug fixes

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Error records which have multiple errors in them will incorrectly report all 
errors after the first one. This results in garbage non-standard error trace 
events to be generated, and for AER and MC errors there will be no kernel 
action to help recover from these errors in the AER and EDAC drivers.

  [Fix]
  Patches in Linus tree fixes this issue:
  aaf2c2fb0f51 ACPI / APEI: clear error status before acknowledging the error
  c4335fdd3822 ACPI: APEI: fix the wrong iteration of generic error status block

  [Testing]
  Insert a e1000 pcie card into the system, run the following command that 
should generate PCIe correctable errors, you will see only the first error in 
each GHES report go to the AER driver rather than all errors from the GHES 
reports.

  $ sudo setpci -s 0002:00:00.0 0x70c.l=0x00808000;sudo setpci -s
  0002:00:00.0 CAP_EXP+0x10.B=0x4b;sleep 1;sudo setpci -s 0002:00:00.0
  CAP_EXP+0x10.B=0x48

  Where "0002:00:00.0" being the root hub for the card.

  Used JTAG to trigger multiple concurrent errors, and observed that all
  errors were parsed, instead of just the first one. As mentioned in
  comment #3. So, the poster of comment #3 will do the verification once
  the patch lands in -proposed.

  [Regression Potential]
  The two patches to ACPI APEI driver was cleanly cherry picked from linus's 
tree and applied to Artful and Zesty. The patches were tested on QDF2400 
platform where it was found to issue and don't introduce any regressions.

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

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

[Kernel-packages] [Bug 1732990] Re: [Artful/Zesty] ACPI APEI error handling bug fixes

2018-02-13 Thread Andrew Cloke

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

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

Title:
  [Artful/Zesty] ACPI APEI error handling bug fixes

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  Error records which have multiple errors in them will incorrectly report all 
errors after the first one. This results in garbage non-standard error trace 
events to be generated, and for AER and MC errors there will be no kernel 
action to help recover from these errors in the AER and EDAC drivers.

  [Fix]
  Patches in Linus tree fixes this issue:
  aaf2c2fb0f51 ACPI / APEI: clear error status before acknowledging the error
  c4335fdd3822 ACPI: APEI: fix the wrong iteration of generic error status block

  [Testing]
  Insert a e1000 pcie card into the system, run the following command that 
should generate PCIe correctable errors, you will see only the first error in 
each GHES report go to the AER driver rather than all errors from the GHES 
reports.

  $ sudo setpci -s 0002:00:00.0 0x70c.l=0x00808000;sudo setpci -s
  0002:00:00.0 CAP_EXP+0x10.B=0x4b;sleep 1;sudo setpci -s 0002:00:00.0
  CAP_EXP+0x10.B=0x48

  Where "0002:00:00.0" being the root hub for the card.

  Used JTAG to trigger multiple concurrent errors, and observed that all
  errors were parsed, instead of just the first one. As mentioned in
  comment #3. So, the poster of comment #3 will do the verification once
  the patch lands in -proposed.

  [Regression Potential]
  The two patches to ACPI APEI driver was cleanly cherry picked from linus's 
tree and applied to Artful and Zesty. The patches were tested on QDF2400 
platform where it was found to issue and don't introduce any regressions.

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

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

[Kernel-packages] [Bug 1748517] Re: Ubuntu 18.04 - Include latest ibmvnic fixes in Ubuntu kernel

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

** Tags added: kernel-da-key

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

Title:
  Ubuntu 18.04 - Include latest ibmvnic fixes in Ubuntu kernel

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  We have a number of patches to submit to Canonical for inclusion in
  the their release kernel for Ubuntu 18.04.

  So far, most of these patches are upstream in Linus' tree, with some
  in Dave M's net-next tree.  According to the ubuntu-bionic tree, the
  latest patch included is 8388a6cf ("ibmvnic: Set state UP").  If
  that's true, we'll need about 15 or more patches.  There may be more
  coming down the pipe soon as well.

  Here is a tentative patch list with commit hash and name:

  1. 69d08dc Allocate and request vpd in init_resources
  2. e791380 Revert to previous mtu when unsupported value requested
  3. 896d869 Modify buffer size and number of queues on failover
  4. a0dca10 Fix IPv6 packet descriptors
  5. f689794 Fix IP offload control buffer
  6. 3d16613 Fix pending MAC address changes
  7. 09fb35ead58c Don't handle RX interrupts when not up
  8. 4eb50ceb5c15 Include header descriptor support for ARP packets
  9. 269431e737d2 Increase maximum number of RX/TX queues
  10. d45cc3a43c43 Rename IBMVNIC_MAX_TX_QUEUES to IBMVNIC_MAX_QUEUES
  11. f743106ec140 fix dma_mapping_error call
  12. 4e6759be28e4 Feature implementation of Vital Product Data (VPD)?
  13. 37798d021131 Add vnic client data to login buffer
  14. 2a1bf597 Fix failover error path for non-fatal resets
  15. c26eba03e407 Update reset infrastructure to support tunable parameters
  16. aa0bf8510dac Let users change net device features
  17. fdb061056f57 Enable TSO support
  18. 154820563dd4 Enable scatter-gather support

  These should apply cleanly, but I'll check on that.

  Thanks!

  
  Here is a tarball of patches.  I also included this patch:

  https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-
  next.git/commit/?id=f813614f531114db796ad66ced75c5dc8db7aa3a

  
  Additional patches that we would like to have included:

  https://marc.info/?l=linux-netdev=151803103818174=2
  ("[PATCH net-next] ibmvnic: queue reset when CRQ gets closed during reset")

  https://marc.info/?l=linux-netdev=151796813926975=2
  ("[PATCH net] ibmvnic: Fix rx queue cleanup for non-fatal resets")

  https://marc.info/?l=linux-netdev=151631440609769=2
  ("[PATCH net v2 1/3] ibmvnic: Modify buffer size and number of queues on 
failover")

  https://marc.info/?l=linux-netdev=151631444309775=2
  ("[PATCH net v2 2/3] ibmvnic: Revert to previous mtu when unsupported value 
requested")

  https://marc.info/?l=linux-netdev=151631448809782=2
  ("[PATCH net v2 3/3] ibmvnic: Allocate and request vpd in init_resources")

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=d45cc3a43c43f867668bdd7ace12b1e6aa68bf46
  ("ibmvnic: Rename IBMVNIC_MAX_TX_QUEUES to IBMVNIC_MAX_QUEUES")

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=269431e737d29da0f496b60188a580822d290a37
  ("ibmvnic: Increase maximum number of RX/TX queues")

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next.git/commit/?id=4eb50ceb5c156a166c0b00ac27f0ff3a0943cdfb
  ("ibmvnic: Include header descriptor support for ARP packets")

  https://marc.info/?l=linux-netdev=151796813526938=2
   [PATCH net] ibmvnic: Ensure that buffers are NULL after free

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1748517/+subscriptions

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

[Kernel-packages] [Bug 1748505] Re: Boot failed with hard LOCKUP linux-image-4.4.0-112

Would it be possible for you to test the latest upstream stable kernel?
Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the
latest v4.4 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
"Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.115

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

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

** Tags added: kernel-da-key

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

Title:
  Boot failed with hard LOCKUP linux-image-4.4.0-112

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Booting this kernel ended with

  [35.111831] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1
  [36.073026] NMI watchdog: Watchdog detected hard LOCKUP on cpu 2
  [36.153549] NMI watchdog: Watchdog detected hard LOCKUP on cpu 0
  [36.451526] NMI watchdog: Watchdog detected hard LOCKUP on cpu 3 

  Booting previous kernel linux-image-4.4.0-109-generic is working
  smoothly as well as previous ones.

  cat /proc/version_signature = Ubuntu 4.4.0-109.132-generic 4.4.98

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dh 2583 F pulseaudio
   /dev/snd/controlC1:  dh 2583 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb  9 19:02:26 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  HibernationDevice: RESUME=UUID=103ed14e-e6b6-49d5-a28f-020343e6a118
  InstallationDate: Installed on 2013-10-13 (1580 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  MachineType: Dell Inc. Latitude E7440
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=8a01ac20-42e5-49f3-b385-674e05cd8d7c ro quiet splash 
acpi_rev_override=1
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-109-generic N/A
   linux-backports-modules-4.4.0-109-generic  N/A
   linux-firmware 1.157.15
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-10-05 (491 days ago)
  dmi.bios.date: 12/15/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A23
  dmi.board.name: 0JNYGR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA23:bd12/15/2017:svnDellInc.:pnLatitudeE7440:pvr00:rvnDellInc.:rn0JNYGR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1748513] Re: BUG: unable to handle kernel paging request at 00007f29ec101010

Do you have a way to reproduce this bug?  If so, we can bisect down to
the commit that introduced it.

** Tags added: kernel-da-key needs-bisect

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

Title:
  BUG: unable to handle kernel paging request at 7f29ec101010

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Got this bug/oops while running with the linux-image-4.4.0-113-generic
  (4.4.0-113.136) kernel from -proposed:

  BUG: unable to handle kernel paging request at 7f29ec101010
  IP: [] csum_and_copy_from_iter+0x55/0x4c0
  PGD 82fcef6f9067 PUD 2fd1615e067 PMD 2fcef77e067 PTE 82fd0009f867
  Oops: 0001 [#1] SMP 
  Modules linked in: binfmt_misc nf_log_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 
ip6table_filter ip6_tables nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_
   fjes wmi
  CPU: 39 PID: 27347 Comm: fping Not tainted 4.4.0-113-generic #136-Ubuntu
  Hardware name: Dell Inc. PowerEdge R830/0VVT0H, BIOS 1.3.4 11/09/2016
  task: 88bd1125e200 ti: 897d0285 task.ti: 897d0285
  RIP: 0010:[]  [] 
csum_and_copy_from_iter+0x55/0x4c0
  RSP: 0018:897d02853a18  EFLAGS: 00010246
  RAX: 0018 RBX: 0006 RCX: 897d02853e98
  RDX: 897d02853a94 RSI: 0040 RDI: 8afcfba4ea24
  RBP: 897d02853a80 R08:  R09: 8afcfba4ea24
  R10: 8afcfba4ea24 R11: 8afcfba4ea00 R12: 897d02853e98
  R13:  R14: 1ee730fc3e9fb34c R15: 7f29ec101008
  FS:  7f29ec282700() GS:8afd7ec4() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f29ec101010 CR3: 02fce5462000 CR4: 00360670
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Stack:
   88bd7ec07340 9772d1d7 8afcf02d8f00 897d02853aaf
   897d02853a94 01c0  1ee730fc3e9fb34c
   0040 8afcf02d8f00  897d02853d30
  Call Trace:
   [] ? __alloc_skb+0x87/0x1f0
   [] ip_generic_getfrag+0x56/0xe0
   [] raw_getfrag+0xaf/0x100
   [] __ip_append_data.isra.45+0x98a/0xb90
   [] ? raw_recvmsg+0x1c0/0x1c0
   [] ? raw_recvmsg+0x1c0/0x1c0
   [] ip_append_data.part.46+0x7a/0xe0
   [] ip_append_data+0x34/0x40
   [] raw_sendmsg+0x724/0xc00
   [] ? aa_sk_perm+0x70/0x210
   [] ? aa_sock_msg_perm+0x61/0x150
   [] inet_sendmsg+0x6b/0xa0
   [] sock_sendmsg+0x3e/0x50
   [] SYSC_sendto+0x101/0x190
   [] ? vm_mmap_pgoff+0xbb/0xe0
   [] ? __do_page_fault+0x1b4/0x400
   [] SyS_sendto+0xe/0x10
   [] entry_SYSCALL_64_fastpath+0x1c/0x93
  Code: f3 48 0f 47 de 48 85 db 0f 84 8b 01 00 00 8b 02 49 89 f9 49 89 cc 4c 8b 
71 08 89 45 c4 8b 01 a8 04 0f 85 79 01 00 00 4c 8b 79 18 <4d> 8b 6f 08 4d 29 f5 
49 39 dd 4c 0f 47 eb a8 02 0f 85 36 02 00 
  RIP  [] csum_and_copy_from_iter+0x55/0x4c0
   RSP 
  CR2: 7f29ec101010
  ---[ end trace 48102008d03cb384 ]---

  This is something new with the -proposed kernel.

  Additional information:

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

  $ apt-cache policy linux-image-4.4.0-113-generic
  linux-image-4.4.0-113-generic:
Installed: 4.4.0-113.136
Candidate: 4.4.0-113.136
Version table:
   *** 4.4.0-113.136 500
  500 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-113-generic 4.4.0-113.136
  ProcVersionSignature: Ubuntu 4.4.0-113.136-generic 4.4.98
  Uname: Linux 4.4.0-113-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Feb  9 10:45 seq
   crw-rw 1 root audio 116, 33 Feb  9 10:45 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  Date: Fri Feb  9 13:41:20 2018
  HibernationDevice: RESUME=/dev/mapper/vghost-swap
  InstallationDate: Installed on 2017-04-01 (314 days ago)
  InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 002: ID 8087:8002 Intel Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 413c:a001 Dell Computer Corp. Hub
   Bus 001 Device 002: ID 8087:800a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. PowerEdge R830
  PciMultimedia:
   
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-113-generic.efi.signed 
root=/dev/mapper/vghost-root

[Kernel-packages] [Bug 1749040] Re: fails to boot on Cavium ThunderX CRB

2018-02-13 Thread dann frazier

A couple more tests - rebuilding the failing kernel w/ the updated GCC also 
shows a failure. Rebuilding the newer artful-proposed kernel (35.39) w/ the 
same toolchain does not show a failure.
Here's the current status:

| 4.13.0-33.36~16.04.1 | 5.4.0-6ubuntu1~16.04.8 | Fails |
| 4.13.0-33.36~16.04.1 | 5.4.0-6ubuntu1~16.04.9 | Fails |
| 4.13.0-33.36 | 7.2.0-8ubuntu3.1   | OK|
| 4.13.0-35.39 | 7.2.0-8ubuntu3.2   | OK|
| 4.13.0-35.39 | 5.4.0-6ubuntu1~16.04.9 | OK|
| 4.13.0-35.39~16.04.1 | 5.4.0-6ubuntu1~16.04.9 | OK|


** Attachment added: "4.13.0-33.36~16.04.1 built w/ gcc 5.4.0-6ubuntu1~16.04.9 
console log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749040/+attachment/5054449/+files/4.13.0-33.36~16.04.1_5.4.0-6ubuntu1~16.04.9.log

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

Title:
  fails to boot on Cavium ThunderX CRB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While regression testing the current linux-hwe proposed kernel
  (4.13.0-33.36~16.04.1), I found that it fails to boot on a Cavium
  ThunderX CRB. I've rebooted twice since upgrading from the current
  -updates kernel, and it's failed to boot both times, with different
  failure modes.

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

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

[Kernel-packages] [Bug 1674568] Re: depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No such file or directory

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

Title:
  depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic:
  No such file or directory

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Please affect that report to the real package; i've chosen apt by
  default as i've no idea about the faulty one.

  Doing some daily upgrades as usual, and have seen that curious error
  while setting 'initramfs':

  Setting up linux-firmware (1.164) ...
  update-initramfs: Generating /boot/initrd.img-4.10.0-14-generic
  update-initramfs: Generating /boot/initrd.img-4.10.0-13-generic
  update-initramfs: Generating /boot/initrd.img-4.8.0-25-generic
  WARNING: missing /lib/modules/4.8.0-25-generic
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-25-generic: No 
such file or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_B55FjX/lib/modules/4.8.0-25-generic/modules.order: No such 
file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_B55FjX/lib/modules/4.8.0-25-generic/modules.builtin: No 
such file or directory
  update-initramfs: Generating /boot/initrd.img-4.8.0-0-generic
  WARNING: missing /lib/modules/4.8.0-0-generic
  Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/4.8.0-0-generic: No such 
file or directory
  depmod: FATAL: could not search modules: No such file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_1ESFuC/lib/modules/4.8.0-0-generic/modules.order: No such 
file or directory
  depmod: WARNING: could not open 
/var/tmp/mkinitramfs_1ESFuC/lib/modules/4.8.0-0-generic/modules.builtin: No 
such file or directory

  That ZZ installation indeed only has 4.10 kernels installed, and is
  often checked for cleaning (autoremove/bleachbit). Packages are always
  purged when removed.

  So i wonder why and which process/script has left a crappy /boot/ list
  of initrd.img-4.8* to produce the errors above.

  oem@u64:~$ ls -la /boot/
  total 142448
  drwxr-xr-x  4 root root 4096 Mar 21 06:24 .
  drwxr-xr-x 24 root root 4096 Mar 20 19:13 ..
  -rw-r--r--  1 root root  1442575 Mar  9 14:16 abi-4.10.0-13-generic
  -rw-r--r--  1 root root  1442782 Mar  9 21:30 abi-4.10.0-14-generic
  -rw-r--r--  1 root root   204890 Mar  9 14:16 config-4.10.0-13-generic
  -rw-r--r--  1 root root   204890 Mar  9 21:30 config-4.10.0-14-generic
  drwxr-xr-x  3 root root 4096 Mar 20  2016 efi
  drwxr-xr-x  5 root root 4096 Mar 20 19:17 grub
  -rw-r--r--  1 root root 49676849 Mar 21 06:24 initrd.img-4.10.0-13-generic
  -rw-r--r--  1 root root 49672961 Mar 21 06:23 initrd.img-4.10.0-14-generic
  -rw-r--r--  1 root root 10017268 Mar 21 06:24 initrd.img-4.8.0-0-generic
  -rw-r--r--  1 root root 10017066 Mar 21 06:24 initrd.img-4.8.0-25-generic
  -rw-r--r--  1 root root   182704 Jan 28  2016 memtest86+.bin
  -rw-r--r--  1 root root   184380 Jan 28  2016 memtest86+.elf
  -rw-r--r--  1 root root   184840 Jan 28  2016 memtest86+_multiboot.bin
  -rw---  1 root root  3715891 Mar  9 14:16 System.map-4.10.0-13-generic
  -rw---  1 root root  3716749 Mar  9 21:30 System.map-4.10.0-14-generic
  -rw---  1 root root  7558928 Mar  9 14:16 vmlinuz-4.10.0-13-generic
  -rw---  1 root root  7563024 Mar  9 21:30 vmlinuz-4.10.0-14-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-firmware 1.164
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 21 06:28:04 2017
  Dependencies:

  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1749221] Re: kernel crash / BUG: unable to handle kernel paging request at fffffe3ed8000020

Can you reproduce the bug, or was it a one time event?

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

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

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

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

** Tags added: kernel-da-key

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

Title:
   kernel crash / BUG: unable to handle kernel paging request at
  fe3ed820

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

Bug description:
  Booted under maas in rescue mode system console has the attached failure.
  First bit is

  [ 440.196466] BUG: unable to handle kernel paging request at
  fe3ed820

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-generic (not installed)
  ProcVersionSignature: User Name 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116, 33 Feb 13 15:32 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed 
with exit code 1:
  CRDA: N/A
  Date: Tue Feb 13 15:34:40 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=username/amd64/generic/xenial/daily/boot-kernel 
nomodeset 
root=squash:http://10.247.16.6:5248/images/username/amd64/generic/xenial/daily/squashfs
 ro ip=hostname:BOOTIF ip6=off overlayroot=tmpfs 
overlayroot_cfgdisk=disabled cc:{datasource_list: [MAAS]}end_cc 
cloud-config-url=http://10.247.16.6:5240/MAAS/metadata/latest/by-id/sbgyxn/?op=get_preseed
 apparmor=0 log_host=10.247.16.6 log_port=514 --- console=ttyS1 
BOOTIF=01-ec:b1:d7:7f:2a:6c
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/05/2015
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd03/05/2015:svnHP:pnProLiantDL360Gen9:pvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1749230] Re: Cannot detect SD card at os init on ASUS T101HA-GR030T

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/

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

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

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

Title:
  Cannot detect SD card at os init on ASUS T101HA-GR030T

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I am using xubuntu 17.10 on ASUS T101HA-GR030T and different kind of SD cards 
(everything working fine on Windows) :
  1) No one is detected if they are plugged before to load Xubuntu.
  2) Some are detected if plugged when OS is ready : ex : SAMSUNG 32 EVO. 
  3) Some are never detected : ex : TOSHIBA 32 GO and SANDISK 32 GO. 

  For informations,

  4) It is impossible to use the microphone (looking locked) on the same
  computer. Work fine with Windows. I don't know what to do. Blocked.

  5) Impossible to log on with WIFI on a NETGEAR router with Xubuntu
  only. Under investigations.

  Sorry about my poor "Frenglish".

  See you later.

  ==
  Ubuntu 4.13.0-32.35-generic 4.13.13
  ==
  00:00.0 Host bridge [0600]: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [8086:2280] (rev 36)
Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series SoC Transaction Register [1043:13a0]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

  00:03.0 Multimedia controller [0480]: Intel Corporation Atom/Celeron/Pentium 
Processor x5-E8000/J3xxx/N3xxx Series Imaging Unit [8086:22b8] (rev 36)
Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series Imaging Unit [1043:13a0]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- 
SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <512ns, L1 <16us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp-
LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ 
DLActive+ BWMgmt+ ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- 
Surprise-
Slot #0, PowerLimit 10.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- 
LinkChg-
Control: AttnInd Unknown, PwrInd Unknown, Power- 
Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ 
Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ 
CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF 
Not Supported ARIFwd-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis+, LTR+, 
OBFF Disabled ARIFwd-
LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-
 Transmit Margin: Normal Operating Range, 
EnterModifiedCompliance- ComplianceSOS-

[Kernel-packages] [Bug 1748393] Re: No successful resume from hibernate beyond kernel version 4.13.0-21

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/

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

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

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

Title:
  No successful resume from hibernate beyond kernel version 4.13.0-21

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I used hibernate (with uswsusp) in 17.10 successfully until kernel
  4.13.0-21. I cannot resume any more with kernels 25 or 32. I can see
  that suspend works fine, resuming the system works fine too (reading
  the image is successful according to uswsusp output) until the point
  where GDM should come up but the screen just stays black. I tried
  reaching the machine via SSH but it's not reachable.

  Tested on Lenovo T560 and T530 without discrete graphics.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   livewire   1909 F...m pulseaudio
   /dev/snd/controlC0:  livewire   1909 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=f16699b7-6fc8-4762-984c-dfee6eb58275
  InstallationDate: Installed on 2016-03-01 (710 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160228)
  MachineType: LENOVO 20FHCTO1WW
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=/dev/sda2 ro quiet loglevel=3 rd.systemd.show_status=auto 
rd.udev.log-priority=3 nosplash noplymouth rootfstype=ext4 pcie_aspm=force 
i915.lvds_downclock=1 drm.vblankoffdelay=1 i915.fastboot=1 i915.enable_psr=1
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.3
  Tags:  wayland-session artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-09-09 (153 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 09/29/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET35W (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET35W(1.22):bd09/29/2017:svnLENOVO:pn20FHCTO1WW:pvrThinkPadT560:rvnLENOVO:rn20FHCTO1WW:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T560
  dmi.product.name: 20FHCTO1WW
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1748342] Re: cgroup: remove cgroup directory leading kernel crash in kill_css

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

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

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

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

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

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

Title:
  cgroup: remove cgroup directory leading kernel crash in kill_css

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

Bug description:
  We got feedback from customer that cvm(cloud virtual machine) crashed when 
using kubelet updating container-service in ubuntu xenial. Logs show as follow. 
  We find a patch (commit 33c35aa4817864e056fd772230b0c6b552e36ea2) in linux 
mainline, which can indeed fix this bug. But ubuntu-xenial.git has not merged 
it yet. 

  Do you guys have a plan for merging?

  --panic log-
  [2018-02-02 10:21:48][4397731.721563] BUG: unable to handle kernel paging 
request at 0001005c
  [2018-02-02 10:40:50][4397731.722666] IP: css_clear_dir+0x5/0x70
  [2018-02-02 10:40:50][4397731.723261] PGD a12b067 
  [2018-02-02 10:40:50][4397731.723261] PUD 0 
  [2018-02-02 10:40:50][4397731.723628] 
  [2018-02-02 10:40:50][4397731.724004] Oops:  [#1] SMP
  [2018-02-02 10:40:50][4397731.724004] Modules linked in: xt_statistic 
nf_conntrack_netlink ebt_ip ebtable_filter ebtables veth xt_set ip_set_hash_net 
ip_set nfnetlink xt_nat xt_recent xt_mark ipt_REJ[2018-02-02 10:40:50]ECT 
nf_reject_ipv4 xt_tcpudp xt_comment ipt_MASQUERADE nf_nat_masquerade_ipv4 
xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
xt_addrtype iptable_fil[2018-02-02 10:40:50]ter ip_tables xt_conntrack x_tables 
nf_nat nf_conntrack br_netfilter bridge stp llc aufs ppdev sb_edac edac_core 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel joydev input_le[2018-02-02 
10:40:50]ds serio_raw parport_pc parport i2c_piix4 mac_hid ib_iser rdma_cm 
iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi autofs4 btrfs raid10 raid456 a[2018-02-02 
10:40:50]sync_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid1 raid0 multipath
  [2018-02-02 10:40:50][4397731.724004]  linear cirrus ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt aesni_intel fb_sys_fops aes_x86_64 
crypto_simd cryptd glue_helper psmouse virtio_blk virtio_n[2018-02-02 
10:40:50]et drm pata_acpi floppy
  [2018-02-02 10:40:50][4397731.724004] CPU: 0 PID: 23347 Comm: kubelet Not 
tainted 4.10.0-32-generic #36~16.04.1-Ubuntu
  [2018-02-02 10:40:50][4397731.724004] Hardware name: Bochs Bochs, BIOS Bochs 
01/01/2011
  [2018-02-02 10:40:50][4397731.724004] task: 92abde59 task.stack: 
baa94165c000
  [2018-02-02 10:40:50][4397731.724004] RIP: 0010:css_clear_dir+0x5/0x70
  [2018-02-02 10:40:50][4397731.724004] RSP: 0018:baa94165fe10 EFLAGS: 
00010206
  [2018-02-02 10:40:50][4397731.724004] RAX: 47fd40005d7b RBX: 
ffe8 RCX: 92abffc0fcec
  [2018-02-02 10:40:50][4397731.724004] RDX: 9b070800 RSI: 
0206 RDI: ffe8
  [2018-02-02 10:40:50][4397731.724004] RBP: baa94165fe20 R08: 
c8b18701 R09: 000180220017
  [2018-02-02 10:40:50][4397731.724004] R10: 92abc8b187f8 R11: 
92abf7751d00 R12: 92abd5601000
  [2018-02-02 10:40:50][4397731.724004] R13:  R14: 
92abd5601150 R15: 
  [2018-02-02 10:40:50][4397731.724004] FS:  7f6f92ffd700() 
GS:92abffc0() knlGS:
  [2018-02-02 10:40:50][4397731.724004] CS:  0010 DS:  ES:  CR0: 
80050033
  [2018-02-02 10:40:50][4397731.724004] CR2: 0001005c CR3: 
280cb000 CR4: 000406f0
  [2018-02-02 10:40:50][4397731.724004] Call Trace:
  [2018-02-02 10:40:50][4397731.724004]  ? kill_css+0x12/0x60
  [2018-02-02 10:40:50][4397731.724004]  cgroup_destroy_locked+0xa5/0xf0
  [2018-02-02 10:40:50][4397731.724004]  cgroup_rmdir+0x2c/0x90
  [2018-02-02 10:40:50][4397731.724004]  kernfs_iop_rmdir+0x4d/0x80
  [2018-02-02 10:40:50][4397731.724004]  vfs_rmdir+0xb4/0x130
  [2018-02-02 10:40:50][4397731.724004]  do_rmdir+0x1c7/0x1e0
  [2018-02-02 10:40:50][4397731.724004]  SyS_unlinkat+0x22/0x30
  [2018-02-02 10:40:50][4397731.724004]  entry_SYSCALL_64_fastpath+0x1e/0xad
  [2018-02-02 10:40:50][4397731.724004] RIP: 0033:0x481bd4
  [2018-02-02 10:40:50][4397731.724004] RSP: 002b:00c422893af0 EFLAGS: 
0246 ORIG_RAX: 0107
  [2018-02-02 10:40:50][4397731.724004] RAX: ffda RBX: 
 RCX: 00481bd4
  [2018-02-02 10:40:50][4397731.724004] RDX: 0200 RSI: 
00c421c7ef00 RDI: ff9c
  [2018-02-02

[Kernel-packages] [Bug 1748380] Re: [Notebook W65_67SF] hibernate/resume failure

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16-rc1/

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

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

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

Title:
  [Notebook W65_67SF] hibernate/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  .

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35 [modified: 
boot/vmlinuz-4.13.0-32-generic]
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1443 F pulseaudio
jwp1996 F pulseaudio
   /dev/snd/controlC1:  gdm1443 F pulseaudio
jwp1996 F pulseaudio
  Date: Fri Feb  9 08:11:57 2018
  DuplicateSignature: hibernate/resume:Notebook W65_67SF:1.05.01
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=2f57605b-1746-435c-a0af-9242a675f7e8
  InstallationDate: Installed on 2018-02-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
  InterpreterPath: /usr/bin/python3.6
  MachineType: Notebook W65_67SF
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  Title: [Notebook W65_67SF] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 07/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.01
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SF
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.01:bd07/24/2015:svnNotebook:pnW65_67SF:pvrNotApplicable:rvnNotebook:rnW65_67SF:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W65_67SF
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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

[Kernel-packages] [Bug 1748395] Re: btrfs related tests in ubuntu_ecryptfs failed on Precise amd64 / i386

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

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

** Tags added: kernel-da-key

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

Title:
  btrfs related tests in ubuntu_ecryptfs failed on Precise amd64 / i386

Status in linux package in Ubuntu:
  Triaged

Bug description:
  This issue can be reproduced in 3.13.0-142 in proposed and 3.13.0-141.
  So it should not be considered as a regression.

  We didn't have this issue before, until I'm testing 3.13 Precise LTS
  kernel on the systems (201307-13930 - i386 and 201308-14073 - amd64)
  in Cert lab instead of using our regular regression-testing test pool
  from kernel team this cycle.

  All btrfs related tests in ubuntu_ecryptfs failed.

  miscdev-bad-count.sh.btrfs
  extend-file-random.sh.btrfs
  trunc-file.sh.btrfs
  directory-concurrent.sh.btrfs
  file-concurrent.sh.btrfs
  lp-994247.sh.btrfs
  llseek.sh.btrfs
  lp-469664.sh.btrfs
  lp-524919.sh.btrfs
  lp-509180.sh.btrfs
  lp-613873.sh.btrfs
  lp-745836.sh.btrfs
  lp-870326.sh.btrfs
  lp-885744.sh.btrfs
  lp-926292.sh.btrfs
  inotify.sh.btrfs
  mmap-bmap.sh.btrfs
  mmap-close.sh.btrfs
  mmap-dir.sh.btrfs
  read-dir.sh.btrfs
  setattr-flush-dirty.sh.btrfs
  inode-race-stat.sh.btrfs
  lp-911507.sh.btrfs
  lp-561129.sh.btrfs
  mknod.sh.btrfs
  link.sh.btrfs
  xattr.sh.btrfs
  namelen.sh.btrfs

  The output is not really helpful, it's just saying that the return value is 
1, like:
  03:37:47 DEBUG| Running 'tests/run_one.sh -K -t extend-file-random.sh -b 
100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs'
  03:37:59 ERROR| Exception escaping from test:
  Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
  _call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in 
_call_test_function
  return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
  postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in 
_call_run_once
  self.run_once(*args, **dargs)
File 
"/home/ubuntu/autotest/client/tests/ubuntu_ecryptfs/ubuntu_ecryptfs.py", line 
45, in run_once
  self.results = utils.system_output(cmd, retain_output=True)
File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in 
system_output
  verbose=verbose, args=args).stdout
File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run
  "Command returned non-zero exit status")
  CmdError: Command  failed, rc=1, Command returned 
non-zero exit status
  * Command: 
  tests/run_one.sh -K -t extend-file-random.sh -b 100 -D /mnt/image -l
  /mnt/lower -u /mnt/upper -f btrfs
  Exit status: 1
  Duration: 12.1887788773

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

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

[Kernel-packages] [Bug 1748470] Re: Spectre V2 : System may be vulnerable to spectre v2

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

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

** Tags added: pti

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

Title:
  Spectre V2 : System may be vulnerable to spectre v2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hello,

  dmesg:
  [ 1813.660535] vboxdrv: loading out-of-tree module taints kernel.
  [ 1813.660542] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.660552] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1813.661206] vboxdrv: module verification failed: signature and/or required 
key missing - tainting kernel
  [ 1813.680341] vboxdrv: Found 4 processor cores
  [ 1813.697413] vboxdrv: TSC mode is Invariant, tentative frequency 1496590422 
Hz
  [ 1813.697415] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1813.706824] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.706832] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1813.707367] VBoxNetFlt: Successfully started.
  [ 1813.716935] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.716943] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1813.718033] VBoxNetAdp: Successfully started.
  [ 1813.730511] Spectre V2 : System may be vulnerable to spectre v2
  [ 1813.730518] vboxpci: loading module not compiled with retpoline compiler.
  [ 1813.731043] VBoxPciLinuxInit
  [ 1813.735258] vboxpci: IOMMU not found (not registered)
  [ 1818.059815] VBoxPciLinuxLinuxUnload
  [ 1818.182382] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.182394] vboxdrv: loading module not compiled with retpoline compiler.
  [ 1818.203403] vboxdrv: Found 4 processor cores
  [ 1818.225454] vboxdrv: TSC mode is Invariant, tentative frequency 1496570131 
Hz
  [ 1818.225457] vboxdrv: Successfully loaded version 5.2.6_Ubuntu (interface 
0x0029)
  [ 1818.239394] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.239403] vboxnetflt: loading module not compiled with retpoline 
compiler.
  [ 1818.240180] VBoxNetFlt: Successfully started.
  [ 1818.251133] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.251143] vboxnetadp: loading module not compiled with retpoline 
compiler.
  [ 1818.251726] VBoxNetAdp: Successfully started.
  [ 1818.263523] Spectre V2 : System may be vulnerable to spectre v2
  [ 1818.263530] vboxpci: loading module not compiled with retpoline compiler.
  [ 1818.264039] VBoxPciLinuxInit
  [ 1818.266382] vboxpci: IOMMU not found (not registered)
  [ 1857.952441] SUPR0GipMap: fGetGipCpu=0xb
  [ 1859.046216] vboxdrv:  VMMR0.r0
  [ 1859.301126] vboxdrv:  VBoxDDR0.r0

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-9-generic 4.15.0-9.10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1849 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1849 F pulseaudio
  CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME
  Date: Fri Feb  9 13:07:10 2018
  InstallationDate: Installed on 2017-10-13 (119 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-9-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-9-generic N/A
   linux-backports-modules-4.15.0-9-generic  N/A
   linux-firmware1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

-- 
Mailing list:

[Kernel-packages] [Bug 1676912] Re: Kernel 4.9+ regression: Suspend - Freezing of tasks failed

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

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

Title:
  Kernel 4.9+ regression: Suspend - Freezing of tasks failed

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu
  Gnome 17.04 and since then sometimes my Laptop won't suspend when I
  close the lid. The power led does not blink like it is supposed to do
  and when I open the Laptop the lockscreen appears but freezes after a
  short time, followed by a blackscreen until eventually it reappears
  and allows me to unlock it. After that certain application can not be
  started anymore and would freeze if they were running before. These
  include Chrome, Gedit and Gnome System Monitor for example. Also my
  Laptop will not connect to my WLAN until I restart it.

  In syslog I found the line:

  "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to
  freeze, wq_busy=0):"

  According to syslog

  network-nanaeger
  whoopsie
  cups-browsed
  wpa-supplicant
  geoclue
  packagekitd
  several evolution-related processes
  goa-daemon
  gnome-software
  geary
  dropbox
  deja-dup-monitor

  are responsible.
  I tried disabling some of them, but it did not solve the problem.

  Update: I tested different Kernel versions in the last days. So far
  there were no issues with suspend/resume using Kernel 4.8 and 4.9. The
  problem is present in 4.10 and 4.11.

  Update 2: I just encountered this issue with Kernel 4.9.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-19
  ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3
  Uname: Linux 4.10.0-14-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Mar 28 16:27:34 2017
  InstallationDate: Installed on 2017-03-24 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 80J8
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed 
root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: B8CN31WW(V2.09)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Paganini
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 3 11
  dmi.modalias: 
dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311:
  dmi.product.name: 80J8
  dmi.product.version: Lenovo Yoga 3 11
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1676918] Re: Kernel 4.10+ regression: blackscreen when trying to resume from suspend

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

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

** Changed in: gnome-power-manager (Ubuntu)
   Status: New => 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/1676918

Title:
  Kernel 4.10+ regression: blackscreen when trying to resume from
  suspend

Status in gnome-power-manager package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When trying to resume after suspending my Lenovo Yoga 3 11, sometimes
  the screen remains black. The power LED switches from blinking to
  continuous light like it should but nothing else happens. The system
  does not react to anything. I tried to find something in the logs, but
  at least kern.log syslog and xorg.log never have any entries from this
  event.

  This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and
  Wayland.

  I'm currently testing Kernel 4.8 from the mainline ppa because of this
  other suspend resume bug, that appeared only with 17.04:

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912

  Update: So far I did not encounter any issues with suspend/resume with
  Kernel 4.8 and 4.9. This seems to be a regression in 4.10.

  ---
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-03-24 (4 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  Package: systemd 232-19
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Tags:  zesty wayland-session
  Uname: Linux 4.8.17-040817-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  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-power-manager/+bug/1676918/+subscriptions

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

[Kernel-packages] [Bug 1748373] Re: Resume from hibernate fails on latest kernels