[Kernel-packages] [Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

[aproposnix]

@jsalisbury

Sorry for my ignorance but could you help me understand something?

In the past you were putting the kernels in the root folder. This time
there were no kernels in the root folder.  I assumed that I should go to
the folder with the same commit number
(b1b38278e12b04cf9a227f6af2c24651cf6e8a85).

You then mention that I must install the linux-extra package but there's
no extras package in that folder.

Could you please clarify the steps I need to take?

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

Title:
  Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

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

Bug description:
  When I install Ubuntu 16.04 on my computer the screen goes blank at
  login. I can blindly login and it boots but I cannot use the display
  (external monitor through HDMI).

  I've looked online for an answer to this issue but could not find a
  solution.  However, many people report this issue in forums with the
  4.4x kernel.

  On my main computer, I upgraded from 14.04 to 16.04.1. On this
  computer I was able to switch back to the 3.13 kernel which *does
  work*.

  On the same computer, if I use a 16.04 live CD, it does the same
  thing.  The screen goes blank.

  UEFI may be part of the issue as well.  I have it disabled in bios
  (set to legacy mode) but when I first boot, it seems to go into UEFI
  mode first and then, after rebooting with  it shows
  me the list of kernels. I can select the kernel from there but if I
  use a 4.4x kernel, it blanks out at encryption passphrase screen.

  There are also people with similar issues on AskUbuntu.

  Here's some basic HW info.  If you require more, please ask.

  sudo lshw | head
  zbox
  description: Notebook
  product: ZBOX-ID18 (NA)
  vendor: ZOTAC
  version: XX
  serial: G211X
  width: 64 bits
  capabilities: smbios-2.7 dmi-2.7 vsyscall32
  configuration: boot=normal chassis=notebook family=NA sku=NA 
uuid=00020003-0004-0005-0006-000700080009
    *-core

  sudo lshw -C display
    *-display
     description: VGA compatible controller
     product: 3rd Gen Core processor Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 09
     width: 64 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list rom
     configuration: driver=i915 latency=0
     resources: irq:45 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64)

  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user5536 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: #RESUME=UUID=edaa55c6-eb56-43fb-8004-495948b72b38
  InstallationDate: Installed on 2014-07-23 (743 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
  MachineType: ZOTAC ZBOX-ID18
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
  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-3.13.0-92-generic N/A
   linux-backports-modules-3.13.0-92-generic  N/A
   linux-firmware 1.157.2
  RfKill:

  StagingDrivers: rts5139
  Tags:  xenial staging
  Uname: Linux 3.13.0-92-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (3 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B211P011
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID18
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 10
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB211P011:bd03/13/2014:svnZOTAC:pnZBOX-ID18:pvrXX:rvnZOTAC:rnZBOX-ID18:rvrXX:cvnNA:ct10:cvrNA:
  dmi.product.name: ZBOX-ID18
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

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

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

[Kernel-packages] [Bug 1630774] Re: kernel invalid opcode in intel_powerclamp

[Vinson Lee]

I can boot completely with kernel command line parameter
'modprobe.blacklist=intel_powerclamp'.

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

Title:
  kernel invalid opcode in intel_powerclamp

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel error on VMware Fusion when booting to graphical login

  
  invalid opcode:  [#1] SMP
  Modules linked in: ipmi_msghandler intel_powerclamp coretemp crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel vmw_balloon aesni_intel aes_x86_64 lrw 
glue_helper ablk_helper cryptd intel_rapl_perf joydev input_leds serio_raw 
snd_ens1371 snd_ac97_codec gameport ac97_bus snd_pcm binfmt_misc snd_seq_midi 
snd_seq_midi_event snd_rawmidi uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 videobuf2_core videodev media snd_seq btusb btrtl btbcm 
snd_seq_device btintel snd_timer bluetooth snd soundcore shpchp i2c_piix4 
vmw_vmci nfit floppy(+) mac_hid parport_pc ppdev lp parport ip_tables x_tables 
autofs4 hid_generic usbhid hid psmouse vmwgfx ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops drm ahci libahci e1000 mptspi mptscsih 
mptbase scsi_transport_spi pata_acpi fjes
  CPU: 0 PID: 806 Comm: kidle_inject/0 Not tainted 4.8.0-19-generic #21-Ubuntu
  Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference 
Platform, BIOS 6.00 07/02/2015
  task: 9e70f1ce1c80 task.stack: 9e70f679
  RIP: 0010:[]  [] clamp_thread+0x2b8/0x5d0 
[intel_powerclamp]
  RSP: 0018:9e70f6793e00  EFLAGS: 00010246
  RAX: 9e70f6790008 RBX: fffee2fe RCX: 
  RDX:  RSI: 0246 RDI: 0246
  RBP: 9e70f6793ec0 R08: 9e70f679 R09: 
  R10: afb504000afb5041 R11: 9e70fa619ac0 R12: 93958160
  R13: 9e70f679 R14:  R15: 9e70f679
  FS:  () GS:9e70fa60() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7ffd50464ff8 CR3: b89db000 CR4: 001406f0
  Stack:
    0005 c073e5d8 c073ea40
    0003  9e70f6790008
    9e70fa60ff68 fffee2fe c073c0a0
  Call Trace:
   [] ? pkg_state_counter+0xa0/0xa0 [intel_powerclamp]
   [] ? powerclamp_set_cur_state+0x170/0x170 
[intel_powerclamp]
   [] ? powerclamp_set_cur_state+0x170/0x170 
[intel_powerclamp]
   [] kthread+0xd8/0xf0
   [] ret_from_fork+0x1f/0x40
   [] ? kthread_create_on_node+0x1e0/0x1e0
  Code: d2 e9 ba 00 00 00 eb 19 0f 1f 00 0f ae f0 65 48 8b 04 25 04 69 01 00 0f 
ae b8 08 c0 ff ff 0f ae f0 31 d2 48 8b 44 24 38 48 89 d1 <0f> 01 c8 49 8b 45 08 
a8 08 75 0b b9 01 00 00 00 4c 89 f0 0f 01 
  RIP  [] clamp_thread+0x2b8/0x5d0 [intel_powerclamp]
   RSP 
  ---[ end trace fb2ec9f1e269d231 ]---

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

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

[Kernel-packages] [Bug 1633172] Re: Linux 4.8 as in 16.10 hangs during boot

[Dylan Borg]

I meant 4.8.1

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

Title:
  Linux 4.8 as in 16.10 hangs during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel 
seemed to take ages to boot and appears to have hanged. I have managed to boot 
the system with the older 4.4 kernels from 16.04 just fine without any problems 
from systemd etc.. Please fix this so I can stop selecting the kernel manually 
on each boot.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2
  InstallationDate: Installed on 2016-02-19 (236 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-43-generic N/A
   linux-backports-modules-4.4.0-43-generic  N/A
   linux-firmware1.161
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.4.0-43-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3101
  dmi.board.asset.tag: Default string
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1633172/+subscriptions

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

[Kernel-packages] [Bug 1633172] Re: Linux 4.8 as in 16.10 hangs during boot

[Dylan Borg]

CONFIG_HARDENED_USERCOPY_PAGESPAN is disabled in the Kernel PPA builds
of the 4.7.1 kernel. That kernel does not boot for me. So in jmy case
setting that to no will not fix it.

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

Title:
  Linux 4.8 as in 16.10 hangs during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel 
seemed to take ages to boot and appears to have hanged. I have managed to boot 
the system with the older 4.4 kernels from 16.04 just fine without any problems 
from systemd etc.. Please fix this so I can stop selecting the kernel manually 
on each boot.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2
  InstallationDate: Installed on 2016-02-19 (236 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-43-generic N/A
   linux-backports-modules-4.4.0-43-generic  N/A
   linux-firmware1.161
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.4.0-43-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3101
  dmi.board.asset.tag: Default string
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1633172/+subscriptions

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

[Kernel-packages] [Bug 1633172] Re: Linux 4.8 as in 16.10 hangs during boot

[Dylan Borg]

I have a Broadwell-E CPU not Skylar.

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

Title:
  Linux 4.8 as in 16.10 hangs during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel 
seemed to take ages to boot and appears to have hanged. I have managed to boot 
the system with the older 4.4 kernels from 16.04 just fine without any problems 
from systemd etc.. Please fix this so I can stop selecting the kernel manually 
on each boot.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2
  InstallationDate: Installed on 2016-02-19 (236 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-43-generic N/A
   linux-backports-modules-4.4.0-43-generic  N/A
   linux-firmware1.161
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.4.0-43-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3101
  dmi.board.asset.tag: Default string
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1633172/+subscriptions

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

[Kernel-packages] [Bug 1633172] Re: Linux 4.8 as in 16.10 hangs during boot

[Dylan Borg]

*Skylake

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

Title:
  Linux 4.8 as in 16.10 hangs during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel 
seemed to take ages to boot and appears to have hanged. I have managed to boot 
the system with the older 4.4 kernels from 16.04 just fine without any problems 
from systemd etc.. Please fix this so I can stop selecting the kernel manually 
on each boot.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2
  InstallationDate: Installed on 2016-02-19 (236 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-43-generic N/A
   linux-backports-modules-4.4.0-43-generic  N/A
   linux-firmware1.161
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.4.0-43-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3101
  dmi.board.asset.tag: Default string
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1633172/+subscriptions

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

[Kernel-packages] [Bug 1612504] Re: package linux-image-4.4.0-34-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-image-4.4.0-34-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Expired

Bug description:
  Problem occurred just as MS EULA was presented for OK, it froze and
  would not respond. ttf-mscorefonts-installer would not install. New
  problem appears as "font" appears in preparing installation.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-66.74~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-66-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  glenn  2809 F pulseaudio
  Date: Thu Aug 11 22:41:47 2016
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=50593cc7-409e-4190-8b87-199fd8eb6f6c
  InstallationDate: Installed on 2016-06-12 (60 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  MachineType: Dell Inc. Inspiron 1720
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-66-generic 
root=UUID=932b86e7-7876-4f4d-8b54-b13ee01d9f7a ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.4.0-34-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to xenial on 2016-08-09 (2 days ago)
  dmi.bios.date: 07/11/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd07/11/2008:svnDellInc.:pnInspiron1720:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1720
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1612927] Re: package linux-image-3.19.0-51-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-image-3.19.0-51-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 1

Status in linux package in Ubuntu:
  Expired

Bug description:
  currently, using 3.19.0-15-generic which as grub 2.0 doesn't work must
  be typed in manually.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-51-generic (not installed)
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic i686
  ApportVersion: 2.17.2-0ubuntu1.3
  AptOrdering:
   linux-image-3.19.0-51-generic: Install
   linux-image-3.19.0-51-generic: Configure
   linux-image-extra-3.19.0-51-generic: Configure
   linux-image-generic: Configure
   NULL: ConfigurePending
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ntr 859 F lxpanel
  Date: Sat Aug 13 05:28:11 2016
  DpkgHistoryLog:
   Start-Date: 2016-08-13  05:28:07
   Commandline: /usr/sbin/synaptic
   Install: linux-image-3.19.0-51-generic:i386 (3.19.0-51.58)
  DuplicateSignature: package:linux-image-3.19.0-51-generic:(not 
installed):subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=68bbe611-e3d5-453f-8749-ec1d5ddab85d
  InstallationDate: Installed on 2015-08-07 (371 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Computer Corporation Latitude D600
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic set 
root=/dev/sda1
  RelatedPackageVersions: grub-pc 2.02~beta2-22ubuntu1.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-3.19.0-51-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2003
  dmi.bios.vendor: Dell Computer Corporation
  dmi.bios.version: A08
  dmi.board.name: 0X2034
  dmi.board.vendor: Dell Computer Corporation
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Computer Corporation
  dmi.modalias: 
dmi:bvnDellComputerCorporation:bvrA08:bd10/29/2003:svnDellComputerCorporation:pnLatitudeD600:pvr:rvnDellComputerCorporation:rn0X2034:rvr:cvnDellComputerCorporation:ct8:cvr:
  dmi.product.name: Latitude D600
  dmi.sys.vendor: Dell Computer Corporation

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

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

[Kernel-packages] [Bug 1612283] Re: apt-get upgrade error

[Launchpad Bug Tracker]

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

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

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

Title:
  apt-get upgrade error

Status in linux package in Ubuntu:
  Expired

Bug description:
  Any ideas what is wrong here?

  root@localhost:/home/chadr# apt-get upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  E: The package linux-image-extra-3.13.0-88-generic needs to be reinstalled, 
but I can't find an archive for it.

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

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

[Kernel-packages] [Bug 1613111] Re: Lenovo Flex 3-1580 (80R4) Intel Backlight Issues

[Launchpad Bug Tracker]

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

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

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

Title:
  Lenovo Flex 3-1580 (80R4) Intel Backlight Issues

Status in linux package in Ubuntu:
  Expired

Bug description:
  This laptop suffers from the same issue as just about every Intel
  laptop I've used. xbacklight will not adjust brightness unless
  acpi_backlight=none is set in /etc/default/grub and the grub
  configuration rebuilt to use it as a kernel command line option.

  As a separate but related issue, the backlight keys do not work at all
  for this laptop, and I haven't yet figured out a solution for that.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-34-generic 4.4.0-34.53
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  karen  3647 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Aug 14 16:14:31 2016
  HibernationDevice: RESUME=UUID=94e950bd-4474-40e8-93c8-d9fb78cffee3
  InstallationDate: Installed on 2016-08-12 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 04f3:2089 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 04f2:b50f Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80R4
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-34-generic.efi.signed 
root=UUID=eebf5f5f-0e70-4f2c-ae02-0a3d2218ea40 ro rootflags=subvol=@ quiet 
splash acpi_osi=Linux acpi_backlight=none vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-34-generic N/A
   linux-backports-modules-4.4.0-34-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D3CN28WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Flex 3-1580
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Flex 3-1580
  dmi.modalias: 
dmi:bvnLENOVO:bvrD3CN28WW:bd05/09/2016:svnLENOVO:pn80R4:pvrFlex3-1580:rvnLENOVO:rnFlex3-1580:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrFlex3-1580:
  dmi.product.name: 80R4
  dmi.product.version: Flex 3-1580
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1633662] Re: Wireless card monitor mode

[Ahmad Abdulnasir Shu'aib]

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

Title:
  Wireless card monitor mode

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot get to set wireless card on monitor mode, while checking
  dmesg i have came across some string said "cut here".

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

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

[Kernel-packages] [Bug 1490130] Re: Elantech touchpad stops working after suspend

[Harris Anggara]

i will try it and report the result as soon as posible. thank you very
much.

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

Title:
  Elantech touchpad stops working after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  i have asus a455ld i5 5200u running kubuntu 15.04 with kernel 
4.0.8-040008-generic.
  touchpad is recognized as elantech version 4. everything was fine until my 
notebook go to suspend and resume without touchpad working.
  I tried :
  modprobe -r psmouse
  modprobe psmouse

  it only work before suspend.
  execute those commands after resume from suspend is not working.

  the last thing i tried is this.

  when i use this command before suspend :

  insmod
  /lib/modules/4.0.8-040008-generic/kernel/drivers/input/mouse/psmouse.ko

  these appear in the dmesg:

  [  820.207105] psmouse serio1: elantech: assuming hardware version 4 (with 
firmware version 0x381f00)
  [  820.70] psmouse serio1: elantech: Synaptics capabilities query result 
0x10, 0x14, 0x0e.
  [  820.294698] input: ETPS/2 Elantech Touchpad as 
/devices/platform/i8042/serio1/input/input146

  but when i use the command after suspend, there is nothing any output
  in the dmesg.

  i tried all ubuntu varian and opensuse 13.2 live usb, the result is the same.
  but in windows 10,  touchpad still active after suspend.
  ---
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-06-20 (69 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Package: linux (not installed)
  Tags:  vivid
  Uname: Linux 4.0.8-040008-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  ---
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  blackhole   1460 F pulseaudio
   /dev/snd/controlC1:  blackhole   1460 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=668506c6-5b13-4a29-9c34-956c6c34a45a
  InstallationDate: Installed on 2015-06-20 (129 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 13d3:3423 IMC Networks
   Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X455LDB
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic 
root=UUID=4318cf1f-564c-47ff-8b0c-f3acf77aa34f ro quiet splash 
i915.enable_ips=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.3
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X455LDB.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X455LDB
  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.:bvrX455LDB.206:bd02/12/2015:svnASUSTeKCOMPUTERINC.:pnX455LDB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX455LDB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X455LDB
  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/1490130/+subscriptions

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

[Kernel-packages] [Bug 1504445] Re: FocalTech touchpad stops working after suspend

[Marcos Paulo de Souzas]

Hi guys, Linus picked patch today that solves this problem for some Asus
models:

A455LD
K401LB
K501LB
K501LX
R409L
V502LX
X302LA
X450LCP
X450LD
X455LAB
X455LDB
X455LF
Z450LA

So, can you please check this patch[1] and then report if this really
fixes your problem? This patch will be available in kernel 4.9.

Also, if yuor version is not covered in this patch, please let me know.

Thanks!

[1]
https://git.kernel.org/cgit/linux/kernel/git/dtor/input.git/commit/?id=930e19248e9b61da36c967687ca79c4d5f977919

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

Title:
   FocalTech touchpad stops working after suspend

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I have an Asus V502LX the persian version of the Asus K501LX.

  I have Ubuntu 14.04 installed and the kernel 4.1.6 installed. I had to
  install the kernel 4.1.6 to have the touchpad recognised. Under kernel
  3.19.30, as I am running now to file in this bug, the touchpad is
  recognised as a simple mouse (no two fingers scrolling...) and the
  problem I am describing below is also present...

  I noticed one problem. The Focaltech touchpad is not working after
  suspending the computer.

  Here is what I could find about the touchpad in
  /proc/bus/input/devices

  I: Bus=0011 Vendor=0002 Product=0012 Version=
  N: Name="FocalTechPS/2 FocalTech FocalTech Touchpad"
  P: Phys=isa0060/serio1/input0
  S: Sysfs=/devices/platform/i8042/serio1/input/input5
  U: Uniq=
  H: Handlers=mouse0 event4
  B: PROP=5
  B: EV=b
  B: KEY=e520 1 0 0 0 0
  B: ABS=2608003

  Before suspending the computer, I can deactivate and activate again
  the touchpad with the hotkey of my keyboard without problem. However,
  once the computer suspended, nothing work to re-activate the touchpad.

  I tried a solution given on internet but it doesn't work properly.

  I created a file here /etc/pm/sleep.d/trackpad
  sudo gedit /etc/pm/sleep.d/trackpad

  and add the following
  #!/bin/sh
  case "$1" in
  suspend|hibernate)
  modprobe -r psmouse;
  resume|thaw)
  modprobe psmouse;
  esac

  With this file, the computer refuse to suspend. The touchpad keep
  working so it does something but I can't make my computer sleeping...

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.34~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct  9 12:05:16 2015
  InstallationDate: Installed on 2015-09-26 (12 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  yogo   2073 F pulseaudio
   /dev/snd/controlC0:  yogo   2073 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=943b03af-c1bf-489e-8e42-485931fc619c
  InstallationDate: Installed on 2015-09-26 (12 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 8087:07dc Intel Corp. 
   Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501LX
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed 
root=UUID=37bd087e-a2f6-437e-8d20-b19536eb738a ro quiet splash acpi_osi= 
vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-30-generic N/A
   linux-backports-modules-3.19.0-30-generic  N/A
   linux-firmware 1.127.15
  Tags:  trusty
  Uname: Linux 3.19.0-30-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
  _MarkForUpload: True
  dmi.bios.date: 04/16/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501LX.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501LX
  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.:bvrK501LX.203:bd04/16/2015:svnASUSTeKCOMPUTERINC.:pnK501LX:pvr

[Kernel-packages] [Bug 1406014] Re: Bluetooth: can't load firmware, may not work correctly

[Christopher M. Penalver]

Yota, it will help immensely if you filed a new report with the Ubuntu 
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

Title:
  Bluetooth: can't load firmware, may not work correctly

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Bluetooth does not work. The tray icon appears, but none of the functionality 
is available. Probable cause:
  The firmware for Bus 001 Device 003: ID 0a5c:21e6 Broadcom Corp. BCM20702 
Bluetooth 4.0 [ThinkPad] does not load. The message in dmesg is "Bluetooth: 
can't load firmware, may not work correctly". The problem appeared after 
upgrading from the previous LTS version (12.04?).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-44-generic 3.13.0-44.73
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weber  2408 F pulseaudio
    weber  2744 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Dec 27 22:58:37 2014
  HibernationDevice: RESUME=UUID=4dd72213-9a42-4532-aa22-2ccc72d46062
  InstallationDate: Installed on 2012-07-21 (889 days ago)
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120423)
  MachineType: LENOVO 2320CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic 
root=UUID=a58cd4c1-52b5-4b88-b5a8-3bf530c20c4a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-44-generic N/A
   linux-backports-modules-3.13.0-44-generic  N/A
   linux-firmware 1.127.11
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-12-26 (1 days ago)
  dmi.bios.date: 05/24/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET31WW (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2320CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET31WW(1.11):bd05/24/2012:svnLENOVO:pn2320CTO:pvrThinkPadX230:rvnLENOVO:rn2320CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2320CTO
  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/1406014/+subscriptions

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

[Kernel-packages] [Bug 1604313] Re: Ubuntu 16.04: system freezes instead of suspend after undocking

[Christopher M. Penalver]

brandon211, the next step is to fully reverse commit bisect from kernel
4.7-rc7 to 4.8.1 in order to identify the last bad commit, followed
immediately by the first good one. Once this good commit has been
identified, it may be reviewed for backporting. Could you please do this
following
https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
?

Please note, finding adjacent kernel versions is not fully commit
bisecting.

Also, the kernel release names are irrelevant for the purposes of
bisecting.

It is most helpful that after the fix commit (not kernel version) has
been identified, you then mark this report Status Confirmed.

Thank you for your help.

** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.8.1 needs-
reverse-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/1604313

Title:
  Ubuntu 16.04: system freezes instead of suspend after undocking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using a Lenovo ThinkPad T450s. When the system was docked and then 
undocked, suspend won't work. Instead, the screen goes black, the system 
freezes and the fan runs on high speed.
  This problem persists with the (as of today) most recent kernel 
4.4.0-31-generic #50.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  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/controlC0:  buerger3534 F pulseaudio
   /dev/snd/pcmC1D0p:   buerger3534 F...m pulseaudio
   /dev/snd/controlC1:  buerger3534 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jul 19 11:13:41 2016
  HibernationDevice: RESUME=UUID=21eeaf61-c437-45dc-80e3-e581eb6f795c
  InstallationDate: Installed on 2015-09-15 (307 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20BX000XGE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7
  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: Upgraded to xenial on 2016-04-22 (87 days ago)
  dmi.bios.date: 03/23/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET57WW (1.22 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BX000XGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET57WW(1.22):bd03/23/2016:svnLENOVO:pn20BX000XGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000XGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BX000XGE
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO

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

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

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

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1633662

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

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

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

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

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

Title:
  Wireless card monitor mode

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot get to set wireless card on monitor mode, while checking
  dmesg i have came across some string said "cut here".

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

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

[Kernel-packages] [Bug 1618782] Re: wifi stops functioning briefly after connecting to network

[Christopher M. Penalver]

Kgorbi:
1) To keep this relevant to upstream, one would want to continually check for, 
and test the latest mainline kernel (now 4.8.1) as it is released. Could you 
please advise?
2) Please provide the output of the following terminal command (not perform an 
apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

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

Title:
  wifi stops functioning briefly after connecting to network

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Lenovo W530, after upgrade from 14.04 to 16.04:
  Although wifi card is still connected to the wifi-router (network manager 
states so), no user traffic is passing through after a few seconds from 
authentication.

  Workaround: 'iwconfig wlan0 power off' executed after the connection
  becomes unusable brings it back to operation.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kgar   4992 F pulseaudio
   /dev/snd/controlC0:  kgar   4992 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Aug 31 10:48:01 2016
  HibernationDevice: RESUME=UUID=eeaac5ff-7cb9-4674-963c-2641065f84b6
  InstallationDate: Installed on 2014-01-17 (956 days ago)
  InstallationMedia: It
  MachineType: LENOVO 244759G
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=20cbb6d9-2c69-427b-a27f-09a0787436b9 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-08-13 (18 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: 244759G
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ET92WW(2.52):bd02/27/2013:svnLENOVO:pn244759G:pvrThinkPadW530:rvnLENOVO:rn244759G:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 244759G
  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/1618782/+subscriptions

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

[Kernel-packages] [Bug 292480] Fw: examples of my work

[ixzel]

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

Dear!

I've started a new project recently, so you  can find some examples of
my  recenr  works here  

All the best, oscurospira

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

Title:
  E:var/cache/apt/archives/linux-
  image-2.6.27-7-generic_2.6.27-7.15_amd64.deb:unable to make backup
  link of '/boot/vmlinuz-2.6.27-7 generic'before installine new version

Status in linux package in Ubuntu:
  New

Bug description:
  E:/var/cache/apt/archives/linux-
  image-2.6.27-7-generic_2.6.27-7.15_amd64.deb:unable to make backup
  link of'/boot/vmlinux-2.6.27-7 generic'before installing new version

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

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

[Kernel-packages] [Bug 1633662] [NEW] Wireless card monitor mode

[Ahmad Abdulnasir Shu'aib]

Public bug reported:

I cannot get to set wireless card on monitor mode, while checking dmesg
i have came across some string said "cut here".

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

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

Title:
  Wireless card monitor mode

Status in linux package in Ubuntu:
  New

Bug description:
  I cannot get to set wireless card on monitor mode, while checking
  dmesg i have came across some string said "cut here".

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

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

[Kernel-packages] [Bug 1490130] Re: Elantech touchpad stops working after suspend

[Marcos Paulo de Souzas]

Linus just picked the today's input PR with a fix for this problem for
A455LD, X455LDB, K501LB, K501LX and X302LA.

Can you please check this patchset:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=689f891c980949d3eb64f61651db53cb347e0a13
?

If you have a different model, that needs to be included is this list,
please tell us here in the kernel bug:
https://bugzilla.kernel.org/show_bug.cgi?id=107971

Please, let me know if this fixes your problem.

Thanks!

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

Title:
  Elantech touchpad stops working after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  i have asus a455ld i5 5200u running kubuntu 15.04 with kernel 
4.0.8-040008-generic.
  touchpad is recognized as elantech version 4. everything was fine until my 
notebook go to suspend and resume without touchpad working.
  I tried :
  modprobe -r psmouse
  modprobe psmouse

  it only work before suspend.
  execute those commands after resume from suspend is not working.

  the last thing i tried is this.

  when i use this command before suspend :

  insmod
  /lib/modules/4.0.8-040008-generic/kernel/drivers/input/mouse/psmouse.ko

  these appear in the dmesg:

  [  820.207105] psmouse serio1: elantech: assuming hardware version 4 (with 
firmware version 0x381f00)
  [  820.70] psmouse serio1: elantech: Synaptics capabilities query result 
0x10, 0x14, 0x0e.
  [  820.294698] input: ETPS/2 Elantech Touchpad as 
/devices/platform/i8042/serio1/input/input146

  but when i use the command after suspend, there is nothing any output
  in the dmesg.

  i tried all ubuntu varian and opensuse 13.2 live usb, the result is the same.
  but in windows 10,  touchpad still active after suspend.
  ---
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2015-06-20 (69 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Package: linux (not installed)
  Tags:  vivid
  Uname: Linux 4.0.8-040008-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  ---
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  blackhole   1460 F pulseaudio
   /dev/snd/controlC1:  blackhole   1460 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=668506c6-5b13-4a29-9c34-956c6c34a45a
  InstallationDate: Installed on 2015-06-20 (129 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 13d3:3423 IMC Networks
   Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X455LDB
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic 
root=UUID=4318cf1f-564c-47ff-8b0c-f3acf77aa34f ro quiet splash 
i915.enable_ips=0 vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.3
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X455LDB.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X455LDB
  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.:bvrX455LDB.206:bd02/12/2015:svnASUSTeKCOMPUTERINC.:pnX455LDB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX455LDB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X455LDB
  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/1490130/+subscriptions

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

[Kernel-packages] [Bug 1631058] Re: scsi host6: runtime PM trying to activate child device host6 but parent (3-3:1.0) is not active

[Vijay]

I have a similar problem: I cannot even boot my computer(Thinkpad X220)
from a live usb of 16.10. See this screenshot: http://imgur.com/a/nITS0

Apologies for the screen glare.

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

Title:
  scsi host6: runtime PM trying to activate child device host6 but
  parent (3-3:1.0) is not active

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [  420.107609] scsi host6: runtime PM trying to activate child device
  host6 but parent (3-3:1.0) is not active

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-19-lowlatency 4.8.0-19.21
  ProcVersionSignature: Ubuntu 4.8.0-19.21-lowlatency 4.8.0-rc8
  Uname: Linux 4.8.0-19-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2728 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2728 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Oct  6 13:16:46 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (438 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-19-lowlatency 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-19-lowlatency N/A
   linux-backports-modules-4.8.0-19-lowlatency  N/A
   linux-firmware   1.161
  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.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/1631058/+subscriptions

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

[Kernel-packages] [Bug 1628698] Re: Hibernate stopped working after upgrading to Ubuntu 16.04.1 LTS

[Nilesh Pereira]

** Summary changed:

- Hibernate stopped working after upgrading to Xubuntu 16.04.1 LTS
+ Hibernate stopped working after upgrading to Ubuntu 16.04.1 LTS

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

Title:
  Hibernate stopped working after upgrading to Ubuntu 16.04.1 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hibernate has stopped working for me after upgrading from Xubuntu
  14.04 LTS to Xubuntu 16.04.1 LTS. I tried Ubuntu Mate and Ubuntu
  Gnome, but it made no difference.

  Laptop model HP G42-303DX.

  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  uname -a
  Linux xubu 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

  Expected behavior after clicking on "Hibernate" button in shutdown
  menu, or by running "sudo pm-hibernate" in a terminal would be for the
  laptop to go into hibernate mode.

  Actual behavior is that when resuming after hibernation, the laptop
  simply restarts. This worked in Xubuntu 14.04. I have also followed
  the instructions to enable hibernation as per
  https://help.ubuntu.com/stable/ubuntu-help/power-hibernate.html.

  Please let me know what additional information you require from me.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nilesh 2440 F pulseaudio
   /dev/snd/controlC1:  nilesh 2440 F pulseaudio
   /dev/snd/seq:nilesh 5140 F chrome
  CurrentDesktop: MATE
  Date: Wed Sep 28 17:16:04 2016
  HibernationDevice: RESUME=UUID=13d31939-fce3-4392-a570-d6a4826efc05
  InstallationDate: Installed on 2015-01-02 (635 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  MachineType: Hewlett-Packard HP G42 Notebook PC
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=/dev/mapper/vg-root ro quiet splash acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-08-17 (42 days ago)
  dmi.bios.date: 11/07/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.17
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1444
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 69.26
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.17:bd11/07/2010:svnHewlett-Packard:pnHPG42NotebookPC:pvr0593110002242710010020100:rvnHewlett-Packard:rn1444:rvr69.26:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP G42 Notebook PC
  dmi.product.version: 0593110002242710010020100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1628698] Re: Hibernate stopped working after upgrading to Xubuntu 16.04.1 LTS

[Nilesh Pereira]

Bug exists with latest mainline kernel 4.8.1. Updated tags.

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

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

Title:
  Hibernate stopped working after upgrading to Xubuntu 16.04.1 LTS

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hibernate has stopped working for me after upgrading from Xubuntu
  14.04 LTS to Xubuntu 16.04.1 LTS. I tried Ubuntu Mate and Ubuntu
  Gnome, but it made no difference.

  Laptop model HP G42-303DX.

  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  uname -a
  Linux xubu 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

  Expected behavior after clicking on "Hibernate" button in shutdown
  menu, or by running "sudo pm-hibernate" in a terminal would be for the
  laptop to go into hibernate mode.

  Actual behavior is that when resuming after hibernation, the laptop
  simply restarts. This worked in Xubuntu 14.04. I have also followed
  the instructions to enable hibernation as per
  https://help.ubuntu.com/stable/ubuntu-help/power-hibernate.html.

  Please let me know what additional information you require from me.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-38-generic 4.4.0-38.57
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nilesh 2440 F pulseaudio
   /dev/snd/controlC1:  nilesh 2440 F pulseaudio
   /dev/snd/seq:nilesh 5140 F chrome
  CurrentDesktop: MATE
  Date: Wed Sep 28 17:16:04 2016
  HibernationDevice: RESUME=UUID=13d31939-fce3-4392-a570-d6a4826efc05
  InstallationDate: Installed on 2015-01-02 (635 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  MachineType: Hewlett-Packard HP G42 Notebook PC
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=/dev/mapper/vg-root ro quiet splash acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-08-17 (42 days ago)
  dmi.bios.date: 11/07/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.17
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1444
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 69.26
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.17:bd11/07/2010:svnHewlett-Packard:pnHPG42NotebookPC:pvr0593110002242710010020100:rvnHewlett-Packard:rn1444:rvr69.26:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP G42 Notebook PC
  dmi.product.version: 0593110002242710010020100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1633172] Re: Linux 4.8 as in 16.10 hangs during boot

[Grief]

I am on i5 but I don't think this is relevant. I am rebuilding the
kernel CONFIG_HARDENED_USERCOPY_PAGESPAN, it's pretty slow in VM
though...

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

Title:
  Linux 4.8 as in 16.10 hangs during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel 
seemed to take ages to boot and appears to have hanged. I have managed to boot 
the system with the older 4.4 kernels from 16.04 just fine without any problems 
from systemd etc.. Please fix this so I can stop selecting the kernel manually 
on each boot.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2
  InstallationDate: Installed on 2016-02-19 (236 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-43-generic N/A
   linux-backports-modules-4.4.0-43-generic  N/A
   linux-firmware1.161
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.4.0-43-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3101
  dmi.board.asset.tag: Default string
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1633172/+subscriptions

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

[Kernel-packages] [Bug 1626371] Re: cdc_ether fills kernel log

[Keith McClelland]

I've had the same problem with every 4.8 I tried including the one that
is in the brand new Ubuntu 16.10 (4.8.0-22) [via live cd, not
installed!]. My computer is a Surface Pro 3 which uses a Marvell chipset
in the docking station. I'm pretty sure I have updated to the latest
mwifiex in my installed 16.04.

The computer does seem to work, but syslog grows by several lines per
second (but now and again it skips a few seconds while it's worrying
about a limit and then away it goes 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/1626371

Title:
  cdc_ether fills kernel log

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo X1 4th gen with a dock attached:

  [ 1764.086306] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been 
dropped
  [ 1764.150317] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been 
dropped

  
  The USB Ethernet device would warn occasionally under the 4.4 kernel. Under 
the 4.8 kernel, it spams my kernel log so much that I don't get anything else.

  $ uname -a
  Linux aurora 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 20:00:03 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  joel@aurora ~ 
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

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

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

[Kernel-packages] [Bug 1633172] Re: Linux 4.8 as in 16.10 hangs during boot

[Armin Kunaschik]

@borgdylan writes in bug 1627198 that he has an i7 6900K. My VM runs on an i5 
6600 (in 32 bit mode).
Can this be a Skylake issue?

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

Title:
  Linux 4.8 as in 16.10 hangs during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel 
seemed to take ages to boot and appears to have hanged. I have managed to boot 
the system with the older 4.4 kernels from 16.04 just fine without any problems 
from systemd etc.. Please fix this so I can stop selecting the kernel manually 
on each boot.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2
  InstallationDate: Installed on 2016-02-19 (236 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-43-generic N/A
   linux-backports-modules-4.4.0-43-generic  N/A
   linux-firmware1.161
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.4.0-43-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3101
  dmi.board.asset.tag: Default string
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1633172/+subscriptions

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

[Kernel-packages] [Bug 1633172] Re: Linux 4.8 as in 16.10 hangs during boot

[Grief]

@jsalisbury - the issue is CONFIG_HARDENED_USERCOPY_PAGESPAN which is
enabled in all kernels in ubuntu kernel ppa starting from 4.8 while it
has to be disabled according to this issue:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627198

I am a little bit lost. Where can I find the repo with the kernel
compiled with that option disabled?

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

Title:
  Linux 4.8 as in 16.10 hangs during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel 
seemed to take ages to boot and appears to have hanged. I have managed to boot 
the system with the older 4.4 kernels from 16.04 just fine without any problems 
from systemd etc.. Please fix this so I can stop selecting the kernel manually 
on each boot.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2
  InstallationDate: Installed on 2016-02-19 (236 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-43-generic N/A
   linux-backports-modules-4.4.0-43-generic  N/A
   linux-firmware1.161
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.4.0-43-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3101
  dmi.board.asset.tag: Default string
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1633172/+subscriptions

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

[Kernel-packages] [Bug 1633172] Re: Linux 4.8 as in 16.10 hangs during boot

[Armin Kunaschik]

I did some more reboots and got me a screenshot from 4.8rc1 crash.
I switch to the first console (Ctrl-Alt-F1) as soon as the graphical login 
screen appears.
I'll try to catch one for kernel 4.8.0-22. So far there is no output. The 
cursor at the login prompt simply disappears and the VM hangs.


** Attachment added: "Screenshot_2016-10-15_02-03-31.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+attachment/4761356/+files/Screenshot_2016-10-15_02-03-31.png

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

Title:
  Linux 4.8 as in 16.10 hangs during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel 
seemed to take ages to boot and appears to have hanged. I have managed to boot 
the system with the older 4.4 kernels from 16.04 just fine without any problems 
from systemd etc.. Please fix this so I can stop selecting the kernel manually 
on each boot.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2
  InstallationDate: Installed on 2016-02-19 (236 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-43-generic N/A
   linux-backports-modules-4.4.0-43-generic  N/A
   linux-firmware1.161
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.4.0-43-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3101
  dmi.board.asset.tag: Default string
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1633172/+subscriptions

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

[Kernel-packages] [Bug 1633172] Re: Linux 4.8 as in 16.10 hangs during boot

[Grief]

@jsalisbury I can confirm that even 4.7.2 is good, I can boot with it
without the subject issue.

Adding yakkety-proposal repo has lead to installation of update for
libapparmor package, but that didn't fix the issue.

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

Title:
  Linux 4.8 as in 16.10 hangs during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel 
seemed to take ages to boot and appears to have hanged. I have managed to boot 
the system with the older 4.4 kernels from 16.04 just fine without any problems 
from systemd etc.. Please fix this so I can stop selecting the kernel manually 
on each boot.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2
  InstallationDate: Installed on 2016-02-19 (236 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-43-generic N/A
   linux-backports-modules-4.4.0-43-generic  N/A
   linux-firmware1.161
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.4.0-43-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3101
  dmi.board.asset.tag: Default string
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1633172/+subscriptions

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

[Kernel-packages] [Bug 1633172] Re: Linux 4.8 as in 16.10 hangs during boot

[Armin Kunaschik]

Installing apparmor 2.10.95-4ubuntu5.1 did not change then problem for me.
Kernel 4.8rc1 hangs too.
Kernel 4.7 worked once for a few minutes and crashed the second time.
See attachment for console output (screenshot from VMWare only)

I remember I saw a similar message once with kernel 4.8.0-22, but
unfortunately didn't save it.


** Attachment added: "Screenshot_2016-10-15_01-43-27.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1633172/+attachment/4761348/+files/Screenshot_2016-10-15_01-43-27.png

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

Title:
  Linux 4.8 as in 16.10 hangs during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel 
seemed to take ages to boot and appears to have hanged. I have managed to boot 
the system with the older 4.4 kernels from 16.04 just fine without any problems 
from systemd etc.. Please fix this so I can stop selecting the kernel manually 
on each boot.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2
  InstallationDate: Installed on 2016-02-19 (236 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-43-generic N/A
   linux-backports-modules-4.4.0-43-generic  N/A
   linux-firmware1.161
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.4.0-43-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3101
  dmi.board.asset.tag: Default string
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1633172/+subscriptions

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

[Kernel-packages] [Bug 1632368] Re: linux: 3.19.0-72.80 -proposed tracker

[Steve Beattie]

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

Title:
  linux: 3.19.0-72.80 -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 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 Vivid:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-72.80 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
  derivative-trackers-created: 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/1632368/+subscriptions

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

[Kernel-packages] [Bug 1632369] Re: linux-lts-vivid: 3.19.0-72.80~14.04.1 -proposed tracker

[Brad Figg]

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

** Description changed:

  This bug is for tracking the 3.19.0-72.80~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1632368
  phase: Uploaded

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

Title:
  linux-lts-vivid: 3.19.0-72.80~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  derivative-trackers-created: true
  kernel-stable-master-bug: 1632368
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1632368] Re: linux: 3.19.0-72.80 -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Released

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

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

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 3.19.0-72.80 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
  derivative-trackers-created: true
  phase: Uploaded
+ kernel-stable-phase-changed:Friday, 14. October 2016 22:49 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the 3.19.0-72.80 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
  derivative-trackers-created: true
- phase: Uploaded
- kernel-stable-phase-changed:Friday, 14. October 2016 22:49 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 3.19.0-72.80 -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:
  Confirmed
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 Vivid:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-72.80 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
  derivative-trackers-created: 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/1632368/+subscriptions

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

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

[bugproxy]

--- Comment From ha...@us.ibm.com 2016-10-14 18:37 EDT---
Our systems are now upgraded to:

$ uname -a
Linux dlfire5 4.4.0-43-generic #63-Ubuntu SMP Wed Oct 12 13:45:41 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

$ dpkg -l docker.io
...
ii  docker.io   1.12.1-0ubuntu13~16.04.1  ppc64el

$ modinfo aufs
filename:   /lib/modules/4.4.0-43-generic/kernel/fs/aufs/aufs.ko
alias:  fs-aufs
version:4.x-rcN-20160111
description:aufs -- Advanced multi layered unification filesystem
author: Junjiro R. Okajima 
license:GPL
srcversion: BD1C47D04FE5C2D88F63AAB
depends:
intree: Y
vermagic:   4.4.0-43-generic SMP mod_unload modversions
parm:   brs:use /fs/aufs/si_*/brN (int)
parm:   allow_userns:allow unprivileged to mount under userns (bool)

I'll be doing more builds in the coming days. Will report if I see the
problem 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/1633223

Title:
  rcu_sched detected stalls with kernel 3.19.0-58, NVIDIA driver, and
  docker

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Seeing occasional rcu_sched detected stalls on 14.04 LTS with kernel 
3.19.0-58. The system is running docker containers, and has the NVIDIA GPU 
driver loaded. We've seen about 4 stalls in the last month, all with the 
3.19.0-58 kernel, and with the NVIDIA 352.93 and 361.49 drivers.

  ---uname output---
  Linux dldev1 3.19.0-58-generic #64~14.04.1-Ubuntu SMP Fri Mar 18 19:05:01 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  2 x NVIDIA K80 GPU adapter:
  $ lspci | grep NV
  0002:03:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1)
  0002:04:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1)
  0006:03:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1)
  0006:04:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) 

   
  Machine Type = 8247-42L 
   
  ---System Hang---
   Usual symptom is that the system is unresponsive except maybe for ping and 
writing the stall-detection messages to the console. Login/getty isn't 
available either via ssh nor on the console. System must be power cycled to 
recover.
   
  Attached is the kernel log from a stall detection on May 18th. The detection 
first occurs at: May 18 15:17:55.

  The system is later rebooted and those messages indicate the kernel
  (3.19.0-58) and NVIDIA driver version (352.93) that were active at the
  time.

  We've suffered 3 or 4 stalls since, all with the same kernel, but some
  with a newer NVIDIA driver (361.49).

  Unfortunately, information about the newer stalls wasn't preserved in
  the various log files (and we're not capturing the console
  constantly), so we don't have detailed data for those.

  We'd welcome any suggestions for how to collect additional data for
  these occurrences.

  I can't say for sure that we haven't seen the stalls on other systems,
  but they're occuring fairly frequently on this system, and it's
  unusual in that it's running both Docker and NVIDIA GPU driver. So
  maybe aufs or the NVIDIA driver are somehow involved.

  From the kern.log,

  The Call trace points to some kind of deadlock in aufs -

  May 18 15:17:55 dldev1 kernel: [713670.798624] Task dump for CPU 3:
  May 18 15:17:55 dldev1 kernel: [713670.798628] cc1 R  running 
task0 99183  99173 0x00040004
  May 18 15:17:55 dldev1 kernel: [713670.798633] Call Trace:
  May 18 15:17:55 dldev1 kernel: [713670.798643] [c00fa64673a0] 
[c00cf004] wake_up_worker+0x44/0x60 (unreliable)
  May 18 15:17:55 dldev1 kernel: [713670.798671] [c00fa6467570] 
[c00fa64675d0] 0xc00fa64675d0
  May 18 15:17:55 dldev1 kernel: [713670.798676] [c00fa64675d0] 
[c0a1b050] __schedule+0x370/0x900
  May 18 15:17:55 dldev1 kernel: [713670.798679] [c00fa64677f0] 
[c00fa6467850] 0xc00fa6467850
  May 18 15:17:55 dldev1 kernel: [713670.798682] Task dump for CPU 75:
  May 18 15:17:55 dldev1 kernel: [713670.798684] cc1 D 
105d9410 0 99427  99405 0x00040004
  May 18 15:17:55 dldev1 kernel: [713670.798688] Call Trace:
  May 18 15:17:55 dldev1 kernel: [713670.798691] [c017efdd3460] 
[c017efdd34a0] 0xc017efdd34a0 (unreliable)
  May 18 15:17:55 dldev1 kernel: [713670.798695] [c017efdd3630] 
[c017efdd3690] 0xc017efdd3690
  May 18 15:17:55 dldev1 kernel: [713670.798698] [c017efdd3690] 
[c0a1b050] __schedule+0x370/0x900
  May 18 15:17:55 dldev1 kernel: [713670.798702] [c017efdd38b0] 
[c0a1f128] rwsem_down_write_failed+0x288/0x400
  May 18 15:17:55 dldev1 kernel: [713670.798706] [c017efdd3940] 
[c0a1e538] down_write+0x88/0x90
  May 18 15:17:55 dldev1 kernel: [713670.798716] [c017efdd3970] 
[d0001ead562c] do_ii_write_l

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

[Brad Figg]

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

Title:
  sr-iov not working on ubuntu 16.04 kvm

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The exact same set up (hardware and commands I have made) worked
  perfectly on Ubuntu 14.04 but I can't get it working with 16.04. The
  only thing I have changed between the 2 setups is adding  to the network definition as the now default vfio also
  failed with

  qemu-system-x86_64: vfio_dma_map(0x55f1c4f8bb00, 0xfe00, 0x4000, 
0x7fa68770) = -14 (Bad address)
  qemu: hardware error: vfio: DMA mapping failed, unable to continue

  If I am doing something wrong I apologise, this is my first bug report
  and I'm still relatively new to Linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-42-generic 4.4.0-42.62
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 14 20:11 seq
   crw-rw 1 root audio 116, 33 Oct 14 20:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Oct 14 23:05:26 2016
  HibernationDevice: RESUME=UUID=bb1632fb-69fe-4d67-bc51-8182d2546d91
  InstallationDate: Installed on 2016-10-08 (6 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: FUJITSU PRIMERGY TX1310 M1
  PciMultimedia:
   
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic 
root=UUID=07b95c7c-db77-4cee-8336-6f24b2072da6 ro pcie_aspm=off intel_iommu=on 
iommu=pt pci=assign-busses quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2015
  dmi.bios.vendor: FUJITSU // American Megatrends Inc.
  dmi.bios.version: V4.6.5.4 R1.5.0 for D3219-A1x
  dmi.board.name: D3219-A1
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D3219-A1
  dmi.chassis.type: 6
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: TX1310M1
  dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.4R1.5.0forD3219-A1x:bd09/15/2015:svnFUJITSU:pnPRIMERGYTX1310M1:pvr:rvnFUJITSU:rnD3219-A1:rvrS26361-D3219-A1:cvnFUJITSU:ct6:cvrTX1310M1:
  dmi.product.name: PRIMERGY TX1310 M1
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1633267] Re: Wifi and sound no longer detected in kernel 4.4.0-43

[Mossroy]

It seems that this issue can have even more critical symptoms :
http://askubuntu.com/questions/837003/ubuntu-16-04-freezes-on-login-
screen-no-keyboard-or-mouse-working

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

Title:
  Wifi and sound no longer detected in kernel 4.4.0-43

Status in One Hundred Papercuts:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 
and rebooting the system didn't seem to recognize my Wifi or sound hardware: 
there was no Wifi icon or ability to connect to a network, and the only output 
on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matt   3400 F pulseaudio
   /dev/snd/controlC1:  matt   3400 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423
  InstallationDate: Installed on 2015-08-23 (417 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  MachineType: LENOVO 20ANCTO1WW
  Package: linux (not installed)
  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.4.0-42-generic.efi.signed 
root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.4
  Tags:  xenial
  Uname: Linux 4.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET84WW (2.38 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ANCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ANCTO1WW
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1633634] [NEW] sr-iov not working on ubuntu 16.04 kvm

[Sarah Coxon]

Public bug reported:

The exact same set up (hardware and commands I have made) worked
perfectly on Ubuntu 14.04 but I can't get it working with 16.04. The
only thing I have changed between the 2 setups is adding  to the network definition as the now default vfio also
failed with

qemu-system-x86_64: vfio_dma_map(0x55f1c4f8bb00, 0xfe00, 0x4000, 
0x7fa68770) = -14 (Bad address)
qemu: hardware error: vfio: DMA mapping failed, unable to continue

If I am doing something wrong I apologise, this is my first bug report
and I'm still relatively new to Linux.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-42-generic 4.4.0-42.62
ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
Uname: Linux 4.4.0-42-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Oct 14 20:11 seq
 crw-rw 1 root audio 116, 33 Oct 14 20:11 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Fri Oct 14 23:05:26 2016
HibernationDevice: RESUME=UUID=bb1632fb-69fe-4d67-bc51-8182d2546d91
InstallationDate: Installed on 2016-10-08 (6 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: FUJITSU PRIMERGY TX1310 M1
PciMultimedia:
 
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic 
root=UUID=07b95c7c-db77-4cee-8336-6f24b2072da6 ro pcie_aspm=off intel_iommu=on 
iommu=pt pci=assign-busses quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-42-generic N/A
 linux-backports-modules-4.4.0-42-generic  N/A
 linux-firmware1.157.4
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2015
dmi.bios.vendor: FUJITSU // American Megatrends Inc.
dmi.bios.version: V4.6.5.4 R1.5.0 for D3219-A1x
dmi.board.name: D3219-A1
dmi.board.vendor: FUJITSU
dmi.board.version: S26361-D3219-A1
dmi.chassis.type: 6
dmi.chassis.vendor: FUJITSU
dmi.chassis.version: TX1310M1
dmi.modalias: 
dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.4R1.5.0forD3219-A1x:bd09/15/2015:svnFUJITSU:pnPRIMERGYTX1310M1:pvr:rvnFUJITSU:rnD3219-A1:rvrS26361-D3219-A1:cvnFUJITSU:ct6:cvrTX1310M1:
dmi.product.name: PRIMERGY TX1310 M1
dmi.sys.vendor: FUJITSU

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


** Tags: amd64 apport-bug xenial

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

Title:
  sr-iov not working on ubuntu 16.04 kvm

Status in linux package in Ubuntu:
  New

Bug description:
  The exact same set up (hardware and commands I have made) worked
  perfectly on Ubuntu 14.04 but I can't get it working with 16.04. The
  only thing I have changed between the 2 setups is adding  to the network definition as the now default vfio also
  failed with

  qemu-system-x86_64: vfio_dma_map(0x55f1c4f8bb00, 0xfe00, 0x4000, 
0x7fa68770) = -14 (Bad address)
  qemu: hardware error: vfio: DMA mapping failed, unable to continue

  If I am doing something wrong I apologise, this is my first bug report
  and I'm still relatively new to Linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-42-generic 4.4.0-42.62
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 14 20:11 seq
   crw-rw 1 root audio 116, 33 Oct 14 20:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Oct 14 23:05:26 2016
  HibernationDevice: RESUME=UUID=bb1632fb-69fe-4d67-bc51-8182d2546d91
  InstallationDate: Installed on 2016-10-08 (6 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: FUJITSU PRIMERGY TX1310 M1
  PciMultimedia:
   
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-42-generic 
root=UUID=07b95c7c-db77-4cee-8336-6f24b2072da6 ro pcie_aspm=off intel_iommu=on 
iommu=pt pci=assign-busses quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.4
  RfKill: Err

[Kernel-packages] [Bug 1626371] Re: cdc_ether fills kernel log

[Richard Powell]

Still reproduces in the latest upstream mainline kernel:

richard@server:~$ uname -a
Linux server 4.8.1-040801-generic #201610071031 SMP Fri Oct 7 14:34:10 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux


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

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

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

Title:
  cdc_ether fills kernel log

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo X1 4th gen with a dock attached:

  [ 1764.086306] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been 
dropped
  [ 1764.150317] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been 
dropped

  
  The USB Ethernet device would warn occasionally under the 4.4 kernel. Under 
the 4.8 kernel, it spams my kernel log so much that I don't get anything else.

  $ uname -a
  Linux aurora 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 20:00:03 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  joel@aurora ~ 
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

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

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

[Kernel-packages] [Bug 1633172] Re: Linux 4.8 as in 16.10 hangs during boot

[Dylan Borg]

After looking at those links, I realise that those debs need manual
installation. That is no problem for me and I will be trying them ASAP.

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

Title:
  Linux 4.8 as in 16.10 hangs during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel 
seemed to take ages to boot and appears to have hanged. I have managed to boot 
the system with the older 4.4 kernels from 16.04 just fine without any problems 
from systemd etc.. Please fix this so I can stop selecting the kernel manually 
on each boot.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2
  InstallationDate: Installed on 2016-02-19 (236 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-43-generic N/A
   linux-backports-modules-4.4.0-43-generic  N/A
   linux-firmware1.161
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.4.0-43-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3101
  dmi.board.asset.tag: Default string
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1633172/+subscriptions

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

[Kernel-packages] [Bug 1626371] Re: cdc_ether fills kernel log

[Richard Powell]

Same issue on yakkety with a Surface USB Ethernet device.

richard@server:~$ uname -a
Linux server 4.8.0-22-generic #24-Ubuntu SMP Sat Oct 8 09:15:00 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux

richard@server:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.10
Release:16.10
Codename:   yakkety

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

Title:
  cdc_ether fills kernel log

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo X1 4th gen with a dock attached:

  [ 1764.086306] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been 
dropped
  [ 1764.150317] cdc_ether 2-4.1.3:2.0 enx0050b6d331fe: kevent 11 may have been 
dropped

  
  The USB Ethernet device would warn occasionally under the 4.4 kernel. Under 
the 4.8 kernel, it spams my kernel log so much that I don't get anything else.

  $ uname -a
  Linux aurora 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 20:00:03 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
  joel@aurora ~ 
  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  Codename: yakkety

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

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

[Kernel-packages] [Bug 1631287] Re: CVE-2016-7039 and CVE-2016-8666

[Steve Beattie]

** Summary changed:

- CVE-2016-7039 and CVE-2016-
+ CVE-2016-7039 and CVE-2016-8666

** Description changed:

  CRD: Mon, Oct 10, 2016 (no time given)
  
  OWNERS
  security team: sbeattie
  kernel team:
  archive admin:
  
  CVE-2016-7039 fix has been sent by email
-  break-fix: 9b174d88c257150562b0101fcc6cb6c3cb74275c -
-  break-fix: 66e5133f19e901a044fa5eaeeb6ecff4545839e5 -
+  break-fix: 9b174d88c257150562b0101fcc6cb6c3cb74275c -
+  break-fix: 66e5133f19e901a044fa5eaeeb6ecff4545839e5 -
  
- CVE-2016- is addressed by upstream commit 
fac8e0f579695a3ecbc4d3cac369139d7f819971
-  break-fix: bf5a755f5e9186406bbf50f4087100af5bd68e40 
fac8e0f579695a3ecbc4d3cac369139d7f819971
+ CVE-2016-8666 is addressed by upstream commit 
fac8e0f579695a3ecbc4d3cac369139d7f819971
+  break-fix: bf5a755f5e9186406bbf50f4087100af5bd68e40 
fac8e0f579695a3ecbc4d3cac369139d7f819971

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

Title:
  CVE-2016-7039 and CVE-2016-8666

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  CRD: Mon, Oct 10, 2016 (no time given)

  OWNERS
  security team: sbeattie
  kernel team:
  archive admin:

  CVE-2016-7039 fix has been sent by email
   break-fix: 9b174d88c257150562b0101fcc6cb6c3cb74275c -
   break-fix: 66e5133f19e901a044fa5eaeeb6ecff4545839e5 -

  CVE-2016-8666 is addressed by upstream commit 
fac8e0f579695a3ecbc4d3cac369139d7f819971
   break-fix: bf5a755f5e9186406bbf50f4087100af5bd68e40 
fac8e0f579695a3ecbc4d3cac369139d7f819971

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

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

[Kernel-packages] [Bug 1633629] [NEW] arm64: KASLR breaks MODVERSIONS

[dann frazier]

Public bug reported:

[Impact]
On certain arm64 platforms, modules will not load. This doesn't impact any 
certified hardware to date, but is known to impact some pre-release platforms, 
as well as QEMU when a virtio-rng-pci device is attached.

[Test Case]
On a xenial/arm64 host, run:

sudo apt install qemu-system-arm qemu-efi
wget 
http://ports.ubuntu.com/ubuntu-ports/dists/yakkety/main/installer-arm64/20101020ubuntu483/images/netboot/mini.iso
cp /usr/share/AAVMF/AAVMF_CODE.fd flash0.img
cp /usr/share/AAVMF/AAVMF_VARS.fd flash1.img
sudo qemu-system-aarch64 -enable-kvm -m 2048 -cpu host -M virt,gic_version=host 
-nographic -pflash flash0.img -pflash flash1.img -drive 
file=mini.iso,id=cdrom,if=none,media=cdrom -device virtio-scsi-device -device 
scsi-cd,drive=cdrom -device virtio-rng-pci

Select Install from the GRUB menu, and continue through the installer
menus to "Detect network hardware".

On failure, the installer will report 'Error while running "modprobe -v
-b usb-storage"'. On success, it'll continue through to the network
configuration screens.

[Regression Risk]
This will be a simple cherry pick from upstream, so we'll have upstream support 
w/ any regressions.

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

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

Title:
  arm64: KASLR breaks MODVERSIONS

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  On certain arm64 platforms, modules will not load. This doesn't impact any 
certified hardware to date, but is known to impact some pre-release platforms, 
as well as QEMU when a virtio-rng-pci device is attached.

  [Test Case]
  On a xenial/arm64 host, run:

  sudo apt install qemu-system-arm qemu-efi
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/yakkety/main/installer-arm64/20101020ubuntu483/images/netboot/mini.iso
  cp /usr/share/AAVMF/AAVMF_CODE.fd flash0.img
  cp /usr/share/AAVMF/AAVMF_VARS.fd flash1.img
  sudo qemu-system-aarch64 -enable-kvm -m 2048 -cpu host -M 
virt,gic_version=host -nographic -pflash flash0.img -pflash flash1.img -drive 
file=mini.iso,id=cdrom,if=none,media=cdrom -device virtio-scsi-device -device 
scsi-cd,drive=cdrom -device virtio-rng-pci

  Select Install from the GRUB menu, and continue through the installer
  menus to "Detect network hardware".

  On failure, the installer will report 'Error while running "modprobe
  -v -b usb-storage"'. On success, it'll continue through to the network
  configuration screens.

  [Regression Risk]
  This will be a simple cherry pick from upstream, so we'll have upstream 
support w/ any regressions.

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

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

[Kernel-packages] [Bug 1633172] Re: Linux 4.8 as in 16.10 hangs during boot

[Dylan Borg]

Are those links to apt repositories or do I have to use dpkg manually?

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

Title:
  Linux 4.8 as in 16.10 hangs during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel 
seemed to take ages to boot and appears to have hanged. I have managed to boot 
the system with the older 4.4 kernels from 16.04 just fine without any problems 
from systemd etc.. Please fix this so I can stop selecting the kernel manually 
on each boot.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2
  InstallationDate: Installed on 2016-02-19 (236 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-43-generic N/A
   linux-backports-modules-4.4.0-43-generic  N/A
   linux-firmware1.161
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.4.0-43-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3101
  dmi.board.asset.tag: Default string
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1633172/+subscriptions

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

[Kernel-packages] [Bug 1609242] Re: Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

[Joseph Salisbury]

The bisect reported the following as the first bad commit:

commit b1b38278e12b04cf9a227f6af2c24651cf6e8a85
Author: David Weinehall 
Date:   Wed May 20 17:00:13 2015 +0300

drm/i915: add a context parameter to {en, dis}able zero address
mapping


I built a Xenial test kernel with this commit reverted.  The test kernel can be 
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1609242

Can you test that kernel and report back if it has the bug or not?

Note, to test this kernel, you need to install both the linux-image adn
linux-image-extra .deb 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/1609242

Title:
  Kernels 4.3-4.8 result in blackscreen - Intel Ivybridge

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

Bug description:
  When I install Ubuntu 16.04 on my computer the screen goes blank at
  login. I can blindly login and it boots but I cannot use the display
  (external monitor through HDMI).

  I've looked online for an answer to this issue but could not find a
  solution.  However, many people report this issue in forums with the
  4.4x kernel.

  On my main computer, I upgraded from 14.04 to 16.04.1. On this
  computer I was able to switch back to the 3.13 kernel which *does
  work*.

  On the same computer, if I use a 16.04 live CD, it does the same
  thing.  The screen goes blank.

  UEFI may be part of the issue as well.  I have it disabled in bios
  (set to legacy mode) but when I first boot, it seems to go into UEFI
  mode first and then, after rebooting with  it shows
  me the list of kernels. I can select the kernel from there but if I
  use a 4.4x kernel, it blanks out at encryption passphrase screen.

  There are also people with similar issues on AskUbuntu.

  Here's some basic HW info.  If you require more, please ask.

  sudo lshw | head
  zbox
  description: Notebook
  product: ZBOX-ID18 (NA)
  vendor: ZOTAC
  version: XX
  serial: G211X
  width: 64 bits
  capabilities: smbios-2.7 dmi-2.7 vsyscall32
  configuration: boot=normal chassis=notebook family=NA sku=NA 
uuid=00020003-0004-0005-0006-000700080009
    *-core

  sudo lshw -C display
    *-display
     description: VGA compatible controller
     product: 3rd Gen Core processor Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 09
     width: 64 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list rom
     configuration: driver=i915 latency=0
     resources: irq:45 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64)

  lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user5536 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: #RESUME=UUID=edaa55c6-eb56-43fb-8004-495948b72b38
  InstallationDate: Installed on 2014-07-23 (743 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140313)
  MachineType: ZOTAC ZBOX-ID18
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
  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-3.13.0-92-generic N/A
   linux-backports-modules-3.13.0-92-generic  N/A
   linux-firmware 1.157.2
  RfKill:

  StagingDrivers: rts5139
  Tags:  xenial staging
  Uname: Linux 3.13.0-92-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (3 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/13/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B211P011
  dmi.board.asset.tag: NA
  dmi.board.name: ZBOX-ID18
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: NA
  dmi.chassis.type: 10
  dmi.chassis.vendor: NA
  dmi.chassis.version: NA
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB211P011:bd03/13/2014:svnZOTAC:pnZBOX-ID18:pvrXX:rvnZOTAC:rnZBOX-ID18:rvrXX:cvnNA:ct10:cvrNA:
  dmi.product.name: ZBOX-ID18
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC

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

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

[Kernel-packages] [Bug 1633615] [NEW] package bluez 5.41-0ubuntu3 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[nil]

Public bug reported:

after upgrade to ubuntu 16.10

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: bluez 5.41-0ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
Date: Fri Oct 14 10:52:50 2016
ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
InstallationDate: Installed on 2013-11-30 (1049 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Inspiron 1545
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=03c53b2c-c3ae-48ae-a246-49246e8c0344 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.1
SourcePackage: bluez
Title: package bluez 5.41-0ubuntu3 failed to install/upgrade: sub-processo 
script post-installation instalado retornou estado de saída de erro 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0W299R
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd02/25/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0W299R:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1545
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 00:24:2B:F9:D9:87  ACL MTU: 1021:8  SCO MTU: 64:1
DOWN 
RX bytes:511 acl:0 sco:0 events:23 errors:0
TX bytes:339 acl:0 sco:0 commands:23 errors:0
rfkill:
 0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no

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


** Tags: amd64 apport-package yakkety

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

Title:
  package bluez 5.41-0ubuntu3 failed to install/upgrade: sub-processo
  script post-installation instalado retornou estado de saída de erro 1

Status in bluez package in Ubuntu:
  New

Bug description:
  after upgrade to ubuntu 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: bluez 5.41-0ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Fri Oct 14 10:52:50 2016
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  InstallationDate: Installed on 2013-11-30 (1049 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 1545
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic 
root=UUID=03c53b2c-c3ae-48ae-a246-49246e8c0344 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: bluez
  Title: package bluez 5.41-0ubuntu3 failed to install/upgrade: sub-processo 
script post-installation instalado retornou estado de saída de erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0W299R
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd02/25/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0W299R:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:24:2B:F9:D9:87  ACL MTU: 1021:8  SCO MTU: 64:1
DOWN 
RX bytes:511 acl:0 sco:0 events:23 errors:0
TX bytes:339 acl:0 sco:0 commands:23 errors:0
  rfkill:
   0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no

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

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

[Kernel-packages] [Bug 1632369] Re: linux-lts-vivid: 3.19.0-72.80~14.04.1 -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

Title:
  linux-lts-vivid: 3.19.0-72.80~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1632368
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1632369] Re: linux-lts-vivid: 3.19.0-72.80~14.04.1 -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

Title:
  linux-lts-vivid: 3.19.0-72.80~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1632368
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1633583] Re: Can not connect to Bluetooth headset

[Paul White]

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

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

Title:
  Can not connect to Bluetooth  headset

Status in bluez package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I managed to pair with my wireless headset, but I was unable to
  connect to it.

  Every time I try to do it, I get this message in syslog:
  Oct 14 21:38:09 localhost bluetoothd[2246]: Unable to get Headset Voice 
gateway SDP record: Host is down

  Relating info is below

   Info from bluetoothctl: 
  bluetooth]# devices 
  Device 00:1B:66:03:C4:66 MOMENTUM M2 AEBT
  bluetooth]# info 00:1B:66:03:C4:66
  Device 00:1B:66:03:C4:66
  Name: MOMENTUM M2 AEBT
  Alias: MOMENTUM M2 AEBT
  Class: 0x240404
  Icon: audio-card
  Paired: yes
  Trusted: yes
  Blocked: no
  Connected: no
  LegacyPairing: yes
  UUID: Headset   (1108--1000-8000-00805f9b34fb)
  UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
  UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
  UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
  UUID: Handsfree (111e--1000-8000-00805f9b34fb)
  UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
  UUID: Vendor specific   (1ddce62a-ecb1-4455-8153-0743c87aec9f)
  Modalias: bluetooth:v0082p004Bd010E

  
   Info from hciconfig 
  $ sudo hciconfig -a
  [sudo] password for dimanne: 
  hci0:   Type: Primary  Bus: USB
  BD Address: 5C:F3:70:73:F2:B1  ACL MTU: 1021:8  SCO MTU: 64:1
  UP RUNNING PSCAN ISCAN 
  RX bytes:14866 acl:33 sco:0 events:2022 errors:0
  TX bytes:17848 acl:33 sco:0 commands:1639 errors:0
  Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
  Link policy: RSWITCH SNIFF 
  Link mode: SLAVE ACCEPT 
  Name: 'impedance #1'
  Class: 0x1c0104
  Service Classes: Rendering, Capturing, Object Transfer
  Device Class: Computer, Desktop workstation
  HCI Version: 4.0 (0x6)  Revision: 0x1000
  LMP Version: 4.0 (0x6)  Subversion: 0x220e
  Manufacturer: Broadcom Corporation (15)

  hci1:   Type: Primary  Bus: USB
  BD Address: 54:27:1E:33:4B:85  ACL MTU: 1021:8  SCO MTU: 64:1
  DOWN 
  RX bytes:2926 acl:0 sco:0 events:161 errors:0
  TX bytes:5699 acl:0 sco:0 commands:157 errors:0
  Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
  Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
  Link policy: RSWITCH SNIFF 
  Link mode: SLAVE ACCEPT 

  
   rfkill: 
  $ rfkill list
  1: hci1: Bluetooth
  Soft blocked: no
  Hard blocked: no
  2: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  
   Info from dmesg: 
  $ dmesg | grep -i blue
  [5.170808] Bluetooth: Core ver 2.21
  [5.170819] Bluetooth: HCI device and connection manager initialized
  [5.170821] Bluetooth: HCI socket layer initialized
  [5.170822] Bluetooth: L2CAP socket layer initialized
  [5.170826] Bluetooth: SCO socket layer initialized
  [5.185923] Bluetooth: hci0: BCM: chip id 63
  [5.186665] Bluetooth: hci1: BCM: chip id 63
  [5.202506] Bluetooth: hci0: impedance #2
  [5.203150] Bluetooth: hci1: ChromeLinux_5818
  [5.203498] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [5.203670] bluetooth hci0: Direct firmware load for 
brcm/BCM20702A1-0b05-17cb.hcd failed with error -2
  [5.203671] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0b05-17cb.hcd not 
found
  [5.204662] Bluetooth: hci1: BCM20702A1 (001.002.014) build 
  [5.204671] bluetooth hci1: Direct firmware load for 
brcm/BCM20702A1-0b05-17cf.hcd failed with error -2
  [5.204671] Bluetooth: hci1: BCM: Patch brcm/BCM20702A1-0b05-17cf.hcd not 
found
  [   11.359871] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   11.359872] Bluetooth: BNEP filters: protocol multicast
  [   11.359874] Bluetooth: BNEP socket layer initialized
  [   34.046364] Bluetooth: RFCOMM TTY layer initialized
  [   34.046368] Bluetooth: RFCOMM socket layer initialized
  [   34.046371] Bluetooth: RFCOMM ver 1.11
  [ 1193.523500] Bluetooth: hci0: BCM: chip id 63
  [ 1193.539525] Bluetooth: hci0: BCM20702A
  [ 1193.540524] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [ 1193.540535] bluetooth hci0: Direct firmware load for 
brcm/BCM20702A1-0b05-17cb.hcd failed with e

[Kernel-packages] [Bug 1633267] Re: Wifi and sound no longer detected in kernel 4.4.0-43

[Alexis de Lattre]

I've also been hit by this critical bug on my Thinkpad T550 (intel
graphic card). The symptom was that I had a very low resolution on boot
; Xorg logs showed it was using vesa ! Then I installed the package
linux-image-extra-4.4.0-43-generic and everything went back to normal.

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

Title:
  Wifi and sound no longer detected in kernel 4.4.0-43

Status in One Hundred Papercuts:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 
and rebooting the system didn't seem to recognize my Wifi or sound hardware: 
there was no Wifi icon or ability to connect to a network, and the only output 
on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matt   3400 F pulseaudio
   /dev/snd/controlC1:  matt   3400 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423
  InstallationDate: Installed on 2015-08-23 (417 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  MachineType: LENOVO 20ANCTO1WW
  Package: linux (not installed)
  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.4.0-42-generic.efi.signed 
root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.4
  Tags:  xenial
  Uname: Linux 4.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET84WW (2.38 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ANCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ANCTO1WW
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1632045] Re: KVM: PPC: Book3S HV: Migrate pinned pages out of CMA

[Tim Gardner]

sarah.han...@us.ibm.com - the earliest you will see a proposed kernel
with this fix commit is the week of Oct 31, 2016 with release to
-updates on Nov 21

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

Title:
  KVM: PPC: Book3S HV: Migrate pinned pages out of CMA

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  ---Problem Description---
  https://github.com/open-power/supermicro-openpower/issues/59

  SW/HW Configuration

  PNOR image version: 5/3/2016
  BMC image version: 0.25
  CPLD Version: B2.81.01
  Host OS version: Ubuntu 16.04 LTS
  UbuntuKVM Guest OS version: Ubuntu 14.04.4 LTS
  HTX version: 394
  Processor: 00UL865 * 2
  Memory: SK hynix 16GB 2Rx4 PC4-2133P * 16
  Summary of Issue

  Two UbuntuKVM guests are each configured with 8 processors, 64 GB of
  memory, 1 disk of 128 GB, 1 network interface, and 1 GPU (pass-
  through'd from the Host OS's K80).

  The two guests are each put into a Create/Destroy loop, with HTX
  running on each of the guests (NOT HOST) in between its creation and
  destruction. The mdt.bu profile is used, and the processors, memory,
  and the GPU are put under load. The HTX session lasts 9 minutes.

  While this is running, the amount of available memory (free memory) in
  the Host OS will slowly decrease, and this can continue until the
  point wherein there's no more free memory for the Host OS to do
  anything, including creating the two VM guests. It seems to be that
  after every cycle, a small portion of the memory that was allocated to
  the VM guest does not get released back to the Host OS, and
  eventually, this can and will add up to take up all the available
  memory in the Host OS.

  At some point, the VM guest(s) might get disconnected and will display
  the following error:

  error: Disconnected from qemu:///system due to I/O error

  error: One or more references were leaked after disconnect from
  the hypervisor

  Then, when the Host OS tries to start the VM guest again, the
  following error shows up:

  error: Failed to create domain from guest2_trusty.xml
  error: internal error: early end of file from monitor, possible problem: 
Unexpected error in spapr_alloc_htab() at 
/build/qemu-c3ZrbA/qemu-2.5+dfsg/hw/ppc/spapr.c:1030:
  2016-05-23T16:18:16.871549Z qemu-system-ppc64: Failed to allocate HTAB of 
requested size, try with smaller maxmem

  The Host OS syslog, as seen HERE, also contains quite some errors.
  To just list a few:

  May 13 20:27:44 191-136 kernel: [36827.151228] alloc_contig_range: 
[3fb800, 3fd8f8) PFNs busy
  May 13 20:27:44 191-136 kernel: [36827.151291] alloc_contig_range: 
[3fb800, 3fd8fc) PFNs busy
  May 13 20:27:44 191-136 libvirtd[19263]: *** Error in 
`/usr/sbin/libvirtd': realloc(): invalid next size: 0x01000a780400 ***
  May 13 20:27:44 191-136 libvirtd[19263]: === Backtrace: =
  May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(+0x8720c)[0x3fffaf6a720c]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(+0x96f70)[0x3fffaf6b6f70]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(realloc+0x16c)[0x3fffaf6b87fc]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virReallocN+0x68)[0x3fffaf90ccc8]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0x8ef6c)[0x3fff9346ef6c]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0xa826c)[0x3fff9348826c]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventPollRunOnce+0x8b4)[0x3fffaf9332b4]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventRunDefaultImpl+0x54)[0x3fffaf931334]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virNetDaemonRun+0x1f0)[0x3fffafad2f70]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/sbin/libvirtd(+0x15d74)[0x52e45d74]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(+0x2319c)[0x3fffaf64319c]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(__libc_start_main+0xb8)[0x3fffaf6433b8]
  May 13 20:27:44 191-136 libvirtd[19263]: === Memory map: 
  May 13 20:27:44 191-136 libvirtd[19263]: 52e3-52eb r-xp  
08:02 65540510 /usr/sbin/libvirtd
  May 13 20:27:44 191-136 libvirtd[19263]: 52ec-52ed r--p 0008 
08:02 65540510 /usr/sbin/libvirtd
  May 13 20:27:44 191-136 libvirtd[19263]: 52ed-52ee rw-p 0009 
08:02 65540510 /usr/sbin/libvirtd
  M

Re: [Kernel-packages] [Bug 1628586] Re: using version 4.4.0-38-generic, x86_64 on MacMini

[Gerald Lovel]

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

This is my experience as well. I believe this was part of the original bug,
but the important issue is that because $USER does not work, automated file
system attaches using user credentials do not work. (Or to make them work,
we would have to have an autofs.conf file with special-case logic for every
possible user, contrary to the point of the utility.)

Or, we could drop the user certificate logins and use root login with share
passwords, defeating the security of the shares. Therefore the bug is a
security issue, and the priority should be upped accordingly.

Gerald

Gerald Lovel   |  901.276.1004
glo...@aaltsys.com |  AAltSys.com
AAltSys Technology Center


On Fri, Oct 14, 2016 at 11:49 AM, kalyp <1628...@bugs.launchpad.net>
wrote:

> *** This bug is a duplicate of bug 1626749 ***
> https://bugs.launchpad.net/bugs/1626749
>
> I don't think this is a duplicate bug, or rather, I am not affected by
> this one and am by #1626749. On my side, replacing $USER by my username
> works. I have 2 identical lines in autofs, one with
> credentials=/home/$USER/.credentials (fails as it looks for
> /home/root/.credentials), one with
> credentials=/home/myusername/.credentials (works just fine for me).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1628586
>
> Title:
>   using version 4.4.0-38-generic, x86_64 on MacMini
>
> Status in linux package in Ubuntu:
>   New
>
> Bug description:
>   Confirmation of bug #1626749 regarding $USER token substitution
>   problem in autofs. Even when the $USER token was replaced with a valid
>   username for the share, autofs was unable to mount shares using
>   certificates, nor could sshfs. These programs reverted to password
>   authentication instead. The reason for mounting with certificates
>   instead of passwords is security, of course.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1628586/+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/1628586

Title:
  using version 4.4.0-38-generic, x86_64 on MacMini

Status in linux package in Ubuntu:
  New

Bug description:
  Confirmation of bug #1626749 regarding $USER token substitution
  problem in autofs. Even when the $USER token was replaced with a valid
  username for the share, autofs was unable to mount shares using
  certificates, nor could sshfs. These programs reverted to password
  authentication instead. The reason for mounting with certificates
  instead of passwords is security, of course.

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

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

[Kernel-packages] [Bug 1633577] Re: linux: Enable live patching for all supported architectures

[Tim Gardner]

** Description changed:

- In the interested of feature parity, live patching should be enabled on
+ In the interest of feature parity, live patching should be enabled on
  all supported architectures.

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

Title:
  linux: Enable live patching for all supported architectures

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  In the interest of feature parity, live patching should be enabled on
  all supported architectures.

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

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

[Kernel-packages] [Bug 1632368] Re: linux: 3.19.0-72.80 -proposed tracker

[Andy Whitcroft]

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

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

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

Title:
  linux: 3.19.0-72.80 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.19.0-72.80 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
  derivative-trackers-created: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1633577] Re: linux: Enable live patching for all supported architectures

[Tim Gardner]

https://lists.ubuntu.com/archives/kernel-team/2016-October/080378.html

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

Title:
  linux: Enable live patching for all supported architectures

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  In the interested of feature parity, live patching should be enabled
  on all supported architectures.

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

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

[Kernel-packages] [Bug 1632918] Re: linux: 4.8.0-25.27 -proposed tracker

[Andy Whitcroft]

** Changed in: kernel-development-workflow/promote-to-proposed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft 
(apw)

** Changed in: kernel-development-workflow/promote-to-proposed
   Status: Confirmed => In Progress

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

Title:
  linux: 4.8.0-25.27 -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:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  In Progress
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 Yakkety:
  Confirmed

Bug description:
  This bug is for tracking the 4.8.0-25.27 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
  derivative-trackers-created: true
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1633579] Re: zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build

[James]

Please close. Was filesystem resource issue. Module built successfully
after removing extraneous /boot images.

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  n/a; just doing regular apt update && apt upgrade

  /boot is 86% with 68M free

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu14
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-43-generic (x86_64)
   Fri Oct 14 14:19:06 EDT 2016
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.4.0-43-generic
  Date: Fri Oct 14 14:19:10 2016
  InstallationDate: Installed on 2016-05-23 (144 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 0.6.5.6-0ubuntu14
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build
  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/1633579/+subscriptions

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

[Kernel-packages] [Bug 1633579] Re: zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build

[James]

/boot 86% at start; 94% at completion.

Did see this though...

...
gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
...

Filesystem  Size  Used Avail Use% Mounted on
udev7.8G 0  7.8G   0% /dev
tmpfs   1.6G   18M  1.6G   2% /run
rpool/ROOT  226G   34G  192G  15% /
tmpfs   7.8G  221M  7.6G   3% /dev/shm
tmpfs   5.0M  4.0K  5.0M   1% /run/lock
tmpfs   7.8G 0  7.8G   0% /sys/fs/cgroup
/dev/sda1   465M  432M   29M  94% /boot
tmpfs   1.6G  100K  1.6G   1% /run/user/1000

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  n/a; just doing regular apt update && apt upgrade

  /boot is 86% with 68M free

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu14
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-43-generic (x86_64)
   Fri Oct 14 14:19:06 EDT 2016
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.4.0-43-generic
  Date: Fri Oct 14 14:19:10 2016
  InstallationDate: Installed on 2016-05-23 (144 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 0.6.5.6-0ubuntu14
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build
  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/1633579/+subscriptions

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

[Kernel-packages] [Bug 1633579] Re: zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build

[James]

A pre build, space allocation calculation, before dkms attempt? Leave
package partially configured and warn?

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  n/a; just doing regular apt update && apt upgrade

  /boot is 86% with 68M free

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu14
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-43-generic (x86_64)
   Fri Oct 14 14:19:06 EDT 2016
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.4.0-43-generic
  Date: Fri Oct 14 14:19:10 2016
  InstallationDate: Installed on 2016-05-23 (144 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 0.6.5.6-0ubuntu14
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build
  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/1633579/+subscriptions

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

[Kernel-packages] [Bug 1633579] [NEW] zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build

[James]

Public bug reported:

n/a; just doing regular apt update && apt upgrade

/boot is 86% with 68M free

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: zfs-dkms 0.6.5.6-0ubuntu14
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
DKMSBuildLog:
 DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-43-generic (x86_64)
 Fri Oct 14 14:19:06 EDT 2016
 make: *** No targets specified and no makefile found.  Stop.
DKMSKernelVersion: 4.4.0-43-generic
Date: Fri Oct 14 14:19:10 2016
InstallationDate: Installed on 2016-05-23 (144 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageVersion: 0.6.5.6-0ubuntu14
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: zfs-linux
Title: zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  n/a; just doing regular apt update && apt upgrade

  /boot is 86% with 68M free

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu14
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-43-generic (x86_64)
   Fri Oct 14 14:19:06 EDT 2016
   make: *** No targets specified and no makefile found.  Stop.
  DKMSKernelVersion: 4.4.0-43-generic
  Date: Fri Oct 14 14:19:10 2016
  InstallationDate: Installed on 2016-05-23 (144 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 0.6.5.6-0ubuntu14
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu14: zfs kernel module failed to build
  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/1633579/+subscriptions

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

[Kernel-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

[Isaac]

Same problem here with a Dell Latitude e5470.
Tried in Ubuntu 16.04 and 16.10.

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

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Kernel-packages] [Bug 1633577] [NEW] linux: Enable live patching for all supported architectures

[Tim Gardner]

Public bug reported:

In the interested of feature parity, live patching should be enabled on
all supported architectures.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Affects: linux (Ubuntu Xenial)
 Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

** Affects: linux (Ubuntu Yakkety)
 Importance: Undecided
 Assignee: Tim Gardner (timg-tpi)
 Status: In Progress

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

** Changed in: linux (Ubuntu Yakkety)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  linux: Enable live patching for all supported architectures

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  In the interested of feature parity, live patching should be enabled
  on all supported architectures.

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

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

[Kernel-packages] [Bug 1633404] Re: audit: prevent a new auditd to stop an old auditd still alive

[Joseph Salisbury]

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

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

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

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

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

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

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

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

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

Title:
  audit: prevent a new auditd to stop an old auditd still alive

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

Bug description:
  The following upstream patch (v4.6) has fixed this problem:

  audit: stop an old auditd being starved out by a new auditd
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=133e1e5acd4a

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

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

[Kernel-packages] [Bug 1633058] Re: ghash-clmulni-intel module fails to load

[Joseph Salisbury]

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

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

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

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

Title:
  ghash-clmulni-intel module fails to load

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

Bug description:
  The module ghash-clmulni-intel always fails to load with "Invalid
  argument":

  $ sudo modprobe ghash-clmulni-intel
  modprobe: ERROR: could not insert 'ghash_clmulni_intel': Invalid argument

  That was caused by the commit 8996eafdc ("crypto: ahash - ensure
  statesize is non-zero"), that added a requirement that all ahash
  algorithms now need to implement import() and export() and define a
  non zero statesize.

  The fix is composed by two commits:

  3a020a7 crypto: ghash-clmulni - Fix load failure
  1a07834 crypto: cryptd - Assign statesize properly

  Xenial and Trusty are affected and Yakkety already included the
  solution above.

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

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

[Kernel-packages] [Bug 1630063] Re: specific USB devices disconnect and don't reconnect

[Bryan P]

Yes I can. I will work on this tonight.

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

Title:
  specific USB devices disconnect and don't reconnect

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

Bug description:
  2 USB ports randomly disconnect and don't reconnect (it's always the
  same two), and in dmesg all I get is

  "
  [ 1276.916458] ohci-pci :00:12.0: HcDoneHead not written back; disabled
  [ 1276.916467] ohci-pci :00:12.0: HC died; cleaning up
  [ 1276.916553] usb 3-1: USB disconnect, device number 2
  [ 1277.017302] usb 3-2: USB disconnect, device number 3
  "
  This only started happening when Yakkety went to the 4.8 branch, with 4.7 
branch this doesn't occur, hence the bug report since it's unlikely that a 
hardware failure will only stick to one OS and one branch of the kernel for 
that OS. (these USB ports don't randomly die on Windows or BSD, I've tested 
that in the past couple of days)

  
  kernel version: 4.8.0.17.27
  Ubuntu version
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  c_smith2213 F pulseaudio
   /dev/snd/controlC0:  c_smith2213 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1a29baaa-55ea-4817-ba45-8c618f65ec4b
  InstallationDate: Installed on 2016-10-03 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20161002)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic 
root=/dev/mapper/Linux-root ro nomodeset quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/09/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-78LMT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1633019] Re: BT driver in dell xps 9343 not functioning

[Joseph Salisbury]

Can you test the following two kernels? If 4.7 is good and 4.8-rc1 is
bad, we can bisect between those two:

4.7 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/
4.8-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc1/

If both those kernels are good, we can test later 4.8 release
candidates. If they are both bad, we can test some of the 4.7 release
candidates.

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

** Also affects: linux (Ubuntu Yakkety)
   Importance: Medium
   Status: Confirmed

** Tags added: kernel-da-key

** Tags removed: kernel-da-key
** 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/1633019

Title:
  BT driver in dell xps 9343 not functioning

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

Bug description:
  Scanning reveals no mice, keyboards or computers.

  Everything looks to be fine but the Bluetooth seemingly does nothing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.8.0-22-generic 4.8.0-22.24 [modified: 
boot/vmlinuz-4.8.0-22-generic]
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   2157 F pulseaudio
   /dev/snd/controlC1:  dave   2157 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Oct 13 11:08:00 2016
  HibernationDevice: RESUME=UUID=7a85aeaa-7621-4d4f-8dd3-f28c0426f22a
  InstallationDate: Installed on 2016-10-13 (0 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-22-generic.efi.signed 
root=UUID=ed0a9de6-b9f4-4471-843b-2d8d2135c189 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-22-generic N/A
   linux-backports-modules-4.8.0-22-generic  N/A
   linux-firmware1.161
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1633058] Re: ghash-clmulni-intel module fails to load

[Joseph Salisbury]

Please ignore comment #2.  Posted in the wrong bug report.

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

Title:
  ghash-clmulni-intel module fails to load

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

Bug description:
  The module ghash-clmulni-intel always fails to load with "Invalid
  argument":

  $ sudo modprobe ghash-clmulni-intel
  modprobe: ERROR: could not insert 'ghash_clmulni_intel': Invalid argument

  That was caused by the commit 8996eafdc ("crypto: ahash - ensure
  statesize is non-zero"), that added a requirement that all ahash
  algorithms now need to implement import() and export() and define a
  non zero statesize.

  The fix is composed by two commits:

  3a020a7 crypto: ghash-clmulni - Fix load failure
  1a07834 crypto: cryptd - Assign statesize properly

  Xenial and Trusty are affected and Yakkety already included the
  solution above.

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

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

[Kernel-packages] [Bug 1633172] Re: Linux 4.8 as in 16.10 hangs during boot

[Joseph Salisbury]

If both those kernels are good, we can test later 4.8 release
candidates.  If they are both bad, we can test some of the 4.7 release
candidates.

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

Title:
  Linux 4.8 as in 16.10 hangs during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel 
seemed to take ages to boot and appears to have hanged. I have managed to boot 
the system with the older 4.4 kernels from 16.04 just fine without any problems 
from systemd etc.. Please fix this so I can stop selecting the kernel manually 
on each boot.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2
  InstallationDate: Installed on 2016-02-19 (236 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-43-generic N/A
   linux-backports-modules-4.4.0-43-generic  N/A
   linux-firmware1.161
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.4.0-43-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3101
  dmi.board.asset.tag: Default string
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1633172/+subscriptions

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

[Kernel-packages] [Bug 1633058] Re: ghash-clmulni-intel module fails to load

[Joseph Salisbury]

Can you test the following two kernels? If 4.7 is good and 4.8-rc1 is
bad, we can bisect between those two:

4.7 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/
4.8-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc1/

If both those kernels are good, we can test later 4.8 release
candidates. If they are both bad, we can test some of the 4.7 release
candidates.


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

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

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

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

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

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

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

** Tags added: kernel-da-key trusty xenial

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

Title:
  ghash-clmulni-intel module fails to load

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

Bug description:
  The module ghash-clmulni-intel always fails to load with "Invalid
  argument":

  $ sudo modprobe ghash-clmulni-intel
  modprobe: ERROR: could not insert 'ghash_clmulni_intel': Invalid argument

  That was caused by the commit 8996eafdc ("crypto: ahash - ensure
  statesize is non-zero"), that added a requirement that all ahash
  algorithms now need to implement import() and export() and define a
  non zero statesize.

  The fix is composed by two commits:

  3a020a7 crypto: ghash-clmulni - Fix load failure
  1a07834 crypto: cryptd - Assign statesize properly

  Xenial and Trusty are affected and Yakkety already included the
  solution above.

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

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

[Kernel-packages] [Bug 1633172] Re: Linux 4.8 as in 16.10 hangs during boot

[Joseph Salisbury]

Can you test the following two kernels?  If 4.7 is good and 4.8-rc1 is
bad, we can bisect between those two:

4.7 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/
4.8-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc1/

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

** Tags added: kernel-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/1633172

Title:
  Linux 4.8 as in 16.10 hangs during boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have just upgraded to 16.10 and restarted my machine. The new 4.8 kernel 
seemed to take ages to boot and appears to have hanged. I have managed to boot 
the system with the older 4.4 kernels from 16.04 just fine without any problems 
from systemd etc.. Please fix this so I can stop selecting the kernel manually 
on each boot.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1147110e-7ff9-41b0-a446-ac19e62a85c2
  InstallationDate: Installed on 2016-02-19 (236 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp4s0no wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: ASUS All Series
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-43-generic 
root=UUID=c4c28e9f-4a06-4a3d-b8c3-05297050ebca ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-43-generic N/A
   linux-backports-modules-4.4.0-43-generic  N/A
   linux-firmware1.161
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.4.0-43-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (0 days ago)
  UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/04/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3101
  dmi.board.asset.tag: Default string
  dmi.board.name: SABERTOOTH X99
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3101:bd05/04/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTHX99:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  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/1633172/+subscriptions

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

[Kernel-packages] [Bug 1633267] Re: Wifi and sound no longer detected in kernel 4.4.0-43

[Joseph Salisbury]

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

** Tags added: kernel-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/1633267

Title:
  Wifi and sound no longer detected in kernel 4.4.0-43

Status in One Hundred Papercuts:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 
and rebooting the system didn't seem to recognize my Wifi or sound hardware: 
there was no Wifi icon or ability to connect to a network, and the only output 
on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matt   3400 F pulseaudio
   /dev/snd/controlC1:  matt   3400 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423
  InstallationDate: Installed on 2015-08-23 (417 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  MachineType: LENOVO 20ANCTO1WW
  Package: linux (not installed)
  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.4.0-42-generic.efi.signed 
root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.4
  Tags:  xenial
  Uname: Linux 4.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET84WW (2.38 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ANCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ANCTO1WW
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1611078] Re: Support snaps inside of lxd containers

[John Johansen]

** Also affects: apparmor (Ubuntu Yakkety)
   Importance: Critical
 Assignee: Tyler Hicks (tyhicks)
   Status: Fix Released

** Also affects: linux (Ubuntu Yakkety)
   Importance: Critical
 Assignee: John Johansen (jjohansen)
   Status: Fix Released

** Also affects: lxd (Ubuntu Yakkety)
   Importance: Critical
 Assignee: Stéphane Graber (stgraber)
   Status: 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/1611078

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxd source package in Yakkety:
  Fix Released

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

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

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

[Kernel-packages] [Bug 1633391] Re: Ubuntu doesn't boot anymore {REGRESSION}

[Joseph Salisbury]

This could be related to bug 1632902.  Can you also see if the -36
kernel boots, but not -38?

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

Title:
  Ubuntu doesn't boot anymore {REGRESSION}

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

Bug description:
  After I upgraded to latest kernel, Ubuntu does not boot without messing with 
grub (I had to delete quiet splash options). 
  Before upgrade it was OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-42-generic 4.4.0-42.62
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tomas  2090 F pulseaudio
   /dev/snd/controlC1:  tomas  2090 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Oct 14 11:32:56 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ff267c2-ec30-4f81-975c-46640f436942
  InstallationDate: Installed on 2016-09-13 (30 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 10104
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-42-generic 
root=UUID=fd50bb86-da1a-45bb-957b-ea19b330d7ff ro rootflags=subvol=@ 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.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/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ELKT31AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193 STD
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrELKT31AUS:bd03/21/2013:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvr3193STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.name: 10104
  dmi.product.version: Lenovo C440
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1633492] Re: Ubuntu 16.04 LTS Wifi, Eth connection not detected when booting on 4.4.0-43

[Joseph Salisbury]

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

** This bug has been marked a duplicate of bug 1633267
   Wifi and sound no longer detected in kernel 4.4.0-43

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

Title:
  Ubuntu 16.04 LTS  Wifi, Eth connection not detected when booting on
  4.4.0-43

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

Bug description:
  I'm running Ubuntu 16.04 LTS on a DELL Vostro 15 3300. On upgrading to 
4.4.0-43 and rebooting the system didn't seem to recognize Eth cable or Wifi, 
nor my mouse (connected to USB): 
  There was no Wifi ability to detect any network, neither the eth cable. After 
trying to load drivers via USB, I also notice that any USB port couldn't 
recognize usb sticks
  Rebooting into 4.4.0-42 solved the issue. I can't send ubuntu-bug linux 
because I can't connect on the current 4.4.0-43.

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

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

[Kernel-packages] [Bug 1632902] Re: kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36

[Joseph Salisbury]

This could be related to bug 1633391

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

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

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

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

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

Title:
  kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36

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

Bug description:
  This occurred after rebooting after running Kubuntu's Update Manager
  5.6.2 on 2016-10-12. Unfortunately, I hadn't rebooted after the last
  update that required me to do so, and thus I don't know if the problem
  was from that update or this one.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jacob  1494 F pulseaudio
   /dev/snd/controlC0:  jacob  1494 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Oct 12 19:54:03 2016
  HibernationDevice: RESUME=UUID=c5fdca37-edfe-4f31-928b-970bd6696164
  InstallationDate: Installed on 2016-05-25 (140 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=c70ba36b-21e9-48ae-bf12-79060d17dcfc ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.4
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/02/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1632902] Re: kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36

[Joseph Salisbury]

I'd like to perform a bisect to identify the commit that introduced this
regression. Can you test the following kernels and see which ones
exhibit the bug:

4.4.19: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.19/
4.4.20: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.20/
4.4.21: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.21

You don't have to test all of them, just up until the first one shows
the bug.


Thanks in advance!

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

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

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

Title:
  kernel panic when booting 4.4.0-42 and 4.4.0-38, but not 4.4.0-36

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

Bug description:
  This occurred after rebooting after running Kubuntu's Update Manager
  5.6.2 on 2016-10-12. Unfortunately, I hadn't rebooted after the last
  update that required me to do so, and thus I don't know if the problem
  was from that update or this one.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-36-generic 4.4.0-36.55
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jacob  1494 F pulseaudio
   /dev/snd/controlC0:  jacob  1494 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Oct 12 19:54:03 2016
  HibernationDevice: RESUME=UUID=c5fdca37-edfe-4f31-928b-970bd6696164
  InstallationDate: Installed on 2016-05-25 (140 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=c70ba36b-21e9-48ae-bf12-79060d17dcfc ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.4
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-DS3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/02/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.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: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1633557] [NEW] zfs not installed on yakety upgrade

[Cyrus Harmon]

Public bug reported:

On upgrading to yakety, zfs was no longer installed. I manually
installed zfsutils-linux and that fixed things, but it was rather
disconcerting to (temporarily) lose my zfs volume on upgrading.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: zfsutils-linux 0.6.5.8-0ubuntu4
ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
Uname: Linux 4.8.0-22-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Oct 14 09:47:31 2016
InstallationDate: Installed on 2015-07-28 (444 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: zfs-linux
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)
modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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


** Tags: amd64 apport-bug yakkety

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

Title:
  zfs not installed on yakety upgrade

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  On upgrading to yakety, zfs was no longer installed. I manually
  installed zfsutils-linux and that fixed things, but it was rather
  disconcerting to (temporarily) lose my zfs volume on upgrading.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: zfsutils-linux 0.6.5.8-0ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 09:47:31 2016
  InstallationDate: Installed on 2015-07-28 (444 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: zfs-linux
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)
  modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/zfs']

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

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

[Kernel-packages] [Bug 1611078] Re: Support snaps inside of lxd containers

[Stéphane Graber]

** Changed in: lxd (Ubuntu Xenial)
   Status: New => 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/1611078

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released
Status in lxd source package in Yakkety:
  Fix Released

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

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

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

[Kernel-packages] [Bug 1626749] Re: autofs set $USER to "root" instead of current user

[kalyp]

The bug is still occurring with kernel 4.4.0-43, as a FYI.

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

Title:
  autofs set $USER to "root" instead of current user

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since last kernel upgrade from 4.4.0-36 to 4.4.0-38 automount failed to mount 
remote smb FS.
  The configuration file use $USER, $UID and $GID variables :
  i.e. :
  music 
-fstype=cifs,credentials=/home/$USER/.creds-file,user=$USER,uid=$UID,gid=$GID 
://192.168.1.9/music

  When a user account try to mount the FS, automount complain :

   >> error 2 (No such file or directory) opening credential file
  /home/root/.creds-file

  $USER, $UID and $GID are now sets with root variables instead of user
  account variables

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: autofs 5.1.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep 22 23:17:27 2016
  ExecutablePath: /usr/sbin/automount
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
  SourcePackage: autofs
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nicolas1941 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1ad9a17c-8b27-4436-a024-6c9ae99a5b87
  InstallationDate: Installed on 2016-02-07 (228 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Sony Corporation SVS1511R9ES
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=fr_FR
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic.efi.signed 
root=UUID=df815dd3-2e1b-42d3-aef8-1823eb5d4f75 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.157.3
  Tags:  xenial
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-28 (147 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/30/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0140C5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0140C5:bd03/30/2012:svnSonyCorporation:pnSVS1511R9ES:pvrC60AGQAL:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVS1511R9ES
  dmi.product.version: C60AGQAL
  dmi.sys.vendor: Sony Corporation

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

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

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

[bugproxy]

--- Comment From sarah.han...@us.ibm.com 2016-10-14 12:38 EDT---
When can we expect the patch? This defect is still blocking many of our tests.

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

Title:
  KVM: PPC: Book3S HV: Migrate pinned pages out of CMA

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Yakkety:
  In Progress

Bug description:
  ---Problem Description---
  https://github.com/open-power/supermicro-openpower/issues/59

  SW/HW Configuration

  PNOR image version: 5/3/2016
  BMC image version: 0.25
  CPLD Version: B2.81.01
  Host OS version: Ubuntu 16.04 LTS
  UbuntuKVM Guest OS version: Ubuntu 14.04.4 LTS
  HTX version: 394
  Processor: 00UL865 * 2
  Memory: SK hynix 16GB 2Rx4 PC4-2133P * 16
  Summary of Issue

  Two UbuntuKVM guests are each configured with 8 processors, 64 GB of
  memory, 1 disk of 128 GB, 1 network interface, and 1 GPU (pass-
  through'd from the Host OS's K80).

  The two guests are each put into a Create/Destroy loop, with HTX
  running on each of the guests (NOT HOST) in between its creation and
  destruction. The mdt.bu profile is used, and the processors, memory,
  and the GPU are put under load. The HTX session lasts 9 minutes.

  While this is running, the amount of available memory (free memory) in
  the Host OS will slowly decrease, and this can continue until the
  point wherein there's no more free memory for the Host OS to do
  anything, including creating the two VM guests. It seems to be that
  after every cycle, a small portion of the memory that was allocated to
  the VM guest does not get released back to the Host OS, and
  eventually, this can and will add up to take up all the available
  memory in the Host OS.

  At some point, the VM guest(s) might get disconnected and will display
  the following error:

  error: Disconnected from qemu:///system due to I/O error

  error: One or more references were leaked after disconnect from
  the hypervisor

  Then, when the Host OS tries to start the VM guest again, the
  following error shows up:

  error: Failed to create domain from guest2_trusty.xml
  error: internal error: early end of file from monitor, possible problem: 
Unexpected error in spapr_alloc_htab() at 
/build/qemu-c3ZrbA/qemu-2.5+dfsg/hw/ppc/spapr.c:1030:
  2016-05-23T16:18:16.871549Z qemu-system-ppc64: Failed to allocate HTAB of 
requested size, try with smaller maxmem

  The Host OS syslog, as seen HERE, also contains quite some errors.
  To just list a few:

  May 13 20:27:44 191-136 kernel: [36827.151228] alloc_contig_range: 
[3fb800, 3fd8f8) PFNs busy
  May 13 20:27:44 191-136 kernel: [36827.151291] alloc_contig_range: 
[3fb800, 3fd8fc) PFNs busy
  May 13 20:27:44 191-136 libvirtd[19263]: *** Error in 
`/usr/sbin/libvirtd': realloc(): invalid next size: 0x01000a780400 ***
  May 13 20:27:44 191-136 libvirtd[19263]: === Backtrace: =
  May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(+0x8720c)[0x3fffaf6a720c]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(+0x96f70)[0x3fffaf6b6f70]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(realloc+0x16c)[0x3fffaf6b87fc]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virReallocN+0x68)[0x3fffaf90ccc8]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0x8ef6c)[0x3fff9346ef6c]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so(+0xa826c)[0x3fff9348826c]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventPollRunOnce+0x8b4)[0x3fffaf9332b4]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virEventRunDefaultImpl+0x54)[0x3fffaf931334]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/lib/powerpc64le-linux-gnu/libvirt.so.0(virNetDaemonRun+0x1f0)[0x3fffafad2f70]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/usr/sbin/libvirtd(+0x15d74)[0x52e45d74]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(+0x2319c)[0x3fffaf64319c]
  May 13 20:27:44 191-136 libvirtd[19263]: 
/lib/powerpc64le-linux-gnu/libc.so.6(__libc_start_main+0xb8)[0x3fffaf6433b8]
  May 13 20:27:44 191-136 libvirtd[19263]: === Memory map: 
  May 13 20:27:44 191-136 libvirtd[19263]: 52e3-52eb r-xp  
08:02 65540510 /usr/sbin/libvirtd
  May 13 20:27:44 191-136 libvirtd[19263]: 52ec-52ed r--p 0008 
08:02 65540510 /usr/sbin/libvirtd
  May 13 20:27:44 191-136 libvirtd[19263]: 52ed-52ee rw-p 0009 
08:02 65540510 /usr/sbin/libvirtd
  May

[Kernel-packages] [Bug 1628586] Re: using version 4.4.0-38-generic, x86_64 on MacMini

[kalyp]

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

I don't think this is a duplicate bug, or rather, I am not affected by
this one and am by #1626749. On my side, replacing $USER by my username
works. I have 2 identical lines in autofs, one with
credentials=/home/$USER/.credentials (fails as it looks for
/home/root/.credentials), one with
credentials=/home/myusername/.credentials (works just fine for me).

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

Title:
  using version 4.4.0-38-generic, x86_64 on MacMini

Status in linux package in Ubuntu:
  New

Bug description:
  Confirmation of bug #1626749 regarding $USER token substitution
  problem in autofs. Even when the $USER token was replaced with a valid
  username for the share, autofs was unable to mount shares using
  certificates, nor could sshfs. These programs reverted to password
  authentication instead. The reason for mounting with certificates
  instead of passwords is security, of course.

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

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

[Kernel-packages] [Bug 1633492] Re: Ubuntu 16.04 LTS Wifi, Eth connection not detected when booting on 4.4.0-43

[Joseph Salisbury]

** Tags added: performing-bisect xenial

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

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

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

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

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

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

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

Title:
  Ubuntu 16.04 LTS  Wifi, Eth connection not detected when booting on
  4.4.0-43

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

Bug description:
  I'm running Ubuntu 16.04 LTS on a DELL Vostro 15 3300. On upgrading to 
4.4.0-43 and rebooting the system didn't seem to recognize Eth cable or Wifi, 
nor my mouse (connected to USB): 
  There was no Wifi ability to detect any network, neither the eth cable. After 
trying to load drivers via USB, I also notice that any USB port couldn't 
recognize usb sticks
  Rebooting into 4.4.0-42 solved the issue. I can't send ubuntu-bug linux 
because I can't connect on the current 4.4.0-43.

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

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

[Kernel-packages] [Bug 1633391] Re: Ubuntu doesn't boot anymore {REGRESSION}

[Joseph Salisbury]

I'd like to perform a bisect to identify the commit that introduced this
regression.  Can you test the following kernels and see which ones
exhibit the bug:

4.4.19: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.19/
4.4.20: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.20/
4.4.21: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.21

You don't have to test all of them, just up until the first one shows
the bug.

Also, does this issue only happen with the -42 kernel?  Do you know if
it happens with the -39 kernel?  Do you know the last kernel version
that did not have the bug?

Thanks in advance!

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

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

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

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

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

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

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

** Tags added: kernel-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/1633391

Title:
  Ubuntu doesn't boot anymore {REGRESSION}

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

Bug description:
  After I upgraded to latest kernel, Ubuntu does not boot without messing with 
grub (I had to delete quiet splash options). 
  Before upgrade it was OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-42-generic 4.4.0-42.62
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tomas  2090 F pulseaudio
   /dev/snd/controlC1:  tomas  2090 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Oct 14 11:32:56 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ff267c2-ec30-4f81-975c-46640f436942
  InstallationDate: Installed on 2016-09-13 (30 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 10104
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-42-generic 
root=UUID=fd50bb86-da1a-45bb-957b-ea19b330d7ff ro rootflags=subvol=@ 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.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/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ELKT31AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193 STD
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrELKT31AUS:bd03/21/2013:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvr3193STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.name: 10104
  dmi.product.version: Lenovo C440
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1605731] Re: Kernel 4.4.0-31 Causes kernel panic at startup

[Joseph Salisbury]

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

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

Title:
  Kernel 4.4.0-31 Causes kernel panic at startup

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

Bug description:
  Latest kernel update 4.4.0-31 causes kernel panic at startup. Had to reboot 
with 4.4.0-28 which works fine. I have no idea if it's on all filesystems but 
I'm using btrfs.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robi   3230 F pulseaudio
   /dev/snd/pcmC1D0p:   robi   3230 F...m pulseaudio
   /dev/snd/controlC1:  robi   3230 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d64a307b-b7ea-4308-b997-0587321ff7ea
  InstallationDate: Installed on 2016-07-01 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. X750LN
  NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-28-generic 
root=UUID=e075f560-d606-43a0-9cc3-5596a9416d30 ro rootflags=subvol=@ quiet 
splash
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 201
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X750LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  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.:bvr201:bd02/19/2014:svnASUSTeKCOMPUTERINC.:pnX750LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX750LN:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: X750LN
  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/1605731/+subscriptions

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

[Kernel-packages] [Bug 1633223] Re: rcu_sched detected stalls with kernel 3.19.0-58, NVIDIA driver, and docker

[Felix]

On 16.04, the version of aufs looks correct, maybe it's a different bug. Did 
you also try with Docker 1.12 on 16.04?
Looking at the other bug, there is a Docker container than can help diagnose if 
you are encountering the aufs issue:
docker run -it --rm akihirosuda/test18180

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

Title:
  rcu_sched detected stalls with kernel 3.19.0-58, NVIDIA driver, and
  docker

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Seeing occasional rcu_sched detected stalls on 14.04 LTS with kernel 
3.19.0-58. The system is running docker containers, and has the NVIDIA GPU 
driver loaded. We've seen about 4 stalls in the last month, all with the 
3.19.0-58 kernel, and with the NVIDIA 352.93 and 361.49 drivers.

  ---uname output---
  Linux dldev1 3.19.0-58-generic #64~14.04.1-Ubuntu SMP Fri Mar 18 19:05:01 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  2 x NVIDIA K80 GPU adapter:
  $ lspci | grep NV
  0002:03:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1)
  0002:04:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1)
  0006:03:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1)
  0006:04:00.0 3D controller: NVIDIA Corporation GK210GL [Tesla K80] (rev a1) 

   
  Machine Type = 8247-42L 
   
  ---System Hang---
   Usual symptom is that the system is unresponsive except maybe for ping and 
writing the stall-detection messages to the console. Login/getty isn't 
available either via ssh nor on the console. System must be power cycled to 
recover.
   
  Attached is the kernel log from a stall detection on May 18th. The detection 
first occurs at: May 18 15:17:55.

  The system is later rebooted and those messages indicate the kernel
  (3.19.0-58) and NVIDIA driver version (352.93) that were active at the
  time.

  We've suffered 3 or 4 stalls since, all with the same kernel, but some
  with a newer NVIDIA driver (361.49).

  Unfortunately, information about the newer stalls wasn't preserved in
  the various log files (and we're not capturing the console
  constantly), so we don't have detailed data for those.

  We'd welcome any suggestions for how to collect additional data for
  these occurrences.

  I can't say for sure that we haven't seen the stalls on other systems,
  but they're occuring fairly frequently on this system, and it's
  unusual in that it's running both Docker and NVIDIA GPU driver. So
  maybe aufs or the NVIDIA driver are somehow involved.

  From the kern.log,

  The Call trace points to some kind of deadlock in aufs -

  May 18 15:17:55 dldev1 kernel: [713670.798624] Task dump for CPU 3:
  May 18 15:17:55 dldev1 kernel: [713670.798628] cc1 R  running 
task0 99183  99173 0x00040004
  May 18 15:17:55 dldev1 kernel: [713670.798633] Call Trace:
  May 18 15:17:55 dldev1 kernel: [713670.798643] [c00fa64673a0] 
[c00cf004] wake_up_worker+0x44/0x60 (unreliable)
  May 18 15:17:55 dldev1 kernel: [713670.798671] [c00fa6467570] 
[c00fa64675d0] 0xc00fa64675d0
  May 18 15:17:55 dldev1 kernel: [713670.798676] [c00fa64675d0] 
[c0a1b050] __schedule+0x370/0x900
  May 18 15:17:55 dldev1 kernel: [713670.798679] [c00fa64677f0] 
[c00fa6467850] 0xc00fa6467850
  May 18 15:17:55 dldev1 kernel: [713670.798682] Task dump for CPU 75:
  May 18 15:17:55 dldev1 kernel: [713670.798684] cc1 D 
105d9410 0 99427  99405 0x00040004
  May 18 15:17:55 dldev1 kernel: [713670.798688] Call Trace:
  May 18 15:17:55 dldev1 kernel: [713670.798691] [c017efdd3460] 
[c017efdd34a0] 0xc017efdd34a0 (unreliable)
  May 18 15:17:55 dldev1 kernel: [713670.798695] [c017efdd3630] 
[c017efdd3690] 0xc017efdd3690
  May 18 15:17:55 dldev1 kernel: [713670.798698] [c017efdd3690] 
[c0a1b050] __schedule+0x370/0x900
  May 18 15:17:55 dldev1 kernel: [713670.798702] [c017efdd38b0] 
[c0a1f128] rwsem_down_write_failed+0x288/0x400
  May 18 15:17:55 dldev1 kernel: [713670.798706] [c017efdd3940] 
[c0a1e538] down_write+0x88/0x90
  May 18 15:17:55 dldev1 kernel: [713670.798716] [c017efdd3970] 
[d0001ead562c] do_ii_write_lock+0x8c/0xd0 [aufs]
  May 18 15:17:55 dldev1 kernel: [713670.798724] [c017efdd39a0] 
[d0001eac0e98] aufs_read_lock+0xb8/0xd0 [aufs]
  May 18 15:17:55 dldev1 kernel: [713670.798733] [c017efdd39e0] 
[d0001ead8208] aufs_d_revalidate+0x98/0x7a0 [aufs]
  May 18 15:17:55 dldev1 kernel: [713670.798737] [c017efdd3aa0] 
[c02c88f8] lookup_fast+0x368/0x3b0
  May 18 15:17:55 dldev1 kernel: [713670.798740] [c017efdd3b10] 
[c02cb620] path_lookupat+0x180/0x970
  May 18 15:17:55 dldev1 kernel: [713670.798743] [c017efdd3be0] 
[c02cbe68] filename_lookup+0x58/0x140
  May 18 15:17:55 d

[Kernel-packages] [Bug 1630063] Re: specific USB devices disconnect and don't reconnect

[Joseph Salisbury]

@Bryan, do you plan of sending a patch upstream?

To submit your patch, send your patch with the detailed
description/changelog and your Signoff (ending with Signed-off-by: your
name ), to the emails listed from ./scripts/get_maintainer.pl
drivers/SUBSYSTEM-DETAILS (the get_maintainer.pl is from the kernel
sources). Once you have sent the patch upstream and it's accepted,
please drop a note here so that we can cherry-pick/include the patch
into Ubuntu 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/1630063

Title:
  specific USB devices disconnect and don't reconnect

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

Bug description:
  2 USB ports randomly disconnect and don't reconnect (it's always the
  same two), and in dmesg all I get is

  "
  [ 1276.916458] ohci-pci :00:12.0: HcDoneHead not written back; disabled
  [ 1276.916467] ohci-pci :00:12.0: HC died; cleaning up
  [ 1276.916553] usb 3-1: USB disconnect, device number 2
  [ 1277.017302] usb 3-2: USB disconnect, device number 3
  "
  This only started happening when Yakkety went to the 4.8 branch, with 4.7 
branch this doesn't occur, hence the bug report since it's unlikely that a 
hardware failure will only stick to one OS and one branch of the kernel for 
that OS. (these USB ports don't randomly die on Windows or BSD, I've tested 
that in the past couple of days)

  
  kernel version: 4.8.0.17.27
  Ubuntu version
  Description:  Ubuntu Yakkety Yak (development branch)
  Release:  16.10
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  c_smith2213 F pulseaudio
   /dev/snd/controlC0:  c_smith2213 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=1a29baaa-55ea-4817-ba45-8c618f65ec4b
  InstallationDate: Installed on 2016-10-03 (0 days ago)
  InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20161002)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-S2
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-17-generic 
root=/dev/mapper/Linux-root ro nomodeset quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-17-generic N/A
   linux-backports-modules-4.8.0-17-generic  N/A
   linux-firmware1.161
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  yakkety
  Uname: Linux 4.8.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/09/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: GA-78LMT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1311987] Re: deploy-ironic ramdisks do not boot: Failed to execute /init (error -28)

[Gregory Haynes]

** Changed in: diskimage-builder
   Status: Triaged => 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/1311987

Title:
  deploy-ironic ramdisks do not boot:  Failed to execute /init (error
  -28)

Status in devstack:
  Fix Released
Status in diskimage-builder:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  The default ubuntu release for ramdisks was bumped to Trusty
  https://review.openstack.org/#/c/88384/  Ironic + devstack deployments
  stopped functioning.  The ramdisk fails to run init, crashing with the
  following error:

  [   23.154016] Failed to execute /init (error -28)
  [   23.154909] Starting init: /sbin/init exists but couldn't execute it 
(error -28)
  [   23.156388] Starting init: /bin/init exists but couldn't execute it (error 
-28)
  [   23.157490] Starting init: /bin/sh exists but couldn't execute it (error 
-28)
  [   23.160313] Kernel panic - not syncing: No working init found.  Try 
passing init= option to kernel. See Linux Documentation/init.txt for guidance.
  [   23.164146] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.13.0-24-generic 
#46-Ubuntu
  [   23.164146] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
  [   23.164146]   88001a3a9ec0 81715a64 
81a39f38
  [   23.164146]  88001a3a9f38 8170ec65 0008 
88001a3a9f48
  [   23.164146]  88001a3a9ee8 81a39a38 13981396 
1396
  [   23.164146] Call Trace:
  [   23.164146]  [] dump_stack+0x45/0x56
  [   23.164146]  [] panic+0xc8/0x1d7
  [   23.164146]  [] ? rest_init+0x80/0x80
  [   23.164146]  [] kernel_init+0x122/0x130
  [   23.164146]  [] ret_from_fork+0x7c/0xb0
  [   23.164146]  [] ? rest_init+0x80/0x80
  [   23.164146] general protection fault: fff2 [#1] SMP
  [   23.164146] Modules linked in:
  [   23.164146] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.13.0-24-generic 
#46-Ubuntu
  [   23.164146] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2011
  [   23.164146] task: 88001a3a ti: 88001a3a8000 task.ti: 
88001a3a8000
  [   23.164146] RIP: 0010:[]  [] 
panic+0x193/0x1d7
  [   23.164146] RSP: :88001a3a9ed0  EFLAGS: 0246
  [   23.164146] RAX: 14a814a8 RBX: 81a39f38 RCX: 
0854
  [   23.164146] RDX: 14a8 RSI:  RDI: 
0046

  #define ENOSPC  28  /* No space left on device */

  Setting DIB_RELEASE=saucy fixes the issue.A saucy ramdisk is 83M
  compressed, 238M decompressed.  trusty ramdisk is 87M compressed, 245M
  decompressed.

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

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

[Kernel-packages] [Bug 1633267] Re: Wifi, sound not detected when booting on 4.4.0-43

[Alberto Salvia Novella]

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

** Also affects: hundredpapercuts
   Importance: Undecided
   Status: New

** Changed in: hundredpapercuts
   Status: New => Confirmed

** Changed in: hundredpapercuts
   Importance: Undecided => High

** Summary changed:

- Wifi, sound not detected when booting on 4.4.0-43
+ Wifi and sound no longer detected in kernel 4.4.0-43

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

Title:
  Wifi and sound no longer detected in kernel 4.4.0-43

Status in One Hundred Papercuts:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Gnome 16.04 on a Thinkpad T440p. On upgrading to 4.4.0-43 
and rebooting the system didn't seem to recognize my Wifi or sound hardware: 
there was no Wifi icon or ability to connect to a network, and the only output 
on the sound menu was "Dummy Output." Rebooting into 4.4.0-42 solved the issue.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matt   3400 F pulseaudio
   /dev/snd/controlC1:  matt   3400 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=29856bc8-3313-4425-95eb-a0afbc112423
  InstallationDate: Installed on 2015-08-23 (417 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  MachineType: LENOVO 20ANCTO1WW
  Package: linux (not installed)
  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.4.0-42-generic.efi.signed 
root=UUID=18bf0a8f-3ce6-4c05-aff3-96f8da1e9ce5 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.4
  Tags:  xenial
  Uname: Linux 4.4.0-42-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-07-24 (81 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET84WW (2.38 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ANCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98405 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET84WW(2.38):bd08/18/2016:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvr0B98405STD:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ANCTO1WW
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1633391] Re: Ubuntu doesn't boot anymore {REGRESSION}

[Alberto Salvia Novella]

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

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

Title:
  Ubuntu doesn't boot anymore {REGRESSION}

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After I upgraded to latest kernel, Ubuntu does not boot without messing with 
grub (I had to delete quiet splash options). 
  Before upgrade it was OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-42-generic 4.4.0-42.62
  ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
  Uname: Linux 4.4.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tomas  2090 F pulseaudio
   /dev/snd/controlC1:  tomas  2090 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Oct 14 11:32:56 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=2ff267c2-ec30-4f81-975c-46640f436942
  InstallationDate: Installed on 2016-09-13 (30 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 10104
  ProcEnviron:
   LANGUAGE=cs_CZ
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-42-generic 
root=UUID=fd50bb86-da1a-45bb-957b-ea19b330d7ff ro rootflags=subvol=@ 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-42-generic N/A
   linux-backports-modules-4.4.0-42-generic  N/A
   linux-firmware1.157.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/21/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ELKT31AUS
  dmi.board.name: MAHOBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193 STD
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrELKT31AUS:bd03/21/2013:svnLENOVO:pn10104:pvrLenovoC440:rvnLENOVO:rnMAHOBAY:rvr3193STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.name: 10104
  dmi.product.version: Lenovo C440
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1632369] Re: linux-lts-vivid: 3.19.0-72.80~14.04.1 -proposed tracker

[Brad Figg]

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

** Description changed:

  This bug is for tracking the 3.19.0-72.80~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1632368
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Friday, 14. October 2016 15:03 UTC

** Description changed:

  This bug is for tracking the 3.19.0-72.80~14.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1632368
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Friday, 14. October 2016 15:03 UTC
+ phase: Uploaded

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

Title:
  linux-lts-vivid: 3.19.0-72.80~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  derivative-trackers-created: true
  kernel-stable-master-bug: 1632368
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1626517] Re: Access to some folders hangs and in dmesg see kernel BUG report

[Vadim Shalts]

Nope, was wrong. It is broken in upstream too. My system:

Linux vshalts_da.vshalts.com 4.8.0-040800-generic #201610022031 SMP Mon
Oct 3 00:32:57 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Fresh dmesg error:

[276405.098149] [ cut here ]
[276405.098172] kernel BUG at /home/kernel/COD/linux/fs/namei.c:2777!
[276405.098188] invalid opcode:  [#1] SMP
[276405.098199] Modules linked in: cpuid ppp_async ppp_generic slhc fuse 
ipt_REJECT nf_reject_ipv4 nf_log_ipv4 xt_recent nf_conntrack_ipv6 
nf_defrag_ipv6 xt_conntrack ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 
nf_log_common xt_LOG xt_limit xt_hashlimit ip6table_filter ip6_tables 
xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp 
pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bridge stp llc 
iptable_filter ip_tables x_tables binfmt_misc dm_crypt dm_mod ecb intel_rapl 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_realtek 
snd_hda_codec_generic uvcvideo snd_hda_intel videobuf2_vmalloc videobuf2_memops 
videobuf2_v4l2 snd_hda_codec videobuf2_core snd_usb_audio snd_hda_core videodev
[276405.098426]  snd_usbmidi_lib media snd_hwdep snd_pcm snd_seq_midi 
snd_seq_midi_event snd_rawmidi joydev eeepc_wmi kvm_intel asus_wmi 
sparse_keymap rfkill kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel snd_seq snd_seq_device snd_timer aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd intel_cstate intel_rapl_perf snd 
serio_raw mei_me sg lpc_ich mei shpchp soundcore battery evdev tpm_infineon 
ecryptfs parport_pc ppdev lp parport autofs4 ext4 crc16 jbd2 fscrypto mbcache 
hid_generic usbhid hid btrfs xor raid6_pq i915 i2c_algo_bit drm_kms_helper 
syscopyarea crc32c_intel sysfillrect psmouse sysimgblt fb_sys_fops drm ahci 
r8169 libahci mii wmi thermal fan button fjes video
[276405.098660] CPU: 0 PID: 24246 Comm: rm Tainted: GW  OE   
4.8.0-040800-generic #201610022031
[276405.098684] Hardware name: ASUS All Series/H81M-K, BIOS 1002 08/12/2014
[276405.098701] task: 94ab72632a80 task.stack: 94a9fd41c000
[276405.098717] RIP: 0010:[]  [] 
may_delete+0x154/0x170
[276405.098742] RSP: 0018:94a9fd41fdf0  EFLAGS: 00010216
[276405.098757] RAX: 94ab9015dc00 RBX: 94aa28be2000 RCX: 
000e
[276405.098775] RDX:  RSI: 94aa28be2000 RDI: 
94aa06ec3bf8
[276405.098793] RBP: 94ab6a7e8520 R08: 94ab91a4a800 R09: 
94aadbc6308b
[276405.098811] R10: 94aabf9206f8 R11: 18c23f265c15f699 R12: 
94aa06ec3bf8
[276405.098830] R13: 94a9e0e7a6e0 R14: 94a9afe5e800 R15: 

[276405.098848] FS:  7fa4589ce700() GS:94ab9fa0() 
knlGS:
[276405.098868] CS:  0010 DS:  ES:  CR0: 80050033
[276405.098883] CR2: 00f721c8 CR3: 000207fc6000 CR4: 
001406f0
[276405.098900] Stack:
[276405.098908]  94aa28be2000 94a9fd41fe90 94aa06ec3bf8 
94a9e0e7a6e0
[276405.098932]  94a9afe5e800 92c21de3 94aa28be2000 
94a9fd41fe90
[276405.098955]  94ab9015dc00 94a9acc05c00 94a9afe5e800 
94aa06ec3bf8
[276405.098978] Call Trace:
[276405.098989]  [] ? vfs_unlink+0x23/0x180
[276405.099009]  [] ? ecryptfs_do_unlink+0x65/0x120 [ecryptfs]
[276405.099028]  [] ? vfs_unlink+0xe8/0x180
[276405.099043]  [] ? do_unlinkat+0x2ae/0x330
[276405.099062]  [] ? entry_SYSCALL_64_fastpath+0x1e/0xa8
[276405.099080] Code: 60 00 3d 00 00 20 00 74 12 41 bc ec ff ff ff 5b 44 89 e0 
5d 41 5c 41 5d 41 5e c3 48 3b 5b 18 75 96 41 bc f0 ff ff ff eb a2 0f 0b <0f> 0b 
41 bc fe ff ff ff eb 96 41 bc eb ff ff ff eb 8e 66 2e 0f
[276405.099192] RIP  [] may_delete+0x154/0x170
[276405.099209]  RSP 
[276405.105223] ---[ end trace c5fcde2a70cfe731 ]---


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

Title:
  Access to some folders hangs and in dmesg see kernel BUG report

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Probably freeze during access to folder caused by 
  kernel BUG at /build/linux-BvkamA/linux-4.4.0/fs/namei.c:2562!

  Also segfault during collecting information with 'ubuntu-bug linux', but not 
sure it is related:
  [80059.937844] apport-kde[22602]: segfault at 7fdb0f1d4b00 ip 
7fdb44cd40f5 sp 7ffd35400828 error 4 in 
QtCore.cpython-35m-x86_64-linux-gnu.so[7fdb44ae4000+268000]
  [80099.437691] Qt bearer threa[23986]: segfault at 7f23b89942e9 ip 
7f23b3d41ccb sp 7f239fffce50 error 4 in 
libgcc_s.so.1[7f23b3d33000+16000]
  It is looks like separate issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.

[Kernel-packages] [Bug 1626517] Re: Access to some folders hangs and in dmesg see kernel BUG report

[Vadim Shalts]

** Tags removed: 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/1626517

Title:
  Access to some folders hangs and in dmesg see kernel BUG report

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Probably freeze during access to folder caused by 
  kernel BUG at /build/linux-BvkamA/linux-4.4.0/fs/namei.c:2562!

  Also segfault during collecting information with 'ubuntu-bug linux', but not 
sure it is related:
  [80059.937844] apport-kde[22602]: segfault at 7fdb0f1d4b00 ip 
7fdb44cd40f5 sp 7ffd35400828 error 4 in 
QtCore.cpython-35m-x86_64-linux-gnu.so[7fdb44ae4000+268000]
  [80099.437691] Qt bearer threa[23986]: segfault at 7f23b89942e9 ip 
7f23b3d41ccb sp 7f239fffce50 error 4 in 
libgcc_s.so.1[7f23b3d33000+16000]
  It is looks like separate issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vadim  4045 F pulseaudio
   /dev/snd/controlC0:  vadim  4045 F pulseaudio
  Date: Thu Sep 22 13:52:19 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=4ff5857a-eca8-4968-9e7d-16cb2b146f60
  InstallationDate: Installed on 2015-04-28 (512 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: ASUS All Series
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=f0d3e2ee-9f79-431c-9d8a-1079d7638279 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.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (152 days ago)
  dmi.bios.date: 08/12/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1002
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1002:bd08/12/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  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/1626517/+subscriptions

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

[Kernel-packages] [Bug 1403152] Re: unregister_netdevice: waiting for lo to become free. Usage count

[Dan Streetman]

> Well, if that made it into Ubuntu's kernel before and including 4.4.0-42, it 
> didn't fix it 
> (I still get the bug on many machines & VMs).

No, it's not in the released xenial kernel yet, the upstream 4.4.22
stable commits are still in the xenial master-next branch kernel; it'll
be a bit longer before xenial's normal kernel is updated with the patch.

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

Title:
  unregister_netdevice: waiting for lo to become free. Usage count

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Confirmed
Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-xenial source package in Trusty:
  Confirmed
Status in linux source package in Vivid:
  Fix Released

Bug description:
  SRU Justification:

  [Impact]

  Users of kernels that utilize NFS may see the following messages when
  shutting down and starting containers:

  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]

  Setup multiple containers in parallel to mount and NFS share, create
  some traffic and shutdown. Eventually you will see the kernel message.

  Dave's script here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1403152/comments/24

  [Fix]
  commit de84d89030fa4efa44c02c96c8b4a8176042c4ff upstream

  --

  I currently running trusty latest patches and i get on these hardware
  and software:

  Ubuntu 3.13.0-43.72-generic 3.13.11.11

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

  somehow reproducable the subjected error, and lxc is working still but
  not more managable until a reboot.

  managable means every command hangs.

  I saw there are alot of bugs but they seams to relate to older version
  and are closed, so i decided to file a new one?

  I run alot of machine with trusty an lxc containers but only these kind of 
machines produces these errors, all
  other don't show these odd behavior.

  thx in advance

  meno

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

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

[Kernel-packages] [Bug 1633506] Re: backport fwts UEFI test driver to Xenial

[Colin Ian King]

** Summary changed:

- backport fwts UEFI test driver top Xenial
+ backport fwts UEFI test driver to Xenial

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

Title:
  backport fwts UEFI test driver to Xenial

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [SRU Justification, XENIAL]

  The fwts UEFI test driver is now upstream in Linux 4.9 and also in the
  Ubuntu Yakkety 4.8 kernel, so it would be useful for fwts support to
  add it into the Xenial kernel as default (for example Xenial bases
  fwts snaps as we can dispense with the DKMS module support).

  [Fix]
  Upstream commit ff6301dabc3ca20ab8f50f8d0252ac05da610d8 "efi: Add efi_test 
driver for exporting UEFI runtime service interfaces"

  This patch requires a minor patch wiggle on the Makefile and Kconfig
  to backport to Xenial.

  [Test]
  Build fwts from the source and run on a Xenial kernel w/o the fwts dpkg based 
efi driver and run "sudo fwts --uefitests -" and the tests will fail.  Install 
the fixed kernel with the driver and the tests will now run because the module 
is loaded by fwts and we can now exercise the UEFI run time interfaces from 
fwts as root.

  [Regression Potential]
  This adds test functionality and will not impact on any other driver or 
subsystem. To access these test interfaces one requires root privileges, so 
risk of normal unprivileged uses accessing UEFI run time services are zero.

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

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

[Kernel-packages] [Bug 1633506] [NEW] backport fwts UEFI test driver to Xenial

[Colin Ian King]

Public bug reported:

[SRU Justification, XENIAL]

The fwts UEFI test driver is now upstream in Linux 4.9 and also in the
Ubuntu Yakkety 4.8 kernel, so it would be useful for fwts support to add
it into the Xenial kernel as default (for example Xenial bases fwts
snaps as we can dispense with the DKMS module support).

[Fix]
Upstream commit ff6301dabc3ca20ab8f50f8d0252ac05da610d8 "efi: Add efi_test 
driver for exporting UEFI runtime service interfaces"

This patch requires a minor patch wiggle on the Makefile and Kconfig to
backport to Xenial.

[Test]
Build fwts from the source and run on a Xenial kernel w/o the fwts dpkg based 
efi driver and run "sudo fwts --uefitests -" and the tests will fail.  Install 
the fixed kernel with the driver and the tests will now run because the module 
is loaded by fwts and we can now exercise the UEFI run time interfaces from 
fwts as root.

[Regression Potential]
This adds test functionality and will not impact on any other driver or 
subsystem. To access these test interfaces one requires root privileges, so 
risk of normal unprivileged uses accessing UEFI run time services are zero.

** Affects: linux (Ubuntu)
 Importance: Low
 Assignee: Colin Ian King (colin-king)
 Status: In Progress

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  backport fwts UEFI test driver to Xenial

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [SRU Justification, XENIAL]

  The fwts UEFI test driver is now upstream in Linux 4.9 and also in the
  Ubuntu Yakkety 4.8 kernel, so it would be useful for fwts support to
  add it into the Xenial kernel as default (for example Xenial bases
  fwts snaps as we can dispense with the DKMS module support).

  [Fix]
  Upstream commit ff6301dabc3ca20ab8f50f8d0252ac05da610d8 "efi: Add efi_test 
driver for exporting UEFI runtime service interfaces"

  This patch requires a minor patch wiggle on the Makefile and Kconfig
  to backport to Xenial.

  [Test]
  Build fwts from the source and run on a Xenial kernel w/o the fwts dpkg based 
efi driver and run "sudo fwts --uefitests -" and the tests will fail.  Install 
the fixed kernel with the driver and the tests will now run because the module 
is loaded by fwts and we can now exercise the UEFI run time interfaces from 
fwts as root.

  [Regression Potential]
  This adds test functionality and will not impact on any other driver or 
subsystem. To access these test interfaces one requires root privileges, so 
risk of normal unprivileged uses accessing UEFI run time services are zero.

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

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

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

[Brad Figg]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1633492

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

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

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

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

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

Title:
  Ubuntu 16.04 LTS  Wifi, Eth connection not detected when booting on
  4.4.0-43

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm running Ubuntu 16.04 LTS on a DELL Vostro 15 3300. On upgrading to 
4.4.0-43 and rebooting the system didn't seem to recognize Eth cable or Wifi, 
nor my mouse (connected to USB): 
  There was no Wifi ability to detect any network, neither the eth cable. After 
trying to load drivers via USB, I also notice that any USB port couldn't 
recognize usb sticks
  Rebooting into 4.4.0-42 solved the issue. I can't send ubuntu-bug linux 
because I can't connect on the current 4.4.0-43.

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

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

[Kernel-packages] [Bug 1598935] Re: Ubuntu 16.04 won't properly boot due to radeon module issue

[Tomdkat]

I have great news!  The system is now booting properly! No more 20
minute wait to login!  I noticed it with the update to the 4.4.0-42
kernel.  So, this issue might have been fixed with either that kernel
update or the previous, 4.4.0-38 kernel update.

In any event, this is no longer an issue and this bug report can be
closed out.  I'll close it, if I can.  :)

Thanks!

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

Title:
  Ubuntu 16.04 won't properly boot due to radeon module issue

Status in linux package in Ubuntu:
  Expired

Bug description:
  When I boot an Ubuntu 16.04 live DVD on a Gateway system with an AMD A6-5400K 
APU, with an integrated Radeon HD 7540D graphics adapter, I get a black screen 
with no video image. If I look at "dmesg" output, I see these messages:
  ubuntu@ubuntu:~$ dmesg | grep "UMS"
  [4.827258] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon 
module!
  [   39.561534] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon 
module!
  [   76.905778] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon 
module!

  We currently run Ubuntu 14.04.2 on the system with no issue, including
  using the "radeon" video driver.

  WORKAROUND: Boot using kernel parameter:
  nomodeset

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  ubuntu 2057 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2057 F pulseaudio
   /dev/snd/controlC1:  ubuntu 2057 F pulseaudio
  CasperVersion: 1.376
  Date: Mon Jul  4 20:08:04 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  MachineType: Gateway DX4380G
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet splash nomodeset ---
  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.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-A1
  dmi.board.name: DX4380G
  dmi.board.vendor: Gateway
  dmi.board.version: 1.02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-A1:bd09/04/2012:svnGateway:pnDX4380G:pvr:rvnGateway:rnDX4380G:rvr1.02:cvnGateway:ct3:cvr:
  dmi.product.name: DX4380G
  dmi.sys.vendor: Gateway

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

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

[Kernel-packages] [Bug 1611078] Re: Support snaps inside of lxd containers

[Stefan Bader]

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  New

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

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

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

[Kernel-packages] [Bug 1611078] Re: Support snaps inside of lxd containers

[Andy Whitcroft]

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => John Johansen (jjohansen)

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  New

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

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

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

[Kernel-packages] [Bug 1633492] [NEW] Ubuntu 16.04 LTS Wifi, Eth connection not detected when booting on 4.4.0-43

[maria]

Public bug reported:

I'm running Ubuntu 16.04 LTS on a DELL Vostro 15 3300. On upgrading to 4.4.0-43 
and rebooting the system didn't seem to recognize Eth cable or Wifi, nor my 
mouse (connected to USB): 
There was no Wifi ability to detect any network, neither the eth cable. After 
trying to load drivers via USB, I also notice that any USB port couldn't 
recognize usb sticks
Rebooting into 4.4.0-42 solved the issue. I can't send ubuntu-bug linux because 
I can't connect on the current 4.4.0-43.

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

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

Title:
  Ubuntu 16.04 LTS  Wifi, Eth connection not detected when booting on
  4.4.0-43

Status in linux package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 16.04 LTS on a DELL Vostro 15 3300. On upgrading to 
4.4.0-43 and rebooting the system didn't seem to recognize Eth cable or Wifi, 
nor my mouse (connected to USB): 
  There was no Wifi ability to detect any network, neither the eth cable. After 
trying to load drivers via USB, I also notice that any USB port couldn't 
recognize usb sticks
  Rebooting into 4.4.0-42 solved the issue. I can't send ubuntu-bug linux 
because I can't connect on the current 4.4.0-43.

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

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

[Kernel-packages] [Bug 1611078] Re: Support snaps inside of lxd containers

[Andy Whitcroft]

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

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

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

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

Title:
  Support snaps inside of lxd containers

Status in Snappy:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in lxd source package in Xenial:
  New

Bug description:
  I tried following the instructions on snapcraft.io and got a failure.
  See the output below.  I've also attached the relevant output from
  running "journalctl -xe".

  uname: Linux 3.19.0-65-generic x86_64
  release: Ubuntu 16.04
  package: snapd 2.11+0.16.04

  Notably, I'm running this in an LXD container (version: 2.0.0.rc9).

  -

  $ sudo snap install hello-world
  64.75 MB / 64.75 MB 
[==]
 100.00 % 2.85 MB/s 

  error: cannot perform the following tasks:
  - Mount snap "ubuntu-core" (122) ([start snap-ubuntu\x2dcore-122.mount] 
failed with exit status 1: Job for snap-ubuntu\x2dcore-122.mount failed. See 
"systemctl status "snap-ubuntu\\x2dcore-122.mount"" and "journalctl -xe" for 
details.
  )
  $ ls -la /snap
  total 4K
  drwxr-xr-x 3 root root 4096 Aug  8 17:49 ubuntu-core
  $ ls -la /snap/ubuntu-core/
  total 4K
  drwxr-xr-x 2 root root 4096 Aug  8 17:49 122
  $ ls -la /snap/ubuntu-core/122/
  total 0K
  $ systemctl status "snap-ubuntu\\x2dcore-122.mount"
  ● snap-ubuntu\x2dcore-122.mount - Mount unit for ubuntu-core
 Loaded: loaded (/etc/systemd/system/snap-ubuntu\x2dcore-122.mount; 
enabled; vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2016-08-08 17:49:36 UTC; 6min 
ago
  Where: /snap/ubuntu-core/122
   What: /var/lib/snapd/snaps/ubuntu-core_122.snap
Process: 31781 ExecMount=/bin/mount 
/var/lib/snapd/snaps/ubuntu-core_122.snap /snap/ubuntu-core/122 -t squashfs 
(code=exited, status=32)

  Aug 08 17:49:35 my-host systemd[1]: Mounting Mount unit for ubuntu-core...
  Aug 08 17:49:35 my-host mount[31781]: mount: /snap/ubuntu-core/122: mount 
failed: Unknown error -1
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Mount 
process exited, code=exited status=32
  Aug 08 17:49:36 my-host systemd[1]: Failed to mount Mount unit for 
ubuntu-core.
  Aug 08 17:49:36 my-host systemd[1]: snap-ubuntu\x2dcore-122.mount: Unit 
entered failed state.

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

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