date:20160715

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

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

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

Title:
  DRM: intel set pch fifo_underrun_reporting [i915]

Status in linux package in Ubuntu:
  Expired

Bug description:
  I use Samsung NP350V5X-S0IN notebook with intel and AMD graphics with
  Ubuntu 16.04 LTS with Mate 16,04. Very recently i had updated kernel
  due to suspend and wakeup issued and it is cleared now. But however im
  getting an error on bootload as follows:

  [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo 
underrun on pch transcoder A
  [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A 
FIFO underrun

  I tried few methods like customising LSB-RELEASE and rebooting with the 
following file contents:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=15.04
  DISTRIB_CODENAME=wiley
  DISTRIB_DESCRIPTION="Ubuntu 16.04 LTS"
  as found in one 
https://allanbogh.com/2016/01/05/ubuntu-16-04-installing-the-intel-graphics-drivers-using-the-intel-graphics-installer-for-linux/

  It didn't workout for the time being. Is there anything else as required?
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-03 (40 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.4.9-040409-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-03 (40 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  Tags:  xenial
  Uname: Linux 4.4.9-040409-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2016-04-03 (41 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  Tags:  xenial
  Uname: Linux 4.4.9-040409-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1581681] Re: KVM slowed down with aparently no reason.

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

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

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

Title:
  KVM slowed down with aparently no reason.

Status in linux package in Ubuntu:
  Expired

Bug description:
  The server was working perfectly for months, suddenly (yesterday) it
  started to slow down the VMs and now I noticed that the CPU Use is
  very high and a lot of messages on the dmesg.

  I checked if it had any kernel update, but the latest update were from
  last year.

  I will try upgrading the server to 16.04 in a few days if I can't
  solve the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-22-generic 3.19.0-22.22
  ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
  Uname: Linux 3.19.0-22-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri May 13 18:34:48 2016
  HibernationDevice: RESUME=UUID=c4fb9a3e-4d30-4e3b-96d0-404c6707855f
  InstallationDate: Installed on 2015-06-22 (325 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: Intel Corporation S2600CW
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-22-generic 
root=UUID=c6ae046b-62b0-479c-967e-377c7604dd1e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-22-generic N/A
   linux-backports-modules-3.19.0-22-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-07-13 (305 days ago)
  dmi.bios.date: 10/17/2014
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: SE5C610.86B.01.01.0005.101720141054
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: S2600CW
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H44615-351
  dmi.chassis.asset.tag: 
  dmi.chassis.type: 17
  dmi.chassis.vendor: ..
  dmi.chassis.version: ..
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrSE5C610.86B.01.01.0005.101720141054:bd10/17/2014:svnIntelCorporation:pnS2600CW:pvr:rvnIntelCorporation:rnS2600CW:rvrH44615-351:cvn..:ct17:cvr..:
  dmi.product.name: S2600CW
  dmi.product.version: 
  dmi.sys.vendor: Intel Corporation

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

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

[Kernel-packages] [Bug 1572801] Re: Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

2016-07-15 Thread gopinath

Hi guys. I Upgraded to 16.04 2 days back and I am also affected by Memory 
issue. 
I own a Dell Vostro V13 with 2Gb RAM, Intel Cenrino dual Core Proc.
This was working fine on the 14.04.
Now the laptop becomes nearly inoperable as the memory and swap goes to 100% 
when I try to multi task by just opening 2 applications: Firefox Browser and 
Evolution.

Is there a fix/workaround for this issue or do we have to wait till the
.1 release a downgrade to 14.04 till then?

Regards,
Gopinath

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

Title:
  Ubuntu 16.04 Unity desktop uses much more ram than Ubuntu 15.10

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

Bug description:
  Ubuntu 16.04 64bit ISO number 20160420.1
  unity version 7.4.0+16.04.20160415-0ubuntu1
  Ubuntu 16.04 64bit ram usage has increase dramatically over Ubuntu 15.10
  Ubuntu 16.04 ram roughly 1 GB Ubuntu15.10 can be tuned to 420, 450 MB
  Ubuntu 16.04 with unity uses 1GB whereas Kubuntu 16.04 is using 420MB live usb

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.376
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr 21 01:44:22 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor 
Integrated Graphics Controller [1043:8534]
  GsettingsChanges:
   b'org.compiz.core' b'outputs' b"['1920x1080+0+0']"
   b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 
'place', 'regex', 'resize', 'session', 'snap', 'vpswitch', 'wall', 'animation', 
'commands', 'compiztoolbox', 'copytex', 'fade', 'grid', 'imgpng', 'mousepoll', 
'move', 'scale', 'unitymtgrabhandles', 'workarounds', 'expo', 'ezoom', 
'unityshell']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/03/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2004
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2004:bd06/03/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PLUS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Apr 21 01:37:17 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1572801/+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 1602579] Re: the system hangs in the dma driver when reboot or shutdown on a baytrail-m laptop

2016-07-15 Thread Hui Wang

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

** Changed in: hwe-next
   Status: New => Fix Committed

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

Title:
  the system hangs in the dma driver when reboot or shutdown on a
  baytrail-m laptop

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  1. System got hang on reboot of installation phase 1;
  2. Power off system by long-press power button, then power on system again.
  3. System got hang on power off of installation phase 2.

  The hang issue blocked the installation. Can not finish the
  installation procession.

  This bug is for tracking purposes; please do not triage.

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

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

[Kernel-packages] [Bug 1599561] Re: Ubuntu 16.04.01 kdump: IP prefix is missing in the directory name after first dump during kdump over ssh.

This bug was fixed in the package makedumpfile - 1:1.6.0-2

---
makedumpfile (1:1.6.0-2) sid; urgency=medium

  * define_stampdir() : Loop on hostname -I for 5 sec to get IP address
if HOSTTAG=ip. The network stack may not be ready when kdump-config runs.
Give it some time before reverting HOSTTAG to hostname if an IP address
cannot be found. (LP: #1599561)

  * debian/rules : drop the dh_installinit override
Uses a syntax which is no longer supported and generate an error on
install. (LP: #1599491)

 -- Louis Bouchard   Fri, 15 Jul 2016
17:25:33 +0200

** Changed in: makedumpfile (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Ubuntu 16.04.01 kdump: IP prefix is missing in the directory name
  after first dump during kdump over ssh.

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  In Progress

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-06-30 07:12:40 ==
  ---Problem Description---

  During kdump over ssh IP prefix will be present only in first dump,
  subsequent dumps will not have IP in directory name.

  ---Steps to Reproduce---

  1) apt-get install linux-crashdump
  2) increase crashdump size:
  sudo vim /etc/default/grub.d/kexec-tools.cfg

  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel
  =2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M

  3) sudo update-grub ; reboot the machine
  4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools
  5) kdump-config show # should show "ready to dump"
  6) ssh-keygen -t rsa
  7) Edit below parameters in /etc/default/kdump-tools
  SSH="root@"
  SSH_KEY=/root/.ssh/id_rsa
  8)  kdump-config propagate
  9)  kdump-config show
  10) reboot
  11) echo "c" > /proc/sysrq-trigger
  12) verify dump is created in ssh server.
  13) trigger the crash again.

  Logs
  =
  root@ubuntu:/home/ubuntu# uname -a
  Linux ubuntu 4.4.0-26-generic #45-Ubuntu SMP Mon Jun 20 17:27:01 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  dumps on ssh server when 3 crashes are triggered
  
  [root@ltc-fire5 crash]# ls
  192.168.122.25-201606300523
  [root@ltc-fire5 crash]# ls
  192.168.122.25-201606300523  -201606300524
  [root@ltc-fire5 crash]# ls
  192.168.122.25-201606300523  -201606300524  -201606300525
  [root@ltc-fire5 crash]# cd -201606300524
  -bash: cd: -2: invalid option
  cd: usage: cd [-L|[-P [-e]]] [dir]
  [root@ltc-fire5 crash]# cd -- -201606300524
  [root@ltc-fire5 -201606300524]# ls
  dmesg.201606300524  dump.201606300524

  
  == Comment: #8 - Kevin W. Rudd - 2016-07-05 18:23:01 ==

  Canonical,

  The behavior appears to be somewhat intermittent, and it looks as if
  define_stampdir() might be getting called before the network init has
  completed.  If delaying this function is not practical, it might be
  helpful to have define_stampdir() fall back to using just "hostname"
  if "hostname -I" doesn't return any useful information for setting
  THIS_HOST.

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

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

[Kernel-packages] [Bug 1599491] Re: kdump-tools install script uses deprecated syntax

This bug was fixed in the package makedumpfile - 1:1.6.0-2

---
makedumpfile (1:1.6.0-2) sid; urgency=medium

  * define_stampdir() : Loop on hostname -I for 5 sec to get IP address
if HOSTTAG=ip. The network stack may not be ready when kdump-config runs.
Give it some time before reverting HOSTTAG to hostname if an IP address
cannot be found. (LP: #1599561)

  * debian/rules : drop the dh_installinit override
Uses a syntax which is no longer supported and generate an error on
install. (LP: #1599491)

 -- Louis Bouchard   Fri, 15 Jul 2016
17:25:33 +0200

** Changed in: makedumpfile (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  kdump-tools install script uses deprecated syntax

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

Bug description:
  When installing kdump-tools, the apt-get outputs:

  Setting up kdump-tools (1:1.5.9-5) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults

  Full log:

  jayman@jayman-kubuntu:~$ sudo apt-get install kdump-tools
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
crash kexec-tools libdw1 makedumpfile
  The following NEW packages will be installed:
crash kdump-tools kexec-tools libdw1 makedumpfile
  0 upgraded, 5 newly installed, 0 to remove and 10 not upgraded.
  Need to get 0 B/2,962 kB of archives.
  After this operation, 9,379 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Preconfiguring packages ...
  Selecting previously unselected package crash.
  (Reading database ... 235512 files and directories currently installed.)
  Preparing to unpack .../crash_7.1.4-1ubuntu4_amd64.deb ...
  Unpacking crash (7.1.4-1ubuntu4) ...
  Selecting previously unselected package libdw1:amd64.
  Preparing to unpack .../libdw1_0.165-3ubuntu1_amd64.deb ...
  Unpacking libdw1:amd64 (0.165-3ubuntu1) ...
  Selecting previously unselected package makedumpfile.
  Preparing to unpack .../makedumpfile_1%3a1.5.9-5_amd64.deb ...
  Unpacking makedumpfile (1:1.5.9-5) ...
  Selecting previously unselected package kexec-tools.
  Preparing to unpack .../kexec-tools_1%3a2.0.10-1ubuntu2_amd64.deb ...
  Unpacking kexec-tools (1:2.0.10-1ubuntu2) ...
  Selecting previously unselected package kdump-tools.
  Preparing to unpack .../kdump-tools_1%3a1.5.9-5_all.deb ...
  Unpacking kdump-tools (1:1.5.9-5) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for libc-bin (2.23-0ubuntu3) ...
  Processing triggers for systemd (229-4ubuntu6) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  Setting up crash (7.1.4-1ubuntu4) ...
  Setting up libdw1:amd64 (0.165-3ubuntu1) ...
  Setting up makedumpfile (1:1.5.9-5) ...
  Setting up kexec-tools (1:2.0.10-1ubuntu2) ...
  Generating grub configuration file ...
  Found linux image: /boot/vmlinuz-4.4.0-28-generic
  Found initrd image: /boot/initrd.img-4.4.0-28-generic
  Found linux image: /boot/vmlinuz-4.4.0-24-generic
  Found initrd image: /boot/initrd.img-4.4.0-24-generic
  Found memtest86+ image: /boot/memtest86+.elf
  Found memtest86+ image: /boot/memtest86+.bin
  grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your 
device.map.
  Found Windows 7 (loader) on /dev/sda1
  done
  Setting up kdump-tools (1:1.5.9-5) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  Processing triggers for libc-bin (2.23-0ubuntu3) ...
  jayman@jayman-kubuntu:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: kdump-tools 1:1.5.9-5
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Jul  6 08:02:53 2016
  InstallationDate: Installed on 2016-06-16 (19 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: makedumpfile
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool

2016-07-15 Thread Occams Beard

After installing the v4.7-rc7 mainline build kernel I can confirm that
this bug still exists.

I installed the following 3 debs with sudo dpkg -i *.deb:

linux-headers-4.7.0-040700rc7_4.7.0-040700rc7.201607110032_all.deb
linux-headers-4.7.0-040700rc7-generic_4.7.0-040700rc7.201607110032_amd64.deb
linux-image-4.7.0-040700rc7-generic_4.7.0-040700rc7.201607110032_amd64.deb

Next, I rebooted the laptop and confirmed I was running on 4.7 with uname -r:
4.7.0-040700rc7-generic

I used the laptop for a few minutes until the fans came on.  The fans
continued to run, and are still running 30 minutes later.  Here's the
output of lm-sensors showing that the cpu is cool, yet the fans are
spinning away.

dell_smm-virtual-0
Adapter: Virtual device
Processor Fan: 1935 RPM
Processor Fan: 2134 RPM
CPU:+33.0°C  
GPU: +1.0°C  
SODIMM: +45.0°C  


Other thoughts -  I don't know if this is relevant to the fan issue, but in 
powertop under the "idle stats" tab, the CPU package never gets past C2.  This 
is the case with all kernels I've tried.   Perhaps the fan issue is related to 
the screwy skylake power management?  I've attached a text file of the powertop 
idle stats with the 4.7 kernel.


** Attachment added: "powertop-idle-4.7rc7.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602888/+attachment/4701811/+files/powertop-idle-4.7rc7.txt

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

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

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

Title:
  Dell Inspiron 7559 fans do not shut off once started, even when cool

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to
  be an issue with the fan control. When I first boot up the machine the
  fans are off. However, after the laptop warms up under normal usage,
  the fans kick on and then never shut off again.  Even when the CPU
  cools down to below 35c, the fans will continue to run.

  If I suspend the the laptop, and then immediately wake it up again
  then fans are once again off, until it warms up again.  So
  essentially, once the fans start they don't seem to ever shut off.

  Fans seem to work normally under Windows 10.  They turn on as needed,
  and then turn off once the laptop cools down.

  I've tried the various BIOS updates that Dell has released, without
  success. I am currently running Dell's latest BIOS for this laptop
  (v1.1.8)

  Below is the output of lm-sensors showing the fans running when the
  CPU is at a cool 35c

  dell_smm-virtual-0
  Adapter: Virtual device
  Processor Fan: 1925 RPM
  Processor Fan: 2143 RPM
  CPU:+35.0°C  
  GPU: +1.0°C  
  SODIMM: +49.0°C

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob1709 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul 13 19:18:45 2016
  HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77
  InstallationDate: Installed on 2016-07-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Inspiron 7559
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.8
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.1.8
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1603054] Re: FocalTech FocalTech Touchpad freezing as PS/2 mouse in 'ASUS Zenbook UX3030L' after changing touchpad driver

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

Could you please post the results of the following terminal command:
apt policy python-apport
apport-collect 1603054


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

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

Title:
  FocalTech FocalTech Touchpad freezing as PS/2 mouse in 'ASUS Zenbook
  UX3030L' after changing touchpad driver

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have changed from Synaptics to FocalTech in order to use the
  dualfinger scroll, it works but sometimes the Xorg stop working
  (freezing), so I have to change the renderer (Ctrl+Alt+FX) and go back
  to Ctrl+ALt+F7

  
  I have follow the guidelines of the following to submit my bug, 
  DebuggingTouchpadDetection

  
  XUbuntu based on Ubuntu 14.04

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

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

[Kernel-packages] [Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9

H Buus, 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.

Once testing of the latest upstream kernel is complete, please mark this
report Status Confirmed. Please let us know your results.

Thank you for your understanding.

** Tags added: latest-bios-2.06

** Tags added: bisect-done regression-release

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

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

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

Title:
  acpi regression first bad commit
  02b771b64b73226052d6e731a0987db3b47281e9

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I found what I believe is a regression on my Gateway ne570 laptop. It was 
running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I 
installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with 
messages like this:
  Jul 10 17:01:10 buus-ne570 kernel: [   57.741630] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.803775] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.866294] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.928403] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)

  These messages would be repeated several times a second, and then
  pause for several seconds, then start again. I believe they are the
  cause of more sluggish behavior than with the older *Buntu releases.

  I followed the instructions here:
  https://wiki.ubuntu.com/Kernel/KernelBisection
  which lead me to doing "git bisect" on the linux-stable kernel. The result 
lead me to this commit:

  # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI /
  EC: Fix an issue caused by the serialized _Qxx evaluations

  commit 02b771b64b73226052d6e731a0987db3b47281e9
  Author: Lv Zheng 
  Date:   Wed Aug 12 11:12:02 2015 +0800

  ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations

  It is proven that Windows evaluates _Qxx handlers in a parallel way. This
  patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to
  form a separate queue, so that _Qxx evaluations can be queued up on
  different CPUs rather than being queued up on a CPU0 bound queue.
  Event handling related callbacks are also renamed and sorted in this 
patch.

  Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411
  Reported-and-tested-by: Gabriele Mazzotta 
  Signed-off-by: Lv Zheng 
  Signed-off-by: Rafael J. Wysocki 

  The laptop was purchased from tigerdirect. Here's link to specs:
  
http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911

  The laptop appears to be a re-branded Acer Aspire E1-570:

[Kernel-packages] [Bug 1602905] Re: non -working Elan Touchpad

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

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

Title:
  non -working Elan Touchpad

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After a direct install by USB, my Toshiba Satellite Radius P55W-B laptop runs 
ok except for the Elan Touchpad witch dosn't work in any way. I have a 
bluetooth mous workiing OK. I have bin unable to find a driver online.
  Release: 16.04
  Unable to locate package pkgname

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

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

[Kernel-packages] [Bug 1603008] Re: Lockup using nvidia proprietary driver, HP Pavillion Gaming 15-ak008TX

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

To clarify, does this issue occur if you don't have the nvidia
proprietary drivers installed?

** Tags added: bios-outdated-f.80

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

Title:
  Lockup using nvidia proprietary driver, HP Pavillion Gaming 15-ak008TX

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This HP Pavillion Gaming 15-ak008TX has started locking up with the
  4.4.0-28 kernel and the nvidia proprietary driver. It was working fine
  with 4.4.0-24 and all earlier kernels since Xenial release.

  It boots to the login screen, but the system will have completely
  locked within 30 seconds requiring a power cycle. If I switch to a
  text console before that happens, I can use the text console
  indefinitely. When I switch back to the greeter or unity, it will
  shortly lock up.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stub   3711 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 14 16:27:31 2016
  HibernationDevice: RESUME=UUID=dc964c84-fa1f-4004-8a4c-c9626c524a43
  InstallationDate: Installed on 2016-02-26 (138 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224)
  MachineType: HP HP Pavilion Gaming Notebook
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.54
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A9
  dmi.board.vendor: HP
  dmi.board.version: 91.18
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.54:bd09/22/2015:svnHP:pnHPPavilionGamingNotebook:pvrType1ProductConfigId:rvnHP:rn80A9:rvr91.18:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Gaming Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1434136] Re: HP Pavilion 13-b208tu fails to boot with F.26 bios, PSOD

Stuart Bishop, would HP's latest BIOS allow you a boot?

If not, could you please provide the information from
https://wiki.ubuntu.com/DebuggingKernelBoot ?

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

Title:
  HP Pavilion 13-b208tu fails to boot with F.26 bios, PSOD

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  While trying to fix Bug #1432659, I updated the HP Pavilion 13-b208tu bios to 
the latest available on the HP website (F.26):
  
http://support.hp.com/us-en/drivers/selfservice/HP-Pavilion-13-b200-Notebook-PC-series/7527795/model/7597682

  After the update, the laptop no longer boots Ubuntu 14.10 or Ubuntu
  15.04 (Ubuntu 15.04 from the hard drive, Ubuntu 14.10 using a LiveCD).
  The grub menu is available and works, the kernel loads, the initrd
  step works, and then it hangs hard and requires power cycling.

  The required information for a kernel bug report can be found in Bug
  #1432659, from the original shipped F.23 bios. I obviously can't
  attach information with the F.26 bios loaded.

  I can confirm that the bios update worked, and I have repeated it
  twice. HP diagnostics give the system a green light, and I can boot to
  FreeDOS as normal. I'll leave the system unbootable with the F.26 bios
  for a while in case someone can help me diagnose further from grub.

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

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

[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool

Occams Beard, 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.

Once testing of the latest upstream kernel is complete, please mark this
report Status Confirmed. Please let us know your results.

Thank you for your understanding.

** Tags added: latest-bios-1.1.8

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

Title:
  Dell Inspiron 7559 fans do not shut off once started, even when cool

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to
  be an issue with the fan control. When I first boot up the machine the
  fans are off. However, after the laptop warms up under normal usage,
  the fans kick on and then never shut off again.  Even when the CPU
  cools down to below 35c, the fans will continue to run.

  If I suspend the the laptop, and then immediately wake it up again
  then fans are once again off, until it warms up again.  So
  essentially, once the fans start they don't seem to ever shut off.

  Fans seem to work normally under Windows 10.  They turn on as needed,
  and then turn off once the laptop cools down.

  I've tried the various BIOS updates that Dell has released, without
  success. I am currently running Dell's latest BIOS for this laptop
  (v1.1.8)

  Below is the output of lm-sensors showing the fans running when the
  CPU is at a cool 35c

  dell_smm-virtual-0
  Adapter: Virtual device
  Processor Fan: 1925 RPM
  Processor Fan: 2143 RPM
  CPU:+35.0°C  
  GPU: +1.0°C  
  SODIMM: +49.0°C

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob1709 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul 13 19:18:45 2016
  HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77
  InstallationDate: Installed on 2016-07-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Inspiron 7559
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.8
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias:

[Kernel-packages] [Bug 1602743] Re: wifi stops working after xenial upgrade - HP Pavilion 13-b208tu w/ Broadcom BCM43142

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

To advise, the bcmwl proprietary driver is not provided by the open
source linux package.

Despite this, the latest driver for your hardware is available as per
https://launchpad.net/ubuntu/+source/broadcom-sta in
http://cdimage.ubuntu.com/daily-live/current/ . Hence, could you please
test this, and advise to the results?

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

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

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

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

Title:
  wifi stops working after xenial upgrade - HP Pavilion 13-b208tu w/
  Broadcom BCM43142

Status in bcmwl package in Ubuntu:
  Incomplete

Bug description:
  wifi no longer works on this laptop after upgrading to Xenial. I don't
  see any error messages. The wifi device is no longer listed in the
  network manager applet or by ifconfig.

  Per Bug #1434136, this laptop is not using the latest bios availble
  for download, as it has never worked with Linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stub   2235 F pulseaudio
   /dev/snd/controlC0:  stub   2235 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul 13 22:22:54 2016
  HibernationDevice: RESUME=UUID=85d38fc2-ada5-4f5e-83ec-ca176c194dab
  InstallationDate: Installed on 2015-03-13 (488 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Hewlett-Packard HP Pavilion 13 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-07-04 (8 days ago)
  dmi.bios.date: 11/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2340
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 07.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.24:bd11/28/2014:svnHewlett-Packard:pnHPPavilion13NotebookPC:pvr097D12005F0400080:rvnHewlett-Packard:rn2340:rvr07.09:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 13 Notebook PC
  dmi.product.version: 097D12005F0400080
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1434136] Re: HP Pavilion 13-b208tu fails to boot with F.26 bios, PSOD

** Tags added: bios-outdated-f.34

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

Title:
  HP Pavilion 13-b208tu fails to boot with F.26 bios, PSOD

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While trying to fix Bug #1432659, I updated the HP Pavilion 13-b208tu bios to 
the latest available on the HP website (F.26):
  
http://support.hp.com/us-en/drivers/selfservice/HP-Pavilion-13-b200-Notebook-PC-series/7527795/model/7597682

  After the update, the laptop no longer boots Ubuntu 14.10 or Ubuntu
  15.04 (Ubuntu 15.04 from the hard drive, Ubuntu 14.10 using a LiveCD).
  The grub menu is available and works, the kernel loads, the initrd
  step works, and then it hangs hard and requires power cycling.

  The required information for a kernel bug report can be found in Bug
  #1432659, from the original shipped F.23 bios. I obviously can't
  attach information with the F.26 bios loaded.

  I can confirm that the bios update worked, and I have repeated it
  twice. HP diagnostics give the system a green light, and I can boot to
  FreeDOS as normal. I'll leave the system unbootable with the F.26 bios
  for a while in case someone can help me diagnose further from grub.

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

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

[Kernel-packages] [Bug 1602371] Re: Touchpad incorrectly detected as PS/2 mouse in 'HP Pavillion 340G1' after Ubuntu 12.04 upgrade to 14.04.

** Tags added: latest-bios-f.12

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

Title:
  Touchpad incorrectly detected as PS/2 mouse in 'HP Pavillion 340G1'
  after Ubuntu 12.04 upgrade to 14.04.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm currently using Linux 4.2.0-38-generic Kernel.

  
  I adjunct in a .txt the outputs for 
  -dmesg
  -cat /proc/bus/input/devices 

  Regards

  Daniel Ojeda
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  do 3758 F pulseaudio
   /dev/snd/controlC0:  do 3758 F pulseaudio
  CurrentDesktop: Unity
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-stella-yuanli-precise-amd64-20131009-1
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=93204dde-91fd-41de-b63a-8c49d4903331
  InstallationDate: Installed on 2015-07-13 (365 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20131009-06:05
  MachineType: Hewlett-Packard HP 340 G1
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-38-generic 
root=UUID=8fb79e40-a483-431f-ae1f-b6430988c9fd ro quiet splash i8042.reset 
i8042.nomux i8042.nopnp i8042.noloop vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-38.45~14.04.1-generic 4.2.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-38-generic N/A
   linux-backports-modules-4.2.0-38-generic  N/A
   linux-firmware1.127.22
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  trusty
  Uname: Linux 4.2.0-38-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-07-13 (364 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 06/12/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.12
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 21B7
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 46.0B
  dmi.chassis.asset.tag: 5CG4471R2Q
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.12:bd06/12/2014:svnHewlett-Packard:pnHP340G1:pvr099810167:rvnHewlett-Packard:rn21B7:rvrKBCVersion46.0B:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 340 G1
  dmi.product.version: 099810167
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1602632] Re: Focaltech Touchpad not found in devices Asus FX550

Kevin, 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.

Once testing of the latest upstream kernel is complete, please mark this
report Status Confirmed. Please let us know your results.

Thank you for your understanding.

** Tags removed: focaltech missing touchpad
** Tags added: latest-bios-204

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

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

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

Title:
  Focaltech Touchpad not found in devices Asus FX550

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Have been using USB mouse for a few days on my machine. When I was on the 
move switched to my touchpad just to find out it was not working. Checked in 
/proc/bus/input/devices but could not find the focaltech touchpad device that 
was usually there. (It has been working fine for about 6 months up until now).
  I have attached some logs that should help let me know what else you need.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  slugger2317 F pulseaudio
   /dev/snd/controlC1:  slugger2317 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4a99f549-05b6-4992-ba13-de68926939ac
  InstallationDate: Installed on 2016-04-20 (84 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:57b4 Realtek Semiconductor Corp. 
   Bus 001 Device 006: ID 0bb4:0ffe HTC (High Tech Computer Corp.) Desire HD 
(modem mode)
   Bus 001 Device 002: ID 1b1c:1b12 Corsair 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JX
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-64-generic.efi.signed 
root=UUID=e71cf958-4123-4113-88a6-9a127de59c9c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-64.72~14.04.1-generic 3.19.8-ckt22
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-64-generic N/A
   linux-backports-modules-3.19.0-64-generic  N/A
   linux-firmware 1.127.22
  Tags:  trusty
  Uname: Linux 3.19.0-64-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2016-06-23 (20 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/07/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X550JX.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550JX
  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:

[Kernel-packages] [Bug 1588428] Re: PCI bus error on startup while booting into login screen (Kubuntu 16.04)

2016-07-15 Thread Bjorn Helgaas

This looks related to https://bugzilla.kernel.org/show_bug.cgi?id=111601

Is "pci=noaer" (without using "pci=nomsi") sufficient to allow the
system to boot?

If you boot with "pci=noaer", does it still take a long time to boot?
If so, can you collect a dmesg log with timestamps so we can see where
the time is?

** Bug watch added: Linux Kernel Bug Tracker #111601
   http://bugzilla.kernel.org/show_bug.cgi?id=111601

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

Title:
  PCI bus error on startup while booting into login screen (Kubuntu
  16.04)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  With a HP Pavilion Notebook - 15-ab549tx, and Kubuntu 16.04, the problem is 
on startup error messages show up before the login screen as per attached 
screenshot:
  https://launchpadlibrarian.net/263296837/screenshot.jpg

  At times it is just stops at this screen and doesn't move to the login
  screen. Or while it shuts down it stops at this screen.

  WORKAROUND: Adding kernel boot parameters:
  pci=nomsi
  pci=noaer

  stop the messages from showing on startup, but it takes 2.5 minutes to
  boot.

  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
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abhishek   1332 F pulseaudio
  CurrentDesktop: KDE
  Date: Thu Jun  2 21:27:21 2016
  HibernationDevice: RESUME=UUID=bf42c497-2871-4fcb-9c6f-ea792ccf35ab
  InstallationDate: Installed on 2016-05-13 (19 days ago)
  InstallationMedia: Kubuntu 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 0bda:b006 Realtek Semiconductor Corp.
   Bus 001 Device 004: ID 04ca:0060 Lite-On Technology Corp.
   Bus 001 Device 002: ID 04f2:b50d Chicony Electronics Co., Ltd
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=85cd7db1-5379-4a11-84d8-0b7ed7989962 ro quiet splash pci=nomsi 
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/07/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.78
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80A4
  dmi.board.vendor: HP
  dmi.board.version: 91.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.78:bd03/07/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn80A4:rvr91.1D:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

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

2016-07-15 Thread bugproxy

--- Comment From ru...@us.ibm.com 2016-07-15 18:14 EDT---
FYI Canonical:  This is an updated and upstream patch to address the issue 
originally documented in  LP Bug 1560514.

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

Title:
  Hotplug remove and re-add adds PCI adapter to next PCI domain (PCI)

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #26 - Guilherme Guaglianoni Piccoli  - 
2016-07-15 16:26:38 ==
  When performing hotplug operations in PowerPC currently, if we remove a PHB 
and re-add it later, its domain address is incremented. An example below (drmgr 
is the tool we use in PowerPC to perform this operation):

  
  (i) $>  lspci
  :60:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 
10 Gigabit Ethernet
  :60:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 
10 Gigabit Ethernet

  (ii) $>  drmgr -c phb -s "PHB 20" -r  # removing a PHB

  (iii) $>  lspci #empty

  (iv) $>  drmgr -c phb -s "PHB 20" -a  # re-adding the PHB

  (v) $>  lspci
  0001:60:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 
10 Gigabit Ethernet
  0001:60:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 
10 Gigabit Ethernet

  
  This behavior is harmful when kernel is using network predictable naming for 
interfaces, for example, since after the PHB re-add, the PCI address of NIC 
functions changes, and so the interfaces' naming also change. Recently, a patch 
was merged to powerpc-next to avoid this situation, by relating the PCI domain 
number with device-tree properties. With the patch, the above steps (i) and (v) 
present the same output for lspci.

  We want to ask Canonical to merge the patch in Ubuntu Xenial's kernel,
  since it will solve multiple bugs we've experienced by performing NIC
  hotplug - the commit is present on powerpc-next under the commit-id
  63a72284b15.

  A link to the patch:
  
https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/commit/?id=63a72284b159c569ec52f380c9

  Thanks in advance,


  Guilherme

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

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

[Kernel-packages] [Bug 1584597] Re: Hyper-V Memory Ballooning re-broken in 16.04

2016-07-15 Thread Alex Ng

> Committed_AS: 7291440 kB

The amount of committed memory reported by meminfo is about 7GB. So it
shouldn't be surprising to see that the demand as seen by Hyper-V is
also high.

In general, the Hyper-V demand is calculated as Committed_AS value plus
some buffer(roughly 700MB if you have 8GB of total ram). So for the
above meminfo report, I would expect Hyper-V to show that about ~7-8GB
is in use.

Can you show /proc/meminfo when things have calmed down (as well as a
screenshot of what Hyper-V is showing at the same time)?

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

Title:
  Hyper-V Memory Ballooning re-broken in 16.04

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

Bug description:
  Regression: #1294283 fixed memory ballooning in Hyper-V in 14.04, but
  the bug has returned in 16.04.

  
  Steps to reproduce:

  1. Create Gen2 Hyper-V VM
  2. Install Ubuntu 16.04
  3. modprobe hv_balloon
  Memory usage according to Hyper-V Manager will not change

  
  This has been reproduced on 2 fresh Ubuntu Server 16.04 instances.

  I installed linux-generic-xenial on a 14.04 instance, rebooted,
  modprobe'd hv_balloon and memory usage in Hyper-V Manager reduced to
  the correct level.

  Environment:
  Host: Windows NanoServer 2016

  Ubuntu Server 16.04 version_signature: `Ubuntu 4.4.0-21.37-generic 4.4.6`
  Ubuntu Server 14.04 version_signature: `Ubuntu 4.4.0-22.40~14.04.1-generic 
4.4.8`

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

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

[Kernel-packages] [Bug 1603574] [NEW] Hotplug remove and re-add adds PCI adapter to next PCI domain (PCI)

2016-07-15 Thread bugproxy

Public bug reported:

== Comment: #26 - Guilherme Guaglianoni Piccoli  - 
2016-07-15 16:26:38 ==
When performing hotplug operations in PowerPC currently, if we remove a PHB and 
re-add it later, its domain address is incremented. An example below (drmgr is 
the tool we use in PowerPC to perform this operation):


(i) $>  lspci
:60:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 10 
Gigabit Ethernet
:60:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 10 
Gigabit Ethernet

(ii) $>  drmgr -c phb -s "PHB 20" -r  # removing a PHB

(iii) $>  lspci #empty

(iv) $>  drmgr -c phb -s "PHB 20" -a  # re-adding the PHB

(v) $>  lspci
0001:60:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 10 
Gigabit Ethernet
0001:60:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 10 
Gigabit Ethernet


This behavior is harmful when kernel is using network predictable naming for 
interfaces, for example, since after the PHB re-add, the PCI address of NIC 
functions changes, and so the interfaces' naming also change. Recently, a patch 
was merged to powerpc-next to avoid this situation, by relating the PCI domain 
number with device-tree properties. With the patch, the above steps (i) and (v) 
present the same output for lspci.

We want to ask Canonical to merge the patch in Ubuntu Xenial's kernel,
since it will solve multiple bugs we've experienced by performing NIC
hotplug - the commit is present on powerpc-next under the commit-id
63a72284b15.

A link to the patch:
https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/commit/?id=63a72284b159c569ec52f380c9

Thanks in advance,


Guilherme

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-136437 severity-high 
targetmilestone-inin16041

** Tags added: architecture-ppc64le bugnameltc-136437 severity-high
targetmilestone-inin16041

** Changed in: ubuntu
 Assignee: (unassigned) => Taco Screen team (taco-screen-team)

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

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

Title:
  Hotplug remove and re-add adds PCI adapter to next PCI domain (PCI)

Status in linux package in Ubuntu:
  New

Bug description:
  == Comment: #26 - Guilherme Guaglianoni Piccoli  - 
2016-07-15 16:26:38 ==
  When performing hotplug operations in PowerPC currently, if we remove a PHB 
and re-add it later, its domain address is incremented. An example below (drmgr 
is the tool we use in PowerPC to perform this operation):

  
  (i) $>  lspci
  :60:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 
10 Gigabit Ethernet
  :60:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 
10 Gigabit Ethernet

  (ii) $>  drmgr -c phb -s "PHB 20" -r  # removing a PHB

  (iii) $>  lspci #empty

  (iv) $>  drmgr -c phb -s "PHB 20" -a  # re-adding the PHB

  (v) $>  lspci
  0001:60:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 
10 Gigabit Ethernet
  0001:60:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 
10 Gigabit Ethernet

  
  This behavior is harmful when kernel is using network predictable naming for 
interfaces, for example, since after the PHB re-add, the PCI address of NIC 
functions changes, and so the interfaces' naming also change. Recently, a patch 
was merged to powerpc-next to avoid this situation, by relating the PCI domain 
number with device-tree properties. With the patch, the above steps (i) and (v) 
present the same output for lspci.

  We want to ask Canonical to merge the patch in Ubuntu Xenial's kernel,
  since it will solve multiple bugs we've experienced by performing NIC
  hotplug - the commit is present on powerpc-next under the commit-id
  63a72284b15.

  A link to the patch:
  
https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/commit/?id=63a72284b159c569ec52f380c9

  Thanks in advance,


  Guilherme

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

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

[Kernel-packages] [Bug 1603574] [NEW] Hotplug remove and re-add adds PCI adapter to next PCI domain (PCI)

You have been subscribed to a public bug:

== Comment: #26 - Guilherme Guaglianoni Piccoli  - 
2016-07-15 16:26:38 ==
When performing hotplug operations in PowerPC currently, if we remove a PHB and 
re-add it later, its domain address is incremented. An example below (drmgr is 
the tool we use in PowerPC to perform this operation):


(i) $>  lspci
:60:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 10 
Gigabit Ethernet
:60:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 10 
Gigabit Ethernet

(ii) $>  drmgr -c phb -s "PHB 20" -r  # removing a PHB

(iii) $>  lspci #empty

(iv) $>  drmgr -c phb -s "PHB 20" -a  # re-adding the PHB

(v) $>  lspci
0001:60:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 10 
Gigabit Ethernet
0001:60:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 10 
Gigabit Ethernet


This behavior is harmful when kernel is using network predictable naming for 
interfaces, for example, since after the PHB re-add, the PCI address of NIC 
functions changes, and so the interfaces' naming also change. Recently, a patch 
was merged to powerpc-next to avoid this situation, by relating the PCI domain 
number with device-tree properties. With the patch, the above steps (i) and (v) 
present the same output for lspci.

We want to ask Canonical to merge the patch in Ubuntu Xenial's kernel,
since it will solve multiple bugs we've experienced by performing NIC
hotplug - the commit is present on powerpc-next under the commit-id
63a72284b15.

A link to the patch:
https://git.kernel.org/cgit/linux/kernel/git/powerpc/linux.git/commit/?id=63a72284b159c569ec52f380c9

Thanks in advance,


Guilherme

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
 Status: New


** Tags: architecture-ppc64le bugnameltc-136437 severity-high 
targetmilestone-inin16041
-- 
Hotplug remove and re-add adds PCI adapter to next PCI domain (PCI)
https://bugs.launchpad.net/bugs/1603574
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1568729] Re: divide error: 0000 [#1] SMP in task_numa_migrate - handle_mm_fault

2016-07-15 Thread youshotwhointhatwhatnow

According to this message in the ceph thread those three patches are not
sufficient:

https://www.mail-archive.com/ceph-users@lists.ceph.com/msg30390.html

In a follow up Stefan Priebe mentions he has about 20 other patches
applied, and that must have contributed to having the problem solved on
his systems:

https://www.mail-archive.com/ceph-users@lists.ceph.com/msg30392.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/1568729

Title:
  divide error:  [#1] SMP in task_numa_migrate - handle_mm_fault

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

Bug description:
  While running qemu 2.5 on a trusty host running 4.4.0-15.31~14.04.1
  the host system has crashed (load > 200) 3 times in the last 3 days.

  Always with this stack trace:

  Apr  9 19:01:09 cnode9.0 kernel: [197071.195577] divide error:  [#1] SMP 
  Apr  9 19:01:09 cnode9.0 kernel: [197071.195633] Modules linked in: vhost_net 
vhost macvtap macvlan arc4 md4 nls_utf8 ci
  fs nfnetlink_queue nfnetlink xt_CHECKSUM xt_nat iptable_nat nf_nat_ipv4 
xt_NFQUEUE xt_CLASSIFY ip6table_mangle sch_sfq sch_htb veth dccp_diag
   dccp tcp_diag udp_diag inet_diag unix_diag af_packet_diag netlink_diag 
ebtable_filter ebtables nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_fil
  ter ip6_tables iptable_mangle xt_CT iptable_raw xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack iptable_filter ip_tables x_tables dum
  my bridge stp llc ipmi_ssif ipmi_devintf intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm dcdbas irqbypass crct10dif_p
  clmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper 
ablk_helper cryptd joydev input_leds nf_nat_ftp sb_edac nf_conntrack_ftp e
  dac_core cdc_ether nf_nat_pptp usbnet nf_conntrack_pptp mii nf_nat_proto_gre 
lpc_ich nf_nat_sip ioatdma nf_nat nf_conntrack_sip nfsd ipmi_si 
  8250_fintek nf_conntrack_proto_gre ipmi_msghandler acpi_pad wmi shpchp 
nf_conntrack acpi_power_meter mac_hid auth_rpcgss nfs_acl bonding nfs 
  lp lockd parport grace sunrpc fscache tcp_htcp xfs btrfs hid_generic usbhid 
hid raid10 raid456 async_raid6_recov async_memcpy async_pq async_
  xor async_tx xor ixgbe raid6_pq libcrc32c igb vxlan raid1 i2c_algo_bit 
ip6_udp_tunnel dca udp_tunnel ahci raid0 ptp libahci megaraid_sas mult
  ipath pps_core mdio linear fjes
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197014] CPU: 13 PID: 3147726 Comm: 
ceph-osd Not tainted 4.4.0-15-generic #31~14
  .04.1-Ubuntu
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197085] Hardware name: Dell Inc. 
PowerEdge R720/0XH7F2, BIOS 2.5.2 01/28/2015
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197154] task: 88252be1ee00 ti: 
8824fc0d4000 task.ti: 8824fc0d4000
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197221] RIP: 
0010:[]  [] task_numa_find_cpu+0x238/0x700
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197300] RSP: :8824fc0d7ba8  
EFLAGS: 00010257
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197340] RAX:  RBX: 
8824fc0d7c48 RCX: 
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197406] RDX:  RSI: 
88479f18 RDI: 884782a47600
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197473] RBP: 8824fc0d7c10 R08: 
000102eea157 R09: 01a8
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197540] R10: 0002404b R11: 
023f R12: 88238093
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197606] R13: 0008 R14: 
008c R15: 0124
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197673] FS:  7f19aab5b700() 
GS:88479f18() knlGS:
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197741] CS:  0010 DS:  ES:  
CR0: 80050033
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197782] CR2: 25469600 CR3: 
0023846bc000 CR4: 000426e0
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197848] Stack:
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197880]  817425fb 
8829af3e9e00 00f6 88252be1ee00
  Apr  9 19:01:09 cnode9.0 kernel: [197071.197965]  008d 
0225 00016d40 008d
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198047]  88252be1ee00 
01ad 8824fc0d7c48 00e1
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198132] Call Trace:
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198172]  [] ? 
tcp_schedule_loss_probe+0x12b/0x1b0
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198219]  [] 
task_numa_migrate+0x4a0/0x930
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198264]  [] ? 
release_sock+0x117/0x160
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198306]  [] 
numa_migrate_preferred+0x79/0x80
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198350]  [] 
task_numa_fault+0x91d/0xcc0
  Apr  9 19:01:09 cnode9.0 kernel: [197071.198395]  [] ? 
mpol_misplaced+0x14e/0x190
  Apr  9

[Kernel-packages] [Bug 1602726] Re: nvme - reset_controller is not working after adapter's firmware upgrade (adapter quirk is needed)

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

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

** Changed in: linux (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  nvme - reset_controller is not working after adapter's firmware
  upgrade (adapter quirk is needed)

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #16 - Guilherme Guaglianoni Piccoli  - 
2016-07-12 15:46:17 ==
  NVMe adapters provide an interface to reset the controller after a firmware 
(aka microcode) activation, so the new firmware can be used without rebooting 
the whole system, for example.

  To achieve this, firstly one activate the firmware with the command:
  "nvme fw-activate -a 2 -s 2 /dev/nvme0".

  And then, one can perform the reset right after the activate command succeed:
  "echo 1 > /sys/class/nvme/nvme0/reset_controller".

  
  The issue: in NVMe adapter from HGST vendor (PCI identification == 1c58:0003) 
this reset_controller feature does not work in recent kernels. The main reason 
is that the adapter is not dealing well with disabling the controller in the 
reset feature instead of shutdown it (as done in older kernels). To perform a 
successful reset, we need to delay 2 seconds before checking a specific bit 
during the reset process.

  This delay was implemented as a per-device quirk in the nvme driver,
  and is accepted upstream. Currently, it's present on Jens Axboe kernel
  tree, ready to be merged on upstream 4.8 merge window.

  We want to request the quirk's merge in Xenial's kernel. Below, the
  commit information on Axboe's tree:

  54adc01055b7 ("nvme/quirk: Add a delay before checking for adapter
  readiness")

  Link: https://git.kernel.org/cgit/linux/kernel/git/axboe/linux-
  
block.git/commit/?h=for-4.8/drivers=54adc01055b75ec8769c5a36574c7a0895c0c0b2


  Thanks in advance,

  Guilherme

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

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

[Kernel-packages] [Bug 1603449] Re: [LTCTest][Opal][OP820] Machine crashed with Oops: Kernel access of bad area, sig: 11 [#1] while executing Froze PE Error injection

** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)

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

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

** Changed in: linux (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  [LTCTest][Opal][OP820] Machine crashed with Oops: Kernel access of bad
  area, sig: 11 [#1] while executing Froze PE Error injection

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2016-07-13 
01:28:56 ==
  ---Problem Description---
  Machine crashed with Oops: Kernel access of bad area, sig: 11 [#1]
   
  ---uname output---
  Linux ltc-garri2 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  root@ltc-garri2:~# lspci
  :00:00.0 PCI bridge: IBM Device 03dc
  :01:00.0 Infiniband controller: Mellanox Technologies MT27600 [Connect-IB]
  0001:00:00.0 PCI bridge: IBM Device 03dc
  0002:00:00.0 PCI bridge: IBM Device 03dc
  0002:01:00.0 3D controller: NVIDIA Corporation Device 15fe (rev a1)
  0003:00:00.0 PCI bridge: IBM Device 03dc
  0004:00:00.0 PCI bridge: IBM Device 03dc
  0005:00:00.0 PCI bridge: IBM Device 03dc
  0005:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:02.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:03.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:02:04.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
  0005:03:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 
xHCI Host Controller (rev 02)
  0005:04:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 
x2 4-port SATA 6 Gb/s Controller (rev 11)
  0005:05:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge 
(rev 03)
  0005:06:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED 
Graphics Family (rev 30)
  0005:07:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5718 
Gigabit Ethernet PCIe (rev 10)
  0005:07:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5718 
Gigabit Ethernet PCIe (rev 10)
  0006:00:00.0 PCI bridge: IBM Device 03dc
  0006:01:00.0 3D controller: NVIDIA Corporation Device 15fe (rev a1)
  0007:00:00.0 PCI bridge: IBM Device 03dc
  0008:00:00.0 Bridge: IBM Device 04ea
  0008:00:00.1 Bridge: IBM Device 04ea
  0008:00:01.0 Bridge: IBM Device 04ea
  0008:00:01.1 Bridge: IBM Device 04ea
  0009:00:00.0 Bridge: IBM Device 04ea
  0009:00:00.1 Bridge: IBM Device 04ea
  0009:00:01.0 Bridge: IBM Device 04ea
  0009:00:01.1 Bridge: IBM Device 04ea
   

   
  Machine Type = P8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Install a P8 Open Power 8335-GTB Hardware with Ubuntu 16.04.1.
  Then execute the Frozen PE error injection tests as shown below:

  root@ltc-garri2:~# lspci | grep -i 0004:00:00.0
  0004:00:00.0 PCI bridge: IBM Device 03dc
  root@ltc-garri2:~# cat /proc/powerpc/eeh | tail -n 1
  eeh_slot_resets=0

  
  root@ltc-garri2:~# lspci | grep -i 0004:00:00.0
  0004:00:00.0 PCI bridge: IBM Device 03dc
  root@ltc-garri2:~# cat /proc/powerpc/eeh | tail -n 1
  eeh_slot_resets=0
  root@ltc-garri2:~# echo 0:0:4:0:0 > 
/sys/kernel/debug/powerpc/PCI0004/err_injct && lspci -ns 0004:00:00.0; echo $?
  0004:00:00.0 0604: 1014:03dc
  0

  Immediately the kernel crashes with a Oops Message.
   
  Contact Information = pavsu...@in.ibm.com 
   
  Stack trace output:
   [  289.297946] Call Trace:
  [  289.297969] [c00feeb8b9e0] [c0083c78] pnv_eeh_reset+0x58/0x170 
(unreliable)
  [  289.298042] [c00feeb8ba60] [c0038250] eeh_reset_pe+0xb0/0x1c0
  [  289.298105] [c00feeb8bb00] [c0af444c] 
eeh_reset_device+0xd8/0x228
  [  289.298165] [c00feeb8bba0] [c003c520] 
eeh_handle_normal_event+0x390/0x440
  [  289.298234] [c00feeb8bc20] [c003c9c4] 
eeh_handle_event+0x184/0x370
  [  289.298304] [c00feeb8bcd0] [c003cd88] 
eeh_event_handler+0x1d8/0x1e0
  [  289.298374] [c00feeb8bd80] [c00e6420] kthread+0x110/0x130
  [  289.298434] [c00feeb8be30] [c0009538] 
ret_from_kernel_thread+0x5c/0xa4
  [  289.298501] Instruction dump:
  [  289.298531] 6000 813f ebdf0010 792affe3 408200d4 e95e0250 812a000c 
2f890002
  [  289.298630] 419e0054 7fe3fb78 4bfb70c5 6000  2fa9 
419e00dc e9290010

   
  Oops output:
   [

[Kernel-packages] [Bug 1603449] [NEW] [LTCTest][Opal][OP820] Machine crashed with Oops: Kernel access of bad area, sig: 11 [#1] while executing Froze PE Error injection

You have been subscribed to a public bug:

== Comment: #0 - PAVAMAN SUBRAMANIYAM  - 2016-07-13 
01:28:56 ==
---Problem Description---
Machine crashed with Oops: Kernel access of bad area, sig: 11 [#1]
 
---uname output---
Linux ltc-garri2 4.4.0-30-generic #49-Ubuntu SMP Fri Jul 1 10:00:36 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
 
---Additional Hardware Info---
root@ltc-garri2:~# lspci
:00:00.0 PCI bridge: IBM Device 03dc
:01:00.0 Infiniband controller: Mellanox Technologies MT27600 [Connect-IB]
0001:00:00.0 PCI bridge: IBM Device 03dc
0002:00:00.0 PCI bridge: IBM Device 03dc
0002:01:00.0 3D controller: NVIDIA Corporation Device 15fe (rev a1)
0003:00:00.0 PCI bridge: IBM Device 03dc
0004:00:00.0 PCI bridge: IBM Device 03dc
0005:00:00.0 PCI bridge: IBM Device 03dc
0005:01:00.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
0005:02:01.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
0005:02:02.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
0005:02:03.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
0005:02:04.0 PCI bridge: PLX Technology, Inc. PEX 8718 16-Lane, 5-Port PCI 
Express Gen 3 (8.0 GT/s) Switch (rev ab)
0005:03:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI 
Host Controller (rev 02)
0005:04:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 
x2 4-port SATA 6 Gb/s Controller (rev 11)
0005:05:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 
03)
0005:06:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics 
Family (rev 30)
0005:07:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5718 
Gigabit Ethernet PCIe (rev 10)
0005:07:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5718 
Gigabit Ethernet PCIe (rev 10)
0006:00:00.0 PCI bridge: IBM Device 03dc
0006:01:00.0 3D controller: NVIDIA Corporation Device 15fe (rev a1)
0007:00:00.0 PCI bridge: IBM Device 03dc
0008:00:00.0 Bridge: IBM Device 04ea
0008:00:00.1 Bridge: IBM Device 04ea
0008:00:01.0 Bridge: IBM Device 04ea
0008:00:01.1 Bridge: IBM Device 04ea
0009:00:00.0 Bridge: IBM Device 04ea
0009:00:00.1 Bridge: IBM Device 04ea
0009:00:01.0 Bridge: IBM Device 04ea
0009:00:01.1 Bridge: IBM Device 04ea
 

 
Machine Type = P8 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 Install a P8 Open Power 8335-GTB Hardware with Ubuntu 16.04.1.
Then execute the Frozen PE error injection tests as shown below:

root@ltc-garri2:~# lspci | grep -i 0004:00:00.0
0004:00:00.0 PCI bridge: IBM Device 03dc
root@ltc-garri2:~# cat /proc/powerpc/eeh | tail -n 1
eeh_slot_resets=0


root@ltc-garri2:~# lspci | grep -i 0004:00:00.0
0004:00:00.0 PCI bridge: IBM Device 03dc
root@ltc-garri2:~# cat /proc/powerpc/eeh | tail -n 1
eeh_slot_resets=0
root@ltc-garri2:~# echo 0:0:4:0:0 > /sys/kernel/debug/powerpc/PCI0004/err_injct 
&& lspci -ns 0004:00:00.0; echo $?
0004:00:00.0 0604: 1014:03dc
0

Immediately the kernel crashes with a Oops Message.
 
Contact Information = pavsu...@in.ibm.com 
 
Stack trace output:
 [  289.297946] Call Trace:
[  289.297969] [c00feeb8b9e0] [c0083c78] pnv_eeh_reset+0x58/0x170 
(unreliable)
[  289.298042] [c00feeb8ba60] [c0038250] eeh_reset_pe+0xb0/0x1c0
[  289.298105] [c00feeb8bb00] [c0af444c] eeh_reset_device+0xd8/0x228
[  289.298165] [c00feeb8bba0] [c003c520] 
eeh_handle_normal_event+0x390/0x440
[  289.298234] [c00feeb8bc20] [c003c9c4] 
eeh_handle_event+0x184/0x370
[  289.298304] [c00feeb8bcd0] [c003cd88] 
eeh_event_handler+0x1d8/0x1e0
[  289.298374] [c00feeb8bd80] [c00e6420] kthread+0x110/0x130
[  289.298434] [c00feeb8be30] [c0009538] 
ret_from_kernel_thread+0x5c/0xa4
[  289.298501] Instruction dump:
[  289.298531] 6000 813f ebdf0010 792affe3 408200d4 e95e0250 812a000c 
2f890002
[  289.298630] 419e0054 7fe3fb78 4bfb70c5 6000  2fa9 419e00dc 
e9290010

 
Oops output:
 [  289.294622] EEH: Frozen PE#0 on PHB#4 detected
[  289.294785] EEH: PE location: N/A, PHB location: N/A
[  289.295598] EEH: This PCI device has failed 1 times in the last hour
[  289.295600] EEH: Notify device drivers to shutdown
[  289.295605] EEH: Collect temporary log
[  289.295632] EEH: of node=0004:00:00:0
[  289.295635] EEH: PCI device/vendor: 03dc1014
[  289.295638] EEH: PCI cmd/status register: 00100106
[  289.295641] EEH: Bridge secondary status: 
[  289.295644] EEH: Bridge control: 0002
[  289.295645] EEH: PCI-E capabilities and status follow:
[  289.295654] EEH: PCI-E 00: 00420010 8002 0040 00300103
[  289.295661] EEH: PCI-E 10: 01010008   00010010
[  289.295664] EEH: PCI-E 20: 
[  289.295665] EEH: PCI-E AER capability register set follows:
[

[Kernel-packages] [Bug 1211102] Re: Get rid of 0.5s latency when playing audio over Bluetooth with A2DP

2016-07-15 Thread Niklas Keller

Same issue here. More or less often small disruptions. Seems like those
add up and create the latency. Currently using Ubuntu 15.10. Speaker
works totally fine with my phone.

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

Title:
  Get rid of 0.5s latency when playing audio over Bluetooth with A2DP

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:  Ubuntu 13.04
  Release:  13.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  bluez:
Instalados: 4.101- 0ubuntu8b1
Candidato:  4.101-0ubuntu8b1
Tabla de versión:
   *** 4.101-0ubuntu8b1 0
  500 http://es.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen
  The audio always is sync when i listen music on my bluetooth device 
  If i listen music or have a videoconference with skype.. it receive audio 
perfectly without delay.

  4) What happened instead
   I experience a half a second delay when playing audio over Bluetooth with 
A2DP.
  This makes watching movies not possible as the sound is not synchronised with 
the video.

  + If i listen music, then stop about 5 minutes and then restart to listen 
music, it gets work bad.
  + If i get a skype videoconference, it gets too much delay.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: bluez 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4
  Uname: Linux 3.8.0-27-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Mon Aug 12 01:24:24 2013
  InstallationDate: Installed on 2013-07-13 (29 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK Computer Inc. UX31E
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic 
root=UUID=89d221ec-829a-456e-963d-ec7ac2c7d47d ro 
crashkernel=384M-2G:64M,2G-:128M quiet splash rootfstype=ext4 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX31E.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX31E
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX31E.210:bd12/26/2011:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: UX31E
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 74:2F:68:CE:17:57  ACL MTU: 1022:8  SCO MTU: 183:5
UP RUNNING PSCAN 
RX bytes:407502 acl:14820 sco:0 events:8796 errors:0
TX bytes:7391611 acl:8717 sco:0 commands:45 errors:0

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

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

[Kernel-packages] [Bug 1161962] Re: XPS 13 wakes up from suspend spontaneously

2016-07-15 Thread JosephE

Same problem with XPS 13 2016 (i5 processor, 8gb ram, 128gb hard drive).
I am dual booting with W10 using efi. Cinnamon desktop environment.

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

Title:
  XPS 13 wakes up from suspend spontaneously

Status in Dell Sputnik:
  In Progress
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My XPS 13 wakes up from suspend by itself. This is very annoying and 
potentially dangerous since it happens while the computer is its sleeve/bag.
  Can't tell from the pm-suspend and dmesg what causes the behavior so please 
let me know what logs you need to investigate it and I will provide them.

  Further note: It seems like the spontaneous wake up is happening
  around 40 minutes after suspend every time it occurs. However, the
  spontaneous wake up does not occur every time.

  Running Xubuntu 12.10 with the following Sputnik Kernel: 
  3.5.0-26-generic #42+kamal15~DellXPS-Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1161962/+subscriptions

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

[Kernel-packages] [Bug 1602579] Re: the system hangs in the dma driver when reboot or shutdown on a baytrail-m laptop

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

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

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

Title:
  the system hangs in the dma driver when reboot or shutdown on a
  baytrail-m laptop

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  1. System got hang on reboot of installation phase 1;
  2. Power off system by long-press power button, then power on system again.
  3. System got hang on power off of installation phase 2.

  The hang issue blocked the installation. Can not finish the
  installation procession.

  This bug is for tracking purposes; please do not triage.

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

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

[Kernel-packages] [Bug 1602524] Re: [LTC-Test] - NMI watchdog Bug and call traces when trinity is executed.

** Package changed: kernel-package (Ubuntu) => linux (Ubuntu)

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

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

** Changed in: linux (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  [LTC-Test] - NMI watchdog Bug and call traces when trinity is
  executed.

Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Santhosh G  ==
  Problem Statement:
  NMI watchdog bug and call traces occurs when trinity is executed.

  Environment:
  P8 PowerVM Lpar

  uname o/p:
  uname -a
  Linux tuleta4u-lp5 4.4.0-11-generic #26-Ubuntu SMP Sat Mar 5 14:21:51 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux

  Steps to reproduce:

  1) Install ubuntu 16.04 in a PowerVM LPAR.
  2) Download trinity-1.5 and set up ./configure.sh;make;make install
  3)Execute trinity as 
 './trinity --dangerous'

  The test runs for more than one hour and trinity gets killed with call
  traces:

  [19744.229979] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 21s! 
[trinity-c3:26544]
  [19744.229991] Modules linked in: hidp hid bnep rfcomm l2tp_ppp l2tp_netlink 
l2tp_core ip6_udp_tunnel udp_tunnel af_key mpls_router llc2 nfnetlink dn_rtmsg 
xfrm_user xfrm_algo can_raw crypto_user can_bcm cmtp kernelcapi 
scsi_transport_iscsi sctp libcrc32c nfc af_alg caif_socket caif phonet af_rxrpc 
bluetooth can pppoe pppox irda crc_ccitt atm appletalk ipx p8023 p8022 psnap 
llc pseries_rng rtc_generic autofs4 ibmvscsi ibmveth
  [19744.230024] CPU: 3 PID: 26544 Comm: trinity-c3 Not tainted 
4.4.0-11-generic #26-Ubuntu
  [19744.230026] task: cae87e60 ti: cae24000 task.ti: 
cae24000
  [19744.230028] NIP: c03fac78 LR: c03fabfc CTR: 
c039ef10
  [19744.230029] REGS: cae27980 TRAP: 0901   Not tainted  
(4.4.0-11-generic)
  [19744.230030] MSR: 80009033   CR: 2400  
XER: 2000
  [19744.230035] CFAR: c03fae6c SOFTE: 1
 GPR00: c03fabfc cae27c00 c15a3b00 
c000f7f03ba8
 GPR04: 0e02adcb cae27cb0  

 GPR08: 8000  c000ef886000 
c0af0870
 GPR12: 2400 ce7f1c80
  [19744.230045] NIP [c03fac78] ext4_es_lookup_extent+0xc8/0x2c0
  [19744.230047] LR [c03fabfc] ext4_es_lookup_extent+0x4c/0x2c0
  [19744.230048] Call Trace:
  [19744.230050] [cae27c00] [c03fabfc] 
ext4_es_lookup_extent+0x4c/0x2c0 (unreliable)
  [19744.230053] [cae27c50] [c03a6f18] 
ext4_map_blocks+0x78/0x610
  [19744.230055] [cae27d10] [c039f14c] ext4_llseek+0x23c/0x3f0
  [19744.230057] [cae27de0] [c02e02a8] SyS_lseek+0xe8/0x130
  [19744.230060] [cae27e30] [c0009204] system_call+0x38/0xb4
  [19744.230061] Instruction dump:
  [19744.230062] 2fa9 409effec e93e0028 3b80 e9490458 e92a0440 39290001 
f92a0440
  [19744.230065] 7c2004ac 7d20d828 3129 7d20d92d <40c2fff4> 6000 
7f83e378 38210050

  
  == Comment: #8 - Santhosh G  ==

  Tried the scenario as given in 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=128126#c26
  -
  # Create a 624GiB file; Mostly filled with holes though
  $ dd if=/dev/zero of=file-0.bin bs=1M count=1 seek=598382 
  # Invoke lseek with SEEK_DATA option starting with file offset 0
  while [ 1 ]; do xfs_io -f -c "seek -d 0" file-0.bin; done
  
  and I was able to hit the issue in 16.04.1 

  kernel version:
  4.4.0-28-generic

  dmesg o/p:

  [ 1197.994822]40-...: (5249 ticks this GP) idle=975/141/0 
softirq=7812/7812 fqs=5251 
  [ 1197.995071] (t=5251 jiffies g=29144 c=29143 q=3418)
  [ 1197.995115] Task dump for CPU 40:
  [ 1197.995117] xfs_io  R  running task0  3601   3489 
0x00040004
  [ 1197.995121] Call Trace:
  [ 1197.995126] [c03c7c8675b0] [c00fbc00] 
sched_show_task+0xe0/0x180 (unreliable)
  [ 1197.995131] [c03c7c867620] [c013eb74] 
rcu_dump_cpu_stacks+0xe4/0x150
  [ 1197.995134] [c03c7c867670] [c01442a4] 
rcu_check_callbacks+0x6b4/0x9b0
  [ 1197.995136] [c03c7c8677a0] [c014c108] 
update_process_times+0x58/0xa0
  [ 1197.995140] [c03c7c8677d0] [c0163818] 
tick_sched_handle.isra.6+0x48/0xe0
  [ 1197.995143] [c03c7c867810] [c0163914] 
tick_sched_timer+0x64/0xd0
  [ 1197.995146] [c03c7c867850] [c014cbd4] 
__hrtimer_run_queues+0x124/0x450
  [ 1197.995148] [c03c7c8678e0] [c014dbfc] 
hrtimer_interrupt+0xec/0x2c0
  [ 1197.995152] [c03c7c8679a0] [c001f5bc] 
__timer_interrupt+0x8c/0x290
  [ 1197.995154]

[Kernel-packages] [Bug 1599068] Re: Add support for Intel 8265 Bluetooth ([8087:0A2B])

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

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

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

Title:
  Add support for Intel 8265 Bluetooth ([8087:0A2B])

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Backport supports for Intel 8265 Bluetooth from upstream

  The support is introduced in v4.7 so yakkety doesn't need this
  backport

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

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

[Kernel-packages] [Bug 1584192] Re: CVE-2016-4440

** Changed in: linux (Ubuntu Xenial)
   Status: Invalid => Fix Committed

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

Title:
  CVE-2016-4440

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-wily package in Ubuntu:
  Invalid
Status in linux-lts-xenial package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-snapdragon package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-lts-wily source package in Precise:
  Invalid
Status in linux-lts-xenial source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-snapdragon source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Invalid
Status in linux-lts-wily source package in Trusty:
  Invalid
Status in linux-lts-xenial source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-snapdragon source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Vivid:
  New
Status in linux-armadaxp source package in Vivid:
  New
Status in linux-flo source package in Vivid:
  New
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  New
Status in linux-lts-raring source package in Vivid:
  New
Status in linux-lts-saucy source package in Vivid:
  New
Status in linux-lts-trusty source package in Vivid:
  New
Status in linux-lts-utopic source package in Vivid:
  New
Status in linux-lts-vivid source package in Vivid:
  New
Status in linux-lts-wily source package in Vivid:
  New
Status in linux-lts-xenial source package in Vivid:
  New
Status in linux-mako source package in Vivid:
  New
Status in linux-manta source package in Vivid:
  New
Status in linux-raspi2 source package in Vivid:
  New
Status in linux-snapdragon source package in Vivid:
  New
Status in linux-ti-omap4 source package in Vivid:
  New
Status in linux source package in Wily:
  Invalid
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  New
Status in linux-goldfish source package in Wily:
  New
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-lts-wily source package in Wily:
  Invalid
Status in linux-lts-xenial source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  New
Status in linux-manta source package in Wily:
  New
Status in

[Kernel-packages] [Bug 1602724] Re: Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices

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

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

** Changed in: linux (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team 
(canonical-kernel-team)

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

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

Title:
  Ubuntu 16.04 - Full EEH Recovery Support for NVMe devices

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

Bug description:
  == Comment: #0 - Heitor Ricardo Alves de Siqueira  - 
2016-07-12 12:54:27 ==
  Current nvme driver in Ubuntu 16.04 kernel does not handle error recovery; we 
are missing some patches from the upstream nvme driver.

  We would like to ask Canonical to cherry pick the following patches for the 
16.04 kernel, if possible:
  * 9396dec916c0 ("nvme: use a work item to submit async event requests")
  * 79f2b358c9ba ("nvme: don't poll the CQ from the kthread")
  * 2d55cd5f511d ("nvme: replace the kthread with a per-device watchdog 
timer")
  * 9bf2b972afea ("NVMe: Fix reset/remove race")
  * c875a7093f04 ("nvme: Avoid reset work on watchdog timer function during 
error recovery")
  * a5229050b69c ("NVMe: Always use MSI/MSI-x interrupts")

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

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

[Kernel-packages] [Bug 1602524] [NEW] [LTC-Test] - NMI watchdog Bug and call traces when trinity is executed.

You have been subscribed to a public bug:

== Comment: #0 - Santhosh G  ==
Problem Statement:
NMI watchdog bug and call traces occurs when trinity is executed.

Environment:
P8 PowerVM Lpar

uname o/p:
uname -a
Linux tuleta4u-lp5 4.4.0-11-generic #26-Ubuntu SMP Sat Mar 5 14:21:51 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

Steps to reproduce:

1) Install ubuntu 16.04 in a PowerVM LPAR.
2) Download trinity-1.5 and set up ./configure.sh;make;make install
3)Execute trinity as 
   './trinity --dangerous'

The test runs for more than one hour and trinity gets killed with call
traces:

[19744.229979] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 21s! 
[trinity-c3:26544]
[19744.229991] Modules linked in: hidp hid bnep rfcomm l2tp_ppp l2tp_netlink 
l2tp_core ip6_udp_tunnel udp_tunnel af_key mpls_router llc2 nfnetlink dn_rtmsg 
xfrm_user xfrm_algo can_raw crypto_user can_bcm cmtp kernelcapi 
scsi_transport_iscsi sctp libcrc32c nfc af_alg caif_socket caif phonet af_rxrpc 
bluetooth can pppoe pppox irda crc_ccitt atm appletalk ipx p8023 p8022 psnap 
llc pseries_rng rtc_generic autofs4 ibmvscsi ibmveth
[19744.230024] CPU: 3 PID: 26544 Comm: trinity-c3 Not tainted 4.4.0-11-generic 
#26-Ubuntu
[19744.230026] task: cae87e60 ti: cae24000 task.ti: 
cae24000
[19744.230028] NIP: c03fac78 LR: c03fabfc CTR: c039ef10
[19744.230029] REGS: cae27980 TRAP: 0901   Not tainted  
(4.4.0-11-generic)
[19744.230030] MSR: 80009033   CR: 2400  XER: 
2000
[19744.230035] CFAR: c03fae6c SOFTE: 1
   GPR00: c03fabfc cae27c00 c15a3b00 
c000f7f03ba8
   GPR04: 0e02adcb cae27cb0  

   GPR08: 8000  c000ef886000 
c0af0870
   GPR12: 2400 ce7f1c80
[19744.230045] NIP [c03fac78] ext4_es_lookup_extent+0xc8/0x2c0
[19744.230047] LR [c03fabfc] ext4_es_lookup_extent+0x4c/0x2c0
[19744.230048] Call Trace:
[19744.230050] [cae27c00] [c03fabfc] 
ext4_es_lookup_extent+0x4c/0x2c0 (unreliable)
[19744.230053] [cae27c50] [c03a6f18] ext4_map_blocks+0x78/0x610
[19744.230055] [cae27d10] [c039f14c] ext4_llseek+0x23c/0x3f0
[19744.230057] [cae27de0] [c02e02a8] SyS_lseek+0xe8/0x130
[19744.230060] [cae27e30] [c0009204] system_call+0x38/0xb4
[19744.230061] Instruction dump:
[19744.230062] 2fa9 409effec e93e0028 3b80 e9490458 e92a0440 39290001 
f92a0440
[19744.230065] 7c2004ac 7d20d828 3129 7d20d92d <40c2fff4> 6000 7f83e378 
38210050


== Comment: #8 - Santhosh G  ==

Tried the scenario as given in 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=128126#c26
-
# Create a 624GiB file; Mostly filled with holes though
$ dd if=/dev/zero of=file-0.bin bs=1M count=1 seek=598382 
# Invoke lseek with SEEK_DATA option starting with file offset 0
while [ 1 ]; do xfs_io -f -c "seek -d 0" file-0.bin; done

and I was able to hit the issue in 16.04.1 

kernel version:
4.4.0-28-generic

dmesg o/p:

[ 1197.994822]  40-...: (5249 ticks this GP) idle=975/141/0 
softirq=7812/7812 fqs=5251 
[ 1197.995071]   (t=5251 jiffies g=29144 c=29143 q=3418)
[ 1197.995115] Task dump for CPU 40:
[ 1197.995117] xfs_io  R  running task0  3601   3489 0x00040004
[ 1197.995121] Call Trace:
[ 1197.995126] [c03c7c8675b0] [c00fbc00] sched_show_task+0xe0/0x180 
(unreliable)
[ 1197.995131] [c03c7c867620] [c013eb74] 
rcu_dump_cpu_stacks+0xe4/0x150
[ 1197.995134] [c03c7c867670] [c01442a4] 
rcu_check_callbacks+0x6b4/0x9b0
[ 1197.995136] [c03c7c8677a0] [c014c108] 
update_process_times+0x58/0xa0
[ 1197.995140] [c03c7c8677d0] [c0163818] 
tick_sched_handle.isra.6+0x48/0xe0
[ 1197.995143] [c03c7c867810] [c0163914] tick_sched_timer+0x64/0xd0
[ 1197.995146] [c03c7c867850] [c014cbd4] 
__hrtimer_run_queues+0x124/0x450
[ 1197.995148] [c03c7c8678e0] [c014dbfc] 
hrtimer_interrupt+0xec/0x2c0
[ 1197.995152] [c03c7c8679a0] [c001f5bc] 
__timer_interrupt+0x8c/0x290
[ 1197.995154] [c03c7c8679f0] [c001f970] timer_interrupt+0xa0/0xe0
[ 1197.995157] [c03c7c867a20] [c0002714] 
decrementer_common+0x114/0x180
[ 1197.995163] --- interrupt: 901 at 
ext4_es_find_delayed_extent_range+0x20/0x2b0
   LR = ext4_llseek+0x268/0x3f0
[ 1197.995166] [c03c7c867d10] [c03a170c] ext4_llseek+0x23c/0x3f0 
(unreliable)
[ 1197.995170] [c03c7c867de0] [c02e1f08] SyS_lseek+0xe8/0x130
[ 1197.995173] [c03c7c867e30] [c0009204] system_call+0x38/0xb4

=

The call traces does not occur when tried with the kernel with patch.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Triaged


**

[Kernel-packages] [Bug 1593124] Re: Add proper palm detection support for MS Precision Touchpad

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

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

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

Title:
  Add proper  palm detection support for MS Precision Touchpad

Status in HWE Next:
  Confirmed
Status in HWE Next xenial series:
  Confirmed
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Sometimes touchpad doesn't work properly after palm is rejected. The
  pointer either jumping around (described on bugzilla[1]) or doesn't
  move at all (in our cases).

  This problem is introduced with commit:
  25a84db15b3f3a24d3ea7d2baf90693bcff34b0c (HID: multitouch: enable palm
  rejection if device implements confidence usage), by reverting it the
  touchpad can work properly.

  We also contacted with Synaptics, and they provided a workaround to
  fix this issue. Not sure if the workaround will be upstreamed and
  needs to keep co-working with them.

  Commit 25a84db applies to Xenial and Yakkety so only these two release
  were affected.

  The maintainer has provided a patch set to fix this issue and add
  proper palm detection support and the patch set has been merged. We
  also need to introduce this feature to Vivid at OEM's demands.

  [1]: https://bugzilla.kernel.org/show_bug.cgi?id=112791

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

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

[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

2016-07-15 Thread Thomas Mayer

I have ubuntu 16.04, kernel 4.4.0-28-generic, up-to-date. I did not
experience the freezing video in 14.04.

However, in 14.04 (kernel 4.2) I sometimes did not have sound unless
toggling between A2DP and SCO. Freezing videos in 16.04 just come on-top
now.

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

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

apport information

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  reece  2194 F pulseaudio
   /dev/snd/controlC0:  reece  2194 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
  InstallationDate: Installed on 2016-05-11 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision 5510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  reece  2194 F pulseaudio
   /dev/snd/controlC0:  reece  2194 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
  InstallationDate: Installed on 2016-05-11 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision 5510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  reece  2194 F pulseaudio
   /dev/snd/controlC0:  reece  2194 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
  InstallationDate: Installed on 2016-05-11 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision 5510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1603283] Re: REGRESSION: resume fails on recent 4.4.0-31, works on -28

Disregard comment #3... the endpoint seems to be working now.
Let me know if other info would help.
Note that the apport info was collected with 4.4.0-28 after rebooting, not the 
-31 that's causing issues.

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  reece  2194 F pulseaudio
   /dev/snd/controlC0:  reece  2194 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
  InstallationDate: Installed on 2016-05-11 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision 5510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  reece  2194 F pulseaudio
   /dev/snd/controlC0:  reece  2194 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
  InstallationDate: Installed on 2016-05-11 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision 5510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  reece  2194 F pulseaudio
   /dev/snd/controlC0:  reece  2194 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
  InstallationDate: Installed on 2016-05-11 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision 5510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  reece  2194 F pulseaudio
   /dev/snd/controlC0:  reece  2194 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
  InstallationDate: Installed on 2016-05-11 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision 5510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  reece  2194 F pulseaudio
   /dev/snd/controlC0:  reece  2194 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
  InstallationDate: Installed on 2016-05-11 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision 5510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  reece  2194 F pulseaudio
   /dev/snd/controlC0:  reece  2194 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
  InstallationDate: Installed on 2016-05-11 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision 5510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  reece  2194 F pulseaudio
   /dev/snd/controlC0:  reece  2194 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
  InstallationDate: Installed on 2016-05-11 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision 5510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  reece  2194 F pulseaudio
   /dev/snd/controlC0:  reece  2194 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
  InstallationDate: Installed on 2016-05-11 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision 5510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  reece  2194 F pulseaudio
   /dev/snd/controlC0:  reece  2194 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
  InstallationDate: Installed on 2016-05-11 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision 5510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  reece  2194 F pulseaudio
   /dev/snd/controlC0:  reece  2194 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
  InstallationDate: Installed on 2016-05-11 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision 5510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  reece  2194 F pulseaudio
   /dev/snd/controlC0:  reece  2194 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
  InstallationDate: Installed on 2016-05-11 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision 5510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  reece  2194 F pulseaudio
   /dev/snd/controlC0:  reece  2194 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
  InstallationDate: Installed on 2016-05-11 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision 5510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1603283] Re: REGRESSION: resume fails on recent 4.4.0-31, works on -28

apport information

** Tags added: apport-collected xenial

** Description changed:

- Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The
- machine appears to suspend, and this is confirmed in syslog. However,
- when attempting resume, the screen is black and there is no indication
- of resumption. The machine automatically reboots within ~15 seconds. I
- did this three times with -31.  Reverting to the -28 kernel restored
- suspend/resume.
+ Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  reece  2194 F pulseaudio
+  /dev/snd/controlC0:  reece  2194 F pulseaudio
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
+ InstallationDate: Installed on 2016-05-11 (65 days ago)
+ InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
+ MachineType: Dell Inc. Precision 5510
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-28-generic N/A
+  linux-backports-modules-4.4.0-28-generic  N/A
+  linux-firmware1.157.2
+ Tags:  xenial
+ Uname: Linux 4.4.0-28-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 04/07/2016
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 01.02.00
+ dmi.board.name: 0N8J4R
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A01
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
+ dmi.product.name: Precision 5510
+ dmi.sys.vendor: Dell Inc.

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

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

Title:
  REGRESSION: resume fails on recent 4.4.0-31, works on -28

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Today (July 14), I updated Ubuntu 16.04 running 4.4.0-28 to -31.  The machine 
appears to suspend, and this is confirmed in syslog. However, when attempting 
resume, the screen is black and there is no indication of resumption. The 
machine automatically reboots within ~15 seconds. I did this three times with 
-31.  Reverting to the -28 kernel restored suspend/resume.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  reece  2194 F pulseaudio
   /dev/snd/controlC0:  reece  2194 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3329049e-5384-42bd-beaa-c81181926a01
  InstallationDate: Installed on 2016-05-11 (65 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Precision 5510
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  Tags:  xenial
  Uname: Linux 4.4.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

2016-07-15 Thread Thomas Mayer

I experience the same issue for device

Bus 002 Device 003: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth
Module

together with an Arctic P311 head set.

For me, the problem does not occur reproducably, but about every 3-4
tries. Steps to reproduce

- Play video (e.g. youtube video in Firefox)
- Connect headset (by pressing the connect button of the headset)
- When connected via BT, the video playback stops instantly after the connect

Workaround:
- Go to sound settings / head set audio device
- switch from A2DP to SCO (mono playback with low resolution) -> video playback 
continues
- switch back to A2DP -> video playback still continues, now in HiFi stereo

At least after reboot, the workaround has to be applied again.

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

Title:
  Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In 16.04 when a bluetooth audio device is connected it freezes video
  playback and also no sound comes from online audio only streams. Issue
  does not exist with a wired headset.

  This issue does not exist with 15.10. All updates have been installed
  on 16.04 including backports but they have not fixed the issue.

  It is not browser specific and not website specific.

  It is not hardware specific as it affects my laptop with an intel 7260
  card and my pc with an intel 8260 card.

  The issue exists on both ubuntu and kubuntu 16.04.

  I have reported it on the ubuntu support forums and after
  investigation a moderator noticed changed in the kernel from 4.4 and
  4.2 that may becausing the issue and asked me to file a bug report.

  The ubuntu forum thread can be found here.
  http://ubuntuforums.org/showthread.php?t=2326672

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  stephen1435 F pulseaudio
   /dev/snd/controlC0:  stephen1435 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun  3 23:50:00 2016
  HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6
  InstallationDate: Installed on 2016-05-06 (28 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7978
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed 
root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago)
  dmi.bios.date: 05/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: C.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H170 GAMING M3 (MS-7978)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.name: MS-7978
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1602801] Re: linux: 4.6.0-9.10 -proposed tracker

2016-07-15 Thread Brad Figg

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

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft 
(apw)

** Description changed:

  This bug is for tracking the 4.6.0-9.10 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- kernel-phase:Packaging
- kernel-phase-changed:Wednesday, 13. July 2016 19:05 UTC
- 
  -- swm properties --
  derivative-trackers-created: true
  phase: Packaging
+ kernel-phase-changed:Friday, 15. July 2016 19:01 UTC
+ kernel-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.6.0-9.10 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: Packaging
- kernel-phase-changed:Friday, 15. July 2016 19:01 UTC
- kernel-phase:Uploaded
+ phase: Uploaded

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

Title:
  linux: 4.6.0-9.10 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.6.0-9.10 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: Uploaded

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

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

[Kernel-packages] [Bug 1603288] Re: package linux-image-4.4.0-31-generic (not installed) failed to install/upgrade: unable to clean up mess surrounding './boot/config-4.4.0-31-generic' before installi

2016-07-15 Thread David

Verified that is issue did not occur with another Ubuntu 16.04 64-bit
based distro (named for spice which is sometimes used to make tea) which
is also using Mate Desktop (but uses a different pre-installed package
manager). That distro is using identical user added packages.

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

Title:
  package linux-image-4.4.0-31-generic (not installed) failed to
  install/upgrade: unable to clean up mess surrounding
  './boot/config-4.4.0-31-generic' before installing another version:
  Read-only file system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Install attempted by Ubuntu Mate included Update Manager along with
  Grub2 update. The Grub2 update failed and according to the pop-up
  announcement by the Update Manager it also caused the  linux-
  image-4.4.0-31-generic installation failure.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  2162 F pulseaudio
   /dev/snd/controlC0:  david  2162 F pulseaudio
  Date: Thu Jul 14 20:27:23 2016
  DuplicateSignature:
   package:linux-image-4.4.0-31-generic:(not installed)
   Unpacking linux-image-4.4.0-31-generic (4.4.0-31.50) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-31-generic_4.4.0-31.50_amd64.deb 
(--unpack):
unable to clean up mess surrounding './boot/config-4.4.0-31-generic' before 
installing another version: Read-only file system
  ErrorMessage: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
  HibernationDevice: RESUME=UUID=cf771e35-9679-4425-89bc-cdc68ab786e6
  InstallationDate: Installed on 2016-05-23 (53 days ago)
  InstallationMedia: It
  MachineType: GizmoSphere Gizmo2
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=19bf53ad-e512-4435-bbde-ae92ffe72f2a ro elevator=noop quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-31-generic (not installed) failed to 
install/upgrade: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2014
  dmi.bios.vendor: coreboot
  dmi.bios.version: SageBios_Gizmo2-121
  dmi.chassis.type: 3
  dmi.chassis.vendor: GizmoSphere
  dmi.modalias: 
dmi:bvncoreboot:bvrSageBios_Gizmo2-121:bd04/10/2014:svnGizmoSphere:pnGizmo2:pvr1.0:cvnGizmoSphere:ct3:cvr:
  dmi.product.name: Gizmo2
  dmi.product.version: 1.0
  dmi.sys.vendor: GizmoSphere

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

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

[Kernel-packages] [Bug 1603288] Re: package linux-image-4.4.0-31-generic (not installed) failed to install/upgrade: unable to clean up mess surrounding './boot/config-4.4.0-31-generic' before installi

2016-07-15 Thread David

Verified that is issue did not occur with another Ubuntu 16.04 64-bit
based distro (named for spice which is sometimes used to make tea) which
is also using Mate Desktop (but uses a different pre-installed package
manager).

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

Title:
  package linux-image-4.4.0-31-generic (not installed) failed to
  install/upgrade: unable to clean up mess surrounding
  './boot/config-4.4.0-31-generic' before installing another version:
  Read-only file system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Install attempted by Ubuntu Mate included Update Manager along with
  Grub2 update. The Grub2 update failed and according to the pop-up
  announcement by the Update Manager it also caused the  linux-
  image-4.4.0-31-generic installation failure.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  2162 F pulseaudio
   /dev/snd/controlC0:  david  2162 F pulseaudio
  Date: Thu Jul 14 20:27:23 2016
  DuplicateSignature:
   package:linux-image-4.4.0-31-generic:(not installed)
   Unpacking linux-image-4.4.0-31-generic (4.4.0-31.50) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-31-generic_4.4.0-31.50_amd64.deb 
(--unpack):
unable to clean up mess surrounding './boot/config-4.4.0-31-generic' before 
installing another version: Read-only file system
  ErrorMessage: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
  HibernationDevice: RESUME=UUID=cf771e35-9679-4425-89bc-cdc68ab786e6
  InstallationDate: Installed on 2016-05-23 (53 days ago)
  InstallationMedia: It
  MachineType: GizmoSphere Gizmo2
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=19bf53ad-e512-4435-bbde-ae92ffe72f2a ro elevator=noop quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-31-generic (not installed) failed to 
install/upgrade: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2014
  dmi.bios.vendor: coreboot
  dmi.bios.version: SageBios_Gizmo2-121
  dmi.chassis.type: 3
  dmi.chassis.vendor: GizmoSphere
  dmi.modalias: 
dmi:bvncoreboot:bvrSageBios_Gizmo2-121:bd04/10/2014:svnGizmoSphere:pnGizmo2:pvr1.0:cvnGizmoSphere:ct3:cvr:
  dmi.product.name: Gizmo2
  dmi.product.version: 1.0
  dmi.sys.vendor: GizmoSphere

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

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

[Kernel-packages] [Bug 1603483] Re: [Xenial] Include Huawei PCIe SSD hio kernel driver

Xenial amd64 test kernel (4.4.0-32.50~lp1603483):

  http://people.canonical.com/~kamal/lp1603483/

(The hio driver is a module, present in block-modules-4.4.0-32-generic-
di_4.4.0-32.50~lp1603483_amd64.udeb)

  * [Xenial] Include Huawei PCIe SSD hio kernel driver (LP: #1603483)
- SAUCE: import Huawei ES3000_V2 (2.1.0.23)
- SAUCE: hio: bio_endio() no longer takes errors arg
- SAUCE: hio: blk_queue make_request_fn now returns a blk_qc_t
- SAUCE: hio: use alloc_cpumask_var to avoid -Wframe-larger-than
- SAUCE: hio: fix mask maybe-uninitialized warning
- [config] enable CONFIG_HIO (Huawei ES3000_V2 PCIe SSD driver)
- SAUCE: hio: Makefile and Kconfig

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

Title:
  [Xenial] Include Huawei PCIe SSD hio kernel driver

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

Bug description:
  == SRU Justification ==
  Huawei servers, including Huawei PCIe SSD's require the hio driver which is 
currently not included in our kernels.  We would like to carry this driver in 
our kernels for Xenial and newer in order to support platforms with these 
drives.

  == Source ==
  
http://support.huawei.com/enterprisesearch/ebgSearch#sp.keyword=HUAWEI%20ES3000%20V2%20Driver%20SRC

  == Testing ==
  TBD

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

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

[Kernel-packages] [Bug 1603288] Re: package linux-image-4.4.0-31-generic (not installed) failed to install/upgrade: unable to clean up mess surrounding './boot/config-4.4.0-31-generic' before installi

2016-07-15 Thread Alberto Salvia Novella

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

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

Title:
  package linux-image-4.4.0-31-generic (not installed) failed to
  install/upgrade: unable to clean up mess surrounding
  './boot/config-4.4.0-31-generic' before installing another version:
  Read-only file system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Install attempted by Ubuntu Mate included Update Manager along with
  Grub2 update. The Grub2 update failed and according to the pop-up
  announcement by the Update Manager it also caused the  linux-
  image-4.4.0-31-generic installation failure.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  2162 F pulseaudio
   /dev/snd/controlC0:  david  2162 F pulseaudio
  Date: Thu Jul 14 20:27:23 2016
  DuplicateSignature:
   package:linux-image-4.4.0-31-generic:(not installed)
   Unpacking linux-image-4.4.0-31-generic (4.4.0-31.50) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-31-generic_4.4.0-31.50_amd64.deb 
(--unpack):
unable to clean up mess surrounding './boot/config-4.4.0-31-generic' before 
installing another version: Read-only file system
  ErrorMessage: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
  HibernationDevice: RESUME=UUID=cf771e35-9679-4425-89bc-cdc68ab786e6
  InstallationDate: Installed on 2016-05-23 (53 days ago)
  InstallationMedia: It
  MachineType: GizmoSphere Gizmo2
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-generic 
root=UUID=19bf53ad-e512-4435-bbde-ae92ffe72f2a ro elevator=noop quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.1
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.4.0-31-generic (not installed) failed to 
install/upgrade: unable to clean up mess surrounding 
'./boot/config-4.4.0-31-generic' before installing another version: Read-only 
file system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2014
  dmi.bios.vendor: coreboot
  dmi.bios.version: SageBios_Gizmo2-121
  dmi.chassis.type: 3
  dmi.chassis.vendor: GizmoSphere
  dmi.modalias: 
dmi:bvncoreboot:bvrSageBios_Gizmo2-121:bd04/10/2014:svnGizmoSphere:pnGizmo2:pvr1.0:cvnGizmoSphere:ct3:cvr:
  dmi.product.name: Gizmo2
  dmi.product.version: 1.0
  dmi.sys.vendor: GizmoSphere

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

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

[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool

2016-07-15 Thread Alberto Salvia Novella

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

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

Title:
  Dell Inspiron 7559 fans do not shut off once started, even when cool

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to
  be an issue with the fan control. When I first boot up the machine the
  fans are off. However, after the laptop warms up under normal usage,
  the fans kick on and then never shut off again.  Even when the CPU
  cools down to below 35c, the fans will continue to run.

  If I suspend the the laptop, and then immediately wake it up again
  then fans are once again off, until it warms up again.  So
  essentially, once the fans start they don't seem to ever shut off.

  Fans seem to work normally under Windows 10.  They turn on as needed,
  and then turn off once the laptop cools down.

  I've tried the various BIOS updates that Dell has released, without
  success. I am currently running Dell's latest BIOS for this laptop
  (v1.1.8)

  Below is the output of lm-sensors showing the fans running when the
  CPU is at a cool 35c

  dell_smm-virtual-0
  Adapter: Virtual device
  Processor Fan: 1925 RPM
  Processor Fan: 2143 RPM
  CPU:+35.0°C  
  GPU: +1.0°C  
  SODIMM: +49.0°C

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob1709 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul 13 19:18:45 2016
  HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77
  InstallationDate: Installed on 2016-07-13 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. Inspiron 7559
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed 
root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/17/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.8
  dmi.board.name: 0H0CC0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.1.8
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1572659] Re: bcmwl driver does not work with kernel 4.4.0-21 when secure boot enabled

2016-07-15 Thread J. Lowry Snow

any plans to get this fixed so SecureBoot can be enabled w 16.04?

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

Title:
  bcmwl driver does not work with kernel 4.4.0-21 when secure boot
  enabled

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  After updating ubuntu 16.04 to latest kernel 4.4.0-21, bcmwl driver
  (package bcmwl-kernel-source) does not load and wifi not work.

  sudo modprobe wl
  modprobe: ERROR: could not insert 'wl': Required key not available

  If I boot with kernel 4.4.0-18 - bcmwl loads normally and wifi works.

  If secure boot disabled - bcmwl loads normally with kernel 4.4.0-21
  and wifi works.

  
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-12-02 (140 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  NonfreeKernelModules: wl
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Tags:  xenial
  Uname: Linux 4.4.0-18-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (47 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1603504] Re: build-arch and build-indep are now manditory

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

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

** Changed in: linux-meta (Ubuntu)
 Assignee: (unassigned) => Andy Whitcroft (apw)

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

Title:
  build-arch and build-indep are now manditory

Status in linux-meta package in Ubuntu:
  In Progress

Bug description:
  dpkg has now made build-arch and build-indep manditory targets.  We
  need to fix linux-meta to have these.

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

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

[Kernel-packages] [Bug 1603504] [NEW] build-arch and build-indep are now manditory

Public bug reported:

dpkg has now made build-arch and build-indep manditory targets.  We need
to fix linux-meta to have these.

** Affects: linux-meta (Ubuntu)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

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

Title:
  build-arch and build-indep are now manditory

Status in linux-meta package in Ubuntu:
  In Progress

Bug description:
  dpkg has now made build-arch and build-indep manditory targets.  We
  need to fix linux-meta to have these.

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

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

[Kernel-packages] [Bug 1603476] Re: Boot failure with EFI stub

2016-07-15 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  Boot failure with EFI stub

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating kernel to 3.13.0-92 system cannot startup with these errors:
   Failed to get file info size 
   Failed to alloc highmem for files

  I've found patch fixing it here — 
http://kernel.opensuse.org/cgit/kernel/commit/?h=v3.15.9=396f1a08db212138418b38f784e4bbe516d2fdb2
  Works like a charm.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-92-generic 3.13.0-92.139
  ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-92-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrei 2236 F pulseaudio
   /dev/snd/controlC1:  andrei 2236 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jul 15 17:41:11 2016
  InstallationDate: Installed on 2014-11-26 (596 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: root=UUID=33a02342-70da-4f8d-9868-2f8e7330ec90 ro 
rootfstype=ext4 add_efi_memmap initrd=\EFI\ubuntu\initrd.img
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-92-generic N/A
   linux-backports-modules-3.13.0-92-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M
  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.:bvr3901:bd09/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-M: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/1603476/+subscriptions

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

[Kernel-packages] [Bug 1602299] Re: bcache is unstable on ppc64el

2016-07-15 Thread Stefan Bader

Recreated on a test system. The fact that the superblock gets written to
is expected. Though for ppc64el this seems to go wrong at early stages.
I am comparing the results on a ppc64el vm and a x86 vm. After setting
up bcache and attaching the cache to the backing dev, the output of
bcache-super-show already differs from sysfs information on ppc64el. On
x86 this in consistent (which means the superblock was already updated
by the kernel at that stage).

On ppc64el the differences are:
- cache dev
  * sb.version is still 0 (should be 3)
  * dev.cache.ordered no (is yes on x86)
- backing dev
  * dev.data.cache_state detached (should be clean)

Created a vm dump to investigate deeper into this.

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

Title:
  bcache is unstable on ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Stopping and unregistering bcache caches and backing devices results
  in losing the bcache superblock on devices rendering bcached devices
  corrupt or broken.

  1. Ubuntu 4.4.0-28.47-generic 4.4.13
  2. attaching lspci log
  3. 

  Description:Ubuntu 16.04 LTS
  Release:16.04

  4. # apt-cache policy linux-image
  linux-image:
Installed: (none)
Candidate: (none)
Version table:
  root@rharper-vm1:~# apt-cache policy linux-image-generic
  linux-image-generic:
Installed: (none)
Candidate: 4.4.0.28.30
Version table:
   4.4.0.28.30 500
  500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main ppc64el 
Packages
  500 http://ports.ubuntu.com/ubuntu-ports xenial-security/main ppc64el 
Packages
   4.4.0.21.22 500
  500 http://ports.ubuntu.com/ubuntu-ports xenial/main ppc64el Packages

  5. After creating bcache devices, upon reboot they continue to remain as 
bcache devices for use
  6. Sometimes after reboot either the cache device, or the backing device 
loses the bcache-super-block rendering them useless to the bcache module (it 
fails to detect them).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-28-generic 4.4.0-28.47
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic ppc64le
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 11 21:30 seq
   crw-rw 1 root audio 116, 33 Jul 11 21:30 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Tue Jul 12 14:20:24 2016
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 OFfb vga
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-4.4.0-28-generic 
root=LABEL=cloudimg-rootfs earlyprintk
  ProcLoadAvg: 6.28 4.78 4.12 1/133 4838
  ProcLocks:
   1: POSIX  ADVISORY  WRITE 1306 00:11:541 0 EOF
   2: FLOCK  ADVISORY  WRITE 918 00:11:521 0 EOF
   3: POSIX  ADVISORY  WRITE 875 00:11:507 0 EOF
   4: POSIX  ADVISORY  WRITE 870 00:11:123 0 EOF
   5: POSIX  ADVISORY  WRITE 682 00:11:358 0 EOF
  ProcSwaps: Filename   TypeSizeUsed
Priority
  ProcVersion: Linux version 4.4.0-28-generic (buildd@bos01-ppc64el-018) (gcc 
version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2.1) ) #47-Ubuntu SMP Fri Jun 
24 10:09:20 UTC 2016
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-28-generic N/A
   linux-backports-modules-4.4.0-28-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_dscr: DSCR is 0
  cpu_freq:
   min: 3.684 GHz (cpu 0)
   max: 3.684 GHz (cpu 0)
   avg: 3.684 GHz
  cpu_runmode: run-mode=0
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

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

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

[Kernel-packages] [Bug 1599491] Re: kdump-tools install script uses deprecated syntax

2016-07-15 Thread Louis Bouchard

** Changed in: makedumpfile (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  kdump-tools install script uses deprecated syntax

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Xenial:
  Triaged

Bug description:
  When installing kdump-tools, the apt-get outputs:

  Setting up kdump-tools (1:1.5.9-5) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults

  Full log:

  jayman@jayman-kubuntu:~$ sudo apt-get install kdump-tools
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
crash kexec-tools libdw1 makedumpfile
  The following NEW packages will be installed:
crash kdump-tools kexec-tools libdw1 makedumpfile
  0 upgraded, 5 newly installed, 0 to remove and 10 not upgraded.
  Need to get 0 B/2,962 kB of archives.
  After this operation, 9,379 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Preconfiguring packages ...
  Selecting previously unselected package crash.
  (Reading database ... 235512 files and directories currently installed.)
  Preparing to unpack .../crash_7.1.4-1ubuntu4_amd64.deb ...
  Unpacking crash (7.1.4-1ubuntu4) ...
  Selecting previously unselected package libdw1:amd64.
  Preparing to unpack .../libdw1_0.165-3ubuntu1_amd64.deb ...
  Unpacking libdw1:amd64 (0.165-3ubuntu1) ...
  Selecting previously unselected package makedumpfile.
  Preparing to unpack .../makedumpfile_1%3a1.5.9-5_amd64.deb ...
  Unpacking makedumpfile (1:1.5.9-5) ...
  Selecting previously unselected package kexec-tools.
  Preparing to unpack .../kexec-tools_1%3a2.0.10-1ubuntu2_amd64.deb ...
  Unpacking kexec-tools (1:2.0.10-1ubuntu2) ...
  Selecting previously unselected package kdump-tools.
  Preparing to unpack .../kdump-tools_1%3a1.5.9-5_all.deb ...
  Unpacking kdump-tools (1:1.5.9-5) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for libc-bin (2.23-0ubuntu3) ...
  Processing triggers for systemd (229-4ubuntu6) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  Setting up crash (7.1.4-1ubuntu4) ...
  Setting up libdw1:amd64 (0.165-3ubuntu1) ...
  Setting up makedumpfile (1:1.5.9-5) ...
  Setting up kexec-tools (1:2.0.10-1ubuntu2) ...
  Generating grub configuration file ...
  Found linux image: /boot/vmlinuz-4.4.0-28-generic
  Found initrd image: /boot/initrd.img-4.4.0-28-generic
  Found linux image: /boot/vmlinuz-4.4.0-24-generic
  Found initrd image: /boot/initrd.img-4.4.0-24-generic
  Found memtest86+ image: /boot/memtest86+.elf
  Found memtest86+ image: /boot/memtest86+.bin
  grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your 
device.map.
  Found Windows 7 (loader) on /dev/sda1
  done
  Setting up kdump-tools (1:1.5.9-5) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  Processing triggers for libc-bin (2.23-0ubuntu3) ...
  jayman@jayman-kubuntu:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: kdump-tools 1:1.5.9-5
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Jul  6 08:02:53 2016
  InstallationDate: Installed on 2016-06-16 (19 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: makedumpfile
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1603483] [NEW] [Xenial] Include Huawei PCIe SSD hio kernel driver

Public bug reported:

== SRU Justification ==
Huawei servers, including Huawei PCIe SSD's require the hio driver which is 
currently not included in our kernels.  We would like to carry this driver in 
our kernels for Xenial and newer in order to support platforms with these 
drives.

== Source ==
http://support.huawei.com/enterprisesearch/ebgSearch#sp.keyword=HUAWEI%20ES3000%20V2%20Driver%20SRC

== Testing ==
TBD

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Leann Ogasawara (leannogasawara)
 Status: In Progress

** Affects: linux (Ubuntu Xenial)
 Importance: High
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Leann Ogasawara (leannogasawara)

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

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

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

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

Title:
  [Xenial] Include Huawei PCIe SSD hio kernel driver

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

Bug description:
  == SRU Justification ==
  Huawei servers, including Huawei PCIe SSD's require the hio driver which is 
currently not included in our kernels.  We would like to carry this driver in 
our kernels for Xenial and newer in order to support platforms with these 
drives.

  == Source ==
  
http://support.huawei.com/enterprisesearch/ebgSearch#sp.keyword=HUAWEI%20ES3000%20V2%20Driver%20SRC

  == Testing ==
  TBD

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

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

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

2016-07-15 Thread Brad Figg

This change was made by a bot.

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

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

Title:
  Boot failure with EFI stub

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating kernel to 3.13.0-92 system cannot startup with these errors:
   Failed to get file info size 
   Failed to alloc highmem for files

  I've found patch fixing it here — 
http://kernel.opensuse.org/cgit/kernel/commit/?h=v3.15.9=396f1a08db212138418b38f784e4bbe516d2fdb2
  Works like a charm.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-92-generic 3.13.0-92.139
  ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-92-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrei 2236 F pulseaudio
   /dev/snd/controlC1:  andrei 2236 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jul 15 17:41:11 2016
  InstallationDate: Installed on 2014-11-26 (596 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: root=UUID=33a02342-70da-4f8d-9868-2f8e7330ec90 ro 
rootfstype=ext4 add_efi_memmap initrd=\EFI\ubuntu\initrd.img
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-92-generic N/A
   linux-backports-modules-3.13.0-92-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M
  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.:bvr3901:bd09/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-M: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/1603476/+subscriptions

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

[Kernel-packages] [Bug 1603476] [NEW] Boot failure with EFI stub

2016-07-15 Thread Andrei Demin

Public bug reported:

After updating kernel to 3.13.0-92 system cannot startup with these errors:
 Failed to get file info size 
 Failed to alloc highmem for files

I've found patch fixing it here — 
http://kernel.opensuse.org/cgit/kernel/commit/?h=v3.15.9=396f1a08db212138418b38f784e4bbe516d2fdb2
Works like a charm.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-92-generic 3.13.0-92.139
ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
Uname: Linux 3.13.0-92-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  andrei 2236 F pulseaudio
 /dev/snd/controlC1:  andrei 2236 F pulseaudio
CurrentDesktop: KDE
Date: Fri Jul 15 17:41:11 2016
InstallationDate: Installed on 2014-11-26 (596 days ago)
InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
IwConfig:
 eth0  no wireless extensions.
 
 lono wireless extensions.
MachineType: System manufacturer System Product Name
ProcFB: 0 EFI VGA
ProcKernelCmdLine: root=UUID=33a02342-70da-4f8d-9868-2f8e7330ec90 ro 
rootfstype=ext4 add_efi_memmap initrd=\EFI\ubuntu\initrd.img
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-92-generic N/A
 linux-backports-modules-3.13.0-92-generic  N/A
 linux-firmware 1.127.22
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/12/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3901
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H67-M
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.:bvr3901:bd09/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug efi efistub trusty uefi

** Patch added: "patch"
   https://bugs.launchpad.net/bugs/1603476/+attachment/4701524/+files/patch

** Tags added: efi efistub uefi

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

Title:
  Boot failure with EFI stub

Status in linux package in Ubuntu:
  New

Bug description:
  After updating kernel to 3.13.0-92 system cannot startup with these errors:
   Failed to get file info size 
   Failed to alloc highmem for files

  I've found patch fixing it here — 
http://kernel.opensuse.org/cgit/kernel/commit/?h=v3.15.9=396f1a08db212138418b38f784e4bbe516d2fdb2
  Works like a charm.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-92-generic 3.13.0-92.139
  ProcVersionSignature: Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-92-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrei 2236 F pulseaudio
   /dev/snd/controlC1:  andrei 2236 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jul 15 17:41:11 2016
  InstallationDate: Installed on 2014-11-26 (596 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: root=UUID=33a02342-70da-4f8d-9868-2f8e7330ec90 ro 
rootfstype=ext4 add_efi_memmap initrd=\EFI\ubuntu\initrd.img
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-92-generic N/A
   linux-backports-modules-3.13.0-92-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3901
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8H67-M
  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.:bvr3901:bd09/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H67-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To

[Kernel-packages] [Bug 1603137] Re: libbfd changed name without transition

2016-07-15 Thread Adam Conrad

Hello Julian, or anyone else affected,

Accepted binutils into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/binutils/2.26.1-1ubuntu1~16.04.1 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation 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: binutils (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

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

Title:
  libbfd changed name without transition

Status in binutils package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in binutils source package in Xenial:
  Fix Committed
Status in linux source package in Xenial:
  Invalid

Bug description:
  [SRU Justification]
  the latest binutils update in xenial to 2.26.1-1ubuntu1~16.04 changed the 
name of the libbfd library from: libbfd-2.26-system.so to 
libbfd-2.26.1-system.so
  This apparently happened without transitioning all dependencies.
  For example it broke the perf tool from the linux-tools-common package as it 
is still linked against the old libbfd name.

  To reproduce run "perf" with linux >= 4.4.0-24.43 and binutils
  2.26.1-1ubuntu1~16.04 and you get an cannot open libbfd-2.26-system.so
  error.

  [Test case]
  1. Install eztrace on 16.04.
  2. Install binutils from xenial-updates.
  3. Run 'eztrace'.  Confirm that this fails with a library error.
  4. Install binutils from xenial-proposed.
  5. Run 'eztrace'.  Confirm that this gives usage output instead of failing 
with a library error.

  [Regression potential]
  Packages which depend on libbfd-2.26-system.so are currently broken with the 
binutils in xenial-updates.  No packages appear to have been built yet against 
the libbfd-2.26.1-system.so soname.  Therefore the regression potential is 
minimal.  The solution is intended to be compatible with both upstream sonames, 
so that any future packages which do rebuild against the 2.26.1 soname will 
have a versioned dependency on binutils (>= 2.26.1), binutils (<= 2.27).

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

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

[Kernel-packages] [Bug 1603468] [NEW] ovs nat: conntrack netlink event are missing

2016-07-15 Thread Nicolas Dichtel

Public bug reported:

Fixed upstream by this patch:
d913d3a763a6 openvswitch: fix conntrack netlink event delivery

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


** Tags: 6wind

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

Title:
  ovs nat: conntrack netlink event are missing

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fixed upstream by this patch:
  d913d3a763a6 openvswitch: fix conntrack netlink event delivery

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

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

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

2016-07-15 Thread Brad Figg

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

apport-collect 1603468

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

Title:
  ovs nat: conntrack netlink event are missing

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Fixed upstream by this patch:
  d913d3a763a6 openvswitch: fix conntrack netlink event delivery

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

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

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

2016-07-15 Thread bugproxy

--- Comment From ru...@us.ibm.com 2016-07-15 10:45 EDT---
*** Bug 143716 has been marked as a duplicate of 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/1572712

Title:
  console hung during Ubuntu 16.04 netboot install 4.4.0-12-generic
  [soft lockup]

Status in linux package in Ubuntu:
  New

Bug description:
  Canonical,

  FYI and reference only at this time.

  Details:
  ---Problem Description---
  IPMI Console gets hung for 15 to 30 mins, can not traverse when trying to 
install 
  latest copy of Ubuntu 16.04 on Habanero from 
http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
  which is 4.4.0-12-generic 
   [   36.803240] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! 
[swapper/2:0]
   
  ---uname output---
  4.4.0-12-generic 
   
  ---Additional Hardware Info---
  TN71-BP012  

   
  Machine Type = TN71-BP012  
   
  ---System Hang---
   we have to wait for 15 to 30 mins to regain the console access.

   
  ---Steps to Reproduce---
  use IPMI console for  petitboot on habanero, configure IP to a network 
device, make sure you have internet outbound BSO authenticated. 
  on petit shell run following commands 
  cd /tmp;
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/vmlinux
 ;
  wget 
http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/initrd.gz
 ;
  kexec -l /tmp/vmlinux  -i /tmp/initrd.gz  ;
  kexec -e ;

   
  Stack trace output:
   [   36.803240] NMI watchdog: BUG: soft lockup - CPU#2 stuck for 23s! 
[swapper/2:0]
  [   36.803425] Modules linked in: hid_generic(E) ast(E) i2c_algo_bit(E) 
drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) ttm
  ) usb_storage(E)
  [   36.803436] CPU: 2 PID: 0 Comm: swapper/2 Tainted: GE   
4.4.0-12-generic #28-Ubuntu
  [   36.803438] task: c03c8fe8e7b0 ti: c03c9753 task.ti: 
c03c9753
  [   36.803440] NIP: c0010a24 LR: c0010a24 CTR: 
c060c2f0
  [   36.803442] REGS: c03c97533510 TRAP: 0901   Tainted: GE
(4.4.0-12-generic)
  [   36.803443] MSR: 90019033   CR: 28002824  
XER: 
  [   36.803448] CFAR: c060c330 SOFTE: 1 
  [   36.803448] GPR00: c00db8b4 c03c97533790 c15a3b00 
0900 
  [   36.803448] GPR04: c03c8fef6e00 0001  
03ff 
  [   36.803448] GPR08:  c03ffb064605 0001 
0004 
  [   36.803448] GPR12: c060c2f0 cfb41300 
  [   36.803460] NIP [c0010a24] arch_local_irq_restore+0x74/0x90
  [   36.803462] LR [c0010a24] arch_local_irq_restore+0x74/0x90
  [   36.803463] Call Trace:
  [   36.803465] [c03c97533790] [c014b184] mod_timer+0x154/0x300 
(unreliable)
  [   36.803468] [c03c975337b0] [c00db8b4] queue_work_on+0x74/0xf0
  [   36.803471] [c03c975337f0] [c060c334] 
cursor_timer_handler+0x44/0x80
  [   36.803474] [c03c97533820] [c0149ebc] call_timer_fn+0x5c/0x1c0
  [   36.803476] [c03c975338b0] [c014a37c] 
run_timer_softirq+0x31c/0x3f0
  [   36.803480] [c03c97533980] [c00beaf8] __do_softirq+0x188/0x3e0
  [   36.803483] [c03c97533a70] [c00befc8] irq_exit+0xc8/0x100
  [   36.803487] [c03c97533a90] [c001f954] timer_interrupt+0xa4/0xe0
  [   36.803490] [c03c97533ac0] [c0002714] 
decrementer_common+0x114/0x180
  [   36.803494] --- interrupt: 901 at arch_local_irq_restore+0x74/0x90
  [   36.803494] LR = arch_local_irq_restore+0x74/0x90
  [   36.803497] [c03c97533db0] [c03ffc49d678] 0xc03ffc49d678 
(unreliable)
  [   36.803502] [c03c97533dd0] [c0900708] 
cpuidle_enter_state+0x1a8/0x410
  [   36.803504] [c03c97533e30] [c0119898] call_cpuidle+0x78/0xd0
  [   36.803506] [c03c97533e70] [c0119c6c] 
cpu_startup_entry+0x37c/0x490
  [   36.803509] [c03c97533f30] [c004565c] 
start_secondary+0x33c/0x360
  [   36.803511] [c03c97533f90] [c0008b6c] 
start_secondary_prolog+0x10/0x14
  [   36.803512] Instruction dump:
  [   36.803514] 994d02ca 2fa3 409e0024 e92d0020 61298000 7d210164 38210020 
e8010010 
  [   36.803517] 7c0803a6 4e800020 6042 4bff17ad <6000> 4be4 
6042 e92d0020 
  [   57.811232] INFO: rcu_sched self-detected stall on CPU
  [   57.811236]  2-...: (1 GPs behind) idle=913/2/0 softirq=1849/1979 fqs=5229 
  [   57.811238]   (t=5250 jiffies g=-114 c=-115 q=1)
  [   57.811242] Task dump for CPU 2:
  [   57.811243] swapper/2   R  running task0 0  1 
0x0804
  [   57.811246] Call Trace:
  [   57.811248]

[Kernel-packages] [Bug 1599491] Re: kdump-tools install script uses deprecated syntax

2016-07-15 Thread Louis Bouchard

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

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

** Changed in: makedumpfile (Ubuntu)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

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

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

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

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

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

Title:
  kdump-tools install script uses deprecated syntax

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

Bug description:
  When installing kdump-tools, the apt-get outputs:

  Setting up kdump-tools (1:1.5.9-5) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults

  Full log:

  jayman@jayman-kubuntu:~$ sudo apt-get install kdump-tools
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
crash kexec-tools libdw1 makedumpfile
  The following NEW packages will be installed:
crash kdump-tools kexec-tools libdw1 makedumpfile
  0 upgraded, 5 newly installed, 0 to remove and 10 not upgraded.
  Need to get 0 B/2,962 kB of archives.
  After this operation, 9,379 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  Preconfiguring packages ...
  Selecting previously unselected package crash.
  (Reading database ... 235512 files and directories currently installed.)
  Preparing to unpack .../crash_7.1.4-1ubuntu4_amd64.deb ...
  Unpacking crash (7.1.4-1ubuntu4) ...
  Selecting previously unselected package libdw1:amd64.
  Preparing to unpack .../libdw1_0.165-3ubuntu1_amd64.deb ...
  Unpacking libdw1:amd64 (0.165-3ubuntu1) ...
  Selecting previously unselected package makedumpfile.
  Preparing to unpack .../makedumpfile_1%3a1.5.9-5_amd64.deb ...
  Unpacking makedumpfile (1:1.5.9-5) ...
  Selecting previously unselected package kexec-tools.
  Preparing to unpack .../kexec-tools_1%3a2.0.10-1ubuntu2_amd64.deb ...
  Unpacking kexec-tools (1:2.0.10-1ubuntu2) ...
  Selecting previously unselected package kdump-tools.
  Preparing to unpack .../kdump-tools_1%3a1.5.9-5_all.deb ...
  Unpacking kdump-tools (1:1.5.9-5) ...
  Processing triggers for man-db (2.7.5-1) ...
  Processing triggers for libc-bin (2.23-0ubuntu3) ...
  Processing triggers for systemd (229-4ubuntu6) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  Setting up crash (7.1.4-1ubuntu4) ...
  Setting up libdw1:amd64 (0.165-3ubuntu1) ...
  Setting up makedumpfile (1:1.5.9-5) ...
  Setting up kexec-tools (1:2.0.10-1ubuntu2) ...
  Generating grub configuration file ...
  Found linux image: /boot/vmlinuz-4.4.0-28-generic
  Found initrd image: /boot/initrd.img-4.4.0-28-generic
  Found linux image: /boot/vmlinuz-4.4.0-24-generic
  Found initrd image: /boot/initrd.img-4.4.0-24-generic
  Found memtest86+ image: /boot/memtest86+.elf
  Found memtest86+ image: /boot/memtest86+.bin
  grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your 
device.map.
  Found Windows 7 (loader) on /dev/sda1
  done
  Setting up kdump-tools (1:1.5.9-5) ...
  update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
  Processing triggers for libc-bin (2.23-0ubuntu3) ...
  jayman@jayman-kubuntu:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: kdump-tools 1:1.5.9-5
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Jul  6 08:02:53 2016
  InstallationDate: Installed on 2016-06-16 (19 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: makedumpfile
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1599561] Re: Ubuntu 16.04.01 kdump: IP prefix is missing in the directory name after first dump during kdump over ssh.

2016-07-15 Thread Louis Bouchard

Hello,

Thanks for testing the fix. I will proceed with the SRU process.

Kind regards,

...Louis

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

Title:
  Ubuntu 16.04.01 kdump: IP prefix is missing in the directory name
  after first dump during kdump over ssh.

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

Bug description:
  == Comment: #0 - PAVITHRA R. PRAKASH - 2016-06-30 07:12:40 ==
  ---Problem Description---

  During kdump over ssh IP prefix will be present only in first dump,
  subsequent dumps will not have IP in directory name.

  ---Steps to Reproduce---

  1) apt-get install linux-crashdump
  2) increase crashdump size:
  sudo vim /etc/default/grub.d/kexec-tools.cfg

  GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel
  =2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M

  3) sudo update-grub ; reboot the machine
  4) sudo sed -i 's/USE_KDUMP=0/USE_KDUMP=1/g' /etc/default/kdump-tools
  5) kdump-config show # should show "ready to dump"
  6) ssh-keygen -t rsa
  7) Edit below parameters in /etc/default/kdump-tools
  SSH="root@"
  SSH_KEY=/root/.ssh/id_rsa
  8)  kdump-config propagate
  9)  kdump-config show
  10) reboot
  11) echo "c" > /proc/sysrq-trigger
  12) verify dump is created in ssh server.
  13) trigger the crash again.

  Logs
  =
  root@ubuntu:/home/ubuntu# uname -a
  Linux ubuntu 4.4.0-26-generic #45-Ubuntu SMP Mon Jun 20 17:27:01 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  dumps on ssh server when 3 crashes are triggered
  
  [root@ltc-fire5 crash]# ls
  192.168.122.25-201606300523
  [root@ltc-fire5 crash]# ls
  192.168.122.25-201606300523  -201606300524
  [root@ltc-fire5 crash]# ls
  192.168.122.25-201606300523  -201606300524  -201606300525
  [root@ltc-fire5 crash]# cd -201606300524
  -bash: cd: -2: invalid option
  cd: usage: cd [-L|[-P [-e]]] [dir]
  [root@ltc-fire5 crash]# cd -- -201606300524
  [root@ltc-fire5 -201606300524]# ls
  dmesg.201606300524  dump.201606300524

  
  == Comment: #8 - Kevin W. Rudd - 2016-07-05 18:23:01 ==

  Canonical,

  The behavior appears to be somewhat intermittent, and it looks as if
  define_stampdir() might be getting called before the network init has
  completed.  If delaying this function is not practical, it might be
  helpful to have define_stampdir() fall back to using just "hostname"
  if "hostname -I" doesn't return any useful information for setting
  THIS_HOST.

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

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

[Kernel-packages] [Bug 1586169] Re: [Yakkety] fanatic fails running lxd test

Now uses the latest LTS image for testing, which always exists in all
releases.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  [Yakkety] fanatic fails running lxd test

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed

Bug description:
  Running Yakkety 16.10, fanatic text for lxd fails because the
  "requested image couldn't be found", but then continues to emit error
  messages until killed.  fanatic should gracefully fail the test and
  move on.  Raw output is as follows:

  $ sudo fanatic
  Welcome to the fanatic fan networking wizard.  This will help you set
  up an example fan network and optionally configure docker and/or LXD to
  use this network.  See fanatic(1) for more details.

  Configure fan underlay (hit return to accept, or specify alternative) 
[192.168.0.0/16]:
  Configure fan overlay (hit return to accept, or specify alternative) 
[250.0.0.0/8]:
  Create LXD networking for underlay:192.168.0.0/16 overlay:250.0.0.0/8 [Yn]: Y
  Profile fan-250 created
  Create docker networking for underlay:192.168.0.0/16 overlay:250.0.0.0/8 
[Yn]: Y
  Test LXD networking for underlay:192.168.1.16/16 overlay:250.0.0.0/8
  (NOTE: potentially triggers large image downloads) [Yn]: Y
  local lxd test: creating test container (Ubuntu:16.10) ...
  Creating fanatic-test
  error: The requested image couldn't be found.
  lxd test: Waiting for addresses on eth0 ...
  error: not found
  lxd test: Waiting for addresses on eth0 ...
  error: not found
  lxd test: Waiting for addresses on eth0 ...
  error: not found
  lxd test: Waiting for addresses on eth0 ...
  error: not found

  ===
  [Impact]

  Unable to test LXC configuration.

  [Test Case]

  Configure fan and confirm LXC testing.

  [Regression Potential]

  Low, only used during initial configuration.

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

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

[Kernel-packages] [Bug 1602888] Re: Dell Inspiron 7559 fans do not shut off once started, even when cool

2016-07-15 Thread Max

A lot of Dell Inspiron 7559 users are facing this annoying bug.
It doesn't matter if we're using the Intel Graphic card or the Nvidia one.
I have the problem under Linux Mint and Kubuntu.

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

Title:
Dell Inspiron 7559 fans do not shut off once started, even when cool

Status in linux package in Ubuntu:
Confirmed

Bug description:
Running Ubuntu 16.04 on a Dell Inspiron 7559 laptop there appears to
be an issue with the fan control. When I first boot up the machine the
fans are off. However, after the laptop warms up under normal usage,
the fans kick on and then never shut off again. Even when the CPU
cools down to below 35c, the fans will continue to run.

If I suspend the the laptop, and then immediately wake it up again
then fans are once again off, until it warms up again. So
essentially, once the fans start they don't seem to ever shut off.

Fans seem to work normally under Windows 10. They turn on as needed,
and then turn off once the laptop cools down.

I've tried the various BIOS updates that Dell has released, without
success. I am currently running Dell's latest BIOS for this laptop
(v1.1.8)

Below is the output of lm-sensors showing the fans running when the
CPU is at a cool 35c

dell_smm-virtual-0
Adapter: Virtual device
Processor Fan: 1925 RPM
Processor Fan: 2143 RPM
CPU:+35.0°C
GPU: +1.0°C
SODIMM: +49.0°C

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-28-generic 4.4.0-28.47
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bob1709 F pulseaudio
CurrentDesktop: Unity
Date: Wed Jul 13 19:18:45 2016
HibernationDevice: RESUME=UUID=14de580b-76f3-47e4-9850-fe7637f9ff77
InstallationDate: Installed on 2016-07-13 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: Dell Inc. Inspiron 7559
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-28-generic.efi.signed
root=UUID=0b3dbcf3-0bdb-4c35-9200-7bb303055a81 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-28-generic N/A
linux-backports-modules-4.4.0-28-generic N/A
linux-firmware1.157.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/17/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.8
dmi.board.name: 0H0CC0
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.8:bd04/17/2016:svnDellInc.:pnInspiron7559:pvr1.1.8:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: Inspiron 7559
dmi.product.version: 1.1.8
dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1551747] Re: ubuntu-fan causes issues during network configuration

2016-07-15 Thread Eliezer Croitoru

@Uli, these users needs to test so when they will have any trouble they would 
probably bump this or another bug report.
I do not like the concept but this is what we have now.

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

Title:
  ubuntu-fan causes issues during network configuration

Status in cloud-init:
  New
Status in Snappy:
  Confirmed
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Yakkety:
  Fix Released

Bug description:
  it seems that ubuntu-fan is causing issues with network configuration.

  On 16.04 daily image:

  root@localhost:~# snappy list
  NameDate   Version  Developer
  canonical-pi2   2016-02-02 3.0  canonical
  canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical
  ubuntu-core 2016-02-22 16.04.0-10.armhf canonical

  I see this when I'm activating a wifi card on a raspberry pi 2.

  root@localhost:~# ifdown wlan0
  ifdown: interface wlan0 not configured
  root@localhost:~# ifup wlan0
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/wlan0/c4:e9:84:17:31:9b
  Sending on   LPF/wlan0/c4:e9:84:17:31:9b
  Sending on   Socket/fallback
  DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x81c0c95e)
  DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 (xid=0x81c0c95e)
  DHCPREQUEST of 192.168.0.170 on wlan0 to 255.255.255.255 port 67 
(xid=0x5ec9c081)
  DHCPOFFER of 192.168.0.170 from 192.168.0.251
  DHCPACK of 192.168.0.170 from 192.168.0.251
  RTNETLINK answers: File exists
  bound to 192.168.0.170 -- renewal in 17145 seconds.
  run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1
  Failed to bring up wlan0.

  ===
  [Impact]

  Installing ubuntu-fan can trigger error messages when initialising
  with no fan configuration.

  [Test Case]

  As above.

  [Regression Potential]

  Low, suppresses errorneous error messages.

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

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

[Kernel-packages] [Bug 1551747] Re: ubuntu-fan causes issues during network configuration

Confirmed "/usr/sbin/fanctl net start ens3" now exits 0 in the face of
an empty configuration.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  ubuntu-fan causes issues during network configuration

Status in cloud-init:
  New
Status in Snappy:
  Confirmed
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Yakkety:
  Fix Released

Bug description:
  it seems that ubuntu-fan is causing issues with network configuration.

  On 16.04 daily image:

  root@localhost:~# snappy list
  NameDate   Version  Developer
  canonical-pi2   2016-02-02 3.0  canonical
  canonical-pi2-linux 2016-02-03 4.3.0-1006-3 canonical
  ubuntu-core 2016-02-22 16.04.0-10.armhf canonical

  I see this when I'm activating a wifi card on a raspberry pi 2.

  root@localhost:~# ifdown wlan0
  ifdown: interface wlan0 not configured
  root@localhost:~# ifup wlan0
  Internet Systems Consortium DHCP Client 4.3.3
  Copyright 2004-2015 Internet Systems Consortium.
  All rights reserved.
  For info, please visit https://www.isc.org/software/dhcp/

  Listening on LPF/wlan0/c4:e9:84:17:31:9b
  Sending on   LPF/wlan0/c4:e9:84:17:31:9b
  Sending on   Socket/fallback
  DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3 (xid=0x81c0c95e)
  DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 (xid=0x81c0c95e)
  DHCPREQUEST of 192.168.0.170 on wlan0 to 255.255.255.255 port 67 
(xid=0x5ec9c081)
  DHCPOFFER of 192.168.0.170 from 192.168.0.251
  DHCPACK of 192.168.0.170 from 192.168.0.251
  RTNETLINK answers: File exists
  bound to 192.168.0.170 -- renewal in 17145 seconds.
  run-parts: /etc/network/if-up.d/ubuntu-fan exited with return code 1
  Failed to bring up wlan0.

  ===
  [Impact]

  Installing ubuntu-fan can trigger error messages when initialising
  with no fan configuration.

  [Test Case]

  As above.

  [Regression Potential]

  Low, suppresses errorneous error messages.

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

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

[Kernel-packages] [Bug 1586176] Re: [Yakkety] fanatic fails running docker test

Confirmed docker tests now install ping (and nc) as needed and complete
successfully.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  [Yakkety] fanatic fails running docker test

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed

Bug description:
  On Yakkety 16.10, fanatic fails trying to run docker tests and then
  hangs:

  $sudo fanatic
  Welcome to the fanatic fan networking wizard.  This will help you set
  up an example fan network and optionally configure docker and/or LXD to
  use this network.  See fanatic(1) for more details.

  Configure fan underlay (hit return to accept, or specify alternative) 
[192.168.0.0/16]:
  Configure fan overlay (hit return to accept, or specify alternative) 
[250.0.0.0/8]:
  LXD already configured
  Docker already configured
  Test LXD networking for underlay:192.168.1.16/16 overlay:250.0.0.0/8
  (NOTE: potentially triggers large image downloads) [Yn]: n
  Test docker networking for underlay:192.168.1.16/16 overlay:250.0.0.0/8
  (NOTE: potentially triggers large image downloads) [Yn]: Y
  local docker test: pulling container images ...
  Using default tag: latest
  latest: Pulling from library/ubuntu
  6d28225f8d96: Pull complete
  166102ec41af: Pull complete
  d09bfba2bd6a: Pull complete
  c80dad39a6c0: Pull complete
  a3ed95caeb02: Pull complete
  Digest: 
sha256:5718d664299eb1db14d87db7bfa6945b28879a67b74f36da3e34f5914866b71c
  Status: Downloaded newer image for ubuntu:latest
  local docker test: creating test container ...
  f0cc43d63b6f687e47773fb6087bf1615dc7f479ef8e536594e0f4ec6a08b404
  test master: ping test (250.1.16.0) ...
  test slave: ping test (250.1.16.1) ...
  test slave: ping test ... FAIL
  --- transcript start ---
  /bin/sh: 74: ping: not found
  --- transcript end ---
  test slave: short data test (250.1.16.0 -> 250.1.16.1) ...
  test master: ping test ... PASS
  test master: short data test (250.1.16.1 -> 250.1.16.0) ...

  ===
  [Impact]

  Unable to test docker configuration due to the removal of ping from
  the default images.

  [Test Case]

  Request docker configuration and testing.

  [Regression Potential]

  Low, only used during initial configuration.

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

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

[Kernel-packages] [Bug 1584878] Re: fanatic remote host test fails when using non-default subnet sizes

Confirmed remote tests now work on non-default network masks.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  fanatic remote host test fails when using non-default subnet sizes

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed

Bug description:
  When conducting the remote host testing, fanatic incorrectly
  calculates the ip for the remote test host on the Fan.

  My remote host ip's are 192.168.1.3 and 192.168.1.10.  I'm using non-
  default subnet sizes for the overlay/underlays (ie -o 250.99.0.0/16
  and -u 192.168.1.0/24).  Both LXD and Docker tests pass, but, as
  noted, the remote host testing fails:

  test slave: ping test (250.99.1.4) ...
  test slave: ping test ... FAIL

  You'll notice the ip is incorrect, 250.99.1.4.  It should be
  250.99.3.1 in this example.

  Raw output of failing fanatic test run is below:

  $ sudo fanatic
  Welcome to the fanatic fan networking wizard.  This will help you set
  up an example fan network and optionally configure docker and/or LXD to
  use this network.  See fanatic(1) for more details.

  Configure fan underlay (hit return to accept, or specify alternative) 
[192.168.0.0/16]: 192.168.1.0/24
  Configure fan overlay (hit return to accept, or specify alternative) 
[250.0.0.0/8]: 250.99.0.0/16
  Create LXD networking for underlay:192.168.1.0/24 overlay:250.99.0.0/16 [Yn]: 
Y
  Profile fan-250-99 created
  Create docker networking for underlay:192.168.1.0/24 overlay:250.99.0.0/16 
[Yn]: Y
  Test LXD networking for underlay:192.168.1.10/24 overlay:250.99.0.0/16
  (NOTE: potentially triggers large image downloads) [Yn]: Y
  local lxd test: creating test container (Ubuntu:16.04) ...
  Creating fanatic-test
  Starting fanatic-test
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  lxd test: Waiting for addresses on eth0 ...
  test master: ping test (250.99.10.166) ...
  test slave: ping test (250.99.10.1) ...
  test master: ping test ... PASS
  test master: short data test (250.99.10.1 -> 250.99.10.166) ...
  test slave: ping test ... PASS
  test slave: short data test (250.99.10.166 -> 250.99.10.1) ...
  test slave: short data ... PASS
  test master: short data ... PASS
  test slave: long data test (250.99.10.166 -> 250.99.10.1) ...
  test master: long data test (250.99.10.1 -> 250.99.10.166) ...
  test master: long data ... PASS
  test slave: long data ... PASS
  local lxd test: destroying test container ...
  local lxd test: test complete PASS (master=0 slave=0)
  Test docker networking for underlay:192.168.1.10/24 overlay:250.99.0.0/16
  (NOTE: potentially triggers large image downloads) [Yn]: Y
  local docker test: creating test container ...
  e47583ee4f18c95edfcb28e5b2514c0924527f30b3485f62d343fe8bf1000170
  test master: ping test (250.99.10.0) ...
  test slave: ping test (250.99.10.1) ...
  test master: ping test ... PASS
  test master: short data test (250.99.10.1 -> 250.99.10.0) ...
  test slave: ping test ... PASS
  test slave: short data test (250.99.10.0 -> 250.99.10.1) ...
  test slave: short data ... PASS
  test master: short data ... PASS
  test slave: long data test (250.99.10.0 -> 250.99.10.1) ...
  test master: long data test (250.99.10.1 -> 250.99.10.0) ...
  test master: long data ... PASS
  test slave: long data ... PASS
  local docker test: destroying test container ...
  fanatic-test
  fanatic-test
  local docker test: test complete PASS (master=0 slave=0)
  This host IP address: 192.168.1.10
  Remote test host IP address (none to skip): 192.168.1.3
  host test: starting ...
  test slave: ping test (250.99.1.4) ...
  test slave: ping test ... FAIL
  --- transcript start ---
  PING 250.99.1.4 (250.99.1.4) 56(84) bytes of data.
  From 250.99.10.1 icmp_seq=1 Destination Host Unreachable
  From 250.99.10.1 icmp_seq=2 Destination Host Unreachable
  From 250.99.10.1 icmp_seq=3 Destination Host Unreachable
  From 250.99.10.1 icmp_seq=4 Destination Host Unreachable
  From 250.99.10.1 icmp_seq=5 Destination Host Unreachable

  --- 250.99.1.4 ping statistics ---
  5 packets transmitted, 0 received, +5 errors, 100% packet loss, time 3998ms
  pipe 3
  --- transcript end ---
  test slave: short data test (250.99.10.1 -> 250.99.1.4) ...

  ===
  [Impact]

  Remote host testing does not function correctly with non-default
  overlay/underlay combinations.

  [Test Case]

  As above.

  [Regression Potential]

  Low, this is only used during initial setup.

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

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

[Kernel-packages] [Bug 1584775] Re: fanatic does not use the correct LXD command to import image for fanatic-test container

Confirmed this now directly references the most recent lts image.  We no
longer attempt to run the lxd-images.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  fanatic does not use the correct LXD command to import image for
  fanatic-test container

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed

Bug description:
  Something I noticed while trying to use fanatic (see related bug
  1584692):

  /usr/sbin/fanatic: 808: /usr/sbin/fanatic: lxd-images: not found

  Because of this the lxd test cannot spin up the test container, as it can't 
import the image.
  I managed to get it to work by patching fanatic like this:

  ---
  # Check if we have images already...
  lxc image show fanatic-test >/dev/null 2>&1
  if [ "$?" -ne 0 ]; then
  echo "local lxd test: pulling container images ..."
  lxc image copy ubuntu:xenial local: --alias fanatic-test
  local rc="$?"
  if [ "$rc" -ne 0 ]; then
  echo "local lxd test: lxc image import failure, 
skipping test."
  return "$rc"
  fi
  fi
  ---

  There's no lxd-images on my machine and I suspect it used to be one in
  an earlier version of the LXD package. I'm using lxd 2.0.1-0ubuntu1~16
  amd64

  ubuntu-fan is 0.9.0

  ===
  [Impact]

  LXC has changed how images are fetched.  Preventing testing of a new
  install.

  [Test Case]

  Setup the default fan overlay/underlay and request LXC testing.

  [Regression Potential]

  Low, this is only used during initial setup.

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

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

[Kernel-packages] [Bug 1584692] Re: fanatic does not use the user-specified underlay, but 192.168.0.0/16

Confirmed that manually supplying only the underlay address with take
that and the default overlay addresses.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  fanatic does not use the user-specified underlay, but 192.168.0.0/16

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed

Bug description:
  On a xenial machine, I tried to use fanatic to configure the fan with
  underlay 10.88.0.0/16 and the suggested overlay 250.0.0.0/8, but the
  underlay suggested by fanatic (192.168.0.0/16) was used instead of
  10.88.0.0/16 I specified.

  Here's the paste of the session: http://paste.ubuntu.com/16630235/

  ===
  [Impact]

  Configuration for some combinations which including using the default
  overlay only will be miss-parsed.

  [Test Case]

  As above.

  [Regression Potential]

  Low, only affects new setup.

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

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

[Kernel-packages] [Bug 1582956] Re: fan[ctl | atic] man page has reference to ubuntu.com/fan which 404s

Confirmed reference now gone.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  fan[ctl | atic]  man page has reference to ubuntu.com/fan which 404s

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed

Bug description:
  Reading the man page for fanctl and fanatic I see a reference to
  ubuntu.com/fan, but that page is currently 404'ing

  Specifically:

  $ man fanctl
   -or-
  $ man fanatic

  . . .

  SEE ALSO
     fanctl(8) /usr/share/doc/ubuntu-fan/README
     http://www.ubuntu.com/fan

  ===
  [Impact]

  Missleading documentation.

  [Test Case]

  Confirm non-existant link is removed from manual page.

  [Regression Potential]

  None, non functional change.

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

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

[Kernel-packages] [Bug 1584092] Re: Docker misconfigured when using non-default overlay/underlay netmask size

Confirmed that appropriate non-default masks now produce sensible docket
configurations.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  Docker misconfigured when using non-default overlay/underlay netmask
  size

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed

Bug description:
  Fan allows for variable sized subnet map sizes.  For example, if I
  want to map a /24 to a /16 instead of the default /16 to /8, Fan
  supports this.  However, when configuring this via fanatic, I see that
  docker configuration fails.  In /etc/default/docker, the --fixed-cidr
  flag is defined incorrectly.

  $ sudo fanatic
  Welcome to the fanatic fan networking wizard.  This will help you set
  up an example fan network and optionally configure docker and/or LXD touse 
this network.  See fanatic(1) for more details.

  Configure fan underlay (hit return to accept, or specify alternative) 
[192.168.0.0/16]: 192.168.1.0/24
  Configure fan overlay (hit return to accept, or specify alternative) 
[250.0.0.0/8]: 250.99.0.0/16
  Create LXD networking for underlay:192.168.1.0/24 overlay:250.99.0.0/16 [Yn]: 
Y
  Profile fan-250-99 created
  Create docker networking for underlay:192.168.1.0/24 overlay:250.99.0.0/16 
[Yn]: Y
  Job for docker.service failed because the control process exited with error 
code. See "systemctl status docker.service" and "journalctl -xe" for details.
  Test LXD networking for underlay:192.168.1.10/24 overlay:250.99.0.0/16
  (NOTE: potentially triggers large image downloads) [Yn]: n
  Test docker networking for underlay:192.168.1.10/24 overlay:250.99.0.0/16
  (NOTE: potentially triggers large image downloads) [Yn]: n
  This host IP address: 192.168.1.10
  Remote test host IP address (none to skip):
  /usr/sbin/fanatic: Testing skipped

  $ grep "DOCKER_OPTS" /etc/default/docker
  # Use DOCKER_OPTS to modify the daemon startup options.
  #DOCKER_OPTS="--dns 8.8.8.8 --dns 8.8.4.4"
  DOCKER_OPTS=" -b fan-250-99 --mtu=1450 --iptables=false 
--fixed-cidr=250.99.10.0/40"

  May 20 05:15:30 macbook docker[27364]:
  time="2016-05-20T05:15:30.411933688-07:00" level=fatal msg="Error
  starting daemon: Error initializing network controller: invalid CIDR
  address: 250.99.10.0/40"

  ===
  [Impact]

  Non default network splits are not honoured correctly.

  [Test Case]

  Setup fan with non /8 /16 split, as per reporter.

  [Regression Potential]

  Low, as these currently do not work correctly.

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

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

[Kernel-packages] [Bug 1584150] Re: fanatic: legacy mode triggers syntax error

Confirmed can now use legacy mode.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  fanatic: legacy mode triggers syntax error

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed

Bug description:
  Attempting to use the legacy command line format leads to a syntax
  error.

  ===
  [Impact]

  Legacy use cases will fail.

  [Test Case]

  Confirm "fanctl up 250.0.0.0/8 192.168.0.0/16" is parsed correctly.

  [Regression Potential]

  Low, these are rarely used.

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

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

[Kernel-packages] [Bug 1535054] Re: fanatic doesn't respond to --help

Confirmed new help functionality is now available.

** Tags removed: verification-needed
** Tags added: verification-done

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

Title:
  fanatic doesn't respond to --help

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed

Bug description:
  Trying out fanatic today I found it didn't respect a lot of
  conventional input, like --help or -h.

  Please provide useful output for -? and -h and --help as well as
  "fanatic help"

  Also, you have a typo with "uknown command" :)

  Thanks!

  ===
  [Impact]

  Barrier to user adoption.

  [Test Case]

  Confirm fanatic --help et al produce useful output.

  [Regression Potential]

  Low, these are only triggered by specific command line forms.

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

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

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

apport information

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

Title:
  booting new 3.19.0-65, monitor stays in power save

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last two kernel updates boot but the monitor stays in "power save"
  mode, so i can't do anything from keyboard.  I can login via ethernet.
  The failing upgrades were 3.19.0-64 and 3.19.0-65. Everything works if
  i revert back to 3.19.0-61.  64-bit kernel on dell inspiron 3252

  attachment is from running working 0-61
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dunigan2046 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=df810611-f3c4-4a35-82db-3eb71f58a145
  InstallationDate: Installed on 2016-02-13 (152 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 3252
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic 
root=UUID=dc45dd36-b97d-465b-8602-f72c422b6bc0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware 1.127.22
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.3
  dmi.board.name: 0WVYMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.3:bd09/08/2015:svnDellInc.:pnInspiron3252:pvr2.2.3:rvnDellInc.:rn0WVYMC:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3252
  dmi.product.version: 2.2.3
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  booting new 3.19.0-65, monitor stays in power save

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last two kernel updates boot but the monitor stays in "power save"
  mode, so i can't do anything from keyboard.  I can login via ethernet.
  The failing upgrades were 3.19.0-64 and 3.19.0-65. Everything works if
  i revert back to 3.19.0-61.  64-bit kernel on dell inspiron 3252

  attachment is from running working 0-61
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dunigan2046 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=df810611-f3c4-4a35-82db-3eb71f58a145
  InstallationDate: Installed on 2016-02-13 (152 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 3252
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic 
root=UUID=dc45dd36-b97d-465b-8602-f72c422b6bc0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware 1.127.22
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.3
  dmi.board.name: 0WVYMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.3:bd09/08/2015:svnDellInc.:pnInspiron3252:pvr2.2.3:rvnDellInc.:rn0WVYMC:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3252
  dmi.product.version: 2.2.3
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  booting new 3.19.0-65, monitor stays in power save

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last two kernel updates boot but the monitor stays in "power save"
  mode, so i can't do anything from keyboard.  I can login via ethernet.
  The failing upgrades were 3.19.0-64 and 3.19.0-65. Everything works if
  i revert back to 3.19.0-61.  64-bit kernel on dell inspiron 3252

  attachment is from running working 0-61
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dunigan2046 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=df810611-f3c4-4a35-82db-3eb71f58a145
  InstallationDate: Installed on 2016-02-13 (152 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 3252
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic 
root=UUID=dc45dd36-b97d-465b-8602-f72c422b6bc0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware 1.127.22
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.3
  dmi.board.name: 0WVYMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.3:bd09/08/2015:svnDellInc.:pnInspiron3252:pvr2.2.3:rvnDellInc.:rn0WVYMC:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3252
  dmi.product.version: 2.2.3
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  booting new 3.19.0-65, monitor stays in power save

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last two kernel updates boot but the monitor stays in "power save"
  mode, so i can't do anything from keyboard.  I can login via ethernet.
  The failing upgrades were 3.19.0-64 and 3.19.0-65. Everything works if
  i revert back to 3.19.0-61.  64-bit kernel on dell inspiron 3252

  attachment is from running working 0-61
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dunigan2046 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=df810611-f3c4-4a35-82db-3eb71f58a145
  InstallationDate: Installed on 2016-02-13 (152 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 3252
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic 
root=UUID=dc45dd36-b97d-465b-8602-f72c422b6bc0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware 1.127.22
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.3
  dmi.board.name: 0WVYMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.3:bd09/08/2015:svnDellInc.:pnInspiron3252:pvr2.2.3:rvnDellInc.:rn0WVYMC:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3252
  dmi.product.version: 2.2.3
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  booting new 3.19.0-65, monitor stays in power save

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last two kernel updates boot but the monitor stays in "power save"
  mode, so i can't do anything from keyboard.  I can login via ethernet.
  The failing upgrades were 3.19.0-64 and 3.19.0-65. Everything works if
  i revert back to 3.19.0-61.  64-bit kernel on dell inspiron 3252

  attachment is from running working 0-61
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dunigan2046 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=df810611-f3c4-4a35-82db-3eb71f58a145
  InstallationDate: Installed on 2016-02-13 (152 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 3252
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic 
root=UUID=dc45dd36-b97d-465b-8602-f72c422b6bc0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware 1.127.22
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.3
  dmi.board.name: 0WVYMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.3:bd09/08/2015:svnDellInc.:pnInspiron3252:pvr2.2.3:rvnDellInc.:rn0WVYMC:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3252
  dmi.product.version: 2.2.3
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  booting new 3.19.0-65, monitor stays in power save

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last two kernel updates boot but the monitor stays in "power save"
  mode, so i can't do anything from keyboard.  I can login via ethernet.
  The failing upgrades were 3.19.0-64 and 3.19.0-65. Everything works if
  i revert back to 3.19.0-61.  64-bit kernel on dell inspiron 3252

  attachment is from running working 0-61
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dunigan2046 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=df810611-f3c4-4a35-82db-3eb71f58a145
  InstallationDate: Installed on 2016-02-13 (152 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 3252
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic 
root=UUID=dc45dd36-b97d-465b-8602-f72c422b6bc0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware 1.127.22
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.3
  dmi.board.name: 0WVYMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.3:bd09/08/2015:svnDellInc.:pnInspiron3252:pvr2.2.3:rvnDellInc.:rn0WVYMC:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3252
  dmi.product.version: 2.2.3
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  booting new 3.19.0-65, monitor stays in power save

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last two kernel updates boot but the monitor stays in "power save"
  mode, so i can't do anything from keyboard.  I can login via ethernet.
  The failing upgrades were 3.19.0-64 and 3.19.0-65. Everything works if
  i revert back to 3.19.0-61.  64-bit kernel on dell inspiron 3252

  attachment is from running working 0-61
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dunigan2046 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=df810611-f3c4-4a35-82db-3eb71f58a145
  InstallationDate: Installed on 2016-02-13 (152 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 3252
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic 
root=UUID=dc45dd36-b97d-465b-8602-f72c422b6bc0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware 1.127.22
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.3
  dmi.board.name: 0WVYMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.3:bd09/08/2015:svnDellInc.:pnInspiron3252:pvr2.2.3:rvnDellInc.:rn0WVYMC:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3252
  dmi.product.version: 2.2.3
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  booting new 3.19.0-65, monitor stays in power save

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last two kernel updates boot but the monitor stays in "power save"
  mode, so i can't do anything from keyboard.  I can login via ethernet.
  The failing upgrades were 3.19.0-64 and 3.19.0-65. Everything works if
  i revert back to 3.19.0-61.  64-bit kernel on dell inspiron 3252

  attachment is from running working 0-61
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dunigan2046 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=df810611-f3c4-4a35-82db-3eb71f58a145
  InstallationDate: Installed on 2016-02-13 (152 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 3252
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic 
root=UUID=dc45dd36-b97d-465b-8602-f72c422b6bc0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware 1.127.22
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.3
  dmi.board.name: 0WVYMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.3:bd09/08/2015:svnDellInc.:pnInspiron3252:pvr2.2.3:rvnDellInc.:rn0WVYMC:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3252
  dmi.product.version: 2.2.3
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  booting new 3.19.0-65, monitor stays in power save

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last two kernel updates boot but the monitor stays in "power save"
  mode, so i can't do anything from keyboard.  I can login via ethernet.
  The failing upgrades were 3.19.0-64 and 3.19.0-65. Everything works if
  i revert back to 3.19.0-61.  64-bit kernel on dell inspiron 3252

  attachment is from running working 0-61
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dunigan2046 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=df810611-f3c4-4a35-82db-3eb71f58a145
  InstallationDate: Installed on 2016-02-13 (152 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 3252
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic 
root=UUID=dc45dd36-b97d-465b-8602-f72c422b6bc0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware 1.127.22
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.3
  dmi.board.name: 0WVYMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.3:bd09/08/2015:svnDellInc.:pnInspiron3252:pvr2.2.3:rvnDellInc.:rn0WVYMC:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3252
  dmi.product.version: 2.2.3
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1603397] BootDmesg.txt

apport information

** Attachment added: "BootDmesg.txt"
   
https://bugs.launchpad.net/bugs/1603397/+attachment/4701443/+files/BootDmesg.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/1603397

Title:
  booting new 3.19.0-65, monitor stays in power save

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last two kernel updates boot but the monitor stays in "power save"
  mode, so i can't do anything from keyboard.  I can login via ethernet.
  The failing upgrades were 3.19.0-64 and 3.19.0-65. Everything works if
  i revert back to 3.19.0-61.  64-bit kernel on dell inspiron 3252

  attachment is from running working 0-61
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dunigan2046 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=df810611-f3c4-4a35-82db-3eb71f58a145
  InstallationDate: Installed on 2016-02-13 (152 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 3252
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic 
root=UUID=dc45dd36-b97d-465b-8602-f72c422b6bc0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware 1.127.22
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.3
  dmi.board.name: 0WVYMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.3:bd09/08/2015:svnDellInc.:pnInspiron3252:pvr2.2.3:rvnDellInc.:rn0WVYMC:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3252
  dmi.product.version: 2.2.3
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1603397] UdevLog.txt

apport information

** Attachment added: "UdevLog.txt"
   
https://bugs.launchpad.net/bugs/1603397/+attachment/4701456/+files/UdevLog.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/1603397

Title:
  booting new 3.19.0-65, monitor stays in power save

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last two kernel updates boot but the monitor stays in "power save"
  mode, so i can't do anything from keyboard.  I can login via ethernet.
  The failing upgrades were 3.19.0-64 and 3.19.0-65. Everything works if
  i revert back to 3.19.0-61.  64-bit kernel on dell inspiron 3252

  attachment is from running working 0-61
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dunigan2046 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=df810611-f3c4-4a35-82db-3eb71f58a145
  InstallationDate: Installed on 2016-02-13 (152 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 3252
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic 
root=UUID=dc45dd36-b97d-465b-8602-f72c422b6bc0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware 1.127.22
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.3
  dmi.board.name: 0WVYMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.3:bd09/08/2015:svnDellInc.:pnInspiron3252:pvr2.2.3:rvnDellInc.:rn0WVYMC:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3252
  dmi.product.version: 2.2.3
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  booting new 3.19.0-65, monitor stays in power save

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last two kernel updates boot but the monitor stays in "power save"
  mode, so i can't do anything from keyboard.  I can login via ethernet.
  The failing upgrades were 3.19.0-64 and 3.19.0-65. Everything works if
  i revert back to 3.19.0-61.  64-bit kernel on dell inspiron 3252

  attachment is from running working 0-61
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dunigan2046 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=df810611-f3c4-4a35-82db-3eb71f58a145
  InstallationDate: Installed on 2016-02-13 (152 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 3252
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic 
root=UUID=dc45dd36-b97d-465b-8602-f72c422b6bc0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware 1.127.22
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.3
  dmi.board.name: 0WVYMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.3:bd09/08/2015:svnDellInc.:pnInspiron3252:pvr2.2.3:rvnDellInc.:rn0WVYMC:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3252
  dmi.product.version: 2.2.3
  dmi.sys.vendor: Dell Inc.

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

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

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

apport information

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

Title:
  booting new 3.19.0-65, monitor stays in power save

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last two kernel updates boot but the monitor stays in "power save"
  mode, so i can't do anything from keyboard.  I can login via ethernet.
  The failing upgrades were 3.19.0-64 and 3.19.0-65. Everything works if
  i revert back to 3.19.0-61.  64-bit kernel on dell inspiron 3252

  attachment is from running working 0-61
  --- 
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dunigan2046 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=df810611-f3c4-4a35-82db-3eb71f58a145
  InstallationDate: Installed on 2016-02-13 (152 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Dell Inc. Inspiron 3252
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-61-generic 
root=UUID=dc45dd36-b97d-465b-8602-f72c422b6bc0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-61.69~14.04.1-generic 3.19.8-ckt21
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-61-generic N/A
   linux-backports-modules-3.19.0-61-generic  N/A
   linux-firmware 1.127.22
  Tags:  trusty
  Uname: Linux 3.19.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo uucp
  _MarkForUpload: True
  dmi.bios.date: 09/08/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.2.3
  dmi.board.name: 0WVYMC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.2.3:bd09/08/2015:svnDellInc.:pnInspiron3252:pvr2.2.3:rvnDellInc.:rn0WVYMC:rvrA00:cvnDellInc.:ct3:cvrNotSpecified:
  dmi.product.name: Inspiron 3252
  dmi.product.version: 2.2.3
  dmi.sys.vendor: Dell Inc.

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

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

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