date:20160428

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

Title:
  Linux 4.4.0: wrong value for /sys/*/queue/discard_granularity

Status in linux package in Ubuntu:
  Confirmed
Status in linux package in Fedora:
  Unknown

Bug description:
  With kernel 4.4.0-21.37 in xenial and yakkety, the value of
  queue/discard_granularity is set to '1' instead of to a multiple of
  the block size as expected.

  $ cat 
/sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/queue/discard_granularity
  1
  $

  This is at odds with the values on ramdisks:
  $ cat /sys/devices/virtual/block/ram0/queue/discard_granularity
  4096
  $

  And with lvm2 2.02.150-1ubuntu1, currently in yakkety-proposed, this
  always results in an error message from lvremove if discard is
  configured, and discard is not actually used; e.g., from my schroot
  output:

  E: 05lvm:   WARNING: Device /dev/sda7: queue/discard_granularity is 1
  and is unexpectedly less than sector.

  This bug has also been reported against Linux 4.4 in Fedora.
  https://bugzilla.redhat.com/show_bug.cgi?id=1314687

  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/controlC1:  vorlon 3681 F pulseaudio
   /dev/snd/pcmC0D0p:   vorlon 3681 F...m pulseaudio
   /dev/snd/controlC0:  vorlon 3681 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Apr 28 16:39:54 2016
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2043 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/hostname-root ro quiet splash 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: Upgraded to xenial on 2016-04-15 (13 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1562618] Re: whole OS freezes seemingly randomly

2016-04-28 Thread Vincent Gerris

Hi,

I installed the latest included kernel:
Linux vincent-Lenovo-Yoga-2-11 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 
18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
I will test that and then the 4.6.0-rc4 after.

Is there anything patched there that could be a solution to the fix?

Thank you and regards,
Vincent

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

Title:
  whole OS freezes seemingly randomly

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I had some random freezes of the whole operating system.
  No caps lock response or terminal switching, nothng.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  vincent1714 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar 27 23:46:02 2016
  HibernationDevice: RESUME=UUID=8180a7b6-a1c0-494a-9f65-99a7b54f6deb
  InstallationDate: Installed on 2015-11-01 (147 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20332
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic.efi.signed 
root=UUID=44fb018f-3dbd-4eb6-ab9a-6668de8d13d2 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-03-25 (2 days ago)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 92CN26WW(V1.06)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: AIUU1
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900042STD
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga 2 11
  dmi.modalias: 
dmi:bvnLENOVO:bvr92CN26WW(V1.06):bd12/26/2013:svnLENOVO:pn20332:pvrLenovoYoga211:rvnLENOVO:rnAIUU1:rvr31900042STD:cvnLENOVO:ct10:cvrLenovoYoga211:
  dmi.product.name: 20332
  dmi.product.version: Lenovo Yoga 2 11
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1285434] Re: hyper-v: Keyboard dysfunctional while booting 14.04 Generation 2 virtual machines on Hyper-V

2016-04-28 Thread Jeff Waugh

Can confirm I've seen the same thing per #27 (though with the server
installer, not a big difference). Turn off secure boot and it's fine.

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

Title:
  hyper-v: Keyboard dysfunctional while booting 14.04 Generation 2
  virtual machines on Hyper-V

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Hi folks,

  While booting in to Generation 2 virtual machine mode, I noticed that
  the keyboard stops functioning. It appears that the keyboard is
  operational during the Grub 2 menu (see attached picture) but when we
  get to the screen to select a language, the keyboard stops responding.
  Is it feasible for you to check if the Hyper-V keyboard driver has
  been included from here:

  http://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/tree/drivers/input/serio/hyperv-keyboard.c?id=HEAD

  Please let me know.
  Thanks,
  Abhishek

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

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

[Kernel-packages] [Bug 1576451] [NEW] Linux 4.4.0: wrong value for /sys/*/queue/discard_granularity

2016-04-28 Thread Steve Langasek

Public bug reported:

With kernel 4.4.0-21.37 in xenial and yakkety, the value of
queue/discard_granularity is set to '1' instead of to a multiple of the
block size as expected.

$ cat 
/sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/queue/discard_granularity
1
$

This is at odds with the values on ramdisks:
$ cat /sys/devices/virtual/block/ram0/queue/discard_granularity
4096
$

And with lvm2 2.02.150-1ubuntu1, currently in yakkety-proposed, this
always results in an error message from lvremove if discard is
configured, and discard is not actually used; e.g., from my schroot
output:

E: 05lvm:   WARNING: Device /dev/sda7: queue/discard_granularity is 1
and is unexpectedly less than sector.

This bug has also been reported against Linux 4.4 in Fedora.
https://bugzilla.redhat.com/show_bug.cgi?id=1314687

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/controlC1:  vorlon 3681 F pulseaudio
 /dev/snd/pcmC0D0p:   vorlon 3681 F...m pulseaudio
 /dev/snd/controlC0:  vorlon 3681 F pulseaudio
CurrentDesktop: Unity
Date: Thu Apr 28 16:39:54 2016
HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
InstallationDate: Installed on 2010-09-24 (2043 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MachineType: LENOVO 2306CTO
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic 
root=/dev/mapper/hostname-root ro quiet splash 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: Upgraded to xenial on 2016-04-15 (13 days ago)
dmi.bios.date: 10/25/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET97WW (2.57 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2306CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2306CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

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

** Affects: linux (Fedora)
 Importance: Unknown
 Status: Unknown


** Tags: amd64 apport-bug xenial

** Bug watch added: Red Hat Bugzilla #1314687
   https://bugzilla.redhat.com/show_bug.cgi?id=1314687

** Also affects: linux (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1314687
   Importance: Unknown
   Status: Unknown

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

Title:
  Linux 4.4.0: wrong value for /sys/*/queue/discard_granularity

Status in linux package in Ubuntu:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  With kernel 4.4.0-21.37 in xenial and yakkety, the value of
  queue/discard_granularity is set to '1' instead of to a multiple of
  the block size as expected.

  $ cat 
/sys/devices/pci:00/:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/queue/discard_granularity
  1
  $

  This is at odds with the values on ramdisks:
  $ cat /sys/devices/virtual/block/ram0/queue/discard_granularity
  4096
  $

  And with lvm2 2.02.150-1ubuntu1, currently in yakkety-proposed, this
  always results in an error message from lvremove if discard is
  configured, and discard is not actually used; e.g., from my schroot
  output:

  E: 05lvm:   WARNING: Device /dev/sda7: queue/discard_granularity is 1
  and is unexpectedly less than sector.

  This bug has also been reported against Linux 4.4 in Fedora.
  https://bugzilla.redhat.com/show_bug.cgi?id=1314687

  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/controlC1:  vorlon 3681 F pulseaudio
   /dev/snd/pcmC0D0p:   vorlon 3681 F...m pulseaudio
   /dev/snd/controlC0:  vorlon 3681 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Apr 28 16:39:54 2016
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2043 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine:

[Kernel-packages] [Bug 1552504] Re: clicking noise on acer 131t-c1yf

2016-04-28 Thread bhikkhu subhuti

I am running Lubuntu 16.04 on legacy. The new release still has problems if I
run certain programs like Wine or Thunderbird.
I think it is related to graphics and it may be related to gtk3 too. Not
totally sure. It is easy to test.. even in Lubuntu.

Because I am on legacy, I can upgrade the bios again if you wish. But
currently, this is unassigned.

Can someone tell me what this clicking noise is? Is it something
dangerous. it is a solid state computer.

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

Title:
clicking noise on acer 131t-c1yf

Status in linux package in Ubuntu:
Incomplete

Bug description:
My machine is solid state.
I updated the intel graphics driver
I update a few days ago via ubuntu udpater

Lubuntu installed on top of ubuntu still makes the noise.
Lubuntu live usb does NOT make the noise.
Windows 10 does not make the noise.

I suspect compiz, but ultimately I think it is a kernal problem.
I suspect this is a CherryView Bug.

This bug has been reported on ubuntu forums and ask ubuntu and no responses.
I will be switching to Lubuntu in a few days unless I hear back from you. I
am technical and willing to help.

Bhikkhu Subhuti

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

[Kernel-packages] [Bug 1571791] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 13, failed: 3

tests ran:  13, failed: 3;
  
http://kernel.ubuntu.com/testing/4.4.0-22.38/ms10-35-mcdivittB0-kernel__4.4.0-22.38__2016-04-28_21-13-00/results-index.html

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

Title:
  linux: 4.4.0-21.37 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-21.37 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Monday, 18. April 2016 18:15 UTC
  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true

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

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

[Kernel-packages] [Bug 1463740] Re: CVE-2015-4004

2016-04-28 Thread Kamal Mostafa

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

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

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

Title:
  CVE-2015-4004

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty 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-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  Fix Committed
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Invalid
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
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-mvl-dove source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
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:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-raspi2 source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  Won't Fix
Status in linux-lts-backport-natty source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Fix Committed
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  New
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  New
Status in linux-lts-backport-maverick source package in Vivid:
  New
Status in linux-lts-backport-natty source package in Vivid:
  New
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid

[Kernel-packages] [Bug 1543461] Re: linux: intermittent ADT test failures on ppc64el

** Also affects: qa-regression-testing
   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/1543461

Title:
  linux: intermittent ADT test failures on ppc64el

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The linux internal test suites fail intermittently (1/3 approx) as
  below:

  [...]
test_parser_testsuite (__main__.ApparmorTestsuites)
Run parser regression tests ... ok
test_regression_testsuite (__main__.ApparmorTestsuites)
Run kernel regression tests ... FAIL
test_stress_parser_testsuite (__main__.ApparmorTestsuites)
Run parser stress test ... ok
  [...]
==
FAIL: test_regression_testsuite (__main__.ApparmorTestsuites)
Run kernel regression tests
--
Traceback (most recent call last):
  File "./test-apparmor.py", line 1589, in test_regression_testsuite
self.assertEquals(expected, rc, result + report)
AssertionError: Got exit code 2, expected 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1543461/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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-04-28 Thread Simon Déziel

I recently reinstalled the affected host to run Xenial so I can no
longer test the proposed fix for the 3.13 kernel.

-- 
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] RSP: :880003a11a58  EFLAGS: 00010292
  [Thu Feb 19 06:25:09 2015] RAX:  RBX:

[Kernel-packages] [Bug 1569831] Re: Laptop does not resume after suspend (blackscreen).

2016-04-28 Thread Roberto Fierros

I am having the same problem running kernel 4.4.8 and Linux Mint 17.3.

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

Title:
  Laptop does not resume after suspend (blackscreen).

Status in bcmwl package in Ubuntu:
  Incomplete

Bug description:
  I have installed OS multiple times. I have to manually install the BCM
  driver. After installing the bcmwl-kernal-source the laptop will
  suspend, but not resume after. If I disable the external driver, the
  suspend resume works again. I have tried with a variety of different
  configs.

  Network card is BCM4352 [14e4-43b1](rev03)

  When I try to resume the laptop turns on, but screen never turns on. I've 
tried to the shortuts to turn the screen back on. 
  I'm using NVIDIA drivers, but even if I use the generic drivers the laptop 
will not resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7
  ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
  Uname: Linux 4.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Apr 13 11:05:08 2016
  InstallationDate: Installed on 2016-03-05 (39 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  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/1569831/+subscriptions

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

[Kernel-packages] [Bug 1529971] bantam (amd64) - tests ran: 28, failed: 4

tests ran:  28, failed: 4;
  
http://kernel.ubuntu.com/testing/4.4.0-22.38/kernel01__4.4.0-22.38__2016-04-28_14-51-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/1529971

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

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 29. December 2015 22:50 UTC
  kernel-stable-master-bug:1529362
  kernel-stable-Prepare-package-end:Friday, 01. January 2016 21:01 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 01. January 2016 21:01 UTC
  kernel-stable-Certification-testing-end:Monday, 04. January 2016 16:01 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 04. January 2016 18:08 UTC
  kernel-stable-Security-signoff-start:Monday, 04. January 2016 18:30 UTC
  kernel-stable-Regression-testing-start:Monday, 04. January 2016 18:30 UTC
  proposed-announcement-sent:True
  kernel-stable-Verification-testing-start:Monday, 04. January 2016 18:30 UTC
  kernel-stable-Verification-testing-end:Monday, 04. January 2016 20:01 UTC
  kernel-stable-Regression-testing-end:Monday, 04. January 2016 20:01 UTC
  kernel-stable-Security-signoff-end:Tuesday, 05. January 2016 09:00 UTC
  kernel-stable-Promote-to-updates-start:Tuesday, 05. January 2016 10:01 UTC
  kernel-stable-Promote-to-updates-end:Tuesday, 05. January 2016 16:10 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Tuesday, 05. January 2016 18:02 UTC

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

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

[Kernel-packages] [Bug 1532746] Re: SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

2016-04-28 Thread Paolo Sabatino

CAPS LOCK led doesn't work with dumbkbd because dumbkbd option disables
the i8042 module write capability, so the i8042 can't write the led
status to the keyboard controller. Unfortunately this is a side effect
of dumbkbd option, but there can be others too. I digged a bit into
kernel source code and found that both i8042 and atkbd modules affect
the keyboard controller behavior, but I'm still experimenting...

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

Title:
  SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I've a problem with the keyboard of notebook HP Pavilion 15 ab062nl.
  the problem is with SHIFT ALT and CTRL buttons of the keyboard.

  for example when i use ALT-TAB shortcut, after few seconds, the ALT-TAB menu 
disappear as if i release ALT key, but isn't so.
  another example is when i navigate on web, when i scroll page with mouse 
wheel, sometimes the page start to resize, as if i'm pressing CTRL command 
while scroll, or if i'm writing a text, sometimes, borwser launch shortcut, as 
if i'm pressing CTRL while i type text, for exaple if i'm typing "b" letter, 
opens bookmarks...

  another example is while i'm typing text, if i press SHIFT key and
  start typing, begins to write uppercase letters and after a while,
  writes lowercase like I released shift, but i'm still pressing shift.

  for example if i press SHIFT+s, the result is this:
  SSs
  some letters are uppercase, but others are lowercase.

  i haven't found a solution.
  the only way to solve momentarily the problem, is pressing for some seconds 
the only SHIFT key, after that, the problems disappears indefinitely, or until 
the next restart.

  This problem occurs with all ubuntu version (x86 and x86_64), now i'm
  using Ubuntu 15.10, but i've also tried ubuntu 15.04, ubuntu 14.04,
  ubuntu 12.04, ubuntu 10.04.

  furthermore i've this problem also with other GNU/Linux Distributions (i've 
tried Fedora, OpenSuse, ArchLinux, Antergos, Debian, SteamOS).
  but isn't and hardware problem, because on Windows 8.1 and Windows 10 i 
haven't these problems.

  i've also tried to plug in an externa USB keyboard, and if i use
  external USB keybaord i haven't problems.

  i think is a problem of compatibility, with integrated keyboard of
  this notebook.

  i've tried to monitor these problems using XEV, and the results is
  that also if i'm not using notebook, sometimes XEV reads an INPUT of
  one of these 3 key (SHIFT, ALT, CTRL), and while i'm pressing one of
  these 3 key, XEV see also if i release and immedialty after press
  again the key.

  this is an example of the input while i press Left_ALT key for a while

  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 129987, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  KeyRelease event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130147, (-142,152), root:(452,476),
  state 0x18, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130391, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  whole log here http://pastebin.com/CPGz40aw

  and this is the output of xev, leaving the notebook on a few hours
  without using it http://pastebin.com/sYSHAbGy

  
  this is "xinput" output

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Laser Mouseid=11   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ HP Truevision HDid=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP

[Kernel-packages] [Bug 1529971] bantam (amd64) - tests ran: 28, failed: 0

tests ran:  28, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-22.38/azure-sut-1__4.4.0-22.38__2016-04-28_12-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/1529971

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

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
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:
  Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Released

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 29. December 2015 22:50 UTC
  kernel-stable-master-bug:1529362
  kernel-stable-Prepare-package-end:Friday, 01. January 2016 21:01 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 01. January 2016 21:01 UTC
  kernel-stable-Certification-testing-end:Monday, 04. January 2016 16:01 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 04. January 2016 18:08 UTC
  kernel-stable-Security-signoff-start:Monday, 04. January 2016 18:30 UTC
  kernel-stable-Regression-testing-start:Monday, 04. January 2016 18:30 UTC
  proposed-announcement-sent:True
  kernel-stable-Verification-testing-start:Monday, 04. January 2016 18:30 UTC
  kernel-stable-Verification-testing-end:Monday, 04. January 2016 20:01 UTC
  kernel-stable-Regression-testing-end:Monday, 04. January 2016 20:01 UTC
  kernel-stable-Security-signoff-end:Tuesday, 05. January 2016 09:00 UTC
  kernel-stable-Promote-to-updates-start:Tuesday, 05. January 2016 10:01 UTC
  kernel-stable-Promote-to-updates-end:Tuesday, 05. January 2016 16:10 UTC
  kernel-stable-phase:Released
  kernel-stable-phase-changed:Tuesday, 05. January 2016 18:02 UTC

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

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

[Kernel-packages] [Bug 1559705] Re: linux: apparmor ADT test failures in changeprofile test

AppArmor 2.10.95 landed in xenial, which fixes these failing test cases.
Closing bug.

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

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

Title:
  linux: apparmor ADT test failures in changeprofile test

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  We are seeing ADT test failures in the apparmor kernel regression test
  suite.  We are reporting ENOENT rather than EACCESS:

running changeprofile
Error: changeprofile failed. Test 'CHANGEPROFILE (no target, 
/tmp/sdtest.10794-16623-rfX1oc/file)' was expected to 'fail'. Reason for 
failure expect errno 13 != 2
Error: changeprofile failed. Test 'CHANGEPROFILE (no target, 
/tmp/sdtest.10794-16623-rfX1oc/file2)' was expected to 'fail'. Reason for 
failure expect errno 13 != 2

  This is occuring on amd64, i386 and ppc64el, armhf and s390x are both
  reporting good:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20160320_121949@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20160320_120702@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20160320_115958@/log.gz

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

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

[Kernel-packages] [Bug 1528232] Re: [ADT test failure] linux: ubuntu_qrt_apparmor.test-apparmor.py -- dbus tests failing

** Also affects: qa-regression-testing
   Importance: Undecided
   Status: New

** Summary changed:

- [ADT test failure] linux: ubuntu_qrt_apparmor.test-apparmor.py -- dbus tests 
failing
+ [ADT test failure] linux: ubuntu_qrt_apparmor.test-apparmor.py -- parser dbus 
tests failing

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

Title:
  [ADT test failure] linux: ubuntu_qrt_apparmor.test-apparmor.py --
  parser dbus tests failing

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We have a new ADT test failure in Xenial:
#   Failed test './simple_tests//generated_dbus/message-rules-31834.sd: no 
description for testcase'
#   at simple.pl line 139.

#   Failed test './simple_tests//generated_dbus/message-rules-31835.sd: no 
description for testcase'
#   at simple.pl line 139.
# Looks like you failed 2 tests of 71454.
simple.pl .. 
not ok 26617 - ./simple_tests//generated_dbus/message-rules-31834.sd: no 
description for testcase
not ok 26618 - ./simple_tests//generated_dbus/message-rules-31835.sd: no 
description for testcase
Dubious, test returned 2 (wstat 512, 0x200)

  Full log:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20151218_073022@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1528232/+subscriptions

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

[Kernel-packages] [Bug 1528228] Re: [ADT test failure] linux-lts-utopic: ubuntu_qrt_apparmor.test-apparmor.py -- FAIL: test_aa_unconfined (main.ApparmorTest)

** Also affects: qa-regression-testing
   Importance: Undecided
   Status: New

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

Title:
  [ADT test failure] linux-lts-utopic: ubuntu_qrt_apparmor.test-
  apparmor.py --   FAIL: test_aa_unconfined (__main__.ApparmorTest)

Status in QA Regression Testing:
  New
Status in apparmor package in Ubuntu:
  New
Status in linux-lts-utopic package in Ubuntu:
  Confirmed

Bug description:
  New ADT test failure in linux-lts-utopic in Trusty:

    FAIL: test_aa_unconfined (__main__.ApparmorTest)
    Test aa-unconfined
    --
    Traceback (most recent call last):
  File "./test-apparmor.py", line 815, in test_aa_unconfined
    self.assertTrue(re.search('[1-9][0-9]* /bin/nc(.openbsd|.traditional)( 
\(/bin/nc\))? not confined', report), result + report)
    AssertionError: Could not find /bin/nc* in report
    609 /sbin/dhclient confined by '/sbin/dhclient (enforce)'
    894 /usr/sbin/sshd not confined
    5326 /usr/sbin/exim4 not confined

  Full log:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/linux-lts-utopic/20151218_194502@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1528228/+subscriptions

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

[Kernel-packages] [Bug 1532746] Re: SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

2016-04-28 Thread Dea1993

i've added simply 
i8042.dumbkbd

without 
=1

do you work led of caps lock?

on my notebook led not works if i use
i8042.dumbkbd

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

Title:
  SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I've a problem with the keyboard of notebook HP Pavilion 15 ab062nl.
  the problem is with SHIFT ALT and CTRL buttons of the keyboard.

  for example when i use ALT-TAB shortcut, after few seconds, the ALT-TAB menu 
disappear as if i release ALT key, but isn't so.
  another example is when i navigate on web, when i scroll page with mouse 
wheel, sometimes the page start to resize, as if i'm pressing CTRL command 
while scroll, or if i'm writing a text, sometimes, borwser launch shortcut, as 
if i'm pressing CTRL while i type text, for exaple if i'm typing "b" letter, 
opens bookmarks...

  another example is while i'm typing text, if i press SHIFT key and
  start typing, begins to write uppercase letters and after a while,
  writes lowercase like I released shift, but i'm still pressing shift.

  for example if i press SHIFT+s, the result is this:
  SSs
  some letters are uppercase, but others are lowercase.

  i haven't found a solution.
  the only way to solve momentarily the problem, is pressing for some seconds 
the only SHIFT key, after that, the problems disappears indefinitely, or until 
the next restart.

  This problem occurs with all ubuntu version (x86 and x86_64), now i'm
  using Ubuntu 15.10, but i've also tried ubuntu 15.04, ubuntu 14.04,
  ubuntu 12.04, ubuntu 10.04.

  furthermore i've this problem also with other GNU/Linux Distributions (i've 
tried Fedora, OpenSuse, ArchLinux, Antergos, Debian, SteamOS).
  but isn't and hardware problem, because on Windows 8.1 and Windows 10 i 
haven't these problems.

  i've also tried to plug in an externa USB keyboard, and if i use
  external USB keybaord i haven't problems.

  i think is a problem of compatibility, with integrated keyboard of
  this notebook.

  i've tried to monitor these problems using XEV, and the results is
  that also if i'm not using notebook, sometimes XEV reads an INPUT of
  one of these 3 key (SHIFT, ALT, CTRL), and while i'm pressing one of
  these 3 key, XEV see also if i release and immedialty after press
  again the key.

  this is an example of the input while i press Left_ALT key for a while

  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 129987, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  KeyRelease event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130147, (-142,152), root:(452,476),
  state 0x18, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130391, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  whole log here http://pastebin.com/CPGz40aw

  and this is the output of xev, leaving the notebook on a few hours
  without using it http://pastebin.com/sYSHAbGy

  
  this is "xinput" output

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Laser Mouseid=11   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ HP Truevision HDid=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=14   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=15   [slave  
keyboard (3)]

  i hope that this bug can be solved

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package:

[Kernel-packages] [Bug 1546694] Re: Bluetooth cannot detect other devices (Lite-on 3014 + Atheros AR9565)

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

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

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

** Also affects: linux (Ubuntu Wily)
   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/1546694

Title:
  Bluetooth cannot detect other devices (Lite-on 3014 + Atheros AR9565)

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  New
Status in linux source package in Vivid:
  New
Status in linux source package in Wily:
  New
Status in linux source package in Xenial:
  New

Bug description:
  I bought an Acer Cloudbook 11 but the bluetooth doesn't seem to work.
  The system shows the indicator icon but he doesn't detect any devices.
  The wifi works correctly.

  lsb_release -rb:
  Description:  Ubuntu 15.10
  Release:  15.10
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thenawaker   1387 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=8e395c05-c5e5-482d-ac5e-bbfeffcc37a6
  InstallationDate: Installed on 2016-02-17 (0 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04ca:3014 Lite-On Technology Corp. 
   Bus 001 Device 003: ID 064e:9404 Suyin Corp. 
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire one 1-131
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-27-generic.efi.signed 
root=/dev/mmcblk0p2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-27.32-generic 4.2.8-ckt1
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-27-generic N/A
   linux-backports-modules-4.2.0-27-generic  N/A
   linux-firmware1.144+ar3012
  Tags:  wily
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  Uname: Linux 4.2.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Caltech
  dmi.board.vendor: Acer
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/30/2015:svnAcer:pnAspireone1-131:pvrV1.06:rvnAcer:rnCaltech:rvrV1.06:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire one 1-131
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1557776] Re: CONFIG_AUFS_XATTR is not set

@Fabien,

The comment was to verify it on xenial, the commit has not made it to
Wily yet. I have just verified it's fixed in Xenial.

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

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

Title:
  CONFIG_AUFS_XATTR is not set

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

Bug description:
  I am using ubuntu 15.10 with kernel linux-image-4.2.0-27-generic.
  The setting  CONFIG_AUFS_XATTR is not set.

  With the previous ubuntu version 15.04 and linux-
  image-3.19.0-42-generic this setting was compiled as
  CONFIG_AUFS_XATTR=y

  Without  CONFIG_AUFS_XATTR docker users using the AUFS driver can not
  work with capabilities.

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

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

[Kernel-packages] [Bug 484045] Re: kswapd0 at 100% cpu

2016-04-28 Thread erik

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

** This bug has been marked a duplicate of bug 1518457
   kswapd0 100% CPU usage

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

Title:
  kswapd0 at 100% cpu

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:Ubuntu 9.10
  Release:9.10

  Package ... unknown, going to guess the linux kernel.

  The process kswapd0 takes of 100% of one of my processors.  I can't
  kill it and have no idea why it starts churning away and never stops.
  Seems to happen only after suspending the computer.

  See http://ubuntu-ky.ubuntuforums.org/showthread.php?t=1315869 for
  another report of similar problem.

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

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

[Kernel-packages] [Bug 1528230] Re: [ADT test failure] linux: ubuntu_qrt_apparmor.test-apparmor.py -- ONEXEC - check current 'unconfined' != expected

** Tags added: apparmor

** Tags added: qart

** Also affects: qa-regression-testing
   Importance: Undecided
   Status: New

** Tags removed: qart

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

Title:
  [ADT test failure] linux: ubuntu_qrt_apparmor.test-apparmor.py --
  ONEXEC - check current 'unconfined' != expected

Status in QA Regression Testing:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  New ADT test failure in Vivid:

    running onexec
    ONEXEC - check current 'unconfined' != expected 
'/tmp/testlibIUFsmN/source/vivid/apparmor-2.9.1/tests/regression/apparmor/onexec'
    Fatal Error (onexec): Unable to run test sub-executable

  Full log:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-vivid/vivid/ppc64el/l/linux/20151218_175610@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1528230/+subscriptions

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

[Kernel-packages] [Bug 1407505] Re: No UMS support in radeon module

I'm was running: "apport-collect 1407505", all of my comments up there are 
autogenerated by apport-collect, I'm sorry for the quantities.
I have updated from Ubuntu 15.10 to Ubuntu 16.04 LTS and now I'm affected from 
this bug. 

The kernel version is: 4.4.0-21-generic
Running: dmesg | egrep 'drm|radeon' I'm getting this error:

[1.127347] [drm] Initialized drm 1.1.0 20060810
[1.159659] [drm] VGACON disable radeon kernel modesetting.
[1.159734] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon 
module!
[1.196474] [drm] VGACON disable radeon kernel modesetting.
[1.196549] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon 
module!
[   18.569430] [drm] VGACON disable radeon kernel modesetting.
[   18.569467] [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon 
module!

I'm tried to edit the /etc/default/grub from

GRUB_CMDLINE_LINUX_DEFAULT: "quiet splash"

to

GRUB_CMDLINE_LINUX_DEFAULT: "radeon.modeset=1"

without success.

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

Title:
  No UMS support in radeon module

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Confirmed

Bug description:
  System: Kubuntu (adm64) 14.10.
  Last update: 4-Jan-2015
  No proprietary drivers.
  No 3rd party software.

  The last kernel I was able to run on my Utopic system is
  3.16.0-17-generic. Every update thereafter failed. The last one I
  tried is -28.

  From syslog for -28 kernel:

  Jan  4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [   10.340446] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [   10.340448] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [  101.573768] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [  101.573771] [drm:radeon_init] *ERROR* No 
UMS support in radeon module! 

  From syslog for -17 kernel:

  Jan  4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel 
modesetting enabled.


   
  Jan  4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb 
from VESA VGA   

  
  Jan  4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel 
modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA).

[Kernel-packages] [Bug 1576367] Re: Aquaris M10 tablet can't connect to bluetooth version 4.0 devices

2016-04-28 Thread Tomas Öqvist

Interestingly I managed to pair the Designer Mouse through bluetoothctl
in the terminal. It is still not recognized by the bluetooth system
settings though, which shows only my connected keyboard!!

My trick seems to survive a reboot, but I have to turn bluetooth off and
then on again for the mouse to become reenabled. Remains to be seen if
this trick will work with the foldable keyboard as well.

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

Title:
  Aquaris M10 tablet can't connect to bluetooth version 4.0 devices

Status in bluez package in Ubuntu:
  New

Bug description:
  I have tried to pair my Bq Aquaris M10 running Ubuntu 15.05 (OTA-10.1)
  to Microsofts Universal Foldable Keyboard and Designer Moust, both
  equipped with bluetooth version 4.0 through the bluetooth settings on
  the tablet.

  Expected behaviour:
  Search and discover device
  Click on device and choose "pair"

  What happens:
  Nothing
  None of the devices above are being discovered in the bluetooth settings.

  The command

  dpkg --status bluez | grep '^Version:'

  on the tablet gives me:

  Version: 5.37-0ubuntu5-overlay1

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

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

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

apport information

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

Title:
  No UMS support in radeon module

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Confirmed

Bug description:
  System: Kubuntu (adm64) 14.10.
  Last update: 4-Jan-2015
  No proprietary drivers.
  No 3rd party software.

  The last kernel I was able to run on my Utopic system is
  3.16.0-17-generic. Every update thereafter failed. The last one I
  tried is -28.

  From syslog for -28 kernel:

  Jan  4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [   10.340446] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [   10.340448] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [  101.573768] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [  101.573771] [drm:radeon_init] *ERROR* No 
UMS support in radeon module! 

  From syslog for -17 kernel:

  Jan  4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel 
modesetting enabled.


   
  Jan  4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb 
from VESA VGA   

  
  Jan  4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel 
modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA).


 
  Jan  4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 
0xFDDC  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 
131072  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM 
RAM=1024M, BAR=256M

[Kernel-packages] [Bug 1145234] Re: FAIL: parent ptrace(PTRACE_SINGLESTEP) failed - : No such process

This was not a qa-regression-testing bug, closing that task.

** Changed in: qa-regression-testing
   Status: Confirmed => Invalid

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

Title:
  FAIL: parent ptrace(PTRACE_SINGLESTEP) failed - : No such process

Status in QA Regression Testing:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Fix Released

Bug description:
  Running an SRU regression test for Lucid today, the ptrace tests seem to be 
failing.  The full logs of one of the runs can be found at:
  
https://jenkins.qa.ubuntu.com/job/sru_kernel-lucid-generic_amd64-kvm-virtual/14/testReport/junit/autotest/ubuntu_qrt_apparmor/test_apparmor_py/

  Proposed kernel version: 2.6.32-46.105-generic 2.6.32.60+drm33.26

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1145234/+subscriptions

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

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

apport information

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

Title:
  No UMS support in radeon module

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Confirmed

Bug description:
  System: Kubuntu (adm64) 14.10.
  Last update: 4-Jan-2015
  No proprietary drivers.
  No 3rd party software.

  The last kernel I was able to run on my Utopic system is
  3.16.0-17-generic. Every update thereafter failed. The last one I
  tried is -28.

  From syslog for -28 kernel:

  Jan  4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [   10.340446] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [   10.340448] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [  101.573768] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [  101.573771] [drm:radeon_init] *ERROR* No 
UMS support in radeon module! 

  From syslog for -17 kernel:

  Jan  4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel 
modesetting enabled.


   
  Jan  4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb 
from VESA VGA   

  
  Jan  4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel 
modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA).


 
  Jan  4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 
0xFDDC  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 
131072  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM 
RAM=1024M, BAR=256M

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

apport information

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

Title:
  No UMS support in radeon module

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Confirmed

Bug description:
  System: Kubuntu (adm64) 14.10.
  Last update: 4-Jan-2015
  No proprietary drivers.
  No 3rd party software.

  The last kernel I was able to run on my Utopic system is
  3.16.0-17-generic. Every update thereafter failed. The last one I
  tried is -28.

  From syslog for -28 kernel:

  Jan  4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [   10.340446] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [   10.340448] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [  101.573768] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [  101.573771] [drm:radeon_init] *ERROR* No 
UMS support in radeon module! 

  From syslog for -17 kernel:

  Jan  4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel 
modesetting enabled.


   
  Jan  4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb 
from VESA VGA   

  
  Jan  4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel 
modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA).


 
  Jan  4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 
0xFDDC  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 
131072  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM 
RAM=1024M, BAR=256M

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

apport information

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

Title:
  No UMS support in radeon module

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Confirmed

Bug description:
  System: Kubuntu (adm64) 14.10.
  Last update: 4-Jan-2015
  No proprietary drivers.
  No 3rd party software.

  The last kernel I was able to run on my Utopic system is
  3.16.0-17-generic. Every update thereafter failed. The last one I
  tried is -28.

  From syslog for -28 kernel:

  Jan  4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [   10.340446] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [   10.340448] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [  101.573768] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [  101.573771] [drm:radeon_init] *ERROR* No 
UMS support in radeon module! 

  From syslog for -17 kernel:

  Jan  4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel 
modesetting enabled.


   
  Jan  4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb 
from VESA VGA   

  
  Jan  4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel 
modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA).


 
  Jan  4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 
0xFDDC  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 
131072  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM 
RAM=1024M, BAR=256M

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

apport information

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

Title:
  No UMS support in radeon module

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Confirmed

Bug description:
  System: Kubuntu (adm64) 14.10.
  Last update: 4-Jan-2015
  No proprietary drivers.
  No 3rd party software.

  The last kernel I was able to run on my Utopic system is
  3.16.0-17-generic. Every update thereafter failed. The last one I
  tried is -28.

  From syslog for -28 kernel:

  Jan  4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [   10.340446] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [   10.340448] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [  101.573768] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [  101.573771] [drm:radeon_init] *ERROR* No 
UMS support in radeon module! 

  From syslog for -17 kernel:

  Jan  4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel 
modesetting enabled.


   
  Jan  4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb 
from VESA VGA   

  
  Jan  4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel 
modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA).


 
  Jan  4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 
0xFDDC  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 
131072  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM 
RAM=1024M, BAR=256M

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

apport information

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

Title:
  No UMS support in radeon module

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Confirmed

Bug description:
  System: Kubuntu (adm64) 14.10.
  Last update: 4-Jan-2015
  No proprietary drivers.
  No 3rd party software.

  The last kernel I was able to run on my Utopic system is
  3.16.0-17-generic. Every update thereafter failed. The last one I
  tried is -28.

  From syslog for -28 kernel:

  Jan  4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [   10.340446] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [   10.340448] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [  101.573768] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [  101.573771] [drm:radeon_init] *ERROR* No 
UMS support in radeon module! 

  From syslog for -17 kernel:

  Jan  4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel 
modesetting enabled.


   
  Jan  4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb 
from VESA VGA   

  
  Jan  4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel 
modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA).


 
  Jan  4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 
0xFDDC  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 
131072  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM 
RAM=1024M, BAR=256M

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

apport information

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

Title:
  No UMS support in radeon module

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Confirmed

Bug description:
  System: Kubuntu (adm64) 14.10.
  Last update: 4-Jan-2015
  No proprietary drivers.
  No 3rd party software.

  The last kernel I was able to run on my Utopic system is
  3.16.0-17-generic. Every update thereafter failed. The last one I
  tried is -28.

  From syslog for -28 kernel:

  Jan  4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [   10.340446] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [   10.340448] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [  101.573768] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [  101.573771] [drm:radeon_init] *ERROR* No 
UMS support in radeon module! 

  From syslog for -17 kernel:

  Jan  4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel 
modesetting enabled.


   
  Jan  4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb 
from VESA VGA   

  
  Jan  4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel 
modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA).


 
  Jan  4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 
0xFDDC  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 
131072  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM 
RAM=1024M, BAR=256M

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

apport information

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

Title:
  No UMS support in radeon module

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Confirmed

Bug description:
  System: Kubuntu (adm64) 14.10.
  Last update: 4-Jan-2015
  No proprietary drivers.
  No 3rd party software.

  The last kernel I was able to run on my Utopic system is
  3.16.0-17-generic. Every update thereafter failed. The last one I
  tried is -28.

  From syslog for -28 kernel:

  Jan  4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [   10.340446] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [   10.340448] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [  101.573768] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [  101.573771] [drm:radeon_init] *ERROR* No 
UMS support in radeon module! 

  From syslog for -17 kernel:

  Jan  4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel 
modesetting enabled.


   
  Jan  4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb 
from VESA VGA   

  
  Jan  4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel 
modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA).


 
  Jan  4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 
0xFDDC  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 
131072  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM 
RAM=1024M, BAR=256M

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

apport information

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

Title:
  No UMS support in radeon module

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Confirmed

Bug description:
  System: Kubuntu (adm64) 14.10.
  Last update: 4-Jan-2015
  No proprietary drivers.
  No 3rd party software.

  The last kernel I was able to run on my Utopic system is
  3.16.0-17-generic. Every update thereafter failed. The last one I
  tried is -28.

  From syslog for -28 kernel:

  Jan  4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [   10.340446] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [   10.340448] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [  101.573768] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [  101.573771] [drm:radeon_init] *ERROR* No 
UMS support in radeon module! 

  From syslog for -17 kernel:

  Jan  4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel 
modesetting enabled.


   
  Jan  4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb 
from VESA VGA   

  
  Jan  4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel 
modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA).


 
  Jan  4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 
0xFDDC  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 
131072  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM 
RAM=1024M, BAR=256M

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

apport information

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

Title:
  No UMS support in radeon module

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Confirmed

Bug description:
  System: Kubuntu (adm64) 14.10.
  Last update: 4-Jan-2015
  No proprietary drivers.
  No 3rd party software.

  The last kernel I was able to run on my Utopic system is
  3.16.0-17-generic. Every update thereafter failed. The last one I
  tried is -28.

  From syslog for -28 kernel:

  Jan  4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [   10.340446] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [   10.340448] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [  101.573768] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [  101.573771] [drm:radeon_init] *ERROR* No 
UMS support in radeon module! 

  From syslog for -17 kernel:

  Jan  4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel 
modesetting enabled.


   
  Jan  4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb 
from VESA VGA   

  
  Jan  4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel 
modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA).


 
  Jan  4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 
0xFDDC  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 
131072  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM 
RAM=1024M, BAR=256M

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

apport information

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

Title:
  No UMS support in radeon module

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Confirmed

Bug description:
  System: Kubuntu (adm64) 14.10.
  Last update: 4-Jan-2015
  No proprietary drivers.
  No 3rd party software.

  The last kernel I was able to run on my Utopic system is
  3.16.0-17-generic. Every update thereafter failed. The last one I
  tried is -28.

  From syslog for -28 kernel:

  Jan  4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [   10.340446] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [   10.340448] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [  101.573768] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [  101.573771] [drm:radeon_init] *ERROR* No 
UMS support in radeon module! 

  From syslog for -17 kernel:

  Jan  4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel 
modesetting enabled.


   
  Jan  4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb 
from VESA VGA   

  
  Jan  4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel 
modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA).


 
  Jan  4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 
0xFDDC  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 
131072  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM 
RAM=1024M, BAR=256M

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

apport information

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

Title:
  No UMS support in radeon module

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Confirmed

Bug description:
  System: Kubuntu (adm64) 14.10.
  Last update: 4-Jan-2015
  No proprietary drivers.
  No 3rd party software.

  The last kernel I was able to run on my Utopic system is
  3.16.0-17-generic. Every update thereafter failed. The last one I
  tried is -28.

  From syslog for -28 kernel:

  Jan  4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [   10.340446] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [   10.340448] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [  101.573768] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [  101.573771] [drm:radeon_init] *ERROR* No 
UMS support in radeon module! 

  From syslog for -17 kernel:

  Jan  4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel 
modesetting enabled.


   
  Jan  4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb 
from VESA VGA   

  
  Jan  4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel 
modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA).


 
  Jan  4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 
0xFDDC  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 
131072  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM 
RAM=1024M, BAR=256M

[Kernel-packages] [Bug 1407505] Re: No UMS support in radeon module

ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC3:  marco  1976 F pulseaudio
 /dev/snd/controlC0:  marco  1976 F pulseaudio
 /dev/snd/controlC1:  marco  1976 F pulseaudio
 /dev/snd/controlC2:  marco  1976 F pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
InstallationDate: Installed on 2016-04-22 (5 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
 enp9s0no wireless extensions.
 
 enp7s0no wireless extensions.
 
 lono wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=dc0372d0-03d5-4b50-9cbb-a83a7c27da67 ro recovery nomodeset
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 xenial
Uname: Linux 4.4.0-21-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/03/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0610
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6T DELUXE V2
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.:bvr0610:bd09/03/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXEV2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer


** Tags added: apport-collected 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/1407505

Title:
  No UMS support in radeon module

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Confirmed

Bug description:
  System: Kubuntu (adm64) 14.10.
  Last update: 4-Jan-2015
  No proprietary drivers.
  No 3rd party software.

  The last kernel I was able to run on my Utopic system is
  3.16.0-17-generic. Every update thereafter failed. The last one I
  tried is -28.

  From syslog for -28 kernel:

  Jan  4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [   10.340446] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [   10.340448] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [  101.573768] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [  101.573771] [drm:radeon_init] *ERROR* No 
UMS support in radeon module! 

  From syslog for -17 kernel:

  Jan  4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 
20060810

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

apport information

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

Title:
  No UMS support in radeon module

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Confirmed

Bug description:
  System: Kubuntu (adm64) 14.10.
  Last update: 4-Jan-2015
  No proprietary drivers.
  No 3rd party software.

  The last kernel I was able to run on my Utopic system is
  3.16.0-17-generic. Every update thereafter failed. The last one I
  tried is -28.

  From syslog for -28 kernel:

  Jan  4 14:22:41 aldebaran kernel: [1.712424] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:22:41 aldebaran kernel: [1.736322] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [1.736375] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [   10.340446] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [   10.340448] [drm:radeon_init] *ERROR* No 
UMS support in radeon module!   

  
  Jan  4 14:22:41 aldebaran kernel: [  101.573768] [drm] VGACON disable radeon 
kernel modesetting. 

   
  Jan  4 14:22:41 aldebaran kernel: [  101.573771] [drm:radeon_init] *ERROR* No 
UMS support in radeon module! 

  From syslog for -17 kernel:

  Jan  4 14:27:56 aldebaran kernel: [1.676277] [drm] Initialized drm 1.1.0 
20060810

   
  Jan  4 14:27:56 aldebaran kernel: [1.698850] [drm] radeon kernel 
modesetting enabled.


   
  Jan  4 14:27:56 aldebaran kernel: [1.698924] fb: switching to radeondrmfb 
from VESA VGA   

  
  Jan  4 14:27:56 aldebaran kernel: [1.699341] [drm] initializing kernel 
modesetting (TURKS 0x1002:0x6758 0x1043:0x03EA).


 
  Jan  4 14:27:56 aldebaran kernel: [1.699351] [drm] register mmio base: 
0xFDDC  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699352] [drm] register mmio size: 
131072  


 
  Jan  4 14:27:56 aldebaran kernel: [1.699877] [drm] Detected VRAM 
RAM=1024M, BAR=256M

[Kernel-packages] [Bug 1027524] Re: QRT failed on test_072_config_debug_rodata and test_072_strict_devmem

The tests in question have been modified to take the different
architectures where CONFIG_DEBUG_RODATA and CONFIG_STRICT_DEVMEM are
enabled into account. Closing this bug.

** Changed in: qa-regression-testing
   Status: Confirmed => Fix Released

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

Title:
  QRT failed on test_072_config_debug_rodata and test_072_strict_devmem

Status in QA Regression Testing:
  Fix Released
Status in linux-ti-omap4 package in Ubuntu:
  Invalid

Bug description:
  ubuntu@panda-quantal:~/qrt-test-kernel$ sudo ./test-kernel-security.py -v
  Running test: './test-kernel-security.py' distro: 'Ubuntu 12.10' kernel: 
'3.4.0-203.8 (Ubuntu 3.4.0-203.8-omap4 3.4.0)' arch: 'armhf' uid: 0/0 
SUDO_USER: 'ubuntu')
  test_000_make (__main__.KernelSecurityTest)
  Prepare to build helper tools ... (4.7.1 (Ubuntu/Linaro 4.7.1-5ubuntu1)) ok
  test_010_proc_maps (__main__.KernelSecurityTest)
  /proc/$pid/maps is correctly protected ... ok
  test_020_aslr_00_proc (__main__.KernelSecurityTest)
  ASLR enabled ... ok
  test_020_aslr_dapper_stack (__main__.KernelSecurityTest)
  ASLR of stack ... ok
  test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
  ASLR of libs ... ok
  test_021_aslr_dapper_mmap (__main__.KernelSecurityTest)
  ASLR of mmap ... ok
  test_022_aslr_hardy_text (__main__.KernelSecurityTest)
  ASLR of text ... ok
  test_022_aslr_hardy_vdso (__main__.KernelSecurityTest)
  ASLR of vdso ...  (skipped: only x86) ok
  test_022_aslr_intrepid_brk (__main__.KernelSecurityTest)
  ASLR of brk ... ok
  test_030_mmap_min (__main__.KernelSecurityTest)
  Low memory allocation respects mmap_min_addr ...  (32768) ok
  test_031_apparmor (__main__.KernelSecurityTest)
  AppArmor loaded ... ok
  test_031_seccomp (__main__.KernelSecurityTest)
  PR_SET_SECCOMP works ... ok
  test_032_dev_kmem (__main__.KernelSecurityTest)
  /dev/kmem not available ... ok
  test_033_syn_cookies (__main__.KernelSecurityTest)
  SYN cookies is enabled ... ok
  test_040_pcaps (__main__.KernelSecurityTest)
  init's CAPABILITY list is clean ... ok
  test_050_personality (__main__.KernelSecurityTest)
  init missing READ_IMPLIES_EXEC ...  (/proc/1/personality) ok
  test_060_nx (__main__.KernelSecurityTest)
  NX bit is working ... ok
  test_061_guard_page (__main__.KernelSecurityTest)
  Userspace stack guard page exists (CVE-2010-2240) ... ok
  test_070_config_brk (__main__.KernelSecurityTest)
  CONFIG_COMPAT_BRK disabled ... ok
  test_070_config_devkmem (__main__.KernelSecurityTest)
  CONFIG_DEVKMEM disabled ... ok
  test_070_config_seccomp (__main__.KernelSecurityTest)
  CONFIG_SECCOMP enabled ... ok
  test_070_config_security (__main__.KernelSecurityTest)
  CONFIG_SECURITY enabled ... ok
  test_070_config_security_selinux (__main__.KernelSecurityTest)
  CONFIG_SECURITY_SELINUX enabled ... ok
  test_070_config_syn_cookies (__main__.KernelSecurityTest)
  CONFIG_SYN_COOKIES enabled ... ok
  test_071_config_seccomp (__main__.KernelSecurityTest)
  CONFIG_SECCOMP enabled ... ok
  test_072_config_compat_vdso (__main__.KernelSecurityTest)
  CONFIG_COMPAT_VDSO disabled ... ok
  test_072_config_debug_rodata (__main__.KernelSecurityTest)
  CONFIG_DEBUG_RODATA enabled ...  (skipped: only x86) FAIL
  test_072_config_debug_set_module_ronx (__main__.KernelSecurityTest)
  CONFIG_DEBUG_SET_MODULE_RONX enabled ...  (skipped: only x86) ok
  test_072_config_security_apparmor (__main__.KernelSecurityTest)
  CONFIG_SECURITY_APPARMOR enabled ... ok
  test_072_config_strict_devmem (__main__.KernelSecurityTest)
  CONFIG_STRICT_DEVMEM enabled ... ok
  test_072_strict_devmem (__main__.KernelSecurityTest)
  /dev/mem unreadable for kernel memory ... FAIL
  test_073_config_security_file_capabilities (__main__.KernelSecurityTest)
  CONFIG_SECURITY_FILE_CAPABILITIES enabled ...  (skipped: only Intrepid 
through Lucid) ok
  test_073_config_security_smack (__main__.KernelSecurityTest)
  CONFIG_SECURITY_SMACK enabled ... ok
  test_074_config_security_default_mmap_min_addr (__main__.KernelSecurityTest)
  CONFIG_DEFAULT_MMAP_MIN_ADDR ...  (32768) ok
  test_075_config_stack_protector (__main__.KernelSecurityTest)
  CONFIG_CC_STACKPROTECTOR set ... ok
  test_082_stack_guard_kernel (__main__.KernelSecurityTest)
  Kernel stack guard ... ok
  test_090_module_blocking (__main__.KernelSecurityTest)
  Sysctl to disable module loading exists ... ok
  test_091_symlink_following_in_sticky_directories (__main__.KernelSecurityTest)
  Symlinks not followable across differing uids in sticky directories ... ok
  test_092_hardlink_restriction (__main__.KernelSecurityTest)
  Hardlink disallowed for unreadable/unwritable sources ... ok
  test_093_ptrace_restriction (__main__.KernelSecurityTest)
  ptrace allowed only on children or declared processes ... ok
  test_093_ptrace_restriction_extras (__main__.KernelSecurityTest)
  ptrace from thread on tracee

[Kernel-packages] [Bug 1571791] fozzie (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.4.0-22.38/fozzie__4.4.0-22.38__2016-04-28_20-03-00/results-index.html

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

Title:
  linux: 4.4.0-21.37 -proposed tracker

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

Bug description:
  This bug is for tracking the 4.4.0-21.37 upload package. This bug will
  contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Monday, 18. April 2016 18:15 UTC
  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true

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

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

[Kernel-packages] [Bug 1574690] Re: linux: 4.4.0-22.38 -proposed tracker

** Tags added: regression-tests-passed

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

Title:
  linux: 4.4.0-22.38 -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:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  This bug is for tracking the 4.4.0-22.38 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 --
  phase: Promoted to proposed
  proposed-announcement-sent: true

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

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

[Kernel-packages] [Bug 1575437] Re: Asus ZenBook UX501VW frequently hangs during boot under Ubuntu 16.04

2016-04-28 Thread Stéphane Roussel

When i hae tried 4.6-rc5-wily without nvidia, the bugs still present.

But when i tried to install nvidia driver, kernel mod does not compil,
nouveau driver does not load and intel graphic work fine.

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

Title:
  Asus ZenBook UX501VW frequently hangs during boot under Ubuntu 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A fresh install of Ubuntu Gnome 16.04 on an Asus ZenBook UX501VW hangs
  during boot, approximately 80% to 90% of the time... occasionally it
  manages to complete the startup for no discrenable reason, at which
  point the fan will run at full speed nonstop (very loud) until the
  machine is powered down. Due to the information from
  , I installed the wily 4.3.5 kernel (replacing 4.4.0)
  from ,
  which appears to work perfectly... no bootup hangs or odd fan
  behaviour

  The hang occurs shortly after providing the disk decryption key (I
  opted for full-disk encryption during installation). The issue occurs
  frequently when booting Ubuntu Gnome from a flash drive using "try
  before installation" mode, however, so I'm confident that it's not
  actually encryption related.

  I am *not* using any proprietary drivers (no nvidia, etc.).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: 
boot/vmlinuz-4.4.0-21-generic]
  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:  adric  1574 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Apr 26 19:19:26 2016
  HibernationDevice: RESUME=UUID=74c52e77-74c8-49d1-843b-23584516bd07
  InstallationDate: Installed on 2016-04-26 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  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: 02/03/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN501VW.206:bd02/03/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  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/1575437/+subscriptions

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

[Kernel-packages] [Bug 1566221] Re: linux: Enforce signed module loading when UEFI secure boot

Vivid tested in QEMU/OVMF with signed kernel, with and without
MokSBState enabled.

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

Title:
  linux: Enforce signed module loading when UEFI secure boot

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

Bug description:
  This work is authorized by an approved UOS spec and blueprint at
  https://wiki.ubuntu.com/Spec/InstallingUnsignedSecureBoot

  Add code to implement secure boot checks. Unsigned or incorrectly
  signed modules will continue to install while tainting the kernel
  _until_ EFI_SECURE_BOOT_SIG_ENFORCE is enabled.

  When EFI_SECURE_BOOT_SIG_ENFORCE is enabled, then the only recourse
  for platforms booting in secure boot mode with a DKMS dependency is to
  disable secure boot using mokutil:

  sudo mokutil --disable-validation
  sudo reboot

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

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

[Kernel-packages] [Bug 1576367] Re: Aquaris M10 tablet can't connect to bluetooth version 4.0 devices

2016-04-28 Thread Tomas Öqvist

Is it the fact that these bluetooth devices are "bluetooth smart" or BLE
enabled that is the problem? If so, in what way and is it something we
can expect to be fixed in future versions of Bluez?

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

Title:
  Aquaris M10 tablet can't connect to bluetooth version 4.0 devices

Status in bluez package in Ubuntu:
  New

Bug description:
  I have tried to pair my Bq Aquaris M10 running Ubuntu 15.05 (OTA-10.1)
  to Microsofts Universal Foldable Keyboard and Designer Moust, both
  equipped with bluetooth version 4.0 through the bluetooth settings on
  the tablet.

  Expected behaviour:
  Search and discover device
  Click on device and choose "pair"

  What happens:
  Nothing
  None of the devices above are being discovered in the bluetooth settings.

  The command

  dpkg --status bluez | grep '^Version:'

  on the tablet gives me:

  Version: 5.37-0ubuntu5-overlay1

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

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

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

This change was made by a bot.

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

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

Title:
  Macbook Air network unreliable under Xenial

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This seems to be a regression from Wily.   I previously had Wily
  installed on this Macbook Air and noticed no issues with network
  connectivity.

  Yesterday I upgraded to Xenial and networking has been unreliable ever
  since.  It seems to be OK after booting, but after a while of use
  (maybe an hour? maybe less) I start to see a lot of packets dropped
  and very high RTT per ping.

  At first I thought this may have been an issue with my ISP, as I was
  seeing THIS while pinging 8.8.8.8 from my Xenial install:

   64 bytes from 8.8.8.8: icmp_seq=116 ttl=40 time=28.5 ms
  64 bytes from 8.8.8.8: icmp_seq=117 ttl=40 time=27.8 ms
  64 bytes from 8.8.8.8: icmp_seq=122 ttl=40 time=49879 ms
  64 bytes from 8.8.8.8: icmp_seq=123 ttl=40 time=49096 ms
  64 bytes from 8.8.8.8: icmp_seq=124 ttl=40 time=48228 ms

  But I pinged using a network tools app on iOS connected to the same
  WiFI network (using Cable internet as the outbound connection) and
  pings were very steady in the 30ms range with no dropped packets.

  Needless to say, this makes working VERY difficult, as I am unable to
  reliably do hangouts, download files, work on GoogleDocs, or maintain
  SSH connections or VPN connections because of the unreliable network.

  So I rebooted and ran several ping tests on OSX, and the results are
  as follows:

  --- 8.8.8.8 ping statistics ---
  100 packets transmitted, 100 packets received, 0.0% packet loss
  round-trip min/avg/max/stddev = 21.692/30.785/91.193/12.906 ms

  --- 8.8.8.8 ping statistics ---
  100 packets transmitted, 100 packets received, 0.0% packet loss
  round-trip min/avg/max/stddev = 21.726/28.498/58.639/7.604 ms

  Then on Xenial after rebooting:
  bladernr@Rogue1:~$ uptime
   15:06:12 up 42 min,  2 users,  load average: 0.17, 0.18, 0.21

  --- 8.8.8.8 ping statistics ---
  100 packets transmitted, 26 received, 74% packet loss, time 99612ms
  rtt min/avg/max/mdev = 22.456/42.526/168.247/39.368 ms

  --- 8.8.8.8 ping statistics ---
  100 packets transmitted, 77 received, 23% packet loss, time 99275ms
  rtt min/avg/max/mdev = 23.043/36.687/195.534/28.956 ms

  --- 8.8.8.8 ping statistics ---
  100 packets transmitted, 43 received, +6 errors, 57% packet loss, time 99525ms
  rtt min/avg/max/mdev = 23.866/339.391/4078.260/859.057 ms, pipe 5

  And this is from my phone, run around the same time the pings were run
  from Xenial showing such issues with traffic:

  Results Summary
  Average RTT   41.97 ms
  Min/Max RTT   24.05/199.18 ms
  STD Deviation 26.37 ms
  Packets (Rvcd/Sent)   104/104 (100%)

  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
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bladernr   1614 F pulseaudio
   /dev/snd/controlC1:  bladernr   1614 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Apr 28 14:58:17 2016
  HibernationDevice: RESUME=UUID=1ec334c0-b29f-454a-9668-0e6f5cc2d152
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0290 Apple, Inc. 
   Bus 001 Device 006: ID 05ac:828f Apple, Inc. 
   Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookAir6,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=3d44-163a-4386-9871-83e8515efd90 ro quiet splash 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: 09/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0099.B20.1509081314
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-35C1E88140C3E6CF
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-35C1E88140C3E6CF
  dmi.modalias:

[Kernel-packages] [Bug 1576379] [NEW] Macbook Air network unreliable under Xenial

2016-04-28 Thread Jeff Lane

Public bug reported:

This seems to be a regression from Wily.   I previously had Wily
installed on this Macbook Air and noticed no issues with network
connectivity.

Yesterday I upgraded to Xenial and networking has been unreliable ever
since.  It seems to be OK after booting, but after a while of use (maybe
an hour? maybe less) I start to see a lot of packets dropped and very
high RTT per ping.

At first I thought this may have been an issue with my ISP, as I was
seeing THIS while pinging 8.8.8.8 from my Xenial install:

 64 bytes from 8.8.8.8: icmp_seq=116 ttl=40 time=28.5 ms
64 bytes from 8.8.8.8: icmp_seq=117 ttl=40 time=27.8 ms
64 bytes from 8.8.8.8: icmp_seq=122 ttl=40 time=49879 ms
64 bytes from 8.8.8.8: icmp_seq=123 ttl=40 time=49096 ms
64 bytes from 8.8.8.8: icmp_seq=124 ttl=40 time=48228 ms

But I pinged using a network tools app on iOS connected to the same WiFI
network (using Cable internet as the outbound connection) and pings were
very steady in the 30ms range with no dropped packets.

Needless to say, this makes working VERY difficult, as I am unable to
reliably do hangouts, download files, work on GoogleDocs, or maintain
SSH connections or VPN connections because of the unreliable network.

So I rebooted and ran several ping tests on OSX, and the results are as
follows:

--- 8.8.8.8 ping statistics ---
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 21.692/30.785/91.193/12.906 ms

--- 8.8.8.8 ping statistics ---
100 packets transmitted, 100 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 21.726/28.498/58.639/7.604 ms

Then on Xenial after rebooting:
bladernr@Rogue1:~$ uptime
 15:06:12 up 42 min,  2 users,  load average: 0.17, 0.18, 0.21

--- 8.8.8.8 ping statistics ---
100 packets transmitted, 26 received, 74% packet loss, time 99612ms
rtt min/avg/max/mdev = 22.456/42.526/168.247/39.368 ms

--- 8.8.8.8 ping statistics ---
100 packets transmitted, 77 received, 23% packet loss, time 99275ms
rtt min/avg/max/mdev = 23.043/36.687/195.534/28.956 ms

--- 8.8.8.8 ping statistics ---
100 packets transmitted, 43 received, +6 errors, 57% packet loss, time 99525ms
rtt min/avg/max/mdev = 23.866/339.391/4078.260/859.057 ms, pipe 5

And this is from my phone, run around the same time the pings were run
from Xenial showing such issues with traffic:

Results Summary
Average RTT 41.97 ms
Min/Max RTT 24.05/199.18 ms
STD Deviation   26.37 ms
Packets (Rvcd/Sent) 104/104 (100%)

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
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  bladernr   1614 F pulseaudio
 /dev/snd/controlC1:  bladernr   1614 F pulseaudio
CurrentDesktop: Unity
Date: Thu Apr 28 14:58:17 2016
HibernationDevice: RESUME=UUID=1ec334c0-b29f-454a-9668-0e6f5cc2d152
InstallationDate: Installed on 2015-10-21 (189 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 05ac:0290 Apple, Inc. 
 Bus 001 Device 006: ID 05ac:828f Apple, Inc. 
 Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of 
BCM2046 Bluetooth)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Apple Inc. MacBookAir6,1
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=3d44-163a-4386-9871-83e8515efd90 ro quiet splash 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: 09/08/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBA61.88Z.0099.B20.1509081314
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-35C1E88140C3E6CF
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookAir6,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-35C1E88140C3E6CF
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B20.1509081314:bd09/08/2015:svnAppleInc.:pnMacBookAir6,1:pvr1.0:rvnAppleInc.:rnMac-35C1E88140C3E6CF:rvrMacBookAir6,1:cvnAppleInc.:ct10:cvrMac-35C1E88140C3E6CF:
dmi.product.name: MacBookAir6,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple 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/1576379

Title:
  Macbook Air network unreliable under Xenial

Status in linux package in Ubuntu:
  New

Bug description:
  This seems to be a

[Kernel-packages] [Bug 1472478] Re: [Dell Venue 11 Pro 7140] Power button not working

2016-04-28 Thread Asvin

This bug appears to be still present on mainline kernel 4.6-rc5 and
16.04.

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

** Changed in: linux (Ubuntu)
   Status: Triaged => 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/1472478

Title:
  [Dell Venue 11 Pro 7140] Power button not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When pressing the power button on the Dell Venue 11 Pro 7140 there is
  no reaction. dmesg and showkey are not detecting any key event when
  pressing the power button.

  This is identical to the RedHat bug report:
  https://bugzilla.redhat.com/show_bug.cgi?id=1194632

  Here are my details:
  $sudo evtest /dev/input/event1
  Input driver version is 1.0.1
  Input device ID: bus 0x19 vendor 0x0 product 0x1 version 0x0
  Input device name: "Power Button"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 116 (KEY_POWER)
  Properties:
  Testing ... (interrupt to exit)

  [Pressing button gives no output]

  $cat /sys/firmware/acpi/interrupts/ff_pwr_btn
 0   invalid

  I've attached the acpidata.dat file as well as the minimum
  requirements.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-generic (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-43.58-generic 3.16.7-ckt13
  Uname: Linux 3.16.0-43-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tudor  1763 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jul  8 14:19:01 2015
  HibernationDevice: RESUME=UUID=3acb1340-1be5-453c-a918-25f6b6ff404e
  InstallationDate: Installed on 2015-07-06 (1 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 004: ID 114d:1002 Alpha Imaging Technology Corp. 
   Bus 001 Device 003: ID 0bda:5757 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Venue 11 Pro 7140
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-43-generic 
root=UUID=f0dc97e1-7d1c-4d05-a7d8-3cfc8551bdc4 ro quiet splash 
i915.i915_enable_rc6=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-43-generic N/A
   linux-backports-modules-3.16.0-43-generic  N/A
   linux-firmware 1.143.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-07-07 (0 days ago)
  dmi.bios.date: 06/30/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd06/30/2015:svnDellInc.:pnVenue11Pro7140:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7140
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1576367] [NEW] Aquaris M10 tablet can't connect to bluetooth version 4.0 devices

2016-04-28 Thread Tomas Öqvist

Public bug reported:

I have tried to pair my Bq Aquaris M10 running Ubuntu 15.05 (OTA-10.1)
to Microsofts Universal Foldable Keyboard and Designer Moust, both
equipped with bluetooth version 4.0 through the bluetooth settings on
the tablet.

Expected behaviour:
Search and discover device
Click on device and choose "pair"

What happens:
Nothing
None of the devices above are being discovered in the bluetooth settings.

The command

dpkg --status bluez | grep '^Version:'

on the tablet gives me:

Version: 5.37-0ubuntu5-overlay1

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

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

Title:
  Aquaris M10 tablet can't connect to bluetooth version 4.0 devices

Status in bluez package in Ubuntu:
  New

Bug description:
  I have tried to pair my Bq Aquaris M10 running Ubuntu 15.05 (OTA-10.1)
  to Microsofts Universal Foldable Keyboard and Designer Moust, both
  equipped with bluetooth version 4.0 through the bluetooth settings on
  the tablet.

  Expected behaviour:
  Search and discover device
  Click on device and choose "pair"

  What happens:
  Nothing
  None of the devices above are being discovered in the bluetooth settings.

  The command

  dpkg --status bluez | grep '^Version:'

  on the tablet gives me:

  Version: 5.37-0ubuntu5-overlay1

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

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

[Kernel-packages] [Bug 1532746] Re: SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

2016-04-28 Thread César Alejandro Bustíos Benites

Ok, I confirm that is working perfectly with:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.dumbkbd=1"

Cheers!

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

Title:
  SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I've a problem with the keyboard of notebook HP Pavilion 15 ab062nl.
  the problem is with SHIFT ALT and CTRL buttons of the keyboard.

  for example when i use ALT-TAB shortcut, after few seconds, the ALT-TAB menu 
disappear as if i release ALT key, but isn't so.
  another example is when i navigate on web, when i scroll page with mouse 
wheel, sometimes the page start to resize, as if i'm pressing CTRL command 
while scroll, or if i'm writing a text, sometimes, borwser launch shortcut, as 
if i'm pressing CTRL while i type text, for exaple if i'm typing "b" letter, 
opens bookmarks...

  another example is while i'm typing text, if i press SHIFT key and
  start typing, begins to write uppercase letters and after a while,
  writes lowercase like I released shift, but i'm still pressing shift.

  for example if i press SHIFT+s, the result is this:
  SSs
  some letters are uppercase, but others are lowercase.

  i haven't found a solution.
  the only way to solve momentarily the problem, is pressing for some seconds 
the only SHIFT key, after that, the problems disappears indefinitely, or until 
the next restart.

  This problem occurs with all ubuntu version (x86 and x86_64), now i'm
  using Ubuntu 15.10, but i've also tried ubuntu 15.04, ubuntu 14.04,
  ubuntu 12.04, ubuntu 10.04.

  furthermore i've this problem also with other GNU/Linux Distributions (i've 
tried Fedora, OpenSuse, ArchLinux, Antergos, Debian, SteamOS).
  but isn't and hardware problem, because on Windows 8.1 and Windows 10 i 
haven't these problems.

  i've also tried to plug in an externa USB keyboard, and if i use
  external USB keybaord i haven't problems.

  i think is a problem of compatibility, with integrated keyboard of
  this notebook.

  i've tried to monitor these problems using XEV, and the results is
  that also if i'm not using notebook, sometimes XEV reads an INPUT of
  one of these 3 key (SHIFT, ALT, CTRL), and while i'm pressing one of
  these 3 key, XEV see also if i release and immedialty after press
  again the key.

  this is an example of the input while i press Left_ALT key for a while

  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 129987, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  KeyRelease event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130147, (-142,152), root:(452,476),
  state 0x18, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130391, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  whole log here http://pastebin.com/CPGz40aw

  and this is the output of xev, leaving the notebook on a few hours
  without using it http://pastebin.com/sYSHAbGy

  
  this is "xinput" output

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Laser Mouseid=11   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ HP Truevision HDid=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=14   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=15   [slave  
keyboard (3)]

  i hope that this bug can be solved

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic

[Kernel-packages] [Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

2016-04-28 Thread Rasmus Larsen

Bisecting...

Current candidate seems to be 31c2013e4ea2e594522980acc3d20e88664b19f1

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

Bug description:
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 4.4.0-21-generic (buildd@lgw01-21) (gcc version 
5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 
UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=8ea401db-b84b-4cd6-a628-d72f30bbf1e5 ro console=tty1 console=ttyS0
  [0.00] KERNEL supported cpus:
  [0.00]   Intel GenuineIntel
  [0.00]   AMD AuthenticAMD
  [0.00]   Centaur CentaurHauls
  [0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
  [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point 
registers'
  [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
  [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
  [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 
bytes, using 'standard' format.
  [0.00] x86/fpu: Using 'eager' FPU context switches.
  [0.00] e820: BIOS-provided physical RAM map:
  [0.00] BIOS-e820: [mem 0x-0x0009dfff] usable
  [0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved
  [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
  [0.00] BIOS-e820: [mem 0x0010-0xefff] usable
  [0.00] BIOS-e820: [mem 0xfc00-0x] reserved
  [0.00] BIOS-e820: [mem 0x0001-0x0001efff] usable
  [0.00] NX (Execute Disable) protection: active
  [0.00] SMBIOS 2.4 present.
  [0.00] Hypervisor detected: Xen
  [0.00] Xen version 4.2.
  [0.00] Netfront and the Xen platform PCI driver have been compiled 
for this kernel: unplug emulated NICs.
  [0.00] Blkfront and the Xen platform PCI driver have been compiled 
for this kernel: unplug emulated disks.
  [0.00] You might have to change the root device
  [0.00] from /dev/hd[a-d] to /dev/xvd[a-d]
  [0.00] in your root= kernel command line option
  [0.00] e820: last_pfn = 0x1f max_arch_pfn = 0x4
  [0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
  [0.00] e820: last_pfn = 0xf max_arch_pfn = 0x4
  [0.00] found SMP MP-table at [mem 0x000fbba0-0x000fbbaf] mapped at 
[880fbba0]
  [0.00] Scanning 1 areas for low memory corruption
  [0.00] RAMDISK: [mem 0x3407e000-0x36036fff]
  [0.00] ACPI: Early table checksum verification disabled
  [0.00] ACPI: RSDP 0x000EA020 24 (v02 Xen   )
  [0.00] ACPI: XSDT 0xFC00F5A0 54 (v01 XenHVM  
 HVML )
  [0.00] ACPI: FACP 0xFC00F260 F4 (v04 XenHVM  
 HVML )
  [0.00] ACPI: DSDT 0xFC0035E0 00BBF6 (v02 XenHVM  
 INTL 20090123)
  [0.00] ACPI: FACS 0xFC0035A0 40
  [0.00] ACPI: FACS 0xFC0035A0 40
  [0.00] ACPI: APIC 0xFC00F360 D8 (v02 XenHVM  
 HVML )
  [0.00] ACPI: HPET 0xFC00F4B0 38 (v01 XenHVM  
 HVML )
  [0.00] ACPI: WAET 0xFC00F4F0 28 (v01 XenHVM  
 HVML )
  [0.00] ACPI: SSDT 0xFC00F520 31 (v02 XenHVM  
 INTL 20090123)
  [0.00] ACPI: SSDT 0xFC00F560 31 (v02 XenHVM  
 INTL 20090123)
  [0.00] No NUMA configuration found
  [0.00] Faking a node at [mem 0x-0x0001efff]
  [0.00] NODE_DATA(0) allocated [mem 0x1efff7000-0x1efffbfff]
  [0.00] Zone ranges:
  [0.00]   DMA  [mem 0x1000-0x00ff]
  [0.00]   DMA32[mem 0x0100-0x]
  [0.00]   Normal   [mem 0x0001-0x0001efff]
  [0.00]   Device   empty
  [0.00] Movable zone start for each node
  [0.00] Early memory node ranges
  [0.00]   node   0: [mem 0x1000-0x0009dfff]
  [0.00]   node   0: [mem 0x0010-0xefff]
  [0.00]   node   0: [mem 0x0001-0x0001efff]
  [0.00] Initmem setup node

[Kernel-packages] [Bug 1573062] Re: memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

** Tags added: kernel-key

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

Title:
  memory_stress_ng failing for IBM Power S812LC(TN71-BP012) for 16.04

Status in linux package in Ubuntu:
  Triaged

Bug description:
  memory_stress_ng, as part of server certification is failing for IBM
  Power S812LC(TN71-BP012) in bare metal mode. Failing in this case is
  defined by the test locking up the server in an unrecoverable state
  which only a reboot will fix.

  I will be attaching screen and kern logs for the failures and a
  successful run on 14.04 on the same server.

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

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

[Kernel-packages] [Bug 1571691] Re: linux: MokSBState is ignored

2016-04-28 Thread Pavel Rojtberg

re-read the initial description.
So if I get "[0.00] Secure boot MOKSBState disabled", this is exactly 
what I want?

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

Title:
  linux: MokSBState is ignored

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

Bug description:
  Ubuntu-4.4.0-20.36 was released with signed module enforcement
  enabled, but contained no way of disabling secure boot for DKMS.
  Without these kernel patches it is possible to get your machine in an
  unbootable state, especially if you don't have a fallback kernel.

  This patch set implements the ability to disable secure boot on demand
  from user space (with some password shennaigans). If one boots in
  secure boot mode and then installs a third party module (such as
  DKMS), then a dialog is displayed giving the user an option to disable
  secure boot, thereby also disabling module signature verification.
  Patch 1/2 is a scaffold patch of which only the GUID macros are
  actually used. The rest of the code is fenced by
  CONFIG_MODULE_SIG_UEFI which will not be enabled until a later series.
  Patch 2/2 is where MOKSBState is read and implemented. Patch 3/3
  simply prints a bit more informative state information.

  Information regarding secure boot and signed module enforcement will
  appear in the kernel log thusly:

  'Secure boot enabled' - normal secure boot operation with signed module 
enforcement.
  'Secure boot MOKSBState disabled' - UEFI Secure boot state has been 
over-ridden by MOKSBState. No signed module enforcement.

  In the absense of a 'Secure boot' string assume that secure boot is
  disabled or does not exist.

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

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

[Kernel-packages] [Bug 1571691] Re: linux: MokSBState is ignored

2016-04-28 Thread Pavel Rojtberg

1. asks for a password
2. Setting SB State Failed
3. nothing says I should reboot
4. upon reboot configuration screen pops up and asks random characters from the 
password entered before
5. allows me to disable verification

in case the above is the correct user story, I have the following
remark:

this seems to disable all verification after shim. Before the change the kernel 
was still verified and only the the modules were not.
Therefore I would say things were more secure before.

Is it possible to just disable signed module enforcement again?

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

Title:
  linux: MokSBState is ignored

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

Bug description:
  Ubuntu-4.4.0-20.36 was released with signed module enforcement
  enabled, but contained no way of disabling secure boot for DKMS.
  Without these kernel patches it is possible to get your machine in an
  unbootable state, especially if you don't have a fallback kernel.

  This patch set implements the ability to disable secure boot on demand
  from user space (with some password shennaigans). If one boots in
  secure boot mode and then installs a third party module (such as
  DKMS), then a dialog is displayed giving the user an option to disable
  secure boot, thereby also disabling module signature verification.
  Patch 1/2 is a scaffold patch of which only the GUID macros are
  actually used. The rest of the code is fenced by
  CONFIG_MODULE_SIG_UEFI which will not be enabled until a later series.
  Patch 2/2 is where MOKSBState is read and implemented. Patch 3/3
  simply prints a bit more informative state information.

  Information regarding secure boot and signed module enforcement will
  appear in the kernel log thusly:

  'Secure boot enabled' - normal secure boot operation with signed module 
enforcement.
  'Secure boot MOKSBState disabled' - UEFI Secure boot state has been 
over-ridden by MOKSBState. No signed module enforcement.

  In the absense of a 'Secure boot' string assume that secure boot is
  disabled or does not exist.

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

-- 
Mailing list: https://launchpad.net/~kernel-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-04-28 Thread Jonathan Hartley

@shinyblue: Very nice work.

Does the ticket title need updating to reflect it isn't just Nvidia
drivers?

-- 
You 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:
  New
Status in Ubuntu GNOME:
  New
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=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 1574814] Re: ThunderX: soft lockup in cursor_timer_handler() Edit

2016-04-28 Thread dann frazier

I have been able to reproduce a soft lockup using a pure upstream kernel
(post-4.5 git, after the thunderx pcie drivers were merged) and the d-i
initrd mentioned above. I've attached a log of one of those boots.

I used the Ubuntu config with the following exceptions:

CONFIG_DRM=y and CONFIG_DRM_AST=y - because, so far, I've only seen this with 
vga enabled.
CONFIG_KVM=n - because some commits fail to boot due to a panic in armpmu code, 
and KVM won't build w/ ARMPMU diabled.
(and just pressed enter during make oldconfig for everything else).

I could not reproduce with 4.6.0-rc1, so I thought this would be a good
bisect candidate. Unfortunately, that went off into the weeds for a
couple of reasons - vga doesn't work with some changesets, so I had to
skip those, and I also suspect that this issue does not appear in every
boot of a broken kernel, leading to false positive results.


** Attachment added: "upstream-kernel-softlockup.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574814/+attachment/4650499/+files/upstream-kernel-softlockup.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/1574814

Title:
  ThunderX: soft lockup in cursor_timer_handler() Edit

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I booted a Cavium ThunderX crb1s 2.0 system using the netboot mini iso via 
virtual media:

http://ports.ubuntu.com/ubuntu-ports/dists/xenial/main/installer-arm64/20101020ubuntu451/images/netboot/mini.iso

  During boot I observed the following lockup on the serial console:

  [ 28.128327] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 84.912299] NMI watchdog: BUG: soft lockup - CPU#14 stuck for 23s! 
[swapper/14:0]
  [ 84.922718] Modules linked in: hid_generic(E) usbhid(E) hid(E) 
usb_storage(E) mdio_thunder(E) nicvf(E) ast(E) i2c_algo_bit(E) 
drm_kms_helper(E) syscopyarea(E) sysfillrect(E) sysimgblt(E) fb_sys_fops(E) 
ttm(E) drm(E) nicpf(E) thunder_bgx(E) mdio_cavium(E)
  [ 84.922749]
  [ 84.922754] CPU: 14 PID: 0 Comm: swapper/14 Tainted: G E 4.4.0-21-generic 
#37-Ubuntu
  [ 84.922757] Hardware name: Cavium ThunderX CN88XX board (DT)
  [ 84.922761] task: 801f6c9d4100 ti: 801f6c9e8000 task.ti: 
801f6c9e8000
  [ 84.922771] PC is at cursor_timer_handler+0x30/0x58
  [ 84.922775] LR is at cursor_timer_handler+0x30/0x58
  [ 84.922778] pc : [] lr : [] pstate: 
00400145
  [ 84.922781] sp : 801f6c9ebc20
  [ 84.922784] x29: 801f6c9ebc20 x28: 8000f94398d8
  [ 84.922789] x27: 801f6c9ebd00 x26: 801f7b3bebb8
  [ 84.922793] x25: 801f6c9e8000 x24: 80e5ec00
  [ 84.922798] x23: 801f667d9800 x22: 804ec4c0
  [ 84.922802] x21: 0100 x20: 8000f94398d8
  [ 84.922807] x19: 8000f9439800 x18: c76a5358
  [ 84.922811] x17: 97bbd2a8 x16: 802a5040
  [ 84.922816] x15: 3e4cf1e0 x14: 0008
  [ 84.922820] x13:  x12: 003d0900
  [ 84.922824] x11: 003d0900 x10: 8090f200
  [ 84.922829] x9 : 3d09 x8 : 000e
  [ 84.922833] x7 : 801f7b3c5008 x6 : 
  [ 84.922837] x5 :  x4 : 0001
  [ 84.922842] x3 :  x2 : 801f6c899e05
  [ 84.922846] x1 : 801f667d99e0 x0 : 
  [ 84.922850]
  [ 101.008387] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 101.180375] usb 1-1.1: reset high-speed USB device number 3 using xhci_hcd
  [ 101.342677] random: nonblocking pool is initialized

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

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

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

This change was made by a bot.

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

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

Title:
  Freeze Screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   I am "just" surfing the internet(not running other app) with Chromium and 
suddenly it freezes. 
  No keyboard or mouse response the only option shutdown button. 
  My laptop it's an HP Pavillon x360, before the upgrade I was using 
Ubuntu14.04 and I never had this kind of freezes.
  I Just  upgraded to Ubuntu 16.04 (previously 15.04 as recommended) and I 
doesn't make other change (software or hardware) 
  The two days I am using ubuntu 16.04  I get the same error.

  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:  alfredpal   1887 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Apr 28 12:08:30 2016
  HibernationDevice: RESUME=UUID=0791f747-0831-4189-8bce-4cdeca672281
  InstallationDate: Installed on 2015-02-16 (437 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 002: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision 
HD camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=5bb61af5-fa7f-457f-865b-ef5255bf5231 ro quiet splash 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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2209
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.36
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/28/2014:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.36:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 11 x360 PC
  dmi.product.version: 097710405F00010420180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1576335] [NEW] Freeze Screen

2016-04-28 Thread alfred

Public bug reported:

 I am "just" surfing the internet(not running other app) with Chromium and 
suddenly it freezes. 
No keyboard or mouse response the only option shutdown button. 
My laptop it's an HP Pavillon x360, before the upgrade I was using Ubuntu14.04 
and I never had this kind of freezes.
I Just  upgraded to Ubuntu 16.04 (previously 15.04 as recommended) and I 
doesn't make other change (software or hardware) 
The two days I am using ubuntu 16.04  I get the same error.

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:  alfredpal   1887 F pulseaudio
CurrentDesktop: Unity
Date: Thu Apr 28 12:08:30 2016
HibernationDevice: RESUME=UUID=0791f747-0831-4189-8bce-4cdeca672281
InstallationDate: Installed on 2015-02-16 (437 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
 Bus 001 Device 002: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision HD 
camera
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=5bb61af5-fa7f-457f-865b-ef5255bf5231 ro quiet splash 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
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/28/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.14
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2209
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.36
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/28/2014:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097710405F00010420180:rvnHewlett-Packard:rn2209:rvr57.36:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion 11 x360 PC
dmi.product.version: 097710405F00010420180
dmi.sys.vendor: Hewlett-Packard

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


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

Title:
  Freeze Screen

Status in linux package in Ubuntu:
  Confirmed

Bug description:
   I am "just" surfing the internet(not running other app) with Chromium and 
suddenly it freezes. 
  No keyboard or mouse response the only option shutdown button. 
  My laptop it's an HP Pavillon x360, before the upgrade I was using 
Ubuntu14.04 and I never had this kind of freezes.
  I Just  upgraded to Ubuntu 16.04 (previously 15.04 as recommended) and I 
doesn't make other change (software or hardware) 
  The two days I am using ubuntu 16.04  I get the same error.

  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:  alfredpal   1887 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Apr 28 12:08:30 2016
  HibernationDevice: RESUME=UUID=0791f747-0831-4189-8bce-4cdeca672281
  InstallationDate: Installed on 2015-02-16 (437 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 002: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision 
HD camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=5bb61af5-fa7f-457f-865b-ef5255bf5231 ro quiet splash 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
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/28/2014
  dmi.bios.vendor: Insyde

[Kernel-packages] [Bug 1571156] Re: vbox: resync with 5.0.18-dfsg-2build1

2016-04-28 Thread LocutusOfBorg

I think you have to remove the virtualbox-dkms package.

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

Title:
  vbox: resync with 5.0.18-dfsg-2build1

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  We are behind main vbox packages:

  virtualbox (5.0.16-dfsg-3) experimental; urgency=low

* Build without xorg legacy with the backport of 5.0.17
  code (revision 106564)
* Bump std-version to 3.9.8, no changes required.
* Add vbox-img (LP: #1558521).
  - thanks sworddragon for the bug report!

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

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

[Kernel-packages] [Bug 1571156] Re: vbox: resync with 5.0.18-dfsg-2build1

2016-04-28 Thread Lars Kumbier

Tested proposed kernel 4.4.0-22.38 for xenial, does not solve the
virtualbox-bug. Virtualbox package is 5.0.18-dfsg-2build1, kernel module
won't load with error message "modprobe: ERROR: could not insert
'vboxdrv': Required key not available".

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

Title:
  vbox: resync with 5.0.18-dfsg-2build1

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  We are behind main vbox packages:

  virtualbox (5.0.16-dfsg-3) experimental; urgency=low

* Build without xorg legacy with the backport of 5.0.17
  code (revision 106564)
* Bump std-version to 3.9.8, no changes required.
* Add vbox-img (LP: #1558521).
  - thanks sworddragon for the bug report!

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

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

[Kernel-packages] [Bug 1566221] Re: linux: Enforce signed module loading when UEFI secure boot

Wily tested in QEMU/OVMF with signed kernel, with and without MokSBState
enabled.

** Description changed:

  Add code to implement secure boot checks. Unsigned or incorrectly signed
  modules will continue to install while tainting the kernel _until_
  EFI_SECURE_BOOT_SIG_ENFORCE is enabled.
+ 
+ When EFI_SECURE_BOOT_SIG_ENFORCE is enabled, then the only recourse for
+ platforms booting in secure boot mode with a DKMS dependency is to
+ disable secure boot using mokutils:
+ 
+ sudo mokutil --disable-validation
+ sudo reboot

** Description changed:

  Add code to implement secure boot checks. Unsigned or incorrectly signed
  modules will continue to install while tainting the kernel _until_
  EFI_SECURE_BOOT_SIG_ENFORCE is enabled.
  
  When EFI_SECURE_BOOT_SIG_ENFORCE is enabled, then the only recourse for
  platforms booting in secure boot mode with a DKMS dependency is to
- disable secure boot using mokutils:
+ disable secure boot using mokutil:
  
  sudo mokutil --disable-validation
  sudo reboot

** Description changed:

+ This work is authorized by an approved UOS spec at
+ https://wiki.ubuntu.com/Spec/InstallingUnsignedSecureBoot
+ 
  Add code to implement secure boot checks. Unsigned or incorrectly signed
  modules will continue to install while tainting the kernel _until_
  EFI_SECURE_BOOT_SIG_ENFORCE is enabled.
  
  When EFI_SECURE_BOOT_SIG_ENFORCE is enabled, then the only recourse for
  platforms booting in secure boot mode with a DKMS dependency is to
  disable secure boot using mokutil:
  
  sudo mokutil --disable-validation
  sudo reboot

** Description changed:

- This work is authorized by an approved UOS spec at
+ This work is authorized by an approved UOS spec and blueprint at
  https://wiki.ubuntu.com/Spec/InstallingUnsignedSecureBoot
  
  Add code to implement secure boot checks. Unsigned or incorrectly signed
  modules will continue to install while tainting the kernel _until_
  EFI_SECURE_BOOT_SIG_ENFORCE is enabled.
  
  When EFI_SECURE_BOOT_SIG_ENFORCE is enabled, then the only recourse for
  platforms booting in secure boot mode with a DKMS dependency is to
  disable secure boot using mokutil:
  
  sudo mokutil --disable-validation
  sudo reboot

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

Title:
  linux: Enforce signed module loading when UEFI secure boot

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

Bug description:
  This work is authorized by an approved UOS spec and blueprint at
  https://wiki.ubuntu.com/Spec/InstallingUnsignedSecureBoot

  Add code to implement secure boot checks. Unsigned or incorrectly
  signed modules will continue to install while tainting the kernel
  _until_ EFI_SECURE_BOOT_SIG_ENFORCE is enabled.

  When EFI_SECURE_BOOT_SIG_ENFORCE is enabled, then the only recourse
  for platforms booting in secure boot mode with a DKMS dependency is to
  disable secure boot using mokutil:

  sudo mokutil --disable-validation
  sudo reboot

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

-- 
Mailing list: https://launchpad.net/~kernel-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: Ubuntu 16.04 consistently freezes up / hangs

2016-04-28 Thread Andrew

It's up at the top. No worries. I think i changed it back. I do hope
someone is able to help us figure out what specific package this affects
as getting it to the right person should help speed up the bug fixing
process. I'm still not sure if this is a memory issue, or a kernel
issue, or a video driver issue, or a grub issue.

** Changed in: linux (Ubuntu)
   Status: Fix Released => 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/1575467

Title:
  Ubuntu 16.04 consistently freezes up / hangs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Not sure what package this is related to. I honestly have no idea.
  After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron
  laptop consistently freezes up and is unresponsive 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. So i wonder if this
  has something to do with my memory buffer or something. It seems to
  happen more often in Google Chrome than Firefox, but it happens with
  both. I know Google Chrome uses more memory though. And it has
  happened at least once with no videos loaded, so i doubt it's some
  sort of weird flash issue. 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.

  I will try to upload any log files that people think may be useful. I
  will see if i can do the recommended ssh monitoring method while
  trying to reproduce it to see if i can see an error that way.

  Not sure if this hardware info helps:
  lspci reports:
  00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
SoC Transaction Register (rev 0e)
  00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
  00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA 
AHCI Controller (rev 0e)
  00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, 
Celeron N2000 Series USB xHCI (rev 0e)
  00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx 
Series Trusted Execution Engine (rev 0e)
  00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
High Definition Audio Controller (rev 0e)
  00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 1 (rev 0e)
  00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 3 (rev 0e)
  00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
Power Control Unit (rev 0e)
  00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller 
(rev 0e)
  03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter (rev 01)

  andrew@andrew-Inspiron-3451:~$ sudo lshw
  andrew-inspiron-3451
  description: Computer
  width: 64 bits
  capabilities: smbios-2.8 vsyscall32
    *-core
     description: Motherboard
     physical id: 0
   *-memory
    description: System memory
    physical id: 0
    size: 3834MiB
   *-cpu
    product: Intel(R) Pentium(R) CPU  N3540  @ 2.16GHz
    vendor: Intel Corp.
    physical id: 1
    bus info: cpu@0
    size: 909MHz
    capacity: 2665MHz
    width: 64 bits
    capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good 
nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx 
est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer 
rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid 
tsc_adjust smep erms dtherm ida arat cpufreq
   *-pci
    description: Host bridge
    product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction 
Register
    vendor: Intel Corporation
    physical id: 100
    bus info: pci@:00:00.0
    version: 0e
    width: 32 bits
    clock: 33MHz
    configuration: driver=iosf_mbi_pci
    resources: irq:0
  *-display
   description: VGA compatible controller
   product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 0e
   width: 32 bits
   clock: 33MHz
   capabilities: pm msi vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:89 memory:d000-d03f 
memory:c000-cfff

[Kernel-packages] [Bug 1575467] Re: Ubuntu 16.04 consistently freezes up / hangs

2016-04-28 Thread Andrew

Thanks Tim, good to see other people have the same problem as usually
that means this is a bug that will get fixed quickly. And good to see
that there is a potential workaround to potentially solve the problem.
But isn't the "fix released" status meant for developers to mark?
Meaning that code has actually been changed in an upstream package and
future update? If your not a developer then i'm not sure the "fix
released" status is appropriate as it probably means no one will no
longer look at this bug because they think someone else already fixed
it.

In the past i may have ventured to go fiddling around with grub or some
other file (as i did in 14.04 with my non-working bluetooth), but for
something like this i'm only going to wait for an official fix. And to
me this is a pretty serious issue. If my understanding of how launchpad
works, then just ignore my comments.

I am also using 16.04 64bit. (not sure if many people still use 32bit or
if 32bit users are unaffected).

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

Title:
  Ubuntu 16.04 consistently freezes up / hangs

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Not sure what package this is related to. I honestly have no idea.
  After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron
  laptop consistently freezes up and is unresponsive 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. So i wonder if this
  has something to do with my memory buffer or something. It seems to
  happen more often in Google Chrome than Firefox, but it happens with
  both. I know Google Chrome uses more memory though. And it has
  happened at least once with no videos loaded, so i doubt it's some
  sort of weird flash issue. 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.

  I will try to upload any log files that people think may be useful. I
  will see if i can do the recommended ssh monitoring method while
  trying to reproduce it to see if i can see an error that way.

  Not sure if this hardware info helps:
  lspci reports:
  00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
SoC Transaction Register (rev 0e)
  00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
  00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA 
AHCI Controller (rev 0e)
  00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, 
Celeron N2000 Series USB xHCI (rev 0e)
  00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx 
Series Trusted Execution Engine (rev 0e)
  00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
High Definition Audio Controller (rev 0e)
  00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 1 (rev 0e)
  00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 3 (rev 0e)
  00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
Power Control Unit (rev 0e)
  00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller 
(rev 0e)
  03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter (rev 01)

  andrew@andrew-Inspiron-3451:~$ sudo lshw
  andrew-inspiron-3451
  description: Computer
  width: 64 bits
  capabilities: smbios-2.8 vsyscall32
    *-core
     description: Motherboard
     physical id: 0
   *-memory
    description: System memory
    physical id: 0
    size: 3834MiB
   *-cpu
    product: Intel(R) Pentium(R) CPU  N3540  @ 2.16GHz
    vendor: Intel Corp.
    physical id: 1
    bus info: cpu@0
    size: 909MHz
    capacity: 2665MHz
    width: 64 bits
    capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good 
nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx 
est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer 
rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid 
tsc_adjust smep erms dtherm ida arat cpufreq
   *-pci
    description: Host bridge
    product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction 
Register
    vendor: Intel Corporation
    physical id: 100
    bus info: pci@:00:00.0
    version: 0e
    width: 32 bits
    clock: 33MHz
    configuration: driver=iosf_mbi_pci

[Kernel-packages] [Bug 1532746] Re: SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

2016-04-28 Thread César Alejandro Bustíos Benites

Is this correct?

This is the original line on /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.old_scheme_first=1"

And now it looks like this:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.old_scheme_first=1
i8042.dumbkbd=1"

Should I be setting it to 1?

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

Title:
  SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I've a problem with the keyboard of notebook HP Pavilion 15 ab062nl.
  the problem is with SHIFT ALT and CTRL buttons of the keyboard.

  for example when i use ALT-TAB shortcut, after few seconds, the ALT-TAB menu 
disappear as if i release ALT key, but isn't so.
  another example is when i navigate on web, when i scroll page with mouse 
wheel, sometimes the page start to resize, as if i'm pressing CTRL command 
while scroll, or if i'm writing a text, sometimes, borwser launch shortcut, as 
if i'm pressing CTRL while i type text, for exaple if i'm typing "b" letter, 
opens bookmarks...

  another example is while i'm typing text, if i press SHIFT key and
  start typing, begins to write uppercase letters and after a while,
  writes lowercase like I released shift, but i'm still pressing shift.

  for example if i press SHIFT+s, the result is this:
  SSs
  some letters are uppercase, but others are lowercase.

  i haven't found a solution.
  the only way to solve momentarily the problem, is pressing for some seconds 
the only SHIFT key, after that, the problems disappears indefinitely, or until 
the next restart.

  This problem occurs with all ubuntu version (x86 and x86_64), now i'm
  using Ubuntu 15.10, but i've also tried ubuntu 15.04, ubuntu 14.04,
  ubuntu 12.04, ubuntu 10.04.

  furthermore i've this problem also with other GNU/Linux Distributions (i've 
tried Fedora, OpenSuse, ArchLinux, Antergos, Debian, SteamOS).
  but isn't and hardware problem, because on Windows 8.1 and Windows 10 i 
haven't these problems.

  i've also tried to plug in an externa USB keyboard, and if i use
  external USB keybaord i haven't problems.

  i think is a problem of compatibility, with integrated keyboard of
  this notebook.

  i've tried to monitor these problems using XEV, and the results is
  that also if i'm not using notebook, sometimes XEV reads an INPUT of
  one of these 3 key (SHIFT, ALT, CTRL), and while i'm pressing one of
  these 3 key, XEV see also if i release and immedialty after press
  again the key.

  this is an example of the input while i press Left_ALT key for a while

  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 129987, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  KeyRelease event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130147, (-142,152), root:(452,476),
  state 0x18, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130391, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  whole log here http://pastebin.com/CPGz40aw

  and this is the output of xev, leaving the notebook on a few hours
  without using it http://pastebin.com/sYSHAbGy

  
  this is "xinput" output

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Laser Mouseid=11   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ HP Truevision HDid=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=14   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys

[Kernel-packages] [Bug 1532746] Re: SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

2016-04-28 Thread César Alejandro Bustíos Benites

Ok, let me see if that works on my laptop and get back to you! 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/1532746

Title:
  SHIFT, ALT and CTRL problem with HP pavilion 15 ab062nl

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I've a problem with the keyboard of notebook HP Pavilion 15 ab062nl.
  the problem is with SHIFT ALT and CTRL buttons of the keyboard.

  for example when i use ALT-TAB shortcut, after few seconds, the ALT-TAB menu 
disappear as if i release ALT key, but isn't so.
  another example is when i navigate on web, when i scroll page with mouse 
wheel, sometimes the page start to resize, as if i'm pressing CTRL command 
while scroll, or if i'm writing a text, sometimes, borwser launch shortcut, as 
if i'm pressing CTRL while i type text, for exaple if i'm typing "b" letter, 
opens bookmarks...

  another example is while i'm typing text, if i press SHIFT key and
  start typing, begins to write uppercase letters and after a while,
  writes lowercase like I released shift, but i'm still pressing shift.

  for example if i press SHIFT+s, the result is this:
  SSs
  some letters are uppercase, but others are lowercase.

  i haven't found a solution.
  the only way to solve momentarily the problem, is pressing for some seconds 
the only SHIFT key, after that, the problems disappears indefinitely, or until 
the next restart.

  This problem occurs with all ubuntu version (x86 and x86_64), now i'm
  using Ubuntu 15.10, but i've also tried ubuntu 15.04, ubuntu 14.04,
  ubuntu 12.04, ubuntu 10.04.

  furthermore i've this problem also with other GNU/Linux Distributions (i've 
tried Fedora, OpenSuse, ArchLinux, Antergos, Debian, SteamOS).
  but isn't and hardware problem, because on Windows 8.1 and Windows 10 i 
haven't these problems.

  i've also tried to plug in an externa USB keyboard, and if i use
  external USB keybaord i haven't problems.

  i think is a problem of compatibility, with integrated keyboard of
  this notebook.

  i've tried to monitor these problems using XEV, and the results is
  that also if i'm not using notebook, sometimes XEV reads an INPUT of
  one of these 3 key (SHIFT, ALT, CTRL), and while i'm pressing one of
  these 3 key, XEV see also if i release and immedialty after press
  again the key.

  this is an example of the input while i press Left_ALT key for a while

  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 129987, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  KeyRelease event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130147, (-142,152), root:(452,476),
  state 0x18, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  KeyPress event, serial 37, synthetic NO, window 0x3e1,
  root 0x498, subw 0x0, time 130391, (-142,152), root:(452,476),
  state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
  XLookupString gives 0 bytes:
  XmbLookupString gives 0 bytes:
  XFilterEvent returns: False
   
  whole log here http://pastebin.com/CPGz40aw

  and this is the output of xev, leaving the notebook on a few hours
  without using it http://pastebin.com/sYSHAbGy

  
  this is "xinput" output

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Laser Mouseid=11   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Video Bus   id=8[slave  
keyboard (3)]
  ↳ Power Buttonid=9[slave  
keyboard (3)]
  ↳ HP Truevision HDid=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ HP WMI hotkeys  id=14   [slave  
keyboard (3)]
  ↳ HP Wireless hotkeys id=15   [slave  
keyboard (3)]

  i hope that this bug can be solved

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu

[Kernel-packages] [Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

2016-04-28 Thread Rasmus Larsen

I can still reproduce this in 4.6-rc5. See attached boot log.

I might do a bisect on this if I find the time...

** Attachment added: "kernel4.6-rc5.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573231/+attachment/4650339/+files/kernel4.6-rc5.log

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

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

Bug description:
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 4.4.0-21-generic (buildd@lgw01-21) (gcc version 
5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 
UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=8ea401db-b84b-4cd6-a628-d72f30bbf1e5 ro console=tty1 console=ttyS0
  [0.00] KERNEL supported cpus:
  [0.00]   Intel GenuineIntel
  [0.00]   AMD AuthenticAMD
  [0.00]   Centaur CentaurHauls
  [0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
  [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point 
registers'
  [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
  [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
  [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 
bytes, using 'standard' format.
  [0.00] x86/fpu: Using 'eager' FPU context switches.
  [0.00] e820: BIOS-provided physical RAM map:
  [0.00] BIOS-e820: [mem 0x-0x0009dfff] usable
  [0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved
  [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
  [0.00] BIOS-e820: [mem 0x0010-0xefff] usable
  [0.00] BIOS-e820: [mem 0xfc00-0x] reserved
  [0.00] BIOS-e820: [mem 0x0001-0x0001efff] usable
  [0.00] NX (Execute Disable) protection: active
  [0.00] SMBIOS 2.4 present.
  [0.00] Hypervisor detected: Xen
  [0.00] Xen version 4.2.
  [0.00] Netfront and the Xen platform PCI driver have been compiled 
for this kernel: unplug emulated NICs.
  [0.00] Blkfront and the Xen platform PCI driver have been compiled 
for this kernel: unplug emulated disks.
  [0.00] You might have to change the root device
  [0.00] from /dev/hd[a-d] to /dev/xvd[a-d]
  [0.00] in your root= kernel command line option
  [0.00] e820: last_pfn = 0x1f max_arch_pfn = 0x4
  [0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
  [0.00] e820: last_pfn = 0xf max_arch_pfn = 0x4
  [0.00] found SMP MP-table at [mem 0x000fbba0-0x000fbbaf] mapped at 
[880fbba0]
  [0.00] Scanning 1 areas for low memory corruption
  [0.00] RAMDISK: [mem 0x3407e000-0x36036fff]
  [0.00] ACPI: Early table checksum verification disabled
  [0.00] ACPI: RSDP 0x000EA020 24 (v02 Xen   )
  [0.00] ACPI: XSDT 0xFC00F5A0 54 (v01 XenHVM  
 HVML )
  [0.00] ACPI: FACP 0xFC00F260 F4 (v04 XenHVM  
 HVML )
  [0.00] ACPI: DSDT 0xFC0035E0 00BBF6 (v02 XenHVM  
 INTL 20090123)
  [0.00] ACPI: FACS 0xFC0035A0 40
  [0.00] ACPI: FACS 0xFC0035A0 40
  [0.00] ACPI: APIC 0xFC00F360 D8 (v02 XenHVM  
 HVML )
  [0.00] ACPI: HPET 0xFC00F4B0 38 (v01 XenHVM  
 HVML )
  [0.00] ACPI: WAET 0xFC00F4F0 28 (v01 XenHVM  
 HVML )
  [0.00] ACPI: SSDT 0xFC00F520 31 (v02 XenHVM  
 INTL 20090123)
  [0.00] ACPI: SSDT 0xFC00F560 31 (v02 XenHVM  
 INTL 20090123)
  [0.00] No NUMA configuration found
  [0.00] Faking a node at [mem 0x-0x0001efff]
  [0.00] NODE_DATA(0) allocated [mem 0x1efff7000-0x1efffbfff]
  [0.00] Zone ranges:
  [0.00]   DMA  [mem 0x1000-0x00ff]
  [0.00]   DMA32[mem 0x0100-0x]
  [0.00]   Normal   [mem 0x0001-0x0001efff]
  [0.00]   Device   empty
  [0.00] Movable zone start for each node
  [0.00] Early memory node ranges
  [0.00]   node   0:

[Kernel-packages] [Bug 1575467] Re: Ubuntu 16.04 consistently freezes up / hangs

Oh sorry I clicked some thing wrong... I never said a fix was released
lol... how can I remove that part?

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

Title:
  Ubuntu 16.04 consistently freezes up / hangs

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Not sure what package this is related to. I honestly have no idea.
  After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron
  laptop consistently freezes up and is unresponsive 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. So i wonder if this
  has something to do with my memory buffer or something. It seems to
  happen more often in Google Chrome than Firefox, but it happens with
  both. I know Google Chrome uses more memory though. And it has
  happened at least once with no videos loaded, so i doubt it's some
  sort of weird flash issue. 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.

  I will try to upload any log files that people think may be useful. I
  will see if i can do the recommended ssh monitoring method while
  trying to reproduce it to see if i can see an error that way.

  Not sure if this hardware info helps:
  lspci reports:
  00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
SoC Transaction Register (rev 0e)
  00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
  00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA 
AHCI Controller (rev 0e)
  00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, 
Celeron N2000 Series USB xHCI (rev 0e)
  00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx 
Series Trusted Execution Engine (rev 0e)
  00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
High Definition Audio Controller (rev 0e)
  00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 1 (rev 0e)
  00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 3 (rev 0e)
  00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
Power Control Unit (rev 0e)
  00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller 
(rev 0e)
  03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter (rev 01)

  andrew@andrew-Inspiron-3451:~$ sudo lshw
  andrew-inspiron-3451
  description: Computer
  width: 64 bits
  capabilities: smbios-2.8 vsyscall32
    *-core
     description: Motherboard
     physical id: 0
   *-memory
    description: System memory
    physical id: 0
    size: 3834MiB
   *-cpu
    product: Intel(R) Pentium(R) CPU  N3540  @ 2.16GHz
    vendor: Intel Corp.
    physical id: 1
    bus info: cpu@0
    size: 909MHz
    capacity: 2665MHz
    width: 64 bits
    capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good 
nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx 
est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer 
rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid 
tsc_adjust smep erms dtherm ida arat cpufreq
   *-pci
    description: Host bridge
    product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction 
Register
    vendor: Intel Corporation
    physical id: 100
    bus info: pci@:00:00.0
    version: 0e
    width: 32 bits
    clock: 33MHz
    configuration: driver=iosf_mbi_pci
    resources: irq:0
  *-display
   description: VGA compatible controller
   product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 0e
   width: 32 bits
   clock: 33MHz
   capabilities: pm msi vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:89 memory:d000-d03f 
memory:c000-cfff ioport:f080(size=8)
  *-storage
   description: SATA controller
   product: Atom Processor E3800 Series SATA AHCI Controller
   vendor: Intel Corporation
   physical id: 13
   bus info: pci@:00:13.0
   version: 0e

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

This change was made by a bot.

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

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

Title:
  BTRFS Page allocation failure with Bacula.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As soon as bacula starts running I see the below errors in the kernel
  log, and the server eventually hangs at some point. I'm backing up our
  servers to a local BTRFS volume on a local drive, nothing fancy and it
  used to work really well in Ubuntu 14.04.

  Apr 27 21:05:18 backup kernel: [343463.805173] kworker/u4:5: page allocation 
failure: order:0, mode:0x2204020
  Apr 27 21:05:18 backup kernel: [343463.805178] CPU: 1 PID: 19811 Comm: 
kworker/u4:5 Not tainted 4.4.0-21-generic #37-Ubuntu
  Apr 27 21:05:18 backup kernel: [343463.805179] Hardware name: Bochs Bochs, 
BIOS Bochs 01/01/2011
  Apr 27 21:05:18 backup kernel: [343463.805199] Workqueue: btrfs-submit 
btrfs_submit_helper [btrfs]
  Apr 27 21:05:18 backup kernel: [343463.805201]  0086 
5236f502 880019f2b548 813e93c3
  Apr 27 21:05:18 backup kernel: [343463.805203]  02204020 
 880019f2b5d8 81192fba
  Apr 27 21:05:18 backup kernel: [343463.805205]  88007fff9d40 
88007fffb6e0  0060
  Apr 27 21:05:18 backup kernel: [343463.805206] Call Trace:
  Apr 27 21:05:18 backup kernel: [343463.805211]  [] 
dump_stack+0x63/0x90
  Apr 27 21:05:18 backup kernel: [343463.805214]  [] 
warn_alloc_failed+0xfa/0x150
  Apr 27 21:05:18 backup kernel: [343463.805217]  [] 
__alloc_pages_nodemask+0x341/0xb60
  Apr 27 21:05:18 backup kernel: [343463.805220]  [] 
alloc_pages_current+0x8c/0x110
  Apr 27 21:05:18 backup kernel: [343463.805222]  [] 
new_slab+0x28f/0x490
  Apr 27 21:05:18 backup kernel: [343463.805224]  [] 
___slab_alloc+0x22b/0x460
  Apr 27 21:05:18 backup kernel: [343463.805227]  [] ? 
alloc_indirect.isra.4+0x1d/0x50
  Apr 27 21:05:18 backup kernel: [343463.805228]  [] ? 
alloc_indirect.isra.4+0x1d/0x50
  Apr 27 21:05:18 backup kernel: [343463.805230]  [] 
__slab_alloc+0x20/0x40
  Apr 27 21:05:18 backup kernel: [343463.805231]  [] 
__kmalloc+0x1d5/0x250
  Apr 27 21:05:18 backup kernel: [343463.805233]  [] 
alloc_indirect.isra.4+0x1d/0x50
  Apr 27 21:05:18 backup kernel: [343463.805234]  [] 
virtqueue_add_sgs+0x2ca/0x3a0
  Apr 27 21:05:18 backup kernel: [343463.805237]  [] 
__virtblk_add_req+0xbd/0x220
  Apr 27 21:05:18 backup kernel: [343463.805239]  [] ? 
mempool_alloc_slab+0x15/0x20
  Apr 27 21:05:18 backup kernel: [343463.805242]  [] ? 
blk_rq_map_sg+0x223/0x570
  Apr 27 21:05:18 backup kernel: [343463.805243]  [] 
virtio_queue_rq+0x112/0x280
  Apr 27 21:05:18 backup kernel: [343463.805245]  [] 
__blk_mq_run_hw_queue+0x1d6/0x380
  Apr 27 21:05:18 backup kernel: [343463.805247]  [] 
blk_mq_run_hw_queue+0x8e/0xb0
  Apr 27 21:05:18 backup kernel: [343463.805248]  [] 
blk_mq_insert_requests+0xf6/0x1c0
  Apr 27 21:05:18 backup kernel: [343463.805250]  [] 
blk_mq_flush_plug_list+0x128/0x150
  Apr 27 21:05:18 backup kernel: [343463.805251]  [] 
blk_flush_plug_list+0xd6/0x240
  Apr 27 21:05:18 backup kernel: [343463.805253]  [] 
blk_finish_plug+0x2c/0x40
  Apr 27 21:05:18 backup kernel: [343463.805264]  [] 
run_scheduled_bios+0x363/0x530 [btrfs]
  Apr 27 21:05:18 backup kernel: [343463.805275]  [] 
pending_bios_fn+0x15/0x20 [btrfs]
  Apr 27 21:05:18 backup kernel: [343463.805285]  [] 
btrfs_scrubparity_helper+0xca/0x2f0 [btrfs]
  Apr 27 21:05:18 backup kernel: [343463.805294]  [] 
btrfs_submit_helper+0xe/0x10 [btrfs]
  Apr 27 21:05:18 backup kernel: [343463.805297]  [] 
process_one_work+0x162/0x480
  Apr 27 21:05:18 backup kernel: [343463.805298]  [] 
worker_thread+0x4b/0x4c0
  Apr 27 21:05:18 backup kernel: [343463.805300]  [] ? 
process_one_work+0x480/0x480
  Apr 27 21:05:18 backup kernel: [343463.805301]  [] ? 
process_one_work+0x480/0x480
  Apr 27 21:05:18 backup kernel: [343463.805303]  [] 
kthread+0xd8/0xf0
  Apr 27 21:05:18 backup kernel: [343463.805305]  [] ? 
kthread_create_on_node+0x1e0/0x1e0
  Apr 27 21:05:18 backup kernel: [343463.805308]  [] 
ret_from_fork+0x3f/0x70
  Apr 27 21:05:18 backup kernel: [343463.805309]  [] ? 
kthread_create_on_node+0x1e0/0x1e0
  Apr 27 21:05:18 backup kernel: [343463.805310] Mem-Info:
  Apr 27 21:05:18 backup kernel: [343463.805313] active_anon:43184 
inactive_anon:51940 isolated_anon:0
  Apr 27 21:05:18 backup kernel: [343463.805313]  active_file:123451 
inactive_file:249283 isolated_file:0
  Apr 27 21:05:18 backup kernel: [343463.805313]  unevictable:1752 dirty:32219 
writeback:6149 unstable:0
  Apr 27 21:05:18 backup kernel: [343463.805313]  slab_reclaimable:18341 
slab_unreclaimable:4095
  Apr 27 21:05:18 backup kernel: [343463.805313]  mapped:58659 shmem:79658 
pagetables:1755 bounce:0
  Apr 27 21:05:18 backup kernel: [343463.805313]

[Kernel-packages] [Bug 1576297] [NEW] BTRFS Page allocation failure with Bacula.

2016-04-28 Thread MikeB

Public bug reported:

As soon as bacula starts running I see the below errors in the kernel
log, and the server eventually hangs at some point. I'm backing up our
servers to a local BTRFS volume on a local drive, nothing fancy and it
used to work really well in Ubuntu 14.04.

Apr 27 21:05:18 backup kernel: [343463.805173] kworker/u4:5: page allocation 
failure: order:0, mode:0x2204020
Apr 27 21:05:18 backup kernel: [343463.805178] CPU: 1 PID: 19811 Comm: 
kworker/u4:5 Not tainted 4.4.0-21-generic #37-Ubuntu
Apr 27 21:05:18 backup kernel: [343463.805179] Hardware name: Bochs Bochs, BIOS 
Bochs 01/01/2011
Apr 27 21:05:18 backup kernel: [343463.805199] Workqueue: btrfs-submit 
btrfs_submit_helper [btrfs]
Apr 27 21:05:18 backup kernel: [343463.805201]  0086 
5236f502 880019f2b548 813e93c3
Apr 27 21:05:18 backup kernel: [343463.805203]  02204020 
 880019f2b5d8 81192fba
Apr 27 21:05:18 backup kernel: [343463.805205]  88007fff9d40 
88007fffb6e0  0060
Apr 27 21:05:18 backup kernel: [343463.805206] Call Trace:
Apr 27 21:05:18 backup kernel: [343463.805211]  [] 
dump_stack+0x63/0x90
Apr 27 21:05:18 backup kernel: [343463.805214]  [] 
warn_alloc_failed+0xfa/0x150
Apr 27 21:05:18 backup kernel: [343463.805217]  [] 
__alloc_pages_nodemask+0x341/0xb60
Apr 27 21:05:18 backup kernel: [343463.805220]  [] 
alloc_pages_current+0x8c/0x110
Apr 27 21:05:18 backup kernel: [343463.805222]  [] 
new_slab+0x28f/0x490
Apr 27 21:05:18 backup kernel: [343463.805224]  [] 
___slab_alloc+0x22b/0x460
Apr 27 21:05:18 backup kernel: [343463.805227]  [] ? 
alloc_indirect.isra.4+0x1d/0x50
Apr 27 21:05:18 backup kernel: [343463.805228]  [] ? 
alloc_indirect.isra.4+0x1d/0x50
Apr 27 21:05:18 backup kernel: [343463.805230]  [] 
__slab_alloc+0x20/0x40
Apr 27 21:05:18 backup kernel: [343463.805231]  [] 
__kmalloc+0x1d5/0x250
Apr 27 21:05:18 backup kernel: [343463.805233]  [] 
alloc_indirect.isra.4+0x1d/0x50
Apr 27 21:05:18 backup kernel: [343463.805234]  [] 
virtqueue_add_sgs+0x2ca/0x3a0
Apr 27 21:05:18 backup kernel: [343463.805237]  [] 
__virtblk_add_req+0xbd/0x220
Apr 27 21:05:18 backup kernel: [343463.805239]  [] ? 
mempool_alloc_slab+0x15/0x20
Apr 27 21:05:18 backup kernel: [343463.805242]  [] ? 
blk_rq_map_sg+0x223/0x570
Apr 27 21:05:18 backup kernel: [343463.805243]  [] 
virtio_queue_rq+0x112/0x280
Apr 27 21:05:18 backup kernel: [343463.805245]  [] 
__blk_mq_run_hw_queue+0x1d6/0x380
Apr 27 21:05:18 backup kernel: [343463.805247]  [] 
blk_mq_run_hw_queue+0x8e/0xb0
Apr 27 21:05:18 backup kernel: [343463.805248]  [] 
blk_mq_insert_requests+0xf6/0x1c0
Apr 27 21:05:18 backup kernel: [343463.805250]  [] 
blk_mq_flush_plug_list+0x128/0x150
Apr 27 21:05:18 backup kernel: [343463.805251]  [] 
blk_flush_plug_list+0xd6/0x240
Apr 27 21:05:18 backup kernel: [343463.805253]  [] 
blk_finish_plug+0x2c/0x40
Apr 27 21:05:18 backup kernel: [343463.805264]  [] 
run_scheduled_bios+0x363/0x530 [btrfs]
Apr 27 21:05:18 backup kernel: [343463.805275]  [] 
pending_bios_fn+0x15/0x20 [btrfs]
Apr 27 21:05:18 backup kernel: [343463.805285]  [] 
btrfs_scrubparity_helper+0xca/0x2f0 [btrfs]
Apr 27 21:05:18 backup kernel: [343463.805294]  [] 
btrfs_submit_helper+0xe/0x10 [btrfs]
Apr 27 21:05:18 backup kernel: [343463.805297]  [] 
process_one_work+0x162/0x480
Apr 27 21:05:18 backup kernel: [343463.805298]  [] 
worker_thread+0x4b/0x4c0
Apr 27 21:05:18 backup kernel: [343463.805300]  [] ? 
process_one_work+0x480/0x480
Apr 27 21:05:18 backup kernel: [343463.805301]  [] ? 
process_one_work+0x480/0x480
Apr 27 21:05:18 backup kernel: [343463.805303]  [] 
kthread+0xd8/0xf0
Apr 27 21:05:18 backup kernel: [343463.805305]  [] ? 
kthread_create_on_node+0x1e0/0x1e0
Apr 27 21:05:18 backup kernel: [343463.805308]  [] 
ret_from_fork+0x3f/0x70
Apr 27 21:05:18 backup kernel: [343463.805309]  [] ? 
kthread_create_on_node+0x1e0/0x1e0
Apr 27 21:05:18 backup kernel: [343463.805310] Mem-Info:
Apr 27 21:05:18 backup kernel: [343463.805313] active_anon:43184 
inactive_anon:51940 isolated_anon:0
Apr 27 21:05:18 backup kernel: [343463.805313]  active_file:123451 
inactive_file:249283 isolated_file:0
Apr 27 21:05:18 backup kernel: [343463.805313]  unevictable:1752 dirty:32219 
writeback:6149 unstable:0
Apr 27 21:05:18 backup kernel: [343463.805313]  slab_reclaimable:18341 
slab_unreclaimable:4095
Apr 27 21:05:18 backup kernel: [343463.805313]  mapped:58659 shmem:79658 
pagetables:1755 bounce:0
Apr 27 21:05:18 backup kernel: [343463.805313]  free:12908 free_pcp:138 
free_cma:0
Apr 27 21:05:18 backup kernel: [343463.805315] Node 0 DMA free:9992kB min:40kB 
low:48kB high:60kB active_anon:28kB inactive_anon:396kB active_file:256kB 
inactive_file:884kB unevictable:92kB isolated(anon):0kB isolated(file):0kB 
present:15992kB managed:15908kB mlocked:92kB dirty:936kB writeback:0kB 
mapped:60kB shmem:316kB slab_reclaimable:3424kB slab_unreclaimable:308kB 
kernel_stack:192kB pagetables:60kB unstable:0kB

[Kernel-packages] [Bug 1576222] Re: Clock does not update TZ based on location

Removing linux as the suspect package

** Package changed: linux (Ubuntu) => 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/1576222

Title:
  Clock does not update TZ based on location

Status in Ubuntu:
  Confirmed

Bug description:
  See attached screenshot of the configs.  Despite the fact that it is
  configured to update the time based on location, this simply does not
  work.  I always have to manually re-configure the system time to the
  correct current timezone.

  This is rather annoying.  Even Google Calendar, running inside a
  browser, properly detects location and offers to change TZ to match.
  But Ubuntu simply does not.

  This has been a problem for quite some time, please fix it.

  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
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bladernr   1607 F pulseaudio
   /dev/snd/controlC1:  bladernr   1607 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Apr 28 09:21:48 2016
  HibernationDevice: RESUME=UUID=1ec334c0-b29f-454a-9668-0e6f5cc2d152
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0290 Apple, Inc. 
   Bus 001 Device 006: ID 05ac:828f Apple, Inc. 
   Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookAir6,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=3d44-163a-4386-9871-83e8515efd90 ro quiet splash 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: 09/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0099.B20.1509081314
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-35C1E88140C3E6CF
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-35C1E88140C3E6CF
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B20.1509081314:bd09/08/2015:svnAppleInc.:pnMacBookAir6,1:pvr1.0:rvnAppleInc.:rnMac-35C1E88140C3E6CF:rvrMacBookAir6,1:cvnAppleInc.:ct10:cvrMac-35C1E88140C3E6CF:
  dmi.product.name: MacBookAir6,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1576222] Re: Clock does not update TZ based on location

2016-04-28 Thread Jeff Lane

It's not really a kernel issue, it's an issue in whatever bits in
Unity?? that set the system/calendar time (e.g. the Date/Time settings).

I filed generically against Ubuntu because I coudn't find a name for the
appropriate piece of UserSpace that does this (I failed at name
searching).

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

Title:
  Clock does not update TZ based on location

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  See attached screenshot of the configs.  Despite the fact that it is
  configured to update the time based on location, this simply does not
  work.  I always have to manually re-configure the system time to the
  correct current timezone.

  This is rather annoying.  Even Google Calendar, running inside a
  browser, properly detects location and offers to change TZ to match.
  But Ubuntu simply does not.

  This has been a problem for quite some time, please fix it.

  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
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bladernr   1607 F pulseaudio
   /dev/snd/controlC1:  bladernr   1607 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Apr 28 09:21:48 2016
  HibernationDevice: RESUME=UUID=1ec334c0-b29f-454a-9668-0e6f5cc2d152
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0290 Apple, Inc. 
   Bus 001 Device 006: ID 05ac:828f Apple, Inc. 
   Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookAir6,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=3d44-163a-4386-9871-83e8515efd90 ro quiet splash 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: 09/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0099.B20.1509081314
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-35C1E88140C3E6CF
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-35C1E88140C3E6CF
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B20.1509081314:bd09/08/2015:svnAppleInc.:pnMacBookAir6,1:pvr1.0:rvnAppleInc.:rnMac-35C1E88140C3E6CF:rvrMacBookAir6,1:cvnAppleInc.:ct10:cvrMac-35C1E88140C3E6CF:
  dmi.product.name: MacBookAir6,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1531768] Re: [arm64] locks up some time after booting

2016-04-28 Thread Colin Ian King

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

Title:
  [arm64] locks up some time after booting

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I
  want to use for armhf autopkgtesting in LXD). I started with wily as
  that has lxd available (it's not yet available in trusty nor the PPA
  for arm64).

  However, pretty much any LXD task that I do (I haven't tried much
  else) on this machine takes unbearably long. A simple "lxc profile set
  default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes.

  I see tons of

  [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0
  [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds.

  in dmesg (the attached apport info has the complete dmesg).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic 4.2.0-22.27
  ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  7 09:18 seq
   crw-rw 1 root audio 116, 33 Jan  7 09:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Thu Jan  7 09:24:01 2016
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.

   lxcbr0no wireless extensions.
  Lspci:
   00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008]
    Subsystem: Red Hat, Inc Device [1af4:1100]
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=LABEL=cloudimg-rootfs earlyprintk
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   linux-backports-modules-4.2.0-22-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1556264] Re: [Hyper-V] vmbus: Fix a bug in hv_need_to_signal_on_read()

** Changed in: linux-lts-vivid (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  [Hyper-V] vmbus: Fix a bug in hv_need_to_signal_on_read()

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Released

Bug description:
  The following patch has been submitted upstream in response to
  investigation of customer issues with network connections hanging
  under high load.

  On the consumer side, we have interrupt driven flow management of the
  producer. It is sufficient to base the signalling decision on the
  amount of space that is available to write after the read is complete.
  The current code samples the previous available space and uses this in
  making the signalling decision. This state can be stale and is
  unnecessary. Since the state can be stale, we end up not signalling
  the host (when we should) and this can result in a hang. Fix this
  problem by removing the unnecessary check.

  I would like to thank Arseney Romanenko 
  for pointing out this bug.

  Signed-off-by: K. Y. Srinivasan 
  Tested-by: Dexuan Cui 
  Cc: 
  ---
   drivers/hv/ring_buffer.c |7 +++
   1 files changed, 3 insertions(+), 4 deletions(-)

  diff --git a/drivers/hv/ring_buffer.c b/drivers/hv/ring_buffer.c
  index 5613e2b..085003a 100644
  --- a/drivers/hv/ring_buffer.c
  +++ b/drivers/hv/ring_buffer.c
  @@ -103,8 +103,7 @@ static bool hv_need_to_signal(u32 old_write, struct 
hv_ring_buffer_info *rbi)
*there is room for the producer to send the pending packet.
*/

  -static bool hv_need_to_signal_on_read(u32 prev_write_sz,
  - struct hv_ring_buffer_info *rbi)
  +static bool hv_need_to_signal_on_read(struct hv_ring_buffer_info *rbi)
   {
  u32 cur_write_sz;
  u32 r_size;
  @@ -120,7 +119,7 @@ static bool hv_need_to_signal_on_read(u32 prev_write_sz,
  cur_write_sz = write_loc >= read_loc ? r_size - (write_loc - 
read_loc) :
  read_loc - write_loc;

  -   if ((prev_write_sz < pending_sz) && (cur_write_sz >= pending_sz))
  +   if (cur_write_sz >= pending_sz)
  return true;

  return false;
  @@ -455,7 +454,7 @@ int hv_ringbuffer_read(struct hv_ring_buffer_info 
*inring_info,
  /* Update the read index */
  hv_set_next_read_location(inring_info, next_read_location);

  -   *signal = hv_need_to_signal_on_read(bytes_avail_towrite, inring_info);
  +   *signal = hv_need_to_signal_on_read(inring_info);

  return ret;
   }

  We have customers who are encountering this issue. Although this patch
  is not yet accepted upstream, we would like to get them a test kernel
  as soon as we can.

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

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

[Kernel-packages] [Bug 1518457] Re: kswapd0 100% CPU usage

2016-04-28 Thread erik

I can see this bug on a system recently upgraded from Ubuntu 15.04 to 16.04.
I did not see this behaviour before upgrading.
The system is an Intel NUC Desktop with 8 GB RAM and kswapd0 completely locks 
up the system after a while.

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

Title:
  kswapd0 100% CPU usage

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  As per bug 721896 and various others:

  I'm on an AWS t2.micro instance (Xeon E5-2670, 991MiB of memory).
  Occasionally (about once a day), kswapd0 falls into a busy loop and
  spins on 100% CPU usage indefinitely. This can be provoked by
  copying/writing large files (e.g. dding a 256MB file), but it happens
  occasionally otherwise. System memory usage (not including
  buffers/caches) currently sits at 36%, which is typical[1]. Initially
  I had no swap space configured; I've since tried enabling a 256MB swap
  file, but the problem continues to occur and no swap space is used.
  The system can be recovered with `echo 1 > /proc/sys/vm/drop_caches`.

  Happy to provide further information/take further debugging actions.

  
  [1] Full output from `free`:
   total   used   free sharedbuffers cached
  Mem:   1014936 483448 531488  28556   9756 112700
  -/+ buffers/cache: 360992 653944
  Swap:   262140  0 262140

  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
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 19 19:40 seq
   crw-rw 1 root audio 116, 33 Nov 19 19:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Fri Nov 20 20:44:30 2015
  Ec2AMI: ami-1c552a76
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-east-1d
  Ec2InstanceType: t2.micro
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  MachineType: Xen HVM domU
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 xen
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-18-generic 
root=UUID=35bc01f4-4602-4823-976e-508edef899df ro console=tty1 console=ttyS0 
net.ifnames=0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-18-generic N/A
   linux-backports-modules-4.2.0-18-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  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: 05/06/2015
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd05/06/2015:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

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-rc5-wily/

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

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

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

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

** Tags added: kernel-key

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

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

Bug description:
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 4.4.0-21-generic (buildd@lgw01-21) (gcc version 
5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:33:37 
UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=8ea401db-b84b-4cd6-a628-d72f30bbf1e5 ro console=tty1 console=ttyS0
  [0.00] KERNEL supported cpus:
  [0.00]   Intel GenuineIntel
  [0.00]   AMD AuthenticAMD
  [0.00]   Centaur CentaurHauls
  [0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
  [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point 
registers'
  [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
  [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
  [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 
bytes, using 'standard' format.
  [0.00] x86/fpu: Using 'eager' FPU context switches.
  [0.00] e820: BIOS-provided physical RAM map:
  [0.00] BIOS-e820: [mem 0x-0x0009dfff] usable
  [0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved
  [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
  [0.00] BIOS-e820: [mem 0x0010-0xefff] usable
  [0.00] BIOS-e820: [mem 0xfc00-0x] reserved
  [0.00] BIOS-e820: [mem 0x0001-0x0001efff] usable
  [0.00] NX (Execute Disable) protection: active
  [0.00] SMBIOS 2.4 present.
  [0.00] Hypervisor detected: Xen
  [0.00] Xen version 4.2.
  [0.00] Netfront and the Xen platform PCI driver have been compiled 
for this kernel: unplug emulated NICs.
  [0.00] Blkfront and the Xen platform PCI driver have been compiled 
for this kernel: unplug emulated disks.
  [0.00] You might have to change the root device
  [0.00] from /dev/hd[a-d] to /dev/xvd[a-d]
  [0.00] in your root= kernel command line option
  [0.00] e820: last_pfn = 0x1f max_arch_pfn = 0x4
  [0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
  [0.00] e820: last_pfn = 0xf max_arch_pfn = 0x4
  [0.00] found SMP MP-table at [mem 0x000fbba0-0x000fbbaf] mapped at 
[880fbba0]
  [0.00] Scanning 1 areas for low memory corruption
  [0.00] RAMDISK: [mem 0x3407e000-0x36036fff]
  [0.00] ACPI: Early table checksum verification disabled
  [0.00] ACPI: RSDP 0x000EA020 24 (v02 Xen   )
  [0.00] ACPI: XSDT 0xFC00F5A0 54 (v01 XenHVM  
 HVML )
  [0.00] ACPI: FACP 0xFC00F260 F4 (v04 XenHVM  
 HVML )
  [0.00] ACPI: DSDT 0xFC0035E0 00BBF6 (v02 XenHVM  
 INTL 20090123)
  [0.00] ACPI: FACS 0xFC0035A0 40
  [0.00] ACPI: FACS 0xFC0035A0 40
  [0.00] ACPI: APIC 0xFC00F360 D8 (v02 XenHVM  
 HVML )
  [0.00] ACPI: HPET 0xFC00F4B0 38 (v01 XenHVM  
 HVML )
  [0.00] ACPI: WAET 0xFC00F4F0 28 (v01 XenHVM  
 HVML )
  [0.00] ACPI: SSDT 0xFC00F520 31 (v02 XenHVM  
 INTL 20090123)
  [0.00] ACPI: SSDT 0xFC00F560 31 (v02 XenHVM  
 INTL 20090123)
  [0.00] No NUMA configuration found
  [

[Kernel-packages] [Bug 1575506] Re: Xenial: ARM64: Unable to handle kernel NULL pointer dereference at virtual address 00000038

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

** Tags added: kernel-da-key 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/1575506

Title:
  Xenial: ARM64: Unable to handle kernel NULL pointer dereference at
  virtual address 0038

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  When running 'stress-ng --all 64 -t 800 -v' on Xenial/ARM64, the following 
kernel oops is triggered.

  
  [   93.309158] Unable to handle kernel NULL pointer dereference at virtual 
address 0038
  [   93.309160] pgd = 8007a5914000
  [   93.309163] [0038] *pgd=0047a5b15003, *pud=0047a5b16003, 
*pmd=
  [   93.309167] Internal error: Oops: 9606 [#1] SMP
  [   93.309202] Modules linked in: wp512 rmd320 rmd256 rmd160 rmd128 md4 
algif_hash af_alg xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables nls_iso8859_1 shpchp ghash_ce sha2_ce sha1_ce 
xgene_rng i2c_xgene_slimpro xgene_edac dwc3 edac_core udc_core 
i2c_designware_platform ulpi i2c_designware_core uio_pdrv_genirq uio gpio_keys 
rtc_efi autofs4 tg3 ptp pps_core sdhci_of_arasan ahci_xgene gpio_dwapb 
sdhci_pltfm xgene_enet libahci_platform sdhci libahci gpio_xgene_sb
  [   93.309208] CPU: 5 PID: 2062 Comm: stress-ng-remap Not tainted 
4.4.0-15.31-generic #31+clk.1
  [   93.309209] Hardware name: AppliedMicro Mustang/Mustang, BIOS 2.04.08-beta 
Feb  2 2016
  [   93.309211] task: 8007a58c5b00 ti: 8007a7a3 task.ti: 
8007a7a3
  [   93.309217] PC is at fput+0x20/0xd0
  [   93.309222] LR is at vma_do_fput+0x24/0x48
  [   93.309223] pc : [] lr : [] pstate: 
6145
  [   93.309224] sp : 8007a7a33e20
  [   93.309226] x29: 8007a7a33e20 x28: 8007a7a3 
  [   93.309228] x27: 0003 x26: 8007a59886e8 
  [   93.309229] x25: 800746248ed8 x24: 8011 
  [   93.309231] x23:  x22: 8091b780 
  [   93.309232] x21: 1000 x20:  
  [   93.309233] x19:  x18: 1140 
  [   93.309235] x17: 8915f2c0 x16: 80133de0 
  [   93.309236] x15: 893c2000 x14:  
  [   93.309237] x13: 0003e800 x12: 734b0200 
  [   93.309239] x11: 003d0f00 x10: 0930 
  [   93.309240] x9 :  x8 :  
  [   93.309242] x7 : 80074645ac10 x6 : 00680f43 
  [   93.309243] x5 : 00680f4f x4 : 0064 
  [   93.309245] x3 : 00680f53 x2 : 0038 
  [   93.309246] x1 : 8091b780 x0 : 801fe1f4 

  [   93.309248] Process stress-ng-remap (pid: 2062, stack limit = 
0x8007a7a30020)
  [   93.309250] Stack: (0x8007a7a33e20 to 0x8007a7a34000)
  [   93.309252] 3e20: 8007a7a33e40 801fe1f4  
8007a59886e8
  [   93.309253] 3e40: 8007a7a33e60 8020c1c0 8830 
80d8e000
  [   93.309255] 3e60: c85b2280 80085c70  
88301000
  [   93.309257] 3e80:  89161ea8 8000 
0015
  [   93.309258] 3ea0: 011d 00ea 80901000 
8007a7a3
  [   93.309260] 3ec0: 1000 cb88537fdc8ba606 8830 
1000
  [   93.309261] 3ee0:    
0200
  [   93.309262] 3f00: 00d1 00d1 00ea 
2626
  [   93.309264] 3f20: 0101010101010101 001e 0018 
0003e800
  [   93.309266] 3f40:  893c2cc0 004828c0 
89161ea0
  [   93.309267] 3f60: 1140 0050 88301000 
1000
  [   93.309269] 3f80: 1000 c85b2368 88d96fd0 
4650
  [   93.309270] 3fa0: 004558f0 c85b34b8 0048f000 
c85b2280
  [   93.309271] 3fc0: 0042ec60 c85b2280 89161ea8 
8000
  [   93.309273] 3fe0: 8830 00ea 8007a7a33fe8 

  [   93.309274] Call trace:
  [   93.309277] [] fput+0x20/0xd0
  [   93.309280] [] vma_do_fput+0x24/0x48
  [   93.309283] [] SyS_remap_file_pages+0x258/0x2a0
  [   93.309287] [] el0_svc_naked+0x24/0x28
  [   93.309289] Code: aa1e03e0 d503201f 9100e262 f9800051 (c85f7c40) 
  [   93.309308] ---[ end trace e42a31bddbea7038 ]---
  [   93.672808] Unable to handle kernel NULL pointer dereference at virtual 
address 0038
  [   93.672809] pgd = 8007d8f22000
  [   93.672813] [0038] *pgd=0047d9123003,

[Kernel-packages] [Bug 1576222] Re: Clock does not update TZ based on location

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-rc5-wily/

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

** Tags added: kernel-da-key

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

Title:
  Clock does not update TZ based on location

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  See attached screenshot of the configs.  Despite the fact that it is
  configured to update the time based on location, this simply does not
  work.  I always have to manually re-configure the system time to the
  correct current timezone.

  This is rather annoying.  Even Google Calendar, running inside a
  browser, properly detects location and offers to change TZ to match.
  But Ubuntu simply does not.

  This has been a problem for quite some time, please fix it.

  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
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bladernr   1607 F pulseaudio
   /dev/snd/controlC1:  bladernr   1607 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Apr 28 09:21:48 2016
  HibernationDevice: RESUME=UUID=1ec334c0-b29f-454a-9668-0e6f5cc2d152
  InstallationDate: Installed on 2015-10-21 (189 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0290 Apple, Inc. 
   Bus 001 Device 006: ID 05ac:828f Apple, Inc. 
   Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part 
of BCM2046 Bluetooth)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookAir6,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=3d44-163a-4386-9871-83e8515efd90 ro quiet splash 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: 09/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA61.88Z.0099.B20.1509081314
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-35C1E88140C3E6CF
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir6,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-35C1E88140C3E6CF
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B20.1509081314:bd09/08/2015:svnAppleInc.:pnMacBookAir6,1:pvr1.0:rvnAppleInc.:rnMac-35C1E88140C3E6CF:rvrMacBookAir6,1:cvnAppleInc.:ct10:cvrMac-35C1E88140C3E6CF:
  dmi.product.name: MacBookAir6,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1575148] Re: Ubuntu 16.04 with kernel 4.4.0.21 does not recognize at all the nvidia card of a macbook pro 11, 1

2016-04-28 Thread Albert

More issues related to this:

1. Once every few minutes the screen flickers.

2. Upon resume from sleep, more often than not the laptop screen is
black: not working. Switching to a tty and back to control+alt+F7
sometimes makes the screen work again. What works always, though, is to
plug in an external monitor which shows the desktop background overlaid
with a grid of dots indicative of the password screen, type in the
password blindly (fortunately the focus is by default on the password
input field, which is in the blackened laptop screen), and then move the
mouse into the other display, go to top-right and push the system menu
icon to then select the System Settings, go to Display, choose "Mirror",
and then the laptop screen works again. Of course, this workaround is
not always feasible, given that one does not carries a second monitor
around.

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

Title:
  Ubuntu 16.04 with kernel 4.4.0.21 does not recognize at all the nvidia
  card of a macbook pro 11,1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This macbook pro 11,1 has two cards:

  1. An nvidia card, which was both recognized in Ubuntu 14.04 with
  kernels 3.13.*, and worked well using the provided drivers under
  "Additional drivers".

  2. An intel integrated card, which was not in use under Ubuntu 14.04, but 
which now, under ubuntu 16.04, is the only card in use. The 'lspci' command 
states:
  00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT 
Integrated Graphics Controller [8086:0a2e] (rev 09)

  ... and there is no trace at all of the nvidia card under lspci.

  dmesg shows one crytic message, perhaps indicating that the nvidia
  card could not be recognized:

  [0.190838] pci :00:02.0: Video device with shadowed ROM

  dmesg lists a number of "failed" entries, such as:

  [   11.791463] usb 1-3: hub failed to enable device, error -62

  [   24.891009] wl: module verification failed: signature and/or
  required key missing - tainting kernel

  ... and also:

  [0.190096] pci :06:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [0.190098] pci :06:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [0.190099] pci :06:04.0: BAR 14: no space for [mem size 0x0020]
  [0.190100] pci :06:04.0: BAR 14: failed to assign [mem size 
0x0020]
  [0.190102] pci :06:04.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [0.190103] pci :06:04.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [0.190104] pci :06:06.0: BAR 14: no space for [mem size 0x0020]
  [0.190105] pci :06:06.0: BAR 14: failed to assign [mem size 
0x0020]
  [0.190107] pci :06:06.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [0.190108] pci :06:06.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [0.190109] pci :06:00.0: BAR 13: no space for [io  size 0x1000]
  [0.190110] pci :06:00.0: BAR 13: failed to assign [io  size 0x1000]
  [0.190111] pci :06:04.0: BAR 13: no space for [io  size 0x1000]
  [0.190112] pci :06:04.0: BAR 13: failed to assign [io  size 0x1000]
  [0.190113] pci :06:06.0: BAR 13: no space for [io  size 0x1000]
  [0.190114] pci :06:06.0: BAR 13: failed to assign [io  size 0x1000]
  [0.190116] pci :06:06.0: BAR 14: no space for [mem size 0x0020]
  [0.190117] pci :06:06.0: BAR 14: failed to assign [mem size 
0x0020]
  [0.190119] pci :06:06.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [0.190120] pci :06:06.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [0.190121] pci :06:06.0: BAR 13: no space for [io  size 0x1000]
  [0.190122] pci :06:06.0: BAR 13: failed to assign [io  size 0x1000]
  [0.190124] pci :06:04.0: BAR 14: no space for [mem size 0x0020]
  [0.190125] pci :06:04.0: BAR 14: failed to assign [mem size 
0x0020]
  [0.190126] pci :06:04.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [0.190127] pci :06:04.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [0.190129] pci :06:04.0: BAR 13: no space for [io  size 0x1000]
  [0.190130] pci :06:04.0: BAR 13: failed to assign [io  size 0x1000]
  [0.190131] pci :06:00.0: BAR 15: no space for [mem size 0x0020 
64bit pref]
  [0.190132] pci :06:00.0: BAR 15: failed to assign [mem size 
0x0020 64bit pref]
  [0.190133] pci :06:00.0: BAR 13: no space for [io  size 0x1000]
  [0.190134] pci :06:00.0: BAR 13: failed to assign [io  size 0x1000]

  
  Please let me know what further information I could provide to facilitate 
addressing these issues.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu

[Kernel-packages] [Bug 1574982] Re: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler

2016-04-28 Thread LocutusOfBorg

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

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

Title:
  Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong
  not supported by compiler

Status in dkms package in Ubuntu:
  Confirmed
Status in gcc-defaults package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Installing the latest 4.4.0-22 kernel ends with that error logged into 
dkmsbuildlog
  (only affect yakkety kernel; 4.4.0-22 kernel installation on xenial is fine)

  https://launchpadlibrarian.net/256055415/DKMSBuildLog.txt

  make "CC=cc"  KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build 
M=/var/lib/dkms/nvidia-361/361.42/build ARCH=x86_64 
NV_KERNEL_SOURCES=/lib/modules/4.4.0-22-generic/build 
NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia 
nvidia-uvm nvidia-modeset" INSTALL_MOD_DIR=kernel/drivers/video modules
  make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic'
  arch/x86/Makefile:133: stack-protector enabled but compiler support broken
  Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: 
-fstack-protector-strong not supported by compiler

  the latest error logged is:

  /var/lib/dkms/nvidia-361/361.42/build/nvidia/nv-frontend.c:1:0: error:
  code model kernel does not support PIC mode

  Looks like it is related to the latest changes updates: gcc-6/gcc-5 
5.3.1-16ubuntu2 (some packages built with gcc-6; gcc-5 disabled for the 
packages built with gcc-6)
  Maybe some alternatives has not been updated to take care of these changes, 
as asked some time ago:
  http://askubuntu.com/questions/26498/choose-gcc-and-g-version

  This has been firstly reported against a nvidia crash:
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1574838

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gcc 4:5.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr 26 08:41:32 2016
  SourcePackage: gcc-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem2014 F pulseaudio
   /dev/snd/pcmC0D0p:   oem2014 F...m pulseaudio
   /dev/snd/controlC0:  oem2014 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth0  no wireless extensions.

   eth1  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: ubuntu
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  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:  yakkety
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

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

-- 
Mailing list: https://launchpad.net/~kernel-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: Ubuntu 16.04 consistently freezes up / hangs

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

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

Title:
  Ubuntu 16.04 consistently freezes up / hangs

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Not sure what package this is related to. I honestly have no idea.
  After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron
  laptop consistently freezes up and is unresponsive 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. So i wonder if this
  has something to do with my memory buffer or something. It seems to
  happen more often in Google Chrome than Firefox, but it happens with
  both. I know Google Chrome uses more memory though. And it has
  happened at least once with no videos loaded, so i doubt it's some
  sort of weird flash issue. 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.

  I will try to upload any log files that people think may be useful. I
  will see if i can do the recommended ssh monitoring method while
  trying to reproduce it to see if i can see an error that way.

  Not sure if this hardware info helps:
  lspci reports:
  00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
SoC Transaction Register (rev 0e)
  00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
  00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA 
AHCI Controller (rev 0e)
  00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, 
Celeron N2000 Series USB xHCI (rev 0e)
  00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx 
Series Trusted Execution Engine (rev 0e)
  00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
High Definition Audio Controller (rev 0e)
  00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 1 (rev 0e)
  00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 3 (rev 0e)
  00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
Power Control Unit (rev 0e)
  00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller 
(rev 0e)
  03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter (rev 01)

  andrew@andrew-Inspiron-3451:~$ sudo lshw
  andrew-inspiron-3451
  description: Computer
  width: 64 bits
  capabilities: smbios-2.8 vsyscall32
    *-core
     description: Motherboard
     physical id: 0
   *-memory
    description: System memory
    physical id: 0
    size: 3834MiB
   *-cpu
    product: Intel(R) Pentium(R) CPU  N3540  @ 2.16GHz
    vendor: Intel Corp.
    physical id: 1
    bus info: cpu@0
    size: 909MHz
    capacity: 2665MHz
    width: 64 bits
    capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good 
nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx 
est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer 
rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid 
tsc_adjust smep erms dtherm ida arat cpufreq
   *-pci
    description: Host bridge
    product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction 
Register
    vendor: Intel Corporation
    physical id: 100
    bus info: pci@:00:00.0
    version: 0e
    width: 32 bits
    clock: 33MHz
    configuration: driver=iosf_mbi_pci
    resources: irq:0
  *-display
   description: VGA compatible controller
   product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 0e
   width: 32 bits
   clock: 33MHz
   capabilities: pm msi vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:89 memory:d000-d03f 
memory:c000-cfff ioport:f080(size=8)
  *-storage
   description: SATA controller
   product: Atom Processor E3800 Series SATA AHCI Controller
   vendor: Intel Corporation
   physical id: 13
   bus info: pci@:00:13.0
   version: 0e
   width: 32 bits

[Kernel-packages] [Bug 1576025] Re: Different kernel image seen hiding

That just means you have a 32 bit installation. i686 is the minimum
supported CPU instruction set for the i386 32 bit series of processors.

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

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

Title:
  Different kernel image seen hiding

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I got i686 when I used the following command

  madhu@madhu-desktop:~$ uname -mrsn
  Linux madhu-desktop 4.4.0-21-generic i686

  madhu@madhu-desktop:~$ dpkg --list | grep linux-image
  ii  linux-image-4.4.0-21-generic 4.4.0-21.37  
   i386 Linux kernel image for version 4.4.0 on 32 
bit x86 SMP
  ii  linux-image-extra-4.4.0-21-generic   4.4.0-21.37  
   i386 Linux kernel extra modules for version 
4.4.0 on 32 bit x86 SMP
  ii  linux-image-generic  4.4.0.21.22  
   i386 Generic Linux kernel image
  madhu@madhu-desktop:~$
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  madhu  1519 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e7fdca52-e71c-49c7-8f88-05c9b52cb128
  InstallationDate: Installed on 2016-04-23 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=a7e88f7c-3feb-4944-8547-2c8bb94f5255 ro quiet splash vt.handoff=7
  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 i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/10/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PE94510M.86A.0050.2007.0710.1559
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: D945GCPE
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD97209-201
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPE94510M.86A.0050.2007.0710.1559:bd07/10/2007:svn:pn:pvr:rvnIntelCorporation:rnD945GCPE:rvrAAD97209-201:cvn:ct3:cvr:

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

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

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

2016-04-28 Thread mookey41

Same here, 4.4. kernel on Ubutnu 16.04 LTS and Lenovo z51-70 80K, i5.

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

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

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

[Kernel-packages] [Bug 1568573] Re: i915 Skylake - Ultra Dock external displays not detected after suspend/resume cycle

2016-04-28 Thread Adam Chasen

I am seeing similar behavior with other versions of linux as well
(fedora 23 4.4.7-300.fc23.x86_64). I also have upgraded the DisplayPort
Hub firmware in the ultra dock per
http://www.thinkwiki.org/wiki/ThinkPad_Ultra_Dock

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

Title:
  i915 Skylake - Ultra Dock external displays not detected after
  suspend/resume cycle

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  System is Thinkpad T460, Skylake graphics, Thinkpad Ultra dock. DVI and HDMI 
displays connected via dock. 4.4.0-18.

  After a suspend-resume cycle, when the laptop is docked the dock
  connected external displays are not initialized/connected. If I
  disconnect the displays from the dock and connect them directly to the
  laptop, they are initialized successfully and can be configured via
  xrandr etc.

  If the laptop is power cycled, the displays can be used normally until
  the next suspend-resume cycle.

  Example from relevant dmesg:
  [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many 
voltage retries, give up
  [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many 
voltage retries, give up
  [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many 
voltage retries, give up
  [drm:intel_dp_start_link_train [i915_bpo]] *ERROR* failed to train DP, 
aborting
  [drm:intel_dp_set_idle_link_train [i915_bpo]] *ERROR* Timed out waiting for 
DP idle patterns
  [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many 
voltage retries, give up
  [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many 
voltage retries, give up
  [drm:intel_dp_link_training_clock_recovery [i915_bpo]] *ERROR* too many 
voltage retries, give up

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-18-generic 4.4.0-18.34
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ryan   1838 F pulseaudio
  Date: Sun Apr 10 09:39:32 2016
  HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d
  InstallationDate: Installed on 2015-09-21 (201 days ago)
  InstallationMedia: It
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FNCTO1WW
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-18-generic 
root=/dev/mapper/it--vg-root ro quiet
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-18-generic N/A
   linux-backports-modules-4.4.0-18-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-02-24 (45 days ago)
  dmi.bios.date: 03/09/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R06ET35W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FNCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FNCTO1WW
  dmi.product.version: ThinkPad T460
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-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: Ubuntu 16.04 consistently freezes up / hangs

I have the same issue. The work around with
"GRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_idle.max_cstate=1" seems
to have solved the issue for now on my Acer E511 with Intel Pentium
N3540 CHIP.  And the temp has not increased very much after recent hard
use.

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

Title:
  Ubuntu 16.04 consistently freezes up / hangs

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Not sure what package this is related to. I honestly have no idea.
  After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron
  laptop consistently freezes up and is unresponsive 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. So i wonder if this
  has something to do with my memory buffer or something. It seems to
  happen more often in Google Chrome than Firefox, but it happens with
  both. I know Google Chrome uses more memory though. And it has
  happened at least once with no videos loaded, so i doubt it's some
  sort of weird flash issue. 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.

  I will try to upload any log files that people think may be useful. I
  will see if i can do the recommended ssh monitoring method while
  trying to reproduce it to see if i can see an error that way.

  Not sure if this hardware info helps:
  lspci reports:
  00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
SoC Transaction Register (rev 0e)
  00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
  00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA 
AHCI Controller (rev 0e)
  00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, 
Celeron N2000 Series USB xHCI (rev 0e)
  00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx 
Series Trusted Execution Engine (rev 0e)
  00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
High Definition Audio Controller (rev 0e)
  00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 1 (rev 0e)
  00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 3 (rev 0e)
  00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
Power Control Unit (rev 0e)
  00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller 
(rev 0e)
  03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter (rev 01)

  andrew@andrew-Inspiron-3451:~$ sudo lshw
  andrew-inspiron-3451
  description: Computer
  width: 64 bits
  capabilities: smbios-2.8 vsyscall32
    *-core
     description: Motherboard
     physical id: 0
   *-memory
    description: System memory
    physical id: 0
    size: 3834MiB
   *-cpu
    product: Intel(R) Pentium(R) CPU  N3540  @ 2.16GHz
    vendor: Intel Corp.
    physical id: 1
    bus info: cpu@0
    size: 909MHz
    capacity: 2665MHz
    width: 64 bits
    capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good 
nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx 
est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer 
rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid 
tsc_adjust smep erms dtherm ida arat cpufreq
   *-pci
    description: Host bridge
    product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction 
Register
    vendor: Intel Corporation
    physical id: 100
    bus info: pci@:00:00.0
    version: 0e
    width: 32 bits
    clock: 33MHz
    configuration: driver=iosf_mbi_pci
    resources: irq:0
  *-display
   description: VGA compatible controller
   product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 0e
   width: 32 bits
   clock: 33MHz
   capabilities: pm msi vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:89 memory:d000-d03f 
memory:c000-cfff ioport:f080(size=8)
  *-storage
   description: SATA controller
   product: Atom Processor E3800 Series SATA

[Kernel-packages] [Bug 1575467] Re: Ubuntu 16.04 consistently freezes up / hangs

Oh sorry forgot to mention I am using Ubuntu 16.04. 64 bit.

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

Title:
  Ubuntu 16.04 consistently freezes up / hangs

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Not sure what package this is related to. I honestly have no idea.
  After upgrading from stock Ubuntu 14.04 to 16.04 on my Dell Inspiron
  laptop consistently freezes up and is unresponsive 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. So i wonder if this
  has something to do with my memory buffer or something. It seems to
  happen more often in Google Chrome than Firefox, but it happens with
  both. I know Google Chrome uses more memory though. And it has
  happened at least once with no videos loaded, so i doubt it's some
  sort of weird flash issue. 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.

  I will try to upload any log files that people think may be useful. I
  will see if i can do the recommended ssh monitoring method while
  trying to reproduce it to see if i can see an error that way.

  Not sure if this hardware info helps:
  lspci reports:
  00:00.0 Host bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
SoC Transaction Register (rev 0e)
  00:02.0 VGA compatible controller: Intel Corporation Atom Processor 
Z36xxx/Z37xxx Series Graphics & Display (rev 0e)
  00:13.0 SATA controller: Intel Corporation Atom Processor E3800 Series SATA 
AHCI Controller (rev 0e)
  00:14.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx, 
Celeron N2000 Series USB xHCI (rev 0e)
  00:1a.0 Encryption controller: Intel Corporation Atom Processor Z36xxx/Z37xxx 
Series Trusted Execution Engine (rev 0e)
  00:1b.0 Audio device: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
High Definition Audio Controller (rev 0e)
  00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 1 (rev 0e)
  00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express 
Root Port 3 (rev 0e)
  00:1f.0 ISA bridge: Intel Corporation Atom Processor Z36xxx/Z37xxx Series 
Power Control Unit (rev 0e)
  00:1f.3 SMBus: Intel Corporation Atom Processor E3800 Series SMBus Controller 
(rev 0e)
  03:00.0 Network controller: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter (rev 01)

  andrew@andrew-Inspiron-3451:~$ sudo lshw
  andrew-inspiron-3451
  description: Computer
  width: 64 bits
  capabilities: smbios-2.8 vsyscall32
    *-core
     description: Motherboard
     physical id: 0
   *-memory
    description: System memory
    physical id: 0
    size: 3834MiB
   *-cpu
    product: Intel(R) Pentium(R) CPU  N3540  @ 2.16GHz
    vendor: Intel Corp.
    physical id: 1
    bus info: cpu@0
    size: 909MHz
    capacity: 2665MHz
    width: 64 bits
    capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht 
tm pbe syscall nx rdtscp x86-64 constant_tsc arch_perfmon pebs bts rep_good 
nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx 
est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer 
rdrand lahf_lm 3dnowprefetch epb tpr_shadow vnmi flexpriority ept vpid 
tsc_adjust smep erms dtherm ida arat cpufreq
   *-pci
    description: Host bridge
    product: Atom Processor Z36xxx/Z37xxx Series SoC Transaction 
Register
    vendor: Intel Corporation
    physical id: 100
    bus info: pci@:00:00.0
    version: 0e
    width: 32 bits
    clock: 33MHz
    configuration: driver=iosf_mbi_pci
    resources: irq:0
  *-display
   description: VGA compatible controller
   product: Atom Processor Z36xxx/Z37xxx Series Graphics & Display
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 0e
   width: 32 bits
   clock: 33MHz
   capabilities: pm msi vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:89 memory:d000-d03f 
memory:c000-cfff ioport:f080(size=8)
  *-storage
   description: SATA controller
   product: Atom Processor E3800 Series SATA AHCI Controller
   vendor: Intel Corporation
   physical id: 13
   bus info: pci@:00:13.0
   version: 0e
   width: 32 bits

[Kernel-packages] [Bug 1575506] Re: Xenial: ARM64: Unable to handle kernel NULL pointer dereference at virtual address 00000038

Ming - please try the kernel at
http://people.canonical.com/~rtg/lp1575506/ - I've updated AUFS to the
latest stable branch. Source at git://kernel.ubuntu.com/rtg/ubuntu-
xenial.git aufs

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

Title:
  Xenial: ARM64: Unable to handle kernel NULL pointer dereference at
  virtual address 0038

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  When running 'stress-ng --all 64 -t 800 -v' on Xenial/ARM64, the following 
kernel oops is triggered.

  
  [   93.309158] Unable to handle kernel NULL pointer dereference at virtual 
address 0038
  [   93.309160] pgd = 8007a5914000
  [   93.309163] [0038] *pgd=0047a5b15003, *pud=0047a5b16003, 
*pmd=
  [   93.309167] Internal error: Oops: 9606 [#1] SMP
  [   93.309202] Modules linked in: wp512 rmd320 rmd256 rmd160 rmd128 md4 
algif_hash af_alg xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter ip_tables x_tables nls_iso8859_1 shpchp ghash_ce sha2_ce sha1_ce 
xgene_rng i2c_xgene_slimpro xgene_edac dwc3 edac_core udc_core 
i2c_designware_platform ulpi i2c_designware_core uio_pdrv_genirq uio gpio_keys 
rtc_efi autofs4 tg3 ptp pps_core sdhci_of_arasan ahci_xgene gpio_dwapb 
sdhci_pltfm xgene_enet libahci_platform sdhci libahci gpio_xgene_sb
  [   93.309208] CPU: 5 PID: 2062 Comm: stress-ng-remap Not tainted 
4.4.0-15.31-generic #31+clk.1
  [   93.309209] Hardware name: AppliedMicro Mustang/Mustang, BIOS 2.04.08-beta 
Feb  2 2016
  [   93.309211] task: 8007a58c5b00 ti: 8007a7a3 task.ti: 
8007a7a3
  [   93.309217] PC is at fput+0x20/0xd0
  [   93.309222] LR is at vma_do_fput+0x24/0x48
  [   93.309223] pc : [] lr : [] pstate: 
6145
  [   93.309224] sp : 8007a7a33e20
  [   93.309226] x29: 8007a7a33e20 x28: 8007a7a3 
  [   93.309228] x27: 0003 x26: 8007a59886e8 
  [   93.309229] x25: 800746248ed8 x24: 8011 
  [   93.309231] x23:  x22: 8091b780 
  [   93.309232] x21: 1000 x20:  
  [   93.309233] x19:  x18: 1140 
  [   93.309235] x17: 8915f2c0 x16: 80133de0 
  [   93.309236] x15: 893c2000 x14:  
  [   93.309237] x13: 0003e800 x12: 734b0200 
  [   93.309239] x11: 003d0f00 x10: 0930 
  [   93.309240] x9 :  x8 :  
  [   93.309242] x7 : 80074645ac10 x6 : 00680f43 
  [   93.309243] x5 : 00680f4f x4 : 0064 
  [   93.309245] x3 : 00680f53 x2 : 0038 
  [   93.309246] x1 : 8091b780 x0 : 801fe1f4 

  [   93.309248] Process stress-ng-remap (pid: 2062, stack limit = 
0x8007a7a30020)
  [   93.309250] Stack: (0x8007a7a33e20 to 0x8007a7a34000)
  [   93.309252] 3e20: 8007a7a33e40 801fe1f4  
8007a59886e8
  [   93.309253] 3e40: 8007a7a33e60 8020c1c0 8830 
80d8e000
  [   93.309255] 3e60: c85b2280 80085c70  
88301000
  [   93.309257] 3e80:  89161ea8 8000 
0015
  [   93.309258] 3ea0: 011d 00ea 80901000 
8007a7a3
  [   93.309260] 3ec0: 1000 cb88537fdc8ba606 8830 
1000
  [   93.309261] 3ee0:    
0200
  [   93.309262] 3f00: 00d1 00d1 00ea 
2626
  [   93.309264] 3f20: 0101010101010101 001e 0018 
0003e800
  [   93.309266] 3f40:  893c2cc0 004828c0 
89161ea0
  [   93.309267] 3f60: 1140 0050 88301000 
1000
  [   93.309269] 3f80: 1000 c85b2368 88d96fd0 
4650
  [   93.309270] 3fa0: 004558f0 c85b34b8 0048f000 
c85b2280
  [   93.309271] 3fc0: 0042ec60 c85b2280 89161ea8 
8000
  [   93.309273] 3fe0: 8830 00ea 8007a7a33fe8 

  [   93.309274] Call trace:
  [   93.309277] [] fput+0x20/0xd0
  [   93.309280] [] vma_do_fput+0x24/0x48
  [   93.309283] [] SyS_remap_file_pages+0x258/0x2a0
  [   93.309287] [] el0_svc_naked+0x24/0x28
  [   93.309289] Code: aa1e03e0 d503201f 9100e262 f9800051 (c85f7c40) 
  [   93.309308] ---[ end trace e42a31bddbea7038 ]---
  [   93.672808] Unable to handle kernel NULL pointer dereference at virtual 
address 0038
  [

[Kernel-packages] [Bug 1576025] Re: Different kernel image seen hiding

2016-04-28 Thread MadhuSoodanan

** Summary changed:

- Different kernal images seen
+ Different kernel image seen hiding

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

Title:
  Different kernel image seen hiding

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I got i686 when I used the following command

  madhu@madhu-desktop:~$ uname -mrsn
  Linux madhu-desktop 4.4.0-21-generic i686

  madhu@madhu-desktop:~$ dpkg --list | grep linux-image
  ii  linux-image-4.4.0-21-generic 4.4.0-21.37  
   i386 Linux kernel image for version 4.4.0 on 32 
bit x86 SMP
  ii  linux-image-extra-4.4.0-21-generic   4.4.0-21.37  
   i386 Linux kernel extra modules for version 
4.4.0 on 32 bit x86 SMP
  ii  linux-image-generic  4.4.0.21.22  
   i386 Generic Linux kernel image
  madhu@madhu-desktop:~$
  --- 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  madhu  1519 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=e7fdca52-e71c-49c7-8f88-05c9b52cb128
  InstallationDate: Installed on 2016-04-23 (5 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=a7e88f7c-3feb-4944-8547-2c8bb94f5255 ro quiet splash vt.handoff=7
  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 i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/10/2007
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PE94510M.86A.0050.2007.0710.1559
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: D945GCPE
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD97209-201
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPE94510M.86A.0050.2007.0710.1559:bd07/10/2007:svn:pn:pvr:rvnIntelCorporation:rnD945GCPE:rvrAAD97209-201:cvn:ct3:cvr:

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

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

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

2016-04-28 Thread bugproxy

--- Comment From hbath...@in.ibm.com 2016-04-28 09:20 EDT---
(In reply to comment #20)
> That patch (http://patchwork.ozlabs.org/patch/577193/) should have made it
> upstream by now. What is going on with it ?

Mahesh spoke to PPC Maintainer offline about this patch. Since the
changes are more invasive (and at the code path which is used at every
boot) review is taking time. Maintainer is also thinking about alternate
solution but that includes rewriting lots of cpu numbering code. So as
of now maintainer conveyed that he needs some more time (hasn't mention
specific time) to review this patch to be very sure that it is not
harmful.

So as it stands, this patch may not be going anywhere at least for some
time..

Thanks
Hari

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

Title:
  ISST-LTE: high cpus number need a high crashkernel value in kdump

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

Bug description:
  ---Problem Description---
  The kdump kernel will be booted with "maxcpus=1", so no matter how many cpus 
this system has, only one cpu will be brought up during kdump I think. But on 
LPAR thymelp2, if we allocate 40 cpus on it, then kdump works just fine with 
512M  as crashkernel value. But if we allocate 200 cpus on it, kdump fails by 
trggering OOM. It has been proved that in latter situation we need 1.5G RAM 
reserved for kdump to let it works.
   
  ---Steps to Reproduce---
   1. configure kdump with crashkernel=512M on thymelp2
  2. allcoate 40 cpus on thymelp2 and trigger kdump
  3. allocate 200 cpus on thymelp2 then do kdump again
   
  ---
  Mahesh has posted a patch upstream to provide support for nr_cpus in kdump 
kernel.
  That should take care of this problem..

  https://lists.ozlabs.org/pipermail/linuxppc-dev/2016-February/138619.html
  ---

  Heads up Canonical: We'll want this patch included as soon
  possible/practical.

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

-- 
Mailing list: https://launchpad.net/~kernel-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-04-28 Thread shinyblue

Phew! Just done all 48 of these tests...

Tests:

1. GDM starts
2. Lightdm starts
3. Can launch Gnome
4. Can launch Gnome Classic
5. External monitor with Lightdm
6. External monitor with Gdm
7. External monitor with Gnome
8. External monitor with Gnome Classic

Results: . is fine, E is error (caused hang), F is fail but not hang. S
is skipped, e.g. couldn't get to that test.

Variables:

- graphics driver
- prime select, one of:
- intel (530 Skylake GT2)
- NVIDIA Corporation GM107M [GeForce GTX 960M]

Results
---
Config Driver Prime 12345678
---
c1 361.42-0ubuntu2 intel EF*F
c2 361.42-0ubuntu2 nvidia FFFF
c3 361.42-0ubuntu0~gpu16.04.1 intel FFEE
c4 361.42-0ubuntu0~gpu16.04.1 nvidia FFFF
c5 364.19-0ubuntu0~gpu16.04.1 intel .FEE
c6 364.19-0ubuntu0~gpu16.04.1 nvidia F.FF?SSS
---

## Config 1 ##

- 7:* Probably an E. I had it as a pass because when one monitor is ON it
works, but having done the other tests I realised that the hang comes when
two are turned on at once, which was not something I tested here.

- 5:E With monitor plugged in, working under Gnome, logging out to LightDm
caused hang. Also booting to lightdm with hdmi monitor caused hang.

- 6:F. gdm goes blinky on laptop, unusable with external screen plugged in. See
note below, seems to be the same problem: can't do two screens at once.
Unplugging restores a working laptop screen.

- 8:F on test 8 first plugin of monitor caused blank screens. Unplug, replug
gave
an image on the external, laptop turned off. Nb. I had the 'Displays' config
ui up the 2nd time I plugged in, not sure if this makes any difference. This
is working. But trying to turn them both on at once resulted in a flashing
unusable display on the laptop

## Config 2 ##

- 1:F gdm gives completely black screen. Can swap to tty, system not
dead.

- 7:F both screens blank, laptop one twitches a bit. Removing cable brought
back system.

- 8:F as 7:F, but when unplugged needed to swap to tty and back to get
functioning mouse/interface.

- 6:F as for 1:F

## Config 3 ##

- 5:F lightdm goes all black/flickery when external monitor plugged in.
Recoverable, though.

- 6:F gdm like lightdm when external monitor plugged in.

- 7:E, 8:E **gnome works on one screen**, but selecting both on causes a
complete hang.

## Config 4 ##

- 1:F black screen. Pressing power button does cause normal shutdown

- 7:F both go black. Recovered after unplug.

- 8:F as 7:F

## Config 5 ##

- 6:F flashy screen, mostly blank. Removing cable (quickly) brought
stability.

- 7:E, 8:E ext. monitor works but hang if 2 displays at once.

## Config 6 ##

Was all the same.

## Conclusions ##

- GDM: intel only across the three drivers.

- Gnome/Gnome classic behave the same.

- Two monitors:

- both on: you just can't have it with gnome. (lightdm works, and previously
I had Unity working, too)

- one on: works with intel, not nvidia.

** Attachment added: "syslog and Xorg.* logs"

https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1559576/+attachment/4650172/+files/syslog.tgz

--
You 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:
New
Status in Ubuntu GNOME:
New
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=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

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

This change was made by a bot.

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

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

Title:
  Ubuntu 16.04 doesn't recognize CyPS/2 Cypress Trackpad

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop: Dell XPS13 L321x
  Trackpad: Cypress Trackpad / Clickpad

  Problem appeared after update from 14.04 to 16.04

  The touchpad is not listed under /proc/bus/input/devices altough it
  shows up if using 14.04 via live usb

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

-- 
Mailing list: https://launchpad.net/~kernel-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-04-28 Thread shinyblue

Attempt to re-do formatting...

---
Config Driver  Prime   12345678
---
c1 361.42-0ubuntu2 intel   EF.F
c2 361.42-0ubuntu2 nvidia  FFFF
c3 361.42-0ubuntu0~gpu16.04.1  intel   FFEE
c4 361.42-0ubuntu0~gpu16.04.1  nvidia  FFFF
c5 364.19-0ubuntu0~gpu16.04.1  intel   .FEE
c6 364.19-0ubuntu0~gpu16.04.1  nvidia  F.FF?SSS
---

-- 
You 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:
  New
Status in Ubuntu GNOME:
  New
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=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 1560552] Comment bridged from LTC Bugzilla

2016-04-28 Thread bugproxy

--- Comment From hbath...@in.ibm.com 2016-04-28 09:20 EDT---
Mahesh spoke to PPC Maintainer offline about this patch. Since the changes are 
more invasive (and at the code path which is used at every boot) review is 
taking time. Maintainer is also thinking about alternate solution but that 
includes rewriting lots of cpu numbering code. So as of now maintainer conveyed 
that he needs some more time (hasn't mention specific time) to review this 
patch to be very sure that it is not harmful.

So as it stands, this patch may not be going anywhere at least for some
time..

Thanks
Hari

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

Title:
  ISST-LTE: pVM:high cpus number need a high crashkernel value in kdump

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

Bug description:
  The kdump kernel will be booted with "maxcpus=1", so no matter how many cpus 
this system has, only one cpu will be brought up during kdump I think. But on 
LPAR thymelp2, if we allocate 40 cpus on it, then kdump works just fine with 
512M  as crashkernel value. But if we allocate 200 cpus on it, kdump fails by 
trggering OOM. It has been proved that in latter situation we need 1.5G RAM 
reserved for kdump to let it works.
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux thymelp2 4.2.0-23-generic #28~14.04.1-Ubuntu SMP Thu Dec 31 13:41:19 
UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = 8247-22L, LPAR 
   ---Debugger---
  A debugger was configured, however the system did not enter into the debugger
   
  ---Steps to Reproduce---
   1. configure kdump with crashkernel=512M on thymelp2
  2. allcoate 40 cpus on thymelp2 and trigger kdump
  3. allocate 200 cpus on thymelp2 then do kdump again
   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #1 - Nadia N. Fry  - 2016-02-19 13:53:02 ==
  Any update?

  == Comment: #2 - Hari Krishna Bathini  - 2016-02-22 
03:40:05 ==
  Mahesh posted a patch upstream which should take care of this problem

  http://patchwork.ozlabs.org/patch/577193/

  Thanks
  Hari

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

-- 
Mailing list: https://launchpad.net/~kernel-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-04-28 Thread shinyblue

Attempt to re-do formatting AGAIN!

---
Config_Driver__Prime___12345678
---
c1_361.42-0ubuntu2_intel___EF.F
c2_361.42-0ubuntu2_nvidia__FFFF
c3_361.42-0ubuntu0~gpu16.04.1__intel___FFEE
c4_361.42-0ubuntu0~gpu16.04.1__nvidia__FFFF
c5_364.19-0ubuntu0~gpu16.04.1__intel___.FEE
c6_364.19-0ubuntu0~gpu16.04.1__nvidia__F.FF?SSS
---

-- 
You 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:
  New
Status in Ubuntu GNOME:
  New
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=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 1576222] Status changed to Confirmed