[Kernel-packages] [Bug 1514711] Re: Installer doesn't include ast GPU driver for OpenPower machines

2016-01-20 Thread Tim Gardner
Jeremy - use livecd-rootfs ? I'd ask on #ubuntu-devel.

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

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

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

Title:
  Installer doesn't include ast GPU driver for OpenPower machines

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  When booting the Ubuntu 14.03.4 installer on an OpenPower machine with
  a VGA monitor attached, we see no output - the only installer output
  is over the physical UART (or SOL session).

  Petitboot is displayed over both VGA and UART, but not the installer
  UI.

  It seems like the ast GPU driver isn't present on the installer image
  (but is present for the non-installer kernels), which is required for
  graphics output on these machines.

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

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


[Kernel-packages] [Bug 1514711] Re: Installer doesn't include ast GPU driver for OpenPower machines

2016-01-20 Thread Tim Gardner
** Changed in: linux (Ubuntu Vivid)
   Status: In Progress => Fix Committed

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

Title:
  Installer doesn't include ast GPU driver for OpenPower machines

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  When booting the Ubuntu 14.03.4 installer on an OpenPower machine with
  a VGA monitor attached, we see no output - the only installer output
  is over the physical UART (or SOL session).

  Petitboot is displayed over both VGA and UART, but not the installer
  UI.

  It seems like the ast GPU driver isn't present on the installer image
  (but is present for the non-installer kernels), which is required for
  graphics output on these machines.

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

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


[Kernel-packages] [Bug 1536285] Re: linux-lts-trusty: 3.13.0-77.121~precise1 -proposed tracker

2016-01-20 Thread Brad Figg
All builds are complete, packages in this bug can be copied to
-proposed.

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

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

** Description changed:

  This bug is for tracking the 3.13.0-77.121~precise1 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-stable-Prepare-package-start:Wednesday, 20. January 2016 17:20 UTC
- kernel-stable-phase:Prepare
- kernel-stable-phase-changed:Wednesday, 20. January 2016 17:20 UTC
  kernel-stable-master-bug:1535880
+ kernel-stable-phase:CopyToProposed
+ kernel-stable-Prepare-package-end:Thursday, 21. January 2016 01:02 UTC
+ kernel-stable-Promote-to-proposed-start:Thursday, 21. January 2016 01:02 UTC
+ kernel-stable-phase-changed:Thursday, 21. January 2016 01:02 UTC

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

Title:
  linux-lts-trusty: 3.13.0-77.121~precise1 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-77.121~precise1 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-stable-Prepare-package-start:Wednesday, 20. January 2016 17:20 UTC
  kernel-stable-master-bug:1535880
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Thursday, 21. January 2016 01:02 UTC
  kernel-stable-Promote-to-proposed-start:Thursday, 21. January 2016 01:02 UTC
  kernel-stable-phase-changed:Thursday, 21. January 2016 01:02 UTC

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

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


[Kernel-packages] [Bug 1531824] Re: Xorg freeze

2016-01-20 Thread Christopher M. Penalver
Phill, both.

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

Title:
  Xorg freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Symptoms:

  * Video is frozen.

  Observations:

  * Mouse moves normally.
  * There is no hard-disc activity.
  * Once  minute or so the video will respond like it's doing so a frame at a 
time.
  * Pressing CTRL+ALT+F6 and then waiting a minute or so puts you into a 
terminal.
  * Text terminals work normally without any problems.
  * Pressing ALT+F7 from a text terminal puts you into either black frozen 
screen or a frozen graphical display.
  * Restarting LightDM doesn't resolve the problem, it shows the login screen 
and freezes.

  When does it occur:

  * More often than not on or immediately after resume from suspend.
  * Occasionally, but not very often, during normal use.
  * It occurs several times a week, usually after several hours of suspend.

  It started a few months ago.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20
  Uname: Linux 3.16.0-57-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  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 Jan  7 11:29:40 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 4.3.34, 3.16.0-56-generic, x86_64: installed
   virtualbox, 4.3.34, 3.16.0-57-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e22] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
 Subsystem: ASUSTeK Computer Inc. Device [1043:8276]
  InstallationDate: Installed on 2015-07-13 (177 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: System manufacturer V-P5G45
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-57-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0405
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: V-P5G45
  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.:bvr0405:bd05/18/2009:svnSystemmanufacturer:pnV-P5G45:pvrSystemVersion:rvnASUSTeKComputerINC.:rnV-P5G45:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: V-P5G45
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Jan  7 11:11:57 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   41085 
   vendor DEL
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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


[Kernel-packages] [Bug 1536428] [NEW] package linux-image-extra-3.19.0-47-generic 3.19.0-47.53~14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit stat

2016-01-20 Thread CelticWhisper
Public bug reported:

Error appeared while not taking any action related to distro upgrade.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.19.0-47-generic 3.19.0-47.53~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-43.49~14.04.1-generic 3.19.8-ckt10
Uname: Linux 3.19.0-43-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
Date: Wed Jan 20 19:17:59 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-12-14 (37 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.5
 apt  1.0.1ubuntu2.10
SourcePackage: linux-lts-vivid
Title: package linux-image-extra-3.19.0-47-generic 3.19.0-47.53~14.04.1 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  package linux-image-extra-3.19.0-47-generic 3.19.0-47.53~14.04.1
  failed to install/upgrade: subprocess installed post-installation
  script returned error exit status 1

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  Error appeared while not taking any action related to distro upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.19.0-47-generic 3.19.0-47.53~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-43.49~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-43-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  Date: Wed Jan 20 19:17:59 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-12-14 (37 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.10
  SourcePackage: linux-lts-vivid
  Title: package linux-image-extra-3.19.0-47-generic 3.19.0-47.53~14.04.1 
failed to install/upgrade: subprocess installed post-installation script 
returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2016-01-20 Thread bugproxy
--- Comment From praveen.pan...@in.ibm.com 2016-01-21 00:20 EDT---
Hi ,

Tested on today build and it works fine .

root@tuleta4u-lp6:~# vim /etc/default/kdump-tools
root@tuleta4u-lp6:~# kdump-config load
* fadump registered successfully
root@tuleta4u-lp6:~# dpkg -l | grep makedumpfile
ii  makedumpfile   1.5.5-2ubuntu1.5 ppc64el 
 VMcore extraction tool
root@tuleta4u-lp6:~#

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

Title:
  Unable to configure Firmware Assisted dump

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Trusty:
  Fix Released

Bug description:
  [SRU justification]
  This represent a hardware enablement SRU : Firmware assisted dumps (fadump) 
are not possible on LTS.

  [Impact]
  The fadump mechanism cannot be used on Power systems running Trusty

  [Fix]
  Backport fadump functionality from makedumpfile 1.5.8 present in Wily and 
onward.

  [Test Case]
  See comment #9 : The proposed SRU has been tested from a PPA on a Power VM.

  [Regression]
  None expected from a functionality point of view as it is a new feature. 
Existing code paths are minimally modified.

  [Original description of the problem]

  ---Steps to Reproduce---
  1) Using latest daily ISO install 14.04.02 as a Power VM guest.
  2) Upgrade the kernel to 3.19 level (3.19.0-18-generic)
  3) In order to use Firmware Assisted Dump feature update the kernel command 
with fadump=on.
  4) Reboot.

  Post reboot using kdump-config load command fails with following
  message :

  # kdump-config load
  Memory for crashkernel is not reserved
  Please reserve memory by passing"crashkernel=X@Y" parameter to kernel
  Then try to loading kdump kernel
   * failed to load kdump kernel

  # kdump-config status
  current state   : Not ready to kdump
  #

  # cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-3.19.0-18-generic 
root=UUID=3ea23bcf-7269-432f-bacc-f82c6cdd774e ro splash quiet fadump=on 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
vt.handoff=7
  # cat /sys/kernel/fadump_enabled
  1
  # cat /sys/kernel/fadump_registered
  0
  #

  # dmesg | grep -i Firmware
  [0.00] Reserved 5120MB of memory at 97279MB for firmware-assisted dump
  [0.00] firmware_features = 0x0001c45ffc5f
  #
  # cat /boot/config-3.19.0-18-generic | grep -i FA_DUMP
  CONFIG_FA_DUMP=y
  #

  Are there any user space fixes missing which prevents me from
  configuring firmware assisted dump ?

  == Comment: #4 - Hari Krishna Bathini  - 2015-06-12 
05:28:24 ==
  This patch makes kdump-tools fadump aware so as to switch between
  kdump & fadump seemlessly based on the dump method enabled (fadump/kdump).

  Thanks
  Hari

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

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


[Kernel-packages] [Bug 1528005] Re: 10ec:8821 rtl8821ae has no connectivity in 5GHz networks

2016-01-20 Thread Christopher M. Penalver
Simon Naunton, it will help immensely if you filed a new report with the Ubuntu 
repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

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

Title:
  10ec:8821 rtl8821ae has no connectivity in 5GHz networks

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Attempting to connect to a ASUS Wireless Router RT-AC51U (firmware
  3.0.0.4.378_9135-gac2b2c2on) on 5GHz I get an IP address and
  everything, but no connectivity. I cannot ping the router.

  WORKAROUND: Execute via a terminal:
  git clone https://github.com/lwfinger/rtlwifi_new.git
  cd rtlwifi_new
  sudo make install
  sudo restart now

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-2-generic 4.3.0-2.11 [modified: 
boot/vmlinuz-4.3.0-2-generic]
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mikaela1567 F pulseaudio
   /dev/snd/controlC1:  mikaela1567 F pulseaudio
  CurrentDesktop: MATE
  Date: Sun Dec 20 16:01:13 2015
  HibernationDevice: RESUME=UUID=431ec214-73ef-4058-b283-5721bb5a45d2
  InstallationDate: Installed on 2015-12-12 (7 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151212)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp.
   Bus 001 Device 006: ID 13d3:3414 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic.efi.signed 
root=UUID=ab0e7270-40bc-4a68-a541-59fd96690354 ro rw acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-2-generic N/A
   linux-backports-modules-4.3.0-2-generic  N/A
   linux-firmware   1.154
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Tiedostoa tai hakemistoa ei ole: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  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: 
dmi:bvnAmericanMegatrendsInc.:bvrX550JX.204:bd05/07/2015:svnASUSTeKCOMPUTERINC.:pnX550JX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JX
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1507472] Re: XHCI controller causing MacbookPro12, 1 to resume immediately after suspend

2016-01-20 Thread Christopher M. Penalver
Michael Gratton, 4.4 is not older than 4.4-rc8. Its time stamp is
earlier because of changes made to the folder, not due to chronology.

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

Title:
  XHCI controller causing MacbookPro12,1 to resume immediately after
  suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my MacbookPro12,1 with Wily and Linux 4.2, by default the kernel
  successfully suspends but then immediately resumes again. The problem
  seems to be the XHCI controller causing spurious ACPI wakeups.

  Also, the Broadcom wifi module seems to have problems with
  suspend/resume, so I am also unloading the `brcmfmac` module prior to
  suspend and loading it again after resume.

  WORKAROUND: Disable XHC1 prior to sleeping:
  > # echo XHC1 > /proc/acpi/wakeup

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mjg1441 F pulseaudio
   /dev/snd/controlC0:  mjg1441 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Oct 19 18:13:15 2015
  HibernationDevice: RESUME=UUID=bc879a1f-ac27-48ae-82dd-3c81b7307dd0
  InstallationDate: Installed on 2015-07-22 (89 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc.
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash acpi_backlight=vendor 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  RfKill:
   3: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-08-27 (52 days ago)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B07.1506051617
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B07.1506051617:bd06/05/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1525324] Re: kernel/bonding: wrong netlink messages when deleting a bonding interface

2016-01-20 Thread Christopher M. Penalver
** Tags removed: 6wind
** Tags added: cherry-pick

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

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

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

Title:
  kernel/bonding: wrong netlink messages when deleting a bonding
  interface

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Here is the bug:

  root@ubuntu1404:~# modprobe bonding
  root@ubuntu1404:~# modprobe dummy
  root@ubuntu1404:~# ip link set dummy0 master bond0
  root@ubuntu1404:~# ip monitor link&
  [1] 1065
  root@ubuntu1404:~# ip link del bond0
  Deleted 6: bond0:  mtu 1500 qdisc noop state DOWN 
group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  7: dummy0:  mtu 1500 qdisc noqueue state 
UNKNOWN group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  7: dummy0:  mtu 1500 qdisc noqueue state UNKNOWN 
group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  6: bond0:  mtu 1500 qdisc noop state DOWN group 
default 
  link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff
  6: bond0:  mtu 1500 qdisc noop state DOWN group 
default 
  root@ubuntu1404:~# link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff
  7: dummy0:  mtu 1500 qdisc noqueue state DOWN group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  7: dummy0:  mtu 1500 qdisc noqueue state DOWN group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  ^C
  root@ubuntu1404:~# uname -a
  Linux ubuntu1404 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux
  root@ubuntu1404:~#

  A netlink message advertise that bond0 is deleted and after that two
  netlink messages are sent telling that bond0 exists again.

  This bug has been fixed by these upstream commits:
  56bfa7ee7c88 unregister_netdevice : move RTM_DELLINK to until after ndo_uninit
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=56bfa7ee7c88
  395eea6ccf2b rtnetlink: delay RTM_DELLINK notification until after 
ndo_uninit()
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=395eea6ccf2b

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

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


[Kernel-packages] [Bug 1511196] Re: System wakeup disabled by ACPI

2016-01-20 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  System wakeup disabled by ACPI

Status in linux package in Ubuntu:
  Expired

Bug description:
  What you’re trying to achieve:
  1. I was trying to 'suspend to ram'  my Computer through Xubuntu.

  What steps you take:

  1. Clicked the Xfce Blue Mouse Mascot.
  2. Clicked the Logout icon from the XFCE Menu.
  3. Clicked Suspend.

  What happens:
  1. The computer simply shuts itself down without suspending to the ram and 
kills all the USB Ports (I used to use USB ports even when computer is 
suspended to ram).
  2. The computer forces a fsck after hitting the power button again and 
recovers the file system (ext4) from an unclean shutdown from the issue above.

  What should happen instead:
  1. The computer should have suspended itself to ram.
  2. The USB ports should have continued to function in this low power mode.

  Additional Information:
    I have tried playing around with 'Hibernate' rather than 'Suspend' too and 
hibernate works as it suspends to disk. However, hibernate is not an option in 
my Xubuntu. Although I rather use suspend to ram  anyway as it is more useful. 
During playing around to see what works and what does not. I have suspended my 
computer with systemctl  hybrid-sleep and the computer resumes only because in 
this dual mode the 'hibernate' portion from 'hybrid-sleep' works. Here is dmesg:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511196/+attachment/4523050/+files/dmesg

  I have tried this on multiple distros with similar results but I like
  Ubuntu (and flavours used Ubuntu since 4.04) the most and hope this
  can be fixed. If you need anything else for the logs please let me
  know.

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

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


[Kernel-packages] [Bug 1528005] Re: 10ec:8821 rtl8821ae has no connectivity in 5GHz networks

2016-01-20 Thread Simon Naunton
Same problem here (yesterday, 2016-01-20) on a Lenovo Ideapad 300
(80Q7008EAU - 15.6" i5 8Gb 1TB) on fresh install of amd64 Wily/15.10.
Wifi worked ok under Windows 10 home that came with it.

rtl8821ae driver loaded. Connected to AP fine. Got IP address, GW, DNS
etc correctly, but no traffic.

Workaround worked fine:
git clone https://github.com/lwfinger/rtlwifi_new.git
cd rtlwifi_new
sudo make install
sudo restart now

FWIW, proper 802.11ac speeds copying large files.

Same problem after apt-get upgrade installed latest kernel  at time of
writing (sorry, my laptop is at home and I am at work, so no kernel
versions quote here, but more than likely linux-image-4.2.0-25-generic).
make installed the above driver again and all good.

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

Title:
  10ec:8821 rtl8821ae has no connectivity in 5GHz networks

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Attempting to connect to a ASUS Wireless Router RT-AC51U (firmware
  3.0.0.4.378_9135-gac2b2c2on) on 5GHz I get an IP address and
  everything, but no connectivity. I cannot ping the router.

  WORKAROUND: Execute via a terminal:
  git clone https://github.com/lwfinger/rtlwifi_new.git
  cd rtlwifi_new
  sudo make install
  sudo restart now

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-2-generic 4.3.0-2.11 [modified: 
boot/vmlinuz-4.3.0-2-generic]
  ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0
  Uname: Linux 4.3.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mikaela1567 F pulseaudio
   /dev/snd/controlC1:  mikaela1567 F pulseaudio
  CurrentDesktop: MATE
  Date: Sun Dec 20 16:01:13 2015
  HibernationDevice: RESUME=UUID=431ec214-73ef-4058-b283-5721bb5a45d2
  InstallationDate: Installed on 2015-12-12 (7 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151212)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57b4 Realtek Semiconductor Corp.
   Bus 001 Device 006: ID 13d3:3414 IMC Networks
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X550JX
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-2-generic.efi.signed 
root=UUID=ab0e7270-40bc-4a68-a541-59fd96690354 ro rw acpi_osi=
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-2-generic N/A
   linux-backports-modules-4.3.0-2-generic  N/A
   linux-firmware   1.154
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Tiedostoa tai hakemistoa ei ole: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  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: 
dmi:bvnAmericanMegatrendsInc.:bvrX550JX.204:bd05/07/2015:svnASUSTeKCOMPUTERINC.:pnX550JX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550JX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550JX
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1440422] Re: No hardware mouse cursor with modesetting X driver

2016-01-20 Thread Christopher M. Penalver
Shevek, to see if this is already resolved upstream, could you please
test the latest mainline kernel (4.4) and advise to the results?

** Tags removed: bios-outdated-1.07
** Tags added: latest-bios-1.10

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

Title:
  No hardware mouse cursor with modesetting X driver

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Worked with linux-image-3.19.0-9-generic
  Does not work with linux-image-3.19.0-12-generic

  Adding Option "SWCursor" "on" to xorg.conf makes it work again.

  X.Org X Server 1.17.1
  Release Date: 2015-02-10

  Section "Device"
  Identifier "intel"
  Driver "modesetting"
  Option "SWCursor" "on"
  # Driver "intel"
  # Option "AccelMethod" "none"
  EndSection

  Not using intel driver because entirely too crashy.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-12-generic 3.19.0-12.12
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  shevek 3269 F pulseaudio
   /dev/snd/controlC0:  shevek 3269 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Apr  4 14:45:05 2015
  HibernationDevice: RESUME=UUID=cd97b65a-0d29-4887-a0e6-7c9eea8707b0
  InstallationDate: Installed on 2015-03-05 (30 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: LENOVO 20CKCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-12-generic.efi.signed 
root=/dev/mapper/xubuntu--vg-root ro quiet splash crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-12-generic N/A
   linux-backports-modules-3.19.0-12-generic  N/A
   linux-firmware 1.143
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (16 days ago)
  dmi.bios.date: 12/26/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET29W (1.05 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CKCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET29W(1.05):bd12/26/2014:svnLENOVO:pn20CKCTO1WW:pvrThinkPadT550:rvnLENOVO:rn20CKCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CKCTO1WW
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1255428] Re: 8086:0116 [Lenovo IdeaPad Z570] LCD brightness control keys and widget do not work on Intel Graphics

2016-01-20 Thread Christopher M. Penalver
Shriramana Sharma, that would be fine for now.

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

Title:
  8086:0116 [Lenovo IdeaPad Z570] LCD brightness control keys and widget
  do not work on Intel Graphics

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Saucy, on my Lenovo IdeaPad Z570 with Intel HD
  Graphics 3000, it is no longer possible to control the LCD brightness
  using the hardware brightness control keys. Likewise for the KDE power
  management settings or the battery icon on my Kubuntu Plasma tray. (I
  don't use GNOME/Unity.) Until Raring I did not have this problem.

  WORKAROUND: At a terminal:
  echo 150 | sudo tee /sys/class/backlight/intel_backlight/brightness

  where 150 is on the scale of 0 to whatever is given within
  /sys/class/backlight/intel_backlight/max_brightness. Based on this I
  wrote a GUI which however needs to be run using sudo/kdesudo/gksudo. I
  have attached it.

  ---
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2013-10-19 (38 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  Package: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Tags:  saucy
  Uname: Linux 3.11.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  ---
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  samjnaa1717 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=ba00d992-e43e-4bce-8689-9647370add15
  InstallationDate: Installed on 2013-10-19 (117 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO HuronRiver Platform
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=(hd0,msdos9)/vmlinuz root=/dev/sda9 ro quiet 
splash
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  StagingDrivers: rts5139
  Tags:  saucy staging
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 02/22/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 45CN28WW
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Emerald Lake
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnLENOVO:bvr45CN28WW:bd02/22/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
  dmi.product.name: HuronRiver Platform
  dmi.product.version: Ideapad Z570
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1536433] [NEW] Bluetooth not working for Ubuntu 14.04

2016-01-20 Thread Ashish
Public bug reported:

My laptop is HP 14r 004TU 64 Bits. I have installed Ubuntu 14.04. The
problem is that Bluetooth is not getting activated. It neither gets on
nor shows its visibility. All options are shown grey in color. I want to
connect my laptop to Bose Soundlink mini, but it is not also paired with
any other device. It always say "No Bluetooth adapters found".  Please
help me regarding this. Thanks in advance.

Below are some details of the output.
Command - lspci

00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 09)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 09)
00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 (rev 
04)
00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller (rev 
04)
00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
00:1c.1 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 2 
(rev e4)
00:1c.2 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 3 
(rev e4)
00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation Lynx Point-LP SATA Controller 1 
[AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E 
PCI Express Fast Ethernet controller (rev 07)
09:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
09:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth

Command - lsusb

Bus 001 Device 003: ID 064e:c342 Suyin Corp. 
Bus 001 Device 002: ID 8087:8000 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

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

Title:
  Bluetooth not working for Ubuntu 14.04

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My laptop is HP 14r 004TU 64 Bits. I have installed Ubuntu 14.04. The
  problem is that Bluetooth is not getting activated. It neither gets on
  nor shows its visibility. All options are shown grey in color. I want
  to connect my laptop to Bose Soundlink mini, but it is not also paired
  with any other device. It always say "No Bluetooth adapters found".
  Please help me regarding this. Thanks in advance.

  Below are some details of the output.
  Command - lspci

  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 09)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
09)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 
(rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.1 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 2 
(rev e4)
  00:1c.2 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 3 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 SATA controller: Intel Corporation Lynx Point-LP SATA Controller 1 
[AHCI mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  08:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 07)
  09:00.0 Network controller: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe
  09:00.1 Bluetooth: Ralink corp. RT3290 Bluetooth

  Command - lsusb

  Bus 001 Device 003: ID 064e:c342 Suyin Corp. 
  Bus 001 Device 002: ID 8087:8000 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 002 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

To manage notifications about this bug 

[Kernel-packages] [Bug 1518642] Re: rtl8192cu kernel driver not working

2016-01-20 Thread Christopher M. Penalver
Javier Barroso, it will help immensely if you filed a new report with the 
Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

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

Title:
  rtl8192cu kernel driver not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Connection is dropped after some time. 
  Workaround install patched dkms driver.
  Should work out of the box for "normal users"

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vincent1352 F pulseaudio
   /dev/snd/controlC0:  vincent1352 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Nov 22 00:58:18 2015
  HibernationDevice: RESUME=UUID=2dfaf257-b29b-4238-b562-b7769b0aaa49
  InstallationDate: Installed on 2015-11-21 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=23870d18-dac9-4325-be37-c76e2a75da2e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.2
  RfKill:
   
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Maximus IV GENE-Z
  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.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusIVGENE-Z:rvrRev1.xx: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/1518642/+subscriptions

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


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

2016-01-20 Thread Po-Hsu Lin
Hardware Certification have begun testing this -proposed kernel.

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => Po-Hsu 
Lin (cypressyew)

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Thursday, 14. January 2016 01:03 UTC
  kernel-stable-master-bug:1533715
  kernel-stable-Prepare-package-end:Friday, 15. January 2016 04:02 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 15. January 2016 04:02 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 15. January 2016 21:26 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Friday, 15. January 2016 23:01 UTC
  kernel-stable-Verification-testing-start:Friday, 15. January 2016 23:01 UTC
  kernel-stable-Certification-testing-start:Friday, 15. January 2016 23:02 UTC
  kernel-stable-Security-signoff-start:Friday, 15. January 2016 23:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 15. January 2016 23:02 UTC
  kernel-stable-Security-signoff-end:Saturday, 16. January 2016 01:01 UTC

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

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


[Kernel-packages] [Bug 1536490] Re: rtl8821ae has no connectivity in 5GHz networks

2016-01-20 Thread Christopher M. Penalver
Simon Naunton, thank you for reporting this and helping make Ubuntu
better.

As per http://support.lenovo.com/us/en/products/Laptops-and-
netbooks/300-Series/300-15isk?linkTrack=Homepage:Body_Search%20Products
an update to your computer's buggy and outdated BIOS is available (29).
If you update to this following
https://help.ubuntu.com/community/BIOSUpdate does it change anything?

For more on BIOS updates and linux, please see
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
.

Please note your current BIOS is already in the Bug Description, so
posting this on the old BIOS would not be helpful. As well, you don't
have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an 
apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement 
or not.
3) Please mark this report Status Confirmed. If it's not reproducible, please 
mark this as Invalid.

Thank you for your understanding.

** Tags added: bios-outdated-d5cn28ww

** Tags removed: bios-outdated-d5cn28ww
** Tags added: bios-outdated-d5cn29ww

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

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

Title:
  rtl8821ae has no connectivity in 5GHz networks

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Seems to be the same as
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1528005/

  Lenovo Ideapad 300 (80Q7008EAU - 15.6" i5 8Gb 1TB) on fresh install of
  amd64 Wily/15.10. Wifi worked ok under Windows 10 home that came with
  it.

  rtl8821ae driver loaded. Connected to AP fine. Got IP address, GW, DNS
  etc correctly, but no traffic.

  Workaround worked fine:
  git clone https://github.com/lwfinger/rtlwifi_new.git
  cd rtlwifi_new
  sudo make install
  sudo restart now

  FWIW, proper 802.11ac speeds copying large files.

  Same problem after apt-get upgrade installed linux-
  image-4.2.0-25-generic. make installed the above driver again and all
  good.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-25-generic 4.2.0-25.30
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  si 1379 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Jan 21 17:25:45 2016
  HibernationDevice: RESUME=UUID=ccc3ab01-94d8-4d55-89b4-21ece100a3d6
  InstallationDate: Installed on 2016-01-21 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 174f:14e9 Syntek 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80Q7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=cab1a31f-1f61-43e6-a6e7-2edc12bb048d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: D5CN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Paris 5A8
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 300-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrD5CN28WW:bd08/13/2015:svnLENOVO:pn80Q7:pvrLenovoideapad300-15ISK:rvnLENOVO:rnParis5A8:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad300-15ISK:
  dmi.product.name: 80Q7
  dmi.product.version: Lenovo ideapad 300-15ISK
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1532774] Re: linux: 3.2.0-98.138 -proposed tracker

2016-01-20 Thread Po-Hsu Lin
Hardware Certification have begun testing this -proposed kernel.

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

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: Canonical Hardware Certification (canonical-hw-cert) => Po-Hsu 
Lin (cypressyew)

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

Title:
  linux: 3.2.0-98.138 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.2.0-98.138 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-stable-Prepare-package-start:Monday, 11. January 2016 11:52 UTC
  kernel-stable-Prepare-package-end:Monday, 11. January 2016 20:03 UTC
  kernel-stable-Promote-to-proposed-start:Monday, 11. January 2016 20:03 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 13. January 2016 20:44 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Wednesday, 13. January 2016 22:00 UTC
  kernel-stable-Verification-testing-start:Wednesday, 13. January 2016 22:00 UTC
  kernel-stable-Certification-testing-start:Wednesday, 13. January 2016 22:00 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 13. January 2016 22:00 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 13. January 2016 22:00 UTC
  kernel-stable-Regression-testing-end:Thursday, 14. January 2016 14:02 UTC
  kernel-stable-Security-signoff-end:Thursday, 14. January 2016 18:01 UTC

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

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


[Kernel-packages] [Bug 1536490] [NEW] rtl8821ae has no connectivity in 5GHz networks

2016-01-20 Thread Simon Naunton
Public bug reported:

Seems to be the same as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1528005/

Lenovo Ideapad 300 (80Q7008EAU - 15.6" i5 8Gb 1TB) on fresh install of
amd64 Wily/15.10. Wifi worked ok under Windows 10 home that came with
it.

rtl8821ae driver loaded. Connected to AP fine. Got IP address, GW, DNS
etc correctly, but no traffic.

Workaround worked fine:
git clone https://github.com/lwfinger/rtlwifi_new.git
cd rtlwifi_new
sudo make install
sudo restart now

FWIW, proper 802.11ac speeds copying large files.

Same problem after apt-get upgrade installed linux-
image-4.2.0-25-generic. make installed the above driver again and all
good.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-25-generic 4.2.0-25.30
ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
Uname: Linux 4.2.0-25-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  si 1379 F pulseaudio
CurrentDesktop: XFCE
Date: Thu Jan 21 17:25:45 2016
HibernationDevice: RESUME=UUID=ccc3ab01-94d8-4d55-89b4-21ece100a3d6
InstallationDate: Installed on 2016-01-21 (0 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 174f:14e9 Syntek 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80Q7
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=cab1a31f-1f61-43e6-a6e7-2edc12bb048d ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-25-generic N/A
 linux-backports-modules-4.2.0-25-generic  N/A
 linux-firmware1.149.3
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: D5CN28WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Paris 5A8
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 300-15ISK
dmi.modalias: 
dmi:bvnLENOVO:bvrD5CN28WW:bd08/13/2015:svnLENOVO:pn80Q7:pvrLenovoideapad300-15ISK:rvnLENOVO:rnParis5A8:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad300-15ISK:
dmi.product.name: 80Q7
dmi.product.version: Lenovo ideapad 300-15ISK
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug wily

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

Title:
  rtl8821ae has no connectivity in 5GHz networks

Status in linux package in Ubuntu:
  New

Bug description:
  Seems to be the same as
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1528005/

  Lenovo Ideapad 300 (80Q7008EAU - 15.6" i5 8Gb 1TB) on fresh install of
  amd64 Wily/15.10. Wifi worked ok under Windows 10 home that came with
  it.

  rtl8821ae driver loaded. Connected to AP fine. Got IP address, GW, DNS
  etc correctly, but no traffic.

  Workaround worked fine:
  git clone https://github.com/lwfinger/rtlwifi_new.git
  cd rtlwifi_new
  sudo make install
  sudo restart now

  FWIW, proper 802.11ac speeds copying large files.

  Same problem after apt-get upgrade installed linux-
  image-4.2.0-25-generic. make installed the above driver again and all
  good.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-25-generic 4.2.0-25.30
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  si 1379 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Jan 21 17:25:45 2016
  HibernationDevice: RESUME=UUID=ccc3ab01-94d8-4d55-89b4-21ece100a3d6
  InstallationDate: Installed on 2016-01-21 (0 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 174f:14e9 Syntek 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80Q7
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic.efi.signed 
root=UUID=cab1a31f-1f61-43e6-a6e7-2edc12bb048d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   

[Kernel-packages] [Bug 1464833] Re: Unable to configure Firmware Assisted dump

2016-01-20 Thread Louis Bouchard
** Changed in: makedumpfile (Ubuntu Trusty)
 Assignee: Louis Bouchard (louis-bouchard) => (unassigned)

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

Title:
  Unable to configure Firmware Assisted dump

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Trusty:
  Fix Released

Bug description:
  [SRU justification]
  This represent a hardware enablement SRU : Firmware assisted dumps (fadump) 
are not possible on LTS.

  [Impact]
  The fadump mechanism cannot be used on Power systems running Trusty

  [Fix]
  Backport fadump functionality from makedumpfile 1.5.8 present in Wily and 
onward.

  [Test Case]
  See comment #9 : The proposed SRU has been tested from a PPA on a Power VM.

  [Regression]
  None expected from a functionality point of view as it is a new feature. 
Existing code paths are minimally modified.

  [Original description of the problem]

  ---Steps to Reproduce---
  1) Using latest daily ISO install 14.04.02 as a Power VM guest.
  2) Upgrade the kernel to 3.19 level (3.19.0-18-generic)
  3) In order to use Firmware Assisted Dump feature update the kernel command 
with fadump=on.
  4) Reboot.

  Post reboot using kdump-config load command fails with following
  message :

  # kdump-config load
  Memory for crashkernel is not reserved
  Please reserve memory by passing"crashkernel=X@Y" parameter to kernel
  Then try to loading kdump kernel
   * failed to load kdump kernel

  # kdump-config status
  current state   : Not ready to kdump
  #

  # cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-3.19.0-18-generic 
root=UUID=3ea23bcf-7269-432f-bacc-f82c6cdd774e ro splash quiet fadump=on 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
vt.handoff=7
  # cat /sys/kernel/fadump_enabled
  1
  # cat /sys/kernel/fadump_registered
  0
  #

  # dmesg | grep -i Firmware
  [0.00] Reserved 5120MB of memory at 97279MB for firmware-assisted dump
  [0.00] firmware_features = 0x0001c45ffc5f
  #
  # cat /boot/config-3.19.0-18-generic | grep -i FA_DUMP
  CONFIG_FA_DUMP=y
  #

  Are there any user space fixes missing which prevents me from
  configuring firmware assisted dump ?

  == Comment: #4 - Hari Krishna Bathini  - 2015-06-12 
05:28:24 ==
  This patch makes kdump-tools fadump aware so as to switch between
  kdump & fadump seemlessly based on the dump method enabled (fadump/kdump).

  Thanks
  Hari

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

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


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

2016-01-20 Thread Jorma Hytonen
"But would like a more permanent solution" - I agree with that! 
I upgrade XUbuntu 14.10 to 15.10 and then software update kernel 
4.2.0-25-generic and then I got same error.

The problem solved as Derek wrote, but what about next update?

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

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

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This machine (I believe) has PAE capabilities (Pentium-M), but 15.10 has 
become very unforgiving of machines that don't report PAE flags in 
/proc/cpuinfo.  
  I had a royal pain in the behind upgrading from 15.04 (where --forcepae just 
did the business) to 15.10 because this package wouldn't install and only 
managed to retrive a completely stuffed machine by hacking /proc/cpuinfo to 
force the PAE flag on there. This is of course temporary.

  It would be useful if whoever maintains the code that does
  /proc/cpuinfo would recognize the exception created by Intel with not
  correctly reporting PAE and fix this flag if future Ubuntu releases
  are going to barf so badly on not seeing it.

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-21.25-generic 4.2.6
  Uname: Linux 4.2.0-21-generic i686
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  der1402 F pulseaudio
  Date: Sun Dec 20 20:38:38 2015
  DpkgTerminalLog:
   Preparing to unpack .../linux-image-4.2.0-22-generic_4.2.0-22.27_i386.deb ...
   This kernel does not support a non-PAE CPU.
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.2.0-22-generic_4.2.0-22.27_i386.deb 
(--unpack):
subprocess new pre-installation script returned error exit status 1
  DuplicateSignature: package:linux-image-4.2.0-22-generic:(not 
installed):subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=8c5a77c4-3860-4ef9-8bed-60184472e824
  InstallationDate: Installed on 2015-01-29 (324 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: IBM 2371EG2
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-21-generic 
root=UUID=332336ad-e4aa-403e-bca9-8c4d9c38a491 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-29ubuntu0.2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.2.0-22-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
  UpgradeStatus: Upgraded to wily on 2015-12-17 (2 days ago)
  dmi.bios.date: 10/13/2004
  dmi.bios.vendor: IBM
  dmi.bios.version: 1UET93WW (1.43 )
  dmi.board.name: 2371EG2
  dmi.board.vendor: IBM
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: IBM
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnIBM:bvr1UET93WW(1.43):bd10/13/2004:svnIBM:pn2371EG2:pvrThinkPadX40:rvnIBM:rn2371EG2:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
  dmi.product.name: 2371EG2
  dmi.product.version: ThinkPad X40
  dmi.sys.vendor: IBM

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

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


[Kernel-packages] [Bug 1519897] Re: [Hyper-V] hv: vmbus: Fix a host signaling bug

2016-01-20 Thread Joseph Salisbury
** Also affects: linux-lts-trusty (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux-lts-trusty (Ubuntu Vivid)

** No longer affects: linux-lts-trusty (Ubuntu Wily)

** No longer affects: linux-lts-trusty (Ubuntu Xenial)

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

Title:
  [Hyper-V] hv: vmbus: Fix a host signaling bug

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-trusty package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Triaged
Status in linux-lts-trusty source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  The following fix has been submitted upstream, but has high enough
  severity that we would like early inclusion into the Ubuntu kernel.
  Please consider for wily, vivid, and trusty (and the HWE kernels for
  the same).

  Patch follows:

  Currently we have two policies for deciding when to signal the host:
  One based on the ring buffer state and the other based on what the VMBUS 
client driver wants to do. Consider the case when the client wants to 
explicitly control when to signal the host. In this case, if the client were to 
defer signaling, we will not be able to signal the host subsequently when the 
client does want to signal since the ring buffer state will prevent the 
signaling. Implement logic to have only one signaling policy in force for a 
given channel.

  Signed-off-by: K. Y. Srinivasan 
  Reviewed-by: Haiyang Zhang 
  Tested-by: Haiyang Zhang 
  Cc:  # v4.2+
  ---
   drivers/hv/channel.c   |   18 ++
   include/linux/hyperv.h |   12 
   2 files changed, 30 insertions(+), 0 deletions(-)

  diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c index 
77d2579..c6278c7 100644
  --- a/drivers/hv/channel.c
  +++ b/drivers/hv/channel.c
  @@ -653,10 +653,19 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel, 
void *buffer,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  @@ -756,10 +765,19 @@ int vmbus_sendpacket_pagebuffer_ctl(struct 
vmbus_channel *channel,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index 
437c9c8..7b1af52 100644
  --- a/include/linux/hyperv.h
  +++ b/include/linux/hyperv.h
  @@ -756,8 +756,20 @@ struct vmbus_channel {
     * link up channels based on their CPU affinity.
     */
    struct list_head percpu_list;
  + /*
  +  * Host signaling policy: The default policy will be
  +  * based on the ring buffer state. We will also support
  +  * a policy where the client driver can have explicit
  +  * signaling control.
  +  */
  + bool signal_state;
   };

  +static inline void set_channel_signal_state(struct vmbus_channel *c,
  +bool state) {
  + c->signal_state = state;
  +}
  +
   static inline void set_channel_read_state(struct vmbus_channel *c, bool 
state)  {
    c->batched_reading = state;
  --
  1.7.4.1

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

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


[Kernel-packages] [Bug 1519897] Re: [Hyper-V] hv: vmbus: Fix a host signaling bug

2016-01-20 Thread Joseph Salisbury
** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New => In Progress

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

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

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Importance: Undecided => High

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

** Changed in: linux-lts-trusty (Ubuntu Trusty)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
  [Hyper-V] hv: vmbus: Fix a host signaling bug

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-trusty package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Triaged
Status in linux-lts-trusty source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  The following fix has been submitted upstream, but has high enough
  severity that we would like early inclusion into the Ubuntu kernel.
  Please consider for wily, vivid, and trusty (and the HWE kernels for
  the same).

  Patch follows:

  Currently we have two policies for deciding when to signal the host:
  One based on the ring buffer state and the other based on what the VMBUS 
client driver wants to do. Consider the case when the client wants to 
explicitly control when to signal the host. In this case, if the client were to 
defer signaling, we will not be able to signal the host subsequently when the 
client does want to signal since the ring buffer state will prevent the 
signaling. Implement logic to have only one signaling policy in force for a 
given channel.

  Signed-off-by: K. Y. Srinivasan 
  Reviewed-by: Haiyang Zhang 
  Tested-by: Haiyang Zhang 
  Cc:  # v4.2+
  ---
   drivers/hv/channel.c   |   18 ++
   include/linux/hyperv.h |   12 
   2 files changed, 30 insertions(+), 0 deletions(-)

  diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c index 
77d2579..c6278c7 100644
  --- a/drivers/hv/channel.c
  +++ b/drivers/hv/channel.c
  @@ -653,10 +653,19 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel, 
void *buffer,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  @@ -756,10 +765,19 @@ int vmbus_sendpacket_pagebuffer_ctl(struct 
vmbus_channel *channel,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index 
437c9c8..7b1af52 100644
  --- a/include/linux/hyperv.h
  +++ b/include/linux/hyperv.h
  @@ -756,8 +756,20 @@ struct vmbus_channel {
     * link up channels based on their CPU affinity.
     */
    struct list_head percpu_list;
  + /*
  +  * Host signaling policy: The default policy will be
  +  * based on the ring buffer state. We will also support
  +  * a policy where the client driver can have explicit
  +  * signaling control.
  +  */
  + bool signal_state;
   };

  +static inline void set_channel_signal_state(struct vmbus_channel *c,
  +bool state) {
  + c->signal_state = state;
  +}
  +
   static inline void set_channel_read_state(struct vmbus_channel *c, bool 
state)  {
    c->batched_reading = state;
  --
  1.7.4.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1519897/+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 1535736] dwalin (amd64) - tests ran: 66, failed: 0

2016-01-20 Thread Brad Figg
tests ran:  66, failed: 0;
  
http://kernel.ubuntu.com/testing/4.3.0-7.18/dwalin__4.3.0-7.18__2016-01-20_14-23-00/results-index.html

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

Title:
  linux: 4.3.0-7.18 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.3.0-7.18 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-Prepare-package-start:Tuesday, 19. January 2016 14:09 UTC
  kernel-phase-changed:Tuesday, 19. January 2016 14:09 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 19. January 2016 15:00 UTC
  proposed-announcement-sent:True

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

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


[Kernel-packages] [Bug 1526027] Re: [BBB] Fixing recursive fault but reboot is needed!

2016-01-20 Thread Paolo Pisati
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Paolo Pisati (p-pisati)

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

Title:
  [BBB] Fixing recursive fault but reboot is needed!

Status in Snappy:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On beaglebone black, rolling/edge #255 (and probably some earlier ones as 
well) I'm seeing an oops on boot. 
  I've pasted the full text from serial output at:
  http://paste.ubuntu.com/14008126/

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

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


Re: [Kernel-packages] [Bug 1533009] Re: arm64: "unsupported RELA relocation"

2016-01-20 Thread dann frazier
On Sat, Jan 16, 2016 at 2:44 AM, Matthias Klose  wrote:
> --- fsf/multipath.mod.s 2016-01-15 22:23:24.0 +0100
> +++ linaro/multipath.mod.s  2016-01-15 22:20:11.0 +0100
> @@ -1,7 +1,6 @@
> -   .cpu generic+fp+simd
> .file   "multipath.mod.c"
> .global __this_module
> -   .section.modinfo,"a",%progbits
> +   .section.modinfo,"a",@progbits
> .align  3
> .type   __UNIQUE_ID_srcversion1, %object
> .size   __UNIQUE_ID_srcversion1, 35

[...]
I got rid of the @progbits/%progbits differences in the assembly, as
well as the .cpu and .arch differences,
but still observe the same failure.

  -dann

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

Title:
  arm64: "unsupported RELA relocation"

Status in Linaro GCC:
  Unknown
Status in Linux:
  Unknown
Status in gcc-5 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  linux-image-4.3.0-5-generic 4.3.0-5.16 arm64 fails to load modules
  (and therefore boot). It emits messages like the following for each
  attempted module load:

  [2.156817] module libahci: unsupported RELA relocation: 275

  This is reminiscent of LP: #1502946 - except that fix appears to still
  be in-tact. What has changed, however, is the build environment. If I
  rebuild the same kernel source in a wily chroot, it boots fine.

  Marking "Confirmed" because Paulo Pisatti reported this to me, and I
  reproduced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc-linaro/+bug/1533009/+subscriptions

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


[Kernel-packages] [Bug 1519897] Re: [Hyper-V] hv: vmbus: Fix a host signaling bug

2016-01-20 Thread Joseph Salisbury
The patch is in the mainline tree as the following commit:

8599846 - Drivers: hv: vmbus: Fix a Host signaling bug

However, it has not been tagged in an official release upstream as of
yet.  It was cc'd to stable, so it will make it's way into the stable
kernels through the usual stable update process.

A SAUCE patch is in Vivid for this patch.  I have a SAUCE patch for Wily
and Xenial until the fix comes down from upstream.  I can SRU the SAUCE
patch once it is tested per comment #5.

The patch was not applying cleanly to Trusty and the lts-trusty kernels.
I'll work on backporting that again and post a Trusty test kernel
shortly.

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

Title:
  [Hyper-V] hv: vmbus: Fix a host signaling bug

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-trusty package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Triaged
Status in linux-lts-trusty source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  The following fix has been submitted upstream, but has high enough
  severity that we would like early inclusion into the Ubuntu kernel.
  Please consider for wily, vivid, and trusty (and the HWE kernels for
  the same).

  Patch follows:

  Currently we have two policies for deciding when to signal the host:
  One based on the ring buffer state and the other based on what the VMBUS 
client driver wants to do. Consider the case when the client wants to 
explicitly control when to signal the host. In this case, if the client were to 
defer signaling, we will not be able to signal the host subsequently when the 
client does want to signal since the ring buffer state will prevent the 
signaling. Implement logic to have only one signaling policy in force for a 
given channel.

  Signed-off-by: K. Y. Srinivasan 
  Reviewed-by: Haiyang Zhang 
  Tested-by: Haiyang Zhang 
  Cc:  # v4.2+
  ---
   drivers/hv/channel.c   |   18 ++
   include/linux/hyperv.h |   12 
   2 files changed, 30 insertions(+), 0 deletions(-)

  diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c index 
77d2579..c6278c7 100644
  --- a/drivers/hv/channel.c
  +++ b/drivers/hv/channel.c
  @@ -653,10 +653,19 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel, 
void *buffer,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  @@ -756,10 +765,19 @@ int vmbus_sendpacket_pagebuffer_ctl(struct 
vmbus_channel *channel,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index 
437c9c8..7b1af52 100644
  --- a/include/linux/hyperv.h
  +++ b/include/linux/hyperv.h
  @@ -756,8 +756,20 @@ struct vmbus_channel {
     * link up channels based on their CPU affinity.
     */
    struct list_head percpu_list;
  + /*
  +  * Host signaling policy: The default policy will be
  +  * based on the ring buffer state. We will also support
  +  * a policy where the client driver can have explicit
  +  * signaling control.
  +  */
  + bool signal_state;
   };

  +static inline void set_channel_signal_state(struct vmbus_channel *c,
  +bool state) {
  + c->signal_state = state;
  +}
  +
   static inline void set_channel_read_state(struct vmbus_channel *c, bool 
state)  {
    c->batched_reading = state;
  --
  1.7.4.1

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

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

[Kernel-packages] [Bug 1536292] [NEW] package linux-image-extra-3.13.0-76-generic 3.13.0-76.120 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-01-20 Thread Kevin Cook
Public bug reported:

Problem occurred on startup of system

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-76-generic 3.13.0-76.120
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic i686
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  kcook 25412 F pulseaudio
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Wed Jan 20 10:42:59 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
HibernationDevice: RESUME=UUID=0be3c66a-a4cb-4bb6-90ee-511da38fb2c4
InstallationDate: Installed on 2015-11-23 (57 days ago)
InstallationMedia: LXLE 14.04 - Release i386
MachineType: HP-Pavilion GN702AA-ABA a6244n
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-74-generic 
root=/dev/mapper/qwerty--vg-root ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.7
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
StagingDrivers: zram
Title: package linux-image-extra-3.13.0-76-generic 3.13.0-76.120 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
 
dmi.bios.date: 10/30/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.23
dmi.board.name: Leonite2
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 6.00
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: 
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.23:bd10/30/2007:svnHP-Pavilion:pnGN702AA-ABAa6244n:pvr:rvnASUSTekComputerINC.:rnLeonite2:rvr6.00:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: GN702AA-ABA a6244n
dmi.sys.vendor: HP-Pavilion

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


** Tags: apport-package i386 staging trusty

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

Title:
  package linux-image-extra-3.13.0-76-generic 3.13.0-76.120 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Problem occurred on startup of system

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-76-generic 3.13.0-76.120
  ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-74-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kcook 25412 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Wed Jan 20 10:42:59 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  HibernationDevice: RESUME=UUID=0be3c66a-a4cb-4bb6-90ee-511da38fb2c4
  InstallationDate: Installed on 2015-11-23 (57 days ago)
  InstallationMedia: LXLE 14.04 - Release i386
  MachineType: HP-Pavilion GN702AA-ABA a6244n
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-74-generic 
root=/dev/mapper/qwerty--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: zram
  Title: package linux-image-extra-3.13.0-76-generic 3.13.0-76.120 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 10/30/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.23
  dmi.board.name: Leonite2
  dmi.board.vendor: ASUSTek Computer INC.
  dmi.board.version: 6.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: 
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.23:bd10/30/2007:svnHP-Pavilion:pnGN702AA-ABAa6244n:pvr:rvnASUSTekComputerINC.:rnLeonite2:rvr6.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: GN702AA-ABA a6244n
  dmi.sys.vendor: HP-Pavilion

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

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


[Kernel-packages] [Bug 1533221] Re: Booting with intel graphics enabled results in a lockup

2016-01-20 Thread Christopher M. Penalver
** Changed in: linux (Ubuntu)
   Status: Incomplete => Triaged

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

Title:
  Booting with intel graphics enabled results in a lockup

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Booting with intel graphics enabled results in a lockup loading lightdm or 
logging in results in the greeter screen appearing again. The laptop has a 
Nvidia GTX730 graphics card which can be switched off via bumblebee or prime.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian2045 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=df036c01-8f22-4d8f-ad55-6add4f99f5f4
  MachineType: Notebook P65_P67RGRERA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-43-generic 
root=UUID=2077d068-d7ee-4407-89e1-7d2b884173de ro quiet splash
  ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-43-generic N/A
   linux-backports-modules-3.19.0-43-generic  N/A
   linux-firmware 1.155
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.10
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.10:bd11/20/2015:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65_P67RGRERA
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

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


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

2016-01-20 Thread Jonathan Kamens
apport information

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

Title:
  Network filesystems don't mount on boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by
  IP address, mount says the network is unreachable in the boot logs.

  If fixed this by adding the following in /etc/systemd/system/remote-
  fs-pre.target.d/override.conf:

  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service

  See also #1313513. This is a problem in older, pre-systemd versions of Ubuntu 
as well.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jik2922 F pulseaudio
   /dev/snd/controlC1:  jik2922 F pulseaudio
   /dev/snd/controlC0:  jik2922 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=77f36398-76d6-438c-95c5-2a0ac83629ea
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: systemd 225-1ubuntu9
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

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

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


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

2016-01-20 Thread Jonathan Kamens
apport information

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

Title:
  Network filesystems don't mount on boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by
  IP address, mount says the network is unreachable in the boot logs.

  If fixed this by adding the following in /etc/systemd/system/remote-
  fs-pre.target.d/override.conf:

  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service

  See also #1313513. This is a problem in older, pre-systemd versions of Ubuntu 
as well.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jik2922 F pulseaudio
   /dev/snd/controlC1:  jik2922 F pulseaudio
   /dev/snd/controlC0:  jik2922 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=77f36398-76d6-438c-95c5-2a0ac83629ea
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: systemd 225-1ubuntu9
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1526027] Re: [BBB] Fixing recursive fault but reboot is needed!

2016-01-20 Thread Leo Arias
Thanks for looking at it Paolo.

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

Title:
  [BBB] Fixing recursive fault but reboot is needed!

Status in Snappy:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On beaglebone black, rolling/edge #255 (and probably some earlier ones as 
well) I'm seeing an oops on boot. 
  I've pasted the full text from serial output at:
  http://paste.ubuntu.com/14008126/

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

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


[Kernel-packages] [Bug 1536249] [NEW] XPS 13 9350: reboot fails with "Transaction is destructive" after resume from suspend

2016-01-20 Thread Robin Winslow
Public bug reported:

With my brand new Dell XPS 13 9350 and Ubuntu 15.10. The graphical
"reboot" and "shut down" buttons don't do anything, and from the CLI I
get:

$ reboot
Failed to execute operation: Transaction is destructive.

I imagine it's associated with closing the lid to suspend because when I
first start the system it reboots fine. It resumes fine when I open the
lid in the sense that I can enter my password and continue to use
Ubuntu, but it would make sense if there's something hanging about in
the background. I don't know how to check this.

(I initially found this "wontfix" bug which describes the same problem:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253)

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

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

Title:
  XPS 13 9350: reboot fails with "Transaction is destructive" after
  resume from suspend

Status in linux package in Ubuntu:
  New

Bug description:
  With my brand new Dell XPS 13 9350 and Ubuntu 15.10. The graphical
  "reboot" and "shut down" buttons don't do anything, and from the CLI I
  get:

  $ reboot
  Failed to execute operation: Transaction is destructive.

  I imagine it's associated with closing the lid to suspend because when
  I first start the system it reboots fine. It resumes fine when I open
  the lid in the sense that I can enter my password and continue to use
  Ubuntu, but it would make sense if there's something hanging about in
  the background. I don't know how to check this.

  (I initially found this "wontfix" bug which describes the same
  problem:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253)

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

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


[Kernel-packages] [Bug 320638] Re: hot-add/remove in mixed (IDE/SATA/USB/SD-card/...) RAIDs with device mapper on top => data corruption (bio too big device md0 (248 > 240))

2016-01-20 Thread Bug Watch Updater
** Changed in: linux
   Status: Confirmed => Fix Released

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

Title:
  hot-add/remove in mixed (IDE/SATA/USB/SD-card/...)  RAIDs with device
  mapper on top => data corruption (bio too big device md0 (248 > 240))

Status in Linux:
  Fix Released
Status in mdadm:
  Confirmed
Status in debian-installer package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Won't Fix
Status in mdadm package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Invalid

Bug description:
  Problem: md changes max_sector setting of an already running and busy
  md device, when a (hotplugable) device is added or removed. However,
  the device mapper and filesystem layer on top of the raid can not
  (always?) cope with that.

  Observations:
  * "bio too big device mdX (248 > 240)" messages in the syslog
  * read/write errors (some dropped silently, no noticable errors reported 
during operation, until things like dhcpclient looses its IP etc.)

  Expected:
  Adding and removing members to running raids (hotplugging) should not change 
the raid device characteristics. If the new member supports only smaller 
max_sector values, buffer and split the data steam, until the raid device can 
be set up from a clean state with a more appropriate max_sector value. To avoid 
buffering and splitting in the future, md could save the smallest max_sector 
value of the known members in the superblock, and use that when setting up the 
raid even if that member is not present.

  Note: This is reproducible in much more common scenarios as the
  original reporter had (e.g. --add a USB (3.0 these days) drive to an
  already running SATA raid1 and grow the number of devices).

  Fix:
  Upsteam has no formal bug tracking, but a mailing list. The response was that 
finally this needs to be "fixed [outside of mdadm] by cleaning up the bio path 
so that big bios are split by the device that needs the split, not be the fs 
sending the bio."

  However, in the meantime mdadm needs to saveguard against the date
  corruption:

  > > [The mdadm] fix is to reject the added device [if] its limits are
  > > too low.
  > 
  > Good Idea to avoid the data corruption. MD could save the
  > max_sectors default limit for arrays. If the array is modified and the new 
  > limit gets smaller, postpone the sync until the next assembe/restart.
  > 
  > And of course print a message if postponing, that explains when --force 
would be save.
  > What ever that would be: no block device abstraction layer (device mapper, 
lvm, luks,...) 
  > between an unmounted? ext, fat?, ...? filesystem and md?

  As upsteam does not do public bug tracking, the status and
  rememberence of this need remains unsure though.

  
  ---

  This is on a MSI Wind U100 and I've got the following stack running:
  HDD & SD card (USB card reader) -> RAID1 -> LUKS -> LVM -> Reiser

  Whenever I remove the HDD from the Raid1
  > mdadm /dev/md0 --fail /dev/sda2
  > mdadm /dev/md0 --remove /dev/sda2)
  for powersaving reasons, I cannot run any apt related tools.

  > sudo apt-get update
  [...]
  Hit http://de.archive.ubuntu.com intrepid-updates/multiverse Sources
  Reading package lists... Error!
  E: Read error - read (5 Input/output error)
  E: The package lists or status file could not be parsed or opened.

  Taking a look at the kernel log shows (and many more above):
  > dmesg|tail
  [ 9479.330550] bio too big device md0 (248 > 240)
  [ 9479.331375] bio too big device md0 (248 > 240)
  [ 9479.332182] bio too big device md0 (248 > 240)
  [ 9611.980294] bio too big device md0 (248 > 240)
  [ 9742.929761] bio too big device md0 (248 > 240)
  [ 9852.932001] bio too big device md0 (248 > 240)
  [ 9852.935395] bio too big device md0 (248 > 240)
  [ 9852.938064] bio too big device md0 (248 > 240)
  [ 9853.081046] bio too big device md0 (248 > 240)
  [ 9853.081688] bio too big device md0 (248 > 240)

  $ sudo mdadm --detail /dev/md0
  /dev/md0:
  Version : 00.90
    Creation Time : Tue Jan 13 11:25:57 2009
   Raid Level : raid1
   Array Size : 3871552 (3.69 GiB 3.96 GB)
    Used Dev Size : 3871552 (3.69 GiB 3.96 GB)
     Raid Devices : 2
    Total Devices : 1
  Preferred Minor : 0
  Persistence : Superblock is persistent

    Intent Bitmap : Internal

  Update Time : Fri Jan 23 21:47:35 2009
    State : active, degraded
   Active Devices : 1
  Working Devices : 1
   Failed Devices : 0
    Spare Devices : 0

     UUID : 89863068:bc52a0c0:44a5346e:9d69deca (local to host m-twain)
   Events : 0.8767

  Number   Major   Minor   RaidDevice State
     0   000  removed
     1   8   171  active sync writemostly   /dev/sdb1

  $ sudo ubuntu-bug -p linux-meta
  dpkg-query: failed in buffer_read(fd): copy info file 

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

2016-01-20 Thread Jonathan Kamens
apport information

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

Title:
  Network filesystems don't mount on boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by
  IP address, mount says the network is unreachable in the boot logs.

  If fixed this by adding the following in /etc/systemd/system/remote-
  fs-pre.target.d/override.conf:

  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service

  See also #1313513. This is a problem in older, pre-systemd versions of Ubuntu 
as well.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jik2922 F pulseaudio
   /dev/snd/controlC1:  jik2922 F pulseaudio
   /dev/snd/controlC0:  jik2922 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=77f36398-76d6-438c-95c5-2a0ac83629ea
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: systemd 225-1ubuntu9
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

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

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


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

2016-01-20 Thread Jonathan Kamens
apport information

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

Title:
  Network filesystems don't mount on boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by
  IP address, mount says the network is unreachable in the boot logs.

  If fixed this by adding the following in /etc/systemd/system/remote-
  fs-pre.target.d/override.conf:

  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service

  See also #1313513. This is a problem in older, pre-systemd versions of Ubuntu 
as well.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jik2922 F pulseaudio
   /dev/snd/controlC1:  jik2922 F pulseaudio
   /dev/snd/controlC0:  jik2922 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=77f36398-76d6-438c-95c5-2a0ac83629ea
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: systemd 225-1ubuntu9
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

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

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


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

2016-01-20 Thread Jonathan Kamens
apport information

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

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

** Description changed:

  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.
  
  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by IP
  address, mount says the network is unreachable in the boot logs.
  
  If fixed this by adding the following in /etc/systemd/system/remote-fs-
  pre.target.d/override.conf:
  
  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service
  
  See also #1313513. This is a problem in older, pre-systemd versions of Ubuntu 
as well.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jik2922 F pulseaudio
   /dev/snd/controlC1:  jik2922 F pulseaudio
   /dev/snd/controlC0:  jik2922 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=77f36398-76d6-438c-95c5-2a0ac83629ea
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
+ --- 
+ ApportVersion: 2.19.1-0ubuntu5
+ Architecture: amd64
+ DistroRelease: Ubuntu 15.10
+ InstallationDate: Installed on 2016-01-16 (4 days ago)
+ InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
+ MachineType: Acer Predator G6-710
+ NonfreeKernelModules: nvidia
+ Package: systemd 225-1ubuntu9
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
+ Tags:  wily
+ UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
+ Uname: Linux 4.2.0-25-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 09/21/2015
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: R01-A1
+ dmi.board.name: Predator G6-710
+ dmi.board.vendor: Acer
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Acer
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
+ dmi.product.name: Predator G6-710
+ dmi.sys.vendor: Acer

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

Title:
  Network filesystems don't mount on boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by
  IP address, mount says the network is unreachable in the boot logs.

  If fixed this by adding the following in /etc/systemd/system/remote-
  fs-pre.target.d/override.conf:

  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service

  See also #1313513. This is a problem in older, pre-systemd versions of Ubuntu 
as well.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jik2922 F pulseaudio
   /dev/snd/controlC1:  jik2922 F pulseaudio
   /dev/snd/controlC0:  jik2922 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=77f36398-76d6-438c-95c5-2a0ac83629ea
 

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

2016-01-20 Thread Jonathan Kamens
apport information

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

Title:
  Network filesystems don't mount on boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by
  IP address, mount says the network is unreachable in the boot logs.

  If fixed this by adding the following in /etc/systemd/system/remote-
  fs-pre.target.d/override.conf:

  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service

  See also #1313513. This is a problem in older, pre-systemd versions of Ubuntu 
as well.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jik2922 F pulseaudio
   /dev/snd/controlC1:  jik2922 F pulseaudio
   /dev/snd/controlC0:  jik2922 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=77f36398-76d6-438c-95c5-2a0ac83629ea
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: systemd 225-1ubuntu9
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

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

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


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

2016-01-20 Thread Jonathan Kamens
apport information

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

Title:
  Network filesystems don't mount on boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by
  IP address, mount says the network is unreachable in the boot logs.

  If fixed this by adding the following in /etc/systemd/system/remote-
  fs-pre.target.d/override.conf:

  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service

  See also #1313513. This is a problem in older, pre-systemd versions of Ubuntu 
as well.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jik2922 F pulseaudio
   /dev/snd/controlC1:  jik2922 F pulseaudio
   /dev/snd/controlC0:  jik2922 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=77f36398-76d6-438c-95c5-2a0ac83629ea
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: systemd 225-1ubuntu9
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

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

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


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

2016-01-20 Thread Jonathan Kamens
apport information

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

Title:
  Network filesystems don't mount on boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by
  IP address, mount says the network is unreachable in the boot logs.

  If fixed this by adding the following in /etc/systemd/system/remote-
  fs-pre.target.d/override.conf:

  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service

  See also #1313513. This is a problem in older, pre-systemd versions of Ubuntu 
as well.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jik2922 F pulseaudio
   /dev/snd/controlC1:  jik2922 F pulseaudio
   /dev/snd/controlC0:  jik2922 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=77f36398-76d6-438c-95c5-2a0ac83629ea
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: systemd 225-1ubuntu9
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

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

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


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

2016-01-20 Thread Jonathan Kamens
apport information

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

Title:
  Network filesystems don't mount on boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by
  IP address, mount says the network is unreachable in the boot logs.

  If fixed this by adding the following in /etc/systemd/system/remote-
  fs-pre.target.d/override.conf:

  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service

  See also #1313513. This is a problem in older, pre-systemd versions of Ubuntu 
as well.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jik2922 F pulseaudio
   /dev/snd/controlC1:  jik2922 F pulseaudio
   /dev/snd/controlC0:  jik2922 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=77f36398-76d6-438c-95c5-2a0ac83629ea
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: systemd 225-1ubuntu9
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

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

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


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

2016-01-20 Thread Jonathan Kamens
apport information

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

Title:
  Network filesystems don't mount on boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by
  IP address, mount says the network is unreachable in the boot logs.

  If fixed this by adding the following in /etc/systemd/system/remote-
  fs-pre.target.d/override.conf:

  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service

  See also #1313513. This is a problem in older, pre-systemd versions of Ubuntu 
as well.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jik2922 F pulseaudio
   /dev/snd/controlC1:  jik2922 F pulseaudio
   /dev/snd/controlC0:  jik2922 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=77f36398-76d6-438c-95c5-2a0ac83629ea
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: systemd 225-1ubuntu9
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

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

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


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

2016-01-20 Thread Jonathan Kamens
apport information

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

Title:
  Network filesystems don't mount on boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by
  IP address, mount says the network is unreachable in the boot logs.

  If fixed this by adding the following in /etc/systemd/system/remote-
  fs-pre.target.d/override.conf:

  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service

  See also #1313513. This is a problem in older, pre-systemd versions of Ubuntu 
as well.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jik2922 F pulseaudio
   /dev/snd/controlC1:  jik2922 F pulseaudio
   /dev/snd/controlC0:  jik2922 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=77f36398-76d6-438c-95c5-2a0ac83629ea
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: systemd 225-1ubuntu9
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

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

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


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

2016-01-20 Thread Jonathan Kamens
apport information

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

Title:
  Network filesystems don't mount on boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by
  IP address, mount says the network is unreachable in the boot logs.

  If fixed this by adding the following in /etc/systemd/system/remote-
  fs-pre.target.d/override.conf:

  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service

  See also #1313513. This is a problem in older, pre-systemd versions of Ubuntu 
as well.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jik2922 F pulseaudio
   /dev/snd/controlC1:  jik2922 F pulseaudio
   /dev/snd/controlC0:  jik2922 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=77f36398-76d6-438c-95c5-2a0ac83629ea
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: systemd 225-1ubuntu9
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1536294] Re: Network filesystems don't mount on boot

2016-01-20 Thread Jonathan Kamens
apport information

** Tags added: apport-collected wily

** Description changed:

  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.
  
  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by IP
  address, mount says the network is unreachable in the boot logs.
  
  If fixed this by adding the following in /etc/systemd/system/remote-fs-
  pre.target.d/override.conf:
  
  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service
  
- See also #1313513. This is a problem in older, pre-systemd versions of
- Ubuntu as well.
+ See also #1313513. This is a problem in older, pre-systemd versions of Ubuntu 
as well.
+ --- 
+ ApportVersion: 2.19.1-0ubuntu5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  jik2922 F pulseaudio
+  /dev/snd/controlC1:  jik2922 F pulseaudio
+  /dev/snd/controlC0:  jik2922 F pulseaudio
+ DistroRelease: Ubuntu 15.10
+ HibernationDevice: RESUME=UUID=77f36398-76d6-438c-95c5-2a0ac83629ea
+ InstallationDate: Installed on 2016-01-16 (4 days ago)
+ InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
+ MachineType: Acer Predator G6-710
+ NonfreeKernelModules: nvidia
+ Package: linux (not installed)
+ ProcFB: 0 EFI VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
+ RelatedPackageVersions:
+  linux-restricted-modules-4.2.0-25-generic N/A
+  linux-backports-modules-4.2.0-25-generic  N/A
+  linux-firmware1.149.3
+ Tags:  wily
+ UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
+ Uname: Linux 4.2.0-25-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 09/21/2015
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: R01-A1
+ dmi.board.name: Predator G6-710
+ dmi.board.vendor: Acer
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Acer
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
+ dmi.product.name: Predator G6-710
+ dmi.sys.vendor: Acer

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

Title:
  Network filesystems don't mount on boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by
  IP address, mount says the network is unreachable in the boot logs.

  If fixed this by adding the following in /etc/systemd/system/remote-
  fs-pre.target.d/override.conf:

  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service

  See also #1313513. This is a problem in older, pre-systemd versions of Ubuntu 
as well.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jik2922 F pulseaudio
   /dev/snd/controlC1:  jik2922 F pulseaudio
   /dev/snd/controlC0:  jik2922 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=77f36398-76d6-438c-95c5-2a0ac83629ea
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 

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

2016-01-20 Thread Jonathan Kamens
apport information

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

Title:
  Network filesystems don't mount on boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by
  IP address, mount says the network is unreachable in the boot logs.

  If fixed this by adding the following in /etc/systemd/system/remote-
  fs-pre.target.d/override.conf:

  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service

  See also #1313513. This is a problem in older, pre-systemd versions of Ubuntu 
as well.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jik2922 F pulseaudio
   /dev/snd/controlC1:  jik2922 F pulseaudio
   /dev/snd/controlC0:  jik2922 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=77f36398-76d6-438c-95c5-2a0ac83629ea
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: systemd 225-1ubuntu9
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1536285] [NEW] linux-lts-trusty: 3.13.0-77.121~precise1 -proposed tracker

2016-01-20 Thread Brad Figg
Public bug reported:

This bug is for tracking the 3.13.0-77.121~precise1 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-stable-Prepare-package-start:Wednesday, 20. January 2016 17:20 UTC
kernel-stable-phase:Prepare
kernel-stable-phase-changed:Wednesday, 20. January 2016 17:20 UTC
kernel-stable-master-bug:1535880

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Medium
 Status: Invalid

** Affects: linux-lts-trusty (Ubuntu Precise)
 Importance: Medium
 Status: New


** Tags: block-proposed-precise kernel-release-tracking-bug precise

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed-precise

** Also affects: linux-lts-trusty (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Tags added: precise

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   

[Kernel-packages] [Bug 1532956] Re: linux-lts-trusty: 3.13.0-75.119~precise1 -proposed tracker

2016-01-20 Thread Luis Henriques
*** This bug is a duplicate of bug 1536285 ***
https://bugs.launchpad.net/bugs/1536285

** This bug has been marked a duplicate of bug 1536285
   linux-lts-trusty: 3.13.0-77.121~precise1 -proposed tracker

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

Title:
  linux-lts-trusty: 3.13.0-75.119~precise1 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-75.119~precise1 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-stable-Prepare-package-start:Monday, 11. January 2016 21:02 UTC
  kernel-stable-master-bug:1532781
  kernel-stable-Prepare-package-end:Tuesday, 12. January 2016 19:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 12. January 2016 19:02 UTC
  kernel-stable-Promote-to-proposed-end:Wednesday, 13. January 2016 20:47 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Wednesday, 13. January 2016 22:05 UTC
  kernel-stable-Verification-testing-start:Wednesday, 13. January 2016 22:05 UTC
  kernel-stable-Certification-testing-start:Wednesday, 13. January 2016 22:05 
UTC
  kernel-stable-Security-signoff-start:Wednesday, 13. January 2016 22:05 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Wednesday, 13. January 2016 22:05 UTC
  kernel-stable-Security-signoff-end:Thursday, 14. January 2016 21:01 UTC

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

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


[Kernel-packages] [Bug 1454892] Re: [Hyper-V] hv_netvsc: Use the xmit_more skb flag to optimize signaling the host

2016-01-20 Thread Chris Valean
Hi Joe,
We've attempted to validate the linux-lts-utopic test kernel provided, however 
on a Trusty system the VM is not stable in terms of getting the network 
connectivity, as during performance testing, the system tend to loose the test 
interface connection.

Can you please confirm if commit  8599846d73 is checked in?
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8599846d73997cdbccf63f23394d871cfad1e5e6

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

Title:
  [Hyper-V] hv_netvsc: Use the xmit_more skb flag to optimize signaling
  the host

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-utopic package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux-lts-utopic source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  hv_netvsc: Use the xmit_more skb flag to optimize signaling the host
  Based on the information given to this driver (via the xmit_more skb flag),
  we can defer signaling the host if more packets are on the way. This will help
  make the host more efficient since it can potentially process a larger batch 
of
  packets. Implement this optimization.

  Upstream commit: https://git.kernel.org/cgit/linux/kernel/git/davem
  /net-next.git/commit/?id=82fa3c776e5abba7ed6e4b4f4983d14731c37d6a

  This commit may imply other commits previously requested, for example
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452074

  Requested for all typical Hyper-V targets: 15.10, 15.04, 14.10, 14.04,
  14.04 HWE, 12.02, and 12.02 HWE

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

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


[Kernel-packages] [Bug 1535880] Re: linux: 3.13.0-77.121 -proposed tracker

2016-01-20 Thread Brad Figg
All builds are complete, packages in this bug can be copied to
-proposed.

Derivative packages from packages here can be worked on, the following tracking 
bugs were opened for them:
linux-keystone - bug 1536284

Backport packages from packages here can be worked on, the following tracking 
bugs were opened for them:
linux-lts-trusty (precise1) - bug 1536285

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

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

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

** Description changed:

  This bug is for tracking the 3.13.0-77.121 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-stable-Prepare-package-start:Tuesday, 19. January 2016 19:59 UTC
- kernel-stable-phase:Prepare
- kernel-stable-phase-changed:Tuesday, 19. January 2016 19:59 UTC
+ kernel-stable-phase:CopyToProposed
+ kernel-stable-Prepare-package-end:Wednesday, 20. January 2016 17:22 UTC
+ kernel-stable-Promote-to-proposed-start:Wednesday, 20. January 2016 17:22 UTC
+ kernel-stable-phase-changed:Wednesday, 20. January 2016 17:22 UTC

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

Title:
  linux: 3.13.0-77.121 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-77.121 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-stable-Prepare-package-start:Tuesday, 19. January 2016 19:59 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Wednesday, 20. January 2016 17:22 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 20. January 2016 17:22 UTC
  kernel-stable-phase-changed:Wednesday, 20. January 2016 17:22 UTC

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

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


[Kernel-packages] [Bug 1536294] [NEW] Network filesystems don't mount on boot

2016-01-20 Thread Jonathan Kamens
Public bug reported:

Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

They don't mount at boot. If I list them by host name in /etc/fstab,
mount says name resolution failed in the boot logs. If I list them by IP
address, mount says the network is unreachable in the boot logs.

If fixed this by adding the following in /etc/systemd/system/remote-fs-
pre.target.d/override.conf:

[Unit]
Requires=NetworkManager-wait-online.service
After=NetworkManager-wait-online.service

See also #1313513. This is a problem in older, pre-systemd versions of
Ubuntu as well.

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

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

Title:
  Network filesystems don't mount on boot

Status in linux package in Ubuntu:
  New

Bug description:
  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by
  IP address, mount says the network is unreachable in the boot logs.

  If fixed this by adding the following in /etc/systemd/system/remote-
  fs-pre.target.d/override.conf:

  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service

  See also #1313513. This is a problem in older, pre-systemd versions of
  Ubuntu as well.

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

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


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

2016-01-20 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/1536292

Title:
  package linux-image-extra-3.13.0-76-generic 3.13.0-76.120 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Problem occurred on startup of system

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-76-generic 3.13.0-76.120
  ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-74-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kcook 25412 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Wed Jan 20 10:42:59 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  HibernationDevice: RESUME=UUID=0be3c66a-a4cb-4bb6-90ee-511da38fb2c4
  InstallationDate: Installed on 2015-11-23 (57 days ago)
  InstallationMedia: LXLE 14.04 - Release i386
  MachineType: HP-Pavilion GN702AA-ABA a6244n
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-74-generic 
root=/dev/mapper/qwerty--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  StagingDrivers: zram
  Title: package linux-image-extra-3.13.0-76-generic 3.13.0-76.120 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 10/30/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.23
  dmi.board.name: Leonite2
  dmi.board.vendor: ASUSTek Computer INC.
  dmi.board.version: 6.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: 
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.23:bd10/30/2007:svnHP-Pavilion:pnGN702AA-ABAa6244n:pvr:rvnASUSTekComputerINC.:rnLeonite2:rvr6.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: GN702AA-ABA a6244n
  dmi.sys.vendor: HP-Pavilion

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

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


[Kernel-packages] [Bug 1536149] Re: linux-lts-utopic: 3.16.0-60.80~14.04.1 -proposed tracker

2016-01-20 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

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

Title:
  linux-lts-utopic: 3.16.0-60.80~14.04.1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Wednesday, 20. January 2016 11:41 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Wednesday, 20. January 2016 11:41 UTC

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

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


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

2016-01-20 Thread Brad Figg
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1536294

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

Title:
  Network filesystems don't mount on boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by
  IP address, mount says the network is unreachable in the boot logs.

  If fixed this by adding the following in /etc/systemd/system/remote-
  fs-pre.target.d/override.conf:

  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service

  See also #1313513. This is a problem in older, pre-systemd versions of
  Ubuntu as well.

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

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


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

2016-01-20 Thread Jonathan Kamens
apport information

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

Title:
  Network filesystems don't mount on boot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 15.10, I have several CIFS filesystems listed in /etc/fstab.

  They don't mount at boot. If I list them by host name in /etc/fstab,
  mount says name resolution failed in the boot logs. If I list them by
  IP address, mount says the network is unreachable in the boot logs.

  If fixed this by adding the following in /etc/systemd/system/remote-
  fs-pre.target.d/override.conf:

  [Unit]
  Requires=NetworkManager-wait-online.service
  After=NetworkManager-wait-online.service

  See also #1313513. This is a problem in older, pre-systemd versions of Ubuntu 
as well.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jik2922 F pulseaudio
   /dev/snd/controlC1:  jik2922 F pulseaudio
   /dev/snd/controlC0:  jik2922 F pulseaudio
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=77f36398-76d6-438c-95c5-2a0ac83629ea
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2016-01-16 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Predator G6-710
  NonfreeKernelModules: nvidia
  Package: systemd 225-1ubuntu9
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.2.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R01-A1
  dmi.board.name: Predator G6-710
  dmi.board.vendor: Acer
  dmi.chassis.type: 3
  dmi.chassis.vendor: Acer
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR01-A1:bd09/21/2015:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr:
  dmi.product.name: Predator G6-710
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1535565] Re: i have wifi connnection problem

2016-01-20 Thread Steve Beattie
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  i have wifi connnection problem

Status in linux package in Ubuntu:
  New

Bug description:
  i have a problem in connection to internet,

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: 
boot/vmlinuz-3.13.0-24-generic]
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  acer   1650 F pulseaudio
acer   3994 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 19 13:52:31 2016
  HibernationDevice: RESUME=UUID=3727c696-a786-465f-a2b0-4a2052cdad14
  InstallationDate: Installed on 2016-01-05 (13 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Acer Aspire V3-471
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=UUID=b0772e3e-4f65-444d-b1c5-46a188be95a0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA40_HC
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.24:bd10/11/2012:svnAcer:pnAspireV3-471:pvrV1.24:rvnAcer:rnVA40_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V3-471
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1463654] Re: Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation

2016-01-20 Thread Luciano Chavez
** 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/1463654

Title:
  Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation
   
  Contact Information = Sachin Sant / ss...@in.ibm.com 
   
  ---uname output---
  3.19.0-18-generic
   
  ---Patches Installed---
  A patched powerpc-ibm-utils package is required
   
  Machine Type = POWER8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1) Using latest daily ISO install 14.04.02 as a Power VM guest
  2) Upgrade the kernel to 3.19 level (3.19.0-18-generic)
  3) Ensure ksh and powerpc-ibm-utils packages are installed.
  4) Download following DLPAR packages from 
http://ausgsa.ibm.com/projects/r/rsctdev/builds/muthu/rmuts006a/ppc64le/

  devices.chrp.base.servicerm_2.5.0.1-15111_ppc64el.deb
  dynamicrm_2.0.1-3_ppc64el.deb
  rsct.core_3.2.0.6-15111_ppc64el.deb
  rsct.core.utils_3.2.0.6-15111_ppc64el.deb
  src_3.2.0.6-15111_ppc64el.deb

  5) Install the packages.
  6) Perform a add memory operation via HMC
   
  Stack trace output:

  alp9 kernel: [44170.234662] [ cut here ]
  alp9 kernel: [44170.234667] WARNING: at 
/build/buildd/linux-lts-vivid-3.19.0/drivers/base/memory.c:200
  alp9 kernel: [44170.234668] Modules linked in: rpadlpar_io rpaphp pseries_rng 
rtc_generic
  alp9 kernel: [44170.234675] CPU: 2 PID: 1391 Comm: systemd-udevd Not tainted 
3.19.0-18-generic #18~14.04.1-Ubuntu
  alp9 kernel: [44170.234677] task: c003dbea7c80 ti: c003dbf1 
task.ti: c003dbf1
  Jun  4 19:44:47 alp9 kernel: [44170.234678] NIP: c0668f34 LR: 
c06699b0 CTR: 
  Jun  4 19:44:47 alp9 kernel: [44170.234680] REGS: c003dbf13910 TRAP: 0700 
  Not tainted  (3.19.0-18-generic)
  Jun  4 19:44:47 alp9 kernel: [44170.234680] MSR: 80029033 
  CR: 28042888  XER: 2000
  Jun  4 19:44:47 alp9 kernel: [44170.234686] CFAR: c0668ed8 SOFTE: 1 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR00: c06699b0 
c003dbf13b90 c144c760 0001 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR04: 0779 
0100 00078000 f1de4000 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR08: c13ac760 
0001 7790 003f 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR12: c172cb00 
ce831200 0100074a0010  
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR16: 10032230 
100311d0 3fffcb59bf20 0003 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR20: 100527f8 
100322b0 01312d00 0100074af7f0 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR24: 100322d0 
3fffcb59bf20 c003dbf13e00  
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR28: 1000 
 00077000 00077900 
  Jun  4 19:44:47 alp9 kernel: [44170.234707] NIP [c0668f34] 
pages_correctly_reserved+0x134/0x1c0
  Jun  4 19:44:47 alp9 kernel: [44170.234709] LR [c06699b0] 
memory_subsys_online+0x70/0x140
  Jun  4 19:44:47 alp9 kernel: [44170.234710] Call Trace:
  Jun  4 19:44:47 alp9 kernel: [44170.234711] [c003dbf13b90] 
[0006] 0x6 (unreliable)
  Jun  4 19:44:47 alp9 kernel: [44170.234714] [c003dbf13c00] 
[c06699b0] memory_subsys_online+0x70/0x140
  Jun  4 19:44:47 alp9 kernel: [44170.234716] [c003dbf13c40] 
[c06476f4] device_online+0xb4/0x120
  Jun  4 19:44:47 alp9 kernel: [44170.234718] [c003dbf13c80] 
[c066987c] store_mem_state+0x8c/0x150
  Jun  4 19:44:47 alp9 kernel: [44170.234721] [c003dbf13cc0] 
[c0643618] dev_attr_store+0x68/0xa0
  Jun  4 19:44:47 alp9 kernel: [44170.234724] [c003dbf13d00] 
[c035afd0] sysfs_kf_write+0x80/0xb0
  Jun  4 19:44:47 alp9 kernel: [44170.234726] [c003dbf13d40] 
[c0359f0c] kernfs_fop_write+0x18c/0x1f0
  Jun  4 19:44:47 alp9 kernel: [44170.234730] [c003dbf13d90] 
[c02b450c] vfs_write+0xdc/0x260
  Jun  4 19:44:47 alp9 kernel: [44170.234732] [c003dbf13de0] 
[c02b53bc] SyS_write+0x6c/0x110
  Jun  4 19:44:47 alp9 kernel: [44170.234735] [c003dbf13e30] 
[c0009258] system_call+0x38/0xd0
  Jun  4 19:44:47 alp9 kernel: [44170.234736] Instruction dump:
  Jun  4 19:44:47 alp9 kernel: [44170.234737] 419e0024 788a2428 7d095214 
2fa8 41de0014 7d29502a 38e74000 7928ffe3 
  Jun  4 19:44:47 alp9 kernel: [44170.234740] 4082ff7c 3d02fff6 892808e3 
69290001 <0b09> 2fa9 40de0068 

[Kernel-packages] [Bug 1536245] [NEW] s390x kernel image needs weightwatchers

2016-01-20 Thread Dimitri John Ledkov
Public bug reported:

http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer-
amd64/current/images/cdrom/vmlinuz

is 6.6M

http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-
s390x/current/images/generic/kernel.debian

is 12M

Yet, s390x has much less drivers. I would have expected it to be slimmer
than amd64.

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

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

Title:
  s390x kernel image needs weightwatchers

Status in linux package in Ubuntu:
  New

Bug description:
  http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer-
  amd64/current/images/cdrom/vmlinuz

  is 6.6M

  http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-
  s390x/current/images/generic/kernel.debian

  is 12M

  Yet, s390x has much less drivers. I would have expected it to be
  slimmer than amd64.

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

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


[Kernel-packages] [Bug 1535660] Re: Certain Bluetooth mice do not pair with Ubuntu

2016-01-20 Thread Launchpad Bug Tracker
** Branch linked: lp:~ken-vandine/ubuntu-system-
settings/bluetooth_lp1535660

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

Title:
  Certain Bluetooth mice do not pair with Ubuntu

Status in The Avila project:
  Confirmed
Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  I have a Microsoft Arc Mouse Surface Edition, and tried to pair it
  with my Ubuntu (trusty) desktop.

  It shows up in the pairing gui with a little mouse icon, but the UI
  offers no option to pair to the device.

  On Ubuntu touch, system settings never shows the device as something
  that can be paired to.

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

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


[Kernel-packages] [Bug 1509751] Re: Kernel disabling serial port ttyS0 again

2016-01-20 Thread Hans109h
fix after afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc

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

Title:
  Kernel disabling serial port ttyS0 again

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Upon upgrading from 14.10 to Ubuntu Gnome 15.10 with kernel 4.2 I am
  once again unable to access my serial port.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D0c', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Sat Oct 24 22:50:11 2015
  HibernationDevice: RESUME=UUID=61ccfbf9-f4d0-4989-8d82-be0dd1500450
  InstallationDate: Installed on 2014-11-30 (328 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=e0e80586-764e-42bf-8659-c5da430f1d1e ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-10-24 (0 days ago)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V
  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.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.xx: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/1509751/+subscriptions

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


[Kernel-packages] [Bug 1536038] Re: ELAN1000 touchpad not recognised correctly, with upstream kernel it recognised, but freezes randomly

2016-01-20 Thread Christopher M. Penalver
** Description changed:

- I've got an ASUS E403SA notebook with Ubuntu 15.10 and kernel
- 4.2.0-23-generic from default repository. The touchpad is in PS/2 mouse
- emulation mode so multitouch like two-finger scrolling is not available.
- 
- Dmesg output attached and xinput --list shows:
- 
- ⎡ Virtual core pointerid=2[master pointer  (3)]
- ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
- ⎜   ↳ ELAN1000:00 04F3:0401   id=11   [slave  pointer 
 (2)]
- ⎣ Virtual core keyboard   id=3[master keyboard (2)]
- ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
- ↳ Power Buttonid=6[slave  
keyboard (3)]
- ↳ Video Bus   id=7[slave  
keyboard (3)]
- ↳ Sleep Buttonid=8[slave  
keyboard (3)]
- ↳ USB2.0 VGA UVC WebCam   id=10   [slave  
keyboard (3)]
- ↳ Asus WMI hotkeysid=12   [slave  
keyboard (3)]
- ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
- 
- The correct driver merged in 4.3.x kernel so I decided to test it from
- mainline repo http://kernel.ubuntu.com/~kernel-ppa/mainline/
- 
- With kernel 4.3.x and newer the touchpad recognised correctly and
- multitouch works. After a while (minutes, sometimes hours) the touchpad
- completely freezes with this message in syslog:
- 
+ I've got an ASUS E403SA notebook. With kernel 4.3.x and newer, after a while 
(minutes, sometimes hours) the touchpad completely freezes with this message in 
syslog:
  Jan  5 20:55:27 darkslide-notebook kernel: [ 1531.867948] i2c_designware 
808622C1:03: Unknown Synopsys component type: 0x
  Jan  5 20:55:27 darkslide-notebook kernel: [ 1531.893399] i2c_designware 
808622C1:03: timeout in enabling adapter
  Jan  5 20:55:28 darkslide-notebook kernel: [ 1532.892319] i2c_designware 
808622C1:03: controller timed out
  Jan  5 20:55:28 darkslide-notebook kernel: [ 1532.892334] i2c_designware 
808622C1:03: Unknown Synopsys component type: 0x
  Jan  5 20:55:28 darkslide-notebook kernel: [ 1532.892343] elan_i2c 
i2c-ELAN1000:00: failed to read report data: -110
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-23-generic 4.2.0-23.28
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  darkslide   1511 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  darkslide   1511 F pulseaudio
  Date: Wed Jan 20 08:33:06 2016
  HibernationDevice: RESUME=UUID=2e8dbaca-618a-4aff-95bf-a134e77a2ea5
  InstallationDate: Installed on 2015-12-11 (39 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: ASUSTeK COMPUTER INC. E403SA
  ProcEnviron:
-  LANGUAGE=hu
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=hu_HU.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=hu
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=hu_HU.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic.efi.signed 
root=UUID=9179712a-c5fc-4d70-ad86-517fad86f155 ro intel_idle.max_cstate=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linux-restricted-modules-4.2.0-23-generic N/A
-  linux-backports-modules-4.2.0-23-generic  N/A
-  linux-firmware1.149.3
+  linux-restricted-modules-4.2.0-23-generic N/A
+  linux-backports-modules-4.2.0-23-generic  N/A
+  linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Nincs ilyen fájl vagy könyvtár: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E403SA.212
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E403SA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE403SA.212:bd08/13/2015:svnASUSTeKCOMPUTERINC.:pnE403SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE403SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E403SA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Tags removed: wily
** Tags added: xenial

** Summary changed:

- ELAN1000 touchpad not recognised correctly, with upstream kernel it 
recognised, but freezes randomly
+ [Asus E403SA] ELAN1000 touchpad freezes after minutes to hours

** 

[Kernel-packages] [Bug 1535736] Re: linux: 4.3.0-7.18 -proposed tracker

2016-01-20 Thread Dimitri John Ledkov
d-i has changed paths for s390x installer, and a matching debian-cd code
change is merged.

However debian-cd will need a deployment to production once d-i & kernel
migrate.

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

Title:
  linux: 4.3.0-7.18 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.3.0-7.18 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-Prepare-package-start:Tuesday, 19. January 2016 14:09 UTC
  kernel-phase-changed:Tuesday, 19. January 2016 14:09 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 19. January 2016 15:00 UTC
  proposed-announcement-sent:True

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

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


[Kernel-packages] [Bug 1533009] Re: arm64: "unsupported RELA relocation"

2016-01-20 Thread Christophe Lyon
I've cross compiled the kernel+modules, mostly following the steps in
comment #18.

Then, I've scanned the generated module for the AARCH64_ADR_PREL_PG_HI21
relocation.

When compiled with Linaro-2015.12, this relocation is present.
When compiled with Linaro-2015.10, it is not.
When using Linaro-2015.11, the build fails with errors such as:
Assembler messages:
Error: selected processor does not support `aese v0.16b,v1.16b'

Assuming that these relocations are the real cause of the problem, I'm
going to bisect to identify which commit in our branch introduced them.

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

Title:
  arm64: "unsupported RELA relocation"

Status in Linaro GCC:
  Unknown
Status in Linux:
  Unknown
Status in gcc-5 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  linux-image-4.3.0-5-generic 4.3.0-5.16 arm64 fails to load modules
  (and therefore boot). It emits messages like the following for each
  attempted module load:

  [2.156817] module libahci: unsupported RELA relocation: 275

  This is reminiscent of LP: #1502946 - except that fix appears to still
  be in-tact. What has changed, however, is the build environment. If I
  rebuild the same kernel source in a wily chroot, it boots fine.

  Marking "Confirmed" because Paulo Pisatti reported this to me, and I
  reproduced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc-linaro/+bug/1533009/+subscriptions

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


[Kernel-packages] [Bug 1454892] Re: [Hyper-V] hv_netvsc: Use the xmit_more skb flag to optimize signaling the host

2016-01-20 Thread Joshua R. Poulson
Sorry, the test team was buried under some other items, and we had not
made it to this one yet.

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

Title:
  [Hyper-V] hv_netvsc: Use the xmit_more skb flag to optimize signaling
  the host

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-utopic package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux-lts-utopic source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  hv_netvsc: Use the xmit_more skb flag to optimize signaling the host
  Based on the information given to this driver (via the xmit_more skb flag),
  we can defer signaling the host if more packets are on the way. This will help
  make the host more efficient since it can potentially process a larger batch 
of
  packets. Implement this optimization.

  Upstream commit: https://git.kernel.org/cgit/linux/kernel/git/davem
  /net-next.git/commit/?id=82fa3c776e5abba7ed6e4b4f4983d14731c37d6a

  This commit may imply other commits previously requested, for example
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452074

  Requested for all typical Hyper-V targets: 15.10, 15.04, 14.10, 14.04,
  14.04 HWE, 12.02, and 12.02 HWE

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

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


[Kernel-packages] [Bug 1255428] Re: 8086:0116 [Lenovo IdeaPad Z570] LCD brightness control keys and widget do not work on Intel Graphics

2016-01-20 Thread Shriramana Sharma
I'm sorry but I'm still running Trusty LTS waiting for the next LTS to
install. It seems the 4.4 kernel is only available for Wily but Wily
comes with 4.2 and I'll have to install Wily and the kernel. Is it
sufficient for me to test a recent daily image from
http://cdimage.ubuntu.com/kubuntu/daily-live/current/ and tell you?

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

Title:
  8086:0116 [Lenovo IdeaPad Z570] LCD brightness control keys and widget
  do not work on Intel Graphics

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Saucy, on my Lenovo IdeaPad Z570 with Intel HD
  Graphics 3000, it is no longer possible to control the LCD brightness
  using the hardware brightness control keys. Likewise for the KDE power
  management settings or the battery icon on my Kubuntu Plasma tray. (I
  don't use GNOME/Unity.) Until Raring I did not have this problem.

  WORKAROUND: At a terminal:
  echo 150 | sudo tee /sys/class/backlight/intel_backlight/brightness

  where 150 is on the scale of 0 to whatever is given within
  /sys/class/backlight/intel_backlight/max_brightness. Based on this I
  wrote a GUI which however needs to be run using sudo/kdesudo/gksudo. I
  have attached it.

  ---
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2013-10-19 (38 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  Package: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Tags:  saucy
  Uname: Linux 3.11.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  ---
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  samjnaa1717 F pulseaudio
  DistroRelease: Ubuntu 13.10
  HibernationDevice: RESUME=UUID=ba00d992-e43e-4bce-8689-9647370add15
  InstallationDate: Installed on 2013-10-19 (117 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO HuronRiver Platform
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=(hd0,msdos9)/vmlinuz root=/dev/sda9 ro quiet 
splash
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.116
  StagingDrivers: rts5139
  Tags:  saucy staging
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 02/22/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 45CN28WW
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Emerald Lake
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnLENOVO:bvr45CN28WW:bd02/22/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
  dmi.product.name: HuronRiver Platform
  dmi.product.version: Ideapad Z570
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1536245] Re: s390x kernel image needs weightwatchers

2016-01-20 Thread ChristianEhrhardt
Reference other s390 (RH based z/KVM)
-rwxr-xr-x. 1 root root 3.7M Aug 28 13:00 
/boot/vmlinuz-3.10.0-123.20.1.el7_0.kvmibm.15.s390x

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

Title:
  s390x kernel image needs weightwatchers

Status in linux package in Ubuntu:
  New

Bug description:
  http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer-
  amd64/current/images/cdrom/vmlinuz

  is 6.6M

  http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-
  s390x/current/images/generic/kernel.debian

  is 12M

  Yet, s390x has much less drivers. I would have expected it to be
  slimmer than amd64.

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

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


[Kernel-packages] [Bug 1536249] Re: XPS 13 9350: reboot fails with "Transaction is destructive" after resume from suspend

2016-01-20 Thread Robin Winslow
apport information

** Tags added: apport-collected wily

** Description changed:

  With my brand new Dell XPS 13 9350 and Ubuntu 15.10. The graphical
  "reboot" and "shut down" buttons don't do anything, and from the CLI I
  get:
  
  $ reboot
  Failed to execute operation: Transaction is destructive.
  
  I imagine it's associated with closing the lid to suspend because when I
  first start the system it reboots fine. It resumes fine when I open the
  lid in the sense that I can enter my password and continue to use
  Ubuntu, but it would make sense if there's something hanging about in
  the background. I don't know how to check this.
  
- (I initially found this "wontfix" bug which describes the same problem:
- https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253)
+ (I initially found this "wontfix" bug which describes the same problem: 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253)
+ --- 
+ ApportVersion: 2.19.1-0ubuntu5
+ Architecture: amd64
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 15.10
+ EcryptfsInUse: Yes
+ InstallationDate: Installed on 2016-01-18 (1 days ago)
+ InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
+ Package: linux (not installed)
+ Tags:  wily
+ Uname: Linux 4.3.0-wifitest-custom x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

Title:
  XPS 13 9350: reboot fails with "Transaction is destructive" after
  resume from suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my brand new Dell XPS 13 9350 and Ubuntu 15.10. The graphical
  "reboot" and "shut down" buttons don't do anything, and from the CLI I
  get:

  $ reboot
  Failed to execute operation: Transaction is destructive.

  This only happens after resuming from suspend after the lid was
  closed. Also, the touch screen no longer works after resuming.

  (I initially found this "wontfix" bug which describes the same problem: 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253)
  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-18 (1 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  Tags:  wily
  Uname: Linux 4.3.0-wifitest-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


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

2016-01-20 Thread Robin Winslow
apport information

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

Title:
  XPS 13 9350: reboot fails with "Transaction is destructive" after
  resume from suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my brand new Dell XPS 13 9350 and Ubuntu 15.10. The graphical
  "reboot" and "shut down" buttons don't do anything, and from the CLI I
  get:

  $ reboot
  Failed to execute operation: Transaction is destructive.

  This only happens after resuming from suspend after the lid was
  closed. Also, the touch screen no longer works after resuming.

  (I initially found this "wontfix" bug which describes the same problem: 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253)
  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-18 (1 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  Tags:  wily
  Uname: Linux 4.3.0-wifitest-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1536124] Re: linux: 3.19.0-48.54 -proposed tracker

2016-01-20 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

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

Title:
  linux: 3.19.0-48.54 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.19.0-48.54 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-stable-Prepare-package-start:Wednesday, 20. January 2016 10:56 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Wednesday, 20. January 2016 10:56 UTC

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

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


[Kernel-packages] [Bug 1535880] Re: linux: 3.13.0-77.121 -proposed tracker

2016-01-20 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques 
(henrix)

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

Title:
  linux: 3.13.0-77.121 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.13.0-77.121 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-stable-Prepare-package-start:Tuesday, 19. January 2016 19:59 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 19. January 2016 19:59 UTC

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

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


[Kernel-packages] [Bug 1535736] rukbah (amd64) - tests ran: 83, failed: 1

2016-01-20 Thread Brad Figg
tests ran:  83, failed: 1;
  
http://kernel.ubuntu.com/testing/4.3.0-7.18/rukbah__4.3.0-7.18__2016-01-20_12-35-00/results-index.html

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

Title:
  linux: 4.3.0-7.18 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.3.0-7.18 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-Prepare-package-start:Tuesday, 19. January 2016 14:09 UTC
  kernel-phase-changed:Tuesday, 19. January 2016 14:09 UTC
  kernel-phase:Prepare
  kernel-stable-Promote-to-proposed-end:Tuesday, 19. January 2016 15:00 UTC
  proposed-announcement-sent:True

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

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


[Kernel-packages] [Bug 1463654] [NEW] Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation

2016-01-20 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

---Problem Description---
Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation
 
Contact Information = Sachin Sant / ss...@in.ibm.com 
 
---uname output---
3.19.0-18-generic
 
---Patches Installed---
A patched powerpc-ibm-utils package is required
 
Machine Type = POWER8 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 1) Using latest daily ISO install 14.04.02 as a Power VM guest
2) Upgrade the kernel to 3.19 level (3.19.0-18-generic)
3) Ensure ksh and powerpc-ibm-utils packages are installed.
4) Download following DLPAR packages from 
http://ausgsa.ibm.com/projects/r/rsctdev/builds/muthu/rmuts006a/ppc64le/

devices.chrp.base.servicerm_2.5.0.1-15111_ppc64el.deb
dynamicrm_2.0.1-3_ppc64el.deb
rsct.core_3.2.0.6-15111_ppc64el.deb
rsct.core.utils_3.2.0.6-15111_ppc64el.deb
src_3.2.0.6-15111_ppc64el.deb

5) Install the packages.
6) Perform a add memory operation via HMC
 
Stack trace output:

alp9 kernel: [44170.234662] [ cut here ]
alp9 kernel: [44170.234667] WARNING: at 
/build/buildd/linux-lts-vivid-3.19.0/drivers/base/memory.c:200
alp9 kernel: [44170.234668] Modules linked in: rpadlpar_io rpaphp pseries_rng 
rtc_generic
alp9 kernel: [44170.234675] CPU: 2 PID: 1391 Comm: systemd-udevd Not tainted 
3.19.0-18-generic #18~14.04.1-Ubuntu
alp9 kernel: [44170.234677] task: c003dbea7c80 ti: c003dbf1 
task.ti: c003dbf1
Jun  4 19:44:47 alp9 kernel: [44170.234678] NIP: c0668f34 LR: 
c06699b0 CTR: 
Jun  4 19:44:47 alp9 kernel: [44170.234680] REGS: c003dbf13910 TRAP: 0700   
Not tainted  (3.19.0-18-generic)
Jun  4 19:44:47 alp9 kernel: [44170.234680] MSR: 80029033 
  CR: 28042888  XER: 2000
Jun  4 19:44:47 alp9 kernel: [44170.234686] CFAR: c0668ed8 SOFTE: 1 
Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR00: c06699b0 
c003dbf13b90 c144c760 0001 
Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR04: 0779 
0100 00078000 f1de4000 
Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR08: c13ac760 
0001 7790 003f 
Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR12: c172cb00 
ce831200 0100074a0010  
Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR16: 10032230 
100311d0 3fffcb59bf20 0003 
Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR20: 100527f8 
100322b0 01312d00 0100074af7f0 
Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR24: 100322d0 
3fffcb59bf20 c003dbf13e00  
Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR28: 1000 
 00077000 00077900 
Jun  4 19:44:47 alp9 kernel: [44170.234707] NIP [c0668f34] 
pages_correctly_reserved+0x134/0x1c0
Jun  4 19:44:47 alp9 kernel: [44170.234709] LR [c06699b0] 
memory_subsys_online+0x70/0x140
Jun  4 19:44:47 alp9 kernel: [44170.234710] Call Trace:
Jun  4 19:44:47 alp9 kernel: [44170.234711] [c003dbf13b90] 
[0006] 0x6 (unreliable)
Jun  4 19:44:47 alp9 kernel: [44170.234714] [c003dbf13c00] 
[c06699b0] memory_subsys_online+0x70/0x140
Jun  4 19:44:47 alp9 kernel: [44170.234716] [c003dbf13c40] 
[c06476f4] device_online+0xb4/0x120
Jun  4 19:44:47 alp9 kernel: [44170.234718] [c003dbf13c80] 
[c066987c] store_mem_state+0x8c/0x150
Jun  4 19:44:47 alp9 kernel: [44170.234721] [c003dbf13cc0] 
[c0643618] dev_attr_store+0x68/0xa0
Jun  4 19:44:47 alp9 kernel: [44170.234724] [c003dbf13d00] 
[c035afd0] sysfs_kf_write+0x80/0xb0
Jun  4 19:44:47 alp9 kernel: [44170.234726] [c003dbf13d40] 
[c0359f0c] kernfs_fop_write+0x18c/0x1f0
Jun  4 19:44:47 alp9 kernel: [44170.234730] [c003dbf13d90] 
[c02b450c] vfs_write+0xdc/0x260
Jun  4 19:44:47 alp9 kernel: [44170.234732] [c003dbf13de0] 
[c02b53bc] SyS_write+0x6c/0x110
Jun  4 19:44:47 alp9 kernel: [44170.234735] [c003dbf13e30] 
[c0009258] system_call+0x38/0xd0
Jun  4 19:44:47 alp9 kernel: [44170.234736] Instruction dump:
Jun  4 19:44:47 alp9 kernel: [44170.234737] 419e0024 788a2428 7d095214 2fa8 
41de0014 7d29502a 38e74000 7928ffe3 
Jun  4 19:44:47 alp9 kernel: [44170.234740] 4082ff7c 3d02fff6 892808e3 69290001 
<0b09> 2fa9 40de0068 3860 
Jun  4 19:44:47 alp9 kernel: [44170.234744] ---[ end trace f8d28c560fa5c980 ]---
 

System Dump Info:
  The system is not configured to capture a system dump.
 
== Comment: #1 - SACHIN P. SANT  - 2015-06-05 01:28:00 ==
The DLPAR memory operation succeeds and is not affected by this warning.

== Comment: #3 - Nathan D. Fontenot  - 2015-06-05 07:11:45 
==
Looking at this issue further, it appears to only happen when adding memory 
that was previously removed. When adding 

[Kernel-packages] [Bug 1463654] Re: Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation

2016-01-20 Thread bugproxy
--- Comment From cha...@us.ibm.com 2016-01-20 10:29 EDT---
The patch is tested for the kernel version 4.4.0 and it works as expected.

** Tags removed: targetmilestone-inin14043
** Tags added: targetmilestone-inin14044

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

Title:
  Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation
   
  Contact Information = Sachin Sant / ss...@in.ibm.com 
   
  ---uname output---
  3.19.0-18-generic
   
  ---Patches Installed---
  A patched powerpc-ibm-utils package is required
   
  Machine Type = POWER8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1) Using latest daily ISO install 14.04.02 as a Power VM guest
  2) Upgrade the kernel to 3.19 level (3.19.0-18-generic)
  3) Ensure ksh and powerpc-ibm-utils packages are installed.
  4) Download following DLPAR packages from 
http://ausgsa.ibm.com/projects/r/rsctdev/builds/muthu/rmuts006a/ppc64le/

  devices.chrp.base.servicerm_2.5.0.1-15111_ppc64el.deb
  dynamicrm_2.0.1-3_ppc64el.deb
  rsct.core_3.2.0.6-15111_ppc64el.deb
  rsct.core.utils_3.2.0.6-15111_ppc64el.deb
  src_3.2.0.6-15111_ppc64el.deb

  5) Install the packages.
  6) Perform a add memory operation via HMC
   
  Stack trace output:

  alp9 kernel: [44170.234662] [ cut here ]
  alp9 kernel: [44170.234667] WARNING: at 
/build/buildd/linux-lts-vivid-3.19.0/drivers/base/memory.c:200
  alp9 kernel: [44170.234668] Modules linked in: rpadlpar_io rpaphp pseries_rng 
rtc_generic
  alp9 kernel: [44170.234675] CPU: 2 PID: 1391 Comm: systemd-udevd Not tainted 
3.19.0-18-generic #18~14.04.1-Ubuntu
  alp9 kernel: [44170.234677] task: c003dbea7c80 ti: c003dbf1 
task.ti: c003dbf1
  Jun  4 19:44:47 alp9 kernel: [44170.234678] NIP: c0668f34 LR: 
c06699b0 CTR: 
  Jun  4 19:44:47 alp9 kernel: [44170.234680] REGS: c003dbf13910 TRAP: 0700 
  Not tainted  (3.19.0-18-generic)
  Jun  4 19:44:47 alp9 kernel: [44170.234680] MSR: 80029033 
  CR: 28042888  XER: 2000
  Jun  4 19:44:47 alp9 kernel: [44170.234686] CFAR: c0668ed8 SOFTE: 1 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR00: c06699b0 
c003dbf13b90 c144c760 0001 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR04: 0779 
0100 00078000 f1de4000 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR08: c13ac760 
0001 7790 003f 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR12: c172cb00 
ce831200 0100074a0010  
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR16: 10032230 
100311d0 3fffcb59bf20 0003 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR20: 100527f8 
100322b0 01312d00 0100074af7f0 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR24: 100322d0 
3fffcb59bf20 c003dbf13e00  
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR28: 1000 
 00077000 00077900 
  Jun  4 19:44:47 alp9 kernel: [44170.234707] NIP [c0668f34] 
pages_correctly_reserved+0x134/0x1c0
  Jun  4 19:44:47 alp9 kernel: [44170.234709] LR [c06699b0] 
memory_subsys_online+0x70/0x140
  Jun  4 19:44:47 alp9 kernel: [44170.234710] Call Trace:
  Jun  4 19:44:47 alp9 kernel: [44170.234711] [c003dbf13b90] 
[0006] 0x6 (unreliable)
  Jun  4 19:44:47 alp9 kernel: [44170.234714] [c003dbf13c00] 
[c06699b0] memory_subsys_online+0x70/0x140
  Jun  4 19:44:47 alp9 kernel: [44170.234716] [c003dbf13c40] 
[c06476f4] device_online+0xb4/0x120
  Jun  4 19:44:47 alp9 kernel: [44170.234718] [c003dbf13c80] 
[c066987c] store_mem_state+0x8c/0x150
  Jun  4 19:44:47 alp9 kernel: [44170.234721] [c003dbf13cc0] 
[c0643618] dev_attr_store+0x68/0xa0
  Jun  4 19:44:47 alp9 kernel: [44170.234724] [c003dbf13d00] 
[c035afd0] sysfs_kf_write+0x80/0xb0
  Jun  4 19:44:47 alp9 kernel: [44170.234726] [c003dbf13d40] 
[c0359f0c] kernfs_fop_write+0x18c/0x1f0
  Jun  4 19:44:47 alp9 kernel: [44170.234730] [c003dbf13d90] 
[c02b450c] vfs_write+0xdc/0x260
  Jun  4 19:44:47 alp9 kernel: [44170.234732] [c003dbf13de0] 
[c02b53bc] SyS_write+0x6c/0x110
  Jun  4 19:44:47 alp9 kernel: [44170.234735] [c003dbf13e30] 
[c0009258] system_call+0x38/0xd0
  Jun  4 19:44:47 alp9 kernel: [44170.234736] Instruction dump:
  Jun  4 19:44:47 alp9 kernel: [44170.234737] 419e0024 788a2428 7d095214 
2fa8 41de0014 7d29502a 38e74000 7928ffe3 
  Jun  4 19:44:47 alp9 

[Kernel-packages] [Bug 1525324] Re: kernel/bonding: wrong netlink messages when deleting a bonding interface

2016-01-20 Thread Nicolas Dichtel
Here it is.

** Attachment added: "bug.apport"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1525324/+attachment/4553431/+files/bug.apport

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

Title:
  kernel/bonding: wrong netlink messages when deleting a bonding
  interface

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Here is the bug:

  root@ubuntu1404:~# modprobe bonding
  root@ubuntu1404:~# modprobe dummy
  root@ubuntu1404:~# ip link set dummy0 master bond0
  root@ubuntu1404:~# ip monitor link&
  [1] 1065
  root@ubuntu1404:~# ip link del bond0
  Deleted 6: bond0:  mtu 1500 qdisc noop state DOWN 
group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  7: dummy0:  mtu 1500 qdisc noqueue state 
UNKNOWN group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  7: dummy0:  mtu 1500 qdisc noqueue state UNKNOWN 
group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  6: bond0:  mtu 1500 qdisc noop state DOWN group 
default 
  link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff
  6: bond0:  mtu 1500 qdisc noop state DOWN group 
default 
  root@ubuntu1404:~# link/ether e6:49:16:3b:17:fe brd ff:ff:ff:ff:ff:ff
  7: dummy0:  mtu 1500 qdisc noqueue state DOWN group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  7: dummy0:  mtu 1500 qdisc noqueue state DOWN group default 
  link/ether c2:46:53:08:ee:50 brd ff:ff:ff:ff:ff:ff
  ^C
  root@ubuntu1404:~# uname -a
  Linux ubuntu1404 3.13.0-71-generic #114-Ubuntu SMP Tue Dec 1 02:34:22 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux
  root@ubuntu1404:~#

  A netlink message advertise that bond0 is deleted and after that two
  netlink messages are sent telling that bond0 exists again.

  This bug has been fixed by these upstream commits:
  56bfa7ee7c88 unregister_netdevice : move RTM_DELLINK to until after ndo_uninit
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=56bfa7ee7c88
  395eea6ccf2b rtnetlink: delay RTM_DELLINK notification until after 
ndo_uninit()
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=395eea6ccf2b

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

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


[Kernel-packages] [Bug 1519897] Re: [Hyper-V] hv: vmbus: Fix a host signaling bug

2016-01-20 Thread Joseph Salisbury
I built a Trusty test kernel with commit 8599846 and all the necessary
prereqs.

Please test the following kernel and let us know your results.  If we
can receive positive test feedback by January 29th, we can proceed to
submit the patches for kernel SRU review in an attempt to make the
upcoming kernel SRU cycle starting on January 29th.  Assuming the
patches are accepted for SRU and land in the upcoming SRU cycle, the fix
should be available from the -updates pocket by February 20th.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1519897/trusty

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

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

Title:
  [Hyper-V] hv: vmbus: Fix a host signaling bug

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-trusty package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux-lts-trusty source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  The following fix has been submitted upstream, but has high enough
  severity that we would like early inclusion into the Ubuntu kernel.
  Please consider for wily, vivid, and trusty (and the HWE kernels for
  the same).

  Patch follows:

  Currently we have two policies for deciding when to signal the host:
  One based on the ring buffer state and the other based on what the VMBUS 
client driver wants to do. Consider the case when the client wants to 
explicitly control when to signal the host. In this case, if the client were to 
defer signaling, we will not be able to signal the host subsequently when the 
client does want to signal since the ring buffer state will prevent the 
signaling. Implement logic to have only one signaling policy in force for a 
given channel.

  Signed-off-by: K. Y. Srinivasan 
  Reviewed-by: Haiyang Zhang 
  Tested-by: Haiyang Zhang 
  Cc:  # v4.2+
  ---
   drivers/hv/channel.c   |   18 ++
   include/linux/hyperv.h |   12 
   2 files changed, 30 insertions(+), 0 deletions(-)

  diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c index 
77d2579..c6278c7 100644
  --- a/drivers/hv/channel.c
  +++ b/drivers/hv/channel.c
  @@ -653,10 +653,19 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel, 
void *buffer,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  @@ -756,10 +765,19 @@ int vmbus_sendpacket_pagebuffer_ctl(struct 
vmbus_channel *channel,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index 
437c9c8..7b1af52 100644
  --- a/include/linux/hyperv.h
  +++ b/include/linux/hyperv.h
  @@ -756,8 +756,20 @@ struct vmbus_channel {
     * link up channels based on their CPU affinity.
     */
    struct list_head percpu_list;
  + /*
  +  * Host signaling policy: The default policy will be
  +  * based on the ring buffer state. We will also support
  +  * a policy where the client driver can have explicit
  +  * signaling control.
  +  */
  + bool signal_state;
   };

  +static inline void set_channel_signal_state(struct vmbus_channel *c,
  +bool state) {
  + c->signal_state = state;
  +}
  +
   static inline void set_channel_read_state(struct vmbus_channel *c, bool 
state)  {
    c->batched_reading = state;
  --
  1.7.4.1

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

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

[Kernel-packages] [Bug 1516547] Re: Ubuntu 15.10 crashes with RAID-10

2016-01-20 Thread Joseph Salisbury
I built the next test kernel, up to the following commit:
5c65e7be4cbb015e39759275746f31bb6fa74f77

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1516547

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  Ubuntu 15.10 crashes with RAID-10

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Wily:
  In Progress

Bug description:
  When trying to install Ubuntu 15.10 with a RAID-10 created the system
  crashes after some time during the installation. Hitting Alt+F4 gives
  the following output as seen from screenshots in attachments.

  It looks like kernel 4.2 have some issues with RAID-10 as we can
  install Ubuntu 15.04 (with kernel 3.19) without problems. If we
  upgrade to kernel 4.2 in Ubuntu 15.04 we get the same errors.

  We have no problems when installing without RAID, RAID-0 or RAID-1.
  We've also tried on different hardware and different disk types/sizes
  but we still get system crash.

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

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


[Kernel-packages] [Bug 1533009] Re: arm64: "unsupported RELA relocation"

2016-01-20 Thread Christophe Lyon
That's what I expected: this has nothing to do with relocations.

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

Title:
  arm64: "unsupported RELA relocation"

Status in Linaro GCC:
  Unknown
Status in Linux:
  Unknown
Status in gcc-5 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  linux-image-4.3.0-5-generic 4.3.0-5.16 arm64 fails to load modules
  (and therefore boot). It emits messages like the following for each
  attempted module load:

  [2.156817] module libahci: unsupported RELA relocation: 275

  This is reminiscent of LP: #1502946 - except that fix appears to still
  be in-tact. What has changed, however, is the build environment. If I
  rebuild the same kernel source in a wily chroot, it boots fine.

  Marking "Confirmed" because Paulo Pisatti reported this to me, and I
  reproduced.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gcc-linaro/+bug/1533009/+subscriptions

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


[Kernel-packages] [Bug 1509751] Re: Kernel disabling serial port ttyS0 again

2016-01-20 Thread Hans109h
A recent commit has fixed this problem upstream.  I need to bisect
still, just keeping some notes here.

Fixed prior to commit 5807fcaa9bf7dd87241df739161c119cf78a6bc4 but after
v4.4.0

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

Title:
  Kernel disabling serial port ttyS0 again

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Upon upgrading from 14.10 to Ubuntu Gnome 15.10 with kernel 4.2 I am
  once again unable to access my serial port.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D0c', 
'/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Date: Sat Oct 24 22:50:11 2015
  HibernationDevice: RESUME=UUID=61ccfbf9-f4d0-4989-8d82-be0dd1500450
  InstallationDate: Installed on 2014-11-30 (328 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=e0e80586-764e-42bf-8659-c5da430f1d1e ro crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-10-24 (0 days ago)
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2104
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z77-V
  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.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.xx: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/1509751/+subscriptions

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


[Kernel-packages] [Bug 1454892] Re: [Hyper-V] hv_netvsc: Use the xmit_more skb flag to optimize signaling the host

2016-01-20 Thread Joseph Salisbury
Hi Josh,

Do you happen to know if testing was performed with the test kernel as
of yet?  Some of the Trusty prereqs for bug 1519897 would come in via
this bug fix.

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

Title:
  [Hyper-V] hv_netvsc: Use the xmit_more skb flag to optimize signaling
  the host

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-utopic package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux-lts-utopic source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  hv_netvsc: Use the xmit_more skb flag to optimize signaling the host
  Based on the information given to this driver (via the xmit_more skb flag),
  we can defer signaling the host if more packets are on the way. This will help
  make the host more efficient since it can potentially process a larger batch 
of
  packets. Implement this optimization.

  Upstream commit: https://git.kernel.org/cgit/linux/kernel/git/davem
  /net-next.git/commit/?id=82fa3c776e5abba7ed6e4b4f4983d14731c37d6a

  This commit may imply other commits previously requested, for example
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452074

  Requested for all typical Hyper-V targets: 15.10, 15.04, 14.10, 14.04,
  14.04 HWE, 12.02, and 12.02 HWE

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

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


[Kernel-packages] [Bug 1519897] Re: [Hyper-V] hv: vmbus: Fix a host signaling bug

2016-01-20 Thread Joseph Salisbury
Some of the prereqs needed for Trusty and 12.04.5 would come in via bug
1454892.  We are just waiting for testing on that bug.   However, I can
still build a Trusty test kernel with the assumption that the prereqs
will come in via bug 1454892.

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

Title:
  [Hyper-V] hv: vmbus: Fix a host signaling bug

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-trusty package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Triaged
Status in linux-lts-trusty source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  The following fix has been submitted upstream, but has high enough
  severity that we would like early inclusion into the Ubuntu kernel.
  Please consider for wily, vivid, and trusty (and the HWE kernels for
  the same).

  Patch follows:

  Currently we have two policies for deciding when to signal the host:
  One based on the ring buffer state and the other based on what the VMBUS 
client driver wants to do. Consider the case when the client wants to 
explicitly control when to signal the host. In this case, if the client were to 
defer signaling, we will not be able to signal the host subsequently when the 
client does want to signal since the ring buffer state will prevent the 
signaling. Implement logic to have only one signaling policy in force for a 
given channel.

  Signed-off-by: K. Y. Srinivasan 
  Reviewed-by: Haiyang Zhang 
  Tested-by: Haiyang Zhang 
  Cc:  # v4.2+
  ---
   drivers/hv/channel.c   |   18 ++
   include/linux/hyperv.h |   12 
   2 files changed, 30 insertions(+), 0 deletions(-)

  diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c index 
77d2579..c6278c7 100644
  --- a/drivers/hv/channel.c
  +++ b/drivers/hv/channel.c
  @@ -653,10 +653,19 @@ int vmbus_sendpacket_ctl(struct vmbus_channel *channel, 
void *buffer,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  @@ -756,10 +765,19 @@ int vmbus_sendpacket_pagebuffer_ctl(struct 
vmbus_channel *channel,
     *on the ring. We will not signal if more data is
     *to be placed.
     *
  +  * Based on the channel signal state, we will decide
  +  * which signaling policy will be applied.
  +  *
     * If we cannot write to the ring-buffer; signal the host
     * even if we may not have written anything. This is a rare
     * enough condition that it should not matter.
     */
  +
  + if (channel->signal_state)
  + signal = true;
  + else
  + kick_q = true;
  +
    if (((ret == 0) && kick_q && signal) || (ret))
     vmbus_setevent(channel);

  diff --git a/include/linux/hyperv.h b/include/linux/hyperv.h index 
437c9c8..7b1af52 100644
  --- a/include/linux/hyperv.h
  +++ b/include/linux/hyperv.h
  @@ -756,8 +756,20 @@ struct vmbus_channel {
     * link up channels based on their CPU affinity.
     */
    struct list_head percpu_list;
  + /*
  +  * Host signaling policy: The default policy will be
  +  * based on the ring buffer state. We will also support
  +  * a policy where the client driver can have explicit
  +  * signaling control.
  +  */
  + bool signal_state;
   };

  +static inline void set_channel_signal_state(struct vmbus_channel *c,
  +bool state) {
  + c->signal_state = state;
  +}
  +
   static inline void set_channel_read_state(struct vmbus_channel *c, bool 
state)  {
    c->batched_reading = state;
  --
  1.7.4.1

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

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


[Kernel-packages] [Bug 1534345] Re: Ubuntu 15.10 Crashing Frequently on EC2 Instances w/ Enhanced Networking

2016-01-20 Thread Stefan Bader
Having written that down, it feels quite dangerous to use LIST_POISON in
combination with __hlist_del as the latter only protects against the
next pointer being NULL (indicating the last list entry). That
definitively breaks when trying to detach the same timer twice. Need to
think about whether this would have been ok before (with the double
linked lists)...

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

Title:
  Ubuntu 15.10 Crashing Frequently on EC2 Instances w/ Enhanced
  Networking

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Lots of details and history of the problem here:
  https://askubuntu.com/questions/710747/after-upgrading-
  to-15-10-from-15-04-ec2-webservers-have-become-very-unstable

  10 of my webservers have started crashing immediately following the
  15.10 upgrade. As far as what exactly defines a "crash", Instance
  Status Checks fail, and I can no longer SSH to the machine. Background
  daemons running on the system stop responding, and nothing is written
  to the logs.

  After weeks of working with the AWS team, I finally fixed a netconsole
  issue via "echo 7 > /proc/sys/kernel/printk" and got netconsole
  working properly, and finally have a trace:

  
  [21410.260077] general protection fault:  [#1] SMP
  [21410.261976] Modules linked in: isofs xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc 
iptable_filter ip_tables x_tables ppdev intel_rapl iosf_mbi xen_fbfront 
fb_sys_fops input_leds serio_raw i2c_piix4 parport_pc 8250_fintek parport 
mac_hid netconsole configfs autofs4 crct10dif_pclmul crc32_pclmul cirrus 
syscopyarea sysfillrect sysimgblt aesni_intel ttm aes_x86_64 drm_kms_helper lrw 
gf128mul glue_helper ablk_helper cryptd psmouse drm ixgbevf pata_acpi floppy
  [21410.264054] CPU: 0 PID: 26957 Comm: apache2 Not tainted 4.2.0-23-generic 
#28-Ubuntu
  [21410.264054] Hardware name: Xen HVM domU, BIOS 4.2.amazon 12/07/2015
  [21410.264054] task: 8803f9809b80 ti: 8803f999c000 task.ti: 
8803f999c000
  [21410.264054] RIP: 0010:[]  [] 
run_timer_softirq+0x116/0x2d0
  [21410.264054] RSP: :8803ff203e98  EFLAGS: 00010086
  [21410.264054] RAX: dead00200200 RBX: 8803ff20e9c0 RCX: 
8803ff203ec8
  [21410.264054] RDX: 8803ff203ec8 RSI: 00011fc0 RDI: 
8803ff20e9c0
  [21410.264054] RBP: 8803ff203f08 R08: a77a R09: 

  [21410.264054] R10: 0020 R11: 0004 R12: 
007c
  [21410.264054] R13: 8172aaf0 R14:  R15: 
8803af955be0
  [21410.264054] FS:  7fb0ce6e8780() GS:8803ff20() 
knlGS:
  [21410.264054] CS:  0010 DS:  ES:  CR0: 80050033
  [21410.264054] CR2: 7fb0ce51e130 CR3: 0003fb233000 CR4: 
001406f0
  [21410.264054] Stack:
  [21410.264054]  8803ff203eb8 8803ff20f5f8 8803ff20f3f8 
8803ff20f1f8
  [21410.264054]  8803ff20e9f8 8803af955b58 dead00200200 
f60fabc0
  [21410.264054]  00011fc0 0001 81c0b0c8 
0001
  [21410.264054] Call Trace:
  [21410.264054]  
  [21410.264054]  [] __do_softirq+0xf6/0x250
  [21410.264054]  [] irq_exit+0xa3/0xb0
  [21410.264054]  [] xen_evtchn_do_upcall+0x39/0x50
  [21410.264054]  [] xen_hvm_callback_vector+0x6b/0x70
  [21410.264054]  
  [21410.264054] Code: 81 e6 00 00 20 00 48 85 d2 48 89 45 b8 0f 85 30 01 00 00 
4c 89 7b 08 0f 1f 44 00 00 49 8b 07 49 8b 57 08 48 85 c0 48 89 02 74 04 <48> 89 
50 08 41 f6 47 2a 10 48 b8 00 02 20 00 00 00 ad de 49 c7
  [21410.264054] RIP  [] run_timer_softirq+0x116/0x2d0
  [21410.264054]  RSP 

  I don't have a vmcore at the moment, but I'm trying to get one from
  AWS and should have one in the next couple of days. This is happening
  frequently and repeatedly since I first upgraded to 15.10 on early
  December.

  
  ubuntu@xxx-web-xx:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 15.10
  Release:  15.10
  Codename: wily
  ubuntu@xxx-web-xx:~$ uname -a
  Linux xxx-web-xx 4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  ubuntu@xxx-web-xx:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-23-generic 4.2.0-23.28
  ProcVersionSignature: User Name 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 14 15:42 seq
   crw-rw 1 root audio 116, 33 Jan 14 15:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: 

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

2016-01-20 Thread bugproxy
--- Comment From cha...@us.ibm.com 2016-01-20 11:29 EDT---
BTW, Canonical please ignore the patch attached to the bug back in Nov 2015. 
The fix has been committed in linux-next (a link will follow) and the developer 
will backport the patch and supply a new  one for the LTS kernel if necessary.

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

Title:
  Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation
   
  Contact Information = Sachin Sant / ss...@in.ibm.com 
   
  ---uname output---
  3.19.0-18-generic
   
  ---Patches Installed---
  A patched powerpc-ibm-utils package is required
   
  Machine Type = POWER8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1) Using latest daily ISO install 14.04.02 as a Power VM guest
  2) Upgrade the kernel to 3.19 level (3.19.0-18-generic)
  3) Ensure ksh and powerpc-ibm-utils packages are installed.
  4) Download following DLPAR packages from 
http://ausgsa.ibm.com/projects/r/rsctdev/builds/muthu/rmuts006a/ppc64le/

  devices.chrp.base.servicerm_2.5.0.1-15111_ppc64el.deb
  dynamicrm_2.0.1-3_ppc64el.deb
  rsct.core_3.2.0.6-15111_ppc64el.deb
  rsct.core.utils_3.2.0.6-15111_ppc64el.deb
  src_3.2.0.6-15111_ppc64el.deb

  5) Install the packages.
  6) Perform a add memory operation via HMC
   
  Stack trace output:

  alp9 kernel: [44170.234662] [ cut here ]
  alp9 kernel: [44170.234667] WARNING: at 
/build/buildd/linux-lts-vivid-3.19.0/drivers/base/memory.c:200
  alp9 kernel: [44170.234668] Modules linked in: rpadlpar_io rpaphp pseries_rng 
rtc_generic
  alp9 kernel: [44170.234675] CPU: 2 PID: 1391 Comm: systemd-udevd Not tainted 
3.19.0-18-generic #18~14.04.1-Ubuntu
  alp9 kernel: [44170.234677] task: c003dbea7c80 ti: c003dbf1 
task.ti: c003dbf1
  Jun  4 19:44:47 alp9 kernel: [44170.234678] NIP: c0668f34 LR: 
c06699b0 CTR: 
  Jun  4 19:44:47 alp9 kernel: [44170.234680] REGS: c003dbf13910 TRAP: 0700 
  Not tainted  (3.19.0-18-generic)
  Jun  4 19:44:47 alp9 kernel: [44170.234680] MSR: 80029033 
  CR: 28042888  XER: 2000
  Jun  4 19:44:47 alp9 kernel: [44170.234686] CFAR: c0668ed8 SOFTE: 1 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR00: c06699b0 
c003dbf13b90 c144c760 0001 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR04: 0779 
0100 00078000 f1de4000 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR08: c13ac760 
0001 7790 003f 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR12: c172cb00 
ce831200 0100074a0010  
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR16: 10032230 
100311d0 3fffcb59bf20 0003 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR20: 100527f8 
100322b0 01312d00 0100074af7f0 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR24: 100322d0 
3fffcb59bf20 c003dbf13e00  
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR28: 1000 
 00077000 00077900 
  Jun  4 19:44:47 alp9 kernel: [44170.234707] NIP [c0668f34] 
pages_correctly_reserved+0x134/0x1c0
  Jun  4 19:44:47 alp9 kernel: [44170.234709] LR [c06699b0] 
memory_subsys_online+0x70/0x140
  Jun  4 19:44:47 alp9 kernel: [44170.234710] Call Trace:
  Jun  4 19:44:47 alp9 kernel: [44170.234711] [c003dbf13b90] 
[0006] 0x6 (unreliable)
  Jun  4 19:44:47 alp9 kernel: [44170.234714] [c003dbf13c00] 
[c06699b0] memory_subsys_online+0x70/0x140
  Jun  4 19:44:47 alp9 kernel: [44170.234716] [c003dbf13c40] 
[c06476f4] device_online+0xb4/0x120
  Jun  4 19:44:47 alp9 kernel: [44170.234718] [c003dbf13c80] 
[c066987c] store_mem_state+0x8c/0x150
  Jun  4 19:44:47 alp9 kernel: [44170.234721] [c003dbf13cc0] 
[c0643618] dev_attr_store+0x68/0xa0
  Jun  4 19:44:47 alp9 kernel: [44170.234724] [c003dbf13d00] 
[c035afd0] sysfs_kf_write+0x80/0xb0
  Jun  4 19:44:47 alp9 kernel: [44170.234726] [c003dbf13d40] 
[c0359f0c] kernfs_fop_write+0x18c/0x1f0
  Jun  4 19:44:47 alp9 kernel: [44170.234730] [c003dbf13d90] 
[c02b450c] vfs_write+0xdc/0x260
  Jun  4 19:44:47 alp9 kernel: [44170.234732] [c003dbf13de0] 
[c02b53bc] SyS_write+0x6c/0x110
  Jun  4 19:44:47 alp9 kernel: [44170.234735] [c003dbf13e30] 
[c0009258] system_call+0x38/0xd0
  Jun  4 19:44:47 alp9 kernel: [44170.234736] Instruction dump:
  Jun  4 19:44:47 alp9 kernel: [44170.234737] 419e0024 788a2428 

[Kernel-packages] [Bug 1536249] Re: XPS 13 9350: reboot fails with "Transaction is destructive" after resume from suspend

2016-01-20 Thread Robin Winslow
It says "not installed" 'cos I'm using a kernel from here:
http://askubuntu.com/questions/709794/dell-xps-13-9350-compatibility  -
to get my wifi to work. Does this make this bug invalid? Maybe I should
file a bug about wireless not working with the ubuntu kernel?

** Description changed:

  With my brand new Dell XPS 13 9350 and Ubuntu 15.10. The graphical
  "reboot" and "shut down" buttons don't do anything, and from the CLI I
  get:
  
  $ reboot
  Failed to execute operation: Transaction is destructive.
  
- I imagine it's associated with closing the lid to suspend because when I
- first start the system it reboots fine. It resumes fine when I open the
- lid in the sense that I can enter my password and continue to use
- Ubuntu, but it would make sense if there's something hanging about in
- the background. I don't know how to check this.
+ This only happens after resuming from suspend after the lid was closed.
+ Also, the touch screen no longer works after resuming.
  
  (I initially found this "wontfix" bug which describes the same problem: 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253)
- --- 
+ ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-18 (1 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  Tags:  wily
  Uname: Linux 4.3.0-wifitest-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

Title:
  XPS 13 9350: reboot fails with "Transaction is destructive" after
  resume from suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  With my brand new Dell XPS 13 9350 and Ubuntu 15.10. The graphical
  "reboot" and "shut down" buttons don't do anything, and from the CLI I
  get:

  $ reboot
  Failed to execute operation: Transaction is destructive.

  This only happens after resuming from suspend after the lid was
  closed. Also, the touch screen no longer works after resuming.

  (I initially found this "wontfix" bug which describes the same problem: 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1441253)
  ---
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-01-18 (1 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Package: linux (not installed)
  Tags:  wily
  Uname: Linux 4.3.0-wifitest-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1534345] Re: Ubuntu 15.10 Crashing Frequently on EC2 Instances w/ Enhanced Networking

2016-01-20 Thread Stefan Bader
Note that the following is not final statement but sharing some thoughts
to whoever else is looking at this report (and for me to remember). So
while I did find nothing that really looked odd in the xen-netfront code
I saw there was some change to the generic timer code:

commit 1dabbcec2c0a36fe43509d06499b9e512e70a028
  timer: Use hlist for the timer wheel hash buckets

That change was part of 4.2 but if it would be the cause I would expect
problems not only on AWS instances. But then it might just be that bare-
metal servers with a similarly high traffic tend to be upgraded much
less often anyway... Part of the change above seems to be some
exchange of special meaning of list pointer values. Not sure I grasp the
implications, yet. While using double linked lists before, the pointer
to the next element seemed to serve as pending indicator and the pointer
to the previous element was invalidated with a LIST_POISON2 value. Now
its the other way round. Referring to the detach_timer function which is
called from __run_timers via detached_expired_timer.

The crash happens at offset 0x116 in run_timer_softirq (thats 278
decimal). The disassembly of that function around there is:

   0x810e5c1e <+254>:   mov%r15,0x8(%rbx)
   0x810e5c22 <+258>:   nopl   0x0(%rax,%rax,1)
   // Guest this is __hlist_del(struct hlist_node *n)
   // rax = n->next
   0x810e5c27 <+263>:   mov(%r15),%rax
   // rdx = n->ppev
   0x810e5c2a <+266>:   mov0x8(%r15),%rdx
   0x810e5c2e <+270>:   test   %rax,%rax
   // *(n->pprev) = n->next
   0x810e5c31 <+273>:   mov%rax,(%rdx)
   // if (n->next == NULL) jump
   0x810e5c34 <+276>:   je 0x810e5c3a 

   // (n->next)->pprev = n->pprev (but n->next is LIST_POISON2 / invalid ptr)
   0x810e5c36 <+278>:   mov%rdx,0x8(%rax)
   0x810e5c3a <+282>:   testb  $0x10,0x2a(%r15)
   // here we seem back at detach_timer inlined and clear_pending assumed true
   // entry->next = LIST_POISON2 and entry->pprev = NULL
   0x810e5c3f <+287>:   movabs $0xdead00200200,%rax
   0x810e5c49 <+297>:   movq   $0x0,0x8(%r15)
   0x810e5c51 <+305>:   mov%rax,(%r15)

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

Title:
  Ubuntu 15.10 Crashing Frequently on EC2 Instances w/ Enhanced
  Networking

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Lots of details and history of the problem here:
  https://askubuntu.com/questions/710747/after-upgrading-
  to-15-10-from-15-04-ec2-webservers-have-become-very-unstable

  10 of my webservers have started crashing immediately following the
  15.10 upgrade. As far as what exactly defines a "crash", Instance
  Status Checks fail, and I can no longer SSH to the machine. Background
  daemons running on the system stop responding, and nothing is written
  to the logs.

  After weeks of working with the AWS team, I finally fixed a netconsole
  issue via "echo 7 > /proc/sys/kernel/printk" and got netconsole
  working properly, and finally have a trace:

  
  [21410.260077] general protection fault:  [#1] SMP
  [21410.261976] Modules linked in: isofs xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc 
iptable_filter ip_tables x_tables ppdev intel_rapl iosf_mbi xen_fbfront 
fb_sys_fops input_leds serio_raw i2c_piix4 parport_pc 8250_fintek parport 
mac_hid netconsole configfs autofs4 crct10dif_pclmul crc32_pclmul cirrus 
syscopyarea sysfillrect sysimgblt aesni_intel ttm aes_x86_64 drm_kms_helper lrw 
gf128mul glue_helper ablk_helper cryptd psmouse drm ixgbevf pata_acpi floppy
  [21410.264054] CPU: 0 PID: 26957 Comm: apache2 Not tainted 4.2.0-23-generic 
#28-Ubuntu
  [21410.264054] Hardware name: Xen HVM domU, BIOS 4.2.amazon 12/07/2015
  [21410.264054] task: 8803f9809b80 ti: 8803f999c000 task.ti: 
8803f999c000
  [21410.264054] RIP: 0010:[]  [] 
run_timer_softirq+0x116/0x2d0
  [21410.264054] RSP: :8803ff203e98  EFLAGS: 00010086
  [21410.264054] RAX: dead00200200 RBX: 8803ff20e9c0 RCX: 
8803ff203ec8
  [21410.264054] RDX: 8803ff203ec8 RSI: 00011fc0 RDI: 
8803ff20e9c0
  [21410.264054] RBP: 8803ff203f08 R08: a77a R09: 

  [21410.264054] R10: 0020 R11: 0004 R12: 
007c
  [21410.264054] R13: 8172aaf0 R14:  R15: 
8803af955be0
  [21410.264054] FS:  7fb0ce6e8780() GS:8803ff20() 
knlGS:
  [21410.264054] CS:  0010 DS:  ES:  CR0: 80050033
  [21410.264054] CR2: 7fb0ce51e130 CR3: 0003fb233000 CR4: 
001406f0
  [21410.264054] Stack:
  [21410.264054]  8803ff203eb8 8803ff20f5f8 

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

2016-01-20 Thread Brad Figg
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1536245

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

Title:
  s390x kernel image needs weightwatchers

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer-
  amd64/current/images/cdrom/vmlinuz

  is 6.6M

  http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-
  s390x/current/images/generic/kernel.debian

  is 12M

  Yet, s390x has much less drivers. I would have expected it to be
  slimmer than amd64.

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

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


[Kernel-packages] [Bug 1463654] Re: Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation

2016-01-20 Thread Tim Gardner
Yep, I noticed the patch was up to v4 so I thought I'd wait until it was
closer to being merged.

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

Title:
  Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation
   
  Contact Information = Sachin Sant / ss...@in.ibm.com 
   
  ---uname output---
  3.19.0-18-generic
   
  ---Patches Installed---
  A patched powerpc-ibm-utils package is required
   
  Machine Type = POWER8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1) Using latest daily ISO install 14.04.02 as a Power VM guest
  2) Upgrade the kernel to 3.19 level (3.19.0-18-generic)
  3) Ensure ksh and powerpc-ibm-utils packages are installed.
  4) Download following DLPAR packages from 
http://ausgsa.ibm.com/projects/r/rsctdev/builds/muthu/rmuts006a/ppc64le/

  devices.chrp.base.servicerm_2.5.0.1-15111_ppc64el.deb
  dynamicrm_2.0.1-3_ppc64el.deb
  rsct.core_3.2.0.6-15111_ppc64el.deb
  rsct.core.utils_3.2.0.6-15111_ppc64el.deb
  src_3.2.0.6-15111_ppc64el.deb

  5) Install the packages.
  6) Perform a add memory operation via HMC
   
  Stack trace output:

  alp9 kernel: [44170.234662] [ cut here ]
  alp9 kernel: [44170.234667] WARNING: at 
/build/buildd/linux-lts-vivid-3.19.0/drivers/base/memory.c:200
  alp9 kernel: [44170.234668] Modules linked in: rpadlpar_io rpaphp pseries_rng 
rtc_generic
  alp9 kernel: [44170.234675] CPU: 2 PID: 1391 Comm: systemd-udevd Not tainted 
3.19.0-18-generic #18~14.04.1-Ubuntu
  alp9 kernel: [44170.234677] task: c003dbea7c80 ti: c003dbf1 
task.ti: c003dbf1
  Jun  4 19:44:47 alp9 kernel: [44170.234678] NIP: c0668f34 LR: 
c06699b0 CTR: 
  Jun  4 19:44:47 alp9 kernel: [44170.234680] REGS: c003dbf13910 TRAP: 0700 
  Not tainted  (3.19.0-18-generic)
  Jun  4 19:44:47 alp9 kernel: [44170.234680] MSR: 80029033 
  CR: 28042888  XER: 2000
  Jun  4 19:44:47 alp9 kernel: [44170.234686] CFAR: c0668ed8 SOFTE: 1 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR00: c06699b0 
c003dbf13b90 c144c760 0001 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR04: 0779 
0100 00078000 f1de4000 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR08: c13ac760 
0001 7790 003f 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR12: c172cb00 
ce831200 0100074a0010  
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR16: 10032230 
100311d0 3fffcb59bf20 0003 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR20: 100527f8 
100322b0 01312d00 0100074af7f0 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR24: 100322d0 
3fffcb59bf20 c003dbf13e00  
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR28: 1000 
 00077000 00077900 
  Jun  4 19:44:47 alp9 kernel: [44170.234707] NIP [c0668f34] 
pages_correctly_reserved+0x134/0x1c0
  Jun  4 19:44:47 alp9 kernel: [44170.234709] LR [c06699b0] 
memory_subsys_online+0x70/0x140
  Jun  4 19:44:47 alp9 kernel: [44170.234710] Call Trace:
  Jun  4 19:44:47 alp9 kernel: [44170.234711] [c003dbf13b90] 
[0006] 0x6 (unreliable)
  Jun  4 19:44:47 alp9 kernel: [44170.234714] [c003dbf13c00] 
[c06699b0] memory_subsys_online+0x70/0x140
  Jun  4 19:44:47 alp9 kernel: [44170.234716] [c003dbf13c40] 
[c06476f4] device_online+0xb4/0x120
  Jun  4 19:44:47 alp9 kernel: [44170.234718] [c003dbf13c80] 
[c066987c] store_mem_state+0x8c/0x150
  Jun  4 19:44:47 alp9 kernel: [44170.234721] [c003dbf13cc0] 
[c0643618] dev_attr_store+0x68/0xa0
  Jun  4 19:44:47 alp9 kernel: [44170.234724] [c003dbf13d00] 
[c035afd0] sysfs_kf_write+0x80/0xb0
  Jun  4 19:44:47 alp9 kernel: [44170.234726] [c003dbf13d40] 
[c0359f0c] kernfs_fop_write+0x18c/0x1f0
  Jun  4 19:44:47 alp9 kernel: [44170.234730] [c003dbf13d90] 
[c02b450c] vfs_write+0xdc/0x260
  Jun  4 19:44:47 alp9 kernel: [44170.234732] [c003dbf13de0] 
[c02b53bc] SyS_write+0x6c/0x110
  Jun  4 19:44:47 alp9 kernel: [44170.234735] [c003dbf13e30] 
[c0009258] system_call+0x38/0xd0
  Jun  4 19:44:47 alp9 kernel: [44170.234736] Instruction dump:
  Jun  4 19:44:47 alp9 kernel: [44170.234737] 419e0024 788a2428 7d095214 
2fa8 41de0014 7d29502a 38e74000 7928ffe3 
  Jun  4 19:44:47 alp9 kernel: [44170.234740] 4082ff7c 3d02fff6 892808e3 
69290001 <0b09> 2fa9 40de0068 3860 
  Jun  4 19:44:47 alp9 kernel: 

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

2016-01-20 Thread bugproxy
--- Comment From allen...@us.ibm.com 2016-01-20 12:03 EDT---
The patch (drivers/base/memory.c: fix kernel warning during memory hotplug on 
ppc64) is merged into the 4.4.0 kernel and can be seen here:
https://github.com/torvalds/linux/commit/cb5490a5eea415106d7438df440da5fb1e17318d

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

Title:
  Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation

Status in linux package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation
   
  Contact Information = Sachin Sant / ss...@in.ibm.com 
   
  ---uname output---
  3.19.0-18-generic
   
  ---Patches Installed---
  A patched powerpc-ibm-utils package is required
   
  Machine Type = POWER8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1) Using latest daily ISO install 14.04.02 as a Power VM guest
  2) Upgrade the kernel to 3.19 level (3.19.0-18-generic)
  3) Ensure ksh and powerpc-ibm-utils packages are installed.
  4) Download following DLPAR packages from 
http://ausgsa.ibm.com/projects/r/rsctdev/builds/muthu/rmuts006a/ppc64le/

  devices.chrp.base.servicerm_2.5.0.1-15111_ppc64el.deb
  dynamicrm_2.0.1-3_ppc64el.deb
  rsct.core_3.2.0.6-15111_ppc64el.deb
  rsct.core.utils_3.2.0.6-15111_ppc64el.deb
  src_3.2.0.6-15111_ppc64el.deb

  5) Install the packages.
  6) Perform a add memory operation via HMC
   
  Stack trace output:

  alp9 kernel: [44170.234662] [ cut here ]
  alp9 kernel: [44170.234667] WARNING: at 
/build/buildd/linux-lts-vivid-3.19.0/drivers/base/memory.c:200
  alp9 kernel: [44170.234668] Modules linked in: rpadlpar_io rpaphp pseries_rng 
rtc_generic
  alp9 kernel: [44170.234675] CPU: 2 PID: 1391 Comm: systemd-udevd Not tainted 
3.19.0-18-generic #18~14.04.1-Ubuntu
  alp9 kernel: [44170.234677] task: c003dbea7c80 ti: c003dbf1 
task.ti: c003dbf1
  Jun  4 19:44:47 alp9 kernel: [44170.234678] NIP: c0668f34 LR: 
c06699b0 CTR: 
  Jun  4 19:44:47 alp9 kernel: [44170.234680] REGS: c003dbf13910 TRAP: 0700 
  Not tainted  (3.19.0-18-generic)
  Jun  4 19:44:47 alp9 kernel: [44170.234680] MSR: 80029033 
  CR: 28042888  XER: 2000
  Jun  4 19:44:47 alp9 kernel: [44170.234686] CFAR: c0668ed8 SOFTE: 1 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR00: c06699b0 
c003dbf13b90 c144c760 0001 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR04: 0779 
0100 00078000 f1de4000 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR08: c13ac760 
0001 7790 003f 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR12: c172cb00 
ce831200 0100074a0010  
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR16: 10032230 
100311d0 3fffcb59bf20 0003 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR20: 100527f8 
100322b0 01312d00 0100074af7f0 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR24: 100322d0 
3fffcb59bf20 c003dbf13e00  
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR28: 1000 
 00077000 00077900 
  Jun  4 19:44:47 alp9 kernel: [44170.234707] NIP [c0668f34] 
pages_correctly_reserved+0x134/0x1c0
  Jun  4 19:44:47 alp9 kernel: [44170.234709] LR [c06699b0] 
memory_subsys_online+0x70/0x140
  Jun  4 19:44:47 alp9 kernel: [44170.234710] Call Trace:
  Jun  4 19:44:47 alp9 kernel: [44170.234711] [c003dbf13b90] 
[0006] 0x6 (unreliable)
  Jun  4 19:44:47 alp9 kernel: [44170.234714] [c003dbf13c00] 
[c06699b0] memory_subsys_online+0x70/0x140
  Jun  4 19:44:47 alp9 kernel: [44170.234716] [c003dbf13c40] 
[c06476f4] device_online+0xb4/0x120
  Jun  4 19:44:47 alp9 kernel: [44170.234718] [c003dbf13c80] 
[c066987c] store_mem_state+0x8c/0x150
  Jun  4 19:44:47 alp9 kernel: [44170.234721] [c003dbf13cc0] 
[c0643618] dev_attr_store+0x68/0xa0
  Jun  4 19:44:47 alp9 kernel: [44170.234724] [c003dbf13d00] 
[c035afd0] sysfs_kf_write+0x80/0xb0
  Jun  4 19:44:47 alp9 kernel: [44170.234726] [c003dbf13d40] 
[c0359f0c] kernfs_fop_write+0x18c/0x1f0
  Jun  4 19:44:47 alp9 kernel: [44170.234730] [c003dbf13d90] 
[c02b450c] vfs_write+0xdc/0x260
  Jun  4 19:44:47 alp9 kernel: [44170.234732] [c003dbf13de0] 
[c02b53bc] SyS_write+0x6c/0x110
  Jun  4 19:44:47 alp9 kernel: [44170.234735] [c003dbf13e30] 
[c0009258] system_call+0x38/0xd0
  Jun  4 19:44:47 alp9 kernel: [44170.234736] Instruction dump:
  Jun  4 19:44:47 alp9 kernel: [44170.234737] 419e0024 788a2428 7d095214 

[Kernel-packages] [Bug 1492764] Re: [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled (expected 1, found 0)

2016-01-20 Thread DG
I started getting the error today with the latest patch.  I've sent in a
bug (via "ubuntu-bug linux") but wanted to add that I was able to get
rid of it* by running "sudo dpkg-reconfigure lightdm" in recovery mode.
I was already using lightdm so I don't know why that fixed the problem.

(* - It's possible it was just a coincidence but I tried multiple times
to reboot and failed every time with the drm error until I reconfigured
lightdm and it started the first time.  It's the only change I tried.)

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

Title:
  [drm:intel_pipe_config_compare [i915]] *ERROR* mismatch in ips_enabled
  (expected 1, found 0)

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  System: Kubuntu 15.10

  Since kernel version 4.2 I have a few of this errors:

  Sep 06 16:16:35 benediktZ50-70 kernel: [drm:intel_pipe_config_compare [i915]] 
*ERROR* mismatch in ips_enabled (expected 1, found 0)
  Sep 06 16:16:35 benediktZ50-70 kernel: [ cut here ]
  Sep 06 16:16:35 benediktZ50-70 kernel: WARNING: CPU: 0 PID: 187 at 
/build/linux-4dBub_/linux-4.2.0/drivers/gpu/drm/i915/intel_display.c:12324 
check_crtc_state+0x2c5/0x440 [i915]()
  Sep 06 16:16:35 benediktZ50-70 kernel: pipe state doesn't match!
  Sep 06 16:16:35 benediktZ50-70 kernel: Modules linked in: rtsx_usb_sdmmc 
rtsx_usb i915 i2c_algo_bit drm_kms_helper psmouse ahci drm libahci r8169 mii 
sdhci_acpi video sdhci i2c_hid hid
  Sep 06 16:16:35 benediktZ50-70 kernel: CPU: 0 PID: 187 Comm: plymouthd 
Tainted: GW   4.2.0-7-generic #7-Ubuntu
  Sep 06 16:16:35 benediktZ50-70 kernel: Hardware name: LENOVO 20354/Lancer 
5A5, BIOS 9BCN91WW 07/21/2015
  Sep 06 16:16:35 benediktZ50-70 kernel:  c023f1e8 8802413277e8 
817b0465 
  Sep 06 16:16:35 benediktZ50-70 kernel:  880241327838 880241327828 
81076536 880241327858
  Sep 06 16:16:35 benediktZ50-70 kernel:  8802413278c0 880241152000 
0001 880241152350
  Sep 06 16:16:35 benediktZ50-70 kernel: Call Trace:
  Sep 06 16:16:35 benediktZ50-70 kernel:  [] 
dump_stack+0x45/0x57
  Sep 06 16:16:35 benediktZ50-70 kernel:  [] 
warn_slowpath_common+0x86/0xc0
  Sep 06 16:16:35 benediktZ50-70 kernel:  [] 
warn_slowpath_fmt+0x46/0x50
  Sep 06 16:16:35 benediktZ50-70 kernel:  [] ? 
intel_pipe_config_compare+0xb31/0xc60 [i915]
  Sep 06 16:16:35 benediktZ50-70 kernel:  [] 
check_crtc_state+0x2c5/0x440 [i915]
  Sep 06 16:16:35 benediktZ50-70 kernel:  [] 
intel_modeset_check_state+0x20e/0x6b0 [i915]
  Sep 06 16:16:35 benediktZ50-70 kernel:  [] 
intel_crtc_set_config+0x4c7/0x580 [i915]
  Sep 06 16:16:35 benediktZ50-70 kernel:  [] ? 
drm_mode_create+0x25/0x60 [drm]
  Sep 06 16:16:35 benediktZ50-70 kernel:  [] 
drm_mode_set_config_internal+0x66/0x100 [drm]
  Sep 06 16:16:35 benediktZ50-70 kernel:  [] 
drm_mode_setcrtc+0x3a8/0x4c0 [drm]
  Sep 06 16:16:35 benediktZ50-70 kernel:  [] 
drm_ioctl+0x125/0x610 [drm]
  Sep 06 16:16:35 benediktZ50-70 kernel:  [] ? 
drm_mode_setplane+0x1b0/0x1b0 [drm]
  Sep 06 16:16:35 benediktZ50-70 kernel:  [] 
do_vfs_ioctl+0x285/0x470
  Sep 06 16:16:35 benediktZ50-70 kernel:  [] ? 
do_munmap+0x349/0x480
  Sep 06 16:16:35 benediktZ50-70 kernel:  [] 
SyS_ioctl+0x79/0x90
  Sep 06 16:16:35 benediktZ50-70 kernel:  [] 
entry_SYSCALL_64_fastpath+0x16/0x75
  Sep 06 16:16:35 benediktZ50-70 kernel: ---[ end trace 724377a3c01e4270 ]---

  
  I will check next week if these errors have any impact on my system.

  This is a Nvidia Optimus System with the Intel graphic card activated
  by default.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-7-generic 4.2.0-7.7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  Uname: Linux 4.2.0-7-generic x86_64
  ApportVersion: 2.18-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  benedikt   1550 F pulseaudio
   /dev/snd/controlC1:  benedikt   1550 F pulseaudio
  CurrentDesktop: KDE
  Date: Sun Sep  6 16:22:48 2015
  HibernationDevice: UUID=3383b02e-b89c-462c-903a-cb936e81b2bf
  InstallationDate: Installed on 2014-12-21 (259 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141218)
  MachineType: LENOVO 20354
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=b549945a-67ac-4d14-849c-b54e561d47cc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-7-generic N/A
   linux-backports-modules-4.2.0-7-generic  N/A
   linux-firmware   1.147
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/21/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN91WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 

[Kernel-packages] [Bug 1516215] Re: kernel 4.x has issues with lite-on sata controller in dell xps 13 (2015)

2016-01-20 Thread Christopher M. Penalver
Carolin Latze:
>"I did not see a freeze during boot yet."

Staying focused to this, how many boots did you attempt? We would want
to ensure this is robust across a reasonable number of boots so it's not
improved but less intermittent.

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

Title:
   kernel 4.x has issues with lite-on sata controller in dell xps 13
  (2015)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Dell XPS 13 (2015) which has a Lite-On Sata controller:
  03:00.0 SATA controller: Lite-On Technology Corporation Device 0224 (rev 10)

  Right from the beginning, I have issues with that one under Linux (not
  Windows). It might happen that the notebook just dies (loosing its
  SSD), or it might not even boot. Whenever it does not boot, it usually
  stops with a message around "job 1 of 12 ..." (I don't find them in
  any logs ). Sometimes when I boot into Windows and then immediately
  reboot into Linux it works. It usually helps to boot a 3.19.x kernel,
  although even that one can have the same issues (although way less
  than 4.x).

  The system almost always crashes completely when I run the dump tool.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-18-generic 4.2.0-18.22
  ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3
  Uname: Linux 4.2.0-18-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  latze  1599 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Nov 14 09:29:04 2015
  HibernationDevice: RESUME=UUID=b8662265-a1f0-487e-9d85-2731c765b3eb
  InstallationDate: Installed on 2015-08-23 (82 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:5682 Realtek Semiconductor Corp.
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
   Bus 001 Device 002: ID 8087:0a2a Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic.efi.signed 
root=UUID=9e67912b-c59e-47ac-b2f1-3ef39e3d38fb ro debug
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmware1.149.1
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-31 (13 days ago)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1536280] Re: domain shutdown fails for libvirt/lxc

2016-01-20 Thread Serge Hallyn
marking as affecting kernel given the description.


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

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

Title:
  domain shutdown fails for libvirt/lxc

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

Bug description:
  There appears to be a regression from kernel 3.13.0-58-generic where
  virDomainShutdown no longer brings the domain to shutoff state in
  newer Ubuntu kernels.

  Details:
  

  OS:
  ---
  $ lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  Kernel:
  ---
  $ uname -a
  Linux thomas-devstack01 3.13.0-76-generic #120-Ubuntu SMP Mon Jan 18 15:59:10 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  Package:
  
  $ dpkg -l | grep libvirt-bin
  ii  libvirt-bin  1.2.2-0ubuntu13.1.16 
 amd64programs for the libvirt library

  Libvirt virt driver: LXC

  Issue seen from console:
  

  $ sudo virsh -c lxc:/// shutdown instance-0001
  error: Failed to shutdown domain instance-0001
  error: internal error: Child process (1304) unexpected exit status 1

  libvirtd logs:
  --

  2016-01-20 16:42:38.267+: 14089: debug : virDomainShutdown:3094 : 
dom=0x7f89d0004a70, (VM: name=instance-0001, 
uuid=e342beb8-8666-4a47-8b40-5844e866e1f7)
  2016-01-20 16:42:38.269+: 14089: error : virProcessWait:191 : internal 
error: Child process (1304) unexpected exit status 1

  nova-compute logs
  -
  *Note*: From when attempting to do a nova stop  in devstack

  
  2016-01-20 16:37:35.244 ERROR oslo_messaging.rpc.dispatcher 
[req-dd0fe69c-9bd2-4de5-b59b-77619699d69b demo demo] Exception during message 
handling: internal error: Child process
  (631) unexpected exit status 1
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher Traceback (most 
recent call last):
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
143, in _dispatch_and_reply
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
executor_callback))
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
189, in _dispatch
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
executor_callback)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
130, in _do_dispatch
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher result = 
func(ctxt, **new_args)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/exception.py", line 110, in wrapped
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher payload)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204, in 
__exit__
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/exception.py", line 89, in wrapped
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher return 
f(self, context, *args, **kw)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 357, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
LOG.warning(msg, e, instance=instance)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204, in 
__exit__
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 330, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher return 
function(self, context, *args, **kwargs)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 407, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher return 
function(self, context, *args, **kwargs)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 385, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
kwargs['instance'], e, sys.exc_info())
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 

[Kernel-packages] [Bug 1536280] Re: domain shutdown fails for libvirt/lxc

2016-01-20 Thread Thomas Maddox
** Description changed:

  There appears to be a regression from kernel 3.13.0-58-generic where
  virDomainShutdown no longer brings the domain to shutoff state in newer
  Ubuntu kernels.
  
  Details:
+ 
  
  OS:
+ ---
  $ lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  
  Kernel:
+ ---
  $ uname -a
  Linux thomas-devstack01 3.13.0-76-generic #120-Ubuntu SMP Mon Jan 18 15:59:10 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
  
  Package:
+ 
  $ dpkg -l | grep libvirt-bin
  ii  libvirt-bin  1.2.2-0ubuntu13.1.16 
 amd64programs for the libvirt library
  
- 
- Kernel: 3.13.0-76-generic
- Libvirt Version: 1.2.2
  Libvirt virt driver: LXC
  
- 
  Issue seen from console:
+ 
  
  $ sudo virsh -c lxc:/// shutdown instance-0001
  error: Failed to shutdown domain instance-0001
  error: internal error: Child process (1304) unexpected exit status 1
  
- 
  libvirtd logs:
+ --
  
  2016-01-20 16:42:38.267+: 14089: debug : virDomainShutdown:3094 : 
dom=0x7f89d0004a70, (VM: name=instance-0001, 
uuid=e342beb8-8666-4a47-8b40-5844e866e1f7)
  2016-01-20 16:42:38.269+: 14089: error : virProcessWait:191 : internal 
error: Child process (1304) unexpected exit status 1
  
- 
- nova-compute logs (when attempting to do a nova stop  in devstack):
+ nova-compute logs
+ - 
+ *Note*: From when attempting to do a nova stop  in devstack
  
  2016-01-20 16:37:35.244 ERROR oslo_messaging.rpc.dispatcher 
[req-dd0fe69c-9bd2-4de5-b59b-77619699d69b demo demo] Exception during message 
handling: internal error: Child process
  (631) unexpected exit status 1
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher Traceback (most 
recent call last):
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
143, in _dispatch_and_reply
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
executor_callback))
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
189, in _dispatch
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
executor_callback)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
130, in _do_dispatch
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher result = 
func(ctxt, **new_args)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/exception.py", line 110, in wrapped
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher payload)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204, in 
__exit__
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/exception.py", line 89, in wrapped
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher return 
f(self, context, *args, **kw)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 357, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
LOG.warning(msg, e, instance=instance)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204, in 
__exit__
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 330, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher return 
function(self, context, *args, **kwargs)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 407, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher return 
function(self, context, *args, **kwargs)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 385, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
kwargs['instance'], e, sys.exc_info())
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204, in 
__exit__
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 373, in 

[Kernel-packages] [Bug 1536327] [NEW] lenovo g50-30 linus freeze bug revisited

2016-01-20 Thread Marko Lazic
Public bug reported:

On behalf of this bug report

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511019

The administrator closed discussion. After upgrading BIOS to 48. Bug
still remains.

I am using kernel 4.2.0-26-generic. The best one and most reliable that
i found was kernel 4.1.13-realtime however it have its wifi bugs and
system freezes as well.

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

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

Title:
  lenovo g50-30 linus freeze bug revisited

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On behalf of this bug report

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511019

  The administrator closed discussion. After upgrading BIOS to 48. Bug
  still remains.

  I am using kernel 4.2.0-26-generic. The best one and most reliable
  that i found was kernel 4.1.13-realtime however it have its wifi bugs
  and system freezes as well.

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

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


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

2016-01-20 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/1535565

Title:
  i have wifi connnection problem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  i have a problem in connection to internet,

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: 
boot/vmlinuz-3.13.0-24-generic]
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  acer   1650 F pulseaudio
acer   3994 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 19 13:52:31 2016
  HibernationDevice: RESUME=UUID=3727c696-a786-465f-a2b0-4a2052cdad14
  InstallationDate: Installed on 2016-01-05 (13 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Acer Aspire V3-471
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=UUID=b0772e3e-4f65-444d-b1c5-46a188be95a0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA40_HC
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.24:bd10/11/2012:svnAcer:pnAspireV3-471:pvrV1.24:rvnAcer:rnVA40_HC:rvrType2-BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire V3-471
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

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

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


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

2016-01-20 Thread Brad Figg
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1536280

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

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

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

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

** Tags added: trusty

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

Title:
  domain shutdown fails for libvirt/lxc

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

Bug description:
  There appears to be a regression from kernel 3.13.0-58-generic where
  virDomainShutdown no longer brings the domain to shutoff state in
  newer Ubuntu kernels.

  Details:
  

  OS:
  ---
  $ lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  Kernel:
  ---
  $ uname -a
  Linux thomas-devstack01 3.13.0-76-generic #120-Ubuntu SMP Mon Jan 18 15:59:10 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

  Package:
  
  $ dpkg -l | grep libvirt-bin
  ii  libvirt-bin  1.2.2-0ubuntu13.1.16 
 amd64programs for the libvirt library

  Libvirt virt driver: LXC

  Issue seen from console:
  

  $ sudo virsh -c lxc:/// shutdown instance-0001
  error: Failed to shutdown domain instance-0001
  error: internal error: Child process (1304) unexpected exit status 1

  libvirtd logs:
  --

  2016-01-20 16:42:38.267+: 14089: debug : virDomainShutdown:3094 : 
dom=0x7f89d0004a70, (VM: name=instance-0001, 
uuid=e342beb8-8666-4a47-8b40-5844e866e1f7)
  2016-01-20 16:42:38.269+: 14089: error : virProcessWait:191 : internal 
error: Child process (1304) unexpected exit status 1

  nova-compute logs
  -
  *Note*: From when attempting to do a nova stop  in devstack

  
  2016-01-20 16:37:35.244 ERROR oslo_messaging.rpc.dispatcher 
[req-dd0fe69c-9bd2-4de5-b59b-77619699d69b demo demo] Exception during message 
handling: internal error: Child process
  (631) unexpected exit status 1
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher Traceback (most 
recent call last):
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
143, in _dispatch_and_reply
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
executor_callback))
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
189, in _dispatch
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
executor_callback)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
130, in _do_dispatch
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher result = 
func(ctxt, **new_args)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/exception.py", line 110, in wrapped
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher payload)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204, in 
__exit__
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/exception.py", line 89, in wrapped
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher return 
f(self, context, *args, **kw)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 357, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
LOG.warning(msg, e, instance=instance)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204, in 
__exit__
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 330, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher return 
function(self, context, *args, **kwargs)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 407, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher return 
function(self, 

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

2016-01-20 Thread Brad Figg
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1536327

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

Title:
  lenovo g50-30 linus freeze bug revisited

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On behalf of this bug report

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511019

  The administrator closed discussion. After upgrading BIOS to 48. Bug
  still remains.

  I am using kernel 4.2.0-26-generic. The best one and most reliable
  that i found was kernel 4.1.13-realtime however it have its wifi bugs
  and system freezes as well.

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

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


[Kernel-packages] [Bug 1536280] Re: domain shutdown fails for libvirt/lxc

2016-01-20 Thread Thomas Maddox
** Description changed:

  There appears to be a regression from kernel 3.13.0-58-generic where
  virDomainShutdown no longer brings the domain to shutoff state in newer
  Ubuntu kernels.
  
  Details:
  
  
  OS:
  ---
  $ lsb_release -rd
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  
  Kernel:
  ---
  $ uname -a
  Linux thomas-devstack01 3.13.0-76-generic #120-Ubuntu SMP Mon Jan 18 15:59:10 
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
  
  Package:
  
  $ dpkg -l | grep libvirt-bin
  ii  libvirt-bin  1.2.2-0ubuntu13.1.16 
 amd64programs for the libvirt library
  
  Libvirt virt driver: LXC
  
  Issue seen from console:
  
  
  $ sudo virsh -c lxc:/// shutdown instance-0001
  error: Failed to shutdown domain instance-0001
  error: internal error: Child process (1304) unexpected exit status 1
  
  libvirtd logs:
  --
  
  2016-01-20 16:42:38.267+: 14089: debug : virDomainShutdown:3094 : 
dom=0x7f89d0004a70, (VM: name=instance-0001, 
uuid=e342beb8-8666-4a47-8b40-5844e866e1f7)
  2016-01-20 16:42:38.269+: 14089: error : virProcessWait:191 : internal 
error: Child process (1304) unexpected exit status 1
  
  nova-compute logs
  -
  *Note*: From when attempting to do a nova stop  in devstack
  
- ```
+ 
  2016-01-20 16:37:35.244 ERROR oslo_messaging.rpc.dispatcher 
[req-dd0fe69c-9bd2-4de5-b59b-77619699d69b demo demo] Exception during message 
handling: internal error: Child process
  (631) unexpected exit status 1
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher Traceback (most 
recent call last):
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
143, in _dispatch_and_reply
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
executor_callback))
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
189, in _dispatch
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
executor_callback)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_messaging/rpc/dispatcher.py", line 
130, in _do_dispatch
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher result = 
func(ctxt, **new_args)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/exception.py", line 110, in wrapped
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher payload)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204, in 
__exit__
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/exception.py", line 89, in wrapped
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher return 
f(self, context, *args, **kw)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 357, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
LOG.warning(msg, e, instance=instance)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204, in 
__exit__
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 330, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher return 
function(self, context, *args, **kwargs)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 407, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher return 
function(self, context, *args, **kwargs)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 385, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
kwargs['instance'], e, sys.exc_info())
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/usr/local/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 204, in 
__exit__
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher 
six.reraise(self.type_, self.value, self.tb)
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher   File 
"/opt/stack/nova/nova/compute/manager.py", line 373, in decorated_function
  2016-01-20 16:37:35.244 TRACE oslo_messaging.rpc.dispatcher return 
function(self, context, *args, **kwargs)
 

[Kernel-packages] [Bug 1463654] Re: Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation

2016-01-20 Thread Tim Gardner
Indeed it has been merged, albeit with a slightly different commit
subject (which is why I did not find it). I'm marking this fix released
for Xenial since the v4.4 based kernel will be uploaded real soon now.

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: Triaged

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

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

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

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

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

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

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

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

Title:
  Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation

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

Bug description:
  ---Problem Description---
  Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation
   
  Contact Information = Sachin Sant / ss...@in.ibm.com 
   
  ---uname output---
  3.19.0-18-generic
   
  ---Patches Installed---
  A patched powerpc-ibm-utils package is required
   
  Machine Type = POWER8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1) Using latest daily ISO install 14.04.02 as a Power VM guest
  2) Upgrade the kernel to 3.19 level (3.19.0-18-generic)
  3) Ensure ksh and powerpc-ibm-utils packages are installed.
  4) Download following DLPAR packages from 
http://ausgsa.ibm.com/projects/r/rsctdev/builds/muthu/rmuts006a/ppc64le/

  devices.chrp.base.servicerm_2.5.0.1-15111_ppc64el.deb
  dynamicrm_2.0.1-3_ppc64el.deb
  rsct.core_3.2.0.6-15111_ppc64el.deb
  rsct.core.utils_3.2.0.6-15111_ppc64el.deb
  src_3.2.0.6-15111_ppc64el.deb

  5) Install the packages.
  6) Perform a add memory operation via HMC
   
  Stack trace output:

  alp9 kernel: [44170.234662] [ cut here ]
  alp9 kernel: [44170.234667] WARNING: at 
/build/buildd/linux-lts-vivid-3.19.0/drivers/base/memory.c:200
  alp9 kernel: [44170.234668] Modules linked in: rpadlpar_io rpaphp pseries_rng 
rtc_generic
  alp9 kernel: [44170.234675] CPU: 2 PID: 1391 Comm: systemd-udevd Not tainted 
3.19.0-18-generic #18~14.04.1-Ubuntu
  alp9 kernel: [44170.234677] task: c003dbea7c80 ti: c003dbf1 
task.ti: c003dbf1
  Jun  4 19:44:47 alp9 kernel: [44170.234678] NIP: c0668f34 LR: 
c06699b0 CTR: 
  Jun  4 19:44:47 alp9 kernel: [44170.234680] REGS: c003dbf13910 TRAP: 0700 
  Not tainted  (3.19.0-18-generic)
  Jun  4 19:44:47 alp9 kernel: [44170.234680] MSR: 80029033 
  CR: 28042888  XER: 2000
  Jun  4 19:44:47 alp9 kernel: [44170.234686] CFAR: c0668ed8 SOFTE: 1 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR00: c06699b0 
c003dbf13b90 c144c760 0001 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR04: 0779 
0100 00078000 f1de4000 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR08: c13ac760 
0001 7790 003f 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR12: c172cb00 
ce831200 0100074a0010  
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR16: 10032230 
100311d0 3fffcb59bf20 0003 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR20: 100527f8 
100322b0 01312d00 0100074af7f0 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR24: 100322d0 
3fffcb59bf20 c003dbf13e00  
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR28: 1000 
 00077000 00077900 
  Jun  4 19:44:47 alp9 kernel: [44170.234707] NIP [c0668f34] 
pages_correctly_reserved+0x134/0x1c0
  Jun  4 19:44:47 alp9 kernel: [44170.234709] LR [c06699b0] 
memory_subsys_online+0x70/0x140
  Jun  4 19:44:47 alp9 kernel: [44170.234710] Call Trace:
  Jun  4 19:44:47 alp9 kernel: [44170.234711] [c003dbf13b90] 
[0006] 0x6 (unreliable)
  Jun  4 19:44:47 alp9 kernel: [44170.234714] [c003dbf13c00] 
[c06699b0] memory_subsys_online+0x70/0x140
  Jun  4 19:44:47 alp9 kernel: [44170.234716] [c003dbf13c40] 
[c06476f4] 

[Kernel-packages] [Bug 1536038] Re: [Asus E403SA] ELAN1000 touchpad freezes after minutes to hours

2016-01-20 Thread Christopher M. Penalver
Kulcsár Gergő, the issue you are reporting is an upstream one. Could you
please report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO Benjamin Tissoires, Jiri Kosina, Jonathan Cameron, and Srinivas
Pandruvada CC linux-input)?

Please provide a direct URL to your post to the mailing list when it
becomes available so that it may be tracked.

Thank you for your understanding.

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

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

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

Title:
  [Asus E403SA] ELAN1000 touchpad freezes after minutes to hours

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I've got an ASUS E403SA notebook. With kernel 4.3.x and newer, after a while 
(minutes, sometimes hours) the touchpad completely freezes with this message in 
syslog:
  Jan  5 20:55:27 darkslide-notebook kernel: [ 1531.867948] i2c_designware 
808622C1:03: Unknown Synopsys component type: 0x
  Jan  5 20:55:27 darkslide-notebook kernel: [ 1531.893399] i2c_designware 
808622C1:03: timeout in enabling adapter
  Jan  5 20:55:28 darkslide-notebook kernel: [ 1532.892319] i2c_designware 
808622C1:03: controller timed out
  Jan  5 20:55:28 darkslide-notebook kernel: [ 1532.892334] i2c_designware 
808622C1:03: Unknown Synopsys component type: 0x
  Jan  5 20:55:28 darkslide-notebook kernel: [ 1532.892343] elan_i2c 
i2c-ELAN1000:00: failed to read report data: -110

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-23-generic 4.2.0-23.28
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  darkslide   1511 F pulseaudio
  Date: Wed Jan 20 08:33:06 2016
  HibernationDevice: RESUME=UUID=2e8dbaca-618a-4aff-95bf-a134e77a2ea5
  InstallationDate: Installed on 2015-12-11 (39 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: ASUSTeK COMPUTER INC. E403SA
  ProcEnviron:
   LANGUAGE=hu
   TERM=xterm
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-23-generic.efi.signed 
root=UUID=9179712a-c5fc-4d70-ad86-517fad86f155 ro intel_idle.max_cstate=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-23-generic N/A
   linux-backports-modules-4.2.0-23-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Nincs ilyen fájl vagy könyvtár: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E403SA.212
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: E403SA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE403SA.212:bd08/13/2015:svnASUSTeKCOMPUTERINC.:pnE403SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE403SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: E403SA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1454892] Re: [Hyper-V] hv_netvsc: Use the xmit_more skb flag to optimize signaling the host

2016-01-20 Thread Joseph Salisbury
Hi Chris,

The linux-lts-utopic test kernel did not have that commit applied since
it is being addressed in bug 1519897.

It sounds like these two bugs should be tied togeter.  What do you
think?  I can rebuild the test kernel with all the commits for this bug
and with commit 8599846d7.

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

Title:
  [Hyper-V] hv_netvsc: Use the xmit_more skb flag to optimize signaling
  the host

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-utopic package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux-lts-utopic source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  hv_netvsc: Use the xmit_more skb flag to optimize signaling the host
  Based on the information given to this driver (via the xmit_more skb flag),
  we can defer signaling the host if more packets are on the way. This will help
  make the host more efficient since it can potentially process a larger batch 
of
  packets. Implement this optimization.

  Upstream commit: https://git.kernel.org/cgit/linux/kernel/git/davem
  /net-next.git/commit/?id=82fa3c776e5abba7ed6e4b4f4983d14731c37d6a

  This commit may imply other commits previously requested, for example
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452074

  Requested for all typical Hyper-V targets: 15.10, 15.04, 14.10, 14.04,
  14.04 HWE, 12.02, and 12.02 HWE

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

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


[Kernel-packages] [Bug 1440608] Re: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one

2016-01-20 Thread Cavsfan
Jarno, I did notice that those commands were in the original script after I 
posted that.
I got the 4.3.0-6-generic installed in Xubuntu 16.04 just a while ago and your 
script worked flawlessly.
I had 3 kernels: 4.3.0-2-generic, 4.3.0-5-generic and 4.3.0-6-generic after 
installation and the 01autoremove-kernels file contained just the last 2 both 
before and after rebooting. The output is attached

** Attachment added: "01autoremove-kernels contents"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1440608/+attachment/4553589/+files/01autoremove-kernels%20after%204.3.0-6-generic%20installed%20as%20well%20as%20after%20reboot

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

Title:
  /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels
  except the latest one

Status in One Hundred Papercuts:
  Triaged
Status in apt package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After installing a 3rd kernel currently 3.19.0-12-generic, the
  /etc/apt/apt.conf.d/01autoremove-kernels file looks normal listing the
  3.19.0-11-generic and 3.19.0-12-generic with 3.19.0-10-generic listed
  to be autoremoved. But once autoremove is completed the machine
  requests to be rebooted and at that time the /etc/apt/apt.conf.d
  /01autoremove-kernels file lists the 3.19.0-12-generic and
  3.19.0-10-generic kernels. So upon rebooting the 3.19.0-11-generic is
  requested to be autoremoved leaving only one kernel the latest one
  3.19.0-12-generic.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apt 1.0.9.7ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Sun Apr  5 17:03:01 2015
  InstallationDate: Installed on 2015-04-02 (3 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150401)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


  1   2   3   >