date:20160909

tests ran:  10, failed: 2;
  
http://kernel.ubuntu.com/testing/4.4.0-38.57/ms10-34-mcdivittB0-kernel__4.4.0-38.57__2016-09-10_02-18-00/results-index.html

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

Title:
  linux: 4.4.0-38.57 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-38.57 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
  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/1620658/+subscriptions

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

[Kernel-packages] [Bug 1608499] Re: Parallel depmod failure with dkms autoinstall

2016-09-09 Thread Mathew Hodson

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

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

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

Title:
  Parallel depmod failure with dkms autoinstall

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Committed
Status in dkms source package in Xenial:
  Fix Committed

Bug description:
  Description of problem
  --

  "dkms autoinstall" installs DKMS modules in parallel, potentially executing
  several depmod instances in parallel.

  The resulting race condition causes depmod to fail and dkms install as
  well.

  This problem is critical because some DKMS modules can be left in "built"
  state after a kernel upgrade, thus the kernel modules will not be re-installed
  in /lib/modules/.

  Ubuntu release
  --
  # lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  DKMS package version
  

  # apt-cache policy dkms
  dkms:
Installed: 2.2.0.3-2ubuntu11
Candidate: 2.2.0.3-2ubuntu11
Version table:
   *** 2.2.0.3-2ubuntu11 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  Steps to reproduce
  --

  Add 2 simple DKMS modules, mod1 and mod2 (test case in attachment) with
  "dkms add", then run "dkms autoinstall".

  # dkms add mod1 ; dkms add mod2

  Creating symlink /var/lib/dkms/mod1/1.0/source ->
   /usr/src/mod1-1.0

  DKMS: add completed.

  Creating symlink /var/lib/dkms/mod2/1.0/source ->
   /usr/src/mod2-1.0

  DKMS: add completed.

  # dkms autoinstall

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area...
  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area
  .make KERNELRELEASE=4.4.0-28-generic -C /lib/modules/4.4.0-28-generic/build 
SUBDIRS=/var/lib/dkms/mod2/1.0/build S=/var/lib/dkms/mod2/1.0/build modules...
  make KERNELRELEASE=4.4.0-28-generic -C /lib/modules/4.4.0-28-generic/build 
SUBDIRS=/var/lib/dkms/mod1/1.0/build S=/var/lib/dkms/mod1/1.0/build modules.

  cleaning build area...cleaning build area.

  
  DKMS: build completed.

  DKMS: build completed.

  mod2.ko:
  Running module version sanity check.

  mod1.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.4.0-28-generic/updates/dkms/
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.4.0-28-generic/updates/dkms/

  
  depmod...depmod...(bad exit status: 1)

   Uninstall Beginning 
  Module:  mod2
  Version: 1.0
  Kernel:  4.4.0-28-generic (x86_64)
  -

  
  DKMS: install completed.

  Status: Before uninstall, this module version was ACTIVE on this
  kernel.

  mod2.ko:
   - Uninstallation
 - Deleting from: /lib/modules/4.4.0-28-generic/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.

  depmod

  DKMS: uninstall completed.
  Error! Problems with depmod detected.  Automatically uninstalling this module.
  DKMS: Install Failed (depmod problems).  Module rolled back to built state.

  root@ubuntu1604:~/dkms-depmod# dkms status
  mod1, 1.0, 4.4.0-28-generic, x86_64: installed
  mod2, 1.0, 4.4.0-28-generic, x86_64: built

  => mod2 should be in "installed" state as well.

  # modinfo mod1
  filename:   /lib/modules/4.4.0-28-generic/updates/dkms/mod1.ko
  author: 6WIND
  license:GPL
  srcversion: 8D30BAE7A8F4D38F20AEB57
  depends:
  vermagic:   4.4.0-28-generic SMP mod_unload modversions 

  # modinfo mod2
  modinfo: ERROR: Module mod2 not found.

  Solution
  

  The problem is fixed in dkms official repository by commit
  
https://github.com/dell-oss/dkms/commit/00114cbc0a1f8c0aa5143808205d1a7cc9e58d3b
  (also in attachment).

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

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

[Kernel-packages] [Bug 1620658] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 23, failed: 1

tests ran:  23, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-38.57/ms10-34-mcdivittB0-kernel__4.4.0-38.57__2016-09-10_01-46-00/results-index.html

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

Title:
  linux: 4.4.0-38.57 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-38.57 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
  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/1620658/+subscriptions

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

[Kernel-packages] [Bug 1620658] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 83, failed: 0

tests ran:  83, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-38.57/ms10-34-mcdivittB0-kernel__4.4.0-38.57__2016-09-09_23-46-00/results-index.html

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

Title:
  linux: 4.4.0-38.57 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-38.57 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
  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/1620658/+subscriptions

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

[Kernel-packages] [Bug 1621989] Re: chown of SUID executable in docker container on overlayfs fails with kernel BUG at linux-4.4.0/fs/attr.c:280

2016-09-09 Thread Vladimir Rutsky

Tim, thank you for the quick response!

I tried linux-image-4.4.0-38-generic package (version 4.4.0-38.57) from
xenial-proposed and can't reproduce this bug on it, looks like it is
fixed in proposed version.

Thanks for the help, this issue should be resolved when linux-
image-4.4.0-38-generic will reach xenial-updates channel.

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

Title:
  chown of SUID executable in docker container on overlayfs fails with
  kernel BUG at linux-4.4.0/fs/attr.c:280

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1. Take any fresh installation of Ubuntu 16.04. I used Vagrant to
  reproduce this bug, but it also reproduces on my VM with Ubuntu 16.04
  in Azure.

  2. Upgrade kernel to current latest release (linux-
  image-4.4.0-36-generic).

  # uname -r
  4.4.0-36-generic

  3. Install Docker 1.11.2 from Ubuntu repositories (also can be
  reproduced with Docker 1.12.1 from official Docker repositories for
  Debian/Ubuntu):

  # apt install docker.io

  4. Use overlayfs as storage driver in Docker. Edit /etc/default/docker
  and add DOCKER_OPTS="--storage-driver=overlay":

  # echo 'DOCKER_OPTS="--storage-driver=overlay"' >> /etc/default/docker
  # systemctl restart docker
  # docker info
  Containers: 1
   Running: 1
   Paused: 0
   Stopped: 0
  Images: 1
  Server Version: 1.11.2
  Storage Driver: overlay
   Backing Filesystem: extfs
  Logging Driver: json-file
  Cgroup Driver: cgroupfs
  Plugins: 
   Volume: local
   Network: bridge null host
  Kernel Version: 4.4.0-36-generic
  Operating System: Ubuntu 16.04.1 LTS
  OSType: linux
  Architecture: x86_64
  CPUs: 1
  Total Memory: 488.5 MiB
  Name: vagrant
  ID: COJW:JDNB:4KBK:VJJN:PDW4:ECVU:6TCT:BAEY:5Z4T:WYGD:Q5BD:PZHH
  Docker Root Dir: /var/lib/docker
  Debug mode (client): false
  Debug mode (server): false
  Registry: https://index.docker.io/v1/
  WARNING: No swap limit support

  
  5. Start container and run following commands in container:

  # docker run --rm -ti busybox:latest /bin/sh
  Unable to find image 'busybox:latest' locally
  latest: Pulling from library/busybox
  8ddc19f16526: Pull complete 
  Digest: 
sha256:a59906e33509d14c036c8678d687bd4eec81ed7c4b8ce907b888c607f6a1e0e6
  Status: Downloaded newer image for busybox:latest
  / # touch a
  / # chmod 04744 a
  / # stat a
File: a
Size: 0   Blocks: 0  IO Block: 4096   regular empty file
  Device: fc00h/64512dInode: 264640  Links: 1
  Access: (4744/-rwsr--r--)  Uid: (0/root)   Gid: (0/root)
  Access: 2016-09-09 19:18:50.0
  Modify: 2016-09-09 19:18:50.0
  Change: 2016-09-09 19:18:56.0

  / # chown 0:12345 a
  Segmentation fault
  / # 

  During chown fault following appears in dmesg:

  [  753.808988] [ cut here ]
  [  753.809003] kernel BUG at /build/linux-a2WvEb/linux-4.4.0/fs/attr.c:280!
  [  753.809016] invalid opcode:  [#1] SMP 
  [  753.809026] Modules linked in: overlay veth ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_na
  t nf_conntrack br_netfilter bridge stp llc aufs vboxsf ppdev crct10dif_pclmul 
crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd 
input_leds serio_raw vboxvideo 8250_fintek parpo
  rt_pc parport ttm drm_kms_helper mac_hid drm fb_sys_fops i2c_piix4 
syscopyarea vboxguest sysfillrect sysimgblt sunrpc autofs4 psmouse ahci libahci 
e1000 pata_acpi video fjes
  [  753.809172] CPU: 0 PID: 5971 Comm: chown Tainted: GW   
4.4.0-36-generic #55-Ubuntu
  [  753.809188] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS 
VirtualBox 12/01/2006
  [  753.809203] task: 88001f042c40 ti: 880010c74000 task.ti: 
880010c74000
  [  753.809217] RIP: 0010:[]  [] 
notify_change+0x303/0x360
  [  753.809258] RSP: 0018:880010c77db0  EFLAGS: 00010202
  [  753.809270] RAX: 57d30b2d RBX: 1847 RCX: 
0017
  [  753.809297] RDX: 0771653f RSI: 0771653f RDI: 
57d30b2d
  [  753.809312] RBP: 880010c77de0 R08:  R09: 
0001
  [  753.809332] R10:  R11: 880017582a0c R12: 
880010c77e78
  [  753.809352] R13: 8800194f7cc0 R14: 89e4 R15: 
880016a77b88
  [  753.809389] FS:  011991f0(0063) GS:88001fc0() 
knlGS:
  [  753.809420] CS:  0010 DS:  ES:  CR0: 8005003b
  [  753.809431] CR2: 0119abf8 CR3: 17cbe000 CR4: 
000406f0
  [  753.809446] DR0:  DR1:  DR2: 

  [  753.809461] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  753.809491] Stack:
  [  753.809496]

[Kernel-packages] [Bug 1620658] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 2, failed: 0

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-38.57/ms10-34-mcdivittB0-kernel__4.4.0-38.57__2016-09-09_23-04-00/results-index.html

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

Title:
  linux: 4.4.0-38.57 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-38.57 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
  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/1620658/+subscriptions

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

[Kernel-packages] [Bug 1620658] ms10-34-mcdivittB0-kernel (arm64) - tests ran: 65, failed: 0

tests ran:  65, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-38.57/ms10-34-mcdivittB0-kernel__4.4.0-38.57__2016-09-09_22-25-00/results-index.html

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

Title:
  linux: 4.4.0-38.57 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-38.57 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
  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/1620658/+subscriptions

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

[Kernel-packages] [Bug 1615200] Re: Can't read battery state

2016-09-09 Thread mforonda

I've reproduced the error on 4.8-rc4 and 4.8-rc5.

** Attachment added: "dmesg_48rc5"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1615200/+attachment/4737986/+files/dmesg_48rc5

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

Title:
  Can't read battery state

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My HP ENVY m4-1015dx Notebook PC can't read the battery state. This happens 
roughly once every three sessions, with no obvious trigger, thus no way to 
reproduce but to boot and wait, usually a couple of hours. The error displayed 
on dmesg is the following:
  ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC0.MMRD] (Node 
8802468b4f50), AE_AML_INFINITE_LOOP (20150930/psparse-542)
  ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC0.RDMB] (Node 
8802468b5938), AE_AML_INFINITE_LOOP (20150930/psparse-542)
  ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC0.RDMW] (Node 
8802468b5960), AE_AML_INFINITE_LOOP (20150930/psparse-542)
  ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC0.BAT0._BST] 
(Node 8802468b54d8), AE_AML_INFINITE_LOOP (20150930/psparse-542)

  This makes every process that depends on reading battery state hang
  indefinitely, including suspend and shutdown. It is my understanding
  that \_SB.PCI0.LPCB.EC0.MMRD is the PCI Node of Memory Read 32-bit
  double word, and that these other nodes reference it in their
  definitions. In the session I share (dmesg), no event gets registered
  in dmesg for several minutes before these errors. As I said, no
  obvious trigger.

  Also, perhaps related, I find two other ACPI parsing/execution errors that 
repeat on every boot and frequently show on dmesg without any visible effect:
  ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.EC0.ACCR] (Node 
8802b68b4ed8), AE_AML_INFINITE_LOOP (20150930/psparse-542)
  ACPI Error: Method parse/execution failed [\_SB.PCI0.ACEL._STA] (Node 
8802b68b90a0), AE_AML_INFINITE_LOOP (20150930/psparse-542)

  I haven't been able to find anything on the first node.

  This has been reproducible on kernel 3.19.

  Maybe worth mentioning. When disassembling DSDT from IASL I get a warning:
  iASL Warning: There were 6 external control methods found during disassembly, 
but additional ACPI tables to resolve these externals were not specified. The 
resulting disassembler output file may not compile because the disassembler did 
not know how many arguments to assign to these methods.

  ---
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   m  3446 F...m pulseaudio
   /dev/snd/controlC1:  m  3446 F pulseaudio
   /dev/snd/controlC0:  m  3446 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=bed51ac4-b6b1-43fc-8304-7b7b4a88b7bb
  InstallationDate: Installed on 2016-08-06 (26 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP ENVY m4 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=5a61dc86-7c12-4f8c-9f3c-717f399c2afc ro quiet splash 
acpi_backlight=vendor acpi_osi=Linux "acpi_osi=!Windows 2012" vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  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
  Tags:  xenial
  Uname: Linux 4.4.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/04/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 18EE
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 78.0D
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd06/04/2014:svnHewlett-Packard:pnHPENVYm4NotebookPC:pvr0877100022345B10001620130:rvnHewlett-Packard:rn18EE:rvr78.0D:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY m4 Notebook PC
  dmi.product.version: 0877100022345B10001620130
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1615881] Re: The label build for onexec when stacking is wrong

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1615881

Title:
  The label build for onexec when stacking is wrong

Status in AppArmor:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  The label build for onexec when crossing a namespace boundry is not   
  
  quite correct. The label needs to be built per profile and not based  
  
  on the whole label because the onexec transition only applies to  
  
  profiles within the ns. Where merging against the label could include 
  
  profile that are transitioned via the profile_transition callback 
  
  and should not be in the final label.

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

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

[Kernel-packages] [Bug 1593874] Re: warning stack trace while playing with apparmor namespaces

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1593874

Title:
  warning stack trace while playing with apparmor namespaces

Status in linux package in Ubuntu:
  Expired
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  I'm not sure what exactly I was doing when this happened, but
  something fairly basic (creating containers, adding/removing
  profiles). Let me know if you need more than the trace and I can try
  and figure out how to reproduce.

  Jun 17 20:20:06 dev kernel: [13314.032676] [ cut here 
]
  Jun 17 20:20:06 dev kernel: [13314.032689] WARNING: CPU: 3 PID: 8964 at 
/build/linux-oXTOqc/linux-4.4.0/security/apparmor/label.c:82 
__aa_proxy_redirect+0xff/0x130()
  Jun 17 20:20:06 dev kernel: [13314.032692] AppArmor WARN __aa_proxy_redirect: 
((!!queued_write_can_lock(&(&(&(&((orig)->vec[0])))[(((orig)->size)) - 
1])->ns))->labels)->lock)->raw_lock))): 
  Jun 17 20:20:06 dev kernel: [13314.032693] Modules linked in: binfmt_misc 
veth 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 bridge stp llc iptable_filter ip_tables x_tables isofs zfs(PO) 
zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) ppdev kvm_intel kvm joydev 
serio_raw irqbypass parport_pc parport ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad 
ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq libcrc32c raid1 raid0 multipath linear psmouse floppy
  Jun 17 20:20:06 dev kernel: [13314.032751] CPU: 3 PID: 8964 Comm: lxd 
Tainted: P        W  O    4.4.0-24-generic #43-Ubuntu
  Jun 17 20:20:06 dev kernel: [13314.032753] Hardware name: QEMU Standard PC 
(i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014
  Jun 17 20:20:06 dev kernel: [13314.032756]  0286 dc104ca4 
880044db3d18 813eab23
  Jun 17 20:20:06 dev kernel: [13314.032760]  880044db3d60 81cec7f0 
880044db3d50 810810d2
  Jun 17 20:20:06 dev kernel: [13314.032763]  880047f04360 88007a08d360 
88004a551b00 88004a551b38
  Jun 17 20:20:06 dev kernel: [13314.032766] Call Trace:
  Jun 17 20:20:06 dev kernel: [13314.032773]  [] 
dump_stack+0x63/0x90
  Jun 17 20:20:06 dev kernel: [13314.032777]  [] 
warn_slowpath_common+0x82/0xc0
  Jun 17 20:20:06 dev kernel: [13314.032780]  [] 
warn_slowpath_fmt+0x5c/0x80
  Jun 17 20:20:06 dev kernel: [13314.032784]  [] ? 
__list_remove_profile+0x62/0xe0
  Jun 17 20:20:06 dev kernel: [13314.032788]  [] 
__aa_proxy_redirect+0xff/0x130
  Jun 17 20:20:06 dev kernel: [13314.032792]  [] 
destroy_ns+0x86/0xa0
  Jun 17 20:20:06 dev kernel: [13314.032794]  [] 
__aa_remove_ns+0x2f/0x60
  Jun 17 20:20:06 dev kernel: [13314.032798]  [] 
aa_remove_profiles+0x193/0x270
  Jun 17 20:20:06 dev kernel: [13314.032800]  [] ? 
__aa_kvmalloc+0x41/0x60
  Jun 17 20:20:06 dev kernel: [13314.032803]  [] 
profile_remove+0x9e/0x1f0
  Jun 17 20:20:06 dev kernel: [13314.032808]  [] 
__vfs_write+0x18/0x40
  Jun 17 20:20:06 dev kernel: [13314.032811]  [] 
vfs_write+0xa9/0x1a0
  Jun 17 20:20:06 dev kernel: [13314.032814]  [] ? 
do_sys_open+0x1bf/0x2a0
  Jun 17 20:20:06 dev kernel: [13314.032818]  [] 
SyS_write+0x55/0xc0
  Jun 17 20:20:06 dev kernel: [13314.032823]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
  Jun 17 20:20:06 dev kernel: [13314.032826] ---[ end trace 2eb06377c45f3d4c 
]---

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

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

[Kernel-packages] [Bug 1615878] Re: __label_update proxy comparison test is wrong

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1615878

Title:
  __label_update proxy comparison test is wrong

Status in AppArmor:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  The comparing the proxy pointer, not the address of the labels proxy
  pointer.

  This results in labels that shouldn't entering into the invalidate
  label update path.

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

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

[Kernel-packages] [Bug 1615880] Re: The inherit check for new to old label comparison for domain transitions is wrong

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1615880

Title:
  The inherit check for new to old label comparison for domain
  transitions is wrong

Status in AppArmor:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  For the purposes of inherit we should be treating a profile/label transition  
  
  to its replacement as if the replacement is the profile/label.
  

  
  So make the comparison based off of the label proxy, not the label itself.

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

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

[Kernel-packages] [Bug 1615882] Re: dfa is missing a bounds check which can cause an oops

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1615882

Title:
  dfa is missing a bounds check which can cause an oops

Status in AppArmor:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  A custom crafted or corrupted binary profile can cause an oops when
  loaded due to a missing bounds check

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

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

[Kernel-packages] [Bug 1579135] Re: AppArmor profile reloading causes an intermittent kernel BUG

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1579135

Title:
  AppArmor profile reloading causes an intermittent kernel BUG

Status in apparmor package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Fix Committed
Status in apparmor source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in apparmor source package in Yakkety:
  Incomplete
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  First, a bit of background: I've built a go binary of the upstream
  snappy integration tests, and built them into a snap so that we can
  easily keep them up to date, and call them from other test suites.

  I'm running through the tests in qemu on a current 16 image (built
  yesteray), and hitting this most of the time with the homeInterface
  Suite tests in particular. The networkInterfaceSuite tests also seem
  to produce a similar problem:

  sudo snap connect home-consumer:home ubuntu-core:home
  [/] Connect home-consumer:home to ubuntu-core:home
  home-consumer.writer /home/ubuntu/snap/snappy-tests/11/writable
  sudo snap disconnect home-consumer:home ubuntu-core:home
  [  519.416354] BUG: unable to handle kernel NULL pointer dereference at 
0038
  [  519.417327] IP: [] profile_cmp+0x2f/0x180
  [  519.417978] PGD 1f26a067 PUD 1aa4f067 PMD 0 
  [  519.418574] Oops:  [#1] SMP 
  [  519.419032] Modules linked in: kvm_intel joydev kvm ppdev snd_pcm 
snd_timer irqbypass snd soundcore parport_pc pcspkr input_leds floppy parport 
evbug psmouse e1000 8250_fintek i2c_piix4 mac_hid pata_acpi serio_raw autofs4 
nls_iso8859_1 usb_storage ahci libahci squashfs
  [  519.422747] CPU: 0 PID: 1915 Comm: apparmor_parser Tainted: GW 
  4.4.0-21-generic #37-Ubuntu
  [  519.423689] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [  519.424627] task: 88001d23cb00 ti: 88001b58c000 task.ti: 
88001b58c000
  [  519.425385] RIP: 0010:[]  [] 
profile_cmp+0x2f/0x180
  [  519.426242] RSP: 0018:88001b58fcb0  EFLAGS: 00010086
  [  519.426791] RAX:  RBX: 88001b1b1400 RCX: 
0006
  [  519.427628] RDX:  RSI:  RDI: 
0009
  [  519.428405] RBP: 88001b58fcc0 R08: 000a R09: 
0274
  [  519.429127] R10: 88001f236890 R11: 0274 R12: 

  [  519.429956] R13: 000b R14:  R15: 
88001abff950
  [  519.430957] FS:  7f0c1609b740() GS:88001fc0() 
knlGS:
  [  519.432256] CS:  0010 DS:  ES:  CR0: 80050033
  [  519.433030] CR2: 0038 CR3: 1b14b000 CR4: 
06f0
  [  519.433868] Stack:
  [  519.434204]  000c 88001abff9b0 88001b58fd08 
8138a0c3
  [  519.435355]  00011f2b9450 880c 88001abff950 
88001b1b1760
  [  519.436480]  88001f236848 88001abff900 88001f236840 
88001b58fd98
  [  519.437609] Call Trace:
  [  519.438007]  [] aa_vec_unique+0x163/0x240
  [  519.438709]  [] __aa_labelset_update_subtree+0x687/0x820
  [  519.439537]  [] aa_replace_profiles+0x59b/0xb70
  [  519.440268]  [] ? __kmalloc+0x22e/0x250
  [  519.440944]  [] policy_update+0x9f/0x1f0
  [  519.441617]  [] profile_replace+0x13/0x20
  [  519.442299]  [] __vfs_write+0x18/0x40
  [  519.443032]  [] vfs_write+0xa9/0x1a0
  [  519.443721]  [] ? do_sys_open+0x1bf/0x2a0
  [  519.16]  [] SyS_write+0x55/0xc0
  [  519.445042]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [  519.445802] Code: 00 55 48 85 ff 48 89 e5 41 54 53 49 89 f4 48 89 fb 0f 84 
8b 00 00 00 4d 85 e4 0f 84 aa 00 00 00 48 83 7b 38 00 0f 84 c9 00 00 00 <49> 83 
7c 24 38 00 0f 84 e8 00 00 00 48 83 7b 08 00 0f 84 07 01 
  [  519.451336] RIP  [] profile_cmp+0x2f/0x180
  [  519.452088]  RSP 
  [  519.452570] CR2: 0038
  [  519.453032] ---[ end trace 65ff12ee2e7c26af ]---

  The details of this test can be found at:
  
https://github.com/ubuntu-core/snappy/tree/master/integration-tests/data/snaps/home-consumer

  Will follow up with more details

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

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

[Kernel-packages] [Bug 1615887] Re: profiles from different namespaces can block other namespaces from being able to load a profile

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1615887

Title:
  profiles from different namespaces can block other namespaces from
  being able to load a profile

Status in AppArmor:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  If ns1 has a profile A in it. It can cause loading a profile with the
  name A into ns2, and if it does succeed can result in compound labels
  crossing namespaces resulting in mediation not from one ns being
  applied to another.

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

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

[Kernel-packages] [Bug 1615889] Re: label vec reductions can result in reference labels instead of direct access to labels

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1615889

Title:
  label vec reductions can result in reference labels instead of direct
  access to labels

Status in AppArmor:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  The label vec cleanup/reduction can result in a reference label which
  while not causing wrong mediation is effectively a reference leak as
  the label will populate the label tree, consume memory and not be
  removed, it will only reduce to a reference of replacement vars.

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

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

[Kernel-packages] [Bug 1615895] Re: apparmor module parameters can be changed after the policy is locked

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1615895

Title:
  apparmor module parameters can be changed after the policy is locked

Status in AppArmor:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  the policy_lock parameter is a one way switch that prevents policy
  
  from being further modified. Unfortunately some of the module parameters  
  
  can effectively modify policy by turning off enforcement. 
  

  
  split policy_admin_capable into a view check and a full admin check,  
  
  and update the admin check to test the policy_lock parameter.

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

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

[Kernel-packages] [Bug 1615890] Re: stacking to unconfined in a child namespace confuses mediation

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1615890

Title:
  stacking to unconfined in a child namespace confuses mediation

Status in AppArmor:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  when viewing a stack involving unconfined from across a ns boundary   
  
  the mode is reported as mixed.
  

  
  Eg.   
  
  lxc-container-default//&:lxdns1://unconfined (mixed)  
  

  
  This is because the unconfined profile is in the special unconfined   
  
  mode. Which will result in a (mixed) mode for any stack with profiles 
  
  in enforcing or complain mode.
  

  
  This can however lead to confusion as to what mode is being used as   
  
  mixed is also used for enforcing stacked with complain, and This can
  also currently messes up mediation of trusted helpers like dbus.

  Since unconfined doesn't affect the stack just special case it.

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

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

[Kernel-packages] [Bug 1615893] Re: change_hat is logging failures during expected hat probing

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1615893

Title:
  change_hat is logging failures during expected hat probing

Status in AppArmor:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  change_hat using probing to find and transition to the first available
  
  hat. Hats missing as part of this probe are expected and should not   
  
  be logged except in complain mode.

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

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

[Kernel-packages] [Bug 1615892] Re: deleted files outside of the namespace are not being treated as disconnected

** Tags removed: verification-needed-xenial
** Tags added: verification-done-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/1615892

Title:
  deleted files outside of the namespace are not being treated as
  disconnected

Status in AppArmor:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Incomplete

Bug description:
  Deleted files outside of the namespace should be treated the same as
  other disconnected files

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

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

[Kernel-packages] [Bug 1497428] Re: kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968

2016-09-09 Thread Dan Streetman

That is very definitely not the same bug as this bug.

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

Title:
  kernel BUG at /build/buildd/linux-3.13.0/mm/page_alloc.c:968

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

Bug description:
  The kernel triggers a BUG when it finds it is in move_freepages() but
  the start and end pfns for the move are in different zones.

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

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

[Kernel-packages] [Bug 1618251] onza (amd64) - tests ran: 81, failed: 0

tests ran:  81, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-69.77~14.04.1/onza__3.19.0-69.77~14.04.1__2016-09-09_16-58-00/results-index.html

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-69.77~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
  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/1618251/+subscriptions

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

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

2016-09-09 Thread bugproxy

--- Comment From cdead...@us.ibm.com 2016-09-09 16:21 EDT---

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

Title:
  NVMe stress test fails after 12 hours on Ubuntu 16.04

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
   State: Open by: mdate on 21 June 2016 10:22:28 

  Stress testing for perfromance is being done in preparation for the the 
Tencent PoC Sort Competition using the attached per scripts.  The system either 
hangs, or the NVMe goes offline after 12 hours or so.
  The nvme drives are set up in a RAID 0 config.  The script is run like this:

  ./perf_nvme_fio2.sh nvme_jobfile_raid0_huawei

  mdate (md...@pezman.austin.ibm.com) added native attachment 
/opt/IBM/WebSphere/AppServer/profiles/cqweb/temp/ausratsrv5Node01/server1/TeamEAR/cqweb.war/perf_nvme_fio2.sh
 on 2016-06-21 10:22:28
  mdate (md...@pezman.austin.ibm.com) added native attachment 
/opt/IBM/WebSphere/AppServer/profiles/cqweb/temp/ausratsrv5Node01/server1/TeamEAR/cqweb.war/nvme_jobfile_raid0_huawei
 on 2016-06-21 10:22:28

  == Comment: #48 - Gabriel Krisman Bertazi  - 2016-07-18 12:33:13 ==
  Hi, 

  We need to apply the following patch to the Ubuntu kernel to prevent
  wrongly identification of ATARI partitions, as mentioned in the commit
  log.

  It still didn't make to Linus tree, but Jens Axboe already approved it
  on linux-block.

  https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
  block.git/commit/?h=for-4.8/core

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

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

[Kernel-packages] [Bug 1618550] Re: [HP 15-r085no Notebook PC (ENERGY STAR)] Suspend/resume freezes

2016-09-09 Thread Arto Makkonen

Here is a summary of the information that I can provide:

1. Which part of the process does the issue occur with, the suspend to ram, or
resuming from?
Please advise how you suspended specifically. For example:

Issue occurs when resuming.
I have suspended using the following methods: i) Click GUI menu item
"Suspend" and
ii) Briefly press the power button

2. Please advise how you resumed specifically.

I have resumed by pressing space or the power button. The commands below were
run after
attempting to resume by pressing the power button.

3.-10. [various commands] + Please attach to your report the resume
trace mentioned below.

Commands run but I'm getting an error running the resume trace following the
"resume-trace
debugging procedure for finding buggy drivers" method:

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
sh: 1: cannot create /sys/power/pm_trace: Permission denied

Please advice.

11. Please provide the output of the following terminal command:

cat /sys/kernel/debug/suspend_stats

Done. Please see my reply #10 above.

12. If you have a graphics related issue after resume (corruption,
display blank, etc.) please SSH into your machine and capture both
/var/log/Xorg.0.log and /var/log/Xorg.0.log.old. Please attach each
separately.

I have this issue but SSH connection was not possible during the blank screen
after resume.
Tried both WLAN and fixed connection. Apparently networking is down after
resume. Attached
both log files nevertheless. See the attachments in replies #10 and #11 below

Please help me solve the "Permission denied" error to enable tracing in steps
3.-10. Also, please clarify if you need a separate resume trace from every step
or just one trace after completing all of the steps 3-10.

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

Title:
[HP 15-r085no Notebook PC (ENERGY STAR)] Suspend/resume freezes

Status in linux package in Ubuntu:
Confirmed

Bug description:
My HP notebook won't wake from suspend with 16.04 LTS, waited for the
latest 4.4.0-36 kernel update before reporting this bug. Computer goes
to suspend, but attempts to wake it up just start the fan (and HDD)
while the display remains black.

Also tested this with the mainline upstream kernel
4.8.0-040800rc3-generic. With this version there was different
behaviour but still a bug: the display woke up but Ubuntu was very
unstable, did not connect to Wifi and the GUI froze very soon after
resume.

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/controlC0: arto 3449 F pulseaudio
/dev/snd/controlC1: arto 3449 F pulseaudio
CurrentDesktop: Unity
Date: Tue Aug 30 19:42:38 2016
HibernationDevice: RESUME=UUID=8b70a4a1-df29-4f51-9b65-c2a17b4361a2
InstallationDate: Installed on 2015-09-18 (347 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: Hewlett-Packard HP 15 Notebook PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed
root=UUID=c1e1c032-887a-44c8-b4d2-0850b57082e8 ro quiet splash vt.handoff=7
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-15 (15 days ago)
dmi.bios.date: 05/21/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.18
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2212
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 86.28
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097610405F0620180:rvnHewlett-Packard:rn2212:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 15 Notebook PC
dmi.product.version: 097610405F0620180
dmi.sys.vendor: Hewlett-Packard

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

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

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

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

Title:
  chown of SUID executable in docker container on overlayfs fails with
  kernel BUG at linux-4.4.0/fs/attr.c:280

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1. Take any fresh installation of Ubuntu 16.04. I used Vagrant to
  reproduce this bug, but it also reproduces on my VM with Ubuntu 16.04
  in Azure.

  2. Upgrade kernel to current latest release (linux-
  image-4.4.0-36-generic).

  # uname -r
  4.4.0-36-generic

  3. Install Docker 1.11.2 from Ubuntu repositories (also can be
  reproduced with Docker 1.12.1 from official Docker repositories for
  Debian/Ubuntu):

  # apt install docker.io

  4. Use overlayfs as storage driver in Docker. Edit /etc/default/docker
  and add DOCKER_OPTS="--storage-driver=overlay":

  # echo 'DOCKER_OPTS="--storage-driver=overlay"' >> /etc/default/docker
  # systemctl restart docker
  # docker info
  Containers: 1
   Running: 1
   Paused: 0
   Stopped: 0
  Images: 1
  Server Version: 1.11.2
  Storage Driver: overlay
   Backing Filesystem: extfs
  Logging Driver: json-file
  Cgroup Driver: cgroupfs
  Plugins: 
   Volume: local
   Network: bridge null host
  Kernel Version: 4.4.0-36-generic
  Operating System: Ubuntu 16.04.1 LTS
  OSType: linux
  Architecture: x86_64
  CPUs: 1
  Total Memory: 488.5 MiB
  Name: vagrant
  ID: COJW:JDNB:4KBK:VJJN:PDW4:ECVU:6TCT:BAEY:5Z4T:WYGD:Q5BD:PZHH
  Docker Root Dir: /var/lib/docker
  Debug mode (client): false
  Debug mode (server): false
  Registry: https://index.docker.io/v1/
  WARNING: No swap limit support

  
  5. Start container and run following commands in container:

  # docker run --rm -ti busybox:latest /bin/sh
  Unable to find image 'busybox:latest' locally
  latest: Pulling from library/busybox
  8ddc19f16526: Pull complete 
  Digest: 
sha256:a59906e33509d14c036c8678d687bd4eec81ed7c4b8ce907b888c607f6a1e0e6
  Status: Downloaded newer image for busybox:latest
  / # touch a
  / # chmod 04744 a
  / # stat a
File: a
Size: 0   Blocks: 0  IO Block: 4096   regular empty file
  Device: fc00h/64512dInode: 264640  Links: 1
  Access: (4744/-rwsr--r--)  Uid: (0/root)   Gid: (0/root)
  Access: 2016-09-09 19:18:50.0
  Modify: 2016-09-09 19:18:50.0
  Change: 2016-09-09 19:18:56.0

  / # chown 0:12345 a
  Segmentation fault
  / # 

  During chown fault following appears in dmesg:

  [  753.808988] [ cut here ]
  [  753.809003] kernel BUG at /build/linux-a2WvEb/linux-4.4.0/fs/attr.c:280!
  [  753.809016] invalid opcode:  [#1] SMP 
  [  753.809026] Modules linked in: overlay veth ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_na
  t nf_conntrack br_netfilter bridge stp llc aufs vboxsf ppdev crct10dif_pclmul 
crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd 
input_leds serio_raw vboxvideo 8250_fintek parpo
  rt_pc parport ttm drm_kms_helper mac_hid drm fb_sys_fops i2c_piix4 
syscopyarea vboxguest sysfillrect sysimgblt sunrpc autofs4 psmouse ahci libahci 
e1000 pata_acpi video fjes
  [  753.809172] CPU: 0 PID: 5971 Comm: chown Tainted: GW   
4.4.0-36-generic #55-Ubuntu
  [  753.809188] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS 
VirtualBox 12/01/2006
  [  753.809203] task: 88001f042c40 ti: 880010c74000 task.ti: 
880010c74000
  [  753.809217] RIP: 0010:[]  [] 
notify_change+0x303/0x360
  [  753.809258] RSP: 0018:880010c77db0  EFLAGS: 00010202
  [  753.809270] RAX: 57d30b2d RBX: 1847 RCX: 
0017
  [  753.809297] RDX: 0771653f RSI: 0771653f RDI: 
57d30b2d
  [  753.809312] RBP: 880010c77de0 R08:  R09: 
0001
  [  753.809332] R10:  R11: 880017582a0c R12: 
880010c77e78
  [  753.809352] R13: 8800194f7cc0 R14: 89e4 R15: 
880016a77b88
  [  753.809389] FS:  011991f0(0063) GS:88001fc0() 
knlGS:
  [  753.809420] CS:  0010 DS:  ES:  CR0: 8005003b
  [  753.809431] CR2: 0119abf8 CR3: 17cbe000 CR4: 
000406f0
  [  753.809446] DR0:  DR1:  DR2: 

  [  753.809461] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  753.809491] Stack:
  [  753.809496]    880010c77e78 
880012299e40
  [  753.809517]  8800194f7cc0 880019ed46a8 880010c77e10 
c03573d1
  [  753.809552]  1847 880010c77e78 880012299e40 

  [

[Kernel-packages] [Bug 1621989] Re: chown in docker container on overlayfs fails with kernel BUG at linux-4.4.0/fs/attr.c:280

2016-09-09 Thread Vladimir Rutsky

Same result with kernel from Yakkety (linux-headers-4.4.0-9136-generic):

[   57.178253] [ cut here ]
[   57.178269] kernel BUG at /build/linux-rTsl6N/linux-4.4.0/fs/attr.c:280!
[   57.178297] invalid opcode:  [#1] SMP 
[   57.178321] Modules linked in: veth ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter 
bridge stp llc overlay vboxsf(OE) ppdev crct10dif_pclmul crc32_pclmul 
aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd input_leds 
serio_raw i2c_piix4 parport_pc parport vboxvideo(OE) 8250_fintek vboxguest(OE) 
ttm drm_kms_helper mac_hid drm fb_sys_fops syscopyarea sysfillrect sysimgblt 
sunrpc autofs4 psmouse ahci libahci e1000 pata_acpi fjes video
[   57.178467] CPU: 0 PID: 2311 Comm: chown Tainted: GW  OE   
4.4.0-9136-generic #55-Ubuntu
[   57.178483] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS 
VirtualBox 12/01/2006
[   57.178498] task: 88001a75ac40 ti: 88001be98000 task.ti: 
88001be98000
[   57.178512] RIP: 0010:[]  [] 
notify_change+0x303/0x360
[   57.178536] RSP: 0018:88001be9bdb0  EFLAGS: 00010202
[   57.178547] RAX: 57d31402 RBX: 1847 RCX: 0017
[   57.178559] RDX: 072eb4fc RSI: 072eb4fc RDI: 57d31402
[   57.178572] RBP: 88001be9bde0 R08:  R09: 0001
[   57.178585] R10:  R11: 88001ec4320c R12: 88001be9be78
[   57.178598] R13: 880019ce0e40 R14: 89e4 R15: 880019d14948
[   57.178612] FS:  00f241f0(0063) GS:88001fc0() 
knlGS:
[   57.178626] CS:  0010 DS:  ES:  CR0: 8005003b
[   57.178637] CR2: 00f25bf8 CR3: 1745a000 CR4: 000406f0
[   57.178652] DR0:  DR1:  DR2: 
[   57.178665] DR3:  DR6: fffe0ff0 DR7: 0400
[   57.178677] Stack:
[   57.178698]    88001be9be78 
880019ce0f00
[   57.178716]  880019ce0e40 88001f1bd3f8 88001be9be10 
c02953d1
[   57.178747]  1847 88001be9be78 880019ce0f00 

[   57.178764] Call Trace:
[   57.178773]  [] ovl_setattr+0x81/0xc0 [overlay]
[   57.178786]  [] notify_change+0x235/0x360
[   57.178810]  [] chown_common+0x18b/0x1e0
[   57.178851]  [] SyS_chown+0x9d/0xe0
[   57.178862]  [] entry_SYSCALL_64_fastpath+0x16/0x71
[   57.179294] Code: 4c 89 ef e8 90 87 17 00 31 c0 e9 00 fe ff ff 83 ca 01 41 
89 14 24 89 d3 41 0f b7 07 e9 23 fe ff ff b8 ff ff ff ff e9 e4 fd ff ff <0f> 0b 
48 3b 50 30 0f 85 50 fe ff ff e9 08 ff ff ff 4c 89 e6 4c 
[   57.180459] RIP  [] notify_change+0x303/0x360
[   57.180828]  RSP 
[   57.181247] ---[ end trace 4d5ff9f2f68c4235 ]---


** Summary changed:

- chown in docker container on overlayfs fails with kernel BUG at 
linux-4.4.0/fs/attr.c:280
+ chown of SUID executable in docker container on overlayfs fails with kernel 
BUG at linux-4.4.0/fs/attr.c:280

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

Title:
  chown of SUID executable in docker container on overlayfs fails with
  kernel BUG at linux-4.4.0/fs/attr.c:280

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1. Take any fresh installation of Ubuntu 16.04. I used Vagrant to
  reproduce this bug, but it also reproduces on my VM with Ubuntu 16.04
  in Azure.

  2. Upgrade kernel to current latest release (linux-
  image-4.4.0-36-generic).

  # uname -r
  4.4.0-36-generic

  3. Install Docker 1.11.2 from Ubuntu repositories (also can be
  reproduced with Docker 1.12.1 from official Docker repositories for
  Debian/Ubuntu):

  # apt install docker.io

  4. Use overlayfs as storage driver in Docker. Edit /etc/default/docker
  and add DOCKER_OPTS="--storage-driver=overlay":

  # echo 'DOCKER_OPTS="--storage-driver=overlay"' >> /etc/default/docker
  # systemctl restart docker
  # docker info
  Containers: 1
   Running: 1
   Paused: 0
   Stopped: 0
  Images: 1
  Server Version: 1.11.2
  Storage Driver: overlay
   Backing Filesystem: extfs
  Logging Driver: json-file
  Cgroup Driver: cgroupfs
  Plugins: 
   Volume: local
   Network: bridge null host
  Kernel Version: 4.4.0-36-generic
  Operating System: Ubuntu 16.04.1 LTS
  OSType: linux
  Architecture: x86_64
  CPUs: 1
  Total Memory: 488.5 MiB
  Name: vagrant
  ID: COJW:JDNB:4KBK:VJJN:PDW4:ECVU:6TCT:BAEY:5Z4T:WYGD:Q5BD:PZHH
  Docker Root Dir: /var/lib/docker
  Debug mode (client): false
  Debug mode (server): false
  Registry: https://index.docker.io/v1/
  WARNING: No swap limit support

  
  5. Start container and run following commands in container:

  # docker run --rm -ti

[Kernel-packages] [Bug 1621989] Re: chown in docker container on overlayfs fails with kernel BUG at linux-4.4.0/fs/attr.c:280

2016-09-09 Thread Tim Gardner

Vladimir - please try the kernel in proposed, Ubuntu-4.4.0-38.57. It has
a patch that likely addresses your bug: "UBUNTU: SAUCE: overlayfs: fix
regression in whiteout detection".

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

Title:
  chown of SUID executable in docker container on overlayfs fails with
  kernel BUG at linux-4.4.0/fs/attr.c:280

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:

  1. Take any fresh installation of Ubuntu 16.04. I used Vagrant to
  reproduce this bug, but it also reproduces on my VM with Ubuntu 16.04
  in Azure.

  2. Upgrade kernel to current latest release (linux-
  image-4.4.0-36-generic).

  # uname -r
  4.4.0-36-generic

  3. Install Docker 1.11.2 from Ubuntu repositories (also can be
  reproduced with Docker 1.12.1 from official Docker repositories for
  Debian/Ubuntu):

  # apt install docker.io

  4. Use overlayfs as storage driver in Docker. Edit /etc/default/docker
  and add DOCKER_OPTS="--storage-driver=overlay":

  # echo 'DOCKER_OPTS="--storage-driver=overlay"' >> /etc/default/docker
  # systemctl restart docker
  # docker info
  Containers: 1
   Running: 1
   Paused: 0
   Stopped: 0
  Images: 1
  Server Version: 1.11.2
  Storage Driver: overlay
   Backing Filesystem: extfs
  Logging Driver: json-file
  Cgroup Driver: cgroupfs
  Plugins: 
   Volume: local
   Network: bridge null host
  Kernel Version: 4.4.0-36-generic
  Operating System: Ubuntu 16.04.1 LTS
  OSType: linux
  Architecture: x86_64
  CPUs: 1
  Total Memory: 488.5 MiB
  Name: vagrant
  ID: COJW:JDNB:4KBK:VJJN:PDW4:ECVU:6TCT:BAEY:5Z4T:WYGD:Q5BD:PZHH
  Docker Root Dir: /var/lib/docker
  Debug mode (client): false
  Debug mode (server): false
  Registry: https://index.docker.io/v1/
  WARNING: No swap limit support

  
  5. Start container and run following commands in container:

  # docker run --rm -ti busybox:latest /bin/sh
  Unable to find image 'busybox:latest' locally
  latest: Pulling from library/busybox
  8ddc19f16526: Pull complete 
  Digest: 
sha256:a59906e33509d14c036c8678d687bd4eec81ed7c4b8ce907b888c607f6a1e0e6
  Status: Downloaded newer image for busybox:latest
  / # touch a
  / # chmod 04744 a
  / # stat a
File: a
Size: 0   Blocks: 0  IO Block: 4096   regular empty file
  Device: fc00h/64512dInode: 264640  Links: 1
  Access: (4744/-rwsr--r--)  Uid: (0/root)   Gid: (0/root)
  Access: 2016-09-09 19:18:50.0
  Modify: 2016-09-09 19:18:50.0
  Change: 2016-09-09 19:18:56.0

  / # chown 0:12345 a
  Segmentation fault
  / # 

  During chown fault following appears in dmesg:

  [  753.808988] [ cut here ]
  [  753.809003] kernel BUG at /build/linux-a2WvEb/linux-4.4.0/fs/attr.c:280!
  [  753.809016] invalid opcode:  [#1] SMP 
  [  753.809026] Modules linked in: overlay veth ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_na
  t nf_conntrack br_netfilter bridge stp llc aufs vboxsf ppdev crct10dif_pclmul 
crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd 
input_leds serio_raw vboxvideo 8250_fintek parpo
  rt_pc parport ttm drm_kms_helper mac_hid drm fb_sys_fops i2c_piix4 
syscopyarea vboxguest sysfillrect sysimgblt sunrpc autofs4 psmouse ahci libahci 
e1000 pata_acpi video fjes
  [  753.809172] CPU: 0 PID: 5971 Comm: chown Tainted: GW   
4.4.0-36-generic #55-Ubuntu
  [  753.809188] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS 
VirtualBox 12/01/2006
  [  753.809203] task: 88001f042c40 ti: 880010c74000 task.ti: 
880010c74000
  [  753.809217] RIP: 0010:[]  [] 
notify_change+0x303/0x360
  [  753.809258] RSP: 0018:880010c77db0  EFLAGS: 00010202
  [  753.809270] RAX: 57d30b2d RBX: 1847 RCX: 
0017
  [  753.809297] RDX: 0771653f RSI: 0771653f RDI: 
57d30b2d
  [  753.809312] RBP: 880010c77de0 R08:  R09: 
0001
  [  753.809332] R10:  R11: 880017582a0c R12: 
880010c77e78
  [  753.809352] R13: 8800194f7cc0 R14: 89e4 R15: 
880016a77b88
  [  753.809389] FS:  011991f0(0063) GS:88001fc0() 
knlGS:
  [  753.809420] CS:  0010 DS:  ES:  CR0: 8005003b
  [  753.809431] CR2: 0119abf8 CR3: 17cbe000 CR4: 
000406f0
  [  753.809446] DR0:  DR1:  DR2: 

  [  753.809461] DR3:  DR6: fffe0ff0 DR7: 
0400
  [  753.809491] Stack:
  [  753.809496]    880010c77e78 
880012299e40
  [  753.809517]  8800194f7cc0 880019ed46a8 880010c77e10 
c03573d1
  [

[Kernel-packages] [Bug 1621989] [NEW] chown in docker container on overlayfs fails with kernel BUG at linux-4.4.0/fs/attr.c:280

2016-09-09 Thread Vladimir Rutsky

Public bug reported:

Steps to reproduce:

1. Take any fresh installation of Ubuntu 16.04. I used Vagrant to
reproduce this bug, but it also reproduces on my VM with Ubuntu 16.04 in
Azure.

2. Upgrade kernel to current latest release (linux-
image-4.4.0-36-generic).

# uname -r
4.4.0-36-generic

3. Install Docker 1.11.2 from Ubuntu repositories (also can be
reproduced with Docker 1.12.1 from official Docker repositories for
Debian/Ubuntu):

# apt install docker.io

4. Use overlayfs as storage driver in Docker. Edit /etc/default/docker
and add DOCKER_OPTS="--storage-driver=overlay":

# echo 'DOCKER_OPTS="--storage-driver=overlay"' >> /etc/default/docker
# systemctl restart docker
# docker info
Containers: 1
 Running: 1
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.11.2
Storage Driver: overlay
 Backing Filesystem: extfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins: 
 Volume: local
 Network: bridge null host
Kernel Version: 4.4.0-36-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 488.5 MiB
Name: vagrant
ID: COJW:JDNB:4KBK:VJJN:PDW4:ECVU:6TCT:BAEY:5Z4T:WYGD:Q5BD:PZHH
Docker Root Dir: /var/lib/docker
Debug mode (client): false
Debug mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support


5. Start container and run following commands in container:

# docker run --rm -ti busybox:latest /bin/sh
Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
8ddc19f16526: Pull complete 
Digest: sha256:a59906e33509d14c036c8678d687bd4eec81ed7c4b8ce907b888c607f6a1e0e6
Status: Downloaded newer image for busybox:latest
/ # touch a
/ # chmod 04744 a
/ # stat a
  File: a
  Size: 0   Blocks: 0  IO Block: 4096   regular empty file
Device: fc00h/64512dInode: 264640  Links: 1
Access: (4744/-rwsr--r--)  Uid: (0/root)   Gid: (0/root)
Access: 2016-09-09 19:18:50.0
Modify: 2016-09-09 19:18:50.0
Change: 2016-09-09 19:18:56.0

/ # chown 0:12345 a
Segmentation fault
/ # 

During chown fault following appears in dmesg:

[  753.808988] [ cut here ]
[  753.809003] kernel BUG at /build/linux-a2WvEb/linux-4.4.0/fs/attr.c:280!
[  753.809016] invalid opcode:  [#1] SMP 
[  753.809026] Modules linked in: overlay veth ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 
xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_na
t nf_conntrack br_netfilter bridge stp llc aufs vboxsf ppdev crct10dif_pclmul 
crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd 
input_leds serio_raw vboxvideo 8250_fintek parpo
rt_pc parport ttm drm_kms_helper mac_hid drm fb_sys_fops i2c_piix4 syscopyarea 
vboxguest sysfillrect sysimgblt sunrpc autofs4 psmouse ahci libahci e1000 
pata_acpi video fjes
[  753.809172] CPU: 0 PID: 5971 Comm: chown Tainted: GW   
4.4.0-36-generic #55-Ubuntu
[  753.809188] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS 
VirtualBox 12/01/2006
[  753.809203] task: 88001f042c40 ti: 880010c74000 task.ti: 
880010c74000
[  753.809217] RIP: 0010:[]  [] 
notify_change+0x303/0x360
[  753.809258] RSP: 0018:880010c77db0  EFLAGS: 00010202
[  753.809270] RAX: 57d30b2d RBX: 1847 RCX: 0017
[  753.809297] RDX: 0771653f RSI: 0771653f RDI: 57d30b2d
[  753.809312] RBP: 880010c77de0 R08:  R09: 0001
[  753.809332] R10:  R11: 880017582a0c R12: 880010c77e78
[  753.809352] R13: 8800194f7cc0 R14: 89e4 R15: 880016a77b88
[  753.809389] FS:  011991f0(0063) GS:88001fc0() 
knlGS:
[  753.809420] CS:  0010 DS:  ES:  CR0: 8005003b
[  753.809431] CR2: 0119abf8 CR3: 17cbe000 CR4: 000406f0
[  753.809446] DR0:  DR1:  DR2: 
[  753.809461] DR3:  DR6: fffe0ff0 DR7: 0400
[  753.809491] Stack:
[  753.809496]    880010c77e78 
880012299e40
[  753.809517]  8800194f7cc0 880019ed46a8 880010c77e10 
c03573d1
[  753.809552]  1847 880010c77e78 880012299e40 

[  753.809585] Call Trace:
[  753.809596]  [] ovl_setattr+0x81/0xc0 [overlay]
[  753.809612]  [] notify_change+0x235/0x360
[  753.809626]  [] chown_common+0x18b/0x1e0
[  753.809660]  [] SyS_chown+0x9d/0xe0
[  753.809674]  [] entry_SYSCALL_64_fastpath+0x16/0x71
[  753.810211] Code: 4c 89 ef e8 60 87 17 00 31 c0 e9 00 fe ff ff 83 ca 01 41 
89 14 24 89 d3 41 0f b7 07 e9 23 fe ff ff b8 ff ff ff ff e9 e4 fd ff ff <0f> 0b 
48 3b 50 30 0f 85 50 fe ff ff e9 08 ff ff ff 4c 
89 e6 4c 
[  753.811863] RIP  [] notify_change+0x303/0x360
[  753.812355]  RSP 
[  753.812839] fbcon_switch: detected unhandled fb_set_par error,

[Kernel-packages] [Bug 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

2016-09-09 Thread Steve Langasek

** Changed in: efivar (Ubuntu Trusty)
   Status: Fix Released => Invalid

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

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efibootmgr package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Precise:
  New
Status in efibootmgr source package in Precise:
  Invalid
Status in efivar source package in Precise:
  Fix Released
Status in grub2 source package in Precise:
  Invalid
Status in grub2-signed source package in Precise:
  Invalid
Status in mokutil source package in Precise:
  Fix Released
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  Fix Committed
Status in dkms source package in Trusty:
  Fix Released
Status in efibootmgr source package in Trusty:
  Invalid
Status in efivar source package in Trusty:
  Invalid
Status in grub2 source package in Trusty:
  Invalid
Status in grub2-signed source package in Trusty:
  Invalid
Status in mokutil source package in Trusty:
  Fix Released
Status in shim source package in Trusty:
  New
Status in shim-signed source package in Trusty:
  Fix Released
Status in dkms source package in Wily:
  Fix Released
Status in efibootmgr source package in Wily:
  Fix Released
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  Invalid
Status in grub2-signed source package in Wily:
  Invalid
Status in mokutil source package in Wily:
  Fix Released
Status in shim source package in Wily:
  New
Status in shim-signed source package in Wily:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released
Status in efibootmgr source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in mokutil source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  New
Status in shim-signed source package in Xenial:
  Fix Released

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  
https://docs.google.com/spreadsheets/d/1GbyQDb4-sRv7OlIpbISiwVJ2ARHP3AkG2HbPTRk7p-E/edit#gid=0

  Test cases here are separated by the components that need to be
  changed:

  = mokutil =

  Adding a MOK key:
  1) Install system
  2) Run 'mokutil --import ' to import a signing certificate.
  3) On reboot; validate MOK prompts for new MOK key to add.

  Toggling Secure Boot state:
  1) Install system
  2) mokutil --enable-validationormokutil --disable-validation
  3) Validate that on reboot MOK prompts to change Secure Boot state.

  Listing keys:
  1) mokutil --list-enrolled
  -- should list keys previously enrolled, and Microsoft keys on systems that 
are configured with them for factory Secure Boot.

  
  = efivar =

  libefivar0 gets tested via the use of mokutil. Since it is a library
  with no directly usable binaries; we rely on mokutil / sbsigntool /
  efibootmgr to do testing.

  1) Run efibootmgr -v ; verify it lists BootEntries.
  2) Run efibootmgr -c -L ubuntu2 -l \\EFI\\ubuntu\\shimx64.efi ; verify that 
on reboot; you can get into a boot menu that will list 'ubuntu2', and that 
picking that boot entry boots into Ubuntu.

  
  = shim-signed =

  1) Install system; upgrade to new packages
  1b) Verify /proc/sys/kernel/secure_boot shows 1.
  1c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.
  2) Run 'sudo update-secureboot-policy'; validate that it prompts to disable 
Secure Boot if it's not already disabled.
  3) Run 'sudo update-secureboot-policy'; validate you are not prompted again 
to disable Secure Boot.
  4) Reboot; follow MOK steps to disable Secure Boot.
  4b) Verify /proc/sys/kernel/secure_boot shows 1.
  4c) Verify /proc/sys/kernel/moksbstate_disabled shows 1.
  5) Run 'sudo update-secureboot-policy --enable'; validate you are prompted to 
enable Secure Boot.
  6) Reboot; follow MOK steps to re-enable Secure Boot.
  6b) Verify /proc/sys/kernel/secure_boot shows 1.
  6c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.

  
  = grub2 =

  Booting signed kernels:
  1) Try to boot a custom kernel
  2) Verify that the kernel will not be loaded by

[Kernel-packages] [Bug 1608854] Re: [arm64] nova instances can't boot with 3.13.0-92

2016-09-09 Thread Tim Gardner

Junien - please try the refreshed kernel with boot issue fix at
http://people.canonical.com/~rtg/arm64-efi-lp1608854/ - You should
hopefully not see any arm64 regressions.

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

** Tags removed: verification-done-trusty

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

Title:
  [arm64] nova instances can't boot with 3.13.0-92

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Trusty:
  New
Status in linux source package in Trusty:
  In Progress

Bug description:
  Hi,

  It would appear that arm64 nova instances can't boot on 3.13.0-92.

  The serial console displays :

  error: plain Image kernel not supported - rebuild with CONFIG_(U)EFI_STUB 
enabled.
  unaligned pointer 0xb90002e058000c57
  Aborted. Press any key to exit.

  I suspect this is due to LP#1566221, more specifically :
 * [Config] CONFIG_EFI=n for arm64

  This is pretty serious. I'm not 100% sure the above is the cause, but
  if so, it should be reverted asap.

  Thank you.
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg:
   [   27.314355] random: nonblocking pool is initialized
   [   43.711734] init: jenkins-slave main process (1169) terminated with 
status 143
  DistroRelease: Ubuntu 14.04
  Ec2AMI: ami-08ce
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.medium
  Ec2Kernel: None
  Ec2Ramdisk: None
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic 
root=UUID=88f61243-be05-46db-b772-d7ed13eb39de ro earlyprintk
  ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-85-generic N/A
   linux-backports-modules-3.13.0-85-generic  N/A
   linux-firmware 1.127.22
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty ec2-images
  Uname: Linux 3.13.0-85-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1608854/+subscriptions

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

[Kernel-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp

2016-09-09 Thread Cyril Humbert

The present bug is probably related to
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324 .

The comment given 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/comments/15
seems to confirm #35 and #38: the regression is caused by some patch applied 
for the Ubuntu
Pulseaudio package.

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

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

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

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

[Kernel-packages] [Bug 1574727] Re: [SRU] Enforce using signed kernels and modules on UEFI

2016-09-09 Thread Mathieu Trudel-Lapierre

efivar for trusty ended up not being needed.

** Changed in: efivar (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Enforce using signed kernels and modules on UEFI

Status in dkms package in Ubuntu:
  Fix Released
Status in efibootmgr package in Ubuntu:
  Fix Released
Status in efivar package in Ubuntu:
  Fix Released
Status in grub2 package in Ubuntu:
  New
Status in grub2-signed package in Ubuntu:
  New
Status in mokutil package in Ubuntu:
  Fix Released
Status in shim package in Ubuntu:
  New
Status in shim-signed package in Ubuntu:
  Fix Released
Status in dkms source package in Precise:
  New
Status in efibootmgr source package in Precise:
  Invalid
Status in efivar source package in Precise:
  Fix Released
Status in grub2 source package in Precise:
  Invalid
Status in grub2-signed source package in Precise:
  Invalid
Status in mokutil source package in Precise:
  Fix Released
Status in shim source package in Precise:
  New
Status in shim-signed source package in Precise:
  Fix Committed
Status in dkms source package in Trusty:
  Fix Released
Status in efibootmgr source package in Trusty:
  Invalid
Status in efivar source package in Trusty:
  Fix Released
Status in grub2 source package in Trusty:
  Invalid
Status in grub2-signed source package in Trusty:
  Invalid
Status in mokutil source package in Trusty:
  Fix Released
Status in shim source package in Trusty:
  New
Status in shim-signed source package in Trusty:
  Fix Released
Status in dkms source package in Wily:
  Fix Released
Status in efibootmgr source package in Wily:
  Fix Released
Status in efivar source package in Wily:
  Fix Released
Status in grub2 source package in Wily:
  Invalid
Status in grub2-signed source package in Wily:
  Invalid
Status in mokutil source package in Wily:
  Fix Released
Status in shim source package in Wily:
  New
Status in shim-signed source package in Wily:
  Fix Released
Status in dkms source package in Xenial:
  Fix Released
Status in efibootmgr source package in Xenial:
  Fix Released
Status in efivar source package in Xenial:
  Fix Released
Status in grub2 source package in Xenial:
  Fix Released
Status in grub2-signed source package in Xenial:
  Fix Released
Status in mokutil source package in Xenial:
  Fix Released
Status in shim source package in Xenial:
  New
Status in shim-signed source package in Xenial:
  Fix Released

Bug description:
  [Rationale]
  Secure Boot is good. We want to be able to validate that as much as possible 
of the boot process happens with signed binaries; from our shim (the part that 
is loaded by the EFI firmware itself), down to grub2, the kernel, and even 
loaded modules.

  [Impact]
  All our users booting in UEFI; on all supported releases.

  [Test cases]
  
https://docs.google.com/spreadsheets/d/1GbyQDb4-sRv7OlIpbISiwVJ2ARHP3AkG2HbPTRk7p-E/edit#gid=0

  Test cases here are separated by the components that need to be
  changed:

  = mokutil =

  Adding a MOK key:
  1) Install system
  2) Run 'mokutil --import ' to import a signing certificate.
  3) On reboot; validate MOK prompts for new MOK key to add.

  Toggling Secure Boot state:
  1) Install system
  2) mokutil --enable-validationormokutil --disable-validation
  3) Validate that on reboot MOK prompts to change Secure Boot state.

  Listing keys:
  1) mokutil --list-enrolled
  -- should list keys previously enrolled, and Microsoft keys on systems that 
are configured with them for factory Secure Boot.

  
  = efivar =

  libefivar0 gets tested via the use of mokutil. Since it is a library
  with no directly usable binaries; we rely on mokutil / sbsigntool /
  efibootmgr to do testing.

  1) Run efibootmgr -v ; verify it lists BootEntries.
  2) Run efibootmgr -c -L ubuntu2 -l \\EFI\\ubuntu\\shimx64.efi ; verify that 
on reboot; you can get into a boot menu that will list 'ubuntu2', and that 
picking that boot entry boots into Ubuntu.

  
  = shim-signed =

  1) Install system; upgrade to new packages
  1b) Verify /proc/sys/kernel/secure_boot shows 1.
  1c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.
  2) Run 'sudo update-secureboot-policy'; validate that it prompts to disable 
Secure Boot if it's not already disabled.
  3) Run 'sudo update-secureboot-policy'; validate you are not prompted again 
to disable Secure Boot.
  4) Reboot; follow MOK steps to disable Secure Boot.
  4b) Verify /proc/sys/kernel/secure_boot shows 1.
  4c) Verify /proc/sys/kernel/moksbstate_disabled shows 1.
  5) Run 'sudo update-secureboot-policy --enable'; validate you are prompted to 
enable Secure Boot.
  6) Reboot; follow MOK steps to re-enable Secure Boot.
  6b) Verify /proc/sys/kernel/secure_boot shows 1.
  6c) Verify /proc/sys/kernel/moksbstate_disabled shows 0.

  
  = grub2 =

  Booting signed kernels:
  1) Try to boot a custom

[Kernel-packages] [Bug 1620811] Re: Focaltech touchpad detected as mouse on Asus K501UW laptop

2016-09-09 Thread Egor

The problem persists in 4.8-rc5 (the latest currently available).

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

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

Title:
  Focaltech touchpad detected as mouse on Asus K501UW laptop

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Following the bug reporting documentation here:
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.

  The Focaltech touchpad on Asus K501UW laptop is detected as a mouse,
  so I can't access touchpad features such as two-finger scrolling or
  use two-finger tap as right mouse button. The touchpad is recognized
  in xinput-list as "FTE1001:00 0B05:0101".

  The bug appears in Ubuntu Mate 16.04.1 x64 and Linux Mint 18 Cinnamon
  x64, both with kernel 4.4.0-31. I've also tried Linux Mint 17.3 x64
  with kernel 3.19, and there the touchpad does not work at all (does
  not function even as a mouse).

  The bug is resemblant of #1372609.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: 
boot/vmlinuz-4.4.0-31-generic]
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  e2 3605 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Sep  6 15:13:50 2016
  HibernationDevice: RESUME=UUID=8407ca60-029d-4be6-ab12-a2f1aee1d843
  InstallationDate: Installed on 2016-09-05 (1 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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 0bda:57ed Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=826cac6a-2d18-4d8d-a9ee-85299d3cac91 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UW.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UW
  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.:bvrK501UW.203:bd03/30/2016:svnASUSTeKCOMPUTERINC.:pnK501UW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K501UW
  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/1620811/+subscriptions

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

[Kernel-packages] [Bug 1620658] onibi (i386) - tests ran: 10, failed: 1

tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-38.57/onibi__4.4.0-38.57__2016-09-09_17-23-00/results-index.html

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

Title:
  linux: 4.4.0-38.57 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-38.57 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
  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/1620658/+subscriptions

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

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

apport information

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

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

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

Title:
  Dell XPS 13 9333 (Intel Haswell) hangs several times per day

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello
  Please help - it's very annoying. In logs:

  last hang:

  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971812] invalid opcode:  
[#1] SMP 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971851] Modules linked in: 
uas usb_storage hid_logitech_hidpp hid_plantronics hid_logitech_dj 
snd_usb_audio snd_usbmidi_lib rfcomm snd_seq_dummy ax88179_178a usbnet mii 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep drbg ansi_cprng ctr 
ccm pci_stub intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm irqbypass ath3k crct10dif_pclmul uvcvideo crc32_pclmul dell_wmi 
hid_rmi dell_laptop btusb sparse_keymap dcdbas btrtl videobuf2_vmalloc 
videobuf2_memops btbcm aesni_intel dell_smm_hwmon videobuf2_v4l2 btintel 
videobuf2_core v4l2_common videodev aes_x86_64 bluetooth media lrw gf128mul 
glue_helper hid_multitouch ablk_helper cryptd arc4 ath9k ath9k_common joydev 
ath9k_hw input_leds serio_raw snd_hda_codec_hdmi ath mac80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 snd_soc_rl6231 
snd_hda_intel cfg80211 snd_soc_core lpc_ich snd_hda_codec mei_me mei 
snd_compress snd_hda_core ac97_bus snd_pcm_dmaeng
 ine shpchp snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer acpi_als kfifo_buf industrialio snd elan_i2c 
soundcore snd_soc_sst_acpi dw_dmac dw_dmac_core 8250_dw spi_pxa2xx_platform 
i2c_designware_platform i2c_designware_core dell_rbtn intel_smartconnect 
mac_hid binfmt_misc parport_pc ppdev lp parport autofs4 usbhid i915 psmouse 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops 
libahci drm wmi sdhci_acpi sdhci i2c_hid hid video fjes [last unloaded: vboxdrv]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972447] CPU: 3 PID: 2813 
Comm: Xorg Tainted: G   OE   4.4.0-36-generic #55-Ubuntu
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972477] Hardware name: Dell 
Inc. XPS13 9333/0GFTRT, BIOS A08 08/31/2015
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972500] task: 
88003569c4c0 ti: 8802132b task.ti: 8802132b
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972524] RIP: 
0010:[]  [] drm_vblank_count+0x0/0x40 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972570] RSP: 
0018:8802132b3d10  EFLAGS: 00010246
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972588] RAX:  
RBX: 880035a4c800 RCX: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972611] RDX: 0001 
RSI:  RDI: 880035a4c800
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972633] RBP: 8802132b3da0 
R08: 0006 R09: 00a0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972656] R10: 8802132b3de8 
R11: c00ae950 R12: 8802132b3de8
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972678] R13: 880212409000 
R14: 0001 R15: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972702] FS:  
7f33434a3a00() GS:88021f2c() knlGS:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972728] CS:  0010 DS:  
ES:  CR0: 80050033
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972746] CR2: 36c1789e3000 
CR3: 000210964000 CR4: 001406e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972769] Stack:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972776]  c008e118 
81705f6b 7fff82950ca0 7fff82950ca0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972804]  0040 
880035a46400 8802 817070b4
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972832]  7fff82950ca8 
7fff82950ce0  
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972874] Call Trace:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972896]  [] 
? drm_wait_vblank+0xd8/0x5c0 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972920]  [] 
? sock_recvmsg+0x3b/0x50
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972939]  [] 
? ___sys_recvmsg+0x164/0x1f0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972966]  [] 
drm_ioctl+0x152/0x540 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972992]  [] 
? drm_modeset_ctl+0x60/0x60 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973014]  [] 
? enqueue_hrtimer+0x3d/0x90
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973034]  [] 
?

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

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1621939/+attachment/4737818/+files/UdevDb.txt

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

Title:
  Dell XPS 13 9333 (Intel Haswell) hangs several times per day

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello
  Please help - it's very annoying. In logs:

  last hang:

  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971812] invalid opcode:  
[#1] SMP 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971851] Modules linked in: 
uas usb_storage hid_logitech_hidpp hid_plantronics hid_logitech_dj 
snd_usb_audio snd_usbmidi_lib rfcomm snd_seq_dummy ax88179_178a usbnet mii 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep drbg ansi_cprng ctr 
ccm pci_stub intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm irqbypass ath3k crct10dif_pclmul uvcvideo crc32_pclmul dell_wmi 
hid_rmi dell_laptop btusb sparse_keymap dcdbas btrtl videobuf2_vmalloc 
videobuf2_memops btbcm aesni_intel dell_smm_hwmon videobuf2_v4l2 btintel 
videobuf2_core v4l2_common videodev aes_x86_64 bluetooth media lrw gf128mul 
glue_helper hid_multitouch ablk_helper cryptd arc4 ath9k ath9k_common joydev 
ath9k_hw input_leds serio_raw snd_hda_codec_hdmi ath mac80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 snd_soc_rl6231 
snd_hda_intel cfg80211 snd_soc_core lpc_ich snd_hda_codec mei_me mei 
snd_compress snd_hda_core ac97_bus snd_pcm_dmaeng
 ine shpchp snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer acpi_als kfifo_buf industrialio snd elan_i2c 
soundcore snd_soc_sst_acpi dw_dmac dw_dmac_core 8250_dw spi_pxa2xx_platform 
i2c_designware_platform i2c_designware_core dell_rbtn intel_smartconnect 
mac_hid binfmt_misc parport_pc ppdev lp parport autofs4 usbhid i915 psmouse 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops 
libahci drm wmi sdhci_acpi sdhci i2c_hid hid video fjes [last unloaded: vboxdrv]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972447] CPU: 3 PID: 2813 
Comm: Xorg Tainted: G   OE   4.4.0-36-generic #55-Ubuntu
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972477] Hardware name: Dell 
Inc. XPS13 9333/0GFTRT, BIOS A08 08/31/2015
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972500] task: 
88003569c4c0 ti: 8802132b task.ti: 8802132b
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972524] RIP: 
0010:[]  [] drm_vblank_count+0x0/0x40 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972570] RSP: 
0018:8802132b3d10  EFLAGS: 00010246
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972588] RAX:  
RBX: 880035a4c800 RCX: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972611] RDX: 0001 
RSI:  RDI: 880035a4c800
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972633] RBP: 8802132b3da0 
R08: 0006 R09: 00a0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972656] R10: 8802132b3de8 
R11: c00ae950 R12: 8802132b3de8
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972678] R13: 880212409000 
R14: 0001 R15: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972702] FS:  
7f33434a3a00() GS:88021f2c() knlGS:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972728] CS:  0010 DS:  
ES:  CR0: 80050033
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972746] CR2: 36c1789e3000 
CR3: 000210964000 CR4: 001406e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972769] Stack:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972776]  c008e118 
81705f6b 7fff82950ca0 7fff82950ca0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972804]  0040 
880035a46400 8802 817070b4
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972832]  7fff82950ca8 
7fff82950ce0  
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972874] Call Trace:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972896]  [] 
? drm_wait_vblank+0xd8/0x5c0 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972920]  [] 
? sock_recvmsg+0x3b/0x50
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972939]  [] 
? ___sys_recvmsg+0x164/0x1f0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972966]  [] 
drm_ioctl+0x152/0x540 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972992]  [] 
? drm_modeset_ctl+0x60/0x60 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973014]  [] 
? enqueue_hrtimer+0x3d/0x90
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973034]  [] 
? hrtimer_start_range_ns+0x1d6/0x3e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973056]  []

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

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1621939/+attachment/4737815/+files/ProcInterrupts.txt

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

Title:
  Dell XPS 13 9333 (Intel Haswell) hangs several times per day

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello
  Please help - it's very annoying. In logs:

  last hang:

  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971812] invalid opcode:  
[#1] SMP 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971851] Modules linked in: 
uas usb_storage hid_logitech_hidpp hid_plantronics hid_logitech_dj 
snd_usb_audio snd_usbmidi_lib rfcomm snd_seq_dummy ax88179_178a usbnet mii 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep drbg ansi_cprng ctr 
ccm pci_stub intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm irqbypass ath3k crct10dif_pclmul uvcvideo crc32_pclmul dell_wmi 
hid_rmi dell_laptop btusb sparse_keymap dcdbas btrtl videobuf2_vmalloc 
videobuf2_memops btbcm aesni_intel dell_smm_hwmon videobuf2_v4l2 btintel 
videobuf2_core v4l2_common videodev aes_x86_64 bluetooth media lrw gf128mul 
glue_helper hid_multitouch ablk_helper cryptd arc4 ath9k ath9k_common joydev 
ath9k_hw input_leds serio_raw snd_hda_codec_hdmi ath mac80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 snd_soc_rl6231 
snd_hda_intel cfg80211 snd_soc_core lpc_ich snd_hda_codec mei_me mei 
snd_compress snd_hda_core ac97_bus snd_pcm_dmaeng
 ine shpchp snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer acpi_als kfifo_buf industrialio snd elan_i2c 
soundcore snd_soc_sst_acpi dw_dmac dw_dmac_core 8250_dw spi_pxa2xx_platform 
i2c_designware_platform i2c_designware_core dell_rbtn intel_smartconnect 
mac_hid binfmt_misc parport_pc ppdev lp parport autofs4 usbhid i915 psmouse 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops 
libahci drm wmi sdhci_acpi sdhci i2c_hid hid video fjes [last unloaded: vboxdrv]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972447] CPU: 3 PID: 2813 
Comm: Xorg Tainted: G   OE   4.4.0-36-generic #55-Ubuntu
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972477] Hardware name: Dell 
Inc. XPS13 9333/0GFTRT, BIOS A08 08/31/2015
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972500] task: 
88003569c4c0 ti: 8802132b task.ti: 8802132b
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972524] RIP: 
0010:[]  [] drm_vblank_count+0x0/0x40 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972570] RSP: 
0018:8802132b3d10  EFLAGS: 00010246
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972588] RAX:  
RBX: 880035a4c800 RCX: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972611] RDX: 0001 
RSI:  RDI: 880035a4c800
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972633] RBP: 8802132b3da0 
R08: 0006 R09: 00a0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972656] R10: 8802132b3de8 
R11: c00ae950 R12: 8802132b3de8
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972678] R13: 880212409000 
R14: 0001 R15: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972702] FS:  
7f33434a3a00() GS:88021f2c() knlGS:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972728] CS:  0010 DS:  
ES:  CR0: 80050033
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972746] CR2: 36c1789e3000 
CR3: 000210964000 CR4: 001406e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972769] Stack:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972776]  c008e118 
81705f6b 7fff82950ca0 7fff82950ca0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972804]  0040 
880035a46400 8802 817070b4
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972832]  7fff82950ca8 
7fff82950ce0  
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972874] Call Trace:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972896]  [] 
? drm_wait_vblank+0xd8/0x5c0 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972920]  [] 
? sock_recvmsg+0x3b/0x50
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972939]  [] 
? ___sys_recvmsg+0x164/0x1f0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972966]  [] 
drm_ioctl+0x152/0x540 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972992]  [] 
? drm_modeset_ctl+0x60/0x60 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973014]  [] 
? enqueue_hrtimer+0x3d/0x90
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973034]  [] 
? hrtimer_start_range_ns+0x1d6/0x3e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel:

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

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1621939/+attachment/4737814/+files/ProcEnviron.txt

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

Title:
  Dell XPS 13 9333 (Intel Haswell) hangs several times per day

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello
  Please help - it's very annoying. In logs:

  last hang:

  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971812] invalid opcode:  
[#1] SMP 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971851] Modules linked in: 
uas usb_storage hid_logitech_hidpp hid_plantronics hid_logitech_dj 
snd_usb_audio snd_usbmidi_lib rfcomm snd_seq_dummy ax88179_178a usbnet mii 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep drbg ansi_cprng ctr 
ccm pci_stub intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm irqbypass ath3k crct10dif_pclmul uvcvideo crc32_pclmul dell_wmi 
hid_rmi dell_laptop btusb sparse_keymap dcdbas btrtl videobuf2_vmalloc 
videobuf2_memops btbcm aesni_intel dell_smm_hwmon videobuf2_v4l2 btintel 
videobuf2_core v4l2_common videodev aes_x86_64 bluetooth media lrw gf128mul 
glue_helper hid_multitouch ablk_helper cryptd arc4 ath9k ath9k_common joydev 
ath9k_hw input_leds serio_raw snd_hda_codec_hdmi ath mac80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 snd_soc_rl6231 
snd_hda_intel cfg80211 snd_soc_core lpc_ich snd_hda_codec mei_me mei 
snd_compress snd_hda_core ac97_bus snd_pcm_dmaeng
 ine shpchp snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer acpi_als kfifo_buf industrialio snd elan_i2c 
soundcore snd_soc_sst_acpi dw_dmac dw_dmac_core 8250_dw spi_pxa2xx_platform 
i2c_designware_platform i2c_designware_core dell_rbtn intel_smartconnect 
mac_hid binfmt_misc parport_pc ppdev lp parport autofs4 usbhid i915 psmouse 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops 
libahci drm wmi sdhci_acpi sdhci i2c_hid hid video fjes [last unloaded: vboxdrv]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972447] CPU: 3 PID: 2813 
Comm: Xorg Tainted: G   OE   4.4.0-36-generic #55-Ubuntu
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972477] Hardware name: Dell 
Inc. XPS13 9333/0GFTRT, BIOS A08 08/31/2015
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972500] task: 
88003569c4c0 ti: 8802132b task.ti: 8802132b
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972524] RIP: 
0010:[]  [] drm_vblank_count+0x0/0x40 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972570] RSP: 
0018:8802132b3d10  EFLAGS: 00010246
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972588] RAX:  
RBX: 880035a4c800 RCX: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972611] RDX: 0001 
RSI:  RDI: 880035a4c800
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972633] RBP: 8802132b3da0 
R08: 0006 R09: 00a0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972656] R10: 8802132b3de8 
R11: c00ae950 R12: 8802132b3de8
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972678] R13: 880212409000 
R14: 0001 R15: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972702] FS:  
7f33434a3a00() GS:88021f2c() knlGS:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972728] CS:  0010 DS:  
ES:  CR0: 80050033
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972746] CR2: 36c1789e3000 
CR3: 000210964000 CR4: 001406e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972769] Stack:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972776]  c008e118 
81705f6b 7fff82950ca0 7fff82950ca0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972804]  0040 
880035a46400 8802 817070b4
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972832]  7fff82950ca8 
7fff82950ce0  
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972874] Call Trace:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972896]  [] 
? drm_wait_vblank+0xd8/0x5c0 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972920]  [] 
? sock_recvmsg+0x3b/0x50
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972939]  [] 
? ___sys_recvmsg+0x164/0x1f0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972966]  [] 
drm_ioctl+0x152/0x540 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972992]  [] 
? drm_modeset_ctl+0x60/0x60 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973014]  [] 
? enqueue_hrtimer+0x3d/0x90
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973034]  [] 
? hrtimer_start_range_ns+0x1d6/0x3e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973056]  []

[Kernel-packages] [Bug 1621939] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1621939/+attachment/4737810/+files/JournalErrors.txt

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

Title:
  Dell XPS 13 9333 (Intel Haswell) hangs several times per day

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello
  Please help - it's very annoying. In logs:

  last hang:

  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971812] invalid opcode:  
[#1] SMP 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971851] Modules linked in: 
uas usb_storage hid_logitech_hidpp hid_plantronics hid_logitech_dj 
snd_usb_audio snd_usbmidi_lib rfcomm snd_seq_dummy ax88179_178a usbnet mii 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep drbg ansi_cprng ctr 
ccm pci_stub intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm irqbypass ath3k crct10dif_pclmul uvcvideo crc32_pclmul dell_wmi 
hid_rmi dell_laptop btusb sparse_keymap dcdbas btrtl videobuf2_vmalloc 
videobuf2_memops btbcm aesni_intel dell_smm_hwmon videobuf2_v4l2 btintel 
videobuf2_core v4l2_common videodev aes_x86_64 bluetooth media lrw gf128mul 
glue_helper hid_multitouch ablk_helper cryptd arc4 ath9k ath9k_common joydev 
ath9k_hw input_leds serio_raw snd_hda_codec_hdmi ath mac80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 snd_soc_rl6231 
snd_hda_intel cfg80211 snd_soc_core lpc_ich snd_hda_codec mei_me mei 
snd_compress snd_hda_core ac97_bus snd_pcm_dmaeng
 ine shpchp snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer acpi_als kfifo_buf industrialio snd elan_i2c 
soundcore snd_soc_sst_acpi dw_dmac dw_dmac_core 8250_dw spi_pxa2xx_platform 
i2c_designware_platform i2c_designware_core dell_rbtn intel_smartconnect 
mac_hid binfmt_misc parport_pc ppdev lp parport autofs4 usbhid i915 psmouse 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops 
libahci drm wmi sdhci_acpi sdhci i2c_hid hid video fjes [last unloaded: vboxdrv]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972447] CPU: 3 PID: 2813 
Comm: Xorg Tainted: G   OE   4.4.0-36-generic #55-Ubuntu
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972477] Hardware name: Dell 
Inc. XPS13 9333/0GFTRT, BIOS A08 08/31/2015
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972500] task: 
88003569c4c0 ti: 8802132b task.ti: 8802132b
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972524] RIP: 
0010:[]  [] drm_vblank_count+0x0/0x40 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972570] RSP: 
0018:8802132b3d10  EFLAGS: 00010246
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972588] RAX:  
RBX: 880035a4c800 RCX: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972611] RDX: 0001 
RSI:  RDI: 880035a4c800
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972633] RBP: 8802132b3da0 
R08: 0006 R09: 00a0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972656] R10: 8802132b3de8 
R11: c00ae950 R12: 8802132b3de8
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972678] R13: 880212409000 
R14: 0001 R15: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972702] FS:  
7f33434a3a00() GS:88021f2c() knlGS:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972728] CS:  0010 DS:  
ES:  CR0: 80050033
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972746] CR2: 36c1789e3000 
CR3: 000210964000 CR4: 001406e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972769] Stack:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972776]  c008e118 
81705f6b 7fff82950ca0 7fff82950ca0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972804]  0040 
880035a46400 8802 817070b4
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972832]  7fff82950ca8 
7fff82950ce0  
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972874] Call Trace:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972896]  [] 
? drm_wait_vblank+0xd8/0x5c0 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972920]  [] 
? sock_recvmsg+0x3b/0x50
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972939]  [] 
? ___sys_recvmsg+0x164/0x1f0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972966]  [] 
drm_ioctl+0x152/0x540 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972992]  [] 
? drm_modeset_ctl+0x60/0x60 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973014]  [] 
? enqueue_hrtimer+0x3d/0x90
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973034]  [] 
? hrtimer_start_range_ns+0x1d6/0x3e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973056]

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

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1621939/+attachment/4737816/+files/ProcModules.txt

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

Title:
  Dell XPS 13 9333 (Intel Haswell) hangs several times per day

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello
  Please help - it's very annoying. In logs:

  last hang:

  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971812] invalid opcode:  
[#1] SMP 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971851] Modules linked in: 
uas usb_storage hid_logitech_hidpp hid_plantronics hid_logitech_dj 
snd_usb_audio snd_usbmidi_lib rfcomm snd_seq_dummy ax88179_178a usbnet mii 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep drbg ansi_cprng ctr 
ccm pci_stub intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm irqbypass ath3k crct10dif_pclmul uvcvideo crc32_pclmul dell_wmi 
hid_rmi dell_laptop btusb sparse_keymap dcdbas btrtl videobuf2_vmalloc 
videobuf2_memops btbcm aesni_intel dell_smm_hwmon videobuf2_v4l2 btintel 
videobuf2_core v4l2_common videodev aes_x86_64 bluetooth media lrw gf128mul 
glue_helper hid_multitouch ablk_helper cryptd arc4 ath9k ath9k_common joydev 
ath9k_hw input_leds serio_raw snd_hda_codec_hdmi ath mac80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 snd_soc_rl6231 
snd_hda_intel cfg80211 snd_soc_core lpc_ich snd_hda_codec mei_me mei 
snd_compress snd_hda_core ac97_bus snd_pcm_dmaeng
 ine shpchp snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer acpi_als kfifo_buf industrialio snd elan_i2c 
soundcore snd_soc_sst_acpi dw_dmac dw_dmac_core 8250_dw spi_pxa2xx_platform 
i2c_designware_platform i2c_designware_core dell_rbtn intel_smartconnect 
mac_hid binfmt_misc parport_pc ppdev lp parport autofs4 usbhid i915 psmouse 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops 
libahci drm wmi sdhci_acpi sdhci i2c_hid hid video fjes [last unloaded: vboxdrv]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972447] CPU: 3 PID: 2813 
Comm: Xorg Tainted: G   OE   4.4.0-36-generic #55-Ubuntu
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972477] Hardware name: Dell 
Inc. XPS13 9333/0GFTRT, BIOS A08 08/31/2015
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972500] task: 
88003569c4c0 ti: 8802132b task.ti: 8802132b
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972524] RIP: 
0010:[]  [] drm_vblank_count+0x0/0x40 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972570] RSP: 
0018:8802132b3d10  EFLAGS: 00010246
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972588] RAX:  
RBX: 880035a4c800 RCX: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972611] RDX: 0001 
RSI:  RDI: 880035a4c800
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972633] RBP: 8802132b3da0 
R08: 0006 R09: 00a0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972656] R10: 8802132b3de8 
R11: c00ae950 R12: 8802132b3de8
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972678] R13: 880212409000 
R14: 0001 R15: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972702] FS:  
7f33434a3a00() GS:88021f2c() knlGS:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972728] CS:  0010 DS:  
ES:  CR0: 80050033
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972746] CR2: 36c1789e3000 
CR3: 000210964000 CR4: 001406e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972769] Stack:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972776]  c008e118 
81705f6b 7fff82950ca0 7fff82950ca0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972804]  0040 
880035a46400 8802 817070b4
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972832]  7fff82950ca8 
7fff82950ce0  
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972874] Call Trace:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972896]  [] 
? drm_wait_vblank+0xd8/0x5c0 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972920]  [] 
? sock_recvmsg+0x3b/0x50
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972939]  [] 
? ___sys_recvmsg+0x164/0x1f0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972966]  [] 
drm_ioctl+0x152/0x540 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972992]  [] 
? drm_modeset_ctl+0x60/0x60 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973014]  [] 
? enqueue_hrtimer+0x3d/0x90
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973034]  [] 
? hrtimer_start_range_ns+0x1d6/0x3e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973056]  []

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

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1621939/+attachment/4737817/+files/RfKill.txt

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

Title:
  Dell XPS 13 9333 (Intel Haswell) hangs several times per day

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello
  Please help - it's very annoying. In logs:

  last hang:

  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971812] invalid opcode:  
[#1] SMP 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971851] Modules linked in: 
uas usb_storage hid_logitech_hidpp hid_plantronics hid_logitech_dj 
snd_usb_audio snd_usbmidi_lib rfcomm snd_seq_dummy ax88179_178a usbnet mii 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep drbg ansi_cprng ctr 
ccm pci_stub intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm irqbypass ath3k crct10dif_pclmul uvcvideo crc32_pclmul dell_wmi 
hid_rmi dell_laptop btusb sparse_keymap dcdbas btrtl videobuf2_vmalloc 
videobuf2_memops btbcm aesni_intel dell_smm_hwmon videobuf2_v4l2 btintel 
videobuf2_core v4l2_common videodev aes_x86_64 bluetooth media lrw gf128mul 
glue_helper hid_multitouch ablk_helper cryptd arc4 ath9k ath9k_common joydev 
ath9k_hw input_leds serio_raw snd_hda_codec_hdmi ath mac80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 snd_soc_rl6231 
snd_hda_intel cfg80211 snd_soc_core lpc_ich snd_hda_codec mei_me mei 
snd_compress snd_hda_core ac97_bus snd_pcm_dmaeng
 ine shpchp snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer acpi_als kfifo_buf industrialio snd elan_i2c 
soundcore snd_soc_sst_acpi dw_dmac dw_dmac_core 8250_dw spi_pxa2xx_platform 
i2c_designware_platform i2c_designware_core dell_rbtn intel_smartconnect 
mac_hid binfmt_misc parport_pc ppdev lp parport autofs4 usbhid i915 psmouse 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops 
libahci drm wmi sdhci_acpi sdhci i2c_hid hid video fjes [last unloaded: vboxdrv]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972447] CPU: 3 PID: 2813 
Comm: Xorg Tainted: G   OE   4.4.0-36-generic #55-Ubuntu
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972477] Hardware name: Dell 
Inc. XPS13 9333/0GFTRT, BIOS A08 08/31/2015
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972500] task: 
88003569c4c0 ti: 8802132b task.ti: 8802132b
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972524] RIP: 
0010:[]  [] drm_vblank_count+0x0/0x40 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972570] RSP: 
0018:8802132b3d10  EFLAGS: 00010246
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972588] RAX:  
RBX: 880035a4c800 RCX: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972611] RDX: 0001 
RSI:  RDI: 880035a4c800
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972633] RBP: 8802132b3da0 
R08: 0006 R09: 00a0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972656] R10: 8802132b3de8 
R11: c00ae950 R12: 8802132b3de8
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972678] R13: 880212409000 
R14: 0001 R15: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972702] FS:  
7f33434a3a00() GS:88021f2c() knlGS:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972728] CS:  0010 DS:  
ES:  CR0: 80050033
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972746] CR2: 36c1789e3000 
CR3: 000210964000 CR4: 001406e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972769] Stack:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972776]  c008e118 
81705f6b 7fff82950ca0 7fff82950ca0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972804]  0040 
880035a46400 8802 817070b4
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972832]  7fff82950ca8 
7fff82950ce0  
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972874] Call Trace:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972896]  [] 
? drm_wait_vblank+0xd8/0x5c0 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972920]  [] 
? sock_recvmsg+0x3b/0x50
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972939]  [] 
? ___sys_recvmsg+0x164/0x1f0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972966]  [] 
drm_ioctl+0x152/0x540 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972992]  [] 
? drm_modeset_ctl+0x60/0x60 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973014]  [] 
? enqueue_hrtimer+0x3d/0x90
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973034]  [] 
? hrtimer_start_range_ns+0x1d6/0x3e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973056]  []

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

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1621939/+attachment/4737808/+files/CurrentDmesg.txt

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

Title:
  Dell XPS 13 9333 (Intel Haswell) hangs several times per day

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello
  Please help - it's very annoying. In logs:

  last hang:

  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971812] invalid opcode:  
[#1] SMP 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971851] Modules linked in: 
uas usb_storage hid_logitech_hidpp hid_plantronics hid_logitech_dj 
snd_usb_audio snd_usbmidi_lib rfcomm snd_seq_dummy ax88179_178a usbnet mii 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep drbg ansi_cprng ctr 
ccm pci_stub intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm irqbypass ath3k crct10dif_pclmul uvcvideo crc32_pclmul dell_wmi 
hid_rmi dell_laptop btusb sparse_keymap dcdbas btrtl videobuf2_vmalloc 
videobuf2_memops btbcm aesni_intel dell_smm_hwmon videobuf2_v4l2 btintel 
videobuf2_core v4l2_common videodev aes_x86_64 bluetooth media lrw gf128mul 
glue_helper hid_multitouch ablk_helper cryptd arc4 ath9k ath9k_common joydev 
ath9k_hw input_leds serio_raw snd_hda_codec_hdmi ath mac80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 snd_soc_rl6231 
snd_hda_intel cfg80211 snd_soc_core lpc_ich snd_hda_codec mei_me mei 
snd_compress snd_hda_core ac97_bus snd_pcm_dmaeng
 ine shpchp snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer acpi_als kfifo_buf industrialio snd elan_i2c 
soundcore snd_soc_sst_acpi dw_dmac dw_dmac_core 8250_dw spi_pxa2xx_platform 
i2c_designware_platform i2c_designware_core dell_rbtn intel_smartconnect 
mac_hid binfmt_misc parport_pc ppdev lp parport autofs4 usbhid i915 psmouse 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops 
libahci drm wmi sdhci_acpi sdhci i2c_hid hid video fjes [last unloaded: vboxdrv]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972447] CPU: 3 PID: 2813 
Comm: Xorg Tainted: G   OE   4.4.0-36-generic #55-Ubuntu
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972477] Hardware name: Dell 
Inc. XPS13 9333/0GFTRT, BIOS A08 08/31/2015
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972500] task: 
88003569c4c0 ti: 8802132b task.ti: 8802132b
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972524] RIP: 
0010:[]  [] drm_vblank_count+0x0/0x40 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972570] RSP: 
0018:8802132b3d10  EFLAGS: 00010246
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972588] RAX:  
RBX: 880035a4c800 RCX: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972611] RDX: 0001 
RSI:  RDI: 880035a4c800
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972633] RBP: 8802132b3da0 
R08: 0006 R09: 00a0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972656] R10: 8802132b3de8 
R11: c00ae950 R12: 8802132b3de8
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972678] R13: 880212409000 
R14: 0001 R15: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972702] FS:  
7f33434a3a00() GS:88021f2c() knlGS:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972728] CS:  0010 DS:  
ES:  CR0: 80050033
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972746] CR2: 36c1789e3000 
CR3: 000210964000 CR4: 001406e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972769] Stack:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972776]  c008e118 
81705f6b 7fff82950ca0 7fff82950ca0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972804]  0040 
880035a46400 8802 817070b4
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972832]  7fff82950ca8 
7fff82950ce0  
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972874] Call Trace:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972896]  [] 
? drm_wait_vblank+0xd8/0x5c0 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972920]  [] 
? sock_recvmsg+0x3b/0x50
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972939]  [] 
? ___sys_recvmsg+0x164/0x1f0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972966]  [] 
drm_ioctl+0x152/0x540 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972992]  [] 
? drm_modeset_ctl+0x60/0x60 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973014]  [] 
? enqueue_hrtimer+0x3d/0x90
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973034]  [] 
? hrtimer_start_range_ns+0x1d6/0x3e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973056]

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

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1621939/+attachment/4737813/+files/ProcCpuinfo.txt

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

Title:
  Dell XPS 13 9333 (Intel Haswell) hangs several times per day

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello
  Please help - it's very annoying. In logs:

  last hang:

  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971812] invalid opcode:  
[#1] SMP 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971851] Modules linked in: 
uas usb_storage hid_logitech_hidpp hid_plantronics hid_logitech_dj 
snd_usb_audio snd_usbmidi_lib rfcomm snd_seq_dummy ax88179_178a usbnet mii 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep drbg ansi_cprng ctr 
ccm pci_stub intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm irqbypass ath3k crct10dif_pclmul uvcvideo crc32_pclmul dell_wmi 
hid_rmi dell_laptop btusb sparse_keymap dcdbas btrtl videobuf2_vmalloc 
videobuf2_memops btbcm aesni_intel dell_smm_hwmon videobuf2_v4l2 btintel 
videobuf2_core v4l2_common videodev aes_x86_64 bluetooth media lrw gf128mul 
glue_helper hid_multitouch ablk_helper cryptd arc4 ath9k ath9k_common joydev 
ath9k_hw input_leds serio_raw snd_hda_codec_hdmi ath mac80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 snd_soc_rl6231 
snd_hda_intel cfg80211 snd_soc_core lpc_ich snd_hda_codec mei_me mei 
snd_compress snd_hda_core ac97_bus snd_pcm_dmaeng
 ine shpchp snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer acpi_als kfifo_buf industrialio snd elan_i2c 
soundcore snd_soc_sst_acpi dw_dmac dw_dmac_core 8250_dw spi_pxa2xx_platform 
i2c_designware_platform i2c_designware_core dell_rbtn intel_smartconnect 
mac_hid binfmt_misc parport_pc ppdev lp parport autofs4 usbhid i915 psmouse 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops 
libahci drm wmi sdhci_acpi sdhci i2c_hid hid video fjes [last unloaded: vboxdrv]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972447] CPU: 3 PID: 2813 
Comm: Xorg Tainted: G   OE   4.4.0-36-generic #55-Ubuntu
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972477] Hardware name: Dell 
Inc. XPS13 9333/0GFTRT, BIOS A08 08/31/2015
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972500] task: 
88003569c4c0 ti: 8802132b task.ti: 8802132b
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972524] RIP: 
0010:[]  [] drm_vblank_count+0x0/0x40 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972570] RSP: 
0018:8802132b3d10  EFLAGS: 00010246
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972588] RAX:  
RBX: 880035a4c800 RCX: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972611] RDX: 0001 
RSI:  RDI: 880035a4c800
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972633] RBP: 8802132b3da0 
R08: 0006 R09: 00a0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972656] R10: 8802132b3de8 
R11: c00ae950 R12: 8802132b3de8
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972678] R13: 880212409000 
R14: 0001 R15: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972702] FS:  
7f33434a3a00() GS:88021f2c() knlGS:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972728] CS:  0010 DS:  
ES:  CR0: 80050033
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972746] CR2: 36c1789e3000 
CR3: 000210964000 CR4: 001406e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972769] Stack:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972776]  c008e118 
81705f6b 7fff82950ca0 7fff82950ca0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972804]  0040 
880035a46400 8802 817070b4
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972832]  7fff82950ca8 
7fff82950ce0  
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972874] Call Trace:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972896]  [] 
? drm_wait_vblank+0xd8/0x5c0 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972920]  [] 
? sock_recvmsg+0x3b/0x50
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972939]  [] 
? ___sys_recvmsg+0x164/0x1f0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972966]  [] 
drm_ioctl+0x152/0x540 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972992]  [] 
? drm_modeset_ctl+0x60/0x60 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973014]  [] 
? enqueue_hrtimer+0x3d/0x90
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973034]  [] 
? hrtimer_start_range_ns+0x1d6/0x3e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973056]  []

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

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1621939/+attachment/4737811/+files/Lspci.txt

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

Title:
  Dell XPS 13 9333 (Intel Haswell) hangs several times per day

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello
  Please help - it's very annoying. In logs:

  last hang:

  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971812] invalid opcode:  
[#1] SMP 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971851] Modules linked in: 
uas usb_storage hid_logitech_hidpp hid_plantronics hid_logitech_dj 
snd_usb_audio snd_usbmidi_lib rfcomm snd_seq_dummy ax88179_178a usbnet mii 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep drbg ansi_cprng ctr 
ccm pci_stub intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm irqbypass ath3k crct10dif_pclmul uvcvideo crc32_pclmul dell_wmi 
hid_rmi dell_laptop btusb sparse_keymap dcdbas btrtl videobuf2_vmalloc 
videobuf2_memops btbcm aesni_intel dell_smm_hwmon videobuf2_v4l2 btintel 
videobuf2_core v4l2_common videodev aes_x86_64 bluetooth media lrw gf128mul 
glue_helper hid_multitouch ablk_helper cryptd arc4 ath9k ath9k_common joydev 
ath9k_hw input_leds serio_raw snd_hda_codec_hdmi ath mac80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 snd_soc_rl6231 
snd_hda_intel cfg80211 snd_soc_core lpc_ich snd_hda_codec mei_me mei 
snd_compress snd_hda_core ac97_bus snd_pcm_dmaeng
 ine shpchp snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer acpi_als kfifo_buf industrialio snd elan_i2c 
soundcore snd_soc_sst_acpi dw_dmac dw_dmac_core 8250_dw spi_pxa2xx_platform 
i2c_designware_platform i2c_designware_core dell_rbtn intel_smartconnect 
mac_hid binfmt_misc parport_pc ppdev lp parport autofs4 usbhid i915 psmouse 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops 
libahci drm wmi sdhci_acpi sdhci i2c_hid hid video fjes [last unloaded: vboxdrv]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972447] CPU: 3 PID: 2813 
Comm: Xorg Tainted: G   OE   4.4.0-36-generic #55-Ubuntu
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972477] Hardware name: Dell 
Inc. XPS13 9333/0GFTRT, BIOS A08 08/31/2015
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972500] task: 
88003569c4c0 ti: 8802132b task.ti: 8802132b
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972524] RIP: 
0010:[]  [] drm_vblank_count+0x0/0x40 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972570] RSP: 
0018:8802132b3d10  EFLAGS: 00010246
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972588] RAX:  
RBX: 880035a4c800 RCX: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972611] RDX: 0001 
RSI:  RDI: 880035a4c800
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972633] RBP: 8802132b3da0 
R08: 0006 R09: 00a0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972656] R10: 8802132b3de8 
R11: c00ae950 R12: 8802132b3de8
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972678] R13: 880212409000 
R14: 0001 R15: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972702] FS:  
7f33434a3a00() GS:88021f2c() knlGS:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972728] CS:  0010 DS:  
ES:  CR0: 80050033
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972746] CR2: 36c1789e3000 
CR3: 000210964000 CR4: 001406e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972769] Stack:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972776]  c008e118 
81705f6b 7fff82950ca0 7fff82950ca0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972804]  0040 
880035a46400 8802 817070b4
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972832]  7fff82950ca8 
7fff82950ce0  
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972874] Call Trace:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972896]  [] 
? drm_wait_vblank+0xd8/0x5c0 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972920]  [] 
? sock_recvmsg+0x3b/0x50
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972939]  [] 
? ___sys_recvmsg+0x164/0x1f0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972966]  [] 
drm_ioctl+0x152/0x540 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972992]  [] 
? drm_modeset_ctl+0x60/0x60 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973014]  [] 
? enqueue_hrtimer+0x3d/0x90
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973034]  [] 
? hrtimer_start_range_ns+0x1d6/0x3e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973056]  []

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

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1621939/+attachment/4737809/+files/IwConfig.txt

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

Title:
  Dell XPS 13 9333 (Intel Haswell) hangs several times per day

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello
  Please help - it's very annoying. In logs:

  last hang:

  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971812] invalid opcode:  
[#1] SMP 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971851] Modules linked in: 
uas usb_storage hid_logitech_hidpp hid_plantronics hid_logitech_dj 
snd_usb_audio snd_usbmidi_lib rfcomm snd_seq_dummy ax88179_178a usbnet mii 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep drbg ansi_cprng ctr 
ccm pci_stub intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm irqbypass ath3k crct10dif_pclmul uvcvideo crc32_pclmul dell_wmi 
hid_rmi dell_laptop btusb sparse_keymap dcdbas btrtl videobuf2_vmalloc 
videobuf2_memops btbcm aesni_intel dell_smm_hwmon videobuf2_v4l2 btintel 
videobuf2_core v4l2_common videodev aes_x86_64 bluetooth media lrw gf128mul 
glue_helper hid_multitouch ablk_helper cryptd arc4 ath9k ath9k_common joydev 
ath9k_hw input_leds serio_raw snd_hda_codec_hdmi ath mac80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 snd_soc_rl6231 
snd_hda_intel cfg80211 snd_soc_core lpc_ich snd_hda_codec mei_me mei 
snd_compress snd_hda_core ac97_bus snd_pcm_dmaeng
 ine shpchp snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer acpi_als kfifo_buf industrialio snd elan_i2c 
soundcore snd_soc_sst_acpi dw_dmac dw_dmac_core 8250_dw spi_pxa2xx_platform 
i2c_designware_platform i2c_designware_core dell_rbtn intel_smartconnect 
mac_hid binfmt_misc parport_pc ppdev lp parport autofs4 usbhid i915 psmouse 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops 
libahci drm wmi sdhci_acpi sdhci i2c_hid hid video fjes [last unloaded: vboxdrv]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972447] CPU: 3 PID: 2813 
Comm: Xorg Tainted: G   OE   4.4.0-36-generic #55-Ubuntu
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972477] Hardware name: Dell 
Inc. XPS13 9333/0GFTRT, BIOS A08 08/31/2015
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972500] task: 
88003569c4c0 ti: 8802132b task.ti: 8802132b
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972524] RIP: 
0010:[]  [] drm_vblank_count+0x0/0x40 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972570] RSP: 
0018:8802132b3d10  EFLAGS: 00010246
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972588] RAX:  
RBX: 880035a4c800 RCX: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972611] RDX: 0001 
RSI:  RDI: 880035a4c800
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972633] RBP: 8802132b3da0 
R08: 0006 R09: 00a0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972656] R10: 8802132b3de8 
R11: c00ae950 R12: 8802132b3de8
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972678] R13: 880212409000 
R14: 0001 R15: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972702] FS:  
7f33434a3a00() GS:88021f2c() knlGS:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972728] CS:  0010 DS:  
ES:  CR0: 80050033
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972746] CR2: 36c1789e3000 
CR3: 000210964000 CR4: 001406e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972769] Stack:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972776]  c008e118 
81705f6b 7fff82950ca0 7fff82950ca0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972804]  0040 
880035a46400 8802 817070b4
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972832]  7fff82950ca8 
7fff82950ce0  
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972874] Call Trace:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972896]  [] 
? drm_wait_vblank+0xd8/0x5c0 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972920]  [] 
? sock_recvmsg+0x3b/0x50
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972939]  [] 
? ___sys_recvmsg+0x164/0x1f0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972966]  [] 
drm_ioctl+0x152/0x540 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972992]  [] 
? drm_modeset_ctl+0x60/0x60 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973014]  [] 
? enqueue_hrtimer+0x3d/0x90
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973034]  [] 
? hrtimer_start_range_ns+0x1d6/0x3e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973056]  []

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

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1621939/+attachment/4737807/+files/CRDA.txt

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

Title:
  Dell XPS 13 9333 (Intel Haswell) hangs several times per day

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello
  Please help - it's very annoying. In logs:

  last hang:

  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971812] invalid opcode:  
[#1] SMP 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971851] Modules linked in: 
uas usb_storage hid_logitech_hidpp hid_plantronics hid_logitech_dj 
snd_usb_audio snd_usbmidi_lib rfcomm snd_seq_dummy ax88179_178a usbnet mii 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep drbg ansi_cprng ctr 
ccm pci_stub intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm irqbypass ath3k crct10dif_pclmul uvcvideo crc32_pclmul dell_wmi 
hid_rmi dell_laptop btusb sparse_keymap dcdbas btrtl videobuf2_vmalloc 
videobuf2_memops btbcm aesni_intel dell_smm_hwmon videobuf2_v4l2 btintel 
videobuf2_core v4l2_common videodev aes_x86_64 bluetooth media lrw gf128mul 
glue_helper hid_multitouch ablk_helper cryptd arc4 ath9k ath9k_common joydev 
ath9k_hw input_leds serio_raw snd_hda_codec_hdmi ath mac80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 snd_soc_rl6231 
snd_hda_intel cfg80211 snd_soc_core lpc_ich snd_hda_codec mei_me mei 
snd_compress snd_hda_core ac97_bus snd_pcm_dmaeng
 ine shpchp snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer acpi_als kfifo_buf industrialio snd elan_i2c 
soundcore snd_soc_sst_acpi dw_dmac dw_dmac_core 8250_dw spi_pxa2xx_platform 
i2c_designware_platform i2c_designware_core dell_rbtn intel_smartconnect 
mac_hid binfmt_misc parport_pc ppdev lp parport autofs4 usbhid i915 psmouse 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops 
libahci drm wmi sdhci_acpi sdhci i2c_hid hid video fjes [last unloaded: vboxdrv]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972447] CPU: 3 PID: 2813 
Comm: Xorg Tainted: G   OE   4.4.0-36-generic #55-Ubuntu
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972477] Hardware name: Dell 
Inc. XPS13 9333/0GFTRT, BIOS A08 08/31/2015
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972500] task: 
88003569c4c0 ti: 8802132b task.ti: 8802132b
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972524] RIP: 
0010:[]  [] drm_vblank_count+0x0/0x40 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972570] RSP: 
0018:8802132b3d10  EFLAGS: 00010246
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972588] RAX:  
RBX: 880035a4c800 RCX: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972611] RDX: 0001 
RSI:  RDI: 880035a4c800
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972633] RBP: 8802132b3da0 
R08: 0006 R09: 00a0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972656] R10: 8802132b3de8 
R11: c00ae950 R12: 8802132b3de8
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972678] R13: 880212409000 
R14: 0001 R15: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972702] FS:  
7f33434a3a00() GS:88021f2c() knlGS:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972728] CS:  0010 DS:  
ES:  CR0: 80050033
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972746] CR2: 36c1789e3000 
CR3: 000210964000 CR4: 001406e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972769] Stack:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972776]  c008e118 
81705f6b 7fff82950ca0 7fff82950ca0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972804]  0040 
880035a46400 8802 817070b4
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972832]  7fff82950ca8 
7fff82950ce0  
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972874] Call Trace:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972896]  [] 
? drm_wait_vblank+0xd8/0x5c0 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972920]  [] 
? sock_recvmsg+0x3b/0x50
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972939]  [] 
? ___sys_recvmsg+0x164/0x1f0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972966]  [] 
drm_ioctl+0x152/0x540 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972992]  [] 
? drm_modeset_ctl+0x60/0x60 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973014]  [] 
? enqueue_hrtimer+0x3d/0x90
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973034]  [] 
? hrtimer_start_range_ns+0x1d6/0x3e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973056]  []

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

apport information

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

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

Title:
  Dell XPS 13 9333 (Intel Haswell) hangs several times per day

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello
  Please help - it's very annoying. In logs:

  last hang:

  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971812] invalid opcode:  
[#1] SMP 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971851] Modules linked in: 
uas usb_storage hid_logitech_hidpp hid_plantronics hid_logitech_dj 
snd_usb_audio snd_usbmidi_lib rfcomm snd_seq_dummy ax88179_178a usbnet mii 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep drbg ansi_cprng ctr 
ccm pci_stub intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm irqbypass ath3k crct10dif_pclmul uvcvideo crc32_pclmul dell_wmi 
hid_rmi dell_laptop btusb sparse_keymap dcdbas btrtl videobuf2_vmalloc 
videobuf2_memops btbcm aesni_intel dell_smm_hwmon videobuf2_v4l2 btintel 
videobuf2_core v4l2_common videodev aes_x86_64 bluetooth media lrw gf128mul 
glue_helper hid_multitouch ablk_helper cryptd arc4 ath9k ath9k_common joydev 
ath9k_hw input_leds serio_raw snd_hda_codec_hdmi ath mac80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 snd_soc_rl6231 
snd_hda_intel cfg80211 snd_soc_core lpc_ich snd_hda_codec mei_me mei 
snd_compress snd_hda_core ac97_bus snd_pcm_dmaeng
 ine shpchp snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer acpi_als kfifo_buf industrialio snd elan_i2c 
soundcore snd_soc_sst_acpi dw_dmac dw_dmac_core 8250_dw spi_pxa2xx_platform 
i2c_designware_platform i2c_designware_core dell_rbtn intel_smartconnect 
mac_hid binfmt_misc parport_pc ppdev lp parport autofs4 usbhid i915 psmouse 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops 
libahci drm wmi sdhci_acpi sdhci i2c_hid hid video fjes [last unloaded: vboxdrv]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972447] CPU: 3 PID: 2813 
Comm: Xorg Tainted: G   OE   4.4.0-36-generic #55-Ubuntu
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972477] Hardware name: Dell 
Inc. XPS13 9333/0GFTRT, BIOS A08 08/31/2015
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972500] task: 
88003569c4c0 ti: 8802132b task.ti: 8802132b
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972524] RIP: 
0010:[]  [] drm_vblank_count+0x0/0x40 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972570] RSP: 
0018:8802132b3d10  EFLAGS: 00010246
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972588] RAX:  
RBX: 880035a4c800 RCX: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972611] RDX: 0001 
RSI:  RDI: 880035a4c800
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972633] RBP: 8802132b3da0 
R08: 0006 R09: 00a0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972656] R10: 8802132b3de8 
R11: c00ae950 R12: 8802132b3de8
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972678] R13: 880212409000 
R14: 0001 R15: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972702] FS:  
7f33434a3a00() GS:88021f2c() knlGS:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972728] CS:  0010 DS:  
ES:  CR0: 80050033
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972746] CR2: 36c1789e3000 
CR3: 000210964000 CR4: 001406e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972769] Stack:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972776]  c008e118 
81705f6b 7fff82950ca0 7fff82950ca0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972804]  0040 
880035a46400 8802 817070b4
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972832]  7fff82950ca8 
7fff82950ce0  
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972874] Call Trace:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972896]  [] 
? drm_wait_vblank+0xd8/0x5c0 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972920]  [] 
? sock_recvmsg+0x3b/0x50
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972939]  [] 
? ___sys_recvmsg+0x164/0x1f0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972966]  [] 
drm_ioctl+0x152/0x540 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972992]  [] 
? drm_modeset_ctl+0x60/0x60 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973014]  [] 
? enqueue_hrtimer+0x3d/0x90
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973034]  [] 
? hrtimer_start_range_ns+0x1d6/0x3e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973056]  []

[Kernel-packages] [Bug 1621939] Re: Dell XPS 13 9333 (Intel Haswell) hangs several times per day

apport information

** Tags added: apport-collected xenial

** Description changed:

  Hello
  Please help - it's very annoying. In logs:
  
  last hang:
  
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971812] invalid opcode:  
[#1] SMP 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971851] Modules linked in: 
uas usb_storage hid_logitech_hidpp hid_plantronics hid_logitech_dj 
snd_usb_audio snd_usbmidi_lib rfcomm snd_seq_dummy ax88179_178a usbnet mii 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep drbg ansi_cprng ctr 
ccm pci_stub intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm irqbypass ath3k crct10dif_pclmul uvcvideo crc32_pclmul dell_wmi 
hid_rmi dell_laptop btusb sparse_keymap dcdbas btrtl videobuf2_vmalloc 
videobuf2_memops btbcm aesni_intel dell_smm_hwmon videobuf2_v4l2 btintel 
videobuf2_core v4l2_common videodev aes_x86_64 bluetooth media lrw gf128mul 
glue_helper hid_multitouch ablk_helper cryptd arc4 ath9k ath9k_common joydev 
ath9k_hw input_leds serio_raw snd_hda_codec_hdmi ath mac80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 snd_soc_rl6231 
snd_hda_intel cfg80211 snd_soc_core lpc_ich snd_hda_codec mei_me mei 
snd_compress snd_hda_core ac97_bus snd_pcm_dmaeng
 ine shpchp snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer acpi_als kfifo_buf industrialio snd elan_i2c 
soundcore snd_soc_sst_acpi dw_dmac dw_dmac_core 8250_dw spi_pxa2xx_platform 
i2c_designware_platform i2c_designware_core dell_rbtn intel_smartconnect 
mac_hid binfmt_misc parport_pc ppdev lp parport autofs4 usbhid i915 psmouse 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops 
libahci drm wmi sdhci_acpi sdhci i2c_hid hid video fjes [last unloaded: vboxdrv]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972447] CPU: 3 PID: 2813 
Comm: Xorg Tainted: G   OE   4.4.0-36-generic #55-Ubuntu
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972477] Hardware name: Dell 
Inc. XPS13 9333/0GFTRT, BIOS A08 08/31/2015
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972500] task: 
88003569c4c0 ti: 8802132b task.ti: 8802132b
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972524] RIP: 
0010:[]  [] drm_vblank_count+0x0/0x40 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972570] RSP: 
0018:8802132b3d10  EFLAGS: 00010246
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972588] RAX:  
RBX: 880035a4c800 RCX: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972611] RDX: 0001 
RSI:  RDI: 880035a4c800
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972633] RBP: 8802132b3da0 
R08: 0006 R09: 00a0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972656] R10: 8802132b3de8 
R11: c00ae950 R12: 8802132b3de8
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972678] R13: 880212409000 
R14: 0001 R15: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972702] FS:  
7f33434a3a00() GS:88021f2c() knlGS:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972728] CS:  0010 DS:  
ES:  CR0: 80050033
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972746] CR2: 36c1789e3000 
CR3: 000210964000 CR4: 001406e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972769] Stack:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972776]  c008e118 
81705f6b 7fff82950ca0 7fff82950ca0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972804]  0040 
880035a46400 8802 817070b4
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972832]  7fff82950ca8 
7fff82950ce0  
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972874] Call Trace:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972896]  [] 
? drm_wait_vblank+0xd8/0x5c0 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972920]  [] 
? sock_recvmsg+0x3b/0x50
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972939]  [] 
? ___sys_recvmsg+0x164/0x1f0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972966]  [] 
drm_ioctl+0x152/0x540 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972992]  [] 
? drm_modeset_ctl+0x60/0x60 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973014]  [] 
? enqueue_hrtimer+0x3d/0x90
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973034]  [] 
? hrtimer_start_range_ns+0x1d6/0x3e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973056]  [] 
do_vfs_ioctl+0x29f/0x490
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973075]  [] 
? __sys_recvmsg+0x80/0x90
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973094]  [] 
SyS_ioctl+0x79/0x90
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973112]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973133]

[Kernel-packages] [Bug 1579917] Re: Skylake processor never reaches low power states on X1 Carbon gen 4 with NVMe drive

2016-09-09 Thread Dave Chiluk

Closing as invalid, as the root cause was clearly the IMEI firmware in
my case, and has since been verified.

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

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

Title:
Skylake processor never reaches low power states on X1 Carbon gen 4
with NVMe drive

Status in linux package in Ubuntu:
Invalid

Bug description:
Reproducer
1. Find a skylake machine. - in my case Lenovo x1 carbon gen 4. In my case
with an NVME drive.
2. run powertop, and switch to idle stats tab
3. do nothing. *(as in let the machine idle till the cores regularly reach
low power states.
4. Watch the watts fly. On my machine the package never gets into any power
state other than PC2.

Expected results: PC3-PC10 power states should all show some usage.

I also tried the mainline build of 4.6-rc7 with no benefits.

Public conversations about the issue
https://mjg59.dreamwidth.org/42156.html
https://mjg59.dreamwidth.org/41713.html

As far as I can tell having the nvme drive is part of the overall
problem here. Please keep this case to skylake + nvme. Skylake +
sata appears to have a number of fixes in the 4.6 and newer kernels
that enable some of the higher sleep states, but I have not tested
with a sata drive. Those fixes as of testing 4.6-rc7 do not resolve
this issue with users who have nvme drives.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-22-generic 4.4.0-22.39
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: chiluk 3139 F pulseaudio
CurrentDesktop: Unity
Date: Mon May 9 15:55:03 2016
HibernationDevice: RESUME=UUID=4f4ea88e-642e-4be5-bdf0-bbc7f47f5628
InstallationDate: Installed on 2016-04-25 (14 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f2:b531 Chicony Electronics Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20FBCTO1WW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed
root=UUID=249f91bb-7789-41cc-9cc0-8ba25d7f55bb ro quiet splash pcie_aspm=force
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-22-generic N/A
linux-backports-modules-4.4.0-22-generic N/A
linux-firmware1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/15/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: N1FET37W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FBCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrN1FET37W(1.11):bd03/15/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20FBCTO1WW
dmi.product.version: ThinkPad X1 Carbon 4th
dmi.sys.vendor: LENOVO

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

[Kernel-packages] [Bug 1315221] Re: 8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses connection/becomes unusable on Intel 7260

2016-09-09 Thread Ethan Blanton

Yes, I am running A06.  However, a) the A08 update does not indicate
anything but a touchpad fix for Windows 10 32-bit (I realize this can be
unreliable) and b) since the A06 update I have been unable to
successfully boot a FreeDOS image to update my BIOS.

If you have any information on how to successfully update to A08 without
an installed Windows OS, I'd be happy to hear 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/1315221

Title:
  8086:08b1 (rev 6b) [Dell XPS 13 9333] iwlwifi regularly loses
  connection/becomes unusable on Intel 7260

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My Intel 7260 network card regularly shows very poor performance
  and/or loses its connection entirely. On several occasions I have been
  unable to reestablish an association with the AP without rebooting.
  This occurs even if the laptop is within a few feet of the AP. I did
  not have this problem on 12.04 with a quantal backport kernel.

  Network controller [0280]: Intel Corporation Wireless 7260 [8086:08b1] (rev 
6b)
  Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:c470]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Thu May  1 22:59:32 2014
  HibernationDevice: RESUME=/dev/mapper/cswap0
  InstallationDate: Installed on 2014-04-25 (6 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. XPS13 9333
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elb5375 F pulseaudio
   /dev/snd/controlC0:  elb5375 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=/dev/mapper/cswap0
  InstallationDate: Installed on 2014-04-25 (94 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. XPS13 9333
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic 
root=/dev/mapper/root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty
  Uname: Linux 3.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/19/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0GFTRT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: XPS13 9333
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1620811] Re: Focaltech touchpad detected as mouse on Asus K501UW laptop

David DIDIER, 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/1620811

Title:
  Focaltech touchpad detected as mouse on Asus K501UW laptop

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Following the bug reporting documentation here:
  
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.

  The Focaltech touchpad on Asus K501UW laptop is detected as a mouse,
  so I can't access touchpad features such as two-finger scrolling or
  use two-finger tap as right mouse button. The touchpad is recognized
  in xinput-list as "FTE1001:00 0B05:0101".

  The bug appears in Ubuntu Mate 16.04.1 x64 and Linux Mint 18 Cinnamon
  x64, both with kernel 4.4.0-31. I've also tried Linux Mint 17.3 x64
  with kernel 3.19, and there the touchpad does not work at all (does
  not function even as a mouse).

  The bug is resemblant of #1372609.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified: 
boot/vmlinuz-4.4.0-31-generic]
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  e2 3605 F pulseaudio
  CurrentDesktop: MATE
  Date: Tue Sep  6 15:13:50 2016
  HibernationDevice: RESUME=UUID=8407ca60-029d-4be6-ab12-a2f1aee1d843
  InstallationDate: Installed on 2016-09-05 (1 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  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 0bda:57ed Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=826cac6a-2d18-4d8d-a9ee-85299d3cac91 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UW.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UW
  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.:bvrK501UW.203:bd03/30/2016:svnASUSTeKCOMPUTERINC.:pnK501UW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K501UW
  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/1620811/+subscriptions

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

[Kernel-packages] [Bug 1620811] Re: Focaltech touchpad detected as mouse on Asus K501UW laptop

Egor, thank you for reporting this and helping make Ubuntu better.

In order to allow additional upstream developers to examine the issue, at your
earliest convenience, could you please test the latest upstream kernel
available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please
keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was
released upstream.
4) Install instructions are available at
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't
boot into the OS) please make a comment in your report about this, and continue
to test the next most recent kernel version until you can test to the issue.
Once you've tested the upstream kernel, please comment on which kernel version
specifically you tested. If this issue is fixed in the mainline kernel, please
add the following tags by clicking on the yellow circle with a black pencil
icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest upstream kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

** Tags removed: focaltech touchpad
** Tags added: bios-outdated-300

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

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

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

Title:
Focaltech touchpad detected as mouse on Asus K501UW laptop

Status in linux package in Ubuntu:
Incomplete

Bug description:
Following the bug reporting documentation here:

https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all.

The Focaltech touchpad on Asus K501UW laptop is detected as a mouse,
so I can't access touchpad features such as two-finger scrolling or
use two-finger tap as right mouse button. The touchpad is recognized
in xinput-list as "FTE1001:00 0B05:0101".

The bug appears in Ubuntu Mate 16.04.1 x64 and Linux Mint 18 Cinnamon
x64, both with kernel 4.4.0-31. I've also tried Linux Mint 17.3 x64
with kernel 3.19, and there the touchpad does not work at all (does
not function even as a mouse).

The bug is resemblant of #1372609.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic 4.4.0-31.50 [modified:
boot/vmlinuz-4.4.0-31-generic]
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: e2 3605 F pulseaudio
CurrentDesktop: MATE
Date: Tue Sep 6 15:13:50 2016
HibernationDevice: RESUME=UUID=8407ca60-029d-4be6-ab12-a2f1aee1d843
InstallationDate: Installed on 2016-09-05 (1 days ago)
InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64
(20160719)
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 0bda:57ed Realtek Semiconductor Corp.
Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. K501UW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed
root=UUID=826cac6a-2d18-4d8d-a9ee-85299d3cac91 ro quiet splash
RelatedPackageVersions:
linux-restricted-modules-4.4.0-31-generic N/A
linux-backports-modules-4.4.0-31-generic N/A
linux-firmware1.157.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/30/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K501UW.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name:

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

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

apport-collect 1621939

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

Title:
  Dell XPS 13 9333 (Intel Haswell) hangs several times per day

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello
  Please help - it's very annoying. In logs:

  last hang:

  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971812] invalid opcode:  
[#1] SMP 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971851] Modules linked in: 
uas usb_storage hid_logitech_hidpp hid_plantronics hid_logitech_dj 
snd_usb_audio snd_usbmidi_lib rfcomm snd_seq_dummy ax88179_178a usbnet mii 
vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep drbg ansi_cprng ctr 
ccm pci_stub intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp 
kvm_intel kvm irqbypass ath3k crct10dif_pclmul uvcvideo crc32_pclmul dell_wmi 
hid_rmi dell_laptop btusb sparse_keymap dcdbas btrtl videobuf2_vmalloc 
videobuf2_memops btbcm aesni_intel dell_smm_hwmon videobuf2_v4l2 btintel 
videobuf2_core v4l2_common videodev aes_x86_64 bluetooth media lrw gf128mul 
glue_helper hid_multitouch ablk_helper cryptd arc4 ath9k ath9k_common joydev 
ath9k_hw input_leds serio_raw snd_hda_codec_hdmi ath mac80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_soc_rt5640 snd_soc_rl6231 
snd_hda_intel cfg80211 snd_soc_core lpc_ich snd_hda_codec mei_me mei 
snd_compress snd_hda_core ac97_bus snd_pcm_dmaeng
 ine shpchp snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi 
snd_seq snd_seq_device snd_timer acpi_als kfifo_buf industrialio snd elan_i2c 
soundcore snd_soc_sst_acpi dw_dmac dw_dmac_core 8250_dw spi_pxa2xx_platform 
i2c_designware_platform i2c_designware_core dell_rbtn intel_smartconnect 
mac_hid binfmt_misc parport_pc ppdev lp parport autofs4 usbhid i915 psmouse 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops 
libahci drm wmi sdhci_acpi sdhci i2c_hid hid video fjes [last unloaded: vboxdrv]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972447] CPU: 3 PID: 2813 
Comm: Xorg Tainted: G   OE   4.4.0-36-generic #55-Ubuntu
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972477] Hardware name: Dell 
Inc. XPS13 9333/0GFTRT, BIOS A08 08/31/2015
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972500] task: 
88003569c4c0 ti: 8802132b task.ti: 8802132b
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972524] RIP: 
0010:[]  [] drm_vblank_count+0x0/0x40 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972570] RSP: 
0018:8802132b3d10  EFLAGS: 00010246
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972588] RAX:  
RBX: 880035a4c800 RCX: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972611] RDX: 0001 
RSI:  RDI: 880035a4c800
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972633] RBP: 8802132b3da0 
R08: 0006 R09: 00a0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972656] R10: 8802132b3de8 
R11: c00ae950 R12: 8802132b3de8
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972678] R13: 880212409000 
R14: 0001 R15: 
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972702] FS:  
7f33434a3a00() GS:88021f2c() knlGS:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972728] CS:  0010 DS:  
ES:  CR0: 80050033
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972746] CR2: 36c1789e3000 
CR3: 000210964000 CR4: 001406e0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972769] Stack:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972776]  c008e118 
81705f6b 7fff82950ca0 7fff82950ca0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972804]  0040 
880035a46400 8802 817070b4
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972832]  7fff82950ca8 
7fff82950ce0  
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972874] Call Trace:
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972896]  [] 
? drm_wait_vblank+0xd8/0x5c0 [drm]
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972920]  [] 
? sock_recvmsg+0x3b/0x50
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972939]  [] 
? ___sys_recvmsg+0x164/0x1f0
  Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972966]  []

[Kernel-packages] [Bug 1608499] Re: Parallel depmod failure with dkms autoinstall

2016-09-09 Thread Timo Aaltonen

Hello Julien, or anyone else affected,

Accepted dkms into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-2ubuntu11.2 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: dkms (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed

** Changed in: dkms (Ubuntu Trusty)
   Status: New => Fix Committed

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

Title:
  Parallel depmod failure with dkms autoinstall

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Committed
Status in dkms source package in Xenial:
  Fix Committed

Bug description:
  Description of problem
  --

  "dkms autoinstall" installs DKMS modules in parallel, potentially executing
  several depmod instances in parallel.

  The resulting race condition causes depmod to fail and dkms install as
  well.

  This problem is critical because some DKMS modules can be left in "built"
  state after a kernel upgrade, thus the kernel modules will not be re-installed
  in /lib/modules/.

  Ubuntu release
  --
  # lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  DKMS package version
  

  # apt-cache policy dkms
  dkms:
Installed: 2.2.0.3-2ubuntu11
Candidate: 2.2.0.3-2ubuntu11
Version table:
   *** 2.2.0.3-2ubuntu11 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  Steps to reproduce
  --

  Add 2 simple DKMS modules, mod1 and mod2 (test case in attachment) with
  "dkms add", then run "dkms autoinstall".

  # dkms add mod1 ; dkms add mod2

  Creating symlink /var/lib/dkms/mod1/1.0/source ->
   /usr/src/mod1-1.0

  DKMS: add completed.

  Creating symlink /var/lib/dkms/mod2/1.0/source ->
   /usr/src/mod2-1.0

  DKMS: add completed.

  # dkms autoinstall

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area...
  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area
  .make KERNELRELEASE=4.4.0-28-generic -C /lib/modules/4.4.0-28-generic/build 
SUBDIRS=/var/lib/dkms/mod2/1.0/build S=/var/lib/dkms/mod2/1.0/build modules...
  make KERNELRELEASE=4.4.0-28-generic -C /lib/modules/4.4.0-28-generic/build 
SUBDIRS=/var/lib/dkms/mod1/1.0/build S=/var/lib/dkms/mod1/1.0/build modules.

  cleaning build area...cleaning build area.

  
  DKMS: build completed.

  DKMS: build completed.

  mod2.ko:
  Running module version sanity check.

  mod1.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.4.0-28-generic/updates/dkms/
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.4.0-28-generic/updates/dkms/

  
  depmod...depmod...(bad exit status: 1)

   Uninstall Beginning 
  Module:  mod2
  Version: 1.0
  Kernel:  4.4.0-28-generic (x86_64)
  -

  
  DKMS: install completed.

  Status: Before uninstall, this module version was ACTIVE on this
  kernel.

  mod2.ko:
   - Uninstallation
 - Deleting from: /lib/modules/4.4.0-28-generic/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.

  depmod

  DKMS: uninstall completed.
  Error! Problems with depmod detected.  Automatically uninstalling this module.
  DKMS: Install Failed (depmod problems).  Module rolled back to built state.

  root@ubuntu1604:~/dkms-depmod# dkms status
  mod1, 1.0, 4.4.0-28-generic, x86_64: installed
  mod2, 1.0, 4.4.0-28-generic, x86_64: built

  => mod2 should be in "installed" state as well.

  # modinfo mod1

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

2016-09-09 Thread Timo Aaltonen

Hello Julien, or anyone else affected,

Accepted dkms into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-1.1ubuntu5.14.04.8 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  Parallel depmod failure with dkms autoinstall

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  Fix Committed
Status in dkms source package in Xenial:
  Fix Committed

Bug description:
  Description of problem
  --

  "dkms autoinstall" installs DKMS modules in parallel, potentially executing
  several depmod instances in parallel.

  The resulting race condition causes depmod to fail and dkms install as
  well.

  This problem is critical because some DKMS modules can be left in "built"
  state after a kernel upgrade, thus the kernel modules will not be re-installed
  in /lib/modules/.

  Ubuntu release
  --
  # lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  DKMS package version
  

  # apt-cache policy dkms
  dkms:
Installed: 2.2.0.3-2ubuntu11
Candidate: 2.2.0.3-2ubuntu11
Version table:
   *** 2.2.0.3-2ubuntu11 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  Steps to reproduce
  --

  Add 2 simple DKMS modules, mod1 and mod2 (test case in attachment) with
  "dkms add", then run "dkms autoinstall".

  # dkms add mod1 ; dkms add mod2

  Creating symlink /var/lib/dkms/mod1/1.0/source ->
   /usr/src/mod1-1.0

  DKMS: add completed.

  Creating symlink /var/lib/dkms/mod2/1.0/source ->
   /usr/src/mod2-1.0

  DKMS: add completed.

  # dkms autoinstall

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area...
  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area
  .make KERNELRELEASE=4.4.0-28-generic -C /lib/modules/4.4.0-28-generic/build 
SUBDIRS=/var/lib/dkms/mod2/1.0/build S=/var/lib/dkms/mod2/1.0/build modules...
  make KERNELRELEASE=4.4.0-28-generic -C /lib/modules/4.4.0-28-generic/build 
SUBDIRS=/var/lib/dkms/mod1/1.0/build S=/var/lib/dkms/mod1/1.0/build modules.

  cleaning build area...cleaning build area.

  
  DKMS: build completed.

  DKMS: build completed.

  mod2.ko:
  Running module version sanity check.

  mod1.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.4.0-28-generic/updates/dkms/
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.4.0-28-generic/updates/dkms/

  
  depmod...depmod...(bad exit status: 1)

   Uninstall Beginning 
  Module:  mod2
  Version: 1.0
  Kernel:  4.4.0-28-generic (x86_64)
  -

  
  DKMS: install completed.

  Status: Before uninstall, this module version was ACTIVE on this
  kernel.

  mod2.ko:
   - Uninstallation
 - Deleting from: /lib/modules/4.4.0-28-generic/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.

  depmod

  DKMS: uninstall completed.
  Error! Problems with depmod detected.  Automatically uninstalling this module.
  DKMS: Install Failed (depmod problems).  Module rolled back to built state.

  root@ubuntu1604:~/dkms-depmod# dkms status
  mod1, 1.0, 4.4.0-28-generic, x86_64: installed
  mod2, 1.0, 4.4.0-28-generic, x86_64: built

  => mod2 should be in "installed" state as well.

  # modinfo mod1
  filename:   /lib/modules/4.4.0-28-generic/updates/dkms/mod1.ko
  author: 6WIND
  license:GPL
  srcversion: 8D30BAE7A8F4D38F20AEB57
  depends:

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

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

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [ 2907.698901] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
  [ 2907.698945] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [ 2907.698976] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-9136-generic 4.4.0-9136.55
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2919 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2919 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Sep  9 13:57:53 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (411 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.4.0-9136-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-9136-generic N/A
   linux-backports-modules-4.4.0-9136-generic  N/A
   linux-firmware  1.160
  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/1621937/+subscriptions

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

[Kernel-packages] [Bug 1620762] Re: Support AverMedia DVD EZMaker 7 USB video capture dongle

2016-09-09 Thread Eldar Khayrullin

I sent this question only here

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

Title:
  Support AverMedia DVD EZMaker 7 USB video capture dongle

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Linux doesn't support this capture.
  Link to patch 
https://www.linuxtv.org/wiki/index.php/AVerMedia_DVD_EZMaker_7_(C039). 
  I tested it on Ubuntu 16.04 - OK.
  It will be great if this patch is built-in to kernel.

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

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

[Kernel-packages] [Bug 1621699] Re: Upgrade to 16.04.1 LTS incorrect disk enumeration

2016-09-09 Thread Brian Murray

You could used "ubuntu-bug" with the "--save" switch and then manually
upload the information requested to the 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/1621699

Title:
  Upgrade to 16.04.1 LTS incorrect disk enumeration

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My system had this disk configuration running 14.04 without issue:
  1 SATA SSD ext4 on internal 6Gb SATA port was /dev/sda with 14.04 OS 
installed.
  3 SATA disks (zfs raidz) on internal 3Gb SATA ports was /dev/sd[bcd]
  8 SATA disks ext4 on LSI Megaraid 9240-8i in IT mode was /dev/sd[efghijkl]

  Upgrade to 16.04.1 LTS now looks like this:
  1 SATA SSD ext4 on internal 6Gb SATA port is now /dev/sdi with 16.04.1 
installed.
  3 SATA disks (zfs raidz) on internal 3Gb SATA ports is now /dev/sd[jkl]
  8 SATA disks ext4 on LSI Megaraid 9240-8i in IT mode are /dev/sd[abcdefgh]

  The sytem boots, but any utils e.g. smartd, hdparm etc. referencing
  /dev/sda are now fubared.

  Booting a 12.04 LiveCD enumerates the disks correctly.
  Booting a 16.04 Lice CD enumarates the disks incorrectly as described above.  

  I'm pointing the blame for this at mpt3sas.ko (kernel module loaded
  for the LSI hba) which was previously mpt2sas.ko

  This bug is completely repeatable on every boot.

  See attached:

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

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

[Kernel-packages] [Bug 1621937] [NEW] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] ERROR CPU pipe A FIFO underrun

2016-09-09 Thread Cristian Aravena Romero

Public bug reported:

[ 2907.698901] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
[ 2907.698945] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
[ 2907.698976] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: linux-image-4.4.0-9136-generic 4.4.0-9136.55
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   caravena   2919 F...m pulseaudio
 /dev/snd/controlC0:  caravena   2919 F pulseaudio
CurrentDesktop: GNOME
Date: Fri Sep  9 13:57:53 2016
HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
InstallationDate: Installed on 2015-07-26 (411 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.4.0-9136-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-9136-generic N/A
 linux-backports-modules-4.4.0-9136-generic  N/A
 linux-firmware  1.160
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.

** Affects: 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 linux in Ubuntu.
https://bugs.launchpad.net/bugs/1621937

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

Status in linux package in Ubuntu:
  New

Bug description:
  [ 2907.698901] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
  [ 2907.698945] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [ 2907.698976] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: linux-image-4.4.0-9136-generic 4.4.0-9136.55
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  Uname: Linux 4.4.0-9136-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   2919 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2919 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Sep  9 13:57:53 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (411 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.4.0-9136-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-9136-generic N/A
   linux-backports-modules-4.4.0-9136-generic  N/A
   linux-firmware  1.160
  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:

[Kernel-packages] [Bug 1621939] [NEW] Dell XPS 13 9333 (Intel Haswell) hangs several times per day

Public bug reported:

Hello
Please help - it's very annoying. In logs:

last hang:

Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971812] invalid opcode:  
[#1] SMP 
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.971851] Modules linked in: uas 
usb_storage hid_logitech_hidpp hid_plantronics hid_logitech_dj snd_usb_audio 
snd_usbmidi_lib rfcomm snd_seq_dummy ax88179_178a usbnet mii vboxpci(OE) 
vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep drbg ansi_cprng ctr ccm pci_stub 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
irqbypass ath3k crct10dif_pclmul uvcvideo crc32_pclmul dell_wmi hid_rmi 
dell_laptop btusb sparse_keymap dcdbas btrtl videobuf2_vmalloc videobuf2_memops 
btbcm aesni_intel dell_smm_hwmon videobuf2_v4l2 btintel videobuf2_core 
v4l2_common videodev aes_x86_64 bluetooth media lrw gf128mul glue_helper 
hid_multitouch ablk_helper cryptd arc4 ath9k ath9k_common joydev ath9k_hw 
input_leds serio_raw snd_hda_codec_hdmi ath mac80211 snd_hda_codec_realtek 
snd_hda_codec_generic snd_soc_rt5640 snd_soc_rl6231 snd_hda_intel cfg80211 
snd_soc_core lpc_ich snd_hda_codec mei_me mei snd_compress snd_hda_core 
ac97_bus snd_pcm_dmaengin
 e shpchp snd_hwdep snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq 
snd_seq_device snd_timer acpi_als kfifo_buf industrialio snd elan_i2c soundcore 
snd_soc_sst_acpi dw_dmac dw_dmac_core 8250_dw spi_pxa2xx_platform 
i2c_designware_platform i2c_designware_core dell_rbtn intel_smartconnect 
mac_hid binfmt_misc parport_pc ppdev lp parport autofs4 usbhid i915 psmouse 
i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt fb_sys_fops 
libahci drm wmi sdhci_acpi sdhci i2c_hid hid video fjes [last unloaded: vboxdrv]
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972447] CPU: 3 PID: 2813 Comm: 
Xorg Tainted: G   OE   4.4.0-36-generic #55-Ubuntu
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972477] Hardware name: Dell 
Inc. XPS13 9333/0GFTRT, BIOS A08 08/31/2015
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972500] task: 88003569c4c0 
ti: 8802132b task.ti: 8802132b
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972524] RIP: 
0010:[]  [] drm_vblank_count+0x0/0x40 [drm]
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972570] RSP: 
0018:8802132b3d10  EFLAGS: 00010246
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972588] RAX:  
RBX: 880035a4c800 RCX: 
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972611] RDX: 0001 
RSI:  RDI: 880035a4c800
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972633] RBP: 8802132b3da0 
R08: 0006 R09: 00a0
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972656] R10: 8802132b3de8 
R11: c00ae950 R12: 8802132b3de8
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972678] R13: 880212409000 
R14: 0001 R15: 
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972702] FS:  
7f33434a3a00() GS:88021f2c() knlGS:
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972728] CS:  0010 DS:  ES: 
 CR0: 80050033
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972746] CR2: 36c1789e3000 
CR3: 000210964000 CR4: 001406e0
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972769] Stack:
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972776]  c008e118 
81705f6b 7fff82950ca0 7fff82950ca0
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972804]  0040 
880035a46400 8802 817070b4
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972832]  7fff82950ca8 
7fff82950ce0  
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972874] Call Trace:
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972896]  [] ? 
drm_wait_vblank+0xd8/0x5c0 [drm]
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972920]  [] ? 
sock_recvmsg+0x3b/0x50
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972939]  [] ? 
___sys_recvmsg+0x164/0x1f0
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972966]  [] 
drm_ioctl+0x152/0x540 [drm]
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.972992]  [] ? 
drm_modeset_ctl+0x60/0x60 [drm]
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973014]  [] ? 
enqueue_hrtimer+0x3d/0x90
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973034]  [] ? 
hrtimer_start_range_ns+0x1d6/0x3e0
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973056]  [] 
do_vfs_ioctl+0x29f/0x490
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973075]  [] ? 
__sys_recvmsg+0x80/0x90
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973094]  [] 
SyS_ioctl+0x79/0x90
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973112]  [] 
entry_SYSCALL_64_fastpath+0x16/0x71
Sep  9 09:31:38 adept-XPS13-9333 kernel: [71324.973133] Code: 8b 90 a0 01 00 00 
e8 c0 fc ff ff 5b 41 5c 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 0f 1f 44 00 00 
55 31 c0 48 89 e5 5d c3 0f 1f 00

[Kernel-packages] [Bug 1620658] onibi (amd64) - tests ran: 10, failed: 1

tests ran:  10, failed: 1;
  
http://kernel.ubuntu.com/testing/4.4.0-38.57/onibi__4.4.0-38.57__2016-09-09_16-02-00/results-index.html

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

Title:
  linux: 4.4.0-38.57 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-38.57 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
  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/1620658/+subscriptions

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

[Kernel-packages] [Bug 1618251] onza (i386) - tests ran: 136, failed: 0

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-69.77~14.04.1/onza__3.19.0-69.77~14.04.1__2016-09-09_15-48-00/results-index.html

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-69.77~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
  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/1618251/+subscriptions

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

[Kernel-packages] [Bug 1621725] Re: iwlegacy/iwl3945 driver flashes LED on traffic by default

David Dombrowsky:

>"Having the light flash in your face is not the default behavior in
other OSes."

What OS(es) specifically have what behavior precisely?

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

Title:
  iwlegacy/iwl3945 driver flashes LED on traffic by default

Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is still present in 16.04.  When using the iwlegacy driver,
  the default behavior is to have the blue LED indicator flash whenever
  traffic is going over the wireless.  This is annoying, as it is in the
  user's face on most laptops.

  The workaround is to add something like this to a new file named 
/etc/modprobe.d/iwled.conf 
   
 options iwlegacy led_mode=1

  I suggest that this mode be the default, and require a configuration
  change to ENABLE the flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-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 i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-36-generic.
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davek  3358 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf458 irq 28'
 Mixer name : 'Analog Devices AD1981'
 Components : 'HDA:11d41981,103c30a2,00100200 
HDA:11c13026,103c30a2,00100700'
 Controls  : 34
 Simple ctrls  : 17
  CurrentDesktop: LXDE
  Date: Fri Sep  9 00:17:14 2016
  HibernationDevice: RESUME=UUID=63b899e1-b597-4a6c-9295-5403efb298d6
  InstallationDate: Installed on 2016-07-12 (58 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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: Hewlett-Packard HP Compaq nx7400 (RB525UT#ABA)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=e8da51fc-5ebb-4d97-aaeb-0ba3f9856171 ro
  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: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/28/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YGU Ver. F.07
  dmi.board.name: 30A2
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 40.16
  dmi.chassis.asset.tag: CNU6362XLV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YGUVer.F.07:bd07/28/2006:svnHewlett-Packard:pnHPCompaqnx7400(RB525UT#ABA):pvrF.07:rvnHewlett-Packard:rn30A2:rvrKBCVersion40.16:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nx7400 (RB525UT#ABA)
  dmi.product.version: F.07
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1621899] Re: System failed to suspend properly or resume

I found that the system sometimes suspends and resumes, seemingly ok,
but then there is a kernel trace when I try to reboot that halts the
reboot and need to hard reset on reboot. The trace is not logged.

With the kernel from xenial-updates (4.4.0.36) I found a reliable
reproducer:

1. boot
2. login fully
3. close lid and wait a few seconds
4. open lid (system usually comes up)
5. login
6. reboot and get a trace

The trace was different each time though I now am running
4.4.0.38.40 from xenial-proposed and the above reproducer did not work
and the system suspended and resumed ok, but there were still these
errors from the journal log:

Sep 09 10:09:29 hostname kernel: hdaudio hdaudioC1D3: parent :01:00.1 
should not be sleeping
Sep 09 10:09:29 hostname kernel: snd_hda_codec_hdmi hdaudioC1D3: HDMI: failed 
to get afg sub nodes
Sep 09 10:09:29 hostname kernel: snd_hda_codec_hdmi: probe of hdaudioC1D3 
failed with error -22
Sep 09 10:09:29 hostname kernel: snd_hda_codec_hdmi hdaudioC1D3: HDMI: failed 
to get afg sub nodes
Sep 09 10:09:29 hostname kernel: snd_hda_codec_hdmi: probe of hdaudioC1D3 
failed with error -22
Sep 09 10:09:29 hostname kernel: snd_hda_codec_hdmi hdaudioC1D3: HDMI: failed 
to get afg sub nodes
Sep 09 10:09:29 hostname kernel: snd_hda_codec_hdmi: probe of hdaudioC1D3 
failed with error -22
Sep 09 10:09:29 hostname kernel: snd_hda_codec_generic: probe of hdaudioC1D3 
failed with error -5
Sep 09 10:09:29 hostname kernel: hdaudio hdaudioC1D3: Unable to bind the codec

Also, oddly, after resume from suspend network-indicator doesn't show
the system as connected to wifi, but it is. It will show it on reboot.

I'm not sure if the snd_hda_codec or network-indicator issues are
related or not.

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

Title:
  System failed to suspend properly or resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this system failed to suspend properly and failed to resume.
  Closed the lid, the fans kept going. Opened the lid and lights were
  flashing indicating an error and had to hard reset. It had the
  following in the logs:

  Sep  9 07:43:19 ginny gnome-session[6351]: Traceback (most recent call last):
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  Sep  9 07:43:19 ginny gnome-session[6351]: self._handler(*args, **kwargs)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 78, 
in _on_network_state_changed
  Sep  9 07:43:19 ginny gnome-session[6351]: self._update_3g_state()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 83, 
in _update_3g_state
  Sep  9 07:43:19 ginny gnome-session[6351]: on_3g = 
nm.is_active_connection_gsm_or_cdma()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 172, in 
is_active_connection_gsm_or_cdma
  Sep  9 07:43:19 ginny gnome-session[6351]: active, self.NM_DBUS_IFACE + 
".Connection.Active", 'Default')
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 162, in 
get_dbus_property
  Sep  9 07:43:19 ginny gnome-session[6351]: property = 
props.Get(interface, property)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: return 
self._proxy_method(*args, **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
  Sep  9 07:43:19 ginny gnome-session[6351]: message, timeout)
  Sep  9 07:43:19 ginny gnome-session[6351]: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.freedesktop.DBus.Properties' on object at path 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Selected interface 'wlan0'
  Sep  9 07:43:28 ginny systemd-sleep[18074]: 'SUSPEND' command timed out.
  Sep  9 07:43:28 ginny systemd-sleep[18076]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Suspending system...

  This may be a dupe of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788

  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

[Kernel-packages] [Bug 1608499] Re: Parallel depmod failure with dkms autoinstall

2016-09-09 Thread Robert Hooker

** Changed in: dkms (Ubuntu Xenial)
 Assignee: (unassigned) => Robert Hooker (sarvatt)

** Changed in: dkms (Ubuntu Trusty)
 Assignee: (unassigned) => Robert Hooker (sarvatt)

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

Title:
  Parallel depmod failure with dkms autoinstall

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  New
Status in dkms source package in Xenial:
  New

Bug description:
  Description of problem
  --

  "dkms autoinstall" installs DKMS modules in parallel, potentially executing
  several depmod instances in parallel.

  The resulting race condition causes depmod to fail and dkms install as
  well.

  This problem is critical because some DKMS modules can be left in "built"
  state after a kernel upgrade, thus the kernel modules will not be re-installed
  in /lib/modules/.

  Ubuntu release
  --
  # lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  DKMS package version
  

  # apt-cache policy dkms
  dkms:
Installed: 2.2.0.3-2ubuntu11
Candidate: 2.2.0.3-2ubuntu11
Version table:
   *** 2.2.0.3-2ubuntu11 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  Steps to reproduce
  --

  Add 2 simple DKMS modules, mod1 and mod2 (test case in attachment) with
  "dkms add", then run "dkms autoinstall".

  # dkms add mod1 ; dkms add mod2

  Creating symlink /var/lib/dkms/mod1/1.0/source ->
   /usr/src/mod1-1.0

  DKMS: add completed.

  Creating symlink /var/lib/dkms/mod2/1.0/source ->
   /usr/src/mod2-1.0

  DKMS: add completed.

  # dkms autoinstall

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area...
  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area
  .make KERNELRELEASE=4.4.0-28-generic -C /lib/modules/4.4.0-28-generic/build 
SUBDIRS=/var/lib/dkms/mod2/1.0/build S=/var/lib/dkms/mod2/1.0/build modules...
  make KERNELRELEASE=4.4.0-28-generic -C /lib/modules/4.4.0-28-generic/build 
SUBDIRS=/var/lib/dkms/mod1/1.0/build S=/var/lib/dkms/mod1/1.0/build modules.

  cleaning build area...cleaning build area.

  
  DKMS: build completed.

  DKMS: build completed.

  mod2.ko:
  Running module version sanity check.

  mod1.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.4.0-28-generic/updates/dkms/
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.4.0-28-generic/updates/dkms/

  
  depmod...depmod...(bad exit status: 1)

   Uninstall Beginning 
  Module:  mod2
  Version: 1.0
  Kernel:  4.4.0-28-generic (x86_64)
  -

  
  DKMS: install completed.

  Status: Before uninstall, this module version was ACTIVE on this
  kernel.

  mod2.ko:
   - Uninstallation
 - Deleting from: /lib/modules/4.4.0-28-generic/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.

  depmod

  DKMS: uninstall completed.
  Error! Problems with depmod detected.  Automatically uninstalling this module.
  DKMS: Install Failed (depmod problems).  Module rolled back to built state.

  root@ubuntu1604:~/dkms-depmod# dkms status
  mod1, 1.0, 4.4.0-28-generic, x86_64: installed
  mod2, 1.0, 4.4.0-28-generic, x86_64: built

  => mod2 should be in "installed" state as well.

  # modinfo mod1
  filename:   /lib/modules/4.4.0-28-generic/updates/dkms/mod1.ko
  author: 6WIND
  license:GPL
  srcversion: 8D30BAE7A8F4D38F20AEB57
  depends:
  vermagic:   4.4.0-28-generic SMP mod_unload modversions 

  # modinfo mod2
  modinfo: ERROR: Module mod2 not found.

  Solution
  

  The problem is fixed in dkms official repository by commit
  
https://github.com/dell-oss/dkms/commit/00114cbc0a1f8c0aa5143808205d1a7cc9e58d3b
  (also in attachment).

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

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

[Kernel-packages] [Bug 1618251] onza (amd64) - tests ran: 136, failed: 0

tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-69.77~14.04.1/onza__3.19.0-69.77~14.04.1__2016-09-09_14-34-00/results-index.html

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-69.77~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
  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/1618251/+subscriptions

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

[Kernel-packages] [Bug 1621899] Re: System failed to suspend properly or resume

apport information

** Tags added: apport-collected

** Description changed:

  I noticed this system failed to suspend properly and failed to resume.
  Closed the lid, the fans kept going. Opened the lid and lights were
  flashing indicating an error and had to hard reset. It had the following
  in the logs:
  
  Sep  9 07:43:19 ginny gnome-session[6351]: Traceback (most recent call last):
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  Sep  9 07:43:19 ginny gnome-session[6351]: self._handler(*args, **kwargs)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 78, 
in _on_network_state_changed
  Sep  9 07:43:19 ginny gnome-session[6351]: self._update_3g_state()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 83, 
in _update_3g_state
  Sep  9 07:43:19 ginny gnome-session[6351]: on_3g = 
nm.is_active_connection_gsm_or_cdma()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 172, in 
is_active_connection_gsm_or_cdma
  Sep  9 07:43:19 ginny gnome-session[6351]: active, self.NM_DBUS_IFACE + 
".Connection.Active", 'Default')
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 162, in 
get_dbus_property
  Sep  9 07:43:19 ginny gnome-session[6351]: property = 
props.Get(interface, property)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: return 
self._proxy_method(*args, **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
  Sep  9 07:43:19 ginny gnome-session[6351]: message, timeout)
  Sep  9 07:43:19 ginny gnome-session[6351]: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.freedesktop.DBus.Properties' on object at path 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Selected interface 'wlan0'
  Sep  9 07:43:28 ginny systemd-sleep[18074]: 'SUSPEND' command timed out.
  Sep  9 07:43:28 ginny systemd-sleep[18076]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Suspending system...
  
  This may be a dupe of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788
  
  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 i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Fri Sep  9 09:45:34 2016
  HibernationDevice: RESUME=UUID=400a17a1-efbe-472a-843d-52020a511b39
  InstallationDate: Installed on 2011-01-05 (2073 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: LENOVO 0877
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ee0834ed-203e-41cc-9b74-b509a3dc8970 ro quiet splash
  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-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (155 days ago)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 31CN28WW(V1.09)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnLENOVO:bvr31CN28WW(V1.09):bd11/19/2010:svnLENOVO:pn0877:pvrIdeaPadU460:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: 0877
  dmi.product.version: IdeaPad U460
  dmi.sys.vendor: LENOVO
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: i386
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  tish

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

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1621899/+attachment/4737710/+files/RfKill.txt

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

Title:
  System failed to suspend properly or resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this system failed to suspend properly and failed to resume.
  Closed the lid, the fans kept going. Opened the lid and lights were
  flashing indicating an error and had to hard reset. It had the
  following in the logs:

  Sep  9 07:43:19 ginny gnome-session[6351]: Traceback (most recent call last):
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  Sep  9 07:43:19 ginny gnome-session[6351]: self._handler(*args, **kwargs)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 78, 
in _on_network_state_changed
  Sep  9 07:43:19 ginny gnome-session[6351]: self._update_3g_state()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 83, 
in _update_3g_state
  Sep  9 07:43:19 ginny gnome-session[6351]: on_3g = 
nm.is_active_connection_gsm_or_cdma()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 172, in 
is_active_connection_gsm_or_cdma
  Sep  9 07:43:19 ginny gnome-session[6351]: active, self.NM_DBUS_IFACE + 
".Connection.Active", 'Default')
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 162, in 
get_dbus_property
  Sep  9 07:43:19 ginny gnome-session[6351]: property = 
props.Get(interface, property)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: return 
self._proxy_method(*args, **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
  Sep  9 07:43:19 ginny gnome-session[6351]: message, timeout)
  Sep  9 07:43:19 ginny gnome-session[6351]: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.freedesktop.DBus.Properties' on object at path 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Selected interface 'wlan0'
  Sep  9 07:43:28 ginny systemd-sleep[18074]: 'SUSPEND' command timed out.
  Sep  9 07:43:28 ginny systemd-sleep[18076]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Suspending system...

  This may be a dupe of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788

  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 i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Fri Sep  9 09:45:34 2016
  HibernationDevice: RESUME=UUID=400a17a1-efbe-472a-843d-52020a511b39
  InstallationDate: Installed on 2011-01-05 (2073 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: LENOVO 0877
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ee0834ed-203e-41cc-9b74-b509a3dc8970 ro quiet splash
  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-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (155 days ago)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 31CN28WW(V1.09)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias:

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

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1621899/+attachment/4737709/+files/PulseList.txt

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

Title:
  System failed to suspend properly or resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this system failed to suspend properly and failed to resume.
  Closed the lid, the fans kept going. Opened the lid and lights were
  flashing indicating an error and had to hard reset. It had the
  following in the logs:

  Sep  9 07:43:19 ginny gnome-session[6351]: Traceback (most recent call last):
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  Sep  9 07:43:19 ginny gnome-session[6351]: self._handler(*args, **kwargs)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 78, 
in _on_network_state_changed
  Sep  9 07:43:19 ginny gnome-session[6351]: self._update_3g_state()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 83, 
in _update_3g_state
  Sep  9 07:43:19 ginny gnome-session[6351]: on_3g = 
nm.is_active_connection_gsm_or_cdma()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 172, in 
is_active_connection_gsm_or_cdma
  Sep  9 07:43:19 ginny gnome-session[6351]: active, self.NM_DBUS_IFACE + 
".Connection.Active", 'Default')
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 162, in 
get_dbus_property
  Sep  9 07:43:19 ginny gnome-session[6351]: property = 
props.Get(interface, property)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: return 
self._proxy_method(*args, **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
  Sep  9 07:43:19 ginny gnome-session[6351]: message, timeout)
  Sep  9 07:43:19 ginny gnome-session[6351]: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.freedesktop.DBus.Properties' on object at path 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Selected interface 'wlan0'
  Sep  9 07:43:28 ginny systemd-sleep[18074]: 'SUSPEND' command timed out.
  Sep  9 07:43:28 ginny systemd-sleep[18076]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Suspending system...

  This may be a dupe of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788

  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 i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Fri Sep  9 09:45:34 2016
  HibernationDevice: RESUME=UUID=400a17a1-efbe-472a-843d-52020a511b39
  InstallationDate: Installed on 2011-01-05 (2073 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: LENOVO 0877
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ee0834ed-203e-41cc-9b74-b509a3dc8970 ro quiet splash
  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-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (155 days ago)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 31CN28WW(V1.09)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias:

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

apport information

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

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

Title:
  System failed to suspend properly or resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this system failed to suspend properly and failed to resume.
  Closed the lid, the fans kept going. Opened the lid and lights were
  flashing indicating an error and had to hard reset. It had the
  following in the logs:

  Sep  9 07:43:19 ginny gnome-session[6351]: Traceback (most recent call last):
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  Sep  9 07:43:19 ginny gnome-session[6351]: self._handler(*args, **kwargs)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 78, 
in _on_network_state_changed
  Sep  9 07:43:19 ginny gnome-session[6351]: self._update_3g_state()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 83, 
in _update_3g_state
  Sep  9 07:43:19 ginny gnome-session[6351]: on_3g = 
nm.is_active_connection_gsm_or_cdma()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 172, in 
is_active_connection_gsm_or_cdma
  Sep  9 07:43:19 ginny gnome-session[6351]: active, self.NM_DBUS_IFACE + 
".Connection.Active", 'Default')
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 162, in 
get_dbus_property
  Sep  9 07:43:19 ginny gnome-session[6351]: property = 
props.Get(interface, property)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: return 
self._proxy_method(*args, **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
  Sep  9 07:43:19 ginny gnome-session[6351]: message, timeout)
  Sep  9 07:43:19 ginny gnome-session[6351]: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.freedesktop.DBus.Properties' on object at path 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Selected interface 'wlan0'
  Sep  9 07:43:28 ginny systemd-sleep[18074]: 'SUSPEND' command timed out.
  Sep  9 07:43:28 ginny systemd-sleep[18076]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Suspending system...

  This may be a dupe of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788

  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 i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Fri Sep  9 09:45:34 2016
  HibernationDevice: RESUME=UUID=400a17a1-efbe-472a-843d-52020a511b39
  InstallationDate: Installed on 2011-01-05 (2073 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: LENOVO 0877
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ee0834ed-203e-41cc-9b74-b509a3dc8970 ro quiet splash
  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-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (155 days ago)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 31CN28WW(V1.09)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias:

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

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1621899/+attachment/4737711/+files/UdevDb.txt

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

Title:
  System failed to suspend properly or resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this system failed to suspend properly and failed to resume.
  Closed the lid, the fans kept going. Opened the lid and lights were
  flashing indicating an error and had to hard reset. It had the
  following in the logs:

  Sep  9 07:43:19 ginny gnome-session[6351]: Traceback (most recent call last):
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  Sep  9 07:43:19 ginny gnome-session[6351]: self._handler(*args, **kwargs)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 78, 
in _on_network_state_changed
  Sep  9 07:43:19 ginny gnome-session[6351]: self._update_3g_state()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 83, 
in _update_3g_state
  Sep  9 07:43:19 ginny gnome-session[6351]: on_3g = 
nm.is_active_connection_gsm_or_cdma()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 172, in 
is_active_connection_gsm_or_cdma
  Sep  9 07:43:19 ginny gnome-session[6351]: active, self.NM_DBUS_IFACE + 
".Connection.Active", 'Default')
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 162, in 
get_dbus_property
  Sep  9 07:43:19 ginny gnome-session[6351]: property = 
props.Get(interface, property)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: return 
self._proxy_method(*args, **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
  Sep  9 07:43:19 ginny gnome-session[6351]: message, timeout)
  Sep  9 07:43:19 ginny gnome-session[6351]: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.freedesktop.DBus.Properties' on object at path 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Selected interface 'wlan0'
  Sep  9 07:43:28 ginny systemd-sleep[18074]: 'SUSPEND' command timed out.
  Sep  9 07:43:28 ginny systemd-sleep[18076]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Suspending system...

  This may be a dupe of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788

  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 i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Fri Sep  9 09:45:34 2016
  HibernationDevice: RESUME=UUID=400a17a1-efbe-472a-843d-52020a511b39
  InstallationDate: Installed on 2011-01-05 (2073 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: LENOVO 0877
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ee0834ed-203e-41cc-9b74-b509a3dc8970 ro quiet splash
  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-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (155 days ago)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 31CN28WW(V1.09)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias:

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

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1621899/+attachment/4737706/+files/ProcEnviron.txt

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

Title:
  System failed to suspend properly or resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this system failed to suspend properly and failed to resume.
  Closed the lid, the fans kept going. Opened the lid and lights were
  flashing indicating an error and had to hard reset. It had the
  following in the logs:

  Sep  9 07:43:19 ginny gnome-session[6351]: Traceback (most recent call last):
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  Sep  9 07:43:19 ginny gnome-session[6351]: self._handler(*args, **kwargs)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 78, 
in _on_network_state_changed
  Sep  9 07:43:19 ginny gnome-session[6351]: self._update_3g_state()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 83, 
in _update_3g_state
  Sep  9 07:43:19 ginny gnome-session[6351]: on_3g = 
nm.is_active_connection_gsm_or_cdma()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 172, in 
is_active_connection_gsm_or_cdma
  Sep  9 07:43:19 ginny gnome-session[6351]: active, self.NM_DBUS_IFACE + 
".Connection.Active", 'Default')
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 162, in 
get_dbus_property
  Sep  9 07:43:19 ginny gnome-session[6351]: property = 
props.Get(interface, property)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: return 
self._proxy_method(*args, **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
  Sep  9 07:43:19 ginny gnome-session[6351]: message, timeout)
  Sep  9 07:43:19 ginny gnome-session[6351]: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.freedesktop.DBus.Properties' on object at path 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Selected interface 'wlan0'
  Sep  9 07:43:28 ginny systemd-sleep[18074]: 'SUSPEND' command timed out.
  Sep  9 07:43:28 ginny systemd-sleep[18076]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Suspending system...

  This may be a dupe of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788

  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 i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Fri Sep  9 09:45:34 2016
  HibernationDevice: RESUME=UUID=400a17a1-efbe-472a-843d-52020a511b39
  InstallationDate: Installed on 2011-01-05 (2073 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: LENOVO 0877
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ee0834ed-203e-41cc-9b74-b509a3dc8970 ro quiet splash
  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-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (155 days ago)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 31CN28WW(V1.09)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias:

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

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1621899/+attachment/4737700/+files/CurrentDmesg.txt

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

Title:
  System failed to suspend properly or resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this system failed to suspend properly and failed to resume.
  Closed the lid, the fans kept going. Opened the lid and lights were
  flashing indicating an error and had to hard reset. It had the
  following in the logs:

  Sep  9 07:43:19 ginny gnome-session[6351]: Traceback (most recent call last):
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  Sep  9 07:43:19 ginny gnome-session[6351]: self._handler(*args, **kwargs)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 78, 
in _on_network_state_changed
  Sep  9 07:43:19 ginny gnome-session[6351]: self._update_3g_state()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 83, 
in _update_3g_state
  Sep  9 07:43:19 ginny gnome-session[6351]: on_3g = 
nm.is_active_connection_gsm_or_cdma()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 172, in 
is_active_connection_gsm_or_cdma
  Sep  9 07:43:19 ginny gnome-session[6351]: active, self.NM_DBUS_IFACE + 
".Connection.Active", 'Default')
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 162, in 
get_dbus_property
  Sep  9 07:43:19 ginny gnome-session[6351]: property = 
props.Get(interface, property)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: return 
self._proxy_method(*args, **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
  Sep  9 07:43:19 ginny gnome-session[6351]: message, timeout)
  Sep  9 07:43:19 ginny gnome-session[6351]: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.freedesktop.DBus.Properties' on object at path 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Selected interface 'wlan0'
  Sep  9 07:43:28 ginny systemd-sleep[18074]: 'SUSPEND' command timed out.
  Sep  9 07:43:28 ginny systemd-sleep[18076]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Suspending system...

  This may be a dupe of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788

  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 i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Fri Sep  9 09:45:34 2016
  HibernationDevice: RESUME=UUID=400a17a1-efbe-472a-843d-52020a511b39
  InstallationDate: Installed on 2011-01-05 (2073 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: LENOVO 0877
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ee0834ed-203e-41cc-9b74-b509a3dc8970 ro quiet splash
  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-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (155 days ago)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 31CN28WW(V1.09)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias:

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

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1621899/+attachment/4737707/+files/ProcInterrupts.txt

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

Title:
  System failed to suspend properly or resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this system failed to suspend properly and failed to resume.
  Closed the lid, the fans kept going. Opened the lid and lights were
  flashing indicating an error and had to hard reset. It had the
  following in the logs:

  Sep  9 07:43:19 ginny gnome-session[6351]: Traceback (most recent call last):
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  Sep  9 07:43:19 ginny gnome-session[6351]: self._handler(*args, **kwargs)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 78, 
in _on_network_state_changed
  Sep  9 07:43:19 ginny gnome-session[6351]: self._update_3g_state()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 83, 
in _update_3g_state
  Sep  9 07:43:19 ginny gnome-session[6351]: on_3g = 
nm.is_active_connection_gsm_or_cdma()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 172, in 
is_active_connection_gsm_or_cdma
  Sep  9 07:43:19 ginny gnome-session[6351]: active, self.NM_DBUS_IFACE + 
".Connection.Active", 'Default')
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 162, in 
get_dbus_property
  Sep  9 07:43:19 ginny gnome-session[6351]: property = 
props.Get(interface, property)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: return 
self._proxy_method(*args, **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
  Sep  9 07:43:19 ginny gnome-session[6351]: message, timeout)
  Sep  9 07:43:19 ginny gnome-session[6351]: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.freedesktop.DBus.Properties' on object at path 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Selected interface 'wlan0'
  Sep  9 07:43:28 ginny systemd-sleep[18074]: 'SUSPEND' command timed out.
  Sep  9 07:43:28 ginny systemd-sleep[18076]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Suspending system...

  This may be a dupe of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788

  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 i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Fri Sep  9 09:45:34 2016
  HibernationDevice: RESUME=UUID=400a17a1-efbe-472a-843d-52020a511b39
  InstallationDate: Installed on 2011-01-05 (2073 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: LENOVO 0877
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ee0834ed-203e-41cc-9b74-b509a3dc8970 ro quiet splash
  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-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (155 days ago)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 31CN28WW(V1.09)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias:

[Kernel-packages] [Bug 1621899] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1621899/+attachment/4737702/+files/JournalErrors.txt

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

Title:
  System failed to suspend properly or resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this system failed to suspend properly and failed to resume.
  Closed the lid, the fans kept going. Opened the lid and lights were
  flashing indicating an error and had to hard reset. It had the
  following in the logs:

  Sep  9 07:43:19 ginny gnome-session[6351]: Traceback (most recent call last):
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  Sep  9 07:43:19 ginny gnome-session[6351]: self._handler(*args, **kwargs)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 78, 
in _on_network_state_changed
  Sep  9 07:43:19 ginny gnome-session[6351]: self._update_3g_state()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 83, 
in _update_3g_state
  Sep  9 07:43:19 ginny gnome-session[6351]: on_3g = 
nm.is_active_connection_gsm_or_cdma()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 172, in 
is_active_connection_gsm_or_cdma
  Sep  9 07:43:19 ginny gnome-session[6351]: active, self.NM_DBUS_IFACE + 
".Connection.Active", 'Default')
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 162, in 
get_dbus_property
  Sep  9 07:43:19 ginny gnome-session[6351]: property = 
props.Get(interface, property)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: return 
self._proxy_method(*args, **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
  Sep  9 07:43:19 ginny gnome-session[6351]: message, timeout)
  Sep  9 07:43:19 ginny gnome-session[6351]: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.freedesktop.DBus.Properties' on object at path 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Selected interface 'wlan0'
  Sep  9 07:43:28 ginny systemd-sleep[18074]: 'SUSPEND' command timed out.
  Sep  9 07:43:28 ginny systemd-sleep[18076]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Suspending system...

  This may be a dupe of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788

  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 i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Fri Sep  9 09:45:34 2016
  HibernationDevice: RESUME=UUID=400a17a1-efbe-472a-843d-52020a511b39
  InstallationDate: Installed on 2011-01-05 (2073 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: LENOVO 0877
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ee0834ed-203e-41cc-9b74-b509a3dc8970 ro quiet splash
  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-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (155 days ago)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 31CN28WW(V1.09)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias:

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

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1621899/+attachment/4737708/+files/ProcModules.txt

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

Title:
  System failed to suspend properly or resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this system failed to suspend properly and failed to resume.
  Closed the lid, the fans kept going. Opened the lid and lights were
  flashing indicating an error and had to hard reset. It had the
  following in the logs:

  Sep  9 07:43:19 ginny gnome-session[6351]: Traceback (most recent call last):
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  Sep  9 07:43:19 ginny gnome-session[6351]: self._handler(*args, **kwargs)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 78, 
in _on_network_state_changed
  Sep  9 07:43:19 ginny gnome-session[6351]: self._update_3g_state()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 83, 
in _update_3g_state
  Sep  9 07:43:19 ginny gnome-session[6351]: on_3g = 
nm.is_active_connection_gsm_or_cdma()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 172, in 
is_active_connection_gsm_or_cdma
  Sep  9 07:43:19 ginny gnome-session[6351]: active, self.NM_DBUS_IFACE + 
".Connection.Active", 'Default')
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 162, in 
get_dbus_property
  Sep  9 07:43:19 ginny gnome-session[6351]: property = 
props.Get(interface, property)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: return 
self._proxy_method(*args, **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
  Sep  9 07:43:19 ginny gnome-session[6351]: message, timeout)
  Sep  9 07:43:19 ginny gnome-session[6351]: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.freedesktop.DBus.Properties' on object at path 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Selected interface 'wlan0'
  Sep  9 07:43:28 ginny systemd-sleep[18074]: 'SUSPEND' command timed out.
  Sep  9 07:43:28 ginny systemd-sleep[18076]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Suspending system...

  This may be a dupe of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788

  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 i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Fri Sep  9 09:45:34 2016
  HibernationDevice: RESUME=UUID=400a17a1-efbe-472a-843d-52020a511b39
  InstallationDate: Installed on 2011-01-05 (2073 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: LENOVO 0877
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ee0834ed-203e-41cc-9b74-b509a3dc8970 ro quiet splash
  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-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (155 days ago)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 31CN28WW(V1.09)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias:

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

apport information

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

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

Title:
  System failed to suspend properly or resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this system failed to suspend properly and failed to resume.
  Closed the lid, the fans kept going. Opened the lid and lights were
  flashing indicating an error and had to hard reset. It had the
  following in the logs:

  Sep  9 07:43:19 ginny gnome-session[6351]: Traceback (most recent call last):
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  Sep  9 07:43:19 ginny gnome-session[6351]: self._handler(*args, **kwargs)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 78, 
in _on_network_state_changed
  Sep  9 07:43:19 ginny gnome-session[6351]: self._update_3g_state()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 83, 
in _update_3g_state
  Sep  9 07:43:19 ginny gnome-session[6351]: on_3g = 
nm.is_active_connection_gsm_or_cdma()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 172, in 
is_active_connection_gsm_or_cdma
  Sep  9 07:43:19 ginny gnome-session[6351]: active, self.NM_DBUS_IFACE + 
".Connection.Active", 'Default')
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 162, in 
get_dbus_property
  Sep  9 07:43:19 ginny gnome-session[6351]: property = 
props.Get(interface, property)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: return 
self._proxy_method(*args, **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
  Sep  9 07:43:19 ginny gnome-session[6351]: message, timeout)
  Sep  9 07:43:19 ginny gnome-session[6351]: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.freedesktop.DBus.Properties' on object at path 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Selected interface 'wlan0'
  Sep  9 07:43:28 ginny systemd-sleep[18074]: 'SUSPEND' command timed out.
  Sep  9 07:43:28 ginny systemd-sleep[18076]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Suspending system...

  This may be a dupe of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788

  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 i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Fri Sep  9 09:45:34 2016
  HibernationDevice: RESUME=UUID=400a17a1-efbe-472a-843d-52020a511b39
  InstallationDate: Installed on 2011-01-05 (2073 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: LENOVO 0877
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ee0834ed-203e-41cc-9b74-b509a3dc8970 ro quiet splash
  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-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (155 days ago)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 31CN28WW(V1.09)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias:

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

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1621899/+attachment/4737705/+files/ProcCpuinfo.txt

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

Title:
  System failed to suspend properly or resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this system failed to suspend properly and failed to resume.
  Closed the lid, the fans kept going. Opened the lid and lights were
  flashing indicating an error and had to hard reset. It had the
  following in the logs:

  Sep  9 07:43:19 ginny gnome-session[6351]: Traceback (most recent call last):
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  Sep  9 07:43:19 ginny gnome-session[6351]: self._handler(*args, **kwargs)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 78, 
in _on_network_state_changed
  Sep  9 07:43:19 ginny gnome-session[6351]: self._update_3g_state()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 83, 
in _update_3g_state
  Sep  9 07:43:19 ginny gnome-session[6351]: on_3g = 
nm.is_active_connection_gsm_or_cdma()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 172, in 
is_active_connection_gsm_or_cdma
  Sep  9 07:43:19 ginny gnome-session[6351]: active, self.NM_DBUS_IFACE + 
".Connection.Active", 'Default')
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 162, in 
get_dbus_property
  Sep  9 07:43:19 ginny gnome-session[6351]: property = 
props.Get(interface, property)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: return 
self._proxy_method(*args, **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
  Sep  9 07:43:19 ginny gnome-session[6351]: message, timeout)
  Sep  9 07:43:19 ginny gnome-session[6351]: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.freedesktop.DBus.Properties' on object at path 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Selected interface 'wlan0'
  Sep  9 07:43:28 ginny systemd-sleep[18074]: 'SUSPEND' command timed out.
  Sep  9 07:43:28 ginny systemd-sleep[18076]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Suspending system...

  This may be a dupe of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788

  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 i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Fri Sep  9 09:45:34 2016
  HibernationDevice: RESUME=UUID=400a17a1-efbe-472a-843d-52020a511b39
  InstallationDate: Installed on 2011-01-05 (2073 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: LENOVO 0877
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ee0834ed-203e-41cc-9b74-b509a3dc8970 ro quiet splash
  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-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (155 days ago)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 31CN28WW(V1.09)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias:

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

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1621899/+attachment/4737703/+files/Lspci.txt

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

Title:
  System failed to suspend properly or resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this system failed to suspend properly and failed to resume.
  Closed the lid, the fans kept going. Opened the lid and lights were
  flashing indicating an error and had to hard reset. It had the
  following in the logs:

  Sep  9 07:43:19 ginny gnome-session[6351]: Traceback (most recent call last):
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  Sep  9 07:43:19 ginny gnome-session[6351]: self._handler(*args, **kwargs)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 78, 
in _on_network_state_changed
  Sep  9 07:43:19 ginny gnome-session[6351]: self._update_3g_state()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 83, 
in _update_3g_state
  Sep  9 07:43:19 ginny gnome-session[6351]: on_3g = 
nm.is_active_connection_gsm_or_cdma()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 172, in 
is_active_connection_gsm_or_cdma
  Sep  9 07:43:19 ginny gnome-session[6351]: active, self.NM_DBUS_IFACE + 
".Connection.Active", 'Default')
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 162, in 
get_dbus_property
  Sep  9 07:43:19 ginny gnome-session[6351]: property = 
props.Get(interface, property)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: return 
self._proxy_method(*args, **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
  Sep  9 07:43:19 ginny gnome-session[6351]: message, timeout)
  Sep  9 07:43:19 ginny gnome-session[6351]: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.freedesktop.DBus.Properties' on object at path 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Selected interface 'wlan0'
  Sep  9 07:43:28 ginny systemd-sleep[18074]: 'SUSPEND' command timed out.
  Sep  9 07:43:28 ginny systemd-sleep[18076]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Suspending system...

  This may be a dupe of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788

  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 i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Fri Sep  9 09:45:34 2016
  HibernationDevice: RESUME=UUID=400a17a1-efbe-472a-843d-52020a511b39
  InstallationDate: Installed on 2011-01-05 (2073 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: LENOVO 0877
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ee0834ed-203e-41cc-9b74-b509a3dc8970 ro quiet splash
  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-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (155 days ago)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 31CN28WW(V1.09)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias:

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

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1621899/+attachment/4737701/+files/IwConfig.txt

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

Title:
  System failed to suspend properly or resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this system failed to suspend properly and failed to resume.
  Closed the lid, the fans kept going. Opened the lid and lights were
  flashing indicating an error and had to hard reset. It had the
  following in the logs:

  Sep  9 07:43:19 ginny gnome-session[6351]: Traceback (most recent call last):
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  Sep  9 07:43:19 ginny gnome-session[6351]: self._handler(*args, **kwargs)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 78, 
in _on_network_state_changed
  Sep  9 07:43:19 ginny gnome-session[6351]: self._update_3g_state()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 83, 
in _update_3g_state
  Sep  9 07:43:19 ginny gnome-session[6351]: on_3g = 
nm.is_active_connection_gsm_or_cdma()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 172, in 
is_active_connection_gsm_or_cdma
  Sep  9 07:43:19 ginny gnome-session[6351]: active, self.NM_DBUS_IFACE + 
".Connection.Active", 'Default')
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 162, in 
get_dbus_property
  Sep  9 07:43:19 ginny gnome-session[6351]: property = 
props.Get(interface, property)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: return 
self._proxy_method(*args, **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
  Sep  9 07:43:19 ginny gnome-session[6351]: message, timeout)
  Sep  9 07:43:19 ginny gnome-session[6351]: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.freedesktop.DBus.Properties' on object at path 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Selected interface 'wlan0'
  Sep  9 07:43:28 ginny systemd-sleep[18074]: 'SUSPEND' command timed out.
  Sep  9 07:43:28 ginny systemd-sleep[18076]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Suspending system...

  This may be a dupe of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788

  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 i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Fri Sep  9 09:45:34 2016
  HibernationDevice: RESUME=UUID=400a17a1-efbe-472a-843d-52020a511b39
  InstallationDate: Installed on 2011-01-05 (2073 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: LENOVO 0877
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ee0834ed-203e-41cc-9b74-b509a3dc8970 ro quiet splash
  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-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (155 days ago)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 31CN28WW(V1.09)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias:

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

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1621899/+attachment/4737699/+files/CRDA.txt

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

Title:
  System failed to suspend properly or resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this system failed to suspend properly and failed to resume.
  Closed the lid, the fans kept going. Opened the lid and lights were
  flashing indicating an error and had to hard reset. It had the
  following in the logs:

  Sep  9 07:43:19 ginny gnome-session[6351]: Traceback (most recent call last):
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  Sep  9 07:43:19 ginny gnome-session[6351]: self._handler(*args, **kwargs)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 78, 
in _on_network_state_changed
  Sep  9 07:43:19 ginny gnome-session[6351]: self._update_3g_state()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 83, 
in _update_3g_state
  Sep  9 07:43:19 ginny gnome-session[6351]: on_3g = 
nm.is_active_connection_gsm_or_cdma()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 172, in 
is_active_connection_gsm_or_cdma
  Sep  9 07:43:19 ginny gnome-session[6351]: active, self.NM_DBUS_IFACE + 
".Connection.Active", 'Default')
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 162, in 
get_dbus_property
  Sep  9 07:43:19 ginny gnome-session[6351]: property = 
props.Get(interface, property)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: return 
self._proxy_method(*args, **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
  Sep  9 07:43:19 ginny gnome-session[6351]: message, timeout)
  Sep  9 07:43:19 ginny gnome-session[6351]: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.freedesktop.DBus.Properties' on object at path 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Selected interface 'wlan0'
  Sep  9 07:43:28 ginny systemd-sleep[18074]: 'SUSPEND' command timed out.
  Sep  9 07:43:28 ginny systemd-sleep[18076]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Suspending system...

  This may be a dupe of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788

  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 i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Fri Sep  9 09:45:34 2016
  HibernationDevice: RESUME=UUID=400a17a1-efbe-472a-843d-52020a511b39
  InstallationDate: Installed on 2011-01-05 (2073 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: LENOVO 0877
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ee0834ed-203e-41cc-9b74-b509a3dc8970 ro quiet splash
  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-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (155 days ago)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 31CN28WW(V1.09)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias:

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

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

Title:
  System failed to suspend properly or resume

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed this system failed to suspend properly and failed to resume.
  Closed the lid, the fans kept going. Opened the lid and lights were
  flashing indicating an error and had to hard reset. It had the
  following in the logs:

  Sep  9 07:43:19 ginny gnome-session[6351]: Traceback (most recent call last):
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
  Sep  9 07:43:19 ginny gnome-session[6351]: self._handler(*args, **kwargs)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 78, 
in _on_network_state_changed
  Sep  9 07:43:19 ginny gnome-session[6351]: self._update_3g_state()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 83, 
in _update_3g_state
  Sep  9 07:43:19 ginny gnome-session[6351]: on_3g = 
nm.is_active_connection_gsm_or_cdma()
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 172, in 
is_active_connection_gsm_or_cdma
  Sep  9 07:43:19 ginny gnome-session[6351]: active, self.NM_DBUS_IFACE + 
".Connection.Active", 'Default')
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 162, in 
get_dbus_property
  Sep  9 07:43:19 ginny gnome-session[6351]: property = 
props.Get(interface, property)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: return 
self._proxy_method(*args, **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
  Sep  9 07:43:19 ginny gnome-session[6351]: **keywords)
  Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
  Sep  9 07:43:19 ginny gnome-session[6351]: message, timeout)
  Sep  9 07:43:19 ginny gnome-session[6351]: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.freedesktop.DBus.Properties' on object at path 
/org/freedesktop/NetworkManager/ActiveConnection/1
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Selected interface 'wlan0'
  Sep  9 07:43:28 ginny systemd-sleep[18074]: 'SUSPEND' command timed out.
  Sep  9 07:43:28 ginny systemd-sleep[18076]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
  Sep  9 07:43:28 ginny systemd-sleep[18074]: Suspending system...

  This may be a dupe of
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788

  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 i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  Date: Fri Sep  9 09:45:34 2016
  HibernationDevice: RESUME=UUID=400a17a1-efbe-472a-843d-52020a511b39
  InstallationDate: Installed on 2011-01-05 (2073 days ago)
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  MachineType: LENOVO 0877
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ee0834ed-203e-41cc-9b74-b509a3dc8970 ro quiet splash
  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-36-generic N/A
   linux-backports-modules-4.4.0-36-generic  N/A
   linux-firmware1.157.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-07 (155 days ago)
  dmi.bios.date: 11/19/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 31CN28WW(V1.09)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Base Board Product Name
  dmi.board.vendor: LENOVO
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias:

[Kernel-packages] [Bug 1608499] Re: Parallel depmod failure with dkms autoinstall

2016-09-09 Thread Launchpad Bug Tracker

This bug was fixed in the package dkms - 2.2.0.3-2ubuntu13

---
dkms (2.2.0.3-2ubuntu13) yakkety; urgency=medium

  * debian/patches/Parallel-depmod-failure.patch: (LP: #1608499)
- Backport fix from 2.3 to fix a race condition in dkms autoinstall

 -- Robert Hooker   Thu, 08 Sep 2016 16:43:56 -0400

** Changed in: dkms (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Parallel depmod failure with dkms autoinstall

Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Trusty:
  New
Status in dkms source package in Xenial:
  New

Bug description:
  Description of problem
  --

  "dkms autoinstall" installs DKMS modules in parallel, potentially executing
  several depmod instances in parallel.

  The resulting race condition causes depmod to fail and dkms install as
  well.

  This problem is critical because some DKMS modules can be left in "built"
  state after a kernel upgrade, thus the kernel modules will not be re-installed
  in /lib/modules/.

  Ubuntu release
  --
  # lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  DKMS package version
  

  # apt-cache policy dkms
  dkms:
Installed: 2.2.0.3-2ubuntu11
Candidate: 2.2.0.3-2ubuntu11
Version table:
   *** 2.2.0.3-2ubuntu11 500
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://fr.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  Steps to reproduce
  --

  Add 2 simple DKMS modules, mod1 and mod2 (test case in attachment) with
  "dkms add", then run "dkms autoinstall".

  # dkms add mod1 ; dkms add mod2

  Creating symlink /var/lib/dkms/mod1/1.0/source ->
   /usr/src/mod1-1.0

  DKMS: add completed.

  Creating symlink /var/lib/dkms/mod2/1.0/source ->
   /usr/src/mod2-1.0

  DKMS: add completed.

  # dkms autoinstall

  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area...
  Kernel preparation unnecessary for this kernel.  Skipping...

  Building module:
  cleaning build area
  .make KERNELRELEASE=4.4.0-28-generic -C /lib/modules/4.4.0-28-generic/build 
SUBDIRS=/var/lib/dkms/mod2/1.0/build S=/var/lib/dkms/mod2/1.0/build modules...
  make KERNELRELEASE=4.4.0-28-generic -C /lib/modules/4.4.0-28-generic/build 
SUBDIRS=/var/lib/dkms/mod1/1.0/build S=/var/lib/dkms/mod1/1.0/build modules.

  cleaning build area...cleaning build area.

  
  DKMS: build completed.

  DKMS: build completed.

  mod2.ko:
  Running module version sanity check.

  mod1.ko:
  Running module version sanity check.
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.4.0-28-generic/updates/dkms/
   - Original module
 - No original module exists within this kernel
   - Installation
 - Installing to /lib/modules/4.4.0-28-generic/updates/dkms/

  
  depmod...depmod...(bad exit status: 1)

   Uninstall Beginning 
  Module:  mod2
  Version: 1.0
  Kernel:  4.4.0-28-generic (x86_64)
  -

  
  DKMS: install completed.

  Status: Before uninstall, this module version was ACTIVE on this
  kernel.

  mod2.ko:
   - Uninstallation
 - Deleting from: /lib/modules/4.4.0-28-generic/updates/dkms/
   - Original module
 - No original module was found for this module on this kernel.
 - Use the dkms install command to reinstall any previous module version.

  depmod

  DKMS: uninstall completed.
  Error! Problems with depmod detected.  Automatically uninstalling this module.
  DKMS: Install Failed (depmod problems).  Module rolled back to built state.

  root@ubuntu1604:~/dkms-depmod# dkms status
  mod1, 1.0, 4.4.0-28-generic, x86_64: installed
  mod2, 1.0, 4.4.0-28-generic, x86_64: built

  => mod2 should be in "installed" state as well.

  # modinfo mod1
  filename:   /lib/modules/4.4.0-28-generic/updates/dkms/mod1.ko
  author: 6WIND
  license:GPL
  srcversion: 8D30BAE7A8F4D38F20AEB57
  depends:
  vermagic:   4.4.0-28-generic SMP mod_unload modversions 

  # modinfo mod2
  modinfo: ERROR: Module mod2 not found.

  Solution
  

  The problem is fixed in dkms official repository by commit
  
https://github.com/dell-oss/dkms/commit/00114cbc0a1f8c0aa5143808205d1a7cc9e58d3b
  (also in attachment).

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

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

[Kernel-packages] [Bug 1621899] [NEW] System failed to suspend properly or resume

Public bug reported:

I noticed this system failed to suspend properly and failed to resume.
Closed the lid, the fans kept going. Opened the lid and lights were
flashing indicating an error and had to hard reset. It had the following
in the logs:

Sep  9 07:43:19 ginny gnome-session[6351]: Traceback (most recent call last):
Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 230, in 
maybe_handle_message
Sep  9 07:43:19 ginny gnome-session[6351]: self._handler(*args, **kwargs)
Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 78, 
in _on_network_state_changed
Sep  9 07:43:19 ginny gnome-session[6351]: self._update_3g_state()
Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/AlertWatcher.py", line 83, 
in _update_3g_state
Sep  9 07:43:19 ginny gnome-session[6351]: on_3g = 
nm.is_active_connection_gsm_or_cdma()
Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 172, in 
is_active_connection_gsm_or_cdma
Sep  9 07:43:19 ginny gnome-session[6351]: active, self.NM_DBUS_IFACE + 
".Connection.Active", 'Default')
Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/UpdateManager/Core/roam.py", line 162, in 
get_dbus_property
Sep  9 07:43:19 ginny gnome-session[6351]: property = props.Get(interface, 
property)
Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 70, in __call__
Sep  9 07:43:19 ginny gnome-session[6351]: return self._proxy_method(*args, 
**keywords)
Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/proxies.py", line 145, in __call__
Sep  9 07:43:19 ginny gnome-session[6351]: **keywords)
Sep  9 07:43:19 ginny gnome-session[6351]:   File 
"/usr/lib/python3/dist-packages/dbus/connection.py", line 651, in call_blocking
Sep  9 07:43:19 ginny gnome-session[6351]: message, timeout)
Sep  9 07:43:19 ginny gnome-session[6351]: dbus.exceptions.DBusException: 
org.freedesktop.DBus.Error.UnknownMethod: No such interface 
'org.freedesktop.DBus.Properties' on object at path 
/org/freedesktop/NetworkManager/ActiveConnection/1
Sep  9 07:43:28 ginny systemd-sleep[18074]: Selected interface 'wlan0'
Sep  9 07:43:28 ginny systemd-sleep[18074]: 'SUSPEND' command timed out.
Sep  9 07:43:28 ginny systemd-sleep[18076]: 
/lib/systemd/system-sleep/wpasupplicant failed with error code 254.
Sep  9 07:43:28 ginny systemd-sleep[18074]: Suspending system...

This may be a dupe of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543788

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 i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D1', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
Date: Fri Sep  9 09:45:34 2016
HibernationDevice: RESUME=UUID=400a17a1-efbe-472a-843d-52020a511b39
InstallationDate: Installed on 2011-01-05 (2073 days ago)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: LENOVO 0877
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ee0834ed-203e-41cc-9b74-b509a3dc8970 ro quiet splash
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-36-generic N/A
 linux-backports-modules-4.4.0-36-generic  N/A
 linux-firmware1.157.3
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-04-07 (155 days ago)
dmi.bios.date: 11/19/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 31CN28WW(V1.09)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: LENOVO
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnLENOVO:bvr31CN28WW(V1.09):bd11/19/2010:svnLENOVO:pn0877:pvrIdeaPadU460:rvnLENOVO:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: 0877
dmi.product.version: IdeaPad U460
dmi.sys.vendor: LENOVO

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


** Tags: apport-bug i386 xenial

** Summary changed:

- System failed to resume from suspend
+ System failed to suspend properly or resume

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1566302] Re: Ubuntu 16.04: Suspend freezes the system after upgrade to linux image 4.4.0-16

2016-09-09 Thread rewound

Bug 1620733 may be of interest, it uses kernel 4.8.0-040800rc5-generic

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

Title:
  Ubuntu 16.04: Suspend freezes the system after upgrade to linux image
  4.4.0-16

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  I'm using ubuntu 16.04 on a XPS 15 9550.

  Suspend/resume worked flawlessly with linux image 4.4.0-15, and after
  standard upgrade yesterday (5/04/2016) which installed image 4.4.0-16,
  the system freezes when attempting a suspend. I get  no response from
  the system (nor keyboard, nor screen, nor touchpad), but it gets very
  hot, so that it must be running something.

  Booting with 4.4.0-15 makes the suspend to work perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-16-generic 4.4.0-16.32
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  macias 1770 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Tue Apr  5 14:56:17 2016
  HibernationDevice: RESUME=UUID=4180adfa-3852-4a96-86b4-f3696448c743
  InstallationDate: Installed on 2016-03-07 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. 
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=es_ES
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=673f4658-75f8-4c01-bcd8-0af860269699 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.01.19
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.01.19:bd01/25/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1618251] onza (i386) - tests ran: 20, failed: 1

tests ran:  20, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-69.77~14.04.1/onza__3.19.0-69.77~14.04.1__2016-09-09_12-48-00/results-index.html

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-69.77~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
  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/1618251/+subscriptions

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

[Kernel-packages] [Bug 1621725] Re: iwlegacy/iwl3945 driver flashes LED on traffic by default

2016-09-09 Thread David Dombrowsky

> Regarding the LED blinking when WiFi traffic is occurring, while you
may find this annoying, and it could be many others find this also, this
being the default action it isn't considered a software bug.

A new user is probably not going to take the time to google the problem,
find this and related bugs, and create a specific file with specific
options in order to make the system usable.  Having the light flash in
your face is not the default behavior in other OSes.  I would consider
it a real bug.

That said, I get your point.  This is also a legacy driver and will
probably go away eventually.

Thank you for your response.

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

Title:
  iwlegacy/iwl3945 driver flashes LED on traffic by default

Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is still present in 16.04.  When using the iwlegacy driver,
  the default behavior is to have the blue LED indicator flash whenever
  traffic is going over the wireless.  This is annoying, as it is in the
  user's face on most laptops.

  The workaround is to add something like this to a new file named 
/etc/modprobe.d/iwled.conf 
   
 options iwlegacy led_mode=1

  I suggest that this mode be the default, and require a configuration
  change to ENABLE the flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-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 i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-36-generic.
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davek  3358 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf458 irq 28'
 Mixer name : 'Analog Devices AD1981'
 Components : 'HDA:11d41981,103c30a2,00100200 
HDA:11c13026,103c30a2,00100700'
 Controls  : 34
 Simple ctrls  : 17
  CurrentDesktop: LXDE
  Date: Fri Sep  9 00:17:14 2016
  HibernationDevice: RESUME=UUID=63b899e1-b597-4a6c-9295-5403efb298d6
  InstallationDate: Installed on 2016-07-12 (58 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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: Hewlett-Packard HP Compaq nx7400 (RB525UT#ABA)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=e8da51fc-5ebb-4d97-aaeb-0ba3f9856171 ro
  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: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/28/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YGU Ver. F.07
  dmi.board.name: 30A2
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 40.16
  dmi.chassis.asset.tag: CNU6362XLV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YGUVer.F.07:bd07/28/2006:svnHewlett-Packard:pnHPCompaqnx7400(RB525UT#ABA):pvrF.07:rvnHewlett-Packard:rn30A2:rvrKBCVersion40.16:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nx7400 (RB525UT#ABA)
  dmi.product.version: F.07
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1621474] Re: VLAN creation fails with VF multi queueuing

2016-09-09 Thread Wijdene REKIK

With additional tests basing on the last driver versions on the host and guest:
 * 4.4.6 ixgbe version on the host 
 * 3.2.2 ixgbevf version on the guest, 

and with following kernel version:

root@ubuntu1604:~# uname -a
Linux ubuntu1604 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
root@ubuntu1604:~# lsb_release -da
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename:   xenial

on both host and VM, the creation of VLAN was not supported:

root@ubuntu1604:~# ip link add link ens5 name vlan2 type vlan id 2
[ 3275.847268] VF could not set VLAN 2 <=

Thus, even with recent versions, issue can be reproduced.

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

Title:
  VLAN creation fails with VF multi queueuing

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description
  

  It can be read in SR-IOV companion guide that 82599 chipsets :

  * The 82599 has 128 Transmit and 128 Receive queues. They are generally 
referred to/thought of as queue pairs (1 Transmit and 1 Receive queue). This 
gives the 82599 128 queue pairs.
  * The 82599 has up to 64 pools, with each pool having two queue pairs in 
it. That is two Transmit and Receive queue assigned to each VF.
  * The 82599 allows for a variable configuration for the number of pools. 
In SR-IOV mode, there can be 16, 32 or 64 pools.

  The last line suggest using combined queues of 2, 4 and 8.

  The only way, for now we found, is using tc on the host especially as the 
ethtool command is not supported (ethtool -L eth10 combined 8 for example).
  And, with following command "tc qdisc add dev eth10 root mqprio num_tc 8", we 
will be able to use up to 8 combined queues on the host PF and guests which are 
using VFs.
  Yet, with 8 combined queues with tc commnad, VLAN creation was not permitted.

  Following driver versions have been used on host and guest to enable this 
multiqueue option:
* 4.3.15 ixgbe in the host
* 3.1.2  ixgbevf in the guest

  To reproduce
  -

  On the host side
  

  root@ubuntu1404:~# rmmod ixgbe
  root@ubuntu1404:~# modprobe ixgbe
  [ 4817.027637] ixgbe :05:00.0: failed to load because an unsupported SFP+ 
or QSFP module type was detected.
  [ 4817.038630] ixgbe :05:00.0: Reload the driver after installing a 
supported module.
  [ 4817.418360] ixgbe :41:00.1: failed to load because an unsupported SFP+ 
or QSFP module type was detected.
  [ 4817.429354] ixgbe :41:00.1: Reload the driver after installing a 
supported module.
  [ 4817.838086] ixgbe :43:00.0: failed to load because an unsupported SFP+ 
or QSFP module type was detected.
  [ 4817.849091] ixgbe :43:00.0: Reload the driver after installing a 
supported module.
  [ 4817.889189] ixgbe :43:00.1: failed to load because an unsupported SFP+ 
or QSFP module type was detected.
  [ 4817.900178] ixgbe :43:00.1: Reload the driver after installing a 
supported module.
  [ 4817.940318] ixgbe :44:00.0: failed to load because an unsupported SFP+ 
or QSFP module type was detected.
  [ 4817.951357] ixgbe :44:00.0: Reload the driver after installing a 
supported module.
  root@ubuntu1404:~# modinfo ixgbe
  filename:   
/lib/modules/3.13.0-91-generic/updates/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.3.15
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver
  author: Intel Corporation, 
  srcversion: 7AED484083B2C5B86424A3A
  alias:  pci:v8086d15ADsv*sd*bc*sc*i*
  alias:  pci:v8086d15ACsv*sd*bc*sc*i*
  alias:  pci:v8086d15ABsv*sd*bc*sc*i*
  alias:  pci:v8086d15AAsv*sd*bc*sc*i*
  alias:  pci:v8086d15D1sv*sd*bc*sc*i*
  alias:  pci:v8086d1563sv*sd*bc*sc*i*
  alias:  pci:v8086d1560sv*sd*bc*sc*i*
  alias:  pci:v8086d1558sv*sd*bc*sc*i*
  alias:  pci:v8086d154Asv*sd*bc*sc*i*
  alias:  pci:v8086d1557sv*sd*bc*sc*i*
  alias:  pci:v8086d154Fsv*sd*bc*sc*i*
  alias:  pci:v8086d154Dsv*sd*bc*sc*i*
  alias:  pci:v8086d1528sv*sd*bc*sc*i*
  alias:  pci:v8086d10F8sv*sd*bc*sc*i*
  alias:  pci:v8086d151Csv*sd*bc*sc*i*
  alias:  pci:v8086d1529sv*sd*bc*sc*i*
  alias:  pci:v8086d152Asv*sd*bc*sc*i*
  alias:  pci:v8086d10F9sv*sd*bc*sc*i*
  alias:  pci:v8086d1514sv*sd*bc*sc*i*
  alias:  pci:v8086d1507sv*sd*bc*sc*i*
  alias:  pci:v8086d10FBsv*sd*bc*sc*i*
  alias:  pci:v8086d1517sv*sd*bc*sc*i*
  alias:

[Kernel-packages] [Bug 1621725] Re: iwlegacy/iwl3945 driver flashes LED on traffic by default

David Dombrowsky, thank you for reporting this and helping make Ubuntu
better.

Regarding the LED blinking when WiFi traffic is occurring, while you may
find this annoying, and it could be many others find this also, this
being the default action it isn't considered a software bug. Given the
fact you have an option to turn it off in software, you also have a way
to address the issue as you see fit. If anything, the LED light
installed into the laptop would be brighter than preferred, making this
a manufacturer design issue you have.

Please feel free to report any future bugs you may find.

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

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

Title:
  iwlegacy/iwl3945 driver flashes LED on traffic by default

Status in linux package in Ubuntu:
  Invalid

Bug description:
  This bug is still present in 16.04.  When using the iwlegacy driver,
  the default behavior is to have the blue LED indicator flash whenever
  traffic is going over the wireless.  This is annoying, as it is in the
  user's face on most laptops.

  The workaround is to add something like this to a new file named 
/etc/modprobe.d/iwled.conf 
   
 options iwlegacy led_mode=1

  I suggest that this mode be the default, and require a configuration
  change to ENABLE the flashing.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-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 i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-36-generic.
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davek  3358 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf458 irq 28'
 Mixer name : 'Analog Devices AD1981'
 Components : 'HDA:11d41981,103c30a2,00100200 
HDA:11c13026,103c30a2,00100700'
 Controls  : 34
 Simple ctrls  : 17
  CurrentDesktop: LXDE
  Date: Fri Sep  9 00:17:14 2016
  HibernationDevice: RESUME=UUID=63b899e1-b597-4a6c-9295-5403efb298d6
  InstallationDate: Installed on 2016-07-12 (58 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.3)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 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: Hewlett-Packard HP Compaq nx7400 (RB525UT#ABA)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=e8da51fc-5ebb-4d97-aaeb-0ba3f9856171 ro
  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: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/28/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YGU Ver. F.07
  dmi.board.name: 30A2
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 40.16
  dmi.chassis.asset.tag: CNU6362XLV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YGUVer.F.07:bd07/28/2006:svnHewlett-Packard:pnHPCompaqnx7400(RB525UT#ABA):pvrF.07:rvnHewlett-Packard:rn30A2:rvrKBCVersion40.16:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nx7400 (RB525UT#ABA)
  dmi.product.version: F.07
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1618952] Re: Display brightness keys not registered by ~$acpi_listen

Omadas, please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect 1618952

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at 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/1618952

Title:
  Display brightness keys not registered by ~$acpi_listen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brightness keys donot repond, Brightness controls on
  xfce4_power_manager behave as expected.  Either kernel is not
  recognizing the fn+f5/f6 commands or their is a problem with my
  configuration.

  here is the event output of all of my fn+(f keys):
  ~ $ acpi_listen
  button/volumeup VOLUP 0080  K
  button/volumedown VOLDN 0080  K
  button/mute MUTE 0080  K
  button/mute MUTE 0080  K
   PNP0C14:00 00ff 
   PNP0C14:00 00ff 
   PNP0C14:00 00ff 
  button/sleep SBTN 0080 
  button/sleep PNP0C0E:00 0080 0001

  (As a side note, my bios has no configuration options for the function
  keys.)

  (On another note, it is worth noting the fn+f2 does not respond with
  an event calling for airplane mode either, which is not important to
  me but may be important for others, if this is fixed by any solution
  here I will make note, though airplane mode may be a feature request
  and not a bug.)

  I have tried several options in the etc/default/grub file, these include:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video.use_native_backlight=1"
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video.use_native_backlight=0"
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor"
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=intel_backlight"
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi="
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=Linux"

  I am using Mint XFCE Sarah (Ubuntu Xenial) 64-bit, xfce4_power_manager
  was tested with all above configurations to both handle and not handle
  display brightness keys.  My Computer is an ASUS model is X540LA.  I
  am attaching a few files to help with this bug report.

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

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

[Kernel-packages] [Bug 1587674] Re: Wifi cannot connect to router on Ubuntu 16.04 LTS - Ralink RT5390

Salvatore Delpiano / Brian Carrozza, 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.

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

** Summary changed:

- Wifi cannot connect to router on Ubuntu 16.04 LTS - Ralink RT5390
+ [HP Pavilion dm1-3205au Entertainment Notebook PC] Wifi cannot connect to 
router on Ubuntu 16.04 LTS - Ralink RT5390

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

Title:
  [HP Pavilion dm1-3205au Entertainment Notebook PC] Wifi cannot connect
  to router on Ubuntu 16.04 LTS - Ralink RT5390

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have researched all possible solutions. The correct driver rt2800pci
  is installed correctly out of the box. No hardware faults. Wifi works
  on Ubuntu 14.04 and Windows 10. Confirmed also driver is not blocked
  and hardware is enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  johnnel1436 F pulseaudio
   /dev/snd/controlC0:  johnnel1436 F pulseaudio
  CurrentDesktop: XFCE
  Date: Tue May 31 18:35:18 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=f7d6820f-3da5-44be-9899-a3286c944329
  InstallationDate: Installed on 2016-05-20 (11 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Hewlett-Packard HP Pavilion dm1 Notebook PC
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1611
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 96.3A
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd07/07/2011:svnHewlett-Packard:pnHPPaviliondm1NotebookPC:pvr058911252B0310100:rvnHewlett-Packard:rn1611:rvr96.3A:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dm1 Notebook PC
  dmi.product.version: 058911252B0310100
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1581799] Re: radeon driver hangs : nothing else that static effect on display

magowiz, the issue you are reporting is an upstream one. Could you
please report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO Alex Deucher, and Christian König CC dri-devel)?

Please provide a direct URL to your post to the mailing list when it
becomes available so that it may be tracked.

Thank you for your help.

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

Title:
  radeon driver hangs : nothing else that static effect on display

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi,
  since upgrade from ubuntu 15.10 to 16.04 I was unable to use mine videocard 
due to drop support of fglrx driver (that was working) and due to radeon 
opensource driver not working with my VGA.

  Mine video card:
  $ lspci -nn | grep VGA
  00:01.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Sumo [Radeon HD 6410D] [1002:9645]

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

  I'll attach further files (dmesg.log , version.log, lspci-vnvn.log) .
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   magowiz4930 F...m pulseaudio
   /dev/snd/pcmC0D0p:   magowiz4930 F...m pulseaudio
   /dev/snd/controlC0:  magowiz4930 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=472405e9-ecbe-44ee-9931-9eedcc0a759a
  InstallationDate: Installed on 2012-01-03 (1615 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=acd61f09-2fc9-4a54-bf0b-23f0a297d2e4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-26 (40 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  _MarkForUpload: True
  dmi.bios.date: 12/09/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1003
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F1A55-M LE
  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.:bvr1003:bd12/09/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF1A55-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1618251] onza (amd64) - tests ran: 20, failed: 0

tests ran:  20, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-69.77~14.04.1/onza__3.19.0-69.77~14.04.1__2016-09-09_11-00-00/results-index.html

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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-69.77~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
  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/1618251/+subscriptions

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

[Kernel-packages] [Bug 1618952] Re: Display brightness keys not registered by ~$acpi_listen

2016-09-09 Thread Omadas

Here is the make.log for ndiswrapper during failed kernel upgrade.
Should I open a new bug?

** Attachment added: "Failed kernel upgrade"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1618952/+attachment/4737639/+files/make.log

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

Title:
  Display brightness keys not registered by ~$acpi_listen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brightness keys donot repond, Brightness controls on
  xfce4_power_manager behave as expected.  Either kernel is not
  recognizing the fn+f5/f6 commands or their is a problem with my
  configuration.

  here is the event output of all of my fn+(f keys):
  ~ $ acpi_listen
  button/volumeup VOLUP 0080  K
  button/volumedown VOLDN 0080  K
  button/mute MUTE 0080  K
  button/mute MUTE 0080  K
   PNP0C14:00 00ff 
   PNP0C14:00 00ff 
   PNP0C14:00 00ff 
  button/sleep SBTN 0080 
  button/sleep PNP0C0E:00 0080 0001

  (As a side note, my bios has no configuration options for the function
  keys.)

  (On another note, it is worth noting the fn+f2 does not respond with
  an event calling for airplane mode either, which is not important to
  me but may be important for others, if this is fixed by any solution
  here I will make note, though airplane mode may be a feature request
  and not a bug.)

  I have tried several options in the etc/default/grub file, these include:
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video.use_native_backlight=1"
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash video.use_native_backlight=0"
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor"
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=intel_backlight"
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi="
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_osi=Linux"

  I am using Mint XFCE Sarah (Ubuntu Xenial) 64-bit, xfce4_power_manager
  was tested with all above configurations to both handle and not handle
  display brightness keys.  My Computer is an ASUS model is X540LA.  I
  am attaching a few files to help with this bug report.

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

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

[Kernel-packages] [Bug 1581799] Re: radeon driver hangs : nothing else that static effect on display