Re: [Kernel-packages] [Bug 1460365] Re: 3.19 kernels in 15.04 do not work on my 32bit system

[Bryan Cebuliak]

Thank you, Christopher Penalver, for your prompt response. I updated  the
BIOS  from 5.16 to 5.22 as  you directed via the Windows Vista partition.
All aforementioned Ubuntu Linux kernels, old, new official 15.04 and
upstream now boot  properly on the  machine [and even  the Debian partition
kernels] :) The BIOS update successfully worked  around the kernel bug.

On 31 May 2015 at 23:27, Christopher M. Penalver 
christopher.m.penal...@gmail.com wrote:

 Bryan Cebuliak, thank you for reporting this and helping make Ubuntu
 better. As per http://support.hp.com/us-en/drivers/selfservice/HP-
 Pavilion-a6700-Desktop-PC-series/3823602/model/3830446 an update to your
 computer's buggy and outdated BIOS is available (5.22). If you update to
 this following https://help.ubuntu.com/community/BIOSUpdate does it
 change anything?

 If it doesn't, could you please both specify what happened, and provide
 the output of the following terminal command:
 sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date

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

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

 Once the BIOS is updated, and the information above is provided, then
 please mark this report Status Confirmed.

 Thank you for your understanding.

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

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1460365

 Title:
   3.19 kernels in 15.04 do not work  on my  32bit system

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


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

Title:
  3.19 kernels in 15.04 do not work  on my  32bit system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since  upgrading from 14.10  [3.16 kernel]  to 15.04 the 3.19 kernels  
including 3.19.0-20 will   either  stall   on  bootor   leave   me   
without   proper   graphics or nil  keyboard  and  mouse even  on recovery boot 
.  The  next functioning mainline kernel is  v4.0-rc1-vivid. No  problem there. 
 I  suggest you  abandon  completely  this very problematic end of life   
kernel and   quickly test and  backport a newer series.  3.19 up to 3.19.7 has 
also given me similar   grief on my old  Macbook 2,1 64bit.
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: i386
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2012-09-04 (998 days ago)
  InstallationMedia: Lubuntu 12.04 Precise Pangolin - Release i386 (20120423)
  Package: linux (not installed)
  Tags:  vivid
  Uname: Linux 4.0.0-04rc1-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to vivid on 2015-05-31 (0 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse lp lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  elaine 1316 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=cf1e0e2c-e614-46b7-af16-815ef38b4dfc
  InstallationDate: Installed on 2012-09-04 (998 days ago)
  InstallationMedia: Lubuntu 12.04 Precise Pangolin - Release i386 (20120423)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: HP-Pavilion FT958AA-ABG a6710a
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic 
root=UUID=3a08a446-f1f6-42a5-ba42-c00b38ccfac0 ro
  ProcVersionSignature: Ubuntu 3.16.0-38.52-generic 3.16.7-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-38-generic N/A
   linux-backports-modules-3.16.0-38-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   
  Tags:  vivid
  Uname: Linux 3.16.0-38-generic i686
  UpgradeStatus: Upgraded to vivid on 2015-05-31 (0 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse lp lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 11/10/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.16
  dmi.board.name: Boston
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.16:bd11/10/2008:svnHP-Pavilion:pnFT958AA-ABGa6710a:pvr:rvnMSI:rnBoston:rvr1.0:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: FT958AA-ABG a6710a
  dmi.sys.vendor: HP-Pavilion
  --- 
  ApportVersion: 

[Kernel-packages] [Bug 1458618] Re: linux: 3.13.0-54.91 -proposed tracker

[John Johansen]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed = In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) = John Johansen 
(jjohansen)

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

Title:
  linux: 3.13.0-54.91 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow package-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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 25. May 2015 16:17 UTC
  kernel-stable-Prepare-package-end:Wednesday, 27. May 2015 02:03 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 27. May 2015 02:03 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:12 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:28 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:28 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:28 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:28 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:28 UTC

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

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

[Kernel-packages] [Bug 1458778] Re: linux: 3.16.0-39.53 -proposed tracker

[John Johansen]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed = In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) = John Johansen 
(jjohansen)

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

Title:
  linux: 3.16.0-39.53 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow package-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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Utopic:
  New

Bug description:
  This bug is for tracking the 3.16.0-39.53 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, 26. May 2015 08:17 UTC
  kernel-stable-Prepare-package-end:Tuesday, 26. May 2015 19:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 26. May 2015 19:02 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:00 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:00 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:00 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:00 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:00 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:00 UTC

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

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

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

[John Johansen]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed = In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) = John Johansen 
(jjohansen)

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow package-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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.16.0-39.53~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, 26. May 2015 19:00 UTC
  kernel-stable-master-bug:1458778
  kernel-stable-Prepare-package-end:Wednesday, 27. May 2015 19:01 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 27. May 2015 19:01 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:00 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:01 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:01 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:01 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:01 UTC

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

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

[Kernel-packages] [Bug 1459957] Re: linux: 3.19.0-20.20 -proposed tracker

[John Johansen]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed = In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) = John Johansen 
(jjohansen)

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

Title:
  linux: 3.19.0-20.20 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow package-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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Confirmed

Bug description:
  This bug is for tracking the 3.19.0-20.20 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:Friday, 29. May 2015 08:47 UTC
  kernel-stable-Prepare-package-end:Friday, 29. May 2015 19:03 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 29. May 2015 19:03 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:01 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:02 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:02 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:02 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:02 UTC

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

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

[Kernel-packages] [Bug 1458999] Re: linux-ti-omap4: 3.2.0-1465.85 -proposed tracker

[John Johansen]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed = In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) = John Johansen 
(jjohansen)

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

Title:
  linux-ti-omap4: 3.2.0-1465.85 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow package-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 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:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New

Bug description:
  This bug is for tracking the version to be filled 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, 26. May 2015 20:03 UTC
  kernel-stable-master-bug:1458901
  kernel-stable-Certification-testing-end:Friday, 29. May 2015 09:00 UTC
  kernel-stable-Prepare-package-end:Friday, 29. May 2015 12:01 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 29. May 2015 12:01 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 21:29 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 23:01 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 23:01 UTC
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 23:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 23:01 UTC

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

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

[Kernel-packages] [Bug 1458901] Re: linux: 3.2.0-85.122 -proposed tracker

[John Johansen]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed = In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) = John Johansen 
(jjohansen)

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

Title:
  linux: 3.2.0-85.122 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.2.0-85.122 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, 26. May 2015 14:37 UTC
  kernel-stable-Prepare-package-end:Tuesday, 26. May 2015 20:06 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 26. May 2015 20:06 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 21:29 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 23:00 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 23:00 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 23:00 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 23:00 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 23:00 UTC

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

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

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

[John Johansen]

** Changed in: kernel-sru-workflow/security-signoff
   Status: Confirmed = In Progress

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) = John Johansen 
(jjohansen)

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow package-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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.13.0-54.91~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Wednesday, 27. May 2015 02:01 UTC
  kernel-stable-master-bug:1458618
  kernel-stable-Prepare-package-end:Wednesday, 27. May 2015 18:01 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 27. May 2015 18:01 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:12 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:30 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:30 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:30 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:30 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:30 UTC

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

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

[Kernel-packages] [Bug 1460601] Re: Surface Pro 2 wifi crash

[Christopher M. Penalver]

Tom, thank you for reporting this and helping make Ubuntu better. Could
you please test the latest upstream kernel available from the very top
line at the top of the page (the release names are irrelevant for
testing, and please do not test the daily folder) following
https://wiki.ubuntu.com/Kernel/MainlineBuilds ? It will allow additional
upstream developers to examine the issue.

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

Where XY and Z are numbers corresponding to the kernel version.

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

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

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results.

Thank you for your understanding.

** Tags added: latest-bios-v2.5.250.0

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

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

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

Title:
  Surface Pro 2 wifi crash

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  System hangs as soon as any network traffic is generated from wifi
  adaptor.

  think i may have caught the crash trying to install wireshark via the
  console (ctrl + alt + f1)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-18-generic 3.19.0-18.18
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tom1635 F pulseaudio
  Date: Mon Jun  1 20:03:57 2015
  HibernationDevice: RESUME=UUID=ae61b08a-a372-4d5a-b4d6-64bf1c8a55a8
  InstallationDate: Installed on 2015-05-31 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  MachineType: Microsoft Corporation Surface Pro 2
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed 
root=UUID=cc5fc4f0-7f27-42c3-b890-87ac9cbf1628 ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware 1.143.1
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.05.0250
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Surface Pro 2
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: 0
  dmi.chassis.type: 11
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.05.0250:bd04/10/2015:svnMicrosoftCorporation:pnSurfacePro2:pvr1:rvnMicrosoftCorporation:rnSurfacePro2:rvr1:cvnMicrosoftCorporation:ct11:cvr1:
  dmi.product.name: Surface Pro 2
  dmi.product.version: 1
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1458351] Re: Some Fn+ Keys Not Working

[Christopher M. Penalver]

Carlo Abelli, could you please test the latest upstream kernel available
from the very top line at the top of the page (the release names are
irrelevant for testing, and please do not test the daily folder)
following https://wiki.ubuntu.com/Kernel/MainlineBuilds ? It will allow
additional upstream developers to examine the issue.

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

Where XY and Z are numbers corresponding to the kernel version.

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

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

Once testing of the upstream kernel is complete, please mark this bug's
Status as Confirmed. Please let us know your results.

Thank you for your understanding.

** Tags added: vivid

** Package changed: xorg (Ubuntu) = linux (Ubuntu)

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

Title:
  Some Fn+ Keys Not Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Brightness control keys on my laptop not being recognized (including
  no output from acpi_listen). Running Ubuntu 14.04.2 LTS. Other
  function keys do work and are recognized ex. volume.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10
  Uname: Linux 3.16.0-38-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun May 24 12:59:49 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:181d]
  InstallationDate: Installed on 2015-05-23 (0 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 003: ID 064e:9700 Suyin Corp. 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305FA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic.efi.signed 
root=UUID=246981b4-9b06-41f9-ac18-1e5ba27d4247 ro quiet splash acpi_osi=Linux 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305FA.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305FA
  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.:bvrUX305FA.208:bd03/26/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: UX305FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun May 24 12:07:13 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id8493 
   vendor   

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

[Tomek]

apport information

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

Title:
  Random screen locking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random screen locking happens about once an hour. Mouse is not
  responding, keyboard is, but GUI does not respond. To overcome the
  problem I have to switch to terminal with ctrl+alt+1 and go back. In
  dmesg I can see:

  [   68.509976] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510021] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510044] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510064] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510083] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510102] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510134] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510154] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510644] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.615945] vgaarb: this pci device is not a vga device

  $ dmesg | grep vgaarb
  [0.524324] vgaarb: setting as boot device: PCI::00:02.0
  [0.524325] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [0.524328] vgaarb: loaded
  [0.524329] vgaarb: bridge control possible :00:02.0
  [1.498735] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [5.667900] vgaarb: this pci device is not a vga device
  [6.409112] vgaarb: this pci device is not a vga device
  [   68.506178] vgaarb: this pci device is not a vga device
  [   68.615945] vgaarb: this pci device is not a vga device

  $ lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 
(rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 
01)
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 
620M/625M/630M/720M] (rev a1)

  Dell Latitude E5540

  SMBIOS 2.7 present.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: A11
Release Date: 02/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 14336 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25/1.2 MB floppy services are supported (int 13h)
3.5/720 kB floppy services are supported (int 13h)
3.5/2.88 MB floppy 

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

[Tomek]

apport information

** Attachment added: RfKill.txt
   https://bugs.launchpad.net/bugs/1460551/+attachment/4408018/+files/RfKill.txt

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

Title:
  Random screen locking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random screen locking happens about once an hour. Mouse is not
  responding, keyboard is, but GUI does not respond. To overcome the
  problem I have to switch to terminal with ctrl+alt+1 and go back. In
  dmesg I can see:

  [   68.509976] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510021] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510044] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510064] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510083] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510102] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510134] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510154] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510644] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.615945] vgaarb: this pci device is not a vga device

  $ dmesg | grep vgaarb
  [0.524324] vgaarb: setting as boot device: PCI::00:02.0
  [0.524325] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [0.524328] vgaarb: loaded
  [0.524329] vgaarb: bridge control possible :00:02.0
  [1.498735] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [5.667900] vgaarb: this pci device is not a vga device
  [6.409112] vgaarb: this pci device is not a vga device
  [   68.506178] vgaarb: this pci device is not a vga device
  [   68.615945] vgaarb: this pci device is not a vga device

  $ lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 
(rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 
01)
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 
620M/625M/630M/720M] (rev a1)

  Dell Latitude E5540

  SMBIOS 2.7 present.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: A11
Release Date: 02/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 14336 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25/1.2 MB floppy services are supported (int 13h)
3.5/720 kB floppy services are supported (int 13h)
3.5/2.88 MB floppy services 

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

[Tomek]

apport information

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

Title:
  Random screen locking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random screen locking happens about once an hour. Mouse is not
  responding, keyboard is, but GUI does not respond. To overcome the
  problem I have to switch to terminal with ctrl+alt+1 and go back. In
  dmesg I can see:

  [   68.509976] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510021] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510044] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510064] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510083] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510102] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510134] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510154] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510644] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.615945] vgaarb: this pci device is not a vga device

  $ dmesg | grep vgaarb
  [0.524324] vgaarb: setting as boot device: PCI::00:02.0
  [0.524325] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [0.524328] vgaarb: loaded
  [0.524329] vgaarb: bridge control possible :00:02.0
  [1.498735] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [5.667900] vgaarb: this pci device is not a vga device
  [6.409112] vgaarb: this pci device is not a vga device
  [   68.506178] vgaarb: this pci device is not a vga device
  [   68.615945] vgaarb: this pci device is not a vga device

  $ lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 
(rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 
01)
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 
620M/625M/630M/720M] (rev a1)

  Dell Latitude E5540

  SMBIOS 2.7 present.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: A11
Release Date: 02/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 14336 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25/1.2 MB floppy services are supported (int 13h)
3.5/720 kB floppy services are supported (int 13h)
3.5/2.88 MB floppy services 

[Kernel-packages] [Bug 1390223] Re: Apparmor related regression on access to unix sockets on a candidate 3.16 backport kernel

[Lee Lists]

Hi,

Where is the Fix Committed, is there a package we could try or build ?

Regards,
Lee

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

Title:
  Apparmor related regression on access to unix sockets on a candidate
  3.16 backport kernel

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Utopic:
  Confirmed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  I recently noticed a bunch of containers failing in a rather odd way
  when running postfix.

  The most visible example is when running mailq on an empty queue.
  Without apparmor (unconfined container) I see that the queue is empty,
  with apparmor, I get Permission denied.

  That's all running as root so the permission denied looks a tiny bit
  odd. Also, running the 3.13 kernel, I don't get any of that weirdness.

  My guess is that it has to do with the work that went into the 3.16
  kernel for socket mediation. In theory only systems that run the
  utopic apparmor (which I DO NOT) should be seeing that kind of
  behavior, but it looks like some code path isn't checking things
  properly :)

  == strace in unconfined container ==
  chdir(/var/spool/postfix) = 0
  rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART, 
0x7f8963a62c30}, {SIG_IGN, [], 0}, 8) = 0
  getuid()= 0
  socket(PF_LOCAL, SOCK_STREAM, 0)= 4
  fcntl(4, F_GETFL)   = 0x2 (flags O_RDWR)
  fcntl(4, F_SETFL, O_RDWR)   = 0
  connect(4, {sa_family=AF_LOCAL, sun_path=public/showq}, 110) = 0
  poll([{fd=4, events=POLLIN}], 1, 360) = 1 ([{fd=4, 
revents=POLLIN|POLLHUP}])
  read(4, Mail queue is empty\n, 4096)  = 20
  poll([{fd=4, events=POLLIN}], 1, 360) = 1 ([{fd=4, 
revents=POLLIN|POLLHUP}])
  read(4, , 4096)   = 0
  write(1, Mail queue is empty\n, 20Mail queue is empty
  )   = 20
  close(4)= 0
  exit_group(0)   = ?
  +++ exited with 0 +++

  == strace in confined container ==
  chdir(/var/spool/postfix) = 0
  rt_sigaction(SIGPIPE, {SIG_IGN, [PIPE], SA_RESTORER|SA_RESTART, 
0x7ffe62de4c30}, {SIG_IGN, [], 0}, 8) = 0
  getuid()= 0
  socket(PF_LOCAL, SOCK_STREAM, 0)= 4
  fcntl(4, F_GETFL)   = 0x2 (flags O_RDWR)
  fcntl(4, F_SETFL, O_RDWR)   = 0
  connect(4, {sa_family=AF_LOCAL, sun_path=public/showq}, 110) = 0
  poll([{fd=4, events=POLLIN}], 1, 360) = 1 ([{fd=4, 
revents=POLLIN|POLLHUP}])
  read(4, 0x7ffe65b35c00, 4096)   = -1 EACCES (Permission denied)
  close(4)= 0
  write(2, postqueue: warning: close: Permi..., 45postqueue: warning: close: 
Permission denied
  ) = 45
  sendto(3, 20Nov  6 20:40:42 postfix/post..., 78, MSG_NOSIGNAL, NULL, 0) = 
78
  exit_group(0)   = ?

  Kernel is a slightly outdated version of the kernel from the kernel team PPA:
  Linux shell01 3.16.0-23-generic #31-Ubuntu SMP Thu Oct 23 20:13:35 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

  If you think the latest build will improve this, I can test it, but
  seeing how this is a production server, I can't just flip kernels
  every 5 minutes (I'm running 3.16 to avoid a nasty btrfs bug on 3.13).

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

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

[Kernel-packages] [Bug 1458351] [NEW] Some Fn+ Keys Not Working

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Brightness control keys on my laptop not being recognized (including no
output from acpi_listen). Running Ubuntu 14.04.2 LTS. Other function
keys do work and are recognized ex. volume.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10
Uname: Linux 3.16.0-38-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun May 24 12:59:49 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:181d]
InstallationDate: Installed on 2015-05-23 (0 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 003: ID 064e:9700 Suyin Corp. 
 Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX305FA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic.efi.signed 
root=UUID=246981b4-9b06-41f9-ac18-1e5ba27d4247 ro quiet splash acpi_osi=Linux 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/26/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX305FA.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX305FA
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.:bvrUX305FA.208:bd03/26/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX305FA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sun May 24 12:07:13 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id8493 
 vendor AUO
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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


** Tags: amd64 apport-bug compiz-0.9 latest-bios-208 trusty ubuntu vivid
-- 
Some Fn+ Keys Not Working
https://bugs.launchpad.net/bugs/1458351
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1460551] UdevLog.txt

[Tomek]

apport information

** Attachment added: UdevLog.txt
   
https://bugs.launchpad.net/bugs/1460551/+attachment/4408020/+files/UdevLog.txt

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

Title:
  Random screen locking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random screen locking happens about once an hour. Mouse is not
  responding, keyboard is, but GUI does not respond. To overcome the
  problem I have to switch to terminal with ctrl+alt+1 and go back. In
  dmesg I can see:

  [   68.509976] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510021] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510044] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510064] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510083] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510102] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510134] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510154] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510644] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.615945] vgaarb: this pci device is not a vga device

  $ dmesg | grep vgaarb
  [0.524324] vgaarb: setting as boot device: PCI::00:02.0
  [0.524325] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [0.524328] vgaarb: loaded
  [0.524329] vgaarb: bridge control possible :00:02.0
  [1.498735] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [5.667900] vgaarb: this pci device is not a vga device
  [6.409112] vgaarb: this pci device is not a vga device
  [   68.506178] vgaarb: this pci device is not a vga device
  [   68.615945] vgaarb: this pci device is not a vga device

  $ lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 
(rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 
01)
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 
620M/625M/630M/720M] (rev a1)

  Dell Latitude E5540

  SMBIOS 2.7 present.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: A11
Release Date: 02/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 14336 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25/1.2 MB floppy services are supported (int 13h)
3.5/720 kB floppy services are supported (int 13h)
3.5/2.88 MB floppy 

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

[Tomek]

apport information

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

Title:
  Random screen locking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random screen locking happens about once an hour. Mouse is not
  responding, keyboard is, but GUI does not respond. To overcome the
  problem I have to switch to terminal with ctrl+alt+1 and go back. In
  dmesg I can see:

  [   68.509976] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510021] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510044] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510064] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510083] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510102] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510134] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510154] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510644] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.615945] vgaarb: this pci device is not a vga device

  $ dmesg | grep vgaarb
  [0.524324] vgaarb: setting as boot device: PCI::00:02.0
  [0.524325] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [0.524328] vgaarb: loaded
  [0.524329] vgaarb: bridge control possible :00:02.0
  [1.498735] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [5.667900] vgaarb: this pci device is not a vga device
  [6.409112] vgaarb: this pci device is not a vga device
  [   68.506178] vgaarb: this pci device is not a vga device
  [   68.615945] vgaarb: this pci device is not a vga device

  $ lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 
(rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 
01)
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 
620M/625M/630M/720M] (rev a1)

  Dell Latitude E5540

  SMBIOS 2.7 present.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: A11
Release Date: 02/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 14336 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25/1.2 MB floppy services are supported (int 13h)
3.5/720 kB floppy services are supported (int 13h)
3.5/2.88 MB floppy services are 

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

[Tomek]

apport information

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

Title:
  Random screen locking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random screen locking happens about once an hour. Mouse is not
  responding, keyboard is, but GUI does not respond. To overcome the
  problem I have to switch to terminal with ctrl+alt+1 and go back. In
  dmesg I can see:

  [   68.509976] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510021] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510044] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510064] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510083] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510102] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510134] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510154] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510644] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.615945] vgaarb: this pci device is not a vga device

  $ dmesg | grep vgaarb
  [0.524324] vgaarb: setting as boot device: PCI::00:02.0
  [0.524325] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [0.524328] vgaarb: loaded
  [0.524329] vgaarb: bridge control possible :00:02.0
  [1.498735] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [5.667900] vgaarb: this pci device is not a vga device
  [6.409112] vgaarb: this pci device is not a vga device
  [   68.506178] vgaarb: this pci device is not a vga device
  [   68.615945] vgaarb: this pci device is not a vga device

  $ lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 
(rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 
01)
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 
620M/625M/630M/720M] (rev a1)

  Dell Latitude E5540

  SMBIOS 2.7 present.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: A11
Release Date: 02/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 14336 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25/1.2 MB floppy services are supported (int 13h)
3.5/720 kB floppy services are supported (int 13h)
3.5/2.88 MB 

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

[Tomek]

apport information

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

Title:
  Random screen locking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random screen locking happens about once an hour. Mouse is not
  responding, keyboard is, but GUI does not respond. To overcome the
  problem I have to switch to terminal with ctrl+alt+1 and go back. In
  dmesg I can see:

  [   68.509976] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510021] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510044] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510064] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510083] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510102] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510134] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510154] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510644] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.615945] vgaarb: this pci device is not a vga device

  $ dmesg | grep vgaarb
  [0.524324] vgaarb: setting as boot device: PCI::00:02.0
  [0.524325] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [0.524328] vgaarb: loaded
  [0.524329] vgaarb: bridge control possible :00:02.0
  [1.498735] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [5.667900] vgaarb: this pci device is not a vga device
  [6.409112] vgaarb: this pci device is not a vga device
  [   68.506178] vgaarb: this pci device is not a vga device
  [   68.615945] vgaarb: this pci device is not a vga device

  $ lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 
(rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 
01)
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 
620M/625M/630M/720M] (rev a1)

  Dell Latitude E5540

  SMBIOS 2.7 present.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: A11
Release Date: 02/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 14336 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25/1.2 MB floppy services are supported (int 13h)
3.5/720 kB floppy services are supported (int 13h)
3.5/2.88 MB 

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

[Tomek]

apport information

** Attachment added: IwConfig.txt
   
https://bugs.launchpad.net/bugs/1460551/+attachment/4408010/+files/IwConfig.txt

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

Title:
  Random screen locking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random screen locking happens about once an hour. Mouse is not
  responding, keyboard is, but GUI does not respond. To overcome the
  problem I have to switch to terminal with ctrl+alt+1 and go back. In
  dmesg I can see:

  [   68.509976] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510021] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510044] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510064] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510083] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510102] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510134] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510154] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510644] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.615945] vgaarb: this pci device is not a vga device

  $ dmesg | grep vgaarb
  [0.524324] vgaarb: setting as boot device: PCI::00:02.0
  [0.524325] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [0.524328] vgaarb: loaded
  [0.524329] vgaarb: bridge control possible :00:02.0
  [1.498735] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [5.667900] vgaarb: this pci device is not a vga device
  [6.409112] vgaarb: this pci device is not a vga device
  [   68.506178] vgaarb: this pci device is not a vga device
  [   68.615945] vgaarb: this pci device is not a vga device

  $ lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 
(rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 
01)
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 
620M/625M/630M/720M] (rev a1)

  Dell Latitude E5540

  SMBIOS 2.7 present.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: A11
Release Date: 02/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 14336 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25/1.2 MB floppy services are supported (int 13h)
3.5/720 kB floppy services are supported (int 13h)
3.5/2.88 MB floppy 

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

[Tomek]

apport information

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

Title:
  Random screen locking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random screen locking happens about once an hour. Mouse is not
  responding, keyboard is, but GUI does not respond. To overcome the
  problem I have to switch to terminal with ctrl+alt+1 and go back. In
  dmesg I can see:

  [   68.509976] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510021] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510044] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510064] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510083] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510102] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510134] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510154] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510644] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.615945] vgaarb: this pci device is not a vga device

  $ dmesg | grep vgaarb
  [0.524324] vgaarb: setting as boot device: PCI::00:02.0
  [0.524325] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [0.524328] vgaarb: loaded
  [0.524329] vgaarb: bridge control possible :00:02.0
  [1.498735] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [5.667900] vgaarb: this pci device is not a vga device
  [6.409112] vgaarb: this pci device is not a vga device
  [   68.506178] vgaarb: this pci device is not a vga device
  [   68.615945] vgaarb: this pci device is not a vga device

  $ lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 
(rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 
01)
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 
620M/625M/630M/720M] (rev a1)

  Dell Latitude E5540

  SMBIOS 2.7 present.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: A11
Release Date: 02/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 14336 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25/1.2 MB floppy services are supported (int 13h)
3.5/720 kB floppy services are supported (int 13h)
3.5/2.88 MB 

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

[Tomek]

apport information

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

Title:
  Random screen locking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random screen locking happens about once an hour. Mouse is not
  responding, keyboard is, but GUI does not respond. To overcome the
  problem I have to switch to terminal with ctrl+alt+1 and go back. In
  dmesg I can see:

  [   68.509976] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510021] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510044] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510064] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510083] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510102] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510134] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510154] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510644] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.615945] vgaarb: this pci device is not a vga device

  $ dmesg | grep vgaarb
  [0.524324] vgaarb: setting as boot device: PCI::00:02.0
  [0.524325] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [0.524328] vgaarb: loaded
  [0.524329] vgaarb: bridge control possible :00:02.0
  [1.498735] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [5.667900] vgaarb: this pci device is not a vga device
  [6.409112] vgaarb: this pci device is not a vga device
  [   68.506178] vgaarb: this pci device is not a vga device
  [   68.615945] vgaarb: this pci device is not a vga device

  $ lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 
(rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 
01)
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 
620M/625M/630M/720M] (rev a1)

  Dell Latitude E5540

  SMBIOS 2.7 present.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: A11
Release Date: 02/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 14336 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25/1.2 MB floppy services are supported (int 13h)
3.5/720 kB floppy services are supported (int 13h)
3.5/2.88 MB 

[Kernel-packages] [Bug 1460551] Re: Random screen locking

[Tomek]

apport information

** Tags added: apport-collected

** Description changed:

  Random screen locking happens about once an hour. Mouse is not
  responding, keyboard is, but GUI does not respond. To overcome the
  problem I have to switch to terminal with ctrl+alt+1 and go back. In
  dmesg I can see:
  
  [   68.509976] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510021] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510044] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510064] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510083] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510102] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510134] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510154] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510644] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.615945] vgaarb: this pci device is not a vga device
  
  $ dmesg | grep vgaarb
  [0.524324] vgaarb: setting as boot device: PCI::00:02.0
  [0.524325] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [0.524328] vgaarb: loaded
  [0.524329] vgaarb: bridge control possible :00:02.0
  [1.498735] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [5.667900] vgaarb: this pci device is not a vga device
  [6.409112] vgaarb: this pci device is not a vga device
  [   68.506178] vgaarb: this pci device is not a vga device
  [   68.615945] vgaarb: this pci device is not a vga device
  
  $ lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 
(rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 
01)
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 
620M/625M/630M/720M] (rev a1)
  
  Dell Latitude E5540
  
  SMBIOS 2.7 present.
  
  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: A11
Release Date: 02/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 14336 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25/1.2 MB floppy services are supported (int 13h)
3.5/720 kB floppy services are supported (int 13h)
3.5/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported

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

[Tomek]

apport information

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

Title:
  Random screen locking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random screen locking happens about once an hour. Mouse is not
  responding, keyboard is, but GUI does not respond. To overcome the
  problem I have to switch to terminal with ctrl+alt+1 and go back. In
  dmesg I can see:

  [   68.509976] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510021] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510044] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510064] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510083] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510102] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510134] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510154] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510644] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.615945] vgaarb: this pci device is not a vga device

  $ dmesg | grep vgaarb
  [0.524324] vgaarb: setting as boot device: PCI::00:02.0
  [0.524325] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [0.524328] vgaarb: loaded
  [0.524329] vgaarb: bridge control possible :00:02.0
  [1.498735] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [5.667900] vgaarb: this pci device is not a vga device
  [6.409112] vgaarb: this pci device is not a vga device
  [   68.506178] vgaarb: this pci device is not a vga device
  [   68.615945] vgaarb: this pci device is not a vga device

  $ lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 
(rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 
01)
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 
620M/625M/630M/720M] (rev a1)

  Dell Latitude E5540

  SMBIOS 2.7 present.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: A11
Release Date: 02/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 14336 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25/1.2 MB floppy services are supported (int 13h)
3.5/720 kB floppy services are supported (int 13h)
3.5/2.88 MB 

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

[Tomek]

apport information

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

Title:
  Random screen locking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random screen locking happens about once an hour. Mouse is not
  responding, keyboard is, but GUI does not respond. To overcome the
  problem I have to switch to terminal with ctrl+alt+1 and go back. In
  dmesg I can see:

  [   68.509976] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510021] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510044] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510064] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510083] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510102] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510134] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510154] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510644] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.615945] vgaarb: this pci device is not a vga device

  $ dmesg | grep vgaarb
  [0.524324] vgaarb: setting as boot device: PCI::00:02.0
  [0.524325] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [0.524328] vgaarb: loaded
  [0.524329] vgaarb: bridge control possible :00:02.0
  [1.498735] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [5.667900] vgaarb: this pci device is not a vga device
  [6.409112] vgaarb: this pci device is not a vga device
  [   68.506178] vgaarb: this pci device is not a vga device
  [   68.615945] vgaarb: this pci device is not a vga device

  $ lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 
(rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 
01)
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 
620M/625M/630M/720M] (rev a1)

  Dell Latitude E5540

  SMBIOS 2.7 present.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: A11
Release Date: 02/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 14336 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25/1.2 MB floppy services are supported (int 13h)
3.5/720 kB floppy services are supported (int 13h)
3.5/2.88 MB floppy 

[Kernel-packages] [Bug 1437913] Re: 8086:095b [Lenovo ThinkPad X250] Wifi unstable on vivid with Intel 7265

[Christopher M. Penalver]

** Tags added: needs-bisect

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

Title:
  8086:095b [Lenovo ThinkPad X250] Wifi unstable on vivid with Intel
  7265

Status in The Linux Kernel:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  After upgrading from utopic to vivid beta, wifi on the Intel 7265 on my 
Thinkpad X250 has become unstable (linux-image 3.19.0-10.10, linux-firmware 
1.143):
  03:00.0 Network controller [0280]: Intel Corporation Wireless 7265 
[8086:095b] (rev 59)
Subsystem: Intel Corporation Dual Band Wireless-AC 7265 [8086:5210]

  I'm seeing two primary problems:
   * On 5GHz 802.11ac, I'll get DEAUTH_LEAVING almost exactly every minute, 
followed by an immediate reconnect.
   * On both 2.4GHz and 5GHz, all network activity will cease after 10-20 
minutes.  A manual reconnect will temporarily fix network activity.

  This is complicated by the fact that the newer firmware requires
  kernel 3.19 and kernel 3.19 requires the iwlwifi-7265D*.ucode firmware
  instead of the old iwlwifi-7265*.ucode firmware, so it's not possible
  to mix/match older/newer kernel/firmware combinations, nor do a kernel
  bisect.

  FAOD, the latest utopic kernel/firmware combination (linux-image
  3.16.0-33.44, linux-firmware 1.138.1) works fine, which I can use in
  vivid if I manually install them.

  I have tested ~kernel-ppa/mainline 3.19.3-031903.201503261036 and
  4.0.0-04rc5.201503230035, which exhibit the same problems.

  WORKAROUND: iw reg set US

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-10-generic 3.19.0-10.10
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ryan   1862 F pulseaudio
   /dev/snd/controlC1:  ryan   1862 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Mar 29 11:42:13 2015
  HibernationDevice: RESUME=UUID=c21a0227-27e2-4c4f-8bd9-30793932acbc
  InstallationDate: Installed on 2015-03-07 (22 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: LENOVO 20CMCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro acpi_osi=Linux acpi_backlight=vendor 
psmouse.proto=imps quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-10-generic N/A
   linux-backports-modules-3.19.0-10-generic  N/A
   linux-firmware 1.143
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago)
  dmi.bios.date: 01/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET28W (1.05 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CMCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET28W(1.05):bd01/23/2015:svnLENOVO:pn20CMCTO1WW:pvrThinkPadX250:rvnLENOVO:rn20CMCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CMCTO1WW
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1460551] BootDmesg.txt

[Tomek]

apport information

** Attachment added: BootDmesg.txt
   
https://bugs.launchpad.net/bugs/1460551/+attachment/4408007/+files/BootDmesg.txt

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

Title:
  Random screen locking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random screen locking happens about once an hour. Mouse is not
  responding, keyboard is, but GUI does not respond. To overcome the
  problem I have to switch to terminal with ctrl+alt+1 and go back. In
  dmesg I can see:

  [   68.509976] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510021] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510044] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510064] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510083] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510102] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510134] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510154] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510644] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.615945] vgaarb: this pci device is not a vga device

  $ dmesg | grep vgaarb
  [0.524324] vgaarb: setting as boot device: PCI::00:02.0
  [0.524325] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [0.524328] vgaarb: loaded
  [0.524329] vgaarb: bridge control possible :00:02.0
  [1.498735] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [5.667900] vgaarb: this pci device is not a vga device
  [6.409112] vgaarb: this pci device is not a vga device
  [   68.506178] vgaarb: this pci device is not a vga device
  [   68.615945] vgaarb: this pci device is not a vga device

  $ lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 
(rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 
01)
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 
620M/625M/630M/720M] (rev a1)

  Dell Latitude E5540

  SMBIOS 2.7 present.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: A11
Release Date: 02/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 14336 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25/1.2 MB floppy services are supported (int 13h)
3.5/720 kB floppy services are supported (int 13h)
3.5/2.88 MB floppy 

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

[Tomek]

apport information

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

Title:
  Random screen locking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random screen locking happens about once an hour. Mouse is not
  responding, keyboard is, but GUI does not respond. To overcome the
  problem I have to switch to terminal with ctrl+alt+1 and go back. In
  dmesg I can see:

  [   68.509976] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510021] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510044] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510064] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510083] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510102] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510134] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510154] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510644] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.615945] vgaarb: this pci device is not a vga device

  $ dmesg | grep vgaarb
  [0.524324] vgaarb: setting as boot device: PCI::00:02.0
  [0.524325] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [0.524328] vgaarb: loaded
  [0.524329] vgaarb: bridge control possible :00:02.0
  [1.498735] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [5.667900] vgaarb: this pci device is not a vga device
  [6.409112] vgaarb: this pci device is not a vga device
  [   68.506178] vgaarb: this pci device is not a vga device
  [   68.615945] vgaarb: this pci device is not a vga device

  $ lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 
(rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 
01)
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 
620M/625M/630M/720M] (rev a1)

  Dell Latitude E5540

  SMBIOS 2.7 present.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: A11
Release Date: 02/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 14336 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25/1.2 MB floppy services are supported (int 13h)
3.5/720 kB floppy services are supported (int 13h)
3.5/2.88 MB floppy services 

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

[Tomek]

apport information

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

Title:
  Random screen locking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random screen locking happens about once an hour. Mouse is not
  responding, keyboard is, but GUI does not respond. To overcome the
  problem I have to switch to terminal with ctrl+alt+1 and go back. In
  dmesg I can see:

  [   68.509976] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510021] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510044] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510064] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510083] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510102] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510134] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510154] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510644] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.615945] vgaarb: this pci device is not a vga device

  $ dmesg | grep vgaarb
  [0.524324] vgaarb: setting as boot device: PCI::00:02.0
  [0.524325] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [0.524328] vgaarb: loaded
  [0.524329] vgaarb: bridge control possible :00:02.0
  [1.498735] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [5.667900] vgaarb: this pci device is not a vga device
  [6.409112] vgaarb: this pci device is not a vga device
  [   68.506178] vgaarb: this pci device is not a vga device
  [   68.615945] vgaarb: this pci device is not a vga device

  $ lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 
(rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 
01)
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 
620M/625M/630M/720M] (rev a1)

  Dell Latitude E5540

  SMBIOS 2.7 present.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: A11
Release Date: 02/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 14336 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25/1.2 MB floppy services are supported (int 13h)
3.5/720 kB floppy services are supported (int 13h)
3.5/2.88 MB floppy services 

[Kernel-packages] [Bug 1441852] Re: Audio broken on HP Spectre x360, broadwell-U audio controller

[Christopher M. Penalver]

Gabriel Lemieux, just click Hide at the bottom right of the comment.

** Changed in: linux (Ubuntu)
   Status: Confirmed = Triaged

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

Title:
  Audio broken on HP Spectre x360, broadwell-U audio controller

Status in The Linux Kernel:
  Unknown
Status in linux package in Ubuntu:
  Triaged

Bug description:
  On ubuntu trusty, Audio driver on HP Spectre x360 doesn't work.

  May be related to the bug found on the 2015 XPS 13.
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413446)

  On the kernel 4.0-rc4+ given as solution for the bug found on the XPS 13, the
  dmesg -t | egrep (audio|snd|INT3438) command return:

  dmar: ACPI device INT3438:00 under DMAR at fed91000 as 00:13.0
  snd_hda_intel :00:03.0: enabling device ( - 0002)
  sst-acpi INT3438:00: DesignWare DMA Controller, 8 channels
  haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: 
type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  broadwell-audio broadwell-audio: ASoC: CODEC DAI rt286-aif1 not registered
  ---
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  isatis 1479 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1e13c664-5747-48ed-942c-18c0610b50dd
  InstallationDate: Installed on 2015-04-01 (12 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  MachineType: Hewlett-Packard HP Spectre x360 Convertible 13
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic.efi.signed 
root=UUID=70117e8f-97a5-40f7-90fd-aa25fdba1bba ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-34.45~14.04.1-generic 3.16.7-ckt8
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-34-generic N/A
   linux-backports-modules-3.16.0-34-generic  N/A
   linux-firmware 1.127.11
  Tags:  trusty
  Uname: Linux 3.16.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/05/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 802D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 58.25
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.11:bd02/05/2015:svnHewlett-Packard:pnHPSpectrex360Convertible13:pvr:rvnHewlett-Packard:rn802D:rvr58.25:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Spectre x360 Convertible 13
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1448485] Re: kernel don't recognize laptop backlight fn keys

[Martin Bångens]

This bisection thing didn't work, I got many different compile errors from 
testing ubuntu-archive/quantal.git
I'v read the documentation 20 times carefully, and it's still not clear. 
I'm so frustrated, fuck it! wasting my time

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

Title:
  kernel don't recognize laptop backlight fn keys

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 15.04 and fn+f7 and fn+f8 use to lower and higher the 
brightness of the screen.
  In slackware using kernel 3.14.33 those keys works and give output from 
acpi_listen.
  In kernel 3.16 to 4.0 those keys don't work and acpi_listen outputs nothing.

  I expected fn+f7 and fn+f8 to work

  https://bugzilla.kernel.org/show_bug.cgi?id=60670
  This bug my be related

  This is my first bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15 [modified: 
boot/vmlinuz-3.19.0-15-generic]
  ProcVersionSignature: Ubuntu 3.19.0-15.15-lowlatency 3.19.3
  Uname: Linux 3.19.0-15-lowlatency x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marbangens   1334 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 25 17:04:30 2015
  HibernationDevice: RESUME=UUID=22f95b90-3ec0-4b6d-9e76-13042dc0a290
  InstallationDate: Installed on 2015-04-23 (1 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  MachineType: Hewlett-Packard Compaq Presario CQ60 Notebook PC
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-lowlatency 
root=UUID=d4f39d6b-137e-4248-81cb-ce920cdee909 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-lowlatency N/A
   linux-backports-modules-3.19.0-15-lowlatency  N/A
   linux-firmware1.143
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Filen eller katalogen finns inte: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.54
  dmi.board.name: 303C
  dmi.board.vendor: Wistron
  dmi.board.version: 08.60
  dmi.chassis.type: 10
  dmi.chassis.vendor: Wistron
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.54:bd08/18/2009:svnHewlett-Packard:pnCompaqPresarioCQ60NotebookPC:pvrF.54:rvnWistron:rn303C:rvr08.60:cvnWistron:ct10:cvrN/A:
  dmi.product.name: Compaq Presario CQ60 Notebook PC
  dmi.product.version: F.54
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1458208] Re: AR8161 ethernet stopped working after upgrade from 3.19.0-16 to 3.19.0-18

[Christopher M. Penalver]

Mark Sapiro, then it appears you have a downstream patch that is causing
this issue. Hence, let us mark this Triaged for now.

** Tags removed: kernel-fixed-upstream-3.19.8

** Changed in: linux (Ubuntu)
   Status: Confirmed = Triaged

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

Title:
  AR8161 ethernet stopped working after upgrade from 3.19.0-16 to
  3.19.0-18

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Partial lshw output:

*-network
 description: Ethernet interface
 product: AR8161 Gigabit Ethernet
 vendor: Qualcomm Atheros
 physical id: 0
 bus info: pci@:04:00.0
 logical name: eth0
 version: 08
 serial: 70:54:d2:97:05:11
 size: 1Gbit/s
 capacity: 1Gbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi msix bus_master cap_list ethernet 
physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=alx duplex=full 
latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
 resources: irq:30 memory:f710-f713 ioport:d000(size=128)

  Partial ifconfig output:
  eth0  Link encap:Ethernet  HWaddr 70:54:d2:97:05:11  
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:1276 errors:609 dropped:0 overruns:609 frame:0
TX packets:1215 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000 
RX bytes:230131 (230.1 KB)  TX bytes:142978 (142.9 KB)
Interrupt:17 

  The ethernet adapter stopped working on upgrade from linux
  3.19.0-16-generic to 3.19.0-18-generic. Upon inital system start, I
  can successfully ping a remote server, but once I try any TCP
  connection, even ping fails.

  If I fallback to 3.19.0-16, everything is working OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-18-generic 3.19.0-18.18
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  mark   2611 F pulseaudio
   /dev/snd/controlC1:  mark   2611 F pulseaudio
   /dev/snd/controlC0:  mark   2611 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat May 23 10:21:44 2015
  HibernationDevice: RESUME=UUID=b4733b71-2c28-4a85-8450-6f330135cfe4
  InstallationDate: Installed on 2013-04-24 (758 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 
(20130213)
  MachineType: Hewlett-Packard h8-1360t
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic 
root=UUID=578349d7-ca6f-4750-b977-7674ad95c763 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-05-20 (3 days ago)
  dmi.bios.date: 07/02/2012
  dmi.bios.vendor: AMI
  dmi.bios.version: 7.15
  dmi.board.name: 2AD5
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.03
  dmi.chassis.asset.tag: 2MD3140FD9
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAMI:bvr7.15:bd07/02/2012:svnHewlett-Packard:pnh8-1360t:pvr1.00:rvnPEGATRONCORPORATION:rn2AD5:rvr1.03:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: h8-1360t
  dmi.product.version: 1.00
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1460365] Re: 3.19 kernels in 15.04 do not work on my 32bit system

[Christopher M. Penalver]

Bryan Cebuliak, just to clarify, if you updated your BIOS and a problem
went away, then the bug was in the BIOS, not the kernel. Despite this,
this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1460365/comments/35
regarding this being fixed with a BIOS update. For future reference you
can manage the status of your own bugs by clicking on the current status
in the yellow line and then choosing a new status in the revealed drop
down box. You can learn more about bug statuses at
https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time
to report this bug and helping to make Ubuntu better. Please submit any
future bugs you may find.

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

Title:
  3.19 kernels in 15.04 do not work  on my  32bit system

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Since  upgrading from 14.10  [3.16 kernel]  to 15.04 the 3.19 kernels  
including 3.19.0-20 will   either  stall   on  bootor   leave   me   
without   proper   graphics or nil  keyboard  and  mouse even  on recovery boot 
.  The  next functioning mainline kernel is  v4.0-rc1-vivid. No  problem there. 
 I  suggest you  abandon  completely  this very problematic end of life   
kernel and   quickly test and  backport a newer series.  3.19 up to 3.19.7 has 
also given me similar   grief on my old  Macbook 2,1 64bit.
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: i386
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 15.04
  InstallationDate: Installed on 2012-09-04 (998 days ago)
  InstallationMedia: Lubuntu 12.04 Precise Pangolin - Release i386 (20120423)
  Package: linux (not installed)
  Tags:  vivid
  Uname: Linux 4.0.0-04rc1-generic i686
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to vivid on 2015-05-31 (0 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse lp lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  elaine 1316 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=cf1e0e2c-e614-46b7-af16-815ef38b4dfc
  InstallationDate: Installed on 2012-09-04 (998 days ago)
  InstallationMedia: Lubuntu 12.04 Precise Pangolin - Release i386 (20120423)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: HP-Pavilion FT958AA-ABG a6710a
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic 
root=UUID=3a08a446-f1f6-42a5-ba42-c00b38ccfac0 ro
  ProcVersionSignature: Ubuntu 3.16.0-38.52-generic 3.16.7-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-38-generic N/A
   linux-backports-modules-3.16.0-38-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   
  Tags:  vivid
  Uname: Linux 3.16.0-38-generic i686
  UpgradeStatus: Upgraded to vivid on 2015-05-31 (0 days ago)
  UserGroups: adm cdrom dialout dip fax floppy fuse lp lpadmin plugdev 
sambashare sudo tape video
  _MarkForUpload: True
  dmi.bios.date: 11/10/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.16
  dmi.board.name: Boston
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.16:bd11/10/2008:svnHP-Pavilion:pnFT958AA-ABGa6710a:pvr:rvnMSI:rnBoston:rvr1.0:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: FT958AA-ABG a6710a
  dmi.sys.vendor: HP-Pavilion
  --- 
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  elaine 1316 F pulseaudio
  CurrentDesktop: LXDE
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=cf1e0e2c-e614-46b7-af16-815ef38b4dfc
  InstallationDate: Installed on 2012-09-04 (998 days ago)
  InstallationMedia: Lubuntu 12.04 Precise Pangolin - Release i386 (20120423)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: HP-Pavilion FT958AA-ABG a6710a
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-38-generic 
root=UUID=3a08a446-f1f6-42a5-ba42-c00b38ccfac0 ro
  ProcVersionSignature: Ubuntu 3.16.0-38.52-generic 3.16.7-ckt10
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-38-generic N/A
   linux-backports-modules-3.16.0-38-generic  N/A
   linux-firmware 1.143.1
  RfKill:
   
  Tags:  vivid
  Uname: Linux 3.16.0-38-generic i686
  UpgradeStatus: Upgraded to vivid on 2015-05-31 (0 

[Kernel-packages] [Bug 1459367] Re: Realtek RTL8723BE wireless card drops connection in Linux kernel 3.19.0-18

[Arnaud LE CAM]

Here it is :

Module = rtl8723be

  Attributes:
coresize= 98304
initsize= 0
initstate   = live
refcnt  = 0
srcversion  = 35F1A640DD23340CE249D81
taint   = 
uevent  = store method only

  Parameters:
debug   = 0
disable_watchdog= N
fwlps   = Y
ips = Y
swenc   = N
swlps   = N

  Sections:
.bss= 0x
.data   = 0x
.exit.text  = 0x
.gnu.linkonce.this_module= 0x
.init.text  = 0x
.note.gnu.build-id  = 0x
.parainstructions   = 0x
.rodata = 0x
.rodata.str1.1  = 0x
.rodata.str1.8  = 0x
.strtab = 0x
.symtab = 0x
.text   = 0x
__mcount_loc= 0x
__param = 0x

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

Title:
  Realtek RTL8723BE wireless card drops connection in Linux kernel
  3.19.0-18

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  I loose my connection randomly (HP laptop, model 15-r207nf) with Realtek 
RTL8723BE wireless card.
  Linux 3.19.0-18-generic on Xubuntu 15.04

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-18-generic 3.19.0-18.18
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   arnaud 1415 F...m pulseaudio
   /dev/snd/controlC0:  arnaud 1409 F panel-17-mixer
arnaud 1415 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed May 27 19:46:19 2015
  HibernationDevice: RESUME=UUID=677c116e-29ca-4442-a248-9302170fbb6b
  InstallationDate: Installed on 2015-04-18 (38 days ago)
  InstallationMedia: Xubuntu 15.04 Vivid Vervet - Beta amd64 (20150326)
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed 
root=UUID=3c2695c5-1341-4096-966f-ad24d315f451 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware 1.143.1
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.32
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2213
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.47
  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.32:bd10/28/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr097412405F0620180:rvnHewlett-Packard:rn2213:rvr57.47:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 097412405F0620180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1456123] Re: [i915_bpo] Update driver code to 4.1-rc4 + backported fixes

[Timo Aaltonen]

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

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

Title:
  [i915_bpo] Update driver code to 4.1-rc4 + backported fixes

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  Pull changes from 4.1-rc4, and add further backports for CHV  SKL.

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

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

[Kernel-packages] [Bug 1452547] Re: Report cpu frequency throttling

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-vivid

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

Title:
  Report cpu frequency throttling

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  [Impact]

  == Comment: #0 - Shilpasri G. Bhat shigb...@in.ibm.com - 2015-05-06 
07:24:11 ==
  The user can see a drop in performance when frequency is throttled and
  is unaware of throttling. So detect and report such a condition, so
  the user can check the OCC status to reboot the system or check for
  power supply or fan failures.

  The cpu frequency can be throttled by OCC for the following reasons:
  1)If a processor crosses its power and temperature limit then OCC will
  lower its Pmax to reduce the frequency and voltage.
  2)If OCC crashes then the system is forced to Psafe frequency.
  3)If OCC fails to recover then the kernel is not allowed to do any
   further frequency changes and the chip will remain in Psafe.

  
  [Test Case]
  Get into a state where hardware OCC throttles CPU frequency.
  Ensure kernel log shows cpufreq throttling messages.

  
  [Fix]

  This bug is fixed upstream 09a972d1620934142d30cfda455ffe429af751c4

  ---uname output---
  3.19.0-15

  Machine Type = llmtul02b.in.ibm.com

  Contact Information = Shilpasri G Bhat /
  shilpa.b...@linux.vnet.ibm.com

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

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

[Kernel-packages] [Bug 1454013] Re: Booting takes very long time on Intel Braswell caused by eMMC

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-utopic

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

Title:
  Booting takes very long time on Intel Braswell caused by eMMC

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Released

Bug description:
  This patch could fix this issue, otherwise booting will take very long
  time.

  
  4e93b9a6abc0d028daf3c8a00cb77b679d8a4df4
  mmc: card: Don't access RPMB partitions for normal read/write
  During kernel boot, it will try to read some logical sectors
  of each block device node for the possible partition table.

  But since RPMB partition is special and can not be accessed
  by normal eMMC read / write CMDs, it will cause below error
  messages during kernel boot:
  ...
   mmc0: Got data interrupt 0x0002 even though no data operation was in 
progress.
   mmcblk0rpmb: error -110 transferring data, sector 0, nr 32, cmd response 
0x900, card status 0xb00
   mmcblk0rpmb: retrying using single block read
   mmcblk0rpmb: timed out sending r/w cmd command, card status 0x400900
   mmcblk0rpmb: timed out sending r/w cmd command, card status 0x400900
   mmcblk0rpmb: timed out sending r/w cmd command, card status 0x400900
   mmcblk0rpmb: timed out sending r/w cmd command, card status 0x400900
   mmcblk0rpmb: timed out sending r/w cmd command, card status 0x400900
   mmcblk0rpmb: timed out sending r/w cmd command, card status 0x400900
   end_request: I/O error, dev mmcblk0rpmb, sector 0
   Buffer I/O error on device mmcblk0rpmb, logical block 0
   end_request: I/O error, dev mmcblk0rpmb, sector 8
   Buffer I/O error on device mmcblk0rpmb, logical block 1
   end_request: I/O error, dev mmcblk0rpmb, sector 16
   Buffer I/O error on device mmcblk0rpmb, logical block 2
   end_request: I/O error, dev mmcblk0rpmb, sector 24
   Buffer I/O error on device mmcblk0rpmb, logical block 3
  ...

  This patch will discard the access request in eMMC queue if
  it is RPMB partition access request. By this way, it avoids
  trigger above error messages.

  Fixes: 090d25fe224c (mmc: core: Expose access to RPMB partition)
  Signed-off-by: Yunpeng Gao yunpeng@intel.com
  Signed-off-by: Chuanxiao Dong chuanxiao.d...@intel.com
  Tested-by: Michael Shigorin m...@altlinux.org
  Signed-off-by: Ulf Hansson ulf.hans...@linaro.org

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

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

[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-utopic

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

Title:
  Some touchpads' right button doesn't work under I2C mode, need support
  of clickpads

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  We need to add this support, otherwise some touchpads' right button
  doesn't work under I2C mode.

  commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch)
  HID: multitouch: add support of clickpads
  Touchpads that have only one button are called clickpads and should
  be advertised as such by the kernel.

  Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com
  Tested-by: Jason Ekstrand ja...@jlekstrand.net
  Signed-off-by: Jiri Kosina jkos...@suse.cz

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

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

[Kernel-packages] [Bug 1446517] Re: num_steps = 0 error on ALC256

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-vivid

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

Title:
  num_steps = 0 error on ALC256

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  This bug is used for tracking, please do not triage.

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

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

[Kernel-packages] [Bug 1450584] Re: mono occassionally crashes since kernel 3.13.0-48 on multi-cpu vm

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!

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

Title:
  mono occassionally crashes since kernel 3.13.0-48 on multi-cpu vm

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  The addition of the commit:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=11f4e0339c8dc8d760483258efd9f15b4c6dcda2

  Causes SIGSEGVs when running certain workloads on multi-cpu VMs.

  [Test Case]

  Mono test case here that causes the SIGSEGV
  https://bugzilla.xamarin.com/show_bug.cgi?id=29212

  [Fix]

  These two commits are required for fixing this issue:
  
https://github.com/torvalds/linux/commit/80f7fdb1c7f0f9266421f823964fd1962681f6ce
  
https://github.com/torvalds/linux/commit/0a4e6be9ca17c54817cf814b4b5aa60478c6df27

  --

  Gradually since late March more and more users started to complain
  about frequent SIGSEGV crashes in our .net/mono application. Early
  April I started to investigate it actively.

  After eliminating possible native libraries, and testing various mono
  versions I discovered the crashes would occur more frequently on a
  vbox vm with multiple cpus configured. And discovered that the mono
  bug-18026.cs testcase would fairly consistently crash. At that point
  it was reported to the mono bug tracker.

  I finally got a break when we found a correlation with the kernel version. 
3.13.0-46 didn't crash while 3.13.0-48,49 did.
  More and more users upgrade to these newer kernel versions and start running 
into issues, which explains the gradual increase in reports.

  Early this week I performed a full git bisect on the kernel between 3.13.0-46 
and -48 and isolated the commit that seems to trigger the crashes.
  Namely 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=11f4e0339c8dc8d760483258efd9f15b4c6dcda2

  At this point I don't know if the commit messed up something, or that mono 
simply handles it incorrectly. However, a few commits for linux 4.x seem to fix 
it:
  
https://github.com/torvalds/linux/commit/80f7fdb1c7f0f9266421f823964fd1962681f6ce
  
https://github.com/torvalds/linux/commit/0a4e6be9ca17c54817cf814b4b5aa60478c6df27
  I applied these commits myself on top of commit 11f4e033, compiled and ran 
the testcase... didn't crash in the 200x test runs I did.
  Although I don't know if those two patches have unknown side-effects.
  I'm not an expert on the kernel, not even remotely. But I thought it would be 
nice to be able to point at a possible solution.

  My current test vm is a virtualbox vm 64bit installed using the 14.04.2 
server iso running on an older i7 quad core Windows 7 64bit host.
  In the vm I've tested numerous mono and kernel combinations. Last test was 
with kernel 3.16.0-36 and 3.13.0-51 and mono 4.0.1, in which the problem still 
occurs.

  By now I've debugged the app using gdb several dozen times on various
  user setups, compiled mono half a dozen times, and then the 8x3h
  compile kernel bisect :) Speaking of down the rabbit-hole...

  So I'm pretty desperate for some expert to help me out here. :D

  Reference to mono bug report:
  https://bugzilla.xamarin.com/show_bug.cgi?id=29212

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-51-generic 3.13.0-51.84
  ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-51-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 30 18:53 seq
   crw-rw 1 root audio 116, 33 Apr 30 18:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.10
  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: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDmesg: [9.379188] init: plymouth-upstart-bridge main process 
ended, respawning
  Date: Thu Apr 30 19:45:43 2015
  HibernationDevice: RESUME=UUID=b35ef328-166d-4476-a418-e7e80d22cb30
  InstallationDate: Installed on 2015-04-22 (7 days ago)
  InstallationMedia: Ubuntu-Server 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  IwConfig:
   

[Kernel-packages] [Bug 1444179] Re: add hid drivers to virtual kernel

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

Title:
  add hid drivers to virtual kernel

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  Please move hid_hyperv and hyperv_fb to the -virtual kernel. Microsoft
  reports that these drivers are needed for connecting to Azure VM's
  using the Hyper-V manager.

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

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

[Kernel-packages] [Bug 1450497] Re: Enable CONFIG_VIRT_CPU_ACCOUNTING_NATIVE for ppc64el

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-utopic

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

Title:
  Enable CONFIG_VIRT_CPU_ACCOUNTING_NATIVE for ppc64el

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  [Impact]
  I would like to ask to set  CONFIG_VIRT_CPU_ACCOUNTING_NATIVE=y on ppc64el 
kernel config in 3.16 kernel (14.10 and/or 14.04.2) to provide %steal number 
properly reported.

  Historically, it was enabled, became disabled and later enabled again:

  Ubuntu 14.04:
  # cat /boot/config-3.13.0-24-generic | grep VIRT_CPU
  CONFIG_VIRT_CPU_ACCOUNTING_NATIVE=y

  Ubuntu 14.10:
  # cat /boot/config-3.16.0-23-generic | grep VIRT_CPU
  # CONFIG_VIRT_CPU_ACCOUNTING_NATIVE is not set

  Ubuntu 15.04:
  # cat /boot/config-3.19.0-12-generic | grep VIRT_CPU
  CONFIG_VIRT_CPU_ACCOUNTING_NATIVE=y

  [Test Case]
  Run VM and ensure %steal is reported properly.

  [Fix]
  CONFIG_VIRT_CPU_ACCOUNTING_NATIVE=y in config.

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

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

[Kernel-packages] [Bug 1452628] Re: beaglebone: random MAC on boot

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

Title:
  beaglebone: random MAC on boot

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: after every reboot, the nic on the beaglebone gets a
  completely different MAC address.

  Fix: Apply the patches, recompile and reboot.

  Testcase: Try booting two times in a row with and without the
  patches applied and check if the MAC address of eth0 changes or not.

  With this series applied:

  ...
  [2.847766] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
  [2.854144] davinci_mdio 4a101000.mdio: detected phy mask fffe
  [2.866722] libphy: 4a101000.mdio: probed
  [2.871020] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, 
driver SMSC LAN8710/LAN8720
  [2.886827] Detected MACID = 90:59:af:5a:b6:ca
  ...

  and it won't change anymore.
  ---

  On the beaglebone, the NIC keeps getting a random MAC after every
  reboot, making it impossible to associate a static ip with the board:

  ...
  [2.839176] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
  [2.845579] davinci_mdio 4a101000.mdio: detected phy mask fffe
  [2.858195] libphy: 4a101000.mdio: probed
  [2.862510] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, 
driver SMSC LAN8710/LAN8720
  [2.872364] cpu cpu0: cpu0 regulator not ready, retry
  [2.878372] Random MACID = ee:7a:fa:cd:13:39
  ...

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

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

[Kernel-packages] [Bug 1456881] Re: Some touchpads' right button doesn't work under I2C mode, need support of clickpads

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

Title:
  Some touchpads' right button doesn't work under I2C mode, need support
  of clickpads

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  We need to add this support, otherwise some touchpads' right button
  doesn't work under I2C mode.

  commit015fdaa9f8edd89a456b3331088e1b77ebdad9d0 (patch)
  HID: multitouch: add support of clickpads
  Touchpads that have only one button are called clickpads and should
  be advertised as such by the kernel.

  Signed-off-by: Benjamin Tissoires benjamin.tissoi...@redhat.com
  Tested-by: Jason Ekstrand ja...@jlekstrand.net
  Signed-off-by: Jiri Kosina jkos...@suse.cz

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

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

[Kernel-packages] [Bug 1457369] Re: kernel 3.19.0-18 breaks HDMI audio for snd_hda_intel

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-vivid

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

Title:
  kernel 3.19.0-18 breaks HDMI audio for snd_hda_intel

Status in System76:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  Problem appears on multiple computers with exact same kernel update, so 
clearly the problem is within the kernel. 3.19.0-16 did work without any 
problems.
  Before sound worked great via HDMI, now the HDMI output is not visible in 
neither alsamixer nor pulseaudio. Audio via the headphone jack still works.
  The computers are Intel-NUC-Kit-D54250WYK:
  00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT 
Integrated Graphics Controller [8086:0a26] (rev 09)
Subsystem: Intel Corporation Device [8086:2054]
Kernel driver in use: i915
  00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio 
Controller [8086:0a0c] (rev 09)
Subsystem: Intel Corporation Device [8086:2054]
Kernel driver in use: snd_hda_inte

  dmesg gives:
  [3.178745] sound hdaudioC1D0: autoconfig: line_outs=1 
(0x21/0x0/0x0/0x0/0x0) type:hp
  [3.178750] sound hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
  [3.178753] sound hdaudioC1D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0)
  [3.178754] sound hdaudioC1D0:mono: mono_out=0x0
  [3.178756] sound hdaudioC1D0:inputs:
  [3.178759] sound hdaudioC1D0:  Mic=0x19
  ...
  [3.215371] snd_hda_intel :00:03.0: Cannot turn on display power on 
i915
  ...
  [3.297561] [drm] Initialized i915 1.6.0 20141121 for :00:02.0 on 
minor 0
  ...
  [3.304357] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.304360] i915 :00:02.0: registered panic notifier
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  maarten1669 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  Lsusb:
   Bus 001 Device 008: ID 8087:07dc Intel Corp. 
   Bus 001 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic 
root=UUID=6c65d9ee-31fe-4832-8907-f47ac02d6f83 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware 1.143.1
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: WYLPT10H.86A.0038.2015.0410.1634
  dmi.board.name: D54250WYK
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H13922-302
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrWYLPT10H.86A.0038.2015.0410.1634:bd04/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD54250WYK:rvrH13922-302:cvn:ct3:cvr:
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  maarten1669 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  Lsusb:
   Bus 001 Device 008: ID 8087:07dc Intel Corp. 
   Bus 001 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic 
root=UUID=6c65d9ee-31fe-4832-8907-f47ac02d6f83 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware 1.143.1
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  

[Kernel-packages] [Bug 1457369] Re: kernel 3.19.0-18 breaks HDMI audio for snd_hda_intel

[Maarten Fonville]

The package in proposed does indeed resolve the problem! :-)

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

Title:
  kernel 3.19.0-18 breaks HDMI audio for snd_hda_intel

Status in System76:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  Problem appears on multiple computers with exact same kernel update, so 
clearly the problem is within the kernel. 3.19.0-16 did work without any 
problems.
  Before sound worked great via HDMI, now the HDMI output is not visible in 
neither alsamixer nor pulseaudio. Audio via the headphone jack still works.
  The computers are Intel-NUC-Kit-D54250WYK:
  00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT 
Integrated Graphics Controller [8086:0a26] (rev 09)
Subsystem: Intel Corporation Device [8086:2054]
Kernel driver in use: i915
  00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio 
Controller [8086:0a0c] (rev 09)
Subsystem: Intel Corporation Device [8086:2054]
Kernel driver in use: snd_hda_inte

  dmesg gives:
  [3.178745] sound hdaudioC1D0: autoconfig: line_outs=1 
(0x21/0x0/0x0/0x0/0x0) type:hp
  [3.178750] sound hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
  [3.178753] sound hdaudioC1D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0)
  [3.178754] sound hdaudioC1D0:mono: mono_out=0x0
  [3.178756] sound hdaudioC1D0:inputs:
  [3.178759] sound hdaudioC1D0:  Mic=0x19
  ...
  [3.215371] snd_hda_intel :00:03.0: Cannot turn on display power on 
i915
  ...
  [3.297561] [drm] Initialized i915 1.6.0 20141121 for :00:02.0 on 
minor 0
  ...
  [3.304357] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.304360] i915 :00:02.0: registered panic notifier
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  maarten1669 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  Lsusb:
   Bus 001 Device 008: ID 8087:07dc Intel Corp. 
   Bus 001 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic 
root=UUID=6c65d9ee-31fe-4832-8907-f47ac02d6f83 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware 1.143.1
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: WYLPT10H.86A.0038.2015.0410.1634
  dmi.board.name: D54250WYK
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H13922-302
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrWYLPT10H.86A.0038.2015.0410.1634:bd04/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD54250WYK:rvrH13922-302:cvn:ct3:cvr:
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  maarten1669 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  Lsusb:
   Bus 001 Device 008: ID 8087:07dc Intel Corp. 
   Bus 001 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic 
root=UUID=6c65d9ee-31fe-4832-8907-f47ac02d6f83 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware 1.143.1
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: WYLPT10H.86A.0038.2015.0410.1634
  dmi.board.name: D54250WYK
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H13922-302
  dmi.chassis.type: 3
  dmi.modalias: 

[Kernel-packages] [Bug 1444766] Re: Wifi connection issues

[Marvin Scholz]

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

** This bug has been marked a duplicate of bug 1437913
   8086:095b [Lenovo ThinkPad X250] Wifi unstable on vivid with Intel 7265

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

Title:
  Wifi connection issues

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1) Ubuntu Version: 15.04 (Vivid Vervet)
  2) Kernel Version: 3.19.0-12-generic

  Wireless: Intel Wireless 7265 (on Thinkpad X250)

  3) I expect Wifi to work as expected without connection drops.

  4) I am experiencing sudden connection drops, which means I am not
  able to connect to anything after a certain time and it seems that it
  only happens after certain amount of data has be downloaded. Although
  the Wifi still appears as connected, it behaves like it isn't.

  Other:
  When I am booting with Kernel 3.16.0-23-generic I do not experience any Wifi 
connection problems at all.

  (I am not sure if this bugreport is fine, as this is the first time I am 
reporting a bug here, I will be happy to do improvements to the report if I did 
anything wrong or provide as much data as possible upon request.)
  --- 
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  epirat 1708 F pulseaudio
   /dev/snd/controlC0:  epirat 1708 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-04-09 (6 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: LENOVO 20CLS0JA00
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic 
root=UUID=28d14754-0ce2-45a9-a1aa-068caaab54d0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-12-generic N/A
   linux-backports-modules-3.19.0-12-generic  N/A
   linux-firmware 1.143
  Tags:  vivid
  Uname: Linux 3.19.0-12-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-04-09 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N10ET28W (1.05 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CLS0JA00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN10ET28W(1.05):bd01/23/2015:svnLENOVO:pn20CLS0JA00:pvrThinkPadX250:rvnLENOVO:rn20CLS0JA00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20CLS0JA00
  dmi.product.version: ThinkPad X250
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1460551] Re: Random screen locking

[Christopher M. Penalver]

Tomek, thank you for reporting this and helping make Ubuntu better. Please 
execute the following command, as it will automatically gather debugging 
information, in a terminal:
apport-collect 1460551

** Package changed: linux-lts-utopic (Ubuntu) = linux (Ubuntu)

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

** Changed in: linux (Ubuntu)
   Status: New = Incomplete

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

Title:
  Random screen locking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Random screen locking happens about once an hour. Mouse is not
  responding, keyboard is, but GUI does not respond. To overcome the
  problem I have to switch to terminal with ctrl+alt+1 and go back. In
  dmesg I can see:

  [   68.509976] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510021] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510044] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510064] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510083] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510102] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510134] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510154] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.510644] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [   68.615945] vgaarb: this pci device is not a vga device

  $ dmesg | grep vgaarb
  [0.524324] vgaarb: setting as boot device: PCI::00:02.0
  [0.524325] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
  [0.524328] vgaarb: loaded
  [0.524329] vgaarb: bridge control possible :00:02.0
  [1.498735] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [5.667900] vgaarb: this pci device is not a vga device
  [6.409112] vgaarb: this pci device is not a vga device
  [   68.506178] vgaarb: this pci device is not a vga device
  [   68.615945] vgaarb: this pci device is not a vga device

  $ lspci
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 
(rev 04)
  00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM 
(rev 04)
  00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller 
(rev 04)
  00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
  00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
  00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 
(rev e4)
  00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
  00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
  00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
  01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 
01)
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
  03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 
620M/625M/630M/720M] (rev a1)

  Dell Latitude E5540

  SMBIOS 2.7 present.

  Handle 0x, DMI type 0, 24 bytes
  BIOS Information
Vendor: Dell Inc.
Version: A11
Release Date: 02/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 14336 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
 

[Kernel-packages] [Bug 1393079] Re: [Acer Aspire E5-571G] Touchpad not working after suspend/resume

[Christopher M. Penalver]

svenmeier, it will help immensely if you filed a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

** Summary changed:

- Touchpad not working after suspend/resume
+ [Acer Aspire E5-571G] Touchpad not working after suspend/resume

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

Title:
  [Acer Aspire E5-571G] Touchpad not working after suspend/resume

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu 14.10 on an Acer Laptop, model: Aspire E5-571G-941Y
  $ uname -a
  Linux Acer-Aspire-E5-571G 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 
13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

  Every time I suspend, the trackpad no longer works when resuming.

  I see several other people have the same issue with the same laptop here:
  http://ubuntuforums.org/showthread.php?t=2250002
  (some people say it's a 14.10 specific problem)

  I realize this report is very poor but please don't hesitate to request data 
/ clarifications from me, I'll be happy to help.
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bod3942 F pulseaudio
   /dev/snd/controlC1:  bod3942 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=2e6e7d72-637c-4b16-8cda-0471dfb711d4
  InstallationDate: Installed on 2014-11-14 (15 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Acer Aspire E5-571G
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed 
root=UUID=94aa9203-873c-4dff-8207-4e6b33a6a3e7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-25-generic N/A
   linux-backports-modules-3.16.0-25-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-25-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-11-14 (15 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/06/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_HB
  dmi.board.vendor: Acer
  dmi.board.version: V1.04
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571G:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-571G
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1460551] [NEW] Random screen locking

[Tomek]

Public bug reported:

Random screen locking happens about once an hour. Mouse is not
responding, keyboard is, but GUI does not respond. To overcome the
problem I have to switch to terminal with ctrl+alt+1 and go back. In
dmesg I can see:

[   68.509976] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
[   68.510021] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
[   68.510044] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
[   68.510064] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
[   68.510083] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
[   68.510102] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
[   68.510134] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
[   68.510154] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
[   68.510644] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
[   68.615945] vgaarb: this pci device is not a vga device

$ dmesg | grep vgaarb
[0.524324] vgaarb: setting as boot device: PCI::00:02.0
[0.524325] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none
[0.524328] vgaarb: loaded
[0.524329] vgaarb: bridge control possible :00:02.0
[1.498735] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[5.667900] vgaarb: this pci device is not a vga device
[6.409112] vgaarb: this pci device is not a vga device
[   68.506178] vgaarb: this pci device is not a vga device
[   68.615945] vgaarb: this pci device is not a vga device

$ lspci
00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b)
00:14.0 USB controller: Intel Corporation Lynx Point-LP USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation Lynx Point-LP HECI #0 (rev 
04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM (rev 
04)
00:1b.0 Audio device: Intel Corporation Lynx Point-LP HD Audio Controller (rev 
04)
00:1c.0 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 1 
(rev e4)
00:1c.3 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 4 
(rev e4)
00:1c.4 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 5 
(rev e4)
00:1c.5 PCI bridge: Intel Corporation Lynx Point-LP PCI Express Root Port 6 
(rev e4)
00:1d.0 USB controller: Intel Corporation Lynx Point-LP USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Lynx Point-LP LPC Controller (rev 04)
00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller 
[RAID mode] (rev 04)
00:1f.3 SMBus: Intel Corporation Lynx Point-LP SMBus Controller (rev 04)
01:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 
01)
02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73)
03:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/820M / GT 
620M/625M/630M/720M] (rev a1)

Dell Latitude E5540

SMBIOS 2.7 present.

Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version: A11
Release Date: 02/02/2015
Address: 0xF
Runtime Size: 64 kB
ROM Size: 14336 kB
Characteristics:
PCI is supported
PNP is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
5.25/1.2 MB floppy services are supported (int 13h)
3.5/720 kB floppy services are supported (int 13h)
3.5/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
Smart battery is supported
BIOS boot specification is supported
Function key-initiated 

[Kernel-packages] [Bug 1124250] Re: Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

[marz_cyclone]

Hi,

the prolem is still present with

dpkg -s linux-image-3.16.0-38-generic
Package: linux-image-3.16.0-38-generic
Status: install ok installed
Priority: optional
Section: kernel
Installed-Size: 43744
Maintainer: Ubuntu Kernel Team kernel-t...@lists.ubuntu.com
Architecture: amd64
Source: linux-lts-utopic
Version: 3.16.0-38.52~14.04.1

I would be happy contributing to fix the problem. Not using nfsv4 is not
a nice option.

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

Title:
  Partially incorrect uid mapping with nfs4/idmapd/ldap-auth

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in nfs-utils package in Debian:
  Fix Released
Status in Fedora:
  Unknown

Bug description:
  [Impact]

   * This bug is likely to cause an incorrect UID/GID mapping for NFS
  shares in case of large numbers of differend UIDs/GIDs or in case of
  expired UID/GID mappings (stored as keys in the kernel).

  [Test Case]

   1. Setup a nfs4 server exporting /home with a large number of different 
users and ldap-based authentication.
   2. Mount the share on a ldap-connected client machine.
   3. List the mounted /home directory.
   4. Wait more than 10 minutes (the default key expiration time) and list it 
again with ls -l.

  Expected result - all directories are listed with correct UIDs/GIDs.
  Actual result - some of the directories may be listed with incorrect UID/GID 
of 4294967294.

  [Regression Potential]

   * This issue has been merged upstream in the 3.18 kernel and is also
  present in Debian's 3.16 kernel.

  [Other Info]

  * Original bug description:

  I'm running a nfs4 server exporting a directory /home (ext4,usrquota). This 
server is running Ubuntu 12.04 amd64(up-to-date). This directory is handling 
662 homedirs for ldap authenticated users.
  /etc/exports is :
  /exports  192.168.0.0/24(rw,fsid=0,no_subtree_check)

  Important lines in /etc/idmapd.conf :
  domain=my-domain.org

  [Translation]
  Method=nsswitch.

  In /etc/default/nfs-common :
  NEED_IDMAPD=yes

  In /etc/default/nfs-kernel-server :
  RPCNFSDCOUNT=75
  RPCMOUNTDOPTS=--manage-gids

  2 Clients (rhel6 x86  Ubuntu 12.04.2 i686) are mounting this nfs4 exported 
directory with no problems :
  When doing ls -l /home on this clients, I have :
  ...
  drwx--   4 user100 oldusers 4096 sept. 21  2011 user100
  drwx--   4 user101 oldusers 4096 sept. 21  2011 user101
  drwx--  37 user102 oldusers 4096 oct.   1 19:06 user102
  drwx--  36 user103 users4096 févr. 5 21:08 user103
  drwx--  36 user104 users4096 févr. 8 14:03 user104
  drwx--  30 user105 users4096 févr. 4 18:01 user105
  drwx--  28 user106 oldusers 4096 oct.   5  2011 user106
  drwx--  37 user107 oldusers 4096 janv.  8 14:52 user107
  drwx--  31 user108 users4096 déc.  4 11:52 user108
  drwx--   4 user109 oldusers 4096 sept. 21  2011 user109
  drwx--x--x  45 user110 oldusers 4096 janv. 22 15:53 user109
  drwx--  31 user111 users4096 janv. 29 12:03 user110
  ...
  uid/gid mapping works fine, authldap works fine, ...

  All Clients running Ubuntu 12.10 i686  or  Ubuntu 12.10 amd64 are 
experiencing the same problem :
  The config files are the same that used in ubuntu 12.04.
  Auth ldap is correctly configured, user can log in.

  This is the /etc/fstab entry for /home :
  192.168.0.1:/ /home nfs  rw,nfsvers=4 0  0

  Important lines in /etc/idmapd.conf :
  domain=my-domain.org
  [Translation]
  Method=nsswitch

  In /etc/default/nfs-common :
  NEED_IDMAPD=yes

  /etc/nsswitch.conf is :
  passwd: files ldap
  group: files ldap
  shadow: files ldap

  When doing ls -l /home there is a strange problem :

  drwx--   4 4294967294 oldusers 4096 sept. 21  2011 user100
  drwx--   4 user101oldusers 4096 sept. 21  2011 user101
  drwx--  37 user102oldusers 4096 oct.   1 19:06 user102
  drwx--  36 4294967294 users4096 févr. 5 21:08 user103
  drwx--  36 4294967294 users4096 févr. 8 14:03 user104
  drwx--  30 4294967294 users4096 févr. 4 18:01 user105
  drwx--  28 4294967294 oldusers 4096 oct.   5  2011 user106
  drwx--  37 4294967294 oldusers 4096 janv.  8 14:52 user107
  drwx--  31 4294967294 users4096 déc.  4 11:52 user108
  drwx--   4 user109oldusers 4096 sept. 21  2011 user109
  drwx--x--x  45 4294967294 oldusers 4096 janv. 22 15:53 user110
  drwx--  31 4294967294 users4096 janv. 29 12:03 user111

  for  571 homedirs (this number varies at each reboot)/662, the owner is the 
value 4294967294. For the  91 remaining homedirs,
  the owner is correct. The gidnumber is correctly mapped for all (only  5 

[Kernel-packages] [Bug 1458999] Re: linux-ti-omap4: 3.2.0-1465.85 -proposed tracker

[John Johansen]

No CVEs

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress = Invalid

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

Title:
  linux-ti-omap4: 3.2.0-1465.85 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow package-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 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:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New

Bug description:
  This bug is for tracking the version to be filled 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, 26. May 2015 20:03 UTC
  kernel-stable-master-bug:1458901
  kernel-stable-Certification-testing-end:Friday, 29. May 2015 09:00 UTC
  kernel-stable-Prepare-package-end:Friday, 29. May 2015 12:01 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 29. May 2015 12:01 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 21:29 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 23:01 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 23:01 UTC
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 23:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 23:01 UTC

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

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

[Kernel-packages] [Bug 1438585] Re: no console when starting VM from cloud image

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

Title:
  no console when starting VM from cloud image

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Released
Status in linux source package in Vivid:
  Fix Released

Bug description:
  In current arm64 utopic cloud image, the 'console=' parameter has been
  removed from grub config, and always resort to 'stdout' DT property
  which is setup from QEMU.

  Unfortunately parsing 'stdout' DT property is just merged to 3.19
  kernel, so there is no console usable any more for arm64 utopic VM
  when booting via uefi/grub.

  SRU Justification:
  Impact: No console if arm64 Utopic based VM is booted from the cloud image.
  Fix: backport stdout enablement patches from 3.19. 5 of these 6 patches are 
cherry picked from 3.19 to Utopic, and the other one is backported by just 
dropping the dt self-test code, and with these 6 patches, arm64 utopic VM can 
be booted with console.
  Testcase: Boot one arm64 Utopic VM via uefi/grub.

  5ba2ee8 of: support passing console options with stdout-path
  5c64126 of: add optional options parameter to of_find_node_by_path()
  7507839 of: Add bindings for chosen node, stdout-path
  54e15d7 of: correct of_console_check()'s return value
  4f2b1f0 of: Enable console on serial ports specified by /chosen/stdout-path
  a699dfd of: Create of_console_check() for selecting a console specified in 
/chosen

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

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

[Kernel-packages] [Bug 1405807] Re: linux-lts-utopic-tools-common package is empty

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

Title:
  linux-lts-utopic-tools-common package is empty

Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Committed
Status in linux-lts-vivid source package in Trusty:
  Fix Committed

Bug description:
  Hi,

  I installed linux-lts-utopic-tools-common under Ubuntu 14.04.1 and
  hoped to find the same binaries in it as under Ubuntu utopic, but the
  package is empty.

  I guess, do_tools must be set to true somewhere, but I don't know
  exactly where.

  Under utopic, it looks like this:
  /.
  /usr
  /usr/share
  /usr/share/man
  /usr/share/man/man1
  /usr/share/man/man1/cpupower-frequency-set.1.gz
  /usr/share/man/man1/perf-inject.1.gz
  /usr/share/man/man1/cpupower-idle-info.1.gz
  /usr/share/man/man1/perf-buildid-cache.1.gz
  /usr/share/man/man1/perf-diff.1.gz
  /usr/share/man/man1/cpupower-monitor.1.gz
  /usr/share/man/man1/perf-mem.1.gz
  /usr/share/man/man1/cpupower-idle-set.1.gz
  /usr/share/man/man1/perf-report.1.gz
  /usr/share/man/man1/perf.1.gz
  /usr/share/man/man1/usbip.8.gz
  /usr/share/man/man1/perf-timechart.1.gz
  /usr/share/man/man1/perf-script-perl.1.gz
  /usr/share/man/man1/cpupower-info.1.gz
  /usr/share/man/man1/perf-help.1.gz
  /usr/share/man/man1/perf-archive.1.gz
  /usr/share/man/man1/perf-buildid-list.1.gz
  /usr/share/man/man1/perf-kmem.1.gz
  /usr/share/man/man1/perf-top.1.gz
  /usr/share/man/man1/perf-trace.1.gz
  /usr/share/man/man1/perf-stat.1.gz
  /usr/share/man/man1/usbipd.8.gz
  /usr/share/man/man1/cpupower-set.1.gz
  /usr/share/man/man1/perf-bench.1.gz
  /usr/share/man/man1/perf-sched.1.gz
  /usr/share/man/man1/perf-annotate.1.gz
  /usr/share/man/man1/perf-record.1.gz
  /usr/share/man/man1/perf-script-python.1.gz
  /usr/share/man/man1/cpupower-frequency-info.1.gz
  /usr/share/man/man1/perf-kvm.1.gz
  /usr/share/man/man1/perf-script.1.gz
  /usr/share/man/man1/perf-test.1.gz
  /usr/share/man/man1/perf-probe.1.gz
  /usr/share/man/man1/perf-lock.1.gz
  /usr/share/man/man1/perf-evlist.1.gz
  /usr/share/man/man1/cpupower.1.gz
  /usr/share/man/man1/perf-list.1.gz
  /usr/share/man/man8
  /usr/share/man/man8/x86_energy_perf_policy.8.gz
  /usr/share/man/man8/turbostat.8.gz
  /usr/share/doc
  /usr/share/doc/linux-tools-common
  /usr/share/doc/linux-tools-common/copyright
  /usr/share/doc/linux-tools-common/changelog.Debian.gz
  /usr/bin
  /usr/bin/turbostat
  /usr/bin/usbip
  /usr/bin/x86_energy_perf_policy
  /usr/bin/perf
  /usr/bin/usbipd
  /usr/bin/cpupower

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

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

[Kernel-packages] [Bug 1458778] Re: linux: 3.16.0-39.53 -proposed tracker

[John Johansen]

No CVEs

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress = 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/1458778

Title:
  linux: 3.16.0-39.53 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow package-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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Utopic:
  New

Bug description:
  This bug is for tracking the 3.16.0-39.53 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, 26. May 2015 08:17 UTC
  kernel-stable-Prepare-package-end:Tuesday, 26. May 2015 19:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 26. May 2015 19:02 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:00 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:00 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:00 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:00 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:00 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:00 UTC

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

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

[Kernel-packages] [Bug 1411193] Re: [Asus F200MA] bluetooth not working

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-precise

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

Title:
  [Asus F200MA] bluetooth not working

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released

Bug description:
  In my opinion, this is a very similar bug to

  https://bugs.launchpad.net/bugs/1395465

  in the sense that the bluetooth indicator works but no external devices are 
detected.
  I don't know which information I should provide here so I just insert uname 
-a and lsusb.

  lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 13d3:3423 IMC Networks 
  Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
  Bus 001 Device 002: ID 04f2:b483 Chicony Electronics Co., Ltd 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  uname -a
  Linux languasc-asus 3.16.0-30-generic #40-Ubuntu SMP Mon Jan 12 22:06:37 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

  Any help will be greatly appreciated. Alessandro

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

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

[Kernel-packages] [Bug 1354975] Re: iwlwifi Intel 7260 Wifi disconnects

[SkyRaT]

@dradetsky
Thanks.
Fixed by disabling BT using rfkill on Kubuntu 15.04, kernel 3.19,  on Lenovo 
T440s  with Intel 7260 (rev 83)

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

Title:
  iwlwifi Intel 7260 Wifi disconnects

Status in Unity Linux:
  New
Status in linux-firmware package in Ubuntu:
  Fix Released

Bug description:
  I experience frequent disconnects and auth issues, never more than 30
  minutes without a disconnect. Sometimes dozens of disconnects in a few
  minutes.

  This happens with the default 7260-8 firmware.
  Tried replacing the -8 with -9 ucode. Failed to load due to API version. This 
loaded the -7 driver which seems to be more stable.

  Tested against 2.4ghz APs (Apple, Netgear, Linksys).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-32-generic 3.13.0-32.57
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  steve  2577 F pulseaudio
   /dev/snd/controlC1:  steve  2577 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Aug 10 17:49:06 2014
  HibernationDevice: RESUME=UUID=374a0c1c-4ac2-456b-a67e-9ea54fe11fe6
  InstallationDate: Installed on 2013-12-28 (225 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Dell Inc. XPS 12-9Q33
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=58deb355-7a09-440b-ade2-69a84fd74460 ro ipv6.disable=1 quiet splash 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-32-generic N/A
   linux-backports-modules-3.13.0-32-generic  N/A
   linux-firmware 1.127.5
  SourcePackage: linux
  UpgradeStatus: Upgraded to trusty on 2014-07-06 (35 days ago)
  dmi.bios.date: 05/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A00
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA00:bd05/06/2013:svnDellInc.:pnXPS12-9Q33:pvrA00:rvnDellInc.:rnXPS12-9Q33:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A00
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1436745] Re: Audio can not output via system internal speaker on a HP machine

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
precise' to 'verification-done-precise'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-precise

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

Title:
  Audio can not output via system internal speaker on a HP machine

Status in HWE Next Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released

Bug description:
  Steps to Reproduce:
  1.Into OS
  2.Play an audio file from internal speaker, no sound can be heard
  3.Plug an external Speaker to audio jack, and play audio from external 
speaker, we can hear sound (like headphone)

  This bug is used for tracking purposes. Please do not triage.

  ===
  break-fix: - af95b41426e0b58279f8ff0ebe420df49a4e96b8

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

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

[Kernel-packages] [Bug 1438585] Re: no console when starting VM from cloud image

[Ming Lei]

[tom@vm-test]$vim arm64-qemu
[tom@vm-test]$./arm64-qemu
[0.00] Initializing cgroup subsys cpu
[0.00] Linux version 3.13.11-ckt20+ (tom@tom-T450) (gcc version 4.8.2 
20140110 (prerelease) [ibm/gcc-4_8-branch merged from gcc-4_8-branch, revision 
205847] (Ubuntu/Linaro 4.8.2-13ubuntu1) ) #181 SMP PREEMPT Mon Jun 1 17:48:14 
CST 2015 ()
[0.00] CPU: AArch64 Processor [411fd070] revision 0
[0.00] Memory limited to 1024MB
[0.00] efi: Getting parameters from FDT:
[0.00] efi: Can't find System Table in device tree!
[0.00] On node 0 totalpages: 262144
[0.00]   DMA32 zone: 3584 pages used for memmap
[0.00]   DMA32 zone: 0 pages reserved
[0.00]   DMA32 zone: 262144 pages, LIFO batch:31
[0.00] psci: probing for conduit method from DT.
[0.00] psci: PSCIv0.2 detected in firmware.
[0.00] psci: Using standard PSCI v0.2 function IDs
[0.00] PERCPU: Embedded 10 pages/cpu @ffc03ffda000 s10880 r8192 
d21888 u40960
[0.00] pcpu-alloc: s10880 r8192 d21888 u40960 alloc=10*4096
[0.00] pcpu-alloc: [0] 0 [0] 1 
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 258560
[0.00] Kernel command line: mem=1024M rootfstype=ext4 root=/dev/vda rw 
loglevel=9 no_console_suspend ip=dhcp
[0.00] PID hash table entries: 4096 (order: 3, 32768 bytes)
[0.00] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
[0.00] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
[0.00] software IO TLB [mem 0x7b00-0x7f00] (64MB) mapped at 
[ffc03b00-ffc03eff]
[0.00] Memory: 938804K/1048576K available (3508K kernel code, 249K 
rwdata, 1324K rodata, 194K init, 1180K bss, 109772K reserved)
[0.00] Virtual kernel memory layout:
[0.00] vmalloc : 0xff80 - 0xffbb   (245759 
MB)
[0.00] vmemmap : 0xffbc00e0 - 0xffbc01c0   (14 
MB)
[0.00] modules : 0xffbffc00 - 0xffc0   (64 
MB)
[0.00] memory  : 0xffc0 - 0xffc04000   (  1024 
MB)
[0.00]   .init : 0xffc00053a000 - 0xffc00056aa80   (   195 
kB)
[0.00]   .text : 0xffc8 - 0xffc000539154   (  4837 
kB)
[0.00]   .data : 0xffc00056b000 - 0xffc0005a94e0   (   250 
kB)
[0.00] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[0.00] Preemptible hierarchical RCU implementation.
[0.00]  RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=2.
[0.00] NR_IRQS:64 nr_irqs:64 0
[0.00] Architected cp15 timer(s) running at 62.50MHz (virt).
[0.00] sched_clock: 56 bits at 62MHz, resolution 16ns, wraps every 
219902322ns
[0.00] Console: colour dummy device 80x25
[0.00] console [tty0] enabled
[0.004477] Calibrating delay loop (skipped), value calculated using timer 
frequency.. 125.00 BogoMIPS (lpj=625000)


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

Title:
  no console when starting VM from cloud image

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in linux source package in Vivid:
  Fix Released

Bug description:
  In current arm64 utopic cloud image, the 'console=' parameter has been
  removed from grub config, and always resort to 'stdout' DT property
  which is setup from QEMU.

  Unfortunately parsing 'stdout' DT property is just merged to 3.19
  kernel, so there is no console usable any more for arm64 utopic VM
  when booting via uefi/grub.

  SRU Justification:
  Impact: No console if arm64 Utopic based VM is booted from the cloud image.
  Fix: backport stdout enablement patches from 3.19. 5 of these 6 patches are 
cherry picked from 3.19 to Utopic, and the other one is backported by just 
dropping the dt self-test code, and with these 6 patches, arm64 utopic VM can 
be booted with console.
  Testcase: Boot one arm64 Utopic VM via uefi/grub.

  5ba2ee8 of: support passing console options with stdout-path
  5c64126 of: add optional options parameter to of_find_node_by_path()
  7507839 of: Add bindings for chosen node, stdout-path
  54e15d7 of: correct of_console_check()'s return value
  4f2b1f0 of: Enable console on serial ports specified by /chosen/stdout-path
  a699dfd of: Create of_console_check() for selecting a console specified in 
/chosen

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

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

[Kernel-packages] [Bug 1446517] Re: num_steps = 0 error on ALC256

[David Henningsson]

Comes from upstream stable, does not need verification.

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

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

Title:
  num_steps = 0 error on ALC256

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  This bug is used for tracking, please do not triage.

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

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

[Kernel-packages] [Bug 1457369] Re: kernel 3.19.0-18 breaks HDMI audio for snd_hda_intel

[Benjamin Xiao]

As per my previous comment, I've already verified the package in
proposed. It works fine. Thanks everyone for the bug fix!

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

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

Title:
  kernel 3.19.0-18 breaks HDMI audio for snd_hda_intel

Status in System76:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  Problem appears on multiple computers with exact same kernel update, so 
clearly the problem is within the kernel. 3.19.0-16 did work without any 
problems.
  Before sound worked great via HDMI, now the HDMI output is not visible in 
neither alsamixer nor pulseaudio. Audio via the headphone jack still works.
  The computers are Intel-NUC-Kit-D54250WYK:
  00:02.0 VGA compatible controller [0300]: Intel Corporation Haswell-ULT 
Integrated Graphics Controller [8086:0a26] (rev 09)
Subsystem: Intel Corporation Device [8086:2054]
Kernel driver in use: i915
  00:03.0 Audio device [0403]: Intel Corporation Haswell-ULT HD Audio 
Controller [8086:0a0c] (rev 09)
Subsystem: Intel Corporation Device [8086:2054]
Kernel driver in use: snd_hda_inte

  dmesg gives:
  [3.178745] sound hdaudioC1D0: autoconfig: line_outs=1 
(0x21/0x0/0x0/0x0/0x0) type:hp
  [3.178750] sound hdaudioC1D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
  [3.178753] sound hdaudioC1D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0)
  [3.178754] sound hdaudioC1D0:mono: mono_out=0x0
  [3.178756] sound hdaudioC1D0:inputs:
  [3.178759] sound hdaudioC1D0:  Mic=0x19
  ...
  [3.215371] snd_hda_intel :00:03.0: Cannot turn on display power on 
i915
  ...
  [3.297561] [drm] Initialized i915 1.6.0 20141121 for :00:02.0 on 
minor 0
  ...
  [3.304357] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.304360] i915 :00:02.0: registered panic notifier
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  maarten1669 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  Lsusb:
   Bus 001 Device 008: ID 8087:07dc Intel Corp. 
   Bus 001 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic 
root=UUID=6c65d9ee-31fe-4832-8907-f47ac02d6f83 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware 1.143.1
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: WYLPT10H.86A.0038.2015.0410.1634
  dmi.board.name: D54250WYK
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H13922-302
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrWYLPT10H.86A.0038.2015.0410.1634:bd04/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD54250WYK:rvrH13922-302:cvn:ct3:cvr:
  --- 
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  maarten1669 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  Lsusb:
   Bus 001 Device 008: ID 8087:07dc Intel Corp. 
   Bus 001 Device 007: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 8087:8000 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic 
root=UUID=6c65d9ee-31fe-4832-8907-f47ac02d6f83 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware 1.143.1
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip fuse lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: WYLPT10H.86A.0038.2015.0410.1634
  dmi.board.name: D54250WYK
 

[Kernel-packages] [Bug 1457781] Re: armhf: cpufreq doesn't autoload by default

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-vivid

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

Title:
  armhf: cpufreq doesn't autoload by default

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: upon boot, frequency scaling is not working.

  Fix: Apply the patches, recompile and reboot.

  Testcase: Try booting a beaglebone with and without a patched
  kernel.

  With this series applied there should be:

  ubuntu@beaglebone:~$ ls -la /sys/devices/system/cpu/cpu0/cpufreq/
  total 0
  drwxr-xr-x 3 root root0 May 22 07:03 .
  drwxr-xr-x 5 root root0 May 22 07:03 ..
  -r--r--r-- 1 root root 4096 May 22 07:03 affected_cpus
  -r 1 root root 4096 May 22 07:03 cpuinfo_cur_freq
  -r--r--r-- 1 root root 4096 May 22 07:03 cpuinfo_max_freq
  -r--r--r-- 1 root root 4096 May 22 07:03 cpuinfo_min_freq
  -r--r--r-- 1 root root 4096 May 22 07:03 cpuinfo_transition_latency
  -r--r--r-- 1 root root 4096 May 22 07:03 related_cpus
  -r--r--r-- 1 root root 4096 May 22 07:03 scaling_available_frequencies
  -r--r--r-- 1 root root 4096 May 22 07:03 scaling_available_governors
  -r--r--r-- 1 root root 4096 May 22 07:03 scaling_cur_freq
  -r--r--r-- 1 root root 4096 May 22 07:03 scaling_driver
  -rw-r--r-- 1 root root 4096 May 22 04:43 scaling_governor
  -rw-r--r-- 1 root root 4096 May 22 07:03 scaling_max_freq
  -rw-r--r-- 1 root root 4096 May 22 07:03 scaling_min_freq
  -rw-r--r-- 1 root root 4096 May 22 07:03 scaling_setspeed
  drwxr-xr-x 2 root root0 May 22 07:03 stats
  ubuntu@beaglebone:~$

  With an unpatched kernel, until the cpufreq module is loaded, that
  directory doesn't exist.

  ...

  While cpufreq support on armhf is available for a while, if support is
  compiled as a kernel module, the corresponding module doesn't autoload
  by default, and thus frequency scaling is not active upon boot until a
  user manually load it (or until /etc/modules is modified to forcibly
  load it).

  While in Trusty cpufreq was built-in on armhf, starting with Utopic we
  made support available as a kernel module, making people think that
  cpufreq was either broken or missing in their new kernels.

  To fix it, revert back that decision and make cpufreq compiled-in
  again on armhf - it affects Utopic and Vivid kernels.

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

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

[Kernel-packages] [Bug 1450584] Re: mono occassionally crashes since kernel 3.13.0-48 on multi-cpu vm

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-utopic

** Tags added: verification-needed-vivid

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

Title:
  mono occassionally crashes since kernel 3.13.0-48 on multi-cpu vm

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  The addition of the commit:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=11f4e0339c8dc8d760483258efd9f15b4c6dcda2

  Causes SIGSEGVs when running certain workloads on multi-cpu VMs.

  [Test Case]

  Mono test case here that causes the SIGSEGV
  https://bugzilla.xamarin.com/show_bug.cgi?id=29212

  [Fix]

  These two commits are required for fixing this issue:
  
https://github.com/torvalds/linux/commit/80f7fdb1c7f0f9266421f823964fd1962681f6ce
  
https://github.com/torvalds/linux/commit/0a4e6be9ca17c54817cf814b4b5aa60478c6df27

  --

  Gradually since late March more and more users started to complain
  about frequent SIGSEGV crashes in our .net/mono application. Early
  April I started to investigate it actively.

  After eliminating possible native libraries, and testing various mono
  versions I discovered the crashes would occur more frequently on a
  vbox vm with multiple cpus configured. And discovered that the mono
  bug-18026.cs testcase would fairly consistently crash. At that point
  it was reported to the mono bug tracker.

  I finally got a break when we found a correlation with the kernel version. 
3.13.0-46 didn't crash while 3.13.0-48,49 did.
  More and more users upgrade to these newer kernel versions and start running 
into issues, which explains the gradual increase in reports.

  Early this week I performed a full git bisect on the kernel between 3.13.0-46 
and -48 and isolated the commit that seems to trigger the crashes.
  Namely 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=11f4e0339c8dc8d760483258efd9f15b4c6dcda2

  At this point I don't know if the commit messed up something, or that mono 
simply handles it incorrectly. However, a few commits for linux 4.x seem to fix 
it:
  
https://github.com/torvalds/linux/commit/80f7fdb1c7f0f9266421f823964fd1962681f6ce
  
https://github.com/torvalds/linux/commit/0a4e6be9ca17c54817cf814b4b5aa60478c6df27
  I applied these commits myself on top of commit 11f4e033, compiled and ran 
the testcase... didn't crash in the 200x test runs I did.
  Although I don't know if those two patches have unknown side-effects.
  I'm not an expert on the kernel, not even remotely. But I thought it would be 
nice to be able to point at a possible solution.

  My current test vm is a virtualbox vm 64bit installed using the 14.04.2 
server iso running on an older i7 quad core Windows 7 64bit host.
  In the vm I've tested numerous mono and kernel combinations. Last test was 
with kernel 3.16.0-36 and 3.13.0-51 and mono 4.0.1, in which the problem still 
occurs.

  By now I've debugged the app using gdb several dozen times on various
  user setups, compiled mono half a dozen times, and then the 8x3h
  compile kernel bisect :) Speaking of down the rabbit-hole...

  So I'm pretty desperate for some expert to help me out here. :D

  Reference to mono bug report:
  https://bugzilla.xamarin.com/show_bug.cgi?id=29212

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-51-generic 3.13.0-51.84
  ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-51-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 30 18:53 seq
   crw-rw 1 root audio 116, 33 Apr 30 18:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.10
  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: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDmesg: [9.379188] init: plymouth-upstart-bridge main process 
ended, respawning
  Date: Thu Apr 30 19:45:43 2015
  HibernationDevice: RESUME=UUID=b35ef328-166d-4476-a418-e7e80d22cb30
  InstallationDate: Installed on 2015-04-22 (7 days ago)
  

[Kernel-packages] [Bug 1455105] Re: [SRU vivid] re-enable GPIO_DWAPB for arm64 to enable graceful shutdown on HP Proliant m400

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-vivid

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

Title:
  [SRU vivid] re-enable GPIO_DWAPB for arm64 to enable graceful shutdown
  on HP Proliant m400

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  Graceful shutdown from the ILO-CM does not work on Ubuntu 15.04 due to commit 
1972c97db5b, but is fixed by commit b90f8f22ed8.

  [Test Case]
  Login to the iLO-CM and issue 'set node power off shutdown c#n#'
  Check the console to ensure the node is shutting down.

  [Regression Risk]
  This re-enables a gpio driver on arm64 that was enabled on older versions of 
the kernel and is enabled for arm in general currently.

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

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

[Kernel-packages] [Bug 1450584] Re: mono occassionally crashes since kernel 3.13.0-48 on multi-cpu vm

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

Title:
  mono occassionally crashes since kernel 3.13.0-48 on multi-cpu vm

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  The addition of the commit:
  
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=11f4e0339c8dc8d760483258efd9f15b4c6dcda2

  Causes SIGSEGVs when running certain workloads on multi-cpu VMs.

  [Test Case]

  Mono test case here that causes the SIGSEGV
  https://bugzilla.xamarin.com/show_bug.cgi?id=29212

  [Fix]

  These two commits are required for fixing this issue:
  
https://github.com/torvalds/linux/commit/80f7fdb1c7f0f9266421f823964fd1962681f6ce
  
https://github.com/torvalds/linux/commit/0a4e6be9ca17c54817cf814b4b5aa60478c6df27

  --

  Gradually since late March more and more users started to complain
  about frequent SIGSEGV crashes in our .net/mono application. Early
  April I started to investigate it actively.

  After eliminating possible native libraries, and testing various mono
  versions I discovered the crashes would occur more frequently on a
  vbox vm with multiple cpus configured. And discovered that the mono
  bug-18026.cs testcase would fairly consistently crash. At that point
  it was reported to the mono bug tracker.

  I finally got a break when we found a correlation with the kernel version. 
3.13.0-46 didn't crash while 3.13.0-48,49 did.
  More and more users upgrade to these newer kernel versions and start running 
into issues, which explains the gradual increase in reports.

  Early this week I performed a full git bisect on the kernel between 3.13.0-46 
and -48 and isolated the commit that seems to trigger the crashes.
  Namely 
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=11f4e0339c8dc8d760483258efd9f15b4c6dcda2

  At this point I don't know if the commit messed up something, or that mono 
simply handles it incorrectly. However, a few commits for linux 4.x seem to fix 
it:
  
https://github.com/torvalds/linux/commit/80f7fdb1c7f0f9266421f823964fd1962681f6ce
  
https://github.com/torvalds/linux/commit/0a4e6be9ca17c54817cf814b4b5aa60478c6df27
  I applied these commits myself on top of commit 11f4e033, compiled and ran 
the testcase... didn't crash in the 200x test runs I did.
  Although I don't know if those two patches have unknown side-effects.
  I'm not an expert on the kernel, not even remotely. But I thought it would be 
nice to be able to point at a possible solution.

  My current test vm is a virtualbox vm 64bit installed using the 14.04.2 
server iso running on an older i7 quad core Windows 7 64bit host.
  In the vm I've tested numerous mono and kernel combinations. Last test was 
with kernel 3.16.0-36 and 3.13.0-51 and mono 4.0.1, in which the problem still 
occurs.

  By now I've debugged the app using gdb several dozen times on various
  user setups, compiled mono half a dozen times, and then the 8x3h
  compile kernel bisect :) Speaking of down the rabbit-hole...

  So I'm pretty desperate for some expert to help me out here. :D

  Reference to mono bug report:
  https://bugzilla.xamarin.com/show_bug.cgi?id=29212

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-51-generic 3.13.0-51.84
  ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-51-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 30 18:53 seq
   crw-rw 1 root audio 116, 33 Apr 30 18:53 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.10
  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: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDmesg: [9.379188] init: plymouth-upstart-bridge main process 
ended, respawning
  Date: Thu Apr 30 19:45:43 2015
  HibernationDevice: RESUME=UUID=b35ef328-166d-4476-a418-e7e80d22cb30
  InstallationDate: Installed on 2015-04-22 (7 days ago)
  InstallationMedia: Ubuntu-Server 14.04.2 LTS Trusty Tahr - 

[Kernel-packages] [Bug 1454013] Re: Booting takes very long time on Intel Braswell caused by eMMC

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-vivid

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

Title:
  Booting takes very long time on Intel Braswell caused by eMMC

Status in HWE Next Project:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed
Status in linux source package in Wily:
  Fix Released

Bug description:
  This patch could fix this issue, otherwise booting will take very long
  time.

  
  4e93b9a6abc0d028daf3c8a00cb77b679d8a4df4
  mmc: card: Don't access RPMB partitions for normal read/write
  During kernel boot, it will try to read some logical sectors
  of each block device node for the possible partition table.

  But since RPMB partition is special and can not be accessed
  by normal eMMC read / write CMDs, it will cause below error
  messages during kernel boot:
  ...
   mmc0: Got data interrupt 0x0002 even though no data operation was in 
progress.
   mmcblk0rpmb: error -110 transferring data, sector 0, nr 32, cmd response 
0x900, card status 0xb00
   mmcblk0rpmb: retrying using single block read
   mmcblk0rpmb: timed out sending r/w cmd command, card status 0x400900
   mmcblk0rpmb: timed out sending r/w cmd command, card status 0x400900
   mmcblk0rpmb: timed out sending r/w cmd command, card status 0x400900
   mmcblk0rpmb: timed out sending r/w cmd command, card status 0x400900
   mmcblk0rpmb: timed out sending r/w cmd command, card status 0x400900
   mmcblk0rpmb: timed out sending r/w cmd command, card status 0x400900
   end_request: I/O error, dev mmcblk0rpmb, sector 0
   Buffer I/O error on device mmcblk0rpmb, logical block 0
   end_request: I/O error, dev mmcblk0rpmb, sector 8
   Buffer I/O error on device mmcblk0rpmb, logical block 1
   end_request: I/O error, dev mmcblk0rpmb, sector 16
   Buffer I/O error on device mmcblk0rpmb, logical block 2
   end_request: I/O error, dev mmcblk0rpmb, sector 24
   Buffer I/O error on device mmcblk0rpmb, logical block 3
  ...

  This patch will discard the access request in eMMC queue if
  it is RPMB partition access request. By this way, it avoids
  trigger above error messages.

  Fixes: 090d25fe224c (mmc: core: Expose access to RPMB partition)
  Signed-off-by: Yunpeng Gao yunpeng@intel.com
  Signed-off-by: Chuanxiao Dong chuanxiao.d...@intel.com
  Tested-by: Michael Shigorin m...@altlinux.org
  Signed-off-by: Ulf Hansson ulf.hans...@linaro.org

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

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

[Kernel-packages] [Bug 1453848] Re: Compilation warning on Utopic

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-utopic

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

Title:
  Compilation warning on Utopic

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  [Impact]

  When compiling the Utopic kernel, the following warning can is shown:

  /tmp/kernel-henrix-EluZkimP/build/fs/exec.c: In function 'do_open_exec':
  /tmp/kernel-henrix-EluZkimP/build/fs/exec.c:780:18: warning: passing argument 
1 of 'trace_open_exec' from incompatible pointer type
trace_open_exec(name);
^
  In file included from 
/tmp/kernel-henrix-EluZkimP/build/include/trace/syscall.h:4:0,
   from 
/tmp/kernel-henrix-EluZkimP/build/include/linux/syscalls.h:80,
   from /tmp/kernel-henrix-EluZkimP/build/fs/exec.c:48:
  /tmp/kernel-henrix-EluZkimP/build/include/linux/tracepoint.h:163:21: note: 
expected 'const char *' but argument is of type 'struct filename *'
static inline void trace_##name(proto)\
   ^
  /tmp/kernel-henrix-EluZkimP/build/include/linux/tracepoint.h:270:3: note: in 
expansion of macro '__DECLARE_TRACE'
 __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), 1, \
 ^
  /tmp/kernel-henrix-EluZkimP/build/include/linux/tracepoint.h:404:2: note: in 
expansion of macro 'DECLARE_TRACE'
DECLARE_TRACE(name, PARAMS(proto), PARAMS(args))
^
  /tmp/kernel-henrix-EluZkimP/build/include/trace/events/fs.h:32:1: note: in 
expansion of macro 'TRACE_EVENT'
   TRACE_EVENT(open_exec,
   ^

  This is due to a wrong parameter type being used while invoking
  trace_open_exec()

  [Test Case]

  A simple compilation of the kernel shows this warning.

  [Fix]

  A patch with the following should fix it:

  -   trace_open_exec(name);
  +   trace_open_exec(name-name);

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

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

[Kernel-packages] [Bug 1456123] Re: [i915_bpo] Update driver code to 4.1-rc4 + backported fixes

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-vivid

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

Title:
  [i915_bpo] Update driver code to 4.1-rc4 + backported fixes

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  Pull changes from 4.1-rc4, and add further backports for CHV  SKL.

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

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

[Kernel-packages] [Bug 1457781] Re: armhf: cpufreq doesn't autoload by default

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-utopic

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

Title:
  armhf: cpufreq doesn't autoload by default

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Utopic:
  Fix Committed
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: upon boot, frequency scaling is not working.

  Fix: Apply the patches, recompile and reboot.

  Testcase: Try booting a beaglebone with and without a patched
  kernel.

  With this series applied there should be:

  ubuntu@beaglebone:~$ ls -la /sys/devices/system/cpu/cpu0/cpufreq/
  total 0
  drwxr-xr-x 3 root root0 May 22 07:03 .
  drwxr-xr-x 5 root root0 May 22 07:03 ..
  -r--r--r-- 1 root root 4096 May 22 07:03 affected_cpus
  -r 1 root root 4096 May 22 07:03 cpuinfo_cur_freq
  -r--r--r-- 1 root root 4096 May 22 07:03 cpuinfo_max_freq
  -r--r--r-- 1 root root 4096 May 22 07:03 cpuinfo_min_freq
  -r--r--r-- 1 root root 4096 May 22 07:03 cpuinfo_transition_latency
  -r--r--r-- 1 root root 4096 May 22 07:03 related_cpus
  -r--r--r-- 1 root root 4096 May 22 07:03 scaling_available_frequencies
  -r--r--r-- 1 root root 4096 May 22 07:03 scaling_available_governors
  -r--r--r-- 1 root root 4096 May 22 07:03 scaling_cur_freq
  -r--r--r-- 1 root root 4096 May 22 07:03 scaling_driver
  -rw-r--r-- 1 root root 4096 May 22 04:43 scaling_governor
  -rw-r--r-- 1 root root 4096 May 22 07:03 scaling_max_freq
  -rw-r--r-- 1 root root 4096 May 22 07:03 scaling_min_freq
  -rw-r--r-- 1 root root 4096 May 22 07:03 scaling_setspeed
  drwxr-xr-x 2 root root0 May 22 07:03 stats
  ubuntu@beaglebone:~$

  With an unpatched kernel, until the cpufreq module is loaded, that
  directory doesn't exist.

  ...

  While cpufreq support on armhf is available for a while, if support is
  compiled as a kernel module, the corresponding module doesn't autoload
  by default, and thus frequency scaling is not active upon boot until a
  user manually load it (or until /etc/modules is modified to forcibly
  load it).

  While in Trusty cpufreq was built-in on armhf, starting with Utopic we
  made support available as a kernel module, making people think that
  cpufreq was either broken or missing in their new kernels.

  To fix it, revert back that decision and make cpufreq compiled-in
  again on armhf - it affects Utopic and Vivid kernels.

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

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

[Kernel-packages] [Bug 1452628] Re: beaglebone: random MAC on boot

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-utopic

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

Title:
  beaglebone: random MAC on boot

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: after every reboot, the nic on the beaglebone gets a
  completely different MAC address.

  Fix: Apply the patches, recompile and reboot.

  Testcase: Try booting two times in a row with and without the
  patches applied and check if the MAC address of eth0 changes or not.

  With this series applied:

  ...
  [2.847766] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
  [2.854144] davinci_mdio 4a101000.mdio: detected phy mask fffe
  [2.866722] libphy: 4a101000.mdio: probed
  [2.871020] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, 
driver SMSC LAN8710/LAN8720
  [2.886827] Detected MACID = 90:59:af:5a:b6:ca
  ...

  and it won't change anymore.
  ---

  On the beaglebone, the NIC keeps getting a random MAC after every
  reboot, making it impossible to associate a static ip with the board:

  ...
  [2.839176] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
  [2.845579] davinci_mdio 4a101000.mdio: detected phy mask fffe
  [2.858195] libphy: 4a101000.mdio: probed
  [2.862510] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, 
driver SMSC LAN8710/LAN8720
  [2.872364] cpu cpu0: cpu0 regulator not ready, retry
  [2.878372] Random MACID = ee:7a:fa:cd:13:39
  ...

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

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

[Kernel-packages] [Bug 1453848] Re: Compilation warning on Utopic

[Luis Henriques]

I've verified that the build logs for the utopic kernel in -proposed
(3.16.0-39.53) do not have the warning in this bug description.  Tagging
as verified.

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

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

Title:
  Compilation warning on Utopic

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  [Impact]

  When compiling the Utopic kernel, the following warning can is shown:

  /tmp/kernel-henrix-EluZkimP/build/fs/exec.c: In function 'do_open_exec':
  /tmp/kernel-henrix-EluZkimP/build/fs/exec.c:780:18: warning: passing argument 
1 of 'trace_open_exec' from incompatible pointer type
trace_open_exec(name);
^
  In file included from 
/tmp/kernel-henrix-EluZkimP/build/include/trace/syscall.h:4:0,
   from 
/tmp/kernel-henrix-EluZkimP/build/include/linux/syscalls.h:80,
   from /tmp/kernel-henrix-EluZkimP/build/fs/exec.c:48:
  /tmp/kernel-henrix-EluZkimP/build/include/linux/tracepoint.h:163:21: note: 
expected 'const char *' but argument is of type 'struct filename *'
static inline void trace_##name(proto)\
   ^
  /tmp/kernel-henrix-EluZkimP/build/include/linux/tracepoint.h:270:3: note: in 
expansion of macro '__DECLARE_TRACE'
 __DECLARE_TRACE(name, PARAMS(proto), PARAMS(args), 1, \
 ^
  /tmp/kernel-henrix-EluZkimP/build/include/linux/tracepoint.h:404:2: note: in 
expansion of macro 'DECLARE_TRACE'
DECLARE_TRACE(name, PARAMS(proto), PARAMS(args))
^
  /tmp/kernel-henrix-EluZkimP/build/include/trace/events/fs.h:32:1: note: in 
expansion of macro 'TRACE_EVENT'
   TRACE_EVENT(open_exec,
   ^

  This is due to a wrong parameter type being used while invoking
  trace_open_exec()

  [Test Case]

  A simple compilation of the kernel shows this warning.

  [Fix]

  A patch with the following should fix it:

  -   trace_open_exec(name);
  +   trace_open_exec(name-name);

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

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

[Kernel-packages] [Bug 1451593] Re: [SRU] Forward port XGene MSI-X driver to vivid

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-vivid

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

Title:
  [SRU] Forward port XGene MSI-X driver to vivid

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
  Without the MSI-X driver, network performance on the HP Proliant m400 will be 
degraded in vivid from what can be achieved in trusty and utopic.

  [Test Case]
  All commands work on the HP Proliant m400:

  'lspci -v' should show 'MSI-X: Enable+' under the Mellanox entry.
  'cat /proc/interrupts' will list 'xgene-msi' next to the eth# and mlx4... 
entries.

  [Regression Risk]
  This driver is self contained for the xgene1 platform.

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

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

[Kernel-packages] [Bug 1442411] Re: Intel 3160 wireless card no longer able to connect to wifi networks

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
vivid' to 'verification-done-vivid'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-vivid

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

Title:
  Intel 3160 wireless card no longer able to connect to wifi networks

Status in System76:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  [Impact]

  Laptop: Lenovo Y70 Touch
  Wireless Card: Intel Corporation Wireless 3160 (rev 93)

  When running Ubuntu Gnome 14.10 (on a live USB drive) I am able to
  connect to wifi networks without any issue. When running Ubuntu Gnome
  15.04 (either on live USB or installed and fully updated) I am able to
  see the list of available wifi networks, but not able to connect.
  Selecting one and entering the password makes the network manager
  applet indicate that it is Connecting... but then it gives up after
  about a minute or so and reverts back to Not Connected. I have
  tested this without network encryption as well, and the same result
  occurs.

  [Test Case]

  I have ran a wifi debugging script, here is the output:

  For Ubuntu 14.10 - http://pastebin.com/aLUhTyrM
  For Ubuntu 15.04 - http://pastebin.com/f0yRjQUC

  Again, the card seems to work perfectly on 14.10, but is unable to
  connect to any networks on 15.04.

  [Fix]

  commit afcee962b09842d0f4191beb4a2d08251b4c7705 upstream

  [Workaround]

  Boot with bluetooth turned off. If the computer boots with the
  bluetooth turned on, the wifi will not work, even if you first turn
  off the bluetooth. A restart is needed.

  ---
  ApportVersion: 2.17-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mboratko   1609 F pulseaudio
   /dev/snd/controlC1:  mboratko   1609 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 15.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-04-10 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Beta amd64 (20150326)
  MachineType: LENOVO 80DU
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic.efi.signed 
root=UUID=0fb46cba-f7ac-4bc5-aa7d-5f6aa74636c1 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-12-generic N/A
   linux-backports-modules-3.19.0-12-generic  N/A
   linux-firmware 1.143
  Tags:  vivid
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 3.19.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/11/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN37WW(V2.01)
  dmi.board.asset.tag: 31900058WIN
  dmi.board.name: Lenovo Y70-70 Touch
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: 31900058WIN
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y70-70 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN37WW(V2.01):bd02/11/2015:svnLENOVO:pn80DU:pvrLenovoY70-70Touch:rvnLENOVO:rnLenovoY70-70Touch:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY70-70Touch:
  dmi.product.name: 80DU
  dmi.product.version: Lenovo Y70-70 Touch
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1444179] Re: add hid drivers to virtual kernel

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-utopic

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

Title:
  add hid drivers to virtual kernel

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  Please move hid_hyperv and hyperv_fb to the -virtual kernel. Microsoft
  reports that these drivers are needed for connecting to Azure VM's
  using the Hyper-V manager.

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

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

[Kernel-packages] [Bug 1290745] Re: [Radeon HD 8670A][1002:6660] Unable to load into live desktop after clicked Try Ubuntu on 12.04.4 bootable usb drive

[Yung Shen]

@penalvch
tried on both stable vivid and 14.04.2 image, 
it cannot be reproduce( and uma/integrated graphic is under use)


** Changed in: linux (Ubuntu)
   Status: Incomplete = Won't Fix

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

Title:
  [Radeon HD 8670A][1002:6660] Unable to load into live desktop after
  clicked Try Ubuntu  on 12.04.4 bootable usb drive

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  
  Failed to load into live desktop after clicked the Try Ubuntu button on 
welcome screen.

  Expected:
  Log into live desktop

  Actual result:
  Following prompted window, trying to run low-graphic mode still not able to 
load the desktop, will fallback to console.
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.11.0-15-generic.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 1: PCH [HDA Intel PCH], device 0: ALC292 Analog [ALC292 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 3516 F pulseaudio
   /dev/snd/controlC1:  ubuntu 3516 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xf7d34000 irq 48'
 Mixer name : 'Intel Haswell HDMI'
 Components : 'HDA:80862807,80860101,0010'
 Controls  : 21
 Simple ctrls  : 3
  Card1.Amixer.info:
   Card hw:1 'PCH'/'HDA Intel PCH at 0xf7d3 irq 49'
 Mixer name : 'Realtek ALC292'
 Components : 'HDA:10ec0292,102805bd,0011'
 Controls  : 28
 Simple ctrls  : 13
  CasperVersion: 1.315.1
  DistroRelease: Ubuntu 12.04
  LiveMediaBuild: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
  MachineType: Dell Inc. Latitude E6440
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --
  ProcVersionSignature: Ubuntu 3.11.0-15.25~precise1-generic 3.11.10
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware 1.79.9
  Tags:  precise
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/03/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X23
  dmi.board.name: 02P3T1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrX23:bd07/03/2013:svnDellInc.:pnLatitudeE6440:pvr01:rvnDellInc.:rn02P3T1:rvrX03:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  --- 
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CasperVersion: 1.315.1
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  DistUpgraded: Fresh install
  DistroCodename: precise
  DistroRelease: Ubuntu 12.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, even including gdb or git bisection work if 
needed
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:05bd]
 Subsystem: Dell Device [1028:05bd]
  LiveMediaBuild: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 
(20140204)
  MachineType: Dell Inc. Latitude E6440
  MarkForUpload: True
  Package: xorg 1:7.6+12ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --
  ProcVersionSignature: Ubuntu 3.11.0-15.25~precise1-generic 3.11.10
  Tags:  precise ubuntu referred-by-support
  Uname: Linux 3.11.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 07/03/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: X23
  dmi.board.name: 02P3T1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrX23:bd07/03/2013:svnDellInc.:pnLatitudeE6440:pvr01:rvnDellInc.:rn02P3T1:rvrX03:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.7.12-0ubuntu3
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 

[Kernel-packages] [Bug 1438585] Re: no console when starting VM from cloud image

[Ming Lei]

** Tags removed: verification-needed-trusty

** Tags added: verification-done-trusty

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

Title:
  no console when starting VM from cloud image

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in linux source package in Vivid:
  Fix Released

Bug description:
  In current arm64 utopic cloud image, the 'console=' parameter has been
  removed from grub config, and always resort to 'stdout' DT property
  which is setup from QEMU.

  Unfortunately parsing 'stdout' DT property is just merged to 3.19
  kernel, so there is no console usable any more for arm64 utopic VM
  when booting via uefi/grub.

  SRU Justification:
  Impact: No console if arm64 Utopic based VM is booted from the cloud image.
  Fix: backport stdout enablement patches from 3.19. 5 of these 6 patches are 
cherry picked from 3.19 to Utopic, and the other one is backported by just 
dropping the dt self-test code, and with these 6 patches, arm64 utopic VM can 
be booted with console.
  Testcase: Boot one arm64 Utopic VM via uefi/grub.

  5ba2ee8 of: support passing console options with stdout-path
  5c64126 of: add optional options parameter to of_find_node_by_path()
  7507839 of: Add bindings for chosen node, stdout-path
  54e15d7 of: correct of_console_check()'s return value
  4f2b1f0 of: Enable console on serial ports specified by /chosen/stdout-path
  a699dfd of: Create of_console_check() for selecting a console specified in 
/chosen

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

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

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  Surface Pro 2 wifi crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System hangs as soon as any network traffic is generated from wifi
  adaptor.

  think i may have caught the crash trying to install wireshark via the
  console (ctrl + alt + f1)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-18-generic 3.19.0-18.18
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tom1635 F pulseaudio
  Date: Mon Jun  1 20:03:57 2015
  HibernationDevice: RESUME=UUID=ae61b08a-a372-4d5a-b4d6-64bf1c8a55a8
  InstallationDate: Installed on 2015-05-31 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
  MachineType: Microsoft Corporation Surface Pro 2
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-18-generic.efi.signed 
root=UUID=cc5fc4f0-7f27-42c3-b890-87ac9cbf1628 ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-18-generic N/A
   linux-backports-modules-3.19.0-18-generic  N/A
   linux-firmware 1.143.1
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.05.0250
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Surface Pro 2
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: 0
  dmi.chassis.type: 11
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.05.0250:bd04/10/2015:svnMicrosoftCorporation:pnSurfacePro2:pvr1:rvnMicrosoftCorporation:rnSurfacePro2:rvr1:cvnMicrosoftCorporation:ct11:cvr1:
  dmi.product.name: Surface Pro 2
  dmi.product.version: 1
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1449438] Re: Marvell 88W8797 wifi (module mwifiex) does not work on Surface Pro

[Tom]

Thanks Christopher, i have submitted a new report and subscribed you to
it, also attached a screen shot of when the crash happened.

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

Title:
  Marvell 88W8797 wifi (module mwifiex) does not work on Surface Pro

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been running Ubuntu 14.10 on a Microsoft Surface Pro. After some
  initial problems (see
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1165938) (fixed
  by kernel updates I guess) the wifi was working fine. Since the
  upgrade to 15.04 the problems are back: I can connect to a wifi
  network, the connection is working for a few seconds but drops right
  after. I attached the relevant entries in dmes.log.

  I tried installing the marvell firmware from git://git.marvell.com
  /mwifiex-firmware.git, that didn't change anything. I also tried the
  mainline kernel from http://kernel.ubuntu.com/~kernel-
  ppa/mainline/v4.1-rc1-vivid/: the connection is again working for a
  few seconds but the whole system hangs afterwards.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wilk   1792 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 28 10:57:42 2015
  HibernationDevice: RESUME=UUID=adb12a68-9928-4181-b4e2-487010d3c501
  InstallationDate: Installed on 2014-02-19 (432 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Microsoft Corporation Surface with Windows 8 Pro
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed 
root=UUID=919f00b8-5010-46e1-b2f9-c129e17d5312 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2015-04-27 (0 days ago)
  dmi.bios.date: 01/08/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.00.0250
  dmi.board.asset.tag: 0
  dmi.board.name: Surface with Windows 8 Pro
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: 0
  dmi.chassis.type: 17
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.00.0250:bd01/08/2013:svnMicrosoftCorporation:pnSurfacewithWindows8Pro:pvr1:rvnMicrosoftCorporation:rnSurfacewithWindows8Pro:rvr1:cvnMicrosoftCorporation:ct17:cvr1:
  dmi.product.name: Surface with Windows 8 Pro
  dmi.product.version: 1
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1458618] Re: linux: 3.13.0-54.91 -proposed tracker

[John Johansen]

No CVEs

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress = 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/1458618

Title:
  linux: 3.13.0-54.91 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow package-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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 25. May 2015 16:17 UTC
  kernel-stable-Prepare-package-end:Wednesday, 27. May 2015 02:03 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 27. May 2015 02:03 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:12 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:28 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:28 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:28 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:28 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:28 UTC

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

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

[Kernel-packages] [Bug 1458901] Re: linux: 3.2.0-85.122 -proposed tracker

[John Johansen]

No CVEs

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress = 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/1458901

Title:
  linux: 3.2.0-85.122 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.2.0-85.122 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, 26. May 2015 14:37 UTC
  kernel-stable-Prepare-package-end:Tuesday, 26. May 2015 20:06 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 26. May 2015 20:06 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 21:29 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 23:00 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 23:00 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 23:00 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 23:00 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 23:00 UTC

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

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

[Kernel-packages] [Bug 1458618] Re: linux: 3.13.0-54.91 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the 3.13.0-54.91 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 25. May 2015 16:17 UTC
  kernel-stable-Prepare-package-end:Wednesday, 27. May 2015 02:03 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 27. May 2015 02:03 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:12 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:28 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:28 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:28 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:28 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:28 UTC
+ kernel-stable-Security-signoff-end:Monday, 01. June 2015 09:00 UTC

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

Title:
  linux: 3.13.0-54.91 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow package-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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Monday, 25. May 2015 16:17 UTC
  kernel-stable-Prepare-package-end:Wednesday, 27. May 2015 02:03 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 27. May 2015 02:03 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:12 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:28 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:28 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:28 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:28 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:28 UTC
  kernel-stable-Security-signoff-end:Monday, 01. June 2015 09:00 UTC

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

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

[Kernel-packages] [Bug 1458778] Re: linux: 3.16.0-39.53 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the 3.16.0-39.53 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, 26. May 2015 08:17 UTC
  kernel-stable-Prepare-package-end:Tuesday, 26. May 2015 19:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 26. May 2015 19:02 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:00 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:00 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:00 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:00 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:00 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:00 UTC
+ kernel-stable-Security-signoff-end:Monday, 01. June 2015 09:00 UTC

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

Title:
  linux: 3.16.0-39.53 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow package-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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Utopic:
  New

Bug description:
  This bug is for tracking the 3.16.0-39.53 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, 26. May 2015 08:17 UTC
  kernel-stable-Prepare-package-end:Tuesday, 26. May 2015 19:02 UTC
  kernel-stable-Promote-to-proposed-start:Tuesday, 26. May 2015 19:02 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:00 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:00 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:00 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:00 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:00 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:00 UTC
  kernel-stable-Security-signoff-end:Monday, 01. June 2015 09:00 UTC

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

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

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

[Brad Figg]

** Description changed:

  This bug is for tracking the 3.16.0-39.53~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, 26. May 2015 19:00 UTC
  kernel-stable-master-bug:1458778
  kernel-stable-Prepare-package-end:Wednesday, 27. May 2015 19:01 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 27. May 2015 19:01 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:00 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:01 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:01 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:01 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:01 UTC
+ kernel-stable-Security-signoff-end:Monday, 01. June 2015 09:00 UTC

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow package-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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.16.0-39.53~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, 26. May 2015 19:00 UTC
  kernel-stable-master-bug:1458778
  kernel-stable-Prepare-package-end:Wednesday, 27. May 2015 19:01 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 27. May 2015 19:01 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:00 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:01 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:01 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:01 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:01 UTC
  kernel-stable-Security-signoff-end:Monday, 01. June 2015 09:00 UTC

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

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

[Kernel-packages] [Bug 1393079] Re: Touchpad not working after suspend/resume

[svenmeier]

A workaround for Ubuntu 15.04 is to add a new service to systemd which
reloads the module after suspend:

sven@:/etc/systemd/system$ more touchscreen.service
[Unit]
Description=Restore touchscreen after suspend
After=suspend.target

[Service]
Type=simple
ExecStartPre=/sbin/modprobe -r hid_multitouch
ExecStart=/sbin/modprobe hid_multitouch

[Install]
WantedBy=suspend.target

sven@:/etc/systemd/system$ sudo systemctl enable
/etc/systemd/system/touchscreen.service

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

Title:
  Touchpad not working after suspend/resume

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu 14.10 on an Acer Laptop, model: Aspire E5-571G-941Y
  $ uname -a
  Linux Acer-Aspire-E5-571G 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 
13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

  Every time I suspend, the trackpad no longer works when resuming.

  I see several other people have the same issue with the same laptop here:
  http://ubuntuforums.org/showthread.php?t=2250002
  (some people say it's a 14.10 specific problem)

  I realize this report is very poor but please don't hesitate to request data 
/ clarifications from me, I'll be happy to help.
  --- 
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bod3942 F pulseaudio
   /dev/snd/controlC1:  bod3942 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=2e6e7d72-637c-4b16-8cda-0471dfb711d4
  InstallationDate: Installed on 2014-11-14 (15 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Acer Aspire E5-571G
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed 
root=UUID=94aa9203-873c-4dff-8207-4e6b33a6a3e7 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-25-generic N/A
   linux-backports-modules-3.16.0-25-generic  N/A
   linux-firmware 1.138
  Tags:  utopic
  Uname: Linux 3.16.0-25-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-11-14 (15 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/06/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_HB
  dmi.board.vendor: Acer
  dmi.board.version: V1.04
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd05/06/2014:svnAcer:pnAspireE5-571G:pvrV1.04:rvnAcer:rnEA50_HB:rvrV1.04:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-571G
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1452620] Re: beaglebone: kernel BUG on boot

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

Title:
  beaglebone: kernel BUG on boot

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  SRU Justification:

  Impact: Crash upon boot.

  Fix: Apply the patch, recompile and reboot.

  Testcase: Try booting the board several times in a row with and
  without a patched kernel.

  ---

  Booting a trusty kernel on a beaglebone, you often ends up with:

  ...
  [9.758659] libphy: PHY 4a101000.mdio:01 not found
  [9.763789] net eth0: phy 4a101000.mdio:01 not found on slave 1
  [   10.211356] [ cut here ]
  [   10.216201] kernel BUG at /build/buildd/linux-3.13.0/kernel/timer.c:1084!
  [   10.223280] Internal error: Oops - BUG: 0 [#1] SMP ARM
  [   10.228637] Modules linked in: tda998x tilcdc drm_kms_helper omap_sham drm 
omap_aes omap_rng tps65217 uio_pdrv_genirq uio leds_gpio nls1
  [   10.242317] CPU: 0 PID: 302 Comm: systemd-udevd Not tainted 
3.13.0-52-generic #86-Ubuntu
  [   10.250758] task: db1085c0 ti: db35c000 task.ti: db35c000
  [   10.256398] PC is at cascade+0x98/0x9c
  [   10.260305] LR is at cascade+0x80/0x9c
  [   10.264212] pc : [c0060ab4]lr : [c0060a9c]psr: 80030193
  [   10.264212] sp : db35dd18  ip : fffee500  fp : 00a9
  [   10.276182] r10: c0a78080  r9 : db35c000  r8 : db35dd58
  [   10.281627] r7 : 0025  r6 : db35dd18  r5 : c0b48a80  r4 : c0b493f4
  [   10.288432] r3 : db22b0a8  r2 : 002c  r1 : de217230  r0 : c0b493f4
  [   10.295239] Flags: Nzcv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment 
user
  [   10.302770] Control: 10c5387d  Table: 9b398019  DAC: 0015
  [   10.308760] Process systemd-udevd (pid: 302, stack limit = 0xdb35c238)
  [   10.315565] Stack: (0xdb35dd18 to 0xdb35e000)
  [   10.320107] dd00:   
db22b0a8 c0acd78c
  [   10.328637] dd20: c0a713b0 c0b48a80  0004 c0a78088 c0060ce4 
c0a713b8 c1024458
  [   10.337167] dd40: c1024490 00200200 c0b32c30 c0a780c0 c0b49294 c0b49494 
6071f4b5 0002
  [   10.345697] dd60: 6071f4b5 0001 0101 0004 c0a78088 c0a78084 
db35c000 c0a78080
  [   10.354226] dd80: 00a9 c0058bf8 0001 00015200 0100 0004 
c0a71540 c0b32ba4
  [   10.362756] dda0:  000a c0b48840 c0a780c0 fffee501 db35c008 
c0ac0360 00400140
  [   10.371285] ddc0: db1085c0 db35c028 0054  0054 01b8216c 
db1085c0 db1f08f8
  [   10.379816] dde0: 00a9 c005917c c0a73030 c0010420 fa20 c0b477ac 
db35de18 c00093f4
  [   10.388346] de00: c00975d4 c00975d4 60030113  db35de4c c06baac0 
db1f08fc 00030113
  [   10.396877] de20: db1f0900 02ef db1f08f8 db1f08fc 0001 0817 
01b8216c db1085c0
  [   10.405407] de40: db1f08f8 00a9  db35de60 c00975d4 c00975d4 
60030113 
  [   10.413938] de60: db35dfb0 db35c030 db1f08c0 c06bc098 0001 c0160cd4 
db320d80 db35dee8
  [   10.422468] de80: 0001 db320e90 0800    
0561 0001
  [   10.430997] dea0: 0561 007f db35df08 db35df00 00080001 0001 
db245010 
  [   10.439526] dec0: 0561  01b81be1  c0194868  
 db35dfb0
  [   10.448054] dee0: 0817 01b8216c 01b8216c db35dfb0 00020420 0581 
00b1 c06bc410
  [   10.456583] df00: 0817 c06bc3ac c0a84b98 c00091d4 0400  
ddc3f090 c015effc
  [   10.465111] df20:   0400  0400  
 2000
  [   10.473639] df40:  c0194974  db320e48 0400  
 
  [   10.482167] df60: be826bf8 be826bf8 0008   c015f14c 
 c015faac
  [   10.490695] df80: 2000   01b76468   
b6dbd3c6 20030030
  [   10.499223] dfa0:  0589 0588 c06bac38 0589  
0001fe99 01b82168
  [   10.507753] dfc0: 01b81be8 b6e4b4e8 01b81be0 0589 0588 00020420 
0581 00b1
  [   10.516281] dfe0: 0598 be826b68 b6dbf011 b6dbd3c6 20030030  
 
  [   10.524829] [c0060ab4] (cascade+0x98/0x9c) from [c0060ce4] 
(run_timer_softirq+0x22c/0x2b4)
  [   10.533821] [c0060ce4] (run_timer_softirq+0x22c/0x2b4) from [c0058bf8] 
(__do_softirq+0x144/0x340)
  [   

[Kernel-packages] [Bug 1381005] Re: Long stdin from terminal can result in code execution

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

Title:
  Long stdin from terminal can result in code execution

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Utopic:
  In Progress
Status in linux source package in Vivid:
  In Progress

Bug description:
  Under certain conditions, the input entered from a terminal with a
  foreground process waiting for stdin, can be interpreted and executed
  by the shell.

  Steps to reproduce:
  1) Open a terminal
  2) Run a simple program that waits for stdin (like cat, tee, head, tail, ...) 
or even the bash-builtin command read. No need to specify arguments
  3) Type or paste exactly 4096 ASCII characters into the terminal (see sample 
attachment)
  4) Press Enter

  What should happen:
  The program in foreground reads 4097 characters (the last one is new line).

  What actually happens:
  Instead of reading the input, the current program exits (read() only reads 
one character before EOF) and the shell executes the same input starting from 
the second character.

  I believe that the issue can be reproduced with:
  - any terminal (tested on xterm, gnome-terminal, tty)
  - any shell (tested on bash, zsh)
  - any program that reads stdin from terminal (not attached to a pipe)

  Debugging the shell with gdb suggests that the bug is in the implementation 
of read(), hence libc6 or under (kernel).
  Specifically, the bug is caused by read() reading only one character (new 
line) when entering a text of 4096 characters in stdin on the terminal. It 
looks like read() is then closing the stdin descriptor.
  If the input is 4097 characters long, read() will read two characters and the 
shell will interpret from the 3rd character, and so on.

  Verified on:
  Ubuntu 14.04.1 LTS

  Kernel:
  3.13.0-24-generic x86_64
  3.13.0-32-generic x86_64
  3.13.0-36-generic x86_64

  libc6:
  2.19-0ubuntu6
  2.19-0ubuntu6.1
  2.19-0ubuntu6.3

  I'm happy to provide more information if it helps.
  Angelo

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

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

[Kernel-packages] [Bug 1455121] Re: [SRU trusty] net/mlx4_core: Adjust command timeouts to conform to the firmware spec

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-trusty

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

Title:
  [SRU trusty] net/mlx4_core: Adjust command timeouts to conform to the
  firmware spec

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  On reboot, initialization commands can timeout causing the mellanox card to 
not initialize on boot.

  [Test Case]
  Reboot the system many, many times (this issue is rare).

  [Regression Risk]
  The fix comes from upstream and was submitted by Mellanox to bring the driver 
in-line with the way their firmware works.

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

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

[Kernel-packages] [Bug 1455372] Re: Trusty arm64 VM doesn't support 'reboot' and 'powerdown'

[Luis Henriques]

This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Summary changed:

- Trausty arm64 VM doesn't support 'reboot' and 'powerdown'
+ Trusty arm64 VM doesn't support 'reboot' and 'powerdown'

** Tags added: verification-needed-trusty

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

Title:
  Trusty arm64 VM doesn't support 'reboot' and 'powerdown'

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  Trusty arm64/arm kernel can't support reboot and powerdown function.

  If user runs 'reboot', then finally the VM hangs in the last step
  instead of going another booting, and similar problem exists during
  powerdown.

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

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

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

[John Johansen]

No CVEs

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress = Invalid

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow package-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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.13.0-54.91~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Wednesday, 27. May 2015 02:01 UTC
  kernel-stable-master-bug:1458618
  kernel-stable-Prepare-package-end:Wednesday, 27. May 2015 18:01 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 27. May 2015 18:01 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:12 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:30 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:30 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:30 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:30 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:30 UTC

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

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

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

[John Johansen]

No CVEs

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress = Invalid

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow package-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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.16.0-39.53~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, 26. May 2015 19:00 UTC
  kernel-stable-master-bug:1458778
  kernel-stable-Prepare-package-end:Wednesday, 27. May 2015 19:01 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 27. May 2015 19:01 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:00 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:01 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:01 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:01 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:01 UTC

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

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

[Kernel-packages] [Bug 1458999] Re: linux-ti-omap4: 3.2.0-1465.85 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the version to be filled 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, 26. May 2015 20:03 UTC
  kernel-stable-master-bug:1458901
  kernel-stable-Certification-testing-end:Friday, 29. May 2015 09:00 UTC
  kernel-stable-Prepare-package-end:Friday, 29. May 2015 12:01 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 29. May 2015 12:01 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 21:29 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 23:01 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 23:01 UTC
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 23:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 23:01 UTC
+ kernel-stable-Security-signoff-end:Monday, 01. June 2015 09:00 UTC

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

Title:
  linux-ti-omap4: 3.2.0-1465.85 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow package-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 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:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  Fix Released
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New

Bug description:
  This bug is for tracking the version to be filled 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, 26. May 2015 20:03 UTC
  kernel-stable-master-bug:1458901
  kernel-stable-Certification-testing-end:Friday, 29. May 2015 09:00 UTC
  kernel-stable-Prepare-package-end:Friday, 29. May 2015 12:01 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 29. May 2015 12:01 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 21:29 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 23:01 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 23:01 UTC
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 23:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 23:01 UTC
  kernel-stable-Security-signoff-end:Monday, 01. June 2015 09:00 UTC

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

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

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

[Brad Figg]

** Description changed:

  This bug is for tracking the 3.13.0-54.91~precise1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Wednesday, 27. May 2015 02:01 UTC
  kernel-stable-master-bug:1458618
  kernel-stable-Prepare-package-end:Wednesday, 27. May 2015 18:01 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 27. May 2015 18:01 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:12 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:30 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:30 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:30 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:30 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:30 UTC
+ kernel-stable-Security-signoff-end:Monday, 01. June 2015 09:01 UTC

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow package-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:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

Bug description:
  This bug is for tracking the 3.13.0-54.91~precise1 upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Wednesday, 27. May 2015 02:01 UTC
  kernel-stable-master-bug:1458618
  kernel-stable-Prepare-package-end:Wednesday, 27. May 2015 18:01 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 27. May 2015 18:01 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 29. May 2015 20:12 UTC
  kernel-stable-phase:Verification  Testing
  kernel-stable-phase-changed:Friday, 29. May 2015 21:30 UTC
  kernel-stable-Verification-testing-start:Friday, 29. May 2015 21:30 UTC
  kernel-stable-Certification-testing-start:Friday, 29. May 2015 21:30 UTC
  kernel-stable-Security-signoff-start:Friday, 29. May 2015 21:30 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Friday, 29. May 2015 21:30 UTC
  kernel-stable-Security-signoff-end:Monday, 01. June 2015 09:01 UTC

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

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

[Kernel-packages] [Bug 1460402] UdevLog.txt

[Gabriel Pérez]

apport information

** Attachment added: UdevLog.txt
   
https://bugs.launchpad.net/bugs/1460402/+attachment/4407923/+files/UdevLog.txt

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

Title:
  FS-Cache: Assertion failed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Happens in two nodes at the same time.

  Node 1:

  [205458.631304] [ cut here ]
  [205458.633636] kernel BUG at 
/build/buildd/linux-3.13.0/fs/fscache/page.c:244!
  [205458.633636] invalid opcode:  [#1] SMP 
  [205458.633636] Modules linked in: veth xt_nat xt_tcpudp xt_addrtype 
xt_conntrack ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp 
llc dm_thin_pool dm_persistent_data dm_bufio dm_bio_prison libcrc32c cachefiles 
nfsv3 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt syscopyarea 
sysfillrect sysimgblt fb_sys_fops serio_raw isofs crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd floppy psmouse
  [205458.633636] CPU: 3 PID: 6217 Comm: php5-fpm Not tainted 3.13.0-53-generic 
#89-Ubuntu
  [205458.633636] Hardware name: Xen HVM domU, BIOS 4.2.amazon 05/06/2015
  [205458.633636] task: 8801e3ede000 ti: 880107ace000 task.ti: 
880107ace000
  [205458.633636] RIP: 0010:[a00b8c14]  [a00b8c14] 
fscache_release_retrieval_op+0x74/0x80 [fscache]
  [205458.633636] RSP: 0018:880107acfad8  EFLAGS: 00010286
  [205458.633636] RAX: 000f RBX: 880014be1a80 RCX: 

  [205458.633636] RDX: 8801efc6f020 RSI: 8801efc6d408 RDI: 
0246
  [205458.633636] RBP: 880107acfae0 R08: 0096 R09: 
0231
  [205458.633636] R10: 8185ade0 R11: 880107acf806 R12: 
8800c3e469f8
  [205458.633636] R13: 880107acfbbc R14: ff97 R15: 
8801e3ff9b68
  [205458.633636] FS:  7f383346c740() GS:8801efc6() 
knlGS:
  [205458.633636] CS:  0010 DS:  ES:  CR0: 80050033
  [205458.633636] CR2: 7f382032cf08 CR3: 0001206ea000 CR4: 
001406e0
  [205458.633636] Stack:
  [205458.633636]  880014be1a80 880107acfb08 a00b6eab 
880014be1a80
  [205458.633636]  8800c3e469f8 880107acfbbc 880107acfb58 
a00b9753
  [205458.633636]  8800c3e46a00 8801e3ff9b00 880107acfcb8 
ff97
  [205458.633636] Call Trace:
  [205458.633636]  [a00b6eab] fscache_put_operation+0x5b/0x220 
[fscache]
  [205458.633636]  [a00b9753] 
__fscache_read_or_alloc_pages+0x1b3/0x350 [fscache]
  [205458.633636]  [a01645c1] __nfs_readpages_from_fscache+0x71/0x1b0 
[nfs]
  [205458.633636]  [a015b7b8] nfs_readpages+0xa8/0x190 [nfs]
  [205458.633636]  [81197c53] ? alloc_pages_current+0xa3/0x160
  [205458.633636]  [8114f757] ? __page_cache_alloc+0x97/0xc0
  [205458.633636]  [8115ba39] __do_page_cache_readahead+0x1b9/0x260
  [205458.633636]  [8115bf12] ondemand_readahead+0x152/0x2a0
  [205458.633636]  [8115c091] page_cache_sync_readahead+0x31/0x50
  [205458.633636]  [81151b65] generic_file_aio_read+0x4c5/0x700
  [205458.633636]  [a0150949] nfs_file_read+0x69/0xf0 [nfs]
  [205458.633636]  [811bd8ba] do_sync_read+0x5a/0x90
  [205458.633636]  [811bdf55] vfs_read+0x95/0x160
  [205458.633636]  [811bea69] SyS_read+0x49/0xa0
  [205458.633636]  [8173391d] system_call_fastpath+0x1a/0x1f
  [205458.633636] Code: c0 e8 92 3b 66 e1 48 c7 c7 ae cc 0b a0 31 c0 e8 84 3b 
66 e1 48 63 b3 90 00 00 00 31 d2 48 c7 c7 e3 cc 0b a0 31 c0 e8 6d 3b 66 e1 0f 
0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 
  [205458.633636] RIP  [a00b8c14] 
fscache_release_retrieval_op+0x74/0x80 [fscache]
  [205458.633636]  RSP 880107acfad8
  [205458.833163] ---[ end trace 30960a6ba86a197f ]---

  Node 2:

  [360136.745210] FS-Cache: Assertion failed
  [360136.747121] 1 == 0 is false
  [360136.748704] [ cut here ]
  [360136.751217] kernel BUG at 
/build/buildd/linux-3.13.0/fs/fscache/page.c:244!
  [360136.752666] invalid opcode:  [#1] SMP 
  [360136.752666] Modules linked in: veth xt_nat xt_tcpudp xt_addrtype 
xt_conntrack ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp 
llc dm_thin_pool dm_persistent_data dm_bufio dm_bio_prison libcrc32c cachefiles 
nfsv3 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt syscopyarea 
sysfillrect sysimgblt fb_sys_fops serio_raw isofs crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
  [360136.752666] CPU: 2 PID: 7105 

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

[Gabriel Pérez]

apport information

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

Title:
  FS-Cache: Assertion failed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Happens in two nodes at the same time.

  Node 1:

  [205458.631304] [ cut here ]
  [205458.633636] kernel BUG at 
/build/buildd/linux-3.13.0/fs/fscache/page.c:244!
  [205458.633636] invalid opcode:  [#1] SMP 
  [205458.633636] Modules linked in: veth xt_nat xt_tcpudp xt_addrtype 
xt_conntrack ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp 
llc dm_thin_pool dm_persistent_data dm_bufio dm_bio_prison libcrc32c cachefiles 
nfsv3 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt syscopyarea 
sysfillrect sysimgblt fb_sys_fops serio_raw isofs crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd floppy psmouse
  [205458.633636] CPU: 3 PID: 6217 Comm: php5-fpm Not tainted 3.13.0-53-generic 
#89-Ubuntu
  [205458.633636] Hardware name: Xen HVM domU, BIOS 4.2.amazon 05/06/2015
  [205458.633636] task: 8801e3ede000 ti: 880107ace000 task.ti: 
880107ace000
  [205458.633636] RIP: 0010:[a00b8c14]  [a00b8c14] 
fscache_release_retrieval_op+0x74/0x80 [fscache]
  [205458.633636] RSP: 0018:880107acfad8  EFLAGS: 00010286
  [205458.633636] RAX: 000f RBX: 880014be1a80 RCX: 

  [205458.633636] RDX: 8801efc6f020 RSI: 8801efc6d408 RDI: 
0246
  [205458.633636] RBP: 880107acfae0 R08: 0096 R09: 
0231
  [205458.633636] R10: 8185ade0 R11: 880107acf806 R12: 
8800c3e469f8
  [205458.633636] R13: 880107acfbbc R14: ff97 R15: 
8801e3ff9b68
  [205458.633636] FS:  7f383346c740() GS:8801efc6() 
knlGS:
  [205458.633636] CS:  0010 DS:  ES:  CR0: 80050033
  [205458.633636] CR2: 7f382032cf08 CR3: 0001206ea000 CR4: 
001406e0
  [205458.633636] Stack:
  [205458.633636]  880014be1a80 880107acfb08 a00b6eab 
880014be1a80
  [205458.633636]  8800c3e469f8 880107acfbbc 880107acfb58 
a00b9753
  [205458.633636]  8800c3e46a00 8801e3ff9b00 880107acfcb8 
ff97
  [205458.633636] Call Trace:
  [205458.633636]  [a00b6eab] fscache_put_operation+0x5b/0x220 
[fscache]
  [205458.633636]  [a00b9753] 
__fscache_read_or_alloc_pages+0x1b3/0x350 [fscache]
  [205458.633636]  [a01645c1] __nfs_readpages_from_fscache+0x71/0x1b0 
[nfs]
  [205458.633636]  [a015b7b8] nfs_readpages+0xa8/0x190 [nfs]
  [205458.633636]  [81197c53] ? alloc_pages_current+0xa3/0x160
  [205458.633636]  [8114f757] ? __page_cache_alloc+0x97/0xc0
  [205458.633636]  [8115ba39] __do_page_cache_readahead+0x1b9/0x260
  [205458.633636]  [8115bf12] ondemand_readahead+0x152/0x2a0
  [205458.633636]  [8115c091] page_cache_sync_readahead+0x31/0x50
  [205458.633636]  [81151b65] generic_file_aio_read+0x4c5/0x700
  [205458.633636]  [a0150949] nfs_file_read+0x69/0xf0 [nfs]
  [205458.633636]  [811bd8ba] do_sync_read+0x5a/0x90
  [205458.633636]  [811bdf55] vfs_read+0x95/0x160
  [205458.633636]  [811bea69] SyS_read+0x49/0xa0
  [205458.633636]  [8173391d] system_call_fastpath+0x1a/0x1f
  [205458.633636] Code: c0 e8 92 3b 66 e1 48 c7 c7 ae cc 0b a0 31 c0 e8 84 3b 
66 e1 48 63 b3 90 00 00 00 31 d2 48 c7 c7 e3 cc 0b a0 31 c0 e8 6d 3b 66 e1 0f 
0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 
  [205458.633636] RIP  [a00b8c14] 
fscache_release_retrieval_op+0x74/0x80 [fscache]
  [205458.633636]  RSP 880107acfad8
  [205458.833163] ---[ end trace 30960a6ba86a197f ]---

  Node 2:

  [360136.745210] FS-Cache: Assertion failed
  [360136.747121] 1 == 0 is false
  [360136.748704] [ cut here ]
  [360136.751217] kernel BUG at 
/build/buildd/linux-3.13.0/fs/fscache/page.c:244!
  [360136.752666] invalid opcode:  [#1] SMP 
  [360136.752666] Modules linked in: veth xt_nat xt_tcpudp xt_addrtype 
xt_conntrack ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp 
llc dm_thin_pool dm_persistent_data dm_bufio dm_bio_prison libcrc32c cachefiles 
nfsv3 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt syscopyarea 
sysfillrect sysimgblt fb_sys_fops serio_raw isofs crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
  [360136.752666] CPU: 2 

[Kernel-packages] [Bug 1460402] Re: FS-Cache: Assertion failed

[Gabriel Pérez]

apport information

** Tags added: apport-collected ec2-images

** Description changed:

  Happens in two nodes at the same time.
  
  Node 1:
  
  [205458.631304] [ cut here ]
  [205458.633636] kernel BUG at 
/build/buildd/linux-3.13.0/fs/fscache/page.c:244!
  [205458.633636] invalid opcode:  [#1] SMP 
  [205458.633636] Modules linked in: veth xt_nat xt_tcpudp xt_addrtype 
xt_conntrack ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp 
llc dm_thin_pool dm_persistent_data dm_bufio dm_bio_prison libcrc32c cachefiles 
nfsv3 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt syscopyarea 
sysfillrect sysimgblt fb_sys_fops serio_raw isofs crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd floppy psmouse
  [205458.633636] CPU: 3 PID: 6217 Comm: php5-fpm Not tainted 3.13.0-53-generic 
#89-Ubuntu
  [205458.633636] Hardware name: Xen HVM domU, BIOS 4.2.amazon 05/06/2015
  [205458.633636] task: 8801e3ede000 ti: 880107ace000 task.ti: 
880107ace000
  [205458.633636] RIP: 0010:[a00b8c14]  [a00b8c14] 
fscache_release_retrieval_op+0x74/0x80 [fscache]
  [205458.633636] RSP: 0018:880107acfad8  EFLAGS: 00010286
  [205458.633636] RAX: 000f RBX: 880014be1a80 RCX: 

  [205458.633636] RDX: 8801efc6f020 RSI: 8801efc6d408 RDI: 
0246
  [205458.633636] RBP: 880107acfae0 R08: 0096 R09: 
0231
  [205458.633636] R10: 8185ade0 R11: 880107acf806 R12: 
8800c3e469f8
  [205458.633636] R13: 880107acfbbc R14: ff97 R15: 
8801e3ff9b68
  [205458.633636] FS:  7f383346c740() GS:8801efc6() 
knlGS:
  [205458.633636] CS:  0010 DS:  ES:  CR0: 80050033
  [205458.633636] CR2: 7f382032cf08 CR3: 0001206ea000 CR4: 
001406e0
  [205458.633636] Stack:
  [205458.633636]  880014be1a80 880107acfb08 a00b6eab 
880014be1a80
  [205458.633636]  8800c3e469f8 880107acfbbc 880107acfb58 
a00b9753
  [205458.633636]  8800c3e46a00 8801e3ff9b00 880107acfcb8 
ff97
  [205458.633636] Call Trace:
  [205458.633636]  [a00b6eab] fscache_put_operation+0x5b/0x220 
[fscache]
  [205458.633636]  [a00b9753] 
__fscache_read_or_alloc_pages+0x1b3/0x350 [fscache]
  [205458.633636]  [a01645c1] __nfs_readpages_from_fscache+0x71/0x1b0 
[nfs]
  [205458.633636]  [a015b7b8] nfs_readpages+0xa8/0x190 [nfs]
  [205458.633636]  [81197c53] ? alloc_pages_current+0xa3/0x160
  [205458.633636]  [8114f757] ? __page_cache_alloc+0x97/0xc0
  [205458.633636]  [8115ba39] __do_page_cache_readahead+0x1b9/0x260
  [205458.633636]  [8115bf12] ondemand_readahead+0x152/0x2a0
  [205458.633636]  [8115c091] page_cache_sync_readahead+0x31/0x50
  [205458.633636]  [81151b65] generic_file_aio_read+0x4c5/0x700
  [205458.633636]  [a0150949] nfs_file_read+0x69/0xf0 [nfs]
  [205458.633636]  [811bd8ba] do_sync_read+0x5a/0x90
  [205458.633636]  [811bdf55] vfs_read+0x95/0x160
  [205458.633636]  [811bea69] SyS_read+0x49/0xa0
  [205458.633636]  [8173391d] system_call_fastpath+0x1a/0x1f
  [205458.633636] Code: c0 e8 92 3b 66 e1 48 c7 c7 ae cc 0b a0 31 c0 e8 84 3b 
66 e1 48 63 b3 90 00 00 00 31 d2 48 c7 c7 e3 cc 0b a0 31 c0 e8 6d 3b 66 e1 0f 
0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 
  [205458.633636] RIP  [a00b8c14] 
fscache_release_retrieval_op+0x74/0x80 [fscache]
  [205458.633636]  RSP 880107acfad8
  [205458.833163] ---[ end trace 30960a6ba86a197f ]---
  
  Node 2:
  
  [360136.745210] FS-Cache: Assertion failed
  [360136.747121] 1 == 0 is false
  [360136.748704] [ cut here ]
  [360136.751217] kernel BUG at 
/build/buildd/linux-3.13.0/fs/fscache/page.c:244!
  [360136.752666] invalid opcode:  [#1] SMP 
  [360136.752666] Modules linked in: veth xt_nat xt_tcpudp xt_addrtype 
xt_conntrack ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp 
llc dm_thin_pool dm_persistent_data dm_bufio dm_bio_prison libcrc32c cachefiles 
nfsv3 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt syscopyarea 
sysfillrect sysimgblt fb_sys_fops serio_raw isofs crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
  [360136.752666] CPU: 2 PID: 7105 Comm: php5-fpm Not tainted 3.13.0-53-generic 
#89-Ubuntu
  [360136.752666] Hardware name: Xen HVM domU, BIOS 4.2.amazon 05/06/2015
  [360136.752666] task: 880116254800 ti: 88010cb8a000 task.ti: 
88010cb8a000
  [360136.752666] RIP: 0010:[a00b1c14]  [a00b1c14] 

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

[Gabriel Pérez]

apport information

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

Title:
  FS-Cache: Assertion failed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Happens in two nodes at the same time.

  Node 1:

  [205458.631304] [ cut here ]
  [205458.633636] kernel BUG at 
/build/buildd/linux-3.13.0/fs/fscache/page.c:244!
  [205458.633636] invalid opcode:  [#1] SMP 
  [205458.633636] Modules linked in: veth xt_nat xt_tcpudp xt_addrtype 
xt_conntrack ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp 
llc dm_thin_pool dm_persistent_data dm_bufio dm_bio_prison libcrc32c cachefiles 
nfsv3 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt syscopyarea 
sysfillrect sysimgblt fb_sys_fops serio_raw isofs crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd floppy psmouse
  [205458.633636] CPU: 3 PID: 6217 Comm: php5-fpm Not tainted 3.13.0-53-generic 
#89-Ubuntu
  [205458.633636] Hardware name: Xen HVM domU, BIOS 4.2.amazon 05/06/2015
  [205458.633636] task: 8801e3ede000 ti: 880107ace000 task.ti: 
880107ace000
  [205458.633636] RIP: 0010:[a00b8c14]  [a00b8c14] 
fscache_release_retrieval_op+0x74/0x80 [fscache]
  [205458.633636] RSP: 0018:880107acfad8  EFLAGS: 00010286
  [205458.633636] RAX: 000f RBX: 880014be1a80 RCX: 

  [205458.633636] RDX: 8801efc6f020 RSI: 8801efc6d408 RDI: 
0246
  [205458.633636] RBP: 880107acfae0 R08: 0096 R09: 
0231
  [205458.633636] R10: 8185ade0 R11: 880107acf806 R12: 
8800c3e469f8
  [205458.633636] R13: 880107acfbbc R14: ff97 R15: 
8801e3ff9b68
  [205458.633636] FS:  7f383346c740() GS:8801efc6() 
knlGS:
  [205458.633636] CS:  0010 DS:  ES:  CR0: 80050033
  [205458.633636] CR2: 7f382032cf08 CR3: 0001206ea000 CR4: 
001406e0
  [205458.633636] Stack:
  [205458.633636]  880014be1a80 880107acfb08 a00b6eab 
880014be1a80
  [205458.633636]  8800c3e469f8 880107acfbbc 880107acfb58 
a00b9753
  [205458.633636]  8800c3e46a00 8801e3ff9b00 880107acfcb8 
ff97
  [205458.633636] Call Trace:
  [205458.633636]  [a00b6eab] fscache_put_operation+0x5b/0x220 
[fscache]
  [205458.633636]  [a00b9753] 
__fscache_read_or_alloc_pages+0x1b3/0x350 [fscache]
  [205458.633636]  [a01645c1] __nfs_readpages_from_fscache+0x71/0x1b0 
[nfs]
  [205458.633636]  [a015b7b8] nfs_readpages+0xa8/0x190 [nfs]
  [205458.633636]  [81197c53] ? alloc_pages_current+0xa3/0x160
  [205458.633636]  [8114f757] ? __page_cache_alloc+0x97/0xc0
  [205458.633636]  [8115ba39] __do_page_cache_readahead+0x1b9/0x260
  [205458.633636]  [8115bf12] ondemand_readahead+0x152/0x2a0
  [205458.633636]  [8115c091] page_cache_sync_readahead+0x31/0x50
  [205458.633636]  [81151b65] generic_file_aio_read+0x4c5/0x700
  [205458.633636]  [a0150949] nfs_file_read+0x69/0xf0 [nfs]
  [205458.633636]  [811bd8ba] do_sync_read+0x5a/0x90
  [205458.633636]  [811bdf55] vfs_read+0x95/0x160
  [205458.633636]  [811bea69] SyS_read+0x49/0xa0
  [205458.633636]  [8173391d] system_call_fastpath+0x1a/0x1f
  [205458.633636] Code: c0 e8 92 3b 66 e1 48 c7 c7 ae cc 0b a0 31 c0 e8 84 3b 
66 e1 48 63 b3 90 00 00 00 31 d2 48 c7 c7 e3 cc 0b a0 31 c0 e8 6d 3b 66 e1 0f 
0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 
  [205458.633636] RIP  [a00b8c14] 
fscache_release_retrieval_op+0x74/0x80 [fscache]
  [205458.633636]  RSP 880107acfad8
  [205458.833163] ---[ end trace 30960a6ba86a197f ]---

  Node 2:

  [360136.745210] FS-Cache: Assertion failed
  [360136.747121] 1 == 0 is false
  [360136.748704] [ cut here ]
  [360136.751217] kernel BUG at 
/build/buildd/linux-3.13.0/fs/fscache/page.c:244!
  [360136.752666] invalid opcode:  [#1] SMP 
  [360136.752666] Modules linked in: veth xt_nat xt_tcpudp xt_addrtype 
xt_conntrack ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp 
llc dm_thin_pool dm_persistent_data dm_bufio dm_bio_prison libcrc32c cachefiles 
nfsv3 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt syscopyarea 
sysfillrect sysimgblt fb_sys_fops serio_raw isofs crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
  [360136.752666] CPU: 2 PID: 7105 

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

[Gabriel Pérez]

apport information

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

Title:
  FS-Cache: Assertion failed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Happens in two nodes at the same time.

  Node 1:

  [205458.631304] [ cut here ]
  [205458.633636] kernel BUG at 
/build/buildd/linux-3.13.0/fs/fscache/page.c:244!
  [205458.633636] invalid opcode:  [#1] SMP 
  [205458.633636] Modules linked in: veth xt_nat xt_tcpudp xt_addrtype 
xt_conntrack ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp 
llc dm_thin_pool dm_persistent_data dm_bufio dm_bio_prison libcrc32c cachefiles 
nfsv3 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt syscopyarea 
sysfillrect sysimgblt fb_sys_fops serio_raw isofs crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd floppy psmouse
  [205458.633636] CPU: 3 PID: 6217 Comm: php5-fpm Not tainted 3.13.0-53-generic 
#89-Ubuntu
  [205458.633636] Hardware name: Xen HVM domU, BIOS 4.2.amazon 05/06/2015
  [205458.633636] task: 8801e3ede000 ti: 880107ace000 task.ti: 
880107ace000
  [205458.633636] RIP: 0010:[a00b8c14]  [a00b8c14] 
fscache_release_retrieval_op+0x74/0x80 [fscache]
  [205458.633636] RSP: 0018:880107acfad8  EFLAGS: 00010286
  [205458.633636] RAX: 000f RBX: 880014be1a80 RCX: 

  [205458.633636] RDX: 8801efc6f020 RSI: 8801efc6d408 RDI: 
0246
  [205458.633636] RBP: 880107acfae0 R08: 0096 R09: 
0231
  [205458.633636] R10: 8185ade0 R11: 880107acf806 R12: 
8800c3e469f8
  [205458.633636] R13: 880107acfbbc R14: ff97 R15: 
8801e3ff9b68
  [205458.633636] FS:  7f383346c740() GS:8801efc6() 
knlGS:
  [205458.633636] CS:  0010 DS:  ES:  CR0: 80050033
  [205458.633636] CR2: 7f382032cf08 CR3: 0001206ea000 CR4: 
001406e0
  [205458.633636] Stack:
  [205458.633636]  880014be1a80 880107acfb08 a00b6eab 
880014be1a80
  [205458.633636]  8800c3e469f8 880107acfbbc 880107acfb58 
a00b9753
  [205458.633636]  8800c3e46a00 8801e3ff9b00 880107acfcb8 
ff97
  [205458.633636] Call Trace:
  [205458.633636]  [a00b6eab] fscache_put_operation+0x5b/0x220 
[fscache]
  [205458.633636]  [a00b9753] 
__fscache_read_or_alloc_pages+0x1b3/0x350 [fscache]
  [205458.633636]  [a01645c1] __nfs_readpages_from_fscache+0x71/0x1b0 
[nfs]
  [205458.633636]  [a015b7b8] nfs_readpages+0xa8/0x190 [nfs]
  [205458.633636]  [81197c53] ? alloc_pages_current+0xa3/0x160
  [205458.633636]  [8114f757] ? __page_cache_alloc+0x97/0xc0
  [205458.633636]  [8115ba39] __do_page_cache_readahead+0x1b9/0x260
  [205458.633636]  [8115bf12] ondemand_readahead+0x152/0x2a0
  [205458.633636]  [8115c091] page_cache_sync_readahead+0x31/0x50
  [205458.633636]  [81151b65] generic_file_aio_read+0x4c5/0x700
  [205458.633636]  [a0150949] nfs_file_read+0x69/0xf0 [nfs]
  [205458.633636]  [811bd8ba] do_sync_read+0x5a/0x90
  [205458.633636]  [811bdf55] vfs_read+0x95/0x160
  [205458.633636]  [811bea69] SyS_read+0x49/0xa0
  [205458.633636]  [8173391d] system_call_fastpath+0x1a/0x1f
  [205458.633636] Code: c0 e8 92 3b 66 e1 48 c7 c7 ae cc 0b a0 31 c0 e8 84 3b 
66 e1 48 63 b3 90 00 00 00 31 d2 48 c7 c7 e3 cc 0b a0 31 c0 e8 6d 3b 66 e1 0f 
0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 
  [205458.633636] RIP  [a00b8c14] 
fscache_release_retrieval_op+0x74/0x80 [fscache]
  [205458.633636]  RSP 880107acfad8
  [205458.833163] ---[ end trace 30960a6ba86a197f ]---

  Node 2:

  [360136.745210] FS-Cache: Assertion failed
  [360136.747121] 1 == 0 is false
  [360136.748704] [ cut here ]
  [360136.751217] kernel BUG at 
/build/buildd/linux-3.13.0/fs/fscache/page.c:244!
  [360136.752666] invalid opcode:  [#1] SMP 
  [360136.752666] Modules linked in: veth xt_nat xt_tcpudp xt_addrtype 
xt_conntrack ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp 
llc dm_thin_pool dm_persistent_data dm_bufio dm_bio_prison libcrc32c cachefiles 
nfsv3 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt syscopyarea 
sysfillrect sysimgblt fb_sys_fops serio_raw isofs crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
  [360136.752666] CPU: 2 

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

[Gabriel Pérez]

apport information

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

Title:
  FS-Cache: Assertion failed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Happens in two nodes at the same time.

  Node 1:

  [205458.631304] [ cut here ]
  [205458.633636] kernel BUG at 
/build/buildd/linux-3.13.0/fs/fscache/page.c:244!
  [205458.633636] invalid opcode:  [#1] SMP 
  [205458.633636] Modules linked in: veth xt_nat xt_tcpudp xt_addrtype 
xt_conntrack ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp 
llc dm_thin_pool dm_persistent_data dm_bufio dm_bio_prison libcrc32c cachefiles 
nfsv3 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt syscopyarea 
sysfillrect sysimgblt fb_sys_fops serio_raw isofs crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd floppy psmouse
  [205458.633636] CPU: 3 PID: 6217 Comm: php5-fpm Not tainted 3.13.0-53-generic 
#89-Ubuntu
  [205458.633636] Hardware name: Xen HVM domU, BIOS 4.2.amazon 05/06/2015
  [205458.633636] task: 8801e3ede000 ti: 880107ace000 task.ti: 
880107ace000
  [205458.633636] RIP: 0010:[a00b8c14]  [a00b8c14] 
fscache_release_retrieval_op+0x74/0x80 [fscache]
  [205458.633636] RSP: 0018:880107acfad8  EFLAGS: 00010286
  [205458.633636] RAX: 000f RBX: 880014be1a80 RCX: 

  [205458.633636] RDX: 8801efc6f020 RSI: 8801efc6d408 RDI: 
0246
  [205458.633636] RBP: 880107acfae0 R08: 0096 R09: 
0231
  [205458.633636] R10: 8185ade0 R11: 880107acf806 R12: 
8800c3e469f8
  [205458.633636] R13: 880107acfbbc R14: ff97 R15: 
8801e3ff9b68
  [205458.633636] FS:  7f383346c740() GS:8801efc6() 
knlGS:
  [205458.633636] CS:  0010 DS:  ES:  CR0: 80050033
  [205458.633636] CR2: 7f382032cf08 CR3: 0001206ea000 CR4: 
001406e0
  [205458.633636] Stack:
  [205458.633636]  880014be1a80 880107acfb08 a00b6eab 
880014be1a80
  [205458.633636]  8800c3e469f8 880107acfbbc 880107acfb58 
a00b9753
  [205458.633636]  8800c3e46a00 8801e3ff9b00 880107acfcb8 
ff97
  [205458.633636] Call Trace:
  [205458.633636]  [a00b6eab] fscache_put_operation+0x5b/0x220 
[fscache]
  [205458.633636]  [a00b9753] 
__fscache_read_or_alloc_pages+0x1b3/0x350 [fscache]
  [205458.633636]  [a01645c1] __nfs_readpages_from_fscache+0x71/0x1b0 
[nfs]
  [205458.633636]  [a015b7b8] nfs_readpages+0xa8/0x190 [nfs]
  [205458.633636]  [81197c53] ? alloc_pages_current+0xa3/0x160
  [205458.633636]  [8114f757] ? __page_cache_alloc+0x97/0xc0
  [205458.633636]  [8115ba39] __do_page_cache_readahead+0x1b9/0x260
  [205458.633636]  [8115bf12] ondemand_readahead+0x152/0x2a0
  [205458.633636]  [8115c091] page_cache_sync_readahead+0x31/0x50
  [205458.633636]  [81151b65] generic_file_aio_read+0x4c5/0x700
  [205458.633636]  [a0150949] nfs_file_read+0x69/0xf0 [nfs]
  [205458.633636]  [811bd8ba] do_sync_read+0x5a/0x90
  [205458.633636]  [811bdf55] vfs_read+0x95/0x160
  [205458.633636]  [811bea69] SyS_read+0x49/0xa0
  [205458.633636]  [8173391d] system_call_fastpath+0x1a/0x1f
  [205458.633636] Code: c0 e8 92 3b 66 e1 48 c7 c7 ae cc 0b a0 31 c0 e8 84 3b 
66 e1 48 63 b3 90 00 00 00 31 d2 48 c7 c7 e3 cc 0b a0 31 c0 e8 6d 3b 66 e1 0f 
0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 
  [205458.633636] RIP  [a00b8c14] 
fscache_release_retrieval_op+0x74/0x80 [fscache]
  [205458.633636]  RSP 880107acfad8
  [205458.833163] ---[ end trace 30960a6ba86a197f ]---

  Node 2:

  [360136.745210] FS-Cache: Assertion failed
  [360136.747121] 1 == 0 is false
  [360136.748704] [ cut here ]
  [360136.751217] kernel BUG at 
/build/buildd/linux-3.13.0/fs/fscache/page.c:244!
  [360136.752666] invalid opcode:  [#1] SMP 
  [360136.752666] Modules linked in: veth xt_nat xt_tcpudp xt_addrtype 
xt_conntrack ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp 
llc dm_thin_pool dm_persistent_data dm_bufio dm_bio_prison libcrc32c cachefiles 
nfsv3 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt syscopyarea 
sysfillrect sysimgblt fb_sys_fops serio_raw isofs crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
  [360136.752666] CPU: 2 PID: 7105 Comm: 

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

[Gabriel Pérez]

apport information

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

Title:
  FS-Cache: Assertion failed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Happens in two nodes at the same time.

  Node 1:

  [205458.631304] [ cut here ]
  [205458.633636] kernel BUG at 
/build/buildd/linux-3.13.0/fs/fscache/page.c:244!
  [205458.633636] invalid opcode:  [#1] SMP 
  [205458.633636] Modules linked in: veth xt_nat xt_tcpudp xt_addrtype 
xt_conntrack ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp 
llc dm_thin_pool dm_persistent_data dm_bufio dm_bio_prison libcrc32c cachefiles 
nfsv3 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt syscopyarea 
sysfillrect sysimgblt fb_sys_fops serio_raw isofs crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd floppy psmouse
  [205458.633636] CPU: 3 PID: 6217 Comm: php5-fpm Not tainted 3.13.0-53-generic 
#89-Ubuntu
  [205458.633636] Hardware name: Xen HVM domU, BIOS 4.2.amazon 05/06/2015
  [205458.633636] task: 8801e3ede000 ti: 880107ace000 task.ti: 
880107ace000
  [205458.633636] RIP: 0010:[a00b8c14]  [a00b8c14] 
fscache_release_retrieval_op+0x74/0x80 [fscache]
  [205458.633636] RSP: 0018:880107acfad8  EFLAGS: 00010286
  [205458.633636] RAX: 000f RBX: 880014be1a80 RCX: 

  [205458.633636] RDX: 8801efc6f020 RSI: 8801efc6d408 RDI: 
0246
  [205458.633636] RBP: 880107acfae0 R08: 0096 R09: 
0231
  [205458.633636] R10: 8185ade0 R11: 880107acf806 R12: 
8800c3e469f8
  [205458.633636] R13: 880107acfbbc R14: ff97 R15: 
8801e3ff9b68
  [205458.633636] FS:  7f383346c740() GS:8801efc6() 
knlGS:
  [205458.633636] CS:  0010 DS:  ES:  CR0: 80050033
  [205458.633636] CR2: 7f382032cf08 CR3: 0001206ea000 CR4: 
001406e0
  [205458.633636] Stack:
  [205458.633636]  880014be1a80 880107acfb08 a00b6eab 
880014be1a80
  [205458.633636]  8800c3e469f8 880107acfbbc 880107acfb58 
a00b9753
  [205458.633636]  8800c3e46a00 8801e3ff9b00 880107acfcb8 
ff97
  [205458.633636] Call Trace:
  [205458.633636]  [a00b6eab] fscache_put_operation+0x5b/0x220 
[fscache]
  [205458.633636]  [a00b9753] 
__fscache_read_or_alloc_pages+0x1b3/0x350 [fscache]
  [205458.633636]  [a01645c1] __nfs_readpages_from_fscache+0x71/0x1b0 
[nfs]
  [205458.633636]  [a015b7b8] nfs_readpages+0xa8/0x190 [nfs]
  [205458.633636]  [81197c53] ? alloc_pages_current+0xa3/0x160
  [205458.633636]  [8114f757] ? __page_cache_alloc+0x97/0xc0
  [205458.633636]  [8115ba39] __do_page_cache_readahead+0x1b9/0x260
  [205458.633636]  [8115bf12] ondemand_readahead+0x152/0x2a0
  [205458.633636]  [8115c091] page_cache_sync_readahead+0x31/0x50
  [205458.633636]  [81151b65] generic_file_aio_read+0x4c5/0x700
  [205458.633636]  [a0150949] nfs_file_read+0x69/0xf0 [nfs]
  [205458.633636]  [811bd8ba] do_sync_read+0x5a/0x90
  [205458.633636]  [811bdf55] vfs_read+0x95/0x160
  [205458.633636]  [811bea69] SyS_read+0x49/0xa0
  [205458.633636]  [8173391d] system_call_fastpath+0x1a/0x1f
  [205458.633636] Code: c0 e8 92 3b 66 e1 48 c7 c7 ae cc 0b a0 31 c0 e8 84 3b 
66 e1 48 63 b3 90 00 00 00 31 d2 48 c7 c7 e3 cc 0b a0 31 c0 e8 6d 3b 66 e1 0f 
0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 
  [205458.633636] RIP  [a00b8c14] 
fscache_release_retrieval_op+0x74/0x80 [fscache]
  [205458.633636]  RSP 880107acfad8
  [205458.833163] ---[ end trace 30960a6ba86a197f ]---

  Node 2:

  [360136.745210] FS-Cache: Assertion failed
  [360136.747121] 1 == 0 is false
  [360136.748704] [ cut here ]
  [360136.751217] kernel BUG at 
/build/buildd/linux-3.13.0/fs/fscache/page.c:244!
  [360136.752666] invalid opcode:  [#1] SMP 
  [360136.752666] Modules linked in: veth xt_nat xt_tcpudp xt_addrtype 
xt_conntrack ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp 
llc dm_thin_pool dm_persistent_data dm_bufio dm_bio_prison libcrc32c cachefiles 
nfsv3 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt syscopyarea 
sysfillrect sysimgblt fb_sys_fops serio_raw isofs crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
  [360136.752666] CPU: 2 

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

[Gabriel Pérez]

apport information

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

Title:
  FS-Cache: Assertion failed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Happens in two nodes at the same time.

  Node 1:

  [205458.631304] [ cut here ]
  [205458.633636] kernel BUG at 
/build/buildd/linux-3.13.0/fs/fscache/page.c:244!
  [205458.633636] invalid opcode:  [#1] SMP 
  [205458.633636] Modules linked in: veth xt_nat xt_tcpudp xt_addrtype 
xt_conntrack ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp 
llc dm_thin_pool dm_persistent_data dm_bufio dm_bio_prison libcrc32c cachefiles 
nfsv3 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt syscopyarea 
sysfillrect sysimgblt fb_sys_fops serio_raw isofs crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd floppy psmouse
  [205458.633636] CPU: 3 PID: 6217 Comm: php5-fpm Not tainted 3.13.0-53-generic 
#89-Ubuntu
  [205458.633636] Hardware name: Xen HVM domU, BIOS 4.2.amazon 05/06/2015
  [205458.633636] task: 8801e3ede000 ti: 880107ace000 task.ti: 
880107ace000
  [205458.633636] RIP: 0010:[a00b8c14]  [a00b8c14] 
fscache_release_retrieval_op+0x74/0x80 [fscache]
  [205458.633636] RSP: 0018:880107acfad8  EFLAGS: 00010286
  [205458.633636] RAX: 000f RBX: 880014be1a80 RCX: 

  [205458.633636] RDX: 8801efc6f020 RSI: 8801efc6d408 RDI: 
0246
  [205458.633636] RBP: 880107acfae0 R08: 0096 R09: 
0231
  [205458.633636] R10: 8185ade0 R11: 880107acf806 R12: 
8800c3e469f8
  [205458.633636] R13: 880107acfbbc R14: ff97 R15: 
8801e3ff9b68
  [205458.633636] FS:  7f383346c740() GS:8801efc6() 
knlGS:
  [205458.633636] CS:  0010 DS:  ES:  CR0: 80050033
  [205458.633636] CR2: 7f382032cf08 CR3: 0001206ea000 CR4: 
001406e0
  [205458.633636] Stack:
  [205458.633636]  880014be1a80 880107acfb08 a00b6eab 
880014be1a80
  [205458.633636]  8800c3e469f8 880107acfbbc 880107acfb58 
a00b9753
  [205458.633636]  8800c3e46a00 8801e3ff9b00 880107acfcb8 
ff97
  [205458.633636] Call Trace:
  [205458.633636]  [a00b6eab] fscache_put_operation+0x5b/0x220 
[fscache]
  [205458.633636]  [a00b9753] 
__fscache_read_or_alloc_pages+0x1b3/0x350 [fscache]
  [205458.633636]  [a01645c1] __nfs_readpages_from_fscache+0x71/0x1b0 
[nfs]
  [205458.633636]  [a015b7b8] nfs_readpages+0xa8/0x190 [nfs]
  [205458.633636]  [81197c53] ? alloc_pages_current+0xa3/0x160
  [205458.633636]  [8114f757] ? __page_cache_alloc+0x97/0xc0
  [205458.633636]  [8115ba39] __do_page_cache_readahead+0x1b9/0x260
  [205458.633636]  [8115bf12] ondemand_readahead+0x152/0x2a0
  [205458.633636]  [8115c091] page_cache_sync_readahead+0x31/0x50
  [205458.633636]  [81151b65] generic_file_aio_read+0x4c5/0x700
  [205458.633636]  [a0150949] nfs_file_read+0x69/0xf0 [nfs]
  [205458.633636]  [811bd8ba] do_sync_read+0x5a/0x90
  [205458.633636]  [811bdf55] vfs_read+0x95/0x160
  [205458.633636]  [811bea69] SyS_read+0x49/0xa0
  [205458.633636]  [8173391d] system_call_fastpath+0x1a/0x1f
  [205458.633636] Code: c0 e8 92 3b 66 e1 48 c7 c7 ae cc 0b a0 31 c0 e8 84 3b 
66 e1 48 63 b3 90 00 00 00 31 d2 48 c7 c7 e3 cc 0b a0 31 c0 e8 6d 3b 66 e1 0f 
0b 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 
  [205458.633636] RIP  [a00b8c14] 
fscache_release_retrieval_op+0x74/0x80 [fscache]
  [205458.633636]  RSP 880107acfad8
  [205458.833163] ---[ end trace 30960a6ba86a197f ]---

  Node 2:

  [360136.745210] FS-Cache: Assertion failed
  [360136.747121] 1 == 0 is false
  [360136.748704] [ cut here ]
  [360136.751217] kernel BUG at 
/build/buildd/linux-3.13.0/fs/fscache/page.c:244!
  [360136.752666] invalid opcode:  [#1] SMP 
  [360136.752666] Modules linked in: veth xt_nat xt_tcpudp xt_addrtype 
xt_conntrack ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 
nf_nat_ipv4 iptable_filter ip_tables x_tables nf_nat nf_conntrack bridge stp 
llc dm_thin_pool dm_persistent_data dm_bufio dm_bio_prison libcrc32c cachefiles 
nfsv3 nfsd auth_rpcgss nfs_acl nfs lockd sunrpc fscache dm_crypt syscopyarea 
sysfillrect sysimgblt fb_sys_fops serio_raw isofs crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd psmouse floppy
  [360136.752666] CPU: