[Kernel-packages] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus

2016-05-24 Thread Tim
Alvin, please don't change the bug status unless you plan to fix this
bug ;) thanks!

** Changed in: ubuntu-gnome
   Status: In Progress => 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/1559576

Title:
  Ubuntu GNOME boots to black screen when using proprietary Nvidia
  drivers on a laptop with Optimus

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  Triaged
Status in gdm3 package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in gdm3 source package in Xenial:
  Triaged
Status in linux source package in Xenial:
  Invalid

Bug description:
  Using latest Ubuntu Gnome x64 daily build with all updates installed. 
  Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure 
boot and other potentially problematic BIOS settings disabled.

  Can only see a black screen instead of a log-in screen after boot completes 
when proprietary Nvidia drivers are installed.
  Regular Ubuntu works absolutely fine on the same machine with the same driver 
version. Attempting to use older drivers on Ubuntu Gnome made no difference.

  Bug is affecting more than just me. We were talking about workarounds
  in ubuntuforums. User fthx claims that switching to lightdm fixes the
  issue
  http://ubuntuforums.org/showthread.php?t=2317628&p=13457703#post13457703

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-14-generic 4.4.0-14.30
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sat Mar 19 23:19:21 2016
  HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6
  InstallationDate: Installed on 2016-03-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160318)
  MachineType: LENOVO 80FG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed 
root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-14-generic N/A
   linux-backports-modules-4.4.0-14-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ABCN96WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo Z70-80
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z70-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80:
  dmi.product.name: 80FG
  dmi.product.version: Lenovo Z70-80
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1585434] Re: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

2016-05-24 Thread cooloutac
that cs:go crash was when i tabbed to the desktop I think I was low on
ram, probably unrelated.  don't know about those libgl errors.  I know
that is needed for steam.   Could it be caused by the nvidia driver?

I had the same issue on linuxmint when upgrading to the 4.4 kernel so I
just stuck with the 3.19 kernel there as well where i didn't have the
messages. I also tried manually make a cryptswap with password prompt on
boot for hibernation but that didnt' help either.   I'm gonna test with
diff video drivers maybe I dunno.

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

Title:
  ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

  ecryptfs_readpage: Error decrypting page; rc = [-4]

  I dont' have this issue showing in dmesg when using 3.19 kernel,  only
  with later kernels.  Is it related to selecting encrypted home on
  install or something?

   I don't notice any issues with performance because of it or have any
  other error messages.  I am using default ubuntu xenial 16.04 with
  unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cooloutac   2054 F pulseaudio
   /dev/snd/pcmC0D0p:   cooloutac   2054 F...m pulseaudio
   /dev/snd/controlC0:  cooloutac   2054 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 24 22:38:44 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=0118ec29-2bd5-4cbc-9800-9c04bbe083d1
  InstallationDate: Installed on 2016-05-20 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. Studio XPS 7100
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=fcd92967-7d59-44bf-bb88-06efa6fac5f7 ro ipv6.disable=1 quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NWWY0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: Studio XPS 7100
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1553687] Re: Lenovo Y700-17ISK Boot Error: Failure writing sector 0x21c8800 to 'hd0'

2016-05-24 Thread Jeb Rosen
I finally got down to do some debugging. I downloaded the grub source
via apt and made some changes to the source code. Specifically, near
line 567 of grub-core/disk/efi/efidisk.c, adding the status code to the
error message:

"failure writing sector 0x%llx to `%s' [status %lx]" with variable
status passed in.

Now I can read the actual error code, which on my machine is [status
80012]. The error code of 12 seemingly corresponds to
GRUB_EFI_NO_MEDIA.

Obviously reads and writes from the physical device succeed, as the boot
loader runs and the operating system runs. I have no idea why only
GRUB's writes are not working (or why NO_MEDIA specifically is the
returned error), but I plan to look into that more over the next week or
so. The drive itself is reported as using the SATA3 interface by hdparm,
smartctl, etc., and I know it is an M.2 chip from specifications.

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

Title:
  Lenovo Y700-17ISK Boot Error: Failure writing sector 0x21c8800 to
  'hd0'

Status in grub2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Expired

Bug description:
  Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB)
  Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 
4.4.0-10-generic, nvidia 361.28)

  Boot Error:
  failure writing sector 0x21c8800 to 'hd0'
  press any key to continue...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  aljosa 1776 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar  6 11:11:22 2016
  HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
  InstallationDate: Installed on 2016-03-05 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 80Q0
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed 
root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CDCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Allsparks 7A
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad Y700-17ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
  dmi.product.name: 80Q0
  dmi.product.version: Lenovo ideapad Y700-17ISK
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1576953] Re: 8086:153a e1000e driver failed with error -3

2016-05-24 Thread Diego
Joerg Albert, you were right. We are suffering the same bug.

I've updated bug report upstream

http://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-
Mon-20160523/005468.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/1576953

Title:
  8086:153a e1000e driver failed with error -3

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When I switch on my laptop, running Ubuntu 16.04 LTS amd64,  it will
  boot and load e1000e, but no eth* interface is present. Even repeated
  rmmod and modprobe don't bring up the interface. After a reboot (i.e.
  no fresh power-up) it works just fine. After the next power-cycle the
  problem is there again. Laptop is a Clevo W130SV, network card is
  Intel I217-LM (rev 05).

  Upstream report:
  
http://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20160516/005431.html

   dmesg | grep e1000e
  [0.985539] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
  [0.985541] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
  [0.985710] e1000e :00:19.0: Interrupt Throttling Rate (ints/sec) set 
to dynamic conservative mode
  [1.979369] e1000e: probe of :00:19.0 failed with error -3

  On warm reboot, last line is gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2235 F pulseaudio
   /dev/snd/controlC1:  diego  2235 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Apr 30 11:24:15 2016
  HibernationDevice: RESUME=UUID=1c631208-0b9d-4ea8-b00c-42463325399c
  MachineType: TEKNO SERVICE SL W130SV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=011e1a79-9a2b-47d7-a20c-c1b362ffd636 ro splash quiet vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W130SV
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/21/2014:svnTEKNOSERVICESL:pnW130SV:pvrNotApplicable:rvnNotebook:rnW130SV:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: W130SV
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TEKNO SERVICE SL

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

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


[Kernel-packages] [Bug 1580943] Re: Kernel is very unstable on Dell XPS15 (model 2014)

2016-05-24 Thread Benjamin Zeller
I can not reproduce this anymore on the upstream kernel and a manually
compiled zfs module

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

** Tags added: kernel-fixed-upstream

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

Title:
  Kernel is very unstable on Dell XPS15 (model 2014)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The system is halted on my machine in different scenarios:

  1) Running debootstrap, the oops happens when chroot tries to mount a kernel 
filesystem from the host
  2) Running ubuntu-emulator create from the Ubuntu SDK IDE: 
http://pastebin.ubuntu.com/16373613/

  3) USB devices are disconnected sometimes, they are immediately
  reconnected but when a ubuntu phone is attached chances are high the
  system might hang as well

  I will attach more logs as soon as I hit the problem again

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  zbenjamin   3703 F pulseaudio
   /dev/snd/controlC2:  zbenjamin   3703 F pulseaudio
   /dev/snd/controlC1:  zbenjamin   3703 F pulseaudio
   /dev/snd/controlC0:  zbenjamin   3703 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 12 11:36:15 2016
  HibernationDevice: RESUME=UUID=ffa1bf0f-220e-4288-9b84-9970818474fc
  InstallationDate: Installed on 2016-03-15 (57 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  MachineType: Dell Inc. XPS 15 9530
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=b09b103f-4a2d-4347-8844-6892dcb781ae ro i915.semaphores=0 
i915.enable_rc6=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: XPS 15 9530
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/16/2014:svnDellInc.:pnXPS159530:pvrA06:rvnDellInc.:rnXPS159530:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 15 9530
  dmi.product.version: A06
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1576953] Re: 8086:153a e1000e driver failed with error -3

2016-05-24 Thread Diego
And this is the log after a warm reboot


~$ dmesg | grep e1000e
[1.308156] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[1.308158] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[1.308326] e1000e :00:19.0: Interrupt Throttling Rate (ints/sec) set to 
dynamic conservative mode
[1.481950] e1000e :00:19.0 eth0: registered PHC clock
[1.481954] e1000e :00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 
80:fa:5b:13:9f:02
[1.481956] e1000e :00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[1.482015] e1000e :00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FF-0FF
[   32.693226] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: 
Rx/Tx
[   32.693232] e1000e :00:19.0 eth0: 10/100 speed: disabling TSO

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

Title:
  8086:153a e1000e driver failed with error -3

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When I switch on my laptop, running Ubuntu 16.04 LTS amd64,  it will
  boot and load e1000e, but no eth* interface is present. Even repeated
  rmmod and modprobe don't bring up the interface. After a reboot (i.e.
  no fresh power-up) it works just fine. After the next power-cycle the
  problem is there again. Laptop is a Clevo W130SV, network card is
  Intel I217-LM (rev 05).

  Upstream report:
  
http://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20160516/005431.html

   dmesg | grep e1000e
  [0.985539] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
  [0.985541] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
  [0.985710] e1000e :00:19.0: Interrupt Throttling Rate (ints/sec) set 
to dynamic conservative mode
  [1.979369] e1000e: probe of :00:19.0 failed with error -3

  On warm reboot, last line is gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2235 F pulseaudio
   /dev/snd/controlC1:  diego  2235 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Apr 30 11:24:15 2016
  HibernationDevice: RESUME=UUID=1c631208-0b9d-4ea8-b00c-42463325399c
  MachineType: TEKNO SERVICE SL W130SV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=011e1a79-9a2b-47d7-a20c-c1b362ffd636 ro splash quiet vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W130SV
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/21/2014:svnTEKNOSERVICESL:pnW130SV:pvrNotApplicable:rvnNotebook:rnW130SV:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: W130SV
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TEKNO SERVICE SL

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

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


[Kernel-packages] [Bug 1576953] Re: 8086:153a e1000e driver failed with error -3

2016-05-24 Thread Diego
Finally got it. Long time since last kernel I compiled back in Debian
Potato days.

~$ dmesg | grep e1000e
[1.273616] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[1.273619] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[1.273784] e1000e :00:19.0: Interrupt Throttling Rate (ints/sec) set to 
dynamic conservative mode
[2.270530] e1000e :00:19.0 :00:19.0 (uninitialized): Failed to 
acquire the semaphore, FW or HW has it: FWSM=0x6040 EXTCNF_CTRL=0x002800c9)
[2.272412] e1000e :00:19.0 :00:19.0 (uninitialized): Failed to 
initialize PHY flow (-3)
[2.273634] e1000e :00:19.0 :00:19.0 (uninitialized): 
e1000_init_phy_params_pchlan: e1000_init_phy_workarounds_pchlan returned -3
[2.275351] e1000e :00:19.0: e1000_init_phy_params-* failed with -3 
(mac.type 11)
[2.276444] e1000e :00:19.0: ei->get_variants failed with -3
[2.286596] e1000e: probe of :00:19.0 failed with error -3

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

Title:
  8086:153a e1000e driver failed with error -3

Status in linux package in Ubuntu:
  Triaged

Bug description:
  When I switch on my laptop, running Ubuntu 16.04 LTS amd64,  it will
  boot and load e1000e, but no eth* interface is present. Even repeated
  rmmod and modprobe don't bring up the interface. After a reboot (i.e.
  no fresh power-up) it works just fine. After the next power-cycle the
  problem is there again. Laptop is a Clevo W130SV, network card is
  Intel I217-LM (rev 05).

  Upstream report:
  
http://lists.osuosl.org/pipermail/intel-wired-lan/Week-of-Mon-20160516/005431.html

   dmesg | grep e1000e
  [0.985539] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
  [0.985541] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
  [0.985710] e1000e :00:19.0: Interrupt Throttling Rate (ints/sec) set 
to dynamic conservative mode
  [1.979369] e1000e: probe of :00:19.0 failed with error -3

  On warm reboot, last line is gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diego  2235 F pulseaudio
   /dev/snd/controlC1:  diego  2235 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Apr 30 11:24:15 2016
  HibernationDevice: RESUME=UUID=1c631208-0b9d-4ea8-b00c-42463325399c
  MachineType: TEKNO SERVICE SL W130SV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=011e1a79-9a2b-47d7-a20c-c1b362ffd636 ro splash quiet vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W130SV
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/21/2014:svnTEKNOSERVICESL:pnW130SV:pvrNotApplicable:rvnNotebook:rnW130SV:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.name: W130SV
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TEKNO SERVICE SL

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

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


[Kernel-packages] [Bug 1585434] Re: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

2016-05-24 Thread cooloutac
hmm I can't recreate the issue now. maybe it doesn't have to do with
steam.

[ 1251.616611] ecryptfs_decrypt_page: Error attempting to read lower page; rc = 
[-4]
[ 1251.616617] ecryptfs_readpage: Error decrypting page; rc = [-4]
[ 1538.783265] audit: type=1400 audit(1464116426.163:70): apparmor="DENIED" 
operation="mknod" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" 
name="/dev/shm/UIaQHa" pid=6040 comm="firefox" requested_mask="c" 
denied_mask="c" fsuid=1000 ouid=1000
[ 1568.092683] csgo_linux[5922]: segfault at 18 ip f7454b07 sp 
d0bbc220 error 4 in libGL.so.340.96[f740a000+b6000]
[ 1569.428923] ecryptfs_decrypt_page: Error attempting to read lower page; rc = 
[-4]
[ 1569.428930] ecryptfs_readpage: Error decrypting page; rc = [-4]
[ 1640.892711] ecryptfs_decrypt_page: Error attempting to read lower page; rc = 
[-4]
[ 1640.892723] ecryptfs_readpage: Error decrypting page; rc = [-4]
[ 4124.250393] ecryptfs_decrypt_page: Error attempting to read lower page; rc = 
[-4]
[ 4124.250398] ecryptfs_readpage: Error decrypting page; rc = [-4]
[ 5915.012016] ecryptfs_decrypt_page: Error attempting to read lower page; rc = 
[-4]
[ 5915.012023] ecryptfs_readpage: Error decrypting page; rc = [-4]
[ 8108.952281] ecryptfs_decrypt_page: Error attempting to read lower page; rc = 
[-4]
[ 8108.952288] ecryptfs_readpage: Error decrypting page; rc = [-4]
[ 9707.657787] ecryptfs_decrypt_page: Error attempting to read lower page; rc = 
[-4]
[ 9707.657794] ecryptfs_readpage: Error decrypting page; rc = [-4]
[ 9881.697323] ecryptfs_decrypt_page: Error attempting to read lower page; rc = 
[-4]
[ 9881.697329] ecryptfs_readpage: Error decrypting page; rc = [-4]
[ 9881.697390] ecryptfs_decrypt_page: Error attempting to read lower page; rc = 
[-4]
[ 9881.697392] ecryptfs_readpage: Error decrypting page; rc = [-4]
[11543.724208] ecryptfs_decrypt_page: Error attempting to read lower page; rc = 
[-4]
[11543.724215] ecryptfs_readpage: Error decrypting page; rc = [-4]
[11543.724260] ecryptfs_decrypt_page: Error attempting to read lower page; rc = 
[-4]
[11543.724262] ecryptfs_readpage: Error decrypting page; rc = [-4]
[11568.143245] device enp2s0 left promiscuous mode
[17325.475556] audit: type=1400 audit(1464132212.890:71): apparmor="DENIED" 
operation="mknod" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" 
name="/dev/shm/qyew6g" pid=8394 comm="firefox" requested_mask="c" 
denied_mask="c" fsuid=1000 ouid=1000
[17416.319524] audit: type=1400 audit(1464132303.738:72): apparmor="DENIED" 
operation="open" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" 
name="/sys/devices/system/node/node0/meminfo" pid=8394 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[22292.050865] ecryptfs_decrypt_page: Error attempting to read lower page; rc = 
[-4]
[22292.050878] ecryptfs_readpage: Error decrypting page; rc = [-4]
[23325.017089] csgo_linux[8580]: segfault at 18 ip f7449b07 sp 
f4b6e220 error 4 in libGL.so.340.96[f73ff000+b6000]
[23328.975790] ecryptfs_decrypt_page: Error attempting to read lower page; rc = 
[-4]
[23328.975802] ecryptfs_readpage: Error decrypting page; rc = [-4]
[23328.976185] ecryptfs_decrypt_page: Error attempting to read lower page; rc = 
[-4]
[23328.976190] ecryptfs_readpage: Error decrypting page; rc = [-4]
[23414.968054] Adding 6289916k swap on /dev/mapper/cryptswap1.  Priority:-1 
extents:1 across:6289916k FS
[24035.193435] ecryptfs_decrypt_page: Error attempting to read lower page; rc = 
[-4]
[24035.193447] ecryptfs_readpage: Error decrypting page; rc = [-4]
[24205.827724] ecryptfs_decrypt_page: Error attempting to read lower page; rc = 
[-4]
[24205.827729] ecryptfs_readpage: Error decrypting page; rc = [-4]
[26773.034290] ecryptfs_decrypt_page: Error attempting to read lower page; rc = 
[-4]
[26773.034302] ecryptfs_readpage: Error decrypting page; rc = [-4]
[26773.034370] ecryptfs_decrypt_page: Error attempting to read lower page; rc = 
[-4]
[26773.034375] ecryptfs_readpage: Error decrypting page; rc = [-4]
[26826.033068] audit: type=1400 audit(1464141713.474:73): apparmor="DENIED" 
operation="mknod" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" 
name="/dev/shm/veUluV" pid=9538 comm="firefox" requested_mask="c" 
denied_mask="c" fsuid=1000 ouid=1000
[26917.107416] audit: type=1400 audit(1464141804.547:74): apparmor="DENIED" 
operation="open" profile="/usr/lib/firefox/firefox{,*[^s][^h]}" 
name="/sys/devices/system/node/node0/meminfo" pid=9538 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[29047.655500] cfg80211: World regulatory domain updated:
[29047.655507] cfg80211:  DFS Master region: unset
[29047.655509] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp), (dfs_cac_time)
[29047.655513] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 
mBm), (N/A)
[29047.655517] cfg80211:   (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 
mBm), (N/A)
[29047.655519] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (N/

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

2016-05-24 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

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

** Description changed:

  This bug is for tracking the 3.13.0-87.133~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
  -- swm properties --
  kernel-stable-master-bug: 1585315
+ kernel-stable-phase:Packaging
+ kernel-stable-phase-changed:Wednesday, 25. May 2016 04:00 UTC

** Description changed:

  This bug is for tracking the 3.13.0-87.133~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
  -- swm properties --
  kernel-stable-master-bug: 1585315
- kernel-stable-phase:Packaging
- kernel-stable-phase-changed:Wednesday, 25. May 2016 04:00 UTC
+ phase: Packaging

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

Title:
  linux-lts-trusty: 3.13.0-87.133~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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  Invalid
Status in Kernel SRU Workflow prepare-package-signed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-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-87.133~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
  -- swm properties --
  kernel-stable-master-bug: 1585315
  phase: Packaging

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

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


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

2016-05-24 Thread Brad Figg
tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-59.66~14.04.1/onza__3.19.0-59.66~14.04.1__2016-05-25_02-48-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-60.67~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:
  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:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

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

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

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

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


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

2016-05-24 Thread Brad Figg
tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-59.66~14.04.1/onibi__3.19.0-59.66~14.04.1__2016-05-25_02-48-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-60.67~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:
  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:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

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

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

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

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


[Kernel-packages] [Bug 1585090] Re: virtualbox-dkms 5.0.20-dfsg-2: virtualbox kernel module failed to build [error: code model kernel does not support PIC mode]

2016-05-24 Thread Daniel van Vugt
** Summary changed:

- virtualbox-dkms 5.0.20-dfsg-2: virtualbox kernel module failed to build
+ virtualbox-dkms 5.0.20-dfsg-2: virtualbox kernel module failed to build 
[error: code model kernel does not support PIC mode]

** Package changed: dkms (Ubuntu) => virtualbox (Ubuntu)

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

Title:
  virtualbox-dkms 5.0.20-dfsg-2: virtualbox kernel module failed to
  build [error: code model kernel does not support PIC mode]

Status in virtualbox package in Ubuntu:
  New

Bug description:
  Just installed today's (24/5/16) updates for 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: virtualbox-dkms 5.0.20-dfsg-2
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  ApportVersion: 2.20.1-0ubuntu4
  Architecture: amd64
  DKMSKernelVersion: 4.4.0-22-generic
  Date: Tue May 24 08:28:35 2016
  DuplicateSignature: 
dkms:virtualbox-dkms:5.0.20-dfsg-2:/var/lib/dkms/virtualbox/5.0.20/build/vboxdrv/vboxdrv.mod.c:1:0:
 error: code model kernel does not support PIC mode
  InstallationDate: Installed on 2014-08-13 (649 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810)
  PackageArchitecture: all
  PackageVersion: 5.0.20-dfsg-2
  RelatedPackageVersions:
   dpkg 1.18.7ubuntu1
   apt  1.3~exp1
  SourcePackage: virtualbox
  Title: virtualbox-dkms 5.0.20-dfsg-2: virtualbox kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus

2016-05-24 Thread Alvin
** Changed in: ubuntu-gnome
   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/1559576

Title:
  Ubuntu GNOME boots to black screen when using proprietary Nvidia
  drivers on a laptop with Optimus

Status in gdm:
  Confirmed
Status in Ubuntu GNOME:
  In Progress
Status in gdm3 package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Invalid
Status in gdm3 source package in Xenial:
  Triaged
Status in linux source package in Xenial:
  Invalid

Bug description:
  Using latest Ubuntu Gnome x64 daily build with all updates installed. 
  Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure 
boot and other potentially problematic BIOS settings disabled.

  Can only see a black screen instead of a log-in screen after boot completes 
when proprietary Nvidia drivers are installed.
  Regular Ubuntu works absolutely fine on the same machine with the same driver 
version. Attempting to use older drivers on Ubuntu Gnome made no difference.

  Bug is affecting more than just me. We were talking about workarounds
  in ubuntuforums. User fthx claims that switching to lightdm fixes the
  issue
  http://ubuntuforums.org/showthread.php?t=2317628&p=13457703#post13457703

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-14-generic 4.4.0-14.30
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sat Mar 19 23:19:21 2016
  HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6
  InstallationDate: Installed on 2016-03-19 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160318)
  MachineType: LENOVO 80FG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed 
root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-14-generic N/A
   linux-backports-modules-4.4.0-14-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: ABCN96WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo Z70-80
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z70-80
  dmi.modalias: 
dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80:
  dmi.product.name: 80FG
  dmi.product.version: Lenovo Z70-80
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1585434] Re: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

2016-05-24 Thread cooloutac
I can confirm once i quit steam it causes the error messages.

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

Title:
  ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

  ecryptfs_readpage: Error decrypting page; rc = [-4]

  I dont' have this issue showing in dmesg when using 3.19 kernel,  only
  with later kernels.  Is it related to selecting encrypted home on
  install or something?

   I don't notice any issues with performance because of it or have any
  other error messages.  I am using default ubuntu xenial 16.04 with
  unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cooloutac   2054 F pulseaudio
   /dev/snd/pcmC0D0p:   cooloutac   2054 F...m pulseaudio
   /dev/snd/controlC0:  cooloutac   2054 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 24 22:38:44 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=0118ec29-2bd5-4cbc-9800-9c04bbe083d1
  InstallationDate: Installed on 2016-05-20 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. Studio XPS 7100
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=fcd92967-7d59-44bf-bb88-06efa6fac5f7 ro ipv6.disable=1 quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NWWY0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: Studio XPS 7100
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1585434] Re: ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

2016-05-24 Thread cooloutac
I think it is possibly caused by steam.  I can recreate the issue, cause
the lines to show in dmesg.  By opening up Steam,  load a game,  then
quit the game,  and then quit steam.  Then the new error lines will be
there.  As I said though it doesn't happen on 3.19 kernel.

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

Title:
  ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

  ecryptfs_readpage: Error decrypting page; rc = [-4]

  I dont' have this issue showing in dmesg when using 3.19 kernel,  only
  with later kernels.  Is it related to selecting encrypted home on
  install or something?

   I don't notice any issues with performance because of it or have any
  other error messages.  I am using default ubuntu xenial 16.04 with
  unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cooloutac   2054 F pulseaudio
   /dev/snd/pcmC0D0p:   cooloutac   2054 F...m pulseaudio
   /dev/snd/controlC0:  cooloutac   2054 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 24 22:38:44 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=0118ec29-2bd5-4cbc-9800-9c04bbe083d1
  InstallationDate: Installed on 2016-05-20 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. Studio XPS 7100
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=fcd92967-7d59-44bf-bb88-06efa6fac5f7 ro ipv6.disable=1 quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NWWY0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: Studio XPS 7100
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1585315] Re: linux: 3.13.0-87.133 -proposed tracker

2016-05-24 Thread Brad Figg
Derivative packages from packages here can be worked on, the following tracking 
bugs were opened for them:
linux-keystone - bug 1585439

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

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

** Description changed:

  This bug is for tracking the 3.13.0-87.133 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-phase-changed:Tuesday, 24. May 2016 19:02 UTC
  kernel-stable-phase:Uploaded
  
  -- swm properties --
+ derivative-trackers-created: true
  phase: Uploaded

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

Title:
  linux: 3.13.0-87.133 -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:
  Invalid
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:
  New

Bug description:
  This bug is for tracking the 3.13.0-87.133 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-phase-changed:Tuesday, 24. May 2016 19:02 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  derivative-trackers-created: true
  phase: Uploaded

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

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


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

2016-05-24 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/1585434

Title:
  ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

  ecryptfs_readpage: Error decrypting page; rc = [-4]

  I dont' have this issue showing in dmesg when using 3.19 kernel,  only
  with later kernels.  Is it related to selecting encrypted home on
  install or something?

   I don't notice any issues with performance because of it or have any
  other error messages.  I am using default ubuntu xenial 16.04 with
  unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cooloutac   2054 F pulseaudio
   /dev/snd/pcmC0D0p:   cooloutac   2054 F...m pulseaudio
   /dev/snd/controlC0:  cooloutac   2054 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 24 22:38:44 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=0118ec29-2bd5-4cbc-9800-9c04bbe083d1
  InstallationDate: Installed on 2016-05-20 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. Studio XPS 7100
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=fcd92967-7d59-44bf-bb88-06efa6fac5f7 ro ipv6.disable=1 quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NWWY0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: Studio XPS 7100
  dmi.sys.vendor: Dell Inc.

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

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


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

2016-05-24 Thread Brad Figg
Public bug reported:

This bug is for tracking the 3.13.0-87.133~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
-- swm properties --
kernel-stable-master-bug: 1585315

** 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: Invalid

** 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: Undecided
 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-meta
   Status: New => Invalid

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

** Changed in: kernel

[Kernel-packages] [Bug 1585434] [NEW] ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

2016-05-24 Thread cooloutac
Public bug reported:

ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

ecryptfs_readpage: Error decrypting page; rc = [-4]

I dont' have this issue showing in dmesg when using 3.19 kernel,  only
with later kernels.  Is it related to selecting encrypted home on
install or something?

 I don't notice any issues with performance because of it or have any
other error messages.  I am using default ubuntu xenial 16.04 with
unity.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-22-generic 4.4.0-22.40
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  cooloutac   2054 F pulseaudio
 /dev/snd/pcmC0D0p:   cooloutac   2054 F...m pulseaudio
 /dev/snd/controlC0:  cooloutac   2054 F pulseaudio
CurrentDesktop: Unity
Date: Tue May 24 22:38:44 2016
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=0118ec29-2bd5-4cbc-9800-9c04bbe083d1
InstallationDate: Installed on 2016-05-20 (5 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
 enp2s0no wireless extensions.
 
 lono wireless extensions.
MachineType: Dell Inc. Studio XPS 7100
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=fcd92967-7d59-44bf-bb88-06efa6fac5f7 ro ipv6.disable=1 quiet splash
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic  N/A
 linux-firmware1.157
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/10/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0NWWY0
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: Studio XPS 7100
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

Status in linux package in Ubuntu:
  New

Bug description:
  ecryptfs_decrypt_page: Error attempting to read lower page; rc = [-4]

  ecryptfs_readpage: Error decrypting page; rc = [-4]

  I dont' have this issue showing in dmesg when using 3.19 kernel,  only
  with later kernels.  Is it related to selecting encrypted home on
  install or something?

   I don't notice any issues with performance because of it or have any
  other error messages.  I am using default ubuntu xenial 16.04 with
  unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  cooloutac   2054 F pulseaudio
   /dev/snd/pcmC0D0p:   cooloutac   2054 F...m pulseaudio
   /dev/snd/controlC0:  cooloutac   2054 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 24 22:38:44 2016
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=0118ec29-2bd5-4cbc-9800-9c04bbe083d1
  InstallationDate: Installed on 2016-05-20 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. Studio XPS 7100
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=fcd92967-7d59-44bf-bb88-06efa6fac5f7 ro ipv6.disable=1 quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NWWY0
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd09/10/2010:svnDellInc.:pnStudioXPS7100:pvr:rvnDellInc.:rn0NWWY0:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: Studio XPS 7100
  dmi.sys.vendor: Dell Inc.

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

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

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

2016-05-24 Thread Brad Figg
tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-60.67~14.04.1/onibi__3.19.0-60.67~14.04.1__2016-05-25_01-49-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-60.67~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:
  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:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

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

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

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

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


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

2016-05-24 Thread Brad Figg
tests ran: 136, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-60.67~14.04.1/onza__3.19.0-60.67~14.04.1__2016-05-25_01-34-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-60.67~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:
  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:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

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

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

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

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


[Kernel-packages] [Bug 1581005] Re: Dell XPS 15 9550 Freezes when HDMI is plugged in

2016-05-24 Thread Mike O'Connell
The provided directory is empty...

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

Title:
  Dell XPS 15 9550 Freezes when HDMI is plugged in

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

Bug description:
  This is fixed upstream in the 4.6.0 series.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael2087 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu May 12 07:25:29 2016
  HibernationDevice: RESUME=UUID=20adf9e8-41f0-4bf8-8075-dcff091511d4
  InstallationDate: Installed on 2016-03-12 (60 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  MachineType: Dell Inc. XPS 15 9550
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed 
root=UUID=ea2a2622-df89-4bf1-8f58-99f313ed3908 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1584233] Re: No bluetooth audio regardless of profile

2016-05-24 Thread EvilWayz
I tried using older kernels, no effect.  My system wouldn't boot with
the mainline kernel.  What should I tag it.  Also, how do I tag?

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

Title:
  No bluetooth audio regardless of profile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As of this morning's upgrade, I no longer have bluetooth audio.  Both
  my audio headsets will connect, and they show up in the sound dialog
  box as options, but they cannot be selected as options, the dialog box
  that lets use choose between hsp or ad2p still says analog stereo, and
  if I test the sound, it comes from the speakers.

  I am using ubuntu 16.04LTS with the 4.4.0-23-generic kernel.  I am
  using Cinnamon 3.0 with Blueberry as my bluez frontend.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-23-generic 4.4.0-23.41
  ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
  Uname: Linux 4.4.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wolf   1997 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Fri May 20 17:41:28 2016
  HibernationDevice: RESUME=UUID=816d36ac-98af-4a51-bf2b-f2e09a34ae15
  InstallationDate: Installed on 2014-12-05 (532 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP xw4400 Workstation
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-23-generic 
root=UUID=e8e318f8-e227-4920-9adc-8362b2cf72e0 ro nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-23-generic N/A
   linux-backports-modules-4.4.0-23-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-01 (19 days ago)
  dmi.bios.date: 07/06/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786D7 v01.02
  dmi.board.name: 0A68h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786D7v01.02:bd07/06/2006:svnHewlett-Packard:pnHPxw4400Workstation:pvr:rvnHewlett-Packard:rn0A68h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP xw4400 Workstation
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1579610] Re: drm.ko < kernel version 4.5 has a dead lock bug

2016-05-24 Thread Qiang Yu
OK. Thanks. We're testing on this. But our driver only support 14.04.4 &
16.04, so we can only verify on 4.2 & 4.4 kernel, is that OK?

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

Title:
  drm.ko < kernel version 4.5 has a dead lock bug

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  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
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  This bug go the code path
  drvers/gpu/drm/{drm_prime.c,drm_gem.c}

  drm_gem_prime_fd_to_handle()
  | mutex_lock(&file_priv->prime.lock);
  | drm_gem_handle_create_tail()
  | | dev->driver->gem_open_object() (for amdgpu.ko driver, this is 
amdgpu_gem_object_open)
  | | drm_gem_handle_delete()
  | | | drm_gem_remove_prime_handles()
  | | | | mutex_lock(&filp->prime.lock);

  This causes the dead lock if gem_open_object() return with error.

  Patch fixing this is already in Linux 4.5:
  
https://github.com/torvalds/linux/commit/6984128d01cf935820a0563f3a00c6623ba58109

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.22.23
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yuq1566 F pulseaudio
   /dev/snd/controlC1:  yuq1566 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon May  9 11:20:26 2016
  HibernationDevice: RESUME=UUID=2e71a82b-c613-4a96-88e3-0672a366c396
  InstallationDate: Installed on 2016-03-01 (69 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160228)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=c137e0c1-ad99-47f4-acf5-e7f4792afa9e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FE
  dmi.board.name: X58A-UD3R
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFE:bd12/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: X58A-UD3R
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1582963] onibi (i386) - tests ran: 18, failed: 6

2016-05-24 Thread Brad Figg
tests ran:  18, failed: 6;
  
http://kernel.ubuntu.com/testing/3.19.0-60.67~14.04.1/onibi__3.19.0-60.67~14.04.1__2016-05-24_21-56-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-60.67~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:
  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:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

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

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

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

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


[Kernel-packages] [Bug 1582963] onza (i386) - tests ran: 18, failed: 6

2016-05-24 Thread Brad Figg
tests ran:  18, failed: 6;
  
http://kernel.ubuntu.com/testing/3.19.0-60.67~14.04.1/onza__3.19.0-60.67~14.04.1__2016-05-24_23-11-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-60.67~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:
  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:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

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

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

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

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


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

2016-05-24 Thread Joshua R. Poulson
Per https://technet.microsoft.com/en-us/library/dn531029.aspx the
recommended kernel and tools to load is as follows:

# apt-get update
# apt-get install --install-recommends linux-virtual-lts-xenial
# apt-get install --install-recommends linux-tools-virtual-lts-xenial 
linux-cloud-tools-virtual-lts-xenial

Of course, it has to be rebooted after this... I *don't* recreate the
problem when I do this... but I did recreate it on a VM that had been
running for a couple weeks.

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

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

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

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

  
  Steps to reproduce:

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

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

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

  Environment:
  Host: Windows NanoServer 2016

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

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

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


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

2016-05-24 Thread Joshua R. Poulson
I have tried a number of different reproduction scenarios at this point
on 4.4.0-21 and 4.4.0-22 and am not getting 100% except on a fresh
install.

Why are you modprobing hv_balloon? It should always be present and
should never need to be loaded manually.

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

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

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

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

  
  Steps to reproduce:

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

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

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

  Environment:
  Host: Windows NanoServer 2016

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

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

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


[Kernel-packages] [Bug 1580798] Re: Suspend breaks on gnome session not on unity session - dell xps 14z

2016-05-24 Thread Cruz Fernandez
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Suspend breaks on gnome session not on unity session - dell xps 14z

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've got two users on this computer. When using gnome 3 session the
  suspend behaves really quirky. After suspend it might have rendering
  problems or it doesn't come back or it comes back with a very slow
  response afterwards.

  In Unity the problem doesn't appear, so a hardware problem seems to
  not affect this other software.

  I'll try to make a screenshot of the rendering problem

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.39
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cruzyfer  13248 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed May 11 19:07:00 2016
  HibernationDevice: RESUME=UUID=4ce8949c-31c9-4b40-bb2f-613863afdb18
  InstallationDate: Installed on 2014-12-06 (522 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: Dell Inc. XPS L412Z
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=caa13b82-560e-4281-83c3-de58dcbd96ef ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-23 (17 days ago)
  dmi.bios.date: 11/15/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 008DD8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A03
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd11/15/2011:svnDellInc.:pnXPSL412Z:pvrA03:rvnDellInc.:rn008DD8:rvrA00:cvnDellInc.:ct8:cvrA03:
  dmi.product.name: XPS L412Z
  dmi.product.version: A03
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1418040] Re: Calling from car using bluetooth, call is placed on ril_0, even though ril_1 is default

2016-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-system-settings -
0.3+16.10.20160523-0ubuntu1

---
ubuntu-system-settings (0.3+16.10.20160523-0ubuntu1) yakkety; urgency=medium

  * Catch connection errors asynchronously

 -- Ken VanDine   Mon, 23 May 2016 12:27:38
+

** Changed in: ubuntu-system-settings (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Calling from car using bluetooth, call is placed on ril_0, even though
  ril_1 is default

Status in Canonical System Image:
  Fix Committed
Status in bluez package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Fix Released
Status in telephony-service package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released

Bug description:
  What happened
  Placed call from car over bluetooth
  Call was placed on my first SIM card, even though I selected my second SIM as 
default for calls

  What should have happened
  The call should have been placed on my second SIM

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: telephony-service 0.1+15.04.20150124-0ubuntu1
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: armhf
  Date: Wed Feb  4 14:25:44 2015
  InstallationDate: Installed on 2015-02-02 (2 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20150202-020204)
  SourcePackage: telephony-service
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418040/+subscriptions

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


[Kernel-packages] [Bug 1585408] [NEW] Broadcom STA driver monitor mode freezes system

2016-05-24 Thread Eric Theis
Public bug reported:

Per the instructions for activating an interface for use in monitor mode
provided by broadcom
(http://www.broadcom.com/docs/linux_sta/README_6.30.223.271.txt), I
execute:

echo 1 > /proc/brcm_monitor0

Nothing happens, and if I execute it with sudo privileges, the entire
system freezes. Thus, I am unable to activate the prism0 monitor mode
interface.

Research shows that this issue occurs beginning in ubuntu 13.10, but
other sources indicate it has since been patched. I am currently running
16.04 on a mac (version 10.1, Retina MBP mid 2012) with a BCM4331
network card.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 24 16:26:26 2016
InstallationDate: Installed on 2016-05-24 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: bcmwl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  Broadcom STA driver monitor mode freezes system

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Per the instructions for activating an interface for use in monitor
  mode provided by broadcom
  (http://www.broadcom.com/docs/linux_sta/README_6.30.223.271.txt), I
  execute:

  echo 1 > /proc/brcm_monitor0

  Nothing happens, and if I execute it with sudo privileges, the entire
  system freezes. Thus, I am unable to activate the prism0 monitor mode
  interface.

  Research shows that this issue occurs beginning in ubuntu 13.10, but
  other sources indicate it has since been patched. I am currently
  running 16.04 on a mac (version 10.1, Retina MBP mid 2012) with a
  BCM4331 network card.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 24 16:26:26 2016
  InstallationDate: Installed on 2016-05-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1526393] Re: ASUS ROG G752 TouchPad not detected

2016-05-24 Thread @pjf
First time reporting using launchpad, so I'm not yet sure of correct
procedures, but I've also got this bug. Different laptop (Gigabyte P57)
but same touchpad ( Sunrex/JME Ghost Key Elimiantion Keyboard ),
expressing itself under Ubuntu 14.04 with a 4.4.0 kernel.

Using a mainline 4.6.0 kernel does not resolve the issue.

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

Title:
   ASUS ROG G752 TouchPad not detected

Status in linux package in Ubuntu:
  Expired

Bug description:
  Laptop Model :  ASUS ROG G752VT-DH72
  First Appearance :  I got two ASUS ROG G752 laptops yesterday afternoon. 
Installed Ubuntu 14.04.03 with pre-installed Windows 10. Both two laptops can 
not detect launchpad.
  Manufacturer : ASUSwith

  *xinput list

  xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Sunrex/JME Ghost Key Elimiantion Keyboard   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ ASUS Tech Inc. ASUS HID Device  id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ASUS Tech Inc. ASUS HID Device  id=14   [slave  pointer 
 (2)]
  ⎜   ↳ Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)  id=12   [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)]
  ↳ Sunrex/JME Ghost Key Elimiantion Keyboard   id=9[slave  
keyboard (3)]
  ↳ USB2.0 HD UVC WebCamid=11   [slave  
keyboard (3)]
  ↳ Asus WMI hotkeysid=15   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=16   [slave  
keyboard (3)]

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-25-generic 3.19.0-25.26~14.04.1 [modified: 
boot/vmlinuz-3.19.0-25-generic]
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 15 10:37:27 2015
  InstallationDate: Installed on 2015-12-14 (1 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  logan  1976 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=d21349d4-a2e3-4591--a533881af2e8
  InstallationDate: Installed on 2015-12-14 (3 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: ASUSTeK COMPUTER INC. G752VT
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-39-generic.efi.signed 
root=UUID=feeb3b62-a26b-486a-bba9-8f4eedd0f6df ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-39.44~14.04.1-generic 3.19.8-ckt9
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-39-generic N/A
   linux-backports-modules-3.19.0-39-generic  N/A
   linux-firmware 1.127.19
  Tags:  trusty
  Uname: Linux 3.19.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G752VT.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G752VT
  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.:bvrG752VT.205:bd09/23/2015:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G752VT
  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/1526393/+subscriptions

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


[Kernel-packages] [Bug 1582963] onza (amd64) - tests ran: 18, failed: 5

2016-05-24 Thread Brad Figg
tests ran:  18, failed: 5;
  
http://kernel.ubuntu.com/testing/3.19.0-60.67~14.04.1/onza__3.19.0-60.67~14.04.1__2016-05-24_20-59-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-60.67~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:
  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:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

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

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

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

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


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

2016-05-24 Thread Omar Siam
apport information

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

Title:
  Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy
  (e. g. GA-78LMT-USB3 Rev 5.0 BIOS FA)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  linux-image-generic:
Installiert:   4.4.0.21.22
Installationskandidat: 4.4.0.21.22
Versionstabelle:
   *** 4.4.0.21.22 500
  500 http://at.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  I would expect the system to boot up like it did before I upgraded to xenial
  When I try to boot my virtual machine host using a xenial based Xen system 
(Xen 4.6, linux generic 4.4.0) it crashes immediately.
  My system setup is non standard as I tried to fix the dom0 memory using 
dom0_mem. This is due to this FAQ entry: 
http://zfsonlinux.org/faq.html#CanIRunZFSForXenHypervisor . I use ZFS for 
virutal machine disks and other storage.
  The systems bios is not updated by manufacturer anymore (2013). The on board 
graphics card is used.
  Shared graphics memory is set to auto. Setting it to 128 MB didn't change 
anything.
  Using a wily kernel 4.2.0 generic or a 4.1.22 mainline kernel works.
  Using a mainline kernel 4.4.8 or 4.5.2 also crashes.
  A quick google search using the first crash report line leads to this
  https://lkml.org/lkml/2015/8/19/366
  and this
  http://code.metager.de/source/history/linux/stable/arch/x86/xen/
  I checked that the two patches that seem most relevant here are present in 
the ubuntu kernel.
  Workaround is to not force a particular amount of memory for dom0 (delete 
dom0_mem parameter)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin8784 F pulseaudio
   /dev/snd/controlC1:  vmadmin8784 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (309 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro net.ifnames=0 rootwait rootdelay=30 usbcore.autosuspend=120 
usbcore.old_scheme_first=1 usbcore.initial_descriptor_timeout=60 
usb-storage.delay_use=10 console=hvc0 console=tty0 earlyprintk=xen quiet splash 
nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (7 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirtd lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin7610 F pulseaudio
   /dev/snd/controlC1:  vmadmin7610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (332 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro dom0_mem=8G,min:8G,max:8G net.ifnames=0 rootwait rootdelay=30 
usbcore.autosuspend=120 usbcore.old_scheme_first=1 
usbcore.initial_descriptor_timeout=60 usb-storage.delay_use=10 console=hvc0 
console=tty0 earlyprintk=xen quiet splash nomdmonddf nom

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

2016-05-24 Thread Omar Siam
apport information

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

Title:
  Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy
  (e. g. GA-78LMT-USB3 Rev 5.0 BIOS FA)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  linux-image-generic:
Installiert:   4.4.0.21.22
Installationskandidat: 4.4.0.21.22
Versionstabelle:
   *** 4.4.0.21.22 500
  500 http://at.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  I would expect the system to boot up like it did before I upgraded to xenial
  When I try to boot my virtual machine host using a xenial based Xen system 
(Xen 4.6, linux generic 4.4.0) it crashes immediately.
  My system setup is non standard as I tried to fix the dom0 memory using 
dom0_mem. This is due to this FAQ entry: 
http://zfsonlinux.org/faq.html#CanIRunZFSForXenHypervisor . I use ZFS for 
virutal machine disks and other storage.
  The systems bios is not updated by manufacturer anymore (2013). The on board 
graphics card is used.
  Shared graphics memory is set to auto. Setting it to 128 MB didn't change 
anything.
  Using a wily kernel 4.2.0 generic or a 4.1.22 mainline kernel works.
  Using a mainline kernel 4.4.8 or 4.5.2 also crashes.
  A quick google search using the first crash report line leads to this
  https://lkml.org/lkml/2015/8/19/366
  and this
  http://code.metager.de/source/history/linux/stable/arch/x86/xen/
  I checked that the two patches that seem most relevant here are present in 
the ubuntu kernel.
  Workaround is to not force a particular amount of memory for dom0 (delete 
dom0_mem parameter)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin8784 F pulseaudio
   /dev/snd/controlC1:  vmadmin8784 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (309 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro net.ifnames=0 rootwait rootdelay=30 usbcore.autosuspend=120 
usbcore.old_scheme_first=1 usbcore.initial_descriptor_timeout=60 
usb-storage.delay_use=10 console=hvc0 console=tty0 earlyprintk=xen quiet splash 
nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (7 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirtd lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin7610 F pulseaudio
   /dev/snd/controlC1:  vmadmin7610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (332 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro dom0_mem=8G,min:8G,max:8G net.ifnames=0 rootwait rootdelay=30 
usbcore.autosuspend=120 usbcore.old_scheme_first=1 
usbcore.initial_descriptor_timeout=60 usb-storage.delay_use=10 console=hvc0 
console=tty0 earlyprintk=xen quiet splash n

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

2016-05-24 Thread Omar Siam
apport information

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

Title:
  Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy
  (e. g. GA-78LMT-USB3 Rev 5.0 BIOS FA)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  linux-image-generic:
Installiert:   4.4.0.21.22
Installationskandidat: 4.4.0.21.22
Versionstabelle:
   *** 4.4.0.21.22 500
  500 http://at.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  I would expect the system to boot up like it did before I upgraded to xenial
  When I try to boot my virtual machine host using a xenial based Xen system 
(Xen 4.6, linux generic 4.4.0) it crashes immediately.
  My system setup is non standard as I tried to fix the dom0 memory using 
dom0_mem. This is due to this FAQ entry: 
http://zfsonlinux.org/faq.html#CanIRunZFSForXenHypervisor . I use ZFS for 
virutal machine disks and other storage.
  The systems bios is not updated by manufacturer anymore (2013). The on board 
graphics card is used.
  Shared graphics memory is set to auto. Setting it to 128 MB didn't change 
anything.
  Using a wily kernel 4.2.0 generic or a 4.1.22 mainline kernel works.
  Using a mainline kernel 4.4.8 or 4.5.2 also crashes.
  A quick google search using the first crash report line leads to this
  https://lkml.org/lkml/2015/8/19/366
  and this
  http://code.metager.de/source/history/linux/stable/arch/x86/xen/
  I checked that the two patches that seem most relevant here are present in 
the ubuntu kernel.
  Workaround is to not force a particular amount of memory for dom0 (delete 
dom0_mem parameter)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin8784 F pulseaudio
   /dev/snd/controlC1:  vmadmin8784 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (309 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro net.ifnames=0 rootwait rootdelay=30 usbcore.autosuspend=120 
usbcore.old_scheme_first=1 usbcore.initial_descriptor_timeout=60 
usb-storage.delay_use=10 console=hvc0 console=tty0 earlyprintk=xen quiet splash 
nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (7 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirtd lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin7610 F pulseaudio
   /dev/snd/controlC1:  vmadmin7610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (332 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro dom0_mem=8G,min:8G,max:8G net.ifnames=0 rootwait rootdelay=30 
usbcore.autosuspend=120 usbcore.old_scheme_first=1 
usbcore.initial_descriptor_timeout=60 usb-storage.delay_use=10 console=hvc0 
console=tty0 earlyprintk=xen quiet splash nomdmonddf nomdm

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

2016-05-24 Thread Omar Siam
apport information

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

Title:
  Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy
  (e. g. GA-78LMT-USB3 Rev 5.0 BIOS FA)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  linux-image-generic:
Installiert:   4.4.0.21.22
Installationskandidat: 4.4.0.21.22
Versionstabelle:
   *** 4.4.0.21.22 500
  500 http://at.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  I would expect the system to boot up like it did before I upgraded to xenial
  When I try to boot my virtual machine host using a xenial based Xen system 
(Xen 4.6, linux generic 4.4.0) it crashes immediately.
  My system setup is non standard as I tried to fix the dom0 memory using 
dom0_mem. This is due to this FAQ entry: 
http://zfsonlinux.org/faq.html#CanIRunZFSForXenHypervisor . I use ZFS for 
virutal machine disks and other storage.
  The systems bios is not updated by manufacturer anymore (2013). The on board 
graphics card is used.
  Shared graphics memory is set to auto. Setting it to 128 MB didn't change 
anything.
  Using a wily kernel 4.2.0 generic or a 4.1.22 mainline kernel works.
  Using a mainline kernel 4.4.8 or 4.5.2 also crashes.
  A quick google search using the first crash report line leads to this
  https://lkml.org/lkml/2015/8/19/366
  and this
  http://code.metager.de/source/history/linux/stable/arch/x86/xen/
  I checked that the two patches that seem most relevant here are present in 
the ubuntu kernel.
  Workaround is to not force a particular amount of memory for dom0 (delete 
dom0_mem parameter)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin8784 F pulseaudio
   /dev/snd/controlC1:  vmadmin8784 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (309 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro net.ifnames=0 rootwait rootdelay=30 usbcore.autosuspend=120 
usbcore.old_scheme_first=1 usbcore.initial_descriptor_timeout=60 
usb-storage.delay_use=10 console=hvc0 console=tty0 earlyprintk=xen quiet splash 
nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (7 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirtd lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin7610 F pulseaudio
   /dev/snd/controlC1:  vmadmin7610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (332 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro dom0_mem=8G,min:8G,max:8G net.ifnames=0 rootwait rootdelay=30 
usbcore.autosuspend=120 usbcore.old_scheme_first=1 
usbcore.initial_descriptor_timeout=60 usb-storage.delay_use=10 console=hvc0 
console=tty0 earlyprintk=xen quiet splash nomdm

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

2016-05-24 Thread Omar Siam
apport information

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

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

Title:
  Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy
  (e. g. GA-78LMT-USB3 Rev 5.0 BIOS FA)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  linux-image-generic:
Installiert:   4.4.0.21.22
Installationskandidat: 4.4.0.21.22
Versionstabelle:
   *** 4.4.0.21.22 500
  500 http://at.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  I would expect the system to boot up like it did before I upgraded to xenial
  When I try to boot my virtual machine host using a xenial based Xen system 
(Xen 4.6, linux generic 4.4.0) it crashes immediately.
  My system setup is non standard as I tried to fix the dom0 memory using 
dom0_mem. This is due to this FAQ entry: 
http://zfsonlinux.org/faq.html#CanIRunZFSForXenHypervisor . I use ZFS for 
virutal machine disks and other storage.
  The systems bios is not updated by manufacturer anymore (2013). The on board 
graphics card is used.
  Shared graphics memory is set to auto. Setting it to 128 MB didn't change 
anything.
  Using a wily kernel 4.2.0 generic or a 4.1.22 mainline kernel works.
  Using a mainline kernel 4.4.8 or 4.5.2 also crashes.
  A quick google search using the first crash report line leads to this
  https://lkml.org/lkml/2015/8/19/366
  and this
  http://code.metager.de/source/history/linux/stable/arch/x86/xen/
  I checked that the two patches that seem most relevant here are present in 
the ubuntu kernel.
  Workaround is to not force a particular amount of memory for dom0 (delete 
dom0_mem parameter)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin8784 F pulseaudio
   /dev/snd/controlC1:  vmadmin8784 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (309 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro net.ifnames=0 rootwait rootdelay=30 usbcore.autosuspend=120 
usbcore.old_scheme_first=1 usbcore.initial_descriptor_timeout=60 
usb-storage.delay_use=10 console=hvc0 console=tty0 earlyprintk=xen quiet splash 
nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (7 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirtd lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin7610 F pulseaudio
   /dev/snd/controlC1:  vmadmin7610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (332 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro dom0_mem=8G,min:8G,max:8G net.ifnames=0 rootwait rootdelay=30 
usbcore.autosuspend=120 usbcore.old_scheme_first=1 
usbcore.initial_descriptor_timeout=60 usb-storage.delay_use=10 console=hvc0 
console=tty0 earlyprintk=xen quiet splash nom

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

2016-05-24 Thread Omar Siam
apport information

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

Title:
  Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy
  (e. g. GA-78LMT-USB3 Rev 5.0 BIOS FA)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  linux-image-generic:
Installiert:   4.4.0.21.22
Installationskandidat: 4.4.0.21.22
Versionstabelle:
   *** 4.4.0.21.22 500
  500 http://at.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  I would expect the system to boot up like it did before I upgraded to xenial
  When I try to boot my virtual machine host using a xenial based Xen system 
(Xen 4.6, linux generic 4.4.0) it crashes immediately.
  My system setup is non standard as I tried to fix the dom0 memory using 
dom0_mem. This is due to this FAQ entry: 
http://zfsonlinux.org/faq.html#CanIRunZFSForXenHypervisor . I use ZFS for 
virutal machine disks and other storage.
  The systems bios is not updated by manufacturer anymore (2013). The on board 
graphics card is used.
  Shared graphics memory is set to auto. Setting it to 128 MB didn't change 
anything.
  Using a wily kernel 4.2.0 generic or a 4.1.22 mainline kernel works.
  Using a mainline kernel 4.4.8 or 4.5.2 also crashes.
  A quick google search using the first crash report line leads to this
  https://lkml.org/lkml/2015/8/19/366
  and this
  http://code.metager.de/source/history/linux/stable/arch/x86/xen/
  I checked that the two patches that seem most relevant here are present in 
the ubuntu kernel.
  Workaround is to not force a particular amount of memory for dom0 (delete 
dom0_mem parameter)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin8784 F pulseaudio
   /dev/snd/controlC1:  vmadmin8784 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (309 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro net.ifnames=0 rootwait rootdelay=30 usbcore.autosuspend=120 
usbcore.old_scheme_first=1 usbcore.initial_descriptor_timeout=60 
usb-storage.delay_use=10 console=hvc0 console=tty0 earlyprintk=xen quiet splash 
nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (7 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirtd lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin7610 F pulseaudio
   /dev/snd/controlC1:  vmadmin7610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (332 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro dom0_mem=8G,min:8G,max:8G net.ifnames=0 rootwait rootdelay=30 
usbcore.autosuspend=120 usbcore.old_scheme_first=1 
usbcore.initial_descriptor_timeout=60 usb-storage.delay_use=10 console=hvc0 
console=tty0 earlyprintk=xen quiet splash n

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

2016-05-24 Thread Omar Siam
apport information

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

Title:
  Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy
  (e. g. GA-78LMT-USB3 Rev 5.0 BIOS FA)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  linux-image-generic:
Installiert:   4.4.0.21.22
Installationskandidat: 4.4.0.21.22
Versionstabelle:
   *** 4.4.0.21.22 500
  500 http://at.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  I would expect the system to boot up like it did before I upgraded to xenial
  When I try to boot my virtual machine host using a xenial based Xen system 
(Xen 4.6, linux generic 4.4.0) it crashes immediately.
  My system setup is non standard as I tried to fix the dom0 memory using 
dom0_mem. This is due to this FAQ entry: 
http://zfsonlinux.org/faq.html#CanIRunZFSForXenHypervisor . I use ZFS for 
virutal machine disks and other storage.
  The systems bios is not updated by manufacturer anymore (2013). The on board 
graphics card is used.
  Shared graphics memory is set to auto. Setting it to 128 MB didn't change 
anything.
  Using a wily kernel 4.2.0 generic or a 4.1.22 mainline kernel works.
  Using a mainline kernel 4.4.8 or 4.5.2 also crashes.
  A quick google search using the first crash report line leads to this
  https://lkml.org/lkml/2015/8/19/366
  and this
  http://code.metager.de/source/history/linux/stable/arch/x86/xen/
  I checked that the two patches that seem most relevant here are present in 
the ubuntu kernel.
  Workaround is to not force a particular amount of memory for dom0 (delete 
dom0_mem parameter)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin8784 F pulseaudio
   /dev/snd/controlC1:  vmadmin8784 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (309 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro net.ifnames=0 rootwait rootdelay=30 usbcore.autosuspend=120 
usbcore.old_scheme_first=1 usbcore.initial_descriptor_timeout=60 
usb-storage.delay_use=10 console=hvc0 console=tty0 earlyprintk=xen quiet splash 
nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (7 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirtd lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin7610 F pulseaudio
   /dev/snd/controlC1:  vmadmin7610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (332 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro dom0_mem=8G,min:8G,max:8G net.ifnames=0 rootwait rootdelay=30 
usbcore.autosuspend=120 usbcore.old_scheme_first=1 
usbcore.initial_descriptor_timeout=60 usb-storage.delay_use=10 console=hvc0 
console=tty0 earlyprintk=xen quiet splash nomdmonddf nom

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

2016-05-24 Thread Omar Siam
apport information

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

Title:
  Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy
  (e. g. GA-78LMT-USB3 Rev 5.0 BIOS FA)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  linux-image-generic:
Installiert:   4.4.0.21.22
Installationskandidat: 4.4.0.21.22
Versionstabelle:
   *** 4.4.0.21.22 500
  500 http://at.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  I would expect the system to boot up like it did before I upgraded to xenial
  When I try to boot my virtual machine host using a xenial based Xen system 
(Xen 4.6, linux generic 4.4.0) it crashes immediately.
  My system setup is non standard as I tried to fix the dom0 memory using 
dom0_mem. This is due to this FAQ entry: 
http://zfsonlinux.org/faq.html#CanIRunZFSForXenHypervisor . I use ZFS for 
virutal machine disks and other storage.
  The systems bios is not updated by manufacturer anymore (2013). The on board 
graphics card is used.
  Shared graphics memory is set to auto. Setting it to 128 MB didn't change 
anything.
  Using a wily kernel 4.2.0 generic or a 4.1.22 mainline kernel works.
  Using a mainline kernel 4.4.8 or 4.5.2 also crashes.
  A quick google search using the first crash report line leads to this
  https://lkml.org/lkml/2015/8/19/366
  and this
  http://code.metager.de/source/history/linux/stable/arch/x86/xen/
  I checked that the two patches that seem most relevant here are present in 
the ubuntu kernel.
  Workaround is to not force a particular amount of memory for dom0 (delete 
dom0_mem parameter)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin8784 F pulseaudio
   /dev/snd/controlC1:  vmadmin8784 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (309 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro net.ifnames=0 rootwait rootdelay=30 usbcore.autosuspend=120 
usbcore.old_scheme_first=1 usbcore.initial_descriptor_timeout=60 
usb-storage.delay_use=10 console=hvc0 console=tty0 earlyprintk=xen quiet splash 
nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (7 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirtd lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin7610 F pulseaudio
   /dev/snd/controlC1:  vmadmin7610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (332 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro dom0_mem=8G,min:8G,max:8G net.ifnames=0 rootwait rootdelay=30 
usbcore.autosuspend=120 usbcore.old_scheme_first=1 
usbcore.initial_descriptor_timeout=60 usb-storage.delay_use=10 console=hvc0 
console=tty0 earlyprintk=xen quiet spla

[Kernel-packages] [Bug 1577018] Re: Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy (e. g. GA-78LMT-USB3 Rev 5.0 BIOS FA)

2016-05-24 Thread Omar Siam
Changed Mainboard to some ASUS. Works for me now.

** Summary changed:

- Kernel crashes on dom0 startup when dom0_mem is set
+ Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy (e. g. 
GA-78LMT-USB3 Rev 5.0 BIOS FA)

** Description changed:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  linux-image-generic:
Installiert:   4.4.0.21.22
Installationskandidat: 4.4.0.21.22
Versionstabelle:
   *** 4.4.0.21.22 500
  500 http://at.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  I would expect the system to boot up like it did before I upgraded to xenial
  When I try to boot my virtual machine host using a xenial based Xen system 
(Xen 4.6, linux generic 4.4.0) it crashes immediately.
  My system setup is non standard as I tried to fix the dom0 memory using 
dom0_mem. This is due to this FAQ entry: 
http://zfsonlinux.org/faq.html#CanIRunZFSForXenHypervisor . I use ZFS for 
virutal machine disks and other storage.
  The systems bios is not updated by manufacturer anymore (2013). The on board 
graphics card is used.
  Shared graphics memory is set to auto. Setting it to 128 MB didn't change 
anything.
  Using a wily kernel 4.2.0 generic or a 4.1.22 mainline kernel works.
  Using a mainline kernel 4.4.8 or 4.5.2 also crashes.
  A quick google search using the first crash report line leads to this
  https://lkml.org/lkml/2015/8/19/366
  and this
  http://code.metager.de/source/history/linux/stable/arch/x86/xen/
  I checked that the two patches that seem most relevant here are present in 
the ubuntu kernel.
  Workaround is to not force a particular amount of memory for dom0 (delete 
dom0_mem parameter)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin8784 F pulseaudio
   /dev/snd/controlC1:  vmadmin8784 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (309 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro net.ifnames=0 rootwait rootdelay=30 usbcore.autosuspend=120 
usbcore.old_scheme_first=1 usbcore.initial_descriptor_timeout=60 
usb-storage.delay_use=10 console=hvc0 console=tty0 earlyprintk=xen quiet splash 
nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (7 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirtd lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  vmadmin7610 F pulseaudio
+  /dev/snd/controlC1:  vmadmin7610 F pulseaudio
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
+ InstallationDate: Installed on 2015-06-27 (332 days ago)
+ InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
+ MachineType: System manufacturer System Product Name
+ NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
+ Package: linux (not installed)
+ ProcFB: 0 radeondrmfb
+ ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro dom0_mem=8G,min:8G,max:8G net.ifnames=0 rootwait rootdelay=30 
usbcore.autosuspend=120 usbcore.old_scheme_first=1 
usbcore.initial_descriptor_timeout=60 usb-storage.delay_use=10 console=hvc0 
console=tty0 earlyprintk=xen quiet splash nomdmonddf nomdmonisw
+ ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-22-generic N/A
+  linux-backports-modules-4.4.0-22-generic  N/A
+  linux-firmware   

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

2016-05-24 Thread Omar Siam
apport information

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

Title:
  Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy
  (e. g. GA-78LMT-USB3 Rev 5.0 BIOS FA)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  linux-image-generic:
Installiert:   4.4.0.21.22
Installationskandidat: 4.4.0.21.22
Versionstabelle:
   *** 4.4.0.21.22 500
  500 http://at.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  I would expect the system to boot up like it did before I upgraded to xenial
  When I try to boot my virtual machine host using a xenial based Xen system 
(Xen 4.6, linux generic 4.4.0) it crashes immediately.
  My system setup is non standard as I tried to fix the dom0 memory using 
dom0_mem. This is due to this FAQ entry: 
http://zfsonlinux.org/faq.html#CanIRunZFSForXenHypervisor . I use ZFS for 
virutal machine disks and other storage.
  The systems bios is not updated by manufacturer anymore (2013). The on board 
graphics card is used.
  Shared graphics memory is set to auto. Setting it to 128 MB didn't change 
anything.
  Using a wily kernel 4.2.0 generic or a 4.1.22 mainline kernel works.
  Using a mainline kernel 4.4.8 or 4.5.2 also crashes.
  A quick google search using the first crash report line leads to this
  https://lkml.org/lkml/2015/8/19/366
  and this
  http://code.metager.de/source/history/linux/stable/arch/x86/xen/
  I checked that the two patches that seem most relevant here are present in 
the ubuntu kernel.
  Workaround is to not force a particular amount of memory for dom0 (delete 
dom0_mem parameter)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin8784 F pulseaudio
   /dev/snd/controlC1:  vmadmin8784 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (309 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro net.ifnames=0 rootwait rootdelay=30 usbcore.autosuspend=120 
usbcore.old_scheme_first=1 usbcore.initial_descriptor_timeout=60 
usb-storage.delay_use=10 console=hvc0 console=tty0 earlyprintk=xen quiet splash 
nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (7 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirtd lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin7610 F pulseaudio
   /dev/snd/controlC1:  vmadmin7610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (332 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro dom0_mem=8G,min:8G,max:8G net.ifnames=0 rootwait rootdelay=30 
usbcore.autosuspend=120 usbcore.old_scheme_first=1 
usbcore.initial_descriptor_timeout=60 usb-storage.delay_use=10 console=hvc0 
console=tty0 earlyprintk=xen quiet splash n

[Kernel-packages] [Bug 1577018] AlsaInfo.txt

2016-05-24 Thread Omar Siam
apport information

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

Title:
  Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy
  (e. g. GA-78LMT-USB3 Rev 5.0 BIOS FA)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  linux-image-generic:
Installiert:   4.4.0.21.22
Installationskandidat: 4.4.0.21.22
Versionstabelle:
   *** 4.4.0.21.22 500
  500 http://at.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  I would expect the system to boot up like it did before I upgraded to xenial
  When I try to boot my virtual machine host using a xenial based Xen system 
(Xen 4.6, linux generic 4.4.0) it crashes immediately.
  My system setup is non standard as I tried to fix the dom0 memory using 
dom0_mem. This is due to this FAQ entry: 
http://zfsonlinux.org/faq.html#CanIRunZFSForXenHypervisor . I use ZFS for 
virutal machine disks and other storage.
  The systems bios is not updated by manufacturer anymore (2013). The on board 
graphics card is used.
  Shared graphics memory is set to auto. Setting it to 128 MB didn't change 
anything.
  Using a wily kernel 4.2.0 generic or a 4.1.22 mainline kernel works.
  Using a mainline kernel 4.4.8 or 4.5.2 also crashes.
  A quick google search using the first crash report line leads to this
  https://lkml.org/lkml/2015/8/19/366
  and this
  http://code.metager.de/source/history/linux/stable/arch/x86/xen/
  I checked that the two patches that seem most relevant here are present in 
the ubuntu kernel.
  Workaround is to not force a particular amount of memory for dom0 (delete 
dom0_mem parameter)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin8784 F pulseaudio
   /dev/snd/controlC1:  vmadmin8784 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (309 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro net.ifnames=0 rootwait rootdelay=30 usbcore.autosuspend=120 
usbcore.old_scheme_first=1 usbcore.initial_descriptor_timeout=60 
usb-storage.delay_use=10 console=hvc0 console=tty0 earlyprintk=xen quiet splash 
nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (7 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirtd lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin7610 F pulseaudio
   /dev/snd/controlC1:  vmadmin7610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (332 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro dom0_mem=8G,min:8G,max:8G net.ifnames=0 rootwait rootdelay=30 
usbcore.autosuspend=120 usbcore.old_scheme_first=1 
usbcore.initial_descriptor_timeout=60 usb-storage.delay_use=10 console=hvc0 
console=tty0 earlyprintk=xen quiet splash nomdmon

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

2016-05-24 Thread Omar Siam
apport information

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

Title:
  Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy
  (e. g. GA-78LMT-USB3 Rev 5.0 BIOS FA)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  linux-image-generic:
Installiert:   4.4.0.21.22
Installationskandidat: 4.4.0.21.22
Versionstabelle:
   *** 4.4.0.21.22 500
  500 http://at.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  I would expect the system to boot up like it did before I upgraded to xenial
  When I try to boot my virtual machine host using a xenial based Xen system 
(Xen 4.6, linux generic 4.4.0) it crashes immediately.
  My system setup is non standard as I tried to fix the dom0 memory using 
dom0_mem. This is due to this FAQ entry: 
http://zfsonlinux.org/faq.html#CanIRunZFSForXenHypervisor . I use ZFS for 
virutal machine disks and other storage.
  The systems bios is not updated by manufacturer anymore (2013). The on board 
graphics card is used.
  Shared graphics memory is set to auto. Setting it to 128 MB didn't change 
anything.
  Using a wily kernel 4.2.0 generic or a 4.1.22 mainline kernel works.
  Using a mainline kernel 4.4.8 or 4.5.2 also crashes.
  A quick google search using the first crash report line leads to this
  https://lkml.org/lkml/2015/8/19/366
  and this
  http://code.metager.de/source/history/linux/stable/arch/x86/xen/
  I checked that the two patches that seem most relevant here are present in 
the ubuntu kernel.
  Workaround is to not force a particular amount of memory for dom0 (delete 
dom0_mem parameter)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin8784 F pulseaudio
   /dev/snd/controlC1:  vmadmin8784 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (309 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro net.ifnames=0 rootwait rootdelay=30 usbcore.autosuspend=120 
usbcore.old_scheme_first=1 usbcore.initial_descriptor_timeout=60 
usb-storage.delay_use=10 console=hvc0 console=tty0 earlyprintk=xen quiet splash 
nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (7 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirtd lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin7610 F pulseaudio
   /dev/snd/controlC1:  vmadmin7610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (332 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro dom0_mem=8G,min:8G,max:8G net.ifnames=0 rootwait rootdelay=30 
usbcore.autosuspend=120 usbcore.old_scheme_first=1 
usbcore.initial_descriptor_timeout=60 usb-storage.delay_use=10 console=hvc0 
console=tty0 earlyprintk=xen quiet splash

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

2016-05-24 Thread Omar Siam
apport information

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

Title:
  Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy
  (e. g. GA-78LMT-USB3 Rev 5.0 BIOS FA)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  linux-image-generic:
Installiert:   4.4.0.21.22
Installationskandidat: 4.4.0.21.22
Versionstabelle:
   *** 4.4.0.21.22 500
  500 http://at.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  I would expect the system to boot up like it did before I upgraded to xenial
  When I try to boot my virtual machine host using a xenial based Xen system 
(Xen 4.6, linux generic 4.4.0) it crashes immediately.
  My system setup is non standard as I tried to fix the dom0 memory using 
dom0_mem. This is due to this FAQ entry: 
http://zfsonlinux.org/faq.html#CanIRunZFSForXenHypervisor . I use ZFS for 
virutal machine disks and other storage.
  The systems bios is not updated by manufacturer anymore (2013). The on board 
graphics card is used.
  Shared graphics memory is set to auto. Setting it to 128 MB didn't change 
anything.
  Using a wily kernel 4.2.0 generic or a 4.1.22 mainline kernel works.
  Using a mainline kernel 4.4.8 or 4.5.2 also crashes.
  A quick google search using the first crash report line leads to this
  https://lkml.org/lkml/2015/8/19/366
  and this
  http://code.metager.de/source/history/linux/stable/arch/x86/xen/
  I checked that the two patches that seem most relevant here are present in 
the ubuntu kernel.
  Workaround is to not force a particular amount of memory for dom0 (delete 
dom0_mem parameter)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin8784 F pulseaudio
   /dev/snd/controlC1:  vmadmin8784 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (309 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro net.ifnames=0 rootwait rootdelay=30 usbcore.autosuspend=120 
usbcore.old_scheme_first=1 usbcore.initial_descriptor_timeout=60 
usb-storage.delay_use=10 console=hvc0 console=tty0 earlyprintk=xen quiet splash 
nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (7 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirtd lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin7610 F pulseaudio
   /dev/snd/controlC1:  vmadmin7610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (332 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro dom0_mem=8G,min:8G,max:8G net.ifnames=0 rootwait rootdelay=30 
usbcore.autosuspend=120 usbcore.old_scheme_first=1 
usbcore.initial_descriptor_timeout=60 usb-storage.delay_use=10 console=hvc0 
console=tty0 earlyprintk=xen quiet sp

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

2016-05-24 Thread Omar Siam
apport information

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

Title:
  Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy
  (e. g. GA-78LMT-USB3 Rev 5.0 BIOS FA)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  linux-image-generic:
Installiert:   4.4.0.21.22
Installationskandidat: 4.4.0.21.22
Versionstabelle:
   *** 4.4.0.21.22 500
  500 http://at.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  I would expect the system to boot up like it did before I upgraded to xenial
  When I try to boot my virtual machine host using a xenial based Xen system 
(Xen 4.6, linux generic 4.4.0) it crashes immediately.
  My system setup is non standard as I tried to fix the dom0 memory using 
dom0_mem. This is due to this FAQ entry: 
http://zfsonlinux.org/faq.html#CanIRunZFSForXenHypervisor . I use ZFS for 
virutal machine disks and other storage.
  The systems bios is not updated by manufacturer anymore (2013). The on board 
graphics card is used.
  Shared graphics memory is set to auto. Setting it to 128 MB didn't change 
anything.
  Using a wily kernel 4.2.0 generic or a 4.1.22 mainline kernel works.
  Using a mainline kernel 4.4.8 or 4.5.2 also crashes.
  A quick google search using the first crash report line leads to this
  https://lkml.org/lkml/2015/8/19/366
  and this
  http://code.metager.de/source/history/linux/stable/arch/x86/xen/
  I checked that the two patches that seem most relevant here are present in 
the ubuntu kernel.
  Workaround is to not force a particular amount of memory for dom0 (delete 
dom0_mem parameter)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin8784 F pulseaudio
   /dev/snd/controlC1:  vmadmin8784 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (309 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro net.ifnames=0 rootwait rootdelay=30 usbcore.autosuspend=120 
usbcore.old_scheme_first=1 usbcore.initial_descriptor_timeout=60 
usb-storage.delay_use=10 console=hvc0 console=tty0 earlyprintk=xen quiet splash 
nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (7 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirtd lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin7610 F pulseaudio
   /dev/snd/controlC1:  vmadmin7610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (332 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro dom0_mem=8G,min:8G,max:8G net.ifnames=0 rootwait rootdelay=30 
usbcore.autosuspend=120 usbcore.old_scheme_first=1 
usbcore.initial_descriptor_timeout=60 usb-storage.delay_use=10 console=hvc0 
console=tty0 earlyprintk=xen quiet splash nomdmonddf n

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

2016-05-24 Thread Omar Siam
apport information

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

Title:
  Kernel crashes on dom0 startup when dom0_mem is set if BIOS is buggy
  (e. g. GA-78LMT-USB3 Rev 5.0 BIOS FA)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  linux-image-generic:
Installiert:   4.4.0.21.22
Installationskandidat: 4.4.0.21.22
Versionstabelle:
   *** 4.4.0.21.22 500
  500 http://at.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status
  I would expect the system to boot up like it did before I upgraded to xenial
  When I try to boot my virtual machine host using a xenial based Xen system 
(Xen 4.6, linux generic 4.4.0) it crashes immediately.
  My system setup is non standard as I tried to fix the dom0 memory using 
dom0_mem. This is due to this FAQ entry: 
http://zfsonlinux.org/faq.html#CanIRunZFSForXenHypervisor . I use ZFS for 
virutal machine disks and other storage.
  The systems bios is not updated by manufacturer anymore (2013). The on board 
graphics card is used.
  Shared graphics memory is set to auto. Setting it to 128 MB didn't change 
anything.
  Using a wily kernel 4.2.0 generic or a 4.1.22 mainline kernel works.
  Using a mainline kernel 4.4.8 or 4.5.2 also crashes.
  A quick google search using the first crash report line leads to this
  https://lkml.org/lkml/2015/8/19/366
  and this
  http://code.metager.de/source/history/linux/stable/arch/x86/xen/
  I checked that the two patches that seem most relevant here are present in 
the ubuntu kernel.
  Workaround is to not force a particular amount of memory for dom0 (delete 
dom0_mem parameter)
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin8784 F pulseaudio
   /dev/snd/controlC1:  vmadmin8784 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (309 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro net.ifnames=0 rootwait rootdelay=30 usbcore.autosuspend=120 
usbcore.old_scheme_first=1 usbcore.initial_descriptor_timeout=60 
usb-storage.delay_use=10 console=hvc0 console=tty0 earlyprintk=xen quiet splash 
nomdmonddf nomdmonisw
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (7 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse libvirtd lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 04/23/2013
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: GA-78LMT-USB3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/23/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vmadmin7610 F pulseaudio
   /dev/snd/controlC1:  vmadmin7610 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=3352f7fa-317a-4ffc-8890-b1c7e45d183c
  InstallationDate: Installed on 2015-06-27 (332 days ago)
  InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 
(20150422.1)
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: placeholder root=UUID=0ccd0adc-fe68-4104-a524-6e1589a167df 
ro dom0_mem=8G,min:8G,max:8G net.ifnames=0 rootwait rootdelay=30 
usbcore.autosuspend=120 usbcore.old_scheme_first=1 
usbcore.initial_descriptor_timeout=60 usb-storage.delay_use=10 console=hvc0 
console=tty0 earlyprintk=xen quiet splash nomdmon

[Kernel-packages] [Bug 1498667] Re: [Toshiba P50W-B00F] Touchscreen no longer working

2016-05-24 Thread Robert Ancell
linux-
image-4.1.0-040100rc2-generic_4.1.0-040100rc2.201605231400_amd64.deb -
WWW

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

Title:
  [Toshiba P50W-B00F] Touchscreen no longer working

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

Bug description:
  Sometime in the last month or so my touchscreen stopped working on my
  Toshiba P50W. The dmesg log shows it constantly reconnecting to it:

  [  556.407964] usb 1-4: new full-speed USB device number 119 using xhci_hcd
  [  556.538341] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381
  [  556.538347] usb 1-4: New USB device strings: Mfr=4, Product=14, 
SerialNumber=0
  [  556.538349] usb 1-4: Product: Touchscreen
  [  556.538351] usb 1-4: Manufacturer: ELAN
  [  556.538505] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc 
says 80 microframes
  [  556.547788] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A1/input/input2374
  [  556.600478] hid-multitouch 0003:04F3:0381.04A1: input,hiddev0,hidraw4: USB 
HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0
  [  556.600584] usb 1-4: USB disconnect, device number 119

  [  556.860456] usb 1-4: new full-speed USB device number 120 using xhci_hcd
  [  556.990494] usb 1-4: New USB device found, idVendor=04f3, idProduct=0381
  [  556.990500] usb 1-4: New USB device strings: Mfr=4, Product=14, 
SerialNumber=0
  [  556.990503] usb 1-4: Product: Touchscreen
  [  556.990506] usb 1-4: Manufacturer: ELAN
  [  556.990755] usb 1-4: ep 0x2 - rounding interval to 64 microframes, ep desc 
says 80 microframes
  [  557.001248] input: ELAN Touchscreen as 
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:04F3:0381.04A2/input/input2376
  [  557.002517] hid-multitouch 0003:04F3:0381.04A2: input,hiddev0,hidraw4: USB 
HID v1.10 Device [ELAN Touchscreen] on usb-:00:14.0-4/input0
  [  557.013831] usb 1-4: USB disconnect, device number 120

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-11-generic 4.2.0-11.13
  ProcVersionSignature: Ubuntu 4.2.0-11.13-generic 4.2.1
  Uname: Linux 4.2.0-11-generic x86_64
  ApportVersion: 2.18.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bob2041 F pulseaudio
   /dev/snd/controlC0:  bob2041 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Sep 23 09:46:25 2015
  HibernationDevice: RESUME=UUID=5033984a-21af-482d-a1fd-c075e818cd12
  InstallationDate: Installed on 2013-12-26 (635 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: TOSHIBA Satellite P50W-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-11-generic 
root=UUID=885f0f10-b818-4eb4-8ff4-d067e16bef2f ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-11-generic N/A
   linux-backports-modules-4.2.0-11-generic  N/A
   linux-firmware1.148
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2013-12-26 (635 days ago)
  dmi.bios.date: 08/08/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.40:bd08/08/2014:svnTOSHIBA:pnSatelliteP50W-B:pvrPSVP2A-00F002:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite P50W-B
  dmi.product.version: PSVP2A-00F002
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_rea

2016-05-24 Thread Andrew
Joseph, commit 3d9f96d850e4bbfae24dc9aee03033dd77c81596 seems to be
good. Ready for the next one.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1575467

Title:
  [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-
  utopic-vy2yyy/linux-lts-
  utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743
  vlv_wait_port_ready+0x126/0x170 [i915]()

Status in linux package in Ubuntu:
  In Progress

Bug description:
  After upgrading from stock Ubuntu 14.04 to 16.04 my laptop
  consistently freezes up and is unresponsive to keyboard or mouse. The
  only way is to do a hard shutdown. I'm usually in a browser when this
  happens, and often watching a video or two. It seems to happen more
  often in Google Chrome than Firefox, but it happens with both. It has
  happened at least once with no videos loaded. I haven’t observed it
  freeze / hang when I’m not in a browser, but that's mainly what i use
  my laptop for, so that's where most of my time is spent.

  Call trace:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+attachment/4648682/+files/kern.log.2.gz

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrew 1949 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e8aaee7c-d956-4519-94f0-cf7aad745020
  InstallationDate: Installed on 2015-08-08 (263 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Inspiron 3451
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d01f07be-c906-4024-8eef-a58ba3935298 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0H4MK6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3451:pvrA00:rvnDellInc.:rn0H4MK6:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3451
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1582963] onibi (amd64) - tests ran: 18, failed: 5

2016-05-24 Thread Brad Figg
tests ran:  18, failed: 5;
  
http://kernel.ubuntu.com/testing/3.19.0-60.67~14.04.1/onibi__3.19.0-60.67~14.04.1__2016-05-24_18-46-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-60.67~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:
  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:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

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

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

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

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


[Kernel-packages] [Bug 1585366] [NEW] CVE-2016-4580

2016-05-24 Thread Steve Beattie
*** This bug is a security vulnerability ***

Public security bug reported:

The x25_negotiate_facilities function in net/x25/x25_facilities.c in the
Linux kernel before 4.5.5 does not properly initialize a certain data
structure, which allows attackers to obtain sensitive information from
kernel stack memory via an X.25 Call Request.

Break-Fix: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2
79e48650320e6fba48369fccf13fd045315b19b8

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

** Affects: linux-armadaxp (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-flo (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-goldfish (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-lts-quantal (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu)
 Importance: Low
 Status: Invalid

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

** Affects: linux-lts-utopic (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-mako (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-manta (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-snapdragon (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-ti-omap4 (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux-armadaxp (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux-flo (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Precise)
 Importance: Low
 Status: Invalid

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

** Affects: linux-lts-utopic (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-mako (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-manta (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-snapdragon (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-armadaxp (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-flo (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

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

** Affects: linux-lts-utopic (Ubuntu Trusty)
 Importance: Low
 Status: New

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

** Affects: linux-lts-wily (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-lts-xenial (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-mako (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-manta (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-snapdragon (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

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

** Affects: linux-armadaxp (Ubuntu Vivid)
 Importance: Undecided
 Sta

[Kernel-packages] [Bug 1584533] Re: Lenovo X220 unable to wlan after resume from sleep

2016-05-24 Thread Rudolf Leitgeb
** Attachment added: "dmesg file created with mainline kernel: reboot, 
sleep/wakeup + working wlan, sleep/wakeup + broken wlan"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584533/+attachment/4669693/+files/dmesg-flaky-mainline

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

Title:
  Lenovo X220 unable to wlan after resume from sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just upgraded to Ubuntu 16.04, and now whenever I wake up my laptop
  from sleep (hibernate doesn't work due to encrypted home directory), I
  am unable to connect to any wlan network. After a hot reboot or cold
  start everything is back to normal.

  Network manager would allow me to select already known wlan networks
  through "connect to hidden network", however, it would not allow me to
  establish the actual connection (connect button never becomes active).

  I will attach four files to this bug report:

  1. dmesg-pastreboot: dmesg after a hot reboot
  2. dmesg-pastsleep: dmesg after wakeup from sleep
  3. syslog-pastreboot: syslog snippet from timeframe after reboot
  4. syslog-pastsleep: syslog snippet from timeframe after wakeup from sleep

  Please let me know, if you need any further data or info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rudolf 2944 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 22 22:31:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-05-24 (1825 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MachineType: LENOVO 429135G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=080f751d-bbec-44b2-bd86-f4db52f4dddf ro quiet splash 
i915.semaphores=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-18 (4 days ago)
  dmi.bios.date: 04/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET42WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 429135G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET42WW(1.12):bd04/01/2011:svnLENOVO:pn429135G:pvrThinkPadX220:rvnLENOVO:rn429135G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 429135G
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1585364] Re: CVE-2014-8181

2016-05-24 Thread Steve Beattie
CVE-2014-8181

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

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

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

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

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

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

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

** Also affects: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

** Also affects: linux-ti-omap4 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

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

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

** Also affects: linux-ti-omap4 (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubun

[Kernel-packages] [Bug 1584533] Re: Lenovo X220 unable to wlan after resume from sleep

2016-05-24 Thread Rudolf Leitgeb
Thanks for your reply, before I followed your recommended steps I did a
system upgrade as recommended by ubuntu update manager. Since this also
updated systemd which is AFAIK pretty basic to the system, I tested both
after the upgrade AND after the switch to this mainline kernel you
recommended. Behavior became much stranger with the regular system
update, and in both cases (i.e. ubuntu kernel and mainline kernel) the
system behaved more or less the same, as far as wlan is concerned:

- After a reboot everything looks normal, wlan comes on even before
login, and stays intact after login. network manager applet in top bar
shows wlan networks plus the one I am connected to.

- After a sleep/wakeup, network manager shows loss of wlan connection.
No existing wlan networks are shown in wireless network list. Opening
"connect to hidden network" menu lists all networks I ever connected to,
but will not allow me to hit connect with any of them in the list,
connect button is grayed out.

- Now here comes the freaky part: in SOME of these instances I am
actually connected to my home wlan! This is not shown directly in
network manager, only after opening connection information window one
can see that there is a virbr0 device, and an active wlan0 device.

After many reboots and sleep/wakeup cycles with both kernels (ubuntu and
mainline), I can state that there is about a 50% likelyhood that wlan
becomes active, and that if wlan is active after one sleep/wakeup cycle,
chances are high that it will work in consecutive sleep/wakeup cycles.
In two cases (one for each kernel) I could create a special case: wlan
active after reboot, active again after sleep/wakeup, then inactive
after next sleep/wakeup. Since these cases yield a very compact dmesg
file, I post both of them here.

I hope this helps pinning down the issue, please let me know if you need
further data or tests.

Cheers,

Rudi

** Attachment added: "dmesg file created with regular ubuntu kernel: reboot, 
sleep/wakeup + working wlan, sleep/wakeup + broken wlan"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584533/+attachment/4669692/+files/dmesg-flaky-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/1584533

Title:
  Lenovo X220 unable to wlan after resume from sleep

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I just upgraded to Ubuntu 16.04, and now whenever I wake up my laptop
  from sleep (hibernate doesn't work due to encrypted home directory), I
  am unable to connect to any wlan network. After a hot reboot or cold
  start everything is back to normal.

  Network manager would allow me to select already known wlan networks
  through "connect to hidden network", however, it would not allow me to
  establish the actual connection (connect button never becomes active).

  I will attach four files to this bug report:

  1. dmesg-pastreboot: dmesg after a hot reboot
  2. dmesg-pastsleep: dmesg after wakeup from sleep
  3. syslog-pastreboot: syslog snippet from timeframe after reboot
  4. syslog-pastsleep: syslog snippet from timeframe after wakeup from sleep

  Please let me know, if you need any further data or info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rudolf 2944 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 22 22:31:10 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2011-05-24 (1825 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  MachineType: LENOVO 429135G
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=080f751d-bbec-44b2-bd86-f4db52f4dddf ro quiet splash 
i915.semaphores=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-05-18 (4 days ago)
  dmi.bios.date: 04/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET42WW (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 429135G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET42WW(1.12):bd04/01/2011:svnLENOVO:pn429135G:pvrThinkPadX220:rvnLENOVO:rn429135G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 429135G
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchp

[Kernel-packages] [Bug 1585364] [NEW] CVE-2014-8181

2016-05-24 Thread Steve Beattie
*** This bug is a security vulnerability ***

Public security bug reported:

In sg_io, blk_rq_map_user{,_iov} may allocate a set of bounce buffer
pages to do the bio, if it finds the user buffer cannot be directly
mapped. But the allocated pages are not cleared.  If the bounce buffer
is also not written to by device, garbage data is left, and copied back
to user in blk_rq_unmap_user.  The allocated pages should be cleared.
This also eliminates the risk of leaking sensitive information to
userspace, which may have a security impact.

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

** Affects: linux-armadaxp (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-flo (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-goldfish (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-lts-quantal (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu)
 Importance: Low
 Status: Invalid

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

** Affects: linux-lts-utopic (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-mako (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-manta (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-snapdragon (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-ti-omap4 (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux-armadaxp (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux-flo (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Precise)
 Importance: Low
 Status: Invalid

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

** Affects: linux-lts-utopic (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-mako (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-manta (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-snapdragon (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-armadaxp (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-flo (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

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

** Affects: linux-lts-utopic (Ubuntu Trusty)
 Importance: Low
 Status: New

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

** Affects: linux-lts-wily (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-lts-xenial (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-mako (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-manta (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-snapdragon (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux (Ubuntu Vivid)
 Importance: Undeci

[Kernel-packages] [Bug 1585366] Re: CVE-2016-4580

2016-05-24 Thread Steve Beattie
CVE-2016-4580

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

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

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

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

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

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

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

** Also affects: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

** Also affects: linux-ti-omap4 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

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

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

** Also affects: linux-ti-omap4 (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubun

[Kernel-packages] [Bug 1585365] Re: CVE-2016-4951

2016-05-24 Thread Steve Beattie
CVE-2016-4951

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

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

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

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

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

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

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

** Also affects: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

** Also affects: linux-ti-omap4 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

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

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

** Also affects: linux-ti-omap4 (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

** Changed in: linux-lts-trusty (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-trusty (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-wily (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-quantal (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-ti-omap4 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-raring (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-armadaxp (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-xenial (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-saucy (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-manta (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Xenial)
   Status: New => Invalid

** Changed in: linux-lts-vivid (Ubuntu Yakkety)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubuntu Precise)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubuntu Wily)
   Status: New => Invalid

** Changed in: linux-snapdragon (Ubun

[Kernel-packages] [Bug 1585365] [NEW] CVE-2016-4951

2016-05-24 Thread Steve Beattie
*** This bug is a security vulnerability ***

Public security bug reported:

The tipc_nl_publ_dump function in net/tipc/socket.c in the Linux kernel
through 4.6 does not verify socket existence, which allows local users
to cause a denial of service (NULL pointer dereference and system crash)
or possibly have unspecified other impact via a dumpit operation.

Break-Fix: 1a1a143daf84db95dd7212086042004a3abb7bc2
45e093ae2830cd1264677d47ff9a95a71f5d9f9c

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

** Affects: linux-armadaxp (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-flo (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-goldfish (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-lts-quantal (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu)
 Importance: Low
 Status: Invalid

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

** Affects: linux-lts-utopic (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-mako (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-manta (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-snapdragon (Ubuntu)
 Importance: Low
 Status: New

** Affects: linux-ti-omap4 (Ubuntu)
 Importance: Low
 Status: Invalid

** Affects: linux (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux-armadaxp (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux-flo (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Precise)
 Importance: Low
 Status: Invalid

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

** Affects: linux-lts-utopic (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-vivid (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-wily (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-xenial (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-mako (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-manta (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-snapdragon (Ubuntu Precise)
 Importance: Low
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Precise)
 Importance: Low
 Status: New

** Affects: linux (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-armadaxp (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-flo (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-goldfish (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-quantal (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-raring (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-lts-saucy (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

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

** Affects: linux-lts-utopic (Ubuntu Trusty)
 Importance: Low
 Status: New

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

** Affects: linux-lts-wily (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-lts-xenial (Ubuntu Trusty)
 Importance: Low
 Status: New

** Affects: linux-mako (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-manta (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-raspi2 (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-snapdragon (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

** Affects: linux-ti-omap4 (Ubuntu Trusty)
 Importance: Low
 Status: Invalid

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

** Affects: linux-armadaxp (Ubuntu Vivid)
 Importance: 

[Kernel-packages] [Bug 1585363] [NEW] BCM43xx support fails after upgradeto ubuntu 16.04.

2016-05-24 Thread Josy
Public bug reported:

I have upgraded to Ubuntu 16.04. few day after upgrading to Ubuntu
16.04., my internal broadcom wlan chipset did not work any longer. (Now
when writing this I use an USB wlan to access the internet.)

Due to whatever reasons the Broadcom 802.11 Linux STA wireless driver
source was installed. I removed it, but it did not help.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: firmware-b43-installer 1:019-2
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 24 22:35:07 2016
InstallationDate: Installed on 2015-09-05 (262 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: b43-fwcutter
UpgradeStatus: Upgraded to xenial on 2016-04-24 (29 days ago)

** Affects: b43-fwcutter (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  BCM43xx support fails after upgradeto ubuntu 16.04.

Status in b43-fwcutter package in Ubuntu:
  New

Bug description:
  I have upgraded to Ubuntu 16.04. few day after upgrading to Ubuntu
  16.04., my internal broadcom wlan chipset did not work any longer.
  (Now when writing this I use an USB wlan to access the internet.)

  Due to whatever reasons the Broadcom 802.11 Linux STA wireless driver
  source was installed. I removed it, but it did not help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firmware-b43-installer 1:019-2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May 24 22:35:07 2016
  InstallationDate: Installed on 2015-09-05 (262 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: b43-fwcutter
  UpgradeStatus: Upgraded to xenial on 2016-04-24 (29 days ago)

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

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


[Kernel-packages] [Bug 1583962] Re: CVE-2016-4913

2016-05-24 Thread Steve Beattie
** Changed in: linux (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  CVE-2016-4913

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

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

2016-05-24 Thread Brad Figg
tests ran:   4, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-60.67~14.04.1/onza__3.19.0-60.67~14.04.1__2016-05-24_20-41-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-60.67~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:
  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:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

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

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

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

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


[Kernel-packages] [Bug 1579610] Re: drm.ko < kernel version 4.5 has a dead lock bug

2016-05-24 Thread Kamal Mostafa
Hi Qiang Yu-

Can you confirm that the kernel version in -proposed fixes this problem
on your system?  Thanks!

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

Title:
  drm.ko < kernel version 4.5 has a dead lock bug

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  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
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  This bug go the code path
  drvers/gpu/drm/{drm_prime.c,drm_gem.c}

  drm_gem_prime_fd_to_handle()
  | mutex_lock(&file_priv->prime.lock);
  | drm_gem_handle_create_tail()
  | | dev->driver->gem_open_object() (for amdgpu.ko driver, this is 
amdgpu_gem_object_open)
  | | drm_gem_handle_delete()
  | | | drm_gem_remove_prime_handles()
  | | | | mutex_lock(&filp->prime.lock);

  This causes the dead lock if gem_open_object() return with error.

  Patch fixing this is already in Linux 4.5:
  
https://github.com/torvalds/linux/commit/6984128d01cf935820a0563f3a00c6623ba58109

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-generic 4.4.0.22.23
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yuq1566 F pulseaudio
   /dev/snd/controlC1:  yuq1566 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon May  9 11:20:26 2016
  HibernationDevice: RESUME=UUID=2e71a82b-c613-4a96-88e3-0672a366c396
  InstallationDate: Installed on 2016-03-01 (69 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160228)
  IwConfig:
   enp7s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. X58A-UD3R
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=c137e0c1-ad99-47f4-acf5-e7f4792afa9e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FE
  dmi.board.name: X58A-UD3R
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFE:bd12/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: X58A-UD3R
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


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

2016-05-24 Thread Brad Figg
tests ran:   4, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-60.67~14.04.1/onza__3.19.0-60.67~14.04.1__2016-05-24_20-22-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-60.67~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:
  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:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

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

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

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

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


[Kernel-packages] [Bug 1574721] Re: IRQ Storm during Mate 16.04 install

2016-05-24 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

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

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

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


Thanks in advance.

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

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

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

Title:
  IRQ Storm during Mate 16.04 install

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is odd - and it appears to be in the kernel but since I'm still
  feeling my way around I thought someone here would be able to send it
  to the right place.

  This issue affected a 15" Macbook Pro running kernel 4.4.0.15 on T7400
  Dual Core 2.16 GHz with Radeon graphics. It's quite an elderly machine
  and suitable for a more modern OS since Apple no longer supports it.

  When running the live disk I noticed the mouse was "sluggish" and
  eventually the whole thing ground to a shuddering stop. On second try,
  I switched on all the normal options and got it installed to the hard
  drive but I could not even log onto a terminal (switching from GUI to
  a console).

  Third time I switched the CD into text mode by appending the "TEXT"
  switch (removing QUIET and NOSPLASH) and ran the live disk: what do
  you know, it worked like a charm, installed without any incidents and
  rebooted correctly.

  I'm currently upgrading the system to see if that creates any further
  issues.

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

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


[Kernel-packages] [Bug 1574721] [NEW] IRQ Storm during Mate 16.04 install

2016-05-24 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

This is odd - and it appears to be in the kernel but since I'm still
feeling my way around I thought someone here would be able to send it to
the right place.

This issue affected a 15" Macbook Pro running kernel 4.4.0.15 on T7400
Dual Core 2.16 GHz with Radeon graphics. It's quite an elderly machine
and suitable for a more modern OS since Apple no longer supports it.

When running the live disk I noticed the mouse was "sluggish" and
eventually the whole thing ground to a shuddering stop. On second try, I
switched on all the normal options and got it installed to the hard
drive but I could not even log onto a terminal (switching from GUI to a
console).

Third time I switched the CD into text mode by appending the "TEXT"
switch (removing QUIET and NOSPLASH) and ran the live disk: what do you
know, it worked like a charm, installed without any incidents and
rebooted correctly.

I'm currently upgrading the system to see if that creates any further
issues.

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


** Tags: bot-comment
-- 
IRQ Storm during Mate 16.04 install 
https://bugs.launchpad.net/bugs/1574721
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


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

2016-05-24 Thread Brad Figg
tests ran:  13, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-60.67~14.04.1/onza__3.19.0-60.67~14.04.1__2016-05-24_18-43-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-60.67~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:
  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:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

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

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

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

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


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

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

apport-collect 1574721

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

Title:
  IRQ Storm during Mate 16.04 install

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This is odd - and it appears to be in the kernel but since I'm still
  feeling my way around I thought someone here would be able to send it
  to the right place.

  This issue affected a 15" Macbook Pro running kernel 4.4.0.15 on T7400
  Dual Core 2.16 GHz with Radeon graphics. It's quite an elderly machine
  and suitable for a more modern OS since Apple no longer supports it.

  When running the live disk I noticed the mouse was "sluggish" and
  eventually the whole thing ground to a shuddering stop. On second try,
  I switched on all the normal options and got it installed to the hard
  drive but I could not even log onto a terminal (switching from GUI to
  a console).

  Third time I switched the CD into text mode by appending the "TEXT"
  switch (removing QUIET and NOSPLASH) and ran the live disk: what do
  you know, it worked like a charm, installed without any incidents and
  rebooted correctly.

  I'm currently upgrading the system to see if that creates any further
  issues.

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

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


[Kernel-packages] [Bug 1423672] Re: ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor inconsistent: X vs Y

2016-05-24 Thread Kamal Mostafa
Anyone affected by this issue:  We're looking for a positive
verification that the Trusty kernel version currently available in
-proposed (3.13.0-87.132) fixes this problem.  If you can provide that
confirmation, please do!

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

Title:
  ext4_mb_generate_buddy:756: group N, block bitmap and bg descriptor
  inconsistent: X vs Y

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux package in Debian:
  Confirmed

Bug description:
   SRU Justification:

  Impact: Users of VMs running 3.13/3.16 and ext4 can experience data 
corruption in the guest.
  Fix: 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?h=7dec5603b6b8dc4c3e1c65d318bd2a5a8c62a424
  Testcase: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818502#22

  --

  I noticed that one of my VM had this "dmesg -T" output:

  [Tue Feb 17 09:53:27 2015] systemd-udevd[5433]: starting version 204
  [Thu Feb 19 06:25:08 2015] EXT4-fs error (device vda1): 
ext4_mb_generate_buddy:756: group 5, block bitmap and bg descriptor 
inconsistent: 16446 vs 16445 free clusters
  [Thu Feb 19 06:25:09 2015] Aborting journal on device vda1-8.
  [Thu Feb 19 06:25:09 2015] EXT4-fs (vda1): Remounting filesystem read-only
  [Thu Feb 19 06:25:09 2015] [ cut here ]
  [Thu Feb 19 06:25:09 2015] WARNING: CPU: 0 PID: 9946 at 
/build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 
__ext4_handle_dirty_metadata+0x1a2/0x1c0()
  [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 
nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables 
x_tables serio_raw psmouse floppy
  [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Not tainted 
3.13.0-45-generic #74-Ubuntu
  [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
  [Thu Feb 19 06:25:09 2015]  0009 880003a11aa0 
81720eb6 
  [Thu Feb 19 06:25:09 2015]  880003a11ad8 810677cd 
88c41340 
  [Thu Feb 19 06:25:09 2015]  88000a58e000 81835280 
1302 880003a11ae8
  [Thu Feb 19 06:25:09 2015] Call Trace:
  [Thu Feb 19 06:25:09 2015]  [] dump_stack+0x45/0x56
  [Thu Feb 19 06:25:09 2015]  [] 
warn_slowpath_common+0x7d/0xa0
  [Thu Feb 19 06:25:09 2015]  [] warn_slowpath_null+0x1a/0x20
  [Thu Feb 19 06:25:09 2015]  [] 
__ext4_handle_dirty_metadata+0x1a2/0x1c0
  [Thu Feb 19 06:25:09 2015]  [] ? ext4_dirty_inode+0x2a/0x60
  [Thu Feb 19 06:25:09 2015]  [] ext4_free_blocks+0x646/0xbf0
  [Thu Feb 19 06:25:09 2015]  [] ? wake_up_bit+0x25/0x30
  [Thu Feb 19 06:25:09 2015]  [] ext4_ext_rm_leaf+0x505/0x8f0
  [Thu Feb 19 06:25:09 2015]  [] ? 
__ext4_ext_check+0x197/0x370
  [Thu Feb 19 06:25:09 2015]  [] ? 
ext4_ext_remove_space+0xc0/0x7e0
  [Thu Feb 19 06:25:09 2015]  [] 
ext4_ext_remove_space+0x31c/0x7e0
  [Thu Feb 19 06:25:09 2015]  [] ext4_ext_truncate+0xb0/0xe0
  [Thu Feb 19 06:25:09 2015]  [] ext4_truncate+0x379/0x3c0
  [Thu Feb 19 06:25:09 2015]  [] ext4_evict_inode+0x408/0x4d0
  [Thu Feb 19 06:25:09 2015]  [] evict+0xb0/0x1b0
  [Thu Feb 19 06:25:09 2015]  [] iput+0xf5/0x180
  [Thu Feb 19 06:25:09 2015]  [] __dentry_kill+0x1a8/0x200
  [Thu Feb 19 06:25:09 2015]  [] dput+0xa5/0x180
  [Thu Feb 19 06:25:09 2015]  [] __fput+0x176/0x260
  [Thu Feb 19 06:25:09 2015]  [] fput+0xe/0x10
  [Thu Feb 19 06:25:09 2015]  [] task_work_run+0xa7/0xe0
  [Thu Feb 19 06:25:09 2015]  [] do_notify_resume+0x97/0xb0
  [Thu Feb 19 06:25:09 2015]  [] int_signal+0x12/0x17
  [Thu Feb 19 06:25:09 2015] ---[ end trace ebff9843d81b5c41 ]---
  [Thu Feb 19 06:25:09 2015] BUG: unable to handle kernel NULL pointer 
dereference at 0028
  [Thu Feb 19 06:25:09 2015] IP: [] 
__ext4_error_inode+0x31/0x160
  [Thu Feb 19 06:25:09 2015] PGD 167067 PUD 161067 PMD 0
  [Thu Feb 19 06:25:09 2015] Oops:  [#1] SMP
  [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 
nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables 
x_tables serio_raw psmouse floppy
  [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Tainted: G
W 3.13.0-45-generic #74-Ubuntu
  [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
  [Thu Feb 19 06:25:09 2015] task: 880009ac4800 ti: 880003a1 
task.ti: 880003a1
  [Thu Feb 19 06:25:09 2015] RIP: 0010:[]  
[] __ext4_error_inode+0x31/0x160
  [Thu Feb 19 06:25:09 2015]

[Kernel-packages] [Bug 1584195] Re: IMA-appraisal is still unusable in Ubuntu 16.04

2016-05-24 Thread Mehmet Kayaalp
I submitted them on April 8. I will resubmit in a couple of weeks for
the next -rc period. But when it reaches linux-next is up to the
keyrings maintainer (David Howells ).

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

Title:
  IMA-appraisal is still unusable in Ubuntu 16.04

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

Bug description:
  A recent bug (Bug #1558553) that renders IMA and trusted keyrings
  unusable was prematurely marked as fixed. The bug report was missing a
  couple of minor fixes which are attached. These patches are also
  submitted to LSM and keyrings mailing lists to be upstreamed.

  * KEYS: Insert incompressible bytes to vmlinux to reserve space in bzImage
  * KEYS: Print insert-sys-cert information to stout instead of stderr

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

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


[Kernel-packages] [Bug 1242321] Re: USB 3.0 Harddrive not recognised

2016-05-24 Thread Skiold
Hi, I've installed Ubuntu-Gnome 16.04 yesterday on my HP-ProDesk-PC, dual boot 
with Windows 10.
This computer has four USB 3.0 ports and two USB 2.0 ports. 
Same problem here with Ubuntu partition, not in Windows 10 partition. 
My external Toshiba HDD seems to have power, it is rotating and blinking, but 
it is recognized immediately only on USB 2.0 ports, not in USB 3.0 ports.
After rebooting system, USB 3.0 ports works fine but only just one time. If you 
unmount the device the problem starts again.
Another detail: On USB 2.0 ports the Toshiba HDD blinks in white light; on USB 
3.0 ports blinks in blue light (such in Ubuntu as in Windows).

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

Title:
  USB 3.0 Harddrive not recognised

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu is not recognising any device plugged into any USB 3.0 ports.
  Sometimes Ubuntu will freeze for a few seconds when you plug something
  into a USB 3.0 port; when Ubuntu comes out of the freeze, the device
  is still NOT recognised.

  No problems with USB 2.0 ports and devices.

  The USB 3.0 on this computer only works in Windows 7 (I'm dual booting
  Ubuntu 13.10 and Windows 7, both are 64-bit).

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

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


[Kernel-packages] [Bug 1583817] Re: WARNING: CPU: 1 PID: 865 at /home/kernel/COD/linux/drivers/gpu/drm/drm_irq.c:1326 drm_wait_one_vblank+0x1b0/0x1c0 [drm]

2016-05-24 Thread Oliver Leitner
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  WARNING: CPU: 1 PID: 865 at
  /home/kernel/COD/linux/drivers/gpu/drm/drm_irq.c:1326
  drm_wait_one_vblank+0x1b0/0x1c0 [drm]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My HP Compaq 610 has an Intel card built in: 00:02.0 VGA compatible 
controller: Intel Corporation Mobile GME965/GLE960 Integrated Graphics 
Controller (rev 0c)
  running ubuntu lts 16.04, i receive the following errors in the log file, 
which might correspondent to overheating problems with that laptop:
  [8.176079] [ cut here ]
  [8.176121] WARNING: CPU: 1 PID: 865 at 
/home/kernel/COD/linux/drivers/gpu/drm/drm_irq.c:1326 
drm_wait_one_vblank+0x1b0/0x1c0 [drm]
  [8.176123] vblank wait timed out on crtc 0
  [8.176125] Modules linked in: snd_usb_audio snd_usbmidi_lib hp_wmi 
sparse_keymap snd_hda_codec_hdmi snd_hda_codec_idt snd_hda_codec_generic 
snd_hda_intel
   snd_hda_codec coretemp snd_hda_core snd_hwdep snd_pcm arc4 snd_seq_midi 
snd_seq_midi_event iwldvm mac80211 joydev snd_rawmidi input_leds snd_seq 
serio_raw s
  nd_seq_device iwlwifi snd_timer cfg80211 snd lpc_ich shpchp soundcore 
8250_fintek tpm_infineon hp_accel lis3lv02d input_polldev mac_hid squashfs 
parport_pc p
  pdev lp parport sunrpc autofs4 hid_generic usbhid hid i915 i2c_algo_bit 
psmouse drm_kms_helper syscopyarea ahci sysfillrect sysimgblt libahci 
fb_sys_fops drm
   sky2 fjes video wmi
  [8.176180] CPU: 1 PID: 865 Comm: Xorg Tainted: G U  W   
4.6.0-999-lowlatency #201605152200
  [8.176182] Hardware name: Hewlett-Packard Compaq 610/308A, BIOS 68PVU 
Ver. F.20 12/01/2011
  [8.176184]  0286 fd341e93 8800b948f880 
813fbcb1
  [8.176189]  8800b948f8d0  8800b948f8c0 
810841fb
  [8.176192]  052e0200 88003586e000  

  [8.176196] Call Trace:
  [8.176203]  [] dump_stack+0x63/0x82
  [8.176207]  [] __warn+0xcb/0xf0
  [8.176210]  [] warn_slowpath_fmt+0x5a/0x80
  [8.176231]  [] drm_wait_one_vblank+0x1b0/0x1c0 [drm]
  [8.176235]  [] ? wake_atomic_t_function+0x60/0x60
  [8.176280]  [] i9xx_crtc_disable+0x3d/0x450 [i915]
  [8.176307]  [] ? intel_crtc_disable_planes+0xdc/0xf0 
[i915]
  [8.176335]  [] intel_atomic_commit+0x442/0xdb0 [i915]
  [8.176362]  [] ? intel_atomic_check+0x230/0x830 [i915]
  [8.176380]  [] drm_atomic_commit+0x37/0x60 [drm]
  [8.176408]  [] intel_release_load_detect_pipe+0x23/0x80 
[i915]
  [8.176436]  [] intel_tv_detect+0x355/0x640 [i915]
  [8.176451]  [] 
drm_helper_probe_single_connector_modes+0x33b/0x510 [drm_kms_helper]
  [8.176457]  [] ? 
drm_helper_probe_single_connector_modes+0x33b/0x510 [drm_kms_helper]
  [8.176474]  [] drm_mode_getconnector+0x31f/0x370 [drm]
  [8.176488]  [] drm_ioctl+0x123/0x4b0 [drm]
  [8.176504]  [] ? drm_mode_getcrtc+0x140/0x140 [drm]
  [8.176508]  [] do_vfs_ioctl+0xa1/0x5b0
  [8.176511]  [] ? __fget+0x77/0xb0
  [8.176514]  [] SyS_ioctl+0x79/0x90
  [8.176517]  [] entry_SYSCALL_64_fastpath+0x1e/0xa8
  [8.176527] ---[ end trace 39c3d2edaf946884 ]---

  installing the following sped things up a bit but didn't solve the kernel 
panic:
  Intel's proprietary drivers
  mainline
  drm-next
  intel-drm-next
  daily

  ---
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Mobile GME965/GLE960 Integrated Graphics Controller 
[8086:2a12] (rev 0c) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Mobile GME965/GLE960 Integrated 
Graphics Controller [103c:308a]
     Subsystem: Hewlett-Packard Company Mobile GME965/GLE960 Integrated 
Graphics Controller [103c:308a]
  MachineType: Hewlett-Packard Compaq 610
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.6.0-999-lowlatency 
root=UUID=42086018-f6c6-44be-8d35-01b0bd8c2533 ro "acpi_os_name=Microsoft 
Windows NT" acpi_sci=low agp=off consoleblank=0 enable_mtrr_cleanup 
enable_timer_pin_1 iomem=relaxed intel_iommu=on kvm-intel.nested=1 
memory_corruption_check=0 no_timer_check 
pci=routeirq,skip_isa_align,pcie_bus_peer2peer,realloc,pcie_scan_all 
reset_devices rootwait i915.enable_execlists=0 i915.enable_rc6=0 
i915.en

[Kernel-packages] [Bug 1574721] Re: IRQ Storm during Mate 16.04 install

2016-05-24 Thread Paul White
** 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/1574721

Title:
  IRQ Storm during Mate 16.04 install

Status in linux package in Ubuntu:
  New

Bug description:
  This is odd - and it appears to be in the kernel but since I'm still
  feeling my way around I thought someone here would be able to send it
  to the right place.

  This issue affected a 15" Macbook Pro running kernel 4.4.0.15 on T7400
  Dual Core 2.16 GHz with Radeon graphics. It's quite an elderly machine
  and suitable for a more modern OS since Apple no longer supports it.

  When running the live disk I noticed the mouse was "sluggish" and
  eventually the whole thing ground to a shuddering stop. On second try,
  I switched on all the normal options and got it installed to the hard
  drive but I could not even log onto a terminal (switching from GUI to
  a console).

  Third time I switched the CD into text mode by appending the "TEXT"
  switch (removing QUIET and NOSPLASH) and ran the live disk: what do
  you know, it worked like a charm, installed without any incidents and
  rebooted correctly.

  I'm currently upgrading the system to see if that creates any further
  issues.

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

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


[Kernel-packages] [Bug 1581326] Re: Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

2016-05-24 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Xenial)
   Status: Incomplete => Triaged

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

** Tags added: needs-reverse-bisect

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

Title:
  Kernel crashed while Creating a second RAID volume on Ubuntu 16.04 OS.

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

Bug description:
  Booted into Ubuntu16.04(4.4.0-21-generic) OS with inbox driver-
  v12.100.00.00,

  Successfully discovered HBA and the devices connected to HBA.
  >>Launched SAS3IRCU utility and created a RAID volume (RAID0/RAID1/RAID10). 
volume successfully created and listed from SAS3IRCU utility.
  >>Tried to create a second RAID volume (RAID0/RAID1/RAID10) from SAS3IRCU 
utility. 
  Kernel crashed here while creating second volume.
  >>tried with all possible combinations of RAID volumes.

  Please find the attached kernel crash logs.

  >>cat /proc/version_signature 
  Ubuntu 4.4.0-21.37-generic 4.4.6 

  HBA used : LSI SAS3(Fury)

  Issue : Kernel gets crashed , when tried creating 2nd RAID volume.
  Expected : One should be able to create MAX 2 RAID volumes at any point of 
time successfully , without any kernel crash.
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/28/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.0b
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X9DRH-7TF/7F/iTF/iF
  dmi.board.vendor: Supermicro
  dmi.board.version: 1234567890
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 1234567890
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnSupermicro:pnX9DRH-7TF/7F/iTF/iF:pvr1234567890:rvnSupermicro:rnX9DRH-7TF/7F/iTF/iF:rvr1234567890:cvnSupermicro:ct3:cvr1234567890:
  dmi.product.name: X9DRH-7TF/7F/iTF/iF
  dmi.product.version: 1234567890
  dmi.sys.vendor: Supermicro
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=7f36ec0c-c34b-4750-bd78-2c394cc513b2
  InstallationDate: Installed on 2016-05-11 (1 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  IwConfig:
   enp5s0f0  no wireless extensions.
   
   enp5s0f1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Supermicro X9DRH-7TF/7F/iTF/iF
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=8f5b571b-235f-4881-8344-dfaa2bd9ed48 ro
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: XDG_RUNTIME_DIR 
(/run/user/1000) is not owned by us (uid 0), but by uid 1000! (This could e g 
happen if you try to connect to a non-root PulseAudio as a root user, over the 
native protocol. Don't do that.)
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  RfKill:
   
  Tags:  xenial

[Kernel-packages] [Bug 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_rea

2016-05-24 Thread Richard Baka
BzukTuk 2016-02-01 22:06:32 UTC

Created attachment 202701 [details]
Kernel bisection between v4.2 v4.1 for sudden freezes

Hi, small update.

My first bisect was from 4.1 to 4.2-rc1 and as first bad commit
[cf5d8a46a001c9421c7397699db55f962e0410fc] was flagged. But I was not so
sure that i did the bisection properly.

So today I made second bisection - git bisect start v4.2 v4.1. Bisection
process went without problem/confusion/doubt (as my first attempt did).
Last git bisect was good on commit
cf5d8a46a001c9421c7397699db55f962e0410fc (after 90 minutes of glxgears
and vlc). Git pointed that first bad commit was:

[8fb55197e64d5988ec57b54e973daeea72c3f2ff] drm/i915: Agressive
downclocking on Baytrail

then from commit cf5d8a46.. I cherry-picked 8fb55197 and this kernel
froze after 3 minutes.

More cherry-picking/testing tomorrow. Sorry if my previous post made 
confusion/unnecessary work.
Todays 'git bisect log' is in the attachment

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1575467

Title:
  [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-
  utopic-vy2yyy/linux-lts-
  utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743
  vlv_wait_port_ready+0x126/0x170 [i915]()

Status in linux package in Ubuntu:
  In Progress

Bug description:
  After upgrading from stock Ubuntu 14.04 to 16.04 my laptop
  consistently freezes up and is unresponsive to keyboard or mouse. The
  only way is to do a hard shutdown. I'm usually in a browser when this
  happens, and often watching a video or two. It seems to happen more
  often in Google Chrome than Firefox, but it happens with both. It has
  happened at least once with no videos loaded. I haven’t observed it
  freeze / hang when I’m not in a browser, but that's mainly what i use
  my laptop for, so that's where most of my time is spent.

  Call trace:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+attachment/4648682/+files/kern.log.2.gz

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrew 1949 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e8aaee7c-d956-4519-94f0-cf7aad745020
  InstallationDate: Installed on 2015-08-08 (263 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Inspiron 3451
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d01f07be-c906-4024-8eef-a58ba3935298 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0H4MK6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3451:pvrA00:rvnDellInc.:rn0H4MK6:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3451
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1577905] Re: Dell TB15 audio is distorted

2016-05-24 Thread Kamal Mostafa
Fixed via upstream cc: stable; verification not required.

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

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

Title:
  Dell  TB15 audio is distorted

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  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 Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  On the Dell TB15 and Dell WD15 docks, analogue audio output is
  distorted.  This is because of a missing driver quirk on docks.

  It has been fixed upstream here.
  
http://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=adcdd0d5a1cb779f6d455ae70882c19c527627a8

  Please backport it into Ubuntu.

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

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


[Kernel-packages] [Bug 1585315] Re: linux: 3.13.0-87.133 -proposed tracker

2016-05-24 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

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

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

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

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

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

** Description changed:

  This bug is for tracking the 3.13.0-87.133 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-phase-changed:Tuesday, 24. May 2016 19:02 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the 3.13.0-87.133 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-phase-changed:Tuesday, 24. May 2016 19:02 UTC
  kernel-stable-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 3.13.0-87.133 -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:
  Invalid
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:
  New

Bug description:
  This bug is for tracking the 3.13.0-87.133 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-phase-changed:Tuesday, 24. May 2016 19:02 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1584475] Re: No input events for FutureMax Dance Mat

2016-05-24 Thread Xaratas
Ok, tested a bit further. upstream kernel 3.15 generates the input events, but 
the event devices is only accessible for root.
But thats not a problem as there is also a js0 device which is picked up by 
stempania and works fine.

uname -a
Linux Y4e 3.15.0-031500-generic #201406131105 SMP Fri Jun 13 15:06:46 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

ls -l /dev/input/event15
crw-rw 1 root input 13, 79 Mai 24 20:12 /dev/input/event15
ls -al /dev/input/js0 
crw-rw-r-- 1 root input 13, 0 Mai 24 20:46 /dev/input/js0


sudo evtest output:
Event: time 1464115604.587967, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90007
Event: time 1464115604.587967, type 1 (EV_KEY), code 294 (BTN_BASE), value 0
Event: time 1464115604.587967, -- SYN_REPORT 
Event: time 1464115611.017624, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1464115611.017624, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 1
Event: time 1464115611.017624, -- SYN_REPORT 
Event: time 1464115611.104563, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90001
Event: time 1464115611.104563, type 1 (EV_KEY), code 288 (BTN_TRIGGER), value 0
Event: time 1464115611.104563, -- SYN_REPORT 
Event: time 1464115615.113371, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003
Event: time 1464115615.113371, type 1 (EV_KEY), code 290 (BTN_THUMB2), value 1
Event: time 1464115615.113371, -- SYN_REPORT 
Event: time 1464115615.295383, type 4 (EV_MSC), code 4 (MSC_SCAN), value 90003
Event: time 1464115615.295383, type 1 (EV_KEY), code 290 (BTN_THUMB2), value 0


upstream kernel 3.17.0 generates some events, but these are spoty and
unreliable. The dancemat is not working in Stepmania.

uname -a
Linux Y4e 3.17.0-031700-generic #201410060605 SMP Mon Oct 6 10:07:09 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

evtest output: if one event appears, then there are huge repetitions of these 0 
values which, from the name dose not make much sense for a dance pad, which has 
no orientation or analog positon x and y.
Event: time 1464115318.219259, -- SYN_REPORT 
Event: time 1464115318.220260, type 3 (EV_ABS), code 48 (ABS_MT_TOUCH_MAJOR), 
value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 49 (ABS_MT_TOUCH_MINOR), 
value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 50 (ABS_MT_WIDTH_MAJOR), 
value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 51 (ABS_MT_WIDTH_MINOR), 
value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 52 (ABS_MT_ORIENTATION), 
value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 53 (ABS_MT_POSITION_X), 
value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 54 (ABS_MT_POSITION_Y), 
value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 55 (ABS_MT_TOOL_TYPE), 
value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 56 (ABS_MT_BLOB_ID), value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 57 (ABS_MT_TRACKING_ID), 
value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 58 (ABS_MT_PRESSURE), 
value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 59 (ABS_MT_DISTANCE), 
value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 60 (ABS_MT_TOOL_X), value 0
Event: time 1464115318.220260, type 3 (EV_ABS), code 61 (ABS_MT_TOOL_Y), value 0

3.19.8 has the bug

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

Title:
  No input events for FutureMax Dance Mat

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my ubuntu booth of my FutureMax Dance Mats does not generate any input 
events. So they can not be used. The hardware is working, i verified this with 
a windows PC.
  The missing events were checked with cat /dev/input/eventX, evtest, xev.

  On ubuntu the device is set up (udevadm has it, dmesg has it, evtest
  sees it), module joydev is loaded but no input is recognized/ visible
  and /dev/input/eventX

  Expected behavior: Plug and Play with the usb Dance Mat
  Acutal behavior: No play possible as no input events appear and so the game 
can not use it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xar2249 F pulseaudio
   /dev/snd/controlC0:  xar2249 F pulseaudio
  CurrentDesktop: MATE
  Date: Sun May 22 15:29:57 2016
  HibernationDevice: RESUME=UUID=d68a39e5-b419-4307-9af9-6eeda8990336
  MachineType: Sony Corporation VPCZ12C5E
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=18e98aae-17c4-4d7d-80db-421236684825 ro quiet splash
  RelatedPackageVersion

[Kernel-packages] [Bug 1547619] Re: Intermittent screen blinking with 4k external mini display port with 4.4 kernels

2016-05-24 Thread Joseph Salisbury
I built the next test kernel, up to the following commit:
1c431cb4615334fb81c0d1c0ede21aa4354c1187

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

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

Title:
  Intermittent screen blinking with 4k external mini display port with
  4.4 kernels

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

Bug description:
  When using an external 4K monitor plugged into the mini display port on my 
Dell XPS 13 9343 using both the laptop screen and the external monitor 
(external monitor is left and laptop screen right), when using all of the 
following kernels:
  4.4.0-2.16-generic
  4.4.0-4.19-generic
  4.4.0-6.21-generic
  4.4.0-7.22-generic

  the external monitor will sometimes blink off for about a second or
  two, then back on. What is weird is this seems to only happen when
  typing into a gnome-terminal as opposed to firefox or evolution.
  Simply changing to a gnome-terminal and typing into it doesn't cause
  the blinking, but it might happen immediately or it might take several
  minutes.

  4.3.0-7.18-generic worked fine and I can go hours and hours in a
  gnome-terminal with no issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-6-generic 4.4.0-6.21
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jamie  5882 F pulseaudio
   /dev/snd/controlC1:  jamie  5882 F pulseaudio
   /dev/snd/controlC0:  jamie  5882 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb 19 12:09:28 2016
  HibernationDevice: RESUME=UUID=27fa6713-c8c2-4eb8-9766-ba6918bc1cfb
  InstallationDate: Installed on 2015-06-13 (250 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic.efi.signed 
root=UUID=7bc4dcd2-0bd8-4e42-b8b7-9f1ed6b8a3e9 ro libata.force=noncq kaslr 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-6-generic N/A
   linux-backports-modules-4.4.0-6-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-01-12 (38 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1575467] Re: [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-utopic-vy2yyy/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743 vlv_wait_port_rea

2016-05-24 Thread Joseph Salisbury
I built the next test kernel, up to the following commit:
3d9f96d850e4bbfae24dc9aee03033dd77c81596

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

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 the bug report.
https://bugs.launchpad.net/bugs/1575467

Title:
  [Dell Inspiron 3451] WARNING: CPU: 1 PID: 1297 at /build/linux-lts-
  utopic-vy2yyy/linux-lts-
  utopic-3.16.0/drivers/gpu/drm/i915/intel_display.c:1743
  vlv_wait_port_ready+0x126/0x170 [i915]()

Status in linux package in Ubuntu:
  In Progress

Bug description:
  After upgrading from stock Ubuntu 14.04 to 16.04 my laptop
  consistently freezes up and is unresponsive to keyboard or mouse. The
  only way is to do a hard shutdown. I'm usually in a browser when this
  happens, and often watching a video or two. It seems to happen more
  often in Google Chrome than Firefox, but it happens with both. It has
  happened at least once with no videos loaded. I haven’t observed it
  freeze / hang when I’m not in a browser, but that's mainly what i use
  my laptop for, so that's where most of my time is spent.

  Call trace:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1575467/+attachment/4648682/+files/kern.log.2.gz

  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  andrew 1949 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e8aaee7c-d956-4519-94f0-cf7aad745020
  InstallationDate: Installed on 2015-08-08 (263 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. Inspiron 3451
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=d01f07be-c906-4024-8eef-a58ba3935298 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (4 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 12/05/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: 0H4MK6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd12/05/2014:svnDellInc.:pnInspiron3451:pvrA00:rvnDellInc.:rn0H4MK6:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3451
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1585311] Re: [Hyper-V] Put tools/hv/lsvmbus in /usr/sbin

2016-05-24 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

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

** Tags added: kernel-hyper-v

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

Title:
  [Hyper-V] Put tools/hv/lsvmbus in /usr/sbin

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Similar to the Hyper-V daemons that are in cloud-tools, please place
  the python script "lsvmbus" from the Linux kernel source tree in
  tools/hv in /usr/sbin

  This script will show the devices on the Hyper-V vmbus.

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

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


[Kernel-packages] [Bug 1582963] onibi (i386) - tests ran: 4, failed: 0

2016-05-24 Thread Brad Figg
tests ran:   4, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-60.67~14.04.1/onibi__3.19.0-60.67~14.04.1__2016-05-24_18-30-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-60.67~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:
  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:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

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

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

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

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


[Kernel-packages] [Bug 1582963] onza (amd64) - tests ran: 40, failed: 1

2016-05-24 Thread Brad Figg
tests ran:  40, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-60.67~14.04.1/onza__3.19.0-60.67~14.04.1__2016-05-24_16-55-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-60.67~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:
  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:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

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

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

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

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


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

2016-05-24 Thread Joshua R. Poulson
I have verified that 4.4.0-22 does not balloon memory back to Hyper-V
and 4.4.0-21 does. We are investigating, but there doesn't seem to be a
lot of Hyper-V changes that relate to memory between these two kernels.

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

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

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

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

  
  Steps to reproduce:

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

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

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

  Environment:
  Host: Windows NanoServer 2016

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

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

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


[Kernel-packages] [Bug 1585311] Re: [Hyper-V] Put tools/hv/lsvmbus in /usr/sbin

2016-05-24 Thread Joshua R. Poulson
No logs required, upstream commit request.

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

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

Title:
  [Hyper-V] Put tools/hv/lsvmbus in /usr/sbin

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Similar to the Hyper-V daemons that are in cloud-tools, please place
  the python script "lsvmbus" from the Linux kernel source tree in
  tools/hv in /usr/sbin

  This script will show the devices on the Hyper-V vmbus.

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

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


[Kernel-packages] [Bug 1585081] Re: Switching user freezes system

2016-05-24 Thread DavidEG
Since I've upgraded to 16.04 I've started to experience these system crashes:
* Sometimes, when I plug/unplug an external hdmi monitor.
* Sometimes, when I shutdown the machine.
Haven't reported those as they happen a bit randomly. I am not able to 
reproduce them at my will.

The one reported here, happens always. Before upgrading to 16.04 I only
had one user so I don't know if the problem was there. That said, my
feeling is that it is caused by the upgrade because the aforementioned
issues.

Tested with the upstream kernel. The issue disappears
(4.6.0-040600-generic #201605151930).

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

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

Title:
  Switching user freezes system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Just doing this my system freezes:

  1. Click on the top right gear icon.
  2. Select a different user account.

  Login screen appears briefly, then black screen and the system is
  death:

  BUG: unable to handle kernel NULL pointer dereference at 0248
  IP: [] amdgpu_vm_grab_id+0x122/0x310 [amdgpu]
  PGD 0
  Oops:  [#1] SMP
  Modules linked in:  ...
  (See attached syslog for more)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  2739 F pulseaudio
   /dev/snd/controlC1:  david  2739 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 24 08:54:13 2016
  HibernationDevice: RESUME=UUID=d225720a-fc40-49a3-9182-17d278d40460
  InstallationDate: Installed on 2015-06-29 (329 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: TOSHIBA SATELLITE S50-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (31 days ago)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 2.00
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr2.00:bd12/02/2014:svnTOSHIBA:pnSATELLITES50-B:pvrPSPQEE-00F00JEN:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE S50-B
  dmi.product.version: PSPQEE-00F00JEN
  dmi.sys.vendor: TOSHIBA

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

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


[Kernel-packages] [Bug 1582963] onibi (amd64) - tests ran: 4, failed: 0

2016-05-24 Thread Brad Figg
tests ran:   4, failed: 0;
  
http://kernel.ubuntu.com/testing/3.19.0-60.67~14.04.1/onibi__3.19.0-60.67~14.04.1__2016-05-24_18-14-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-60.67~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:
  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:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

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

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

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

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


[Kernel-packages] [Bug 1516025] Re: Realtek ALC3661 Alienware14

2016-05-24 Thread Mohd Imran Jamadar
Audio is still not what i would expect, audio sucks.

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

Title:
  Realtek ALC3661 Alienware14

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When watching the following video (but also audio from other programs) with 
the volume at 100%, the audio loudness is lower in comparison to the same audio 
being played at 100% in Windows 10:
  https://www.youtube.com/watch?v=YQHsXMglC9A

  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-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  imran  1619 F pulseaudio
   /dev/snd/controlC1:  imran  1619 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Nov 13 18:08:07 2015
  HibernationDevice: RESUME=UUID=2401d43e-85ec-4c88-81c1-c597086504a1
  InstallationDate: Installed on 2015-11-07 (5 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Alienware Alienware 14
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=a534221a-37cb-4092-8ce2-934940eede6d ro quiet splash
  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: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2014
  dmi.bios.vendor: Alienware
  dmi.bios.version: A09
  dmi.board.name: 07MJ2Y
  dmi.board.vendor: Alienware
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnAlienware:bvrA09:bd04/23/2014:svnAlienware:pnAlienware14:pvrA09:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA09:
  dmi.product.name: Alienware 14
  dmi.product.version: A09
  dmi.sys.vendor: Alienware

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

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


[Kernel-packages] [Bug 1585081] Re: Switching user freezes system

2016-05-24 Thread DavidEG
** Tags added: kernel-fixed-upstream

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

Title:
  Switching user freezes system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Just doing this my system freezes:

  1. Click on the top right gear icon.
  2. Select a different user account.

  Login screen appears briefly, then black screen and the system is
  death:

  BUG: unable to handle kernel NULL pointer dereference at 0248
  IP: [] amdgpu_vm_grab_id+0x122/0x310 [amdgpu]
  PGD 0
  Oops:  [#1] SMP
  Modules linked in:  ...
  (See attached syslog for more)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  david  2739 F pulseaudio
   /dev/snd/controlC1:  david  2739 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue May 24 08:54:13 2016
  HibernationDevice: RESUME=UUID=d225720a-fc40-49a3-9182-17d278d40460
  InstallationDate: Installed on 2015-06-29 (329 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: TOSHIBA SATELLITE S50-B
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (31 days ago)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 2.00
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr2.00:bd12/02/2014:svnTOSHIBA:pnSATELLITES50-B:pvrPSPQEE-00F00JEN:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: SATELLITE S50-B
  dmi.product.version: PSPQEE-00F00JEN
  dmi.sys.vendor: TOSHIBA

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

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


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

2016-05-24 Thread Brad Figg
tests ran:  13, failed: 1;
  
http://kernel.ubuntu.com/testing/3.19.0-60.67~14.04.1/onibi__3.19.0-60.67~14.04.1__2016-05-24_16-45-00/results-index.html

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

Title:
  linux-lts-vivid: 3.19.0-60.67~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:
  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:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  New

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

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

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

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


[Kernel-packages] [Bug 1585315] [NEW] linux: 3.13.0-87.133 -proposed tracker

2016-05-24 Thread Kamal Mostafa
Public bug reported:

This bug is for tracking the 3.13.0-87.133 upload package. This bug will
contain status and testing results related to that upload.

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

** Affects: kernel-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: Invalid

** 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 (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Trusty)
 Importance: Medium
 Status: New


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

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

** Tags added: block-proposed-trusty

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

** Tags added: trusty

** 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-meta
   Status: New => Invalid

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

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

[Kernel-packages] [Bug 1584283] Re: 'Asus Touchpad' not detected in 'Asus Zenbook 305CA'

2016-05-24 Thread J.Mead
Fixed in Kernel 4.6.0 - thanks!

** Tags added: kernel-fixed-upstream

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

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

Title:
  'Asus Touchpad' not detected in 'Asus Zenbook 305CA'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Following https://wiki.ubuntu.com/DebuggingTouchpadDetection
  Laptop is brand new, touchpad works fine in windows. In each linux distro 
I've tried touchpad is nonresponsive and the hardware doesn't show up at all. 
External mouse works fine.
  The Windows driver looks like it's: AsusSGDrv.sys 8.0.0.19
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mint   2563 F pulseaudio
  CasperVersion: 1.340.2
  CurrentDesktop: X-Cinnamon
  DistroRelease: Ubuntu 14.04
  LiveMediaBuild: Linux Mint 17.3 "Rosa" - Release amd64 20151128
  MachineType: ASUSTeK COMPUTER INC. UX305CA
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/linuxmint.seed boot=casper iso-scan/filename= quiet splash 
--
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-32-generic N/A
   linux-backports-modules-3.19.0-32-generic  N/A
   linux-firmware 1.127.16
  Tags:  rosa
  Uname: Linux 3.19.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/11/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305CA.201
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305CA.201:bd09/11/2015:svnASUSTeKCOMPUTERINC.:pnUX305CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX305CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Kernel-packages] [Bug 1584509] Re: CD-R's not mounted in latest kernel

2016-05-24 Thread Karl Lindheimer
Hi I installed the latest 4.6 generic AMD x64 kernel, and tested various
cd-r's and dvd-r's.  The problem is almost entirely fixed in the v4.6
kernel.  CD-R's mount automatically with the exception of certain x32
cd-r like the i686 bootable clonezilla image.  it does not mount, but it
will run if selected via BIOS at boot-up.  This behavior also occurs
with several other older windows disks (CD-R) as well.

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

Title:
  CD-R's not mounted in latest kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug affects both the X64 and X32 bit versions of the latest
  ubuntu 16.04 it does not occur with ubuntu 15.10 or earlier.  The
  problem is when a known good CD-R is placed in the drive, it is not
  mounted automatically.  However, if it is a bootable CD-R and you
  select the boot option of the BIOS it will function normally.

  Also, When a blank CD-R is inserted into the drive, it is mounted
  automatically, but disk creation software reports an erroneous amount
  of free space available.  Such as 247 MB or 512 MB when the disk is a
  700 MB disk.  However, if you proceed to record to the disk, even with
  an ISO image greater than the supposed available capacity, it records
  just fine.

  Other disk types such as DVD, audio, small cd-r work fine.  This only
  seems to affect the larger, full size cd-r's

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  karl   1886 F pulseaudio
   /dev/snd/controlC0:  karl   1886 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 22 14:38:13 2016
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=03cb5141-d254-414a-950b-2235e068035a
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2016-03-09 (73 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Gateway DX4380G
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=da27bf85-d849-43b8-a8f2-8fdac4f37784 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   14:38:31.725: The udisks-daemon is running (name-owner :1.96).
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-A1
  dmi.board.name: DX4380G
  dmi.board.vendor: Gateway
  dmi.board.version: 1.02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-A1:bd09/04/2012:svnGateway:pnDX4380G:pvr:rvnGateway:rnDX4380G:rvr1.02:cvnGateway:ct3:cvr:
  dmi.product.name: DX4380G
  dmi.sys.vendor: Gateway

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

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


[Kernel-packages] [Bug 1584509] Re: CD-R's not mounted in latest kernel

2016-05-24 Thread Karl Lindheimer
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  CD-R's not mounted in latest kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This bug affects both the X64 and X32 bit versions of the latest
  ubuntu 16.04 it does not occur with ubuntu 15.10 or earlier.  The
  problem is when a known good CD-R is placed in the drive, it is not
  mounted automatically.  However, if it is a bootable CD-R and you
  select the boot option of the BIOS it will function normally.

  Also, When a blank CD-R is inserted into the drive, it is mounted
  automatically, but disk creation software reports an erroneous amount
  of free space available.  Such as 247 MB or 512 MB when the disk is a
  700 MB disk.  However, if you proceed to record to the disk, even with
  an ISO image greater than the supposed available capacity, it records
  just fine.

  Other disk types such as DVD, audio, small cd-r work fine.  This only
  seems to affect the larger, full size cd-r's

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-22-generic 4.4.0-22.40
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  karl   1886 F pulseaudio
   /dev/snd/controlC0:  karl   1886 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun May 22 14:38:13 2016
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=03cb5141-d254-414a-950b-2235e068035a
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2016-03-09 (73 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Gateway DX4380G
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=da27bf85-d849-43b8-a8f2-8fdac4f37784 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  Symptom: storage
  UdevMonitorLog:
   monitor will print the received events for:
   UDEV - the event which udev sends out after rule processing
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   14:38:31.725: The udisks-daemon is running (name-owner :1.96).
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P11-A1
  dmi.board.name: DX4380G
  dmi.board.vendor: Gateway
  dmi.board.version: 1.02
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP11-A1:bd09/04/2012:svnGateway:pnDX4380G:pvr:rvnGateway:rnDX4380G:rvr1.02:cvnGateway:ct3:cvr:
  dmi.product.name: DX4380G
  dmi.sys.vendor: Gateway

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

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


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

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

apport-collect 1585311

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

Title:
  [Hyper-V] Put tools/hv/lsvmbus in /usr/sbin

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Similar to the Hyper-V daemons that are in cloud-tools, please place
  the python script "lsvmbus" from the Linux kernel source tree in
  tools/hv in /usr/sbin

  This script will show the devices on the Hyper-V vmbus.

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

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


[Kernel-packages] [Bug 1584479] Re: [kernel-bug-exists-upstream] MSI touchpad not detected on 16.04

2016-05-24 Thread Sam
Hi,

Sorry to contact to you directly, but I don't understand very well your
:

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

So, I add kernel-bug-exists-upstream to my post title : I hope it's ok.

Thnaks.

--
Cordialement, Best regards,
M. Matthieu Paniez


** Summary changed:

- MSI touchpad not detected on 16.04
+ [kernel-bug-exists-upstream] MSI touchpad not detected on 16.04

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

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

Title:
  [kernel-bug-exists-upstream] MSI touchpad not detected on 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  I just install Ubuntu 16.04 on my new MSI laptop G72 6QE.
  My touchpad doesn't work and recognize at all.

  I try :
  - Fn+F3 to activate my touchpad
  - xinput list and is not listed
  - xev and nothing append (no signal)
  - cat /proc/bus/input/devices ddoesn't display touchpad (only HDMI, mic, 
headphone, external mouse and keyboard)
  - I don't know if there is a link, but some buttons of my keyboard don't work 
(like Fn+arrows to manage sound and luminosity) :
  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input0
  U: Uniq=
  H: Handlers=sysrq kbd event0 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=60070290 8380207af040d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  
  Thanks
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1305 F pulseaudio
moi1668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9649bbed-2d32-42cd-a446-43abaa9ab1f3
  InstallationDate: Installed on 2016-05-20 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Micro-Star International Co., Ltd. GP72 6QE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic 
root=UUID=80432220-0bdf-49f0-a145-0c015ad36c2a ro rootflags=subvol=@ acpi=off 
acpi_osi=! acpi_backlight=native i8042.nopnp quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1795IMS.10C
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-1795
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1795IMS.10C:bd12/10/2015:svnMicro-StarInternationalCo.,Ltd.:pnGP726QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1795:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GP72 6QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Kernel-packages] [Bug 1585311] Re: [Hyper-V] Put tools/hv/lsvmbus in /usr/sbin

2016-05-24 Thread Joshua R. Poulson
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/tools/hv/lsvmbus

This script was introduced upstream August 2015.

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

Title:
  [Hyper-V] Put tools/hv/lsvmbus in /usr/sbin

Status in linux package in Ubuntu:
  New

Bug description:
  Similar to the Hyper-V daemons that are in cloud-tools, please place
  the python script "lsvmbus" from the Linux kernel source tree in
  tools/hv in /usr/sbin

  This script will show the devices on the Hyper-V vmbus.

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

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


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

2016-05-24 Thread Antoine Polatouche
Testing with kernel 4.6.0 64bit.
Open windows : Terminal, system monitor and Firefox (one tab : 
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/).
mysqld is using less than 100Mo at startup, Firefox 140Mo.
A few minutes later, without activity mysqld is using 807.2Mo 

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

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1585311] [NEW] [Hyper-V] Put tools/hv/lsvmbus in /usr/sbin

2016-05-24 Thread Joshua R. Poulson
Public bug reported:

Similar to the Hyper-V daemons that are in cloud-tools, please place the
python script "lsvmbus" from the Linux kernel source tree in tools/hv in
/usr/sbin

This script will show the devices on the Hyper-V vmbus.

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

Title:
  [Hyper-V] Put tools/hv/lsvmbus in /usr/sbin

Status in linux package in Ubuntu:
  New

Bug description:
  Similar to the Hyper-V daemons that are in cloud-tools, please place
  the python script "lsvmbus" from the Linux kernel source tree in
  tools/hv in /usr/sbin

  This script will show the devices on the Hyper-V vmbus.

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

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


[Kernel-packages] [Bug 1584479] Re: MSI touchpad not detected on 16.04

2016-05-24 Thread Sam
Re,
And my syslog.

Thanks

** Attachment added: "syslog.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584479/+attachment/4669563/+files/syslog.log

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

Title:
  MSI touchpad not detected on 16.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I just install Ubuntu 16.04 on my new MSI laptop G72 6QE.
  My touchpad doesn't work and recognize at all.

  I try :
  - Fn+F3 to activate my touchpad
  - xinput list and is not listed
  - xev and nothing append (no signal)
  - cat /proc/bus/input/devices ddoesn't display touchpad (only HDMI, mic, 
headphone, external mouse and keyboard)
  - I don't know if there is a link, but some buttons of my keyboard don't work 
(like Fn+arrows to manage sound and luminosity) :
  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input0
  U: Uniq=
  H: Handlers=sysrq kbd event0 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=60070290 8380207af040d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  
  Thanks
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1305 F pulseaudio
moi1668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=9649bbed-2d32-42cd-a446-43abaa9ab1f3
  InstallationDate: Installed on 2016-05-20 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: Micro-Star International Co., Ltd. GP72 6QE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-22-generic 
root=UUID=80432220-0bdf-49f0-a145-0c015ad36c2a ro rootflags=subvol=@ acpi=off 
acpi_osi=! acpi_backlight=native i8042.nopnp quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-22-generic N/A
   linux-backports-modules-4.4.0-22-generic  N/A
   linux-firmware1.157
  Tags:  xenial
  Uname: Linux 4.4.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1795IMS.10C
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-1795
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.A
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1795IMS.10C:bd12/10/2015:svnMicro-StarInternationalCo.,Ltd.:pnGP726QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1795:rvrREV0.A:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:
  dmi.product.name: GP72 6QE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

-- 
Mailing list: https://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   >