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

[Brad Figg]

tests ran: 153, failed: 0;
  
http://kernel.ubuntu.com/testing/3.16.0-52.71~14.04.1/onza__3.16.0-52.71~14.04.1__2015-10-27_04-46-00/results-index.html

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

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

Bug description:
  This bug is for tracking the 3.16.0-52.71~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, 23. October 2015 13:30 UTC
  kernel-stable-Prepare-package-end:Saturday, 24. October 2015 00:02 UTC
  kernel-stable-Promote-to-proposed-start:Saturday, 24. October 2015 00:02 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:38 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Certification-testing-start:Monday, 26. October 2015 19:03 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:03 UTC

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

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

[Kernel-packages] [Bug 1510405] [NEW] Direct firmware load for radeon/kaveri_sdma1.bin failed with error -2

[Timothy Lyanguzov]

Public bug reported:

Version 1.149 of the package does not have
/lib/firmware/radeon/kaveri_sdma1.bin needed for the latest AMD DRM
module.

After booting my monitor is blank.

For other AMD chipsets *_sdma1.bin is needed as well:
drivers/gpu/drm/amd/amdgpu/cik_sdma.c(126): snprintf(fw_name, sizeof(fw_name), 
"radeon/%s_sdma1.bin", chip_name);

Similar to https://bugs.launchpad.net/ubuntu/+source/linux-
firmware/+bug/1183777, https://bugs.launchpad.net/ubuntu/+source/linux-
firmware/+bug/1218691

Best regards,
Timothy

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

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

Title:
  Direct firmware load for radeon/kaveri_sdma1.bin failed with error -2

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Version 1.149 of the package does not have
  /lib/firmware/radeon/kaveri_sdma1.bin needed for the latest AMD DRM
  module.

  After booting my monitor is blank.

  For other AMD chipsets *_sdma1.bin is needed as well:
  drivers/gpu/drm/amd/amdgpu/cik_sdma.c(126): snprintf(fw_name, 
sizeof(fw_name), "radeon/%s_sdma1.bin", chip_name);

  Similar to https://bugs.launchpad.net/ubuntu/+source/linux-
  firmware/+bug/1183777, https://bugs.launchpad.net/ubuntu/+source
  /linux-firmware/+bug/1218691

  Best regards,
  Timothy

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

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

[Kernel-packages] [Bug 1510301] Re: Graphics corruption with nouveau

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Graphics corruption with nouveau

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Wily, I'm experiencing severe graphics corruption
  in KDE/Plasma. My graphics card is "01:00.0 VGA compatible controller:
  NVIDIA Corporation GT218M [NVS 3100M] (rev a2)" and I use the nouveau
  drivers. My problem matches that of Freedesktop.org bug 92504 [1] and
  applying the patch from its comment 23 [2] seems to alleviate my
  problem.

  After correcting line numbers, the patch applies cleanly to the Wily
  kernel. I do not understand the nouveau code or the patch, but it
  seems the patch could easily be backported to correct a severe problem
  that surely affects a lot of users.

  [1] https://bugs.freedesktop.org/show_bug.cgi?id=92504
  [2] http://lists.freedesktop.org/archives/nouveau/2015-October/022732.html

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

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

[Kernel-packages] [Bug 1509341] Re: linux: 3.13.0-67.110 -proposed tracker

[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 in Ubuntu.
https://bugs.launchpad.net/bugs/1509341

Title:
  linux: 3.13.0-67.110 -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 package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.13.0-67.110 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, 23. October 2015 12:44 UTC
  kernel-stable-Prepare-package-end:Friday, 23. October 2015 20:04 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 23. October 2015 20:04 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:37 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:01 UTC
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:01 UTC
  kernel-stable-Certification-testing-start:Monday, 26. October 2015 19:01 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:01 UTC

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

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

[Kernel-packages] [Bug 1412730] Re: DELL U2415 monitor detection issue

[Michiel Janssens]

Hi Christopher, you are right. Thanks for guiding this in the right direction.
This is the first time for me digging this deep into the kernel, but happy to 
learn.

I will do bisecting as described in the article and will report back.

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

Title:
  DELL U2415 monitor detection issue

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My Laptop HP Elitebook 8740w has two external screens connected, 1
  DELL U2412M connected to vga connector, and 1 DELL U2415 connected to
  Displayport.

  When booting up and with screens attached and active, the 2415 boots in 
1024x768 resolution, the 2412 boots at the same moment in 1920x1200 as it 
should. At the point where the login screen appears the 2415 goes in power save 
mode, most of the time. After logging in, turning the 2415 off and on, 
sometimes helps the get the screen active (out of power save).
  When it gets active, the resolution is 1024x768, not 1920x1200.
  In unity-control-center in display settings the 2415 is displayed as "Unknown 
Display" and the maximum resolution I can select is 1024x768.

  Current partial workaround:
  xorg.conf with monitor section for 1920x1200 as in attachment.
  This doesn't solve booting in 1024x768, but solves the resolution after 
logging in. unity-control-center still lists "Unknown Screen"

  Tried Windows 8.1, no issues with both screens.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.6
  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
  Date: Tue Jan 20 10:48:24 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   vboxhost, 4.3.20, 3.13.0-40-generic, x86_64: installed
   vboxhost, 4.3.20, 3.13.0-43-generic, x86_64: installed
   vboxhost, 4.3.20, 3.13.0-44-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Broadway XT [Mobility Radeon HD 5870] 
[1002:68a0] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company FirePro M7820 [103c:1520]
  InstallationDate: Installed on 2014-05-11 (253 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP EliteBook 8740w
  PccardctlStatus:
   Socket 0:
     3.3V
    16-bit
    PC Card
     Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcKernelCmdLine: BOOT_IMAGE=/@trusty/boot/vmlinuz-3.13.0-44-generic 
root=UUID=cfafe8f3-4766-4fc7-b6f3-857eefcd2aff ro rootflags=subvol=@trusty 
plymouth:debug splash quiet drm.debug=0xe radeon.audio=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2014
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CAD Ver. F.50
  dmi.board.name: 1520
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 33.31
  dmi.chassis.asset.tag: CNU1152Q9W
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CADVer.F.50:bd07/07/2014:svnHewlett-Packard:pnHPEliteBook8740w:pvr:rvnHewlett-Packard:rn1520:rvrKBCVersion33.31:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8740w
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.3
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Jan 20 09:37:08 2015
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.6
  xserver.video_driver: radeon
  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  

[Kernel-packages] [Bug 1509362] fozzie (i386) - tests ran: 153, failed: 0

[Brad Figg]

tests ran: 153, failed: 0;
  
http://kernel.ubuntu.com/testing/3.16.0-52.71~14.04.1/fozzie__3.16.0-52.71~14.04.1__2015-10-27_04-42-00/results-index.html

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

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

Bug description:
  This bug is for tracking the 3.16.0-52.71~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, 23. October 2015 13:30 UTC
  kernel-stable-Prepare-package-end:Saturday, 24. October 2015 00:02 UTC
  kernel-stable-Promote-to-proposed-start:Saturday, 24. October 2015 00:02 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:38 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Certification-testing-start:Monday, 26. October 2015 19:03 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:03 UTC

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

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

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

[Brad Figg]

tests ran: 153, failed: 0;
  
http://kernel.ubuntu.com/testing/3.16.0-52.71~14.04.1/onibi__3.16.0-52.71~14.04.1__2015-10-27_05-39-00/results-index.html

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

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

Bug description:
  This bug is for tracking the 3.16.0-52.71~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, 23. October 2015 13:30 UTC
  kernel-stable-Prepare-package-end:Saturday, 24. October 2015 00:02 UTC
  kernel-stable-Promote-to-proposed-start:Saturday, 24. October 2015 00:02 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:38 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Certification-testing-start:Monday, 26. October 2015 19:03 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:03 UTC

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

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

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

[bugproxy]

--- Comment From mainam...@in.ibm.com 2015-10-27 06:13 EDT---
*** Bug 128832 has been marked as a duplicate of this bug. ***

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

Title:
  ppc64el should use 'deadline' as default io scheduler

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Fix Released

Bug description:
  [Impact]
  Using cfq instead of deadline as the default io scheduler starves certain 
workloads and causes performance issues. In addition every other arch we build 
uses deadline as the default scheduler.

  [Fix]
  Change the configuration to the following for ppc64el:
  CONFIG_DEFAULT_DEADLINE=y
  CONFIG_DEFAULT_IOSCHED="deadline"

  [Test Case]
  Boot and cat /sys/block/*/queue/scheduler to see if deadline is being used.

  --

  -- Problem Description --

  Firestone system given to DASD group failed HTX overnight test with 
miscompare error.
  HTX mdt.hdbuster was running on secondary drive and failed about 12 hours 
into test

  HTX miscompare analysis:
  -==

  Device under test: /dev/sdb
  Stanza running: rule_3
  miscompare offset: 0x40
  Transfer size: Random Size
  LBA number: 0x70fc
  miscompare length: all the blocks in the transfer size

  *- STANZA 3: Creates number of threads twice the queue depth. Each thread  -*
  *- doing 2 num_oper with RC operation with xfer size between 1 block   -*
  *- to 256K.-*

  This miscompare shows read operation is unable to get the expected
  data from the disk. The re-read buffer also shows the same data as the
  first read operation. Since the first read and next re-read shows same
  data, there could be a write operation (of previous rule stanza to
  initialize disk with pattern 007 ) failure on the disk. The same
  miscompare behavior shows for all the blocks in the transfer size.

  /dev/sdb  Jun  2 02:29:43 2015 err=03b6 sev=2 hxestorage  
<<===  device name (/dev/sdb)
  rule_3_13  numopers= 2  loop=   767  blk=0x70fc len=89088
   min_blkno=0 max_blkno=0x74706daf, RANDOM access
  Seed Values= 37303, 290, 23235
  Data Pattern Seed Values = 37303, 291, 23235
  BWRC LBA fencepost Detail:
  th_nummin_lba  max_lba  status
   0 01c9be3ffR
   1  1d1c1b6c3a3836d7F
   2  3a3836d857545243F
   3  5754524474706dafF
  Miscompare at buffer offset 64 (0x40) <<===   
miscompare offset (0x40)
  (Flags: badsig=0; cksum=0x6)  Maximum LBA = 0x74706daf
  wbuf (baseaddr 0x3ffe1c0e6600) b0ff
  rbuf (baseaddr 0x3ffe1c0fc400) 850100fc700200fd700300fe700400ff7005
  Write buffer saved in /tmp/htxsdb.wbuf1
  Read buffer saved in /tmp/htxsdb.rbuf1
  Re-read fails compare at offset64; buffer saved in /tmp/htxsdb.rerd1
  errno: 950(Unknown error 950)

  Asghar reproduced that HTX hang he is seeing. Looking in the kernel
  logs I see some messages from the kernel that there are user threads
  blocked on getting reads serviced. So likely HTX is seeing the same
  thing. I've asked Asghar to try using the deadline I/O scheduler
  rather than CFQ to see if that makes any difference. If that does not
  make any difference, the next thing to try is reducing the queue depth
  of the device. Right now its 31, which I think is pretty high.

  Step 1:

  echo deadline > /sys/block/sda/queue/scheduler
  echo deadline > /sys/block/sdb/queue/scheduler

  If that reproduces the issue, go to step 2:

  echo cfq > /sys/block/sda/queue/scheduler
  echo cfq > /sys/block/sdb/queue/scheduler
  echo 8 > /sys/block/sda/device/queue_depth
  echo 8 > /sys/block/sdb/device/queue_depth

  Breno - it looks like the default I/O scheduler + default queue depth
  for the SATA disks in Firestone is not optimal, in that when running a
  heavy I/O workload, we see read starvation occurring, which is making
  the system nearly unusable.

  Once we changed the I/O scheduler from cfq to deadline, all the issues
  went away and the system is able to run the same workload yet still be
  responsive. Suggest we either encourage Canonical to change the
  default I/O scheduler to deadline or at the very least provide
  documentation to encourage our customers to make this change
  themselves.

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

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

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

[Nicolae Istratii]

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

Title:
  [HP Spectre x360 - 13-4010ca] Audio broken, broadwell-U audio
  controller

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

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

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

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

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

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

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

[Kernel-packages] [Bug 736788] Re: 13d3:3304 IMC Networks bluetooth doesn't work

[Martin Wimpress]

Providing linux-firmware-nonfree is installed, this work in Ubuntu
15.10.

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

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

Title:
  13d3:3304 IMC Networks bluetooth doesn't work

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: bluez

  The "13d3:3304 IMC Networks" internal bluetooth module found in Asus
  U36JC notebook is not working in Ubuntu Maverick nor Natty.

  The systems certainly knows about presence of the bluetooth module -
  the icon in status bar is visible and allows to switch it on/off, but
  nothing else works.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 2.6.38-6.34-generic 2.6.38-rc7
  Uname: Linux 2.6.38-6-generic x86_64
  Architecture: amd64
  CheckboxSubmission: 4c3a0145220348e366d02efaed27e66e
  CheckboxSystem: b8f3ec504801f13fc208edb5c785b099
  Date: Thu Mar 17 12:03:47 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
  InterestingModules: sco bnep l2cap btusb bluetooth
  MachineType: ASUSTeK Computer Inc. U36JC
  ProcEnviron:
   LANGUAGE=cs_CZ:en
   PATH=(custom, user)
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-6-generic 
root=UUID=2d566c56-67c7-4af1-a443-a8c80061120c ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: U36JC.205
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: U36JC
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrU36JC.205:bd01/26/2011:svnASUSTeKComputerInc.:pnU36JC:pvr1.0:rvnASUSTeKComputerInc.:rnU36JC:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: U36JC
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
DOWN 
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0

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

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

[Kernel-packages] [Bug 1509664] Re: Samba shares unavailable after suspend

[Christopher M. Penalver]

rpgmaker, could you please test the latest upstream kernel available
from the very top line at the top of the page from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release
names are irrelevant for testing, and please do not test the daily
folder)? Install instructions are available at
https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow
additional upstream developers to examine the issue.

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, Y, and Z are numbers corresponding to the kernel version.

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.

** Description changed:

- I have noticed that after I suspend my laptop and wake it up again the
- samba shares aren't available, sometimes they may be available after an
- unespecific long time but most times, when I really need to access the
- shares, I just restart the laptop and the shares are then made available
- again. The samba server is a NAS that is on at all times. I'm on ubuntu
- 14.04 on a Dell Inspiron 14z n411z.
+ In 14.04 with either nautilus or nemo filemanager, after I suspend my
+ laptop and wake it up again the samba shares aren't always available,
+ sometimes they may be available after an unspecified long time. The
+ samba server is a NAS that is on at all times. Restarting the file
+ manager sometimes works.
  
- What I do sometimes to accelerate the process of the shares appearing is
- to kill and start again the filemanager. It doesn't always works or it
- may just give me the ilusion of working but the results aren't
- deterministic (sometimes after executing 'nemo -q' several times the
- shares may appear again but maybe they were going to appear anyways
- without issuing the command). This is a really annoying bug.
+ WORKAROUND: Restart.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-43-generic 3.13.0-43.72
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  juliodiaz   2171 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  juliodiaz   2171 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Oct 24 09:37:49 2015
  InstallationDate: Installed on 2014-11-08 (350 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Dell System Inspiron N411Z
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=3b120423-c195-4d2b-8438-0775ba0087e1 ro persistent quiet splash 
nomdmonddf nomdmonisw vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-3.13.0-43-generic N/A
-  linux-backports-modules-3.13.0-43-generic  N/A
-  linux-firmware 1.127.10
+  linux-restricted-modules-3.13.0-43-generic N/A
+  linux-backports-modules-3.13.0-43-generic  N/A
+  linux-firmware 1.127.10
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 0NFVTW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: FAB1
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd09/10/2012:svnDellInc.:pnDellSystemInspironN411Z:pvr:rvnDellInc.:rn0NFVTW:rvrFAB1:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System Inspiron N411Z
  dmi.sys.vendor: Dell Inc.

** Package changed: nemo (Ubuntu) => linux (Ubuntu)

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

Title:
  Samba shares unavailable after suspend

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In 14.04 with either nautilus or nemo filemanager, after I suspend my
  laptop and wake it up again the samba 

[Kernel-packages] [Bug 894374] Re: CVE-2011-4330

[Steve Beattie]

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

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

Title:
  CVE-2011-4330

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:
  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-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:
  Fix Released
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:
  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 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-ti-omap4 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  

Re: [Kernel-packages] [Bug 1484159] Re: Qualcomm Atheros Device [168c:0042] (rev 30) not working on Ubuntu

[Rricha Jalota]

Not until now. :/
On 23-Oct-2015 5:41 pm, "Tiago Sarlo"  wrote:

> no news ?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1477505).
> https://bugs.launchpad.net/bugs/1484159
>
> Title:
>   Qualcomm Atheros Device [168c:0042] (rev 30) not working on Ubuntu
>
> Status in linux package in Ubuntu:
>   Triaged
>
> Bug description:
>   Hi,
>   Qualcomm Atheros Device [168c:0042] (rev 30) is not supported by linux
> kernal. Please add support.
>
>   Thanks
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 14.04
>   Package: linux-image-3.13.0-61-generic 3.13.0-61.100
>   ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
>   Uname: Linux 3.13.0-61-generic i686
>   ApportVersion: 2.14.1-0ubuntu3.11
>   Architecture: i386
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  ubuntu14   1658 F pulseaudio
>/dev/snd/controlC1:  ubuntu14   1658 F pulseaudio
>   CurrentDesktop: Unity
>   Date: Wed Aug 12 20:31:24 2015
>   HibernationDevice: RESUME=UUID=0483444a-0d9a-4215-b36b-4aee75fd9ec0
>   InstallationDate: Installed on 2015-08-11 (0 days ago)
>   InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386
> (20140722.2)
>   IwConfig:
>lono wireless extensions.
>
>eth0  no wireless extensions.
>   MachineType: Acer Aspire E5-573
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic
> root=UUID=72a8a100-d5ec-4e9d-8bc5-45695001a29c ro quiet splash vt.handoff=7
>   RelatedPackageVersions:
>linux-restricted-modules-3.13.0-61-generic N/A
>linux-backports-modules-3.13.0-61-generic  N/A
>linux-firmware 1.127.15
>   SourcePackage: linux
>   StagingDrivers: rts5139
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 04/20/2015
>   dmi.bios.vendor: Insyde Corp.
>   dmi.bios.version: V1.11
>   dmi.board.asset.tag: Type2 - Board Asset Tag
>   dmi.board.name: ZORO_BH
>   dmi.board.vendor: Acer
>   dmi.board.version: Type2 - A01 Board Version
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Chassis Manufacturer
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
> dmi:bvnInsydeCorp.:bvrV1.11:bd04/20/2015:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
>   dmi.product.name: Aspire E5-573
>   dmi.product.version: V3.72
>   dmi.sys.vendor: Acer
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484159/+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/1484159

Title:
  Qualcomm Atheros Device [168c:0042] (rev 30) not working on Ubuntu

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Hi,
  Qualcomm Atheros Device [168c:0042] (rev 30) is not supported by linux 
kernal. Please add support.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-61-generic 3.13.0-61.100
  ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
  Uname: Linux 3.13.0-61-generic i686
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu14   1658 F pulseaudio
   /dev/snd/controlC1:  ubuntu14   1658 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Aug 12 20:31:24 2015
  HibernationDevice: RESUME=UUID=0483444a-0d9a-4215-b36b-4aee75fd9ec0
  InstallationDate: Installed on 2015-08-11 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Acer Aspire E5-573
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic 
root=UUID=72a8a100-d5ec-4e9d-8bc5-45695001a29c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-61-generic N/A
   linux-backports-modules-3.13.0-61-generic  N/A
   linux-firmware 1.127.15
  SourcePackage: linux
  StagingDrivers: rts5139
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.11:bd04/20/2015:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-573
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1423796] Re: Unable to mount lvmcache root device at boot time

[Paul TREHIOU]

Is this corrected in the 15.10 ?

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

Title:
  Unable to mount lvmcache root device at boot time

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  I'm experimenting with Vivid Vervet on a virtual machine and tried a
  new LVM feature, lvmcache. I made a cache for the root file system,
  rebuilt the initrd and rebooted the VM.

  At boot time, the system failed to activate the root LV. After some
  investigation, I found out, it's because the initrd is missing some
  essential stuff needed for activating a cached LV.

  The initrd was missing the dm-cache module. I regenerated the initrd
  with explicitly listing dm-cache in /etc/initramfs-tools/modules, but
  the system still can't boot up, because now it is missing the
  /usr/sbin/cache_check utility.

  As SSDs are becoming more and more common, I think it will be common
  to use them as cache for root file systems, thus it is mandatory to
  make sure that an initrd can mount an lvmcached root device when
  necessary, preferably without /etc/initramfs-tools/modules and other
  manual initrd hacking.

  System details:

  Linux lvmvm 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC
  2015 x86_64 x86_64 x86_64 GNU/Linux

  Distributor ID:   Ubuntu
  Description:  Ubuntu Vivid Vervet (development branch)
  Release:  15.04
  Codename: vivid

  LVM version: 2.02.111(2) (2014-09-01)
  Library version: 1.02.90 (2014-09-01)
  Driver version:  4.28.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1423796/+subscriptions

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

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

[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-utopic in Ubuntu.
https://bugs.launchpad.net/bugs/1509362

Title:
  linux-lts-utopic: 3.16.0-52.71~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-utopic package in Ubuntu:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.16.0-52.71~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, 23. October 2015 13:30 UTC
  kernel-stable-Prepare-package-end:Saturday, 24. October 2015 00:02 UTC
  kernel-stable-Promote-to-proposed-start:Saturday, 24. October 2015 00:02 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:38 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Certification-testing-start:Monday, 26. October 2015 19:03 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:03 UTC

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

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

[Kernel-packages] [Bug 1415153] Re: CVE-2011-1350

[Steve Beattie]

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

** 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-armadaxp (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

** Also affects: linux-mako (Ubuntu Xenial)
   Importance: Low
   Status: New

** Also affects: linux-manta (Ubuntu Xenial)
   Importance: Low
   Status: New

** Also affects: linux-goldfish (Ubuntu Xenial)
   Importance: Low
   Status: New

** Also affects: linux-flo (Ubuntu Xenial)
   Importance: Low
   Status: New

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

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

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

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

Title:
  CVE-2011-1350

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

[Kernel-packages] [Bug 887299] Re: CVE-2011-4081

[Steve Beattie]

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

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

Title:
  CVE-2011-4081

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:
  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-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:
  Fix Released
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 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-ti-omap4 source package in Precise:
  Fix Released
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in 

[Kernel-packages] [Bug 1509350] Re: linux: 3.2.0-93.133 -proposed tracker

[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 in Ubuntu.
https://bugs.launchpad.net/bugs/1509350

Title:
  linux: 3.2.0-93.133 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  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 Precise:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Friday, 23. October 2015 13:02 UTC
  kernel-stable-Prepare-package-end:Friday, 23. October 2015 17:05 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 23. October 2015 17:05 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:38 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Certification-testing-start:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:02 UTC

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

-- 
Mailing list: https://launchpad.net/~kernel-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.

[talat Batheesh]

Hi,
Thank you for your effort.
please make sure that interface link is up, in the machine log above we see 
that link test failed "Link Test1".
could you please retest and update.

Yours,
Talat

-- 
You 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 1509798] Re: Kernel panic during install boot in ohci_hcd module

[nenhard]

Similar thing with 4.3, even after plugging out all USB devices.
I think issue might be with AMD chipset and IOMMU.


** Attachment added: "DSC_0016.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509798/+attachment/4506492/+files/DSC_0016.png

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

Title:
  Kernel panic during install boot in ohci_hcd module

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kernel panic if I try to boot USB from installer 15.10 image or reboot after 
dist-upgrade from 15.10 beta to 15.10 release. 
  This happens in kernel 4.2.0-16, but not in older beta 4.1.0-3-generic kernel.

  I have attached picture of kernel panic and 'sudo lspci -vnvn' output.
  --- 
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   nenad  4242 F...m pulseaudio
   /dev/snd/controlC0:  nenad  4242 F pulseaudio
   /dev/snd/controlC1:  nenad  4242 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-02 (84 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150726)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=c2eb7374-dd07-45ee-9402-27e3527a60b8 ro amd_iommu=on 
pci-stub.ids=1002:665d,1002:aac0,13f6:0111
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-generic N/A
   linux-backports-modules-4.1.0-3-generic  N/A
   linux-firmware   1.149
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd01/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1510213] Re: Regression: Stable kernel update to 3.13.0-66 breaks UDP sockets

[Luis Henriques]

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

Thank you, this seems to be a duplicate of bug #1508510 which has been
fixed already in -proposed.

** This bug has been marked a duplicate of bug 1508510
   Something in the Kernel crashes when I try to mount via NFS

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

Title:
  Regression: Stable kernel update to 3.13.0-66 breaks UDP sockets

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am running the 3.13 series kernel on Ubuntu 14.04 LTS (Trusty Tahr).

  A change introduced in version 3.13.0-66.108 of this kernel breaks UDP
  sockets under certain circumstances. The effect is that the recvfrom
  operation returns with an error, setting errno to EFAULT, even though
  the pointers passed to recvfrom are okay.

  Using bisection, I could track down this problem to a single change:

  2dde51aa53393a531b493e3a8194e4d467e194a3 is the first bad commit
  commit 2dde51aa53393a531b493e3a8194e4d467e194a3
  Author: Herbert Xu 
  Date:   Mon Jul 13 20:01:42 2015 +0800

  net: Fix skb csum races when peeking
  
  BugLink: http://bugs.launchpad.net/bugs/1500810
  
  [ Upstream commit 89c22d8c3b278212eef6a8cc66b570bc840a6f5a ]
  
  When we calculate the checksum on the recv path, we store the
  result in the skb as an optimisation in case we need the checksum
  again down the line.
  
  This is in fact bogus for the MSG_PEEK case as this is done without
  any locking.  So multiple threads can peek and then store the result
  to the same skb, potentially resulting in bogus skb states.
  
  This patch fixes this by only storing the result if the skb is not
  shared.  This preserves the optimisations for the few cases where
  it can be done safely due to locking or other reasons, e.g., SIOCINQ.
  
  Signed-off-by: Herbert Xu 
  Acked-by: Eric Dumazet 
  Signed-off-by: David S. Miller 
  Signed-off-by: Kamal Mostafa 
  Signed-off-by: Luis Henriques 

  :04 04 423debc59ddbc7424283e647e609289fd40dc494
  2511e80df4c30a7309737f6b3cee0260269a0ef7 M  net

  Steps to reproduce the problem: Install freeradius, and have a radius
  client connect to the RADIUS server. After a short amount of time,
  freeradius spins at 100% CPU, alternating between a select and
  recvfrom call. The recvfrom call fails every time with error EFAULT.

  As an alternative to freeradius, you can use the following minimal
  program that I wrote that also exhibits this problem:

  #include 

  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int prepare_socket(int port) {
int sock = socket(AF_INET, SOCK_DGRAM, 0);
if (sock < 0) {
  printf("Could not create socket.\n");
  return -1;
}
int opt = 1;
if (setsockopt(sock, SOL_IP, IP_PKTINFO, , sizeof(opt)) < 0) {
  printf("setsockopt failed.\n");
  return -1;
}
struct sockaddr_in bind_addr;
bind_addr.sin_family = AF_INET;
bind_addr.sin_port = htons(port);
bind_addr.sin_addr.s_addr = INADDR_ANY;
int rc = bind(sock, (struct sockaddr *) _addr, sizeof(bind_addr));
if (rc < 0) {
  printf("Could not bind socket.\n");
  return -1;
}
return sock;
  }

  int main(int argc, char **argv) {
int sock = prepare_socket(1812);
if (sock < 0) {
  return 1;
}
for (;;) {
  unsigned char buffer[4];
  struct sockaddr src;
  socklen_t src_len = sizeof(src);
  ssize_t received_len = recvfrom(sock, buffer, sizeof(buffer), MSG_PEEK, 
, _len);
  if (received_len < 0) {
if (errno == EAGAIN) {
  printf("EAGAIN\n");
  continue;
}
printf("recvfrom failed.\n");
perror(NULL);
return 1;
  }
  if (received_len == 4) {
src_len = sizeof(src);
received_len = recvfrom(sock, buffer, sizeof(buffer), 0, , 
_len);
if (received_len != 4) {
  printf("Strange received length.\n");
  return 1;
}
  }
}
/* Never reached */
return 0;
  }

  However, I did not find out how to craft the traffic that triggers the
  bug. However, the traffic from a RADIUS client (a WiFi AP in my case)
  reliably triggers the bug after a few seconds.

  As this is perfectly legal code and the problem only appears with the
  change introduced earlier, I think that this is a regression and the
  change in question should be removed from the stable kernel tree.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-66-generic 3.13.0-66.108
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 

[Kernel-packages] [Bug 1510247] Re: Last kernel breaks aMule's kad UDP Sockets

[Luis Henriques]

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

This is likely a duplicate of bug #1508510.  I'm marking it as such,
please have a look at that bug and see if the test kernel or the kernel
currently in -proposed fixes this issue for you.  Thanks!

** This bug has been marked a duplicate of bug 1508510
   Something in the Kernel crashes when I try to mount via NFS

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

Title:
  Last kernel breaks aMule's kad UDP Sockets

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The last kernel update: linux-image-3.13.0-63-generic:amd64
  (3.13.0-63.103) makes aMule unable to connect to kad net. Neither UPnP
  nor manually assigned IP:Ports work.

  Here is aMule's error message: MuleUDPSocket: Client UDP-SocketSocket died, 
recreating.
  It is repeated in an infinite loop, always trying to connect to established 
kad UDP port.

  It is not an aMule bug, it appeared when I rebooted the system after
  the last kernel upgrade.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-63-generic:amd64 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-66-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  diego  2395 F pulseaudio
   /dev/snd/controlC0:  diego  2395 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 26 20:27:35 2015
  HibernationDevice: RESUME=UUID=bbe06c01-6bcc-4c59-b165-6dca08ad6886
  InstallationDate: Installed on 2015-01-09 (290 days ago)
  InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140723)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-66-generic 
root=UUID=48e0f8a2-b16d-4449-971a-21be22d6d7f0 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-66-generic N/A
   linux-backports-modules-3.13.0-66-generic  N/A
   linux-firmware 1.127.15
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0308
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A58M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0308:bd02/20/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA58M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 899463] Re: CVE-2011-1162

[Steve Beattie]

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

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

Title:
  CVE-2011-1162

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:
  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-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:
  Fix Released
Status in linux source package in Precise:
  Invalid
Status in linux-armadaxp source package in Precise:
  Fix Released
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 in Precise:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-ti-omap4 source package in Precise:
  Fix Released
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  Invalid
Status in linux-lts-backport-oneiric source package in Saucy:
  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-backport-oneiric source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Invalid
Status 

[Kernel-packages] [Bug 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting

[Marc Reymann]

So, there's still no fix for 12.04 in the standard repos? I mean,
Precise is called "LTS" after all.

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

Title:
  lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66:
  AppArmor denies /dev/ptmx mounting

Status in linux package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in lxc source package in Trusty:
  Fix Released

Bug description:
  We are seeing test suite failures under ADT testing with linux, linux-
  lts-utopic and linux-lts-vivid kernels:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_103318@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_103325@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151009_085841@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151009_091723@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_105332@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_114021@/log.gz

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

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

[Kernel-packages] [Bug 1509664] [NEW] Samba shares unavailable after suspend

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

In 14.04 with either nautilus or nemo filemanager, after I suspend my
laptop and wake it up again the samba shares aren't always available,
sometimes they may be available after an unspecified long time. The
samba server is a NAS that is on at all times. Restarting the file
manager sometimes works.

WORKAROUND: Restart.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-43-generic 3.13.0-43.72
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  juliodiaz   2171 F pulseaudio
CurrentDesktop: Unity
Date: Sat Oct 24 09:37:49 2015
InstallationDate: Installed on 2014-11-08 (350 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. Dell System Inspiron N411Z
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic 
root=UUID=3b120423-c195-4d2b-8438-0775ba0087e1 ro persistent quiet splash 
nomdmonddf nomdmonisw vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-43-generic N/A
 linux-backports-modules-3.13.0-43-generic  N/A
 linux-firmware 1.127.10
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/10/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 0NFVTW
dmi.board.vendor: Dell Inc.
dmi.board.version: FAB1
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd09/10/2012:svnDellInc.:pnDellSystemInspironN411Z:pvr:rvnDellInc.:rn0NFVTW:rvrFAB1:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System Inspiron N411Z
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug latest-bios-a06 trusty
-- 
Samba shares unavailable after suspend 
https://bugs.launchpad.net/bugs/1509664
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 893148] Re: CVE-2011-4132

[Steve Beattie]

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

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

Title:
  CVE-2011-4132

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:
  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-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:
  Fix Released
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:
  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 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-ti-omap4 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  

[Kernel-packages] [Bug 911397] Re: CVE-2011-4127

[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: 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: Medium
   Status: Invalid

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

Title:
  CVE-2011-4127

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:
  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-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:
  Fix Released
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:
  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 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-ti-omap4 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in 

[Kernel-packages] [Bug 894369] Re: CVE-2011-4110

[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: 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: Medium
   Status: Invalid

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

Title:
  CVE-2011-4110

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:
  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-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:
  Fix Released
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:
  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 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-ti-omap4 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status 

[Kernel-packages] [Bug 1509341] kili (amd64) - tests ran: 1, failed: 1

[Brad Figg]

tests ran:   1, failed: 1;
  
http://kernel.ubuntu.com/testing/3.13.0-67.110/kili__3.13.0-67.110__2015-10-27_04-44-00/results-index.html

** Description changed:

  This bug is for tracking the 3.13.0-67.110 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, 23. October 2015 12:44 UTC
  kernel-stable-Prepare-package-end:Friday, 23. October 2015 20:04 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 23. October 2015 20:04 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:37 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:01 UTC
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:01 UTC
  kernel-stable-Certification-testing-start:Monday, 26. October 2015 19:01 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:01 UTC
+ kernel-stable-Security-signoff-end:Tuesday, 27. October 2015 09:00 UTC

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

Title:
  linux: 3.13.0-67.110 -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 package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.13.0-67.110 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, 23. October 2015 12:44 UTC
  kernel-stable-Prepare-package-end:Friday, 23. October 2015 20:04 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 23. October 2015 20:04 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:37 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:01 UTC
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:01 UTC
  kernel-stable-Certification-testing-start:Monday, 26. October 2015 19:01 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:01 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:01 UTC
  kernel-stable-Security-signoff-end:Tuesday, 27. October 2015 09:00 UTC

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

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

[Kernel-packages] [Bug 1320070] Re: Realtek Wifi card RTL8723BE drops connection with MSI enabled

[sadegh]

my machin is thinkpad-E550 and #48 worked for me.
uname -a
Linux ThinkPad 3.19.0-25-generic #26~14.04.1-Ubuntu SMP Fri Jul 24 21:16:20 UTC 
2015 x86_64 x86_64 x86_64 GNU/Linux


BUT MODULE VERIFICATION FAILED!  signature is not validu!???  please explain 
what should i do?

$ dmesg | grep rtl
[   10.250033] rtlwifi: module verification failed: signature and/or  required 
key missing - tainting kernel
[   10.510565] Using firmware rtlwifi/rtl8723befw.bin
[   10.513766] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[   10.514272] rtlwifi: wireless switch is on


lspci -v

u04:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe 
Wireless Network Adapter
Subsystem: Lenovo Device b736
Flags: bus master, fast devsel, latency 0, IRQ 18
I/O ports at 4000 [size=256]
Memory at f120 (64-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number 00-23-b7-fe-ff-4c-e0-00
Capabilities: [150] Latency Tolerance Reporting
Capabilities: [158] L1 PM Substates
Kernel driver in use: rtl8723be

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

Title:
  Realtek Wifi card RTL8723BE drops connection with MSI enabled

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

Bug description:
  As my testing result with ThinkPad E540 and other users' report[1],
  RTL8723BE drops connection with MSI enabled, need to backport
  329d6e299f92a591acb3a80f6d597a5f9dce7e6d "rtlwifi: rtl8723be: disable
  MSI interrupts mode"

  [1] https://bugs.launchpad.net/bugs/1240940

  Tips for RTL8188EE [10ec:8179] and RTL8723BE [10ec:b723] users: those
  hardware modules have MSI compatibility issue, on some certain
  platforms they work fine with MSI but break connections without MSI,
  on some other certain platforms it's opposite. You could try to toggle
  its module parameter "msi"

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

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

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

[Kernel-packages] [Bug 1449910] Re: System hangs apparently randomly when disconnecting iScsi volumes

[Roberto]

After another month of testing, the mainline kernel never failed. So, is
this bug fixed in some release version of the 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/1449910

Title:
  System hangs apparently randomly when disconnecting iScsi volumes

Status in linux package in Ubuntu:
  Triaged

Bug description:
  We have several servers here which mount Ubuntu LTS Trusty Tahr 14.04. We use 
LVM snapshots to do backups during the night. Randomly (witha rate of 1 event 
every 10-12 days) the LVM snapshot creation runs in some problem. The server 
hangs and it must be rebooted hardly. No shell, no even any screen output, just 
a black screen, no ping, nothing. And Magic SysRq key doesn't help.
  No logs are written either (I also tried redirect logs to another machine, 
just in case). This happens with different hardware, and different backup 
software. The only constant is LVM snapshots. Kernel is 3.13.0-49. We tried the 
14.10 kernel (3.16.0-34), we had the same hangs, but this time we had something 
logged:

  Apr 21 23:02:56 server-name kernel: [654840.108023] INFO: task kswapd0:50 
blocked for more than 120 seconds.
  Apr 21 23:02:56 server-name kernel: [654840.108145]   Not tainted 
3.16.0-34-generic #47~14.04.1-Ubuntu
  Apr 21 23:02:56 server-name kernel: [654840.108245] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Apr 21 23:02:56 server-name kernel: [654840.108361] kswapd0 D 
88007fc130c0 050  2 0x
  Apr 21 23:02:56 server-name kernel: [654840.108367]  880077bcf998 
0046 880077bd 880077bcffd8
  Apr 21 23:02:56 server-name kernel: [654840.108372]  000130c0 
000130c0 88007bdef010 c90010d3c000
  Apr 21 23:02:56 server-name kernel: [654840.108377]  c90010d3c0d8 
  c90010d3c000
  Apr 21 23:02:56 server-name kernel: [654840.108382] Call Trace:
  /0x70
  Apr 21 23:02:56 server-name kernel: [654840.108419]  [] 
reiserfs_wait_on_write_block+0x4d/0x80 [reiserfs]
  Apr 21 23:02:56 server-name kernel: [654840.108426]  [] ? 
prepare_to_wait_event+0x100/0x100
  Apr 21 23:02:56 server-name kernel: [654840.108437]  [] 
do_journal_begin_r+0xe1/0x3e0 [reiserfs]
  Apr 21 23:02:56 server-name kernel: [654840.108443]  [] ? 
__enqueue_entity+0x78/0x80
  Apr 21 23:02:56 server-name kernel: [654840.108454]  [] 
journal_begin+0x8a/0x160 [reiserfs]
  Apr 21 23:02:56 server-name kernel: [654840.108464]  [] 
reiserfs_release_dquot+0x4c/0xd0 [reiserfs]
  Apr 21 23:02:56 server-name kernel: [654840.108470]  [] ? 
__percpu_counter_add+0x51/0x70
  Apr 21 23:02:56 server-name kernel: [654840.108476]  [] 
dqput+0x9d/0x200
  Apr 21 23:02:56 server-name kernel: [654840.108480]  [] 
__dquot_drop+0x5d/0x70
  Apr 21 23:02:56 server-name kernel: [654840.108485]  [] 
dquot_drop+0x2d/0x40
  Apr 21 23:02:56 server-name kernel: [654840.108494]  [] 
reiserfs_evic
  t_inode+0xa0/0x180 [reiserfs]
  Apr 21 23:02:56 server-name kernel: [654840.108501]  [] ? 
inode_wait_for_writeback+0x2e/0x40
  Apr 21 23:02:56 server-name kernel: [654840.108507]  [] 
evict+0xb4/0x180
  Apr 21 23:02:56 server-name kernel: [654840.108511]  [] 
dispose_list+0x39/0x50
  Apr 21 23:02:56 server-name kernel: [654840.108515]  [] 
prune_icache_sb+0x47/0x60
  Apr 21 23:02:56 server-name kernel: [654840.108520]  [] 
super_cache_scan+0x105/0x170
  Apr 21 23:02:56 server-name kernel: [654840.108526]  [] 
shrink_slab_node+0x138/0x290
  Apr 21 23:02:56 server-name kernel: [654840.108532]  [] ? 
css_next_descendant_pre+0x3b/0x40
  Apr 21 23:02:56 server-name kernel: [654840.108536]  [] 
shrink_slab+0x8b/0x160
  Apr 21 23:02:56 server-name kernel: [654840.108540]  [] 
balance_pgdat+0x3f2/0x620
  Apr 21 23:02:56 server-name kernel: [654840.108544]  [] 
kswapd+0x15b/0x3f0
  Apr 21 23:02:56 server-name kernel: [654840.108549]  [] ? 
prepare_to_wait_event+0x100/0x100
  Apr 21 23:02:56 server-name kernel: [654840.108552]  [] ? 
balance_pgdat+0x620/0x620
  Apr 21 23:02:56 server-name kernel: [654840.108558]  [] 
kthread+0xd2/0xf0
  Apr 21 23:02:56 server-name kernel: [654840.108562]  [] ? 
kthread_create_on_node+0x1c0/0x1c0
  Apr 21 23:02:56 server-name kernel: [654840.108567]  [] 
ret_from_fork+0x7c/0xb0
  Apr 21 23:02:56 server-name kernel: [654840.108571]  [] ? 
kthread_create_on_node+0x1c0/0x1c0
  Apr 21 23:02:56 server-name kernel: [654840.108595] INFO: task 
kworker/1:1:25606 blocked for more than 120 seconds.
  Apr 21 23:02:56 server-name kernel: [654840.108709]   Not tainted 
3.16.0-34-generic #47~14.04.1-Ubuntu
  Apr 21 23:02:56 server-name kernel: [654840.108809] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
  Apr 21 23:02:56 server-name kernel: [654840.108923] kworker/1:1 D 
88007fc530c0 0 25606  2 0x
  Apr 21 23:02:56 server-name kernel: 

[Kernel-packages] [Bug 1509803] Re: Bluetooth Will not work

[Jeremy]

Your firmware file isn't named correctly

sudo mv /lib/firmware/brcm/BCM43142A0-105b:e065.hcd
/lib/firmware/brcm/BCM43142A0-105b-e065.hcd

Then try Pilot6's fix

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

Title:
  Bluetooth Will not work

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  I have an issue with my Bluetooth, in a Lenovo 50-70.  It will not
  turn on, and if I try to turn it on, it gives the messsage that no
  adapters found.  I tied converting the .hex windows driver t .hcd, but
  that didn't help.  Below is my info:

  02:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n 
[14e4:4365] (rev 01)
  Subsystem: Lenovo Device [17aa:0621]
  Kernel driver in use: wl
  Bus 003 Device 002: ID 8087:8000 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 105b:e065
  Bus 001 Device 004: ID 5986:055d Acer, Inc
  Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
  Bus 001 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical 
Mouse
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  
  dmesg | grep -i blue
  [ 36.077001] Bluetooth: Core ver 2.20
  [ 36.077016] Bluetooth: HCI device and connection manager initialized
  [ 36.077018] Bluetooth: HCI socket layer initialized
  [ 36.077020] Bluetooth: L2CAP socket layer initialized
  [ 36.077024] Bluetooth: SCO socket layer initialized
  [ 36.165964] Bluetooth: RFCOMM TTY layer initialized
  [ 36.165973] Bluetooth: RFCOMM socket layer initialized
  [ 36.165978] Bluetooth: RFCOMM ver 1.11
  [ 36.192237] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [ 36.192239] Bluetooth: BNEP filters: protocol multicast
  [ 36.192242] Bluetooth: BNEP socket layer initialized
  ls -l /lib/firmware/brcm
  total 7716
  -rw-rw-r-- 1 root root 28263 Oct 23 22:38 BCM43142A0-105b:e065.hcd
  -rw-r--r-- 1 root root 269595 Nov 24 2014 bcm4329-fullmac-4.bin
  -rw-r--r-- 1 root root 96224 Dec 1 2014 bcm43xx-0.fw
  -rw-r--r-- 1 root root 180 Dec 1 2014 bcm43xx_hdr-0.fw
  -rw-r--r-- 1 root root 397312 Dec 1 2014 brcmfmac43143.bin
  -rwxr-xr-x 1 root root 385067 Sep 24 16:20 brcmfmac43143-sdio.bin
  -rw-r--r-- 1 root root 348160 Nov 24 2014 brcmfmac43236b.bin
  -rw-r--r-- 1 root root 455745 Dec 1 2014 brcmfmac43241b0-sdio.bin
  -rw-r--r-- 1 root root 403855 Dec 1 2014 brcmfmac43241b4-sdio.bin
  -rw-r--r-- 1 root root 479232 Sep 24 16:20 brcmfmac43242a.bin
  -rw-r--r-- 1 root root 253748 Dec 1 2014 brcmfmac4329-sdio.bin
  -rw-r--r-- 1 root root 222126 Dec 1 2014 brcmfmac4330-sdio.bin
  -rw-r--r-- 1 root root 451566 Dec 1 2014 brcmfmac4334-sdio.bin
  -rw-r--r-- 1 root root 569291 Dec 1 2014 brcmfmac4335-sdio.bin
  -rw-r--r-- 1 root root 219557 Dec 1 2014 brcmfmac43362-sdio.bin
  -rw-r--r-- 1 root root 493599 Sep 24 16:20 brcmfmac4339-sdio.bin
  -rw-r--r-- 1 root root 507752 Sep 24 16:13 brcmfmac4354-sdio.bin
  -rw-r--r-- 1 root root 557056 Sep 24 16:20 brcmfmac43569.bin
  -rw-r--r-- 1 root root 550333 Sep 24 16:20 brcmfmac43570-pcie.bin
  -rw-r--r-- 1 root root 588940 Sep 24 16:20 brcmfmac43602-pcie.ap.bin
  -rw-r--r-- 1 root root 590544 Sep 24 16:20 brcmfmac43602-pcie.bin
  lspci -knn | grep Net -A2; lsusb
  02:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n 
[14e4:4365] (rev 01)
  Subsystem: Lenovo Device [17aa:0621]
  Kernel driver in use: wl
  Bus 003 Device 002: ID 8087:8000 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 105b:e065
  Bus 001 Device 004: ID 5986:055d Acer, Inc
  Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
  Bus 001 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical 
Mouse
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  
  After loading the .hcd file I get this

  dmesg | grep -i blue
  [ 24.144917] Bluetooth: Core ver 2.20
  [ 24.144932] Bluetooth: HCI device and connection manager initialized
  [ 24.144935] Bluetooth: HCI socket layer initialized
  [ 24.144937] Bluetooth: L2CAP socket layer initialized
  [ 24.144941] Bluetooth: SCO socket layer initialized
  [ 24.191155] Bluetooth: RFCOMM TTY layer initialized
  [ 24.191162] Bluetooth: RFCOMM socket layer initialized
  [ 24.191167] Bluetooth: RFCOMM ver 1.11
  [ 24.215839] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [ 24.215842] Bluetooth: BNEP filters: protocol multicast
  [ 24.215845] Bluetooth: BNEP socket layer initialized

  I have tried about everything I could find out there, and nothing
  helped.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-32-generic 3.19.0-32.37~14.04.1
  

[Kernel-packages] [Bug 1415158] Re: CVE-2011-1352

[Steve Beattie]

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

** 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-armadaxp (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

** Also affects: linux-mako (Ubuntu Xenial)
   Importance: High
   Status: New

** Also affects: linux-manta (Ubuntu Xenial)
   Importance: High
   Status: New

** Also affects: linux-goldfish (Ubuntu Xenial)
   Importance: High
   Status: New

** Also affects: linux-flo (Ubuntu Xenial)
   Importance: High
   Status: New

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

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

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

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

Title:
  CVE-2011-1352

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

[Kernel-packages] [Bug 880893] Re: CVE-2011-3347

[Steve Beattie]

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

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

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

Title:
  CVE-2011-3347

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:
  New
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-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:
  Fix Released
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 in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-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-ti-omap4 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  Invalid

[Kernel-packages] [Bug 899466] Re: CVE-2011-2203

[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: 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: Medium
   Status: Invalid

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

Title:
  CVE-2011-2203

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:
  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-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:
  Fix Released
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:
  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 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-ti-omap4 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status 

[Kernel-packages] [Bug 887298] Re: CVE-2011-4077

[Steve Beattie]

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

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

Title:
  CVE-2011-4077

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:
  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-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:
  Fix Released
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:
  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 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-ti-omap4 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package in Saucy:
  

[Kernel-packages] [Bug 1508510] Re: Something in the Kernel crashes when I try to mount via NFS

[Andreas Bouché]

I can confirm that, too. No issue with kernel 3.13.0-67 from trusty-
proposed.

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

Title:
  Something in the Kernel crashes when I try to mount via NFS

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

Bug description:
  I have a vagrant virtual machine that mounts a directory on my
  computer via NFS, this does not work and the reason seems to be this.
  My System is using SMP, reverting to the kernel before solves the
  problem.

  Broken: Linux paul-ThinkPad-T430s 3.13.0-66-generic
  Working: Broken: Linux paul-ThinkPad-T430s 3.13.0-65-generic
   
  BUG: unable to handle kernel NULL pointer dereference at 0008
  [   84.360198] IP: [] 
skb_copy_and_csum_datagram_iovec+0x2d/0x110
  [   84.360224] PGD 0 
  [   84.360232] Oops:  [#1] SMP 
  [   84.360246] Modules linked in: ctr ccm pci_stub vboxpci(OX) vboxnetadp(OX) 
vboxnetflt(OX) vboxdrv(OX) vmw_vsock_vmci_transport vsock vmw_vmci rfcomm bnep 
arc4 iwldvm mac80211 hid_generic usbhid hid snd_hda_codec_hdmi 
snd_hda_codec_realtek iwlwifi cfg80211 binfmt_misc nfsd auth_rpcgss nfs_acl nfs 
lockd sunrpc fscache nls_iso8859_1 uvcvideo videobuf2_vmalloc videobuf2_memops 
videobuf2_core videodev cdc_mbim cdc_ncm usbnet mii cdc_wdm cdc_acm btusb 
bluetooth intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel 
kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 
lrw gf128mul glue_helper ablk_helper cryptd joydev serio_raw snd_hda_intel 
snd_hda_codec snd_hwdep thinkpad_acpi nvram snd_pcm snd_seq_midi lpc_ich 
snd_seq_midi_event snd_rawmidi shpchp snd_page_alloc mei_me mei i915 snd_seq 
drm_kms_helper drm i2c_algo_bit parport_pc wmi snd_seq_device snd_timer ppdev 
snd soundcore lp mac_hid parport video mmc_block psmouse e1000e ahci sdhci_pci 
libahc
 i ptp sdhci pps_core
  [   84.360613] CPU: 2 PID: 1507 Comm: nfsd Tainted: G   OX 
3.13.0-66-generic #108-Ubuntu
  [   84.360643] Hardware name: LENOVO 2355CTO/2355CTO, BIOS G7ET95WW (2.55 ) 
07/10/2013
  [   84.360673] task: 880036929800 ti: 880036b7a000 task.ti: 
880036b7a000
  [   84.360696] RIP: 0010:[]  [] 
skb_copy_and_csum_datagram_iovec+0x2d/0x110
  [   84.360728] RSP: 0018:880036b7bbc0  EFLAGS: 00010216
  [   84.360743] RAX:  RBX: 880035910700 RCX: 

  [   84.360762] RDX:  RSI: 0030 RDI: 
88038e23ab00
  [   84.360781] RBP: 880036b7bbf8 R08:  R09: 
62e59d1a
  [   84.360800] R10:  R11: 0004 R12: 
0008
  [   84.360819] R13: 88038e23ab00 R14: 0028 R15: 
88038e23ab00
  [   84.360838] FS:  () GS:88043e28() 
knlGS:
  [   84.360859] CS:  0010 DS:  ES:  CR0: 80050033
  [   84.360874] CR2: 0008 CR3: 000425ea CR4: 
001427e0
  [   84.360893] Stack:
  [   84.360900]  81616f66 81616fb0 880035910700 
880036b7bdf8
  [   84.360924]   0028 88038e23ab00 
880036b7bc60
  [   84.360948]  8168b2ec 880426f8c028 880035910770 
0002
  [   84.360972] Call Trace:
  [   84.360984]  [] ? skb_checksum+0x26/0x30
  [   84.361005]  [] ? skb_push+0x40/0x40
  [   84.361025]  [] udp_recvmsg+0x1dc/0x380
  [   84.361046]  [] inet_recvmsg+0x6c/0x80
  [   84.361065]  [] sock_recvmsg+0x9a/0xd0
  [   84.361087]  [] ? del_timer_sync+0x4a/0x60
  [   84.361106]  [] ? schedule_timeout+0x17d/0x2d0
  [   84.361126]  [] kernel_recvmsg+0x3a/0x50
  [   84.361164]  [] svc_udp_recvfrom+0x89/0x440 [sunrpc]
  [   84.361185]  [] ? _raw_spin_unlock_bh+0x1b/0x40
  [   84.361211]  [] ? svc_get_next_xprt+0xd8/0x310 [sunrpc]
  [   84.361237]  [] svc_recv+0x4a0/0x5c0 [sunrpc]
  [   84.361255]  [] ? recalc_sigpending+0x1b/0x50
  [   84.361276]  [] nfsd+0xad/0x130 [nfsd]
  [   84.361295]  [] ? nfsd_destroy+0x80/0x80 [nfsd]
  [   84.361313]  [] kthread+0xd2/0xf0
  [   84.361328]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [   84.361346]  [] ret_from_fork+0x58/0x90
  [   84.361362]  [] ? kthread_create_on_node+0x1c0/0x1c0
  [   84.361383] Code: 44 00 00 55 31 c0 48 89 e5 41 57 41 56 41 55 49 89 fd 41 
54 41 89 f4 53 48 83 ec 10 8b 77 68 41 89 f6 45 29 e6 0f 84 89 00 00 00 <48> 8b 
42 08 48 89 d3 48 85 c0 75 14 0f 1f 80 00 00 00 00 48 83 
  [   84.361514] RIP  [] 
skb_copy_and_csum_datagram_iovec+0x2d/0x110
  [   84.361546]  RSP 
  [   84.361557] CR2: 0008
  [   84.366322] ---[ end trace 

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

[Brad Figg]

tests ran: 194, failed: 0;
  
http://kernel.ubuntu.com/testing/4.2.0-17.21/fozzie__4.2.0-17.21__2015-10-27_07-09-00/results-index.html

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

Title:
  linux: 4.2.0-17.21 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux source package in Wily:
  New

Bug description:
  This bug is for tracking the 4.2.0-17.21 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, 23. October 2015 19:00 UTC
  kernel-stable-Prepare-package-end:Saturday, 24. October 2015 06:03 UTC
  kernel-stable-Promote-to-proposed-start:Saturday, 24. October 2015 06:03 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:39 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:04 UTC
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:04 UTC
  kernel-stable-Certification-testing-start:Monday, 26. October 2015 19:04 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:04 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:04 UTC

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

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

[Kernel-packages] [Bug 1441304] Re: CVE-2011-1149

[Steve Beattie]

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

** 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-armadaxp (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

Title:
  CVE-2011-1149

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

[Kernel-packages] [Bug 1509350] Re: linux: 3.2.0-93.133 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the 3.2.0-93.133 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Friday, 23. October 2015 13:02 UTC
  kernel-stable-Prepare-package-end:Friday, 23. October 2015 17:05 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 23. October 2015 17:05 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:38 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Certification-testing-start:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:02 UTC
+ kernel-stable-Security-signoff-end:Tuesday, 27. October 2015 10: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/1509350

Title:
  linux: 3.2.0-93.133 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
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-lbm series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  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 Precise:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Friday, 23. October 2015 13:02 UTC
  kernel-stable-Prepare-package-end:Friday, 23. October 2015 17:05 UTC
  kernel-stable-Promote-to-proposed-start:Friday, 23. October 2015 17:05 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:38 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Certification-testing-start:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:02 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Security-signoff-end:Tuesday, 27. October 2015 10:00 UTC

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

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

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

[Brad Figg]

** Description changed:

  This bug is for tracking the 3.16.0-52.71~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, 23. October 2015 13:30 UTC
  kernel-stable-Prepare-package-end:Saturday, 24. October 2015 00:02 UTC
  kernel-stable-Promote-to-proposed-start:Saturday, 24. October 2015 00:02 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:38 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Certification-testing-start:Monday, 26. October 2015 19:03 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:03 UTC
+ kernel-stable-Security-signoff-end:Tuesday, 27. October 2015 10:00 UTC

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

Title:
  linux-lts-utopic: 3.16.0-52.71~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-utopic package in Ubuntu:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.16.0-52.71~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, 23. October 2015 13:30 UTC
  kernel-stable-Prepare-package-end:Saturday, 24. October 2015 00:02 UTC
  kernel-stable-Promote-to-proposed-start:Saturday, 24. October 2015 00:02 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:38 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Certification-testing-start:Monday, 26. October 2015 19:03 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:03 UTC
  kernel-stable-Security-signoff-end:Tuesday, 27. October 2015 10:00 UTC

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

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

[Kernel-packages] [Bug 1441303] Re: CVE-2010-5321

[Steve Beattie]

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

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

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

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

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

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

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

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

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

Title:
  CVE-2010-5321

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

[Kernel-packages] [Bug 1504781] Re: lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66: AppArmor denies /dev/ptmx mounting

[Stefan Huehner]

Hi Marc,
please check comment #33 from Serge. He explained that formally lxc in precise 
is not covered by lts.

However a very special case as a LTS update in main in precise (kernel) did 
break unrelated software (lxc) which is a clear regression.
And then not having that other software not in being in main -> skips it from 
LTS is lets say very annoying.

@Robert:
using that higher version of lxc is not a perfect drop-up replacement either as 
usage changed compared to old precise lxc (i.e. no lxc-list anymore but lxc-ls 
-f) and maybe other changes.


We'll probably look into backporting the lxc fix for precise as we have quite a 
few machines affected. But no ETA, so if anybody else here can pick that up 
before that would be very welcome.


@Serge:
Any chance to get some policy statement from Ubuntu here?  As i see maybe that 
example as very special regression caused by lts update should maybe warrant 
fixing items not in main if broken by 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/1504781

Title:
  lxc-test-ubuntu hangs forever in trusty-proposed with Linux 3.13.0-66:
  AppArmor denies /dev/ptmx mounting

Status in linux package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Invalid
Status in lxc source package in Trusty:
  Fix Released

Bug description:
  We are seeing test suite failures under ADT testing with linux, linux-
  lts-utopic and linux-lts-vivid kernels:

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_103318@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_103325@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151009_085841@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151009_091723@/log.gz

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/amd64/l/lxc/20151010_105332@/log.gz
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-trusty/trusty/i386/l/lxc/20151010_114021@/log.gz

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

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

[Kernel-packages] [Bug 1505242] Re: WARNING: ... intel_display.c:11100 intel_check_page_flip

[Christopher M. Penalver]

Serhiy Zahoriya, it will help immensely if you filed a new report with the 
Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

** Tags removed: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.3-rc7

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

Title:
  WARNING: ... intel_display.c:11100 intel_check_page_flip

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I see warnings similar to this occasionally in the dmesg output.
  I first noticed it, when the system refused to put load on all but one core, 
and I tried to find the reason.
  But it happened again a few times, and I did not notice that effect (or any).
  I do not know the trigger. I suspect playing video.
  This is a fresh install of Ubuntu 15.04 on a fresh hardware.

  I found several similar error reports with google. All appeared to be 
unsolved.
  I thought, I submit this report, anyway. Perhaps it provides some new 
information.

  [ 5967.045926] [ cut here ]
  [ 5967.045949] WARNING: CPU: 3 PID: 0 at 
/build/linux-qOmAV7/linux-3.19.0/ubuntu/i915/intel_display.c:11100 
intel_check_page_flip+0x11c/0x130 [i915_bpo]()
  [ 5967.045950] Kicking stuck page flip: queued at 343930, now 343934
  [ 5967.045951] Modules linked in: cfg80211 binfmt_misc dm_crypt nls_iso8859_1 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
eeepc_wmi snd_hda_controller asus_wmi sparse_keymap snd_hda_codec snd_usb_audio 
snd_usbmidi_lib snd_hwdep x86_pkg_temp_thermal snd_pcm coretemp kvm_intel kvm 
snd_seq_midi snd_seq_midi_event crct10dif_pclmul snd_rawmidi ip6t_REJECT 
nf_reject_ipv6 crc32_pclmul ghash_clmulni_intel nf_log_ipv6 snd_seq uvcvideo 
aesni_intel videobuf2_vmalloc videobuf2_memops snd_seq_device aes_x86_64 
videobuf2_core lrw xt_hl gf128mul v4l2_common glue_helper hid_multitouch 
videodev ablk_helper ip6t_rt cryptd snd_timer media snd joydev serio_raw 
i915_bpo nf_conntrack_ipv6 soundcore nf_defrag_ipv6 intel_ips drm_kms_helper 
ipt_REJECT nf_reject_ipv4 drm 8250_fintek nf_log_ipv4
  [ 5967.045968]  nf_log_common i2c_algo_bit i2c_hid shpchp xt_LOG mac_hid 
acpi_pad xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 
xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns 
nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack 
iptable_filter ip_tables x_tables parport_pc ppdev lp parport autofs4 btrfs xor 
raid6_pq hid_generic usbhid hid mxm_wmi e1000e psmouse ptp pps_core ahci 
libahci wmi video
  [ 5967.045984] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 3.19.0-30-generic 
#34-Ubuntu
  [ 5967.045985] Hardware name: System manufacturer System Product Name/Z170-A, 
BIOS 0502 07/14/2015
  [ 5967.045986]  c076c138 88046ed83d68 817c4d5f 
0007
  [ 5967.045987]  88046ed83db8 88046ed83da8 81076a8a 
88046ed83db8
  [ 5967.045988]  88045ac18800 880456f46000 88045ac189a8 

  [ 5967.045990] Call Trace:
  [ 5967.045991][] dump_stack+0x45/0x57
  [ 5967.045997]  [] warn_slowpath_common+0x8a/0xc0
  [ 5967.045999]  [] warn_slowpath_fmt+0x46/0x50
  [ 5967.046011]  [] intel_check_page_flip+0x11c/0x130 
[i915_bpo]
  [ 5967.046021]  [] gen8_irq_handler+0x37e/0x5d0 [i915_bpo]
  [ 5967.046023]  [] ? read_tsc+0x9/0x10
  [ 5967.046026]  [] handle_irq_event_percpu+0x77/0x1a0
  [ 5967.046027]  [] handle_irq_event+0x41/0x70
  [ 5967.046029]  [] handle_edge_irq+0x6e/0x120
  [ 5967.046031]  [] handle_irq+0x22/0x40
  [ 5967.046033]  [] do_IRQ+0x4f/0xf0
  [ 5967.046034]  [] common_interrupt+0x6d/0x6d
  [ 5967.046035][] ? finish_task_switch+0x67/0x150
  [ 5967.046039]  [] __schedule+0x39c/0x8e0
  [ 5967.046041]  [] schedule_preempt_disabled+0x29/0x70
  [ 5967.046043]  [] cpu_startup_entry+0x187/0x3b0
  [ 5967.046045]  [] start_secondary+0x197/0x1c0
  [ 5967.046046] ---[ end trace 6b6de72fa2c286b6 ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.34
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lacko  1507 F pulseaudio
   /dev/snd/controlC0:  lacko  1507 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct 12 15:05:50 2015
  InstallationDate: Installed on 2015-10-10 (2 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1509903] Re: After sleeping or hibernating via the K Menu options, the computer suddenly powers on again by itself, some seconds later, in Kubuntu 15.10

[Martin Pitt]

Thanks. Can you verify that "sudo systemctl suspend" exhibits the same
problem? If not, then it's indeed not a matter of pm-utils and its
quirks.

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

Title:
  After sleeping or hibernating via the K Menu options, the computer
  suddenly powers on again by itself, some seconds later, in Kubuntu
  15.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I recently upgraded from Kubuntu 15.04 to Kubuntu 15.10 and I've
  noticed this failure: when going through the graphical K Menu > Logout
  > Sleep or K Menu > Logout > Hibernate, the computer seems to do the
  corresponding operation fine, but some seconds later the computer
  powers on by itself, undoing the previous order to sleep or hibernate.
  A sample of the corresponding log messages stored in the file
  /var/log/syslog is this:

  Oct 25 18:47:16 hostname NetworkManager[663]:   sleep requested 
(sleeping: no  enabled: yes)
  Oct 25 18:47:16 hostname NetworkManager[663]:   sleeping...
  Oct 25 18:47:16 hostname NetworkManager[663]:   NetworkManager state is 
now ASLEEP
  Oct 25 18:47:16 hostname whoopsie[653]: [18:47:16] offline
  Oct 25 18:47:17 hostname systemd[1]: Reached target Sleep.
  Oct 25 18:47:17 hostname systemd[1]: Starting Suspend...
  Oct 25 18:47:18 hostname systemd-sleep[4848]: Suspending system...
  Oct 25 18:47:21 hostname kernel: [13031.018587] PM: Syncing filesystems ... 
done.
  Oct 25 18:47:21 hostname kernel: [13031.280695] PM: Preparing system for 
sleep (mem)
  Oct 25 18:47:21 hostname kernel: [13031.281033] Freezing user space processes 
... (elapsed 0.075 seconds) done.
  Oct 25 18:47:21 hostname kernel: [13031.357037] Freezing remaining freezable 
tasks ... (elapsed 0.001 seconds) done.
  Oct 25 18:47:21 hostname kernel: [13031.358480] PM: Suspending system (mem)
  Oct 25 18:47:21 hostname kernel: [13031.358604] Suspending console(s) (use 
no_console_suspend to debug)
  Oct 25 18:47:21 hostname kernel: [13031.359627] sd 3:0:0:0: [sda] 
Synchronizing SCSI cache
  Oct 25 18:47:21 hostname kernel: [13031.368742] serial 00:05: disabled
  Oct 25 18:47:21 hostname kernel: [13031.368751] serial 00:05: System wakeup 
disabled by ACPI
  Oct 25 18:47:21 hostname kernel: [13031.368785] i8042 aux 00:04: System 
wakeup disabled by ACPI
  Oct 25 18:47:21 hostname kernel: [13031.368858] parport_hostname 00:03: 
disabled
  Oct 25 18:47:21 hostname kernel: [13031.493405] sd 3:0:0:0: [sda] Stopping 
disk
  Oct 25 18:47:21 hostname kernel: [13031.880050] PM: suspend of devices 
complete after 521.067 msecs
  Oct 25 18:47:21 hostname kernel: [13031.896046] PM: late suspend of devices 
complete after 15.988 msecs
  Oct 25 18:47:21 hostname kernel: [13031.896488] pcieport :00:1c.1: System 
wakeup enabled by ACPI
  Oct 25 18:47:21 hostname kernel: [13031.896660] ehci-pci :00:1d.7: System 
wakeup enabled by ACPI
  Oct 25 18:47:21 hostname kernel: [13031.896690] uhci_hcd :00:1d.3: System 
wakeup enabled by ACPI
  Oct 25 18:47:21 hostname kernel: [13031.896723] uhci_hcd :00:1d.2: System 
wakeup enabled by ACPI
  Oct 25 18:47:21 hostname kernel: [13031.896747] uhci_hcd :00:1d.1: System 
wakeup enabled by ACPI
  Oct 25 18:47:21 hostname kernel: [13031.896776] uhci_hcd :00:1d.0: System 
wakeup enabled by ACPI
  Oct 25 18:47:21 hostname kernel: [13031.912105] PM: noirq suspend of devices 
complete after 16.053 msecs
  Oct 25 18:47:21 hostname kernel: [13031.912287] ACPI: Preparing to enter 
system sleep state S3
  Oct 25 18:47:21 hostname kernel: [13031.935217] PM: Saving platform NVS memory
  Oct 25 18:47:21 hostname kernel: [13031.936928] Disabling non-boot CPUs ...
  Oct 25 18:47:21 hostname kernel: [13031.938236] smpboot: CPU 1 is now offline
  Oct 25 18:47:21 hostname kernel: [13031.952279] ACPI: Low-level resume 
complete
  Oct 25 18:47:21 hostname kernel: [13031.952279] PM: Restoring platform NVS 
memory
  Oct 25 18:47:21 hostname kernel: [13031.952279] microcode: CPU0 microcode 
updated early to revision 0xa4, date = 2010-10-02
  Oct 25 18:47:21 hostname kernel: [13031.952279] Enabling non-boot CPUs ...
  Oct 25 18:47:21 hostname kernel: [13031.952279] x86: Booting SMP 
configuration:
  Oct 25 18:47:21 hostname kernel: [13031.952279] smpboot: Booting Node 0 
Processor 1 APIC 0x1
  Oct 25 18:47:21 hostname kernel: [13031.938225] microcode: CPU1 microcode 
updated early to revision 0xa4, date = 2010-10-02
  Oct 25 18:47:21 hostname kernel: [13031.964405]  cache: parent cpu1 should 
not be sleeping
  Oct 25 18:47:21 hostname kernel: [13031.964682] CPU1 is up
  Oct 25 18:47:21 hostname kernel: [13031.966074] ACPI: Waking up from system 
sleep state S3
  Oct 25 18:47:21 hostname kernel: [13031.966634] uhci_hcd :00:1d.0: System 
wakeup disabled by ACPI
  Oct 25 18:47:21 hostname kernel: [13031.966700] uhci_hcd :00:1d.1: System 
wakeup 

[Kernel-packages] [Bug 1509480] dwalin (amd64) - tests ran: 66, failed: 66

[Brad Figg]

tests ran:  66, failed: 66;
  
http://kernel.ubuntu.com/testing/4.2.0-17.21/dwalin__4.2.0-17.21__2015-10-27_05-16-00/results-index.html

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

Title:
  linux: 4.2.0-17.21 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux source package in Wily:
  New

Bug description:
  This bug is for tracking the 4.2.0-17.21 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, 23. October 2015 19:00 UTC
  kernel-stable-Prepare-package-end:Saturday, 24. October 2015 06:03 UTC
  kernel-stable-Promote-to-proposed-start:Saturday, 24. October 2015 06:03 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:39 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:04 UTC
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:04 UTC
  kernel-stable-Certification-testing-start:Monday, 26. October 2015 19:04 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:04 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:04 UTC

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

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

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

[Nicolae Istratii]

Running the latest BIOS F.25, with latest official kernel or 4.3-rc7,
the sound still doesn't work without the grub adjustments.

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

Title:
  [HP Spectre x360 - 13-4010ca] Audio broken, broadwell-U audio
  controller

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1509480] fozzie (i386) - tests ran: 167, failed: 0

[Brad Figg]

tests ran: 167, failed: 0;
  
http://kernel.ubuntu.com/testing/4.2.0-17.21/fozzie__4.2.0-17.21__2015-10-27_10-14-00/results-index.html

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

Title:
  linux: 4.2.0-17.21 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux source package in Wily:
  New

Bug description:
  This bug is for tracking the 4.2.0-17.21 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, 23. October 2015 19:00 UTC
  kernel-stable-Prepare-package-end:Saturday, 24. October 2015 06:03 UTC
  kernel-stable-Promote-to-proposed-start:Saturday, 24. October 2015 06:03 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:39 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:04 UTC
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:04 UTC
  kernel-stable-Certification-testing-start:Monday, 26. October 2015 19:04 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:04 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:04 UTC

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

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

[Kernel-packages] [Bug 1510405] Re: Direct firmware load for radeon/kaveri_sdma1.bin failed with error -2

[Tim Gardner]

** Changed in: linux-firmware (Ubuntu)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  Direct firmware load for radeon/kaveri_sdma1.bin failed with error -2

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Version 1.149 of the package does not have
  /lib/firmware/radeon/kaveri_sdma1.bin needed for the latest AMD DRM
  module.

  After booting my monitor is blank.

  For other AMD chipsets *_sdma1.bin is needed as well:
  drivers/gpu/drm/amd/amdgpu/cik_sdma.c(126): snprintf(fw_name, 
sizeof(fw_name), "radeon/%s_sdma1.bin", chip_name);

  Similar to https://bugs.launchpad.net/ubuntu/+source/linux-
  firmware/+bug/1183777, https://bugs.launchpad.net/ubuntu/+source
  /linux-firmware/+bug/1218691

  Best regards,
  Timothy

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

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

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

[Christopher M. Penalver]

Nicolae Istratii, it will help immensely if you filed a new report with
the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

** Tags removed: 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/1441852

Title:
  [HP Spectre x360 - 13-4010ca] Audio broken, broadwell-U audio
  controller

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

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

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

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

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

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

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

[Kernel-packages] [Bug 949905] Re: CVE-2012-1097

[Steve Beattie]

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
 Assignee: Andy Whitcroft (apw)
   Status: Fix Released

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

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

Title:
  CVE-2012-1097

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:
  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-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:
  Fix Released
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:
  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-ti-omap4 source package in Precise:
  Fix Released
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in 

[Kernel-packages] [Bug 917706] Re: CVE-2012-0038

[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: 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: Medium
   Status: Invalid

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

Title:
  CVE-2012-0038

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:
  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-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:
  Fix Released
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 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-ti-omap4 source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid

[Kernel-packages] [Bug 990368] Re: CVE-2012-2133

[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: 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: Undecided
   Status: New

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

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

Title:
  CVE-2012-2133

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:
  New
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-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:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
Status in linux-lts-backport-maverick source package in Oneiric:
  Invalid
Status in linux-lts-backport-natty source package in Oneiric:
  Invalid
Status in linux-lts-backport-oneiric source package in Oneiric:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  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-ti-omap4 source package in Precise:
  Fix Released
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid

[Kernel-packages] [Bug 1006622] Re: CVE-2012-2136

[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: 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: Undecided
   Status: New

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

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

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

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

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

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

Title:
  CVE-2012-2136

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

[Kernel-packages] [Bug 1506050] Re: intel cpu frequency is stuck at ~400mhz

[Chris Ng]

Turns out that this was because I had a 'new' version of the intel
microcode that I must have downloaded from Intel itself in /lib/firmware
/intel-ucode when trying to diagnose a VM lockup a year or so ago.  It
updated my Haswell to 0x29, whether it's the upgrading of the microcode
or the 0x29 microcode itself causing the problem I'm not sure.

Using the 'vanilla' intel-microcode package without any modifications
seems to work fine.

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

Title:
  intel cpu frequency is stuck at ~400mhz

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  I upgraded an install of 14.0.4.3 to the LST Enablement Stack for
  Vivid (kernel 3.19) that is running on a Xeon E5-1630 V3 (a Haswell
  Quad-Core) .  Booting with 3.19 would result in the system being very
  sluggish.  'cpupower frequency-info' would report that the CPU was
  running at around 400mhz, as would 'cat
  /sys/devices/system/cpu/cpu*/cpufreq/scaling_cur_freq'.  The CPUs
  would remain around 400mhz regardless of load.

  This was using the intel_pstate driver and the powersave governor.
  Switching to the performance governor had no effect.  Using the acpi-
  cpufreq driver also had no effect, the system was still sluggish even
  though the reported frequencies in /sys/devices/.

  Eventually I tracked it down to the original install having had the
  intel_microcode package installed at some point.  Once I removed this
  then the CPU frequencies scaled correctly with load.  FYI the
  particular version installed was intel-microcode/trusty-updates,now
  2.20140624-t-1ubuntu2 amd64.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-30-generic 3.19.0-30.34~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  NonfreeKernelModules: nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.14.1-0ubuntu3.15
  Architecture: amd64
  Date: Wed Oct 14 12:38:05 2015
  InstallationDate: Installed on 2014-08-05 (434 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  SourcePackage: linux-lts-vivid
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1509438] Re: linux-ti-omap4: 3.2.0-1473.95 -proposed tracker

[Brad Figg]

** Description changed:

  This bug is for tracking the  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, 23. October 2015 17:02 UTC
  kernel-stable-master-bug:1509350
  kernel-stable-Certification-testing-end:Monday, 26. October 2015 13:01 UTC
  kernel-stable-Prepare-package-end:Monday, 26. October 2015 15:01 UTC
  kernel-stable-Promote-to-proposed-start:Monday, 26. October 2015 15:01 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:38 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:03 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:03 UTC
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:03 UTC
+ kernel-stable-Security-signoff-end:Tuesday, 27. October 2015 12:00 UTC

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

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

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

Bug description:
  This bug is for tracking the  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, 23. October 2015 17:02 UTC
  kernel-stable-master-bug:1509350
  kernel-stable-Certification-testing-end:Monday, 26. October 2015 13:01 UTC
  kernel-stable-Prepare-package-end:Monday, 26. October 2015 15:01 UTC
  kernel-stable-Promote-to-proposed-start:Monday, 26. October 2015 15:01 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:38 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:03 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:03 UTC
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:03 UTC
  kernel-stable-Security-signoff-end:Tuesday, 27. October 2015 12:00 UTC

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

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

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

[Chris J Arges]

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Chris J Arges 
(arges)

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Friday, 23. October 2015 20:02 UTC
  kernel-stable-master-bug:1509341
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Monday, 26. October 2015 19:05 UTC
  kernel-stable-Promote-to-proposed-start:Monday, 26. October 2015 19:05 UTC
  kernel-stable-phase-changed:Monday, 26. October 2015 19:05 UTC

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

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

[Kernel-packages] [Bug 1509903] Re: After sleeping or hibernating via the K Menu options, the computer suddenly powers on again by itself, some seconds later, in Kubuntu 15.10

[Mishal]

You're welcome.

I restored all of the files to the /usr/lib/pm-utils/sleep.d directory
(I had a backup of them) after I followed given in comment #2. Later, I
run the command "sudo systemctl suspend" and it's working fine: it
suspends the computer, which stays suspended till I manually powered it
on.

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

Title:
  After sleeping or hibernating via the K Menu options, the computer
  suddenly powers on again by itself, some seconds later, in Kubuntu
  15.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I recently upgraded from Kubuntu 15.04 to Kubuntu 15.10 and I've
  noticed this failure: when going through the graphical K Menu > Logout
  > Sleep or K Menu > Logout > Hibernate, the computer seems to do the
  corresponding operation fine, but some seconds later the computer
  powers on by itself, undoing the previous order to sleep or hibernate.
  A sample of the corresponding log messages stored in the file
  /var/log/syslog is this:

  Oct 25 18:47:16 hostname NetworkManager[663]:   sleep requested 
(sleeping: no  enabled: yes)
  Oct 25 18:47:16 hostname NetworkManager[663]:   sleeping...
  Oct 25 18:47:16 hostname NetworkManager[663]:   NetworkManager state is 
now ASLEEP
  Oct 25 18:47:16 hostname whoopsie[653]: [18:47:16] offline
  Oct 25 18:47:17 hostname systemd[1]: Reached target Sleep.
  Oct 25 18:47:17 hostname systemd[1]: Starting Suspend...
  Oct 25 18:47:18 hostname systemd-sleep[4848]: Suspending system...
  Oct 25 18:47:21 hostname kernel: [13031.018587] PM: Syncing filesystems ... 
done.
  Oct 25 18:47:21 hostname kernel: [13031.280695] PM: Preparing system for 
sleep (mem)
  Oct 25 18:47:21 hostname kernel: [13031.281033] Freezing user space processes 
... (elapsed 0.075 seconds) done.
  Oct 25 18:47:21 hostname kernel: [13031.357037] Freezing remaining freezable 
tasks ... (elapsed 0.001 seconds) done.
  Oct 25 18:47:21 hostname kernel: [13031.358480] PM: Suspending system (mem)
  Oct 25 18:47:21 hostname kernel: [13031.358604] Suspending console(s) (use 
no_console_suspend to debug)
  Oct 25 18:47:21 hostname kernel: [13031.359627] sd 3:0:0:0: [sda] 
Synchronizing SCSI cache
  Oct 25 18:47:21 hostname kernel: [13031.368742] serial 00:05: disabled
  Oct 25 18:47:21 hostname kernel: [13031.368751] serial 00:05: System wakeup 
disabled by ACPI
  Oct 25 18:47:21 hostname kernel: [13031.368785] i8042 aux 00:04: System 
wakeup disabled by ACPI
  Oct 25 18:47:21 hostname kernel: [13031.368858] parport_hostname 00:03: 
disabled
  Oct 25 18:47:21 hostname kernel: [13031.493405] sd 3:0:0:0: [sda] Stopping 
disk
  Oct 25 18:47:21 hostname kernel: [13031.880050] PM: suspend of devices 
complete after 521.067 msecs
  Oct 25 18:47:21 hostname kernel: [13031.896046] PM: late suspend of devices 
complete after 15.988 msecs
  Oct 25 18:47:21 hostname kernel: [13031.896488] pcieport :00:1c.1: System 
wakeup enabled by ACPI
  Oct 25 18:47:21 hostname kernel: [13031.896660] ehci-pci :00:1d.7: System 
wakeup enabled by ACPI
  Oct 25 18:47:21 hostname kernel: [13031.896690] uhci_hcd :00:1d.3: System 
wakeup enabled by ACPI
  Oct 25 18:47:21 hostname kernel: [13031.896723] uhci_hcd :00:1d.2: System 
wakeup enabled by ACPI
  Oct 25 18:47:21 hostname kernel: [13031.896747] uhci_hcd :00:1d.1: System 
wakeup enabled by ACPI
  Oct 25 18:47:21 hostname kernel: [13031.896776] uhci_hcd :00:1d.0: System 
wakeup enabled by ACPI
  Oct 25 18:47:21 hostname kernel: [13031.912105] PM: noirq suspend of devices 
complete after 16.053 msecs
  Oct 25 18:47:21 hostname kernel: [13031.912287] ACPI: Preparing to enter 
system sleep state S3
  Oct 25 18:47:21 hostname kernel: [13031.935217] PM: Saving platform NVS memory
  Oct 25 18:47:21 hostname kernel: [13031.936928] Disabling non-boot CPUs ...
  Oct 25 18:47:21 hostname kernel: [13031.938236] smpboot: CPU 1 is now offline
  Oct 25 18:47:21 hostname kernel: [13031.952279] ACPI: Low-level resume 
complete
  Oct 25 18:47:21 hostname kernel: [13031.952279] PM: Restoring platform NVS 
memory
  Oct 25 18:47:21 hostname kernel: [13031.952279] microcode: CPU0 microcode 
updated early to revision 0xa4, date = 2010-10-02
  Oct 25 18:47:21 hostname kernel: [13031.952279] Enabling non-boot CPUs ...
  Oct 25 18:47:21 hostname kernel: [13031.952279] x86: Booting SMP 
configuration:
  Oct 25 18:47:21 hostname kernel: [13031.952279] smpboot: Booting Node 0 
Processor 1 APIC 0x1
  Oct 25 18:47:21 hostname kernel: [13031.938225] microcode: CPU1 microcode 
updated early to revision 0xa4, date = 2010-10-02
  Oct 25 18:47:21 hostname kernel: [13031.964405]  cache: parent cpu1 should 
not be sleeping
  Oct 25 18:47:21 hostname kernel: [13031.964682] CPU1 is up
  Oct 25 18:47:21 hostname kernel: [13031.966074] ACPI: Waking up from system 
sleep state S3
  Oct 25 18:47:21 hostname kernel: 

[Kernel-packages] [Bug 1383184] Re: Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

[Josh Taylor]

Upgraded to 15.04, removed dkms as noted (worked fine in 15.04), and
copied the files as noted in the description (historic: For now, you
guys could use 15.10(purge the ath10k-dkms if you tried installing it),
and make a copy of https://git.kernel.org/cgit/linux/kernel/git/firmware
/linux-firmware.git/plain/ath10k/QCA6174 into /lib/firmware/ath10k/).

I now get the attached in dmesg when connecting to a network. Seems it's
crashing?

** Attachment added: "log_dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/+attachment/4506617/+files/log_dmesg.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/1383184

Title:
  Atheros Qualcomm Killer N1525 Wireless-AC [168c:003e] is not supported

Status in HWE Next:
  Triaged
Status in HWE Next wily series:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux source package in Wily:
  New
Status in linux-firmware source package in Wily:
  New

Bug description:
  =

  CURRENT STATUS:

  Wily(15.10) could not work with and don't need Adam's dkms package 1.0
  or 1.1

  Wily(15.10) has already fixed the driver part, and the firmware part
  is in progress.

  For now, you guys could use 15.10(purge the ath10k-dkms if you tried
  installing it), and make a copy of
  https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-
  firmware.git/plain/ath10k/QCA6174 into /lib/firmware/ath10k/

  Distros before 15.10(lower than 4.2 kernel) please keep using the
  dkms(which will be relocated soon)

  =

  Card detail: Qualcomm Atheros Device [168c:003e] (rev 20)
  Subsystem: Bigfoot Networks, Inc. Device [1a56:1525]

  This is on a fully updated Ubuntu Server 14.04 installation, with the 
ubuntu-desktop environment installed. This happened in order to get the md raid 
drivers for raid0 on my system, as the desktop version doesn't support them.
  ---
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  matanis2333 F pulseaudio
   /dev/snd/controlC0:  matanis2333 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=1b192ee3-f592-43e9-bdcf-08b91c0aa9b6
  InstallationDate: Installed on 2014-10-16 (3 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p2p1  no wireless extensions.

   lono wireless extensions.
  MachineType: Micro-Star International Co., Ltd. GT72 2QE
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic.efi.signed 
root=UUID=80998dbb-1f89-4eda-be90-25e35e1c0a90 ro
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware 1.127.7
  RfKill:

  Tags:  trusty
  Uname: Linux 3.13.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1781IMS.10D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-1781
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.C
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1781IMS.10D:bd09/15/2014:svnMicro-StarInternationalCo.,Ltd.:pnGT722QE:pvrREV0.C:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1781:rvrREV0.C:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: GT72 2QE
  dmi.product.version: REV:0.C
  dmi.sys.vendor: Micro-Star International Co., Ltd.

  Qualcomm Atheros Device [168c:003e] (rev 20)

  mainline commit d63955b33b3bee45d784ffdfafeb93076c765660

  [6.221281] ath10k_pci :02:00.0: pci irq msi interrupts 1 irq_mode 0 
reset_mode 0
  [6.417386] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/cal-pci-:02:00.0.bin failed with error -2
  [6.417404] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/QCA6174/hw2.1/board-pci-168c:003e:17aa:3044.bin failed with error -2
  [6.417407] ath10k_pci :02:00.0: failed to load spec board file, 
falling back to generic: -2
  [6.417416] ath10k_pci :02:00.0: Direct firmware load for 
ath10k/QCA6174/hw2.1/board.bin failed with error -2
  [6.417418] ath10k_pci :02:00.0: 

[Kernel-packages] [Bug 947997] Re: CVE-2012-1090

[Steve Beattie]

** Also affects: linux (Ubuntu Xenial)
   Importance: Low
   Status: Fix Released

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

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

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

Title:
  CVE-2012-1090

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:
  New
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-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:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
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:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  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-ti-omap4 source package in Precise:
  Fix Released
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty source package 

[Kernel-packages] [Bug 1509798] Re: Kernel panic during install boot in ohci_hcd module

[Christopher M. Penalver]

nenhard, 4.3 dot what specifically?

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

Title:
  Kernel panic during install boot in ohci_hcd module

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kernel panic if I try to boot USB from installer 15.10 image or reboot after 
dist-upgrade from 15.10 beta to 15.10 release. 
  This happens in kernel 4.2.0-16, but not in older beta 4.1.0-3-generic kernel.

  I have attached picture of kernel panic and 'sudo lspci -vnvn' output.
  --- 
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   nenad  4242 F...m pulseaudio
   /dev/snd/controlC0:  nenad  4242 F pulseaudio
   /dev/snd/controlC1:  nenad  4242 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-02 (84 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150726)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=c2eb7374-dd07-45ee-9402-27e3527a60b8 ro amd_iommu=on 
pci-stub.ids=1002:665d,1002:aac0,13f6:0111
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-generic N/A
   linux-backports-modules-4.1.0-3-generic  N/A
   linux-firmware   1.149
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd01/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 952828] Re: CVE-2012-1146

[Steve Beattie]

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

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

** Also affects: linux-lts-raring (Ubuntu Xenial)
   Importance: Undecided
   Status: Won't Fix

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

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

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

Title:
  CVE-2012-1146

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:
  New
Status in linux-lts-raring package in Ubuntu:
  Won't Fix
Status in linux-lts-saucy package in Ubuntu:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux-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-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:
  Fix Released
Status in linux-lts-backport-maverick source package in Maverick:
  Invalid
Status in linux-lts-backport-natty source package in Maverick:
  Invalid
Status in linux-lts-backport-oneiric source package in Maverick:
  Invalid
Status in linux-lts-backport-maverick source package in Natty:
  Invalid
Status in linux-lts-backport-natty source package in Natty:
  Invalid
Status in linux-lts-backport-oneiric source package in Natty:
  Invalid
Status in linux-lts-backport-maverick source package in Oneiric:
  Invalid
Status in linux-lts-backport-natty source package in Oneiric:
  Invalid
Status in linux-lts-backport-oneiric source package in Oneiric:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Won't Fix
Status in linux-lts-raring source package in Precise:
  Won't Fix
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  Invalid
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux-lts-vivid source package in Precise:
  Invalid
Status in linux-mako source package in Precise:
  Invalid
Status in linux-manta 

[Kernel-packages] [Bug 987569] Re: CVE-2012-2121

[Steve Beattie]

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
 Assignee: Steve Conklin (sconklin)
   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: Medium
   Status: Invalid

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

Title:
  CVE-2012-2121

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:
  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-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:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
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:
  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-ti-omap4 source package in Precise:
  Fix Released
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in 

[Kernel-packages] [Bug 1509480] onibi (amd64) - tests ran: 194, failed: 13

[Brad Figg]

tests ran: 194, failed: 13;
  
http://kernel.ubuntu.com/testing/4.2.0-17.21/onibi__4.2.0-17.21__2015-10-27_08-32-00/results-index.html

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

Title:
  linux: 4.2.0-17.21 -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:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  New
Status in linux source package in Wily:
  New

Bug description:
  This bug is for tracking the 4.2.0-17.21 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, 23. October 2015 19:00 UTC
  kernel-stable-Prepare-package-end:Saturday, 24. October 2015 06:03 UTC
  kernel-stable-Promote-to-proposed-start:Saturday, 24. October 2015 06:03 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:39 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:04 UTC
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:04 UTC
  kernel-stable-Certification-testing-start:Monday, 26. October 2015 19:04 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:04 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:04 UTC

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

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

[Kernel-packages] [Bug 1497005] Re: 197b:0250 JMicron JMC250 Gigabit ethernet doesn't work

[Driuchatyi Nikolay]

I tried to use the recommended driver version from ASUS support website:
V6.0.27.6
http://dlcdnet.asus.com/pub/ASUS/nb/Drivers/LAN/JMicron/LAN_JMicron_JMC251_Win7_32_Win7_64_Z60276.zip

After that, I used the latest one for Windows 7 x64 from JMicron support
website: http://jmicron-pci-express-gigabit-ethernet-
ada1.drivers.informer.com/

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

Title:
  197b:0250 JMicron JMC250 Gigabit ethernet doesn't work

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Laptop ASUS X52JU can't connect to the router ASUS RT-AC68U via
  ethernet. NetworkManager shows that cable is unplugged. Router has
  Gigabit ethernet ports and laptop doesn't see them. I found that it's
  a bug of the JMC kernel module.

  WORKAROUND: The following allows 100 Mbps speed:
  sudo ethtool -s eth0 speed 100 duplex full

  ---
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  nick   1682 F pulseaudio
   /dev/snd/controlC0:  nick   1682 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=b3669551-f67b-41f1-a310-6b79e24b871c
  InstallationDate: Installed on 2015-06-16 (93 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK Computer Inc. K52JU
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-49-generic 
root=UUID=c8aa6fb0-2c0a-430d-b6e5-7bb4ebb8346e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-49.65~14.04.1-generic 3.16.7-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-49-generic N/A
   linux-backports-modules-3.16.0-49-generic  N/A
   linux-firmware 1.127.15
  Tags:  trusty
  Uname: Linux 3.16.0-49-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K52JU.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K52JU
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK52JU.206:bd01/25/2011:svnASUSTeKComputerInc.:pnK52JU:pvr1.0:rvnASUSTeKComputerInc.:rnK52JU:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K52JU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Kernel-packages] [Bug 1510165] Re: heartbeat module is not loaded

[Paolo Pisati]

** Patch added: "0001-UBUNTU-Config-armhf-LEDS_TRIGGER_HEARTBEAT-y.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1510165/+attachment/4506537/+files/0001-UBUNTU-Config-armhf-LEDS_TRIGGER_HEARTBEAT-y.patch

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

Title:
  heartbeat module is not loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU justification:

  Problem: If the heartbeat function is assigned to a led via a device
  tree, the led instead of beating is turned off, and in case of a
  headless system, the board seems to be dead.

  Fix: Apply the attached patch and recompile

  How to reproduce: Assign the heartbeat trigger to a user configurable
  led and check if it beats:

  echo heartbeat > /sys/class/leds/$LED/trigger

  
  ---

  The beaglebone black has a led that blinks like a heartbeat. But it is
  not working with the snappy image because the ledtrig-heartbeat is not
  loaded.

  When I do:
  sudo modprobe ledtrig-heartbeat

  it starts to blink.

  Please make the ledtrig-heartbeat a build-in option so when we install snappy 
in the bbb it blinks.
  ---
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elopio 7601 F pulseaudio
   /dev/snd/pcmC0D0p:   elopio 7601 F...m pulseaudio
   /dev/snd/controlC0:  elopio 7601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2015-09-07 (49 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150907)
  MachineType: System76, Inc. Wild Dog Performance
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=f1dc8e52-281b-4e3c-9d6c-743c3239c459 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-7-generic N/A
   linux-backports-modules-4.2.0-7-generic  N/A
   linux-firmware   1.149
  Tags:  wily
  UdevLog: Error: [Errno 2] Dosiero aŭ dosierujo ne ekzistas: '/var/log/udev'
  Uname: Linux 4.2.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 02/24/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825
  dmi.board.name: DH77KC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39641-400
  dmi.chassis.type: 3
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: WilP9
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9:
  dmi.product.name: Wild Dog Performance
  dmi.product.version: wilp9
  dmi.sys.vendor: System76, Inc.

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

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

[Kernel-packages] [Bug 1507959] Re: Regression: Kernel update breaks all lxc-containers lxc-start failing with (apparmor="DENIED" operation="mount")

[tapczan]

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

This bug was also introduced after update kernel from 3.19.0-30-generic
to 3.19.0-31-generic. LXC version is 1.0.7-0ubuntu0.1.

Add line to /etc/apparmor.d/abstractions/lxc/start-container fixes
issue:

mount options=bind /dev/pts/** -> /dev/**,

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

Title:
  Regression: Kernel update breaks all lxc-containers lxc-start failing
  with  (apparmor="DENIED" operation="mount")

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,
  The following recent kernel update completely break our lxc-start usage on 
precise both with precise original kernel 3.2 + also the trusty-lts-stack using 
3.13

  After installing those new kernel updates all lxc-start of a container fail 
with:
  "Permission denied - mount failed '/dev/pts/ptmx'->'/dev/ptmx'"

  with strace pointing to:
  13695 mount("/dev/pts/ptmx", "/dev/ptmx", 0x7f4d68c85d37, MS_BIND, NULL) = -1 
EACCES (Permission denied)

  and dmesg showing:
  Oct 20 10:59:00 titan226 kernel: [  663.508664] type=1400 
  audit(1445331540.807:29): apparmor="DENIED" operation="mount" 
  info="failed type match" error=-13 
profile="/usr/bin/lxc-start" 
  name="/dev/ptmx" pid=2897 comm="lxc-start" 
  srcname="/dev/pts/ptmx" flags="rw, bind"

  After downgrading kernel version the problem immediately dissappeared
  and the lxc-start for containers works again as before.

  Bad versions:
  ii  linux-image-3.13.0-66-generic3.13.0-66.108~precise1Linux 
kernel image for version 3.13.0 on 64 bit x86 SMP
  ii  linux-image-3.2.0-92-generic 3.2.0-92.130  Linux 
kernel image for version 3.2.0 on 64 bit x86 SMP

  
  Good versions:
  ii  linux-image-3.13.0-61-generic3.13.0-61.100~precise1Linux 
kernel image for version 3.13.0 on 64 bit x86 SMP
  ii  linux-image-3.2.0-88-generic 3.2.0-88.126  Linux 
kernel image for version 3.2.0 on 64 bit x86 SMP

  From kernel changelog maybe this other issue here maybe causing it but not 
verified:
* SAUCE: (no-up) apparmor: fix mount not handling disconnected paths
  - LP: #1496430
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-61-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.11
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 12.04
  HibernationDevice: RESUME=UUID=ee5d3bc2-531d-4fbf-ba3f-033c27498274
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: FUJITSU PRIMERGY MX130 S1
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-61-generic 
root=UUID=8c11de07-6403-46cf-994b-15750a7404ba ro rootdelay=80
  ProcVersionSignature: Ubuntu 3.13.0-61.100~precise1-generic 3.13.11-ckt22
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-61-generic N/A
   linux-backports-modules-3.13.0-61-generic  N/A
   linux-firmware 1.79.18
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  precise
  Uname: Linux 3.13.0-61-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/18/2011
  dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
  dmi.bios.version: 6.00 R1.01.2974.A1
  dmi.board.asset.tag: -
  dmi.board.name: D2974
  dmi.board.vendor: FUJITSU
  dmi.board.version: S26361-D2974-A1
  dmi.chassis.type: 3
  dmi.chassis.vendor: FUJITSU
  dmi.chassis.version: MX130S1F
  dmi.modalias: 
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvr6.00R1.01.2974.A1:bd01/18/2011:svnFUJITSU:pnPRIMERGYMX130S1:pvr:rvnFUJITSU:rnD2974:rvrS26361-D2974-A1:cvnFUJITSU:ct3:cvrMX130S1F:
  dmi.product.name: PRIMERGY MX130 S1
  dmi.sys.vendor: FUJITSU

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

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

[Kernel-packages] [Bug 1016299] Re: CVE-2012-2372

[Steve Beattie]

** Also affects: linux (Ubuntu Xenial)
   Importance: Low
   Status: Fix Committed

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

** Also affects: linux-manta (Ubuntu Xenial)
   Importance: Low
   Status: New

** Also affects: linux-goldfish (Ubuntu Xenial)
   Importance: Low
   Status: New

** Also affects: linux-flo (Ubuntu Xenial)
   Importance: Low
   Status: New

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

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

Title:
  CVE-2012-2372

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  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:
  Invalid
Status in linux-mako package in Ubuntu:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-lts-backport-maverick source package in Lucid:
  Invalid
Status in linux-lts-backport-natty source package in Lucid:
  Fix Released
Status in linux-lts-backport-oneiric source package in Lucid:
  Fix Released
Status in linux-lts-backport-maverick source package in Natty:
  Invalid
Status in linux-lts-backport-natty source package in Natty:
  Invalid
Status in linux-lts-backport-oneiric source package in Natty:
  Invalid
Status in linux-lts-backport-maverick source package in Oneiric:
  Invalid
Status in linux-lts-backport-natty source package in Oneiric:
  Invalid
Status in linux-lts-backport-oneiric source package in Oneiric:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-armadaxp source package in Precise:
  Fix Released
Status in linux-ec2 source package in Precise:
  Invalid
Status in linux-flo source package in Precise:
  Invalid
Status in linux-fsl-imx51 source package in Precise:
  Invalid
Status in linux-goldfish source package in Precise:
  Invalid
Status in linux-lts-backport-maverick source package in Precise:
  Invalid
Status in linux-lts-backport-natty source package in Precise:
  Invalid
Status in linux-lts-backport-oneiric source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  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-ti-omap4 source package in Precise:
  Fix Released
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid

[Kernel-packages] [Bug 1510165] Re: heartbeat module is not loaded

[Paolo Pisati]

** Description changed:

+ SRU justification:
+ 
+ Problem: If the heartbeat function is assigned to a led via a device
+ tree, the led instead of beating is turned off, and in case of a
+ headless system, the board seems to be dead.
+ 
+ Fix: Apply the attached patch and recompile
+ 
+ How to reproduce: Assign the heartbeat trigger to a user configurable
+ led and check if it beats:
+ 
+ echo heartbeat > /sys/class/leds/$LED/trigger
+ 
+ 
+ ---
+ 
  The beaglebone black has a led that blinks like a heartbeat. But it is
  not working with the snappy image because the ledtrig-heartbeat is not
  loaded.
  
  When I do:
  sudo modprobe ledtrig-heartbeat
  
  it starts to blink.
  
  Please make the ledtrig-heartbeat a build-in option so when we install snappy 
in the bbb it blinks.
- --- 
+ ---
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  elopio 7601 F pulseaudio
-  /dev/snd/pcmC0D0p:   elopio 7601 F...m pulseaudio
-  /dev/snd/controlC0:  elopio 7601 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  elopio 7601 F pulseaudio
+  /dev/snd/pcmC0D0p:   elopio 7601 F...m pulseaudio
+  /dev/snd/controlC0:  elopio 7601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2015-09-07 (49 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150907)
  MachineType: System76, Inc. Wild Dog Performance
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=f1dc8e52-281b-4e3c-9d6c-743c3239c459 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  RelatedPackageVersions:
-  linux-restricted-modules-4.2.0-7-generic N/A
-  linux-backports-modules-4.2.0-7-generic  N/A
-  linux-firmware   1.149
+  linux-restricted-modules-4.2.0-7-generic N/A
+  linux-backports-modules-4.2.0-7-generic  N/A
+  linux-firmware   1.149
  Tags:  wily
  UdevLog: Error: [Errno 2] Dosiero aŭ dosierujo ne ekzistas: '/var/log/udev'
  Uname: Linux 4.2.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 02/24/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825
  dmi.board.name: DH77KC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39641-400
  dmi.chassis.type: 3
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: WilP9
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9:
  dmi.product.name: Wild Dog Performance
  dmi.product.version: wilp9
  dmi.sys.vendor: System76, Inc.

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

Title:
  heartbeat module is not loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU justification:

  Problem: If the heartbeat function is assigned to a led via a device
  tree, the led instead of beating is turned off, and in case of a
  headless system, the board seems to be dead.

  Fix: Apply the attached patch and recompile

  How to reproduce: Assign the heartbeat trigger to a user configurable
  led and check if it beats:

  echo heartbeat > /sys/class/leds/$LED/trigger

  
  ---

  The beaglebone black has a led that blinks like a heartbeat. But it is
  not working with the snappy image because the ledtrig-heartbeat is not
  loaded.

  When I do:
  sudo modprobe ledtrig-heartbeat

  it starts to blink.

  Please make the ledtrig-heartbeat a build-in option so when we install snappy 
in the bbb it blinks.
  ---
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elopio 7601 F pulseaudio
   /dev/snd/pcmC0D0p:   elopio 7601 F...m pulseaudio
   /dev/snd/controlC0:  elopio 7601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2015-09-07 (49 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150907)
  MachineType: System76, Inc. Wild Dog Performance
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=f1dc8e52-281b-4e3c-9d6c-743c3239c459 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-7-generic N/A
   linux-backports-modules-4.2.0-7-generic  N/A
   linux-firmware   1.149
  Tags:  wily
  UdevLog: Error: 

[Kernel-packages] [Bug 1016298] Re: CVE-2012-2137

[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: 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: Undecided
   Status: New

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

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

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

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

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

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

Title:
  CVE-2012-2137

Status in linux package in Ubuntu:
  Invalid
Status in linux-armadaxp package in Ubuntu:
  Invalid
Status in linux-ec2 package in Ubuntu:
  Invalid
Status in linux-flo package in Ubuntu:
  New
Status in linux-fsl-imx51 package in Ubuntu:
  Invalid
Status in linux-goldfish package in Ubuntu:
  New
Status in linux-lts-backport-maverick package in Ubuntu:
  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:
  New
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:
  New
Status in linux-manta package in Ubuntu:
  New
Status in linux-mvl-dove package in Ubuntu:
  Invalid
Status in linux-ti-omap4 package in Ubuntu:
  Invalid
Status in linux-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:
  Fix Released
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:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in linux-lts-saucy source package in Precise:
  New
Status in linux-lts-trusty source package in Precise:
  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-ti-omap4 source package in Precise:
  Fix Released
Status in linux-lts-backport-maverick source package in Quantal:
  Invalid
Status in linux-lts-backport-natty source package in Quantal:
  Invalid
Status in linux-lts-backport-oneiric source package in Quantal:
  Invalid
Status in linux-lts-backport-maverick source package in Raring:
  Invalid
Status in linux-lts-backport-natty source package in Raring:
  Invalid
Status in linux-lts-backport-oneiric source package in Raring:
  Invalid
Status in linux-lts-backport-maverick source package in Saucy:
  Invalid
Status in linux-lts-backport-natty 

[Kernel-packages] [Bug 1509193] Re: Surelock:GA2:Capiredfsp:HID_module file not compiling

[Leann Ogasawara]

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

Title:
  Surelock:GA2:Capiredfsp:HID_module file not compiling

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Problem Description
  ===
  HID_module file not compiling
  The HID_module is a suite of files that will allow us to access the HID 
registers of a CPU.

  
  htx@capiredp01]  [1m/usr/lpp/htx/bin# [0m ver
  cat: /proc/device-tree/openprom/model: No such file or directory
 ver 1.5.4.3 - OS, HTX, Firmware and Machine details

 OS: GNU/Linux
 OS Version: Ubuntu Wily Werewolf (development branch) \n \l
 Kernel Version: 4.2.0-432-5783a51+
HTX Version: htxubuntu-358
  Host Name: capiredp01
  Machine Serial No: 211AEFA
 Machine Type/Model: 8247-22L

  root@capiredp01:/mnt/test/tools# lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu Wily Werewolf (development branch)
  Release:15.10
  Codename:   wily

  GSA Location:
  
/gsa/ausgsa/projects/s/sift/hst/trial_data/Apollo_TULET22L/Ubuntu/OP810/TER94756_capiredfsp/FAIL201510091752

  Additional Information:
  ===
  Steps Taken
  1) Installed HID_module.tgz file to get access to HID registers
  2) Unpacked file
  3) Changed directory to get access to compile.sh file
  4) Ran compile.sh and compilation failed

  # wget 
http://ausgsa.ibm.com/gsa/ausgsa/home/f/d/fdelco/web/public/MPV_RAS/HID_module.tgz
  --2015-10-09 16:36:12--  
http://ausgsa.ibm.com/gsa/ausgsa/home/f/d/fdelco/web/public/MPV_RAS/HID_module.tgz
  Resolving ausgsa.ibm.com (ausgsa.ibm.com)... 9.41.254.82, 9.41.254.37, 
9.41.254.24, ...
  Connecting to ausgsa.ibm.com (ausgsa.ibm.com)|9.41.254.82|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 1314 (1.3K) [application/x-tar]
  Saving to: ?HID_module.tgz?

  HID_module.tgz  100%[=>]   1.28K  --.-KB/s
  in 0s

  2015-10-09 16:36:12 (36.9 MB/s) - ?HID_module.tgz? saved [1314/1314]

  #tar -xvzf HID_module.tgz
  HID_module/
  HID_module/Makefile
  HID_module/mod_hid.c
  HID_module/compile.sh

  # cd HID_module
  # ls
  compile.sh  Makefile  mod_hid.c

  # ./compile.sh
  Please make sure you have installed kernel-devel package.
  Otherwise kernel module compilation will fail.
  make: Entering directory '/usr/src/linux-headers-4.2.0-432-5783a51+'
CC [M]  /root/HID_module/mod_hid.o
Building modules, stage 2.
MODPOST 1 modules
CC  /root/HID_module/mod_hid.mod.o
LD [M]  /root/HID_module/mod_hid.ko
  ld: cannot find arch/powerpc/lib/crtsavres.o: No such file or directory
  scripts/Makefile.modpost:124: recipe for target '/root/HID_module/mod_hid.ko' 
failed
  make[1]: *** [/root/HID_module/mod_hid.ko] Error 1
  Makefile:1389: recipe for target 'modules' failed
  make: *** [modules] Error 2
  make: Leaving directory '/usr/src/linux-headers-4.2.0-432-5783a51+'

  # ls
  compile.sh  mod_hid.c  mod_hid.mod.o  modules.order
  Makefilemod_hid.mod.c  mod_hid.o  Module.symvers


  Here is the expected output:
  ./compile.sh
  Please make sure you have installed kernel-devel package.
  Otherwise kernel module compilation will fail.
  make: Entering directory 
`/usr/src/kernels/3.18.21-350.el7_1.pkvm3_1_0.3200.1.ppc64le'
  CC [M] /root/HID_module/mod_hid.o
  Building modules, stage 2.
  MODPOST 1 modules
  CC /root/HID_module/mod_hid.mod.o
  LD [M] /root/HID_module/mod_hid.ko
  make: Leaving directory 
`/usr/src/kernels/3.18.21-350.el7_1.pkvm3_1_0.3200.1.ppc64le'

  
  
  


  == Comment: #3 - ==
  To me it  looks like packaging issue with linux-image/linux-header package.

  Out of all the installed linux-header, generic did have the
  crtsavres.o file, while it was missing in other case.

  root@capiredp01:/usr/src# ll
  total 32
  drwxr-xr-x  8 root   root   4096 Oct  4 18:50 ./
  drwxr-xr-x 11 313396 928803 4096 Jun 25 03:56 ../
  drwxr-xr-x 23 root   root   4096 Sep  6 02:33 
linux-headers-4.2.0-415-9a5f7d5+/
  drwxr-xr-x 23 root   root   4096 Sep 20 02:36 
linux-headers-4.2.0-418-a436d20+/
  drwxr-xr-x 23 root   root   4096 Sep 27 12:32 
linux-headers-4.2.0-428-ed62cef+/
  drwxr-xr-x 23 root   root   4096 Oct  4 18:52 
linux-headers-4.2.0-432-5783a51+/
  drwxr-xr-x 24 root   root   4096 Sep  6 00:56 linux-headers-4.2.0-7/
  drwxr-xr-x  7 root   root   4096 Sep  6 00:56 linux-headers-4.2.0-7-generic/
  root@capiredp01:/usr/src# 

  root@capiredp01:~# find /usr/src/ -iname crtsavres.o
  /usr/src/linux-headers-4.2.0-7-generic/arch/powerpc/lib/crtsavres.o
  root@capiredp01:~# 

  
  ---
  Recreating the 

[Kernel-packages] [Bug 1509438] Re: linux-ti-omap4: 3.2.0-1473.95 -proposed tracker

[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-ti-omap4 in Ubuntu.
https://bugs.launchpad.net/bugs/1509438

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

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

Bug description:
  This bug is for tracking the  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, 23. October 2015 17:02 UTC
  kernel-stable-master-bug:1509350
  kernel-stable-Certification-testing-end:Monday, 26. October 2015 13:01 UTC
  kernel-stable-Prepare-package-end:Monday, 26. October 2015 15:01 UTC
  kernel-stable-Promote-to-proposed-start:Monday, 26. October 2015 15:01 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:38 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:03 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:03 UTC
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:03 UTC

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

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

[Kernel-packages] [Bug 1509798] Re: Kernel panic during install boot in ohci_hcd module

[nenhard]

There is clearly shown version string in the picture.

linux-
image-4.3.0-040300rc7-generic_4.3.0-040300rc7.201510260712_amd64.deb

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

Title:
  Kernel panic during install boot in ohci_hcd module

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kernel panic if I try to boot USB from installer 15.10 image or reboot after 
dist-upgrade from 15.10 beta to 15.10 release. 
  This happens in kernel 4.2.0-16, but not in older beta 4.1.0-3-generic kernel.

  I have attached picture of kernel panic and 'sudo lspci -vnvn' output.
  --- 
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   nenad  4242 F...m pulseaudio
   /dev/snd/controlC0:  nenad  4242 F pulseaudio
   /dev/snd/controlC1:  nenad  4242 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 15.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-02 (84 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150726)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  NonfreeKernelModules: fglrx
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.0-3-generic 
root=UUID=c2eb7374-dd07-45ee-9402-27e3527a60b8 ro amd_iommu=on 
pci-stub.ids=1002:665d,1002:aac0,13f6:0111
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-3-generic N/A
   linux-backports-modules-4.1.0-3-generic  N/A
   linux-firmware   1.149
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.1.0-3-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/25/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FD
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-D3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFD:bd01/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-D3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1510165] Re: heartbeat module is not loaded

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  heartbeat module is not loaded

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  SRU justification:

  Problem: If the heartbeat function is assigned to a led via a device
  tree, the led instead of beating is turned off, and in case of a
  headless system, the board seems to be dead.

  Fix: Apply the attached patch and recompile

  How to reproduce: Assign the heartbeat trigger to a user configurable
  led and check if it beats:

  echo heartbeat > /sys/class/leds/$LED/trigger

  
  ---

  The beaglebone black has a led that blinks like a heartbeat. But it is
  not working with the snappy image because the ledtrig-heartbeat is not
  loaded.

  When I do:
  sudo modprobe ledtrig-heartbeat

  it starts to blink.

  Please make the ledtrig-heartbeat a build-in option so when we install snappy 
in the bbb it blinks.
  ---
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  elopio 7601 F pulseaudio
   /dev/snd/pcmC0D0p:   elopio 7601 F...m pulseaudio
   /dev/snd/controlC0:  elopio 7601 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2015-09-07 (49 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150907)
  MachineType: System76, Inc. Wild Dog Performance
  Package: linux (not installed)
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-7-generic 
root=UUID=f1dc8e52-281b-4e3c-9d6c-743c3239c459 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-7-generic N/A
   linux-backports-modules-4.2.0-7-generic  N/A
   linux-firmware   1.149
  Tags:  wily
  UdevLog: Error: [Errno 2] Dosiero aŭ dosierujo ne ekzistas: '/var/log/udev'
  Uname: Linux 4.2.0-7-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin lxd plugdev sambashare sbuild sudo
  _MarkForUpload: True
  dmi.bios.date: 02/24/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KCH7710H.86A.0069.2012.0224.1825
  dmi.board.name: DH77KC
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39641-400
  dmi.chassis.type: 3
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: WilP9
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKCH7710H.86A.0069.2012.0224.1825:bd02/24/2012:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp9:rvnIntelCorporation:rnDH77KC:rvrAAG39641-400:cvnSystem76,Inc.:ct3:cvrWilP9:
  dmi.product.name: Wild Dog Performance
  dmi.product.version: wilp9
  dmi.sys.vendor: System76, Inc.

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

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

[Kernel-packages] [Bug 1495043] Re: Suspend/Resume Regression 3.19.0-28-generic Dell xps15

[Mark Pointing]

Although the mainline kernel seemed to fix the problem, no release since
3.19.0-26 has functioned correctly.  I have tried every kernel update,
and am now on ubuntu 15.10, but must still run the old 3.19.0-26 kernel
to get suspend resume to work.

Removing the fixed-upstream tag.

** Tags removed: kernel-fixed-upstream

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

Title:
  Suspend/Resume Regression 3.19.0-28-generic Dell xps15

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Suspend resume was working on 3.19.0-26 but 3.19.0-28 appears to
  suspend, but no longer resumes.  Relevant portion of dmesg info using
  pm-trace is as follows:

  [1.168740] registered taskstats version 1
  [1.170526] Key type trusted registered
  [1.174836] Key type encrypted registered
  [1.174843] AppArmor: AppArmor sha1 policy hashing enabled
  [1.176721] input: AT Translated Set 2 keyboard as 
/devices/platform/i8042/serio0/input/input3
  [1.398911] evm: HMAC attrs: 0x1
  [1.399640]   Magic number: 0:469:661
  [1.399643]   hash matches 
/build/linux-5xFjum/linux-3.19.0/drivers/base/power/main.c:642
  [1.399655]   hash matches 
/build/linux-5xFjum/linux-3.19.0/drivers/base/power/main.c:738
  [1.399670] block ram14: hash matches
  [1.399692] platform PNP0C0A:00: hash matches
  [1.399711] battery PNP0C0A:00: hash matches
  [1.399793] rtc_cmos 00:01: setting system clock to 1976-02-02 02:39:41 
UTC (192076781)
  [1.399886] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
  [1.399887] EDD information not available.
  [1.399970] PM: Hibernation image not present or could not be loaded.
  [1.400304] Freeing unused kernel memory: 1408K (81d36000 - 
81e96000)
  [1.400305] Write protecting the kernel read-only data: 12288k

  To reproduce the bug:
  1) Boot into Ubuntu Gnome with kernel 3.19.0.28-generic
  2) Log in to desktop.
  3) Close laptop lid
  4) Wait about 10 seconds (doesn't seem to be critical how long you wait)
  5) Open laptop lid.

  What happens:
  The keyboard backlight and the power button light come on, but the screen 
remains blank.  Using Ctr-Alt-F1 does nothing (can't get to a virtual console, 
indicating that it's not just X that has stopped)

  What I expect to happen:
  On opening of the laptop lid, I expect the lockscreen to show.

  Other info:
  This laptop has nvidia graphics disabled using nvidia-prime

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-28-generic 3.19.0-28.30
  ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5
  Uname: Linux 3.19.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mark   1566 F pulseaudio
   /dev/snd/controlC0:  mark   1566 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Sep 12 19:26:03 2015
  HibernationDevice: RESUME=UUID=ff91bc8d-f7ef-4650-81e0-608068f4f8cb
  InstallationDate: Installed on 2015-08-31 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  MachineType: Dell Inc. XPS 15 9530
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed 
root=UUID=b69e369b-42c8-4f85-8a2c-dcfec06b7d88 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-28-generic N/A
   linux-backports-modules-3.19.0-28-generic  N/A
   linux-firmware 1.143.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: 07/30/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: XPS 15 9530
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 15 9530
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1499849] Re: Add CAPI flash driver (cxlflash) patches to 15.10

[Mathew Hodson]

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

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

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

Title:
  Add CAPI flash driver (cxlflash) patches to 15.10

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

Bug description:
  == Comment: #2 - Matthew R. Ochs  - 2015-09-24 16:41:19 ==
  Patches for the cxlflash SCSI driver are in the process of being
  upstreamed as part of the rc phase for 4.3. This is to get those
  patches into Ubuntu 15.10.

  == Comment: #3 - Matthew R. Ochs  - 2015-09-24
  17:06:45 ==

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

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

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

[Brad Figg]

** Description changed:

  This bug is for tracking the 3.13.0-67.110~precise1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Friday, 23. October 2015 20:02 UTC
  kernel-stable-master-bug:1509341
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Monday, 26. October 2015 19:05 UTC
  kernel-stable-Promote-to-proposed-start:Monday, 26. October 2015 19:05 UTC
  kernel-stable-phase-changed:Monday, 26. October 2015 19:05 UTC
+ kernel-stable-Promote-to-proposed-end:Tuesday, 27. October 2015 15:46 UTC

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

Title:
  linux-lts-trusty: 3.13.0-67.110~precise1 -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:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Friday, 23. October 2015 20:02 UTC
  kernel-stable-master-bug:1509341
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Monday, 26. October 2015 19:05 UTC
  kernel-stable-Promote-to-proposed-start:Monday, 26. October 2015 19:05 UTC
  kernel-stable-phase-changed:Monday, 26. October 2015 19:05 UTC
  kernel-stable-Promote-to-proposed-end:Tuesday, 27. October 2015 15:46 UTC

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

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

[Kernel-packages] [Bug 1482343] Re: Trigger a checkstop on unrecoverable MCE/HMI errors to inform BMC/OCC about the error.

[Mahesh J Salgaonkar]

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

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

Title:
  Trigger a checkstop on unrecoverable MCE/HMI errors to inform BMC/OCC
  about the error.

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

Bug description:
  The current implementation of Machine Check handler and HMI handler in
  Linux, goes down kernel panic path for unrecoverable errors. On FSP
  based system FSP also gets notified about these errors which then
  forwards it to PRD (that runs on FSP) for error analysis and gard
  record creation.

  On OpenPower (BMC based system e.g. Habanero from TYAN) where PRD runs
  in Linux host, it never gets a chance to do error analysis at the time
  of Linux crash and no gard record is created for such errors. Since
  the faulty component never gets de-configured, the system is
  vulnerable to get hit by same HW error again.

  To fix this issue, a new OPAL call 'opal_cec_reboot2()' has been
  introduced to trigger a checkstop on BMC based system to inform
  BMC/OCC about this error, so that BMC can collect relevant data for
  error analysis and decide what component to de-configure before
  rebooting. Linux kernel should invoke this opal call for unrecoverable
  MCE and HMI instead before calling kernel panic so that OCC is
  informed about the error.

  The kernel changes has already been posted to upstream and are listed
  below:

  https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-May/128341.html
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-May/128342.html
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-August/132045.html
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-August/132114.html 

  Above patches needs to be included in ubuntu 14.04.3+

  We will update this bug with commit ids, once the above patches are
  accepted upstream.

  Contact Information = mahesh.salgaon...@in.ibm.com 
   
  ---uname output---
  Linux rcx2d403 3.19.0-26-generic #27 SMP Tue Aug 4 01:38:15 CDT 2015 ppc64le 
ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Habanero pass2 system 

   
  Machine Type = OpenPower, Habanero 
   
  ---System Hang---
   If system is hung, it can be recovered by sending ipmi power off/on command.
  $ ipmitool -H  -I lanplus -U  -P  power off
  $ ipmitool -H  -I lanplus -U  -P  power on

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

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

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

[bugproxy]

--- Comment From mahesh.salgaon...@in.ibm.com 2015-10-27 15:41 EDT---
I just verified that issue is fixed in Ubuntu-3.19.0-32.37 kernel version


Ubuntu 14.04.3 LTS ltc-fire14 hvc0

ltc-fire14 login: root
Password:
Last login: Tue Oct 27 10:11:22 CDT 2015 on hvc0
Welcome to Ubuntu 14.04.3 LTS (GNU/Linux 3.19.0-32-generic ppc64le)

* Documentation:  https://help.ubuntu.com/
root@ltc-fire14:~# uname -a
Linux ltc-fire14 3.19.0-32-generic #37-Ubuntu SMP Wed Oct 21 10:22:35 UTC 2015 
ppc64le ppc64le ppc64le GNU/Linux
root@ltc-fire14:~# cd /home/workload_scripts/
root@ltc-fire14:/home/workload_scripts# ls
find_work.sh  run_workload.sh
root@ltc-fire14:/home/workload_scripts# ./run_workload.sh
root@ltc-fire14:/home/workload_scripts# getscom -l
Chip ID  | Rev   | Chip type
-|---|
8085 | DD2.0 | Centaur memory buffer
8084 | DD2.0 | Centaur memory buffer
8005 | DD2.0 | Centaur memory buffer
8004 | DD2.0 | Centaur memory buffer
0008 | DD2.0 | P8 (Venice) processor
 | DD2.0 | P8 (Venice) processor
root@ltc-fire14:/home/workload_scripts# getscom -c 0x0 11013100
0
root@ltc-fire14:/home/workload_scripts# getscom -c 0x0 11013106
15a20c688a448b01
root@ltc-fire14:/home/workload_scripts# getscom -c 0x0 11013107
ea5c13970598
root@ltc-fire14:/home/workload_scripts# putscom -c 0x0 11013107 fa5c13970598
fa5c13970598
root@ltc-fire14:/home/workload_scripts# getscom -c 0x0 11013107
fa5c13970598
root@ltc-fire14:/home/workload_scripts# putscom -c 0x0 11013100 1000
[  333.045651] Fatal Hypervisor Maintenance interrupt [Not recovered]
[  333.045916]  Error detail: Malfunction Alert
[  333.046288]  HMER: 8040
[  333.046543]  CPU PIR: 
[  333.046601]  [Unit: IFU] RegFile core check stop
[  333.046778]  [Unit: PC ] Debug Trigger Error inject
1008[  333.046883] F
[194049345926,0] OPAL: Reboot requested due to Platform 
error.at[194049767279,3] OPAL: Reboot requested due to Platform error.al  
1.69405|ERRL|Dumping errors reported prior to registration
3.46924|Ignoring boot flags, incorrect version 0x0
3.70396|ISTEP  6. 3
4.14478|ISTEP  6. 4
4.14531|ISTEP  6. 5
10.54385|HWAS|PRESENT> DIMM[03]=
10.54386|HWAS|PRESENT> Membuf[04]=0C0C
10.54387|HWAS|PRESENT> Proc[05]=C000
23.49515|ISTEP  6. 6
[...]


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

Title:
  Trigger a checkstop on unrecoverable MCE/HMI errors to inform BMC/OCC
  about the error.

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

Bug description:
  The current implementation of Machine Check handler and HMI handler in
  Linux, goes down kernel panic path for unrecoverable errors. On FSP
  based system FSP also gets notified about these errors which then
  forwards it to PRD (that runs on FSP) for error analysis and gard
  record creation.

  On OpenPower (BMC based system e.g. Habanero from TYAN) where PRD runs
  in Linux host, it never gets a chance to do error analysis at the time
  of Linux crash and no gard record is created for such errors. Since
  the faulty component never gets de-configured, the system is
  vulnerable to get hit by same HW error again.

  To fix this issue, a new OPAL call 'opal_cec_reboot2()' has been
  introduced to trigger a checkstop on BMC based system to inform
  BMC/OCC about this error, so that BMC can collect relevant data for
  error analysis and decide what component to de-configure before
  rebooting. Linux kernel should invoke this opal call for unrecoverable
  MCE and HMI instead before calling kernel panic so that OCC is
  informed about the error.

  The kernel changes has already been posted to upstream and are listed
  below:

  https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-May/128341.html
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-May/128342.html
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-August/132045.html
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-August/132114.html 

  Above patches needs to be included in ubuntu 14.04.3+

  We will update this bug with commit ids, once the above patches are
  accepted upstream.

  Contact Information = mahesh.salgaon...@in.ibm.com 
   
  ---uname output---
  Linux rcx2d403 3.19.0-26-generic #27 SMP Tue Aug 4 01:38:15 CDT 2015 ppc64le 
ppc64le ppc64le GNU/Linux
   
  ---Additional Hardware Info---
  Habanero pass2 system 

   
  Machine Type = OpenPower, Habanero 
   
  ---System Hang---
   If system is hung, it can be recovered by sending ipmi power off/on command.
  $ ipmitool -H  -I lanplus -U  -P  power off
  $ 

[Kernel-packages] [Bug 1510570] [NEW] BLE pairing fail

[Guilhem Lettron]

Public bug reported:

On 15.10 we now have bluez 5 so we can pair BLE devices like the
Microsoft Arc Touch Bluetooth Mouse.

But this pairing doesn't work very well. Mouse is seen but pairing fail.
More informations: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

This is due to udev rule that use "hcitool" to power on device.
Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used instead 
of udev rules.

here is a commit with this parameter: 
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
And a ppa to test it: 
https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable

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


** Tags: wily

** Branch linked: lp:~guilhem-fr/bluez/autoenable

** Branch linked: lp:ubuntu/wily/bluez

** Summary changed:

- BLE pairing failed
+ BLE pairing fail

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

Title:
  BLE pairing fail

Status in bluez package in Ubuntu:
  New

Bug description:
  On 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More informations: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used 
instead of udev rules.

  here is a commit with this parameter: 
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  And a ppa to test it: 
https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable

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

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

[Kernel-packages] [Bug 1440536] Re: Oops __d_lookup+0x88/0x194

[Fathi Boudra]

Ming Lei,

yes, on Mustang. We're using U-Boot.

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

Title:
  Oops __d_lookup+0x88/0x194

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Vivid:
  Triaged

Bug description:
  This started happening on a Mustang board after upgrading to
  3.19.0-9.9 and persists in 3.19.0-11.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-11-generic 3.19.0-11.11
  ProcVersionSignature: Ubuntu 3.19.0-11.11-generic 3.19.3
  Uname: Linux 3.19.0-11-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Dec 31  1969 seq
   crw-rw 1 root audio 116, 33 Dec 31  1969 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.17-0ubuntu1
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', 
'/dev/snd/seq'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Sun Apr  5 08:32:28 2015
  HibernationDevice: RESUME=UUID=014663f6-5135-4075-bf04-d2f42c4fc90b
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,115200n8 ro 
earlyprintk=uart8250-32bit,0x1c02
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-11-generic N/A
   linux-backports-modules-3.19.0-11-generic  N/A
   linux-firmware 1.143
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  SystemImageInfo:
   current build number: 0
   device name: ?
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1400235] Re: 10de:11fc [Dell Precision M4800] Screen does not wake up after sleep

[Marius B. Kotsbak]

This bug disappeared some time in Vivid (but the not able to adjust
screen brightness), but now that I upgraded to Wily (15.10), the problem
is back.

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

** Tags added: wily

** Tags removed: latest-bios-a11
** Tags added: latest-bios-a14

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

Title:
  10de:11fc [Dell Precision M4800] Screen does not wake up after sleep

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When the laptop is either set to sleep by entering Fn-F1 or by
  timeout, the screen is black after waking it up again (using the power
  button, it does not wake by mousepad movement or key presses).

  In earlier Ubuntu versions (14.04), a workaround was to enter a
  terminal console by hitting CTRL-ALT-F1, CTRL-ALT-F7, but that does
  not seem to work anymore.

  The problem is is present in todays (2014-12-8) Vivid daily image
  (booted with "nomodeset", but not done any configuration of the
  screen).

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  .tmp.unity.support.test.1:

  ApportVersion: 2.14.7-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.346
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Dec  8 08:28:24 2014
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Dell Device [1028:05cc]
  LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141207)
  MachineType: Dell Inc. Precision M4800
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash nomodeset --
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/26/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 077KCT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd06/26/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn077KCT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4800
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.58-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.1.901-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Mon Dec  8 08:27:01 2014
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.16.1.901-1ubuntu1

  $ cat /proc/acpi/wakeup 
  Device  S-state   Status   Sysfs node
  UAR1  S3*disabled  pnp:00:06
  RP01  S4*disabled  pci::00:1c.0
  PXSX  S4*disabled
  RP02  S4*disabled
  PXSX  S4*disabled
  RP03  S4*disabled  pci::00:1c.2
  PXSX  S4*disabled  pci::03:00.0
  RP04  S4*disabled  pci::00:1c.3
  PXSX  S4*disabled
  RP05  S4*disabled  pci::00:1c.4
  PXSX  S4*disabled
  RP06  S4*disabled
  PXSX  S4*disabled
  RP07  S4*disabled  pci::00:1c.6
  PXSX  S4*disabled
  RP08  S4*disabled  pci::00:1c.7
  PXSX  S4*disabled  pci::11:00.0
  GLAN  S4*enabled   pci::00:19.0
  EHC1  S3*enabled   pci::00:1d.0
  EHC2  S3*enabled   pci::00:1a.0
  XHC   S4*enabled   pci::00:14.0
  HDEF  S4*disabled  pci::00:1b.0
  TPD4  S4*disabled
  TPD7  S0*disabled
  TPD8  S0*disabled
  PEG0  S4*disabled  pci::00:01.0
  PEGP  S4*disabled  pci::01:00.0
  PEG1  S4*disabled
  PEG2  S4*disabled
  LID0  S3*enabled   platform:PNP0C0D:00
  

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

[Brad Figg]

Here's the relevant information:

precise linux-lts-trusty 3.13.0-67.110~precise1 REGR
summary

Please verify test results in http://people.canonical.com/~kernel/status
/adt-matrix/overall.txt


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

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Incomplete

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

Title:
  linux-lts-trusty: 3.13.0-67.110~precise1 -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:
  New
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:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Friday, 23. October 2015 20:02 UTC
  kernel-stable-master-bug:1509341
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Monday, 26. October 2015 19:05 UTC
  kernel-stable-Promote-to-proposed-start:Monday, 26. October 2015 19:05 UTC
  kernel-stable-phase-changed:Monday, 26. October 2015 19:05 UTC

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

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

[Kernel-packages] [Bug 1335691] Re: Server 14.04 does not set static IPv6 addresses on interfaces when auto-config options are turned off

[René Diepstraten]

Unfortunately, I'm not allowed to run apport-collect on the creator's behalf.
It seems to be as follows:

when adding a file in /etc/sysctl.d with temp_addr=0 with a higher number as to 
prevent updates from overwriting my settings, the bug is present.
When editing 10-ipv6-privacy.conf , it seems to work fine.
It's still a bug though.


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

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

Title:
  Server 14.04 does not set static IPv6 addresses on interfaces when
  auto-config options are turned off

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On Ubuntu server 14.04 (upgraded from 13.10) I am trying to get rid of
  the IPv6 auto-config addresses and leave on my statically assigned
  ones. The system has two interfaces, a physical eth0 and vlan10.

  1. privext 0 in /etc/network/interfaces

  When I set the "privext 0" option for both interfaces in
  /etc/network/interfaces, then vlan10 does not get the configured
  static IPv6 address. It only gets the IPv6 link local address.
  However, eth0 is configured as expected with just the given static
  address.

  Using "privext 0" on only one or the other, but not both, worked as
  expected.

  
  2.  net.ipv6.conf.*.use_tempaddr = 0 in /etc/sysctl.conf

  If I add both net.ipv6.conf.eth0.use_tempaddr = 0 and
  net.ipv6.conf.vlan10.use_tempaddr = 0 of /etc/sysctl.conf, then the
  situation is reversed. Vlan10 is configured as expected with just its
  given address and eth0 has only the link-local address.

  If I add only net.ipv6.conf.eth0.use_tempaddr = 0, then again eth0
  only gets the link local address and not the assigned static.

  On using net.ipv6.conf.vlan10.use_tempaddr = 0, then everything ended
  up as expected - eth0 had the auto-config addresses plus its static
  address and vlan10 only had the static address.

  
  1 + 2 kludging attempt:

  Unfortunately, combining net.ipv6.conf.vlan10.use_tempaddr = 0 in
  sysctl.conf and "privext 0" in /etc/network/interfaces for eth0, both
  of which worked as expected alone, did not work togther. The result
  was the same as setting net.ipv6.conf.*.use_tempaddr = 0 on bothg, as
  mentioned above.

  
  3.  net.ipv6.conf.*.use_tempaddr = 0 in /etc/sysctl.conf

  Using net.ipv6.conf.*.autoconf = 0 resulted in eth0 getting only it's
  static address as expected, but vlan10 was still given the autoconfig
  addresses.

  Using only net.ipv6.conf.vlan10.autoconf = 0 had no effect, the
  interface still go the auto-config addresses. Using only
  net.ipv6.conf.eth0.autoconf = 0 did work.

  
  2 + 3 kludging attempt:

  What finally worked was the combination of
  net.ipv6.conf.vlan10.autoconf = 0 and
  net.ipv6.conf.vlan10.use_tempaddr = 0

  Summary:

  So it looks like that of all thee three methods one can potentially
  use to get rid of IPv^ auto-config addresses, one simply doesn't work
  on vlan interfaces and the other two have weird transitive side
  effects when applied at the same time to a parent physical interface
  and a child vlan interface when one would expect them to be entirely
  independent.

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

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

[Kernel-packages] [Bug 1510405] Re: Direct firmware load for radeon/kaveri_sdma1.bin failed with error -2

[Seth Forshee]

It appears AMD hasn't yet supplied these files to upstream linux-
firmware. I'll have to inquire with the radeon developers about this.

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

** Also affects: linux-firmware (Ubuntu Xenial)
   Importance: Undecided
 Assignee: Seth Forshee (sforshee)
   Status: In Progress

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

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

** Changed in: linux-firmware (Ubuntu Wily)
   Status: New => In Progress

** Changed in: linux-firmware (Ubuntu Wily)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: linux-firmware (Ubuntu Xenial)
   Importance: Undecided => Medium

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

Title:
  Direct firmware load for radeon/kaveri_sdma1.bin failed with error -2

Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-firmware source package in Wily:
  In Progress
Status in linux-firmware source package in Xenial:
  In Progress

Bug description:
  Version 1.149 of the package does not have
  /lib/firmware/radeon/kaveri_sdma1.bin needed for the latest AMD DRM
  module.

  After booting my monitor is blank.

  For other AMD chipsets *_sdma1.bin is needed as well:
  drivers/gpu/drm/amd/amdgpu/cik_sdma.c(126): snprintf(fw_name, 
sizeof(fw_name), "radeon/%s_sdma1.bin", chip_name);

  Similar to https://bugs.launchpad.net/ubuntu/+source/linux-
  firmware/+bug/1183777, https://bugs.launchpad.net/ubuntu/+source
  /linux-firmware/+bug/1218691

  Best regards,
  Timothy

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

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

[Kernel-packages] [Bug 1510570] Re: BLE pairing fail

[Guilhem Lettron]

** Description changed:

  On 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.
  
  But this pairing doesn't work very well. Mouse is seen but pairing fail.
- More informations: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5
+ More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5
  
  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used 
instead of udev rules.
  
  here is a commit with this parameter: 
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  And a ppa to test it: 
https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable

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

Title:
  BLE pairing fail

Status in bluez package in Ubuntu:
  New

Bug description:
  On 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used 
instead of udev rules.

  here is a commit with this parameter: 
http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138
  And a ppa to test it: 
https://code.launchpad.net/~guilhem-fr/+archive/ubuntu/bluez-autoenable

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

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

[Kernel-packages] [Bug 1510612] [NEW] package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17

[Karl-Philipp Richter]

Public bug reported:

package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to
install/upgrade: subprocess installed post-installation script returned
error exit status 17

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-17-generic 4.2.0-17.21
ProcVersionSignature: Ubuntu 4.2.0-17.20-generic 4.2.3
Uname: Linux 4.2.0-17-generic x86_64
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   richter3412 F...m pulseaudio
 /dev/snd/controlC0:  root   2162 F fsodeviced
  richter3412 F pulseaudio
Date: Tue Oct 27 16:42:31 2015
DuplicateSignature: package:linux-image-4.2.0-17-generic:4.2.0-17.21:subprocess 
installed post-installation script returned error exit status 17
ErrorMessage: subprocess installed post-installation script returned error exit 
status 17
HibernationDevice: RESUME=UUID=bd202ae7-9602-46bb-88fb-ae03a8769732
InstallationDate: Installed on 2015-09-14 (42 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: LENOVO 20221
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-17-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
Title: package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev'
UpgradeStatus: Upgraded to wily on 2015-10-23 (4 days ago)
dmi.bios.date: 07/12/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 71CN51WW(V1.21)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: INVALID
dmi.board.vendor: LENOVO
dmi.board.version: 3193WIN8 STD MLT
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Z500 Touch
dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
dmi.product.name: 20221
dmi.product.version: Lenovo IdeaPad Z500 Touch
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-package package-from-proposed 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/1510612

Title:
  package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

Status in linux package in Ubuntu:
  New

Bug description:
  package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-17-generic 4.2.0-17.21
  ProcVersionSignature: Ubuntu 4.2.0-17.20-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   richter3412 F...m pulseaudio
   /dev/snd/controlC0:  root   2162 F fsodeviced
richter3412 F pulseaudio
  Date: Tue Oct 27 16:42:31 2015
  DuplicateSignature: 
package:linux-image-4.2.0-17-generic:4.2.0-17.21:subprocess installed 
post-installation script returned error exit status 17
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 17
  HibernationDevice: RESUME=UUID=bd202ae7-9602-46bb-88fb-ae03a8769732
  InstallationDate: Installed on 2015-09-14 (42 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20221
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-17-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-23 (4 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 

[Kernel-packages] [Bug 1509103] Re: Update i915 Skylake firmware to version 1.23

[Timo Aaltonen]

vivid needs this too

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

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

Title:
  Update i915 Skylake firmware to version 1.23

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware source package in Trusty:
  New
Status in linux-firmware source package in Vivid:
  New
Status in linux-firmware source package in Wily:
  Fix Committed

Bug description:
  This is a critical update for Skylake hardware which includes a
  workaround for a Pcode/punit issue that is causing RAM corruption.

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

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

[Kernel-packages] [Bug 1509362] kili (amd64) - tests ran: 2, failed: 0

[Brad Figg]

tests ran:   2, failed: 0;
  
http://kernel.ubuntu.com/testing/3.16.0-52.71~14.04.1/kili__3.16.0-52.71~14.04.1__2015-10-27_14-03-00/results-index.html

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

Title:
  linux-lts-utopic: 3.16.0-52.71~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-utopic package in Ubuntu:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  New

Bug description:
  This bug is for tracking the 3.16.0-52.71~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, 23. October 2015 13:30 UTC
  kernel-stable-Prepare-package-end:Saturday, 24. October 2015 00:02 UTC
  kernel-stable-Promote-to-proposed-start:Saturday, 24. October 2015 00:02 UTC
  kernel-stable-Promote-to-proposed-end:Monday, 26. October 2015 17:38 UTC
  kernel-stable-phase:Verification & Testing
  kernel-stable-phase-changed:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Verification-testing-start:Monday, 26. October 2015 19:02 UTC
  kernel-stable-Certification-testing-start:Monday, 26. October 2015 19:03 UTC
  kernel-stable-Security-signoff-start:Monday, 26. October 2015 19:03 UTC
  proposed-announcement-sent:True
  kernel-stable-Regression-testing-start:Monday, 26. October 2015 19:03 UTC
  kernel-stable-Security-signoff-end:Tuesday, 27. October 2015 10:00 UTC

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

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

[Kernel-packages] [Bug 1509489] Re: No support for seccomp filters

[Kyle Fazzari]

** Description changed:

- The snappy confinement model utilizes both apparmor and seccomp filters,
- and while the former is supported by the phone kernel, the latter is
- not. Snappy cannot be used on the mako, krillin, or vegetahd without
- seccomp filters being backported.
+ [Impact]
+ 
+  * The snappy confinement model utilizes both apparmor and seccomp filters, 
and
+while the former is supported by the phone kernel, the latter is not. 
Snappy
+cannot be used on the mako, krillin, or vegetahd without seccomp filters
+being backported.
+ 
+ [Test Case]
+ 
+  * Run the tests located here:
+ 
+http://kernel.ubuntu.com/git/kyrofa/ubuntu-
+ 
vivid.git/tree/tools/testing/selftests/seccomp?h=backport_seccomp_filters=555777b2449cb4a69604998e8550001231a0f6af
+ 
+They will fail without this change.
+ 
+ [Regression Potential]
+ 
+  * AppArmor regression regarding its use of no_new_privs, since it was
+previously a fake implementation to facilitate the v3 backport.

** Description changed:

  [Impact]
  
-  * The snappy confinement model utilizes both apparmor and seccomp filters, 
and
-while the former is supported by the phone kernel, the latter is not. 
Snappy
-cannot be used on the mako, krillin, or vegetahd without seccomp filters
-being backported.
+  * The snappy confinement model utilizes both apparmor and seccomp
+ filters, and while the former is supported by the phone kernel, the
+ latter is not. Snappy cannot be used on the mako, krillin, or vegetahd
+ without seccomp filters being backported.
  
  [Test Case]
  
-  * Run the tests located here:
+  * Run the tests located here:
  
-http://kernel.ubuntu.com/git/kyrofa/ubuntu-
+    http://kernel.ubuntu.com/git/kyrofa/ubuntu-
  
vivid.git/tree/tools/testing/selftests/seccomp?h=backport_seccomp_filters=555777b2449cb4a69604998e8550001231a0f6af
  
-They will fail without this change.
+    They will fail without this change.
  
  [Regression Potential]
  
-  * AppArmor regression regarding its use of no_new_privs, since it was
-previously a fake implementation to facilitate the v3 backport.
+  * AppArmor regression regarding its use of no_new_privs, since it was
+ previously a fake implementation to facilitate the v3 backport.

** Description changed:

  [Impact]
  
   * The snappy confinement model utilizes both apparmor and seccomp
  filters, and while the former is supported by the phone kernel, the
  latter is not. Snappy cannot be used on the mako, krillin, or vegetahd
  without seccomp filters being backported.
  
  [Test Case]
  
   * Run the tests located here:
  
     http://kernel.ubuntu.com/git/kyrofa/ubuntu-
  
vivid.git/tree/tools/testing/selftests/seccomp?h=backport_seccomp_filters=555777b2449cb4a69604998e8550001231a0f6af
  
     They will fail without this change.
  
  [Regression Potential]
  
-  * AppArmor regression regarding its use of no_new_privs, since it was
- previously a fake implementation to facilitate the v3 backport.
+  * Potential AppArmor regression regarding its use of no_new_privs,
+ since it was previously a fake implementation to facilitate the v3
+ backport.

** Description changed:

  [Impact]
  
   * The snappy confinement model utilizes both apparmor and seccomp
  filters, and while the former is supported by the phone kernel, the
  latter is not. Snappy cannot be used on the mako, krillin, or vegetahd
  without seccomp filters being backported.
  
  [Test Case]
  
   * Run the tests located here:
  
     http://kernel.ubuntu.com/git/kyrofa/ubuntu-
  
vivid.git/tree/tools/testing/selftests/seccomp?h=backport_seccomp_filters=555777b2449cb4a69604998e8550001231a0f6af
  
     They will fail without this change.
  
  [Regression Potential]
  
   * Potential AppArmor regression regarding its use of no_new_privs,
  since it was previously a fake implementation to facilitate the v3
  backport.
+ 
+ [Other Info]
+ 
+  * Backport is from mainline.
+  * Backport only includes seccomp filters introduced in v3.5 (e.g. does not 
include syscall or tsync).

** Summary changed:

- No support for seccomp filters
+ [SRU] seccomp filters backport for Mako

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

Title:
  [SRU] seccomp filters backport for Mako

Status in linux-mako package in Ubuntu:
  New

Bug description:
  [Impact]

   * The snappy confinement model utilizes both apparmor and seccomp
  filters, and while the former is supported by the phone kernel, the
  latter is not. Snappy cannot be used on the mako, krillin, or vegetahd
  without seccomp filters being backported.

  [Test Case]

   * Run the tests located here:

     http://kernel.ubuntu.com/git/kyrofa/ubuntu-
  
vivid.git/tree/tools/testing/selftests/seccomp?h=backport_seccomp_filters=555777b2449cb4a69604998e8550001231a0f6af

     They will fail without this change.

  

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

[Chris J Arges]

linux-lts-trusty| 3.13.0-67.110~precise1 | precise-proposed | source
 linux-meta-lts-trusty   | 3.13.0.67.59   | precise-proposed | source
 linux-signed-lts-trusty | 3.13.0-67.110~precise1 | precise-proposed | source

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Released

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

Title:
  linux-lts-trusty: 3.13.0-67.110~precise1 -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:
  New
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:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Friday, 23. October 2015 20:02 UTC
  kernel-stable-master-bug:1509341
  kernel-stable-phase:CopyToProposed
  kernel-stable-Prepare-package-end:Monday, 26. October 2015 19:05 UTC
  kernel-stable-Promote-to-proposed-start:Monday, 26. October 2015 19:05 UTC
  kernel-stable-phase-changed:Monday, 26. October 2015 19:05 UTC

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

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

[Kernel-packages] [Bug 1509103] Re: Update i915 Skylake firmware to version 1.23

[Timo Aaltonen]

oh and trusty of course..

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

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

Title:
  Update i915 Skylake firmware to version 1.23

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware source package in Trusty:
  New
Status in linux-firmware source package in Vivid:
  New
Status in linux-firmware source package in Wily:
  Fix Committed

Bug description:
  This is a critical update for Skylake hardware which includes a
  workaround for a Pcode/punit issue that is causing RAM corruption.

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

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

[Kernel-packages] [Bug 1510616] [NEW] add new iwlwifi firmware for 7265D

[Timo Aaltonen]

Public bug reported:

My Intel SDP has a version of the hw that needs at least "iwlwifi-
7265D-17.ucode", though I'm not sure where to get that, since upstream
repo doesn't have it.

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

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

Title:
  add new iwlwifi firmware for 7265D

Status in linux-firmware package in Ubuntu:
  New

Bug description:
  My Intel SDP has a version of the hw that needs at least "iwlwifi-
  7265D-17.ucode", though I'm not sure where to get that, since upstream
  repo doesn't have it.

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

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

[Kernel-packages] [Bug 1335691] Re: Server 14.04 does not set static IPv6 addresses on interfaces when auto-config options are turned off

[René Diepstraten]

This bug is still present.
When setting "net.ipv6.conf.br0.use_tempaddr = 0" , the
"iface br0 inet6 static" and following lines are ignored when rebooting.
Setting it back to 2 solves the problem.

When issuing "ifdown br0 && ifup br0", IPv6 just works with
use_tempaddr=0 .

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

Title:
  Server 14.04 does not set static IPv6 addresses on interfaces when
  auto-config options are turned off

Status in linux package in Ubuntu:
  Expired

Bug description:
  On Ubuntu server 14.04 (upgraded from 13.10) I am trying to get rid of
  the IPv6 auto-config addresses and leave on my statically assigned
  ones. The system has two interfaces, a physical eth0 and vlan10.

  1. privext 0 in /etc/network/interfaces

  When I set the "privext 0" option for both interfaces in
  /etc/network/interfaces, then vlan10 does not get the configured
  static IPv6 address. It only gets the IPv6 link local address.
  However, eth0 is configured as expected with just the given static
  address.

  Using "privext 0" on only one or the other, but not both, worked as
  expected.

  
  2.  net.ipv6.conf.*.use_tempaddr = 0 in /etc/sysctl.conf

  If I add both net.ipv6.conf.eth0.use_tempaddr = 0 and
  net.ipv6.conf.vlan10.use_tempaddr = 0 of /etc/sysctl.conf, then the
  situation is reversed. Vlan10 is configured as expected with just its
  given address and eth0 has only the link-local address.

  If I add only net.ipv6.conf.eth0.use_tempaddr = 0, then again eth0
  only gets the link local address and not the assigned static.

  On using net.ipv6.conf.vlan10.use_tempaddr = 0, then everything ended
  up as expected - eth0 had the auto-config addresses plus its static
  address and vlan10 only had the static address.

  
  1 + 2 kludging attempt:

  Unfortunately, combining net.ipv6.conf.vlan10.use_tempaddr = 0 in
  sysctl.conf and "privext 0" in /etc/network/interfaces for eth0, both
  of which worked as expected alone, did not work togther. The result
  was the same as setting net.ipv6.conf.*.use_tempaddr = 0 on bothg, as
  mentioned above.

  
  3.  net.ipv6.conf.*.use_tempaddr = 0 in /etc/sysctl.conf

  Using net.ipv6.conf.*.autoconf = 0 resulted in eth0 getting only it's
  static address as expected, but vlan10 was still given the autoconfig
  addresses.

  Using only net.ipv6.conf.vlan10.autoconf = 0 had no effect, the
  interface still go the auto-config addresses. Using only
  net.ipv6.conf.eth0.autoconf = 0 did work.

  
  2 + 3 kludging attempt:

  What finally worked was the combination of
  net.ipv6.conf.vlan10.autoconf = 0 and
  net.ipv6.conf.vlan10.use_tempaddr = 0

  Summary:

  So it looks like that of all thee three methods one can potentially
  use to get rid of IPv^ auto-config addresses, one simply doesn't work
  on vlan interfaces and the other two have weird transitive side
  effects when applied at the same time to a parent physical interface
  and a child vlan interface when one would expect them to be entirely
  independent.

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

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

[Kernel-packages] [Bug 1510612] Re: package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 17

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-17-generic 4.2.0-17.21
  ProcVersionSignature: Ubuntu 4.2.0-17.20-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   richter3412 F...m pulseaudio
   /dev/snd/controlC0:  root   2162 F fsodeviced
richter3412 F pulseaudio
  Date: Tue Oct 27 16:42:31 2015
  DuplicateSignature: 
package:linux-image-4.2.0-17-generic:4.2.0-17.21:subprocess installed 
post-installation script returned error exit status 17
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 17
  HibernationDevice: RESUME=UUID=bd202ae7-9602-46bb-88fb-ae03a8769732
  InstallationDate: Installed on 2015-09-14 (42 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20221
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-17-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-23 (4 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1509103] Re: Update i915 Skylake firmware to version 1.23

[Timo Aaltonen]

Hello Seth, or anyone else affected,

Accepted linux-firmware into wily-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.149.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: linux-firmware (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-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1509103

Title:
  Update i915 Skylake firmware to version 1.23

Status in linux-firmware package in Ubuntu:
  Confirmed
Status in linux-firmware source package in Trusty:
  New
Status in linux-firmware source package in Vivid:
  New
Status in linux-firmware source package in Wily:
  Fix Committed

Bug description:
  This is a critical update for Skylake hardware which includes a
  workaround for a Pcode/punit issue that is causing RAM corruption.

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

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

[Kernel-packages] [Bug 1509929] Re: kernel panic after booting up 4 hours

[Stefan Bader]

Thanks for the update, I will submit the missing patch to upstream
stable and in parallel try to get it included in the distro kernel as
soon as possible.

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

Title:
  kernel panic after booting up 4 hours

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Wily from Vivid, I always meet kernal panic after
  booting up 4 hours;

  I use wireless, the Ethernet cable is not connected.

  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-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alfred 5470 F pulseaudio
   /dev/snd/controlC0:  alfred 5470 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Oct 26 12:57:59 2015
  HibernationDevice: RESUME=UUID=a9831098-f784-41f9-b1f4-7f39b1040838
  InstallationDate: Installed on 2015-01-23 (275 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  MachineType: LENOVO 20ANS01N00
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed 
root=UUID=cf490836-5dbd-4c19-8796-52575400a1f9 ro nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-16-generic N/A
   linux-backports-modules-4.2.0-16-generic  N/A
   linux-firmware1.149
  SourcePackage: linux
  UpgradeStatus: Upgraded to wily on 2015-10-23 (2 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET79WW (2.33 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20ANS01N00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0A46860 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET79WW(2.33):bd06/23/2015:svnLENOVO:pn20ANS01N00:pvrThinkPadT440p:rvnLENOVO:rn20ANS01N00:rvrSDK0A46860WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20ANS01N00
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

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

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

[Brad Figg]

This change was made by a bot.

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

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

Title:
  package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 17

  ProblemType: Package
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.2.0-17-generic 4.2.0-17.21
  ProcVersionSignature: Ubuntu 4.2.0-17.20-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   richter3412 F...m pulseaudio
   /dev/snd/controlC0:  root   2162 F fsodeviced
richter3412 F pulseaudio
  Date: Tue Oct 27 16:42:31 2015
  DuplicateSignature: 
package:linux-image-4.2.0-17-generic:4.2.0-17.21:subprocess installed 
post-installation script returned error exit status 17
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 17
  HibernationDevice: RESUME=UUID=bd202ae7-9602-46bb-88fb-ae03a8769732
  InstallationDate: Installed on 2015-09-14 (42 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: LENOVO 20221
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-17-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit 
code 2:
  Title: package linux-image-4.2.0-17-generic 4.2.0-17.21 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 17
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: Upgraded to wily on 2015-10-23 (4 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1509803] Re: Bluetooth Will not work

[Mitch Dabbas]

Bluetooth still doesn't work. If I force it on, I still get no adapters
found, when trying to add any bluetooth device.

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

Title:
  Bluetooth Will not work

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  I have an issue with my Bluetooth, in a Lenovo 50-70.  It will not
  turn on, and if I try to turn it on, it gives the messsage that no
  adapters found.  I tied converting the .hex windows driver t .hcd, but
  that didn't help.  Below is my info:

  02:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n 
[14e4:4365] (rev 01)
  Subsystem: Lenovo Device [17aa:0621]
  Kernel driver in use: wl
  Bus 003 Device 002: ID 8087:8000 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 105b:e065
  Bus 001 Device 004: ID 5986:055d Acer, Inc
  Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
  Bus 001 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical 
Mouse
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  
  dmesg | grep -i blue
  [ 36.077001] Bluetooth: Core ver 2.20
  [ 36.077016] Bluetooth: HCI device and connection manager initialized
  [ 36.077018] Bluetooth: HCI socket layer initialized
  [ 36.077020] Bluetooth: L2CAP socket layer initialized
  [ 36.077024] Bluetooth: SCO socket layer initialized
  [ 36.165964] Bluetooth: RFCOMM TTY layer initialized
  [ 36.165973] Bluetooth: RFCOMM socket layer initialized
  [ 36.165978] Bluetooth: RFCOMM ver 1.11
  [ 36.192237] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [ 36.192239] Bluetooth: BNEP filters: protocol multicast
  [ 36.192242] Bluetooth: BNEP socket layer initialized
  ls -l /lib/firmware/brcm
  total 7716
  -rw-rw-r-- 1 root root 28263 Oct 23 22:38 BCM43142A0-105b:e065.hcd
  -rw-r--r-- 1 root root 269595 Nov 24 2014 bcm4329-fullmac-4.bin
  -rw-r--r-- 1 root root 96224 Dec 1 2014 bcm43xx-0.fw
  -rw-r--r-- 1 root root 180 Dec 1 2014 bcm43xx_hdr-0.fw
  -rw-r--r-- 1 root root 397312 Dec 1 2014 brcmfmac43143.bin
  -rwxr-xr-x 1 root root 385067 Sep 24 16:20 brcmfmac43143-sdio.bin
  -rw-r--r-- 1 root root 348160 Nov 24 2014 brcmfmac43236b.bin
  -rw-r--r-- 1 root root 455745 Dec 1 2014 brcmfmac43241b0-sdio.bin
  -rw-r--r-- 1 root root 403855 Dec 1 2014 brcmfmac43241b4-sdio.bin
  -rw-r--r-- 1 root root 479232 Sep 24 16:20 brcmfmac43242a.bin
  -rw-r--r-- 1 root root 253748 Dec 1 2014 brcmfmac4329-sdio.bin
  -rw-r--r-- 1 root root 222126 Dec 1 2014 brcmfmac4330-sdio.bin
  -rw-r--r-- 1 root root 451566 Dec 1 2014 brcmfmac4334-sdio.bin
  -rw-r--r-- 1 root root 569291 Dec 1 2014 brcmfmac4335-sdio.bin
  -rw-r--r-- 1 root root 219557 Dec 1 2014 brcmfmac43362-sdio.bin
  -rw-r--r-- 1 root root 493599 Sep 24 16:20 brcmfmac4339-sdio.bin
  -rw-r--r-- 1 root root 507752 Sep 24 16:13 brcmfmac4354-sdio.bin
  -rw-r--r-- 1 root root 557056 Sep 24 16:20 brcmfmac43569.bin
  -rw-r--r-- 1 root root 550333 Sep 24 16:20 brcmfmac43570-pcie.bin
  -rw-r--r-- 1 root root 588940 Sep 24 16:20 brcmfmac43602-pcie.ap.bin
  -rw-r--r-- 1 root root 590544 Sep 24 16:20 brcmfmac43602-pcie.bin
  lspci -knn | grep Net -A2; lsusb
  02:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n 
[14e4:4365] (rev 01)
  Subsystem: Lenovo Device [17aa:0621]
  Kernel driver in use: wl
  Bus 003 Device 002: ID 8087:8000 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 105b:e065
  Bus 001 Device 004: ID 5986:055d Acer, Inc
  Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
  Bus 001 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical 
Mouse
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  
  After loading the .hcd file I get this

  dmesg | grep -i blue
  [ 24.144917] Bluetooth: Core ver 2.20
  [ 24.144932] Bluetooth: HCI device and connection manager initialized
  [ 24.144935] Bluetooth: HCI socket layer initialized
  [ 24.144937] Bluetooth: L2CAP socket layer initialized
  [ 24.144941] Bluetooth: SCO socket layer initialized
  [ 24.191155] Bluetooth: RFCOMM TTY layer initialized
  [ 24.191162] Bluetooth: RFCOMM socket layer initialized
  [ 24.191167] Bluetooth: RFCOMM ver 1.11
  [ 24.215839] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [ 24.215842] Bluetooth: BNEP filters: protocol multicast
  [ 24.215845] Bluetooth: BNEP socket layer initialized

  I have tried about everything I could find out there, and nothing
  helped.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.19.0-32-generic 3.19.0-32.37~14.04.1
  ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 

[Kernel-packages] [Bug 1509803] Re: Bluetooth Will not work

[Mitch Dabbas]

It has been named correctly, and still doesn't work.  I even connected a
drive that has windows on it, and it shows that the driver in use is:
BCM43142A0_001.001.011.0244.0245.hex.  Also tried that, and nothing
worked.  Thanks

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

Title:
  Bluetooth Will not work

Status in linux-lts-vivid package in Ubuntu:
  New

Bug description:
  I have an issue with my Bluetooth, in a Lenovo 50-70.  It will not
  turn on, and if I try to turn it on, it gives the messsage that no
  adapters found.  I tied converting the .hex windows driver t .hcd, but
  that didn't help.  Below is my info:

  02:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n 
[14e4:4365] (rev 01)
  Subsystem: Lenovo Device [17aa:0621]
  Kernel driver in use: wl
  Bus 003 Device 002: ID 8087:8000 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 105b:e065
  Bus 001 Device 004: ID 5986:055d Acer, Inc
  Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
  Bus 001 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical 
Mouse
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  
  dmesg | grep -i blue
  [ 36.077001] Bluetooth: Core ver 2.20
  [ 36.077016] Bluetooth: HCI device and connection manager initialized
  [ 36.077018] Bluetooth: HCI socket layer initialized
  [ 36.077020] Bluetooth: L2CAP socket layer initialized
  [ 36.077024] Bluetooth: SCO socket layer initialized
  [ 36.165964] Bluetooth: RFCOMM TTY layer initialized
  [ 36.165973] Bluetooth: RFCOMM socket layer initialized
  [ 36.165978] Bluetooth: RFCOMM ver 1.11
  [ 36.192237] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [ 36.192239] Bluetooth: BNEP filters: protocol multicast
  [ 36.192242] Bluetooth: BNEP socket layer initialized
  ls -l /lib/firmware/brcm
  total 7716
  -rw-rw-r-- 1 root root 28263 Oct 23 22:38 BCM43142A0-105b:e065.hcd
  -rw-r--r-- 1 root root 269595 Nov 24 2014 bcm4329-fullmac-4.bin
  -rw-r--r-- 1 root root 96224 Dec 1 2014 bcm43xx-0.fw
  -rw-r--r-- 1 root root 180 Dec 1 2014 bcm43xx_hdr-0.fw
  -rw-r--r-- 1 root root 397312 Dec 1 2014 brcmfmac43143.bin
  -rwxr-xr-x 1 root root 385067 Sep 24 16:20 brcmfmac43143-sdio.bin
  -rw-r--r-- 1 root root 348160 Nov 24 2014 brcmfmac43236b.bin
  -rw-r--r-- 1 root root 455745 Dec 1 2014 brcmfmac43241b0-sdio.bin
  -rw-r--r-- 1 root root 403855 Dec 1 2014 brcmfmac43241b4-sdio.bin
  -rw-r--r-- 1 root root 479232 Sep 24 16:20 brcmfmac43242a.bin
  -rw-r--r-- 1 root root 253748 Dec 1 2014 brcmfmac4329-sdio.bin
  -rw-r--r-- 1 root root 222126 Dec 1 2014 brcmfmac4330-sdio.bin
  -rw-r--r-- 1 root root 451566 Dec 1 2014 brcmfmac4334-sdio.bin
  -rw-r--r-- 1 root root 569291 Dec 1 2014 brcmfmac4335-sdio.bin
  -rw-r--r-- 1 root root 219557 Dec 1 2014 brcmfmac43362-sdio.bin
  -rw-r--r-- 1 root root 493599 Sep 24 16:20 brcmfmac4339-sdio.bin
  -rw-r--r-- 1 root root 507752 Sep 24 16:13 brcmfmac4354-sdio.bin
  -rw-r--r-- 1 root root 557056 Sep 24 16:20 brcmfmac43569.bin
  -rw-r--r-- 1 root root 550333 Sep 24 16:20 brcmfmac43570-pcie.bin
  -rw-r--r-- 1 root root 588940 Sep 24 16:20 brcmfmac43602-pcie.ap.bin
  -rw-r--r-- 1 root root 590544 Sep 24 16:20 brcmfmac43602-pcie.bin
  lspci -knn | grep Net -A2; lsusb
  02:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n 
[14e4:4365] (rev 01)
  Subsystem: Lenovo Device [17aa:0621]
  Kernel driver in use: wl
  Bus 003 Device 002: ID 8087:8000 Intel Corp.
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 005: ID 105b:e065
  Bus 001 Device 004: ID 5986:055d Acer, Inc
  Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
  Bus 001 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical 
Mouse
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  
  After loading the .hcd file I get this

  dmesg | grep -i blue
  [ 24.144917] Bluetooth: Core ver 2.20
  [ 24.144932] Bluetooth: HCI device and connection manager initialized
  [ 24.144935] Bluetooth: HCI socket layer initialized
  [ 24.144937] Bluetooth: L2CAP socket layer initialized
  [ 24.144941] Bluetooth: SCO socket layer initialized
  [ 24.191155] Bluetooth: RFCOMM TTY layer initialized
  [ 24.191162] Bluetooth: RFCOMM socket layer initialized
  [ 24.191167] Bluetooth: RFCOMM ver 1.11
  [ 24.215839] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [ 24.215842] Bluetooth: BNEP filters: protocol multicast
  [ 24.215845] Bluetooth: BNEP socket layer initialized

  I have tried about everything I could find out there, and nothing
  helped.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: