date:20150304

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

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

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

Title:
  linux: 3.16.0-32.42 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.16.0-32.42 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, 03. March 2015 18:53 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 03. March 2015 18:53 UTC

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

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

[Kernel-packages] [Bug 1427942] Re: 15.04 Beta, Toshiba Z835, suspend on lid close does not work.

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
Confirmed.


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc2-vivid/


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

Title:
  15.04 Beta, Toshiba Z835, suspend on lid close does not work.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello friends. I fired up 15.04 beta on my Toshiba Z835 ultrabook.
  Upon lid close, the system does not suspend despite being set to
  suspend on lid close for both battery and on AC power. This worked
  fine under 14.04, however I admittedly never tested 14.10.

  If I select the gear in the upper right corner and hit suspend, it
  suspends and even resumes fine.

  Also worth mentioning is a long standing issue with the Toshiba Z835,
  where following resume from suspend, the function keys which control
  the brightness no longer work. I see the meter go up and down, but it
  doesn't change the actual brightness.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-7-generic 3.19.0-7.7 [modified: 
boot/vmlinuz-3.19.0-7-generic]
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jason  2130 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Mar  3 20:40:39 2015
  InstallationDate: Installed on 2015-03-04 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150303)
  MachineType: TOSHIBA PORTEGE Z835
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=4bf1f853-b598-4a66-874b-8a41c88f3de1 ro quiet splash vt.handoff=7
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.80
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.80:bd04/18/2013:svnTOSHIBA:pnPORTEGEZ835:pvrPT224U-013021:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE Z835
  dmi.product.version: PT224U-013021
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1428121] Re: Intel HDMI Audio not working with IOMMU enabled

2015-03-04 Thread Kelvin Middleton

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

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

Title:
  Intel HDMI Audio not working with IOMMU enabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  New ASRock Z97 Extreme 6 motherboard with an Intel i7 4790S and an
  Nvidia GTX 650.

  Host uses Intel IGD for video and HDMI audio out.

  When I pass kernel flags 'intel_iommu=on' or 'intel_iommu=on,igfx_on'
  HDMI audio no longer functions although the device and modules seem to
  load and I cannot locate any error messages.  In this configuration
  IOMMU functions as expected and I can successfully pass the Nvidia
  card through to a KVM guest using VFIO.

  As per this
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223840) bug
  report and the linked bugzilla thread I attempted to use kernel flag
  'intel_iommu=on,igfx_off'.  This resolves the HDMI audio out but
  breaks IOMMU as in VGA pass through generates DMA errors.

  I'm running from a clean installation of 14.10 with no modifications
  to the kernel or kvm, qemu, libvirt or virt-manager.

  In either scenario above the analogue audio out continues to function,
  I haven't tested the optical out as I have no hardware to do so.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kelvin 3468 F pulseaudio
   /dev/snd/controlC3:  kelvin 3468 F pulseaudio
   /dev/snd/controlC0:  kelvin 3468 F pulseaudio
   /dev/snd/controlC1:  kelvin 3468 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar  4 12:53:17 2015
  HibernationDevice: RESUME=UUID=4d35060a-85c4-45fd-9f8e-530491588931
  InstallationDate: Installed on 2015-02-26 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.10 Utopic Unicorn - Release amd64 
(20141022.2)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed 
root=UUID=4914f227-6bb0-40bb-a781-9ad7111a996f ro intremap=no_x2apic_optout 
intel_iommu=on,forcedac pci-stub.ids=10de:11c8,10de:0e0b nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-31-generic N/A
   linux-backports-modules-3.16.0-31-generic  N/A
   linux-firmware 1.138.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1428155] Re: package linux-image-3.13.0-39-generic 3.13.0-39.66 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package.

If that does not resolve your issue, please mark the bug as Confirmed

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

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

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

Title:
  package linux-image-3.13.0-39-generic 3.13.0-39.66 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  is this a serious problem as it keeps coming up

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-39-generic 3.13.0-39.66
  ProcVersionSignature: Ubuntu 3.8.0-44.66~precise1-generic 3.8.13.25
  Uname: Linux 3.8.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  diane  2180 F pulseaudio
   /dev/snd/seq:timidity   1221 F timidity
  Date: Tue Mar  3 08:31:02 2015
  DpkgHistoryLog:
   
  DpkgTerminalLog:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=7d243088-dbc4-49be-84e5-0504b9121608
  InstallationDate: Installed on 2013-10-14 (505 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 
(20130820.1)
  MachineType: Hewlett-Packard Compaq Presario CQ71 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=Linux ro 
root=UUID=f39978f6-3ec4-4e86-870c-efb0d1221324
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1
  SourcePackage: linux
  Title: package linux-image-3.13.0-39-generic 3.13.0-39.66 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: Upgraded to trusty on 2014-08-13 (202 days ago)
  dmi.bios.date: 09/22/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 306B
  dmi.board.vendor: Quanta
  dmi.board.version: 21.12
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.14:bd09/22/2009:svnHewlett-Packard:pnCompaqPresarioCQ71NotebookPC:pvrRev1:rvnQuanta:rn306B:rvr21.12:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: Compaq Presario CQ71 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1428050] Re: [Matsushita Electric Industrial Co., Ltd. CF-19FHGAXBG] suspend/resume failure

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
Confirmed.


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc2-vivid/


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

Title:
  [Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG] suspend/resume
  failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When opening the lip, to resume after suspend, the computer was frozen
  and some LED's where blinking in a regular rhythmn. I had to reset the
  Toughbook to restart it.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-7-generic 3.19.0-7.7 [modified: 
boot/vmlinuz-3.19.0-7-generic]
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  skb2372 F pulseaudio
  Date: Wed Mar  4 10:16:51 2015
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  InstallationDate: Installed on 2015-03-02 (1 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150302)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-7-generic 
root=UUID=00bc12a3-0121-4e30-8834-27fafd4a0666 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: linux
  Title: [Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG] suspend/resume 
failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/10/2007
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.00L11
  dmi.board.name: CF19-2
  dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.board.version: 001
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.00L11:bd10/10/2007:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-19FHGAXBG:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF19-2:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
  dmi.product.name: CF-19FHGAXBG
  dmi.product.version: 002
  dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.

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

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

[Kernel-packages] [Bug 1428121] Re: Intel HDMI Audio not working with IOMMU enabled

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
Confirmed.


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc2-vivid/

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

Title:
  Intel HDMI Audio not working with IOMMU enabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  New ASRock Z97 Extreme 6 motherboard with an Intel i7 4790S and an
  Nvidia GTX 650.

  Host uses Intel IGD for video and HDMI audio out.

  When I pass kernel flags 'intel_iommu=on' or 'intel_iommu=on,igfx_on'
  HDMI audio no longer functions although the device and modules seem to
  load and I cannot locate any error messages.  In this configuration
  IOMMU functions as expected and I can successfully pass the Nvidia
  card through to a KVM guest using VFIO.

  As per this
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223840) bug
  report and the linked bugzilla thread I attempted to use kernel flag
  'intel_iommu=on,igfx_off'.  This resolves the HDMI audio out but
  breaks IOMMU as in VGA pass through generates DMA errors.

  I'm running from a clean installation of 14.10 with no modifications
  to the kernel or kvm, qemu, libvirt or virt-manager.

  In either scenario above the analogue audio out continues to function,
  I haven't tested the optical out as I have no hardware to do so.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kelvin 3468 F pulseaudio
   /dev/snd/controlC3:  kelvin 3468 F pulseaudio
   /dev/snd/controlC0:  kelvin 3468 F pulseaudio
   /dev/snd/controlC1:  kelvin 3468 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar  4 12:53:17 2015
  HibernationDevice: RESUME=UUID=4d35060a-85c4-45fd-9f8e-530491588931
  InstallationDate: Installed on 2015-02-26 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.10 Utopic Unicorn - Release amd64 
(20141022.2)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed 
root=UUID=4914f227-6bb0-40bb-a781-9ad7111a996f ro intremap=no_x2apic_optout 
intel_iommu=on,forcedac pci-stub.ids=10de:11c8,10de:0e0b nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-31-generic N/A
   linux-backports-modules-3.16.0-31-generic  N/A
   linux-firmware 1.138.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1426113] Re: devel: vbox drivers introduce symlinks which prevent use of orig.tar.gz

2015-03-04 Thread h

when building kernel-sources with quilt i struggled about symlinks created
in other folders.
had to add:
index 18b765f..6e5caa8 100644
--- a/debian.master/reconstruct
+++ b/debian.master/reconstruct
@@ -4,3 +4,5 @@ ln -sf ../r0drv ubuntu/vbox/vboxguest/r0drv
 ln -sf ../include ubuntu/vbox/vboxsf/include
 ln -sf ../r0drv ubuntu/vbox/vboxsf/r0drv
 ln -sf ../include ubuntu/vbox/vboxvideo/include
+rm -f ubuntu/vbox/r0drv/r0drv
+rm -f ubuntu/vbox/include/include


Better way should be to check if symlink exist.

Date: Wed, 4 Mar 2015 17:53:22 +0100
Subject: [PATCH] ubuntu-vbox-guest-fix-symlinks

---
 debian.master/reconstruct | 20 +++-
 1 file changed, 15 insertions(+), 5 deletions(-)

diff --git a/debian.master/reconstruct b/debian.master/reconstruct
index 18b765f..caba9b7 100644
--- a/debian.master/reconstruct
+++ b/debian.master/reconstruct
@@ -1,6 +1,16 @@
 # Reconstruct vbox symlinks (LP:1426113)
-ln -sf ../include ubuntu/vbox/vboxguest/include
-ln -sf ../r0drv ubuntu/vbox/vboxguest/r0drv
-ln -sf ../include ubuntu/vbox/vboxsf/include
-ln -sf ../r0drv ubuntu/vbox/vboxsf/r0drv
-ln -sf ../include ubuntu/vbox/vboxvideo/include
+if ! [ -e ubuntu/vbox/vboxguest/include ]; then
+ln -sf ../include ubuntu/vbox/vboxguest/include
+fi
+if ! [ -e ubuntu/vbox/vboxguest/r0drv ]; then
+ln -sf ../r0drv ubuntu/vbox/vboxguest/r0drv
+fi
+if ! [ -e ubuntu/vbox/vboxsf/include ]; then
+ln -sf ../include ubuntu/vbox/vboxsf/include
+fi
+if ! [ -e ubuntu/vbox/vboxsf/r0drv ]; then
+ln -sf ../r0drv ubuntu/vbox/vboxsf/r0drv
+fi
+if ! [ -e ubuntu/vbox/vboxvideo/include ]; then
+ln -sf ../include ubuntu/vbox/vboxvideo/include
+fi
-- 
1.9.1


** Patch added: check for symlinks
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1426113/+attachment/4334500/+files/0001-ubuntu-vbox-guest-fix-symlinks.patch

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

Title:
  devel: vbox drivers introduce symlinks which prevent use of
  orig.tar.gz

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The introduction of the vbox drivers prevent use of a .orig.tar.gz.
  Need to work out how to remove these and restore them on clean.

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

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

[Kernel-packages] [Bug 1405004] Re: 10de:03d0 mostly unresponsive after login with nouveau on GeForce 6150SE

2015-03-04 Thread Ryan Tandy

This is fixed in Vivid now that 3.19 has landed.

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

Title:
  10de:03d0 mostly unresponsive after login with nouveau on GeForce
  6150SE

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  On a system with a GeForce 6150SE integrated GPU, the system becomes
  mostly unresponsive shortly after logging in. It does not lock up
  completely, but seems to only process pointer events or keystrokes
  once every few seconds, and pings from another machine on the network
  start returning in 3-5 seconds instead of a few ms.

  This began in raring and happens on every subsequent release (and also
  under precise, if a HWE stack from raring or later is installed);
  under quantal it does not happen.

  Based on the hardware, symptoms, kernel versions, and NvMSI=0 workaround, 
these upstream bugs might (or might not) be related:
  https://bugs.freedesktop.org/show_bug.cgi?id=61321
  https://bugs.freedesktop.org/show_bug.cgi?id=71382
  https://bugs.freedesktop.org/show_bug.cgi?id=87361

  WORKAROUND: Use kernel boot parameter:
  nouveau.config=NvMSI=0

  WORKAROUND: Use proprietary nvidia-304 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.16.0-28-generic 3.16.0-28.38
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.15.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4505 F pulseaudio
  CasperVersion: 1.347
  Date: Mon Dec 22 21:40:06 2014
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141222)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 046d:c31c Logitech, Inc. Keyboard K120 for Business
   Bus 002 Device 002: ID 413c:3012 Dell Computer Corp. Optical Wheel Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: initrd=hostname/vivid/desktop/amd64/casper/initrd.lz 
boot=casper netboot=nfs 
nfsroot=10.0.2.1:/var/lib/tftpboot/hostname/vivid/desktop/amd64 quiet splash 
file=/cdrom/preseed/hostname.seed url=http://10.0.2.64/preseed/ubiquity.cfg 
text BOOT_IMAGE=hostname/vivid/desktop/amd64/casper/vmlinuz.efi
  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.16.0-28-generic N/A
   linux-backports-modules-3.16.0-28-generic  N/A
   linux-firmware 1.140
  RfKill:

  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/07/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M61PMP/M61PMP-K
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd06/07/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnFOXCONN:rnM61PMP/M61PMP-K:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1428045] Re: CIFS hangs at cifs_oplock_break

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
Confirmed.


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc2-vivid/


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

** Tags added: kernel-da-key

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

Title:
  CIFS hangs at cifs_oplock_break

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  we're having constant issues with CIFS mounts on our Linux terminal
  servers (Ubuntu 12.04 and 14.04 with updated kernel). Usually after 1
  or 2 days we see the following in dmesg:

  
  [102000.440031] INFO: task cifsiod:2184 blocked for more than 120 seconds.
  [102000.441342]   Not tainted 3.19.0-7-generic #7-Ubuntu
  [102000.441454] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
  [102000.441617] cifsiod D 8800363dfc98 0  2184  2 
0x
  [102000.441796] Workqueue: cifsiod cifs_oplock_break [cifs]
  [102000.442048]  8800363dfc98 8800368b09d0 00014200 
8800363dffd8
  [102000.442215]  00014200 88013ab9bae0 8800368b09d0 
0246
  [102000.442382]  8800363dfd30 88013ffd7c88 0002 
817cb120
  [102000.442628] Call Trace:
  [102000.442681]  [817cb120] ? bit_wait_io+0x50/0x50
  [102000.442828]  [817ca4c9] schedule+0x29/0x70
  [102000.442926]  [817cb14b] bit_wait+0x2b/0x50
  [102000.443023]  [817caca7] __wait_on_bit+0x67/0x90
  [102000.443128]  [810a2857] ? wake_up_process+0x27/0x50
  [102000.443240]  [817cb120] ? bit_wait_io+0x50/0x50
  [102000.443345]  [817cad42] out_of_line_wait_on_bit+0x72/0x80
  [102000.443466]  [810b6f70] ? autoremove_wake_function+0x40/0x40
  [102000.443736]  [c037689b] cifs_oplock_break+0x6b/0x330 [cifs]
  [102000.443994]  [8108f218] process_one_work+0x158/0x460
  [102000.444250]  [8108f6ac] rescuer_thread+0x18c/0x460
  [102000.95]  [8108f520] ? process_one_work+0x460/0x460
  [102000.444745]  [810950e9] kthread+0xc9/0xe0
  [102000.444975]  [81095020] ? kthread_create_on_node+0x1c0/0x1c0
  [102000.445234]  [817cf2bc] ret_from_fork+0x7c/0xb0
  [102000.445472]  [81095020] ? kthread_create_on_node+0x1c0/0x1c0

  
  and later

  
  [102000.445739] INFO: task kworker/3:2:20985 blocked for more than 120 
seconds.
  [102000.446004]   Not tainted 3.19.0-7-generic #7-Ubuntu
  [102000.446239] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
  [102000.446657] kworker/3:2 D 8800bae87cb8 0 20985  2 
0x
  [102000.446949] Workqueue: cifsiod cifs_oplock_break [cifs]
  [102000.447187]  8800bae87cb8 8800baed9d70 00014200 
8800bae87fd8
  [102000.447613]  00014200 88013abf44b0 8800baed9d70 
0246
  [102000.448047]  8800bae87d50 88013ffd7c88 0002 
817cb120
  [102000.448477] Call Trace:
  [102000.448659]  [817cb120] ? bit_wait_io+0x50/0x50
  [102000.448896]  [817ca4c9] schedule+0x29/0x70
  [102000.449127]  [817cb14b] bit_wait+0x2b/0x50
  [102000.449360]  [817caca7] __wait_on_bit+0x67/0x90
  [102000.449595]  [817cb120] ? bit_wait_io+0x50/0x50
  [102000.449834]  [817cad42] out_of_line_wait_on_bit+0x72/0x80
  [102000.450085]  [810b6f70] ? autoremove_wake_function+0x40/0x40
  [102000.450361]  [c037689b] cifs_oplock_break+0x6b/0x330 [cifs]
  [102000.450631]  [8108f218] process_one_work+0x158/0x460
  [102000.450907]  [8108fef3] worker_thread+0x53/0x5a0
  [102000.451163]  [8108fea0] ? idle_worker_timeout+0x110/0x110
  [102000.451834]  [810950e9] kthread+0xc9/0xe0
  [102000.452093]  [81095020] ? kthread_create_on_node+0x1c0/0x1c0
  [102000.452357]  [817cf2bc] ret_from_fork+0x7c/0xb0
  [102000.452601]  [81095020] ? kthread_create_on_node+0x1c0/0x1c0

  
  The same repeats for various other processes like kworker and the hanging 
userspace process. This happens with all recent kernel versions (3.13-3.19) and 
forces us to reboot the server regularly as the requesting processes always 
hang with process state D and (I/O) load increases from

[Kernel-packages] [Bug 1428121] Re: Intel HDMI Audio not working with IOMMU enabled

2015-03-04 Thread Kelvin Middleton

Think I've done all correctly, upstream has the same issues using the
kernel you linked.

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

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

Title:
  Intel HDMI Audio not working with IOMMU enabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  New ASRock Z97 Extreme 6 motherboard with an Intel i7 4790S and an
  Nvidia GTX 650.

  Host uses Intel IGD for video and HDMI audio out.

  When I pass kernel flags 'intel_iommu=on' or 'intel_iommu=on,igfx_on'
  HDMI audio no longer functions although the device and modules seem to
  load and I cannot locate any error messages.  In this configuration
  IOMMU functions as expected and I can successfully pass the Nvidia
  card through to a KVM guest using VFIO.

  As per this
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223840) bug
  report and the linked bugzilla thread I attempted to use kernel flag
  'intel_iommu=on,igfx_off'.  This resolves the HDMI audio out but
  breaks IOMMU as in VGA pass through generates DMA errors.

  I'm running from a clean installation of 14.10 with no modifications
  to the kernel or kvm, qemu, libvirt or virt-manager.

  In either scenario above the analogue audio out continues to function,
  I haven't tested the optical out as I have no hardware to do so.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kelvin 3468 F pulseaudio
   /dev/snd/controlC3:  kelvin 3468 F pulseaudio
   /dev/snd/controlC0:  kelvin 3468 F pulseaudio
   /dev/snd/controlC1:  kelvin 3468 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar  4 12:53:17 2015
  HibernationDevice: RESUME=UUID=4d35060a-85c4-45fd-9f8e-530491588931
  InstallationDate: Installed on 2015-02-26 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.10 Utopic Unicorn - Release amd64 
(20141022.2)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed 
root=UUID=4914f227-6bb0-40bb-a781-9ad7111a996f ro intremap=no_x2apic_optout 
intel_iommu=on,forcedac pci-stub.ids=10de:11c8,10de:0e0b nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-31-generic N/A
   linux-backports-modules-3.16.0-31-generic  N/A
   linux-firmware 1.138.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1428111] Re: Kernel crash on Dell Latitude 5530 (tg3 driver involved)

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
Confirmed.


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc2-vivid/


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

** Tags added: kernel-da-key

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

Title:
  Kernel crash on Dell Latitude 5530 (tg3 driver involved)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from Ubuntu 14.10 to 15.04 the system is not starting
  anymore. After disabling the splash screen I get lots of Error
  messages on the console. The system is unresponsive. Kernel 3.16 runs
  without problems. So does 3.19 on another system without Broadcom LAN-
  adapter. screenshot is attached. The error occures before entering
  the password for Luks-encryption. So it's very likely, it still doing
  initrd-stuff ...

  System is a Dell Latitude 5530, Core i5, 16 GB RAM
  running Ubuntu 15.04 (AMD64) with all updates available until 2015-03-04 
(upgraded from 14.10)

  lspci.log  dmesg.log  are taken wth the old kernel 3.16 as was not
  able to boot 3.19.

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

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

[Kernel-packages] [Bug 1428075] Re: [12.04.2] Realtek r8169 driver is unstable (link up / link down)

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
Confirmed.


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc2-vivid/


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

Title:
  [12.04.2] Realtek r8169 driver is unstable (link up / link down)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My Realtek RTL8111/8168/8411 card is very unstable:
  - led only goes on  30 seconds after pluggin in the cable
  - it takes even longer until I can ping the interface; often it does not 
become possible at all

  dmesg show the link is brought up and down again and again.

  [ 1490.791721] usb 2-3: ep 0x81 - rounding interval to 64 microframes, ep 
desc says 80 micro$
  [ 1490.793653] input: Logitech USB Optical Mouse as 
/devices/pci:00/:00:14.0/usb2/2-$
  [ 1490.793817] hid-generic 0003:046D:C05A.001B: input,hidraw0: USB HID v1.11 
Mouse [Logitech$
  [ 1493.001767] r8169 :02:00.0 p5p1: link down
  [ 1506.635177] r8169 :02:00.0 p5p1: link up
  [ 1513.960191] r8169 :02:00.0 p5p1: link down
  [ 1532.077450] r8169 :02:00.0 p5p1: link up
  [ 1532.433100] r8169 :02:00.0 p5p1: link down
  [ 1550.846755] usb 2-3: USB disconnect, device number 27
  [ 1550.883189] r8169 :02:00.0 p5p1: link up

  There is more often problem with the linux driver:
  
https://www.google.nl/search?q=r8169%20%20%22link%20up%22%20%22link%20down%22rct=j
  ; same bug applies to Oneiric 11.10 (#839393) and was closed (Won't
  fix) because it is no longer supported. It is not fixed, despite the
  suggestion that the 3.1/3.2 kernel would improve the situation.

  As 14.04.2 is LTS, I hereby report it again.

  version: Ubuntu 3.16.0-31.41~14.04.1-generic 3.16.7-ckt5
  see also dmesg.log and lspci-vnvn.log

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

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

[Kernel-packages] [Bug 1427947] Re: unable to shutdown

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
Confirmed.


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc2-vivid/


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

Title:
  unable to shutdown

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  stops at will halt or sumthin

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-46-generic 3.13.0-46.76
  ProcVersionSignature: Ubuntu 3.13.0-46.76-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kishan 2048 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar  4 09:47:18 2015
  HibernationDevice: RESUME=UUID=f58ae439-bd92-4bb4-adeb-d8c564d12e39
  InstallationDate: Installed on 2015-02-26 (5 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 003: ID 04f2:b469 Chicony Electronics Co., Ltd 
   Bus 002 Device 002: ID 04ca:300b Lite-On Technology Corp. 
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire ES1-311
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=c3d4952b-a5c3-489c-99f1-7331a352b71f ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-46-generic N/A
   linux-backports-modules-3.13.0-46-generic  N/A
   linux-firmware 1.127.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Aspire ES1-311
  dmi.board.vendor: Acer
  dmi.board.version: V1.07
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.07
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd08/13/2014:svnAcer:pnAspireES1-311:pvrV1.07:rvnAcer:rnAspireES1-311:rvrV1.07:cvnAcer:ct10:cvrV1.07:
  dmi.product.name: Aspire ES1-311
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1364539] Re: [Dell Latitude E7440] suspend/resume failure

2015-03-04 Thread Michael Thayer

Just seen this again with Vivid.

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

Title:
  [Dell Latitude E7440] suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  If relevant, I docked the laptop between suspending and resuming.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-11-generic 3.16.0-11.16
  ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1
  Uname: Linux 3.16.0-11-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael2707 F pulseaudio
   /dev/snd/controlC0:  michael2707 F pulseaudio
  Date: Tue Sep  2 19:58:10 2014
  DuplicateSignature: suspend/resume:Dell Inc. Latitude E7440:A10
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=6d651e5a-075d-4911-a5ce-6710f7246853
  InstallationDate: Installed on 2014-08-01 (32 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Dell Inc. Latitude E7440
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-11-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-11-generic N/A
   linux-backports-modules-3.16.0-11-generic  N/A
   linux-firmware 1.132
  SourcePackage: linux
  Title: [Dell Inc. Latitude E7440] suspend/resume failure
  UpgradeStatus: Upgraded to utopic on 2014-08-28 (5 days ago)
  UserGroups:
   
  dmi.bios.date: 06/26/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0RYCC9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1426794] Re: Wrong keymap on HP Compaq 8710W

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
Confirmed.


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc2-vivid/


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

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

Title:
  Wrong keymap on HP Compaq 8710W

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On my HP 8710W, before the latest round of updates, the fn+f9, fn+f10,
  and fn+f11 would control brightness up, brightness down, and ambient
  light sensor toggle, respectively. Now, according to evtest, all three
  are mapped to KEY_FN_ESC (fn+esc).

  fn+f9:
  Event: time 1425168035.943444, type 4 (EV_MSC), code 4 (MSC_SCAN), value 81
  Event: time 1425168035.943444, type 1 (EV_KEY), code 465 (KEY_FN_ESC), value 1
  Event: time 1425168035.943444, -- SYN_REPORT 
  Event: time 1425168035.950473, type 4 (EV_MSC), code 4 (MSC_SCAN), value 81
  Event: time 1425168035.950473, type 1 (EV_KEY), code 465 (KEY_FN_ESC), value 0
  Event: time 1425168035.950473, -- SYN_REPORT 

  
  fn+f10:
  Event: time 1425168016.345171, type 4 (EV_MSC), code 4 (MSC_SCAN), value 81
  Event: time 1425168016.345171, type 1 (EV_KEY), code 465 (KEY_FN_ESC), value 1
  Event: time 1425168016.345171, -- SYN_REPORT 
  Event: time 1425168016.352200, type 4 (EV_MSC), code 4 (MSC_SCAN), value 81
  Event: time 1425168016.352200, type 1 (EV_KEY), code 465 (KEY_FN_ESC), value 0
  Event: time 1425168016.352200, -- SYN_REPORT 

  fn+f11:
  Event: time 1425167968.176590, type 4 (EV_MSC), code 4 (MSC_SCAN), value 81
  Event: time 1425167968.176590, type 1 (EV_KEY), code 465 (KEY_FN_ESC), value 1
  Event: time 1425167968.176590, -- SYN_REPORT 
  Event: time 1425167968.183622, type 4 (EV_MSC), code 4 (MSC_SCAN), value 81
  Event: time 1425167968.183622, type 1 (EV_KEY), code 465 (KEY_FN_ESC), value 0
  Event: time 1425167968.183622, -- SYN_REPORT 
  Event: time 1425167968.206663, type 4 (EV_MSC), code 4 (MSC_SCAN), value 57
  Event: time 1425167968.206663, -- SYN_REPORT 

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

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

[Kernel-packages] [Bug 1427925] Re: [Dell Inc. Latitude D620] suspend/resume failure

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, 
please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as 
Confirmed.


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc2-vivid/


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

Title:
  [Dell Inc. Latitude D620] suspend/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Laptop was on battery power with screensaver and lock disabled (no other 
programs open).
  Closed the laptop lid to suspend.
  Upon opening the lid, Ubuntu resumed with blank screen.
  Ctrl+Alt+F1 did not drop me into a shell, Ctrl+Alt+F7 had no effect, had to 
turn off my laptop.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  margetto   2401 F pulseaudio
  Date: Wed Mar  4 00:19:52 2015
  DuplicateSignature: suspend/resume:Dell Inc. Latitude D620:A10
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=d33eda00-0b9e-46b5-b4bf-dd9b2ddb80ab
  InstallationDate: Installed on 2015-02-16 (15 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Dell Inc. Latitude D620
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=c599c63f-d1d4-4c5d-832c-3614c10bd870 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-31-generic N/A
   linux-backports-modules-3.16.0-31-generic  N/A
   linux-firmware 1.138.1
  SourcePackage: linux
  Title: [Dell Inc. Latitude D620] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/16/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0FT292
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd05/16/2008:svnDellInc.:pnLatitudeD620:pvr:rvnDellInc.:rn0FT292:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude D620
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1425803] Re: Driver problem with USB chipset VIA VL812-B2

2015-03-04 Thread Warren

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

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

Title:
Driver problem with USB chipset VIA VL812-B2

Status in linux package in Ubuntu:
Confirmed

Bug description:
Presuming the system info you need is in the automatically generated
collection from ubuntu-bug. Ubuntu 14.10, fully updated. Kernel
3.16.0-31-generic.

The problem described also exists in earlier kernels although I cannot
say when it first appeared.

I have a HooToo HT-UH005 4-Port USB 3.0 hub (VIA VL812-B2 chipset) .
I'm using it with a HP Pavilion 17-e049wm laptop. This computer has
two USB 3.0 ports.

When the computer is quiescent the CPU consumed is normally 0% to 1%.
That's the same whether there are USB 2.0 or 3.0 devices plugged into
its onboard USB 3.0 ports, or not.

As soon as I plug the HT-UH005 hub into one of those USB 3.0 ports, a
system process khubd appears and it takes about 7% of CPU. Also,
several kworker and ksoftirqd threads appear which between them
consume another 18% of CPU, for a total of 25% CPU load. That's just
because the HT-UH005 was plugged in. No peripherals attached to the
HT-UH005.

Stranger still, when I unplug the HT-UH005 the khubd, kworker, and
ksoftirqd threads *continue* to consume 25% CPU. That's with the HT-
UH005 disconnected after it was previously connected. This goes on
indefinitely. The only way I can get things back to normal is to
reboot or to manually stop and restart (unbind and then bind) the
xhci_hcd driver that's servicing the internal hub that runs the
computer's two USB 3.0 ports.

The listing from dmesg shows no apparent problems when the HT-UH005 is
connected or disconnected. Listing from lsusb shows the HT-UH005
successfully connected to a port on the internal USB 3.0 hub using
driver xhci_hcd.

This could be caused by some sort of incompatibility between the AMD
internal hub and the VIA external hub. But, that the condition
persists after the HT- UH005 is disconnected suggests it is almost
surely a linux driver problem.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-31-generic 3.16.0-31.41
ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
NonfreeKernelModules: wl fglrx
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: warren 5539 F pulseaudio
/dev/snd/controlC0: warren 5539 F pulseaudio
CurrentDesktop: Unity
Date: Wed Feb 25 22:12:53 2015
HibernationDevice: RESUME=UUID=d6ce9a82-d272-4efa-bfe4-e13c883b2418
InstallationDate: Installed on 2012-05-23 (1008 days ago)
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64
(20120425)
MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic
root=UUID=515bfe03-1a57-4762-9cc1-6896e081c4c5 ro quiet splash rootfstype=ext4
vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.16.0-31-generic N/A
linux-backports-modules-3.16.0-31-generic N/A
linux-firmware 1.138.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/04/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.31
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1984
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 01.13
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.31:bd12/04/2013:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr088013305B1620100:rvnHewlett-Packard:rn1984:rvr01.13:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion 17 Notebook PC
dmi.product.version: 088013305B1620100
dmi.sys.vendor: Hewlett-Packard

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

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

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

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

apport-collect 1428260

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  __USE_GNU not being set by -std=gnu11 ( struct f_owner_ex not declared
  )

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Not sure if this is a bug in libc6-dev (owner of /usr/include/fcntl.h)
  or in linux-libc-dev (owner of /usr/include/linux/header that declares struct 
f_owner_ex) but
  it definitely appears to be a bug.
  I am trying to compile code that uses the new fcntl interfaces :
 F_SETOWN_EX (struct f_owner_ex *) (since Linux 2.6.32)
 F_GETOWN_EX (struct f_owner_ex *) (since Linux 2.6.32)
  but I cannot get the 'struct f_owner_ex' structure to be declared
  using the standard system headers - I must declare it manually in my code.
  This is on a Ubuntu 14.04.2 LTS x86_64 system, fully up-to-date as
  of 2015-03-04 , with:
gcc :4:4.8.2-1ubuntu6
libc6-dev:2.19-0ubuntu6.6 
linux-libc-dev:  3.13.0-46.76

  Attempts to compile for instance this program always fail :
  $ cat /tmp/t_fcntl.c 
  #include unistd.h
  #include fcntl.h
  void f(void) { struct f_owner_ex foe={0}; }
  $ gcc -c /tmp/t_fcntl.c 
  /tmp/t_fcntl.c: In function ‘f’:
  /tmp/t_fcntl.c:3:23: error: variable ‘foe’ has initializer but incomplete type
   void f(void) { struct f_owner_ex foe={0}; }
 ^
  /tmp/t_fcntl.c:3:23: warning: excess elements in struct initializer [enabled 
by default]
  /tmp/t_fcntl.c:3:23: warning: (near initialization for ‘foe’) [enabled by 
default]
  /tmp/t_fcntl.c:3:34: error: storage size of ‘foe’ isn’t known
   void f(void) { struct f_owner_ex foe={0}; }

  I can see this structure is declared in two places:
  1: /usr/include/bits/fcntl.h @ line 239:
  #ifdef __USE_GNU
  /* Owner types.  */
  enum __pid_type
{
  F_OWNER_TID = 0,  /* Kernel thread.  */
  F_OWNER_PID,  /* Process.  */
  F_OWNER_PGRP, /* Process group.  */
  F_OWNER_GID = F_OWNER_PGRP/* Alternative, obsolete name.  */
};

  /* Structure to use with F_GETOWN_EX and F_SETOWN_EX.  */
  struct f_owner_ex
{
  enum __pid_type type; /* Owner type of ID.  */
  __pid_t pid;  /* ID of owner.  */
};
  #endif

  2: /usr/include/asm-generic/fcntl.h
  struct f_owner_ex {
int type;
__kernel_pid_t  pid;
  };
  ( I am assuming I should not be using the kernel's pid type ).

  My understanding of __USE_GNU is that it is defined when 
  -std=gnu* is specified on the compile command line, or when
  _GNU_SOURCE=1 is set.  

  Only when _GNU_SOURCE=1 is explicitly set is __USE_GNU being defined 
  and the example compiles OK :
  $ gcc -std=gnu11 -D_GNU_SOURCE=1 -c /tmp/t_fcntl.c 
  OK, that worked!

  $ gcc -std=gnu11  -c /tmp/t_fcntl.c 
  /tmp/t_fcntl.c: In function ‘f’:
  /tmp/t_fcntl.c:3:23: error: variable ‘foe’ has initializer but incomplete type
   void f(void) { struct f_owner_ex foe={0}; }
 ^
  /tmp/t_fcntl.c:3:23: warning: excess elements in struct initializer [enabled 
by default]
  /tmp/t_fcntl.c:3:23: warning: (near initialization for ‘foe’) [enabled by 
default]
  /tmp/t_fcntl.c:3:34: error: storage size of ‘foe’ isn’t known
   void f(void) { struct f_owner_ex foe={0}; }
^
  Why isn't _GNU_SOURCE being set when I've asked gcc to enable GNU extensions 
with --std=gnu11 ? 

  From the Standards gcc info node :
   You may also select an extended version of the C language explicitly 
with ... '-std=gnu11' (for C11 with GNU extensions)

  It would appear that libc6-dev / linux-libc-dev has broken GCC's
  '-std=gnuXX' support.

  Also the fcntl.2 manual page makes no mention of _GNU_SOURCE needing to be 
defined 
  in order to use F_SETOWN_EX .

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

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

[Kernel-packages] [Bug 1427808] Re: linux: 3.16.0-32.42 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) = Seth Forshee 
(sforshee)

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

Title:
  linux: 3.16.0-32.42 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.16.0-32.42 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, 03. March 2015 18:53 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 03. March 2015 18:53 UTC

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

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

[Kernel-packages] [Bug 1428260] Re: __USE_GNU not being set by -std=gnu11 ( struct f_owner_ex not declared )

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

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

Title:
  __USE_GNU not being set by -std=gnu11 ( struct f_owner_ex not declared
  )

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Not sure if this is a bug in libc6-dev (owner of /usr/include/fcntl.h)
  or in linux-libc-dev (owner of /usr/include/linux/header that declares struct 
f_owner_ex) but
  it definitely appears to be a bug.
  I am trying to compile code that uses the new fcntl interfaces :
 F_SETOWN_EX (struct f_owner_ex *) (since Linux 2.6.32)
 F_GETOWN_EX (struct f_owner_ex *) (since Linux 2.6.32)
  but I cannot get the 'struct f_owner_ex' structure to be declared
  using the standard system headers - I must declare it manually in my code.
  This is on a Ubuntu 14.04.2 LTS x86_64 system, fully up-to-date as
  of 2015-03-04 , with:
gcc :4:4.8.2-1ubuntu6
libc6-dev:2.19-0ubuntu6.6 
linux-libc-dev:  3.13.0-46.76

  Attempts to compile for instance this program always fail :
  $ cat /tmp/t_fcntl.c 
  #include unistd.h
  #include fcntl.h
  void f(void) { struct f_owner_ex foe={0}; }
  $ gcc -c /tmp/t_fcntl.c 
  /tmp/t_fcntl.c: In function ‘f’:
  /tmp/t_fcntl.c:3:23: error: variable ‘foe’ has initializer but incomplete type
   void f(void) { struct f_owner_ex foe={0}; }
 ^
  /tmp/t_fcntl.c:3:23: warning: excess elements in struct initializer [enabled 
by default]
  /tmp/t_fcntl.c:3:23: warning: (near initialization for ‘foe’) [enabled by 
default]
  /tmp/t_fcntl.c:3:34: error: storage size of ‘foe’ isn’t known
   void f(void) { struct f_owner_ex foe={0}; }

  I can see this structure is declared in two places:
  1: /usr/include/bits/fcntl.h @ line 239:
  #ifdef __USE_GNU
  /* Owner types.  */
  enum __pid_type
{
  F_OWNER_TID = 0,  /* Kernel thread.  */
  F_OWNER_PID,  /* Process.  */
  F_OWNER_PGRP, /* Process group.  */
  F_OWNER_GID = F_OWNER_PGRP/* Alternative, obsolete name.  */
};

  /* Structure to use with F_GETOWN_EX and F_SETOWN_EX.  */
  struct f_owner_ex
{
  enum __pid_type type; /* Owner type of ID.  */
  __pid_t pid;  /* ID of owner.  */
};
  #endif

  2: /usr/include/asm-generic/fcntl.h
  struct f_owner_ex {
int type;
__kernel_pid_t  pid;
  };
  ( I am assuming I should not be using the kernel's pid type ).

  My understanding of __USE_GNU is that it is defined when 
  -std=gnu* is specified on the compile command line, or when
  _GNU_SOURCE=1 is set.  

  Only when _GNU_SOURCE=1 is explicitly set is __USE_GNU being defined 
  and the example compiles OK :
  $ gcc -std=gnu11 -D_GNU_SOURCE=1 -c /tmp/t_fcntl.c 
  OK, that worked!

  $ gcc -std=gnu11  -c /tmp/t_fcntl.c 
  /tmp/t_fcntl.c: In function ‘f’:
  /tmp/t_fcntl.c:3:23: error: variable ‘foe’ has initializer but incomplete type
   void f(void) { struct f_owner_ex foe={0}; }
 ^
  /tmp/t_fcntl.c:3:23: warning: excess elements in struct initializer [enabled 
by default]
  /tmp/t_fcntl.c:3:23: warning: (near initialization for ‘foe’) [enabled by 
default]
  /tmp/t_fcntl.c:3:34: error: storage size of ‘foe’ isn’t known
   void f(void) { struct f_owner_ex foe={0}; }
^
  Why isn't _GNU_SOURCE being set when I've asked gcc to enable GNU extensions 
with --std=gnu11 ? 

  From the Standards gcc info node :
   You may also select an extended version of the C language explicitly 
with ... '-std=gnu11' (for C11 with GNU extensions)

  It would appear that libc6-dev / linux-libc-dev has broken GCC's
  '-std=gnuXX' support.

  Also the fcntl.2 manual page makes no mention of _GNU_SOURCE needing to be 
defined 
  in order to use F_SETOWN_EX .

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

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

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

2015-03-04 Thread bugproxy

--- Comment From bren...@br.ibm.com 2015-03-04 16:13 EDT---
I understand that this problem is only related to the installation, because the 
package linux-firmware contains the expected firmware.

$ dpkg -S /lib/firmware/bnx2x/bnx2x-e2-7.10.51.0.fw
linux-firmware: /lib/firmware/bnx2x/bnx2x-e2-7.10.51.0.fw

So, my suggestion, as a workaround is to install Ubuntu using a
different card, and then testing bnx2x adapter.

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

Title:
  Ubuntu 15.04 PowerNV install error during network due to bnx2x driver
  errors

Status in linux-firmware package in Ubuntu:
  Fix Committed

Bug description:
  ---Problem Description---
  I am trying to install Ubuntu 15.04 on a PowerNV system using a network 
installation.  I am able to obtain an IP address with DHCP from the petitboot 
menu.  I am also able to load the installation kernel and begin the 
installation but the network configuration within the installer fails.  I tried 
to manually configure the network, but that failed too.  When I exited to the 
shell of the installer, I can see my interface has the IP address that I 
manually configured(10.33.8.112), but I cannot connect to the local LAN:

  ~ # ip address
  1: lo: LOOPBACK,UP,LOWER_UP mtu 65536 qdisc noqueue 
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host 
 valid_lft forever preferred_lft forever
  2: eth0: BROADCAST,MULTICAST mtu 1500 qdisc mq qlen 1000
  link/ether 6c:ae:8b:02:10:88 brd ff:ff:ff:ff:ff:ff
  3: eth1: BROADCAST,MULTICAST mtu 1500 qdisc mq qlen 1000
  link/ether 6c:ae:8b:02:10:89 brd ff:ff:ff:ff:ff:ff
  4: eth2: BROADCAST,MULTICAST mtu 1500 qdisc mq qlen 1000
  link/ether 6c:ae:8b:02:10:8a brd ff:ff:ff:ff:ff:ff
  5: eth3: BROADCAST,MULTICAST mtu 1500 qdisc mq qlen 1000
  link/ether 6c:ae:8b:02:10:8b brd ff:ff:ff:ff:ff:ff
  6: eth4: BROADCAST,MULTICAST mtu 1500 qdisc noop qlen 1000
  link/ether 40:f2:e9:31:08:f4 brd ff:ff:ff:ff:ff:ff
  inet 10.33.8.112/16 brd 10.33.255.255 scope global eth4
 valid_lft forever preferred_lft forever
  7: eth5: BROADCAST,MULTICAST mtu 1500 qdisc noop qlen 1000
  link/ether 40:f2:e9:31:08:f5 brd ff:ff:ff:ff:ff:ff
  8: eth6: BROADCAST,MULTICAST mtu 1500 qdisc noop qlen 1000
  link/ether 40:f2:e9:31:08:f6 brd ff:ff:ff:ff:ff:ff
  9: eth7: BROADCAST,MULTICAST mtu 1500 qdisc noop qlen 1000
  link/ether 40:f2:e9:31:08:f7 brd ff:ff:ff:ff:ff:ff

  ~ # ping 10.33.0.1
  PING 10.33.0.1 (10.33.0.1): 56 data bytes
  ping: sendto: Network is unreachable

  I noticed in the /var/log/syslog for the install the following errors related 
to the bnx2x driver:
  Feb 23 18:49:34 kernel: [  546.172944] bnx2x 0005:01:00.2: Direct firmware 
load for bnx2x/bnx2x-e2-7.10.51.0.fw failed with error -2
  Feb 23 18:49:34 kernel: [  546.172950] bnx2x: 
[bnx2x_init_firmware:12958(eth6)]Can't load firmware file 
bnx2x/bnx2x-e2-7.10.51.0.fw
  Feb 23 18:49:34 kernel: [  546.172952] bnx2x: 
[bnx2x_func_hw_init:5523(eth6)]Error loading firmware
  Feb 23 18:49:34 kernel: [  546.172957] bnx2x: [bnx2x_nic_load:2704(eth6)]HW 
init failed, aborting

  I'm wondering if this failure message for the network driver is what is 
preventing me from connecting to the network during the install?

  ---uname output---
  N/A - Trying to do a fresh install of 15.04
   
  Machine Type = 8247-42L 

  ---Steps to Reproduce---
  Boot the PowerNV system to petitboot menu and select network install of 
Ubuntu 15.04.  
   
  Install method: Network install

  Install ISO Information: vivid-server-ppc64el.iso  23-Feb-2015 14:25  
388M
   
  The initrd has an older set of fw files and not the one the driver is 
expecting to load:

  /lib/firmware/bnx2x # ls
  bnx2x-e1-7.8.19.0.fw   bnx2x-e1h-7.8.19.0.fw  bnx2x-e2-7.8.19.0.fw
  /lib/firmware/bnx2x #

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

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

[Kernel-packages] [Bug 1293134] Re: [Samsung 700Z3A-S02DE] Laptop does not resume from suspend upon lid open

2015-03-04 Thread Lars Schütze

Is there anything I can do myself to investigate where the problem is? Upstream 
ignores the bug.
Even with the newer Fedora 21 kernel this does not work.

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

Title:
  [Samsung 700Z3A-S02DE] Laptop does not resume from suspend upon lid
  open

Status in linux package in Ubuntu:
  Triaged

Bug description:
  In 13.10-14.10, what is expected in to happen is when I close the lid,
  it puts the computer to sleep, and when I reopen the lid, it
  automatically resumes from sleep.

  What happens instead, is that the computer goes to sleep, but opening
  the lid does not make it resume.

  With acpi_listen I see that it fires and recognizes the events for lid close 
and open. /proc/acpi/button/lid/LID0/state shows the correct state for each lid 
position. With:
  acpid -d -f -l

  I see that those events trigger /etc/acpi/events/. I tried writing an
  event that matches lid close/open and calls pm-suspend, uncommenting
  lines in /etc/systemd/logind.conf regarding hibernate and suspend,
  echoing LID0 into /etc/acpi/wakeup, passing different acpi_osi strings
  with grub but the ACPI table does not change nor make it any
  difference for the suspend/resume problem.

  WORKAROUND: To resume, open the lid and press the power button once.

  ---
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2013-12-02 (104 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  NonfreeKernelModules: wl
  Package: pm-utils 1.4.1-12ubuntu1
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Tags:  saucy
  Uname: Linux 3.11.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  ---
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lars   4065 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=63d413ce-f76a-4aef-8728-6b94c8328c5a
  InstallationDate: Installed on 2014-11-19 (16 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z3A/700Z4A/700Z5A/700Z5B
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic 
root=UUID=44843d26-d39a-43f4-bfd7-bb8b6bb69a91 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: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 15FD
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 700Z3A/700Z4A/700Z5A/700Z5B
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr15FD:bd11/06/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z3A/700Z4A/700Z5A/700Z5B:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn700Z3A/700Z4A/700Z5A/700Z5B:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 700Z3A/700Z4A/700Z5A/700Z5B
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1425576] Re: Occasional crash in APM xgene enet driver on kernels prior to v3.19

That test kernel should have upstream commit: 0b46b8a, which is the
following commit in Utopic:

commit e16bd2b7e29c5434505929deda4c6bb4436104d3
Author: Sonny Rao sonny...@chromium.org
Date:   Sun Nov 23 23:02:44 2014 -0800

clocksource: arch_timer: Fix code to use physical timers when
requested

git describe --contains e16bd2b
Ubuntu-3.16.0-31.41~254

Commit 0b46b8a was in mainline as of 3.19-rc1.  Vivid has since been
rebased to 3.19 final, so it will have the fix for the other bug.   I'll
apply the fix for this bug to a Vivid kernel and post it for testing.

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

Title:
  Occasional crash in APM xgene enet driver on kernels prior to v3.19

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged

Bug description:
  This crash was submitted upstream and a fix was already present, but
  it didn't land until the 3.19 kernel. This bug is to track getting
  that fix into trusty and utopic.

  Unable to handle kernel NULL pointer dereference at virtual address 00c0
  pgd = ffc3e639a000
  [00c0] *pgd=0043e629d003, *pud=0043e629d003, *pmd=
  Internal error: Oops: 9606 [#1] PREEMPT SMP
  Modules linked in:
  CPU: 0 PID: 6643 Comm: qemu-system-aar Not tainted 3.19.0-rc7+ #254
  Hardware name: APM X-Gene Mustang board (DT)
  task: ffc3ee3aee00 ti: ffc3c044c000 task.ti: ffc3c044c000
  PC is at xgene_enet_process_ring+0x94/0x328
  LR is at xgene_enet_process_ring+0x78/0x328
  pc : [ffc0003f9058] lr : [ffc0003f903c] pstate: 8145
  sp : ffc3c044fa00
  x29: ffc3c044fa00 x28: ffc0fe8aa218
  x27:  x26: 
  x25: ffc3ee2b7000 x24: 0040
  x23: ffc0fe8aa418 x22: 01ff
  x21: 0001 x20: ffc0ff058380
  x19: 001c x18: 007f82d1c1f0
  x17: 007f84afbc90 x16: ffc0001a6a8c
  x15: 007f84b805a0 x14: 
  x13: d0d03820 x12: 
  x11: 0024 x10: d0d30a20
  x9 : ffc00031da28 x8 : ffbdc000
  x7 : ffc3cae0285e x6 : 0040fec0
  x5 : 0c08100801400148 x4 : 0040ff00
  x3 : 000200d1 x2 : 0066
  x1 : 0043cae0285e x0 : ffc3ee2bb818

  Process qemu-system-aar (pid: 6643, stack limit = 0xffc3c044c058)
  Stack: (0xffc3c044fa00 to 0xffc3c045)
  fa00: c044fa70 ffc3 003f93d0 ffc0 fe8aa290 ffc0  
  fa20: 0040  0078e000 ffc0 0016cac3 0001 c044fb20 ffc3
  fa40: ff7d4000 0003 007825c0 ffc0 012c  fff565c0 ffc3
  fa60: ffc0  ee2b7000 ffc3 c044faa0 ffc3 004a5cec ffc0
  fa80: fe8aa290 ffc0   0040  84b805a0 007f
  faa0: c044fb40 ffc3 000b5da0 ffc0 c044c000 ffc3 0078e000 ffc0
  fac0: 0077faa0 ffc0 c044fb40 ffc3 0018  0101 
  fae0: 0003  0078e0c0 ffc0 0078e0d8 ffc0  
  fb00: 0008  006fbd90 ffc0 006fb9f0 ffc0 007e3d74 ffc0
  fb20: c044fb20 ffc3 c044fb20 ffc3 c044fb30 ffc3 c044fb30 ffc3
  fb40: c044fbc0 ffc3 000b6134 ffc0 0078 ffc0  
  fb60:   2010 ff80 6145   
  fb80: 011a  001d  0079e000 ffc0 c044c000 ffc3
  fba0: 000a  0016cac2 0001 00570c08 ffc0 084040c0 000a
  fbc0: c044fbe0 ffc3 000ecb2c ffc0 0078 ffc0 000ecafc ffc0
  fbe0: c044fc20 ffc3 00082420 ffc0 00797000 ffc0 c044fc50 ffc3
  fc00: 200c ff80 000fc014 ffc0 ee01 ffc3 000a253c 005c
  fc20: c044fd70 ffc3 00085da8 ffc0   fd024c90 ffc0
  fc40: c044fd70 ffc3 000d0938 ffc0 fd024c98 ffc0 ee3aee00 ffc3
  fc60:     ae80   
  fc80:   c7e8ed00 5df42439 001d  0092 
  fca0:   001b    0092 
  fcc0:   84b805a0 007f 001a6a8c ffc0 84afbc90 007f
  fce0: 82d1c1f0 007f   fd024c90 ffc0  
  fd00: feabe300 ffc0 ae80    011a 
  fd20: 001d  0079e000 ffc0 c044c000 ffc3 c044fd70 ffc3
  fd40: 0009c1d0 ffc0 c044fd70 ffc3 000d0938 ffc0 6145 
  fd60: c044fd70 ffc3 0009c1a4 ffc0 c044fda0 ffc3 0009c2e0 ffc0
  fd80: feabe300 ffc0 fd024c90 ffc0 0079e000 ffc0 c044c000 
  fda0: c044fe10 ffc3 001a6824 ffc0 feabe300 ffc0

[Kernel-packages] [Bug 1425576] Re: Occasional crash in APM xgene enet driver on kernels prior to v3.19

Hmm, right commit ecf6ba83, the fix for this bug, is in mainline as of
3.19 final, so Vivid should already have the fix for both bugs.

Maybe I'll build a Utopic test kernel using the master-next branch.

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

Title:
  Occasional crash in APM xgene enet driver on kernels prior to v3.19

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged

Bug description:
  This crash was submitted upstream and a fix was already present, but
  it didn't land until the 3.19 kernel. This bug is to track getting
  that fix into trusty and utopic.

  Unable to handle kernel NULL pointer dereference at virtual address 00c0
  pgd = ffc3e639a000
  [00c0] *pgd=0043e629d003, *pud=0043e629d003, *pmd=
  Internal error: Oops: 9606 [#1] PREEMPT SMP
  Modules linked in:
  CPU: 0 PID: 6643 Comm: qemu-system-aar Not tainted 3.19.0-rc7+ #254
  Hardware name: APM X-Gene Mustang board (DT)
  task: ffc3ee3aee00 ti: ffc3c044c000 task.ti: ffc3c044c000
  PC is at xgene_enet_process_ring+0x94/0x328
  LR is at xgene_enet_process_ring+0x78/0x328
  pc : [ffc0003f9058] lr : [ffc0003f903c] pstate: 8145
  sp : ffc3c044fa00
  x29: ffc3c044fa00 x28: ffc0fe8aa218
  x27:  x26: 
  x25: ffc3ee2b7000 x24: 0040
  x23: ffc0fe8aa418 x22: 01ff
  x21: 0001 x20: ffc0ff058380
  x19: 001c x18: 007f82d1c1f0
  x17: 007f84afbc90 x16: ffc0001a6a8c
  x15: 007f84b805a0 x14: 
  x13: d0d03820 x12: 
  x11: 0024 x10: d0d30a20
  x9 : ffc00031da28 x8 : ffbdc000
  x7 : ffc3cae0285e x6 : 0040fec0
  x5 : 0c08100801400148 x4 : 0040ff00
  x3 : 000200d1 x2 : 0066
  x1 : 0043cae0285e x0 : ffc3ee2bb818

  Process qemu-system-aar (pid: 6643, stack limit = 0xffc3c044c058)
  Stack: (0xffc3c044fa00 to 0xffc3c045)
  fa00: c044fa70 ffc3 003f93d0 ffc0 fe8aa290 ffc0  
  fa20: 0040  0078e000 ffc0 0016cac3 0001 c044fb20 ffc3
  fa40: ff7d4000 0003 007825c0 ffc0 012c  fff565c0 ffc3
  fa60: ffc0  ee2b7000 ffc3 c044faa0 ffc3 004a5cec ffc0
  fa80: fe8aa290 ffc0   0040  84b805a0 007f
  faa0: c044fb40 ffc3 000b5da0 ffc0 c044c000 ffc3 0078e000 ffc0
  fac0: 0077faa0 ffc0 c044fb40 ffc3 0018  0101 
  fae0: 0003  0078e0c0 ffc0 0078e0d8 ffc0  
  fb00: 0008  006fbd90 ffc0 006fb9f0 ffc0 007e3d74 ffc0
  fb20: c044fb20 ffc3 c044fb20 ffc3 c044fb30 ffc3 c044fb30 ffc3
  fb40: c044fbc0 ffc3 000b6134 ffc0 0078 ffc0  
  fb60:   2010 ff80 6145   
  fb80: 011a  001d  0079e000 ffc0 c044c000 ffc3
  fba0: 000a  0016cac2 0001 00570c08 ffc0 084040c0 000a
  fbc0: c044fbe0 ffc3 000ecb2c ffc0 0078 ffc0 000ecafc ffc0
  fbe0: c044fc20 ffc3 00082420 ffc0 00797000 ffc0 c044fc50 ffc3
  fc00: 200c ff80 000fc014 ffc0 ee01 ffc3 000a253c 005c
  fc20: c044fd70 ffc3 00085da8 ffc0   fd024c90 ffc0
  fc40: c044fd70 ffc3 000d0938 ffc0 fd024c98 ffc0 ee3aee00 ffc3
  fc60:     ae80   
  fc80:   c7e8ed00 5df42439 001d  0092 
  fca0:   001b    0092 
  fcc0:   84b805a0 007f 001a6a8c ffc0 84afbc90 007f
  fce0: 82d1c1f0 007f   fd024c90 ffc0  
  fd00: feabe300 ffc0 ae80    011a 
  fd20: 001d  0079e000 ffc0 c044c000 ffc3 c044fd70 ffc3
  fd40: 0009c1d0 ffc0 c044fd70 ffc3 000d0938 ffc0 6145 
  fd60: c044fd70 ffc3 0009c1a4 ffc0 c044fda0 ffc3 0009c2e0 ffc0
  fd80: feabe300 ffc0 fd024c90 ffc0 0079e000 ffc0 c044c000 
  fda0: c044fe10 ffc3 001a6824 ffc0 feabe300 ffc0  
  fdc0: edc06f70 ffc3 000b  ae80  0015 
  fde0: 011a  0040 ae80 c044fe20 ffc3 0019772c ffc0
  fe00: edb3 ffc3 0001  c044fe90 ffc3 001a6b10 ffc0
  fe20:   feabe301 ffc0 feabe300 ffc0  
  fe40: c044fe70 ffc3 001b0a2c ffc0

[Kernel-packages] [Bug 1428111] Re: Kernel crash on Dell Latitude 5530 (tg3 driver involved)

2015-03-04 Thread Andreas Herr

Due to the nature of this bug, I am not able to give a log. I will try
the upstream kernel and give feedback.

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

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

Title:
  Kernel crash on Dell Latitude 5530 (tg3 driver involved)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 14.10 to 15.04 the system is not starting
  anymore. After disabling the splash screen I get lots of Error
  messages on the console. The system is unresponsive. Kernel 3.16 runs
  without problems. So does 3.19 on another system without Broadcom LAN-
  adapter. screenshot is attached. The error occures before entering
  the password for Luks-encryption. So it's very likely, it still doing
  initrd-stuff ...

  System is a Dell Latitude 5530, Core i5, 16 GB RAM
  running Ubuntu 15.04 (AMD64) with all updates available until 2015-03-04 
(upgraded from 14.10)

  lspci.log  dmesg.log  are taken wth the old kernel 3.16 as was not
  able to boot 3.19.

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

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

[Kernel-packages] [Bug 1420575] Re: Ubuntu-LE lpar won't boot with vTPM enabled

2015-03-04 Thread Leann Ogasawara

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

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

Title:
  Ubuntu-LE lpar won't boot with vTPM enabled

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]
  Ubuntu-LE lpar on PowerVM system doesn't boot when vTPM is enabled.
  It will fail to boot, showing B200A101 reference code on the HMC.

  Without vTPM, the lpar boots up just fine.

  [Fix]
  commit 84eb186bc37c0900b53077ca21cf6dd15823a232 upstream (not in v3.19)

  [Test Case]
  Boot system with vTPM enabled, ensure system doesn't fail to boot.

  --
  Here is the console output when attempting to activate the lpar with vTPM 
enabled after which it fails to boot:

  Enter Number of Running Partition (q to quit): 24
  24
  Opening Virtual Terminal On Partition br13p29 . . .

   Open in progress

   Open Completed.

  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM

    1 = SMS Menu  5 = Default Boot List
    8 = Open Firmware Prompt  6 = Stored Boot List

   Memory  Keyboard Network Speaker
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM STARTING SOFTWARE   IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBMPLEASE WAIT...   IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
  IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM

Re: [Kernel-packages] [Bug 1338555] Re: Keyboard completely unresponsive

2015-03-04 Thread Bashar

OK. I started all over on this same laptop with a fresh install of 14.04.2
which I also updated. Then from the mainline kernel list I downloaded the
three relevant files inside v3.13-trusty. After reboot the keyboard wasn't
responding. Then back to v4.0-rc2-vivid/ on which the keyboard was fine.
Going halfway between the two back and forth, the 'last bad commit' as you
called it was v3.17-rc5-utopic/ and right above it in the list
v3.17-rc6-utopic/ which was the first good one where my keyboard functioned
properly. Just to confirm my results I tested v3.17-rc4-utopic/ where the
keyboard also didn't respond. Moreover v3.17-rc4-utopic/ right above the
first good commit was checked and the keyboard was fine.
There are other details in the wiki about using github but I'm afraid they
weren't very clear to me.

Hope that was helpful.

On Sun, Mar 1, 2015 at 5:51 PM, Bashar Maree bma...@gmail.com wrote:

I think I roughly understand this requirement. So basically I'm supposed
to go back the mainline kernel list where I used the top link in the
previous email and starting with the original trusty kernel go midway up
the list and test that kernel (as above) and keep using this search
algorithm in addition to testing until the kernel where the bug got fixed
is pinpointed. However when I downloaded the [v3.14-trusty/ 25-Feb-2015
09:38] kernel and installed it using [sudo dpkg -i *.deb] and then booted
into it the keyboard worked fine. Maybe because I already edited the
/etc/default/grub file on this same machine as described above.

On Wed, Feb 25, 2015 at 2:56 AM, Christopher M. Penalver
christopher.m.penal...@gmail.com wrote:

Bashar, the next step is to fully reverse commit bisect from kernel 3.13
to 4.0-rc1 in order to identify the last bad commit, followed
immediately by the first good one. Once this commit has been identified,
then it may be reviewed as a candidate for backporting into your
release. Could you please do this following

https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
?

Please note, finding adjacent kernel versions is not fully commit
bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

** Tags removed: kernel-fixed-upstream-4.0.0-04rc1
** Tags added: apport-bug compiz-0.9 i386 kernel-fixed-upstream-4.0-rc1
needs-reverse-bisect trusty ubuntu

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

Title:
Keyboard completely unresponsive

To manage notifications about this bug go to:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1338555/+subscriptions

--
Bashar Maree

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

Title:
Keyboard completely unresponsive

Status in linux package in Ubuntu:
Incomplete

Bug description:
Trying the USB live session of 14.04 i-386 on my laptop but the
keyboard isn't responding. I'm filing this bug against xorg as stated
in the 'DebuggingKeyboardDetection' wiki page. I plugged in a USB
keyboard in order to be able to file this report.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
CasperVersion: 1.340
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: Mon Jul 7 12:03:56 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] RV530/M56-P [Mobility Radeon X1600]
[1002:71c5] (prog-if 00 [VGA controller])
Subsystem: LG Electronics, Inc. Device [1854:0068]
LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
MachineType: LG Electronics S1-M401E1
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true persistent
file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet
splash -- maybe-ubiquity
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/16/2006
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: RKYWSF0B
dmi.board.name: ROCKY
dmi.board.vendor: LG Electronics
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag

[Kernel-packages] [Bug 1307744] Re: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2: bcmwl kernel module failed to build [error: too few arguments to function ‘cfg80211_ibss_joined’]

2015-03-04 Thread Philip J. Threepwood

I still had this very same bug on an Asus f555l, I managed to get it
working with package  bcmwl-kernel-source_6.30.223.248+bdcom-
0ubuntu1_amd64.deb which is not the one from the repos. I do not
understand if the bug is going to be actually fixed or what.

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

Title:
  bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2: bcmwl kernel module
  failed to build [error: too few arguments to function
  ‘cfg80211_ibss_joined’]

Status in bcmwl package in Ubuntu:
  Fix Released

Bug description:
  installation of the kernel 3.15-RC1 on trusty...

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 3.15.0-031500rc1-generic
  Date: Tue Apr 15 01:19:44 2014
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.141+bdcom-0ubuntu2:/var/lib/dkms/bcmwl/6.30.223.141+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:1844:4:
 error: too few arguments to function ‘cfg80211_ibss_joined’
  InstallationDate: Installed on 2014-04-13 (1 days ago)
  InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326)
  PackageVersion: 6.30.223.141+bdcom-0ubuntu2
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.141+bdcom-0ubuntu2: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1416277] Re: toshiba_acpi: Unknown key 158

@Robert, does this test kernel fix both this bug and bug 1416302 ?

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

Title:
  toshiba_acpi: Unknown key 158

Status in linux package in Ubuntu:
  In Progress

Bug description:
  If I press the wireless key (see attached image) on my Toshiba P50W I
  get the following error in dmesg:

  toshiba_acpi: Unknown key 158

  I'd expect this key to toggle flight mode.
  --- 
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob2980 F pulseaudio
   /dev/snd/controlC1:  bob2980 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=5033984a-21af-482d-a1fd-c075e818cd12
  InstallationDate: Installed on 2013-12-26 (400 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: TOSHIBA Satellite P50W-B
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=885f0f10-b818-4eb4-8ff4-d067e16bef2f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-11-generic N/A
   linux-backports-modules-3.18.0-11-generic  N/A
   linux-firmware 1.141
  Tags:  vivid
  Uname: Linux 3.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2013-12-26 (400 days ago)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin netdev plugdev 
sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/08/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.40:bd08/08/2014:svnTOSHIBA:pnSatelliteP50W-B:pvrPSVP2A-00F002:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite P50W-B
  dmi.product.version: PSVP2A-00F002
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1428302] [NEW] Add Satellite L845 to alternative keymap.

Public bug reported:

An alternative keymap is needed for the Satellite L845.  Reported in bug
1416277 by Enzo.  Creating bug to send patch upstream and SRU.

** Affects: linux (Ubuntu)
 Importance: Medium
 Assignee: Joseph Salisbury (jsalisbury)
 Status: In Progress


** Tags: utopic vivid

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = Joseph Salisbury (jsalisbury)

** Tags added: utopic 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/1428302

Title:
  Add Satellite L845 to alternative keymap.

Status in linux package in Ubuntu:
  In Progress

Bug description:
  An alternative keymap is needed for the Satellite L845.  Reported in
  bug 1416277 by Enzo.  Creating bug to send patch upstream and SRU.

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

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

[Kernel-packages] [Bug 1425576] Re: Occasional crash in APM xgene enet driver on kernels prior to v3.19

I built a Utopic test kernel from the master-next branch, with a cherry-
pick of commit ecf6ba83d.

It can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1425576/

Can you test this kernel to see if it resolves the bug and does not
exhibit bug 1426043 ?

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

Title:
  Occasional crash in APM xgene enet driver on kernels prior to v3.19

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Trusty:
  Triaged
Status in linux source package in Utopic:
  Triaged

Bug description:
  This crash was submitted upstream and a fix was already present, but
  it didn't land until the 3.19 kernel. This bug is to track getting
  that fix into trusty and utopic.

  Unable to handle kernel NULL pointer dereference at virtual address 00c0
  pgd = ffc3e639a000
  [00c0] *pgd=0043e629d003, *pud=0043e629d003, *pmd=
  Internal error: Oops: 9606 [#1] PREEMPT SMP
  Modules linked in:
  CPU: 0 PID: 6643 Comm: qemu-system-aar Not tainted 3.19.0-rc7+ #254
  Hardware name: APM X-Gene Mustang board (DT)
  task: ffc3ee3aee00 ti: ffc3c044c000 task.ti: ffc3c044c000
  PC is at xgene_enet_process_ring+0x94/0x328
  LR is at xgene_enet_process_ring+0x78/0x328
  pc : [ffc0003f9058] lr : [ffc0003f903c] pstate: 8145
  sp : ffc3c044fa00
  x29: ffc3c044fa00 x28: ffc0fe8aa218
  x27:  x26: 
  x25: ffc3ee2b7000 x24: 0040
  x23: ffc0fe8aa418 x22: 01ff
  x21: 0001 x20: ffc0ff058380
  x19: 001c x18: 007f82d1c1f0
  x17: 007f84afbc90 x16: ffc0001a6a8c
  x15: 007f84b805a0 x14: 
  x13: d0d03820 x12: 
  x11: 0024 x10: d0d30a20
  x9 : ffc00031da28 x8 : ffbdc000
  x7 : ffc3cae0285e x6 : 0040fec0
  x5 : 0c08100801400148 x4 : 0040ff00
  x3 : 000200d1 x2 : 0066
  x1 : 0043cae0285e x0 : ffc3ee2bb818

  Process qemu-system-aar (pid: 6643, stack limit = 0xffc3c044c058)
  Stack: (0xffc3c044fa00 to 0xffc3c045)
  fa00: c044fa70 ffc3 003f93d0 ffc0 fe8aa290 ffc0  
  fa20: 0040  0078e000 ffc0 0016cac3 0001 c044fb20 ffc3
  fa40: ff7d4000 0003 007825c0 ffc0 012c  fff565c0 ffc3
  fa60: ffc0  ee2b7000 ffc3 c044faa0 ffc3 004a5cec ffc0
  fa80: fe8aa290 ffc0   0040  84b805a0 007f
  faa0: c044fb40 ffc3 000b5da0 ffc0 c044c000 ffc3 0078e000 ffc0
  fac0: 0077faa0 ffc0 c044fb40 ffc3 0018  0101 
  fae0: 0003  0078e0c0 ffc0 0078e0d8 ffc0  
  fb00: 0008  006fbd90 ffc0 006fb9f0 ffc0 007e3d74 ffc0
  fb20: c044fb20 ffc3 c044fb20 ffc3 c044fb30 ffc3 c044fb30 ffc3
  fb40: c044fbc0 ffc3 000b6134 ffc0 0078 ffc0  
  fb60:   2010 ff80 6145   
  fb80: 011a  001d  0079e000 ffc0 c044c000 ffc3
  fba0: 000a  0016cac2 0001 00570c08 ffc0 084040c0 000a
  fbc0: c044fbe0 ffc3 000ecb2c ffc0 0078 ffc0 000ecafc ffc0
  fbe0: c044fc20 ffc3 00082420 ffc0 00797000 ffc0 c044fc50 ffc3
  fc00: 200c ff80 000fc014 ffc0 ee01 ffc3 000a253c 005c
  fc20: c044fd70 ffc3 00085da8 ffc0   fd024c90 ffc0
  fc40: c044fd70 ffc3 000d0938 ffc0 fd024c98 ffc0 ee3aee00 ffc3
  fc60:     ae80   
  fc80:   c7e8ed00 5df42439 001d  0092 
  fca0:   001b    0092 
  fcc0:   84b805a0 007f 001a6a8c ffc0 84afbc90 007f
  fce0: 82d1c1f0 007f   fd024c90 ffc0  
  fd00: feabe300 ffc0 ae80    011a 
  fd20: 001d  0079e000 ffc0 c044c000 ffc3 c044fd70 ffc3
  fd40: 0009c1d0 ffc0 c044fd70 ffc3 000d0938 ffc0 6145 
  fd60: c044fd70 ffc3 0009c1a4 ffc0 c044fda0 ffc3 0009c2e0 ffc0
  fd80: feabe300 ffc0 fd024c90 ffc0 0079e000 ffc0 c044c000 
  fda0: c044fe10 ffc3 001a6824 ffc0 feabe300 ffc0  
  fdc0: edc06f70 ffc3 000b  ae80  0015 
  fde0: 011a  0040 ae80 c044fe20 ffc3 0019772c ffc0
  fe00: edb3 ffc3 0001  c044fe90 ffc3 001a6b10 ffc0
  fe20:   feabe301 ffc0 feabe300 ffc0

[Kernel-packages] [Bug 1428111] Re: Kernel crash on Dell Latitude 5530 (tg3 driver involved)

** Tags added: performing-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/1428111

Title:
  Kernel crash on Dell Latitude 5530 (tg3 driver involved)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 14.10 to 15.04 the system is not starting
  anymore. After disabling the splash screen I get lots of Error
  messages on the console. The system is unresponsive. Kernel 3.16 runs
  without problems. So does 3.19 on another system without Broadcom LAN-
  adapter. screenshot is attached. The error occures before entering
  the password for Luks-encryption. So it's very likely, it still doing
  initrd-stuff ...

  System is a Dell Latitude 5530, Core i5, 16 GB RAM
  running Ubuntu 15.04 (AMD64) with all updates available until 2015-03-04 
(upgraded from 14.10)

  lspci.log  dmesg.log  are taken wth the old kernel 3.16 as was not
  able to boot 3.19.

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

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

[Kernel-packages] [Bug 1352821] Re: 0489:e078 - Qualcom Atheros - Ubuntu 14.04 bluetooth not working

A request has been sent upstream for inclusion in all the stable
kernels.

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

Title:
  0489:e078 - Qualcom Atheros - Ubuntu 14.04 bluetooth not working

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

Bug description:
  Hi,

  Nature of peoblem : Bluetooth not wotrking under Ubuntu 14.04 but wifi
  working fine. pls help to provide the solution

  Vendor ID : 0489:e078
  Make of Wifi BT combo : Qualcom Atheros QCA9565 /AR9565 

  Regds,
  Bala S

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

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

[Kernel-packages] [Bug 1397028] Re: Add support for the backported lts-utopic stack

2015-03-04 Thread Brian Murray

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

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

Title:
  Add support for the backported lts-utopic stack

Status in bcmwl package in Ubuntu:
  Invalid
Status in bcmwl source package in Precise:
  Fix Committed
Status in bcmwl source package in Trusty:
  Fix Released

Bug description:
  SRU request:

  [Impact]

   * As a result of this bug, bcmwl-kernel-source will fail to build the
  module against linux-generic-lts-utopic in Ubuntu 14.04.2.

  [Test Case]

   * Enable the trusty-proposed repository and install bcmwl-kernel-
  source (6.30.223.248+bdcom-0ubuntu0.1).

   * Install linux-generic-lts-utopic

   * If the package installs without errors from DKMS with both the
  linux-generic and linux-generic-lts-utopic kernels, then the patches
  work correctly.

  [Regression Potential]

   * The patches that I backported from 15.04 will preserve the current
  driver behaviour on linux-generic (3.13) and linux-generic-lts-utopic
  (3.16), thanks to the use of specific macros in the code which check
  the kernel version. As a result, no regressions of any kind can be
  expected on these kernels. As a plus, support for kernels up to 3.18
  is also included.

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

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

[Kernel-packages] [Bug 1416277] Re: toshiba_acpi: Unknown key 158

2015-03-04 Thread Robert Ancell

@Joseph. Yes; both kernels seem to generate appropriate events for the
wireless, video mode and touchpad keys.

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

Title:
  toshiba_acpi: Unknown key 158

Status in linux package in Ubuntu:
  In Progress

Bug description:
  If I press the wireless key (see attached image) on my Toshiba P50W I
  get the following error in dmesg:

  toshiba_acpi: Unknown key 158

  I'd expect this key to toggle flight mode.
  --- 
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob2980 F pulseaudio
   /dev/snd/controlC1:  bob2980 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=5033984a-21af-482d-a1fd-c075e818cd12
  InstallationDate: Installed on 2013-12-26 (400 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: TOSHIBA Satellite P50W-B
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=885f0f10-b818-4eb4-8ff4-d067e16bef2f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-11-generic N/A
   linux-backports-modules-3.18.0-11-generic  N/A
   linux-firmware 1.141
  Tags:  vivid
  Uname: Linux 3.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2013-12-26 (400 days ago)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin netdev plugdev 
sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/08/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.40:bd08/08/2014:svnTOSHIBA:pnSatelliteP50W-B:pvrPSVP2A-00F002:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite P50W-B
  dmi.product.version: PSVP2A-00F002
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1419938] Re: hang in mlx5_create_map_eq in Ubuntu 15.04 due to not getting interrupts (mlx5) (Mellanox)

2015-03-04 Thread Leann Ogasawara

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

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

Title:
  hang in mlx5_create_map_eq in Ubuntu 15.04 due to not getting
  interrupts (mlx5) (Mellanox)

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  ---Problem Description---
  While installing Ubuntu 15.04 LE in powerNV system, I see the following error:

  
  [  242.141309] INFO: task systemd-udevd:623 blocked for more than 120 seconds.
  [  242.141408]   Tainted: GE  3.18.0-12-generic #13-Ubuntu
  [  242.141463] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
  [  242.141529] systemd-udevd   D 3fff8ad27d24 0   623603 
0x0004
  [  242.141597] Call Trace:
  [  242.141625] [c02fe2dbad50] [0005] 0x5 (unreliable)

  
  Mellanox Error from trace:

  [2.609984] /build/buildd/linux-3.18.0/drivers/rtc/hctosys.c: unable to 
open rtc device (rtc0)
  [2.611142] Freeing unused kernel memory: 5760K (c0d9 - 
c133)
  starting version 218
  [2.664785] scsi_transport_fc: module verification failed: signature 
and/or  required key missing - tainting kernel
  [2.668055] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014)
  [2.668124] mlx4_core: Initializing :01:00.0
   

  ---uname output---
  Linux powerio-le21 3.16.0-23-generic #31-Ubuntu SMP Tue Oct 21 17:55:08 UTC 
2014 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Mellanox device which seems to be causing the error:
  :01:00.0 Ethernet controller: Mellanox Technologies MT26448 [ConnectX EN 
10GigE, PCIe 2.0 5GT/s] (rev b0)
   

   
  Machine Type = 8286-42A PowerNV 
   
  ---Debugger---
  ---Steps to Reproduce---
  1. Start install of Ubuntu 15.04 LE
  2. Installer does not start at all. We see the error

  Install ISO Information: Ubuntu 15.04 - vivid-server-ppc64el.iso
   
  Install method: DVD
   
  Install disk info: # ethtool -i  eth17
  driver: mlx4_en
  version: 2.2-1 (Feb 2014)
  firmware-version: 2.9.1326
  bus-info: :01:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: no
  supports-register-dump: no
  supports-priv-flags: yes
   
  The issue is that we are not getting interrupts. 

  I forced to install Mellanox OFED in my virtual guest with ubuntu
  15.04 and I do not see the issue with that code so I will try to look
  tonight for differences between that code and upstream to see if I can
  spot the issue.

  The problem is related to the following commit:

  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/drivers/net/ethernet/mellanox/mlx5/core?id=c7a08ac7ee68b9af0d5af99c7b34b574cac4d144

  They forgot to set the page size for UAR to adapter so that is why is
  not working. So any kernel for power that gets that patch in mlx5 will
  see this issue.

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

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

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

Public bug reported:

This bug is for tracking the 3.13.0-47.78~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, 04. March 2015 20:02 UTC
kernel-stable-phase:Prepare
kernel-stable-phase-changed:Wednesday, 04. March 2015 20:02 UTC
kernel-stable-master-bug:1427733

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Platform QA Team (canonical-platform-qa)
 Status: New

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

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

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

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


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

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

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

** Tags added: precise

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Changed in:

[Kernel-packages] [Bug 1423672] Re: ext4 turned read-only during logrotate daily run

2015-03-04 Thread Simon Déziel

This occurred on another VM. I guess I will have to roll our the 4.0-rc2
kernel everywhere.

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

Title:
  ext4 turned read-only during logrotate daily run

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed that one of my VM had this dmesg -T output:

  [Tue Feb 17 09:53:27 2015] systemd-udevd[5433]: starting version 204
  [Thu Feb 19 06:25:08 2015] EXT4-fs error (device vda1): 
ext4_mb_generate_buddy:756: group 5, block bitmap and bg descriptor 
inconsistent: 16446 vs 16445 free clusters
  [Thu Feb 19 06:25:09 2015] Aborting journal on device vda1-8.
  [Thu Feb 19 06:25:09 2015] EXT4-fs (vda1): Remounting filesystem read-only
  [Thu Feb 19 06:25:09 2015] [ cut here ]
  [Thu Feb 19 06:25:09 2015] WARNING: CPU: 0 PID: 9946 at 
/build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 
__ext4_handle_dirty_metadata+0x1a2/0x1c0()
  [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 
nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables 
x_tables serio_raw psmouse floppy
  [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Not tainted 
3.13.0-45-generic #74-Ubuntu
  [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
  [Thu Feb 19 06:25:09 2015]  0009 880003a11aa0 
81720eb6 
  [Thu Feb 19 06:25:09 2015]  880003a11ad8 810677cd 
88c41340 
  [Thu Feb 19 06:25:09 2015]  88000a58e000 81835280 
1302 880003a11ae8
  [Thu Feb 19 06:25:09 2015] Call Trace:
  [Thu Feb 19 06:25:09 2015]  [81720eb6] dump_stack+0x45/0x56
  [Thu Feb 19 06:25:09 2015]  [810677cd] 
warn_slowpath_common+0x7d/0xa0
  [Thu Feb 19 06:25:09 2015]  [810678aa] warn_slowpath_null+0x1a/0x20
  [Thu Feb 19 06:25:09 2015]  [8126e862] 
__ext4_handle_dirty_metadata+0x1a2/0x1c0
  [Thu Feb 19 06:25:09 2015]  [81246a5a] ? ext4_dirty_inode+0x2a/0x60
  [Thu Feb 19 06:25:09 2015]  [81277086] ext4_free_blocks+0x646/0xbf0
  [Thu Feb 19 06:25:09 2015]  [810aacc5] ? wake_up_bit+0x25/0x30
  [Thu Feb 19 06:25:09 2015]  [812685b5] ext4_ext_rm_leaf+0x505/0x8f0
  [Thu Feb 19 06:25:09 2015]  [81267527] ? 
__ext4_ext_check+0x197/0x370
  [Thu Feb 19 06:25:09 2015]  [8126ad00] ? 
ext4_ext_remove_space+0xc0/0x7e0
  [Thu Feb 19 06:25:09 2015]  [8126af5c] 
ext4_ext_remove_space+0x31c/0x7e0
  [Thu Feb 19 06:25:09 2015]  [8126d300] ext4_ext_truncate+0xb0/0xe0
  [Thu Feb 19 06:25:09 2015]  [81244eb9] ext4_truncate+0x379/0x3c0
  [Thu Feb 19 06:25:09 2015]  [81245a18] ext4_evict_inode+0x408/0x4d0
  [Thu Feb 19 06:25:09 2015]  [811d8f60] evict+0xb0/0x1b0
  [Thu Feb 19 06:25:09 2015]  [811d9775] iput+0xf5/0x180
  [Thu Feb 19 06:25:09 2015]  [811d4698] __dentry_kill+0x1a8/0x200
  [Thu Feb 19 06:25:09 2015]  [811d4795] dput+0xa5/0x180
  [Thu Feb 19 06:25:09 2015]  [811bf7e6] __fput+0x176/0x260
  [Thu Feb 19 06:25:09 2015]  [811bf91e] fput+0xe/0x10
  [Thu Feb 19 06:25:09 2015]  [810882f7] task_work_run+0xa7/0xe0
  [Thu Feb 19 06:25:09 2015]  [81013ed7] do_notify_resume+0x97/0xb0
  [Thu Feb 19 06:25:09 2015]  [81731c2a] int_signal+0x12/0x17
  [Thu Feb 19 06:25:09 2015] ---[ end trace ebff9843d81b5c41 ]---
  [Thu Feb 19 06:25:09 2015] BUG: unable to handle kernel NULL pointer 
dereference at 0028
  [Thu Feb 19 06:25:09 2015] IP: [8125d4c1] 
__ext4_error_inode+0x31/0x160
  [Thu Feb 19 06:25:09 2015] PGD 167067 PUD 161067 PMD 0 
  [Thu Feb 19 06:25:09 2015] Oops:  [#1] SMP 
  [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 
nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables 
x_tables serio_raw psmouse floppy
  [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Tainted: G
W 3.13.0-45-generic #74-Ubuntu
  [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
  [Thu Feb 19 06:25:09 2015] task: 880009ac4800 ti: 880003a1 
task.ti: 880003a1
  [Thu Feb 19 06:25:09 2015] RIP: 0010:[8125d4c1]  
[8125d4c1] __ext4_error_inode+0x31/0x160
  [Thu Feb 19 06:25:09 2015] RSP: :880003a11a58  EFLAGS: 00010292
  [Thu Feb 19 06:25:09 2015] RAX:  RBX:  RCX: 
0086
  [Thu Feb 19 06:25:09 2015] RDX: 1302 RSI: 81a6e81f RDI: 

  [Thu Feb 19 06:25:09 2015] RBP: 880003a11ae8 R08: 81a78568 R09: 
0005
  [Thu Feb 19 06:25:09

[Kernel-packages] [Bug 1427733] Re: linux: 3.13.0-47.78 -proposed tracker

All builds are complete, packages in this bug can be copied to
-proposed.

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

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

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

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

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

** Changed in: kernel-sru-workflow/package-testing
   Status: New = Confirmed

** Description changed:

  This bug is for tracking the 3.13.0-47.78 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, 03. March 2015 15:29 UTC
- kernel-stable-phase:Prepare
- kernel-stable-phase-changed:Tuesday, 03. March 2015 15:29 UTC
+ kernel-stable-phase:CopyToProposed
+ kernel-stable-Prepare-package-end:Wednesday, 04. March 2015 20:03 UTC
+ kernel-stable-Promote-to-proposed-start:Wednesday, 04. March 2015 20:03 UTC
+ kernel-stable-phase-changed:Wednesday, 04. March 2015 20:03 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/1427733

Title:
  linux: 3.13.0-47.78 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  New
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:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.13.0-47.78 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, 03. March 2015 15:29 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Wednesday, 04. March 2015 20:03 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 04. March 2015 20:03 UTC
  kernel-stable-phase-changed:Wednesday, 04. March 2015 20:03 UTC

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

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

[Kernel-packages] [Bug 1428111] Re: Kernel crash on Dell Latitude 5530 (tg3 driver involved)

2015-03-04 Thread Andreas Herr

Kernel 4.0.0-04rc2-generic #201503031836 is working (so far). System
boots up as normal. No suspicious entries in the logfiles.

** Tags added: kernel-fixed-upstream

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

Title:
  Kernel crash on Dell Latitude 5530 (tg3 driver involved)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu 14.10 to 15.04 the system is not starting
  anymore. After disabling the splash screen I get lots of Error
  messages on the console. The system is unresponsive. Kernel 3.16 runs
  without problems. So does 3.19 on another system without Broadcom LAN-
  adapter. screenshot is attached. The error occures before entering
  the password for Luks-encryption. So it's very likely, it still doing
  initrd-stuff ...

  System is a Dell Latitude 5530, Core i5, 16 GB RAM
  running Ubuntu 15.04 (AMD64) with all updates available until 2015-03-04 
(upgraded from 14.10)

  lspci.log  dmesg.log  are taken wth the old kernel 3.16 as was not
  able to boot 3.19.

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

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

[Kernel-packages] [Bug 1416277] Re: toshiba_acpi: Unknown key 158

Thanks for testing.  I'll send this patch upstream and SRU to Ubuntu.

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = Joseph Salisbury (jsalisbury)

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

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

Title:
  toshiba_acpi: Unknown key 158

Status in linux package in Ubuntu:
  In Progress

Bug description:
  If I press the wireless key (see attached image) on my Toshiba P50W I
  get the following error in dmesg:

  toshiba_acpi: Unknown key 158

  I'd expect this key to toggle flight mode.
  --- 
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob2980 F pulseaudio
   /dev/snd/controlC1:  bob2980 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=5033984a-21af-482d-a1fd-c075e818cd12
  InstallationDate: Installed on 2013-12-26 (400 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: TOSHIBA Satellite P50W-B
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=885f0f10-b818-4eb4-8ff4-d067e16bef2f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-11-generic N/A
   linux-backports-modules-3.18.0-11-generic  N/A
   linux-firmware 1.141
  Tags:  vivid
  Uname: Linux 3.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2013-12-26 (400 days ago)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin netdev plugdev 
sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/08/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.40:bd08/08/2014:svnTOSHIBA:pnSatelliteP50W-B:pvrPSVP2A-00F002:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite P50W-B
  dmi.product.version: PSVP2A-00F002
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1423672] Re: ext4 turned read-only during logrotate daily run

2015-03-04 Thread Simon Déziel

** Summary changed:

- ext4 turned read-only following a cronjob run
+ ext4 turned read-only during logrotate daily run

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

Title:
  ext4 turned read-only during logrotate daily run

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed that one of my VM had this dmesg -T output:

  [Tue Feb 17 09:53:27 2015] systemd-udevd[5433]: starting version 204
  [Thu Feb 19 06:25:08 2015] EXT4-fs error (device vda1): 
ext4_mb_generate_buddy:756: group 5, block bitmap and bg descriptor 
inconsistent: 16446 vs 16445 free clusters
  [Thu Feb 19 06:25:09 2015] Aborting journal on device vda1-8.
  [Thu Feb 19 06:25:09 2015] EXT4-fs (vda1): Remounting filesystem read-only
  [Thu Feb 19 06:25:09 2015] [ cut here ]
  [Thu Feb 19 06:25:09 2015] WARNING: CPU: 0 PID: 9946 at 
/build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 
__ext4_handle_dirty_metadata+0x1a2/0x1c0()
  [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 
nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables 
x_tables serio_raw psmouse floppy
  [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Not tainted 
3.13.0-45-generic #74-Ubuntu
  [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
  [Thu Feb 19 06:25:09 2015]  0009 880003a11aa0 
81720eb6 
  [Thu Feb 19 06:25:09 2015]  880003a11ad8 810677cd 
88c41340 
  [Thu Feb 19 06:25:09 2015]  88000a58e000 81835280 
1302 880003a11ae8
  [Thu Feb 19 06:25:09 2015] Call Trace:
  [Thu Feb 19 06:25:09 2015]  [81720eb6] dump_stack+0x45/0x56
  [Thu Feb 19 06:25:09 2015]  [810677cd] 
warn_slowpath_common+0x7d/0xa0
  [Thu Feb 19 06:25:09 2015]  [810678aa] warn_slowpath_null+0x1a/0x20
  [Thu Feb 19 06:25:09 2015]  [8126e862] 
__ext4_handle_dirty_metadata+0x1a2/0x1c0
  [Thu Feb 19 06:25:09 2015]  [81246a5a] ? ext4_dirty_inode+0x2a/0x60
  [Thu Feb 19 06:25:09 2015]  [81277086] ext4_free_blocks+0x646/0xbf0
  [Thu Feb 19 06:25:09 2015]  [810aacc5] ? wake_up_bit+0x25/0x30
  [Thu Feb 19 06:25:09 2015]  [812685b5] ext4_ext_rm_leaf+0x505/0x8f0
  [Thu Feb 19 06:25:09 2015]  [81267527] ? 
__ext4_ext_check+0x197/0x370
  [Thu Feb 19 06:25:09 2015]  [8126ad00] ? 
ext4_ext_remove_space+0xc0/0x7e0
  [Thu Feb 19 06:25:09 2015]  [8126af5c] 
ext4_ext_remove_space+0x31c/0x7e0
  [Thu Feb 19 06:25:09 2015]  [8126d300] ext4_ext_truncate+0xb0/0xe0
  [Thu Feb 19 06:25:09 2015]  [81244eb9] ext4_truncate+0x379/0x3c0
  [Thu Feb 19 06:25:09 2015]  [81245a18] ext4_evict_inode+0x408/0x4d0
  [Thu Feb 19 06:25:09 2015]  [811d8f60] evict+0xb0/0x1b0
  [Thu Feb 19 06:25:09 2015]  [811d9775] iput+0xf5/0x180
  [Thu Feb 19 06:25:09 2015]  [811d4698] __dentry_kill+0x1a8/0x200
  [Thu Feb 19 06:25:09 2015]  [811d4795] dput+0xa5/0x180
  [Thu Feb 19 06:25:09 2015]  [811bf7e6] __fput+0x176/0x260
  [Thu Feb 19 06:25:09 2015]  [811bf91e] fput+0xe/0x10
  [Thu Feb 19 06:25:09 2015]  [810882f7] task_work_run+0xa7/0xe0
  [Thu Feb 19 06:25:09 2015]  [81013ed7] do_notify_resume+0x97/0xb0
  [Thu Feb 19 06:25:09 2015]  [81731c2a] int_signal+0x12/0x17
  [Thu Feb 19 06:25:09 2015] ---[ end trace ebff9843d81b5c41 ]---
  [Thu Feb 19 06:25:09 2015] BUG: unable to handle kernel NULL pointer 
dereference at 0028
  [Thu Feb 19 06:25:09 2015] IP: [8125d4c1] 
__ext4_error_inode+0x31/0x160
  [Thu Feb 19 06:25:09 2015] PGD 167067 PUD 161067 PMD 0 
  [Thu Feb 19 06:25:09 2015] Oops:  [#1] SMP 
  [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 
nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables 
x_tables serio_raw psmouse floppy
  [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Tainted: G
W 3.13.0-45-generic #74-Ubuntu
  [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
  [Thu Feb 19 06:25:09 2015] task: 880009ac4800 ti: 880003a1 
task.ti: 880003a1
  [Thu Feb 19 06:25:09 2015] RIP: 0010:[8125d4c1]  
[8125d4c1] __ext4_error_inode+0x31/0x160
  [Thu Feb 19 06:25:09 2015] RSP: :880003a11a58  EFLAGS: 00010292
  [Thu Feb 19 06:25:09 2015] RAX:  RBX:  RCX: 
0086
  [Thu Feb 19 06:25:09 2015] RDX: 1302 RSI: 81a6e81f RDI: 

  [Thu Feb 19 06:25:09 2015] RBP: 880003a11ae8 R08: 81a78568 R09:

[Kernel-packages] [Bug 1426113] Re: devel: vbox drivers introduce symlinks which prevent use of orig.tar.gz

2015-03-04 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  devel: vbox drivers introduce symlinks which prevent use of
  orig.tar.gz

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The introduction of the vbox drivers prevent use of a .orig.tar.gz.
  Need to work out how to remove these and restore them on clean.

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

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

[Kernel-packages] [Bug 1428260] [NEW] __USE_GNU not being set by -std=gnu11 ( struct f_owner_ex not declared )

2015-03-04 Thread JVD

Public bug reported:

Not sure if this is a bug in libc6-dev (owner of /usr/include/fcntl.h)
or in linux-libc-dev (owner of /usr/include/linux/header that declares struct 
f_owner_ex) but
it definitely appears to be a bug.
I am trying to compile code that uses the new fcntl interfaces :
   F_SETOWN_EX (struct f_owner_ex *) (since Linux 2.6.32)
   F_GETOWN_EX (struct f_owner_ex *) (since Linux 2.6.32)
but I cannot get the 'struct f_owner_ex' structure to be declared
using the standard system headers - I must declare it manually in my code.
This is on a Ubuntu 14.04.2 LTS x86_64 system, fully up-to-date as
of 2015-03-04 , with:
  gcc :4:4.8.2-1ubuntu6
  libc6-dev:2.19-0ubuntu6.6 
  linux-libc-dev:  3.13.0-46.76

Attempts to compile for instance this program always fail :
$ cat /tmp/t_fcntl.c 
#include unistd.h
#include fcntl.h
void f(void) { struct f_owner_ex foe={0}; }
$ gcc -c /tmp/t_fcntl.c 
/tmp/t_fcntl.c: In function ‘f’:
/tmp/t_fcntl.c:3:23: error: variable ‘foe’ has initializer but incomplete type
 void f(void) { struct f_owner_ex foe={0}; }
   ^
/tmp/t_fcntl.c:3:23: warning: excess elements in struct initializer [enabled by 
default]
/tmp/t_fcntl.c:3:23: warning: (near initialization for ‘foe’) [enabled by 
default]
/tmp/t_fcntl.c:3:34: error: storage size of ‘foe’ isn’t known
 void f(void) { struct f_owner_ex foe={0}; }

I can see this structure is declared in two places:
1: /usr/include/bits/fcntl.h @ line 239:
#ifdef __USE_GNU
/* Owner types.  */
enum __pid_type
  {
F_OWNER_TID = 0,/* Kernel thread.  */
F_OWNER_PID,/* Process.  */
F_OWNER_PGRP,   /* Process group.  */
F_OWNER_GID = F_OWNER_PGRP  /* Alternative, obsolete name.  */
  };

/* Structure to use with F_GETOWN_EX and F_SETOWN_EX.  */
struct f_owner_ex
  {
enum __pid_type type;   /* Owner type of ID.  */
__pid_t pid;/* ID of owner.  */
  };
#endif

2: /usr/include/asm-generic/fcntl.h
struct f_owner_ex {
int type;
__kernel_pid_t  pid;
};
( I am assuming I should not be using the kernel's pid type ).

My understanding of __USE_GNU is that it is defined when 
-std=gnu* is specified on the compile command line, or when
_GNU_SOURCE=1 is set.  

Only when _GNU_SOURCE=1 is explicitly set is __USE_GNU being defined 
and the example compiles OK :
$ gcc -std=gnu11 -D_GNU_SOURCE=1 -c /tmp/t_fcntl.c 
OK, that worked!

$ gcc -std=gnu11  -c /tmp/t_fcntl.c 
/tmp/t_fcntl.c: In function ‘f’:
/tmp/t_fcntl.c:3:23: error: variable ‘foe’ has initializer but incomplete type
 void f(void) { struct f_owner_ex foe={0}; }
   ^
/tmp/t_fcntl.c:3:23: warning: excess elements in struct initializer [enabled by 
default]
/tmp/t_fcntl.c:3:23: warning: (near initialization for ‘foe’) [enabled by 
default]
/tmp/t_fcntl.c:3:34: error: storage size of ‘foe’ isn’t known
 void f(void) { struct f_owner_ex foe={0}; }
  ^
Why isn't _GNU_SOURCE being set when I've asked gcc to enable GNU extensions 
with --std=gnu11 ? 

From the Standards gcc info node :
 You may also select an extended version of the C language explicitly with 
... '-std=gnu11' (for C11 with GNU extensions)

It would appear that libc6-dev / linux-libc-dev has broken GCC's
'-std=gnuXX' support.

Also the fcntl.2 manual page makes no mention of _GNU_SOURCE needing to be 
defined 
in order to use F_SETOWN_EX .

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

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

Title:
  __USE_GNU not being set by -std=gnu11 ( struct f_owner_ex not declared
  )

Status in linux package in Ubuntu:
  New

Bug description:
  Not sure if this is a bug in libc6-dev (owner of /usr/include/fcntl.h)
  or in linux-libc-dev (owner of /usr/include/linux/header that declares struct 
f_owner_ex) but
  it definitely appears to be a bug.
  I am trying to compile code that uses the new fcntl interfaces :
 F_SETOWN_EX (struct f_owner_ex *) (since Linux 2.6.32)
 F_GETOWN_EX (struct f_owner_ex *) (since Linux 2.6.32)
  but I cannot get the 'struct f_owner_ex' structure to be declared
  using the standard system headers - I must declare it manually in my code.
  This is on a Ubuntu 14.04.2 LTS x86_64 system, fully up-to-date as
  of 2015-03-04 , with:
gcc :4:4.8.2-1ubuntu6
libc6-dev:2.19-0ubuntu6.6 
linux-libc-dev:  3.13.0-46.76

  Attempts to compile for instance this program always fail :
  $ cat /tmp/t_fcntl.c 
  #include unistd.h
  #include fcntl.h
  void f(void) { struct f_owner_ex foe={0}; }
  $ gcc -c /tmp/t_fcntl.c 
  /tmp/t_fcntl.c: In function ‘f’:
  /tmp/t_fcntl.c:3:23: error: variable ‘foe’ has initializer but incomplete type
   void f(void) { struct f_owner_ex foe={0}; }
 ^

[Kernel-packages] [Bug 1407313] Re: Physical buttons of touchpad do not work on Asus N53S (ETPS/2 Elantech Touchpad)

2015-03-04 Thread Sascha Biermanns

I have the same misbehaviour with kernel 3.19.0-7-generic on Ubuntu
15.04. Synclient -l shows that the ClickPad is activated - but it
doesn't react.

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

Title:
  Physical buttons of touchpad do not work on Asus N53S (ETPS/2 Elantech
  Touchpad)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Physical buttons for left and right button do not work at all on the
  touchpad of Asus N53S.

  I'm now on Linux Mint 17.1, but had the same issue previously on
  Ubuntu 13-10 (http://ubuntuforums.org/showthread.php?t=2196970).

  I have not found any real workaround.

  Plugging in a mouse all works just fine.

  Find attached relevant log files.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-37-generic 3.13.0-37.64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ros1994 F pulseaudio
  CurrentDesktop: X-Cinnamon
  CurrentDmesg: [   32.256027] nouveau E[   PDISP][:01:00.0] chid 0 mthd 
0x0080 data 0x 0x00085080
  Date: Sat Jan  3 18:24:37 2015
  HibernationDevice: RESUME=UUID=b9874704-5718-4a69-88a4-d6d5d08715d7
  InstallationDate: Installed on 2015-01-03 (0 days ago)
  InstallationMedia: Linux Mint 17.1 Rebecca - Release amd64 20141126
  MachineType: ASUSTeK Computer Inc. N53SV
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 inteldrmfb
   1 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=eef70fc7-ad88-4dee-abec-96153d2eb0ed ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.10
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N53SV.215
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N53SV
  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.:bvrN53SV.215:bd01/09/2012:svnASUSTeKComputerInc.:pnN53SV:pvr1.0:rvnASUSTeKComputerInc.:rnN53SV:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: N53SV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Kernel-packages] [Bug 1423672] Re: ext4 turned read-only during logrotate daily run

It would be good to know if v4.0-rc2 fixes this.  If it does, we can
look at the git logs to see what may be the fix, or perform a Reverse
bisect.

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

Title:
  ext4 turned read-only during logrotate daily run

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed that one of my VM had this dmesg -T output:

  [Tue Feb 17 09:53:27 2015] systemd-udevd[5433]: starting version 204
  [Thu Feb 19 06:25:08 2015] EXT4-fs error (device vda1): 
ext4_mb_generate_buddy:756: group 5, block bitmap and bg descriptor 
inconsistent: 16446 vs 16445 free clusters
  [Thu Feb 19 06:25:09 2015] Aborting journal on device vda1-8.
  [Thu Feb 19 06:25:09 2015] EXT4-fs (vda1): Remounting filesystem read-only
  [Thu Feb 19 06:25:09 2015] [ cut here ]
  [Thu Feb 19 06:25:09 2015] WARNING: CPU: 0 PID: 9946 at 
/build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 
__ext4_handle_dirty_metadata+0x1a2/0x1c0()
  [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 
nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables 
x_tables serio_raw psmouse floppy
  [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Not tainted 
3.13.0-45-generic #74-Ubuntu
  [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
  [Thu Feb 19 06:25:09 2015]  0009 880003a11aa0 
81720eb6 
  [Thu Feb 19 06:25:09 2015]  880003a11ad8 810677cd 
88c41340 
  [Thu Feb 19 06:25:09 2015]  88000a58e000 81835280 
1302 880003a11ae8
  [Thu Feb 19 06:25:09 2015] Call Trace:
  [Thu Feb 19 06:25:09 2015]  [81720eb6] dump_stack+0x45/0x56
  [Thu Feb 19 06:25:09 2015]  [810677cd] 
warn_slowpath_common+0x7d/0xa0
  [Thu Feb 19 06:25:09 2015]  [810678aa] warn_slowpath_null+0x1a/0x20
  [Thu Feb 19 06:25:09 2015]  [8126e862] 
__ext4_handle_dirty_metadata+0x1a2/0x1c0
  [Thu Feb 19 06:25:09 2015]  [81246a5a] ? ext4_dirty_inode+0x2a/0x60
  [Thu Feb 19 06:25:09 2015]  [81277086] ext4_free_blocks+0x646/0xbf0
  [Thu Feb 19 06:25:09 2015]  [810aacc5] ? wake_up_bit+0x25/0x30
  [Thu Feb 19 06:25:09 2015]  [812685b5] ext4_ext_rm_leaf+0x505/0x8f0
  [Thu Feb 19 06:25:09 2015]  [81267527] ? 
__ext4_ext_check+0x197/0x370
  [Thu Feb 19 06:25:09 2015]  [8126ad00] ? 
ext4_ext_remove_space+0xc0/0x7e0
  [Thu Feb 19 06:25:09 2015]  [8126af5c] 
ext4_ext_remove_space+0x31c/0x7e0
  [Thu Feb 19 06:25:09 2015]  [8126d300] ext4_ext_truncate+0xb0/0xe0
  [Thu Feb 19 06:25:09 2015]  [81244eb9] ext4_truncate+0x379/0x3c0
  [Thu Feb 19 06:25:09 2015]  [81245a18] ext4_evict_inode+0x408/0x4d0
  [Thu Feb 19 06:25:09 2015]  [811d8f60] evict+0xb0/0x1b0
  [Thu Feb 19 06:25:09 2015]  [811d9775] iput+0xf5/0x180
  [Thu Feb 19 06:25:09 2015]  [811d4698] __dentry_kill+0x1a8/0x200
  [Thu Feb 19 06:25:09 2015]  [811d4795] dput+0xa5/0x180
  [Thu Feb 19 06:25:09 2015]  [811bf7e6] __fput+0x176/0x260
  [Thu Feb 19 06:25:09 2015]  [811bf91e] fput+0xe/0x10
  [Thu Feb 19 06:25:09 2015]  [810882f7] task_work_run+0xa7/0xe0
  [Thu Feb 19 06:25:09 2015]  [81013ed7] do_notify_resume+0x97/0xb0
  [Thu Feb 19 06:25:09 2015]  [81731c2a] int_signal+0x12/0x17
  [Thu Feb 19 06:25:09 2015] ---[ end trace ebff9843d81b5c41 ]---
  [Thu Feb 19 06:25:09 2015] BUG: unable to handle kernel NULL pointer 
dereference at 0028
  [Thu Feb 19 06:25:09 2015] IP: [8125d4c1] 
__ext4_error_inode+0x31/0x160
  [Thu Feb 19 06:25:09 2015] PGD 167067 PUD 161067 PMD 0 
  [Thu Feb 19 06:25:09 2015] Oops:  [#1] SMP 
  [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 
nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables 
x_tables serio_raw psmouse floppy
  [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Tainted: G
W 3.13.0-45-generic #74-Ubuntu
  [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
  [Thu Feb 19 06:25:09 2015] task: 880009ac4800 ti: 880003a1 
task.ti: 880003a1
  [Thu Feb 19 06:25:09 2015] RIP: 0010:[8125d4c1]  
[8125d4c1] __ext4_error_inode+0x31/0x160
  [Thu Feb 19 06:25:09 2015] RSP: :880003a11a58  EFLAGS: 00010292
  [Thu Feb 19 06:25:09 2015] RAX:  RBX:  RCX: 
0086
  [Thu Feb 19 06:25:09 2015] RDX: 1302 RSI: 81a6e81f RDI: 

  [Thu Feb 19 06:25:09 2015] RBP: 880003a11ae8 R08:

[Kernel-packages] [Bug 1423672] Re: ext4 turned read-only during logrotate daily run

Also, did this issue start happening after an update/upgrade? Was there
a prior kernel version where you were not having this particular
problem? This will help determine if the problem you are seeing is the
result of a regression, and when this regression was introduced.   If
this is a regression, we could also perform a kernel bisect to identify
the commit that introduced the problem, if it's not fixed in 4.0.

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

Title:
  ext4 turned read-only during logrotate daily run

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed that one of my VM had this dmesg -T output:

  [Tue Feb 17 09:53:27 2015] systemd-udevd[5433]: starting version 204
  [Thu Feb 19 06:25:08 2015] EXT4-fs error (device vda1): 
ext4_mb_generate_buddy:756: group 5, block bitmap and bg descriptor 
inconsistent: 16446 vs 16445 free clusters
  [Thu Feb 19 06:25:09 2015] Aborting journal on device vda1-8.
  [Thu Feb 19 06:25:09 2015] EXT4-fs (vda1): Remounting filesystem read-only
  [Thu Feb 19 06:25:09 2015] [ cut here ]
  [Thu Feb 19 06:25:09 2015] WARNING: CPU: 0 PID: 9946 at 
/build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 
__ext4_handle_dirty_metadata+0x1a2/0x1c0()
  [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 
nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables 
x_tables serio_raw psmouse floppy
  [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Not tainted 
3.13.0-45-generic #74-Ubuntu
  [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
  [Thu Feb 19 06:25:09 2015]  0009 880003a11aa0 
81720eb6 
  [Thu Feb 19 06:25:09 2015]  880003a11ad8 810677cd 
88c41340 
  [Thu Feb 19 06:25:09 2015]  88000a58e000 81835280 
1302 880003a11ae8
  [Thu Feb 19 06:25:09 2015] Call Trace:
  [Thu Feb 19 06:25:09 2015]  [81720eb6] dump_stack+0x45/0x56
  [Thu Feb 19 06:25:09 2015]  [810677cd] 
warn_slowpath_common+0x7d/0xa0
  [Thu Feb 19 06:25:09 2015]  [810678aa] warn_slowpath_null+0x1a/0x20
  [Thu Feb 19 06:25:09 2015]  [8126e862] 
__ext4_handle_dirty_metadata+0x1a2/0x1c0
  [Thu Feb 19 06:25:09 2015]  [81246a5a] ? ext4_dirty_inode+0x2a/0x60
  [Thu Feb 19 06:25:09 2015]  [81277086] ext4_free_blocks+0x646/0xbf0
  [Thu Feb 19 06:25:09 2015]  [810aacc5] ? wake_up_bit+0x25/0x30
  [Thu Feb 19 06:25:09 2015]  [812685b5] ext4_ext_rm_leaf+0x505/0x8f0
  [Thu Feb 19 06:25:09 2015]  [81267527] ? 
__ext4_ext_check+0x197/0x370
  [Thu Feb 19 06:25:09 2015]  [8126ad00] ? 
ext4_ext_remove_space+0xc0/0x7e0
  [Thu Feb 19 06:25:09 2015]  [8126af5c] 
ext4_ext_remove_space+0x31c/0x7e0
  [Thu Feb 19 06:25:09 2015]  [8126d300] ext4_ext_truncate+0xb0/0xe0
  [Thu Feb 19 06:25:09 2015]  [81244eb9] ext4_truncate+0x379/0x3c0
  [Thu Feb 19 06:25:09 2015]  [81245a18] ext4_evict_inode+0x408/0x4d0
  [Thu Feb 19 06:25:09 2015]  [811d8f60] evict+0xb0/0x1b0
  [Thu Feb 19 06:25:09 2015]  [811d9775] iput+0xf5/0x180
  [Thu Feb 19 06:25:09 2015]  [811d4698] __dentry_kill+0x1a8/0x200
  [Thu Feb 19 06:25:09 2015]  [811d4795] dput+0xa5/0x180
  [Thu Feb 19 06:25:09 2015]  [811bf7e6] __fput+0x176/0x260
  [Thu Feb 19 06:25:09 2015]  [811bf91e] fput+0xe/0x10
  [Thu Feb 19 06:25:09 2015]  [810882f7] task_work_run+0xa7/0xe0
  [Thu Feb 19 06:25:09 2015]  [81013ed7] do_notify_resume+0x97/0xb0
  [Thu Feb 19 06:25:09 2015]  [81731c2a] int_signal+0x12/0x17
  [Thu Feb 19 06:25:09 2015] ---[ end trace ebff9843d81b5c41 ]---
  [Thu Feb 19 06:25:09 2015] BUG: unable to handle kernel NULL pointer 
dereference at 0028
  [Thu Feb 19 06:25:09 2015] IP: [8125d4c1] 
__ext4_error_inode+0x31/0x160
  [Thu Feb 19 06:25:09 2015] PGD 167067 PUD 161067 PMD 0 
  [Thu Feb 19 06:25:09 2015] Oops:  [#1] SMP 
  [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 
nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables 
x_tables serio_raw psmouse floppy
  [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Tainted: G
W 3.13.0-45-generic #74-Ubuntu
  [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
  [Thu Feb 19 06:25:09 2015] task: 880009ac4800 ti: 880003a1 
task.ti: 880003a1
  [Thu Feb 19 06:25:09 2015] RIP: 0010:[8125d4c1]  
[8125d4c1] __ext4_error_inode+0x31/0x160
  [Thu Feb 19 06:25:09 2015] RSP: :880003a11a58

[Kernel-packages] [Bug 1427680] Re: bluetooth on asus n551 not working

2015-03-04 Thread shutt1e

i'm just trying that, seem the patch is quite simple, as it finish to
build i'll test to see if there are firmware issues

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

Title:
  bluetooth on asus n551 not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  can't configure any bluetooth device with this laptop. bluetooth adapter is 
recognized and all seem working but it is unable to find any device on a scan.
  i tried installing blueman also but either it is unable to find any device.
  i've also read many posts with bluetooth solutions for 14.04 but none helped 
to solve the situation.
  i've also tried a mainline kernel (3.19) with no changes.
  currently i'm using 3.13.0-46-generic
  on the attached archive some files taken from the laptop (lspci,lsusb,rfkill 
list,dmesg |grep Blue,lsmod and the output of hciconfig -a)
  there are no evidences of problems but the bluetooth don't work.
  unluckly even the touchpad don't work so well on this laptop, so having to 
use the mouse is a pain

  
  late addition- i forgot to tell, on my dual boot system, the microsoft sculpt 
mouse bluetooth works as expected on windows 7
  Ubuntu is not able to see any blutooth device, i have tried 2 phones and this 
ms mouse, and is not seen by the phones also.

  
  ---
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hook   2242 F pulseaudio
   /dev/snd/controlC1:  hook   2242 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4e7d3097-1e36-4191-98d8-df04a9ce48d2
  InstallationDate: Installed on 2012-11-06 (847 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  MachineType: ASUSTeK COMPUTER INC. N551JM
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=822863c8-1a3d-4ef2-8f89-0a2e8dc58ab9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-46-generic N/A
   linux-backports-modules-3.13.0-46-generic  N/A
   linux-firmware 1.127.11
  Tags:  trusty
  Uname: Linux 3.13.0-46-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-01-04 (57 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551JM.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551JM
  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.:bvrN551JM.204:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N551JM
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1397028] Re: Add support for the backported lts-utopic stack

2015-03-04 Thread Launchpad Bug Tracker

This bug was fixed in the package bcmwl - 6.30.223.248+bdcom-0ubuntu0.1

---
bcmwl (6.30.223.248+bdcom-0ubuntu0.1) trusty-proposed; urgency=medium

  * New upstream release (LP: #1397028):
- This is an official public release from Broadcom.
  * debian/patches/0013-gcc.patch
- Fix build with recent versions of GCC. Credit
  for the patch goes to Robert Ancell.
  * debian/dkms.conf.in,
debian/patches/0014-add-support-for-Linux-3.17.patch,
debian/patches/0015-add-support-for-Linux-3.18.patch:
- Drop patches for kernels 3.10 (now upstream)
- Add support for Linux 3.17.
  Credit for the patch goes to Brian Norris.
- Add support for Linux 3.18.
  Credit for the patch goes to Krzysztof Kolasa.
 -- Alberto Milone alberto.mil...@canonical.com   Thu, 27 Nov 2014 16:36:00 
+0100

** Changed in: bcmwl (Ubuntu Trusty)
   Status: Fix Committed = Fix Released

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

Title:
  Add support for the backported lts-utopic stack

Status in bcmwl package in Ubuntu:
  Invalid
Status in bcmwl source package in Precise:
  Fix Committed
Status in bcmwl source package in Trusty:
  Fix Released

Bug description:
  SRU request:

  [Impact]

   * As a result of this bug, bcmwl-kernel-source will fail to build the
  module against linux-generic-lts-utopic in Ubuntu 14.04.2.

  [Test Case]

   * Enable the trusty-proposed repository and install bcmwl-kernel-
  source (6.30.223.248+bdcom-0ubuntu0.1).

   * Install linux-generic-lts-utopic

   * If the package installs without errors from DKMS with both the
  linux-generic and linux-generic-lts-utopic kernels, then the patches
  work correctly.

  [Regression Potential]

   * The patches that I backported from 15.04 will preserve the current
  driver behaviour on linux-generic (3.13) and linux-generic-lts-utopic
  (3.16), thanks to the use of specific macros in the code which check
  the kernel version. As a result, no regressions of any kind can be
  expected on these kernels. As a plus, support for kernels up to 3.18
  is also included.

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

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

[Kernel-packages] [Bug 1416302] Re: Toshiba P50W switch video mode and disable touchpad not working properly

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

** This bug has been marked a duplicate of bug 1416277
   toshiba_acpi: Unknown key 158

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

Title:
  Toshiba P50W switch video mode and disable touchpad not working
  properly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Toshiba P50W two of the keys are incorrectly connected.

  Pressing video mode toggle (Fn+F4) puts that machine to sleep. From 
acpi_listen:
  button/suspend SUSP 0080  K

  Pressing touchpad disable does nothing. From acpi_listen:
  video/switchmode VMOD 0080  K
  --- 
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob2980 F pulseaudio
   /dev/snd/controlC1:  bob2980 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=5033984a-21af-482d-a1fd-c075e818cd12
  InstallationDate: Installed on 2013-12-26 (400 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: TOSHIBA Satellite P50W-B
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=885f0f10-b818-4eb4-8ff4-d067e16bef2f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-11-generic N/A
   linux-backports-modules-3.18.0-11-generic  N/A
   linux-firmware 1.141
  Tags:  vivid
  Uname: Linux 3.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2013-12-26 (400 days ago)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin netdev plugdev 
sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/08/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.40:bd08/08/2014:svnTOSHIBA:pnSatelliteP50W-B:pvrPSVP2A-00F002:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite P50W-B
  dmi.product.version: PSVP2A-00F002
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1416277] Re: toshiba_acpi: Unknown key 158

Thanks for the update, Robert.  I broke the patch out into two separate
patches, one for each Toshiba models.  I'll send the patches upstream
and cc them to stable.  If upstream gives the thumbs up, I'll also SRU
them to the Ubuntu kernels.

The two models being the P50-W for this bug.  I created a separate bug
for the L845 model, reported by @Enzo, which is bug 1428302

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

Title:
  toshiba_acpi: Unknown key 158

Status in linux package in Ubuntu:
  In Progress

Bug description:
  If I press the wireless key (see attached image) on my Toshiba P50W I
  get the following error in dmesg:

  toshiba_acpi: Unknown key 158

  I'd expect this key to toggle flight mode.
  --- 
  ApportVersion: 2.15.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bob2980 F pulseaudio
   /dev/snd/controlC1:  bob2980 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=5033984a-21af-482d-a1fd-c075e818cd12
  InstallationDate: Installed on 2013-12-26 (400 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: TOSHIBA Satellite P50W-B
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic 
root=UUID=885f0f10-b818-4eb4-8ff4-d067e16bef2f ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3
  RelatedPackageVersions:
   linux-restricted-modules-3.18.0-11-generic N/A
   linux-backports-modules-3.18.0-11-generic  N/A
   linux-firmware 1.141
  Tags:  vivid
  Uname: Linux 3.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2013-12-26 (400 days ago)
  UserGroups: adm autopilot cdrom dip libvirtd lpadmin netdev plugdev 
sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 08/08/2014
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis ManuFacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.40:bd08/08/2014:svnTOSHIBA:pnSatelliteP50W-B:pvrPSVP2A-00F002:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite P50W-B
  dmi.product.version: PSVP2A-00F002
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1423672] Re: ext4 turned read-only during logrotate daily run

2015-03-04 Thread Simon Déziel

The first occurrence of this problem goes back to Feb 17th. While I keep
all the VMs up to date on a daily basis, I now have doubts about the
hypervisor's RAM (not ECC by the way). I brought all the VMs offline to
have their FSes checked (all ext4). Several of them needed fixing by
fsck. Since they are all part of a mdadm RAID1 array with 2 devices,
maybe there was some bit flipping on one of the drives.

Before loosing anyone's time on this issue, I'll first make sure the
hypervisor's RAM is sane. So I'll get back after some memtest86+ then
I'll look at the 4.0 kernel.

Thanks Joseph

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

Title:
  ext4 turned read-only during logrotate daily run

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I noticed that one of my VM had this dmesg -T output:

  [Tue Feb 17 09:53:27 2015] systemd-udevd[5433]: starting version 204
  [Thu Feb 19 06:25:08 2015] EXT4-fs error (device vda1): 
ext4_mb_generate_buddy:756: group 5, block bitmap and bg descriptor 
inconsistent: 16446 vs 16445 free clusters
  [Thu Feb 19 06:25:09 2015] Aborting journal on device vda1-8.
  [Thu Feb 19 06:25:09 2015] EXT4-fs (vda1): Remounting filesystem read-only
  [Thu Feb 19 06:25:09 2015] [ cut here ]
  [Thu Feb 19 06:25:09 2015] WARNING: CPU: 0 PID: 9946 at 
/build/buildd/linux-3.13.0/fs/ext4/ext4_jbd2.c:259 
__ext4_handle_dirty_metadata+0x1a2/0x1c0()
  [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 
nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables 
x_tables serio_raw psmouse floppy
  [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Not tainted 
3.13.0-45-generic #74-Ubuntu
  [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
  [Thu Feb 19 06:25:09 2015]  0009 880003a11aa0 
81720eb6 
  [Thu Feb 19 06:25:09 2015]  880003a11ad8 810677cd 
88c41340 
  [Thu Feb 19 06:25:09 2015]  88000a58e000 81835280 
1302 880003a11ae8
  [Thu Feb 19 06:25:09 2015] Call Trace:
  [Thu Feb 19 06:25:09 2015]  [81720eb6] dump_stack+0x45/0x56
  [Thu Feb 19 06:25:09 2015]  [810677cd] 
warn_slowpath_common+0x7d/0xa0
  [Thu Feb 19 06:25:09 2015]  [810678aa] warn_slowpath_null+0x1a/0x20
  [Thu Feb 19 06:25:09 2015]  [8126e862] 
__ext4_handle_dirty_metadata+0x1a2/0x1c0
  [Thu Feb 19 06:25:09 2015]  [81246a5a] ? ext4_dirty_inode+0x2a/0x60
  [Thu Feb 19 06:25:09 2015]  [81277086] ext4_free_blocks+0x646/0xbf0
  [Thu Feb 19 06:25:09 2015]  [810aacc5] ? wake_up_bit+0x25/0x30
  [Thu Feb 19 06:25:09 2015]  [812685b5] ext4_ext_rm_leaf+0x505/0x8f0
  [Thu Feb 19 06:25:09 2015]  [81267527] ? 
__ext4_ext_check+0x197/0x370
  [Thu Feb 19 06:25:09 2015]  [8126ad00] ? 
ext4_ext_remove_space+0xc0/0x7e0
  [Thu Feb 19 06:25:09 2015]  [8126af5c] 
ext4_ext_remove_space+0x31c/0x7e0
  [Thu Feb 19 06:25:09 2015]  [8126d300] ext4_ext_truncate+0xb0/0xe0
  [Thu Feb 19 06:25:09 2015]  [81244eb9] ext4_truncate+0x379/0x3c0
  [Thu Feb 19 06:25:09 2015]  [81245a18] ext4_evict_inode+0x408/0x4d0
  [Thu Feb 19 06:25:09 2015]  [811d8f60] evict+0xb0/0x1b0
  [Thu Feb 19 06:25:09 2015]  [811d9775] iput+0xf5/0x180
  [Thu Feb 19 06:25:09 2015]  [811d4698] __dentry_kill+0x1a8/0x200
  [Thu Feb 19 06:25:09 2015]  [811d4795] dput+0xa5/0x180
  [Thu Feb 19 06:25:09 2015]  [811bf7e6] __fput+0x176/0x260
  [Thu Feb 19 06:25:09 2015]  [811bf91e] fput+0xe/0x10
  [Thu Feb 19 06:25:09 2015]  [810882f7] task_work_run+0xa7/0xe0
  [Thu Feb 19 06:25:09 2015]  [81013ed7] do_notify_resume+0x97/0xb0
  [Thu Feb 19 06:25:09 2015]  [81731c2a] int_signal+0x12/0x17
  [Thu Feb 19 06:25:09 2015] ---[ end trace ebff9843d81b5c41 ]---
  [Thu Feb 19 06:25:09 2015] BUG: unable to handle kernel NULL pointer 
dereference at 0028
  [Thu Feb 19 06:25:09 2015] IP: [8125d4c1] 
__ext4_error_inode+0x31/0x160
  [Thu Feb 19 06:25:09 2015] PGD 167067 PUD 161067 PMD 0 
  [Thu Feb 19 06:25:09 2015] Oops:  [#1] SMP 
  [Thu Feb 19 06:25:09 2015] Modules linked in: nf_conntrack_ipv6 
nf_defrag_ipv6 ip6table_filter ip6_tables xt_tcpudp nf_conntrack_ipv4 
nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack iptable_filter ip_tables 
x_tables serio_raw psmouse floppy
  [Thu Feb 19 06:25:09 2015] CPU: 0 PID: 9946 Comm: logrotate Tainted: G
W 3.13.0-45-generic #74-Ubuntu
  [Thu Feb 19 06:25:09 2015] Hardware name: QEMU Standard PC (i440FX + PIIX, 
1996), BIOS Bochs 01/01/2011
  [Thu Feb 19 06:25:09 2015] task: 880009ac4800 ti: 880003a1 
task.ti:

[Kernel-packages] [Bug 1428111] Re: Kernel crash on Dell Latitude 5530 (tg3 driver involved)

Thanks for testing!

There are two commits in v4.0 that may be the fix:
d0af71a tg3: Hold tp-lock before calling tg3_halt() from tg3_init_one()
20d14a5 tg3: move init/deinit from open/close to probe/remove

I built a Vivid test kernel with a cherry-pick of these two commits.  It can be 
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1428111/

Can you test this kernel and see if it resolves this bug?

Note that you will need to install both the linux-image and linux-image-
extra .deb packages.

** Also affects: linux (Ubuntu Vivid)
   Importance: High
   Status: Confirmed

** Tags added: 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/1428111

Title:
  Kernel crash on Dell Latitude 5530 (tg3 driver involved)

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

Bug description:
  After upgrading from Ubuntu 14.10 to 15.04 the system is not starting
  anymore. After disabling the splash screen I get lots of Error
  messages on the console. The system is unresponsive. Kernel 3.16 runs
  without problems. So does 3.19 on another system without Broadcom LAN-
  adapter. screenshot is attached. The error occures before entering
  the password for Luks-encryption. So it's very likely, it still doing
  initrd-stuff ...

  System is a Dell Latitude 5530, Core i5, 16 GB RAM
  running Ubuntu 15.04 (AMD64) with all updates available until 2015-03-04 
(upgraded from 14.10)

  lspci.log  dmesg.log  are taken wth the old kernel 3.16 as was not
  able to boot 3.19.

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

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

[Kernel-packages] [Bug 1428351] [NEW] ISST-LTE: LPM on Ubuntu15.04 lpar hangs.

2015-03-04 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Defect Description:
---

LPM on Ubuntu15.04 LE lpar hangs at 0%. I tried it twice and waited for
more then 1 hour but there was not progress.

Details:
--
1. LPM stuck at 0% 
2. No work load tests are running on lpar.
3. Lpar is accessible though out on source CEC side.
4. Destination CEC shows lpar reference code as: End powering on VIO slots.


Machine version details:
---

root@highlp3:~# uname -a
Linux highlp3 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:57:41 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
root@highlp3:~#


root@highlp3:~# cat /etc/issue
Ubuntu Vivid Vervet (development branch) \n \l


VIOS version: 2.2.3.3
Source firmware: b0211p_1507.811
Destination firmware: b0211p_1507.811


Steps to recreate:
---
1. Install Ubuntu15.04 LE on a lpar.
2. Setup LPM environment (install RMC and RSCT packages).
3. Execute LPM operation on HMC.

First, there is a kernel fix needed to make sure the stream id is passed
in cpu endian during hcall to check VASI state. The following in the
dmesg log confirms that this issue is present:

[  666.978230] rtas_ibm_suspend_me: vasi_state returned -4

This is the relevant upstream commit:

commit 3df76a9dcc74d5f012b94ea01ed6e7aaf8362c5a
Author: Cyril Bur cyril...@gmail.com
Date:   Wed Jan 21 13:32:00 2015 +1100

powerpc/pseries: Fix endian problems with LE migration


Just found that this commit took part of kernel 3.19, which is going to be the 
default kernel for 15.04, so, we don't need to worry about asking Canonical to 
integrated it. 

#  git checkout v3.19-rc7
# git show 3df76a9dcc74d5f012b94ea01ed6e7aaf8362c5a

I have updated the kernel in lpar.

root@highlp3:~# dpkg -l | grep linux | grep 3.19.0-6
ii  linux-image-3.19.0-6-generic3.19.0-6.6   ppc64el
  Linux kernel image for version 3.19.0 on PowerPC 64el SMP
ii  linux-image-extra-3.19.0-6-generic  3.19.0-6.6   ppc64el
  Linux kernel extra modules for version 3.19.0 on PowerPC 64el SMP

Still LPM is getting hang. The difference is last time it got hung at 0%
this time it got hung at 99%.

I can't seem to get the console on the desintation even after a rmvterm.
I checked the cpus from the phyp debug console and all of the cpus seem
to be stuck at the same place.

NIA   C00809AC MSR   80019033 LR   C087D7B4

Can you please recover the lpar and look up the following addresses
using addr2line:

addr2line -e path to vmlinuz C00809AC
addr2line -e path to vmlinuz C087D7B4

And please install the kernel source as well so we can cross reference
those lines within the kernel.

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


** Tags: architecture-ppc64le bugnameltc-121922 severity-critical 
targetmilestone-inin---
-- 
ISST-LTE: LPM on Ubuntu15.04 lpar hangs.
https://bugs.launchpad.net/bugs/1428351
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 1397028] Update Released

2015-03-04 Thread Brian Murray

The verification of the Stable Release Update for bcmwl has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Add support for the backported lts-utopic stack

Status in bcmwl package in Ubuntu:
  Invalid
Status in bcmwl source package in Precise:
  Fix Committed
Status in bcmwl source package in Trusty:
  Fix Released

Bug description:
  SRU request:

  [Impact]

   * As a result of this bug, bcmwl-kernel-source will fail to build the
  module against linux-generic-lts-utopic in Ubuntu 14.04.2.

  [Test Case]

   * Enable the trusty-proposed repository and install bcmwl-kernel-
  source (6.30.223.248+bdcom-0ubuntu0.1).

   * Install linux-generic-lts-utopic

   * If the package installs without errors from DKMS with both the
  linux-generic and linux-generic-lts-utopic kernels, then the patches
  work correctly.

  [Regression Potential]

   * The patches that I backported from 15.04 will preserve the current
  driver behaviour on linux-generic (3.13) and linux-generic-lts-utopic
  (3.16), thanks to the use of specific macros in the code which check
  the kernel version. As a result, no regressions of any kind can be
  expected on these kernels. As a plus, support for kernels up to 3.18
  is also included.

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

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

[Kernel-packages] [Bug 1037456] Re: CVE-2012-3412

** Description changed:

  The sfc (aka Solarflare Solarstorm) driver in the Linux kernel before
  3.2.30 allows remote attackers to cause a denial of service (DMA
  descriptor consumption and network-controller outage) via crafted TCP
  packets that trigger a small MSS value.
  
  Break-Fix: - 30b678d844af3305cda5953467005cebb5d7b687
  Break-Fix: - 7e6d06f0de3f74ca929441add094518ae332257c
- Break-Fix: - 1485348d2424e1131ea42efc033cbd9366462b01

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

Title:
  CVE-2012-3412

Status in linux package in Ubuntu:
  Fix Released
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  Invalid
Status in linux-lts-backport-natty package in Ubuntu:
  Invalid
Status in linux-lts-backport-oneiric package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  New
Status in linux-lts-raring package in Ubuntu:
  New
Status in linux-lts-saucy package in Ubuntu:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Fix Released
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  Fix Released
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Invalid
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
Status in linux-lts-quantal source package in Lucid:
  New
Status in linux-lts-raring source package in Lucid:
  New
Status in linux-lts-saucy source package in Lucid:
  New
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Natty:
  Invalid
Status in linux-lts-backport-natty source package in Natty:
  Invalid
Status in linux-lts-backport-oneiric source package in Natty:
  Invalid
Status in linux-lts-backport-maverick source package in Oneiric:
  Invalid
Status in linux-lts-backport-natty source package in Oneiric:
  Invalid
Status in linux-lts-backport-oneiric source package in Oneiric:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  New
Status in linux-lts-raring source package in Precise:
  New
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package

[Kernel-packages] [Bug 1428351] Re: ISST-LTE: LPM on Ubuntu15.04 lpar hangs.

2015-03-04 Thread Luciano Chavez

** Package changed: ubuntu = linux (Ubuntu)

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

Title:
  ISST-LTE: LPM on Ubuntu15.04 lpar hangs.

Status in linux package in Ubuntu:
  New

Bug description:
  Defect Description:
  ---

  LPM on Ubuntu15.04 LE lpar hangs at 0%. I tried it twice and waited
  for more then 1 hour but there was not progress.

  Details:
  --
  1. LPM stuck at 0% 
  2. No work load tests are running on lpar.
  3. Lpar is accessible though out on source CEC side.
  4. Destination CEC shows lpar reference code as: End powering on VIO slots.

  
  Machine version details:
  ---

  root@highlp3:~# uname -a
  Linux highlp3 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:57:41 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
  root@highlp3:~#

  
  root@highlp3:~# cat /etc/issue
  Ubuntu Vivid Vervet (development branch) \n \l

  
  VIOS version: 2.2.3.3
  Source firmware: b0211p_1507.811
  Destination firmware: b0211p_1507.811

  
  Steps to recreate:
  ---
  1. Install Ubuntu15.04 LE on a lpar.
  2. Setup LPM environment (install RMC and RSCT packages).
  3. Execute LPM operation on HMC.

  First, there is a kernel fix needed to make sure the stream id is
  passed in cpu endian during hcall to check VASI state. The following
  in the dmesg log confirms that this issue is present:

  [  666.978230] rtas_ibm_suspend_me: vasi_state returned -4

  This is the relevant upstream commit:

  commit 3df76a9dcc74d5f012b94ea01ed6e7aaf8362c5a
  Author: Cyril Bur cyril...@gmail.com
  Date:   Wed Jan 21 13:32:00 2015 +1100

  powerpc/pseries: Fix endian problems with LE migration

  
  Just found that this commit took part of kernel 3.19, which is going to be 
the default kernel for 15.04, so, we don't need to worry about asking Canonical 
to integrated it. 

  #  git checkout v3.19-rc7
  # git show 3df76a9dcc74d5f012b94ea01ed6e7aaf8362c5a

  I have updated the kernel in lpar.

  root@highlp3:~# dpkg -l | grep linux | grep 3.19.0-6
  ii  linux-image-3.19.0-6-generic3.19.0-6.6   ppc64el  
Linux kernel image for version 3.19.0 on PowerPC 64el SMP
  ii  linux-image-extra-3.19.0-6-generic  3.19.0-6.6   ppc64el  
Linux kernel extra modules for version 3.19.0 on PowerPC 64el SMP

  Still LPM is getting hang. The difference is last time it got hung at
  0% this time it got hung at 99%.

  I can't seem to get the console on the desintation even after a
  rmvterm. I checked the cpus from the phyp debug console and all of the
  cpus seem to be stuck at the same place.

  NIA   C00809AC MSR   80019033 LR   C087D7B4

  Can you please recover the lpar and look up the following addresses
  using addr2line:

  addr2line -e path to vmlinuz C00809AC
  addr2line -e path to vmlinuz C087D7B4

  And please install the kernel source as well so we can cross reference
  those lines within the kernel.

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

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

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

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

apport-collect 1425398

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

** Tags added: 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/1425398

Title:
  Apparmor uses rsyslogd profile for different processes - utopic HWE

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in apparmor source package in Trusty:
  New
Status in linux source package in Trusty:
  Incomplete
Status in linux-lts-utopic source package in Trusty:
  Invalid

Bug description:
  Hi.

  I've noticed that apparmor loads /usr/sbin/rsyslogd profile for
  completely unrelated processes:

  Feb 25 08:36:19 emma kernel: [  134.796218] audit: type=1400 
audit(1424842579.429:245): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd 
requested_mask=r denied_mask=r fsuid=0 ouid=0
  Feb 25 08:36:23 emma kernel: [  139.330989] audit: type=1400 
audit(1424842583.965:246): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo 
requested_mask=r denied_mask=r fsuid=0 ouid=0
  Feb 25 08:35:42 emma kernel: [   97.912402] audit: type=1400 
audit(1424842542.565:241): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie 
requested_mask=r denied_mask=r fsuid=103 ouid=0
  Feb 25 08:34:43 emma kernel: [   38.867998] audit: type=1400 
audit(1424842483.546:226): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd 
requested_mask=r denied_mask=r fsuid=0 ouid=0

  
  I'm not sure how apparmor decides which profile to use for which task, but is 
shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc.

  
  I'm running:
  # lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  # dpkg -l | grep apparmor
  ii  apparmor2.8.95~2430-0ubuntu5.1   
amd64User-space parser utility for AppArmor
  ii  apparmor-profiles   2.8.95~2430-0ubuntu5.1   
all  Profiles for AppArmor Security policies
  ii  apparmor-utils  2.8.95~2430-0ubuntu5.1   
amd64Utilities for controlling AppArmor
  ii  libapparmor-perl2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Perl bindings
  ii  libapparmor1:amd64  2.8.95~2430-0ubuntu5.1   
amd64changehat AppArmor library
  ii  python3-apparmor2.8.95~2430-0ubuntu5.1   
amd64AppArmor Python3 utility library
  ii  python3-libapparmor 2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Python3 bindings

  # uname -a
  Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Kernel-packages] [Bug 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE

So after looking into this more it looks like this is actually a bug in
the trusty kernel, that has been fixed on utopic.

Trusty needs a kernel patch and an update to its policy.


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

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

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

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

** Changed in: linux-lts-utopic (Ubuntu)
   Status: New = Invalid

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = John Johansen (jjohansen)

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) = 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/1425398

Title:
  Apparmor uses rsyslogd profile for different processes - utopic HWE

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in apparmor source package in Trusty:
  New
Status in linux source package in Trusty:
  Incomplete
Status in linux-lts-utopic source package in Trusty:
  Invalid

Bug description:
  Hi.

  I've noticed that apparmor loads /usr/sbin/rsyslogd profile for
  completely unrelated processes:

  Feb 25 08:36:19 emma kernel: [  134.796218] audit: type=1400 
audit(1424842579.429:245): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd 
requested_mask=r denied_mask=r fsuid=0 ouid=0
  Feb 25 08:36:23 emma kernel: [  139.330989] audit: type=1400 
audit(1424842583.965:246): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo 
requested_mask=r denied_mask=r fsuid=0 ouid=0
  Feb 25 08:35:42 emma kernel: [   97.912402] audit: type=1400 
audit(1424842542.565:241): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie 
requested_mask=r denied_mask=r fsuid=103 ouid=0
  Feb 25 08:34:43 emma kernel: [   38.867998] audit: type=1400 
audit(1424842483.546:226): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd 
requested_mask=r denied_mask=r fsuid=0 ouid=0

  
  I'm not sure how apparmor decides which profile to use for which task, but is 
shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc.

  
  I'm running:
  # lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  # dpkg -l | grep apparmor
  ii  apparmor2.8.95~2430-0ubuntu5.1   
amd64User-space parser utility for AppArmor
  ii  apparmor-profiles   2.8.95~2430-0ubuntu5.1   
all  Profiles for AppArmor Security policies
  ii  apparmor-utils  2.8.95~2430-0ubuntu5.1   
amd64Utilities for controlling AppArmor
  ii  libapparmor-perl2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Perl bindings
  ii  libapparmor1:amd64  2.8.95~2430-0ubuntu5.1   
amd64changehat AppArmor library
  ii  python3-apparmor2.8.95~2430-0ubuntu5.1   
amd64AppArmor Python3 utility library
  ii  python3-libapparmor 2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Python3 bindings

  # uname -a
  Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Kernel-packages] [Bug 1427399] Re: CVE-2012-6689

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

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New = Fix Released

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

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

** Changed in: linux-goldfish (Ubuntu Vivid)
   Status: New = Invalid

** Changed in: linux-goldfish (Ubuntu Utopic)
   Status: New = Invalid

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

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

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

** Changed in: linux (Ubuntu Vivid)
   Status: New = Invalid

** Changed in: linux (Ubuntu Utopic)
   Status: New = Invalid

** Changed in: linux-ti-omap4 (Ubuntu Precise)
   Status: New = Fix Committed

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

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

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

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

Title:
  CVE-2012-6689

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Committed
Status in linux source package in Trusty:
  Invalid
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid

[Kernel-packages] [Bug 1427680] Re: bluetooth on asus n551 not working

2015-03-04 Thread shutt1e

ok, just adding the id to both ath3k.c and btusb.c  and recompiling it
make both modules recognize the bt interface. i have successfully paired
my bt mouse (found it disconnected and have to reconnect manually after
a reboot but this is another problem)

i hope this device will be added on next kernel releases due it is
missing on 4.0 too

this patch is for kernel 3.13.0-46-generic #77-Ubuntu

--- original/linux-3.13.0/drivers/bluetooth/ath3k.c 2015-03-04 
23:31:07.0 +0100
+++ patched/linux-3.13.0/drivers/bluetooth/ath3k.c  2015-03-04 
22:42:21.865060950 +0100
@@ -99,6 +99,8 @@
{ USB_DEVICE(0x0cf3, 0x3121) },
{ USB_DEVICE(0x0cf3, 0xe003) },
{ USB_DEVICE(0x13d3, 0x3408) },
+   { USB_DEVICE(0x13d3, 0x3474) },
+   
 
/* Atheros AR5BBU12 with sflash firmware */
{ USB_DEVICE(0x0489, 0xE02C) },
@@ -144,6 +146,7 @@
{ USB_DEVICE(0x0cf3, 0x3121), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0cf3, 0xe003), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x13d3, 0x3408), .driver_info = BTUSB_ATH3012 },
+   { USB_DEVICE(0x13d3, 0x3474), .driver_info = BTUSB_ATH3012 },
 
/* Atheros AR5BBU22 with sflash firmware */
{ USB_DEVICE(0x0489, 0xE03C), .driver_info = BTUSB_ATH3012 },



--- original/linux-3.13.0/drivers/bluetooth/btusb.c 2015-03-04 
23:31:07.0 +0100
+++ patched/linux-3.13.0/drivers/bluetooth/btusb.c  2015-03-04 
14:38:34.403678567 +0100
@@ -175,6 +175,8 @@
{ USB_DEVICE(0x0cf3, 0x3121), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x0cf3, 0xe003), .driver_info = BTUSB_ATH3012 },
{ USB_DEVICE(0x13d3, 0x3408), .driver_info = BTUSB_ATH3012 },
+   { USB_DEVICE(0x13d3, 0x3474), .driver_info = BTUSB_ATH3012 },
+   
 
/* Atheros AR5BBU12 with sflash firmware */
{ USB_DEVICE(0x0489, 0xe02c), .driver_info = BTUSB_IGNORE },

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

Title:
  bluetooth on asus n551 not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  can't configure any bluetooth device with this laptop. bluetooth adapter is 
recognized and all seem working but it is unable to find any device on a scan.
  i tried installing blueman also but either it is unable to find any device.
  i've also read many posts with bluetooth solutions for 14.04 but none helped 
to solve the situation.
  i've also tried a mainline kernel (3.19) with no changes.
  currently i'm using 3.13.0-46-generic
  on the attached archive some files taken from the laptop (lspci,lsusb,rfkill 
list,dmesg |grep Blue,lsmod and the output of hciconfig -a)
  there are no evidences of problems but the bluetooth don't work.
  unluckly even the touchpad don't work so well on this laptop, so having to 
use the mouse is a pain

  
  late addition- i forgot to tell, on my dual boot system, the microsoft sculpt 
mouse bluetooth works as expected on windows 7
  Ubuntu is not able to see any blutooth device, i have tried 2 phones and this 
ms mouse, and is not seen by the phones also.

  
  ---
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hook   2242 F pulseaudio
   /dev/snd/controlC1:  hook   2242 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4e7d3097-1e36-4191-98d8-df04a9ce48d2
  InstallationDate: Installed on 2012-11-06 (847 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  MachineType: ASUSTeK COMPUTER INC. N551JM
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=822863c8-1a3d-4ef2-8f89-0a2e8dc58ab9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-46-generic N/A
   linux-backports-modules-3.13.0-46-generic  N/A
   linux-firmware 1.127.11
  Tags:  trusty
  Uname: Linux 3.13.0-46-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-01-04 (57 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551JM.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551JM
  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.:bvrN551JM.204:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:

[Kernel-packages] [Bug 1415507] Re: CVE-2013-7421

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

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

** Description changed:

- Linux kernel crypto api unprivileged arbitrary module load
+ The Crypto API in the Linux kernel before 3.18.5 allows local users to
+ load arbitrary kernel modules via a bind system call for an AF_ALG
+ socket with a module name in the salg_name field, a different
+ vulnerability than CVE-2014-9644.
  
  Break-Fix: 03c8efc1ffeb6b82a22c1af8dd908af349563314 
5d26a105b5a73e5635eae0629b42fa0a90e07b7b
  Break-Fix: 03c8efc1ffeb6b82a22c1af8dd908af349563314 
3e14dcf7cb80b34a1f38b55bc96f02d23fdf

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

Title:
  CVE-2013-7421

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Invalid
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  Invalid
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  New
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  Fix Committed
Status in linux-armadaxp source package in Utopic:

[Kernel-packages] [Bug 1413109] Re: CVE-2014-8160

** Description changed:

- [iptables restriction bypass if a protocol handler kernel module not
- loaded]
+ net/netfilter/nf_conntrack_proto_generic.c in the Linux kernel before
+ 3.18 generates incorrect conntrack entries during handling of certain
+ iptables rule sets for the SCTP, DCCP, GRE, and UDP-Lite protocols,
+ which allows remote attackers to bypass intended access restrictions via
+ packets with disallowed port numbers.
  
  Break-Fix: - db29a9508a9246e77087c5531e45b2c88ec6988b

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

Title:
  CVE-2014-8160

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  Fix Released
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source

[Kernel-packages] [Bug 1423391] Re: CVE-2014-9683

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New = Fix Committed

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

** Description changed:

- ecryptfs 1-byte overwrite
+ Off-by-one error in the ecryptfs_decode_from_filename function in
+ fs/ecryptfs/crypto.c in the eCryptfs subsystem in the Linux kernel
+ before 3.18.2 allows local users to cause a denial of service (buffer
+ overflow and system crash) or possibly gain privileges via a crafted
+ filename.
  
  Break-Fix: - 942080643bce061c3dd9d5718d3b745dcb39a8bc

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

Title:
  CVE-2014-9683

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-armadaxp source package in Precise:
  Fix Committed
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  New
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  Fix Released
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in

[Kernel-packages] [Bug 1414651] Re: CVE-2015-0239

** Description changed:

- Linux 2.6.32 - 3.18 that runs KVM may enable a malicious guest process
- to crash the guest OS or launch a privilege escalation attack on the
- guest. The attack can be launched by tricking the hypervisor to emulate
- a SYSENTER instruction in 16-bit mode, if the guest OS does not
- initialize the SYSENTER MSRs. KVM does not check under these conditions
- that the selector IA32_SYSENTER_CS is not zero, and does not generate a
- #GP exception as real hardware does. Instead, it sets the guest
- instruction pointer to zero and changes the code privilege level (CPL)
- to zero (privileged). Note that the attack can only be issued under very
- certain conditions (see the details below). Windows and distro Linux
- guest OSes should be safe. The bug existed since the introduction of
- SYSENTER emulation (em_sysenter function on recent Linux releases), in
- commit 8c60435261deaefeb53ce3222d04d7d5bea81296 , which is present in
- Linux 2.6.32 - 3.18.
+ The em_sysenter function in arch/x86/kvm/emulate.c in the Linux kernel
+ before 3.18.5, when the guest OS lacks SYSENTER MSR initialization,
+ allows guest OS users to gain guest OS privileges or cause a denial of
+ service (guest OS crash) by triggering use of a 16-bit code segment for
+ emulation of a SYSENTER instruction.
  
  Break-Fix: - f3747379accba8e95d70cec0eae0582c8c182050

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

Title:
  CVE-2015-0239

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in

[Kernel-packages] [Bug 1407945] Re: CVE-2014-9419

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

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New = Fix Committed

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

Title:
  CVE-2014-9419

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-armadaxp source package in Precise:
  Fix Committed
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  Fix Released
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  Fix Released
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:

[Kernel-packages] [Bug 1416506] Re: CVE-2015-1421

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

** Changed in: linux (Ubuntu Vivid)
   Status: New = Invalid

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

** Changed in: linux-armadaxp (Ubuntu Precise)
   Status: New = Fix Committed

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

Title:
  CVE-2015-1421

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Fix Committed
Status in linux-armadaxp source package in Precise:
  Fix Committed
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  Fix Committed
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in

[Kernel-packages] [Bug 1420027] Re: CVE-2015-1465

** Changed in: linux (Ubuntu Vivid)
   Status: New = Invalid

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

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

Title:
  CVE-2015-1465

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  New
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  Fix Committed
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in

[Kernel-packages] [Bug 1393079] Re: Touchpad not working after suspend/resume

2015-03-04 Thread Michael Litherland

This bug still affects my laptop and my desktop.  I filed a separate
report on my laptop.  Any hope for a fix?  I'm running the 3.16.0-31.41
kernel but it still happens.

-- 
You 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:
  Incomplete

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 1415632] Re: CVE-2014-9644

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

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

** Description changed:

- related to CVE-2013-7421, not handling crypto templates correctly
+ The Crypto API in the Linux kernel before 3.18.5 allows local users to
+ load arbitrary kernel modules via a bind system call for an AF_ALG
+ socket with a parenthesized module template expression in the salg_name
+ field, as demonstrated by the vfat(aes) expression, a different
+ vulnerability than CVE-2013-7421.
  
  Break-Fix: 03c8efc1ffeb6b82a22c1af8dd908af349563314
  4943ba16bbc2db05115707b3ff7b4874e9e3c560

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

Title:
  CVE-2014-9644

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  Invalid
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  Invalid
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  New
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  Fix Committed
Status in linux-armadaxp source package in Utopic:
  Invalid

[Kernel-packages] [Bug 1428440] Re: [FUJITSU LIFEBOOK T904] hibernate/resume failure

2015-03-04 Thread ac

** Description changed:

  Resume has a 50/50 chance of working or not.   I'm unable to find any
  pattern.
  
  Behavior seen with both kernel and userspace hibernation (s2disk).
  
  After grub an empty black screen appears with a blinking caret in the
  upper left hand corner.  If the resume is successful  the lock screen
  appears.  If the resume fails, the blinking caret freezes and a hard
  reboot is required.
  
  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-7-generic 3.19.0-7.7
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  Annotation: This occured during a previous hibernate and prevented it from 
resuming properly.
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  achaudhari   1691 F pulseaudio
-  /dev/snd/controlC0:  achaudhari   1691 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  ac   1691 F pulseaudio
+  /dev/snd/controlC0:  ac   1691 F pulseaudio
  Date: Wed Mar  4 21:28:21 2015
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  InstallationDate: Installed on 2015-03-02 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20150224)
  InterpreterPath: /usr/bin/python3.4
  MachineType: FUJITSU LIFEBOOK T904
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-7-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: linux
  Title: [FUJITSU LIFEBOOK T904] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
-  
+ 
  dmi.bios.date: 11/17/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.14
  dmi.board.name: FJNB27A
  dmi.board.vendor: FUJITSU
  dmi.board.version: K3
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.14:bd11/17/2014:svnFUJITSU:pnLIFEBOOKT904:pvr:rvnFUJITSU:rnFJNB27A:rvrK3:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK T904
  dmi.sys.vendor: FUJITSU

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

Title:
  [FUJITSU LIFEBOOK T904] hibernate/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Resume has a 50/50 chance of working or not.   I'm unable to find any
  pattern.

  Behavior seen with both kernel and userspace hibernation (s2disk).

  After grub an empty black screen appears with a blinking caret in the
  upper left hand corner.  If the resume is successful  the lock screen
  appears.  If the resume fails, the blinking caret freezes and a hard
  reboot is required.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-7-generic 3.19.0-7.7
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  Annotation: This occured during a previous hibernate and prevented it from 
resuming properly.
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ac   1691 F pulseaudio
   /dev/snd/controlC0:  ac   1691 F pulseaudio
  Date: Wed Mar  4 21:28:21 2015
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  InstallationDate: Installed on 2015-03-02 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20150224)
  InterpreterPath: /usr/bin/python3.4
  MachineType: FUJITSU LIFEBOOK T904
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-7-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: linux
  Title: [FUJITSU LIFEBOOK T904] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  dmi.bios.date: 11/17/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.14
  dmi.board.name: FJNB27A
  dmi.board.vendor: FUJITSU
  dmi.board.version: K3
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.14:bd11/17/2014:svnFUJITSU:pnLIFEBOOKT904:pvr:rvnFUJITSU:rnFJNB27A:rvrK3:cvnFUJITSU:ct10:cvr:

[Kernel-packages] [Bug 1428365] [NEW] linux-lts-utopic: 3.16.0-32.42~14.04.1 -proposed tracker

Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-stable-Prepare-package-start:Wednesday, 04. March 2015 23:00 UTC
kernel-stable-phase:Prepare
kernel-stable-phase-changed:Wednesday, 04. March 2015 23:00 UTC
kernel-stable-master-bug:1427808

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

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

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

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

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

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

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

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

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

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Platform QA Team (canonical-platform-qa)
 Status: New

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

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

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

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


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

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

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

** Tags added: trusty

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1427808] Re: linux: 3.16.0-32.42 -proposed tracker

All builds are complete, packages in this bug can be copied to
-proposed.

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

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

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

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

** Changed in: kernel-sru-workflow/package-testing
   Status: New = Confirmed

** Description changed:

  This bug is for tracking the 3.16.0-32.42 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, 03. March 2015 18:53 UTC
- kernel-stable-phase:Prepare
- kernel-stable-phase-changed:Tuesday, 03. March 2015 18:53 UTC
+ kernel-stable-phase:CopyToProposed
+ kernel-stable-Prepare-package-end:Wednesday, 04. March 2015 23:02 UTC
+ kernel-stable-Promote-to-proposed-start:Wednesday, 04. March 2015 23:02 UTC
+ kernel-stable-phase-changed:Wednesday, 04. March 2015 23:02 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/1427808

Title:
  linux: 3.16.0-32.42 -proposed tracker

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

Bug description:
  This bug is for tracking the 3.16.0-32.42 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, 03. March 2015 18:53 UTC
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Wednesday, 04. March 2015 23:02 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 04. March 2015 23:02 UTC
  kernel-stable-phase-changed:Wednesday, 04. March 2015 23:02 UTC

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

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

[Kernel-packages] [Bug 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE

2015-03-04 Thread Seth Arnold

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

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

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

Title:
  Apparmor uses rsyslogd profile for different processes - utopic HWE

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in apparmor source package in Trusty:
  New
Status in linux source package in Trusty:
  Confirmed
Status in linux-lts-utopic source package in Trusty:
  Invalid

Bug description:
  Hi.

  I've noticed that apparmor loads /usr/sbin/rsyslogd profile for
  completely unrelated processes:

  Feb 25 08:36:19 emma kernel: [  134.796218] audit: type=1400 
audit(1424842579.429:245): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=4002 comm=sshd 
requested_mask=r denied_mask=r fsuid=0 ouid=0
  Feb 25 08:36:23 emma kernel: [  139.330989] audit: type=1400 
audit(1424842583.965:246): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=4080 comm=sudo 
requested_mask=r denied_mask=r fsuid=0 ouid=0
  Feb 25 08:35:42 emma kernel: [   97.912402] audit: type=1400 
audit(1424842542.565:241): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=2436 comm=whoopsie 
requested_mask=r denied_mask=r fsuid=103 ouid=0
  Feb 25 08:34:43 emma kernel: [   38.867998] audit: type=1400 
audit(1424842483.546:226): apparmor=DENIED operation=sendmsg 
profile=/usr/sbin/rsyslogd name=/dev/log pid=3762 comm=ntpd 
requested_mask=r denied_mask=r fsuid=0 ouid=0

  
  I'm not sure how apparmor decides which profile to use for which task, but is 
shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc.

  
  I'm running:
  # lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  # dpkg -l | grep apparmor
  ii  apparmor2.8.95~2430-0ubuntu5.1   
amd64User-space parser utility for AppArmor
  ii  apparmor-profiles   2.8.95~2430-0ubuntu5.1   
all  Profiles for AppArmor Security policies
  ii  apparmor-utils  2.8.95~2430-0ubuntu5.1   
amd64Utilities for controlling AppArmor
  ii  libapparmor-perl2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Perl bindings
  ii  libapparmor1:amd64  2.8.95~2430-0ubuntu5.1   
amd64changehat AppArmor library
  ii  python3-apparmor2.8.95~2430-0ubuntu5.1   
amd64AppArmor Python3 utility library
  ii  python3-libapparmor 2.8.95~2430-0ubuntu5.1   
amd64AppArmor library Python3 bindings

  # uname -a
  Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux

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

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

[Kernel-packages] [Bug 1427680] Re: bluetooth on asus n551 not working

2015-03-04 Thread Jeremy

Nice job!  You will likely have to do this for a few kernel updates to
keep your bluetooth going.  Hopefully Joseph or someone else can get
this submitted into the Ubuntu kernel and possibly into linux-next

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

Title:
  bluetooth on asus n551 not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  can't configure any bluetooth device with this laptop. bluetooth adapter is 
recognized and all seem working but it is unable to find any device on a scan.
  i tried installing blueman also but either it is unable to find any device.
  i've also read many posts with bluetooth solutions for 14.04 but none helped 
to solve the situation.
  i've also tried a mainline kernel (3.19) with no changes.
  currently i'm using 3.13.0-46-generic
  on the attached archive some files taken from the laptop (lspci,lsusb,rfkill 
list,dmesg |grep Blue,lsmod and the output of hciconfig -a)
  there are no evidences of problems but the bluetooth don't work.
  unluckly even the touchpad don't work so well on this laptop, so having to 
use the mouse is a pain

  
  late addition- i forgot to tell, on my dual boot system, the microsoft sculpt 
mouse bluetooth works as expected on windows 7
  Ubuntu is not able to see any blutooth device, i have tried 2 phones and this 
ms mouse, and is not seen by the phones also.

  
  ---
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hook   2242 F pulseaudio
   /dev/snd/controlC1:  hook   2242 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=4e7d3097-1e36-4191-98d8-df04a9ce48d2
  InstallationDate: Installed on 2012-11-06 (847 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  MachineType: ASUSTeK COMPUTER INC. N551JM
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=822863c8-1a3d-4ef2-8f89-0a2e8dc58ab9 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-46-generic N/A
   linux-backports-modules-3.13.0-46-generic  N/A
   linux-firmware 1.127.11
  Tags:  trusty
  Uname: Linux 3.13.0-46-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2015-01-04 (57 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N551JM.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N551JM
  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.:bvrN551JM.204:bd10/06/2014:svnASUSTeKCOMPUTERINC.:pnN551JM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN551JM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N551JM
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1428393] Re: [TOSHIBA Satellite C55D-A] suspend/resume failure

2015-03-04 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  [TOSHIBA Satellite C55D-A] suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop required holding of power button to shut down and did not shut
  down systemically.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-7-generic 3.19.0-7.7
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  skellat2323 F pulseaudio
   /dev/snd/controlC0:  skellat2323 F pulseaudio
  Date: Wed Mar  4 14:44:00 2015
  DuplicateSignature: suspend/resume:TOSHIBA Satellite C55D-A:1.80
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=32c42eb1-5aff-4ab2-8cbf-ca09f7de6829
  InstallationDate: Installed on 2015-01-31 (32 days ago)
  InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150131)
  InterpreterPath: /usr/bin/python3.4
  MachineType: TOSHIBA Satellite C55D-A
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic.efi.signed 
root=UUID=bfae61e0-4127-4c9b-b605-3482f487de38 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-7-generic N/A
   linux-backports-modules-3.19.0-7-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  Title: [TOSHIBA Satellite C55D-A] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/27/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.80:bd01/27/2014:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-02U005:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55D-A
  dmi.product.version: PSCFWU-02U005
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1428393] Re: [TOSHIBA Satellite C55D-A] suspend/resume failure

2015-03-04 Thread Stephen Michael Kellat

** Attachment added: version.log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1428393/+attachment/4334784/+files/version.log

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

Title:
  [TOSHIBA Satellite C55D-A] suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop required holding of power button to shut down and did not shut
  down systemically.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-7-generic 3.19.0-7.7
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  skellat2323 F pulseaudio
   /dev/snd/controlC0:  skellat2323 F pulseaudio
  Date: Wed Mar  4 14:44:00 2015
  DuplicateSignature: suspend/resume:TOSHIBA Satellite C55D-A:1.80
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=32c42eb1-5aff-4ab2-8cbf-ca09f7de6829
  InstallationDate: Installed on 2015-01-31 (32 days ago)
  InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150131)
  InterpreterPath: /usr/bin/python3.4
  MachineType: TOSHIBA Satellite C55D-A
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic.efi.signed 
root=UUID=bfae61e0-4127-4c9b-b605-3482f487de38 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-7-generic N/A
   linux-backports-modules-3.19.0-7-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  Title: [TOSHIBA Satellite C55D-A] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/27/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.80:bd01/27/2014:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-02U005:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55D-A
  dmi.product.version: PSCFWU-02U005
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1364539] Re: [Dell Latitude E7440] suspend/resume failure

2015-03-04 Thread Christopher M. Penalver

Michael Thayer, it would help immensely if you filed a new report via a 
terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

Title:
  [Dell Latitude E7440] suspend/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  If relevant, I docked the laptop between suspending and resuming.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-11-generic 3.16.0-11.16
  ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1
  Uname: Linux 3.16.0-11-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael2707 F pulseaudio
   /dev/snd/controlC0:  michael2707 F pulseaudio
  Date: Tue Sep  2 19:58:10 2014
  DuplicateSignature: suspend/resume:Dell Inc. Latitude E7440:A10
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=6d651e5a-075d-4911-a5ce-6710f7246853
  InstallationDate: Installed on 2014-08-01 (32 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Dell Inc. Latitude E7440
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-11-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-11-generic N/A
   linux-backports-modules-3.16.0-11-generic  N/A
   linux-firmware 1.132
  SourcePackage: linux
  Title: [Dell Inc. Latitude E7440] suspend/resume failure
  UpgradeStatus: Upgraded to utopic on 2014-08-28 (5 days ago)
  UserGroups:
   
  dmi.bios.date: 06/26/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0RYCC9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/26/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0RYCC9:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1293134] Re: [Samsung 700Z3A-S02DE] Laptop does not resume from suspend upon lid open

2015-03-04 Thread Christopher M. Penalver

Lars Schütze, in order to keep your bug relevant to upstream, it is
important to continue to test the latest mainline kernel as it comes
out.

As well, testing Fedora is largely useless here in launchpad, as that's
a distro (non-upstream and non-Ubuntu) kernel.

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

Title:
  [Samsung 700Z3A-S02DE] Laptop does not resume from suspend upon lid
  open

Status in linux package in Ubuntu:
  Triaged

Bug description:
  In 13.10-14.10, what is expected in to happen is when I close the lid,
  it puts the computer to sleep, and when I reopen the lid, it
  automatically resumes from sleep.

  What happens instead, is that the computer goes to sleep, but opening
  the lid does not make it resume.

  With acpi_listen I see that it fires and recognizes the events for lid close 
and open. /proc/acpi/button/lid/LID0/state shows the correct state for each lid 
position. With:
  acpid -d -f -l

  I see that those events trigger /etc/acpi/events/. I tried writing an
  event that matches lid close/open and calls pm-suspend, uncommenting
  lines in /etc/systemd/logind.conf regarding hibernate and suspend,
  echoing LID0 into /etc/acpi/wakeup, passing different acpi_osi strings
  with grub but the ACPI table does not change nor make it any
  difference for the suspend/resume problem.

  WORKAROUND: To resume, open the lid and press the power button once.

  ---
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  DistroRelease: Ubuntu 13.10
  InstallationDate: Installed on 2013-12-02 (104 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  NonfreeKernelModules: wl
  Package: pm-utils 1.4.1-12ubuntu1
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
  Tags:  saucy
  Uname: Linux 3.11.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  ---
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lars   4065 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.10
  HibernationDevice: RESUME=UUID=63d413ce-f76a-4aef-8728-6b94c8328c5a
  InstallationDate: Installed on 2014-11-19 (16 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z3A/700Z4A/700Z5A/700Z5B
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB:
   0 inteldrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic 
root=UUID=44843d26-d39a-43f4-bfd7-bb8b6bb69a91 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: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/06/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 15FD
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 700Z3A/700Z4A/700Z5A/700Z5B
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr15FD:bd11/06/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z3A/700Z4A/700Z5A/700Z5B:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rn700Z3A/700Z4A/700Z5A/700Z5B:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 700Z3A/700Z4A/700Z5A/700Z5B
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1428050] Re: [Matsushita Electric Industrial Co., Ltd. CF-19FHGAXBG] suspend/resume failure

2015-03-04 Thread Sascha Biermanns

Suspend work in kernel 4.0.0-04rc2-generic, installed via package
linux-image-4.0.0-04rc2-generic_4.0.0-04rc2.201503031836_amd64
from kernel mainline builds

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

Title:
  [Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG] suspend/resume
  failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When opening the lip, to resume after suspend, the computer was frozen
  and some LED's where blinking in a regular rhythmn. I had to reset the
  Toughbook to restart it.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-7-generic 3.19.0-7.7 [modified: 
boot/vmlinuz-3.19.0-7-generic]
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  skb2372 F pulseaudio
  Date: Wed Mar  4 10:16:51 2015
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  InstallationDate: Installed on 2015-03-02 (1 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150302)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-7-generic 
root=UUID=00bc12a3-0121-4e30-8834-27fafd4a0666 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: linux
  Title: [Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG] suspend/resume 
failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/10/2007
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.00L11
  dmi.board.name: CF19-2
  dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.board.version: 001
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.00L11:bd10/10/2007:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-19FHGAXBG:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF19-2:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
  dmi.product.name: CF-19FHGAXBG
  dmi.product.version: 002
  dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.

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

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

[Kernel-packages] [Bug 1295141] Re: Toshiba Qosmio X75-A7298 - Can't Adjust Brightness

2015-03-04 Thread Robbie Lancaster

Lonnie, I have this same laptop.  When booting the 3.14 or higher
kernels, you don't get a screen freeze at boot unless running
nomodeset or the proprietary Nvidia drivers?  I boot with the kernel
mode nomodeset, but then I don't have any way to control brightness.

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

Title:
  Toshiba Qosmio X75-A7298 - Can't Adjust Brightness

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

Bug description:
  The Toshiba Qosmio X75-A7298 is running Ubuntu 14.04 blazingly fast.

  The only issue I've noticed, is that the OS doesn't seem to have a
  proper mapping to this laptop's function keys.

  Specifically, I'm unable to adjust the screen's brightness. Looking a
  the keyboard layout, I should be able to dim the screen by holding
  down the FN key and then press F2. Alternatively, to make the screen
  brighter you'd key  FN-F3.

  This is a fantasic laptop, I'd like to help (if I can) to get it fully
  functional for Ubuntu 14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-18-generic 3.13.0-18.38 [modified: 
boot/vmlinuz-3.13.0-18-generic]
  ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6
  Uname: Linux 3.13.0-18-generic x86_64
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  steve  2503 F pulseaudio
   /dev/snd/controlC0:  steve  2503 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Thu Mar 20 08:43:44 2014
  HibernationDevice: RESUME=UUID=c040a1e4-2261-47d3-85df-a01363cf3fca
  InstallationDate: Installed on 2014-03-19 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140319)
  MachineType: TOSHIBA Qosmio X75-A
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-18-generic 
root=UUID=82c4632b-cc2b-48f4-b42f-61690dbc80b7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-18-generic N/A
   linux-backports-modules-3.13.0-18-generic  N/A
   linux-firmware 1.126
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.30
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Type2 - Board Vendor Name1
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.30:bd09/18/2013:svnTOSHIBA:pnQosmioX75-A:pvrPSPLTU-017016:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Qosmio X75-A
  dmi.product.version: PSPLTU-017016
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1428393] [NEW] [TOSHIBA Satellite C55D-A] suspend/resume failure

2015-03-04 Thread Stephen Michael Kellat

Public bug reported:

Laptop required holding of power button to shut down and did not shut
down systemically.

ProblemType: KernelOops
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-7-generic 3.19.0-7.7
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
ApportVersion: 2.16.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  skellat2323 F pulseaudio
 /dev/snd/controlC0:  skellat2323 F pulseaudio
Date: Wed Mar  4 14:44:00 2015
DuplicateSignature: suspend/resume:TOSHIBA Satellite C55D-A:1.80
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=32c42eb1-5aff-4ab2-8cbf-ca09f7de6829
InstallationDate: Installed on 2015-01-31 (32 days ago)
InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150131)
InterpreterPath: /usr/bin/python3.4
MachineType: TOSHIBA Satellite C55D-A
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic.efi.signed 
root=UUID=bfae61e0-4127-4c9b-b605-3482f487de38 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-7-generic N/A
 linux-backports-modules-3.19.0-7-generic  N/A
 linux-firmware1.141
SourcePackage: linux
Title: [TOSHIBA Satellite C55D-A] suspend/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 01/27/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.80
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: MP
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.80:bd01/27/2014:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-02U005:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.name: Satellite C55D-A
dmi.product.version: PSCFWU-02U005
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-kerneloops resume suspend vivid

** Attachment added: lspci-vnvn.log
   
https://bugs.launchpad.net/bugs/1428393/+attachment/4334764/+files/lspci-vnvn.log

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

Title:
  [TOSHIBA Satellite C55D-A] suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop required holding of power button to shut down and did not shut
  down systemically.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-7-generic 3.19.0-7.7
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  skellat2323 F pulseaudio
   /dev/snd/controlC0:  skellat2323 F pulseaudio
  Date: Wed Mar  4 14:44:00 2015
  DuplicateSignature: suspend/resume:TOSHIBA Satellite C55D-A:1.80
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=32c42eb1-5aff-4ab2-8cbf-ca09f7de6829
  InstallationDate: Installed on 2015-01-31 (32 days ago)
  InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150131)
  InterpreterPath: /usr/bin/python3.4
  MachineType: TOSHIBA Satellite C55D-A
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic.efi.signed 
root=UUID=bfae61e0-4127-4c9b-b605-3482f487de38 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-7-generic N/A
   linux-backports-modules-3.19.0-7-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  Title: [TOSHIBA Satellite C55D-A] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/27/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA

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

This change was made by a bot.

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

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

Title:
  [TOSHIBA Satellite C55D-A] suspend/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop required holding of power button to shut down and did not shut
  down systemically.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-7-generic 3.19.0-7.7
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  skellat2323 F pulseaudio
   /dev/snd/controlC0:  skellat2323 F pulseaudio
  Date: Wed Mar  4 14:44:00 2015
  DuplicateSignature: suspend/resume:TOSHIBA Satellite C55D-A:1.80
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  HibernationDevice: RESUME=UUID=32c42eb1-5aff-4ab2-8cbf-ca09f7de6829
  InstallationDate: Installed on 2015-01-31 (32 days ago)
  InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150131)
  InterpreterPath: /usr/bin/python3.4
  MachineType: TOSHIBA Satellite C55D-A
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic.efi.signed 
root=UUID=bfae61e0-4127-4c9b-b605-3482f487de38 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-7-generic N/A
   linux-backports-modules-3.19.0-7-generic  N/A
   linux-firmware1.141
  SourcePackage: linux
  Title: [TOSHIBA Satellite C55D-A] suspend/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/27/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.80
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: MP
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.80:bd01/27/2014:svnTOSHIBA:pnSatelliteC55D-A:pvrPSCFWU-02U005:rvnTOSHIBA:rnPortablePC:rvrMP:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.name: Satellite C55D-A
  dmi.product.version: PSCFWU-02U005
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 119940] Re: /proc/cpuinfo reports incorrect information for Via C3

2015-03-04 Thread Rolf Leggewie

Unfortunately, Ubuntu no longer even supports booting from this nice
little CPU beyond lucid.  Obviously, this will not get fixed in Ubuntu.
Marking as such.

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

Title:
  /proc/cpuinfo reports incorrect  information for Via C3

Status in The Linux Kernel:
  Expired
Status in linux package in Ubuntu:
  Won't Fix
Status in linux-source-2.6.15 package in Ubuntu:
  Won't Fix
Status in linux-source-2.6.20 package in Ubuntu:
  Won't Fix
Status in linux-source-2.6.22 package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: linux-source-2.6.15

  The output of cat /proc/cpuinfo is wrong

  processor   : 0
  vendor_id   : CentaurHauls
  cpu family  : 6
  model   : 6
  model name  : VIA Samuel
  stepping: 2
  cpu MHz : 400.179
  [...]

  My CPU has 600 MHz.  And while cpu frequency scaling was still working
  (c.f. bug 45747) I always saw the true frequency to be underreported
  by 33%.  It was 400/200 MHz when the machine was really running at
  600/400 MHz.

  Some possibly related issues where frequency is incorrectly reported
  are being discussed at
  
http://groups.google.de/group/linux.kernel/browse_thread/thread/6d1b20ec35e21cbe/6d2b5fb0419c96e4?lnk=st

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

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

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

This change was made by a bot.

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

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

Title:
  [FUJITSU LIFEBOOK T904] hibernate/resume failure

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Resume has a 50/50 chance of working or not.   I'm unable to find any
  pattern.

  Behavior seen with both kernel and userspace hibernation (s2disk).

  After grub an empty black screen appears with a blinking caret in the
  upper left hand corner.  If the resume is successful  the lock screen
  appears.  If the resume fails, the blinking caret freezes and a hard
  reboot is required.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-7-generic 3.19.0-7.7
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  Annotation: This occured during a previous hibernate and prevented it from 
resuming properly.
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  achaudhari   1691 F pulseaudio
   /dev/snd/controlC0:  achaudhari   1691 F pulseaudio
  Date: Wed Mar  4 21:28:21 2015
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  InstallationDate: Installed on 2015-03-02 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20150224)
  InterpreterPath: /usr/bin/python3.4
  MachineType: FUJITSU LIFEBOOK T904
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-7-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: linux
  Title: [FUJITSU LIFEBOOK T904] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/17/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.14
  dmi.board.name: FJNB27A
  dmi.board.vendor: FUJITSU
  dmi.board.version: K3
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.14:bd11/17/2014:svnFUJITSU:pnLIFEBOOKT904:pvr:rvnFUJITSU:rnFJNB27A:rvrK3:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK T904
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1428050] Re: [Matsushita Electric Industrial Co., Ltd. CF-19FHGAXBG] suspend/resume failure

2015-03-04 Thread Sascha Biermanns

I just installed Ubuntu 15.04 yesterday, and so I can only say, it
happened with the installation from yesterdays actual kernel.

** Tags added: kernel-fixed-upstream

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

Title:
  [Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG] suspend/resume
  failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When opening the lip, to resume after suspend, the computer was frozen
  and some LED's where blinking in a regular rhythmn. I had to reset the
  Toughbook to restart it.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-7-generic 3.19.0-7.7 [modified: 
boot/vmlinuz-3.19.0-7-generic]
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  Annotation: This occured during a previous suspend and prevented it from 
resuming properly.
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  skb2372 F pulseaudio
  Date: Wed Mar  4 10:16:51 2015
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: suspend/resume
  InstallationDate: Installed on 2015-03-02 (1 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150302)
  InterpreterPath: /usr/bin/python3.4
  MachineType: Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-7-generic 
root=UUID=00bc12a3-0121-4e30-8834-27fafd4a0666 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: linux
  Title: [Matsushita Electric Industrial Co.,Ltd. CF-19FHGAXBG] suspend/resume 
failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 10/10/2007
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.00L11
  dmi.board.name: CF19-2
  dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.board.version: 001
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.00L11:bd10/10/2007:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-19FHGAXBG:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF19-2:rvr001:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
  dmi.product.name: CF-19FHGAXBG
  dmi.product.version: 002
  dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.

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

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

[Kernel-packages] [Bug 1425274] Re: CVE-2015-2042

** Changed in: linux (Ubuntu Vivid)
   Status: New = Invalid

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

Title:
  CVE-2015-2042

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  New
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  New
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in linux-lts-trusty source package in Utopic:
  Invalid
Status in linux-lts-utopic source

[Kernel-packages] [Bug 1425271] Re: CVE-2015-2041

** Changed in: linux (Ubuntu Vivid)
   Status: New = Invalid

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

Title:
  CVE-2015-2041

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  New
Status in linux-lts-backport-natty package in Ubuntu:
  New
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Lucid:
  New
Status in linux-armadaxp source package in Lucid:
  Invalid
Status in linux-ec2 source package in Lucid:
  New
Status in linux-flo source package in Lucid:
  Invalid
Status in linux-fsl-imx51 source package in Lucid:
  Invalid
Status in linux-goldfish source package in Lucid:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  New
Status in linux-lts-backport-natty source package in Lucid:
  New
Status in linux-lts-quantal source package in Lucid:
  Invalid
Status in linux-lts-raring source package in Lucid:
  Invalid
Status in linux-lts-saucy source package in Lucid:
  Invalid
Status in linux-lts-trusty source package in Lucid:
  Invalid
Status in linux-lts-utopic source package in Lucid:
  Invalid
Status in linux-mako source package in Lucid:
  Invalid
Status in linux-manta source package in Lucid:
  Invalid
Status in linux-mvl-dove source package in Lucid:
  Invalid
Status in linux-ti-omap4 source package in Lucid:
  Invalid
Status in linux source package in Precise:
  New
Status in linux-armadaxp source package in Precise:
  New
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  New
Status in linux-lts-backport-natty source package in Precise:
  New
Status in linux-lts-quantal source package in Precise:
  New
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  New
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  New
Status in linux source package in Trusty:
  New
Status in linux-armadaxp source package in Trusty:
  Invalid
Status in linux-ec2 source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-fsl-imx51 source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  New
Status in linux-lts-backport-natty source package in Trusty:
  New
Status in linux-lts-quantal source package in Trusty:
  Invalid
Status in linux-lts-raring source package in Trusty:
  Invalid
Status in linux-lts-saucy source package in Trusty:
  Invalid
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-mvl-dove source package in Trusty:
  Invalid
Status in linux-ti-omap4 source package in Trusty:
  Invalid
Status in linux source package in Utopic:
  New
Status in linux-armadaxp source package in Utopic:
  Invalid
Status in linux-ec2 source package in Utopic:
  Invalid
Status in linux-flo source package in Utopic:
  New
Status in linux-fsl-imx51 source package in Utopic:
  Invalid
Status in linux-goldfish source package in Utopic:
  New
Status in linux-lts-backport-maverick source package in Utopic:
  New
Status in linux-lts-backport-natty source package in Utopic:
  New
Status in linux-lts-quantal source package in Utopic:
  Invalid
Status in linux-lts-raring source package in Utopic:
  Invalid
Status in linux-lts-saucy source package in Utopic:
  Invalid
Status in linux-lts-trusty source package in Utopic:
  Invalid
Status in linux-lts-utopic source

[Kernel-packages] [Bug 1428121] Re: Intel HDMI Audio not working with IOMMU enabled

2015-03-04 Thread Christopher M. Penalver

** Tags added: latest-bios-1.70

** Package changed: linux (Ubuntu) = alsa-driver (Ubuntu)

** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed = 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/1428121

Title:
  Intel HDMI Audio not working with IOMMU enabled

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  New ASRock Z97 Extreme 6 motherboard with an Intel i7 4790S and an
  Nvidia GTX 650.

  Host uses Intel IGD for video and HDMI audio out.

  When I pass kernel flags 'intel_iommu=on' or 'intel_iommu=on,igfx_on'
  HDMI audio no longer functions although the device and modules seem to
  load and I cannot locate any error messages.  In this configuration
  IOMMU functions as expected and I can successfully pass the Nvidia
  card through to a KVM guest using VFIO.

  As per this
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1223840) bug
  report and the linked bugzilla thread I attempted to use kernel flag
  'intel_iommu=on,igfx_off'.  This resolves the HDMI audio out but
  breaks IOMMU as in VGA pass through generates DMA errors.

  I'm running from a clean installation of 14.10 with no modifications
  to the kernel or kvm, qemu, libvirt or virt-manager.

  In either scenario above the analogue audio out continues to function,
  I haven't tested the optical out as I have no hardware to do so.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-31-generic 3.16.0-31.41
  ProcVersionSignature: Ubuntu 3.16.0-31.41-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  kelvin 3468 F pulseaudio
   /dev/snd/controlC3:  kelvin 3468 F pulseaudio
   /dev/snd/controlC0:  kelvin 3468 F pulseaudio
   /dev/snd/controlC1:  kelvin 3468 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Mar  4 12:53:17 2015
  HibernationDevice: RESUME=UUID=4d35060a-85c4-45fd-9f8e-530491588931
  InstallationDate: Installed on 2015-02-26 (5 days ago)
  InstallationMedia: Ubuntu-Server 14.10 Utopic Unicorn - Release amd64 
(20141022.2)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed 
root=UUID=4914f227-6bb0-40bb-a781-9ad7111a996f ro intremap=no_x2apic_optout 
intel_iommu=on,forcedac pci-stub.ids=10de:11c8,10de:0e0b nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-31-generic N/A
   linux-backports-modules-3.16.0-31-generic  N/A
   linux-firmware 1.138.1
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1428440] [NEW] [FUJITSU LIFEBOOK T904] hibernate/resume failure

2015-03-04 Thread ac

Public bug reported:

Resume has a 50/50 chance of working or not.   I'm unable to find any
pattern.

Behavior seen with both kernel and userspace hibernation (s2disk).

After grub an empty black screen appears with a blinking caret in the
upper left hand corner.  If the resume is successful  the lock screen
appears.  If the resume fails, the blinking caret freezes and a hard
reboot is required.

ProblemType: KernelOops
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-7-generic 3.19.0-7.7
ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
Uname: Linux 3.19.0-7-generic x86_64
Annotation: This occured during a previous hibernate and prevented it from 
resuming properly.
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  achaudhari   1691 F pulseaudio
 /dev/snd/controlC0:  achaudhari   1691 F pulseaudio
Date: Wed Mar  4 21:28:21 2015
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: hibernate/resume
InstallationDate: Installed on 2015-03-02 (2 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20150224)
InterpreterPath: /usr/bin/python3.4
MachineType: FUJITSU LIFEBOOK T904
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-7-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: linux
Title: [FUJITSU LIFEBOOK T904] hibernate/resume failure
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 11/17/2014
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.14
dmi.board.name: FJNB27A
dmi.board.vendor: FUJITSU
dmi.board.version: K3
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.14:bd11/17/2014:svnFUJITSU:pnLIFEBOOKT904:pvr:rvnFUJITSU:rnFJNB27A:rvrK3:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK T904
dmi.sys.vendor: FUJITSU

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


** Tags: amd64 apport-kerneloops hibernate resume 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/1428440

Title:
  [FUJITSU LIFEBOOK T904] hibernate/resume failure

Status in linux package in Ubuntu:
  New

Bug description:
  Resume has a 50/50 chance of working or not.   I'm unable to find any
  pattern.

  Behavior seen with both kernel and userspace hibernation (s2disk).

  After grub an empty black screen appears with a blinking caret in the
  upper left hand corner.  If the resume is successful  the lock screen
  appears.  If the resume fails, the blinking caret freezes and a hard
  reboot is required.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-7-generic 3.19.0-7.7
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  Annotation: This occured during a previous hibernate and prevented it from 
resuming properly.
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  achaudhari   1691 F pulseaudio
   /dev/snd/controlC0:  achaudhari   1691 F pulseaudio
  Date: Wed Mar  4 21:28:21 2015
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  InstallationDate: Installed on 2015-03-02 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha amd64 (20150224)
  InterpreterPath: /usr/bin/python3.4
  MachineType: FUJITSU LIFEBOOK T904
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-7-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: linux
  Title: [FUJITSU LIFEBOOK T904] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 11/17/2014
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: Version 1.14
  dmi.board.name: FJNB27A
  dmi.board.vendor: FUJITSU
  dmi.board.version: K3
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.14:bd11/17/2014:svnFUJITSU:pnLIFEBOOKT904:pvr:rvnFUJITSU:rnFJNB27A:rvrK3:cvnFUJITSU:ct10:cvr:
  dmi.product.name: LIFEBOOK T904
  dmi.sys.vendor: FUJITSU

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1342548] Re: [Dell Inspiron 5437] Wireless key does not work on this system

2015-03-04 Thread Po-Hsu Lin

Verified with 201305-13673 Dell Inspiron 5437 again, it works with 14.04.1 + 
update (3.13.0-46)
Thanks!

** Changed in: hwe-next
   Status: In Progress = Fix Released

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

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

Title:
  [Dell Inspiron 5437] Wireless key does not work on this system

Status in HWE Next Project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  CID: 201305-13673 Dell Inspiron 5437

  The wireless hotkey does not work on this system

  Steps:
  1. Install 14.04 + update (3.13.0-30), boot to desktop
  2. Try to control wireless / BT with the hotkey

  Expected result:
  * Wireless / BT could be controlled by the hotkey

  Actual result:
  * Hotkey is not working

  Debugging information:
  ubuntu@201305-13673:~$ sudo showkey -k
  kb mode was ?UNKNOWN?
  [ if you are trying this under X, it might not work
  since the X server is also reading /dev/console ]

  press any key (program terminates 10s after last keypress)...
  keycode  28 release
  keycode 240 press
  keycode 240 release
  keycode 240 press
  keycode 240 release
  ^Ccaught signal 2, cleaning up...

  KeyPress event, serial 37, synthetic NO, window 0x3a1,
  root 0x2c0, subw 0x0, time 199006, (-357,353), root:(430,405),
  state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x3a1,
  root 0x2c0, subw 0x0, time 199006, (-357,353), root:(430,405),
  state 0x0, keycode 248 (keysym 0x0, NoSymbol), same_screen YES,
  XLookupString gives 0 bytes: 
  XFilterEvent returns: False

  nothing from sudo showkey -s

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-30-generic 3.13.0-30.55
  ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1638 F pulseaudio
   /dev/snd/controlC1:  ubuntu 1638 F pulseaudio
  CRDA:
   country TW:
(2402 - 2472 @ 40), (3, 27)
(5270 - 5330 @ 40), (3, 17), DFS
(5735 - 5815 @ 40), (3, 30)
  CurrentDesktop: Unity
  Date: Wed Jul 16 01:56:06 2014
  HibernationDevice: RESUME=UUID=67674077-ce03-4513-b8be-b3e9bdd8840d
  InstallationDate: Installed on 2014-07-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 5437
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic.efi.signed 
root=UUID=e56f47e4-b04b-4702-b89f-59e1c08572c4 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-30-generic N/A
   linux-backports-modules-3.13.0-30-generic  N/A
   linux-firmware 1.127.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/14/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/14/2013:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn:rvrA07:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5437
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1422358] Re: Incorrect power/battery status on Lenovo Thinkpad 10

apport information

** Description changed:

  Running live USB of the latest Vivid daily build on Lenovo Thinkpad 10.
  
  Ubuntu 15.04 (vivid-desktop-amd64.iso 2015-02-16 8:05)
  Linux 3.18.0-13-generic
  
  The power/battery applet is always red and suggest that battery is empty
  and AC is unplugged.
  
  With a full charge and AC adapter plugged, the system provides an
  obviously incorrect status:
  
  cat /sys/class/power_supply/ADP1/uevent:
  POWER_SUPPLY_NAME=ADP1
  POWER_SUPPLY_ONLINE=0
  
  cat /sys/class/power_supply/BAT0/uevent:
  POWER_SUPPLY_NAME=BAT0
  POWER_SUPPLY_STATUS=Unknown
  POWER_SUPPLY_PRESENT=1
  POWER_SUPPLY_TECHNOLOGY=Li-ion
  POWER_SUPPLY_CYCLE_COUNT=8
  POWER_SUPPLY_VOLTAGE_MIN_DESIGN=1080
  POWER_SUPPLY_VOLTAGE_NOW=0
  POWER_SUPPLY_CURRENT_NOW=0
  POWER_SUPPLY_CHARGE_FULL_DESIGN=600
  POWER_SUPPLY_CHARGE_FULL=600
  POWER_SUPPLY_CHARGE_NOW=0
  POWER_SUPPLY_CAPACITY=0
  POWER_SUPPLY_CAPACITY_LEVEL=Low
  POWER_SUPPLY_MODEL_NAME=PABAS0241231
  POWER_SUPPLY_MANUFACTURER=LG Chem
  POWER_SUPPLY_SERIAL_NUMBER=41167
  
  Let me know if you need additional information.
  --- 
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.351
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150216)
  Package: gnome-power-manager 3.14.1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Tags:  vivid
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.351
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150216)
  Package: gnome-power-manager 3.14.1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Tags:  vivid
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.351
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150216)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Tags:  vivid
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
+ --- 
+ ApportVersion: 2.16.1-0ubuntu2
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CasperVersion: 1.351
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 15.04
+ IwConfig:
+  usb0  no wireless extensions.
+  
+  lono wireless extensions.
+ LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150216)
+ MachineType: LENOVO 20C1CTO1WW
+ 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=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --
+ ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
+ RfKill:
+  0: LNV4752:00: GPS
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  vivid
+ Uname: Linux 3.18.0-13-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 01/12/2015
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: GWET27WW (1.27)
+ dmi.board.asset.tag: Base Board Asset Tag
+ dmi.board.name: 20C1CTO1WW
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SKG18 I
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 11
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: 0.1
+ dmi.modalias: 
dmi:bvnLENOVO:bvrGWET27WW(1.27):bd01/12/2015:svnLENOVO:pn20C1CTO1WW:pvrThinkPad10:rvnLENOVO:rn20C1CTO1WW:rvrSKG18I:cvnLENOVO:ct11:cvr0.1:
+ dmi.product.name: 20C1CTO1WW
+ dmi.product.version: ThinkPad 10
+ dmi.sys.vendor: LENOVO

** Attachment added: AlsaInfo.txt
   
https://bugs.launchpad.net/bugs/1422358/+attachment/4334906/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1419439] Re: Screen freeze when watching video in VLC

2015-03-04 Thread Prasanna Kumar

I have updated my BIOS. Will check and report back whether the issue is
still present.

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

Title:
  Screen freeze when watching video in VLC

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Screen freezes when I watch video in VLC media player. Moving mouse is
  of no use and Ctrl + Alt + T short cut does not launch terminal. But I
  Could hear the audio even after screen freeze.

  If I press Ctrl + Alt + F1 and wait for several minutes switches to
  console. Then switching to GUI brings back the screen and I am able to
  work as usual.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-30-generic 3.16.0-30.40
  ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  prasanna   2562 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Feb  8 18:51:57 2015
  HibernationDevice: RESUME=UUID=0af44a95-238c-498a-88f2-425c00e1c9a6
  InstallationDate: Installed on 2014-12-15 (54 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  MachineType: LENOVO 24663C1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic 
root=UUID=0155df5a-b3ef-4cff-bf83-c45841ac9ed0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-30-generic N/A
   linux-backports-modules-3.16.0-30-generic  N/A
   linux-firmware 1.138.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G3ET90WW(2.50)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 24663C1
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG3ET90WW(2.50):bd12/26/2012:svnLENOVO:pn24663C1:pvrThinkPadL430:rvnLENOVO:rn24663C1:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 24663C1
  dmi.product.version: ThinkPad L430
  dmi.sys.vendor: LENOVO

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

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

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

apport information

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

Title:
  Incorrect power/battery status on Lenovo Thinkpad 10

Status in gnome-power-manager package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running live USB of the latest Vivid daily build on Lenovo Thinkpad
  10.

  Ubuntu 15.04 (vivid-desktop-amd64.iso 2015-02-16 8:05)
  Linux 3.18.0-13-generic

  The power/battery applet is always red and suggest that battery is
  empty and AC is unplugged.

  With a full charge and AC adapter plugged, the system provides an
  obviously incorrect status:

  cat /sys/class/power_supply/ADP1/uevent:
  POWER_SUPPLY_NAME=ADP1
  POWER_SUPPLY_ONLINE=0

  cat /sys/class/power_supply/BAT0/uevent:
  POWER_SUPPLY_NAME=BAT0
  POWER_SUPPLY_STATUS=Unknown
  POWER_SUPPLY_PRESENT=1
  POWER_SUPPLY_TECHNOLOGY=Li-ion
  POWER_SUPPLY_CYCLE_COUNT=8
  POWER_SUPPLY_VOLTAGE_MIN_DESIGN=1080
  POWER_SUPPLY_VOLTAGE_NOW=0
  POWER_SUPPLY_CURRENT_NOW=0
  POWER_SUPPLY_CHARGE_FULL_DESIGN=600
  POWER_SUPPLY_CHARGE_FULL=600
  POWER_SUPPLY_CHARGE_NOW=0
  POWER_SUPPLY_CAPACITY=0
  POWER_SUPPLY_CAPACITY_LEVEL=Low
  POWER_SUPPLY_MODEL_NAME=PABAS0241231
  POWER_SUPPLY_MANUFACTURER=LG Chem
  POWER_SUPPLY_SERIAL_NUMBER=41167

  Let me know if you need additional information.
  --- 
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.351
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150216)
  Package: gnome-power-manager 3.14.1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Tags:  vivid
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.351
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150216)
  Package: gnome-power-manager 3.14.1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Tags:  vivid
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.351
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150216)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Tags:  vivid
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.351
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  IwConfig:
   usb0  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150216)
  MachineType: LENOVO 20C1CTO1WW
  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=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  RfKill:
   0: LNV4752:00: GPS
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GWET27WW (1.27)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 20C1CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SKG18 I
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.modalias:

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

apport information

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

Title:
  Incorrect power/battery status on Lenovo Thinkpad 10

Status in gnome-power-manager package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running live USB of the latest Vivid daily build on Lenovo Thinkpad
  10.

  Ubuntu 15.04 (vivid-desktop-amd64.iso 2015-02-16 8:05)
  Linux 3.18.0-13-generic

  The power/battery applet is always red and suggest that battery is
  empty and AC is unplugged.

  With a full charge and AC adapter plugged, the system provides an
  obviously incorrect status:

  cat /sys/class/power_supply/ADP1/uevent:
  POWER_SUPPLY_NAME=ADP1
  POWER_SUPPLY_ONLINE=0

  cat /sys/class/power_supply/BAT0/uevent:
  POWER_SUPPLY_NAME=BAT0
  POWER_SUPPLY_STATUS=Unknown
  POWER_SUPPLY_PRESENT=1
  POWER_SUPPLY_TECHNOLOGY=Li-ion
  POWER_SUPPLY_CYCLE_COUNT=8
  POWER_SUPPLY_VOLTAGE_MIN_DESIGN=1080
  POWER_SUPPLY_VOLTAGE_NOW=0
  POWER_SUPPLY_CURRENT_NOW=0
  POWER_SUPPLY_CHARGE_FULL_DESIGN=600
  POWER_SUPPLY_CHARGE_FULL=600
  POWER_SUPPLY_CHARGE_NOW=0
  POWER_SUPPLY_CAPACITY=0
  POWER_SUPPLY_CAPACITY_LEVEL=Low
  POWER_SUPPLY_MODEL_NAME=PABAS0241231
  POWER_SUPPLY_MANUFACTURER=LG Chem
  POWER_SUPPLY_SERIAL_NUMBER=41167

  Let me know if you need additional information.
  --- 
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.351
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150216)
  Package: gnome-power-manager 3.14.1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Tags:  vivid
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.351
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150216)
  Package: gnome-power-manager 3.14.1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Tags:  vivid
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.351
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150216)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Tags:  vivid
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.351
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  IwConfig:
   usb0  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150216)
  MachineType: LENOVO 20C1CTO1WW
  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=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  RfKill:
   0: LNV4752:00: GPS
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GWET27WW (1.27)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 20C1CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SKG18 I
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.modalias:

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

apport information

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

Title:
  Incorrect power/battery status on Lenovo Thinkpad 10

Status in gnome-power-manager package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Running live USB of the latest Vivid daily build on Lenovo Thinkpad
  10.

  Ubuntu 15.04 (vivid-desktop-amd64.iso 2015-02-16 8:05)
  Linux 3.18.0-13-generic

  The power/battery applet is always red and suggest that battery is
  empty and AC is unplugged.

  With a full charge and AC adapter plugged, the system provides an
  obviously incorrect status:

  cat /sys/class/power_supply/ADP1/uevent:
  POWER_SUPPLY_NAME=ADP1
  POWER_SUPPLY_ONLINE=0

  cat /sys/class/power_supply/BAT0/uevent:
  POWER_SUPPLY_NAME=BAT0
  POWER_SUPPLY_STATUS=Unknown
  POWER_SUPPLY_PRESENT=1
  POWER_SUPPLY_TECHNOLOGY=Li-ion
  POWER_SUPPLY_CYCLE_COUNT=8
  POWER_SUPPLY_VOLTAGE_MIN_DESIGN=1080
  POWER_SUPPLY_VOLTAGE_NOW=0
  POWER_SUPPLY_CURRENT_NOW=0
  POWER_SUPPLY_CHARGE_FULL_DESIGN=600
  POWER_SUPPLY_CHARGE_FULL=600
  POWER_SUPPLY_CHARGE_NOW=0
  POWER_SUPPLY_CAPACITY=0
  POWER_SUPPLY_CAPACITY_LEVEL=Low
  POWER_SUPPLY_MODEL_NAME=PABAS0241231
  POWER_SUPPLY_MANUFACTURER=LG Chem
  POWER_SUPPLY_SERIAL_NUMBER=41167

  Let me know if you need additional information.
  --- 
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.351
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150216)
  Package: gnome-power-manager 3.14.1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Tags:  vivid
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.351
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150216)
  Package: gnome-power-manager 3.14.1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Tags:  vivid
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.351
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150216)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Tags:  vivid
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.351
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  IwConfig:
   usb0  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150216)
  MachineType: LENOVO 20C1CTO1WW
  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=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  RfKill:
   0: LNV4752:00: GPS
Soft blocked: no
Hard blocked: no
  Tags:  vivid
  Uname: Linux 3.18.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GWET27WW (1.27)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 20C1CTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SKG18 I
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.modalias:

[Kernel-packages] [Bug 1422338] Re: I/O errors on mmc partitions