[Kernel-packages] [Bug 1537472] Re: Synaptics touchpad not recognised - OK on linux-image-3.13.0-74-generic 3.13.0-74.118

2016-01-26 Thread John Leake
Glad to assist but this is on the edge of my experience.  I had the same
problems with the header dependencies when installing, however 4.5-rc1
booted and the touchpad is still not recognised.  I noticed that there
was a TPM (6) error on boot.  Sorry I do not know how to  provide you
with any more info.

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

Title:
  Synaptics touchpad not recognised - OK on linux-
  image-3.13.0-74-generic  3.13.0-74.118

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Thinkpad T520 mousepad defaults to standard PS2 so there is no edge
  scroll etc. and thus no settings tab for touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-76-generic 3.13.0-76.120
  ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-76-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2053 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan 24 11:06:21 2016
  HibernationDevice: RESUME=UUID=0014b9e9-0896-45dd-8005-73598192eb15
  InstallationDate: Installed on 2015-03-21 (308 days ago)
  InstallationMedia: BackBox Linux 4.1 - Release i386
  MachineType: LENOVO 4242A25
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-76-generic 
root=UUID=52833b54-5bbe-4c2f-97e4-73240dfc57e9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-76-generic N/A
   linux-backports-modules-3.13.0-76-generic  N/A
   linux-firmware 1.127.20
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET64WW (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4242A25
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: 1S4242A25R9FKBZP
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET64WW(1.44):bd07/26/2013:svnLENOVO:pn4242A25:pvrThinkPadT520:rvnLENOVO:rn4242A25:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4242A25
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1537209] Re: Kernel doesn't load after kubuntu upgrade (from 15.04 to 15.10)

2016-01-26 Thread Renato S. Yamane
I tested with 4.4.0-040400-generic_4.4.0-040400.201601101930_amd64
Same problem.

** Attachment added: "It is what happens"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1537209/+attachment/4556768/+files/hangs.jpg

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

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

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

Title:
  Kernel doesn't load after kubuntu upgrade (from 15.04 to 15.10)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updrade my laptop Lenovo T430u from Kubuntu Vivid to Wily), I
  can not load the kernel 4.2.0-23 or 4.2.0-25 (not tested other
  versions).

  The only kernel I can use is 3.19.0-43 (from Kubuntu Vivid).

  If I choose 4.2.0-xx kernel, I just can see a black screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-25-generic 4.2.0-25.30
  ProcVersionSignature: Ubuntu 3.19.0-43.49-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-43-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yamane 1879 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jan 22 19:13:09 2016
  HibernationDevice: RESUME=UUID=f11f0511-b75c-4a11-a486-9119d10ee8d7
  InstallationDate: Installed on 2014-03-08 (685 days ago)
  InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140308)
  MachineType: LENOVO 33525SP
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-43-generic 
root=UUID=0575faf0-2a03-4d14-8eff-4e45024318f0 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-43-generic N/A
   linux-backports-modules-3.19.0-43-generic  N/A
   linux-firmware 1.149.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2016-01-15 (6 days ago)
  dmi.bios.date: 01/11/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ET90WW (2.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 33525SP
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD EM DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ET90WW(2.08):bd01/11/2013:svnLENOVO:pn33525SP:pvrThinkPadT430u:rvnLENOVO:rn33525SP:rvrWin8STDEMDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 33525SP
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1507482] Re: ethtool self-test failed and creates a FW reset.

2016-01-26 Thread Talat Batheesh
Hi Rafael,

Any update with this bug ?

Thanks,
Talat 

** Tags added: wily

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

Title:
  ethtool self-test failed and creates a FW reset.

Status in linux package in Ubuntu:
  In Progress

Bug description:
  On ConnectX3 device we try to run self-test and it’s failed, also seen
  that cause a FW reset.

  Steps to reproduce:

  
  ~# ethtool -t ens2
  The test result is FAIL
  The test extra info:
  Interrupt Test   -16
  Link Test0
  Speed Test   0
  Register Test0
  Loopback Test0

  ~# dmesg
  [341548.619799] mlx4_core :07:00.0: command 0x31 timed out (go bit not 
cleared)
  [341548.803801] mlx4_core :07:00.0: command 0x49 timed out (go bit not 
cleared)
  [341548.803808] mlx4_core :07:00.0: device is going to be reset
  [341549.816587] mlx4_core :07:00.0: device was reset successfully
  [341549.823425] mlx4_en :07:00.0: Internal error detected, restarting 
device

  ~# cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="15.10 (Wily Werewolf)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Wily Werewolf (development branch)"
  VERSION_ID="15.10"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;

  ~# uname -r
  4.2.0-7-generic

  ~# ethtool -i ens2
  driver: mlx4_en
  version: 2.2-1 (Feb 2014)
  firmware-version: 2.34.5000
  bus-info: :07:00.0
  supports-statistics: yes
  supports-test: yes
  supports-eeprom-access: no
  supports-register-dump: no
  supports-priv-flags: yes

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

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


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

2016-01-26 Thread Brad Figg
** Description changed:

  This bug is for tracking the 3.13.0-77.121 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 19. January 2016 19:59 UTC
  kernel-stable-Prepare-package-end:Wednesday, 20. January 2016 17:22 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 20. January 2016 17:22 UTC
  kernel-stable-Promote-to-proposed-end:Thursday, 21. January 2016 15:01 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Thursday, 21. January 2016 16:01 UTC
  kernel-stable-Verification-testing-start:Thursday, 21. January 2016 16:01 UTC
  kernel-stable-Certification-testing-start:Thursday, 21. January 2016 16:01 UTC
  kernel-stable-Security-signoff-start:Thursday, 21. January 2016 16:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Thursday, 21. January 2016 16:02 UTC
  kernel-stable-Security-signoff-end:Friday, 22. January 2016 19:24 UTC
+ kernel-stable-Certification-testing-end:Tuesday, 26. January 2016 11:00 UTC

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

Title:
  linux: 3.13.0-77.121 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 19. January 2016 19:59 UTC
  kernel-stable-Prepare-package-end:Wednesday, 20. January 2016 17:22 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 20. January 2016 17:22 UTC
  kernel-stable-Promote-to-proposed-end:Thursday, 21. January 2016 15:01 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Thursday, 21. January 2016 16:01 UTC
  kernel-stable-Verification-testing-start:Thursday, 21. January 2016 16:01 UTC
  kernel-stable-Certification-testing-start:Thursday, 21. January 2016 16:01 UTC
  kernel-stable-Security-signoff-start:Thursday, 21. January 2016 16:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Thursday, 21. January 2016 16:02 UTC
  kernel-stable-Security-signoff-end:Friday, 22. January 2016 19:24 UTC
  kernel-stable-Certification-testing-end:Tuesday, 26. January 2016 11:00 UTC

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

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


[Kernel-packages] [Bug 1537324] Re: No brightness control on Samsung NP530U4E-K01RU

2016-01-26 Thread Christopher M. Penalver
** Tags removed: kernel-bug-exists-upstream
** Tags added: cherry-pick kernel-fixed-upstream

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

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

Title:
  No brightness control on Samsung NP530U4E-K01RU

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Backlight control does not work, but there are entries in
  /sys/class/backlight.

  Laptop model: NP530U4E-K01RU
  Video adapter: Intel HD graphics 4000

  I've tried all the suggestions from
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight

  kernel parameters  acpi_backlight=vendor,
  video.use_bios_initial_backlight=0,  video.use_native_backlight=1
  didn't work.

  In this laptop brightness is controlled by Fn+F2 and Fn+F3. Whenever i
  try to change brightness, the value in
  /sys/class/backlight/intel_backlight/brightness and
  /sys/class/backlight/intel_backlight/actual_brightness changes, but
  actual screen brightness is the same:

  $ grep . /sys/class/backlight/intel_backlight/*
  /sys/class/backlight/intel_backlight/actual_brightness:2792
  /sys/class/backlight/intel_backlight/bl_power:0
  /sys/class/backlight/intel_backlight/brightness:2792
  grep: /sys/class/backlight/intel_backlight/device: Is a directory
  /sys/class/backlight/intel_backlight/max_brightness:4648
  grep: /sys/class/backlight/intel_backlight/power: Is a directory
  grep: /sys/class/backlight/intel_backlight/subsystem: Is a directory
  /sys/class/backlight/intel_backlight/type:raw

  All the logs are in the attached archive backlight_bug_report.tar.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-25-generic 4.2.0-25.30
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jan 23 09:55:32 2016
  HibernationDevice: RESUME=UUID=9d4a6619-c5f9-46c2-b11b-e230e9d357e3
  InstallationDate: Installed on 2014-05-20 (613 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U4E/540U4E
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic 
root=UUID=686fa320-83d1-4015-a632-bb2a91390ab6 ro quiet splash 
video.use_bios_initial_backlight=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-11-25 (58 days ago)
  dmi.bios.date: 02/26/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P08ACM.065.140226.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP530U4E-K01RU
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP08ACM.065.140226.dg:bd02/26/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U4E/540U4E:pvrP08ACM:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U4E-K01RU:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 530U4E/540U4E
  dmi.product.version: P08ACM
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


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

2016-01-26 Thread Po-Hsu Lin
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-testing/trusty/3.13.0-77.121
/trusty-proposed-frozen.html

** Tags added: certification-testing-passed

** Changed in: kernel-sru-workflow/certification-testing
   Status: In Progress => 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/1535880

Title:
  linux: 3.13.0-77.121 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 19. January 2016 19:59 UTC
  kernel-stable-Prepare-package-end:Wednesday, 20. January 2016 17:22 UTC
  kernel-stable-Promote-to-proposed-start:Wednesday, 20. January 2016 17:22 UTC
  kernel-stable-Promote-to-proposed-end:Thursday, 21. January 2016 15:01 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Thursday, 21. January 2016 16:01 UTC
  kernel-stable-Verification-testing-start:Thursday, 21. January 2016 16:01 UTC
  kernel-stable-Certification-testing-start:Thursday, 21. January 2016 16:01 UTC
  kernel-stable-Security-signoff-start:Thursday, 21. January 2016 16:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Thursday, 21. January 2016 16:02 UTC
  kernel-stable-Security-signoff-end:Friday, 22. January 2016 19:24 UTC

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

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


[Kernel-packages] [Bug 1537324] Re: No brightness control on Samsung NP530U4E-K01RU

2016-01-26 Thread Andrey Makeev
Testing with 4.5-rc1 results:
/sys/class/backlight/acpi_video0/ appeared.
Brightness changes if i echo the value to 
/sys/class/backlight/acpi_video0/brightness

Tracked it down to this kernel.org bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=108971
It seems to be exactly the same issue.

For now I added kernel parameter acpi_backlight=video to grub config and
changed backlight control interface in xorg.conf  to acpi_video0. Works
fine.

** Bug watch added: Linux Kernel Bug Tracker #108971
   http://bugzilla.kernel.org/show_bug.cgi?id=108971

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

Title:
  No brightness control on Samsung NP530U4E-K01RU

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Backlight control does not work, but there are entries in
  /sys/class/backlight.

  Laptop model: NP530U4E-K01RU
  Video adapter: Intel HD graphics 4000

  I've tried all the suggestions from
  https://wiki.ubuntu.com/Kernel/Debugging/Backlight

  kernel parameters  acpi_backlight=vendor,
  video.use_bios_initial_backlight=0,  video.use_native_backlight=1
  didn't work.

  In this laptop brightness is controlled by Fn+F2 and Fn+F3. Whenever i
  try to change brightness, the value in
  /sys/class/backlight/intel_backlight/brightness and
  /sys/class/backlight/intel_backlight/actual_brightness changes, but
  actual screen brightness is the same:

  $ grep . /sys/class/backlight/intel_backlight/*
  /sys/class/backlight/intel_backlight/actual_brightness:2792
  /sys/class/backlight/intel_backlight/bl_power:0
  /sys/class/backlight/intel_backlight/brightness:2792
  grep: /sys/class/backlight/intel_backlight/device: Is a directory
  /sys/class/backlight/intel_backlight/max_brightness:4648
  grep: /sys/class/backlight/intel_backlight/power: Is a directory
  grep: /sys/class/backlight/intel_backlight/subsystem: Is a directory
  /sys/class/backlight/intel_backlight/type:raw

  All the logs are in the attached archive backlight_bug_report.tar.gz

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-25-generic 4.2.0-25.30
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jan 23 09:55:32 2016
  HibernationDevice: RESUME=UUID=9d4a6619-c5f9-46c2-b11b-e230e9d357e3
  InstallationDate: Installed on 2014-05-20 (613 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U4E/540U4E
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic 
root=UUID=686fa320-83d1-4015-a632-bb2a91390ab6 ro quiet splash 
video.use_bios_initial_backlight=0 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-generic N/A
   linux-backports-modules-4.2.0-25-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-11-25 (58 days ago)
  dmi.bios.date: 02/26/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P08ACM.065.140226.dg
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP530U4E-K01RU
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP08ACM.065.140226.dg:bd02/26/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U4E/540U4E:pvrP08ACM:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U4E-K01RU:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 530U4E/540U4E
  dmi.product.version: P08ACM
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


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

2016-01-26 Thread Brad Figg
tests ran: 153, failed: 0;
  
http://kernel.ubuntu.com/testing/3.13.0-77.121/bantam__3.13.0-77.121__2016-01-26_04-01-00/results-index.html

** Description changed:

  This bug is for tracking the 3.19.0-49.55~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:Friday, 22. January 2016 10:41 UTC
  kernel-stable-master-bug:1536775
  kernel-stable-Prepare-package-end:Friday, 22. January 2016 22:57 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 22. January 2016 22:57 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 25. January 2016 20:47 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 25. January 2016 22:01 UTC
  kernel-stable-Verification-testing-start:Monday, 25. January 2016 22:01 UTC
  kernel-stable-Certification-testing-start:Monday, 25. January 2016 22:01 UTC
  kernel-stable-Security-signoff-start:Monday, 25. January 2016 22:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 25. January 2016 22:01 UTC
+ kernel-stable-Security-signoff-end:Tuesday, 26. January 2016 09:02 UTC

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

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

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

Bug description:
  This bug is for tracking the 3.19.0-49.55~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:Friday, 22. January 2016 10:41 UTC
  kernel-stable-master-bug:1536775
  kernel-stable-Prepare-package-end:Friday, 22. January 2016 22:57 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 22. January 2016 22:57 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 25. January 2016 20:47 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 25. January 2016 22:01 UTC
  kernel-stable-Verification-testing-start:Monday, 25. January 2016 22:01 UTC
  kernel-stable-Certification-testing-start:Monday, 25. January 2016 22:01 UTC
  kernel-stable-Security-signoff-start:Monday, 25. January 2016 22:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 25. January 2016 22:01 UTC
  kernel-stable-Security-signoff-end:Tuesday, 26. January 2016 09:02 UTC

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

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


[Kernel-packages] [Bug 1537472] Re: Synaptics touchpad not recognised - OK on linux-image-3.13.0-74-generic 3.13.0-74.118

2016-01-26 Thread John Leake
Glad to assist but this is on the edge of my experience.  I had the same
problems with the header dependencies when installing, however 4.5-rc1
booted and the touchpad is still not recognised.  I noticed that there
was a TPM (6) error on boot.  Sorry I do not know how to  provide you
with any more info.

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

Title:
  Synaptics touchpad not recognised - OK on linux-
  image-3.13.0-74-generic  3.13.0-74.118

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Thinkpad T520 mousepad defaults to standard PS2 so there is no edge
  scroll etc. and thus no settings tab for touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-76-generic 3.13.0-76.120
  ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-76-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2053 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan 24 11:06:21 2016
  HibernationDevice: RESUME=UUID=0014b9e9-0896-45dd-8005-73598192eb15
  InstallationDate: Installed on 2015-03-21 (308 days ago)
  InstallationMedia: BackBox Linux 4.1 - Release i386
  MachineType: LENOVO 4242A25
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-76-generic 
root=UUID=52833b54-5bbe-4c2f-97e4-73240dfc57e9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-76-generic N/A
   linux-backports-modules-3.13.0-76-generic  N/A
   linux-firmware 1.127.20
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET64WW (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4242A25
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: 1S4242A25R9FKBZP
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET64WW(1.44):bd07/26/2013:svnLENOVO:pn4242A25:pvrThinkPadT520:rvnLENOVO:rn4242A25:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4242A25
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

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

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


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

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

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

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

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

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

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

Bug description:
  This bug is for tracking the 3.19.0-49.55~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:Friday, 22. January 2016 10:41 UTC
  kernel-stable-master-bug:1536775
  kernel-stable-Prepare-package-end:Friday, 22. January 2016 22:57 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 22. January 2016 22:57 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 25. January 2016 20:47 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 25. January 2016 22:01 UTC
  kernel-stable-Verification-testing-start:Monday, 25. January 2016 22:01 UTC
  kernel-stable-Certification-testing-start:Monday, 25. January 2016 22:01 UTC
  kernel-stable-Security-signoff-start:Monday, 25. January 2016 22:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 25. January 2016 22:01 UTC

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

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


[Kernel-packages] [Bug 1534345] Re: Ubuntu 15.10 Crashing Frequently on EC2 Instances w/ Enhanced Networking

2016-01-26 Thread Stefan Bader
Would be great if you were able to get it working again. At least to see
whether the crash happens in the same area (timers). At the moment this
sounds like something in user-space changed in a way that allows it to
mess badly with the kernel. That sounds bad. And if its really somethign
getting done with the timers that leaves a lot to look at.

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

Title:
  Ubuntu 15.10 Crashing Frequently on EC2 Instances w/ Enhanced
  Networking

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Lots of details and history of the problem here:
  https://askubuntu.com/questions/710747/after-upgrading-
  to-15-10-from-15-04-ec2-webservers-have-become-very-unstable

  10 of my webservers have started crashing immediately following the
  15.10 upgrade. As far as what exactly defines a "crash", Instance
  Status Checks fail, and I can no longer SSH to the machine. Background
  daemons running on the system stop responding, and nothing is written
  to the logs.

  After weeks of working with the AWS team, I finally fixed a netconsole
  issue via "echo 7 > /proc/sys/kernel/printk" and got netconsole
  working properly, and finally have a trace:

  
  [21410.260077] general protection fault:  [#1] SMP
  [21410.261976] Modules linked in: isofs xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc 
iptable_filter ip_tables x_tables ppdev intel_rapl iosf_mbi xen_fbfront 
fb_sys_fops input_leds serio_raw i2c_piix4 parport_pc 8250_fintek parport 
mac_hid netconsole configfs autofs4 crct10dif_pclmul crc32_pclmul cirrus 
syscopyarea sysfillrect sysimgblt aesni_intel ttm aes_x86_64 drm_kms_helper lrw 
gf128mul glue_helper ablk_helper cryptd psmouse drm ixgbevf pata_acpi floppy
  [21410.264054] CPU: 0 PID: 26957 Comm: apache2 Not tainted 4.2.0-23-generic 
#28-Ubuntu
  [21410.264054] Hardware name: Xen HVM domU, BIOS 4.2.amazon 12/07/2015
  [21410.264054] task: 8803f9809b80 ti: 8803f999c000 task.ti: 
8803f999c000
  [21410.264054] RIP: 0010:[]  [] 
run_timer_softirq+0x116/0x2d0
  [21410.264054] RSP: :8803ff203e98  EFLAGS: 00010086
  [21410.264054] RAX: dead00200200 RBX: 8803ff20e9c0 RCX: 
8803ff203ec8
  [21410.264054] RDX: 8803ff203ec8 RSI: 00011fc0 RDI: 
8803ff20e9c0
  [21410.264054] RBP: 8803ff203f08 R08: a77a R09: 

  [21410.264054] R10: 0020 R11: 0004 R12: 
007c
  [21410.264054] R13: 8172aaf0 R14:  R15: 
8803af955be0
  [21410.264054] FS:  7fb0ce6e8780() GS:8803ff20() 
knlGS:
  [21410.264054] CS:  0010 DS:  ES:  CR0: 80050033
  [21410.264054] CR2: 7fb0ce51e130 CR3: 0003fb233000 CR4: 
001406f0
  [21410.264054] Stack:
  [21410.264054]  8803ff203eb8 8803ff20f5f8 8803ff20f3f8 
8803ff20f1f8
  [21410.264054]  8803ff20e9f8 8803af955b58 dead00200200 
f60fabc0
  [21410.264054]  00011fc0 0001 81c0b0c8 
0001
  [21410.264054] Call Trace:
  [21410.264054]  
  [21410.264054]  [] __do_softirq+0xf6/0x250
  [21410.264054]  [] irq_exit+0xa3/0xb0
  [21410.264054]  [] xen_evtchn_do_upcall+0x39/0x50
  [21410.264054]  [] xen_hvm_callback_vector+0x6b/0x70
  [21410.264054]  
  [21410.264054] Code: 81 e6 00 00 20 00 48 85 d2 48 89 45 b8 0f 85 30 01 00 00 
4c 89 7b 08 0f 1f 44 00 00 49 8b 07 49 8b 57 08 48 85 c0 48 89 02 74 04 <48> 89 
50 08 41 f6 47 2a 10 48 b8 00 02 20 00 00 00 ad de 49 c7
  [21410.264054] RIP  [] run_timer_softirq+0x116/0x2d0
  [21410.264054]  RSP 

  I don't have a vmcore at the moment, but I'm trying to get one from
  AWS and should have one in the next couple of days. This is happening
  frequently and repeatedly since I first upgraded to 15.10 on early
  December.

  
  ubuntu@xxx-web-xx:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 15.10
  Release:  15.10
  Codename: wily
  ubuntu@xxx-web-xx:~$ uname -a
  Linux xxx-web-xx 4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux
  ubuntu@xxx-web-xx:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-23-generic 4.2.0-23.28
  ProcVersionSignature: User Name 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 14 15:42 seq
   crw-rw 1 root audio 116, 33 Jan 14 15:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', 

[Kernel-packages] [Bug 1364511] Re: CVE-2013-2595

2016-01-26 Thread Steve Beattie
** No longer affects: linux-lts-trusty (Ubuntu Lucid)

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

** No longer affects: linux-armadaxp (Ubuntu Lucid)

** No longer affects: linux-armadaxp (Ubuntu Utopic)

** No longer affects: linux-ec2 (Ubuntu Lucid)

** No longer affects: linux-ec2 (Ubuntu Utopic)

** No longer affects: linux-goldfish (Ubuntu Lucid)

** No longer affects: linux-goldfish (Ubuntu Utopic)

** No longer affects: linux-lts-saucy (Ubuntu Lucid)

** No longer affects: linux-lts-saucy (Ubuntu Utopic)

** No longer affects: linux-lts-quantal (Ubuntu Lucid)

** No longer affects: linux-lts-quantal (Ubuntu Utopic)

** No longer affects: linux-raspi2 (Ubuntu Lucid)

** No longer affects: linux-raspi2 (Ubuntu Utopic)

** No longer affects: linux-mvl-dove (Ubuntu Lucid)

** No longer affects: linux-mvl-dove (Ubuntu Utopic)

** No longer affects: linux-ti-omap4 (Ubuntu Lucid)

** No longer affects: linux-ti-omap4 (Ubuntu Utopic)

** No longer affects: linux-lts-vivid (Ubuntu Lucid)

** No longer affects: linux-lts-vivid (Ubuntu Utopic)

** No longer affects: linux (Ubuntu Lucid)

** No longer affects: linux (Ubuntu Utopic)

** No longer affects: linux-mako (Ubuntu Lucid)

** No longer affects: linux-mako (Ubuntu Utopic)

** No longer affects: linux-fsl-imx51 (Ubuntu Lucid)

** No longer affects: linux-fsl-imx51 (Ubuntu Utopic)

** No longer affects: linux-lts-utopic (Ubuntu Lucid)

** No longer affects: linux-lts-utopic (Ubuntu Utopic)

** No longer affects: linux-flo (Ubuntu Lucid)

** No longer affects: linux-flo (Ubuntu Utopic)

** No longer affects: linux-lts-raring (Ubuntu Lucid)

** No longer affects: linux-lts-raring (Ubuntu Utopic)

** No longer affects: linux-manta (Ubuntu Lucid)

** No longer affects: linux-manta (Ubuntu Utopic)

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

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

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

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

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

** Changed in: linux-manta (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-manta (Ubuntu Trusty)
   Importance: Undecided => Medium

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

** Changed in: linux-lts-vivid (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-lts-vivid (Ubuntu Trusty)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Importance: Undecided => Medium

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

** Changed in: linux-mako (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-mako (Ubuntu Trusty)
   Importance: Undecided => Medium

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

** Changed in: linux-lts-utopic (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Importance: Undecided => Medium

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

** Changed in: linux-goldfish (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-goldfish (Ubuntu Trusty)
   Importance: Undecided => Medium

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

** Changed in: linux-flo (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-flo (Ubuntu Trusty)
   Importance: Undecided => Medium

** Description changed:

  The device-initialization functionality in the MSM camera driver for the
  Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC)
  Android contributions for MSM devices and other products, enables
  MSM_CAM_IOCTL_SET_MEM_MAP_INFO ioctl calls for an unrestricted mmap
  interface, which allows attackers to gain privileges via a crafted
  application.
  
  Break-Fix: - If014e6d152786b508c8e7ee6c53631913cd4cfcf
+ Break-Fix: - If014e6d152786b508c8e7ee6c53631913cd4cfcf

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

[Kernel-packages] [Bug 1453216] Re: CVE-2014-3534

2016-01-26 Thread Steve Beattie
** No longer affects: linux-lts-trusty (Ubuntu Utopic)

** No longer affects: linux-armadaxp (Ubuntu Utopic)

** No longer affects: linux-ec2 (Ubuntu Utopic)

** No longer affects: linux-goldfish (Ubuntu Utopic)

** No longer affects: linux-lts-saucy (Ubuntu Utopic)

** No longer affects: linux-lts-quantal (Ubuntu Utopic)

** No longer affects: linux-raspi2 (Ubuntu Utopic)

** No longer affects: linux-mvl-dove (Ubuntu Utopic)

** No longer affects: linux-ti-omap4 (Ubuntu Utopic)

** No longer affects: linux-lts-vivid (Ubuntu Utopic)

** No longer affects: linux (Ubuntu Utopic)

** No longer affects: linux-mako (Ubuntu Utopic)

** No longer affects: linux-fsl-imx51 (Ubuntu Utopic)

** No longer affects: linux-lts-utopic (Ubuntu Utopic)

** No longer affects: linux-flo (Ubuntu Utopic)

** No longer affects: linux-lts-raring (Ubuntu Utopic)

** No longer affects: linux-manta (Ubuntu Utopic)

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided => Medium

** Changed in: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Importance: Undecided => Medium

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

Title:
  CVE-2014-3534

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

[Kernel-packages] [Bug 1356323] Re: CVE-2014-5207

2016-01-26 Thread Steve Beattie
** No longer affects: linux-lts-trusty (Ubuntu Utopic)

** No longer affects: linux-armadaxp (Ubuntu Utopic)

** No longer affects: linux-ec2 (Ubuntu Utopic)

** No longer affects: linux-goldfish (Ubuntu Utopic)

** No longer affects: linux-lts-saucy (Ubuntu Utopic)

** No longer affects: linux-lts-quantal (Ubuntu Utopic)

** No longer affects: linux-raspi2 (Ubuntu Utopic)

** No longer affects: linux-mvl-dove (Ubuntu Utopic)

** No longer affects: linux-ti-omap4 (Ubuntu Utopic)

** No longer affects: linux-lts-vivid (Ubuntu Utopic)

** No longer affects: linux (Ubuntu Utopic)

** No longer affects: linux-mako (Ubuntu Utopic)

** No longer affects: linux-fsl-imx51 (Ubuntu Utopic)

** No longer affects: linux-lts-utopic (Ubuntu Utopic)

** No longer affects: linux-flo (Ubuntu Utopic)

** No longer affects: linux-lts-raring (Ubuntu Utopic)

** No longer affects: linux-manta (Ubuntu Utopic)

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided => High

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

** Changed in: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided => High

** Changed in: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided => High

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

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

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

Title:
  CVE-2014-5207

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

[Kernel-packages] [Bug 1373050] Re: CVE-2014-7145

2016-01-26 Thread Steve Beattie
** No longer affects: linux-armadaxp (Ubuntu Utopic)

** No longer affects: linux-ec2 (Ubuntu Utopic)

** No longer affects: linux-lts-saucy (Ubuntu Utopic)

** No longer affects: linux-lts-quantal (Ubuntu Utopic)

** No longer affects: linux-mvl-dove (Ubuntu Utopic)

** No longer affects: linux-ti-omap4 (Ubuntu Utopic)

** No longer affects: linux (Ubuntu Utopic)

** No longer affects: linux-fsl-imx51 (Ubuntu Utopic)

** No longer affects: linux-lts-raring (Ubuntu Utopic)

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided => Medium

** Changed in: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided => Medium

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

Title:
  CVE-2014-7145

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

[Kernel-packages] [Bug 817975] Re: bluetoothd crashed with SIGSEGV in g_slice_alloc()

2016-01-26 Thread dino99
This version has expired long time ago, and is no more supported

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  bluetoothd crashed with SIGSEGV in g_slice_alloc()

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  resuming from suspend, this happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: bluez 4.95-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-7.8-generic-pae 3.0.0
  Uname: Linux 3.0.0-7-generic-pae i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Fri Jul 29 20:25:58 2011
  ExecutablePath: /usr/sbin/bluetoothd
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110705.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 646067U
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /usr/sbin/bluetoothd
  ProcEnviron:
   LANGUAGE=en_AU:en
   LC_CTYPE=en_US.UTF-8
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-7-generic-pae 
root=UUID=82e014e0-a6a0-4177-b400-5e70455f1b21 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0xb76ff5cd :mov
(%edi),%edx
   PC (0xb76ff5cd) ok
   source "(%edi)" (0x001c) not located in a known VMA region (needed 
readable region)!
   destination "%edx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: bluez
  StacktraceTop:
   g_slice_alloc () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_slist_append () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: bluetoothd crashed with SIGSEGV in g_slice_alloc()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/11/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETC6WW (2.26 )
  dmi.board.name: 646067U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETC6WW(2.26):bd05/11/2009:svnLENOVO:pn646067U:pvrThinkPadT61p:rvnLENOVO:rn646067U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 646067U
  dmi.product.version: ThinkPad T61p
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:1C:26:DB:2B:1A  ACL MTU: 1017:8  SCO MTU: 64:8
UP RUNNING 
RX bytes:450 acl:0 sco:0 events:17 errors:0
TX bytes:81 acl:0 sco:0 commands:17 errors:0

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

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


[Kernel-packages] [Bug 1461360] Re: [Feature]Knights Landing PMU (Performance Monitoring Unit) support

2016-01-26 Thread Tim Gardner
** Information type changed from Proprietary to Public

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  [Feature]Knights Landing PMU (Performance Monitoring Unit) support

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Add PMU support to the perf event subsystem for Knights Landing

  Schedule: 4.5

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

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


[Kernel-packages] [Bug 1158258] Re: CVE-2013-1797

2016-01-26 Thread Steve Beattie
** No longer affects: linux-lts-trusty (Ubuntu Lucid)

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

** No longer affects: linux-armadaxp (Ubuntu Lucid)

** No longer affects: linux-armadaxp (Ubuntu Utopic)

** No longer affects: linux-ec2 (Ubuntu Lucid)

** No longer affects: linux-ec2 (Ubuntu Utopic)

** No longer affects: linux-goldfish (Ubuntu Lucid)

** No longer affects: linux-goldfish (Ubuntu Utopic)

** No longer affects: linux-lts-saucy (Ubuntu Lucid)

** No longer affects: linux-lts-saucy (Ubuntu Utopic)

** No longer affects: linux-lts-quantal (Ubuntu Lucid)

** No longer affects: linux-lts-quantal (Ubuntu Utopic)

** No longer affects: linux-raspi2 (Ubuntu Lucid)

** No longer affects: linux-raspi2 (Ubuntu Utopic)

** No longer affects: linux-mvl-dove (Ubuntu Lucid)

** No longer affects: linux-mvl-dove (Ubuntu Utopic)

** No longer affects: linux-ti-omap4 (Ubuntu Lucid)

** No longer affects: linux-ti-omap4 (Ubuntu Utopic)

** No longer affects: linux-lts-vivid (Ubuntu Lucid)

** No longer affects: linux-lts-vivid (Ubuntu Utopic)

** No longer affects: linux (Ubuntu Lucid)

** No longer affects: linux (Ubuntu Utopic)

** No longer affects: linux-mako (Ubuntu Lucid)

** No longer affects: linux-mako (Ubuntu Utopic)

** No longer affects: linux-fsl-imx51 (Ubuntu Lucid)

** No longer affects: linux-fsl-imx51 (Ubuntu Utopic)

** No longer affects: linux-lts-utopic (Ubuntu Lucid)

** No longer affects: linux-lts-utopic (Ubuntu Utopic)

** No longer affects: linux-flo (Ubuntu Lucid)

** No longer affects: linux-flo (Ubuntu Utopic)

** No longer affects: linux-lts-raring (Ubuntu Lucid)

** No longer affects: linux-lts-raring (Ubuntu Utopic)

** No longer affects: linux-manta (Ubuntu Lucid)

** No longer affects: linux-manta (Ubuntu Utopic)

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

** Changed in: linux-lts-vivid (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-lts-vivid (Ubuntu Vivid)
   Importance: Undecided => Medium

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

** Changed in: linux-lts-vivid (Ubuntu Trusty)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Importance: Undecided => Medium

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

Title:
  CVE-2013-1797

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:
  Invalid
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:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  New
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Invalid
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
Status in linux-lts-backport-oneiric 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:
  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:
  Fix Released
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source 

[Kernel-packages] [Bug 1388974] Re: CVE-2014-7207

2016-01-26 Thread Steve Beattie
** No longer affects: linux-lts-trusty (Ubuntu Utopic)

** No longer affects: linux-armadaxp (Ubuntu Utopic)

** No longer affects: linux-ec2 (Ubuntu Utopic)

** No longer affects: linux-goldfish (Ubuntu Utopic)

** No longer affects: linux-lts-saucy (Ubuntu Utopic)

** No longer affects: linux-lts-quantal (Ubuntu Utopic)

** No longer affects: linux-raspi2 (Ubuntu Utopic)

** No longer affects: linux-mvl-dove (Ubuntu Utopic)

** No longer affects: linux-ti-omap4 (Ubuntu Utopic)

** No longer affects: linux-lts-vivid (Ubuntu Utopic)

** No longer affects: linux (Ubuntu Utopic)

** No longer affects: linux-mako (Ubuntu Utopic)

** No longer affects: linux-fsl-imx51 (Ubuntu Utopic)

** No longer affects: linux-lts-utopic (Ubuntu Utopic)

** No longer affects: linux-flo (Ubuntu Utopic)

** No longer affects: linux-lts-raring (Ubuntu Utopic)

** No longer affects: linux-manta (Ubuntu Utopic)

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided => Medium

** Changed in: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Importance: Undecided => Medium

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

Title:
  CVE-2014-7207

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:
  Invalid
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-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Won't Fix
Status in linux-lts-backport-natty source package in Lucid:
  Won't Fix
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:
  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-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta source package in Precise:
  Invalid
Status in linux-mvl-dove source package in Precise:
  Invalid
Status in linux-raspi2 source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
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
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-lts-vivid source package in Trusty:
  Fix Committed
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in 

[Kernel-packages] [Bug 869243] Re: CVE-2011-2496

2016-01-26 Thread Steve Beattie
** No longer affects: linux-lts-trusty (Ubuntu Lucid)

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

** No longer affects: linux-armadaxp (Ubuntu Lucid)

** No longer affects: linux-armadaxp (Ubuntu Utopic)

** No longer affects: linux-ec2 (Ubuntu Lucid)

** No longer affects: linux-ec2 (Ubuntu Utopic)

** No longer affects: linux-goldfish (Ubuntu Lucid)

** No longer affects: linux-goldfish (Ubuntu Utopic)

** No longer affects: linux-lts-saucy (Ubuntu Lucid)

** No longer affects: linux-lts-saucy (Ubuntu Utopic)

** No longer affects: linux-lts-quantal (Ubuntu Lucid)

** No longer affects: linux-lts-quantal (Ubuntu Utopic)

** No longer affects: linux-raspi2 (Ubuntu Lucid)

** No longer affects: linux-raspi2 (Ubuntu Utopic)

** No longer affects: linux-mvl-dove (Ubuntu Lucid)

** No longer affects: linux-mvl-dove (Ubuntu Utopic)

** No longer affects: linux-ti-omap4 (Ubuntu Lucid)

** No longer affects: linux-ti-omap4 (Ubuntu Utopic)

** No longer affects: linux-lts-vivid (Ubuntu Lucid)

** No longer affects: linux-lts-vivid (Ubuntu Utopic)

** No longer affects: linux (Ubuntu Lucid)

** No longer affects: linux (Ubuntu Utopic)

** No longer affects: linux-mako (Ubuntu Lucid)

** No longer affects: linux-mako (Ubuntu Utopic)

** No longer affects: linux-fsl-imx51 (Ubuntu Lucid)

** No longer affects: linux-fsl-imx51 (Ubuntu Utopic)

** No longer affects: linux-lts-utopic (Ubuntu Lucid)

** No longer affects: linux-lts-utopic (Ubuntu Utopic)

** No longer affects: linux-flo (Ubuntu Lucid)

** No longer affects: linux-flo (Ubuntu Utopic)

** No longer affects: linux-lts-raring (Ubuntu Lucid)

** No longer affects: linux-lts-raring (Ubuntu Utopic)

** No longer affects: linux-manta (Ubuntu Lucid)

** No longer affects: linux-manta (Ubuntu Utopic)

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

** Changed in: linux-lts-vivid (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-lts-vivid (Ubuntu Vivid)
   Importance: Undecided => Medium

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

** Changed in: linux-lts-vivid (Ubuntu Trusty)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Importance: Undecided => Medium

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

Title:
  CVE-2011-2496

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:
  Invalid
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:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  New
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Fix Released
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Invalid
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:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package 

[Kernel-packages] [Bug 869245] Re: CVE-2011-2517

2016-01-26 Thread Steve Beattie
** Also affects: linux (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-oneiric (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-fsl-imx51 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mvl-dove (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ec2 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-maverick (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-natty (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-oneiric (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-manta (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-flo (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-trusty (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

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

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

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

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

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

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Importance: Undecided => Medium

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

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

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

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-lts-raring (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-armadaxp (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-goldfish (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-mvl-dove (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: 

[Kernel-packages] [Bug 1538429] Re: CVE-2016-2069

2016-01-26 Thread Steve Beattie
CVE-2016-2069

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

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1538429] [NEW] CVE-2016-2069

2016-01-26 Thread Steve Beattie
*** This bug is a security vulnerability ***

Public security bug reported:

[x86 Linux TLB flush bug]

Break-Fix: - 71b3c126e61177eb693423f2e18a1914205b165e
Break-Fix: - 4eaffdd5a5fe6ff9f95e1ab4de1ac904d5e0fa8b

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

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

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

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

** Affects: linux-fsl-imx51 (Ubuntu)
 Importance: Medium
 Status: Invalid

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: linux-fsl-imx51 (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-lts-backport-maverick (Ubuntu Precise)
 Importance: Undecided
 Status: New

** Affects: linux-lts-backport-natty (Ubuntu Precise)
 Importance: Undecided
 Status: New

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

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

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

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

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

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

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

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

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

** Affects: linux-mvl-dove (Ubuntu Precise)
 Importance: Undecided
 Status: New

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

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

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

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

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

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

** Affects: linux-fsl-imx51 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-lts-backport-maverick (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Affects: linux-lts-backport-natty (Ubuntu Trusty)
 Importance: Undecided
 Status: New

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

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

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

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

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

** 

[Kernel-packages] [Bug 1527462] Re: [Feature]Skylake GT4e support

2016-01-26 Thread Tim Gardner
** Information type changed from Proprietary to Public

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  [Feature]Skylake GT4e support

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  Add PCIID for SKL GT4e in graphic statck.

  Hardware:
  Greenlow or SKL-H 4+4e

  upstream:
  kernel:  4.5
  drm:  2.4.66
  xf86-video-intel:  TBD
  mesa: mesa-11.1.0

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

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


[Kernel-packages] [Bug 1337339] Re: x86_64, ptrace: Enforce RIP <= TASK_SIZE_MAX (CVE-2014-4699)

2016-01-26 Thread Steve Beattie
** No longer affects: linux (Ubuntu Utopic)

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

** Changed in: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided => High

** Changed in: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided => High

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

Title:
  x86_64,ptrace: Enforce RIP <= TASK_SIZE_MAX (CVE-2014-4699)

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:
  Invalid
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Invalid
Status in linux-armadaxp source package in Vivid:
  Invalid
Status in linux-ec2 source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  Invalid
Status in linux-fsl-imx51 source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  Invalid
Status in linux-lts-quantal source package in Vivid:
  Invalid
Status in linux-lts-raring source package in Vivid:
  Invalid
Status in linux-lts-saucy source package in Vivid:
  Invalid
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid
Status in linux-lts-vivid source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  Invalid
Status in linux-manta source package in Vivid:
  Invalid
Status in linux-mvl-dove source package in Vivid:
  Invalid
Status in linux-raspi2 source package in Vivid:
  Invalid
Status in linux-ti-omap4 source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Invalid
Status in linux-armadaxp source package in Wily:
  Invalid
Status in linux-ec2 source package in Wily:
  Invalid
Status in linux-flo source package in Wily:
  Invalid
Status in linux-fsl-imx51 source package in Wily:
  Invalid
Status in linux-goldfish source package in Wily:
  Invalid
Status in linux-lts-quantal source package in Wily:
  Invalid
Status in linux-lts-raring source package in Wily:
  Invalid
Status in linux-lts-saucy source package in Wily:
  Invalid
Status in linux-lts-trusty source package in Wily:
  Invalid
Status in linux-lts-utopic source package in Wily:
  Invalid
Status in linux-lts-vivid source package in Wily:
  Invalid
Status in linux-mako source package in Wily:
  Invalid
Status in linux-manta source package in Wily:
  Invalid
Status in linux-mvl-dove source package in Wily:
  Invalid
Status in linux-raspi2 source package in Wily:
  New
Status in linux-ti-omap4 source package in Wily:
  Invalid

Bug description:
  The Linux kernel before 3.15.4 on Intel processors does not properly
  restrict use of a non-canonical value for the saved RIP address in the
  case of a system call that does not use IRET, which allows local users
  to leverage a race condition and gain privileges, or cause a denial of
  service (double fault), via a crafted application that makes ptrace
  and fork system calls.

  Break-Fix: 427abfa28afedffadfca9dd8b067eb6d36bac53f
  b9cd18de4db3c9ffa7e17b0dc0ca99ed5aa4d43a

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

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


[Kernel-packages] [Bug 1335314] Re: CVE-2014-4611

2016-01-26 Thread Steve Beattie
** No longer affects: linux-lts-trusty (Ubuntu Utopic)

** No longer affects: linux-armadaxp (Ubuntu Utopic)

** No longer affects: linux-ec2 (Ubuntu Utopic)

** No longer affects: linux-goldfish (Ubuntu Utopic)

** No longer affects: linux-lts-saucy (Ubuntu Utopic)

** No longer affects: linux-lts-quantal (Ubuntu Utopic)

** No longer affects: linux-raspi2 (Ubuntu Utopic)

** No longer affects: linux-mvl-dove (Ubuntu Utopic)

** No longer affects: linux-ti-omap4 (Ubuntu Utopic)

** No longer affects: linux-lts-vivid (Ubuntu Utopic)

** No longer affects: linux (Ubuntu Utopic)

** No longer affects: linux-mako (Ubuntu Utopic)

** No longer affects: linux-fsl-imx51 (Ubuntu Utopic)

** No longer affects: linux-lts-utopic (Ubuntu Utopic)

** No longer affects: linux-flo (Ubuntu Utopic)

** No longer affects: linux-lts-raring (Ubuntu Utopic)

** No longer affects: linux-manta (Ubuntu Utopic)

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided => Medium

** Changed in: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Importance: Undecided => Medium

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

Title:
  CVE-2014-4611

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

[Kernel-packages] [Bug 1356318] Re: CVE-2014-5206

2016-01-26 Thread Steve Beattie
** No longer affects: linux-lts-trusty (Ubuntu Utopic)

** No longer affects: linux-armadaxp (Ubuntu Utopic)

** No longer affects: linux-ec2 (Ubuntu Utopic)

** No longer affects: linux-goldfish (Ubuntu Utopic)

** No longer affects: linux-lts-saucy (Ubuntu Utopic)

** No longer affects: linux-lts-quantal (Ubuntu Utopic)

** No longer affects: linux-raspi2 (Ubuntu Utopic)

** No longer affects: linux-mvl-dove (Ubuntu Utopic)

** No longer affects: linux-ti-omap4 (Ubuntu Utopic)

** No longer affects: linux-lts-vivid (Ubuntu Utopic)

** No longer affects: linux (Ubuntu Utopic)

** No longer affects: linux-mako (Ubuntu Utopic)

** No longer affects: linux-fsl-imx51 (Ubuntu Utopic)

** No longer affects: linux-lts-utopic (Ubuntu Utopic)

** No longer affects: linux-flo (Ubuntu Utopic)

** No longer affects: linux-lts-raring (Ubuntu Utopic)

** No longer affects: linux-manta (Ubuntu Utopic)

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided => High

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

** Changed in: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided => High

** Changed in: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided => High

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

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

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

Title:
  CVE-2014-5206

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

[Kernel-packages] [Bug 1538425] Re: CVE-2015-8785

2016-01-26 Thread Steve Beattie
CVE-2015-8785

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

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1538425] [NEW] CVE-2015-8785

2016-01-26 Thread Steve Beattie
*** This bug is a security vulnerability ***

Public security bug reported:

[fuse: possible denial of service in fuse_fill_write_pages()]

Break-Fix: ea9b9907b82a09bd1a708004454f7065de77c5b0
3ca8138f014a913f98e6ef40e939868e1e9ea876

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

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

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

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

** Affects: linux-fsl-imx51 (Ubuntu)
 Importance: Medium
 Status: Invalid

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: linux-fsl-imx51 (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-lts-backport-maverick (Ubuntu Precise)
 Importance: Undecided
 Status: New

** Affects: linux-lts-backport-natty (Ubuntu Precise)
 Importance: Undecided
 Status: New

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

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

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

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

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

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

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

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

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

** Affects: linux-mvl-dove (Ubuntu Precise)
 Importance: Undecided
 Status: New

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

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

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

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

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

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

** Affects: linux-fsl-imx51 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-lts-backport-maverick (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Affects: linux-lts-backport-natty (Ubuntu Trusty)
 Importance: Undecided
 Status: New

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

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

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

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

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

[Kernel-packages] [Bug 1364516] Re: CVE-2013-2597

2016-01-26 Thread Steve Beattie
** No longer affects: linux-lts-trusty (Ubuntu Lucid)

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

** No longer affects: linux-armadaxp (Ubuntu Lucid)

** No longer affects: linux-armadaxp (Ubuntu Utopic)

** No longer affects: linux-ec2 (Ubuntu Lucid)

** No longer affects: linux-ec2 (Ubuntu Utopic)

** No longer affects: linux-goldfish (Ubuntu Lucid)

** No longer affects: linux-goldfish (Ubuntu Utopic)

** No longer affects: linux-lts-saucy (Ubuntu Lucid)

** No longer affects: linux-lts-saucy (Ubuntu Utopic)

** No longer affects: linux-lts-quantal (Ubuntu Lucid)

** No longer affects: linux-lts-quantal (Ubuntu Utopic)

** No longer affects: linux-raspi2 (Ubuntu Lucid)

** No longer affects: linux-raspi2 (Ubuntu Utopic)

** No longer affects: linux-mvl-dove (Ubuntu Lucid)

** No longer affects: linux-mvl-dove (Ubuntu Utopic)

** No longer affects: linux-ti-omap4 (Ubuntu Lucid)

** No longer affects: linux-ti-omap4 (Ubuntu Utopic)

** No longer affects: linux-lts-vivid (Ubuntu Lucid)

** No longer affects: linux-lts-vivid (Ubuntu Utopic)

** No longer affects: linux (Ubuntu Lucid)

** No longer affects: linux (Ubuntu Utopic)

** No longer affects: linux-mako (Ubuntu Lucid)

** No longer affects: linux-mako (Ubuntu Utopic)

** No longer affects: linux-fsl-imx51 (Ubuntu Lucid)

** No longer affects: linux-fsl-imx51 (Ubuntu Utopic)

** No longer affects: linux-lts-utopic (Ubuntu Lucid)

** No longer affects: linux-lts-utopic (Ubuntu Utopic)

** No longer affects: linux-flo (Ubuntu Lucid)

** No longer affects: linux-flo (Ubuntu Utopic)

** No longer affects: linux-lts-raring (Ubuntu Lucid)

** No longer affects: linux-lts-raring (Ubuntu Utopic)

** No longer affects: linux-manta (Ubuntu Lucid)

** No longer affects: linux-manta (Ubuntu Utopic)

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

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

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

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

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

** Changed in: linux-manta (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-manta (Ubuntu Trusty)
   Importance: Undecided => Medium

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

** Changed in: linux-lts-vivid (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-lts-vivid (Ubuntu Trusty)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Importance: Undecided => Medium

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

** Changed in: linux-mako (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-mako (Ubuntu Trusty)
   Importance: Undecided => Medium

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

** Changed in: linux-lts-utopic (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Importance: Undecided => Medium

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

** Changed in: linux-goldfish (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-goldfish (Ubuntu Trusty)
   Importance: Undecided => Medium

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

** Changed in: linux-flo (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-flo (Ubuntu Trusty)
   Importance: Undecided => Medium

** Description changed:

  Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c
  in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in
  Qualcomm Innovation Center (QuIC) Android contributions for MSM devices
  and other products, allows attackers to gain privileges via an
  application that leverages /dev/msm_acdb access and provides a large
  size value in an ioctl argument.
  
+ Break-Fix: - I4a5b5ca5212bea32b671027d68a66367c5d4c4e7
  Break-Fix: - I8230fdb00a7b57d398929e8ab0eb6587476f3db1
- Break-Fix: - I4a5b5ca5212bea32b671027d68a66367c5d4c4e7

-- 
You received this bug notification because you are a member of Kernel
Packages, which is 

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

2016-01-26 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  logitech wireless keyboard (K270) and trackball (M570) laggy with
  latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently inputs from my logitech wireless keyboard and trackball,
  became very laggy, and dropping out at times.

  This is a regression since 4.3.0-2.11 works perfectly
  4.3.0-5.16 is really bad, with devices often dropping out completely or 
loosing all input for over 30secs at times
  4.3.0.7.8 seems better, but still very slow at times, sometimes is like 
typing 1 character per second or noticable lag on mouse input.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-7-generic 4.3.0-7.18
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  darkness   8233 F pulseaudio
   /dev/snd/controlC0:  darkness   8233 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 27 16:14:55 2016
  InstallationDate: Installed on 2012-09-23 (1221 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
  MachineType: Gigabyte Technology Co., Ltd. P67A-UD3R-B3
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-7-generic 
root=UUID=71eeb904-068b-41c2-9d34-59365ca4c3ad ro quiet splash 
init=/lib/systemd/systemd nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-7-generic N/A
   linux-backports-modules-4.3.0-7-generic  N/A
   linux-firmware   1.155
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: P67A-UD3R-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD3R-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD3R-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P67A-UD3R-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1341472] Re: CVE-2014-4943

2016-01-26 Thread Steve Beattie
** No longer affects: linux-lts-trusty (Ubuntu Utopic)

** No longer affects: linux-armadaxp (Ubuntu Utopic)

** No longer affects: linux-ec2 (Ubuntu Utopic)

** No longer affects: linux-goldfish (Ubuntu Utopic)

** No longer affects: linux-lts-saucy (Ubuntu Utopic)

** No longer affects: linux-lts-quantal (Ubuntu Utopic)

** No longer affects: linux-raspi2 (Ubuntu Utopic)

** No longer affects: linux-mvl-dove (Ubuntu Utopic)

** No longer affects: linux-ti-omap4 (Ubuntu Utopic)

** No longer affects: linux-lts-vivid (Ubuntu Utopic)

** No longer affects: linux (Ubuntu Utopic)

** No longer affects: linux-mako (Ubuntu Utopic)

** No longer affects: linux-fsl-imx51 (Ubuntu Utopic)

** No longer affects: linux-lts-utopic (Ubuntu Utopic)

** No longer affects: linux-flo (Ubuntu Utopic)

** No longer affects: linux-lts-raring (Ubuntu Utopic)

** No longer affects: linux-manta (Ubuntu Utopic)

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided => High

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

** Changed in: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided => High

** Changed in: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided => High

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

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

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

Title:
  CVE-2014-4943

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

[Kernel-packages] [Bug 1349799] Re: CVE-2014-5045

2016-01-26 Thread Steve Beattie
** No longer affects: linux-armadaxp (Ubuntu Utopic)

** No longer affects: linux-ec2 (Ubuntu Utopic)

** No longer affects: linux-lts-saucy (Ubuntu Utopic)

** No longer affects: linux-lts-quantal (Ubuntu Utopic)

** No longer affects: linux-mvl-dove (Ubuntu Utopic)

** No longer affects: linux-ti-omap4 (Ubuntu Utopic)

** No longer affects: linux (Ubuntu Utopic)

** No longer affects: linux-fsl-imx51 (Ubuntu Utopic)

** No longer affects: linux-lts-raring (Ubuntu Utopic)

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided => Medium

** Changed in: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided => Medium

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

Title:
  CVE-2014-5045

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

[Kernel-packages] [Bug 869237] Re: CVE-2011-2491

2016-01-26 Thread Steve Beattie
** Also affects: linux (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-oneiric (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-fsl-imx51 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mvl-dove (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ec2 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-maverick (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-natty (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-oneiric (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-manta (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-flo (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-trusty (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

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

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

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

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

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

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Importance: Undecided => Medium

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

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

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

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-lts-raring (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-armadaxp (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-goldfish (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-mvl-dove (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: 

[Kernel-packages] [Bug 1399142] Re: CVE-2010-5313

2016-01-26 Thread Steve Beattie
** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-fsl-imx51 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mvl-dove (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ec2 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-maverick (Ubuntu Xenial)
   Importance: Undecided
   Status: Invalid

** Also affects: linux-lts-backport-natty (Ubuntu Xenial)
   Importance: Undecided
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-manta (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-flo (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-trusty (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-vivid (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

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

** Changed in: linux-raspi2 (Ubuntu Xenial)
   Importance: Undecided => Medium

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

Title:
  CVE-2010-5313

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:
  Invalid
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-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in linux-lts-saucy package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-lts-vivid package in Ubuntu:
  Invalid
Status in linux-mako package in Ubuntu:
  Invalid
Status in linux-manta package in Ubuntu:
  Invalid
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Invalid
Status in linux-lts-backport-natty source package in Lucid:
  Invalid
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp 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-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-ti-omap4 source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in linux-flo source package in Trusty:
  Invalid
Status in linux-goldfish source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Trusty:
  Invalid
Status in linux-lts-backport-natty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status in linux-mako source package in Trusty:
  Invalid
Status in linux-manta source package in Trusty:
  Invalid
Status in linux-lts-backport-maverick source package in Utopic:
  Invalid
Status in linux-lts-backport-natty source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Invalid
Status in linux-flo source package in Vivid:
  Invalid
Status in linux-goldfish source package in Vivid:
  Invalid
Status in linux-lts-backport-maverick source package in Vivid:
  Invalid
Status in linux-lts-backport-natty source package in Vivid:
  Invalid
Status in linux-mako source package in Vivid:
  Invalid
Status in linux-manta source package in Vivid:
  Invalid
Status in linux source package in Wily:
  Invalid
Status in linux-armadaxp source package in Wily:
  Invalid

[Kernel-packages] [Bug 1538428] Re: CVE-2016-2053

2016-01-26 Thread Steve Beattie
CVE-2016-2053

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

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1538428] [NEW] CVE-2016-2053

2016-01-26 Thread Steve Beattie
*** This bug is a security vulnerability ***

Public security bug reported:

[Denial of service with specially crafted key file]

Break-Fix: 3d167d68e3805ee45ed2e8412fc03ed919c54c24 -

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

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

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

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

** Affects: linux-fsl-imx51 (Ubuntu)
 Importance: Medium
 Status: Invalid

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** Affects: linux-fsl-imx51 (Ubuntu Precise)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-lts-backport-maverick (Ubuntu Precise)
 Importance: Undecided
 Status: New

** Affects: linux-lts-backport-natty (Ubuntu Precise)
 Importance: Undecided
 Status: New

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

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

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

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

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

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

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

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

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

** Affects: linux-mvl-dove (Ubuntu Precise)
 Importance: Undecided
 Status: New

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

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

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

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

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

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

** Affects: linux-fsl-imx51 (Ubuntu Trusty)
 Importance: Medium
 Status: Invalid

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

** Affects: linux-lts-backport-maverick (Ubuntu Trusty)
 Importance: Undecided
 Status: New

** Affects: linux-lts-backport-natty (Ubuntu Trusty)
 Importance: Undecided
 Status: New

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

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

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

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

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

** Affects: linux-lts-vivid 

[Kernel-packages] [Bug 917829] Re: CVE-2011-4324

2016-01-26 Thread Steve Beattie
** Also affects: linux (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-oneiric (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-fsl-imx51 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mvl-dove (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ec2 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-maverick (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-natty (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-oneiric (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-manta (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-flo (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-trusty (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

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

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

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

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

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

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Importance: Undecided => Medium

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

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

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

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-lts-raring (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-armadaxp (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-goldfish (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-mvl-dove (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: 

Re: [Kernel-packages] [Bug 1448485] Re: [Compaq Presario CQ60-300EO Notebook PC] kernel doesn't recognize backlight fn keys

2016-01-26 Thread Martin Bångens
there is no solution, most Fn keys don't work, I don't care, you don't have
the time. So stop this bug report from sending me stupid emails, shut this
down already. Don't think you can even bay this pis of shit computer new
anyway. The cpu is shit plus its nvidia, there is no point.

2016-01-10 9:39 GMT+01:00 Chris <1448...@bugs.launchpad.net>:

> There is a solution?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1448485
>
> Title:
>   [Compaq Presario CQ60-300EO Notebook PC] kernel doesn't recognize
>   backlight fn keys
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I'm using Ubuntu 15.04 and fn+f7 and fn+f8 use to lower and higher the
> brightness of the screen.
>   In slackware using kernel 3.14.33 those keys works and give output from
> acpi_listen.
>   In kernel 3.16 to 4.0 those keys don't work and acpi_listen outputs
> nothing.
>
>   I expected fn+f7 and fn+f8 to work
>
>   https://bugzilla.kernel.org/show_bug.cgi?id=60670
>   This bug my be related
>
>   This is my first bug report.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 15.04
>   Package: linux-image-3.19.0-15-generic 3.19.0-15.15 [modified:
> boot/vmlinuz-3.19.0-15-generic]
>   ProcVersionSignature: Ubuntu 3.19.0-15.15-lowlatency 3.19.3
>   Uname: Linux 3.19.0-15-lowlatency x86_64
>   ApportVersion: 2.17.2-0ubuntu1
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  marbangens   1334 F pulseaudio
>   CurrentDesktop: Unity
>   Date: Sat Apr 25 17:04:30 2015
>   HibernationDevice: RESUME=UUID=22f95b90-3ec0-4b6d-9e76-13042dc0a290
>   InstallationDate: Installed on 2015-04-23 (1 days ago)
>   InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
>   MachineType: Hewlett-Packard Compaq Presario CQ60 Notebook PC
>   ProcFB: 0 nouveaufb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-lowlatency
> root=UUID=d4f39d6b-137e-4248-81cb-ce920cdee909 ro quiet splash vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-3.19.0-15-lowlatency N/A
>linux-backports-modules-3.19.0-15-lowlatency  N/A
>linux-firmware1.143
>   RfKill:
>0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
>   SourcePackage: linux
>   UdevLog: Error: [Errno 2] Filen eller katalogen finns inte:
> '/var/log/udev'
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 08/18/2009
>   dmi.bios.vendor: Hewlett-Packard
>   dmi.bios.version: F.54
>   dmi.board.name: 303C
>   dmi.board.vendor: Wistron
>   dmi.board.version: 08.60
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Wistron
>   dmi.chassis.version: N/A
>   dmi.modalias:
> dmi:bvnHewlett-Packard:bvrF.54:bd08/18/2009:svnHewlett-Packard:pnCompaqPresarioCQ60NotebookPC:pvrF.54:rvnWistron:rn303C:rvr08.60:cvnWistron:ct10:cvrN/A:
>   dmi.product.name: Compaq Presario CQ60 Notebook PC
>   dmi.product.version: F.54
>   dmi.sys.vendor: Hewlett-Packard
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1448485/+subscriptions
>

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

Title:
  [Compaq Presario CQ60-300EO Notebook PC] kernel doesn't recognize
  backlight fn keys

Status in linux package in Ubuntu:
  Incomplete

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

  I expected fn+f7 and fn+f8 to work

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

  This is my first bug report.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-15-generic 3.19.0-15.15 [modified: 
boot/vmlinuz-3.19.0-15-generic]
  ProcVersionSignature: Ubuntu 3.19.0-15.15-lowlatency 3.19.3
  Uname: Linux 3.19.0-15-lowlatency x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marbangens   1334 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 25 17:04:30 2015
  HibernationDevice: RESUME=UUID=22f95b90-3ec0-4b6d-9e76-13042dc0a290
  InstallationDate: Installed on 2015-04-23 (1 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Hewlett-Packard Compaq Presario CQ60 Notebook PC
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-lowlatency 
root=UUID=d4f39d6b-137e-4248-81cb-ce920cdee909 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-lowlatency N/A
   

[Kernel-packages] [Bug 1538404] [NEW] logitech wireless keyboard (K270) and trackball (M570) laggy with latest kernels

2016-01-26 Thread Tim
Public bug reported:

Recently inputs from my logitech wireless keyboard and trackball, became
very laggy, and dropping out at times.

This is a regression since 4.3.0-2.11 works perfectly
4.3.0-5.16 is really bad, with devices often dropping out completely or loosing 
all input for over 30secs at times
4.3.0.7.8 seems better, but still very slow at times, sometimes is like typing 
1 character per second or noticable lag on mouse input.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.3.0-7-generic 4.3.0-7.18
ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
Uname: Linux 4.3.0-7-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.4-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  darkness   8233 F pulseaudio
 /dev/snd/controlC0:  darkness   8233 F pulseaudio
CurrentDesktop: GNOME
Date: Wed Jan 27 16:14:55 2016
InstallationDate: Installed on 2012-09-23 (1221 days ago)
InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
MachineType: Gigabyte Technology Co., Ltd. P67A-UD3R-B3
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-7-generic 
root=UUID=71eeb904-068b-41c2-9d34-59365ca4c3ad ro quiet splash 
init=/lib/systemd/systemd nomdmonddf nomdmonisw
RelatedPackageVersions:
 linux-restricted-modules-4.3.0-7-generic N/A
 linux-backports-modules-4.3.0-7-generic  N/A
 linux-firmware   1.155
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/21/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F9
dmi.board.name: P67A-UD3R-B3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD3R-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD3R-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P67A-UD3R-B3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug xenial

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

Title:
  logitech wireless keyboard (K270) and trackball (M570) laggy with
  latest kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently inputs from my logitech wireless keyboard and trackball,
  became very laggy, and dropping out at times.

  This is a regression since 4.3.0-2.11 works perfectly
  4.3.0-5.16 is really bad, with devices often dropping out completely or 
loosing all input for over 30secs at times
  4.3.0.7.8 seems better, but still very slow at times, sometimes is like 
typing 1 character per second or noticable lag on mouse input.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-7-generic 4.3.0-7.18
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  Uname: Linux 4.3.0-7-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  darkness   8233 F pulseaudio
   /dev/snd/controlC0:  darkness   8233 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Jan 27 16:14:55 2016
  InstallationDate: Installed on 2012-09-23 (1221 days ago)
  InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha 
amd64(20120922)
  MachineType: Gigabyte Technology Co., Ltd. P67A-UD3R-B3
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-7-generic 
root=UUID=71eeb904-068b-41c2-9d34-59365ca4c3ad ro quiet splash 
init=/lib/systemd/systemd nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-7-generic N/A
   linux-backports-modules-4.3.0-7-generic  N/A
   linux-firmware   1.155
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/21/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: P67A-UD3R-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF9:bd03/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD3R-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD3R-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P67A-UD3R-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1538406] Re: REGRESSION ThinkPad T410 fails to see AHCI device on boot with wily SRU kernels

2016-01-26 Thread Stefano Rivera
Nope, it was a fucked initramfs, due to a crazy local udev rule. That
took way too long to debug.

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

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

Title:
  REGRESSION ThinkPad T410 fails to see AHCI device on boot with wily
  SRU kernels

Status in linux package in Ubuntu:
  Invalid

Bug description:
  We have a set of ThinkPads (T410 and T540p) that are failing to boot
  (not locating their root fs device) with post-release kernels.

  The AHCI adaptor (:00:1f.5) simply isn't visible in
  /sys/bus/pci/devices/

  The problem is apparent in 4.2.0.25-30, and not in 4.2.0-16.19

  If the SATA device mode is changed from AHCI to IDE emulation, then
  they reliably boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Jan 27 16:41:50 2016
  HibernationDevice: RESUME=UUID=185cef3a-6688-4034-a910-4f6ecdea2c20
  IwConfig:
   enp0s25   no wireless extensions.
   
   lono wireless extensions.
   
   enx8a549328aae7  no wireless extensions.
  MachineType: LENOVO 253725M
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=e5bcc2d8-520b-4648-9a08-0cc1d65152fd ro BOOTIF=01-f0-de-f1-49-05-1b 
quiet splash crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET75WW (1.35 )
  dmi.board.name: 253725M
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET75WW(1.35):bd02/01/2011:svnLENOVO:pn253725M:pvrThinkPadT410:rvnLENOVO:rn253725M:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 253725M
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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

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


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

2016-01-26 Thread bugproxy
--- Comment From pt...@cn.ibm.com 2016-01-27 02:02 EDT---
FYI. We can reproduce this problem with the 4.2.0-25-generic 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/1463654

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

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

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

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

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

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

[Kernel-packages] [Bug 880890] Re: CVE-2011-3209

2016-01-26 Thread Steve Beattie
** Also affects: linux (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-oneiric (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

** Also affects: linux (Ubuntu Xenial)
   Importance: Low
   Status: Invalid

** Also affects: linux-fsl-imx51 (Ubuntu Xenial)
   Importance: Low
   Status: Invalid

** Also affects: linux-mvl-dove (Ubuntu Xenial)
   Importance: Low
   Status: Invalid

** Also affects: linux-ec2 (Ubuntu Xenial)
   Importance: Low
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Xenial)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-backport-maverick (Ubuntu Xenial)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-backport-natty (Ubuntu Xenial)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-backport-oneiric (Ubuntu Xenial)
   Importance: Low
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Xenial)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Xenial)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Xenial)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Xenial)
   Importance: Low
   Status: Invalid

** Also affects: linux-mako (Ubuntu Xenial)
   Importance: Low
   Status: Invalid

** Also affects: linux-manta (Ubuntu Xenial)
   Importance: Low
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Xenial)
   Importance: Low
   Status: Invalid

** Also affects: linux-flo (Ubuntu Xenial)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-trusty (Ubuntu Xenial)
   Importance: Low
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Xenial)
   Importance: Low
   Status: Invalid

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

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

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

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

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

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Importance: Undecided => Low

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

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

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

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided => Low

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

** Changed in: linux-lts-raring (Ubuntu Wily)
   Importance: Undecided => Low

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

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

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

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

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

** Changed in: linux-mvl-dove (Ubuntu Wily)
   Importance: Undecided => Low

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

** Changed in: 

[Kernel-packages] [Bug 1538406] [NEW] REGRESSION ThinkPad T410 fails to see AHCI device on boot with wily SRU kernels

2016-01-26 Thread Stefano Rivera
Public bug reported:

We have a set of ThinkPads (T410 and T540p) that are failing to boot
(not locating their root fs device) with post-release kernels.

The AHCI adaptor (:00:1f.5) simply isn't visible in
/sys/bus/pci/devices/

The problem is apparent in 4.2.0.25-30, and not in 4.2.0-16.19

If the SATA device mode is changed from AHCI to IDE emulation, then they
reliably boot.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-16-generic 4.2.0-16.19
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: Unity
Date: Wed Jan 27 16:41:50 2016
HibernationDevice: RESUME=UUID=185cef3a-6688-4034-a910-4f6ecdea2c20
IwConfig:
 enp0s25   no wireless extensions.
 
 lono wireless extensions.
 
 enx8a549328aae7  no wireless extensions.
MachineType: LENOVO 253725M
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=e5bcc2d8-520b-4648-9a08-0cc1d65152fd ro BOOTIF=01-f0-de-f1-49-05-1b 
quiet splash crashkernel=384M-:128M
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-16-generic N/A
 linux-backports-modules-4.2.0-16-generic  N/A
 linux-firmware1.149.3
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/01/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 6IET75WW (1.35 )
dmi.board.name: 253725M
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6IET75WW(1.35):bd02/01/2011:svnLENOVO:pn253725M:pvrThinkPadT410:rvnLENOVO:rn253725M:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 253725M
dmi.product.version: ThinkPad T410
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug wily

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

Title:
  REGRESSION ThinkPad T410 fails to see AHCI device on boot with wily
  SRU kernels

Status in linux package in Ubuntu:
  New

Bug description:
  We have a set of ThinkPads (T410 and T540p) that are failing to boot
  (not locating their root fs device) with post-release kernels.

  The AHCI adaptor (:00:1f.5) simply isn't visible in
  /sys/bus/pci/devices/

  The problem is apparent in 4.2.0.25-30, and not in 4.2.0-16.19

  If the SATA device mode is changed from AHCI to IDE emulation, then
  they reliably boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Jan 27 16:41:50 2016
  HibernationDevice: RESUME=UUID=185cef3a-6688-4034-a910-4f6ecdea2c20
  IwConfig:
   enp0s25   no wireless extensions.
   
   lono wireless extensions.
   
   enx8a549328aae7  no wireless extensions.
  MachineType: LENOVO 253725M
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=e5bcc2d8-520b-4648-9a08-0cc1d65152fd ro BOOTIF=01-f0-de-f1-49-05-1b 
quiet splash crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET75WW (1.35 )
  dmi.board.name: 253725M
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET75WW(1.35):bd02/01/2011:svnLENOVO:pn253725M:pvrThinkPadT410:rvnLENOVO:rn253725M:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 253725M
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1340085] Re: CVE-2014-2580

2016-01-26 Thread Steve Beattie
** No longer affects: linux-armadaxp (Ubuntu Utopic)

** No longer affects: linux-ec2 (Ubuntu Utopic)

** No longer affects: linux-lts-saucy (Ubuntu Utopic)

** No longer affects: linux-lts-quantal (Ubuntu Utopic)

** No longer affects: linux-mvl-dove (Ubuntu Utopic)

** No longer affects: linux-ti-omap4 (Ubuntu Utopic)

** No longer affects: linux (Ubuntu Utopic)

** No longer affects: linux-fsl-imx51 (Ubuntu Utopic)

** No longer affects: linux-lts-raring (Ubuntu Utopic)

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided => Medium

** Changed in: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided => Medium

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

Title:
  CVE-2014-2580

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

[Kernel-packages] [Bug 1370031] Re: CVE-2014-3183

2016-01-26 Thread Steve Beattie
** No longer affects: linux-lts-trusty (Ubuntu Utopic)

** No longer affects: linux-armadaxp (Ubuntu Utopic)

** No longer affects: linux-ec2 (Ubuntu Utopic)

** No longer affects: linux-goldfish (Ubuntu Utopic)

** No longer affects: linux-lts-saucy (Ubuntu Utopic)

** No longer affects: linux-lts-quantal (Ubuntu Utopic)

** No longer affects: linux-raspi2 (Ubuntu Utopic)

** No longer affects: linux-mvl-dove (Ubuntu Utopic)

** No longer affects: linux-ti-omap4 (Ubuntu Utopic)

** No longer affects: linux-lts-vivid (Ubuntu Utopic)

** No longer affects: linux (Ubuntu Utopic)

** No longer affects: linux-mako (Ubuntu Utopic)

** No longer affects: linux-fsl-imx51 (Ubuntu Utopic)

** No longer affects: linux-lts-utopic (Ubuntu Utopic)

** No longer affects: linux-flo (Ubuntu Utopic)

** No longer affects: linux-lts-raring (Ubuntu Utopic)

** No longer affects: linux-manta (Ubuntu Utopic)

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided => Medium

** Changed in: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Importance: Undecided => Medium

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

Title:
  CVE-2014-3183

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

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

2016-01-26 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  REGRESSION ThinkPad T410 fails to see AHCI device on boot with wily
  SRU kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We have a set of ThinkPads (T410 and T540p) that are failing to boot
  (not locating their root fs device) with post-release kernels.

  The AHCI adaptor (:00:1f.5) simply isn't visible in
  /sys/bus/pci/devices/

  The problem is apparent in 4.2.0.25-30, and not in 4.2.0-16.19

  If the SATA device mode is changed from AHCI to IDE emulation, then
  they reliably boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Jan 27 16:41:50 2016
  HibernationDevice: RESUME=UUID=185cef3a-6688-4034-a910-4f6ecdea2c20
  IwConfig:
   enp0s25   no wireless extensions.
   
   lono wireless extensions.
   
   enx8a549328aae7  no wireless extensions.
  MachineType: LENOVO 253725M
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=e5bcc2d8-520b-4648-9a08-0cc1d65152fd ro BOOTIF=01-f0-de-f1-49-05-1b 
quiet splash crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET75WW (1.35 )
  dmi.board.name: 253725M
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET75WW(1.35):bd02/01/2011:svnLENOVO:pn253725M:pvrThinkPadT410:rvnLENOVO:rn253725M:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 253725M
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1538406] Re: REGRESSION ThinkPad T410 fails to see AHCI device on boot with wily SRU kernels

2016-01-26 Thread Stefano Rivera
> The AHCI adaptor (:00:1f.5) simply isn't visible in
/sys/bus/pci/devices/

hrm, it seems that was wrong. The adaptor is 1f.2 and is now visible
(although I swear it wasn't, earlier). But ahci didn't bind to it.

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

Title:
  REGRESSION ThinkPad T410 fails to see AHCI device on boot with wily
  SRU kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We have a set of ThinkPads (T410 and T540p) that are failing to boot
  (not locating their root fs device) with post-release kernels.

  The AHCI adaptor (:00:1f.5) simply isn't visible in
  /sys/bus/pci/devices/

  The problem is apparent in 4.2.0.25-30, and not in 4.2.0-16.19

  If the SATA device mode is changed from AHCI to IDE emulation, then
  they reliably boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-16-generic 4.2.0-16.19
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Jan 27 16:41:50 2016
  HibernationDevice: RESUME=UUID=185cef3a-6688-4034-a910-4f6ecdea2c20
  IwConfig:
   enp0s25   no wireless extensions.
   
   lono wireless extensions.
   
   enx8a549328aae7  no wireless extensions.
  MachineType: LENOVO 253725M
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=e5bcc2d8-520b-4648-9a08-0cc1d65152fd ro BOOTIF=01-f0-de-f1-49-05-1b 
quiet splash crashkernel=384M-:128M
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/01/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET75WW (1.35 )
  dmi.board.name: 253725M
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET75WW(1.35):bd02/01/2011:svnLENOVO:pn253725M:pvrThinkPadT410:rvnLENOVO:rn253725M:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 253725M
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1370041] Re: CVE-2014-3631

2016-01-26 Thread Steve Beattie
** No longer affects: linux-lts-trusty (Ubuntu Utopic)

** No longer affects: linux-armadaxp (Ubuntu Utopic)

** No longer affects: linux-ec2 (Ubuntu Utopic)

** No longer affects: linux-goldfish (Ubuntu Utopic)

** No longer affects: linux-lts-saucy (Ubuntu Utopic)

** No longer affects: linux-lts-quantal (Ubuntu Utopic)

** No longer affects: linux-raspi2 (Ubuntu Utopic)

** No longer affects: linux-mvl-dove (Ubuntu Utopic)

** No longer affects: linux-ti-omap4 (Ubuntu Utopic)

** No longer affects: linux-lts-vivid (Ubuntu Utopic)

** No longer affects: linux (Ubuntu Utopic)

** No longer affects: linux-mako (Ubuntu Utopic)

** No longer affects: linux-fsl-imx51 (Ubuntu Utopic)

** No longer affects: linux-lts-utopic (Ubuntu Utopic)

** No longer affects: linux-flo (Ubuntu Utopic)

** No longer affects: linux-lts-raring (Ubuntu Utopic)

** No longer affects: linux-manta (Ubuntu Utopic)

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided => Medium

** Changed in: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Importance: Undecided => Medium

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

Title:
  CVE-2014-3631

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

[Kernel-packages] [Bug 1370040] Re: CVE-2014-3535

2016-01-26 Thread Steve Beattie
** No longer affects: linux-lts-trusty (Ubuntu Utopic)

** No longer affects: linux-armadaxp (Ubuntu Utopic)

** No longer affects: linux-ec2 (Ubuntu Utopic)

** No longer affects: linux-goldfish (Ubuntu Utopic)

** No longer affects: linux-lts-saucy (Ubuntu Utopic)

** No longer affects: linux-lts-quantal (Ubuntu Utopic)

** No longer affects: linux-raspi2 (Ubuntu Utopic)

** No longer affects: linux-mvl-dove (Ubuntu Utopic)

** No longer affects: linux-ti-omap4 (Ubuntu Utopic)

** No longer affects: linux-lts-vivid (Ubuntu Utopic)

** No longer affects: linux (Ubuntu Utopic)

** No longer affects: linux-mako (Ubuntu Utopic)

** No longer affects: linux-fsl-imx51 (Ubuntu Utopic)

** No longer affects: linux-lts-utopic (Ubuntu Utopic)

** No longer affects: linux-flo (Ubuntu Utopic)

** No longer affects: linux-lts-raring (Ubuntu Utopic)

** No longer affects: linux-manta (Ubuntu Utopic)

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided => Medium

** Changed in: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Importance: Undecided => Medium

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

Title:
  CVE-2014-3535

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

[Kernel-packages] [Bug 1432799] Re: CVE-2011-5321

2016-01-26 Thread Steve Beattie
** No longer affects: linux-lts-trusty (Ubuntu Utopic)

** No longer affects: linux-armadaxp (Ubuntu Utopic)

** No longer affects: linux-ec2 (Ubuntu Utopic)

** No longer affects: linux-goldfish (Ubuntu Utopic)

** No longer affects: linux-lts-saucy (Ubuntu Utopic)

** No longer affects: linux-lts-quantal (Ubuntu Utopic)

** No longer affects: linux-raspi2 (Ubuntu Utopic)

** No longer affects: linux-mvl-dove (Ubuntu Utopic)

** No longer affects: linux-ti-omap4 (Ubuntu Utopic)

** No longer affects: linux-lts-vivid (Ubuntu Utopic)

** No longer affects: linux (Ubuntu Utopic)

** No longer affects: linux-mako (Ubuntu Utopic)

** No longer affects: linux-fsl-imx51 (Ubuntu Utopic)

** No longer affects: linux-lts-utopic (Ubuntu Utopic)

** No longer affects: linux-flo (Ubuntu Utopic)

** No longer affects: linux-lts-raring (Ubuntu Utopic)

** No longer affects: linux-manta (Ubuntu Utopic)

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided => Medium

** Changed in: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-raspi2 (Ubuntu Trusty)
   Importance: Undecided => Medium

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

Title:
  CVE-2011-5321

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

[Kernel-packages] [Bug 1370021] Re: CVE-2014-0205

2016-01-26 Thread Steve Beattie
** No longer affects: linux-lts-trusty (Ubuntu Utopic)

** No longer affects: linux-armadaxp (Ubuntu Utopic)

** No longer affects: linux-ec2 (Ubuntu Utopic)

** No longer affects: linux-goldfish (Ubuntu Utopic)

** No longer affects: linux-lts-saucy (Ubuntu Utopic)

** No longer affects: linux-lts-quantal (Ubuntu Utopic)

** No longer affects: linux-raspi2 (Ubuntu Utopic)

** No longer affects: linux-mvl-dove (Ubuntu Utopic)

** No longer affects: linux-ti-omap4 (Ubuntu Utopic)

** No longer affects: linux-lts-vivid (Ubuntu Utopic)

** No longer affects: linux (Ubuntu Utopic)

** No longer affects: linux-mako (Ubuntu Utopic)

** No longer affects: linux-fsl-imx51 (Ubuntu Utopic)

** No longer affects: linux-lts-utopic (Ubuntu Utopic)

** No longer affects: linux-flo (Ubuntu Utopic)

** No longer affects: linux-lts-raring (Ubuntu Utopic)

** No longer affects: linux-manta (Ubuntu Utopic)

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

** Changed in: linux-raspi2 (Ubuntu Precise)
   Importance: Undecided => High

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

** Changed in: linux-raspi2 (Ubuntu Vivid)
   Importance: Undecided => High

** Changed in: linux-raspi2 (Ubuntu Wily)
   Importance: Undecided => High

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

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

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

Title:
  CVE-2014-0205

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

[Kernel-packages] [Bug 869250] Re: CVE-2011-2525

2016-01-26 Thread Steve Beattie
** Also affects: linux (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-oneiric (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-fsl-imx51 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mvl-dove (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ec2 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-maverick (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-natty (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-oneiric (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-manta (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-flo (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-trusty (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

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

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

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

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

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

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Importance: Undecided => Medium

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

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

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

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-lts-raring (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-armadaxp (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-goldfish (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-mvl-dove (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: 

[Kernel-packages] [Bug 917835] Re: CVE-2011-4325

2016-01-26 Thread Steve Beattie
** Also affects: linux (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

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

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

** Also affects: linux-lts-backport-maverick (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-natty (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: linux-lts-backport-oneiric (Ubuntu Wily)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-fsl-imx51 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mvl-dove (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ec2 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-ti-omap4 (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-maverick (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-natty (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-backport-oneiric (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-armadaxp (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-quantal (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-raring (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-saucy (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-mako (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-manta (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-goldfish (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-flo (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-trusty (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

** Also affects: linux-lts-utopic (Ubuntu Xenial)
   Importance: Medium
   Status: Invalid

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

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

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

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

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

** Changed in: linux-lts-quantal (Ubuntu Wily)
   Importance: Undecided => Medium

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

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

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

** Changed in: linux-ti-omap4 (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-lts-raring (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-armadaxp (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-goldfish (Ubuntu Wily)
   Importance: Undecided => Medium

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

** Changed in: linux-mvl-dove (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: 

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

2016-01-26 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

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

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

Bug description:
  This bug is for tracking the 3.19.0-49.55~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:Friday, 22. January 2016 10:41 UTC
  kernel-stable-master-bug:1536775
  kernel-stable-Prepare-package-end:Friday, 22. January 2016 22:57 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 22. January 2016 22:57 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 25. January 2016 20:47 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 25. January 2016 22:01 UTC
  kernel-stable-Verification-testing-start:Monday, 25. January 2016 22:01 UTC
  kernel-stable-Certification-testing-start:Monday, 25. January 2016 22:01 UTC
  kernel-stable-Security-signoff-start:Monday, 25. January 2016 22:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 25. January 2016 22:01 UTC

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

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


[Kernel-packages] [Bug 1470250] Re: [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based Backups

2016-01-26 Thread Frederik Bosch
Thanks @lauwersm and @decui. Our comments seem to have no effect at all.
Yesterday was a read-only day again. Just two weeks after the previous
one. So now it happens two times a month, which is 2 out of 8 backups.
This is just too often, too expensive in labour and really unworkable.

Also, the write latency is extraordinary. Yesterday some data import was
busy (over the network) when the backup started. Took more than 3 hours
to complete. After backup was finished, I started the import again, just
to see the difference. Took just 45 minutes. I would be more than happy
to show an engineer our problem.

Maybe someone knows how to soft reboot a machine when in read-only
state? This could help reducing the pain. But I really really want to
urge getting a final solution. The problem was issued at April 30. My
report at the Microsoft forum was at May 8, and that was after 40 days
of problems already. So this bugging us for almost 10 months.

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

Title:
  [Hyper-V] Ubuntu 14.04.2 LTS Generation 2 SCSI Errors on VSS Based
  Backups

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

Bug description:
  Customers have reported running various versions of Ubuntu 14.04.2 LTS
  on Generation 2 Hyper-V Hosts.On a random Basis, the file system
  will be mounted Read-Only due to a "disk error" (which really isn't
  the case here).As a result, they must reboot the Ubuntu guest to
  get the file system to mount RW again.

  The Error seen are the following:
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968142] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968145] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 00:02:01 balticnetworkstraining kernel: [640153.968161] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed. The Linux SCSI layer does not automatically adjust these 
parameters.
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584164] hv_storvsc 
vmbus_0_4: cmd 0x2a scsi status 0x2 srb status 0x82
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584178] hv_storvsc 
vmbus_0_4: stor pkt 88006eb6c700 autosense data valid - len 18
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584180] storvsc: Sense 
Key : Unit Attention [current] 
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584183] storvsc: Add. 
Sense: Changed operating definition
  Apr 30 01:23:26 balticnetworkstraining kernel: [645039.584198] sd 0:0:0:0: 
Warning! Received an indication that the operating parameters on this target 
have changed.  The Linux SCSI layer does not automatically adjust these 
parameters.

  This relates to the VSS "Windows Server Backup" process that kicks off at 
midnight on the host and finishes an hour and half later.   
  Yes, we do have hv_vss_daemon and hv_kvp_daemon running for the correct 
kernel version we have.   We're currently running kernel version 
3.13.0-49-generic #83 on one system and 3.16.0-34-generic #37 on the other. -- 
We see the same errors on both.
  As a result, we've been hesitant to drop any more ubuntu guests on our 2012R2 
hyper-v system because of this.   We can stop the backup process and all is 
good, but we need nightly backups to image all of our VM's.   All the windows 
guests have no issues of course.   We also have some CentOS based guests 
running without issues from what we've seen.

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

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


[Kernel-packages] [Bug 1535879] Re: It looks to be the (expired ) bug #1451632 drm:intel fifo

2016-01-26 Thread Christopher M. Penalver
carlos palma, thank you for reporting this and helping make Ubuntu
better.

As per http://www.dell.com/support/home/us/en/19/product-
support/product/latitude-e6530/drivers/advanced an update to your
computer's buggy and outdated BIOS is available (A17). If you update to
this following https://help.ubuntu.com/community/BIOSUpdate does it
change anything?

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

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

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

Thank you for your understanding.

** Tags added: bios-outdated-a17

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

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

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

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

Title:
  It looks to be the (expired ) bug #1451632 drm:intel fifo

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1451632/+activity
  dmesg | grep drm:intel

  [1.441536] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [1.441575] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  Returned back (https://bugzilla.kernel.org/show_bug.cgi?id=79261). It
  seamed to be fixed up-stream but not for all.

  Effects on my DELL Precision E6530: without notice it switches from
  nouveau to nvidia. Switching back to nouveau it hangs (need restart)
  and OK.

  Using optimus: 
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  01:00.0 VGA compatible controller: NVIDIA Corporation GF108GLM [NVS 5200M] 
(rev ff)

  I'll try to use the upstream kernels and inform ...

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Jan 19 20:32:03 2016
  DistUpgraded: 2015-10-12 20:30:48,655 DEBUG enabling apt cron job
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0535]
   NVIDIA Corporation GF108GLM [NVS 5200M] [10de:0dfc] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-05-19 (610 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Latitude E6530
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to wily on 2015-10-12 (99 days ago)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  

[Kernel-packages] [Bug 1536810] Re: kernel install failed /bin/cp: cannot stat ‘/boot/initrd.img-4.3.0-7-generic’: No such file or directory

2016-01-26 Thread Andy Whitcroft
@smoser -- the header in your files implies that the kernel at least
created the configuration in the first instance:

print CONF "# Kernel Image management overrides\n";
print CONF "# See kernel-img.conf(5) for details\n";

Though it only appears to write two combinations:

  if (open(CONF, ">$CONF_LOC")) {
print CONF "# Kernel Image management overrides\n";
print CONF "# See kernel-img.conf(5) for details\n";
if ($loader =~ /palo/i) {
  print CONF "link_in_boot = Yes\n";
  print CONF "do_symlinks = Yes\n";
  print CONF "relative_links = Yes\n";
  print CONF "do_bootloader = No\n";
} else {
  print CONF "do_symlinks = $do_symlink\n";
}
close CONF;
  }

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

Title:
  kernel install failed /bin/cp: cannot stat
  ‘/boot/initrd.img-4.3.0-7-generic’: No such file or directory

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi, this failure for kernel package installation occured inside a maas image 
(lp:maas-images) build process.
  The failure log ends like this:

  Unpacking linux-generic (4.3.0.7.8) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up linux-image-4.3.0-7-generic (4.3.0-7.18) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  /bin/cp: cannot stat '/boot/initrd.img-4.3.0-7-generic': No such file or 
directory
  Failed to copy /boot/initrd.img-4.3.0-7-generic to /boot/initrd.img at 
/var/lib/dpkg/info/linux-image-4.3.0-7-generic.postinst line 745.
  dpkg: error processing package linux-image-4.3.0-7-generic (--configure):
   subprocess installed post-installation script returned error exit status 2
  Setting up devio (1.2-1build2) ...
  Setting up linux-base (4.0ubuntu1) ...
  Setting up flash-kernel (3.0~rc.4ubuntu57) ...
  Setting up linux-firmware (1.155) ...
  dpkg: dependency problems prevent configuration of linux-image-generic:
   linux-image-generic depends on linux-image-4.3.0-7-generic; however:
Package linux-image-4.3.0-7-generic is not configured yet.

  dpkg: error processing package linux-image-generic (--configure):
   dependency problems - leaving unconfigured
  Setting up linux-headers-4.3.0-7 (4.3.0-7.18) ...
  Setting up linux-headers-4.3.0-7-generic (4.3.0-7.18) ...
  Setting up linux-headers-generic (4.3.0.7.8) ...
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-image-generic (= 4.3.0.7.8); however:
Package linux-image-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.
  No apport report written because the error message indicates its a followup 
error from a previous failure.
  Errors were encountered while processing:
   linux-image-4.3.0-7-generic
   linux-image-generic
   linux-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  failed install of  linux-generic
  failed chroot and kernel install
  failed
  failed to get linux-generic output

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

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


[Kernel-packages] [Bug 1536841] Re: xenial can't access network printer 14.04.3 no problem

2016-01-26 Thread jerrylamos
Info from 14.04 LTS same hardware, same network, just different partition:
Network prints fine.  Quick.  No authentication problems etc.

cat /media/jerry/9110d642-ba35-4dfd-b42a-ceec94cbf7e3/etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.3 LTS"

ls /boot shows 
vmlinuz-3.13.0-76-generic

Would that kernel install and on work on xenial?  I'm currently at:
vmlinuz-4.4.0-040400-generic

Network pc printer is off at the moment and did get a proper response from 
xenial, 
processing pending   1/0 

Thanks for looking at this.

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

Title:
  xenial can't access network printer 14.04.3 no problem

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  There was an error during the CUPS operation: 'client-error-not-
  possible'.

  14.04.3 on another partition accesses network printer on XP just fine.

  With identical smb.conf xenial cannot access the printer.

  Xenial can access XP jpg images etc. so network connection to XP
  working fine.

  See attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.3.0-6-generic 4.3.0-6.17
  ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
  Uname: Linux 4.3.0-6-generic x86_64
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  Date: Thu Jan 21 18:41:32 2016
  InstallationDate: Installed on 2015-12-26 (26 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-6-generic 
root=UUID=c8c33dea-5f04-4670-84f3-daf1d956e6b8 ro quiet splash vt.handoff=7
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5CKT69AUS
  dmi.board.name: LENOVO
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
  dmi.product.name: 6234A1U
  dmi.product.version: ThinkCentre M58p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1536904] Re: Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

2016-01-26 Thread Louis Bouchard
Hello,

Sorry for the delay in replying.

This is definitively a regression following the implementation of
smaller initrd. I am currently working at fixing this. Your second
problem might be caused by not using smaller initrd so I would suggest
to wait to test the fix for this.

I can have a test package available quickly if you have the possibility
of testing from a PPA (according to a previous bug I think you do) so
let me know & I'll tell you where to find the PPA.

** Changed in: makedumpfile (Ubuntu)
   Status: Invalid => In Progress

** Changed in: makedumpfile (Ubuntu)
   Importance: Undecided => High

** Changed in: makedumpfile (Ubuntu)
 Assignee: Taco Screen team (taco-screen-team) => Louis Bouchard 
(louis-bouchard)

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

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

** Changed in: makedumpfile (Ubuntu Wily)
   Importance: Undecided => High

** Changed in: makedumpfile (Ubuntu Wily)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

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

Title:
  Kdump fails on Ubuntu 16.04 (PowerVM/PowerKVM/BareMetal)

Status in makedumpfile package in Ubuntu:
  In Progress
Status in makedumpfile source package in Wily:
  Confirmed

Bug description:
  == Comment: #0 - ==
  ---Problem Description---
  Kdump fails on Ubuntu 16.04 with Austin adapter(tg3)
   
  Contact Information = hathy...@in.ibm.com, 
iranna.an...@in.ibm.com,mputt...@in.ibm.com 
   
  ---uname output---
  linux ltciofvtr-s822l1 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:32:23 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Machine details:
  9.47.67.156 (root/ltcnetdd) 

   
  Machine Type = 8247-22L 
   
  ---System Hang---
   The system hangs after triggering a crash. Need to reboot to bring it up and 
functional. 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Steps to follow:
  1. apt-get install linux-crashdump
  2. apt-get install kdump-tools
  3. Edit /etc/default/kdump-tools and change the following:
  USE_KDUMP=0 to 1
  4. Change the size of the crash kernel in /boot/grub/grub.cfg to 
crashkernel=4096M-:4096M
  5. Load the kdump config file: kdump-config load
  6. echo 1 > /proc/sys/kernel/sysrq
  7. echo c > /proc/sysrq-trigger

  
  Things to look at to cross-check are:

  After loading the kdump-config file, check for it's status
  root@ltciofvtr-s822l1:~# kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 
  SSH:  root@35.35.35.36
  SSH_KEY:  /root/.ssh/id_rsa
  HOSTTAG:  ip
  current state:ready to kdump

  kexec command:
/sbin/kexec -p --args-linux 
--command-line="root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/boot/initrd.img-4.3.0-5-generic /boot/vmlinux-4.3.0-5-generic


  root@ltciofvtr-s822l1:~# kdump-config status
   * Broken symlink : /var/lib/kdump/vmlinuz: broken symbolic link to 
/boot/vmlinuz-4.3.0-5-generic
  current state   : ready to kdump


  root@ltciofvtr-s822l1:~# cat /proc/cmdline 
  root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M


  root@ltciofvtr-s822l1:~# dmesg| grep -i crash
  [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System 
RAM: 131072MB)
  [0.00] Kernel command line: 
root=UUID=e445a093-4593-4e91-bebb-6968483bf2ea ro quiet splash 
crashkernel=4096M-:4096M

  
  Observations:
  1. Kdump-config status command reports that there is a broken symbloic link 
suggesting that kdump-config file is unable to handle the symbolic link. 

  2. Trace observed on console:
  root@ltciofvtr-s822l1:~# echo c | tee /proc/sysrq-trigger 
  c
  [  238.872102] sysrq: SysRq : Trigger a crash
  [  238.872179] Unable to handle kernel paging request for data at address 
0x
  [  238.872256] Faulting instruction address: 0xc0646534
  [  238.872322] Oops: Kernel access of bad area, sig: 11 [#1]
  [  238.872373] SMP NR_CPUS=2048 NUMA PowerNV
  [  238.872427] Modules linked in: dm_round_robin dm_service_time ipmi_powernv 
ipmi_msghandler leds_powernv uio_pdrv_genirq powernv_rng uio dm_multipath 
sunrpc bonding autofs4 btrfs xor raid6_pq mlx4_en ses enclosure bnx2x mlx4_core 
lpfc qla2xxx mdio libcrc32c be2net e1000e vxlan ipr ip6_udp_tunnel udp_tunnel 
scsi_transport_fc
  [  238.872895] CPU: 121 PID: 3861 Comm: tee Not tainted 4.3.0-5-generic 
#16-Ubuntu
  [  238.872973] task: c00fe01ce860 ti: c00fe022c000 task.ti: 
c00fe022c000
  [  238.873049] NIP: c0646534 LR: c06475f8 CTR: 
c0646500
  [  238.873125] REGS: 

[Kernel-packages] [Bug 1291459] Re: ioctl FE_GET_INFO hangs with DViCO FusionHDTV DVB-T Dual Digital 4 card

2016-01-26 Thread psalter
Thanks to the details above I was able to get my Dvico Fusion Dual Digital 4 
working on Mythbuntu Trusty 14.04.3  . The problem was solved at kernel 3.19. 
Problem is related to cxusb.c where the #define MAX_XFER_SIZE 80 was changed 
from 64 to 80. Details of change are at LinuxTV.org:
https://git.linuxtv.org/media_tree.git/commit/?id=eb9da073bd002f2968c84129a5c49625911a3199


diff --git a/drivers/media/usb/dvb-usb/cxusb.c 
b/drivers/media/usb/dvb-usb/cxusb.c
index b7461ac..f379f7e 100644
--- a/drivers/media/usb/dvb-usb/cxusb.c
+++ b/drivers/media/usb/dvb-usb/cxusb.c
@@ -46,7 +46,7 @@
 #include "si2157.h"
 
 /* Max transfer size done by I2C transfer functions */
-#define MAX_XFER_SIZE  64
+#define MAX_XFER_SIZE  80
 
 /* debug */
 static int dvb_usb_cxusb_debug;

I looked through the ubuntu kernels for the updated cxusb.c and found it looked 
ok after 3.19.0   .
To fix my Mythbuntu Trusty I loaded linux-headers-3.19.0-47  and it all worked.

I wanted to update comments here so that anyone else doing searches for
the problem might find a quick answer as there are not very many search
results relating to Dvico card and later kernel.

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

Title:
  ioctl FE_GET_INFO hangs with DViCO FusionHDTV DVB-T Dual Digital 4
  card

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Top level symptom:
  mythtv-backend fails to listen for client connections.
  It stops at: (strace mythbackend)
  open("/dev/dvb/adapter1/frontend0", O_RDWR|O_NONBLOCK) = 16
  ioctl(16, FE_GET_INFO

  me-tv also hangs in a similar manner.

  I expected the ioctl call to succeed, and for the top level
  applications to function properly. Instead, they hang.

  The machine has 3 dvb tuners as follows:
   Adapter 0
  Mar 12 22:32:53 mythtv kernel: [   17.428195] input: Budget-CI dvb ir 
receiver saa7146 (0) as /devices/pci:00/:00:1e.0/:05
  :00.0/rc/rc0/input13
  Mar 12 22:32:53 mythtv kernel: [   17.428251] rc0: Budget-CI dvb ir receiver 
saa7146 (0) as /devices/pci:00/:00:1e.0/:05:0
  0.0/rc/rc0
  Mar 12 22:32:53 mythtv kernel: [   17.432801] budget_ci dvb :05:00.0: 
DVB: registering adapter 0 frontend 0 (Philips TDA10045H DVB
  -T)...
   Adapter 1
  Mar 12 22:32:53 mythtv kernel: [   17.646727] DVB: registering new adapter 
(DViCO FusionHDTV DVB-T Dual Digital 4)
  Mar 12 22:32:53 mythtv kernel: [   17.797366] usb 3-1: DVB: registering 
adapter 1 frontend 0 (Zarlink ZL10353 DVB-T)...
   Adapter 2
  Mar 12 22:32:53 mythtv kernel: [   17.831769] DVB: registering new adapter 
(DViCO FusionHDTV DVB-T Dual Digital 4)
  Mar 12 22:32:53 mythtv kernel: [   17.882250] cxusb: No IR receiver detected 
on this device.
  Mar 12 22:32:53 mythtv kernel: [   17.882258] usb 3-2: DVB: registering 
adapter 2 frontend 0 (Zarlink ZL10353 DVB-T)...

  There appears to be a problem loading the firmware for the xc2028 in
  the DViCO FusionHDTV card:

  Mar 13 02:07:59 mythtv kernel: [   37.348226] xc2028 10-0061: Loading 
firmware for type=BASE F8MHZ (3), id .
  Mar 13 02:07:59 mythtv kernel: [   37.360226] cxusb: i2c wr: len=64 is too 
big!
  Mar 13 02:07:59 mythtv kernel: [   37.360226] 
  Mar 13 02:07:59 mythtv kernel: [   37.360230] xc2028 10-0061: i2c output 
error: rc = -95 (should be 64)
  Mar 13 02:07:59 mythtv kernel: [   37.360231] xc2028 10-0061: -95 returned 
from send
  Mar 13 02:07:59 mythtv kernel: [   37.360234] xc2028 10-0061: Error -22 while 
loading base firmware
  Mar 13 02:07:59 mythtv kernel: [   37.412233] xc2028 11-0061: Loading 
firmware for type=BASE F8MHZ (3), id .
  Mar 13 02:07:59 mythtv kernel: [   37.424360] cxusb: i2c wr: len=64 is too 
big!
  Mar 13 02:07:59 mythtv kernel: [   37.424360] 
  Mar 13 02:07:59 mythtv kernel: [   37.424364] xc2028 11-0061: i2c output 
error: rc = -95 (should be 64)
  Mar 13 02:07:59 mythtv kernel: [   37.424365] xc2028 11-0061: -95 returned 
from send
  Mar 13 02:07:59 mythtv kernel: [   37.424368] xc2028 11-0061: Error -22 while 
loading base firmware
  Mar 13 02:07:59 mythtv kernel: [   37.428486] xc2028 10-0061: Loading 
firmware for type=BASE F8MHZ (3), id .
  Mar 13 02:07:59 mythtv kernel: [   37.492247] xc2028 11-0061: Loading 
firmware for type=BASE F8MHZ (3), id .

  The firmware is loaded from the file xc3028-v27.fw:
  Mar 13 02:07:42 mythtv kernel: [   18.108746] xc2028 11-0061: creating new 
instance
  Mar 13 02:07:42 mythtv kernel: [   18.108748] xc2028 11-0061: type set to 
XCeive xc2028/xc3028 tuner
  Mar 13 02:07:42 mythtv kernel: [   18.108801] xc2028 11-0061: Loading 80 
firmware images from xc3028-v27.fw, type: xc2028 firmware, ver 2.7
  Mar 13 02:07:42 mythtv kernel: [   18.109670] dvb-usb: DViCO FusionHDTV 

[Kernel-packages] [Bug 1520519] Re: ASUS ROG GL552 TouchPad not detected

2016-01-26 Thread Michael Smith
I'm still having the problem over here, too. ;)

Any luck on using another 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/1520519

Title:
  ASUS ROG GL552 TouchPad not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop Model  : ASUS ROG GL552 DH71
  First Appearance : Got laptop yesterday. dual booted with ubuntu 14.04. 
Touchpad never detected.
  Manufacturer : ASUS ( as listed under windows 10 )

  * xinput list *

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=10   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Power Buttonid=7[slave  
keyboard (3)]
  ↳ Logitech USB Keyboard   id=8[slave  
keyboard (3)]
  ↳ Logitech USB Keyboard   id=9[slave  
keyboard (3)]

  * List of devices *
  : Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=046d Product=c05a Version=0111
  N: Name="Logitech USB Optical Mouse"
  P: Phys=usb-:00:14.0-1/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C05A.0001/input/input4
  U: Uniq=
  H: Handlers=mouse0 event4 
  B: PROP=0
  B: EV=17
  B: KEY=7 0 0 0 0
  B: REL=103
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Asus WMI hotkeys"
  P: Phys=asus-nb-wmi/input0
  S: Sysfs=/devices/platform/asus-nb-wmi/input/input5
  U: Uniq=
  H: Handlers=rfkill kbd event5 
  B: PROP=0
  B: EV=100013
  B: KEY=8 0 8000 0 0 a1606f0090 8200027800501000 e 0
  B: MSC=10

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
  U: Uniq=
  H: Handlers=kbd event6 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input7
  U: Uniq=
  H: Handlers=kbd event7 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=04f2 Product=b424 Version=6969
  N: Name="USB2.0 HD UVC WebCam"
  P: Phys=usb-:00:14.0-4/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input8
  U: Uniq=
  H: Handlers=kbd event8 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9
  U: Uniq=
  H: Handlers=event9 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10
  U: Uniq=
  H: Handlers=event10 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11
  U: Uniq=
  H: Handlers=event11 
  B: PROP=0
  B: EV=21
  B: SW=140

  
  please find Xorg.log attached.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sameer 1813 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=94ecb362-a267-4f7c-834b-a06feb4f2361
  InstallationDate: 

[Kernel-packages] [Bug 1538148] [NEW] man kdump-config is missing the propagate option

2016-01-26 Thread Louis Bouchard
Public bug reported:

Need to fix the manpage

** Affects: kexec-tools (Ubuntu)
 Importance: Medium
 Assignee: Louis Bouchard (louis-bouchard)
 Status: Confirmed

** Affects: kexec-tools (Ubuntu Wily)
 Importance: Medium
 Assignee: Louis Bouchard (louis-bouchard)
 Status: Confirmed

** Changed in: kexec-tools (Ubuntu)
   Status: New => Confirmed

** Changed in: kexec-tools (Ubuntu)
   Importance: Undecided => Critical

** Changed in: kexec-tools (Ubuntu)
   Importance: Critical => Medium

** Changed in: kexec-tools (Ubuntu)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

** Also affects: kexec-tools (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Changed in: kexec-tools (Ubuntu Wily)
   Importance: Undecided => Medium

** Changed in: kexec-tools (Ubuntu Wily)
   Status: New => Confirmed

** Changed in: kexec-tools (Ubuntu Wily)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

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

Title:
  man kdump-config is missing the propagate option

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Wily:
  Confirmed

Bug description:
  Need to fix the manpage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1538148/+subscriptions

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


[Kernel-packages] [Bug 1520519] Re: ASUS ROG GL552 TouchPad not detected

2016-01-26 Thread sameer
Yes, the new kernel  boots fine with the following kernel parameters
"acpi_osi=! idle=nomwait"

you can simple add these to /etc/default/grub.conf and run "update-
grub2"

And yes, the touchpad works great !!

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

Title:
  ASUS ROG GL552 TouchPad not detected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Laptop Model  : ASUS ROG GL552 DH71
  First Appearance : Got laptop yesterday. dual booted with ubuntu 14.04. 
Touchpad never detected.
  Manufacturer : ASUS ( as listed under windows 10 )

  * xinput list *

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=10   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Power Buttonid=7[slave  
keyboard (3)]
  ↳ Logitech USB Keyboard   id=8[slave  
keyboard (3)]
  ↳ Logitech USB Keyboard   id=9[slave  
keyboard (3)]

  * List of devices *
  : Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=046d Product=c05a Version=0111
  N: Name="Logitech USB Optical Mouse"
  P: Phys=usb-:00:14.0-1/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C05A.0001/input/input4
  U: Uniq=
  H: Handlers=mouse0 event4 
  B: PROP=0
  B: EV=17
  B: KEY=7 0 0 0 0
  B: REL=103
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Asus WMI hotkeys"
  P: Phys=asus-nb-wmi/input0
  S: Sysfs=/devices/platform/asus-nb-wmi/input/input5
  U: Uniq=
  H: Handlers=rfkill kbd event5 
  B: PROP=0
  B: EV=100013
  B: KEY=8 0 8000 0 0 a1606f0090 8200027800501000 e 0
  B: MSC=10

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
  U: Uniq=
  H: Handlers=kbd event6 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input7
  U: Uniq=
  H: Handlers=kbd event7 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=04f2 Product=b424 Version=6969
  N: Name="USB2.0 HD UVC WebCam"
  P: Phys=usb-:00:14.0-4/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input8
  U: Uniq=
  H: Handlers=kbd event8 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9
  U: Uniq=
  H: Handlers=event9 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10
  U: Uniq=
  H: Handlers=event10 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11
  U: Uniq=
  H: Handlers=event11 
  B: PROP=0
  B: EV=21
  B: SW=140

  
  please find Xorg.log attached.
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sameer 1813 F pulseaudio

[Kernel-packages] [Bug 1531768] Re: arm64 kernel and multiple CPUs is unusably slow

2016-01-26 Thread Martin Pitt
lxd-armhf1 (8 CPUs) is again in a state where "lxc list" and even "top"
hang forever. lxd-armhf2 was unfortunately shutdown in the previous
days, so I just booted it again.

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

Title:
  arm64 kernel and multiple CPUs is unusably slow

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I
  want to use for armhf autopkgtesting in LXD). I started with wily as
  that has lxd available (it's not yet available in trusty nor the PPA
  for arm64).

  However, pretty much any LXD task that I do (I haven't tried much
  else) on this machine takes unbearably long. A simple "lxc profile set
  default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes.

  I see tons of

  [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0
  [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds.

  in dmesg (the attached apport info has the complete dmesg).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic 4.2.0-22.27
  ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  7 09:18 seq
   crw-rw 1 root audio 116, 33 Jan  7 09:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Thu Jan  7 09:24:01 2016
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.

   lxcbr0no wireless extensions.
  Lspci:
   00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008]
    Subsystem: Red Hat, Inc Device [1af4:1100]
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=LABEL=cloudimg-rootfs earlyprintk
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   linux-backports-modules-4.2.0-22-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1530745] Re: the touchpad is not detected in Ubuntu 14.04.3 . The laptop is ASUS ROG GL552

2016-01-26 Thread Christopher M. Penalver
Guido Granda Muñoz, in order to allow additional upstream developers to examine 
the issue, at your earliest convenience, could you please test the latest 
upstream kernel available from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind 
the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

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

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

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

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

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

Thank you for your understanding.

** This bug is no longer a duplicate of bug 1520519
   ASUS ROG GL552 TouchPad not detected

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

Title:
  the touchpad is not detected in Ubuntu 14.04.3 . The laptop is ASUS
  ROG GL552

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The touchpad is not detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-42-generic 3.19.0-42.48~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-42.48~14.04.1-generic 3.19.8-ckt10
  Uname: Linux 3.19.0-42-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan  3 21:27:06 2016
  InstallationDate: Installed on 2016-01-03 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  guido  1971 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=9b30e230-c384-439e-826e-d9dc68ec6438
  InstallationDate: Installed on 2016-01-03 (6 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0458:003a KYE Systems Corp. (Mouse Systems) 
NetScroll+ Mini Traveler / Genius NetScroll 120
   Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL552VW
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-43-generic.efi.signed 
root=UUID=c12cd212-5dd4-41ab-8c1c-72e851dafc56 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-43.49~14.04.1-generic 3.19.8-ckt10
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-43-generic N/A
   linux-backports-modules-3.19.0-43-generic  N/A
   linux-firmware 1.127.19
  Tags:  trusty
  Uname: Linux 3.19.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL552VW.210
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL552VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  

[Kernel-packages] [Bug 1520519] Re: ASUS ROG GL552 TouchPad not detected

2016-01-26 Thread Christopher M. Penalver
sameer, the next step is to fully reverse commit bisect from kernel 3.19
to 4.5-rc1 in order to identify the last bad commit, followed
immediately by the first good one. Once this good commit has been
identified, it may be reviewed for backporting. 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.

After the fix commit (not kernel version) has been identified, then
please mark this report Status Confirmed.

Thank you for your understanding.

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

** Tags removed: needs-upstream-testing
** Tags added: kernel-fixed-upstream kernel-fixed-upstream-4.5-rc1 
needs-reverse-bisect

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

Title:
  ASUS ROG GL552 TouchPad not detected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Laptop Model  : ASUS ROG GL552 DH71
  First Appearance : Got laptop yesterday. dual booted with ubuntu 14.04. 
Touchpad never detected.
  Manufacturer : ASUS ( as listed under windows 10 )

  * xinput list *

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech USB Optical Mouse  id=10   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Power Buttonid=7[slave  
keyboard (3)]
  ↳ Logitech USB Keyboard   id=8[slave  
keyboard (3)]
  ↳ Logitech USB Keyboard   id=9[slave  
keyboard (3)]

  * List of devices *
  : Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
  U: Uniq=
  H: Handlers=event0 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1
  U: Uniq=
  H: Handlers=kbd event1 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input3
  U: Uniq=
  H: Handlers=sysrq kbd event3 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=046d Product=c05a Version=0111
  N: Name="Logitech USB Optical Mouse"
  P: Phys=usb-:00:14.0-1/input0
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:046D:C05A.0001/input/input4
  U: Uniq=
  H: Handlers=mouse0 event4 
  B: PROP=0
  B: EV=17
  B: KEY=7 0 0 0 0
  B: REL=103
  B: MSC=10

  I: Bus=0019 Vendor= Product= Version=
  N: Name="Asus WMI hotkeys"
  P: Phys=asus-nb-wmi/input0
  S: Sysfs=/devices/platform/asus-nb-wmi/input/input5
  U: Uniq=
  H: Handlers=rfkill kbd event5 
  B: PROP=0
  B: EV=100013
  B: KEY=8 0 8000 0 0 a1606f0090 8200027800501000 e 0
  B: MSC=10

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
  U: Uniq=
  H: Handlers=kbd event6 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input7
  U: Uniq=
  H: Handlers=kbd event7 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=04f2 Product=b424 Version=6969
  N: Name="USB2.0 HD UVC WebCam"
  P: Phys=usb-:00:14.0-4/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input8
  U: Uniq=
  H: Handlers=kbd event8 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9
  U: Uniq=
  H: Handlers=event9 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= 

[Kernel-packages] [Bug 1536810] Re: kernel install failed /bin/cp: cannot stat ‘/boot/initrd.img-4.3.0-7-generic’: No such file or directory

2016-01-26 Thread Scott Moser
"the kernel at least created the configuration".

I don't know where the file came from, but that is the file that is in
official ubuntu cloud images, built by livefs.

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

Title:
  kernel install failed /bin/cp: cannot stat
  ‘/boot/initrd.img-4.3.0-7-generic’: No such file or directory

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi, this failure for kernel package installation occured inside a maas image 
(lp:maas-images) build process.
  The failure log ends like this:

  Unpacking linux-generic (4.3.0.7.8) ...
  Processing triggers for man-db (2.7.5-1) ...
  Setting up linux-image-4.3.0-7-generic (4.3.0-7.18) ...
  Running depmod.
  update-initramfs: deferring update (hook will be called later)
  /bin/cp: cannot stat '/boot/initrd.img-4.3.0-7-generic': No such file or 
directory
  Failed to copy /boot/initrd.img-4.3.0-7-generic to /boot/initrd.img at 
/var/lib/dpkg/info/linux-image-4.3.0-7-generic.postinst line 745.
  dpkg: error processing package linux-image-4.3.0-7-generic (--configure):
   subprocess installed post-installation script returned error exit status 2
  Setting up devio (1.2-1build2) ...
  Setting up linux-base (4.0ubuntu1) ...
  Setting up flash-kernel (3.0~rc.4ubuntu57) ...
  Setting up linux-firmware (1.155) ...
  dpkg: dependency problems prevent configuration of linux-image-generic:
   linux-image-generic depends on linux-image-4.3.0-7-generic; however:
Package linux-image-4.3.0-7-generic is not configured yet.

  dpkg: error processing package linux-image-generic (--configure):
   dependency problems - leaving unconfigured
  Setting up linux-headers-4.3.0-7 (4.3.0-7.18) ...
  Setting up linux-headers-4.3.0-7-generic (4.3.0-7.18) ...
  Setting up linux-headers-generic (4.3.0.7.8) ...
  dpkg: dependency problems prevent configuration of linux-generic:
   linux-generic depends on linux-image-generic (= 4.3.0.7.8); however:
Package linux-image-generic is not configured yet.

  dpkg: error processing package linux-generic (--configure):
   dependency problems - leaving unconfigured
  No apport report written because the error message indicates its a followup 
error from a previous failure.
  No apport report written because the error message indicates its a followup 
error from a previous failure.
  Errors were encountered while processing:
   linux-image-4.3.0-7-generic
   linux-image-generic
   linux-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  failed install of  linux-generic
  failed chroot and kernel install
  failed
  failed to get linux-generic output

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

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


[Kernel-packages] [Bug 655325] Re: rhythmbox-metadata crashed with SIGSEGV in CSoundFile::ReadPTM()

2016-01-26 Thread dino99
This version has expired long ago; no more supported

** Changed in: libmodplug (Ubuntu)
   Status: New => Invalid

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

Title:
  rhythmbox-metadata crashed with SIGSEGV in CSoundFile::ReadPTM()

Status in libmodplug package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: rhythmbox

  Crack show playback problem

  ProblemType: Crash
  DistroRelease: Ubuntu 10.10
  Package: rhythmbox 0.13.1-0ubuntu5
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  Architecture: i386
  Date: Tue Oct  5 15:12:09 2010
  ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
  ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.utf8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x820e9c5 <_ZN10CSoundFile7ReadPTMEPKhj+69>:   rep 
movsl %ds:(%esi),%es:(%edi)
   PC (0x0820e9c5) ok
   source "%ds:(%esi)" (0xb6cfa07b) in non-readable VMA region: 
0xb6cfa000-0xb6d0 ---p None
   destination "%es:(%edi)" (0xb75beea7) ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading VMA None
  Signal: 11
  SourcePackage: rhythmbox
  StacktraceTop:
   CSoundFile::ReadPTM(unsigned char const*, unsigned int) () from 
/usr/lib/libmodplug.so.1
   CSoundFile::Create(unsigned char const*, unsigned int) () from 
/usr/lib/libmodplug.so.1
   ?? () from /usr/lib/gstreamer-0.10/libgstmodplug.so
   ?? () from /usr/lib/libgstreamer-0.10.so.0
   ?? () from /usr/lib/libgstreamer-0.10.so.0
  Title: rhythmbox-metadata crashed with SIGSEGV in CSoundFile::ReadPTM()
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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


[Kernel-packages] [Bug 1483343] Re: NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr tests

2016-01-26 Thread Joseph Salisbury
** Tags removed: kernel-key

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

Title:
  NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr
  tests

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Vivid:
  In Progress

Bug description:
  ---Problem Description---
  NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr tests

  ---uname output---
  Linux alp15 3.19.0-18-generic #18~14.04.1-Ubuntu SMP Wed May 20 09:40:36 UTC 
2015 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = P8 

  ---Steps to Reproduce---
  Install a P8 Power VM LPAR with Ubuntu 14.04.2 ISO.
  Then install the Ubuntu 14.04.3 kernel on the same and reboot.
  Then compile and build the LTP latest test suites on the same.

  root@alp15:~# tar -xvf ltp-full-20150420.tar.bz2
  root@alp15:~# cd ltp-full-20150420/
  root@alp15:~/ltp-full-20150420# ls
  aclocal.m4  configure execltp.in  install-sh  Makefile  
READMErunltplite.shtestcasesutils
  autom4te.cache  configure.ac  IDcheck.sh  lib Makefile.release  
README.kernel_config  runtest  testscripts  ver_linux
  config.guessCOPYING   include ltpmenu missing   
runalltests.shscenario_groups  TODO VERSION
  config.sub  doc   INSTALL m4  pan   
runltpscripts  tools
  root@alp15:~/ltp-full-20150420# ./configure
  root@alp15:~/ltp-full-20150420# make
  root@alp15:~/ltp-full-20150420# make install

  root@alp15:/opt/ltp/testcases/bin# ./lock_torture.sh
  lock_torture 1 TINFO : estimate time 6.00 min
  lock_torture 1 TINFO : spin_lock: running 60 sec...

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034386] NMI watchdog: BUG: soft lockup - CPU#10 stuck 
for 21s! [lock_torture_wr:2337]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034389] NMI watchdog: BUG: soft lockup - CPU#6 stuck for 
22s! [lock_torture_wr:2331]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034394] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 
22s! [lock_torture_wr:2339]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034396] NMI watchdog: BUG: soft lockup - CPU#3 stuck for 
22s! [lock_torture_wr:2346]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034398] NMI watchdog: BUG: soft lockup - CPU#7 stuck for 
21s! [lock_torture_wr:2334]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034410] NMI watchdog: BUG: soft lockup - CPU#11 stuck 
for 22s! [lock_torture_wr:2321]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.034412] NMI watchdog: BUG: soft lockup - CPU#9 stuck for 
22s! [lock_torture_wr:2333]

  Message from syslogd@alp15 at Thu Jun 18 01:23:32 2015 ...
  alp15 vmunix: [  308.038386] NMI watchdog: BUG: soft lockup - CPU#14 stuck 
for 22s! [lock_torture_wr:2327]

   
  Stack trace output:
   root@alp15:~# dmesg | more
  [ 1717.146881] lock_torture_wr R  running task
  [ 1717.146881]
  [ 1717.146885] 0  2555  2 0x0804
  [ 1717.146887] Call Trace:
  [ 1717.146894] [c00c7551b820] [c00c7551b860] 0xc00c7551b860 
(unreliable)
  [ 1717.146899] [c00c7551b860] [c00b4fb0] __do_softirq+0x220/0x3b0
  [ 1717.146904] [c00c7551b960] [c00b5478] irq_exit+0x98/0x100
  [ 1717.146909] [c00c7551b980] [c001fa54] timer_interrupt+0xa4/0xe0
  [ 1717.146913] [c00c7551b9b0] [c0002758] 
decrementer_common+0x158/0x180
  [ 1717.146922] --- interrupt: 901 at _raw_write_lock+0x68/0xc0
  [ 1717.146922] LR = torture_rwlock_write_lock+0x28/0x40 [locktorture]
  [ 1717.146927] [c00c7551bca0] [c00c7551bcd0] 0xc00c7551bcd0 
(unreliable)
  [ 1717.146934] [c00c7551bcd0] [dd4810b8] 
torture_rwlock_write_lock+0x28/0x40 [locktorture]
  [ 1717.146939] [c00c7551bcf0] [dd480578] 
lock_torture_writer+0x98/0x210 [locktorture]
  [ 1717.146944] [c00c7551bd80] [c00da4d4] kthread+0x114/0x140
  [ 1717.146948] [c00c7551be30] [c000956c] 
ret_from_kernel_thread+0x5c/0x70
  [ 1717.146951] Task dump for CPU 10:
  [ 1717.146953] lock_torture_wr R  running task0  2537  2 
0x0804
  [ 1717.146957] Call Trace:
  [ 1717.146961] [c00c7557b820] [c00c7557b860] 0xc00c7557b860 
(unreliable)
  [ 1717.146966] [c00c7557b860] [c00b4fb0] __do_softirq+0x220/0x3b0
  [ 1717.146970] [c00c7557b960] [c00b5478] irq_exit+0x98/0x100
  [ 1717.146975] [c00c7557b980] [c001fa54] timer_interrupt+0xa4/0xe0
  [ 1717.146979] [c00c7557b9b0] [c0002758] 
decrementer_common+0x158/0x180
  [ 1717.146988] --- 

[Kernel-packages] [Bug 1531768] Re: lxd and other commands get stuck on arm64 kernel and multiple CPUs

2016-01-26 Thread Martin Pitt
Retitling. The "unusably slow" part was fixed with installing haveged,
so what remains is that the 8x CPU instance gets into this lockup state
after some time.

On the 4x instance I'm now running adt-run in a loop, so far it's
through ~ 10 iterations. I'll let it run over night and see how it is
keeping up.

** Summary changed:

- arm64 kernel and multiple CPUs is unusably slow
+ lxd and other commands get stuck on arm64 kernel and multiple CPUs

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

Title:
  lxd and other commands get stuck on arm64 kernel and multiple CPUs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I created an 8 CPU arm64 instance on Canonical's Scalingstack (which I
  want to use for armhf autopkgtesting in LXD). I started with wily as
  that has lxd available (it's not yet available in trusty nor the PPA
  for arm64).

  However, pretty much any LXD task that I do (I haven't tried much
  else) on this machine takes unbearably long. A simple "lxc profile set
  default raw.lxc lxc.seccomp=" or "lxc list" takes several minutes.

  I see tons of

  [ 1020.971955] rcu_sched kthread starved for 6000 jiffies! g1095 c1094 f0x0
  [ 1121.166926] INFO: task fsnotify_mark:69 blocked for more than 120 seconds.

  in dmesg (the attached apport info has the complete dmesg).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-22-generic 4.2.0-22.27
  ProcVersionSignature: User Name 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan  7 09:18 seq
   crw-rw 1 root audio 116, 33 Jan  7 09:18 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Thu Jan  7 09:24:01 2016
  IwConfig:
   eth0  no wireless extensions.

   lono wireless extensions.

   lxcbr0no wireless extensions.
  Lspci:
   00:00.0 Host bridge [0600]: Red Hat, Inc. Device [1b36:0008]
    Subsystem: Red Hat, Inc Device [1af4:1100]
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=LABEL=cloudimg-rootfs earlyprintk
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-22-generic N/A
   linux-backports-modules-4.2.0-22-generic  N/A
   linux-firmware1.149.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


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

2016-01-26 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  Reboot then waking up after suspend on Acer Asprire 7540

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 15.10.

  Then I wake up computer after suspend, it just reboots. This happens with 
X.org ATI driver only, but with fglrx I'm greeted with a black screen (even 
backlights are turned off) and I have to reboot anyway. (but whatever, fglrx 
works horrible, I would never install it back) 
  ALSO, computer wakes up normally on latest upstream kernel 
(4.5.0-040500rc1-generic)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-25-lowlatency 4.2.0-25.30
  ProcVersionSignature: Ubuntu 4.2.0-25.30-lowlatency 4.2.6
  Uname: Linux 4.2.0-25-lowlatency x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  potato 2548 F pulseaudio
   /dev/snd/controlC1:  potato 2548 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 26 20:19:24 2016
  HibernationDevice: RESUME=UUID=2277e00a-0411-4136-b180-2892752df2e0
  InstallationDate: Installed on 2016-01-17 (9 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Aspire 7540
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-lowlatency 
root=UUID=ae6c8d51-38da-4c25-9281-6b9ceac5b2ca ro quiet splash acpi_sleep=nonvs 
quiet splash acpi_sleep=nonvs vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-lowlatency N/A
   linux-backports-modules-4.2.0-25-lowlatency  N/A
   linux-firmware   1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1538202] [NEW] Reboot then waking up after suspend on Acer Asprire 7540

2016-01-26 Thread MrRomanze
Public bug reported:

I'm using Ubuntu 15.10.

Then I wake up computer after suspend, it just reboots. This happens with X.org 
ATI driver only, but with fglrx I'm greeted with a black screen (even 
backlights are turned off) and I have to reboot anyway. (but whatever, fglrx 
works horrible, I would never install it back) 
ALSO, computer wakes up normally on latest upstream kernel 
(4.5.0-040500rc1-generic)

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-25-lowlatency 4.2.0-25.30
ProcVersionSignature: Ubuntu 4.2.0-25.30-lowlatency 4.2.6
Uname: Linux 4.2.0-25-lowlatency x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  potato 2548 F pulseaudio
 /dev/snd/controlC1:  potato 2548 F pulseaudio
CurrentDesktop: Unity
Date: Tue Jan 26 20:19:24 2016
HibernationDevice: RESUME=UUID=2277e00a-0411-4136-b180-2892752df2e0
InstallationDate: Installed on 2016-01-17 (9 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Acer Aspire 7540
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-lowlatency 
root=UUID=ae6c8d51-38da-4c25-9281-6b9ceac5b2ca ro quiet splash acpi_sleep=nonvs 
quiet splash acpi_sleep=nonvs vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-25-lowlatency N/A
 linux-backports-modules-4.2.0-25-lowlatency  N/A
 linux-firmware   1.149.3
SourcePackage: linux
UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/07/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.11
dmi.board.name: JV71TR
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
dmi.product.name: Aspire 7540
dmi.product.version: 0100
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug wily

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

Title:
  Reboot then waking up after suspend on Acer Asprire 7540

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 15.10.

  Then I wake up computer after suspend, it just reboots. This happens with 
X.org ATI driver only, but with fglrx I'm greeted with a black screen (even 
backlights are turned off) and I have to reboot anyway. (but whatever, fglrx 
works horrible, I would never install it back) 
  ALSO, computer wakes up normally on latest upstream kernel 
(4.5.0-040500rc1-generic)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-25-lowlatency 4.2.0-25.30
  ProcVersionSignature: Ubuntu 4.2.0-25.30-lowlatency 4.2.6
  Uname: Linux 4.2.0-25-lowlatency x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  potato 2548 F pulseaudio
   /dev/snd/controlC1:  potato 2548 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 26 20:19:24 2016
  HibernationDevice: RESUME=UUID=2277e00a-0411-4136-b180-2892752df2e0
  InstallationDate: Installed on 2016-01-17 (9 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Aspire 7540
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-lowlatency 
root=UUID=ae6c8d51-38da-4c25-9281-6b9ceac5b2ca ro quiet splash acpi_sleep=nonvs 
quiet splash acpi_sleep=nonvs vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-lowlatency N/A
   linux-backports-modules-4.2.0-25-lowlatency  N/A
   linux-firmware   1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1483170] Re: NVidia: Ubuntu: OS crashed into xmon Prompt; scsi_report_bus_reset

2016-01-26 Thread bugproxy
--- Comment From bjki...@us.ibm.com 2016-01-26 11:27 EDT---
Relevant patch is in vivid, which is 14.04.3. Moving to accepted awaiting 
verification.

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

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

Title:
  NVidia: Ubuntu: OS crashed into xmon Prompt;  scsi_report_bus_reset

Status in linux package in Ubuntu:
  New

Bug description:
  Problem Description:
  
  This system is running non-virtualized ubuntu with one nvidia k80 GPU. During 
a hardbootme run the OS crashed.  Here are the details from xmon:

  0:mon> e
  cpu 0x0: Vector: 300 (Data Access) at [c038f3b0]
  pc: c069ba80: scsi_report_bus_reset+0x60/0xb0
  lr: d0001cae524c: ipr_erp_start+0x3bc/0x644 [ipr]
  sp: c038f630
 msr: 90009033
 dar: 100178
   dsisr: 4000
current = 0xc1359b10
paca= 0xcfb8 softe: 0irq_happened: 0x01
  pid   = 0, comm = swapper/0
  0:mon> r
  R00 = d0001cae524c   R16 = 0020
  R01 = c038f630   R17 = 
  R02 = c13d8028   R18 = fffefa58
  R03 = c00fdcb0   R19 = c0e4a000
  R04 =    R20 = c1412180
  R05 = 0002   R21 = 0001
  R06 = 0067   R22 = 0002
  R07 = 0629   R23 = 01f0
  R08 = 0001   R24 = c0001010ea00
  R09 = 001000f0   R25 = c00fdcb00730
  R10 = 00ff   R26 = 0001
  R11 = d0001cae6518   R27 = 0629
  R12 = c069ba20   R28 = c00fdce40cf0
  R13 = cfb8   R29 = c00fa4c50300
  R14 = c135a120   R30 = 
  R15 =    R31 = c00fdcb0
  pc  = c069ba80 scsi_report_bus_reset+0x60/0xb0
  cfar= c0009368 slb_miss_realmode+0x50/0x78
  lr  = d0001cae524c ipr_erp_start+0x3bc/0x644 [ipr]
  msr = 90009033   cr  = 2804
  ctr = c069ba20   xer =    trap =  300
  dar = 00100178   dsisr = 4000
  0:mon> t
  [c038f660] d0001cae524c ipr_erp_start+0x3bc/0x644 [ipr]
  [c038f6c0] d0001caddb20 ipr_scsi_done+0x100/0x120 [ipr]
  [c038f700] d0001cadc5bc ipr_isr_mhrrq+0x10c/0x250 [ipr]
  [c038f760] c012ff90 handle_irq_event_percpu+0x90/0x2b0
  [c038f820] c0130218 handle_irq_event+0x68/0xd0
  [c038f850] c0135380 handle_fasteoi_irq+0xe0/0x250
  [c038f880] c012f188 generic_handle_irq+0x58/0x90
  [c038f8b0] c00119d0 __do_irq+0x80/0x190
  [c038f8e0] c0011bec do_IRQ+0x10c/0x120
  [c038f940] c0002794 hardware_interrupt_common+0x114/0x180
  --- Exception: 501 (Hardware Interrupt) at c06a45b4 
scsi_io_completion+0x1e4/0x800
  [c038fd00] c069662c scsi_finish_command+0x15c/0x1b0
  [c038fd80] c06a41d8 scsi_softirq_done+0x198/0x200
  [c038fe00] c04cbbd4 blk_done_softirq+0xb4/0xe0
  [c038fe40] c00b5244 __do_softirq+0x174/0x3e0
  [c038ff30] c00b5888 irq_exit+0xf8/0x140
  [c038ff60] c00119dc __do_irq+0x8c/0x190
  [c038ff90] c0025320 call_do_irq+0x14/0x24
  [c13d7840] c0011b80 do_IRQ+0xa0/0x120
  [c13d78a0] c0002794 hardware_interrupt_common+0x114/0x180
  --- Exception: 501 (Hardware Interrupt) at c00110d4 
arch_local_irq_restore+0x74/0x90
  [c13d7b90] c00162f8 __switch_to+0x208/0x350 (unreliable)
  [c13d7bb0] c00ef70c finish_task_switch+0x7c/0x1e0
  [c13d7bf0] c09d6c40 __schedule+0x370/0x910
  [c13d7e10] c09d7880 schedule_preempt_disabled+0x20/0x30
  [c13d7e30] c01121e4 cpu_startup_entry+0x1c4/0x500
  [c13d7ee0] c000ccd4 rest_init+0xa4/0xc0
  [c13d7f00] c0d53e4c start_kernel+0x520/0x53c
  [c13d7f90] c0009b6c start_here_common+0x20/0xa8
  0:mon>

  == Comment: #1 - Brian J. King  - 2015-05-28 17:08:13 ==
  Make sure we have the host lock held when calling scsi_report_bus_reset. 
Fixes a crash seen as the __devices list in the scsi host was changing as we 
were iterating through it.

  == Comment: #8 - Wen Xiong  - 2015-08-06 11:09:25 ==
  Release of bug changed to Ubuntu14.04.

  He has tested the patch and " yes the patch worked". We have upstream
  the patch last month. Here is the commit link:

  
https://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/drivers/scsi/ipr.c?h=misc=36b8e180e1e929e00b351c3b72aab3147fc14116

To manage notifications about this bug go to:

[Kernel-packages] [Bug 818354] Re: bluetoothd crashed with SIGSEGV in magazine_chain_pop_head()

2016-01-26 Thread dino99
This version has expired long ago; no more supported

** Changed in: bluez (Ubuntu)
   Status: New => Invalid

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

Title:
  bluetoothd crashed with SIGSEGV in magazine_chain_pop_head()

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Crashed while sending a file to a phone over Bluetooth.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: bluez 4.95-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0
  Uname: Linux 3.0.0-7-generic x86_64
  Architecture: amd64
  Date: Fri Jul 29 22:48:27 2011
  ExecutablePath: /usr/sbin/bluetoothd
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Sony Corporation VPCCW1FFX
  ProcCmdline: /usr/sbin/bluetoothd
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-7-generic 
root=UUID=f415c990-a34d-451b-b69c-2070c5d53e47 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x7f671b71dc58 :mov
0x8(%rax),%rbx
   PC (0x7f671b71dc58) ok
   source "0x8(%rax)" (0x10010021) not located in a known VMA region 
(needed readable region)!
   destination "%rbx" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: bluez
  StacktraceTop:
   magazine_chain_pop_head (mem_size=16) at 
/build/buildd/glib2.0-2.29.14/./glib/gslice.c:488
   thread_memory_magazine1_alloc (mem_size=16) at 
/build/buildd/glib2.0-2.29.14/./glib/gslice.c:795
   g_slice_alloc (mem_size=16) at 
/build/buildd/glib2.0-2.29.14/./glib/gslice.c:833
   g_slist_prepend (list=0x7f671cf1ab10, data=0x7f671c096600) at 
/build/buildd/glib2.0-2.29.14/./glib/gslist.c:302
   ?? ()
  Title: bluetoothd crashed with SIGSEGV in magazine_chain_pop_head()
  UpgradeStatus: Upgraded to oneiric on 2011-07-06 (23 days ago)
  UserGroups:
   
  dmi.bios.date: 09/22/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0190Y5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0190Y5:bd09/22/2009:svnSonyCorporation:pnVPCCW1FFX:pvrR5785054:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCCW1FFX
  dmi.product.version: R5785054
  dmi.sys.vendor: Sony Corporation
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:26:43:A9:97:5F  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING 
RX bytes:467 acl:0 sco:0 events:19 errors:0
TX bytes:88 acl:0 sco:0 commands:19 errors:0

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

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


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

2016-01-26 Thread Christophe H
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1533602/+attachment/4556909/+files/ProcCpuinfo.txt

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

Title:
  Click issue after resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello
  I have a fujitsu laptop with Intel i915

  since migration to 13.04 suspend causes issues: click disappear from
  both trackpad and USB mouse and bluetooth mouse

  some information
  4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 
x86_64 GNU/Linux

  I have this kind of event inside my logs
  ACPI: Waking up from system sleep state S3
  Jan 10 12:08:05 chris-linux kernel: [44974.880943] ehci-pci :00:1d.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.881094] pcieport :00:1c.3: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882387] ehci-pci :00:1a.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882601] PM: noirq resume of 
devices complete after 17.130 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.882884] PM: early resume of 
devices complete after 0.223 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.884702] e1000e :00:19.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.884945] rtc_cmos 00:04: System 
wakeup disabled by ACPI

  and also
  PM: Finishing wakeup.
  Jan 10 12:08:05 chris-linux kernel: [44976.050148] Restarting tasks ... 
  Jan 10 12:08:05 chris-linux kernel: [44976.056926] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059559] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059719] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059907] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059955] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060469] pci_bus :01: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060504] pci_bus :02: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060570] pci_bus :03: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060651] pci_bus :04: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060678] pci_bus :0d: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060708] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060771] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment

  for info I am running a OCZ Vertez 3 240 GB SSD

  later on I have this
  Jan 10 12:08:16 chris-linux kernel: [44987.373377] kactivitymanage[28482]: 
segfault at 7f49079f5cd0 ip 7f48eda7e1b1 sp 7fff0c544be8 error 4 in 
libQt5Sql.so.5.4.2[7f48eda6a000+3f000]

  and the results of cat /proc/acpi/wakeup

  Device  S-state   Status   Sysfs node
  UAR1  S3*disabled  pnp:00:06
  EHC1  S3*enabled   pci::00:1d.0
  EHC2  S3*enabled   pci::00:1a.0
  HDEF  S4*disabled  pci::00:1b.0
  PCE1  S4*disabled
  PCE3  S3*disabled  pci::00:1c.3
  PCE4  S4*disabled  pci::00:1c.4
  GLAN  S4*enabled   pci::00:19.0
  LID   S4*enabled   platform:PNP0C0D:00

  Hope that helps...do not hesitate if you need more info

  Thanks
  --- 
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1556 F pulseaudio
  CasperVersion: 1.366
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  MachineType: FUJITSU LIFEBOOK S761
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-7-generic N/A
   linux-backports-modules-4.3.0-7-generic  N/A
   linux-firmware   1.155
  Tags:  xenial
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: 

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

2016-01-26 Thread Christophe H
apport information

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

Title:
  Click issue after resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello
  I have a fujitsu laptop with Intel i915

  since migration to 13.04 suspend causes issues: click disappear from
  both trackpad and USB mouse and bluetooth mouse

  some information
  4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 
x86_64 GNU/Linux

  I have this kind of event inside my logs
  ACPI: Waking up from system sleep state S3
  Jan 10 12:08:05 chris-linux kernel: [44974.880943] ehci-pci :00:1d.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.881094] pcieport :00:1c.3: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882387] ehci-pci :00:1a.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882601] PM: noirq resume of 
devices complete after 17.130 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.882884] PM: early resume of 
devices complete after 0.223 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.884702] e1000e :00:19.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.884945] rtc_cmos 00:04: System 
wakeup disabled by ACPI

  and also
  PM: Finishing wakeup.
  Jan 10 12:08:05 chris-linux kernel: [44976.050148] Restarting tasks ... 
  Jan 10 12:08:05 chris-linux kernel: [44976.056926] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059559] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059719] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059907] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059955] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060469] pci_bus :01: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060504] pci_bus :02: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060570] pci_bus :03: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060651] pci_bus :04: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060678] pci_bus :0d: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060708] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060771] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment

  for info I am running a OCZ Vertez 3 240 GB SSD

  later on I have this
  Jan 10 12:08:16 chris-linux kernel: [44987.373377] kactivitymanage[28482]: 
segfault at 7f49079f5cd0 ip 7f48eda7e1b1 sp 7fff0c544be8 error 4 in 
libQt5Sql.so.5.4.2[7f48eda6a000+3f000]

  and the results of cat /proc/acpi/wakeup

  Device  S-state   Status   Sysfs node
  UAR1  S3*disabled  pnp:00:06
  EHC1  S3*enabled   pci::00:1d.0
  EHC2  S3*enabled   pci::00:1a.0
  HDEF  S4*disabled  pci::00:1b.0
  PCE1  S4*disabled
  PCE3  S3*disabled  pci::00:1c.3
  PCE4  S4*disabled  pci::00:1c.4
  GLAN  S4*enabled   pci::00:19.0
  LID   S4*enabled   platform:PNP0C0D:00

  Hope that helps...do not hesitate if you need more info

  Thanks
  --- 
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1556 F pulseaudio
  CasperVersion: 1.366
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  MachineType: FUJITSU LIFEBOOK S761
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-7-generic N/A
   linux-backports-modules-4.3.0-7-generic  N/A
   linux-firmware   1.155
  Tags:  xenial
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.b

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

2016-01-26 Thread Christophe H
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1533602/+attachment/4556906/+files/JournalErrors.txt

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

Title:
  Click issue after resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello
  I have a fujitsu laptop with Intel i915

  since migration to 13.04 suspend causes issues: click disappear from
  both trackpad and USB mouse and bluetooth mouse

  some information
  4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 
x86_64 GNU/Linux

  I have this kind of event inside my logs
  ACPI: Waking up from system sleep state S3
  Jan 10 12:08:05 chris-linux kernel: [44974.880943] ehci-pci :00:1d.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.881094] pcieport :00:1c.3: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882387] ehci-pci :00:1a.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882601] PM: noirq resume of 
devices complete after 17.130 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.882884] PM: early resume of 
devices complete after 0.223 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.884702] e1000e :00:19.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.884945] rtc_cmos 00:04: System 
wakeup disabled by ACPI

  and also
  PM: Finishing wakeup.
  Jan 10 12:08:05 chris-linux kernel: [44976.050148] Restarting tasks ... 
  Jan 10 12:08:05 chris-linux kernel: [44976.056926] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059559] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059719] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059907] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059955] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060469] pci_bus :01: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060504] pci_bus :02: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060570] pci_bus :03: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060651] pci_bus :04: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060678] pci_bus :0d: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060708] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060771] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment

  for info I am running a OCZ Vertez 3 240 GB SSD

  later on I have this
  Jan 10 12:08:16 chris-linux kernel: [44987.373377] kactivitymanage[28482]: 
segfault at 7f49079f5cd0 ip 7f48eda7e1b1 sp 7fff0c544be8 error 4 in 
libQt5Sql.so.5.4.2[7f48eda6a000+3f000]

  and the results of cat /proc/acpi/wakeup

  Device  S-state   Status   Sysfs node
  UAR1  S3*disabled  pnp:00:06
  EHC1  S3*enabled   pci::00:1d.0
  EHC2  S3*enabled   pci::00:1a.0
  HDEF  S4*disabled  pci::00:1b.0
  PCE1  S4*disabled
  PCE3  S3*disabled  pci::00:1c.3
  PCE4  S4*disabled  pci::00:1c.4
  GLAN  S4*enabled   pci::00:19.0
  LID   S4*enabled   platform:PNP0C0D:00

  Hope that helps...do not hesitate if you need more info

  Thanks
  --- 
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1556 F pulseaudio
  CasperVersion: 1.366
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  MachineType: FUJITSU LIFEBOOK S761
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-7-generic N/A
   linux-backports-modules-4.3.0-7-generic  N/A
   linux-firmware   1.155
  Tags:  xenial
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  

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

2016-01-26 Thread Christophe H
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1533602/+attachment/4556908/+files/Lsusb.txt

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

Title:
  Click issue after resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello
  I have a fujitsu laptop with Intel i915

  since migration to 13.04 suspend causes issues: click disappear from
  both trackpad and USB mouse and bluetooth mouse

  some information
  4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 
x86_64 GNU/Linux

  I have this kind of event inside my logs
  ACPI: Waking up from system sleep state S3
  Jan 10 12:08:05 chris-linux kernel: [44974.880943] ehci-pci :00:1d.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.881094] pcieport :00:1c.3: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882387] ehci-pci :00:1a.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882601] PM: noirq resume of 
devices complete after 17.130 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.882884] PM: early resume of 
devices complete after 0.223 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.884702] e1000e :00:19.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.884945] rtc_cmos 00:04: System 
wakeup disabled by ACPI

  and also
  PM: Finishing wakeup.
  Jan 10 12:08:05 chris-linux kernel: [44976.050148] Restarting tasks ... 
  Jan 10 12:08:05 chris-linux kernel: [44976.056926] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059559] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059719] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059907] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059955] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060469] pci_bus :01: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060504] pci_bus :02: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060570] pci_bus :03: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060651] pci_bus :04: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060678] pci_bus :0d: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060708] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060771] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment

  for info I am running a OCZ Vertez 3 240 GB SSD

  later on I have this
  Jan 10 12:08:16 chris-linux kernel: [44987.373377] kactivitymanage[28482]: 
segfault at 7f49079f5cd0 ip 7f48eda7e1b1 sp 7fff0c544be8 error 4 in 
libQt5Sql.so.5.4.2[7f48eda6a000+3f000]

  and the results of cat /proc/acpi/wakeup

  Device  S-state   Status   Sysfs node
  UAR1  S3*disabled  pnp:00:06
  EHC1  S3*enabled   pci::00:1d.0
  EHC2  S3*enabled   pci::00:1a.0
  HDEF  S4*disabled  pci::00:1b.0
  PCE1  S4*disabled
  PCE3  S3*disabled  pci::00:1c.3
  PCE4  S4*disabled  pci::00:1c.4
  GLAN  S4*enabled   pci::00:19.0
  LID   S4*enabled   platform:PNP0C0D:00

  Hope that helps...do not hesitate if you need more info

  Thanks
  --- 
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1556 F pulseaudio
  CasperVersion: 1.366
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  MachineType: FUJITSU LIFEBOOK S761
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-7-generic N/A
   linux-backports-modules-4.3.0-7-generic  N/A
   linux-firmware   1.155
  Tags:  xenial
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.b

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

2016-01-26 Thread Christophe H
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1533602/+attachment/4556911/+files/ProcModules.txt

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

Title:
  Click issue after resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello
  I have a fujitsu laptop with Intel i915

  since migration to 13.04 suspend causes issues: click disappear from
  both trackpad and USB mouse and bluetooth mouse

  some information
  4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 
x86_64 GNU/Linux

  I have this kind of event inside my logs
  ACPI: Waking up from system sleep state S3
  Jan 10 12:08:05 chris-linux kernel: [44974.880943] ehci-pci :00:1d.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.881094] pcieport :00:1c.3: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882387] ehci-pci :00:1a.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882601] PM: noirq resume of 
devices complete after 17.130 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.882884] PM: early resume of 
devices complete after 0.223 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.884702] e1000e :00:19.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.884945] rtc_cmos 00:04: System 
wakeup disabled by ACPI

  and also
  PM: Finishing wakeup.
  Jan 10 12:08:05 chris-linux kernel: [44976.050148] Restarting tasks ... 
  Jan 10 12:08:05 chris-linux kernel: [44976.056926] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059559] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059719] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059907] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059955] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060469] pci_bus :01: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060504] pci_bus :02: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060570] pci_bus :03: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060651] pci_bus :04: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060678] pci_bus :0d: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060708] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060771] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment

  for info I am running a OCZ Vertez 3 240 GB SSD

  later on I have this
  Jan 10 12:08:16 chris-linux kernel: [44987.373377] kactivitymanage[28482]: 
segfault at 7f49079f5cd0 ip 7f48eda7e1b1 sp 7fff0c544be8 error 4 in 
libQt5Sql.so.5.4.2[7f48eda6a000+3f000]

  and the results of cat /proc/acpi/wakeup

  Device  S-state   Status   Sysfs node
  UAR1  S3*disabled  pnp:00:06
  EHC1  S3*enabled   pci::00:1d.0
  EHC2  S3*enabled   pci::00:1a.0
  HDEF  S4*disabled  pci::00:1b.0
  PCE1  S4*disabled
  PCE3  S3*disabled  pci::00:1c.3
  PCE4  S4*disabled  pci::00:1c.4
  GLAN  S4*enabled   pci::00:19.0
  LID   S4*enabled   platform:PNP0C0D:00

  Hope that helps...do not hesitate if you need more info

  Thanks
  --- 
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1556 F pulseaudio
  CasperVersion: 1.366
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  MachineType: FUJITSU LIFEBOOK S761
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-7-generic N/A
   linux-backports-modules-4.3.0-7-generic  N/A
   linux-firmware   1.155
  Tags:  xenial
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: 

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

2016-01-26 Thread Christophe H
apport information

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

Title:
  Click issue after resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello
  I have a fujitsu laptop with Intel i915

  since migration to 13.04 suspend causes issues: click disappear from
  both trackpad and USB mouse and bluetooth mouse

  some information
  4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 
x86_64 GNU/Linux

  I have this kind of event inside my logs
  ACPI: Waking up from system sleep state S3
  Jan 10 12:08:05 chris-linux kernel: [44974.880943] ehci-pci :00:1d.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.881094] pcieport :00:1c.3: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882387] ehci-pci :00:1a.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882601] PM: noirq resume of 
devices complete after 17.130 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.882884] PM: early resume of 
devices complete after 0.223 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.884702] e1000e :00:19.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.884945] rtc_cmos 00:04: System 
wakeup disabled by ACPI

  and also
  PM: Finishing wakeup.
  Jan 10 12:08:05 chris-linux kernel: [44976.050148] Restarting tasks ... 
  Jan 10 12:08:05 chris-linux kernel: [44976.056926] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059559] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059719] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059907] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059955] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060469] pci_bus :01: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060504] pci_bus :02: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060570] pci_bus :03: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060651] pci_bus :04: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060678] pci_bus :0d: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060708] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060771] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment

  for info I am running a OCZ Vertez 3 240 GB SSD

  later on I have this
  Jan 10 12:08:16 chris-linux kernel: [44987.373377] kactivitymanage[28482]: 
segfault at 7f49079f5cd0 ip 7f48eda7e1b1 sp 7fff0c544be8 error 4 in 
libQt5Sql.so.5.4.2[7f48eda6a000+3f000]

  and the results of cat /proc/acpi/wakeup

  Device  S-state   Status   Sysfs node
  UAR1  S3*disabled  pnp:00:06
  EHC1  S3*enabled   pci::00:1d.0
  EHC2  S3*enabled   pci::00:1a.0
  HDEF  S4*disabled  pci::00:1b.0
  PCE1  S4*disabled
  PCE3  S3*disabled  pci::00:1c.3
  PCE4  S4*disabled  pci::00:1c.4
  GLAN  S4*enabled   pci::00:19.0
  LID   S4*enabled   platform:PNP0C0D:00

  Hope that helps...do not hesitate if you need more info

  Thanks
  --- 
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1556 F pulseaudio
  CasperVersion: 1.366
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  MachineType: FUJITSU LIFEBOOK S761
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-7-generic N/A
   linux-backports-modules-4.3.0-7-generic  N/A
   linux-firmware   1.155
  Tags:  xenial
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.b

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

2016-01-26 Thread Christophe H
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1533602/+attachment/4556910/+files/ProcInterrupts.txt

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

Title:
  Click issue after resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello
  I have a fujitsu laptop with Intel i915

  since migration to 13.04 suspend causes issues: click disappear from
  both trackpad and USB mouse and bluetooth mouse

  some information
  4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 
x86_64 GNU/Linux

  I have this kind of event inside my logs
  ACPI: Waking up from system sleep state S3
  Jan 10 12:08:05 chris-linux kernel: [44974.880943] ehci-pci :00:1d.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.881094] pcieport :00:1c.3: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882387] ehci-pci :00:1a.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882601] PM: noirq resume of 
devices complete after 17.130 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.882884] PM: early resume of 
devices complete after 0.223 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.884702] e1000e :00:19.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.884945] rtc_cmos 00:04: System 
wakeup disabled by ACPI

  and also
  PM: Finishing wakeup.
  Jan 10 12:08:05 chris-linux kernel: [44976.050148] Restarting tasks ... 
  Jan 10 12:08:05 chris-linux kernel: [44976.056926] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059559] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059719] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059907] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059955] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060469] pci_bus :01: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060504] pci_bus :02: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060570] pci_bus :03: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060651] pci_bus :04: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060678] pci_bus :0d: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060708] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060771] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment

  for info I am running a OCZ Vertez 3 240 GB SSD

  later on I have this
  Jan 10 12:08:16 chris-linux kernel: [44987.373377] kactivitymanage[28482]: 
segfault at 7f49079f5cd0 ip 7f48eda7e1b1 sp 7fff0c544be8 error 4 in 
libQt5Sql.so.5.4.2[7f48eda6a000+3f000]

  and the results of cat /proc/acpi/wakeup

  Device  S-state   Status   Sysfs node
  UAR1  S3*disabled  pnp:00:06
  EHC1  S3*enabled   pci::00:1d.0
  EHC2  S3*enabled   pci::00:1a.0
  HDEF  S4*disabled  pci::00:1b.0
  PCE1  S4*disabled
  PCE3  S3*disabled  pci::00:1c.3
  PCE4  S4*disabled  pci::00:1c.4
  GLAN  S4*enabled   pci::00:19.0
  LID   S4*enabled   platform:PNP0C0D:00

  Hope that helps...do not hesitate if you need more info

  Thanks
  --- 
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1556 F pulseaudio
  CasperVersion: 1.366
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  MachineType: FUJITSU LIFEBOOK S761
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-7-generic N/A
   linux-backports-modules-4.3.0-7-generic  N/A
   linux-firmware   1.155
  Tags:  xenial
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  

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

2016-01-26 Thread Christophe H
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1533602/+attachment/4556912/+files/PulseList.txt

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

Title:
  Click issue after resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello
  I have a fujitsu laptop with Intel i915

  since migration to 13.04 suspend causes issues: click disappear from
  both trackpad and USB mouse and bluetooth mouse

  some information
  4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 
x86_64 GNU/Linux

  I have this kind of event inside my logs
  ACPI: Waking up from system sleep state S3
  Jan 10 12:08:05 chris-linux kernel: [44974.880943] ehci-pci :00:1d.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.881094] pcieport :00:1c.3: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882387] ehci-pci :00:1a.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882601] PM: noirq resume of 
devices complete after 17.130 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.882884] PM: early resume of 
devices complete after 0.223 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.884702] e1000e :00:19.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.884945] rtc_cmos 00:04: System 
wakeup disabled by ACPI

  and also
  PM: Finishing wakeup.
  Jan 10 12:08:05 chris-linux kernel: [44976.050148] Restarting tasks ... 
  Jan 10 12:08:05 chris-linux kernel: [44976.056926] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059559] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059719] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059907] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059955] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060469] pci_bus :01: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060504] pci_bus :02: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060570] pci_bus :03: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060651] pci_bus :04: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060678] pci_bus :0d: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060708] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060771] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment

  for info I am running a OCZ Vertez 3 240 GB SSD

  later on I have this
  Jan 10 12:08:16 chris-linux kernel: [44987.373377] kactivitymanage[28482]: 
segfault at 7f49079f5cd0 ip 7f48eda7e1b1 sp 7fff0c544be8 error 4 in 
libQt5Sql.so.5.4.2[7f48eda6a000+3f000]

  and the results of cat /proc/acpi/wakeup

  Device  S-state   Status   Sysfs node
  UAR1  S3*disabled  pnp:00:06
  EHC1  S3*enabled   pci::00:1d.0
  EHC2  S3*enabled   pci::00:1a.0
  HDEF  S4*disabled  pci::00:1b.0
  PCE1  S4*disabled
  PCE3  S3*disabled  pci::00:1c.3
  PCE4  S4*disabled  pci::00:1c.4
  GLAN  S4*enabled   pci::00:19.0
  LID   S4*enabled   platform:PNP0C0D:00

  Hope that helps...do not hesitate if you need more info

  Thanks
  --- 
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1556 F pulseaudio
  CasperVersion: 1.366
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  MachineType: FUJITSU LIFEBOOK S761
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-7-generic N/A
   linux-backports-modules-4.3.0-7-generic  N/A
   linux-firmware   1.155
  Tags:  xenial
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

2016-01-26 Thread Christophe H
apport information

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

Title:
  Click issue after resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello
  I have a fujitsu laptop with Intel i915

  since migration to 13.04 suspend causes issues: click disappear from
  both trackpad and USB mouse and bluetooth mouse

  some information
  4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 
x86_64 GNU/Linux

  I have this kind of event inside my logs
  ACPI: Waking up from system sleep state S3
  Jan 10 12:08:05 chris-linux kernel: [44974.880943] ehci-pci :00:1d.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.881094] pcieport :00:1c.3: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882387] ehci-pci :00:1a.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882601] PM: noirq resume of 
devices complete after 17.130 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.882884] PM: early resume of 
devices complete after 0.223 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.884702] e1000e :00:19.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.884945] rtc_cmos 00:04: System 
wakeup disabled by ACPI

  and also
  PM: Finishing wakeup.
  Jan 10 12:08:05 chris-linux kernel: [44976.050148] Restarting tasks ... 
  Jan 10 12:08:05 chris-linux kernel: [44976.056926] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059559] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059719] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059907] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059955] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060469] pci_bus :01: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060504] pci_bus :02: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060570] pci_bus :03: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060651] pci_bus :04: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060678] pci_bus :0d: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060708] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060771] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment

  for info I am running a OCZ Vertez 3 240 GB SSD

  later on I have this
  Jan 10 12:08:16 chris-linux kernel: [44987.373377] kactivitymanage[28482]: 
segfault at 7f49079f5cd0 ip 7f48eda7e1b1 sp 7fff0c544be8 error 4 in 
libQt5Sql.so.5.4.2[7f48eda6a000+3f000]

  and the results of cat /proc/acpi/wakeup

  Device  S-state   Status   Sysfs node
  UAR1  S3*disabled  pnp:00:06
  EHC1  S3*enabled   pci::00:1d.0
  EHC2  S3*enabled   pci::00:1a.0
  HDEF  S4*disabled  pci::00:1b.0
  PCE1  S4*disabled
  PCE3  S3*disabled  pci::00:1c.3
  PCE4  S4*disabled  pci::00:1c.4
  GLAN  S4*enabled   pci::00:19.0
  LID   S4*enabled   platform:PNP0C0D:00

  Hope that helps...do not hesitate if you need more info

  Thanks
  --- 
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1556 F pulseaudio
  CasperVersion: 1.366
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  MachineType: FUJITSU LIFEBOOK S761
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-7-generic N/A
   linux-backports-modules-4.3.0-7-generic  N/A
   linux-firmware   1.155
  Tags:  xenial
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  

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

2016-01-26 Thread Christophe H
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1533602/+attachment/4556914/+files/UdevDb.txt

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

Title:
  Click issue after resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello
  I have a fujitsu laptop with Intel i915

  since migration to 13.04 suspend causes issues: click disappear from
  both trackpad and USB mouse and bluetooth mouse

  some information
  4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 
x86_64 GNU/Linux

  I have this kind of event inside my logs
  ACPI: Waking up from system sleep state S3
  Jan 10 12:08:05 chris-linux kernel: [44974.880943] ehci-pci :00:1d.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.881094] pcieport :00:1c.3: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882387] ehci-pci :00:1a.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882601] PM: noirq resume of 
devices complete after 17.130 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.882884] PM: early resume of 
devices complete after 0.223 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.884702] e1000e :00:19.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.884945] rtc_cmos 00:04: System 
wakeup disabled by ACPI

  and also
  PM: Finishing wakeup.
  Jan 10 12:08:05 chris-linux kernel: [44976.050148] Restarting tasks ... 
  Jan 10 12:08:05 chris-linux kernel: [44976.056926] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059559] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059719] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059907] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059955] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060469] pci_bus :01: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060504] pci_bus :02: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060570] pci_bus :03: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060651] pci_bus :04: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060678] pci_bus :0d: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060708] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060771] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment

  for info I am running a OCZ Vertez 3 240 GB SSD

  later on I have this
  Jan 10 12:08:16 chris-linux kernel: [44987.373377] kactivitymanage[28482]: 
segfault at 7f49079f5cd0 ip 7f48eda7e1b1 sp 7fff0c544be8 error 4 in 
libQt5Sql.so.5.4.2[7f48eda6a000+3f000]

  and the results of cat /proc/acpi/wakeup

  Device  S-state   Status   Sysfs node
  UAR1  S3*disabled  pnp:00:06
  EHC1  S3*enabled   pci::00:1d.0
  EHC2  S3*enabled   pci::00:1a.0
  HDEF  S4*disabled  pci::00:1b.0
  PCE1  S4*disabled
  PCE3  S3*disabled  pci::00:1c.3
  PCE4  S4*disabled  pci::00:1c.4
  GLAN  S4*enabled   pci::00:19.0
  LID   S4*enabled   platform:PNP0C0D:00

  Hope that helps...do not hesitate if you need more info

  Thanks
  --- 
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1556 F pulseaudio
  CasperVersion: 1.366
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  MachineType: FUJITSU LIFEBOOK S761
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-7-generic N/A
   linux-backports-modules-4.3.0-7-generic  N/A
   linux-firmware   1.155
  Tags:  xenial
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.b

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

2016-01-26 Thread Christophe H
apport information

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

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

Title:
  Click issue after resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello
  I have a fujitsu laptop with Intel i915

  since migration to 13.04 suspend causes issues: click disappear from
  both trackpad and USB mouse and bluetooth mouse

  some information
  4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 
x86_64 GNU/Linux

  I have this kind of event inside my logs
  ACPI: Waking up from system sleep state S3
  Jan 10 12:08:05 chris-linux kernel: [44974.880943] ehci-pci :00:1d.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.881094] pcieport :00:1c.3: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882387] ehci-pci :00:1a.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882601] PM: noirq resume of 
devices complete after 17.130 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.882884] PM: early resume of 
devices complete after 0.223 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.884702] e1000e :00:19.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.884945] rtc_cmos 00:04: System 
wakeup disabled by ACPI

  and also
  PM: Finishing wakeup.
  Jan 10 12:08:05 chris-linux kernel: [44976.050148] Restarting tasks ... 
  Jan 10 12:08:05 chris-linux kernel: [44976.056926] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059559] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059719] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059907] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059955] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060469] pci_bus :01: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060504] pci_bus :02: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060570] pci_bus :03: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060651] pci_bus :04: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060678] pci_bus :0d: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060708] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060771] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment

  for info I am running a OCZ Vertez 3 240 GB SSD

  later on I have this
  Jan 10 12:08:16 chris-linux kernel: [44987.373377] kactivitymanage[28482]: 
segfault at 7f49079f5cd0 ip 7f48eda7e1b1 sp 7fff0c544be8 error 4 in 
libQt5Sql.so.5.4.2[7f48eda6a000+3f000]

  and the results of cat /proc/acpi/wakeup

  Device  S-state   Status   Sysfs node
  UAR1  S3*disabled  pnp:00:06
  EHC1  S3*enabled   pci::00:1d.0
  EHC2  S3*enabled   pci::00:1a.0
  HDEF  S4*disabled  pci::00:1b.0
  PCE1  S4*disabled
  PCE3  S3*disabled  pci::00:1c.3
  PCE4  S4*disabled  pci::00:1c.4
  GLAN  S4*enabled   pci::00:19.0
  LID   S4*enabled   platform:PNP0C0D:00

  Hope that helps...do not hesitate if you need more info

  Thanks
  --- 
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1556 F pulseaudio
  CasperVersion: 1.366
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  MachineType: FUJITSU LIFEBOOK S761
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-7-generic N/A
   linux-backports-modules-4.3.0-7-generic  N/A
   linux-firmware   1.155
  Tags:  xenial
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: 

[Kernel-packages] [Bug 1533602] Re: Click issue after resume

2016-01-26 Thread Christophe H
apport information

** Tags added: apport-collected xenial

** Description changed:

  Hello
  I have a fujitsu laptop with Intel i915
  
  since migration to 13.04 suspend causes issues: click disappear from
  both trackpad and USB mouse and bluetooth mouse
  
  some information
  4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 
x86_64 GNU/Linux
  
  I have this kind of event inside my logs
  ACPI: Waking up from system sleep state S3
  Jan 10 12:08:05 chris-linux kernel: [44974.880943] ehci-pci :00:1d.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.881094] pcieport :00:1c.3: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882387] ehci-pci :00:1a.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882601] PM: noirq resume of 
devices complete after 17.130 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.882884] PM: early resume of 
devices complete after 0.223 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.884702] e1000e :00:19.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.884945] rtc_cmos 00:04: System 
wakeup disabled by ACPI
  
  and also
  PM: Finishing wakeup.
  Jan 10 12:08:05 chris-linux kernel: [44976.050148] Restarting tasks ... 
  Jan 10 12:08:05 chris-linux kernel: [44976.056926] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059559] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059719] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059907] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059955] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060469] pci_bus :01: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060504] pci_bus :02: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060570] pci_bus :03: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060651] pci_bus :04: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060678] pci_bus :0d: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060708] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060771] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  
  for info I am running a OCZ Vertez 3 240 GB SSD
  
  later on I have this
  Jan 10 12:08:16 chris-linux kernel: [44987.373377] kactivitymanage[28482]: 
segfault at 7f49079f5cd0 ip 7f48eda7e1b1 sp 7fff0c544be8 error 4 in 
libQt5Sql.so.5.4.2[7f48eda6a000+3f000]
  
  and the results of cat /proc/acpi/wakeup
  
  Device  S-state   Status   Sysfs node
  UAR1  S3*disabled  pnp:00:06
  EHC1  S3*enabled   pci::00:1d.0
  EHC2  S3*enabled   pci::00:1a.0
  HDEF  S4*disabled  pci::00:1b.0
  PCE1  S4*disabled
  PCE3  S3*disabled  pci::00:1c.3
  PCE4  S4*disabled  pci::00:1c.4
  GLAN  S4*enabled   pci::00:19.0
  LID   S4*enabled   platform:PNP0C0D:00
  
  Hope that helps...do not hesitate if you need more info
  
  Thanks
+ --- 
+ ApportVersion: 2.19.3-0ubuntu3
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  ubuntu 1556 F pulseaudio
+ CasperVersion: 1.366
+ CurrentDesktop: Unity
+ DistroRelease: Ubuntu 16.04
+ LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
+ MachineType: FUJITSU LIFEBOOK S761
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
+ ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
+ RelatedPackageVersions:
+  linux-restricted-modules-4.3.0-7-generic N/A
+  linux-backports-modules-4.3.0-7-generic  N/A
+  linux-firmware   1.155
+ Tags:  xenial
+ UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
+ Uname: Linux 4.3.0-7-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 04/27/2011
+ dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
+ dmi.bios.version: Version 1.14
+ dmi.board.name: FJNB225
+ dmi.board.vendor: FUJITSU
+ dmi.board.version: B1
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: FUJITSU
+ dmi.chassis.version: LIFEBOOK S761
+ dmi.modalias: 
dmi:

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

2016-01-26 Thread Christophe H
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1533602/+attachment/4556913/+files/RfKill.txt

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

Title:
  Click issue after resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello
  I have a fujitsu laptop with Intel i915

  since migration to 13.04 suspend causes issues: click disappear from
  both trackpad and USB mouse and bluetooth mouse

  some information
  4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 
x86_64 GNU/Linux

  I have this kind of event inside my logs
  ACPI: Waking up from system sleep state S3
  Jan 10 12:08:05 chris-linux kernel: [44974.880943] ehci-pci :00:1d.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.881094] pcieport :00:1c.3: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882387] ehci-pci :00:1a.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882601] PM: noirq resume of 
devices complete after 17.130 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.882884] PM: early resume of 
devices complete after 0.223 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.884702] e1000e :00:19.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.884945] rtc_cmos 00:04: System 
wakeup disabled by ACPI

  and also
  PM: Finishing wakeup.
  Jan 10 12:08:05 chris-linux kernel: [44976.050148] Restarting tasks ... 
  Jan 10 12:08:05 chris-linux kernel: [44976.056926] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059559] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059719] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059907] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059955] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060469] pci_bus :01: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060504] pci_bus :02: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060570] pci_bus :03: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060651] pci_bus :04: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060678] pci_bus :0d: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060708] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060771] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment

  for info I am running a OCZ Vertez 3 240 GB SSD

  later on I have this
  Jan 10 12:08:16 chris-linux kernel: [44987.373377] kactivitymanage[28482]: 
segfault at 7f49079f5cd0 ip 7f48eda7e1b1 sp 7fff0c544be8 error 4 in 
libQt5Sql.so.5.4.2[7f48eda6a000+3f000]

  and the results of cat /proc/acpi/wakeup

  Device  S-state   Status   Sysfs node
  UAR1  S3*disabled  pnp:00:06
  EHC1  S3*enabled   pci::00:1d.0
  EHC2  S3*enabled   pci::00:1a.0
  HDEF  S4*disabled  pci::00:1b.0
  PCE1  S4*disabled
  PCE3  S3*disabled  pci::00:1c.3
  PCE4  S4*disabled  pci::00:1c.4
  GLAN  S4*enabled   pci::00:19.0
  LID   S4*enabled   platform:PNP0C0D:00

  Hope that helps...do not hesitate if you need more info

  Thanks
  --- 
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1556 F pulseaudio
  CasperVersion: 1.366
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  MachineType: FUJITSU LIFEBOOK S761
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-7-generic N/A
   linux-backports-modules-4.3.0-7-generic  N/A
   linux-firmware   1.155
  Tags:  xenial
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.b

[Kernel-packages] [Bug 1486670] Re: using ipsec, many connections result in no buffer space error

2016-01-26 Thread Joseph Salisbury
** 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/1486670

Title:
  using ipsec, many connections result in no buffer space error

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Precise:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Wily:
  In Progress

Bug description:
  Reproduction info:

  set up two LXC containers (although this probably isn't specific to
  LXC containers), and inside each setup ipsec with something similar
  to:

  conn nodeN
  aggressive=yes 
  authby=secret 
  auto=start 
  closeaction=restart 
  dpdaction=restart 
  esp=aes256-aes256gmac-modp1024 
  ike=aes256-sha512-modp1024 
  keyexchange=ikev2 
  left=10.0.3.145 
  leftid=10.0.3.145 
  lifetime=12h 
  reauth=no 
  right=10.0.3.199 
  type=transport 

  
  then repeatedly open connections to the peer, e.g.:

  while true; do ping -c1 10.0.3.199 ; sleep 0.1 ; done

  eventually, the connections will fail with:

  connect: No buffer space available

  the reproduction can be sped up by reducing the xfrm4_gc_thresh, e.g.:

  echo 5 > /proc/sys/net/ipv4/xfrm4_gc_thresh

  
  Once the error occurs, no more connections can be made to the peer (all fail 
with no buffer space available), however after a long period (e.g. overnight) 
the buffers will be cleaned up and connections can be made again.

  this happens even on the latest net-next kernel.

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

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


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

2016-01-26 Thread Christophe H
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1533602/+attachment/4556905/+files/IwConfig.txt

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

Title:
  Click issue after resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello
  I have a fujitsu laptop with Intel i915

  since migration to 13.04 suspend causes issues: click disappear from
  both trackpad and USB mouse and bluetooth mouse

  some information
  4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 
x86_64 GNU/Linux

  I have this kind of event inside my logs
  ACPI: Waking up from system sleep state S3
  Jan 10 12:08:05 chris-linux kernel: [44974.880943] ehci-pci :00:1d.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.881094] pcieport :00:1c.3: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882387] ehci-pci :00:1a.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882601] PM: noirq resume of 
devices complete after 17.130 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.882884] PM: early resume of 
devices complete after 0.223 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.884702] e1000e :00:19.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.884945] rtc_cmos 00:04: System 
wakeup disabled by ACPI

  and also
  PM: Finishing wakeup.
  Jan 10 12:08:05 chris-linux kernel: [44976.050148] Restarting tasks ... 
  Jan 10 12:08:05 chris-linux kernel: [44976.056926] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059559] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059719] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059907] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059955] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060469] pci_bus :01: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060504] pci_bus :02: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060570] pci_bus :03: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060651] pci_bus :04: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060678] pci_bus :0d: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060708] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060771] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment

  for info I am running a OCZ Vertez 3 240 GB SSD

  later on I have this
  Jan 10 12:08:16 chris-linux kernel: [44987.373377] kactivitymanage[28482]: 
segfault at 7f49079f5cd0 ip 7f48eda7e1b1 sp 7fff0c544be8 error 4 in 
libQt5Sql.so.5.4.2[7f48eda6a000+3f000]

  and the results of cat /proc/acpi/wakeup

  Device  S-state   Status   Sysfs node
  UAR1  S3*disabled  pnp:00:06
  EHC1  S3*enabled   pci::00:1d.0
  EHC2  S3*enabled   pci::00:1a.0
  HDEF  S4*disabled  pci::00:1b.0
  PCE1  S4*disabled
  PCE3  S3*disabled  pci::00:1c.3
  PCE4  S4*disabled  pci::00:1c.4
  GLAN  S4*enabled   pci::00:19.0
  LID   S4*enabled   platform:PNP0C0D:00

  Hope that helps...do not hesitate if you need more info

  Thanks
  --- 
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1556 F pulseaudio
  CasperVersion: 1.366
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  MachineType: FUJITSU LIFEBOOK S761
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-7-generic N/A
   linux-backports-modules-4.3.0-7-generic  N/A
   linux-firmware   1.155
  Tags:  xenial
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  

[Kernel-packages] [Bug 1538205] [NEW] Touchpad lock button locks mouse completely on Acer Aspire 7540

2016-01-26 Thread MrRomanze
Public bug reported:

Then I click touchpad lock button, it works, button glows, notification shows 
up, mouse locks. 
However, then I press it again, it wouldn't unlock the touchpad. (but button 
stops to glow and notifications shows up again too) 
The only solution is to reboot.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-25-lowlatency 4.2.0-25.30
ProcVersionSignature: Ubuntu 4.2.0-25.30-lowlatency 4.2.6
Uname: Linux 4.2.0-25-lowlatency x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  potato 2548 F pulseaudio
 /dev/snd/controlC1:  potato 2548 F pulseaudio
CurrentDesktop: Unity
Date: Tue Jan 26 20:29:28 2016
HibernationDevice: RESUME=UUID=2277e00a-0411-4136-b180-2892752df2e0
InstallationDate: Installed on 2016-01-17 (9 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Acer Aspire 7540
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-lowlatency 
root=UUID=ae6c8d51-38da-4c25-9281-6b9ceac5b2ca ro quiet splash acpi_sleep=nonvs 
quiet splash acpi_sleep=nonvs vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.2.0-25-lowlatency N/A
 linux-backports-modules-4.2.0-25-lowlatency  N/A
 linux-firmware   1.149.3
SourcePackage: linux
UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/07/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.11
dmi.board.name: JV71TR
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
dmi.product.name: Aspire 7540
dmi.product.version: 0100
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug wily

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

Title:
  Touchpad lock button locks mouse completely on Acer Aspire 7540

Status in linux package in Ubuntu:
  New

Bug description:
  Then I click touchpad lock button, it works, button glows, notification shows 
up, mouse locks. 
  However, then I press it again, it wouldn't unlock the touchpad. (but button 
stops to glow and notifications shows up again too) 
  The only solution is to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-25-lowlatency 4.2.0-25.30
  ProcVersionSignature: Ubuntu 4.2.0-25.30-lowlatency 4.2.6
  Uname: Linux 4.2.0-25-lowlatency x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  potato 2548 F pulseaudio
   /dev/snd/controlC1:  potato 2548 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 26 20:29:28 2016
  HibernationDevice: RESUME=UUID=2277e00a-0411-4136-b180-2892752df2e0
  InstallationDate: Installed on 2016-01-17 (9 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Aspire 7540
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-lowlatency 
root=UUID=ae6c8d51-38da-4c25-9281-6b9ceac5b2ca ro quiet splash acpi_sleep=nonvs 
quiet splash acpi_sleep=nonvs vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-lowlatency N/A
   linux-backports-modules-4.2.0-25-lowlatency  N/A
   linux-firmware   1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1533602] Re: Click issue after resume

2016-01-26 Thread Christopher M. Penalver
Christophe H, the latest mainline kernel (4.5-rc1) became available two
days ago. Hence, could you please test this and advise to the results?

** Tags added: latest-bios-1.14

** Tags added: regression-release

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

Title:
  Click issue after resume

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello
  I have a fujitsu laptop with Intel i915

  since migration to 13.04 suspend causes issues: click disappear from
  both trackpad and USB mouse and bluetooth mouse

  some information
  4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 
x86_64 GNU/Linux

  I have this kind of event inside my logs
  ACPI: Waking up from system sleep state S3
  Jan 10 12:08:05 chris-linux kernel: [44974.880943] ehci-pci :00:1d.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.881094] pcieport :00:1c.3: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882387] ehci-pci :00:1a.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.882601] PM: noirq resume of 
devices complete after 17.130 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.882884] PM: early resume of 
devices complete after 0.223 msecs
  Jan 10 12:08:05 chris-linux kernel: [44974.884702] e1000e :00:19.0: 
System wakeup disabled by ACPI
  Jan 10 12:08:05 chris-linux kernel: [44974.884945] rtc_cmos 00:04: System 
wakeup disabled by ACPI

  and also
  PM: Finishing wakeup.
  Jan 10 12:08:05 chris-linux kernel: [44976.050148] Restarting tasks ... 
  Jan 10 12:08:05 chris-linux kernel: [44976.056926] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059559] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059719] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059907] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.059955] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060469] pci_bus :01: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060504] pci_bus :02: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060570] pci_bus :03: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060651] pci_bus :04: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060678] pci_bus :0d: 
Allocating resources
  Jan 10 12:08:05 chris-linux kernel: [44976.060708] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment
  Jan 10 12:08:05 chris-linux kernel: [44976.060771] i915 :00:02.0: BAR 6: 
[??? 0x flags 0x2] has bogus alignment

  for info I am running a OCZ Vertez 3 240 GB SSD

  later on I have this
  Jan 10 12:08:16 chris-linux kernel: [44987.373377] kactivitymanage[28482]: 
segfault at 7f49079f5cd0 ip 7f48eda7e1b1 sp 7fff0c544be8 error 4 in 
libQt5Sql.so.5.4.2[7f48eda6a000+3f000]

  and the results of cat /proc/acpi/wakeup

  Device  S-state   Status   Sysfs node
  UAR1  S3*disabled  pnp:00:06
  EHC1  S3*enabled   pci::00:1d.0
  EHC2  S3*enabled   pci::00:1a.0
  HDEF  S4*disabled  pci::00:1b.0
  PCE1  S4*disabled
  PCE3  S3*disabled  pci::00:1c.3
  PCE4  S4*disabled  pci::00:1c.4
  GLAN  S4*enabled   pci::00:19.0
  LID   S4*enabled   platform:PNP0C0D:00

  Hope that helps...do not hesitate if you need more info

  Thanks
  --- 
  ApportVersion: 2.19.3-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1556 F pulseaudio
  CasperVersion: 1.366
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160126)
  MachineType: FUJITSU LIFEBOOK S761
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
  RelatedPackageVersions:
   linux-restricted-modules-4.3.0-7-generic N/A
   linux-backports-modules-4.3.0-7-generic  N/A
   linux-firmware   1.155
  Tags:  xenial
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.3.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm

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

2016-01-26 Thread Brad Figg
This change was made by a bot.

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

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

Title:
  Touchpad lock button locks mouse completely on Acer Aspire 7540

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Then I click touchpad lock button, it works, button glows, notification shows 
up, mouse locks. 
  However, then I press it again, it wouldn't unlock the touchpad. (but button 
stops to glow and notifications shows up again too) 
  The only solution is to reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-25-lowlatency 4.2.0-25.30
  ProcVersionSignature: Ubuntu 4.2.0-25.30-lowlatency 4.2.6
  Uname: Linux 4.2.0-25-lowlatency x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  potato 2548 F pulseaudio
   /dev/snd/controlC1:  potato 2548 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 26 20:29:28 2016
  HibernationDevice: RESUME=UUID=2277e00a-0411-4136-b180-2892752df2e0
  InstallationDate: Installed on 2016-01-17 (9 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Acer Aspire 7540
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-lowlatency 
root=UUID=ae6c8d51-38da-4c25-9281-6b9ceac5b2ca ro quiet splash acpi_sleep=nonvs 
quiet splash acpi_sleep=nonvs vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-25-lowlatency N/A
   linux-backports-modules-4.2.0-25-lowlatency  N/A
   linux-firmware   1.149.3
  SourcePackage: linux
  UdevLog: Error: [Errno 2] Нет такого файла или каталога: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/07/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.11
  dmi.board.name: JV71TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 7540
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

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

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


[Kernel-packages] [Bug 1440103] Re: [Hyper-V] Kernel panic not functional on Vivid

2016-01-26 Thread Joseph Salisbury
Hi Chris,

Can you verify the kernel in -proposed as requested in #33?  That way
the fix can move into -updates.

Thanks in advance!

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

Title:
  [Hyper-V] Kernel panic not functional on Vivid

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

Bug description:
  Issue description:
  Triggering a kernel panic will not produce a crash dump file.

  Steps to Reproduce:
  1. install kdump related packages.
  2. verify crashmem value - defaults to 384M-:129M
  3. verify that the system is ready for crash:
  # cat /sys/kernel/kexec_crash_loaded
  1
  4. trigger kernel panic with # echo c | sudo tee /proc/sysrq-trigger
  5. The system will freeze and no kernel dump will be generated, system is not 
rebooted automatically as configured in kdump-tools config.

  Versions details:
  Windows Server Host Edition: Microsoft Windows Server 2012 R2 Datacenter 
build 9600
  Distribution name and release: Ubuntu Vivid Vervet
  Kernel version: Linux ubuntu31 3.19.0-11-generic #11lp14233432v201504021617 
SMP

  Repro output with VM settings as follows:
  2GB RAM, 1vCPU, crashmem: 384M:128M OR 384M:128M

  [  149.328829] SysRq : Trigger a crash
  [  149.342418] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [  149.346369] IP: [] sysrq_handle_crash+0x16/0x20
  [  149.346369] PGD 367a3067 PUD 7bdf0067 PMD 0
  [  149.346369] Oops: 0002 [#1] SMP
  [  149.346369] Modules linked in: joydev hid_generic hid_hyperv serio_raw hid 
8250_fintek hyperv_keyboard hv_balloon hyp
  erv_fb i2c_piix4 mac_hid autofs4 hv_netvsc hv_utils hv_storvsc psmouse floppy 
pata_acpi hv_vmbus
  [  149.346369] CPU: 0 PID: 1379 Comm: tee Not tainted 3.19.0-11-generic 
#11lp14233432v201504021617
  [  149.346369] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090006  05/23/2012
  [  149.346369] task: 88007a7d3ae0 ti: 88007be7c000 task.ti: 
88007be7c000
  [  149.346369] RIP: 0010:[]  [] 
sysrq_handle_crash+0x16/0x20
  [  149.346369] RSP: 0018:88007be7fe68  EFLAGS: 00010292
  [  149.346369] RAX: 000f RBX: 0063 RCX: 
000f
  [  149.346369] RDX: 88007ce0fd78 RSI: 88007ce0e498 RDI: 
0063
  [  149.346369] RBP: 88007be7fe68 R08: 0002 R09: 
0275
  [  149.346369] R10: 0092 R11: 0275 R12: 
0004
  [  149.346369] R13:  R14: 81cb38e0 R15: 
0008
  [  149.346369] FS:  7f0a2e22a700() GS:88007ce0() 
knlGS:
  [  149.346369] CS:  0010 DS:  ES:  CR0: 8005003b
  [  149.346369] CR2:  CR3: 36047000 CR4: 
06f0
  [  149.346369] Stack:
  [  149.346369]  88007be7fe98 814aef96 0002 
fffb
  [  149.346369]  7ffc64e934b0 0002 88007be7feb8 
814af443
  [  149.346369]  7ffc64e934b0 8800364f15c0 88007be7fed8 
8125ad98
  [  149.346369] Call Trace:
  [  149.346369]  [] __handle_sysrq+0x106/0x170
  [  149.346369]  [] write_sysrq_trigger+0x33/0x40
  [  149.346369]  [] proc_reg_write+0x48/0x70
  [  149.346369]  [] vfs_write+0xb7/0x1f0
  [  149.346369]  [] ? vfs_read+0x11e/0x140
  [  149.346369]  [] SyS_write+0x46/0xb0
  [  149.346369]  [] system_call_fastpath+0x16/0x1b
  [  149.346369] Code: ef e8 df f7 ff ff eb d8 66 2e 0f 1f 84 00 00 00 00 00 0f 
1f 00 66 66 66 66 90 55 c7 05 34 42 a3 00
  01 00 00 00 48 89 e5 0f ae f8  04 25 00 00 00 00 01 5d c3 66 66 66 66 90 
55 31 c0 48 89 e5
  [  149.346369] RIP  [] sysrq_handle_crash+0x16/0x20
  [  149.346369]  RSP 
  [  149.346369] CR2: 
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 3.19.0-11-generic (apw@gloin) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu12) ) #11lp14233432v
  201504021617 SMP Thu Apr 2 15:15:51 UTC 2015 (Ubuntu 
3.19.0-11.11lp14233432v201504021617-generic 3.19.3)
  [0.00] Command line: BOOT_IMAGE=/vmlinuz-3.19.0-11-generic 
root=/dev/mapper/ubuntu31--vg-root ro console=tty0 co
  nsole=ttyS1 irqpoll maxcpus=1 nousb systemd.unit=kdump-tools.service 
elfcorehdr=867700K

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

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


[Kernel-packages] [Bug 1494423] Re: Upstream commits for NUMA node performance in Hyper-V

2016-01-26 Thread Joseph Salisbury
Hi Chris or Josh,

Can you verify the kernel in -proposed as requested in #9?  That way the
fix can move into -updates.

Thanks in advance!

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

Title:
  Upstream commits for NUMA node performance in Hyper-V

Status in linux package in Ubuntu:
  In Progress
Status in linux-lts-trusty package in Ubuntu:
  In Progress
Status in linux-lts-trusty source package in Precise:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Vivid:
  Fix Committed

Bug description:
  Microsoft has investigated networking with NUMA nodes and Hyper-V and
  found a number of areas where Linux performance could be corrected to
  be in line with other virtual machine types.

  Please include the following commits and their necessary prerequisites
  (which have been accepted upstream into the 4.2 kernel series) into
  the kernels for 15.10, 15.04, 14.04 (including HWE), and 12.04
  (including HWE):

  8/5 "Drivers: hv: vmbus: Further improve CPU affiliation logic" 
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3b71107d73b16074afa7658f3f0fcf837aabfe24

  8/5 "Drivers: hv: vmbus: Improve the CPU affiliation for channels"
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=9f01ec53458d9e9b68f1c555e773b5d1a1f66e94

  6/12 "Drivers: hv: vmbus: Allocate ring buffer memory in NUMA aware fashion"
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=294409d20572e9bcf857328286433f851168d54a

  6/1 "Drivers: hv: vmbus: Implement NUMA aware CPU affinity for channels"
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1f656ff3fdddc2f59649cc84b633b799908f1f7b

  5/31 "hv_netvsc: Allocate the receive buffer from the correct NUMA node"
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=0a726c2b499e390b1c1fc3092bd789f2192a2d03

  5/31 "hv_netvsc: Allocate the sendbuf in a NUMA aware way"
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=5defde5946676ee23cd6a9d0e1de899410f4a33f

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

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


[Kernel-packages] [Bug 1537472] Re: Synaptics touchpad not recognised - OK on linux-image-3.13.0-74-generic 3.13.0-74.118

2016-01-26 Thread John Leake
OK so I managed to update the bios.
8AET65WW (1.45 )
05/14/2015

Still fails on 76,  4.4 and 4.5

The 76 boot is worse (no wifi and screen resolution screwed up).
The boot error TPM(6) occurs when attempting to read pcr value.

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

Title:
  Synaptics touchpad not recognised - OK on linux-
  image-3.13.0-74-generic  3.13.0-74.118

Status in linux package in Ubuntu:
  New

Bug description:
  Thinkpad T520 mousepad defaults to standard PS2 so there is no edge
  scroll etc. and thus no settings tab for touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-76-generic 3.13.0-76.120
  ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-76-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2053 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan 24 11:06:21 2016
  HibernationDevice: RESUME=UUID=0014b9e9-0896-45dd-8005-73598192eb15
  InstallationDate: Installed on 2015-03-21 (308 days ago)
  InstallationMedia: BackBox Linux 4.1 - Release i386
  MachineType: LENOVO 4242A25
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-76-generic 
root=UUID=52833b54-5bbe-4c2f-97e4-73240dfc57e9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-76-generic N/A
   linux-backports-modules-3.13.0-76-generic  N/A
   linux-firmware 1.127.20
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET64WW (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4242A25
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: 1S4242A25R9FKBZP
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET64WW(1.44):bd07/26/2013:svnLENOVO:pn4242A25:pvrThinkPadT520:rvnLENOVO:rn4242A25:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4242A25
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1537472] Status changed to Confirmed

2016-01-26 Thread Brad Figg
This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1537472

Title:
  Synaptics touchpad not recognised - OK on linux-
  image-3.13.0-74-generic  3.13.0-74.118

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Thinkpad T520 mousepad defaults to standard PS2 so there is no edge
  scroll etc. and thus no settings tab for touchpad.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-76-generic 3.13.0-76.120
  ProcVersionSignature: Ubuntu 3.13.0-76.120-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-76-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   2053 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sun Jan 24 11:06:21 2016
  HibernationDevice: RESUME=UUID=0014b9e9-0896-45dd-8005-73598192eb15
  InstallationDate: Installed on 2015-03-21 (308 days ago)
  InstallationMedia: BackBox Linux 4.1 - Release i386
  MachineType: LENOVO 4242A25
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-76-generic 
root=UUID=52833b54-5bbe-4c2f-97e4-73240dfc57e9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-76-generic N/A
   linux-backports-modules-3.13.0-76-generic  N/A
   linux-firmware 1.127.20
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET64WW (1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4242A25
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: 1S4242A25R9FKBZP
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET64WW(1.44):bd07/26/2013:svnLENOVO:pn4242A25:pvrThinkPadT520:rvnLENOVO:rn4242A25:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4242A25
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1537472/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 840426] Re: kerneloops crashed with SIGSEGV in memchr()

2016-01-26 Thread dino99
This version has expired long ago; no more supported

** Changed in: kerneloops (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kerneloops in Ubuntu.
https://bugs.launchpad.net/bugs/840426

Title:
  kerneloops crashed with SIGSEGV in memchr()

Status in kerneloops package in Ubuntu:
  Invalid

Bug description:
  Error is reported immediately after logging in and entering password
  for Gnome Keyring.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: kerneloops-daemon 0.12+git20090217-1ubuntu14
  ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3
  Uname: Linux 3.0.0-9-generic i686
  NonfreeKernelModules: wl
  Architecture: i386
  Date: Fri Sep  2 12:57:02 2011
  ExecutablePath: /usr/sbin/kerneloops
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  ProcCmdline: /usr/sbin/kerneloops
  ProcEnviron: PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x1befbd : jne0x1bf04c 
   PC (0x001befbd) ok
   source "0x1bf04c" (0x001bf04c) ok
   SP (0xbfbee138) ok
   Reason could not be automatically determined.
  Signal: 11
  SourcePackage: kerneloops
  StacktraceTop:
   memchr () at ../sysdeps/i386/memchr.S:210
   two_way_short_needle (needle_len=, needle=0x804b927 "RTNL: 
assertion failed", haystack_len=, haystack=0x96e62f2 "RDA for 
country: US") at ../string/str-two-way.h:269
   __strstr_ia32 (haystack_start=0x96e62df "cfg80211: Calling CRDA for country: 
US", needle_start=0x804b927 "RTNL: assertion failed") at ../string/strstr.c:84
   ?? ()
   ?? ()
  Title: kerneloops crashed with SIGSEGV in memchr()
  UpgradeStatus: Upgraded to oneiric on 2011-08-28 (5 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/840426/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1537923] Re: Add pvpanic driver to Ubuntu 15.10 virtual kernel

2016-01-26 Thread Tim Gardner
** Changed in: linux (Ubuntu Wily)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1537923

Title:
  Add pvpanic driver to Ubuntu 15.10 virtual kernel

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Wily:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  GCE's Ubuntu 15.10 images lack the pvpanic driver. The driver is
  useful for detecting guest panics, and we would like to see it added
  to the Ubuntu 15.10 virtual kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1537923/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1446906] Re: lxc container with postfix, permission denied on mailq

2016-01-26 Thread Tim Gardner
** Changed in: linux (Ubuntu Vivid)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Wily)
   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/1446906

Title:
  lxc container with postfix, permission denied on mailq

Status in linux package in Ubuntu:
  Fix Committed
Status in lxc package in Ubuntu:
  Confirmed
Status in linux source package in Vivid:
  Fix Committed
Status in lxc source package in Vivid:
  New
Status in linux source package in Wily:
  Fix Committed
Status in lxc source package in Wily:
  New
Status in linux source package in Xenial:
  Fix Committed
Status in lxc source package in Xenial:
  Confirmed

Bug description:
  [Impact]

   * Users may encounter situations where they use applications, confined by
 AppArmor, that hit EACESS failures when attempting to operate on AF_UNIX
 stream sockets.

   * These failures typically occur when the confined applications attempts to
 read from an AF_UNIX stream socket when the other end of the socket has
 already been closed.

   * AppArmor is mistakenly denying the socket operations due to the socket
 shutdown operation making the sun_path no longer being available for
 AppArmor mediation after the socket is shutdown.

  [Test Case]

   The expected test case is:

   $ sudo apt-get install postfix # installing in 'local only' config is fine
   $ cat > bug-profile << EOF
   profile bug-profile flags=(attach_disconnected) {
 network,
 file,
   }
   EOF
   $ sudo apparmor_parser -r bug.profile 
   $ aa-exec -p bug-profile -- mailq
   Mail queue is empty

   A failed test case will see the mailq command exit with an error:

   $ aa-exec -p bug-profile -- mailq
   postqueue: warning: close: Permission denied

   and these denials will be found in the syslog:

   Jan 25 16:56:29 sec-vivid-amd64 kernel: [  241.096168] audit: type=1400 
audit(1453762589.727:29): apparmor="DENIED" operation="file_perm" 
profile="bug-profile" name="public/showq" pid=4923 comm="postqueue" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
   Jan 25 16:56:29 sec-vivid-amd64 kernel: [  241.096175] audit: type=1400 
audit(1453762589.727:30): apparmor="DENIED" operation="file_perm" 
profile="bug-profile" name="public/showq" pid=4923 comm="postqueue" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  [Regression Potential]

   * The changes are local to the path-based AF_UNIX stream socket mediation 
code
 so that limits the regression potential to some degree.

   * John Johansen authored the patch and I reviewed it. It is small and there's
 no obvious areas of concern to me regarding potential regressions.

  [Other Info]

   * None at this time

  [Original bug report]

  Hello,

  on three Vivid host, all of them up-to-date, I have the problem
  described here:

  https://bugs.launchpad.net/ubuntu/utopic/+source/linux/+bug/1390223

  That bug report shows the problem was fixed, but it is not (at least
  on current Vivid)

  ii  linux-image-generic 3.19.0.15.14   amd64  Generic Linux kernel 
image
  ii  lxc 1.1.2-0ubuntu3 amd64  Linux Containers 
userspace tools
  ii  apparmor2.9.1-0ubuntu9 amd64  User-space parser 
utility for AppArmor

  Reproducible with:

  $ sudo lxc-create -n test -t ubuntu
  $ sudo lxc-start -n test

  (inside container)

  $ sudo apt-get install postfix
  $ mailq
  postqueue: warning: close: Permission denied

  dmesg shows:
  [82140.386109] audit: type=1400 audit(1429661150.086:17067): 
apparmor="DENIED" operation="file_perm" profile="lxc-container-default" 
name="public/showq" pid=27742 comm="postqueue" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0
  ---
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  zoolook1913 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.04
  HibernationDevice: RESUME=UUID=aa25401d-0553-43dc-b7c8-c530fe245fb6
  InstallationDate: Installed on 2015-02-27 (53 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: LENOVO 20150
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-15-generic N/A
   linux-backports-modules-3.19.0-15-generic  N/A
   linux-firmware 1.143
  Tags:  vivid
  Uname: Linux 3.19.0-15-generic x86_64
  UpgradeStatus: Upgraded to vivid on 2015-03-29 (24 days ago)
  UserGroups: adm docker libvirtd lpadmin sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/19/2012
  

  1   2   >