[Kernel-packages] [Bug 1425144] Re: build initial linux-lts-vivid

2015-03-02 Thread Andy Whitcroft
Created linux-lts-vivid, pushed to trusty repo, and uploaded to CKT PPA.
Still need the -signed and -meta.

** Changed in: linux-lts-utopic (Ubuntu)
Milestone: ubuntu-15.02 = ubuntu-15.03

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

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

** Changed in: linux-meta-lts-utopic (Ubuntu)
   Status: New = In Progress

** Changed in: linux-signed-lts-utopic (Ubuntu)
   Status: New = In Progress

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

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

** Changed in: linux-meta-lts-utopic (Ubuntu)
 Assignee: (unassigned) = Andy Whitcroft (apw)

** Changed in: linux-signed-lts-utopic (Ubuntu)
 Assignee: (unassigned) = Andy Whitcroft (apw)

** Changed in: linux-meta-lts-utopic (Ubuntu)
Milestone: None = ubuntu-15.03

** Changed in: linux-signed-lts-utopic (Ubuntu)
Milestone: None = ubuntu-15.03

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

Title:
  build initial linux-lts-vivid

Status in linux-lts-utopic package in Ubuntu:
  In Progress
Status in linux-meta-lts-utopic package in Ubuntu:
  In Progress
Status in linux-signed-lts-utopic package in Ubuntu:
  In Progress

Bug description:
  Need to start producing linux-lts-vivid now we are closing in on
  final.

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

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


[Kernel-packages] [Bug 1413664] Re: 15.04: consider enabling CONFIG_DEBUG_INFO_SPLIT and package the .dwo files

2015-03-02 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
Milestone: ubuntu-15.02 = ubuntu-15.03

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

Title:
  15.04: consider enabling CONFIG_DEBUG_INFO_SPLIT and package the .dwo
  files

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  There is a new more efficient debug format enabled via
  CONFIG_DEBUG_INFO_SPLIT, this spits out new .dwo files which need
  packaging in the .ddeb before we can enable this.  Evaluate whether
  the other tooling we have will handle it before doing so.

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

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


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

2015-03-02 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
Milestone: ubuntu-15.02 = ubuntu-15.03

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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


[Kernel-packages] [Bug 1415580] Re: add nvme to -virtual kernel

2015-03-02 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
Milestone: ubuntu-15.02 = ubuntu-15.03

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

Title:
  add nvme to -virtual kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  GCE has requested that the nvme kernel module be added to the GCE
  images. Please add nvme to the -virtual kernel series.

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

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


[Kernel-packages] [Bug 1408355] Re: devel: hv_vss_daemon now sports a -n flag to prevent daemonisation

2015-03-02 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
Milestone: ubuntu-14.04.2 = ubuntu-14.04.3

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

Title:
  devel: hv_vss_daemon now sports a -n flag to prevent daemonisation

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

Bug description:
  We now have an official way to prevent hv_vss_daemon from deamonising
  by default, the new -n flag mirrors the hack we have been carrying for
  some time.  We need to work out how to migrate to this new form whilst
  maintaining backwards compatibility.

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

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


[Kernel-packages] [Bug 1393877] Re: Hardware enablement meta-packages missing in Trusty

2015-03-02 Thread Andy Whitcroft
** Changed in: linux-meta (Ubuntu Trusty)
Milestone: ubuntu-14.04.2 = ubuntu-14.04.3

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

Title:
  Hardware enablement meta-packages missing in Trusty

Status in linux-meta package in Ubuntu:
  Invalid
Status in linux-meta source package in Trusty:
  Fix Released

Bug description:
  Precise contains a meta package (linux-hwe-generic) that allowed for
  automatic upgrades as HWE kernels expired. We need this same mechanism
  in Trusty.

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

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


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

2015-03-02 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
   Status: Confirmed = In Progress

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

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

Status in linux package in Ubuntu:
  In Progress

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

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

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


[Kernel-packages] [Bug 1426618] Re: Latest 3.13 kernel update (3.13.0-46) is causing kernel panics related to IPv6

2015-03-02 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = Andy Whitcroft (apw)

** Changed in: linux (Ubuntu Trusty)
 Assignee: (unassigned) = Andy Whitcroft (apw)

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

Title:
  Latest 3.13 kernel update (3.13.0-46) is causing kernel panics related
  to IPv6

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

Bug description:
  Hello,

  Pretty similar to what happened with
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404558 but this
  time with the latest 3.13.0-46.

  I've been getting about daily kernel panics (three times so far).

  Screenshot attached. Another user also commented in bug 1404558 about
  the bug being back, though I'm assuming it's a different albeit very
  similar one.

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

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


[Kernel-packages] [Bug 1426618] Re: Latest 3.13 kernel update (3.13.0-46) is causing kernel panics related to IPv6

2015-03-02 Thread Andy Whitcroft
From the looks of things, when v3.13.11-ckt14 was applied which also
contains the fix for the original issue, somehow the fix got applied
reversed and undid the fix!

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

Title:
  Latest 3.13 kernel update (3.13.0-46) is causing kernel panics related
  to IPv6

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

Bug description:
  Hello,

  Pretty similar to what happened with
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404558 but this
  time with the latest 3.13.0-46.

  I've been getting about daily kernel panics (three times so far).

  Screenshot attached. Another user also commented in bug 1404558 about
  the bug being back, though I'm assuming it's a different albeit very
  similar one.

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

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


[Kernel-packages] [Bug 1413968] Re: CONFIG_NO_HZ_IDLE should be the default

2015-03-02 Thread Andy Whitcroft
Confirmed as applied and released as of Ubuntu-3.19.0-7.7.

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

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

Title:
  CONFIG_NO_HZ_IDLE should be the default

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  We have a hodge podge of CONFIG_NO_HZ_IDLE and CONFIG_NO_HZ_FULL
  selected across the architectures.  From the documentation for
  CONFIG_NO_HZ_FULL this option does not even do anything positive until
  the user supplied a CPU list on the kernel command line, and it incurs
  a significant overhead overall.  From the docs we should commonise on
  CONFIG_NO_HZ_IDLE, and separately evaluate the overhead.

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

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


[Kernel-packages] [Bug 1308685] Re: vt_handoff patches were dropped, please resurrect them

2015-03-02 Thread Andy Whitcroft
This is confirmed as applied correctly to the v3.19.0-5.5 version and is
now released into vivid as of Ubuntu-3.19.0-7.7.

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

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

Title:
  vt_handoff patches were dropped, please resurrect them

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  at release sprint apw, cjwatson and I were debugging flickers at boot
  on my laptop. apw noticed that vt_handoff patches were missing in the
  kernel for a while and asked be to open a bug report about
  resurrecting them.

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

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


[Kernel-packages] [Bug 1418743] Re: support vagrant images -- vbox guest drivers in image

2015-03-02 Thread Andy Whitcroft
Initial versions of this applied and released as part of
Ubuntu-3.19.0-7.7.

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

Title:
  support vagrant images -- vbox guest drivers in image

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  We need to support vagrant cloud images.  This means we need binary
  (non-dkms) drivers for the virtualbox guest drivers.

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

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


[Kernel-packages] [Bug 1396383] Re: why signed kernels call update-grub?

2015-03-02 Thread Andy Whitcroft
As we have separate work items to switch to using triggers, this one can
be closed out as Won't Fix.

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

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

Title:
  why signed kernels call update-grub?

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  Looking at the postrm of linux-signed-image-* it looks very different
  from linux-image-* ones

  $ cat linux-signed-image-3.16.0-20-generic.postrm 
  #!/bin/sh -e

  kernel='vmlinuz-3.16.0-20-generic'

  case $0-$1 in
  *.postinst-configure)
rm -f /boot/$kernel.efi.signed
cp /boot/$kernel /boot/$kernel.efi.signed
sbattach --attach /usr/lib/linux/$kernel.efi.signature 
/boot/$kernel.efi.signed

if which update-grub /dev/null 21; then
update-grub || true
fi
;;
  *.postrm-remove)
rm -f /boot/$kernel.efi.signed

if which update-grub /dev/null 21; then
update-grub || true
fi
;;
  esac

  
  Why does it call update-grub direct instead of calling into /etc/kernel like 
the normal kernel packages do?

  In essence on amd64 the amount of calls to update-grub is duplicated
  on both installation and removal of kernel packages, since -signed
  version is installed by default. Why can't we just install signed
  version and make it modify kernel image in-place?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-signed-generic 3.16.0.25.26
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xnox   4525 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Nov 25 23:08:41 2014
  HibernationDevice: RESUME=UUID=2bf263f1-753f-4b2e-92a6-b00381515e0c
  InstallationDate: Installed on 2012-01-12 (1048 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130318)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-25-generic.efi.signed 
root=UUID=6669d411-80c3-41cc-a629-ad84e1ee6854 ro quiet splash nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw 
crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf 
nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M 
nomdmonddf nomdmonisw crashkernel=384M-:128M vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-25-generic N/A
   linux-backports-modules-3.16.0-25-generic  N/A
   linux-firmware 1.138
  RfKill:
   
  SourcePackage: linux
  SystemImageInfo:
   current build number: 0
   device name: ?
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 08/13/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F18g
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-D3H
  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.:bvrF18g:bd08/13/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-D3H: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/1396383/+subscriptions

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


[Kernel-packages] [Bug 1414618] Re: devel: review CONFIG_STACK_TRACER and CONFIG_FUNCTION_TRACER on armhf

2015-03-02 Thread Andy Whitcroft
Confirmed applied and released as of Ubuntu-3.19.0-7.7.

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

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

Title:
  devel: review CONFIG_STACK_TRACER and CONFIG_FUNCTION_TRACER on armhf

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  CONFIG_STACK_TRACER and CONFIG_FUNCTION_TRACER are off for armhf,
  though on for all other architectures including arm64.  Investigate
  why this is so.

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

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


[Kernel-packages] [Bug 1426618] Re: Latest 3.13 kernel update (3.13.0-46) is causing kernel panics related to IPv6

2015-03-02 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
   Status: Triaged = 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/1426618

Title:
  Latest 3.13 kernel update (3.13.0-46) is causing kernel panics related
  to IPv6

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

Bug description:
  Hello,

  Pretty similar to what happened with
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404558 but this
  time with the latest 3.13.0-46.

  I've been getting about daily kernel panics (three times so far).

  Screenshot attached. Another user also commented in bug 1404558 about
  the bug being back, though I'm assuming it's a different albeit very
  similar one.

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

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


[Kernel-packages] [Bug 1426618] Re: Latest 3.13 kernel update (3.13.0-46) is causing kernel panics related to IPv6

2015-03-02 Thread Andy Whitcroft
Ok on investigation it seems git am is broken in the sense it is quite
happy to apply a fix backwards without any warning:

$ git checkout -b TEST Ubuntu-3.13.0-45.74
$ git format-patch -1 f34c7de1e2df67ae3e370da8f6fa37e6e3219e7b
0001-ipv6-fix-swapped-ipv4-ipv6-mtu_reduced-callbacks.patch
$ git am 0001-ipv6-fix-swapped-ipv4-ipv6-mtu_reduced-callbacks.patch
Applying: ipv6: fix swapped ipv4/ipv6 mtu_reduced callbacks
$

Wrong, wrong, wrong, wrong wrong.

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

Title:
  Latest 3.13 kernel update (3.13.0-46) is causing kernel panics related
  to IPv6

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

Bug description:
  Hello,

  Pretty similar to what happened with
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1404558 but this
  time with the latest 3.13.0-46.

  I've been getting about daily kernel panics (three times so far).

  Screenshot attached. Another user also commented in bug 1404558 about
  the bug being back, though I'm assuming it's a different albeit very
  similar one.

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

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


[Kernel-packages] [Bug 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64

2015-02-27 Thread Andy Whitcroft
** Changed in: flash-kernel (Ubuntu)
   Importance: Undecided = Medium

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

Title:
  devel: DTBs have moved into vendor specific directories on arm64

Status in debian-installer package in Ubuntu:
  Confirmed
Status in flash-kernel package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in debian-installer source package in Trusty:
  In Progress
Status in flash-kernel source package in Trusty:
  In Progress
Status in linux source package in Trusty:
  Invalid

Bug description:
  The installed DTBs have moved into vendor specific directories.  We
  need to 1) make sure we are hoovering them up right, and 2) that the
  consumers thereof (d-i etc) are consuming them in the new locations.

  NOTE: this actually is only _installed_ into those new directories on
  arm64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1408004/+subscriptions

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


[Kernel-packages] [Bug 1386973] Re: Ubuntu 14.10 soft lockup with ATI Radeon R7 250 X

2015-03-03 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Vivid)
   Status: Fix Committed = Fix Released

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

Title:
  Ubuntu 14.10 soft lockup with ATI Radeon R7 250 X

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

Bug description:
  I have a VGA controller Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT 
[Radeon HD 7770/8760 / R7 250X].
  When I boot from the Utopic DVD I get to the language menu and I can select 
try ubuntu without installing, but after a few sencods I get BUG: soft lockup 
- CPU#0 stuck for 22s!' and the message just repeats every 22 secods forever.

  I tried setting nomodeset using the F6 menu, but I got exactly the
  same result.

  This is Ubuntu 14.10 64 bits which basically seems unable to boot with
  that hardware.

  The experience was the same with 14.04, but I thought 14.10 would be
  better. In 14.04 disabling the video card and booting off the
  integrated graphics let me set nomodeset in /etc/default/grub and I
  was able boot with the R7 250X with the VESA driver. Installed
  Catalyst afterwards.

  
  ===
  break-fix: - 16b036af31e1456cb69243a5a0c9ef801ecd1f17

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

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


[Kernel-packages] [Bug 1410741] Re: VDSO clock function may be miss-optimised leading to hangs on SMP systems

2015-03-03 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Utopic)
   Status: Fix Committed = Fix Released

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

Title:
  VDSO clock function may be miss-optimised leading to hangs on SMP
  systems

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

Bug description:
  commit 1ddf0b1b11aa8a90cef6706e935fc31c75c406ba
  Author: Andy Lutomirski l...@amacapital.net
  Date:   Sun Dec 21 08:57:46 2014 -0800

  x86, vdso: Use asm volatile in __getcpu

  In Linux 3.18 and below, GCC hoists the lsl instructions in the
  pvclock code all the way to the beginning of __vdso_clock_gettime,
  slowing the non-paravirt case significantly.  For unknown reasons,
  presumably related to the removal of a branch, the performance issue
  is gone as of

  e76b027e6408 x86,vdso: Use LSL unconditionally for vgetcpu

  but I don't trust GCC enough to expect the problem to stay fixed.

  There should be no correctness issue, because the __getcpu calls in
  __vdso_vlock_gettime were never necessary in the first place.

  Note to stable maintainers: In 3.18 and below, depending on
  configuration, gcc 4.9.2 generates code like this:

   9c3:   44 0f 03 e8 lsl%ax,%r13d
   9c7:   45 89 ebmov%r13d,%r11d
   9ca:   0f 03 d8lsl%ax,%ebx

  This patch won't apply as is to any released kernel, but I'll send a
  trivial backported version if needed.

  Fixes: 51c19b4f5927 x86: vdso: pvclock gettime support
  Cc: sta...@vger.kernel.org # 3.8+
  Cc: Marcelo Tosatti mtosa...@redhat.com
  Acked-by: Paolo Bonzini pbonz...@redhat.com
  Signed-off-by: Andy Lutomirski l...@amacapital.net

  ===
  break-fix: 51c19b4f5927f5a646e93d69f73c7e89ea14e737 
1ddf0b1b11aa8a90cef6706e935fc31c75c406ba

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

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


[Kernel-packages] [Bug 1410519] Re: [PowerVM] Kernel BUG @ kernel/irq_work.c:157! - 24x7 hw counters

2015-03-03 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
   Status: Confirmed = Fix Released

** Tags removed: kernel-bug-break-fix

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

Title:
  [PowerVM] Kernel BUG @ kernel/irq_work.c:157!  - 24x7 hw counters

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

Bug description:
  [Impact]
  Using perf with hv_24x7 events can cause a kernel BUG.

  [Fix]
  The following upstream commits:
   d658972
   48bee8a
   f34b6c7
   ec2aef5

  [Test Case]
  Steps to recreate the problem:

  1.  Install Ubuntu 15.04 as a PowerVM guest.
  2.  Install perf tool
  3.  Run following scripts to test 24/7 Power8 hardware counter event with 
perf. tool

  ===  Script 1
  #!/bin/bash

  count=0;

  offset=0x128
  PERF_ARGS=-r 10 -C 0
  while [ $count -lt 100 ]; do

  EVENT=hv_24x7/domain=0x2,offset=$offset,starting_index=10/

  perf stat $PERF_ARGS -x ' ' perf stat $PERF_ARGS -x ' ' -e
  $EVENT ls

  count=)
  done

   Script 2
  #!/bin/bash

  offset=0;

  PERF_ARGS=-r 10 -C 0
  while [ $offset -lt 8192 ]; do

  EVENT=hv_24x7/domain=0x2,offset=$offset,starting_index=10/

  perf stat $PERF_ARGS -x ' ' perf stat $PERF_ARGS -x ' ' -e
  $EVENT ls

  offset=)
  done

  After few iterations I hit the following BUG.

  tt2.sh  tt.sh
  tt2.sh  tt.sh
  tt2.sh  tt.sh
  275679187521558  hv_24x7/domain=0x2,offset=6848,starting_index=10/ 0.00%
  tt2.sh  tt.sh
  [ 4657.314709] softirq: huh, entered softirq 7 SCHED c010abc0 with 
preem
  pt_count 0100, exited with bfff?
  [ 4657.314727] kernel BUG at /build/buildd/linux-3.16.0/kernel/irq_work.c:157!
  [ 4657.314732] Oops: Exception in kernel mode, sig: 5 [#1]
  [ 4657.314740] Modules linked in: rtc_generic pseries_rng
  [ 4657.314749] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.16.0-25-generic 
#33-U
  [ 4657.314755] task: c1375e00 ti: c13d task.ti: 
c13d
  [ 4657.314759] NIP: c01e8ffc LR: c001fe70 CTR: 
c0002800ic)
  [ 4657.314770] MSR: 80029033 SF,EE,ME,IR,DR,RI,LE  CR: 28042024  
XER: 000a
  [ 4657.314782] CFAR: c001fe6c SOFTE: 0
  GPR04: 0010 009c c1424a98 0002
  GPR12: 80009033 ce9a 06a3fcd0 0060
  GPR16: 0020  c0e57c00 
  GPR20: c1595dca c1595478 0001 
  GPR28: c0e40380 c0e40300 c13d3590 c0e56f08
  [ 4657.314832] NIP [c01e8ffc] irq_work_run+0x1c/0x30
  [ 4657.314841] Call Trace:
  4000 (unreliable)
  [ 4657.314861] [c13d34f0] [c001ff90] timer_interrupt+0xa0/0xe0
  [ 4657.314871] [c13d3520] [c0002914] 
decrementer_common+0x114/0x180
  [ 4657.314884] --- Exception: 901 at arch_local_irq_restore+0x14/0x90
  [ 4657.314896] [c13d3810] [c012ed08] vprintk_emit+0x3b8/0x660 
(u
  [ 4657.314908] [c13d38e0] [c0a02650] printk+0x84/0x98
  [ 4657.314918] [c13d3910] [c00b51b4] __do_softirq+0x1e4/0x410
  [ 4657.314927] [c13d3a00] [c00b57b8] irq_exit+0xf8/0x1400
  [ 4657.314948] [c13d3a60] [c0002c14] 
doorbell_super_common+0x114/0x180
  [ 4657.314963] --- Exception: a01 at plpar_hcall_norets+0x8c/0xdc
  [ 4657.314963] LR = check_and_cede_processor+0x34/0x5020/0x50 (unreliable)
  [ 4657.314997] [c13d3df0] [c084077c] 
cpuidle_enter_state+0x6c/0x140c0
  [ 4657.315030] [c13d3f00] [c0d63ea8] start_kernel+0x500/0x51c
  [ 4657.315047] Instruction dump:
  [ 4657.315052] eba1ffe8 7c0803a6 ebc1fff0 ebe1fff8 4e800020 3c4c011f 3842c110 
78290464
  [ 4657.315068] 81290014 752a000f 7d380026 55291ffe 0b09 4bfffec8 
6000
  6000
  [ 4657.315090] ---[ end trace ee202cccd2211e5d ]---
  [ 4657.320224]
  [ 4657.362675] Unable to handle kernel paging request for data at address 
0xc000
  000b35515048
  [ 4657.362680] Faulting instruction address: 0xc006a37c
  [ 4657.362684] Oops: Kernel access of bad area, sig: 11 [#2]
  [ 4657.362686] SMP NR_CPUS=2048 NUMA pSeries
  [ 4657.362695] CPU: 12 PID: 7 Comm: rcu_sched Tainted: G  D   
3.16.0-25-
  [ 4657.362699] task: c000eb581540 ti: c000eb604000 task.ti: 
c000eb60
  [ 4657.362703] NIP: c006a37c LR: c00865a8 CTR: 
c006a340
  [ 4657.362706] REGS: c000eb607800 TRAP: 0300   Tainted: G  D
(3.16.0-25-generic)
  
  [ 4657.362718] CFAR: c00865a4 DAR: c00b35515048 DSISR: 4000 
SOFTE: 0
  GPR00: c00865a8 c000eb607a80 c13d50f0 013d30d0
  GPR08: 00cc c00b35515000 ce9a 
  GPR12: c006a340 ce9a6c00 

[Kernel-packages] [Bug 1317811] Re: Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x slots

2015-03-03 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Utopic)
   Status: Fix Committed = Fix Released

** Tags removed: kernel-bug-break-fix

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

Title:
  Dropped packets on EC2, xen_netfront: xennet: skb rides the rocket: x
  slots

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:
  Running Ubuntu 14.04 LTS on EC2, we see a lot of the following in the
  kernel log:

  xen_netfront: xennet: skb rides the rocket: 19 slots

  Each of these messages corresponds to a dropped TX packet, and
  eventually causes our application's connections to break and timeout.

  The problem appears when network load increases. We have Node.js
  processes doing pubsub with a Redis server, and these are most visibly
  affected, showing frequent connection loss. The processes talk to each
  other using the private addresses EC2 allocates to the machines.

  Notably, the default MTU on the network interface seems to have gone
  up from 1500 on 13.10, to 9000 in 14.04 LTS. Reducing the MTU back to
  1500 seems to drastically reduce dropped packets. (Can't say for
  certain if it completely eliminates the problem.)

  The machines we run are started from ami-896c96fe.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46
  ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  9 09:01 seq
   crw-rw 1 root audio 116, 33 May  9 09:01 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Fri May  9 09:11:18 2014
  Ec2AMI: ami-896c96fe
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1c
  Ec2InstanceType: c3.large
  Ec2Kernel: aki-52a34525
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  9 09:54 seq
   crw-rw 1 root audio 116, 33 May  9 09:54 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: [   24.724129] init: plymouth-upstart-bridge main process 
ended, respawning
  DistroRelease: Ubuntu 14.04
  Ec2AMI: ami-896c96fe
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1c
  Ec2InstanceType: c3.large
  Ec2Kernel: aki-52a34525
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: root=LABEL=cloudimg-rootfs ro console=hvc0
  ProcVersionSignature: User Name 3.13.0-24.46-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty ec2-images
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

  break-fix: - 97a6d1bb2b658ac85ed88205ccd1ab809899884d
  break-fix: - 11d3d2a16cc1f05c6ece69a4392e99efb85666a6

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

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


[Kernel-packages] [Bug 1409123] Re: hw csum failure in encapsulated network topolgies

2015-03-03 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Precise)
   Status: Confirmed = Fix Committed

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

** Changed in: linux-lts-trusty (Ubuntu Precise)
   Status: Fix Committed = Fix Released

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

** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: Fix Committed = Fix Released

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

Title:
  hw csum failure in encapsulated network topolgies

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-trusty 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-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in linux-lts-trusty source package in Utopic:
  Invalid
Status in linux-lts-utopic source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  Virtualized network topologies that utilize encapsulation (e.g.,
  VXLAN) and bridging  may experience kernel errors of the format:

  [ 4297.761899] eth0: hw csum failure
  [ 4297.765210] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G   OE  
3.18.0-rc4
  -nn+ #22
  [ 4297.765212] Hardware name: LENOVO 0829F3U/To be filled by O.E.M., BIOS 
90KT15
  AUS 07/21/2010
  [ 4297.765216]   88013fc03ba8 8172f026 
0
  001
  [ 4297.765219]  88013870e000 88013fc03bc8 8162ba52 
8161c
  1a0
  [ 4297.765221]  8800afdf1000 88013fc03c08 8162325c 
88013870e
  000
  [ 4297.765223] Call Trace:
  [ 4297.765224]  IRQ  [8172f026] dump_stack+0x46/0x58
  [ 4297.765235]  [8162ba52] netdev_rx_csum_fault+0x42/0x50
  [ 4297.765238]  [8161c1a0] ? skb_push+0x40/0x40
  [ 4297.765240]  [8162325c] __skb_checksum_complete+0xbc/0xd0
  [ 4297.765243]  [8168c602] tcp_v4_rcv+0x2e2/0x950
  [ 4297.765246]  [81666ca0] ? ip_rcv_finish+0x360/0x360
  [ 4297.765248]  [81660224] ? nf_hook_slow+0x74/0x130
  [ 4297.765250]  [81666ca0] ? ip_rcv_finish+0x360/0x360
  [ 4297.765253]  [81666d4c] ip_local_deliver_finish+0xac/0x220
  [ 4297.765255]  [81667058] ip_local_deliver+0x48/0x80
  [ 4297.765257]  [816669c1] ip_rcv_finish+0x81/0x360
  [ 4297.765259]  [81667332] ip_rcv+0x2a2/0x3f0
  [ 4297.765261]  [8162e932] __netif_receive_skb_core+0x562/0x7a0
  [ 4297.765263]  [8162eb88] __netif_receive_skb+0x18/0x60
  [ 4297.765265]  [8162f8f6] process_backlog+0xa6/0x150

  The backtrace may vary, stacks descending into conntrack have also
  been observed:

  Call Trace:
   IRQ  [8171a324] dump_stack+0x45/0x56
   [8161bfba] netdev_rx_csum_fault+0x3a/0x40
   [81614782] __skb_checksum_complete_head+0x62/0x70
   [816147a1] __skb_checksum_complete+0x11/0x20
   [816a3eac] nf_ip_checksum+0xcc/0x100
   [a04df33b] udp_error+0xdb/0x1f0 [nf_conntrack]
   [a04d926e] nf_conntrack_in+0xee/0xb40 [nf_conntrack]
   [a0307653] ? do_execute_actions+0x2e3/0xab0 [openvswitch]
   [a0307e4b] ? ovs_execute_actions+0x2b/0x30 [openvswitch]
   [81654540] ? inet_del_offload+0x40/0x40
   [a03b52e2] ipv4_conntrack_in+0x22/0x30 [nf_conntrack_ipv4]
   [8164e0aa] nf_iterate+0x9a/0xb0
   [81654540] ? inet_del_offload+0x40/0x40
   [8164e134] nf_hook_slow+0x74/0x130
   [81654540] ? inet_del_offload+0x40/0x40
   [81654f68] ip_rcv+0x2f8/0x3d0

  The root cause of this is twofold:

  First, the kernel handling of forwarded packets that have been
  encapsulated (e.g., from VXLAN) for devices that support
  CHECKSUM_COMPLETE checksum offload fails to update the running
  checksum when decapsulating the packet.

  Second, for the enic device itself, the hardware is not correctly
  computing the checksum for some cases.

  Both of these issues are patched in mainline:

  commit 17e96834fd35997ca7cdfbf15413bcd5a36ad448
  Author: Govindarajulu Varadarajan _gov...@gmx.com
  Date: Thu Dec 18 15:58:42 2014 +0530

  enic: fix rx skb checksum

  commit 2c26d34bbcc0b3f30385d5587aa232289e2eed8e
  Author: Jay Vosburgh jay.vosbu...@canonical.com
  Date: Fri Dec 19 15:32:00 2014 -0800

  net/core: Handle csum for CHECKSUM_COMPLETE VXLAN 

[Kernel-packages] [Bug 1416001] Re: ISST-LTE: ubuntu15.04 installer is missing ibmvfc driver

2015-03-03 Thread Andy Whitcroft
** Changed in: debian-installer (Ubuntu)
   Status: Confirmed = Invalid

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

Title:
  ISST-LTE: ubuntu15.04 installer is missing ibmvfc driver

Status in debian-installer package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #1 - Hemant Kumar hemantkba...@in.ibm.com - 2015-01-20 11:27:19 
==
  Defect Description:
  ---

  I am trying to install ubuntu15.04LE on multipath disks, but while
  installtion installer is not able to find multipath disks.

  For enabling multipath support is have set disk-
  detect/multipath/enable=true parameter in grub menu while
  installation.

  Here is the error which i am getting:

lqqu [!] Detect disks tqqqk
x x
x No disk drive was detected. If you know the name of the driver needed   x
x by your disk drive, you can select it from the list.x
x x
x Driver needed for your disk drive:  x
x x
x continue with no disk drive x
x login to iSCSI targets  x
x 3w-9xxx  a  x
x 3w-sas   a  x
x 3w-  a  x
x DAC960   a  x
x a100u2w  a  x
x aacraid  a  x
x aic79xx  a  x
x aic7xxx x
x x
x Go Back   x
x x
mqj

  Tab moves; Space selects; Enter activates buttons

  
  I have tried installing other distros and the installer is able to find the 
disks but ubuntu installer is giving error.

  lpar is at installation prompt, please have a look.

  

  == Comment: #10 - Carrie N. Mitsuyoshi carri...@us.ibm.com - 2015-01-27 
11:22:52 ==
  (In reply to comment #6)
   This seems to be a more fundamental error than multipath; the installer
   cannot find any storage at all. I expect you will see the same error w/o the
   above mutlipath parameter.  Can you try this and see if that is true?

  I tried the Ubuntu install without multipath enabled and still hit the
  issue. So it is not related to multipath. On the Detect disks
  screen, I scrolled through the list of available drivers and did not
  find ibmvfc.

   So the installer is assuming, since it finds no storage, that you have some
   adapter installed for which it has no driver.  I don't know if that's true
   or not, but if you can identify the required driver for the adapter you are
   targeting, that would be helpful.  Any other information about the adapter
   hardware would be helpful too.

  The Ubuntu installer does not have the ibmvfc module.

  ~ # uname -a
  Linux highlp3 3.18.0-11-generic #12-Ubuntu SMP Fri Jan 23 22:45:52 UTC 2015 
ppc64le GNU/Linux
  ~ # lsmod
  Module  Size  Used by
  usb_storage71250  0 
  ~ # modinfo ibmvfc
  modinfo: ERROR: Module ibmvfc not found.

  
  == Comment: #12 - Carrie N. Mitsuyoshi carri...@us.ibm.com - 2015-01-27 
11:27:44 ==
  This is from a separate lpar, used to get the ibmvfc info for a running 
Ubuntu 15.04 system.

  (see attachment: modinfo ibmvfc)

  == Comment: #17 - David Heller helle...@us.ibm.com - 2015-01-28 14:13:46 ==
  So clearly ibmvfc is not a builtin on the ppc64el kernel.

  After poking around some more I can verify the ibmvfc.ko is missing
  from the installer initrd files -- both the netboot one and the one on
  the ISO.  I did find one installed system where the module is present
  so it's around but just not in the installer.

  So, I think the next step is to mirror this and request ibmvfc.ko be
  added to the installer.  The other alternative is to request that it
  get builtin all around.  Currently it's built as a module.

  Brian, is this correct?  Do we have a preference?

  == Comment: #18 - Brian J. King bjki...@us.ibm.com - 2015-01-29 

[Kernel-packages] [Bug 1413992] Re: Kernel oopses on access to address 0x8 when cdc-acm device is inserted with invalid descriptor.

2015-03-03 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  Kernel oopses on access to address 0x8 when cdc-acm device is inserted
  with invalid descriptor.

Status in HWE Next Project:
  In Progress
Status in HWE Next trusty series:
  In Progress
Status in HWE Next utopic series:
  In Progress
Status in HWE Next vivid series:
  In Progress
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Invalid configuration descriptor as follows:

  #+BEGIN_SRC text
     09 02 43 00 02 01 00 80 64 09 04 00 00 01 02 02  ..C.d...
  0010   00 00 05 24 00 10 01 04 24 02 06 04 24 01 00 01  ...$$...$...
  0020   05 24 06 00 01 07 05 81 03 08 00 ff 09 04 01 00  .$..
  0030   02 0a 00 00 00 07 05 82 02 40 00 ff 07 05 01 02  .@..
  0040   20 00 ff  ..
  #+END_SRC text

  In particular, the CDC Call Management Descriptor has its length
  declared too short (4 instead of 5), and the following CDC Union
  Descriptor is therefore unreachable.

  *** Code problems:

  1. The ~while (buflen  0)~ loop that parses the interface aux data
 does not perform correct boundary checking.  In the above case,
 ~call_interface_num = buffer[4];~ accesses outside of the
 (declared) descriptor content.
  2. If a union header is missing, there is no code path that checks
 whether the ~data_interface~ (resolved from ~call_interface_num~)
 actually exists.  Later ~if
 (data_interface-cur_altsetting-desc.bInterfaceClass~ dereferences
 ~data_interface~.

  ref: https://bugzilla.kernel.org/show_bug.cgi?id=83551

  issue 2 was already fixed, issue 1's fix is in progress of upstream
  merging, open this bug to track.

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

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


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

2015-03-03 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
   Status: In Progress = Fix Committed

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

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

Status in linux package in Ubuntu:
  Fix Committed

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

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

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


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

2015-03-05 Thread Andy Whitcroft
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New = Confirmed

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided = Medium

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = Andy Whitcroft (apw)

** Changed in: linux (Ubuntu)
Milestone: None = ubuntu-15.03

-- 
You 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 1408004] Re: devel: DTBs have moved into vendor specific directories on arm64

2015-02-27 Thread Andy Whitcroft
** Changed in: debian-installer (Ubuntu)
   Status: Invalid = Confirmed

** Changed in: debian-installer (Ubuntu)
 Assignee: (unassigned) = Adam Conrad (adconrad)

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

Title:
  devel: DTBs have moved into vendor specific directories on arm64

Status in debian-installer package in Ubuntu:
  Confirmed
Status in flash-kernel package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  The installed DTBs have moved into vendor specific directories.  We
  need to 1) make sure we are hoovering them up right, and 2) that the
  consumers thereof (d-i etc) are consuming them in the new locations.

  NOTE: this actually is only _installed_ into those new directories on
  arm64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1408004/+subscriptions

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


[Kernel-packages] [Bug 1425004] [NEW] powerpc/powernv: Ignore smt-enabled on Power8 and later

2015-02-24 Thread Andy Whitcroft
Public bug reported:

Hi Ubuntu kernel folks, 
   

   
This patch isn't quite upstream stable material, but might still be nice to 
   
have. It prevents smt-enabled=off on the kernel command line causing a hung 
   
system at boot. 
   

   
cheers   

===

From: Greg Kurz gk...@linux.vnet.ibm.com  
   

   
Commit d70a54e2d08510a99b1f10eceeae6f2f7086e226 upstream.   
   

   
Starting with POWER8, the subcore logic relies on all threads of a core 
   
being booted so that they can participate in split mode switches. So on 
   
those machines we ignore the smt_enabled_at_boot setting (smt-enabled on
   
the kernel command line).   
   

   
Signed-off-by: Greg Kurz gk...@linux.vnet.ibm.com 
   
[mpe: Update comment and change log to be more precise] 
   
Signed-off-by: Michael Ellerman m...@ellerman.id.au   

--- 
   
 arch/powerpc/platforms/powernv/smp.c | 16 +++- 
   
 1 file changed, 15 insertions(+), 1 deletion(-)

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

** Affects: linux (Ubuntu Utopic)
 Importance: Medium
 Status: Confirmed

** Affects: linux (Ubuntu Vivid)
 Importance: Medium
 Status: Confirmed

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

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

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

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

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

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

Title:
  powerpc/powernv: Ignore smt-enabled on Power8 and later

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

Bug description:
  Hi Ubuntu kernel folks,   
 

 
  This patch isn't quite upstream stable material, but might still be nice to   
 
  have. It prevents smt-enabled=off on the kernel command line causing a hung   
 
  system at boot.   
 

 
  cheers   

  ===

  From: Greg Kurz gk...@linux.vnet.ibm.com
 

 
  Commit d70a54e2d08510a99b1f10eceeae6f2f7086e226 upstream. 
 

 
  Starting with POWER8, the subcore logic relies on all threads of a core   
 
  being booted so that they can participate in split mode switches. So on   
 
  those machines we ignore the smt_enabled_at_boot setting (smt-enabled on  
 
  the kernel command line). 
 


[Kernel-packages] [Bug 1425144] [NEW] build initial linux-lts-vivid

2015-02-24 Thread Andy Whitcroft
Public bug reported:

Need to start producing linux-lts-vivid now we are closing in on final.

** Affects: linux-lts-utopic (Ubuntu)
 Importance: Medium
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

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

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

** Changed in: linux-lts-utopic (Ubuntu)
 Assignee: (unassigned) = Andy Whitcroft (apw)

** Changed in: linux-lts-utopic (Ubuntu)
Milestone: None = ubuntu-15.02

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

Title:
  build initial linux-lts-vivid

Status in linux-lts-utopic package in Ubuntu:
  In Progress

Bug description:
  Need to start producing linux-lts-vivid now we are closing in on
  final.

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

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


[Kernel-packages] [Bug 1425144] Re: build initial linux-lts-vivid

2015-02-24 Thread Andy Whitcroft
Will move this to the right package once it exists.

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

Title:
  build initial linux-lts-vivid

Status in linux-lts-utopic package in Ubuntu:
  In Progress

Bug description:
  Need to start producing linux-lts-vivid now we are closing in on
  final.

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

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


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

2015-02-26 Thread Andy Whitcroft
Public bug reported:

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

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: Confirmed

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = Andy Whitcroft (apw)

** Changed in: linux (Ubuntu)
Milestone: None = ubuntu-15.02

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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


[Kernel-packages] [Bug 1426013] [NEW] linux: 3.19.0-7.7 -proposed tracker

2015-02-26 Thread Andy Whitcroft
Public bug reported:

This bug is for tracking the 3.19.0-7.7 upload package. This bug will
contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-Prepare-package-start:Thursday, 26. February 2015 16:33 UTC
kernel-phase-changed:Thursday, 26. February 2015 16:33 UTC
kernel-phase:Prepare

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

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

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

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

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

** Affects: kernel-development-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

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


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

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

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

** Tags added: vivid

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

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

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

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

** Also affects: kernel-development-workflow/promote-to-release
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-development-workflow/promote-to-release
   Importance: Undecided = Medium

** Changed in: kernel-development-workflow/promote-to-release
 Assignee: (unassigned) = Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

Title:
  linux: 3.19.0-7.7 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow package-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  New
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Thursday, 26. February 2015 16:33 UTC
  kernel-phase-changed:Thursday, 26. February 2015 16:33 UTC
  kernel-phase:Prepare

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

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

[Kernel-packages] [Bug 1437435] [NEW] linux: 3.19.0-11.11 -proposed tracker

2015-03-27 Thread Andy Whitcroft
Public bug reported:

This bug is for tracking the 3.19.0-11.11 upload package. This bug will
contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-Prepare-package-start:Friday, 27. March 2015 17:36 UTC
kernel-phase-changed:Friday, 27. March 2015 17:36 UTC
kernel-phase:Prepare

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

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

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

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

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

** Affects: kernel-development-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

** Affects: linux (Ubuntu Vivid)
 Importance: Undecided
 Status: Invalid


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

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

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

** Tags added: vivid

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

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

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

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

** Also affects: kernel-development-workflow/promote-to-release
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-development-workflow/promote-to-release
   Importance: Undecided = Medium

** Changed in: kernel-development-workflow/promote-to-release
 Assignee: (unassigned) = Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

Title:
  linux: 3.19.0-11.11 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow package-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  New
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Invalid

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Friday, 27. March 2015 17:36 UTC
  kernel-phase-changed:Friday, 27. March 2015 17:36 UTC
  kernel-phase:Prepare

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

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

[Kernel-packages] [Bug 1423343] Re: [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v

2015-03-27 Thread Andy Whitcroft
Could you test the kernels at the URL below and confirm they work
correctly on Azure:

http://people.canonical.com/~apw/lp1423343-vivid/

Please report any testing back here.  Thanks.

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

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

Title:
  [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Following patches are missing from ubuntu vivid 15.04 compared to
  latest upstream (linux-next) , please include them in ubuntu vivid ,
  all the patches listed here are already upstream .

  /arch/x86/include/uapi/asm/hyperv.h

  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9e7827b5ea4ca93b4d864bc07c0fafb838d496b1

  /drivers/hv/hyperv_vmbus.h
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2

  drivers/hv/vmbus_drv.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=a45de93eb10ae6aec2c73d722562ab46092a
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d8a60e000c951f845d9a5fb3e67853e0e63a5659
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=90f3453585479d5beb75058da46eb573ced0e6ac
  5. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=302a3c0f2757ae1a3e7df3f9fa1f20e2214ab945
  6. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=b0209501dc7586cbfbf6d023f2dd3ce4621aff2c

  /drivers/hv/hv_snapshot.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8d9560ebcc6448472b3afe8f36f37d6b0de8f5a4
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=649142074d86afebe0505431a93957505d244dd6

  /drivers/hv/hv_kvp.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8d9560ebcc6448472b3afe8f36f37d6b0de8f5a4

  /drivers/hv/hv_fcopy.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d9b1652947c695d247b5e4603a16213ec55661ed

  /drivers/hv/channel.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67fae053bfc6e84144150e4c6c62670abb215c33
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d61031ee8df6214d58371a1cc36a0591e242fba0
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9f52a1630922bcdab75fc72e59ed58db8e164314

  /drivers/hv/channel_mgmt.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d7f2fbafb4f84306436277664cf28042beaf252a
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67fae053bfc6e84144150e4c6c62670abb215c33
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9c3a6f7e476fc4961297fc66b1177f9f8c8dd238
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=87712bf81dd092821c406ea3fb47a07222484a64
  5. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c3582a2c4d0baf1fa3955c8b3d3d61308df474c7

  /drivers/hv/hv_balloon.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=ab3de22bb4a3d4bda2d0ec8bebcb76a40f1cbf9b
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=22f88475b62ac826acae2f77c3e1bd9543e87b2a
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=79208c57da5311860f165b613c89b3f647e357cd
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=f6712238471a8afdbfcea482483fc121281292d8

  /tools/hv/hv_vss_daemon.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9e5db05aae4657c7ade34ccc4b93f27ab647498e
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=7a401744d517864f8f2f2afba589e58a71d03aa6
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=170f4bea2008054e5098f99359e29823a7b4b1b9
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4f689190bb55d171d2f6614f8a6cbd4b868e48bd

  /tools/hv/hv_fcopy_daemon.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c1136da62170465920eea1ae9ba9ce2234091f77
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=aba474b8185d60ca8cdbf3049fe6d655aa761e23

  /drivers/net/hyperv/netvsc.c
  1. 

[Kernel-packages] [Bug 1313804] Re: [HP Pavilion dv6-6145eo Entertainment Notebook PC] Laptop display does not turn back on after resuming from suspend

2015-03-25 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Utopic)
   Status: Confirmed = Fix Committed

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

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

Title:
  [HP Pavilion dv6-6145eo Entertainment Notebook PC] Laptop display does
  not turn back on after resuming from suspend

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

Bug description:
  On HP Pavilion dv6 the laptop display does not turn back on when resuming 
from suspend.
  External monitor wakes up just fine and the computer works normally except 
for the build in display which remains black. It should be noted that this is a 
dual graphics laptop  (lspci | grep VGA):
  00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
BeaverCreek [Radeon HD 6520G]
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] (rev ff)

  WORKAROUND: Suspending with sudo pm-suspend --quirk-test
  --quirk-s3-bios makes the computer resume normally with fully working
  display.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: 
boot/vmlinuz-3.13.0-24-generic]
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  markus 1907 F pulseaudio
   /dev/snd/controlC0:  markus 1907 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Apr 28 18:53:18 2014
  HibernationDevice: RESUME=UUID=ab1af41b-a639-463f-b406-431c8778f79d
  InstallationDate: Installed on 2014-04-27 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=8b0f125d-261b-4d22-939f-546340147d79 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 358D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 33.18
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.20:bd07/13/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124461620100:rvnHewlett-Packard:rn358D:rvr33.18:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 058F1124461620100
  dmi.sys.vendor: Hewlett-Packard

  ===
  break-fix: - 66c2b84ba6256bc5399eed45582af9ebb3ba2c15

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

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


[Kernel-packages] [Bug 1409123] Re: hw csum failure in encapsulated network topolgies

2015-03-25 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Precise)
   Status: Fix Committed = Fix Released

** Tags removed: kernel-bug-break-fix

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

Title:
  hw csum failure in encapsulated network topolgies

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-utopic package in Ubuntu:
  Invalid
Status in linux source package in Precise:
  Fix Released
Status in linux-lts-trusty source package in Precise:
  Fix Released
Status in linux-lts-utopic source package in Precise:
  Invalid
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-trusty source package in Trusty:
  Invalid
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in linux-lts-trusty source package in Utopic:
  Invalid
Status in linux-lts-utopic source package in Utopic:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in linux-lts-trusty source package in Vivid:
  Invalid
Status in linux-lts-utopic source package in Vivid:
  Invalid

Bug description:
  Virtualized network topologies that utilize encapsulation (e.g.,
  VXLAN) and bridging  may experience kernel errors of the format:

  [ 4297.761899] eth0: hw csum failure
  [ 4297.765210] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G   OE  
3.18.0-rc4
  -nn+ #22
  [ 4297.765212] Hardware name: LENOVO 0829F3U/To be filled by O.E.M., BIOS 
90KT15
  AUS 07/21/2010
  [ 4297.765216]   88013fc03ba8 8172f026 
0
  001
  [ 4297.765219]  88013870e000 88013fc03bc8 8162ba52 
8161c
  1a0
  [ 4297.765221]  8800afdf1000 88013fc03c08 8162325c 
88013870e
  000
  [ 4297.765223] Call Trace:
  [ 4297.765224]  IRQ  [8172f026] dump_stack+0x46/0x58
  [ 4297.765235]  [8162ba52] netdev_rx_csum_fault+0x42/0x50
  [ 4297.765238]  [8161c1a0] ? skb_push+0x40/0x40
  [ 4297.765240]  [8162325c] __skb_checksum_complete+0xbc/0xd0
  [ 4297.765243]  [8168c602] tcp_v4_rcv+0x2e2/0x950
  [ 4297.765246]  [81666ca0] ? ip_rcv_finish+0x360/0x360
  [ 4297.765248]  [81660224] ? nf_hook_slow+0x74/0x130
  [ 4297.765250]  [81666ca0] ? ip_rcv_finish+0x360/0x360
  [ 4297.765253]  [81666d4c] ip_local_deliver_finish+0xac/0x220
  [ 4297.765255]  [81667058] ip_local_deliver+0x48/0x80
  [ 4297.765257]  [816669c1] ip_rcv_finish+0x81/0x360
  [ 4297.765259]  [81667332] ip_rcv+0x2a2/0x3f0
  [ 4297.765261]  [8162e932] __netif_receive_skb_core+0x562/0x7a0
  [ 4297.765263]  [8162eb88] __netif_receive_skb+0x18/0x60
  [ 4297.765265]  [8162f8f6] process_backlog+0xa6/0x150

  The backtrace may vary, stacks descending into conntrack have also
  been observed:

  Call Trace:
   IRQ  [8171a324] dump_stack+0x45/0x56
   [8161bfba] netdev_rx_csum_fault+0x3a/0x40
   [81614782] __skb_checksum_complete_head+0x62/0x70
   [816147a1] __skb_checksum_complete+0x11/0x20
   [816a3eac] nf_ip_checksum+0xcc/0x100
   [a04df33b] udp_error+0xdb/0x1f0 [nf_conntrack]
   [a04d926e] nf_conntrack_in+0xee/0xb40 [nf_conntrack]
   [a0307653] ? do_execute_actions+0x2e3/0xab0 [openvswitch]
   [a0307e4b] ? ovs_execute_actions+0x2b/0x30 [openvswitch]
   [81654540] ? inet_del_offload+0x40/0x40
   [a03b52e2] ipv4_conntrack_in+0x22/0x30 [nf_conntrack_ipv4]
   [8164e0aa] nf_iterate+0x9a/0xb0
   [81654540] ? inet_del_offload+0x40/0x40
   [8164e134] nf_hook_slow+0x74/0x130
   [81654540] ? inet_del_offload+0x40/0x40
   [81654f68] ip_rcv+0x2f8/0x3d0

  The root cause of this is twofold:

  First, the kernel handling of forwarded packets that have been
  encapsulated (e.g., from VXLAN) for devices that support
  CHECKSUM_COMPLETE checksum offload fails to update the running
  checksum when decapsulating the packet.

  Second, for the enic device itself, the hardware is not correctly
  computing the checksum for some cases.

  Both of these issues are patched in mainline:

  commit 17e96834fd35997ca7cdfbf15413bcd5a36ad448
  Author: Govindarajulu Varadarajan _gov...@gmx.com
  Date: Thu Dec 18 15:58:42 2014 +0530

  enic: fix rx skb checksum

  commit 2c26d34bbcc0b3f30385d5587aa232289e2eed8e
  Author: Jay Vosburgh jay.vosbu...@canonical.com
  Date: Fri Dec 19 15:32:00 2014 -0800

  net/core: Handle csum for CHECKSUM_COMPLETE VXLAN forwarding

  
  ===
  break-fix: - 17e96834fd35997ca7cdfbf15413bcd5a36ad448
  break-fix: - 2c26d34bbcc0b3f30385d5587aa232289e2eed8e

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1386534] Re: kernel dependent deterministic view crash on X startup

2015-03-25 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: Fix Committed = Fix Released

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

** Tags removed: kernel-bug-break-fix

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

Title:
  kernel dependent deterministic view crash on X startup

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

Bug description:
  kernel 3.13.0-37 and 3.16.0-23, but not kernel 3.13.0-36

  The phenomenon: just when the user interface starts at the end of the
  Ununtu startup, the screen reamins in one solid color (very light
  grey, this is the everage of my colors), except for the topmost 3-4
  scan lines, where one can see some sort of vibrating content.
  Sometimes there is a 1-3 seconds of normal operation just at the
  start, when Ctrl-Alt-F2 works, and swithing there one can work in the
  character terminal forever.  But as soon as the disorder in the X view
  appears, even the Ctrl-Alt-F2 console change does not work visually,
  however a blindly stroken Ctr-Alt-Del is correctly executed.

  What I know: (1) on the core i3 based laptop there is no trace of this
  kind of view crash, while in case of the Phenom x6 1100t and Radeon HD
  6570 based desktop machine the problem is fully deterministic.  (2)
  the problem is distro independet, i.e.:  I have it with Ubuntu 14.04 +
  kernel 3.13.0-37-generic, and also with Ubuntu 14.10 +
  3.16.0-23-generic, and I do NOT have it with Ubuntu 14.04 + kernel
  3.13.0-36-generic, and also with Ubuntu 14.10 + 3.13.0-36-generic.
  (3) In case of Ubuntu 14.04 in average every second or third boot gave
  a 1-3 seconds of grace period when I could escape to Ctrl-Alt-F2,
  while in case of Ubuntu 14.10 there is no such a short time slot when
  I could escape.  (4) my configuration is set to fall into my only user
  account directly, I will do experiments, whether the problem is there,
  if the startup is without falling into an account.

  If I can, I will apport log files with produced with the
  3.16.0-23-generic kernel as well, not only with the 3.13.0-36-generic.

  I try to send the remaining information after my work day, now I have to 
leave, sorry.
  ---
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.7-0ubuntu8
  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
  CurrentDmesg:
   [   11.299825] init: plymouth-upstart-bridge main process ended, respawning
   [   11.329699] systemd-logind[1615]: Failed to start unit user@1000.service: 
Unknown unit: user@1000.service
   [   11.329706] systemd-logind[1615]: Failed to start user service: Unknown 
unit: user@1000.service
   [   11.332093] systemd-logind[1615]: New session c1 of user prohlep.
   [   11.332112] systemd-logind[1615]: Linked /tmp/.X11-unix/X0 to 
/run/user/1000/X11-display.
  DistUpgraded: 2014-10-27 10:17:33,100 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroRelease: Ubuntu 14.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Turks PRO [Radeon HD 6570/7570/8550] 
[1002:6759] (prog-if 00 [VGA controller])
     Subsystem: XFX Pine Group Inc. Device [1682:3195]
  InstallationDate: Installed on 2014-06-26 (124 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: System manufacturer System Product Name
  Package: xorg 1:7.7+7ubuntu2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic 
root=UUID=db97e979-6d3b-43cb-9159-341be03e6c9e ro
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Tags:  utopic ubuntu compiz-0.9
  Uname: Linux 3.13.0-36-generic x86_64
  UpgradeStatus: Upgraded to utopic on 2014-10-27 (1 days ago)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 07/18/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89GTD-PRO/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2301:bd07/18/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: 

[Kernel-packages] [Bug 1410741] Re: VDSO clock function may be miss-optimised leading to hangs on SMP systems

2015-03-25 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: Fix Committed = Fix Released

** Tags removed: kernel-bug-break-fix

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

Title:
  VDSO clock function may be miss-optimised leading to hangs on SMP
  systems

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

Bug description:
  commit 1ddf0b1b11aa8a90cef6706e935fc31c75c406ba
  Author: Andy Lutomirski l...@amacapital.net
  Date:   Sun Dec 21 08:57:46 2014 -0800

  x86, vdso: Use asm volatile in __getcpu

  In Linux 3.18 and below, GCC hoists the lsl instructions in the
  pvclock code all the way to the beginning of __vdso_clock_gettime,
  slowing the non-paravirt case significantly.  For unknown reasons,
  presumably related to the removal of a branch, the performance issue
  is gone as of

  e76b027e6408 x86,vdso: Use LSL unconditionally for vgetcpu

  but I don't trust GCC enough to expect the problem to stay fixed.

  There should be no correctness issue, because the __getcpu calls in
  __vdso_vlock_gettime were never necessary in the first place.

  Note to stable maintainers: In 3.18 and below, depending on
  configuration, gcc 4.9.2 generates code like this:

   9c3:   44 0f 03 e8 lsl%ax,%r13d
   9c7:   45 89 ebmov%r13d,%r11d
   9ca:   0f 03 d8lsl%ax,%ebx

  This patch won't apply as is to any released kernel, but I'll send a
  trivial backported version if needed.

  Fixes: 51c19b4f5927 x86: vdso: pvclock gettime support
  Cc: sta...@vger.kernel.org # 3.8+
  Cc: Marcelo Tosatti mtosa...@redhat.com
  Acked-by: Paolo Bonzini pbonz...@redhat.com
  Signed-off-by: Andy Lutomirski l...@amacapital.net

  ===
  break-fix: 51c19b4f5927f5a646e93d69f73c7e89ea14e737 
1ddf0b1b11aa8a90cef6706e935fc31c75c406ba

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

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


[Kernel-packages] [Bug 1415580] Re: add nvme to -virtual kernel

2015-03-25 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
   Status: Confirmed = Fix Committed

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

Title:
  add nvme to -virtual kernel

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  GCE has requested that the nvme kernel module be added to the GCE
  images. Please add nvme to the -virtual kernel series.

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

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


[Kernel-packages] [Bug 1386973] Re: Ubuntu 14.10 soft lockup with ATI Radeon R7 250 X

2015-03-25 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Utopic)
   Status: Confirmed = Fix Committed

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

Title:
  Ubuntu 14.10 soft lockup with ATI Radeon R7 250 X

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

Bug description:
  I have a VGA controller Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT 
[Radeon HD 7770/8760 / R7 250X].
  When I boot from the Utopic DVD I get to the language menu and I can select 
try ubuntu without installing, but after a few sencods I get BUG: soft lockup 
- CPU#0 stuck for 22s!' and the message just repeats every 22 secods forever.

  I tried setting nomodeset using the F6 menu, but I got exactly the
  same result.

  This is Ubuntu 14.10 64 bits which basically seems unable to boot with
  that hardware.

  The experience was the same with 14.04, but I thought 14.10 would be
  better. In 14.04 disabling the video card and booting off the
  integrated graphics let me set nomodeset in /etc/default/grub and I
  was able boot with the R7 250X with the VESA driver. Installed
  Catalyst afterwards.

  
  ===
  break-fix: - 16b036af31e1456cb69243a5a0c9ef801ecd1f17

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

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


[Kernel-packages] [Bug 1416001] Re: ISST-LTE: ubuntu15.04 installer is missing ibmvfc driver

2015-03-25 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Utopic)
   Status: New = Fix Committed

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

Title:
  ISST-LTE: ubuntu15.04 installer is missing ibmvfc driver

Status in debian-installer package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in debian-installer source package in Utopic:
  Invalid
Status in linux source package in Utopic:
  Fix Committed

Bug description:
  == Comment: #1 - Hemant Kumar hemantkba...@in.ibm.com - 2015-01-20 11:27:19 
==
  Defect Description:
  ---

  I am trying to install ubuntu15.04LE on multipath disks, but while
  installtion installer is not able to find multipath disks.

  For enabling multipath support is have set disk-
  detect/multipath/enable=true parameter in grub menu while
  installation.

  Here is the error which i am getting:

lqqu [!] Detect disks tqqqk
x x
x No disk drive was detected. If you know the name of the driver needed   x
x by your disk drive, you can select it from the list.x
x x
x Driver needed for your disk drive:  x
x x
x continue with no disk drive x
x login to iSCSI targets  x
x 3w-9xxx  a  x
x 3w-sas   a  x
x 3w-  a  x
x DAC960   a  x
x a100u2w  a  x
x aacraid  a  x
x aic79xx  a  x
x aic7xxx x
x x
x Go Back   x
x x
mqj

  Tab moves; Space selects; Enter activates buttons

  
  I have tried installing other distros and the installer is able to find the 
disks but ubuntu installer is giving error.

  lpar is at installation prompt, please have a look.

  

  == Comment: #10 - Carrie N. Mitsuyoshi carri...@us.ibm.com - 2015-01-27 
11:22:52 ==
  (In reply to comment #6)
   This seems to be a more fundamental error than multipath; the installer
   cannot find any storage at all. I expect you will see the same error w/o the
   above mutlipath parameter.  Can you try this and see if that is true?

  I tried the Ubuntu install without multipath enabled and still hit the
  issue. So it is not related to multipath. On the Detect disks
  screen, I scrolled through the list of available drivers and did not
  find ibmvfc.

   So the installer is assuming, since it finds no storage, that you have some
   adapter installed for which it has no driver.  I don't know if that's true
   or not, but if you can identify the required driver for the adapter you are
   targeting, that would be helpful.  Any other information about the adapter
   hardware would be helpful too.

  The Ubuntu installer does not have the ibmvfc module.

  ~ # uname -a
  Linux highlp3 3.18.0-11-generic #12-Ubuntu SMP Fri Jan 23 22:45:52 UTC 2015 
ppc64le GNU/Linux
  ~ # lsmod
  Module  Size  Used by
  usb_storage71250  0 
  ~ # modinfo ibmvfc
  modinfo: ERROR: Module ibmvfc not found.

  
  == Comment: #12 - Carrie N. Mitsuyoshi carri...@us.ibm.com - 2015-01-27 
11:27:44 ==
  This is from a separate lpar, used to get the ibmvfc info for a running 
Ubuntu 15.04 system.

  (see attachment: modinfo ibmvfc)

  == Comment: #17 - David Heller helle...@us.ibm.com - 2015-01-28 14:13:46 ==
  So clearly ibmvfc is not a builtin on the ppc64el kernel.

  After poking around some more I can verify the ibmvfc.ko is missing
  from the installer initrd files -- both the netboot one and the one on
  the ISO.  I did find one installed system where the module is present
  so it's around but just not in the installer.

  So, I think the next step is to mirror this and request ibmvfc.ko be
  added to the installer.  The other alternative is to request that it
  get builtin all around.  Currently it's built as a module.

  

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

2015-03-25 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Precise)
   Status: Fix Committed = Fix Released

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

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

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

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

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

Bug description:
  Hi,

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

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

  Regds,
  Bala S

  ===
  break-fix: - 4b552bc9edfdc947862af225a0e2521edb5d37a0

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

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


[Kernel-packages] [Bug 1410459] Re: linux: 3.2.0-76.111 -proposed tracker

2015-01-13 Thread Andy Whitcroft
** Also affects: linux (Ubuntu Precise)
   Importance: Undecided
   Status: New

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

Title:
  linux: 3.2.0-76.111 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-stable-Prepare-package-start:Tuesday, 13. January 2015 19:46 UTC
  kernel-stable-phase:Prepare
  kernel-stable-phase-changed:Tuesday, 13. January 2015 19:46 UTC

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

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


[Kernel-packages] [Bug 1435478] [NEW] linux: 3.19.0-10.10 -proposed tracker

2015-03-23 Thread Andy Whitcroft
Public bug reported:

This bug is for tracking the 3.19.0-10.10 upload package. This bug will
contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-Prepare-package-start:Monday, 23. March 2015 18:13 UTC
kernel-phase-changed:Monday, 23. March 2015 18:13 UTC
kernel-phase:Prepare

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

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

** Affects: kernel-development-workflow/prepare-package
 Importance: Medium
 Assignee: Andy Whitcroft (apw)
 Status: New

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

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

** Affects: kernel-development-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

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


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

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

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

** Tags added: vivid

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

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

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

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

** Also affects: kernel-development-workflow/promote-to-release
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-development-workflow/promote-to-release
   Importance: Undecided = Medium

** Changed in: kernel-development-workflow/promote-to-release
 Assignee: (unassigned) = Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

** Changed in: kernel-development-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) = Andy Whitcroft 
(apw)

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

Title:
  linux: 3.19.0-10.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow package-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  New
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Vivid:
  New

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Monday, 23. March 2015 18:13 UTC
  kernel-phase-changed:Monday, 23. March 2015 18:13 UTC
  kernel-phase:Prepare

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

[Kernel-packages] [Bug 1439562] Re: backport request: include support for OpenPower hardware

2015-04-02 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
   Status: New = Confirmed

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

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

Title:
  backport request: include support for OpenPower hardware

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  We've prepared a series of patches (ported to Ubuntu-3.19.0-11.11),
  which add OpenPower support to the Ubuntu kernel.

  The changes are available in the ubuntu/vivid branch of:

   https://github.com/open-power/linux.git

  (or I can attach them separately).

  Changelogs are as follows:

  commit 2f0190bd43764559b250a5bd11aca050f909aa21
  Author: Benjamin Herrenschmidt b...@kernel.crashing.org
  Date:   Fri Nov 14 16:13:50 2014 +1100

  powerpc/powernv: Support OPAL requested heartbeat
  
  If OPAL requests it, call it back via opal_poll_events() at a
  regular interval. Some versions of OPAL on some machines require
  this to operate some internal timeouts properly.
  
  Signed-off-by: Benjamin Herrenschmidt b...@kernel.crashing.org
  
  Backport notes:
   cherry-picked from mpe-next, 3bf57561d4dbd36ba45ce05656b0469bfdcc7ef2
   minor conflicts resolved
  Signed-off-by: Jeremy Kerr j...@ozlabs.org

  commit e1c89541e7163494ad091f3c2622649d91ac7597
  Author: Benjamin Herrenschmidt b...@kernel.crashing.org
  Date:   Mon Feb 16 14:59:08 2015 +1100

  device: Add dev_of_node() accessor
  
  Suggested by Arnd Bergmann, this gives a practical accessor for
  the of_node field of struct device while instructing the compiler
  that it will be NULL if CONFIG_OF is not set.
  
  Signed-off-by: Benjamin Herrenschmidt b...@kernel.crashing.org
  Acked-by: Rob Herring r...@kernel.org
  
  Backport notes:
   Submission to LKML at: https://patchwork.kernel.org/patch/5831161/
  Signed-off-by: Jeremy Kerr j...@ozlabs.org

  commit 2c242b30756f77528516a4e9e986818ac4e90490
  Author: Benjamin Herrenschmidt b...@kernel.crashing.org
  Date:   Wed Feb 18 11:25:18 2015 +1100

  drivers/core/of: Add symlink to device-tree from devices with an OF node
  
  So I've been annoyed lately with having a bunch of devices such as i2c
  eeproms (for use by VPDs, server world !) and other bits and pieces that
  I want to be able to identify from userspace, and possibly provide
  additional data about from FW.
  
  Basically, it boils down to correlating the sysfs device with the OF
  tree device node, so that user space can use device-tree info such as
  additional location or label (or whatever else we can come up with)
  propreties to identify a given device, or get some attributes of use
  about it, etc...
  
  Now, so far, we've done that in some subsystem in a fairly ad-hoc basis
  using devspec properties. For example, PCI creates them if it can
  correlate the probed device with a DT node. Some powerpc specific busses
  do that too.
  
  However, i2c doesn't and it would be nice to have something more generic
  since technically any device can have a corresponding device tree node.
  
  This patch adds an of_node symlink to devices that have a non-NULL
  dev-of_node pointer, the patch is pretty trivial and seems to work just
  fine for me.
  
  Signed-off-by: Benjamin Herrenschmidt b...@kernel.crashing.org
  Acked-by: Rob Herring r...@kernel.org
  
  Backport notes:
   Submission to LKML at: https://patchwork.kernel.org/patch/5842241/
  Signed-off-by: Jeremy Kerr j...@ozlabs.org

  commit 1d9d9bdad2553f39de92eba40f8663eb45819e8c
  Author: Michael Ellerman m...@ellerman.id.au
  Date:   Sat Mar 28 21:35:16 2015 +1100

  powerpc: Add a proper syscall for switching endianness
  
  We currently have a special syscall for switching endianness. This is
  syscall number 0x1ebe, which is handled explicitly in the 64-bit syscall
  exception entry.
  
  That has a few problems, firstly the syscall number is outside of the
  usual range, which confuses various tools. For example strace doesn't
  recognise the syscall at all.
  
  Secondly it's handled explicitly as a special case in the syscall
  exception entry, which is complicated enough without it.
  
  As a first step toward removing the special syscall, we need to add a
  regular syscall that implements the same functionality.
  
  The logic is simple, it simply toggles the MSR_LE bit in the userspace
  MSR. This is the same as the special syscall, with the caveat that the
  special syscall clobbers fewer registers.
  
  This version clobbers r9-r12, XER, CTR, and CR0-1,5-7.
  
  Signed-off-by: Michael Ellerman m...@ellerman.id.au
  
  Backport notes:
 

[Kernel-packages] [Bug 1423343] Re: [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v

2015-04-03 Thread Andy Whitcroft
It seems that due to a bug in debhelper the system units for the hyper-v daemons
are not being enabled correctly.  I think I have this worked around.  Could you 
test these
further builds and confirm whether the daemons start correctly on boot for you:

http://people.canonical.com/~apw/lp1423343-3-vivid/

Let me know what you find. Thanks.

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

Title:
  [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Following patches are missing from ubuntu vivid 15.04 compared to
  latest upstream (linux-next) , please include them in ubuntu vivid ,
  all the patches listed here are already upstream .

  /arch/x86/include/uapi/asm/hyperv.h

  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9e7827b5ea4ca93b4d864bc07c0fafb838d496b1

  /drivers/hv/hyperv_vmbus.h
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2

  drivers/hv/vmbus_drv.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=a45de93eb10ae6aec2c73d722562ab46092a
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d8a60e000c951f845d9a5fb3e67853e0e63a5659
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=90f3453585479d5beb75058da46eb573ced0e6ac
  5. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=302a3c0f2757ae1a3e7df3f9fa1f20e2214ab945
  6. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=b0209501dc7586cbfbf6d023f2dd3ce4621aff2c

  /drivers/hv/hv_snapshot.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8d9560ebcc6448472b3afe8f36f37d6b0de8f5a4
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=649142074d86afebe0505431a93957505d244dd6

  /drivers/hv/hv_kvp.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8d9560ebcc6448472b3afe8f36f37d6b0de8f5a4

  /drivers/hv/hv_fcopy.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d9b1652947c695d247b5e4603a16213ec55661ed

  /drivers/hv/channel.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67fae053bfc6e84144150e4c6c62670abb215c33
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d61031ee8df6214d58371a1cc36a0591e242fba0
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9f52a1630922bcdab75fc72e59ed58db8e164314

  /drivers/hv/channel_mgmt.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d7f2fbafb4f84306436277664cf28042beaf252a
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67fae053bfc6e84144150e4c6c62670abb215c33
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9c3a6f7e476fc4961297fc66b1177f9f8c8dd238
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=87712bf81dd092821c406ea3fb47a07222484a64
  5. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c3582a2c4d0baf1fa3955c8b3d3d61308df474c7

  /drivers/hv/hv_balloon.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=ab3de22bb4a3d4bda2d0ec8bebcb76a40f1cbf9b
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=22f88475b62ac826acae2f77c3e1bd9543e87b2a
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=79208c57da5311860f165b613c89b3f647e357cd
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=f6712238471a8afdbfcea482483fc121281292d8

  /tools/hv/hv_vss_daemon.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9e5db05aae4657c7ade34ccc4b93f27ab647498e
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=7a401744d517864f8f2f2afba589e58a71d03aa6
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=170f4bea2008054e5098f99359e29823a7b4b1b9
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4f689190bb55d171d2f6614f8a6cbd4b868e48bd

  /tools/hv/hv_fcopy_daemon.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c1136da62170465920eea1ae9ba9ce2234091f77
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=aba474b8185d60ca8cdbf3049fe6d655aa761e23

  /drivers/net/hyperv/netvsc.c
  1. 

[Kernel-packages] [Bug 1434579] Re: Unable to install VirtualBox Guest Service in 15.04

2015-04-03 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
   Status: Confirmed = Fix Committed

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

Title:
  Unable to install VirtualBox Guest Service in 15.04

Status in linux package in Ubuntu:
  Fix Committed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  It is not longer possible to select VirtualBox Guest Service in 15.04.
  The only options available are:

* Continue using a manually install driver
* Do not use the device

  The option 'Using x86 virtualisation solution - guest addition module'
  is no longer selectable. See the attached screen shot. This is from a
  fresh install of Ubuntu MATE 15.04 daily (20th March) and no drivers
  have been manually installed.

  In light of the Virtualbox issue where new installs on Virtualbox have
  a resolution of 640x480
  (https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1368784/)
  this is going to be a frustration for many users.

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

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


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

2015-04-03 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: In Progress = Confirmed

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

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

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

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

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

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

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

  ===
  break-fix: - af95b41426e0b58279f8ff0ebe420df49a4e96b8

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

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


[Kernel-packages] [Bug 1427075] Re: Stopping and starting KVM partitions results in guest kernel softlockup

2015-04-03 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
   Status: Confirmed = Fix Committed

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

Title:
  Stopping and starting KVM partitions results in guest kernel
  softlockup

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]
  Stop/continue via qemu monitor can easily trigger soft-lockups due to 
incorrect VM timekeeping.

  [Test Case]
  On a single CPU KVM guest:
  yes  /dev/null 

  Followed by
  (qemu) stop

  Wait a while, then:
  (qemu) cont

  [Fix]
  The following commits upstream:
  commit 545a2bf742fb41f17d03486dd8a8c74ad511dec2
  commit 4be1b29795d692d512bb67b770665d6f8ea5cb0b

  --

  == Comment: #0 - Cyril Bur cyril...@au1.ibm.com - 2015-02-23 18:03:41 ==
  +++ This bug was initially created as a clone of Bug #108455 +++

  I was investigating the cause of some ppc64le KVM guest softlockup
  warnings. On a single CPU KVM guest, I ran something to keep the guest
  busy:

  yes  /dev/null 

  Followed by

  (qemu) stop

  Wait a while, then:

  (qemu) cont

  We get a softlockup error:

  BUG: soft lockup - CPU#0 stuck for 9220s! [yes:2389]

  .__getnstimeofday
  .getnstimeofday
  .ktime_get_real
  .netif_receive_skb
  .ibmveth_poll
  .net_rx_action
  .__do_softirq
  .irq_exit
  .__do_irq
  .call_do_irq
  .do_IRQ

  I was going to file it away in the don't do that bin, but I notice
  x86 have something to detect a paused VM and avoid spewing the soft
  lockup error. Do we need something like this on ppc64?

  commit 5d1c0f4a80a6df73395fb3fc2c302510f8f09d36
  Author: Eric B Munson emun...@mgebm.net
  Date:   Sat Mar 10 14:37:28 2012 -0500

  watchdog: add check for suspended vm in softlockup detector

  A suspended VM can cause spurious soft lockup warnings.  To avoid these, 
the
  watchdog now checks if the kernel knows it was stopped by the host and 
skips
  the warning if so.  When the watchdog is reset successfully, clear the 
guest
  paused flag.

  == Comment: #1 - Cyril Bur cyril...@au1.ibm.com - 2015-02-23 18:03:55 ==
  Hi,

  I have been working on a fix for guest kernels. This requires two
  patches:

  1/2

  commit 545a2bf742fb41f17d03486dd8a8c74ad511dec2
  Author: Cyril Bur cyril...@gmail.com
  Date:   Thu Feb 12 15:01:24 2015 -0800

  kernel/sched/clock.c: add another clock for use with the soft
  lockup watchdog

  and 2/2

  commit 4be1b29795d692d512bb67b770665d6f8ea5cb0b
  Author: Cyril Bur cyril...@gmail.com
  Date:   Thu Feb 12 15:01:28 2015 -0800

  powerpc: add running_clock for powerpc to prevent spurious
  softlockup warnings

  Both are in upstream.

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

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


[Kernel-packages] [Bug 1292234] Re: qcow2 image corruption on non-extent filesystems (ext3)

2015-04-03 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
   Status: Confirmed = Fix Committed

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

Title:
  qcow2 image corruption on non-extent filesystems (ext3)

Status in linux package in Ubuntu:
  Fix Committed
Status in qemu package in Ubuntu:
  Invalid

Bug description:
  [Impact]
  Users of non-extent ext4 filesystems (ext4 ^extents, or ext3 w/ 
CONFIG_EXT4_USE_FOR_EXT23=y) can encounter data corruption when using fallocate 
with FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE flags.

  [Test Case]
  1) Setup ext4 ^extents, or ext3 filesystem with CONFIG_EXT4_USE_FOR_EXT23=y
  2) Create and install a VM using a qcow2 image and store the file on the 
filesystem
  3) Snapshot the image with qemu-img
  4) Boot the image and do some disk operations (fio,etc)
  5) Shutdown image and delete snapshot
  6) Repeat 3-5 until VM no longer boots due to image corruption, generally 
this takes a few iterations depending on disk operations.

  [Fix]
  commit 6f30b7e37a8239f9d27db626a1d3427bc7951908 upstream

  This has been discussed upstream here:
  http://marc.info/?l=linux-fsdevelm=142264422605440w=2

  A temporary fix would be to disable punch_hole for non-extent
  filesystem. This is how the normal ext3 module handles this and it is
  up to userspace to handle the failure. I've run this with the test
  case and was able to run for 600 iterations over 3 days where most
  failures occur within the first 2-20 iterations.

  diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
  index 5653fa4..e14cdfe 100644
  --- a/fs/ext4/inode.c
  +++ b/fs/ext4/inode.c
  @@ -3367,6 +3367,10 @@ int ext4_punch_hole(struct inode *inode, loff_t
  offset, loff_t length)
    unsigned int credits;
    int ret = 0;

  + /* EXTENTS required */
  + if (!(ext4_test_inode_flag(inode, EXT4_INODE_EXTENTS)))
  + return -EOPNOTSUPP;
  +
    if (!S_ISREG(inode-i_mode))
     return -EOPNOTSUPP;

  --

  The security team uses a tool (http://bazaar.launchpad.net/~ubuntu-
  bugcontrol/ubuntu-qa-tools/master/view/head:/vm-tools/uvt) that uses
  libvirt snapshots quite a bit. I noticed after upgrading to trusty
  some time ago that qemu 1.7 (and the qemu 2.0 in the candidate ppa)
  has had stability problems such that the disk/partition table seems to
  be corrupted after removing a libvirt snapshot and then creating
  another with the same name. I don't have a very simple reproducer, but
  had enough that hallyn suggested I file a bug. First off:

  qemu-kvm 2.0~git-20140307.4c288ac-0ubuntu2

  $ cat /proc/version_signature
  Ubuntu 3.13.0-16.36-generic 3.13.5

  $ qemu-img info ./forhallyn-trusty-amd64.img
  image: ./forhallyn-trusty-amd64.img
  file format: qcow2
  virtual size: 8.0G (8589934592 bytes)
  disk size: 4.0G
  cluster_size: 65536
  Format specific information:
  compat: 0.10

  Steps to reproduce:
  1. create a virtual machine. For a simplified reproducer, I used virt-manager 
with:
    OS type: Linux
    Version: Ubuntu 14.04
    Memory: 768
    CPUs: 1

    Select managed or existing (Browse, new volume)
  Create a new storage volume:
    qcow2
    Max capacity: 8192
    Allocation: 0

    Advanced:
  NAT
  kvm
  x86_64
  firmware: default

  2. install a VM. I used trusty-desktop-amd64.iso from Jan 23 since it
  seems like I can hit the bug more reliably if I have lots of updates
  in a dist-upgrade. I have seen this with lucid-trusty guests that are
  i386 and amd64. After the install, reboot and then cleanly shutdown

  3. Backup the image file somewhere since steps 1 and 2 take a while :)

  4. Execute the following commands which are based on what our uvt tool
  does:

  $ virsh snapshot-create-as forhallyn-trusty-amd64 pristine uvt snapshot
  $ virsh snapshot-current --name forhallyn-trusty-amd64
  pristine
  $ virsh start forhallyn-trusty-amd64
  $ virsh snapshot-list forhallyn-trusty-amd64 # this is showing as shutoff 
after start, this might be different with qemu 1.5

  in guest:
  sudo apt-get update
  sudo apt-get dist-upgrade
  780 upgraded...
  shutdown -h now

  $ virsh snapshot-delete forhallyn-trusty-amd64 pristine --children
  $ virsh snapshot-create-as forhallyn-trusty-amd64 pristine uvt snapshot

  $ virsh start forhallyn-trusty-amd64 # this command works, but there
  is often disk corruption

  The idea behind the above is to create a new VM with a pristine
  snapshot that we could revert later if we wanted. Instead, we boot the
  VM, run apt-get dist-upgrade, cleanly shutdown and then remove the old
  'pristine' snapshot and create a new 'pristine' snapshot. The
  intention is to update the VM and the pristine snapshot so that when
  we boot the next time, we boot from the updated VM and can revert back
  to the updated VM.

  After running 'virsh start' after doing snapshot-delete/snapshot-
  create-as, the disk may be 

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

2015-04-21 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
   Status: Fix Released = Confirmed

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

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

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

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

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

  ===
  break-fix: - af95b41426e0b58279f8ff0ebe420df49a4e96b8

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

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


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

2015-04-21 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: Fix Committed = Fix Released

** Tags removed: kernel-bug-break-fix

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

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

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

Bug description:
  Hi,

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

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

  Regds,
  Bala S

  ===
  break-fix: - 4b552bc9edfdc947862af225a0e2521edb5d37a0

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

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


[Kernel-packages] [Bug 1313804] Re: [HP Pavilion dv6-6145eo Entertainment Notebook PC] Laptop display does not turn back on after resuming from suspend

2015-04-21 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: New = Fix Committed

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

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

Title:
  [HP Pavilion dv6-6145eo Entertainment Notebook PC] Laptop display does
  not turn back on after resuming from suspend

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

Bug description:
  On HP Pavilion dv6 the laptop display does not turn back on when resuming 
from suspend.
  External monitor wakes up just fine and the computer works normally except 
for the build in display which remains black. It should be noted that this is a 
dual graphics laptop  (lspci | grep VGA):
  00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
BeaverCreek [Radeon HD 6520G]
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] (rev ff)

  WORKAROUND: Suspending with sudo pm-suspend --quirk-test
  --quirk-s3-bios makes the computer resume normally with fully working
  display.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: 
boot/vmlinuz-3.13.0-24-generic]
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  markus 1907 F pulseaudio
   /dev/snd/controlC0:  markus 1907 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Apr 28 18:53:18 2014
  HibernationDevice: RESUME=UUID=ab1af41b-a639-463f-b406-431c8778f79d
  InstallationDate: Installed on 2014-04-27 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=8b0f125d-261b-4d22-939f-546340147d79 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 358D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 33.18
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.20:bd07/13/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124461620100:rvnHewlett-Packard:rn358D:rvr33.18:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 058F1124461620100
  dmi.sys.vendor: Hewlett-Packard

  ===
  break-fix: - 66c2b84ba6256bc5399eed45582af9ebb3ba2c15

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

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


[Kernel-packages] [Bug 1386973] Re: Ubuntu 14.10 soft lockup with ATI Radeon R7 250 X

2015-04-21 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Utopic)
   Status: Fix Committed = Fix Released

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

Title:
  Ubuntu 14.10 soft lockup with ATI Radeon R7 250 X

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

Bug description:
  I have a VGA controller Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT 
[Radeon HD 7770/8760 / R7 250X].
  When I boot from the Utopic DVD I get to the language menu and I can select 
try ubuntu without installing, but after a few sencods I get BUG: soft lockup 
- CPU#0 stuck for 22s!' and the message just repeats every 22 secods forever.

  I tried setting nomodeset using the F6 menu, but I got exactly the
  same result.

  This is Ubuntu 14.10 64 bits which basically seems unable to boot with
  that hardware.

  The experience was the same with 14.04, but I thought 14.10 would be
  better. In 14.04 disabling the video card and booting off the
  integrated graphics let me set nomodeset in /etc/default/grub and I
  was able boot with the R7 250X with the VESA driver. Installed
  Catalyst afterwards.

  
  ===
  break-fix: - 16b036af31e1456cb69243a5a0c9ef801ecd1f17

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

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


[Kernel-packages] [Bug 1445253] Re: linux: 3.19.0-15.15 -proposed tracker

2015-04-20 Thread Andy Whitcroft
** Tags removed: block-proposed

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

Title:
  linux: 3.19.0-15.15 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow package-testing series:
  Confirmed
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Vivid:
  In Progress

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  kernel-Prepare-package-start:Thursday, 16. April 2015 23:05 UTC
  kernel-stable-Promote-to-proposed-end:Friday, 17. April 2015 00:00 UTC
  kernel-Package-testing-start:Friday, 17. April 2015 08:00 UTC
  kernel-phase:Testing
  kernel-phase-changed:Friday, 17. April 2015 08:00 UTC
  kernel-Prepare-package-end:Friday, 17. April 2015 08:00 UTC

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

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


[Kernel-packages] [Bug 1450754] Re: Wifi breaks in complex wifi scenarios (multiple SSIDs with same name etc)

2015-05-01 Thread Andy Whitcroft
[ 2614.587867] [ cut here ]
[ 2614.587878] WARNING: CPU: 3 PID: 6770 at 
/build/buildd/linux-3.13.0/drivers/net/wireless/iwlwifi/pcie/trans.c:1010 
iwl_trans_pcie_grab_nic_access+0xcb/0xe0 [iwlwifi]()
[ 2614.587879] Timeout waiting for hardware access (CSR_GP_CNTRL 0x)

It very much seems the device has completely stopped responding.  I am
wondering if there is newer firmware available for this device with the
LTS backport kernels.

** Summary changed:

- Wifi breaks when multiple SSIDs with same name
+ Wifi breaks in complex wifi scenarios (multiple SSIDs with same name etc)

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

Title:
  Wifi breaks in complex wifi scenarios (multiple SSIDs with same name
  etc)

Status in linux package in Ubuntu:
  New

Bug description:
  wifi breaks
  Kernel panic after eprom disappeared (reported gone)
  requires poweroff to fix

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-51-generic 3.13.0-51.84
  ProcVersionSignature: Ubuntu 3.13.0-51.84-generic 3.13.11-ckt18
  Uname: Linux 3.13.0-51-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mab3532 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri May  1 10:39:13 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-11 (170 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  IwConfig:
   eth2  no wireless extensions.
   
   lono wireless extensions.
   
   virbr0no wireless extensions.
  MachineType: LENOVO 4291CC3
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-51-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-51-generic N/A
   linux-backports-modules-3.13.0-51-generic  N/A
   linux-firmware 1.127.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4291CC3
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: 2622744
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn4291CC3:pvrThinkPadX220:rvnLENOVO:rn4291CC3:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4291CC3
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1414930] Re: [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't work

2015-05-07 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: Confirmed = Fix Committed

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

Title:
  [Lenovo ThinkPad 2015 models] Buttons of Synaptics trackpad doesn't
  work

Status in HWE Next Project:
  In Progress
Status in The Linux Kernel:
  Fix Released
Status in libinput package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in systemd source package in Trusty:
  Confirmed
Status in linux source package in Utopic:
  Fix Committed
Status in systemd source package in Utopic:
  Confirmed

Bug description:
  Lenovo X1 3rd Carbon (201411-16196)

  Steps to reproduce the bug:
  1, Log in to system
  2, Click left/right/middle buttons of the touchpad

  Actual result:
  No response after clicking the buttons

  Expected results:
  Buttons work as expected behavirour

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-45-generic 3.13.0-45.74 [modified: 
boot/vmlinuz-3.13.0-45-generic]
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  u  1598 F pulseaudio
   /dev/snd/controlC0:  u  1598 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 27 02:48:23 2015
  HibernationDevice: RESUME=UUID=c553e9ba-b74b-43ad-8cf2-496531261e0f
  InstallationDate: Installed on 2015-01-27 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20150126)
  MachineType: LENOVO 20BTZ09ZUS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=1d34e685-c98b-41f3-b649-87770517b194 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-45-generic N/A
   linux-backports-modules-3.13.0-45-generic  N/A
   linux-firmware 1.127.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET24W (1.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTZ09ZUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET24W(1.02):bd10/27/2014:svnLENOVO:pn20BTZ09ZUS:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTZ09ZUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20BTZ09ZUS
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1441876] Re: arm64 efi stub support

2015-05-07 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: In Progress = Fix Committed

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

Title:
  arm64 efi stub support

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

Bug description:
  [Impact]
  ARM64 systems that use UEFI cannot boot the Ubuntu 3.13 kernel shipped in 
14.04. This is significant because the only LTS cloud images Ubuntu provides 
for ARM64/UEFI include this kernel.

  [Test Case]
  Attempt to boot a 14.04 arm64-efi cloud image in QEMU as described here:
https://wiki.ubuntu.com/ARM64/QEMU
  GRUB will fail, reporting that there is no EFI stub in the kernel.

  [Regression Risk]
  The proposed backport has been reworked to not require any changes that 
impact x86, other than new macros/functions that will not be used on x86. The 
biggest regression risk is therefore to other arm64 platforms that are 
currently supported by the 3.13 kernel. Luckily this list is small and can be 
tested.

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

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


[Kernel-packages] [Bug 1434581] Re: Console extremely slow with 3.13 and newer kernels for certified servers with Matrox G200er2 or similar

2015-05-07 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: Confirmed = Fix Committed

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

Title:
  Console extremely slow with 3.13 and newer kernels for certified
  servers with Matrox G200er2 or similar

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

Bug description:
  When I first came across this issue I thought it was the same as bug
  #1316035 (https://bugs.launchpad.net/ubuntu/+source/xorg-
  server/+bug/1316035), but this bug seems to be about X and it is
  reporting xorg-server as the package with the issue. I've seen a
  report on the certification program already on this, but it was
  lacking follow-up and suggested a bug report, question 255332
  (https://answers.launchpad.net/ubuntu-certification/+question/255332).
  I've already asked about this on the forums, and received no replies.

  I originally encountered this issue due to having a bunch of Dell
  servers that I was testing with kernel 3.13 on 12.04. The text console
  is so slow that it is unusable when using vi or doing an operation
  similar to dpkg -l |grep xorg. Comparing the exact same system with
  kernel 3.2 or 3.11 loaded and running lsmod, vesafb is listed and
  performance is excellent. It is not listed on the 3.13 system. The
  same issue exists on 14.04 with the 3.13 or 3.16 kernel.

  Attempting to do modprobe vesa or modprobe vesafb returns modprobe:
  FATAL: Module vesa not found and modprobe: FATAL: Module vesafb not
  found respectively.

  Attempting to use uvesafb on this hardware results in a black screen.
  Attempting to use vga16fb results in good performance, but I am locked
  to 640x480. I tried to use fbset to force higher resolutions, but it
  either results in a distorted display or tells me there is not enough
  memory.

  I need a 1280x1024 console with performance equal to 12.04 with
  kernels 3.2-3.11. The server I'm using for testing is a Dell R320.

  This appears to be regression as I can duplicate it by simply doing a fresh 
install of 12.04.1 and not having the issue, while doing a fresh install of 
12.04.5, 14.04.1, or 14.04.2 results in a very slow console.
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 20 13:17 seq
   crw-rw 1 root audio 116, 33 Mar 20 13:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=3255aa87-ba68-4b74-bdb0-1112aba7d46e
  InstallationDate: Installed on 2015-03-20 (0 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.3)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Dell Inc. PowerEdge R320
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=fda4445f-efe2-4e93-9adb-ecaf6386f8cd ro consoleblank=0
  ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-46-generic N/A
   linux-backports-modules-3.13.0-46-generic  N/A
   linux-firmware 1.127.11
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  trusty
  Uname: Linux 3.13.0-46-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: root
  _MarkForUpload: True
  dmi.bios.date: 09/23/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.21
  dmi.board.name: 0R5KP9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.21:bd09/23/2013:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0R5KP9:rvrA09:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1451900] Re: Trusty update to v3.13.11-ckt19 stable release

2015-05-07 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: New = Fix Committed

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

Title:
  Trusty update to v3.13.11-ckt19 stable release

Status in linux package in Ubuntu:
  New
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from Linus' tree or in a minimally
     backported form of that patch. The v3.13.11-ckt19 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://kernel.ubuntu.com/ubuntu/linux.git

  TEST CASE: TBD

     The following patches are in the v3.13.11-ckt19 stable release:

  Linux 3.13.11-ckt19
  tcp: make connect() mem charging friendly
  net: compat: Update get_compat_msghdr() to match copy_msghdr_from_user() 
behaviour
  tcp: fix tcp fin memory accounting
  ipv6: fix backtracking for throw routes
  Revert net: cx82310_eth: use common match macro
  rxrpc: bogus MSG_PEEK test in rxrpc_recvmsg()
  caif: fix MSG_OOB test in caif_seqpkt_recvmsg()
  inet_diag: fix possible overflow in inet_diag_dump_one_icsk()
  rds: avoid potential stack overflow
  net: sysctl_net_core: check SNDBUF and RCVBUF for min length
  sparc64: Fix several bugs in memmove().
  sparc: Touch NMI watchdog when walking cpus and calling printk
  sparc: perf: Make counting mode actually work
  sparc: perf: Remove redundant perf_pmu_{en|dis}able calls
  sparc: semtimedop() unreachable due to comparison error
  sparc32: destroy_context() and switch_mm() needs to disable interrupts.
  dmaengine: dw: append MODULE_ALIAS for platform driver
  xfrm: release dst_orig in case of error in xfrm_lookup()
  target: Fix virtual LUN=0 target_configure_device failure OOPs
  target/pscsi: Fix NULL pointer dereference in get_device_type
  tcm_fc: missing curly braces in ft_invl_hw_context()
  target: Fix reference leak in target_get_sess_cmd() error path
  tcm_qla2xxx: Fix incorrect use of __transport_register_session
  iscsi-target: Avoid early conn_logout_comp for iser connections
  of/irq: Fix of_irq_parse_one() returned error codes
  pagemap: do not leak physical addresses to non-privileged userspace
  ALSA: hda - Treat stereo-to-mono mix properly
  nl80211: ignore HT/VHT capabilities without QoS/WMM
  can: kvaser_usb: Fix tx queue start/stop race conditions
  x86/fpu: Drop_fpu() should not assume that tsk equals current
  x86/fpu: Avoid math_state_restore() without used_math() in 
__restore_xstate_sig()
  phy: Find the right match in devm_phy_destroy()
  crypto: aesni - fix memory usage in GCM decryption
  ASoC: wm8960: Fix wrong value references for boolean kctl
  ASoC: wm8955: Fix wrong value references for boolean kctl
  ASoC: wm8904: Fix wrong value references for boolean kctl
  ASoC: wm8903: Fix wrong value references for boolean kctl
  ASoC: wm8731: Fix wrong value references for boolean kctl
  ASoC: wm2000: Fix wrong value references for boolean kctl
  ASoC: tas5086: Fix wrong value references for boolean kctl
  ASoC: pcm1681: Fix wrong value references for boolean kctl
  ASoC: cs4271: Fix wrong value references for boolean kctl
  ASoC: ak4641: Fix wrong value references for boolean kctl
  ASoC: adav80x: Fix wrong value references for boolean kctl
  x86/asm/entry/32: Fix user_mode() misuses
  vt6655: RFbSetPower fix missing rate RATE_12M
  regulator: core: Fix enable GPIO reference counting
  regulator: Only enable disabled regulators on resume
  regmap: regcache-rbtree: Fix present bitmap resize
  ASoC: sgtl5000: remove useless register write clearing CHRGPUMP_POWERUP
  x86/vdso: Fix the build on GCC5
  clocksource: efm32: Fix a NULL pointer dereference
  virtio_console: avoid config access from irq
  virtio_console: init work unconditionally
  ASoC: sn95031: Fix control-less DAPM routes
  ASoC: da732x: Fix control-less DAPM routes
  ASoC: ak4671: Fix control-less DAPM routes
  mac80211: disable u-APSD queues by default
  mac80211: drop unencrypted frames in mesh fwding
  crypto: arm/aes update NEON AES module to latest OpenSSL version
  dm io: deal with wandering queue limits when handling REQ_DISCARD and 
REQ_WRITE_SAME
  dm: hold suspend_lock while suspending device during device deletion
  dm thin: fix to consistently zero-fill reads to unprovisioned blocks
  fuse: set stolen page uptodate
  fuse: notify: don't move pages
  rbd: drop an unsafe assertion
  ARM: at91: pm: fix at91rm9200 standby
  ipvs: add missing ip_vs_pe_put in sync code
  ALSA: hda - Don't access stereo amps for mono channel widgets
  nilfs2: fix deadlock of segment constructor during recovery
  ALSA: hda - 

[Kernel-packages] [Bug 1313804] Re: [HP Pavilion dv6-6145eo Entertainment Notebook PC] Laptop display does not turn back on after resuming from suspend

2015-05-07 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: Fix Committed = Fix Released

** Tags removed: kernel-bug-break-fix

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

Title:
  [HP Pavilion dv6-6145eo Entertainment Notebook PC] Laptop display does
  not turn back on after resuming from suspend

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

Bug description:
  On HP Pavilion dv6 the laptop display does not turn back on when resuming 
from suspend.
  External monitor wakes up just fine and the computer works normally except 
for the build in display which remains black. It should be noted that this is a 
dual graphics laptop  (lspci | grep VGA):
  00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
BeaverCreek [Radeon HD 6520G]
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M] (rev ff)

  WORKAROUND: Suspending with sudo pm-suspend --quirk-test
  --quirk-s3-bios makes the computer resume normally with fully working
  display.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: 
boot/vmlinuz-3.13.0-24-generic]
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  markus 1907 F pulseaudio
   /dev/snd/controlC0:  markus 1907 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Apr 28 18:53:18 2014
  HibernationDevice: RESUME=UUID=ab1af41b-a639-463f-b406-431c8778f79d
  InstallationDate: Installed on 2014-04-27 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcFB:
   0 radeondrmfb
   1 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=8b0f125d-261b-4d22-939f-546340147d79 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 358D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 33.18
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.20:bd07/13/2011:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr058F1124461620100:rvnHewlett-Packard:rn358D:rvr33.18:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 058F1124461620100
  dmi.sys.vendor: Hewlett-Packard

  ===
  break-fix: - 66c2b84ba6256bc5399eed45582af9ebb3ba2c15

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

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


[Kernel-packages] [Bug 1386973] Re: Ubuntu 14.10 soft lockup with ATI Radeon R7 250 X

2015-05-07 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: Fix Committed = Fix Released

** Tags removed: kernel-bug-break-fix

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

Title:
  Ubuntu 14.10 soft lockup with ATI Radeon R7 250 X

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

Bug description:
  I have a VGA controller Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT 
[Radeon HD 7770/8760 / R7 250X].
  When I boot from the Utopic DVD I get to the language menu and I can select 
try ubuntu without installing, but after a few sencods I get BUG: soft lockup 
- CPU#0 stuck for 22s!' and the message just repeats every 22 secods forever.

  I tried setting nomodeset using the F6 menu, but I got exactly the
  same result.

  This is Ubuntu 14.10 64 bits which basically seems unable to boot with
  that hardware.

  The experience was the same with 14.04, but I thought 14.10 would be
  better. In 14.04 disabling the video card and booting off the
  integrated graphics let me set nomodeset in /etc/default/grub and I
  was able boot with the R7 250X with the VESA driver. Installed
  Catalyst afterwards.

  
  ===
  break-fix: - 16b036af31e1456cb69243a5a0c9ef801ecd1f17

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

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


[Kernel-packages] [Bug 1408833] Re: broken postinst test for uvtool-libvirt on utopic

2015-05-07 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
   Status: Invalid = Fix Committed

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

Title:
  broken postinst test for uvtool-libvirt on utopic

Status in AppArmor Linux application security framework:
  Confirmed
Status in ubuntu virtualization tools:
  Invalid
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Utopic:
  Fix Released

Bug description:
  Installing uvtool-libvirt *inside an lxc container* on utopic fails
  due to a test in the postinst script.

  It uses socat on the libvirt socket, which fails, despite libvirt
  being installed correctly.

  ubuntu@uoi-bootstrap:~$ sudo apt-get install -f
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
libfreetype6 os-prober
  Use 'apt-get autoremove' to remove them.
  0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Setting up uvtool-libvirt (0~bzr92-0ubuntu2) ...
  2015/01/08 13:01:34 socat[10184] E read(3, 0x13b2a30, 8192): Permission denied
  libvirtd does not appear to be listening on /var/run/libvirt/libvirt-sock.
  On Ubuntu, libvirtd is managed with the libvirt-bin upstart job.
  Repair libvirtd, then reconfigure uvtool-libvirt with:
  sudo apt-get -f install
  dpkg: error processing package uvtool-libvirt (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   uvtool-libvirt
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  ubuntu@uoi-bootstrap:~$ ps -ef | grep libvirt
  libvirt+  9556 1  0 09:52 ?00:00:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  root  9557  9556  0 09:52 ?00:00:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  root  9854 1  0 10:24 ?00:00:00 /usr/sbin/libvirtd -d
  ubuntu   10155 10120  0 12:56 pts/000:00:00 grep libvirt

  ubuntu@uoi-bootstrap:~$ groups
  ubuntu adm dialout cdrom floppy sudo audio dip video plugdev netdev libvirtd

  
  ubuntu@uoi-bootstrap:~$ virsh list
   IdName   State
  

  for a little more context, there are notes here:
  https://gist.github.com/mikemccracken/53c665e6094db21efc03

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

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


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

2015-05-07 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
   Status: Confirmed = Fix Committed

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

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

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

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

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

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

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1413741] Re: CVE-2014-8159

2015-05-07 Thread Andy Whitcroft
** Changed in: linux-lts-saucy (Ubuntu Precise)
   Status: Invalid = Fix Committed

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

Title:
  CVE-2014-8159

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

[Kernel-packages] [Bug 1441291] Re: support EFI rtc on arm64

2015-05-07 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: In Progress = Fix Committed

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

Title:
  support EFI rtc on arm64

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

Bug description:
  [Impact]
  ARM64 EFI platforms have no real time clock support. This can leave a system 
with a very out-of-date system clock. It can be somewhat mitigated by using 
NTP, but that still leaves issues in early boot (inaccurate last mount times, 
etc).

  [Test Case]
  if dmesg | grep -q 'rtc-efi: setting system clock'; then
PASS
  else
FAIL
  fi

  [Regression Risk]
  This enables a new driver only on ARM64, so the risk should be low to other 
platforms. The upstream patches do refactor the rtc-efi driver but, that driver 
was previously only compilable on ia64, which isn't supported by Ubuntu.

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

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


[Kernel-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file

2015-05-18 Thread Andy Whitcroft
** Description changed:

  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on
  
  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
   wrong value for bytes, expected 3145728 got 3018027
   at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process
  
  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.
  
  This was most likely triggered by the kernel update from 3.18 to 3.19.
+ 
+ ===
+ break-fix: 1a48632ffed61352a7810ce089dc5a8bcd505a60 
1a48632ffed61352a7810ce089dc5a8bcd505a60

** Tags added: kernel-bug-break-fix

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

Title:
  FTBFS: upstart test_job_process fails in majority of cases / Kernel
  returning unexpected EIO at end of file

Status in linux package in Ubuntu:
  In Progress
Status in upstart package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  In Progress
Status in upstart source package in Vivid:
  Invalid

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
   wrong value for bytes, expected 3145728 got 3018027
   at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

  This was most likely triggered by the kernel update from 3.18 to 3.19.

  ===
  break-fix: 1a48632ffed61352a7810ce089dc5a8bcd505a60 
1a48632ffed61352a7810ce089dc5a8bcd505a60

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

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


[Kernel-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file

2015-05-18 Thread Andy Whitcroft
** Description changed:

  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on
  
  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
   wrong value for bytes, expected 3145728 got 3018027
   at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process
  
  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.
  
  This was most likely triggered by the kernel update from 3.18 to 3.19.
  
  ===
- break-fix: 1a48632ffed61352a7810ce089dc5a8bcd505a60 
1a48632ffed61352a7810ce089dc5a8bcd505a60
+ break-fix: 52bce7f8d4fc633c9a9d0646eef58ba6ae9a3b73 
1a48632ffed61352a7810ce089dc5a8bcd505a60

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

Title:
  FTBFS: upstart test_job_process fails in majority of cases / Kernel
  returning unexpected EIO at end of file

Status in linux package in Ubuntu:
  In Progress
Status in upstart package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  In Progress
Status in upstart source package in Vivid:
  Invalid

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
   wrong value for bytes, expected 3145728 got 3018027
   at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

  This was most likely triggered by the kernel update from 3.18 to 3.19.

  ===
  break-fix: 52bce7f8d4fc633c9a9d0646eef58ba6ae9a3b73 
1a48632ffed61352a7810ce089dc5a8bcd505a60

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

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


[Kernel-packages] [Bug 1381005] Re: Long stdin from terminal can result in code execution

2015-05-18 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: In Progress = Fix Committed

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

Title:
  Long stdin from terminal can result in code execution

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

Bug description:
  Under certain conditions, the input entered from a terminal with a
  foreground process waiting for stdin, can be interpreted and executed
  by the shell.

  Steps to reproduce:
  1) Open a terminal
  2) Run a simple program that waits for stdin (like cat, tee, head, tail, ...) 
or even the bash-builtin command read. No need to specify arguments
  3) Type or paste exactly 4096 ASCII characters into the terminal (see sample 
attachment)
  4) Press Enter

  What should happen:
  The program in foreground reads 4097 characters (the last one is new line).

  What actually happens:
  Instead of reading the input, the current program exits (read() only reads 
one character before EOF) and the shell executes the same input starting from 
the second character.

  I believe that the issue can be reproduced with:
  - any terminal (tested on xterm, gnome-terminal, tty)
  - any shell (tested on bash, zsh)
  - any program that reads stdin from terminal (not attached to a pipe)

  Debugging the shell with gdb suggests that the bug is in the implementation 
of read(), hence libc6 or under (kernel).
  Specifically, the bug is caused by read() reading only one character (new 
line) when entering a text of 4096 characters in stdin on the terminal. It 
looks like read() is then closing the stdin descriptor.
  If the input is 4097 characters long, read() will read two characters and the 
shell will interpret from the 3rd character, and so on.

  Verified on:
  Ubuntu 14.04.1 LTS

  Kernel:
  3.13.0-24-generic x86_64
  3.13.0-32-generic x86_64
  3.13.0-36-generic x86_64

  libc6:
  2.19-0ubuntu6
  2.19-0ubuntu6.1
  2.19-0ubuntu6.3

  I'm happy to provide more information if it helps.
  Angelo

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

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


[Kernel-packages] [Bug 1429756] Re: FTBFS: upstart test_job_process fails in majority of cases / Kernel returning unexpected EIO at end of file

2015-05-18 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Vivid)
   Status: In Progress = Confirmed

** Changed in: linux (Ubuntu)
   Status: In Progress = 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/1429756

Title:
  FTBFS: upstart test_job_process fails in majority of cases / Kernel
  returning unexpected EIO at end of file

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

Bug description:
  As you see in the history in https://jenkins.qa.ubuntu.com/job/vivid-
  adt-upstart/?, upstart's test fail almost all the time, on

  ok 53 - with single line command writing fast and exiting
  not ok 54 - with single line command writing lots of data fast and exiting
   wrong value for bytes, expected 3145728 got 3018027
   at tests/test_job_process.c:3886 (test_start).
  1..153
  FAIL: test_job_process

  Sometimes they succeed on one architecture, and with lots of luck on
  both, but this is way too flaky to be an useful test. This keeps
  blocking the propagation of other packages from -proposed.

  This was most likely triggered by the kernel update from 3.18 to 3.19.

  ===
  break-fix: 52bce7f8d4fc633c9a9d0646eef58ba6ae9a3b73 
1a48632ffed61352a7810ce089dc5a8bcd505a60

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

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


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

2015-05-13 Thread Andy Whitcroft
Actually there should be no linux-lts-*-tools-common packages, we expect
to share the primary package tools common package as this contains
mostly shared scripts for finding the tools.

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

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

** Changed in: linux-lts-vivid (Ubuntu Trusty)
 Assignee: (unassigned) = Andy Whitcroft (apw)

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

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

** Changed in: linux-lts-utopic (Ubuntu Trusty)
 Assignee: (unassigned) = Andy Whitcroft (apw)

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

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

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

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

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

Bug description:
  Hi,

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

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

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

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

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


[Kernel-packages] [Bug 1445253] [NEW] linux: 3.19.0-15.15 -proposed tracker

2015-04-16 Thread Andy Whitcroft
Public bug reported:

This bug is for tracking the 3.19.0-15.15 upload package. This bug will
contain status and testing results related to that upload.

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
kernel-Prepare-package-start:Thursday, 16. April 2015 23:05 UTC
kernel-phase-changed:Thursday, 16. April 2015 23:05 UTC
kernel-phase:Prepare

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

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

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

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

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

** Affects: kernel-development-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

** Affects: linux (Ubuntu Vivid)
 Importance: Undecided
 Status: Invalid


** Tags: block-proposed kernel-release-tracking-bug vivid

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

** Tags added: block-proposed

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

** Tags added: vivid

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

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

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

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

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

** Also affects: kernel-development-workflow/promote-to-release
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

** Changed in: kernel-development-workflow/promote-to-proposed
   Importance: Undecided = Medium

** Changed in: kernel-development-workflow/promote-to-proposed
 Assignee: (unassigned) = Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-release
   Importance: Undecided = Medium

** Changed in: kernel-development-workflow/promote-to-release
 Assignee: (unassigned) = Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

Title:
  linux: 3.19.0-15.15 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow package-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  New
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  

[Kernel-packages] [Bug 1439706] Re: FFE: Ubuntu FAN networking support (for linux, iproute2 and ubuntu-fan)

2015-04-17 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
   Status: Incomplete = Triaged

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

Title:
  FFE: Ubuntu FAN networking support (for linux, iproute2 and ubuntu-
  fan)

Status in iproute2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged

Bug description:
  FFE general instructions:

  The Ubuntu FAN networking support provides for additional addressing
  within a host system.  These addresses are globally accessible
  within a related group of host systems, and would typically be
  assigned to LXC containers or Docker instances running on that host.
  A typical use case for this would be to allow nested containers on a
  cloud substrate, where the host systems would be guests in that
  cloud.  Each cloud host instance would be able to express multiple
  addresses to other instances on the same substrate simplifying
  deployment.

  The changes consist of fixes for the linux (kernel) and iproute2
  packages, as well as a new ubunt-fan package.  The support is
  completely disabled unless the guest opts in.  Installation of the
  ubuntu-fan package, and configuration of it via /etc/default/ubuntu-
  fan is required before the functionality is expressed.

  These changes are proposed to allow simpler deployment and addressing
  of LXC containers and Docker instances on any substrate in a
  consistent manner without needing cooperation of buy in from that
  substrate, simply having single instance addresses on that substrate
  is sufficient.  This should be a strong enabler for Ubuntu on those
  platforms.

  
  Additional FFE instructions for linux:

  The changes for linux add a new IPIP tunnel routing mode which uses a
  direct address mapping (destination subnet to destination local IP
  address) allowing a single configuration per node to configure the
  entire fan network.  No existing functionality is changed, and this
  new mode must be explicitly requested when configuring (via iproute2
  see below).

  The patches have been applied and the resulting package uploaded to a
  testing PPA: ppa:~apw/ubuntu/fan.

  Testing is described below.

  
  Additional FFE instructions for iproute2:

  The changes for iproute2 add support for enabling the above IPIP
  routing mode, and for displaying it once configured.  No existing
  functionality is changed.  There is a small risk that the interface
  chosen could be reused by upstream, but as it is fan specific that is
  unlikely.

  The patches have been applied and the resulting package uploaded to a
  testing PPA: ppa:~apw/ubuntu/fan.

  Testing is described below.

  
  Additional FFE instructions for new ubuntu-fan package:

  The new ubuntu-fan package enables the fan functionality by
  configuring a new tunnel configured in Ubuntu FAN mode, and a new
  bridge which is used to connect consumers to it.  Typically this
  bridge is then used as the host bridge for LXC containers or Docker
  instances.  Additionally a dnsmasq is connected to the bridge to hand
  out addresses in the host specific range as if they themselves were on
  the wider network.

  The source package is uploaded to the PPA: ppa:~apw/ubuntu/fan as
  ubuntu-fan and represents the master source for this package.

  
  Testing of this combination:

  The above has been tested in combination from the testing PPA:
  ppa:~apw/ubuntu/fan.  These have been tested both locally and on AWS,
  it has been successfully tested with both LXC containers and Docker
  instances.

  ===

  Using the above instructions/checklist, lets draft the FFE
  below...Once we are happy with it let's delete the notes above and we
  can subscribe ubuntu-release.

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

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


[Kernel-packages] [Bug 1423343] Re: [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v

2015-04-07 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Following patches are missing from ubuntu vivid 15.04 compared to
  latest upstream (linux-next) , please include them in ubuntu vivid ,
  all the patches listed here are already upstream .

  /arch/x86/include/uapi/asm/hyperv.h

  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9e7827b5ea4ca93b4d864bc07c0fafb838d496b1

  /drivers/hv/hyperv_vmbus.h
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2

  drivers/hv/vmbus_drv.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=a45de93eb10ae6aec2c73d722562ab46092a
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d8a60e000c951f845d9a5fb3e67853e0e63a5659
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=90f3453585479d5beb75058da46eb573ced0e6ac
  5. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=302a3c0f2757ae1a3e7df3f9fa1f20e2214ab945
  6. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=b0209501dc7586cbfbf6d023f2dd3ce4621aff2c

  /drivers/hv/hv_snapshot.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8d9560ebcc6448472b3afe8f36f37d6b0de8f5a4
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=649142074d86afebe0505431a93957505d244dd6

  /drivers/hv/hv_kvp.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8d9560ebcc6448472b3afe8f36f37d6b0de8f5a4

  /drivers/hv/hv_fcopy.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d9b1652947c695d247b5e4603a16213ec55661ed

  /drivers/hv/channel.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67fae053bfc6e84144150e4c6c62670abb215c33
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d61031ee8df6214d58371a1cc36a0591e242fba0
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9f52a1630922bcdab75fc72e59ed58db8e164314

  /drivers/hv/channel_mgmt.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d7f2fbafb4f84306436277664cf28042beaf252a
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67fae053bfc6e84144150e4c6c62670abb215c33
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9c3a6f7e476fc4961297fc66b1177f9f8c8dd238
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=87712bf81dd092821c406ea3fb47a07222484a64
  5. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c3582a2c4d0baf1fa3955c8b3d3d61308df474c7

  /drivers/hv/hv_balloon.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=ab3de22bb4a3d4bda2d0ec8bebcb76a40f1cbf9b
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=22f88475b62ac826acae2f77c3e1bd9543e87b2a
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=79208c57da5311860f165b613c89b3f647e357cd
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=f6712238471a8afdbfcea482483fc121281292d8

  /tools/hv/hv_vss_daemon.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9e5db05aae4657c7ade34ccc4b93f27ab647498e
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=7a401744d517864f8f2f2afba589e58a71d03aa6
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=170f4bea2008054e5098f99359e29823a7b4b1b9
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4f689190bb55d171d2f6614f8a6cbd4b868e48bd

  /tools/hv/hv_fcopy_daemon.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c1136da62170465920eea1ae9ba9ce2234091f77
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=aba474b8185d60ca8cdbf3049fe6d655aa761e23

  /drivers/net/hyperv/netvsc.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=da19fcd0d85f36420f578fe6dfe7a2a581b4fa6e
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d953ca4ddf71aa91a4596b2ff7ff1598f6ad4708
  3. 

[Kernel-packages] [Bug 1441106] [NEW] 3.19.0-12.12 brightness regression

2015-04-07 Thread Andy Whitcroft
Public bug reported:

I am seeing lack of brightness control in unity when using the -12.12
kernel, booting back to -11.11 resolves the issue.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-12-generic 3.19.0-12.12
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  apw3666 F pulseaudio
CurrentDesktop: Unity
Date: Tue Apr  7 12:01:19 2015
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=56f0e078-c76d-4cf9-a3ef-3b30e0c1a78b
InstallationDate: Installed on 2013-06-20 (655 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618)
MachineType: Intel Corporation 2012 Client Platform
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-12-generic N/A
 linux-backports-modules-3.19.0-12-generic  N/A
 linux-firmware 1.143
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2013-11-10 (512 days ago)
dmi.bios.date: 07/30/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: ACRVMBY1.86C.0094.P02.1207301240
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Latexo FFRD
dmi.board.vendor: Intel Corporation
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 9
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrACRVMBY1.86C.0094.P02.1207301240:bd07/30/2012:svnIntelCorporation:pn2012ClientPlatform:pvrTobefilledbyO.E.M.:rvnIntelCorporation:rnLatexoFFRD:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.:
dmi.product.name: 2012 Client Platform
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Intel Corporation

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: Triaged


** Tags: amd64 apport-bug third-party-packages vivid

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = Andy Whitcroft (apw)

** Changed in: linux (Ubuntu)
Milestone: None = ubuntu-15.04

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

Title:
  3.19.0-12.12 brightness regression

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I am seeing lack of brightness control in unity when using the -12.12
  kernel, booting back to -11.11 resolves the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-12-generic 3.19.0-12.12
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apw3666 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr  7 12:01:19 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=56f0e078-c76d-4cf9-a3ef-3b30e0c1a78b
  InstallationDate: Installed on 2013-06-20 (655 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618)
  MachineType: Intel Corporation 2012 Client Platform
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-12-generic N/A
   linux-backports-modules-3.19.0-12-generic  N/A
   linux-firmware 1.143
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2013-11-10 (512 days ago)
  dmi.bios.date: 07/30/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: ACRVMBY1.86C.0094.P02.1207301240
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Latexo FFRD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrACRVMBY1.86C.0094.P02.1207301240:bd07/30/2012:svnIntelCorporation:pn2012ClientPlatform:pvrTobefilledbyO.E.M.:rvnIntelCorporation:rnLatexoFFRD:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: 2012 Client Platform
  dmi.product.version: To be filled

[Kernel-packages] [Bug 1441106] Re: 3.19.0-12.12 brightness regression

2015-04-07 Thread Andy Whitcroft
Note that the hotkeys work up and down, and the visual slider moves, and
no brightness change is reflected in the display.

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

Title:
  3.19.0-12.12 brightness regression

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I am seeing lack of brightness control in unity when using the -12.12
  kernel, booting back to -11.11 resolves the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-12-generic 3.19.0-12.12
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apw3666 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr  7 12:01:19 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=56f0e078-c76d-4cf9-a3ef-3b30e0c1a78b
  InstallationDate: Installed on 2013-06-20 (655 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618)
  MachineType: Intel Corporation 2012 Client Platform
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-12-generic N/A
   linux-backports-modules-3.19.0-12-generic  N/A
   linux-firmware 1.143
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2013-11-10 (512 days ago)
  dmi.bios.date: 07/30/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: ACRVMBY1.86C.0094.P02.1207301240
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Latexo FFRD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrACRVMBY1.86C.0094.P02.1207301240:bd07/30/2012:svnIntelCorporation:pn2012ClientPlatform:pvrTobefilledbyO.E.M.:rvnIntelCorporation:rnLatexoFFRD:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: 2012 Client Platform
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Intel Corporation

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

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


[Kernel-packages] [Bug 1423343] Re: [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v

2015-04-06 Thread Andy Whitcroft
Any luck with testing these latest builds?

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

Title:
  [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Following patches are missing from ubuntu vivid 15.04 compared to
  latest upstream (linux-next) , please include them in ubuntu vivid ,
  all the patches listed here are already upstream .

  /arch/x86/include/uapi/asm/hyperv.h

  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9e7827b5ea4ca93b4d864bc07c0fafb838d496b1

  /drivers/hv/hyperv_vmbus.h
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2

  drivers/hv/vmbus_drv.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=a45de93eb10ae6aec2c73d722562ab46092a
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d8a60e000c951f845d9a5fb3e67853e0e63a5659
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=90f3453585479d5beb75058da46eb573ced0e6ac
  5. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=302a3c0f2757ae1a3e7df3f9fa1f20e2214ab945
  6. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=b0209501dc7586cbfbf6d023f2dd3ce4621aff2c

  /drivers/hv/hv_snapshot.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8d9560ebcc6448472b3afe8f36f37d6b0de8f5a4
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=649142074d86afebe0505431a93957505d244dd6

  /drivers/hv/hv_kvp.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8d9560ebcc6448472b3afe8f36f37d6b0de8f5a4

  /drivers/hv/hv_fcopy.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d9b1652947c695d247b5e4603a16213ec55661ed

  /drivers/hv/channel.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67fae053bfc6e84144150e4c6c62670abb215c33
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d61031ee8df6214d58371a1cc36a0591e242fba0
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9f52a1630922bcdab75fc72e59ed58db8e164314

  /drivers/hv/channel_mgmt.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d7f2fbafb4f84306436277664cf28042beaf252a
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67fae053bfc6e84144150e4c6c62670abb215c33
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9c3a6f7e476fc4961297fc66b1177f9f8c8dd238
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=87712bf81dd092821c406ea3fb47a07222484a64
  5. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c3582a2c4d0baf1fa3955c8b3d3d61308df474c7

  /drivers/hv/hv_balloon.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=ab3de22bb4a3d4bda2d0ec8bebcb76a40f1cbf9b
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=22f88475b62ac826acae2f77c3e1bd9543e87b2a
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=79208c57da5311860f165b613c89b3f647e357cd
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=f6712238471a8afdbfcea482483fc121281292d8

  /tools/hv/hv_vss_daemon.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9e5db05aae4657c7ade34ccc4b93f27ab647498e
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=7a401744d517864f8f2f2afba589e58a71d03aa6
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=170f4bea2008054e5098f99359e29823a7b4b1b9
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4f689190bb55d171d2f6614f8a6cbd4b868e48bd

  /tools/hv/hv_fcopy_daemon.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c1136da62170465920eea1ae9ba9ce2234091f77
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=aba474b8185d60ca8cdbf3049fe6d655aa761e23

  /drivers/net/hyperv/netvsc.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=da19fcd0d85f36420f578fe6dfe7a2a581b4fa6e
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d953ca4ddf71aa91a4596b2ff7ff1598f6ad4708
  3. 

[Kernel-packages] [Bug 1441317] Re: Utopic update to 3.16.7-ckt9 stable release

2015-04-08 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Utopic)
   Status: New = Fix Committed

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

Title:
  Utopic update to 3.16.7-ckt9 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from Linus' tree or in a minimally
     backported form of that patch. The 3.16.7-ckt9 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://kernel.ubuntu.com/ubuntu/linux.git

  TEST CASE: TBD

     The following patches are in the 3.16.7-ckt9 stable release:
   netfilter: nf_tables: disable preemption when restoring chain 
counters
   netfilter: nf_tables: fix leaks in error path of nf_tables_newchain()
   ipvs: rerouting to local clients is not needed anymore
   netfilter: nft_compat: fix module refcount underflow
   netfilter: xt_socket: fix a stack corruption bug
   ipvs: add missing ip_vs_pe_put in sync code
   flowcache: Fix kernel panic in flow_cache_flush_task
   pktgen: fix UDP checksum computation
   rtnetlink: ifla_vf_policy: fix misuses of NLA_BINARY
   tcp: make sure skb is not shared before using skb_get()
   ipv6: fix ipv6_cow_metrics for non DST_HOST case
   rtnetlink: call -dellink on failure when -newlink exists
   gen_stats.c: Duplicate xstats buffer for later use
   ipv4: ip_check_defrag should correctly check return value of 
skb_copy_bits
   ipv4: ip_check_defrag should not assume that skb_network_offset is 
zero
   net: phy: Fix verification of EEE support in phy_init_eee
   ematch: Fix auto-loading of ematch modules.
   openvswitch: Fix net exit.
   net: reject creation of netdev names with colons
   team: fix possible null pointer dereference in team_handle_frame
   net: compat: Ignore MSG_CMSG_COMPAT in compat_sys_{send, recv}msg
   macvtap: make sure neighbour code can push ethernet header
   usb: plusb: Add support for National Instruments host-to-host cable
   udp: only allow UFO for packets from SOCK_DGRAM sockets
   net: ping: Return EAFNOSUPPORT when appropriate.
   team: don't traverse port list using rcu in team_set_mac_address
   ALSA: hda - Add pin configs for ASUS mobo with IDT 92HD73XX codec
   xfs: Fix quota type in quota structures when reusing quota file
   drm/i915: Dell Chromebook 11 has PWM backlight
   gpiolib: of: allow of_gpiochip_find_and_xlate to find more than one 
chip per node
   gpio: tps65912: fix wrong container_of arguments
   ALSA: pcm: Don't leave PREPARED state after draining
   metag: Fix KSTK_EIP() and KSTK_ESP() macros
   ALSA: hda: controller code - do not export static functions
   drm/i915: Check obj-vma_list under the struct_mutex
   md/raid1: fix read balance when a drive is write-mostly.
   ALSA: hda - Disable runtime PM for Panther Point again
   drm/radeon: use drm_mode_vrefresh() rather than mode-vrefresh
   drm/radeon: fix 1 RB harvest config setup for TN/RL
   arm64: compat Fix siginfo_t - compat_siginfo_t conversion on big 
endian
   nilfs2: fix potential memory overrun on inode
   iio: mxs-lradc: separate touchscreen and buffer virtual channels
   iio: mxs-lradc: make ADC reads not disable touchscreen interrupts
   iio: mxs-lradc: make ADC reads not unschedule touchscreen conversions
   iio: mxs-lradc: only update the buffer when its conversions have 
finished
   iio: imu: adis16400: Fix sign extension
   iio: mxs-lradc: fix iio channel map regression
   iio:adc:mcp3422 Fix incorrect scales table
   iio: ad5686: fix optional reference voltage declaration
   usb: dwc3: dwc3-omap: Fix disable IRQ
   usb: gadget: configfs: don't NUL-terminate (sub)compatible ids
   KVM: emulate: fix CMPXCHG8B on 32-bit hosts
   usb: XHCI: platform: Move the Marvell quirks after the enabling the 
clocks
   xhci: Allocate correct amount of scratchpad buffers
   USB: usbfs: don't leak kernel data in siginfo
   uas: Add US_FL_NO_REPORT_OPCODES for JMicron JMS539
   efi/libstub: Fix boundary checking in efi_high_alloc()
   Revert USB: serial: make bulk_out_size a lower limit
   USB: ftdi_sio: add PIDs for Actisense USB 

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

2015-04-08 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: Confirmed = Fix Committed

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

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

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

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

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

  ===
  break-fix: - af95b41426e0b58279f8ff0ebe420df49a4e96b8

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

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


[Kernel-packages] [Bug 1386973] Re: Ubuntu 14.10 soft lockup with ATI Radeon R7 250 X

2015-04-08 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: Confirmed = Fix Committed

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

Title:
  Ubuntu 14.10 soft lockup with ATI Radeon R7 250 X

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

Bug description:
  I have a VGA controller Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT 
[Radeon HD 7770/8760 / R7 250X].
  When I boot from the Utopic DVD I get to the language menu and I can select 
try ubuntu without installing, but after a few sencods I get BUG: soft lockup 
- CPU#0 stuck for 22s!' and the message just repeats every 22 secods forever.

  I tried setting nomodeset using the F6 menu, but I got exactly the
  same result.

  This is Ubuntu 14.10 64 bits which basically seems unable to boot with
  that hardware.

  The experience was the same with 14.04, but I thought 14.10 would be
  better. In 14.04 disabling the video card and booting off the
  integrated graphics let me set nomodeset in /etc/default/grub and I
  was able boot with the R7 250X with the VESA driver. Installed
  Catalyst afterwards.

  
  ===
  break-fix: - 16b036af31e1456cb69243a5a0c9ef801ecd1f17

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

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


[Kernel-packages] [Bug 1413540] Re: Trusty soft lockup issues with nested KVM

2015-04-08 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: In Progress = Fix Committed

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

Title:
  Trusty soft lockup issues with nested KVM

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  Upstream discussion: https://lkml.org/lkml/2015/2/11/247

  Certain workloads that need to execute functions on a non-local CPU
  using smp_call_function_* can result in soft lockups with the
  following backtrace:

  PID: 22262  TASK: 8804274bb000  CPU: 1   COMMAND: qemu-system-x86
   #0 [88043fd03d18] machine_kexec at 8104ac02
   #1 [88043fd03d68] crash_kexec at 810e7203
   #2 [88043fd03e30] panic at 81719ff4
   #3 [88043fd03ea8] watchdog_timer_fn at 8110d7c5
   #4 [88043fd03ed8] __run_hrtimer at 8108e787
   #5 [88043fd03f18] hrtimer_interrupt at 8108ef4f
   #6 [88043fd03f80] local_apic_timer_interrupt at 81043537
   #7 [88043fd03f98] smp_apic_timer_interrupt at 81733d4f
   #8 [88043fd03fb0] apic_timer_interrupt at 817326dd
  --- IRQ stack ---
   #9 [880426f0d958] apic_timer_interrupt at 817326dd
  [exception RIP: generic_exec_single+130]
  RIP: 810dbe62  RSP: 880426f0da00  RFLAGS: 0202
  RAX: 0002  RBX: 880426f0d9d0  RCX: 0001
  RDX: 8180ad60  RSI:   RDI: 0286
  RBP: 880426f0da30   R8: 8180ad48   R9: 88042713bc68
  R10: 7fe7d1f2dbd0  R11: 0206  R12: 8804274bb000
  R13:   R14: 880407670280  R15: 
  ORIG_RAX: ff10  CS: 0010  SS: 0018
  #10 [880426f0da38] smp_call_function_single at 810dbf75
  #11 [880426f0dab0] smp_call_function_many at 810dc3a6
  #12 [880426f0db10] native_flush_tlb_others at 8105c8f7
  #13 [880426f0db38] flush_tlb_mm_range at 8105c9cb
  #14 [880426f0db68] pmdp_splitting_flush at 8105b80d
  #15 [880426f0db88] __split_huge_page at 811ac90b
  #16 [880426f0dc20] split_huge_page_to_list at 811acfb8
  #17 [880426f0dc48] __split_huge_page_pmd at 811ad956
  #18 [880426f0dcc8] unmap_page_range at 8117728d
  #19 [880426f0dda0] unmap_single_vma at 81177341
  #20 [880426f0ddd8] zap_page_range at 811784cd
  #21 [880426f0de90] sys_madvise at 81174fbf
  #22 [880426f0df80] system_call_fastpath at 8173196d
  RIP: 7fe7ca2cc647  RSP: 7fe7be9febf0  RFLAGS: 0293
  RAX: 001c  RBX: 8173196d  RCX: 
  RDX: 0004  RSI: 007fb000  RDI: 7fe7be1ff000
  RBP:    R8:    R9: 7fe7d1cd2738
  R10: 7fe7d1f2dbd0  R11: 0206  R12: 7fe7be9ff700
  R13: 7fe7be9ff9c0  R14:   R15: 
  ORIG_RAX: 001c  CS: 0033  SS: 002b

  [Fix]

  commit 9242b5b60df8b13b469bc6b7be08ff6ebb551ad3,
  Mitigates this issue if b6b8a1451fc40412c57d1 is applied (as in the case of 
the affected 3.13 distro kernel. However the issue can still occur in some 
cases.

  
  [Workaround]

  In order to avoid this issue, the workload needs to be pinned to CPUs
  such that the function always executes locally. For the nested VM
  case, this means the the L1 VM needs to have all vCPUs pinned to a
  unique CPU. This can be accomplished with the following (for 2 vCPUs):

  virsh vcpupin domain 0 0
  virsh vcpupin domain 1 1

  [Test Case]
  - Deploy openstack on openstack
  - Run tempest on L1 cloud
  - Check kernel log of L1 nova-compute nodes

  (Although this may not necessarily be related to nested KVM)
  Potentially related: https://lkml.org/lkml/2014/11/14/656

  Another test case is to do the following (on affected hardware):

  1) Create an L1 KVM VM with 2 vCPUs (single vCPU case doesn't reproduce)
  2) Create an L2 KVM VM inside the L1 VM with 1 vCPU
  3) Run something like 'stress -c 1 -m 1 -d 1 -t 1200' inside the L2 VM

  Sometimes this is sufficient to reproduce the issue, I've observed that 
running
  KSM in the L1 VM can agitate this issue (it calls native_flush_tlb_others).
  If this doesn't reproduce then you can do the following:
  4) Migrate the L2 vCPU randomly (via virsh vcpupin --live  OR tasksel) between
  L1 vCPUs until the hang occurs.

  --

  Original Description:

  When installing qemu-kvm on a VM, KSM is enabled.

  I have encountered this problem in trusty:$ lsb_release -a
  Distributor ID: Ubuntu
  Description:Ubuntu 14.04.1 LTS
  Release:14.04
  Codename:   trusty
  $ uname -a
  Linux juju-gema-machine-2 3.13.0-40-generic 

[Kernel-packages] [Bug 1441103] Re: CVE-2015-2922

2015-04-08 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Vivid)
   Status: New = Fix Committed

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

Title:
  CVE-2015-2922

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

[Kernel-packages] [Bug 1423343] Re: [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v

2015-04-02 Thread Andy Whitcroft
A couple of people pointed out that these builds have the tools but
the ancillary scripts and systemd configuration etc is all missing.
Turned out to be a bug in the test build system which was incorrectly
building the indep packages on the wrong architecture (which includes the
common packages), which in turn was exposing a bug in our packaging
which meant if you did that the contents got lost.  Anyhow, those are both
now fixed and I have built some new test builds which looks right to my eye.
 


Those are at the URL below (a new one for transparency):



http://people.canonical.com/~apw/lp1423343-2-vivid/ 



Let me know what you find.  Thanks.

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

Title:
  [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Following patches are missing from ubuntu vivid 15.04 compared to
  latest upstream (linux-next) , please include them in ubuntu vivid ,
  all the patches listed here are already upstream .

  /arch/x86/include/uapi/asm/hyperv.h

  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9e7827b5ea4ca93b4d864bc07c0fafb838d496b1

  /drivers/hv/hyperv_vmbus.h
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2

  drivers/hv/vmbus_drv.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=a45de93eb10ae6aec2c73d722562ab46092a
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d8a60e000c951f845d9a5fb3e67853e0e63a5659
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=90f3453585479d5beb75058da46eb573ced0e6ac
  5. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=302a3c0f2757ae1a3e7df3f9fa1f20e2214ab945
  6. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=b0209501dc7586cbfbf6d023f2dd3ce4621aff2c

  /drivers/hv/hv_snapshot.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8d9560ebcc6448472b3afe8f36f37d6b0de8f5a4
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=649142074d86afebe0505431a93957505d244dd6

  /drivers/hv/hv_kvp.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8d9560ebcc6448472b3afe8f36f37d6b0de8f5a4

  /drivers/hv/hv_fcopy.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d9b1652947c695d247b5e4603a16213ec55661ed

  /drivers/hv/channel.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67fae053bfc6e84144150e4c6c62670abb215c33
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d61031ee8df6214d58371a1cc36a0591e242fba0
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9f52a1630922bcdab75fc72e59ed58db8e164314

  /drivers/hv/channel_mgmt.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d7f2fbafb4f84306436277664cf28042beaf252a
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67fae053bfc6e84144150e4c6c62670abb215c33
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9c3a6f7e476fc4961297fc66b1177f9f8c8dd238
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=87712bf81dd092821c406ea3fb47a07222484a64
  5. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c3582a2c4d0baf1fa3955c8b3d3d61308df474c7

  /drivers/hv/hv_balloon.c
  1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=ab3de22bb4a3d4bda2d0ec8bebcb76a40f1cbf9b
  2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=22f88475b62ac826acae2f77c3e1bd9543e87b2a
  3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=79208c57da5311860f165b613c89b3f647e357cd
  4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=f6712238471a8afdbfcea482483fc121281292d8

  /tools/hv/hv_vss_daemon.c
  1. 

[Kernel-packages] [Bug 1434579] Re: Unable to install VirtualBox Guest Service in 15.04

2015-04-02 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
   Status: New = In Progress

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = Andy Whitcroft (apw)

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

Title:
  Unable to install VirtualBox Guest Service in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  It is not longer possible to select VirtualBox Guest Service in 15.04.
  The only options available are:

* Continue using a manually install driver
* Do not use the device

  The option 'Using x86 virtualisation solution - guest addition module'
  is no longer selectable. See the attached screen shot. This is from a
  fresh install of Ubuntu MATE 15.04 daily (20th March) and no drivers
  have been manually installed.

  In light of the Virtualbox issue where new installs on Virtualbox have
  a resolution of 640x480
  (https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1368784/)
  this is going to be a frustration for many users.

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

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


[Kernel-packages] [Bug 1434579] Re: Unable to install VirtualBox Guest Service in 15.04

2015-04-02 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
Milestone: None = ubuntu-15.04

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

Title:
  Unable to install VirtualBox Guest Service in 15.04

Status in linux package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  It is not longer possible to select VirtualBox Guest Service in 15.04.
  The only options available are:

* Continue using a manually install driver
* Do not use the device

  The option 'Using x86 virtualisation solution - guest addition module'
  is no longer selectable. See the attached screen shot. This is from a
  fresh install of Ubuntu MATE 15.04 daily (20th March) and no drivers
  have been manually installed.

  In light of the Virtualbox issue where new installs on Virtualbox have
  a resolution of 640x480
  (https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1368784/)
  this is going to be a frustration for many users.

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

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


[Kernel-packages] [Bug 1441106] Re: 3.19.0-12.12 brightness regression

2015-04-09 Thread Andy Whitcroft
*** This bug is a duplicate of bug 1440270 ***
https://bugs.launchpad.net/bugs/1440270

** This bug has been marked a duplicate of bug 1440270
   regression: backlight can't be adjusted on UX32VD with 3.19.0-12-generic 
kernel

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

Title:
  3.19.0-12.12 brightness regression

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I am seeing lack of brightness control in unity when using the -12.12
  kernel, booting back to -11.11 resolves the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-12-generic 3.19.0-12.12
  ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
  Uname: Linux 3.19.0-12-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  apw3666 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr  7 12:01:19 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=56f0e078-c76d-4cf9-a3ef-3b30e0c1a78b
  InstallationDate: Installed on 2013-06-20 (655 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130618)
  MachineType: Intel Corporation 2012 Client Platform
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-12-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash nomdmonddf nomdmonisw 
nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-12-generic N/A
   linux-backports-modules-3.19.0-12-generic  N/A
   linux-firmware 1.143
  SourcePackage: linux
  UpgradeStatus: Upgraded to vivid on 2013-11-10 (512 days ago)
  dmi.bios.date: 07/30/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: ACRVMBY1.86C.0094.P02.1207301240
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Latexo FFRD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrACRVMBY1.86C.0094.P02.1207301240:bd07/30/2012:svnIntelCorporation:pn2012ClientPlatform:pvrTobefilledbyO.E.M.:rvnIntelCorporation:rnLatexoFFRD:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct9:cvrToBeFilledByO.E.M.:
  dmi.product.name: 2012 Client Platform
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Intel Corporation

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

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


[Kernel-packages] [Bug 1438039] Re: Ubuntu14.04.1 kernel panics with enic driver throwing a NULL Pointer exception

2015-06-04 Thread Andy Whitcroft
** Also affects: linux (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

** Description changed:

  Steps to reproduce the bug:
  1. Install Ubuntu 14.04.1 on the Cisco M-series server.
  2. Run reboot test, OS will come up and go for graceful reboot continuously.
- 3. I am seeing kernel panic in 3 out of 4 Ubuntu machines . Don't know after 
how many iterations of reboot it happened. I checked the server 6 hours after 
starting the reboot test. 
+ 3. I am seeing kernel panic in 3 out of 4 Ubuntu machines . Don't know after 
how many iterations of reboot it happened. I checked the server 6 hours after 
starting the reboot test.
  4. Don't know whether this panic is happening while the OS was booting or 
while going for reboot.
  
  The bug has been root caused to the enic driver and a fix has been posted 
upstream.
  Please find below the details of the patch submitted upstream.
  
  4cfe878537cec0e9c0f84b93cc6aa9526f6942b5 enic: do tx cleanup in napi
  poll.
  
  This bug is submitted for the patch to be pulled in from upstream to
  Ubuntu's releases.
+ 
+ ===
+ break-fix: - 4cfe878537cec0e9c0f84b93cc6aa9526f6942b5

** Tags added: kernel-bug-break-fix

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

Title:
  Ubuntu14.04.1 kernel panics with   enic driver throwing a NULL Pointer
  exception

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

Bug description:
  Steps to reproduce the bug:
  1. Install Ubuntu 14.04.1 on the Cisco M-series server.
  2. Run reboot test, OS will come up and go for graceful reboot continuously.
  3. I am seeing kernel panic in 3 out of 4 Ubuntu machines . Don't know after 
how many iterations of reboot it happened. I checked the server 6 hours after 
starting the reboot test.
  4. Don't know whether this panic is happening while the OS was booting or 
while going for reboot.

  The bug has been root caused to the enic driver and a fix has been posted 
upstream.
  Please find below the details of the patch submitted upstream.

  4cfe878537cec0e9c0f84b93cc6aa9526f6942b5 enic: do tx cleanup in napi
  poll.

  This bug is submitted for the patch to be pulled in from upstream to
  Ubuntu's releases.

  ===
  break-fix: - 4cfe878537cec0e9c0f84b93cc6aa9526f6942b5

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

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


[Kernel-packages] [Bug 1460657] Re: possible infinite loop when parsing CDC headers

2015-06-04 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: Confirmed = Fix Committed

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

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

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

Title:
  possible infinite loop when parsing CDC headers

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

Bug description:
  Bug #1413992 's patch introduced a possible infinite loop.

  commit 0d3bba0287d4e284c3ec7d3397e81eec920d5e7e
  Author: Quentin Casasnovas quentin.casasno...@oracle.com
  Date:   Tue Apr 14 11:25:43 2015 +0200

  cdc-acm: prevent infinite loop when parsing CDC headers.

  Phil and I found out a problem with commit:

    7e860a6e7aa6 (cdc-acm: add sanity checks)

  It added some sanity checks to ignore potential garbage in CDC headers but
  also introduced a potential infinite loop.  This can happen at the first
  loop iteration (elength = 0 in that case) if the description isn't a
  DT_CS_INTERFACE or later if 'buffer[0]' is zero.

  It should also be noted that the wrong length was being added to 'buffer'
  in case 'buffer[1]' was not a DT_CS_INTERFACE descriptor, since elength 
was
  assigned after that check in the loop.

  A specially crafted USB device could be used to trigger this
  infinite loop.

  Fixes: 7e860a6e7aa6 (cdc-acm: add sanity checks)
  Signed-off-by: Phil Turnbull phil.turnb...@oracle.com
  Signed-off-by: Quentin Casasnovas quentin.casasno...@oracle.com
  CC: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
  CC: Oliver Neukum oneu...@suse.de
  CC: Adam Lee adam8...@gmail.com
  CC: sta...@vger.kernel.org
  Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org

  ===
  break-fix: 7e860a6e7aa62b337a61110430cd633db5b0d2dd 
0d3bba0287d4e284c3ec7d3397e81eec920d5e7e

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

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


[Kernel-packages] [Bug 1449005] Re: trim does not work with Samsung 840 EVO after firmware update (EXT0DB6Q)

2015-06-04 Thread Andy Whitcroft
*** This bug is a duplicate of bug 1338706 ***
https://bugs.launchpad.net/bugs/1338706

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

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

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

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

Title:
  trim does not work with Samsung 840 EVO after firmware update
  (EXT0DB6Q)

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

Bug description:
  Hi,
  after updating Samsung SSD 840 EVO to the latest firmware (EXT0DB6Q) the 
fstream command doesn't work anymore. Besides, there are a lot of file system 
errors and bad sectors reports. The problem is certainly caused by Samsung's 
firmware but I reported it as a bug because in Windows TRIM works normally 
after the upgrade. I have attached an image uploaded by a user who is 
experiencing the same problem. If you execute the command sudo fstrim / the  
console gets stuck. If you add that command in rc.local the boot is 
compromised. I really hope this problem could be solved.
  Thanks

  ===
  break-fix: - 6fc4d97a4987c5d247655a157a9377996626221a
  break-fix: - 9a9324d3969678d44b330e1230ad2c8ae67acf81

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

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


[Kernel-packages] [Bug 1438039] Re: Ubuntu14.04.1 kernel panics with enic driver throwing a NULL Pointer exception

2015-06-04 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: New = Confirmed

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

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

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

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

Title:
  Ubuntu14.04.1 kernel panics with   enic driver throwing a NULL Pointer
  exception

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

Bug description:
  Steps to reproduce the bug:
  1. Install Ubuntu 14.04.1 on the Cisco M-series server.
  2. Run reboot test, OS will come up and go for graceful reboot continuously.
  3. I am seeing kernel panic in 3 out of 4 Ubuntu machines . Don't know after 
how many iterations of reboot it happened. I checked the server 6 hours after 
starting the reboot test.
  4. Don't know whether this panic is happening while the OS was booting or 
while going for reboot.

  The bug has been root caused to the enic driver and a fix has been posted 
upstream.
  Please find below the details of the patch submitted upstream.

  4cfe878537cec0e9c0f84b93cc6aa9526f6942b5 enic: do tx cleanup in napi
  poll.

  This bug is submitted for the patch to be pulled in from upstream to
  Ubuntu's releases.

  ===
  break-fix: - 4cfe878537cec0e9c0f84b93cc6aa9526f6942b5

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

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


[Kernel-packages] [Bug 1457168] Re: [Hyper-V] kvp, vrss, fcopy daemons no longer in init

2015-06-04 Thread Andy Whitcroft
The fixes for LP#1405807 are now in trusty-proposed for both linux-lts-
utopic and -vivid, so if you could confirm the kernels there resolve the
issue for you, that would help a lot.

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

Title:
  [Hyper-V] kvp, vrss, fcopy daemons no longer in init

Status in linux-lts-utopic package in Ubuntu:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Confirmed

Bug description:
  hv-fcopy-daemon.conf hv-kvp-daemon.conf and hv-vss-daemon.conf are
  missing from /etc/init and therefore these critical daemons are no
  longer launched on Hyper-V installations that use linux-virtual-lts-
  utopic or other instances of the HWE kernel.

  Because Azure now uses the HWE kernel, in the generic 12.04 and 14.04
  images I see the file /etc/init/hv-kvp-daemon.conf, but executing this
  fails to start the service (because negotiation of these services is
  done in the first minute after an image is started) On the 12.04 image
  I can install the proper linux-tools-`uname -r` and linux-cloud-
  tools-`uname -r`, but it seems that perhaps the init script is not
  pointing to the correct binary.

  Normally /usr/sbin/hv_kvp_daemon is a wrapper to find
  /usr/sbin/hv_kvp_daemon-`uname -r`, but that latter file is never
  installed. On Ubuntu 12.04 I do see that /usr/lib/linux-lts-trusty-
  tools-3.13.0-51/hv_kvp_daemon is installed and works, but I'm not
  sure yet what's missing to get the upstart service working.

  Please correct the init scripts for the HWE kernels on 12.04 and
  14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-virtual-lts-utopic 3.16.0.37.29
  ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9
  Uname: Linux 3.16.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  Date: Wed May 20 11:00:57 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-04-09 (40 days ago)
  InstallationMedia: Ubuntu-Server 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1457168] Re: [Hyper-V] kvp, vrss, fcopy daemons no longer in init

2015-06-04 Thread Andy Whitcroft
I believe that this is the same issue reported in bug #1405807.  Fixes
for which we expect to be in the current kernels in trusty-proposed for
both linux-lts-utopic and linux-lts-vivid.

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

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

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

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

Title:
  [Hyper-V] kvp, vrss, fcopy daemons no longer in init

Status in linux-lts-utopic package in Ubuntu:
  Confirmed
Status in linux-lts-vivid package in Ubuntu:
  Confirmed

Bug description:
  hv-fcopy-daemon.conf hv-kvp-daemon.conf and hv-vss-daemon.conf are
  missing from /etc/init and therefore these critical daemons are no
  longer launched on Hyper-V installations that use linux-virtual-lts-
  utopic or other instances of the HWE kernel.

  Because Azure now uses the HWE kernel, in the generic 12.04 and 14.04
  images I see the file /etc/init/hv-kvp-daemon.conf, but executing this
  fails to start the service (because negotiation of these services is
  done in the first minute after an image is started) On the 12.04 image
  I can install the proper linux-tools-`uname -r` and linux-cloud-
  tools-`uname -r`, but it seems that perhaps the init script is not
  pointing to the correct binary.

  Normally /usr/sbin/hv_kvp_daemon is a wrapper to find
  /usr/sbin/hv_kvp_daemon-`uname -r`, but that latter file is never
  installed. On Ubuntu 12.04 I do see that /usr/lib/linux-lts-trusty-
  tools-3.13.0-51/hv_kvp_daemon is installed and works, but I'm not
  sure yet what's missing to get the upstart service working.

  Please correct the init scripts for the HWE kernels on 12.04 and
  14.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-virtual-lts-utopic 3.16.0.37.29
  ProcVersionSignature: Ubuntu 3.16.0-37.51~14.04.1-generic 3.16.7-ckt9
  Uname: Linux 3.16.0-37-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.10
  Architecture: amd64
  Date: Wed May 20 11:00:57 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-04-09 (40 days ago)
  InstallationMedia: Ubuntu-Server 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-meta-lts-utopic
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1418140] Re: CONFIG_DEFAULT_MMAP_MIN_ADDR needs to match on armhf and arm64 otherwise arm64 cannot run armhf binaries

2015-06-18 Thread Andy Whitcroft
** Also affects: linux (Ubuntu Vivid)
   Importance: Undecided
   Status: New

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

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

** Changed in: linux (Ubuntu Vivid)
 Assignee: (unassigned) = Andy Whitcroft (apw)

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

** Changed in: linux (Ubuntu)
Milestone: ubuntu-15.03 = None

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

Title:
  CONFIG_DEFAULT_MMAP_MIN_ADDR needs to match on armhf and arm64
  otherwise arm64 cannot run armhf binaries

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

Bug description:
  Attempting to run 32bit binaries on arm64 triggers applications to be
  Killed, as the CONFIG_DEFAULT_MMAP_MIN_ADDR used on armhf is not valid
  on arm64.  While this can be overriden via sysctl, the default should
  be sane.

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

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


[Kernel-packages] [Bug 1465998] Re: BUG in overlayfs when updating i386 wily chroot

2015-06-17 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
   Status: Confirmed = Triaged

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = Andy Whitcroft (apw)

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

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

Title:
  BUG in overlayfs when updating i386 wily chroot

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Noticed dpkg unexpectedly crashing when doing a dist-upgrade in a i386
  wily schroot on a amd64 host.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-55-generic 3.13.0-55.92
  ProcVersionSignature: Ubuntu 3.13.0-55.92-generic 3.13.11-ckt20
  Uname: Linux 3.13.0-55-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  smb3535 F pulseaudio
   /dev/snd/pcmC1D0c:   smb3535 F...m pulseaudio
   /dev/snd/controlC0:  smb3535 F pulseaudio
   /dev/snd/pcmC0D0p:   smb3535 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun 17 10:58:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=edf54dd5-2041-47a4-bbdf-da1d83d9bbb7
  InstallationDate: Installed on 2014-07-09 (342 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: MSI MS-7758
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-55-generic.efi.signed 
root=UUID=c2c13cd7-b945-4785-9b44-9b4007adb118 ro quiet splash nomdmonddf 
nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw 
vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-55-generic N/A
   linux-backports-modules-3.13.0-55-generic  N/A
   linux-firmware 1.127.12
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: ZH77A-G43 (MS-7758)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.10:bd10/29/2013:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZH77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7758
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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


[Kernel-packages] [Bug 1460657] Re: possible infinite loop when parsing CDC headers

2015-06-01 Thread Andy Whitcroft
** Description changed:

  Bug #1413992 's patch introduced a possible infinite loop.
  
  commit 0d3bba0287d4e284c3ec7d3397e81eec920d5e7e
  Author: Quentin Casasnovas quentin.casasno...@oracle.com
  Date:   Tue Apr 14 11:25:43 2015 +0200
  
- cdc-acm: prevent infinite loop when parsing CDC headers.
+ cdc-acm: prevent infinite loop when parsing CDC headers.
  
- Phil and I found out a problem with commit:
+ Phil and I found out a problem with commit:
  
-   7e860a6e7aa6 (cdc-acm: add sanity checks)
+   7e860a6e7aa6 (cdc-acm: add sanity checks)
  
- It added some sanity checks to ignore potential garbage in CDC headers but
- also introduced a potential infinite loop.  This can happen at the first
- loop iteration (elength = 0 in that case) if the description isn't a
- DT_CS_INTERFACE or later if 'buffer[0]' is zero.
+ It added some sanity checks to ignore potential garbage in CDC headers but
+ also introduced a potential infinite loop.  This can happen at the first
+ loop iteration (elength = 0 in that case) if the description isn't a
+ DT_CS_INTERFACE or later if 'buffer[0]' is zero.
  
- It should also be noted that the wrong length was being added to 'buffer'
- in case 'buffer[1]' was not a DT_CS_INTERFACE descriptor, since elength 
was
- assigned after that check in the loop.
+ It should also be noted that the wrong length was being added to 'buffer'
+ in case 'buffer[1]' was not a DT_CS_INTERFACE descriptor, since elength 
was
+ assigned after that check in the loop.
  
- A specially crafted USB device could be used to trigger this
+ A specially crafted USB device could be used to trigger this
  infinite loop.
  
- Fixes: 7e860a6e7aa6 (cdc-acm: add sanity checks)
- Signed-off-by: Phil Turnbull phil.turnb...@oracle.com
- Signed-off-by: Quentin Casasnovas quentin.casasno...@oracle.com
- CC: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
- CC: Oliver Neukum oneu...@suse.de
- CC: Adam Lee adam8...@gmail.com
- CC: sta...@vger.kernel.org
- Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org
+ Fixes: 7e860a6e7aa6 (cdc-acm: add sanity checks)
+ Signed-off-by: Phil Turnbull phil.turnb...@oracle.com
+ Signed-off-by: Quentin Casasnovas quentin.casasno...@oracle.com
+ CC: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
+ CC: Oliver Neukum oneu...@suse.de
+ CC: Adam Lee adam8...@gmail.com
+ CC: sta...@vger.kernel.org
+ Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org
+ 
+ ===
+ break-fix: 7e860a6e7aa62b337a61110430cd633db5b0d2dd 
0d3bba0287d4e284c3ec7d3397e81eec920d5e7e

** Tags added: kernel-bug-break-fix

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

Title:
  possible infinite loop when parsing CDC headers

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

Bug description:
  Bug #1413992 's patch introduced a possible infinite loop.

  commit 0d3bba0287d4e284c3ec7d3397e81eec920d5e7e
  Author: Quentin Casasnovas quentin.casasno...@oracle.com
  Date:   Tue Apr 14 11:25:43 2015 +0200

  cdc-acm: prevent infinite loop when parsing CDC headers.

  Phil and I found out a problem with commit:

    7e860a6e7aa6 (cdc-acm: add sanity checks)

  It added some sanity checks to ignore potential garbage in CDC headers but
  also introduced a potential infinite loop.  This can happen at the first
  loop iteration (elength = 0 in that case) if the description isn't a
  DT_CS_INTERFACE or later if 'buffer[0]' is zero.

  It should also be noted that the wrong length was being added to 'buffer'
  in case 'buffer[1]' was not a DT_CS_INTERFACE descriptor, since elength 
was
  assigned after that check in the loop.

  A specially crafted USB device could be used to trigger this
  infinite loop.

  Fixes: 7e860a6e7aa6 (cdc-acm: add sanity checks)
  Signed-off-by: Phil Turnbull phil.turnb...@oracle.com
  Signed-off-by: Quentin Casasnovas quentin.casasno...@oracle.com
  CC: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
  CC: Oliver Neukum oneu...@suse.de
  CC: Adam Lee adam8...@gmail.com
  CC: sta...@vger.kernel.org
  Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org

  ===
  break-fix: 7e860a6e7aa62b337a61110430cd633db5b0d2dd 
0d3bba0287d4e284c3ec7d3397e81eec920d5e7e

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

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


[Kernel-packages] [Bug 1460657] Re: possible infinite loop when parsing CDC headers

2015-06-01 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: New = Confirmed

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

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

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

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

Title:
  possible infinite loop when parsing CDC headers

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

Bug description:
  Bug #1413992 's patch introduced a possible infinite loop.

  commit 0d3bba0287d4e284c3ec7d3397e81eec920d5e7e
  Author: Quentin Casasnovas quentin.casasno...@oracle.com
  Date:   Tue Apr 14 11:25:43 2015 +0200

  cdc-acm: prevent infinite loop when parsing CDC headers.

  Phil and I found out a problem with commit:

    7e860a6e7aa6 (cdc-acm: add sanity checks)

  It added some sanity checks to ignore potential garbage in CDC headers but
  also introduced a potential infinite loop.  This can happen at the first
  loop iteration (elength = 0 in that case) if the description isn't a
  DT_CS_INTERFACE or later if 'buffer[0]' is zero.

  It should also be noted that the wrong length was being added to 'buffer'
  in case 'buffer[1]' was not a DT_CS_INTERFACE descriptor, since elength 
was
  assigned after that check in the loop.

  A specially crafted USB device could be used to trigger this
  infinite loop.

  Fixes: 7e860a6e7aa6 (cdc-acm: add sanity checks)
  Signed-off-by: Phil Turnbull phil.turnb...@oracle.com
  Signed-off-by: Quentin Casasnovas quentin.casasno...@oracle.com
  CC: Sergei Shtylyov sergei.shtyl...@cogentembedded.com
  CC: Oliver Neukum oneu...@suse.de
  CC: Adam Lee adam8...@gmail.com
  CC: sta...@vger.kernel.org
  Signed-off-by: Greg Kroah-Hartman gre...@linuxfoundation.org

  ===
  break-fix: 7e860a6e7aa62b337a61110430cd633db5b0d2dd 
0d3bba0287d4e284c3ec7d3397e81eec920d5e7e

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

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


[Kernel-packages] [Bug 1438501] Re: CVE-2014-9710

2015-06-01 Thread Andy Whitcroft
** Changed in: linux (Ubuntu Trusty)
   Status: New = Fix Committed

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

Title:
  CVE-2014-9710

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

[Kernel-packages] [Bug 1469240] Re: Please ship dm-service-time in multipath-modules

2015-07-01 Thread Andy Whitcroft
** Changed in: linux (Ubuntu)
   Status: In Progress = Fix Committed

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

Title:
  Please ship dm-service-time in multipath-modules

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  multipath-tools 0.5.0 has changed the default path selector algorithm
  from round-robin to service-time.

  In the interest of properly handling the transition, I'd like for
  multipath-modules to ship *both* dm-round-robin and dm-service-time,
  so that we don't need to coordinate landing a kernel with multipath-
  tools, and avoid breakage.

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

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


[Kernel-packages] [Bug 1449678] Re: (Vivid) zram-config 0.3 Job for zram-config.service failed

2015-06-29 Thread Andy Whitcroft
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  (Vivid) zram-config 0.3 Job for zram-config.service failed

Status in linux package in Ubuntu:
  New
Status in zram-config package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  New
Status in zram-config source package in Vivid:
  Fix Committed

Bug description:
  [Impact]
   * People using some non English locale, zram devices are not loaded
   * The service fails to stop and unloading zram module as well

  //who wrote this? The impact is probably for all languages including English. 
The new version works : provided zram module is blacklisted to avoid being 
loaded during boot! See my next comment which will be #13. 
  Thanks, Mélodie

  [Test Case]
   * Install the new zram-config package
   * Reboot and check that the zram devices are created:
  $ swapon -s
  - returns some zram devices
   * $ sudo systemctl status -l zram-config.service
  - no error
   * Stop the service:
  $ sudo systemctl stop zram-config.service
   * $ sudo systemctl status -l zram-config.service
  - no error
   * swapon -s
  - no more zram device listed

  [Regression Potential]
   * Services loading change may impact English-local user. However, the fix 
has already been confirmed to be working on wily.
   * Stopping the service was already failing on unloading the module, so no 
additional regression is possible there.

  
  Hi,

  While testing how zram-config is going in Ubuntu Vivid, I meet with
  error while doing restart and or stop/start.

  It seems to stop fine but throws an error when starting again or
  performing a restart.

  I have installed zram-config 0.3 just today and haven't rebooted yet.
  The CPU is AMD Athlon(tm) II X2 260 Processor

  As stated in bug #1449665 there is one block device created:

  $ cat /proc/swaps
  Filename  TypeSizeUsedPriority
  /dev/zram0  partition 947216  0   5
  $

  Here:
  $ sudo systemctl stop zram-config
  $ cat /proc/swaps
  Filename  TypeSizeUsedPriority
  /dev/zram0  partition 947216  0   5
  $

  after the stop, the prompt is back without error, but it has done
  nothing.

  With restart:
  $ sudo systemctl restart zram-config
  Job for zram-config.service failed. See systemctl status 
zram-config.service and journalctl -xe for details.
  $

  When invoking the suggested commands:
  
  $ LANG=C systemctl status zram-config.service -l
  * zram-config.service - Initializes zram swaping
     Loaded: loaded (/lib/systemd/system/zram-config.service; enabled; vendor 
preset: enabled)
     Active: failed (Result: exit-code) since Tue 2015-04-28 19:34:37 CEST; 
2min 7s ago
    Process: 744 ExecStart=/usr/bin/init-zram-swapping (code=exited, status=255)
   Main PID: 744 (code=exited, status=255)

  Apr 28 19:34:37 bento64 init-zram-swapping[744]: sh: echo: I/O error
  Apr 28 19:34:37 bento64 init-zram-swapping[744]: mkswap: error: /dev/zram0 is 
mounted; will not make swapspace
  Apr 28 19:34:37 bento64 init-zram-swapping[744]: swapon: /dev/zram0 : échec 
de swapon: Périphérique ou ressource occupé
  Apr 28 19:34:37 bento64 init-zram-swapping[744]: /usr/bin/init-zram-swapping: 
21: /usr/bin/init-zram-swapping: cannot create /sys/block/zram1/disksize: 
Directory nonexistent
  Apr 28 19:34:37 bento64 init-zram-swapping[744]: /dev/zram1: Aucun fichier ou 
dossier de ce type
  Apr 28 19:34:37 bento64 init-zram-swapping[744]: swapon: stat failed 
/dev/zram1: Aucun fichier ou dossier de ce type
  Apr 28 19:34:37 bento64 systemd[1]: zram-config.service: main process exited, 
code=exited, status=255/n/a
  Apr 28 19:34:37 bento64 systemd[1]: Failed to start Initializes zram swaping.
  Apr 28 19:34:37 bento64 systemd[1]: Unit zram-config.service entered failed 
state.
  Apr 28 19:34:37 bento64 systemd[1]: zram-config.service failed.
  $
  

  
  -- Unit zram-config.service has begun starting up.
  Apr 28 19:34:37 bento64 audit[781]: audit-1107 pid=781 uid=102 
auid=4294967295 ses=4294967295 msg='apparmo
   exe=/usr/bin/dbus-daemon sauid=102 
hostname=? addr=? terminal=?'
  Apr 28 19:34:37 bento64 init-zram-swapping[744]: sh: echo: I/O error
  Apr 28 19:34:37 bento64 kernel: zram: Cannot change disksize for initialized 
device
  Apr 28 19:34:37 bento64 init-zram-swapping[744]: mkswap: error: /dev/zram0 is 
mounted; will not make swapspa
  Apr 28 19:34:37 bento64 init-zram-swapping[744]: swapon: /dev/zram0C2A0: 
C3A9chec de swapon: PC3
  Apr 28 19:34:37 bento64 init-zram-swapping[744]: /usr/bin/init-zram-swapping: 
21: /usr/bin/init-zram-swappin
  Apr 28 19:34:37 bento64 

[Kernel-packages] [Bug 1470091] [NEW] update for V3 kernel bits and improved multiple fan slice support

2015-06-30 Thread Andy Whitcroft
Public bug reported:

Fan V2 to V3 transition plan


Currently we have V2 Fan kernel patches paired with an
/etc/defaults/ubuntu-fan based single fan mapping setup.  We want to
transition to both V3 Fan kernel patches with fanctl based configuration
allowing multiple fans to be configured together.

The new V3 kernel bits fix a significant limitation wherein we could not
have multiple slices of different overlay address ranges on the same local
address.  This update introduces an incompatible kernel interface against
a different device.  The new functionality is a full superset of the old.

The new V3 kernel bits require updated iproute2 patches to handle the
new netlink form carrying the expanded map forms.

In order to manage multiple Fan devices we are updating ubuntu-fan to use
the new fanctl command line tool and a new fan specific configuration file.

This plan assumes we are not wedded to the kernel interface, that the
supported API is the /etc/defaults/ubuntu-fan fan configuration.

Considerations
==
We are unable to depend on kernel features, as we have no meaninful
dependencies to kernel versions.

We need to change the primary configuration file and format for ubuntu-fan
package to allow multiple slices of multiple fans to be configured
together.

We have V2 kernel bits in the wild.  We have V2 iproute in the wild.

Steps
=
1) update fanctl to support both the V2 and V3 kernel interfaces as we cannot
   depend on a kernel version meaningfully.
2) update iproute2 to support configuring both V2 and V3 kernel interfaces.
3) update ubuntu-fan with the updated fanctl, supporting migration
   of the /etc/default/fan contents to /etc/network/fan (or directly
   handling that form), and depending on the updated iproute2 bits.
4) release updated iproute2 bits.
5) release updated ubuntu-fan bits.
6) release updated kernel bits (V3 kernel module).

Testing
===
Need to test old and new kernels with old and new ubuntu-fan levels.
We obviously do not expect the old userspace to work with the new kernels,
but it should fail obviously.

** Affects: iproute2 (Ubuntu)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

** Affects: ubuntu-fan (Ubuntu)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

** Affects: iproute2 (Ubuntu Vivid)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

** Affects: linux (Ubuntu Vivid)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

** Affects: ubuntu-fan (Ubuntu Vivid)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

** Affects: iproute2 (Ubuntu Wily)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

** Affects: linux (Ubuntu Wily)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

** Affects: ubuntu-fan (Ubuntu Wily)
 Importance: High
 Assignee: Andy Whitcroft (apw)
 Status: In Progress

** Changed in: ubuntu-fan (Ubuntu)
   Status: New = In Progress

** Changed in: ubuntu-fan (Ubuntu)
   Importance: Undecided = High

** Changed in: ubuntu-fan (Ubuntu)
 Assignee: (unassigned) = Andy Whitcroft (apw)

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

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

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

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

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

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

** Changed in: iproute2 (Ubuntu)
 Assignee: (unassigned) = Andy Whitcroft (apw)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) = Andy Whitcroft (apw)

** Also affects: linux (Ubuntu Wily)
   Importance: High
 Assignee: Andy Whitcroft (apw)
   Status: In Progress

** Also affects: iproute2 (Ubuntu Wily)
   Importance: High
 Assignee: Andy Whitcroft (apw)
   Status: In Progress

** Also affects: ubuntu-fan (Ubuntu Wily)
   Importance: High
 Assignee: Andy Whitcroft (apw)
   Status: In Progress

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

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

** Also affects: ubuntu-fan (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: iproute2 (Ubuntu Vivid)
   Status: New = Triaged

** Changed in: iproute2 (Ubuntu Vivid)
   Importance: Undecided = High

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

** Changed in: iproute2 (Ubuntu Vivid)
 Assignee: (unassigned) = Andy Whitcroft (apw)

** Changed in: linux (Ubuntu Vivid

<    5   6   7   8   9   10   11   12   13   14   >